diff --git a/marked/G/T-REC-G.1010-200111-I_PDF-E/raw.md b/marked/G/T-REC-G.1010-200111-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..edc7039ddfcc5c215cdbb9be4b75693d71e20cff --- /dev/null +++ b/marked/G/T-REC-G.1010-200111-I_PDF-E/raw.md @@ -0,0 +1,400 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the center. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.1010** + +(11/2001) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Quality of service and performance + +--- + +**End-user multimedia QoS categories** + +ITU-T Recommendation G.1010 + +--- + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TESTING EQUIPMENTS | G.500–G.599 | +| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 | +| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | +| QUALITY OF SERVICE AND PERFORMANCE | G.1000–G.1999 | +| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 | +| DIGITAL TERMINAL EQUIPMENTS | G.7000–G.7999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **End-user multimedia QoS categories** + +## **Summary** + +This Recommendation defines a model for multimedia Quality of Service (QoS) categories from an end-user viewpoint. By considering user expectations for a range of multimedia applications, eight distinct categories are identified, based on tolerance to information loss and delay. It is intended that these categories form the basis for defining realistic QoS classes for underlying transport networks, and associated QoS control mechanisms. + +###### **Source** + +ITU-T Recommendation G.1010 was prepared by ITU-T Study Group 12 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 November 2001. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2002 + +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 | User-driven performance requirements ..... | 1 | +| 4 | Key parameters impacting the user ..... | 2 | +| 4.1 | Delay..... | 2 | +| 4.2 | Delay variation ..... | 2 | +| 4.3 | Information loss..... | 2 | +| 5 | Performance considerations for different applications..... | 2 | +| 5.1 | Audio ..... | 2 | +| 5.1.1 | Conversational voice ..... | 2 | +| 5.1.2 | Voice messaging ..... | 3 | +| 5.1.3 | Streaming audio..... | 3 | +| 5.2 | Video ..... | 3 | +| 5.2.1 | Videophone ..... | 3 | +| 5.2.2 | One-way video ..... | 3 | +| 5.3 | Data..... | 3 | +| 5.3.1 | Web-browsing ..... | 4 | +| 5.3.2 | Bulk data ..... | 4 | +| 5.3.3 | High-priority transaction services (E-commerce) ..... | 4 | +| 5.3.4 | Command/control..... | 4 | +| 5.3.5 | Still image ..... | 4 | +| 5.3.6 | Interactive games..... | 4 | +| 5.3.7 | Telnet..... | 4 | +| 5.3.8 | E-mail (server access) ..... | 4 | +| 5.3.9 | Instant messaging ..... | 4 | +| 5.4 | Background applications ..... | 5 | +| 5.4.1 | Fax..... | 5 | +| 5.4.2 | Low priority transaction services ..... | 5 | +| 5.4.3 | Email (server-to-server) ..... | 5 | +| 5.4.4 | Usenet..... | 5 | +| 6 | Classification of performance requirements into end-user Quality of Service categories..... | 5 | +| | Appendix I – Performance targets ..... | 8 | +| | Appendix II – Bibliography ..... | 10 | + + + +## **End-user multimedia QoS categories** + +# **1 Scope** + +The intent of this Recommendation is to provide guidance on the key factors that influence Quality of Service (QoS) from the perspective of the end-user. By considering a range of applications involving the media of voice, video, image and text, and the parameters that govern end-user satisfaction for these applications, a broad classification of end-user QoS categories is determined. It is intended that these categories be used as the basis for deriving realistic QoS classes and associated QoS control mechanisms for the underlying transport networks. + +# **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. + +NOTE – 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 F.700 (2000), *Framework Recommendation for multimedia services*. +- [2] ITU-T Recommendation G.131 (1996), *Control of talker echo*. +- [3] ITU-T Recommendation G.114 (2000), *One-way transmission time*. +- [4] ETSI TS 101329-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*. + +# **3 User-driven performance requirements** + +A major challenge for emerging wireline and wireless IP-based networks is to provide adequate Quality of Service (QoS) for different services. To do this requires a detailed knowledge of the performance requirements for particular services and applications. The starting point for deriving these performance requirements must be the user. + +A typical user is not concerned with how a particular service is implemented. However, the user is interested in comparing the same service offered by different providers in terms of universal, user-oriented performance parameters. This implies that performance should be expressed by parameters that: + +- Take into account all aspects of the service from the user's point of view; +- Focus on user-perceivable effects, rather than their causes within the network; +- Are independent of the specific network architecture or technology; +- Can be objectively or subjectively measured at the service access point; +- Can be easily related to network performance parameters; + +- Can be assured to a user by the service providers(s). + +# **4 Key parameters impacting the user** + +## **4.1 Delay** + +Delay manifests itself in a number of ways, including the time taken to establish a particular service from the initial user request and the time to receive specific information once the service is established. Delay has a very direct impact on user satisfaction depending on the application, and includes delays in the terminal, network, and any servers. Note that from a user point of view, delay also takes into account the effect of other network parameters such as throughput. + +## **4.2 Delay variation** + +Delay variation is generally included as a performance parameter since it is very important at the transport layer in packetised data systems due to the inherent variability in arrival times of individual packets. However, services that are highly intolerant of delay variation will usually take steps to remove (or at least significantly reduce) the delay variation by means of buffering, effectively eliminating delay variation as perceived at the user level (although at the expense of adding additional fixed delay). + +## **4.3 Information loss** + +Information loss has a very direct effect on the quality of the information finally presented to the user, whether it be voice, image, video or data. In this context, information loss is not limited to the effects of bit errors or packet loss during transmission, but also includes the effects of any degradation introduced by media coding for more efficient transmission (e.g. the use of low bit-rate speech codecs for voice). + +# **5 Performance considerations for different applications** + +## **5.1 Audio** + +A general classification of audio into five levels of quality, and a mapping to various services, is given in [1]. More specific details are given below. + +### **5.1.1 Conversational voice** + +Requirements for conversational voice are heavily influenced by one-way delay. In fact, there are two distinct effects of delay. The first is the creation of echo in conjunction with two-wire to 4-wire conversions or even acoustic coupling in a terminal. This begins to cause increasing degradation to voice quality for delays of the order of tens of milliseconds, and echo control measures must be taken at this point (provision of echo cancellers etc [2]). The second effect occurs when the delay increases to a point where it begins to impact conversational dynamics, i.e. the delay in the other party responding becomes noticeable. This occurs for delays of the order of several hundred milliseconds [3]. + +However, the human ear is highly intolerant of short-term delay variation (jitter). As a practical matter, for all voice services, delay variation due to variability in incoming packet arrival times must be removed with a de-jitterizing buffer. + +Requirements for information loss are influenced by the fact that the human ear is tolerant to a certain amount of distortion of a speech signal. In IP-based transmission systems a prime source of voice quality degradation is due to the use of low bit-rate speech compression codecs and their performance under conditions of packet loss. + +### **5.1.2 Voice messaging** + +Requirements for information loss are essentially the same as for conversational voice (i.e. dependent on the speech coder), but a key difference here is that there is more tolerance for delay since there is no direct conversation involved. The main issue, therefore becomes one of how much delay can be tolerated between the user issuing a command to replay a voice message and the actual start of the audio. There is no precise data on this, but based on studies related to the acceptability of stimulus-response delay for telecommunications services, a delay of the order of a few seconds seems reasonable for this application. In fact, a distinction is possible between recording and playback, in that user reaction to playback is likely to be the more stringent requirement. + +### **5.1.3 Streaming audio** + +Streaming audio is expected to provide better quality than conventional telephony, and requirements for information loss in terms of packet loss will be correspondingly tighter. However, as with voice messaging, there is no conversational element involved and delay requirements for the audio stream itself can be relaxed, even more so than for voice-messaging, although control commands must be dealt with appropriately (see 5.3.4). + +## **5.2 Video** + +A general classification of video into six levels of quality, and a mapping to various services, is given in [1]. More specific details are given below. + +### **5.2.1 Videophone** + +Videophone as used here implies a full-duplex system, carrying both video and audio and intended for use in a conversational environment. As such, in principle the same delay requirements as for conversational voice will apply, i.e. no echo and minimal effect on conversational dynamics, with the added requirement that the audio and video must be synchronised within certain limits to provide "lip-synch". + +Once again, the human eye is tolerant to some loss of information, so that some degree of packet loss is acceptable depending on the specific video coder and amount of error protection used. It is expected that the latest MPEG-4 video codecs will provide acceptable video quality with frame erasure rates up to about 1%. + +### **5.2.2 One-way video** + +The main distinguishing feature of one-way video is that there is no conversational element involved, meaning that the delay requirement will not be so stringent, and can follow that of streaming audio. + +Taking into account the above considerations, performance targets for audio and video applications are shown in Table I.1. + +## **5.3 Data** + +From a user point of view, a prime requirement for any data transfer application is to guarantee essentially zero loss of information. At the same time, delay variation is not generally noticeable to the user, although there needs to be a limit on synchronisation between media streams in a multimedia session (e.g. audio in conjunction with a white-board presentation). The different applications therefore tend to distinguish themselves on the basis of the delay which can be tolerated by the end-user from the time the source content is requested until it is presented to the user. + +### **5.3.1 Web-browsing** + +In this category we refer to retrieving and viewing the HTML component of a Web page, other components e.g. images, audio/video clips are dealt with under their separate categories. From the user point of view, the main performance factor is how quickly a page appears after it has been requested. Delays of several seconds are acceptable, but not more than about 10 seconds. + +### **5.3.2 Bulk data** + +This category includes file transfers, and is clearly influenced by the size of the file. As long as there is an indication that the file transfer is proceeding, it is reasonable to assume somewhat longer tolerance to delay than for a single Web-page. + +### **5.3.3 High-priority transaction services (E-commerce)** + +The main performance requirement here is to provide a sense of immediacy to the user that the transaction is proceeding smoothly, and a delay of no more than a few seconds is desirable. + +### **5.3.4 Command/control** + +Clearly, command/control implies very tight limits on allowable delay, much less than a second. Note that a key differentiator from conversational voice and video services with similar low delay requirements is the zero tolerance for information loss. + +### **5.3.5 Still image** + +This category includes a variety of encoding formats, some of which may be tolerant to information loss since they will be viewed by a human eye. However, given that even single bit errors can cause large disturbances in other still image formats, it is argued that this category should in general have zero information loss. However, delay requirements for still image transfer are not stringent and may be comparable to that for bulk data transfer, given that the image tends to be built up as it is being received, which provides an indication that data transfer is proceeding. + +### **5.3.6 Interactive games** + +Requirements for interactive games are obviously very dependent on the specific game, but it is clear that demanding applications will require very short delays of the order of a fraction of a second, consistent with demanding interactive applications. + +### **5.3.7 Telnet** + +Telnet is included here with a requirement for a short delay of a fraction of a second in order to provide essentially instantaneous character echo-back. + +### **5.3.8 E-mail (server access)** + +E-mail is generally thought to be a store and forward service which, in principle, can tolerate delays of several minutes or even hours. However, it is important to differentiate between communications between the user and the local email server and server, to server transfer. When the user communicates with the local mail server, there is an expectation that the mail will be transferred within a few seconds. + +### **5.3.9 Instant messaging** + +Instant messaging primarily relates to text, but can also include audio, video and image. In any case, despite the name, it is not a real-time communication in the sense of conversational voice, and delays of several seconds are acceptable. + +## **5.4 Background applications** + +In principle, the only requirement for applications in this category is that information should be delivered to the user essentially error free. However, there is still a delay constraint, since data is effectively useless if it is received too late for any practical purpose. + +### **5.4.1 Fax** + +Fax is included in this category since it is not normally intended to be an accompaniment to highly interactive real-time communication. Nevertheless, for so-called "real-time" fax there is an expectation in most business scenarios that a fax will be received within about 30 seconds. Delay for store and forward fax can be much higher. Note that fax does not require zero information loss. + +### **5.4.2 Low priority transaction services** + +An example in this category is Short Message Service (SMS). 10s of seconds are an acceptable delivery delay value. + +### **5.4.3 Email (server-to-server)** + +This category is included for completeness, since as mentioned earlier, the prime interest in email is in the access time. + +### **5.4.4 Usenet** + +Usenet is a world-wide distributed discussion system. It consists of a set of "newsgroups" with names that are classified hierarchically by subject. "Articles" or "messages" are "posted" to these newsgroups by people on computers with the appropriate software. These articles are then broadcast to other interconnected computer systems via a wide variety of networks. This is a very low priority service, with corresponding relaxed delay requirements. However, it is desirable that messages are received by the user in the order that they are posted, to avoid seeing a reply prior to the original message. + +Taking into account the above considerations, performance targets for data applications are summarised in Table I.2. + +# **6 Classification of performance requirements into end-user Quality of Service categories** + +Based on the target performance requirements identified in Appendix I, the various applications can be mapped onto axes of packet loss and one-way delay as shown in Figure 1. The size and shape of the boxes provide a general indication of the limit of delay and information loss tolerable for each application class. + +![Figure 1/G.1010 – Mapping of user-centric QoS requirements. A graph showing Packet Loss (0% to 5%) on the Y-axis and Delay (100 ms to 100 s) on the X-axis. The graph is divided into four vertical regions: Conversational voice and video (100 ms), Voice/video messaging (1 s), Streaming audio/video (10 s), and Fax (100 s). Below the X-axis, four corresponding application types are listed: Command/control (e.g. Telnet, Interactive games), Transactions (e.g. E-commerce, Web-browsing, E-mail access), Messaging, Downloads (e.g. FTP, still image), and Background (e.g. Usenet).](36ac3e730a00d3f42d3400f5709f641a_img.jpg) + +Figure 1/G.1010 – Mapping of user-centric QoS requirements. A graph showing Packet Loss (0% to 5%) on the Y-axis and Delay (100 ms to 100 s) on the X-axis. The graph is divided into four vertical regions: Conversational voice and video (100 ms), Voice/video messaging (1 s), Streaming audio/video (10 s), and Fax (100 s). Below the X-axis, four corresponding application types are listed: Command/control (e.g. Telnet, Interactive games), Transactions (e.g. E-commerce, Web-browsing, E-mail access), Messaging, Downloads (e.g. FTP, still image), and Background (e.g. Usenet). + +**Figure 1/G.1010 – Mapping of user-centric QoS requirements** + +It can be seen that there are eight distinct groupings which encompass the range of applications identified. Within these eight groupings there is a primary segregation between applications that can tolerate some information loss and those that can not tolerate any information loss at all, and four general areas of delay tolerance. + +This mapping can be formalised in Figure 2, to provide a recommended model for end-user QoS categories, where the four areas of delay are given names chosen to illustrate the type of user interaction involved. Of course, it is possible that each category could be subdivided into further categories to provide a range of quality levels for a specific service, as has been done for conversational voice in ETSI TS 101329-2 [4]. + +| | | | | | +|----------------|--------------------------------------------------|------------------------------------------------------------|----------------------------------------------|---------------------------------------| +| Error tolerant | Conversational voice and video | Voice/video messaging | Streaming audio and video | Fax | +| | Command/control (e.g. Telnet, interactive games) | Transactions (e.g. E-commerce, WWW browsing, Email access) | Messaging, Downloads (e.g. FTP, still image) | Background (e.g. Usenet) | +| | Interactive
(delay <<1 s) | Responsive
(delay ~2 s) | Timely
(delay ~10 s) | Non-critical
(delay >>10 s) | + +T1213060-02 + +**Figure 2/G.1010 – Model for user-centric QoS categories** + +Several useful features of this model are: + +- 1) The model is based on end-to-end user perception of impairments and is therefore not dependent on any specific technology for its validity. This feature means that the model can be applied regardless of the underlying transport technology (IP, ATM, wireline, wireless etc). +- 2) The model provides an indication of the upper and lower boundaries for applications to be perceived as essentially acceptable to the user. Exceed an upper boundary (in loss or delay) and the service will be considered unsatisfactory; exceed a lower boundary, and the service will still be considered acceptable but may be wasteful from a network resource point of view because the service is using unnecessary resources. +- 3) The model provides a simple means of determining whether a bearer channel qualifies to carry a given application's data. For example, a channel with one-way delay of 1 second cannot support effective, natural real-time communication such as voice and Telnet. Furthermore, even if the one-way delay were reduced to 100 ms, Telnet would still be compromised if there were any information loss: loss of a single character would be conspicuous. +- 4) The model shows how the underlying impairments of information loss and delay can be grouped appropriately, without implying that one class is "better" than another (as in categorisations that use Gold, Silver, etc.). This can be used as the basis for deriving realistic and meaningful network QoS classes for differentiating service performance. +- 5) Note that the particular applications cited are exemplars rather than exhaustive. Other applications can be located in the schema by their similarity to these exemplars. + +# APPENDIX I + +## Performance targets + +Based on information in the Bibliography (Appendix II), Table I.1 provides an indication of suitable performance targets for audio and video applications. + +**Table I.1/G.1010 – Performance targets for audio and video applications** + +| Medium | Application | Degree of symmetry | Typical data rates | Key performance parameters and target values | | | | +|--------|------------------------------|--------------------|------------------------|------------------------------------------------------|-----------------|------------------------------|--------------------| +| | | | | One-way delay | Delay variation | Information loss (Note 2) | Other | +| Audio | Conversational voice | Two-way | 4-64 kbit/s | <150 ms preferred (Note 1)
<400 ms limit (Note 1) | < 1 ms | < 3% packet loss ratio (PLR) | | +| Audio | Voice messaging | Primarily one-way | 4-32 kbit/s | < 1 s for playback
< 2 s for record | < 1 ms | < 3% PLR | | +| Audio | High quality streaming audio | Primarily one-way | 16-128 kbit/s (Note 3) | < 10 s | << 1 ms | < 1% PLR | | +| Video | Videophone | Two-way | 16-384 kbit/s | < 150 ms preferred (Note 4)
<400 ms limit | | < 1% PLR | Lip-synch: < 80 ms | +| Video | One-way | One-way | 16-384 kbit/s | < 10 s | | < 1% PLR | | + +NOTE 1 – Assumes adequate echo control. +NOTE 2 – Exact values depend on specific codec, but assumes use of a packet loss concealment algorithm to minimise effect of packet loss. +NOTE 3 – Quality is very dependent on codec type and bit-rate. +NOTE 4 – These values are to be considered as long-term target values which may not be met by current technology. + +Based on information in the Bibliography (Appendix II), Table I.2 provides an indication of suitable performance targets for data applications. + +**Table I.2/G.1010 – Performance targets for data applications** + +| Medium | Application | Degree of symmetry | Typical amount of data | Key performance parameters and target values | | | +|--------|-----------------------------------------------------------|----------------------|------------------------|-------------------------------------------------|-----------------|-----------------------| +| | | | | One-way delay (Note) | Delay variation | Information loss | +| Data | Web-browsing – HTML | Primarily one-way | ~10 KB | Preferred < 2 s /page
Acceptable < 4 s /page | N.A. | Zero | +| Data | Bulk data transfer/retrieval | Primarily one-way | 10 KB-10 MB | Preferred < 15 s
Acceptable < 60 s | N.A. | Zero | +| Data | Transaction services – high priority e.g. e-commerce, ATM | Two-way | < 10 KB | Preferred < 2 s
Acceptable < 4 s | N.A. | Zero | +| Data | Command/control | Two-way | ~ 1 KB | < 250 ms | N.A. | Zero | +| Data | Still image | One-way | < 100 KB | Preferred < 15 s
Acceptable < 60 s | N.A. | Zero | +| Data | Interactive games | Two-way | < 1 KB | < 200 ms | N.A. | Zero | +| Data | Telnet | Two-way (asymmetric) | < 1 KB | < 200 ms | N.A. | Zero | +| Data | E-mail (server access) | Primarily one-way | < 10 KB | Preferred < 2 s
Acceptable < 4 s | N.A. | Zero | +| Data | E-mail (server to server transfer) | Primarily one-way | < 10 KB | Can be several minutes | N.A. | Zero | +| Data | Fax ("real-time") | Primarily one-way | ~ 10 KB | < 30 s/page | N.A. | <10 -6 BER | +| Data | Fax (store & forward) | Primarily one-way | ~ 10 KB | Can be several minutes | N.A. | <10 -6 BER | +| Data | Low priority transactions | Primarily one-way | < 10 KB | < 30 s | N.A. | Zero | +| Data | Usenet | Primarily one-way | Can be 1 MB or more | Can be several minutes | N.A. | Zero | + +NOTE – In some cases, it may be more appropriate to consider these values as response times. + +## APPENDIX II + +## Bibliography + +- KWOK (T.): Residential broadband Internet services and application requirements, *IEEE Communications Magazine*, June 1997. +- STEINMETZ (R.): Human Perception of Jitter and Media Synchronisation, *IEEE J-SAC*, Vol. 14, Issue 1, January 1996. +- SHNEIDERMAN (B.): Response Time and Display Rate in Human Performance with Computers, *ACM-Computing Surveys*, Vol. 16, No. 3, September 1984. +- MACDONALD (D.M.), ARCHAMBAULT (S.): Using customer perception in setting objectives for Intelligent Network services, *ITC-14*, 1994 . +- GALLAWAY (Glen R.): Response time to user activities in Interactive Man/Machine computer systems, *Proceedings of the Human Factors Society*, 25th Annual meeting, 1981. +- ETSI ETR 160, 1995, *Human factors aspects of multimedia telecommunications*. +- SHUR and MORTON, Performance of character-echo oriented applications on X.25 packet networks, *Globecom'92*. +- DANESHMAND (M.F.), ROY (R.R.) and SAVOLAINE (C.G.): Framework and requirements of Quality of Service for multimedia applications, *IIS'97*. +- GOLICK (Jerry): Catching the Multimedia Wave, *Data Communications Tech Tutorials*, 21st March 1999. +- WANG (S.Y.), MEYER (S.E.) and MY LAI: Quality of Service for Residential Broadband Video Service, *Globecom'96*. +- ANSI T1.522-2000, *Quality of Service for Business Multimedia Conferencing*. +- ZANETTIN (Alberto): Applications Prioritization: Giving the Green Light to Business Apps., *Data Communications Tech Tutorials*, March 1999. +- ISO-IEC/JTC 1/SC 29/WG 11 Report N2604, *Report of the formal verification tests on MPEG-4 video error resilience*, December 1998. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | + +\*21883\* \ No newline at end of file diff --git a/marked/G/T-REC-G.1032-201710-I_PDF-E/raw.md b/marked/G/T-REC-G.1032-201710-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6ec15f23cf4d07b2bb46dcc5c8410b88f7244e36 --- /dev/null +++ b/marked/G/T-REC-G.1032-201710-I_PDF-E/raw.md @@ -0,0 +1,432 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.1032** + +(10/2017) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Multimedia Quality of Service and performance – Generic +and user-related aspects + +--- + +**Influence factors on gaming quality of +experience** + +Recommendation ITU-T G.1032 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in blue, with "ITU" in a larger, bold font above it. + +ITU logo + +International +Telecommunication +Union + +# 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 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T G.1032 + +# Influence factors on gaming quality of experience + +## Summary + +Recommendation ITU-T G.1032 presents a list of factors which may influence the quality of experience (QoE) of cloud gaming and online gaming. The factors are grouped into user, system, and context factors. They should be taken into account when planning and implementing online gaming services, and when evaluating their quality of experience with subjective methods or instrumental quality prediction models. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.1032 | 2017-10-29 | 12 | 11.1002/1000/13396 | + +## Keywords + +Quality of experience, QoE, game, influence factor. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 2 | +| 6 Categorization of influence factors..... | 2 | +| 7 Human influence factors..... | 4 | +| 8 System influence factors..... | 5 | +| 8.1 Game..... | 5 | +| 8.2 Playing devices ..... | 6 | +| 8.3 Network transmission..... | 7 | +| 8.4 Compression ..... | 7 | +| 9 Context influence factors..... | 8 | +| Bibliography..... | 10 | + +## Introduction + +In addition to voice, video and web browsing, increasingly popular services running on IP-based networks are online computer games. However, in comparison to the aforementioned services, less information exist on factors (and their interactions) influencing the quality of experience experienced by the user (player) of such online computer games. Knowledge of such influence factors is important to apply subjective methods for assessing gaming of the QoE, or for building instrumental quality prediction models. This Recommendation is the basis of the related ITU Recommendations that describe subjective evaluation methods for gaming quality as well as prediction models for gaming quality. + +## Recommendation ITU-T G.1032 + +## Influence factors on gaming quality of experience + +# 1 Scope + +This Recommendation is intended to present a list of potential influencing factors for gaming QoE assessment. The list of influencing factors can be considered for several purposes including, but not limited to, interactive and passive gaming QoE assessment, steps during the game development circle, and network service providers for (cloud) online gaming. + +# 2 References + +None. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following term defined elsewhere: + +**3.1.1 frame rate** [b-ITU-T H.262]: The rate at which frames are output from the decoding process. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 cloud gaming:** Cloud gaming is characterized by game content delivered from a server to a client as a video stream with game controls sent from the client to the server. The execution of the game logic, rendering of the virtual scene, and video encoding are performed at the server, while the client is responsible for video decoding and capturing of client input. + +**3.2.2 critical flicker fusion threshold:** A threshold that is referring to the frequency at which an intermittent light stimulus appears to be completely steady to the average human observer. + +**3.2.3 eSport:** A form of sports where the primary aspects of the sport are facilitated by electronic systems; the input of players and teams as well as the output of the eSports system are mediated by human-computer interfaces. + +**3.2.4 game bricks:** A rule-based game classification splitting the games into several fundamental elements such as moving and shooting. In total, ten "gameplay bricks" in two categories are proposed by [b-Djaouti], rules stating goals, including avoid, match, and destroy, and rules defining the means and constraints to reach the goals consisting of create, manage, move, random, select, shoot, and write. + +**3.2.5 genre:** A classification of games where games are grouped according to their gameplay characteristics. + +**3.2.6 online gaming:** A service that enables a video game to be either partially or primarily played over a broadband network. The service renders the game at the client device while the updated states of game are transferred over a broadband network. + +**3.2.7 refresh rate:** The rate at which frames can be displayed on monitor. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|-------------------| +| CBR | Constant Bit Rate | +|-----|-------------------| + +| | | +|---------|-------------------------------------------------| +| CQP | Constant Quantization Parameter | +| CRF | Constant Rate Factor | +| FPS | First Person Shooter | +| GoP | Group of Pictures | +| HD | High-Definition video | +| LED | Light-Emitting Diode | +| LCD | Liquid-Crystal Display | +| MMORPGs | Massively-Multiplayer Online Role-Playing Games | +| QoE | Quality of Experience | +| QP | Quantization Parameter | + +# 5 Conventions + +In his Recommendation, online gaming is understood to be a service that renders the game at the client device while the updated states of the game are transferred over a broadband network. In contrast, in cloud gaming there is no processing (execution of the game logic, rendering of the virtual scene) on the client. Within the scope of this Recommendation, the person interacting with a game is referred to as player, whereas the software that is used in cloud gaming set-ups to display a remotely rendered game video stream is referred to as a client. + +# 6 Categorization of influence factors + +[b-Le Callet] defines the quality of experience (QoE) influence factor as: + +"Any characteristic of a user, system, service, application, or context whose actual state or setting may have influence on the Quality of Experience for the user." + +In this Recommendation, the factor groups proposed is in accordance with [b-Le Callet] are: human influence factors (clause 7), system influence factors (clause 8) and context influence factors (clause 9). + +QoE of an online gaming service can be measured through subjective tests as a passive viewing-and-listening (watching videos of recorded game play) or interactive scenario (participants are playing the game). In addition, an experiment could aim to investigate either cloud gaming or online gaming services. Based on the design and aim of the experiment, some of the factors may have a significant impact on the QoE. For example, video-encoding factors are not relevant for an experiment aimed at online gaming. The list of relevant influence factors for each test paradigm is shown in Table 1. Detailed information on each factor is presented in clauses 7 to 9. + +**Table 1 – List of relevant influencing factors based on test paradigm** + +| Factors | Test paradigm | | | +|------------------------------------|-------------------------------|---------------------------|--------------------------| +| | Passive viewing-and-listening | Interactive online gaming | Interactive cloud gaming | +| User influencing factors | | | | +| Experience | X | X | X | +| Intrinsic and extrinsic motivation | X | X | X | + +**Table 1 – List of relevant influencing factors based on test paradigm** + +| Factors | Test paradigm | | | +|---------------------------------------------------|-------------------------------|---------------------------|--------------------------| +| | Passive viewing-and-listening | Interactive online gaming | Interactive cloud gaming | +| Static and dynamic human factors | X | X | X | +| Human vision | X | X | X | +| System influencing factors (Game) | | | | +| Game genre | X | X | X | +| Game mechanics and rules | | X | X | +| Temporal and spatial accuracy | | X | X | +| Temporal and spatial video complexity | X | | X | +| Pace | | X | X | +| Visual perspective of the player | | X | X | +| Aesthetics and design characteristics | X | X | X | +| Learning difficulty | | X | X | +| System influencing factors (Playing device) | | | | +| Device portability | X | X | X | +| Handheld device size | | X | X | +| Input modalities | | X | X | +| Output modalities | X | X | X | +| Display | X | X | X | +| System influencing factors (Network transmission) | | | | +| Delay | | X | X | +| Jitter | | X | X | +| Bandwidth | X | X (Note) | X | +| Packet loss | X | X (Note) | X | +| System influencing factors (Compression) | | | | +| Frame rate | X | | X | +| Resolution | X | | X | +| Rate controller modes | X | | X | +| GoP | X | | X | +| Motion range search | X | | X | +| Audio compression | X | | X | +| Context influencing factors | | | | +| Physical environment factors | X | X | X | + +**Table 1 – List of relevant influencing factors based on test paradigm** + +| Factors | Test paradigm | | | +|-------------------------------|-------------------------------|---------------------------|--------------------------| +| | Passive viewing-and-listening | Interactive online gaming | Interactive cloud gaming | +| Social context | X | X | X | +| Service factors | | X | X | +| Novelty | X | X | X | +| NOTE – Minor impact expected. | | | | + +# 7 Human influence factors + +A Human influence factor is "any variant or invariant property or characteristic of a human user. The characteristic can describe the demographic and socio-economic background, the physical and mental constitution, or the user's emotional state" [b-Le Callet]. + +*Experience with gaming in general:* Both in scientific and in popular literature a classification of "hardcore gamer" and "casual gamer" is widely used, distinguishing the classes based on the average time of playing per time period. Despite the division's broad adoption, no common threshold exists to delimit the two groups. Another popular distinction exists between "newbie" and "pro gamer" based on the experience with a particular game or game genre. These characteristics are related to the gamer's skill, and change dynamically. It must be noted that a well-experienced player may rate the QoE differently compared to casual gamers. + +*Experience with a specific game or genre:* Each service is best evaluated by users who are familiar with how it should function. Digital games are a very broad term and the complexity of the game under test can vary. For simple games, the knowledge of the player about the game under test may not matter because the gameplay is simple and easy to understand. On the other hand, in more complex games such as massively multiplayer online role-playing games (MMORPGs) it is intuitive that the users which are using it should normally be the ones which can best evaluate its quality, because some aspects of the system may not function properly and if the testing player does not know how it should function he/she cannot notice the degradation. + +*Intrinsic and extrinsic motivation:* Intrinsic and extrinsic motivation can have a strong influence on the QoE of gaming since the high diversity of games offers different kinds of fun and motivation to play them. For example, players who want to prove themselves by beating other players may not be satisfied when playing a purely artificial intelligence controlled game. According to the self-determination theory, intrinsic motivation is the core type of motivation underlying sports and play [b-Frederick]. Nevertheless, the external validity of lab studies with paid test participants playing games without intrinsic motivation remains potentially problematic. In the context of massively-multiplayer online role-playing games, ten motivation sub-components can be grouped into the overarching components achievement, social, and immersion as explained in [b-Yee]. Therefore, as stated in [b-Yee]: "MMORPGs appeal to many players because they are able to cater to many different kinds of play styles". + +*Static and dynamic human factors:* Static human factors are the static characteristics of a player such as age, gender and native language, while dynamic factors refer to emotional status including boredom, distraction, curiosity and so forth. + +*Human vision:* Visual perception varies depending to the characteristics of the visual stimulus. The sensitivity of a user to video/network artifacts differs between users. As an example, sensitivity to frame rate as encoding parameter depends on a user's critical flicker fusion threshold. See [b-Davis]. + +## 8 System influence factors + +System influence factors refer to "properties and characteristics that determine the technically produced quality of an application or service" [b-Jumisko-1]. The factors in this section contain not only the game, which is being played by the user, but also the whole setup and user-perceivable design of the hardware and software. Depending on the kind of gaming system the relevant factors differ. Since, for example, online (multi-player) gaming typically uses online connectivity just for state synchronization with a server, video compression-related factors do not apply in this case. Furthermore, technologies such as stereoscopic 3D through head-mounted displays introduce new influence factors and likely impact the effect of other factors. + +### 8.1 Game + +As with other types of media, the content of a game (e.g., mechanics, dynamics, aesthetics [b-Hunicke]) decidedly influence a player's gaming experience. However, differing from other types of media, the content and the underlying technical implementation are strongly interwoven: even games from the same genre often employ entirely different stacks of software to generate the gaming experience. This influences the perceivable effects of variations of influence factors as different compensation strategies may be implemented. + +The game content has a major influence on QoE especially when other influencing factors are considered. In fact, the sensitivity to parameters like delay is more influential to some types of games than to others. Therefore, the selection of appropriate content for a subjective test is an important part of any experiment design. In this clause, the parameters that must be considered for the selection of the game type are explained. + +*Game genre:* Genre classification is a broad term and is not precise enough to characterize the games. However, in the absent of an appropriate game classification, game genres can be used as a basic criterion of content selection in the experimental design. It must be noted that several game interactions (game bricks) such as shooting, moving, and avoiding could be a part of a single game (genre) while the impact of technical parameters such as delay for each of these interactions most likely is not the same. Thus, the game genre alone will not be sufficient to characterize the sensitivity of the game towards technical parameters. + +*Game mechanics and rules:* These largely influence and determine game outcomes and are individual to each game. + +*Temporal and spatial accuracy:* Temporal accuracy is defined as the time required to complete an action. Spatial accuracy is the degree of accuracy required to complete the interaction successfully. These two factors might determine the playability of a certain game under delay. The broad classification of games on the temporal accuracy (deadliness) and spatial accuracy (precision) plane was suggested in [b-Claypool-1]. It should to be noted that these factors play an important role when investigating the temporal factors such as delay and frame rates. + +*Temporal and spatial video complexity:* Video complexity plays an important role in streaming services especially when bitrate and other encoding factors are considered. Video games with different spatial and temporal complexity might have a different degree of perceptual quality. Video content with high complexity may suffer more from network parameters like bandwidth, packet loss and encoding artifacts than low-complexity content. Consequently, the bandwidth itself cannot sufficiently characterize the quality degradation of a game video sequence, even if all the other parameters have been fixed. In other words, for the same bandwidth due to the difference of video complexity, different qualities may be perceived for two video games. + +*Pace:* Pace refers to the speed of a gameplay. Although this factor seems to be similar to the two previously mentioned factors (the temporal accuracy concept as well as temporal complexity of games), there is a small difference between pace and the two other factors. First, pace has to be seen as a speed in one game type (or one game genre in general) which means that there could be two + +games with the same temporal complexity while their paces are not comparable (e.g., a racing game and shooting game with same temporal complexity). In addition, a game with high-required reaction time does not necessarily have a high pace (e.g., a static scene with some blinking points that has to be hit). Overall, pace has to be seen as a speed of a gameplay in a particular type of game (or genre), but there is no classification of pace in the literature. Pace should to be considered as an influencing factor especially when investigating the temporal factors such as delay and frame rate. + +*Visual perspective of the player:* Based on the perspective of the camera, games have been classified into First-person Linear Perspective, Third-person Linear Perspective, and Third-person Isometric Perspective [b-Claypool-2]. The perspectives of the game are very important in cloud gaming and an interplay with the video coding can be assumed. + +*Aesthetics and design characteristics:* Aesthetics is the sensory experience that the system elicits, and the extent to which this experience fits individual goals and spirit [b-Vilnai]. Aesthetics and design characteristics describe the design of a game, which can be experienced by the player, and is commonly specified by design experts. There is no known classification for game designs. However, there might be a strong influence on player experience considering both the variety in addressed types of "fun" [b-Hunicke] and the effort that is being invested into creating a distinguished visual and audible appearance of games. + +*Learning difficulty:* The required time to learn how to play a game is a critical criterion when aiming at short interactive test. Games such as racing games do not necessarily need a long time to learn the game rules, actions and game elements because of limited number of control buttons and game rules. On the contrary, there are games that need a long time (even days and weeks) to achieve the goals and learn the elements of the game . Such games should be avoided for short interactive tests. + +## 8.2 Playing devices + +*Portability:* The continued success of portable gaming devices suggests that the benefit of mobility outweighs the limitations of a portable device for a group of players. The success of smartphone gaming may also be attributed partly to the portability of the devices, but a quantification of that particular influence is challenging and attempts are currently limited. + +*Size:* The size of a handheld device has been shown to exert an influence on playing test participants' ratings [b-Beyer-1]. Unless it is the object of investigation in a study, it should therefore remain constant. + +*Input modalities:* Modalities used for game input differ vastly in terms of attributes such as precision, speed and feedback. In the past, new forms of input (e.g., gesture control) have repeatedly enabled new playing paradigms. However, in some contexts different controls can be used interchangeably (e.g., inertial vs button control in racing games, touch-screen overlay buttons vs physical keyboards or pads) and likely influence the experience of a game unless it explicitly adapts to the different modalities (e.g., in terms of reduced difficulty). + +*Output modalities:* The availability of output modalities and their technical attributes confine the perceivable experiences. A comparative study showed that participants wearing a VR headset perceive higher levels of immersion than players of the same simulation game using a conventional 2D screen [b-Hupont]. + +*Display:* For video quality assessment, it was shown [b-Winkler] that the perceived quality is strongly influenced by the viewing distance, display size, brightness, contrast, sharpness, screen resolution, refresh rate and color. If the frame rate is high the size of the display as well the refresh rate of the display can bring higher quality. If the high-definition (HD) video games are targeted for the test, a full HD resolution display needs to be used. + +The display size is an important aspect whenever control elements are placed directly on the screen. A device that is too small influences the usability of the game. An outcome of the study [b-Beyer-2] shows that a screen size for mobile games should always be larger than 5". However, the screen size + +should also not be too large as this would result in a scenario with a negative impact on reaction times or cause less awareness. For that reason, in the eSport domain a screen size for PC games of 24" is commonly used. + +Regarding the monitor refresh rate, the technology is evolving at a fast pace. For interactive applications such as gaming, a high frame rate and refresh rate is expected. Additionally, new methods to synchronize the GPU rendering and monitor refresh rate (G-Sync and Free-Sync) are available on the market. When using such a new technology, it should be noted that there will most likely be a large difference when compared to older technologies, especially when coding parameter or very fast-paced games are considered. + +In addition, game content can be represented to users in different ways such as using head-mounted displays, mobile displays, light-emitting diode (LED) displays, liquid-crystal display (LCD) displays, etc. The impact of using head-mounted displays on gaming QoE, especially on immersion, has been proven and it should be considered when comparing results between platforms [b-Hupont], [b-Tan]. + +## 8.3 Network transmission + +Given the highly interactive nature of online games, a network distortion can negatively influence the user's experience. There is a distinction between studies focusing on online gaming and cloud gaming in terms of network transmission distortion, whereby online gaming mostly suffers from delay, jitter and packet loss, while cloud gaming additionally has to deal with a limited bandwidth. + +*Delay:* The delay perceived by an end user corresponds to the delay from the execution of the user commands to visible game event shown on the display. While most studies focus on the impact of networking delays, often the consideration of additional system components contributing to overall end-to-end delay are neglected (e.g., system tick rate, processing and rendering delay). + +The influence of delay on the QoE strongly depends on game factors, as discussed earlier. Therefore, investigating delay as an influencing factor of QoE without considering the characteristics of the game is not valid, and results are not comparable with other studies. In addition to game characteristics, the perceived delay may differ considerably depending on the input devices used for playing. + +*Jitter:* Jitter has a perceivable influence on online gaming and cloud gaming experience [b-Ries], [b-Quax]. It is also a concern in cloud gaming settings as high levels of jitter may introduce delays due to additional buffering or cause packet loss if data is delivered too late for rendering. Depending on the client implementation, jitter may also result in a less smooth visual appearance of the game as frames are displayed at varying intervals. + +*Bandwidth:* The impact of bandwidth restrictions on QoE in the context of cloud gaming has been proven in numerous studies (e.g., [b-Beyer-3]-[b-Wen]) and has been shown to be a contributing influence factor to gaming QoE. Depending on employed mechanism to deal with limited bandwidth, it could result in packet loss, delay (due to buffering mechanism) and video artifact due to video compression. + +*Packet loss:* Network packet loss has a significant impact on gaming QoE while playing intensive games such as first person shooter (FPS), with packet loss less than 1% causing serious degradation of user experience [b-Chen]. Increased packet loss causes severe degradation of the graphics quality of the games, culminating with lower frame rate and unplayable gaming experience. In a non-cloud-gaming setting, the effects of packet loss are less homogenous and depend strongly on the implementation of a game and the effectiveness of the countermeasures it employs. + +## 8.4 Compression + +Given bandwidth limitations, different QoE-driven codec configuration strategies may be specified for various types of games. These strategies also interact with the delay influence factor as many redundancy reduction strategies in modern video codecs benefit from additional buffering which is + +detrimental to low-latency video transmission. The most important encoding parameters linked to cloud gaming QoE are: + +*Frame rate:* The frame rate has a significant impact on a user's performance and consequently influences the QoE. However, perceiving the difference between very high frame rates strongly depends on human vision abilities, a player's commonly used gaming setup, and game characteristics (especially the game pace). It should be noted that display specifications such as display size and refresh rate would be substantial when investigating the impact frame rate on the QoE. + +*Resolution:* The encoding resolution is an important parameter, which affects the video quality in all streaming applications while it has little impact on the user performance [b-Claypool-3]. For a given resolution, an increasing bit rate may increase the quality up to a specific level; beyond this level, increasing the bit rate cannot further improve the quality. Therefore, for users with a high bandwidth, a higher resolution is needed instead of improving other encoding parameters such as quantization parameter (QP). + +*Rate controller modes:* There are some strategies to control the video streaming rates in order to reach a certain target quality with a given bandwidth. Three different rate controller modes were implemented in x264 (VBR is excluded since it is out of the scope of cloud gaming services) including constant quantization parameter (CQP), constant rate factor (CRF) and constant bit rate (CBR); all of them resulted in a different quality. CQP is the straightforward strategy which encodes the video based on constant QP and leads to variable bit rate and quality. CRF attempts to keep the quality at a certain level by adjusting the QP for each frame. Finally, CBR tries to encode the video by keeping the bit rate constant. Rate control strategies do not only affect the QoE, but they also have an impact on the overall delay of a gaming service. It should be noted that, after deciding on a rate controller strategy, other parameters linked to the selected rate controller strategy should be investigated. For example, the overall quality of a video generated by using a CQP strategy depends on the chosen quantization parameter. + +*Group of Pictures:* Group of Pictures (GoP) is a structure that specifies the order of inter and intra frames (I, B and P frames) in a video sequence. There are two terminologies related to the GoP. The GoP *value* is determined by the distance between two anchor frames (number of frames between an I-frame and the next P-frame). The GoP *length* is determined by the distance between two I-frames. The selection of the GoP length is a trade-off between the propagation error and the video compression. A small GoP length may lead to a higher bitrate for encoding, since more I-frames are involved in the encoding process. On the other hand, a larger GoP length increases the chance of error propagation, since in the case of a transmission loss, more frames are needed to receive an I-frame to correct the error. As a result, the GoP length may affect the perceived quality, and the impact of GoP size should be investigated for video gaming service. + +*Motion range search:* A motion estimation algorithm has an influence on the efficiency of coding, and indirectly impacts the overall quality of a gaming service. Besides the motion estimation algorithm, the motion range search needs to be determined based on the video content, which may significantly impact the QoE (see discussion above). For highly dynamic video content a wider-range motion search is desirable, and for mostly static content a smaller motion range should be chosen to reduce the computation time. + +*Audio compression:* A similar influence as the video compression factor is assumed for audio. However, audio compression in the context of cloud gaming has so far not been subjected to the same degree of scientific scrutiny as video compression. + +# 9 Context influence factors + +Context influence factors "are factors that embrace any situational property to describe the user's environment in terms of physical, temporal, social, economic, task, and technical characteristics" [b-Jumisko-1], [b-Jumisko-2]. While in some rare cases, such as special car or airplane simulators, + +the player's environment is formed, lit, and even moved in a way to resemble the corresponding original, the ordinary case is that it lies outside the reach of the games designers. Besides these physical environmental factors, the success of online multiplayer games (e.g., MMORPGs) or party games (e.g., various karaoke) have demonstrated the significance of the social context. + +*Physical environment factors:* Physical factors refer to room characteristics (space, acoustics, and lighting) and usage situation (in-house, on the move, etc.). The physical environment may influence gaming QoE and must be chosen in a way that represents the real gaming environment. + +*Social context:* Relationships to other players who are involved in the game, potential parallel activities of the player, privacy and security issues, which might be particularly relevant in multiplayer games. The social context is one of the influential QoE factors that is difficult to measure objectively. Therefore, the influence of other factors (especially technical factors) on gaming QoE are hard to measure if social context is also considered. Hence, it is recommended to avoid this factor in gaming QoE studies, unless the main focus of the work is to study the influence of such factors. + +*Service factors:* [b-Yang] discusses the influence of service factors (e.g., ease of access, availability, pricing) on customer satisfaction for online game services, which is likely to be present especially in the context of cloud gaming. + +*Novelty:* Novelty, which means that the user experience is improved when a new technology is introduced, has an impact on quality judgments, not because of any actual improvement in learning or achievement, but in response to an increased interest in the new technology [b-Meline]. Thus, it can be expected that the impact of quality factors on perceived quality will be different with any "new" technologies and services. + +## Bibliography + +- [b-ITU-T H.262] Recommendation ITU-T H.262 (2012) | ISO/IEC 13818-2 (2013), *Information technology – Generic coding of moving pictures and associated audio information: Video*. +- [b-Beyer-1] Beyer, J., Miruchna, V., and Möller, S. (2014), Assessing the impact of display size, game type, and usage context on mobile gaming QOE, in *2014 Sixth International Workshop on Quality of Multimedia Experience (QoMEX)*, P. 69-70. +- [b-Beyer-2] Beyer, J. and Möller, S. (2014), Assessing the Impact of Game Type, Display Size and Network Delay on Mobile Gaming QoE, *PIK-Prax. Informationsverarbeitung Kommun.*, Vol. 37, Nr. 4, P. 287-295. +- [b-Beyer-3] Beyer, J., Varbelow, R., Antons, J.-N., and Möller, S. (2015), Using electroencephalography and subjective self-assessment to measure the influence of quality variations in cloud gaming, in *Quality of Multimedia Experience (QoMEX), 2015 Seventh International Workshop on*, P. 1-6. +- [b-Chen] Chen, K.-T., Chang, Y.-C., Hsu, H.-J., Chen, D.-Y., Huang, C.-Y., and Hsu, C.-H. (2014), On the quality of service of cloud gaming systems, *IEEE Trans. Multimed.*, Vol. 16, Nr. 2, P. 480-495. +- [b-Claypool-1] Claypool, M. and Claypool, K. (2006), Latency and player actions in online games, *Commun. ACM*, Vol. 49, Nr. 11, P. 40-45. +- [b-Claypool-2] Claypool, M. and Claypool, K. (2009), Perspectives, frame rates and resolutions: it's all in the game, in *Proceedings of the 4th International Conference on Foundations of Digital Games*, P. 42-49. +- [b-Claypool-3] Claypool, M., Claypool, K., and Damaa, F. (2006), The effects of frame rate and resolution on users playing first person shooter games, in *Electronic Imaging 2006*, P. 607101-607101. +- [b-Davis] Davis, J., Hsieh, Y.-H., and Lee, H.-C. (2015), *Humans perceive flicker artifacts at 500 Hz*, *Sci. Rep.*, Vol. 5, P. 7861, Feb. +- [b-Djaouti] Djaouti, D., Alvarez, J., Jessel J.-P., Methel G., and P. Molinier (2008), A gameplay definition through videogame classification, *Int. J. Comput. Games Technol.*, Vol. 2008, P. 4. +- [b-Frederick] Frederick, C.M. and Ryan, R.M. (1993), Differences in motivation for sport and exercise and their relations with participation and mental health, *J. Sport Behav.*, Vol. 16, Nr. 3, P. 124. +- [b-Hunicke] Hunicke, R., LeBlanc, M., and Zubek, R. (2004), MDA: A formal approach to game design and game research, in *Proceedings of the AAAI Workshop on Challenges in Game AI*, Vol. 4, P. 1. +- [b-Hupont] Hupont, I., Gracia, J., Sanagustín, L., and Gracia, M.A. (2015), How do new visual immersive systems influence gaming QoE? A use case of serious gaming with Oculus Rift, in *Quality of Multimedia Experience (QoMEX), 2015 Seventh International Workshop on*, P. 1-6. +- [b-Jumisko-1] Jumisko-Pyykkö, P. (2011), User-centered quality of experience and its evaluation methods for mobile television, *Dr. Diss. Tamp. Univ. Technol.* + +- [b-Jumisko-2] Jumisko-Pyykkö, S. and T. Vainio, Framing the context of use for mobile HCI (2012), *Soc. Organ. Impacts Emerg. Mob. Devices Eval. Use Eval. Use*, P. 217. +- [b-Le Callet] Le Callet, P., Möller, S., Perkis, A., etal. (2012), Qualinet white paper on definitions of quality of experience, *Eur. Netw. Qual. Exp. Multimed. Syst. Serv. COST Action IC 1003*. +- [b-Meline] Meline, T. (2009), *A research primer for communication sciences and disorders*. Allyn & Bacon. +- [b-Möller] Möller, S., Pommer, D., Beyer, J., and Rake-Revelant, J. (2013), Factors influencing gaming qoe: Lessons learned from the evaluation of cloud gaming services, in *Proceedings of the 4th International Workshop on Perceptual Quality of Systems (PQS 2013)*, P. 1-5. +- [b-Quax] Quax, P., Beznosyk, A., Vanmontfort, W., Marx, R., and Lamotte, W. (2013), An evaluation of the impact of game genre on user experience in cloud gaming, in *2013 IEEE International Games Innovation Conference (IGIC)*, P. 216-221. +- [b-Ries] Ries, M., Svoboda, P., and Rupp, M. (2008), Empirical study of subjective quality for massive multiplayer games, in *2008 15th International Conference on Systems, Signals and Image Processing*, P. 181-184. +- [b-Tan] Tan, C.T., Leong, T.W., Shen, S., Dubravs, C., and Si, C. (2015), Exploring Gameplay Experiences on the Oculus Rift, in *Proceedings of the 2015 Annual Symposium on Computer-Human Interaction in Play*, P. 253-263. +- [b-Vilnai] Vilnai-Yavetz, I., Rafaeli, A, and Yaacov, C. S. (2005) Instrumentality, aesthetics, and symbolism of office design. *Environment and Behavior* 37, no. 4 (2005): 533-551. +- [b-Winkler] Winkler, S. (1999), Issues in vision modeling for perceptual video quality assessment, *Signal Process*, Vol. 78, Nr. 2, P. 231-252. +- [b-Wen] Wen, Z.-Y. and Hsiao, H.-F. (2014), QoE-driven performance analysis of cloud gaming services, in *Multimedia Signal Processing (MMSP), 2014 IEEE 16th International Workshop on*, P. 1-6. +- [b-Yang] Yang, H.-E., Wu, C.-C., and Wang, K.-C. (2009), An empirical analysis of online game service satisfaction and loyalty, *Expert Syst. Appl.*, Vol. 36, Nr. 2, P. 1816-1825. +- [b-Yee] Yee, N. (2006), Motivations for play in online games, *Cyberpsychol. Behav.*, Vol. 9, Nr. 6, P. 772-775. + + + + + +## 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.1051-202303-I_PDF-E/011fecb4a85637472f0c697a6cbdb15d_img.jpg b/marked/G/T-REC-G.1051-202303-I_PDF-E/011fecb4a85637472f0c697a6cbdb15d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88c94dcffc650bfe35f86d9946c4b0fc69c39b88 --- /dev/null +++ b/marked/G/T-REC-G.1051-202303-I_PDF-E/011fecb4a85637472f0c697a6cbdb15d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25eed99fdcb189277dc0728835221ea57f4b0ed524318db37b919c2ceece27cc +size 75374 diff --git a/marked/G/T-REC-G.1051-202303-I_PDF-E/0245dc88c1db93181871e732bc0655dd_img.jpg b/marked/G/T-REC-G.1051-202303-I_PDF-E/0245dc88c1db93181871e732bc0655dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d92b4c31c8bb2a9948261f1fdd4cb14a40f1f61 --- /dev/null +++ b/marked/G/T-REC-G.1051-202303-I_PDF-E/0245dc88c1db93181871e732bc0655dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7bf87d77dee046f892aeeaeff759ca2ce7d281a8e469b76df91c18d1793405f +size 62839 diff --git a/marked/G/T-REC-G.1051-202303-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.1051-202303-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/G/T-REC-G.1051-202303-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.1051-202303-I_PDF-E/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg b/marked/G/T-REC-G.1051-202303-I_PDF-E/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c36ebd20fb930d4777762df6028116958eb0edd --- /dev/null +++ b/marked/G/T-REC-G.1051-202303-I_PDF-E/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40d522209e89c9740e35ba73e5f68da66f6afbaac0822982a5b5da4c7cddf540 +size 38509 diff --git a/marked/G/T-REC-G.1051-202303-I_PDF-E/5adf12d50dfea82178ca002a2c48641b_img.jpg b/marked/G/T-REC-G.1051-202303-I_PDF-E/5adf12d50dfea82178ca002a2c48641b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecbe4df5f7053838affb474669086099bc986570 --- /dev/null +++ b/marked/G/T-REC-G.1051-202303-I_PDF-E/5adf12d50dfea82178ca002a2c48641b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af79130129d7adf52d3da39a0dfa7aec9d860eca8df5b3e02cb2918e8e9f9c8c +size 35231 diff --git a/marked/G/T-REC-G.1051-202303-I_PDF-E/5ed9189841659dfb01f809b8e3b21f74_img.jpg b/marked/G/T-REC-G.1051-202303-I_PDF-E/5ed9189841659dfb01f809b8e3b21f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59eaf0833e5a583048aeb63cb7bf68748d12f512 --- /dev/null +++ b/marked/G/T-REC-G.1051-202303-I_PDF-E/5ed9189841659dfb01f809b8e3b21f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f84ec4d3a80aa4f93333de1ad6537abf235126efeda5284ac13c1dd3533713f +size 39550 diff --git a/marked/G/T-REC-G.1051-202303-I_PDF-E/60e9207be66a64332619bb4b667fe67b_img.jpg b/marked/G/T-REC-G.1051-202303-I_PDF-E/60e9207be66a64332619bb4b667fe67b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62576da148a1a89cbe15863523c4962a5228e42a --- /dev/null +++ b/marked/G/T-REC-G.1051-202303-I_PDF-E/60e9207be66a64332619bb4b667fe67b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54f0c3b676df5b87123b4966c16eceec930ebd2f4896a8a886fe7710febbaba1 +size 52856 diff --git a/marked/G/T-REC-G.1051-202303-I_PDF-E/65f66758012e229247953202e8adf35d_img.jpg b/marked/G/T-REC-G.1051-202303-I_PDF-E/65f66758012e229247953202e8adf35d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d6a810497bbbd7f1cea670e1b8dca4b36fee591 --- /dev/null +++ b/marked/G/T-REC-G.1051-202303-I_PDF-E/65f66758012e229247953202e8adf35d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9213b07bb21359574f6df9c94450dad185cfbf3f037fc81648f406407195773b +size 50278 diff --git a/marked/G/T-REC-G.1051-202303-I_PDF-E/9ce50bc10864dc86e1cdee4be08f1897_img.jpg b/marked/G/T-REC-G.1051-202303-I_PDF-E/9ce50bc10864dc86e1cdee4be08f1897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..240120d0fcd4b3df5e92aeedc7c6f216448dbdf5 --- /dev/null +++ b/marked/G/T-REC-G.1051-202303-I_PDF-E/9ce50bc10864dc86e1cdee4be08f1897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c82a11e334dc6857d272243f31d47e2c9b28b01595c6cf43c00421952e24fb4c +size 41601 diff --git a/marked/G/T-REC-G.1051-202303-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg b/marked/G/T-REC-G.1051-202303-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02629bcde4d98c2da155ffd94996b2d109093dcf --- /dev/null +++ b/marked/G/T-REC-G.1051-202303-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20778e17f6cb94d9e93397414916dc4132281543876efc0f86479cf75cc956c6 +size 64051 diff --git a/marked/G/T-REC-G.1051-202303-I_PDF-E/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg b/marked/G/T-REC-G.1051-202303-I_PDF-E/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..714c9a798bbbeac2a3942234dc4ad592daf92cc3 --- /dev/null +++ b/marked/G/T-REC-G.1051-202303-I_PDF-E/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a4a9dcf003e95f1975ef570adac16e1f3009d3e3f61b44ef7433afffd2e62dc +size 52928 diff --git a/marked/G/T-REC-G.1051-202303-I_PDF-E/dc0cec98faa3ead994c1b171cb56265d_img.jpg b/marked/G/T-REC-G.1051-202303-I_PDF-E/dc0cec98faa3ead994c1b171cb56265d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f11c84476326d014987d07c5fe75ca9be1fdc40 --- /dev/null +++ b/marked/G/T-REC-G.1051-202303-I_PDF-E/dc0cec98faa3ead994c1b171cb56265d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e940b8ed189ab1950a5f0ce3454329a5fee9910d0e627d8caf9806bca29066ac +size 61031 diff --git a/marked/G/T-REC-G.108.1-200005-I_PDF-E/raw.md b/marked/G/T-REC-G.108.1-200005-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b833e313179c95a917514896addc28adb01f3092 --- /dev/null +++ b/marked/G/T-REC-G.108.1-200005-I_PDF-E/raw.md @@ -0,0 +1,687 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the center. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.108.1** + +(05/2000) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +International telephone connections and circuits – General +definitions + +--- + +**Guidance for assessing conversational speech +transmission quality effects not covered by the +E-model** + +ITU-T Recommendation G.108.1 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| General definitions | G.100–G.109 | +| General Recommendations on the transmission quality for an entire international telephone connection | G.110–G.119 | +| General characteristics of national systems forming part of international connections | G.120–G.129 | +| General characteristics of the 4-wire chain formed by the international circuits and national extension circuits | G.130–G.139 | +| General characteristics of the 4-wire chain of international circuits; international transit | G.140–G.149 | +| General characteristics of international telephone circuits and national extension circuits | G.150–G.159 | +| Apparatus associated with long-distance telephone circuits | G.160–G.169 | +| Transmission plan aspects of special circuits and connections using the international telephone connection network | G.170–G.179 | +| Protection and restoration of transmission systems | G.180–G.189 | +| Software tools for transmission systems | G.190–G.199 | +| INTERNATIONAL ANALOGUE CARRIER SYSTEM | | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| DIGITAL TRANSMISSION SYSTEMS | | +| TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | + +For further details, please refer to the list of ITU-T Recommendations. + +# **Guidance for assessing conversational speech transmission quality effects not covered by the E-model** + +## **Summary** + +This ITU-T Recommendation provides guidance for transmission planners on how to evaluate those effects impacting end-to-end speech transmission performance which are not covered by the E-model (ITU-T Recommendation G.107 [2] – The E-model, a computational model for use in transmission planning) and its associated Planning Guide (ITU-T Recommendation G.108 [3] – Application of the E-model – A planning guide). Procedures for informal subjective and objective evaluations that can be used to complement the E-model are provided here. + +## **Source** + +ITU-T Recommendation G.108.1 was prepared by ITU-T Study Group 12 (1997-2000) and approved under the WTSC Resolution 1 procedure on 18 May 2000. + +## **Keywords** + +Conversational impacts, E-model, speech transmission quality, voice quality. + +## 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 Conference (WTSC), 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 WTSC Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Abbreviations and definitions..... | 2 | +| 3.1 Abbreviations..... | 2 | +| 3.2 Definitions ..... | 2 | +| 4 General considerations..... | 2 | +| 4.1 Parameters describing speech transmission quality (including terminals) ..... | 6 | +| 4.2 Test setup for terminals..... | 7 | +| 4.3 Test setup for echo cancelling devices..... | 8 | +| 4.4 Test signals for conversational evaluation..... | 8 | +| 5 Evaluation of the conversational situation..... | 8 | +| 5.1 Double talk performance..... | 9 | +| 5.2 Subjective evaluations ..... | 9 | +| 5.2.1 Conversational evaluation ..... | 9 | +| 5.2.2 Specific double talk tests and listening only tests ..... | 11 | +| 5.3 Objective evaluations..... | 12 | +| 6 Guidance on the improvement of conversational speech quality..... | 12 | +| 6.1 Delay and echo..... | 13 | +| 6.2 Background noise transmission ..... | 13 | +| 6.3 Double talk performance..... | 14 | +| 6.4 Quality of speech sound and loudness..... | 14 | + +# Introduction + +This ITU-T Recommendation provides guidance for transmission planners on supplementary conversational parameters impacting end-to-end speech transmission performance which are not covered by ITU-T Recommendation G.108, since: + +- these supplementary factors are not covered by the E-model as it stands; +- the guidelines and principles in ITU-T Recommendation G.108 are based on the use of the E-model, which is applicable to 3.1 kHz handset telephony, only; +- the current E-Model cannot completely predict the conversational effects of electric or acoustic echo cancelling devices, which may affect quality during only some time segments of the conversation; +- conversational impacts on end-to-end speech transmission performance will occur in conjunction with conversation over hands-free terminals. + +## ITU-T Recommendation G.108.1 + +## Guidance for assessing conversational speech transmission quality effects not covered by the E-model + +# 1 Scope + +This ITU-T Recommendation is intended to provide guidance on the conversational impairments which are not covered by the E-model and which are thus not included in ITU-T Recommendation G.108 [3]. Those impairments have been investigated thoroughly by ITU-T during the study period 1997-2000. + +# 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. + +- [1] ITU-T Recommendation G.100 (1993), *Definitions used in Recommendations on general characteristics of international telephone connections and circuits.* +- [2] ITU-T Recommendation G.107 (2000), *The E-model, a computational model for use in transmission planning.* +- [3] ITU-T Recommendation G.108 (1999), *Application of the E-model: a planning guide.* +- [4] ITU-T Recommendation G.167 (1993), *Acoustic echo controllers.* +- [5] ITU-T Recommendation G.168 (2000), *Digital network echo cancellers.* +- [6] ITU-T Recommendation P.50 (1999), *Artificial voices.* +- [7] ITU-T Recommendation P.57 (1996), *Artificial ears.* +- [8] ITU-T Recommendation P.58 (1996), *Head and torso simulator for telephonometry.* +- [9] ITU-T Recommendation P.59 (1993), *Artificial conversational speech.* +- [10] ITU-T Recommendation P.64 (1999), *Determination of sensitivity/frequency characteristics of local telephone systems.* +- [11] ITU-T Recommendation P.340 (2000), *Transmission characteristics and speech quality parameters of hands-free terminals.* +- [12] ITU-T Recommendation P.501 (2000), *Test signals for use in telephonometry.* +- [13] ITU-T Recommendation P.502 (2000), *Objective test methods for speech communication systems using complex test signals.* +- [14] ITU-T Recommendation P.581 (2000), *Use of head and torso simulator (HATS) for hands-free terminal testing.* +- [15] ITU-T Recommendation P.800 (1996), *Methods for subjective determination of transmission quality.* +- [16] ITU-T Recommendation P.831 (1998), *Subjective performance evaluation of network echo cancellers.* + +- [17] ITU-T Recommendation P.832 (2000), *Subjective performance evaluation of hands-free terminals*. +- [18] ITU-T Recommendation P.861 (1998), *Objective quality measurement of telephone-band (300-3400 Hz) speech codecs*. +- [19] ETSI EG 201 377-1 (1999), *Speech Processing, Transmission and Quality Aspects (STQ); Specification and measurement of speech transmission quality; Part 1: Introduction to objective comparison measurement methods for one-way speech quality across networks*. + +# 3 Abbreviations and definitions + +## 3.1 Abbreviations + +This ITU-T Recommendation uses the following abbreviations: + +| | | +|-------|-------------------------------------------------------------------------------------------------| +| DCME | Digital Circuit Multiplication Equipment | +| ECD | Echo Cancelling Device | +| HATS | Head and Torso Simulator | +| HEC | Half Echo Canceller | +| ITU | International Telecommunication Union | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector (former CCITT) | +| NLP | Non-Linear Processor | +| RCV | Receive | +| SCT | Short Conversational Test | +| SND | Send | +| TCLw | Terminal Coupling Loss weighted | +| VAD | Voice Activity Detection | + +## 3.2 Definitions + +This ITU-T Recommendation defines the following term: + +The term "**Lab Conditions**" is used in this ITU-T Recommendation in order to describe a testing environment which is well controllable and which allows for speech quality testing under defined and reproducible conditions. + +# 4 General considerations + +When evaluating the end-to-end speech transmission quality, it may be found that networks and terminals impact the speech quality of a telephone connection quite significantly: coding and decoding processes, introduction of additional delay, packetization and signal processing techniques as implemented, e.g. in echo cancelling devices or DCME are mainly deployed in the network domain but can increasingly be found in terminal devices as well. The frequency response and loudness ratings of a connection are mainly determined by the terminals, the background noise and the background noise transmission are highly influenced by the terminal and the acoustical environment the terminal is exposed to. The conversational properties which are the most important ones in a conversation are determined by the terminal in combination with the network: double talk capability, switching characteristics and delay are dominant impairments which are often introduced. + +In order to evaluate the factors which determine end-to-end speech transmission quality a set of subjective test procedures has been developed. These procedures allow to extract the dominant quality aspects: conversational tests, talking and listening tests, double talk tests and listening only tests as described in ITU-T Recommendations P.800 [15], P.831 [16] and P.832 [17] are the basis for the parameter extraction procedure. + +An overview of the methodologies is given in Figures 1 through 3. + +![Figure 1/G.108.1 – Overview of test methods used for subjective evaluation – direct parameter access. The diagram shows three columns: Test Environment, Auditory Tests, and Performance Parameters. The Test Environment column shows a vertical axis from 'Realistic Conditions ](562f471e8153729557e6a4ee6343c32c_img.jpg) + +**Test Environment** + +Realistic Conditions "Human Factor" + +↑ + +↓ + +Measurement Conditions (exactly defined and identical for each test and reproducible) + +**Auditory Tests** + +**Conversational Tests** +2 subjects involved (one at the near end of the telephone connection, the other at the far end) + +**Double Talk Tests** +2 subjects involved (one at the near end of the telephone connection, the other at the far end) + +or + +**Talking and Listening Tests** +1 artificial head used (at the near end of the telephone connection), 1 subject involved (at the far end), acting as listener and talker + +**Listening-only Tests** +2 artificial heads used (one at the near end of the telephone connection, the other at the far end) +1 subject as "observer" + +**Performance Parameters** + +End-to-end speech transmission quality + +Difficulty in communicating + +Sound quality + +Annoyance caused by echoes and switching + +Double talk performance + +Method of background noise transmission + +Speech level variations vs. time + +Comparison of individual parameters under defined conditions + +Classification of disturbances + +Database for further tests + +T1212320-00 + +Figure 1/G.108.1 – Overview of test methods used for subjective evaluation – direct parameter access. The diagram shows three columns: Test Environment, Auditory Tests, and Performance Parameters. The Test Environment column shows a vertical axis from 'Realistic Conditions + +NOTE – The assignment of "near end" and "far end" is chosen according to the E-model (ITU-T Recommendation G.107). + +**Figure 1/G.108.1 – Overview of test methods used for subjective evaluation – direct parameter access** + +![Diagram showing the relationship between Test Environment, Auditory Tests, and Performance Parameters. It includes categories like Realistic Conditions, Conversational Tests, Double Talk Tests, Talking and Listening Tests, and Listening-only Tests, linked to parameters such as speech transmission quality and sound quality.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +The diagram illustrates the relationship between test environments, auditory tests, and performance parameters for subjective evaluation. It is organized into three columns: Test Environment, Auditory Tests, and Performance Parameters. + +**Test Environment:** + +- Realistic Conditions "Human Factor" (top) +- ↑ Increasing reality of the testing +- ↓ Increasing comparability, more analytic +- Measurement Conditions (exactly defined and identical for each tests and reproducible) (bottom) + +**Auditory Tests:** + +- Conversational Tests** +2 subjects involved (one at the near end of the telephone connection, the other at the far end) +- Double Talk Tests** +2 subjects involved (one at the near end of the telephone connection, the other at the far end) +- or +- Talking and Listening Tests** +1 artificial head used (at the near end of the telephone connection), 1 subject involved (at the far end), acting as listener and talker +- Listening-only Tests** +2 artificial heads used (one at the near end of the telephone connection, the other at the far end) +1 subject as "observer" + +**Performance Parameters:** + +- End-to-end speech transmission quality +- Difficulty in communicating +- Sound quality +- Annoyance caused by echoes and switching +- Double talk performance +- Method of background noise transmission +- Speech level variations vs. time +- Comparison of individual parameters under defined conditions +- Classification of disturbances +- Database for further tests + +Arrows indicate the following connections: + +- From **Conversational Tests** to: End-to-end speech transmission quality, Difficulty in communicating, Annoyance caused by echoes and switching, Double talk performance, and Method of background noise transmission. +- From the junction between **Double Talk Tests** and **Talking and Listening Tests** to: Difficulty in communicating, Annoyance caused by echoes and switching, Double talk performance, and Method of background noise transmission. +- From **Listening-only Tests** to: Classification of disturbances and Database for further tests. + +T1212330-00 + +Diagram showing the relationship between Test Environment, Auditory Tests, and Performance Parameters. It includes categories like Realistic Conditions, Conversational Tests, Double Talk Tests, Talking and Listening Tests, and Listening-only Tests, linked to parameters such as speech transmission quality and sound quality. + +NOTE – The assignment of "near end" and "far end" is chosen according to the E-model (ITU-T Recommendation G.107). + +**Figure 2/G.108.1 – Overview of test methods used for subjective evaluation – Parameter access via interviews** + +![Diagram showing the relationship between Test Environment, Auditory Tests, and Performance Parameters. The Test Environment ranges from Realistic Conditions to Measurement Conditions. Auditory Tests include Conversational, Double Talk, Talking and Listening, and Listening-only. Performance Parameters include speech quality, communication difficulty, sound quality, etc. Arrows show how different tests access different parameters.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +**Test Environment** + +Realistic Conditions +"Human Factor" + +↑ +Increasing reality of the testing + +↓ +Increasing comparability, more analytic + +Measurement Conditions +(exactly defined and identical for each tests and reproducible) + +**Auditory Tests** + +**Conversational Tests** +2 subjects involved +(one at the near end of +the telephone connection, +the other at the far end) + +**Double Talk Tests** +2 subjects involved +(one at the near end of +the telephone connection, +the other at the far end) + +or + +**Talking and Listening Tests** +1 artificial head used +(at the near end of the +telephone connection), +1 subject involved +(at the far end), acting as +listener and talker + +**Listening-only Tests** +2 artificial heads used +(one at the near end of +the telephone connection, +the other at the far end) +1 subject as "observer" + +**Performance Parameters** + +End-to-end speech +transmission quality + +Difficulty in +communicating + +Sound quality + +Annoyance caused by +echoes and switching + +Double talk +performance + +Method of background +noise transmission + +Speech level variations +vs. time + +Comparison of individual +parameters under defined +conditions + +Classification of +disturbances + +Database for +further tests + +T1212340-00 + +Diagram showing the relationship between Test Environment, Auditory Tests, and Performance Parameters. The Test Environment ranges from Realistic Conditions to Measurement Conditions. Auditory Tests include Conversational, Double Talk, Talking and Listening, and Listening-only. Performance Parameters include speech quality, communication difficulty, sound quality, etc. Arrows show how different tests access different parameters. + +NOTE – The assignment of "near end" and "far end" is chosen according to the E-model (ITU-T Recommendation G.107). + +**Figure 3/G.108.1 – Overview of test methods used for subjective evaluation – +Parameter access by using reference conditions** + +The subjectively relevant parameters determining the "speech transmission quality" are as follows: + +- sound quality; +- method of background noise transmission at idle, under single talk and under double talk conditions; +- speech level variations during single talk and double talk conditions; +- disturbances caused by switching during single talk and double talk conditions (completeness of speech transmission); +- disturbances caused by echoes during single talk and double talk conditions; +- disturbances caused by delay and jitter; +- time-variant impairments due to transmission errors. + +Consequently, for objective evaluations it should be distinguished between evaluations under single talk conditions and between double talk evaluation. Furthermore, a third type of evaluations is required during periods of silence where only background noise is present. + +In order to serve as an approach to end-to-end scenarios a test setup should consider all components involved in the mouth-to-ear transmission; hence it should include the terminals "attached". Thereby a realistic replica of a user and his typical environment is possible. + +Some parameters mentioned in the list above are already dealt with by the E-model. + +## 4.1 Parameters describing speech transmission quality (including terminals) + +The parameters affecting the subjectively perceived speech quality and their correlating objective parameter are in general very important. An overview of the most important parameters – found in extensive auditory tests – and indication whether the parameters are covered by the E-model is provided in Table 1. + +**Table 1/G.108.1 – Correlation between subjective and objective parameters and indication whether or not parameters are covered by the E-model** + +| Subjectively relevant parameter | More detailed description | Correlating objective parameter | Covered by the E-model | +|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| Echo | Talker echo and listener echo |
  • • echo loss
  • • TCLw
  • • delay
  • • switching characteristics
|
  • • Yes
  • • Yes
  • • Yes
  • • No
| +| Absolute delay | One way transmission time caused by signal processing, packetizing and transmission |
  • • delay
|
  • • Yes
| +| Method of background noise transmission | Typically the transmission in SND direction
  • • at idle mode
  • • with far end speech
  • • with near end speech
|
  • • attenuation range
  • • attenuation in SND direction
  • • switching characteristics
  • • minimum activation level in SND direction
  • • frequency response
  • • design of NLP or center clippers in conjunction with ECDs
  • • design of noise reduction systems
  • • sensitivity of background noise detection (activation level, absolute level, level fluctuations)
|
  • • No
| + +**Table 1/G.108.1 – Correlation between subjective and objective parameters and indication whether or not parameters are covered by the E-model (concluded)** + +| Subjectively relevant parameter | More detailed description | Correlating objective parameter | Covered by the E-model | +|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| Double talk performance | Typically in SND and RCV direction
  • loudness variation between single and double talk periods
  • loudness variation during double talk
  • echo disturbances
  • occurrence of speech gaps
|
  • attenuation range
  • attenuation in SND/RCV direction during double talk
  • switching characteristics
  • minimum activation level to switch over from RCV to SND direction and from SND to RCV direction
  • echo attenuation
  • spectral and time dependent echo characteristics
  • design of NLP or center clippers in conjunction with ECDs
|
  • No
| +| Echo disturbances under single talk conditions | Measured between RCV and SND direction |
  • echo level
  • echo level fluctuation vs. time
  • spectral echo attenuation
|
  • Yes
  • No
  • No
| +| Speech sound quality | In SND and RCV direction |
  • frequency responses
  • distortions
|
  • No
  • Yes
| +| Loudness | In SND and RCV direction |
  • loudness ratings in SND and RCV
|
  • Yes
| +| Noise | In SND and RCV direction |
  • noise level
  • level fluctuations
  • spectral characteristics
|
  • Yes
  • No
  • No
| + +These parameter correlations have been identified in tests with hands-free terminals and network echo cancelling devices. It should be noted, that these parameters are of general nature, the type of device which introduces such a degradation into a telephone connection is of minor importance for the subject exposed to this degradation + +## 4.2 Test setup for terminals + +The general test setup for the assessment of terminals can be found in ITU-T Recommendations P.64 [10], P.340 [11] and P.581 [14]. In addition, ITU-T Recommendations P.57 [7] and P.58 [8] describe HATS and the artificial ears which are recommended to be used for this kind of conversational application. + +These Recommendations – dealing with standardized methods for tests under lab conditions – provide nevertheless useful information on how test setups in such an environment where the terminals are used, can be designed in practice. Basically, the individual conditions, such as background noise conditions, typical type of use of the equipment and other individual factors need to be adequately taken into account and should be reflected in the design of the test setup. Such test setups may differ from those described in the Recommendations mentioned afore but are closer to the real use condition of the connection and/or equipment under test. + +## **4.3 Test setup for echo cancelling devices** + +Echo cancellers – as a general rule – are realized as so-called "Half Echo Canceller" devices (HEC), i.e. operative into one of either directions of transmission only. HEC devices may be deployed at various places within an end-to-end telephone connection: + +- in the centre part of the network facing either terminal; +- at the edge of the network part facing the near-end terminal; +- at the edge of the network part facing the far-end terminal; +- in either of both terminals involved in the connection. + +In combination with devices which are introducing significant delay Half Echo Cancelling devices are often deployed in the network. If contained in the terminal they are intended for cancelling the acoustic echo or the (electrical) hybrid echo. Appropriate test setups for the individual devices can be found in ITU-T Recommendations G.167 [4], G.168 [5] and P.340 [11]. + +For end-to-end scenarios those Recommendations give basic information on how the setup should be made. In practice all equipment typically involved in a connection needs to be included in the test setup. For end-to-end scenarios it is obvious that the terminals should be included. If individual sections of a connection are subject to a test, it is recommended to make – in principle – use of the same end-to-end test setups. Examples for such tests are the following: + +- performance test of a network echo canceller in conjunction with a variety of typically used equipment in the end echo path; +- performance test of an acoustic canceller contained in a terminal in the specific room where the terminal is used – in conjunction with the equipment involved in the connection; or +- the performance test of echo cancellers in tandem. + +## **4.4 Test signals for conversational evaluation** + +The basis for test signals can be found in ITU-T Recommendations P.50 [6], P.59 [9], P.501 [12] and P.502 [13]; according test signals are recommended to be used for objective evaluation of the conversational situation. The signals and test methods described here can be used for the objective assessment. + +For subjective evaluation speech signals and test methods are required as described below. + +# **5 Evaluation of the conversational situation** + +In an end-to-end telephone connection the conversational situation is the most important one to be considered and the most difficult one to evaluate. This is especially true if non-linear and/or time variant systems and devices are involved in a connection. The non-linear or time variant process may be integrated in either of the terminals involved in the connection or in one of the devices forming the network. + +A very extreme situation where all types of signal processing may be present is the situation where hands-free terminals are involved in the connection. In general, the use of hands-free telephones leads to acoustical stability problems. Therefore, various types of signal processing devices such as speech detectors, level switching, echo cancellation, non-linear processes, dynamic level control and others are included in most hands-free terminals. + +As discussed above not only the echo problem causes a degradation of end-to-end speech transmission quality. The use of one of the mentioned signal processing devices – or even a multitude of them – impacts the quality in various ways. Besides echo disturbances the remarkable parameters are: + +- conversational capability; +- double talk performance; +- sound quality in send and receive direction; +- audible level variations; +- quality of background noise transmission; or +- reverberation in the listening situation. + +Some of these parameters come immediately to the attention of the subscriber and impact the quality during the whole course of a conversation. Other parameters are important only in the listening situation. In addition, there is a third group of disturbances which occurs only if either one or both subscribers involved in a connection are talking (such as echo, modulated background noise, double talk performance). + +## 5.1 Double talk performance + +A very high influence on subjectively perceived speech quality of a telephone connection results from its double talk capability; this may be due to absolute delay or by signal processing, switching, etc. Although double talk situations are not predominant in an average conversation, double talk performance is one of the main factors determining the end-to-end speech transmission quality as perceived by the user. + +If double talk capability in a telephone conversation is not given or is very restricted only, then both subscribers involved in that particular call will realize this impact immediately. In these situations a higher concentration is required from either subscriber during the entire telephone call and the naturalness of the conversation decreases. The double talk performance of the evaluated telephone connection has an influence on the quality ratings received from conversational tests. + +This (subjective) quality parameter "Double Talk Performance" is determined by several (objective) technical parameters and by the combination of various types of signal processing; accordingly, the complexity of required quality evaluation rises dramatically. These influences on double talk performance have to be distinguished according to different aspects. Subjective procedures are necessary in order to determine the significance of each parameter which should be sensitive and efficient. While evaluating the quality subjectively, specific double talk tests and third party listening only tests are applicable – besides the complete conversational tests. + +## 5.2 Subjective evaluations + +As far as the following subclauses do refer to subjective evaluations or auditory testing procedures it should be clearly understood that the procedures recommended herein, do neither replace nor supersede the appropriate ITU-T Recommendations in force. The only intention of those subclauses is to provide practical procedures in addition to the E-model for quick access to conversational impacts outside of subjective test labs. + +NOTE – Care should be taken not to express the results in terms of MOS since typically neither the conditions can be controlled in a proper way nor those conducting the test do typically have the necessary background knowledge for conducting these tests formally correct. Nevertheless such tests may be quite useful to evaluate problems seen in the field more in detail. + +### 5.2.1 Conversational evaluation + +Conversational evaluations in complex scenarios are a critical issue since – in general – no lab conditions can be achieved. Therefore, while a controlled evaluation is not possible, nevertheless a good estimate of the speech quality can be the outcome when applying the test methods as described in ITU-T Recommendations P.800 [15], P.831 [16] and P.832 [17]. + +A very simple and easy to use method for such tests are the so called short conversational tests, SCT. + +These scenarios are structured to a high degree and are natural, while resulting in conversations of approx. 2.5 min. each. For purposes of conversational tests, they seem to be more easy to use than other scenarios. A comparison with the so-called "Kandinsky" scenarios leads to similar useful test results, whereas the required conversation time is being reduced. + +A general structure for such a test is given in Figure 4. The subject for the conversations are enquiry and booking situations, where the telephone serves as a means of information exchange, i.e. a very typical purpose. The dialogue structure is provided with the test instructions, which include parts with longer monologues as well as others with various turn-takings, and some parts which are intended to evoke double talk. + +![Figure 4/G.108.1 – Possible theoretical structure of a SCT dialogue. The diagram shows a sequence of dialogue sections between a caller and a called person. The sections are: greeting (both), inquiry (caller), question (called person), precision (caller), offer (called person), order (caller), information (caller) and treating of order (called person) with a bidirectional arrow labeled 'questions' between them, discussion of open question (both), and farewell (both).](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +| caller | called person | +|-----------------------------|-------------------| +| greeting | | +| inquiry | | +| | question | +| precision | | +| | offer | +| order | | +| information | treating of order | +| ← questions → | | +| discussion of open question | | +| farewell | | + +T1212350-00 + +Figure 4/G.108.1 – Possible theoretical structure of a SCT dialogue. The diagram shows a sequence of dialogue sections between a caller and a called person. The sections are: greeting (both), inquiry (caller), question (called person), precision (caller), offer (called person), order (caller), information (caller) and treating of order (called person) with a bidirectional arrow labeled 'questions' between them, discussion of open question (both), and farewell (both). + +**Figure 4/G.108.1 – Possible theoretical structure of a SCT dialogue** + +Due to their fixed structure, the dialogues during SCTs may be significantly shorter than during more traditional types of conversational tests; while offering this advantage SCTs are still maintaining the various dialogue sections required for concise conversational tests. Various possible situations (e.g. inquiries with railway information, travel agency, pizza service, theatre reservation, medical appointment, flight schedule, car rental, etc.) increase the probability that the conversations carried out remain interesting for the test subjects, and that different type of vocabulary is used. Pictograms, tables, etc., can be used as formal and quasi-standardized means of test instruction. As none of the subjects involved in a conversational test has *a priori* knowledge which information the other subject is requesting, they cannot shorten the conversation after some dialogues (as it happens when the same scenario is being repeated several times). + +These types of tests have been used by several Administrations with success, e.g. for the subjective evaluations of hands-free terminals and echo cancellers and are for further study. + +One Administration found a very useful multi-criteria approach which had been employed to collect the opinion of the subjects involved in the test; this approach follows the suggestions in ITU-T Recommendation P.831 [16]. The following two types of questionnaire had been prepared for conducting this test: + +- a first type of questionnaire for each of the two subjects involved in the conversation under test; +- a second type of questionnaire for the observer who has the task to listen to the very same conversation under test as a third party. + +The first type of questionnaire which either of the subjects involved in the conversation had been requested to fill in after having talked with their respective conversation partner consists of six questions; whereas the second type of questionnaire which the third party observer had to fill in consists only of a subset of four questions (see Table 2). The specific question (i.e. Question No. 4) related to the sound level is not intended for speech performance evaluation; but as it is supposed to get a constant mean score (requires appropriate test setup) it may be used for normalization purposes. + +**Table 2/G.108.1 – Questionnaires for multi-criteria approach** + +| Questionnaire for either of the two subjects involved in the conversation | | Questionnaire for the third party observer (not actively involved in the conversation) | | +|----------------------------------------------------------------------------------|-----------------------------------------------------------|-----------------------------------------------------------------------------------------------|-------------------------------------------------| +| Q.1 | Fidelity of your partner's voice | Q.1 | Fidelity of the voices | +| Q.2 | Annoyance due to the perception of your own voice delayed | | | +| Q.3 | Annoyance due to various perceived degradations | Q.2 | Annoyance due to various perceived degradations | +| Q.4 | Effort to interrupt your partner | | | +| Q.5 | Sound level | Q.3 | Sound level | +| Q.6 | Overall quality | Q.4 | Overall quality | + +NOTE – The third party observer in the test described here should be attached to the conversation under test by using a passive circuitry – thus not influencing the conversation. The use of conference or multi-line circuits – which may actively influence the two-party conversation – should not be considered for this type of test. + +### **5.2.2 Specific double talk tests and listening only tests** + +Although a continuous process of improvement of objective measurement techniques for the assessment of speech transmission quality is under way, subjective tests are still required. This subclause gives an overview of different subjective evaluation procedures for hands-free telephones and network echo cancellers which have been developed by ITU-T during the study period 1997-2000. The objective of these subjective tests is the evaluation of the performance under double talk conditions. Based on a brief overview of possible influences of hands-free telephones on the perceived quality, different kinds of subjective test procedures are described. Each of these procedures has a certain purpose and the combination of all tests provides a very comprehensive evaluation tool. + +The double talk test procedure as described in ITU-T Recommendation P.832 [17] allows a very specific evaluation of the double talk situation and can be used for complete end-to-end scenarios; some administrations have applied this method successfully, e.g. for the hands-free situation. Typical parameters found in such tests are: + +- double talk capability; +- completeness of speech transmission; +- loudness during double talk; +- echo level; +- echo characteristics; +- sound quality; +- transmission of background noise. + +Listening only tests as described in ITU-T Recommendations P.800 [15], P.831 [16] and P.832 [17] can be employed to investigate speech impacting parameters with a very refined granularity. More easily than other types of tests, these tests will allow to identify impacts in detail and assign them to specific technical implementations. + +As a matter of fact such listening tests are less realistic (see Figures 1 through 3) than other, e.g. conversational tests; but especially in third party listening tests it is possible to investigate even conversational situations. Further guidance on these issues is provided by ITU-T Recommendations P.831 [16] and P.832 [17]. + +## 5.3 Objective evaluations + +It is important that the design of objective measurements for terminals, networks and end-to-end scenarios be chosen appropriately in order to evaluate each of the important parameters. These parameters have been identified by and derived from subjective tests which were conducted for hands-free terminals and network echo cancellers. + +The application of objective tests can be directed towards the assessment of values for these parameters as well as towards compliance checks with respect to requirement limits for each of these parameters; whereby the definition of the requirement limits itself is also based on subjective tests results. This combination of subjective testing for parameter identification and value selection on the one hand and the more efficient objective laboratory tests on the other hand provide a good correlation of objective measures with subjectively perceived speech quality. + +The objective test methods derived accordingly are described in ITU-T Recommendation P.502 [13]. Such test methods can be applied to all scenarios where the impact on speech quality which may be described by parameters listed in Table 1. The objective test methods take into account background noise scenarios, single talk conditions and the conversational situation. For all scenarios a detailed, diagnostic evaluation can be made. + +Besides these parameter oriented methods, a more general investigation with respect to end-to-end speech transmission performance may be conducted by applying methods which are based on modelling the human perception of speech; they are described in ITU-T Recommendation P.861 [18] and other methods which were under study by ITU-T during the study period 1997-2000. Further guidance on perceptual speech quality measurement methods is provided in ETSI EG 201 377-1 [19]. + +# 6 Guidance on the improvement of conversational speech quality + +Based on the investigations made for hands-free terminals and network echo cancelling devices, the important parameters impacting the speech transmission quality are well known. It should be noted, that these parameters are of a general nature and do not specifically refer to a certain technical implementation. From a subjective point of view there is no perception with regard to the type, number or location of any network or terminal elements that cause any impact to the telephone connection, as e.g. echo or switching; only the parameters measured with regard to this impact are important for the speech quality as perceived by the subscriber. + +The perceived speech quality parameters are listed below in detail. + +The test signals can be found in ITU-T Recommendations P.50 [6], P.59 [9] and P.501 [12], the test methods can be found in ITU-T Recommendation P.502 [13]. + +Requirement limits for the individual parameters can be found in ITU-T Recommendation P.340 [11]. Although not all requirement limits for the individual parameters have been evaluated yet, many important parameters are already defined. ITU-T Recommendation P.340 [11] provides information on echo loss requirements during double talk and on switching parameters. Although + +these parameters have been evaluated in subjective tests for combinations of hands-free terminals and handset terminals, the values provided herein can be applied to other scenarios with a sufficient degree of confidence. + +In addition, requirement limits for echo cancellers, especially on their convergence behaviour, their performance in the presence of background noise and in double talk situations can be found in ITU-T Recommendation G.168 [5]. These requirement limits are also based on subjective evaluations of the various parameters. + +## **6.1 Delay and echo** + +Impacts to end-to-end speech transmission performance due to high values of absolute delay or due to talker or listener echo are the most obvious to the subscribers of a telephone connection. For simple situations where a constant delay and a non-time variant echo loss can be assumed, the E-model gives good estimations of the speech degradation introduced by delay and echo. + +If, however, the echo loss is time variant and associated with switching and or time variant loudness variation (caused, e.g. by VAD, non-linear processors and other types of signal processing) a more detailed evaluation is necessary. + +In this case it is recommended to employ the methods described in clause 6. + +## **6.2 Background noise transmission** + +Impacts due to background noise transmission may turn out to be the most disturbing ones. In general, the background noise should be transmitted with a low level and with as less variations – in the time and in the frequency domain – as possible. Any injection of so-called "comfort-noise" should be rendered inoperative in cases where the time or frequency characteristic cannot be reproduced correctly; it should be noted that comfort-noise injection typically occurs in conjunction with switching effects. + +In the presence of background noise any speech detection device should work reliable in order not to cut off syllables or parts thereof. + +Furthermore, background noise performance of low-bitrate codecs might in some cases not be correctly covered by the corresponding $I_e$ (equipment impairment factor) value and the $R_o$ value (taking the room noise at send side, $P_s$ , into account) in the E-model. This holds true, if the additivity of both impairments is not strictly satisfied. In such cases, an integral $I_e$ value may be determined for the codec working under background noise conditions. For the derivation of such an $I_e$ value, the Lombard effect (the effect of a person adapting its speaking behaviour in a noisy environment) should be included in the subjective test setup, namely the recordings should be made in the noisy environment. This is important in order to cover the conversational impacts of the background noise in a realistic way. An $I_e$ value derived by this procedure can then be used as an input to the E-model, setting the $P_s$ parameter to its default value ( $P_s = 35$ dB(A)). + +Background noise in many situations is being considered as a plain signal in cases where there is no other signal present beside the background noise. + +The requirement limits for the background noise transmission have not yet been evaluated in detail and thus are for further study. However, the test procedures have been defined and can be found in ITU-T Recommendation P.502 [13]. + +While evaluating configurations with respect to the presence of background noise at the far-end subscriber side no additional (circuit or near-end) noise should be inserted. + +The transmission method of background noise (from the near end in sending direction) can be evaluated: + +- at idle mode; +- with far end speech; +- with near end speech. + +In all these cases important parameters are: + +- the sensitivity of background noise detection in terms of activation level; +- the absolute level of the transmitted signal; +- level fluctuations; +- variation of the spectral content of the background noise. + +## **6.3 Double talk performance** + +The double talk situation is the most critical one for configurations where various types of signal processing (e.g. echo cancellation, level dependant switching and attenuation) are involved. Conversational tests in combination with double talk tests and third party listening tests proved the importance of the double talk situation in a complete conversation (see annexes to Recommendation P.340 [11]). The most annoying effects during double talk are: + +- sentences, words, syllables or parts thereof being interrupted or being not completely transmitted during or shortly after/before double talk; +- transmission of speech and/or background noise with time variable level causing annoying "level variations during double talk"; +- echo during double talk. + +The most critical situations during double talk are the time intervals shortly before and shortly after double talk. + +In this case it is recommended to employ the methods described in clause 6. + +## **6.4 Quality of speech sound and loudness** + +Speech sound quality are mainly determined by the terminals. For handsets it is important to measure these parameters in a most realistic condition. This requires the measurement setup using HATS in combination with type 3.3 or 3.4 ears and positioning according to ITU-T Recommendation P.64 [10]. By employing this setup the acoustical coupling of the signal as well as of the noise is achieved in a very realistic manner. Speech sound quality can – in a first step – be determined by measuring the standard parameters frequency response and loudness rating. + +Care should be taken in order to use the appropriate test signals to receive the correct estimations for frequency responses and loudness ratings. + +Speech or speech-like signals should be used in test scenarios where one or more of the involved network or terminal elements are unknown (e.g. proprietary low bit-rate coding). + +In this case it is recommended to employ the methods described in clause 6. + +# **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/G/T-REC-G.117-199602-I_PDF-E/raw.md b/marked/G/T-REC-G.117-199602-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a03bf386d5b5aa7304d0b6786894061dae11d311 --- /dev/null +++ b/marked/G/T-REC-G.117-199602-I_PDF-E/raw.md @@ -0,0 +1,596 @@ + + +![ITU logo: A globe with the letters ITU and a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with the letters ITU and a lightning bolt. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**G.117** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(02/96) + +**TRANSMISSION SYSTEMS AND MEDIA** + +**GENERAL CHARACTERISTICS OF INTERNATIONAL +TELEPHONE CONNECTIONS AND INTERNATIONAL +TELEPHONE CIRCUITS** + +--- + +**TRANSMISSION ASPECTS OF +UNBALANCE ABOUT EARTH** + +**ITU-T Recommendation G.117** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). + +ITU-T Recommendation G.117 was revised by ITU-T Study Group 12 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 6th of February 1996. + +--- + +# NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +| | | Page | +|------------|------------------------------------------------------------------------------------------------------------------|-------------| +| 1 | Objective ..... | 1 | +| 2 | Principles of the scheme of nomenclature ..... | 1 | +| 3 | Summary of the descriptive terms used..... | 2 | +| 3.1 | One-port networks ..... | 2 | +| 3.2 | Two-port networks ..... | 2 | +| 3.3 | Signal generating devices ..... | 2 | +| 3.4 | Signal receiving devices ..... | 2 | +| 4 | Definitions and measuring techniques based on idealized measuring arrangements ..... | 3 | +| 4.1 | One-port networks ..... | 4 | +| 4.2 | Two-port networks ..... | 7 | +| 4.3 | Signal generating devices ..... | 10 | +| 4.4 | Signal receiving devices ..... | 11 | +| 5 | Other measurement definitions ..... | 12 | +| 5.1 | Common-mode rejection ratio ..... | 13 | +| Annex A | – Aspects of conversion from longitudinal to transversal signals at analogue ports in some practical cases ..... | 14 | +| A.1 | Introduction ..... | 14 | +| A.2 | Calculation of the longitudinal conversion loss ..... | 14 | +| A.3 | The difference between $LCL_c$ and $LCL_m$ in a practical case – two examples..... | 16 | +| A.4 | Additional Insight into Longitudinal Conversion Loss ..... | 16 | +| References | ..... | 18 | + +# **SUMMARY** + +In many applications, the balance performance of equipment is crucial in order to ensure a satisfactory suppression of unwanted signals from the normal transmission path. This Recommendation gives guidance of suitable measurement methods for evaluating different effects of unbalance. + +# TRANSMISSION ASPECTS OF UNBALANCE ABOUT EARTH + +(Geneva, 1980; amended at Malaga-Torremolinos, 1984 and Melbourne, 1988; +revised in 1996) + +# 1 Objective + +This Recommendation gives a comprehensive set of prescriptive measurements of various balance parameters for one-port and two-port networks. These are intended for use either in the field or in the factory with relatively simple test apparatus (e.g. standard transmission oscillators, level measuring sets), and a special test bridge. Measuring arrangements for assessing the degree of unbalance are covered in Recommendation O.9 [1], which are consistent with this Recommendation. + +The definitions and methods are so devised that the results obtained from separately-measured (or specified) items of equipment (e.g. feeding-bridges, cable pairs, audio inputs to channel translating equipment, etc.) can be meaningfully combined though not necessarily by simple decibel addition. This allows the performance of a tandem connection of such items to be predicted or at least, bounds determined for that performance. Performance in this sense means those features affected by unbalanced conditions, e.g. level of impulsive noise, sensitivity to longitudinal exposure, crosstalk ratios, etc. + +# 2 Principles of the scheme of nomenclature + +Many different terms have been used throughout the literature concerning unbalance about earth, some conflicting, or in other respects inadequate. The descriptive titles of the quantities given in this Recommendation are based on the following principles which have been adopted: + +- a) Mode *conversion*, e.g. a poor (unbalanced) termination will develop an unwanted transverse signal when excited by a longitudinal signal. The measure of this effect is here termed *longitudinal conversion ratio*, and when expressed in transmission units *Longitudinal Conversion Loss*, or LCL. +- b) When a two-port is involved where for example an excitation at one port produces a signal at the other port, then the designation will include the word *transfer*, for example *longitudinal conversion transfer ratio* and the corresponding *loss*, LCTL. +- c) The impedance of the longitudinal path presented by a test object is a key parameter. The term *longitudinal impedance ratio* and the corresponding decibel expression, *longitudinal impedance loss*, are used to characterize the particular measurement defined. +- d) Active devices which are sources of signals (e.g. an oscillator, the output port of an amplifier) are additionally characterized by the amount of unwanted longitudinal signal that is present in the output. The key word *output* is now included, to give *longitudinal output voltage*, and the corresponding *longitudinal output level*. When such unwanted signals are expressed as a proportion of the wanted (transverse) signal the key phrase is *output signal balance ratio*, the decibel expression of which is *output signal balance*. +- e) Devices which continuously respond to signals (e.g. level-measuring sets, the input port of an amplifier) and which can in principle respond to unwanted longitudinal signals by reason of internal mechanisms (i.e. even if their input impedances were perfectly balanced) are characterized by measures containing the words *input interference*. These measures are *input longitudinal interference ratio* and the corresponding decibel expression *input longitudinal interference loss*. The long-established and well-defined *common-mode rejection ratio* is maintained. The term *sensitivity coefficient* is avoided, since this is widely used in the Directives [2] and the work of Study Group 5 with a rather specialized meaning. + +- f) When a two-port network is involved, the input and output signals may not be the same, for example, they may have different levels, frequencies (FDM modems) or structure (PCM multiplex equipments). These aspects should be taken into account when formulating proposals for the item under test. +- g) In the case of receiving devices in which the operation is not a linear continuous function of the level of the input signal (e.g. a group-delay measuring set or a data modem) the key principle is the *threshold* level of the interference; this is the level at or above which an unacceptable amount of degradation of performance or misoperation occurs. Thus *longitudinal interference threshold voltage* and the corresponding *levels* are obtained. + +# 3 Summary of the descriptive terms used + +## 3.1 One-port networks + +- a) transverse reflexion factor (transverse return loss: TRL); +- b) transverse conversion ratio (loss: TCL); +- c) longitudinal conversion ratio (loss: LCL); +- d) longitudinal impedance ratio (loss: LIL); +- e) transverse output voltage (level: TOL); +- f) longitudinal output voltage (level: LOL). + +Voltages e) and f) are unwanted signals uncorrelated to the wanted signals. + +## 3.2 Two-port networks + +#### 3.2.1 Separate measurement + +For each port taken separately the one-port measures: + +- a) transverse reflexion factors (transverse return losses: TRL); +- b) transverse conversion ratio (loss: TCL); +- c) longitudinal conversion ratios (losses: LCL); +- d) longitudinal impedance ratios (losses: LIL); +- e) transverse output voltage (levels: TOL); +- f) longitudinal output voltage (levels: LOL). + +#### 3.2.2 Measurement combined + +In addition, the following transfer parameters are for each of the two directions of transmission: + +- a) transverse transfer ratios (losses: TTL); +- b) transverse conversion transfer ratios (losses: TCTL); +- c) longitudinal transfer ratios (losses: LTL); +- d) longitudinal conversion transfer ratios (losses: LCTL). + +## 3.3 Signal generating devices + +- Output signal balance ratio (losses: OSB). + +This is in addition to the six one-port measures listed in 3.1. + +## 3.4 Signal receiving devices + +- a) Input longitudinal interference ratio (loss: ILIL). +- b) Longitudinal interference threshold voltage (level). + +These are in addition to the six one-port measures listed in 3.1. If the wanted signal is longitudinal (e.g. as in a signalling system) and the interfering voltage transverse, replace the word *longitudinal* with *transverse* in the descriptive terms. + +# 4 Definitions and measuring techniques based on idealized measuring arrangements + +The illustrated definitions in this clause assume ideal test bridges (with lossless infinite-inductance centre-tapped coils), zero impedance voltage generators and infinite-impedance voltmeters. + +An important aspect of this set of mutually consistent measurements is that the test bridge provides simultaneously defined reference terminations of $Z$ ohms for the transverse paths, and $Z/4$ ohms for the longitudinal paths. From this starting point, the performance of cascaded items, each measured in the prescribed fashion, can be calculated. This takes account of the fact that the cascaded items do not, in general, exhibit the reference impedances provided by the test conditions. + +It simplifies the mathematical treatment if the reference impedance is non-reactive and this also accords with the important objective of being able to use readily-available transmission test-apparatus to obtain field and factory measurement results. + +The ideal test bridge configuration used in the following pages is shown in Figure 1. + +Note, however, that this test bridge configuration, with transversal impedance $Z$ and longitudinal impedance $Z/4$ , in general does not represent conditions met in practice. Thus, some care is needed when translating measured unbalance parameters into useful unbalance information for practical cases. This applies in particular for the commonly used parameter LCL, Longitudinal Conversion Loss. This is discussed in more detail in Annex A. + +The transverse and longitudinal sources $E_T$ and $E_L$ are activated as required by the particular measurement being made. In Figure 6, neither source is active, and the bridge then provides only passive terminations of $Z$ and $Z/4$ . + +NOTE – It would have been in keeping with traditional transmission theory for the parameters to be defined in terms of half the open-circuit e.m.f. However, to harmonize with Recommendation O.9, this Recommendation defines some parameters in terms of $V_{T1}$ . If the input impedance of the device under test is nominally equal to the driving device, then the two methods are equivalent. + +![Circuit diagram of an ideal test bridge configuration. It shows a central vertical wire with a resistor Z and voltage source E_T in parallel at the top, and a resistor Z/4 and voltage source E_L in series at the bottom. On the right, there are two sets of terminals. The top set is labeled 'Transverse termination' with a bracket, connected across the top parallel combination. The bottom set is labeled 'Longitudinal termination' with a bracket, connected across the bottom series combination. The diagram is labeled T1208210-96/d01 at the bottom right.](ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg) + +Circuit diagram of an ideal test bridge configuration. It shows a central vertical wire with a resistor Z and voltage source E\_T in parallel at the top, and a resistor Z/4 and voltage source E\_L in series at the bottom. On the right, there are two sets of terminals. The top set is labeled 'Transverse termination' with a bracket, connected across the top parallel combination. The bottom set is labeled 'Longitudinal termination' with a bracket, connected across the bottom series combination. The diagram is labeled T1208210-96/d01 at the bottom right. + +FIGURE 1/G.117 + +## 4.1 One-port networks + +#### 4.1.1 Transverse reflexion factor (return loss) (see Figure 2) + +![Circuit diagram for measuring transverse reflexion factor. A voltage source E_T is connected in series with two resistors R. This is in parallel with a series combination of a resistor Z and an inductor Z. A transmission line with characteristic impedance Z_T is connected across the inductor Z. The voltage across the transmission line is V_T. A resistor Z/4 is connected between the bottom of the inductor and ground. The voltage across the resistors R is V_R.](990567efebf979be51f56d1150012c9d_img.jpg) + +Circuit diagram for measuring transverse reflexion factor. A voltage source E\_T is connected in series with two resistors R. This is in parallel with a series combination of a resistor Z and an inductor Z. A transmission line with characteristic impedance Z\_T is connected across the inductor Z. The voltage across the transmission line is V\_T. A resistor Z/4 is connected between the bottom of the inductor and ground. The voltage across the resistors R is V\_R. + +T1208220-96/d02 + +$$\text{Transverse reflexion factor } \rho = \frac{Z - Z_T}{Z + Z_T} = \frac{\text{reflected voltage}}{\text{forward voltage}} = \frac{2V_R}{E_T}$$ + +and + +$$\text{Transverse Return Loss (TRL)} = 20 \log_{10} \left| \frac{1}{\rho} \right| = 20 \log_{10} \left| \frac{E_T}{2V_R} \right| \text{ dB}$$ + +##### NOTES + +- 1 The value of $R$ is (theoretically) irrelevant. The potential divider across the zero-impedance generator is only needed to derive half the generator voltage, which is numerically equal to the forward voltage needed for the definition. +- 2 Conventional return-loss measuring bridges do not terminate the longitudinal path with $Z/4$ . This is unimportant when the return loss is some 20 dB or so less than the longitudinal conversion loss of the test object. In this case the reflected power is substantially greater than the power diverted to the longitudinal path, and there is negligible error. +- 3 If $Z_T$ is known then clearly $\rho = 1 - \frac{2V_T}{E_T}$ is not needed. If $V_T$ is measured $\rho$ can be calculated from the expression $\rho = 1 - \frac{2V_T}{E_T}$ , which is however somewhat inconvenient for high values of return loss. + +FIGURE 2/G.117 + +#### 4.1.2 Transverse conversion ratio (loss) (see Figure 3) + +![Circuit diagram for transverse conversion ratio measurement. A signal generator is connected to a network with impedance Z. A voltage source V_T is applied across the network. The output voltage V_L is measured across a load impedance Z/4. The diagram is labeled T1208230-96/d03.](acfc53eca625d62b38aa2563efa95c3e_img.jpg) + +Circuit diagram for transverse conversion ratio measurement. A signal generator is connected to a network with impedance Z. A voltage source V\_T is applied across the network. The output voltage V\_L is measured across a load impedance Z/4. The diagram is labeled T1208230-96/d03. + +Transverse conversion ratio, $k = \frac{V_L}{V_T}$ + and + Transverse Conversion Loss (TCL) = $20 \log_{10} \left| \frac{1}{k} \right| = 20 \log_{10} \left| \frac{V_T}{V_L} \right| \text{ dB}$ + +##### NOTES + +- 1 In the case where the network is linear passive and bilateral, the transverse Conversion Loss (TCL) is equal to half the longitudinal conversion ratio $c$ . However, this relationship is not true for other network arrangements. +- 2 The dotted component is needed for a two-terminal device which, when in use, only bridges the transmission circuit and will not be explicitly referred to again. + +FIGURE 3/G.117 + +#### 4.1.3 Longitudinal conversion ratio (loss) (see Figure 4) + +![Circuit diagram for longitudinal conversion ratio measurement. A signal generator is connected to a network with impedance Z. The output voltage V_T is measured across the network. A voltage source E_L is applied across a load impedance Z/4. The diagram is labeled T1208240-96/d04.](0b87abe67b21a93777287649c33e755d_img.jpg) + +Circuit diagram for longitudinal conversion ratio measurement. A signal generator is connected to a network with impedance Z. The output voltage V\_T is measured across the network. A voltage source E\_L is applied across a load impedance Z/4. The diagram is labeled T1208240-96/d04. + +Longitudinal conversion ratio, $c = \frac{V_T}{E_L}$ + and + Longitudinal Conversion Loss (LCL) = $20 \log_{10} \left| \frac{1}{c} \right| = 20 \log_{10} \left| \frac{E_L}{V_T} \right| \text{ dB}$ + +##### NOTES + +- 1 This measure is variously referred to in other Recommendations as: + - a) Longitudinal balance. + - b) Degree of unbalance. + - c) Unbalance. + - d) Degree of longitudinal balance. + - e) Signal balance ratio. + - f) Impedance unbalanced to earth. +- 2 The longitudinal conversion ratio is applicable to any one-port, even to those which are sources of signals (e.g.: oscillateur output terminals). In such cases the transverse voltage $V_T$ must be measured selectively if it is required to measure this loss in respect of a signal generator in operation. + +FIGURE 4/G.117 + +#### 4.1.4 Longitudinal impedance ratio (loss) (see Figure 5) + +![Circuit diagram for longitudinal impedance ratio measurement. A rectangular box represents the test object. A resistor Z is connected across its input terminals. A voltage source E_L is connected in series with a resistor Z/4 between the input and ground. The voltage across Z/4 is labeled V_L. A label T1208250-96/d05 is present.](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +Circuit diagram for longitudinal impedance ratio measurement. A rectangular box represents the test object. A resistor Z is connected across its input terminals. A voltage source E\_L is connected in series with a resistor Z/4 between the input and ground. The voltage across Z/4 is labeled V\_L. A label T1208250-96/d05 is present. + +Longitudinal impedance ratio, $q = \frac{E_L}{V_L}$ + and + Longitudinal Impedance Loss (LIL) = $20 \log_{10} |q| = 20 \log_{10} \left| \frac{E_L}{V_L} \right| \text{ dB}$ + +##### NOTES + +- 1 This is an additional measure that is needed if the performance of a cascade of items is to be predicted. +- 2 In the case of test-objects which are virtually earth free (e.g.: double-insulated, portable test apparatus with no deliberate connection to earth) the value of $V_L$ will be very small and the corresponding ratio (and loss) will be very large. In such cases the coupling introduced between longitudinal and transverse paths will be very small and the effect is not important. + +FIGURE 5/G.117 + +#### 4.1.5 Transverse and longitudinal output voltages (levels) (see Figure 6) + +![Circuit diagram for transverse and longitudinal output voltages. A rectangular box represents the test object. A resistor Z is connected across its output terminals, with the voltage across it labeled V_T. A resistor Z/4 is connected between one output terminal and ground, with the voltage across it labeled V_L. A label T1208260-96/d06 is present.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +Circuit diagram for transverse and longitudinal output voltages. A rectangular box represents the test object. A resistor Z is connected across its output terminals, with the voltage across it labeled V\_T. A resistor Z/4 is connected between one output terminal and ground, with the voltage across it labeled V\_L. A label T1208260-96/d06 is present. + +Transverse output voltage = $V_T$ + Transverse Output Level (TOL) = $20 \log_{10} \left| \frac{V_T}{1 \text{ volt}} \right| \text{ dBV}$ + Longitudinal output voltage = $V_L$ + Longitudinal output level (LOL) = $20 \log_{10} \left| \frac{V_L}{1 \text{ volt}} \right| \text{ dBV}$ + +##### NOTES + +- 1 These measures relate to unwanted signals uncorrelated to the wanted signal. For example, a.d.c. signaling system in the longitudinal path may deliver unwanted transverse signals. Similarly the output of an amplifier may deliver an unwanted longitudinal "hum" signal, or a cable pair may deliver unwanted longitudinal signals arising from induction or radiation. +- 2 Other reference voltages than 1 volt may be used, for example 0.775 V for 1 mW at 600 $\Omega$ (with the designation dB [3]). + +FIGURE 6/G.117 + +## 4.2 Two-port networks + +These follow similar principles to those defined for one-port networks but now signals can be transferred from one port to the other. The two ports are distinguished by the subscripts 1/1' for one end and 2/2' for the other. There are two types of measurements: + +- those in which the excitation and response are at the same side of the network; these are as already defined for a one-port but will carry a single subscript 1/1' or 2/2' as appropriate; +- those in which the excitation and response are at opposite sides of the network. The designation will contain the word transfer and the symbol two subscripts, the order of which indicates the direction of transmission. + +#### 4.2.1 Transverse reflexion factors (return losses) (see Figure 7) + +![Circuit diagram of a two-port network. A central rectangular block represents the network with input ports 1 and 1' on the left, and output ports 2 and 2' on the right. Port 1 is connected to a voltage source E_T1 in series with a resistor R. Port 1' is connected to a resistor Z/4 in series with a ground connection. Port 2 is connected to a load Z in series with a resistor Z/4. Port 2' is connected to a ground connection. The voltage across the resistor R at port 1 is labeled V_R1. The impedance presented by port 1/1' when port 2/2' is terminated is labeled Z_T1. The diagram is labeled T1208270-96/d07.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +Circuit diagram of a two-port network. A central rectangular block represents the network with input ports 1 and 1' on the left, and output ports 2 and 2' on the right. Port 1 is connected to a voltage source E\_T1 in series with a resistor R. Port 1' is connected to a resistor Z/4 in series with a ground connection. Port 2 is connected to a load Z in series with a resistor Z/4. Port 2' is connected to a ground connection. The voltage across the resistor R at port 1 is labeled V\_R1. The impedance presented by port 1/1' when port 2/2' is terminated is labeled Z\_T1. The diagram is labeled T1208270-96/d07. + +$$\text{Transverse reflexion factor at port } 1/1' = p_1 = \frac{Z - Z_{T1}}{Z + Z_{T1}} = \frac{2V_{R1}}{E_{T1}}$$ + +and + +$$\text{Transverse Return Loss at port } 1/1' \text{ (TRL}_1\text{)} = 20 \log_{10} \left| \frac{1}{p_1} \right| = 20 \log_{10} \left| \frac{E_{T1}}{2V_{R1}} \right| \text{ dB.}$$ + +and similarly for port 2/2' (TRL2) + +NOTE – $Z_{T1}$ is the impedance presented by port 1/1' when port 2/2' is terminated with a test-bridge as shown. + +FIGURE 7/G.117 + +#### 4.2.2 Transverse transfer ratios (losses) and conversion transfer ratios (losses) (see Figure 8) + +![Circuit diagram for Figure 8/G.117 showing a two-port network with input and output impedances and voltages.](007b053fe94a8348f75128a584503fd0_img.jpg) + +The diagram shows a two-port network represented by a rectangle with four terminals: 1, 2, 1', and 2'. A voltage source \$V\_{T1}\$ is connected across terminals 1 and 1'. An impedance \$Z\_1\$ is connected in parallel with the input at terminals 1 and 1'. A longitudinal impedance \$Z\_{L1}\$ is connected between terminal 1' and ground. The output terminals 2 and 2' are connected to an impedance \$Z\_2\$ across which a voltage \$V\_{T2}\$ is measured. A longitudinal impedance \$Z\_{L2}\$ is connected between terminal 2' and ground, across which a voltage \$V\_{L2}\$ is measured. The ground connection is common to \$Z\_{L1}\$, \$Z\_{L2}\$, and the negative terminal of the output voltage source. The text 'T1208280-96/d08' is present in the bottom right of the diagram. + +Circuit diagram for Figure 8/G.117 showing a two-port network with input and output impedances and voltages. + +$$\text{Transverse transfer ratio 1 to 2} = g_{12} = \frac{V_{T2}}{V_{T1}}$$ + +and + +$$\text{Transverse Transfer Loss 1 to 2 (TTL}_{12}) = 20 \log_{10} \left| \frac{1}{g_{12}} \right| = 20 \log_{10} \left| \frac{V_{T1}}{V_{T2}} \right| \text{ dB}$$ + +$$\text{Transverse conversion transfer ratio 1 to 2} = t_{12} = \frac{V_{L2}}{V_{T1}}$$ + +and + +$$\text{Transverse Conversion Transfer Loss 1 to 2 (TCTL}_{12}) = 20 \log_{10} \left| \frac{1}{t_{12}} \right| = 20 \log_{10} \left| \frac{V_{T1}}{V_{L2}} \right| \text{ dB}$$ + +Interchanging 1 and 2 gives the definition for the transfer ratios TCTL for the other direction of transmission. + +NOTE – $Z_1$ and $Z_2$ are the terminating impedances connected to the input and/or output port respectively of the item under test. $Z_1$ and $Z_2$ are generally within $\pm 25$ percent of the nominal impedance of the port to which they are connected. If measurements are made via high-impedance input ports, an additional impedance $Z_1$ should be connected to the input port 1/1'. The longitudinal impedances $Z_{L1}$ , and $Z_{L2}$ are nominally equal to $Z_1/4$ and $Z_2/4$ respectively. Different values, however, may be used. This may be necessary to more properly simulate operating conditions of the time under test. In such cases the value of $Z_{L1}$ or $Z_{L2}$ shall be specified by the Recommendation covering the item under test. + +FIGURE 8/G.117 + +#### 4.2.3 Longitudinal transfer ratios (losses) and conversion transfer ratios (losses) (see Figure 9) + +![Circuit diagram for measuring longitudinal transfer ratios. A central box represents the item under test with four ports: 1, 2, 1', and 2'. Port 1 is connected to a parallel combination of impedance Z1 and an inductor. Port 1' is connected to a series combination of impedance ZL1 and an e.m.f. source EL1. Port 2 is connected to a parallel combination of impedance Z2 and an inductor, with the output voltage VT2 measured across Z2. Port 2' is connected to a series combination of impedance ZL2 and a ground connection, with the voltage VL2 measured across ZL2. The diagram is labeled T1208290-96/d09.](4e4be0bd8b235167902f2c03e41da651_img.jpg) + +Circuit diagram for measuring longitudinal transfer ratios. A central box represents the item under test with four ports: 1, 2, 1', and 2'. Port 1 is connected to a parallel combination of impedance Z1 and an inductor. Port 1' is connected to a series combination of impedance ZL1 and an e.m.f. source EL1. Port 2 is connected to a parallel combination of impedance Z2 and an inductor, with the output voltage VT2 measured across Z2. Port 2' is connected to a series combination of impedance ZL2 and a ground connection, with the voltage VL2 measured across ZL2. The diagram is labeled T1208290-96/d09. + +$$\text{Longitudinal transfer ratio 1 to 2} = m_{12} = \frac{V_{L2}}{E_{L1}}$$ + +and + +$$\text{Longitudinal Transfer Loss 1 to 2 (LTL}_{12}\text{)} = 20 \log_{10} \left| \frac{1}{m_{12}} \right| = 20 \log_{10} \left| \frac{E_{L1}}{V_{L2}} \right| \text{ dB}$$ + +$$\text{Longitudinal conversion transfer ratio 1 to 2} = h_{12} = \frac{V_{T2}}{E_{L1}}$$ + +and + +$$\text{Longitudinal Conversion Transfer Loss 1 to 2 (LCTL}_{12}\text{)} = 20 \log_{10} \left| \frac{1}{h_{12}} \right| = 20 \log_{10} \left| \frac{E_{L1}}{V_{T2}} \right| \text{ dB}$$ + +Interchanging ports 1/1' and 2/2' gives the definition for the transfer ratios and losses $\text{LTL}_{21}$ and $\text{LCTL}_{21}$ for the other direction of transmission. + +##### NOTES + +- 1 This measure is referred to in other Recommendations as *impedance imbalance to earth*. +- 2 It would have been more in keeping with traditional transmission theory if these quantities were defined in terms of *half* the open-circuit e.m.f. However, the ITU-T Recommendations concerning balance parameters involving a longitudinal excitation are already in terms of the open-circuit e.m.f. It is not thought useful to introduce a 6-dB “discrepancy” between existing practice and these new definitions. +- 3 $Z_1$ et $Z_2$ are the impedances connected in parallel to the input and/or output port respectively of the item under test. $Z_1$ and $Z_2$ are generally within $\pm 25$ percent of the nominal impedance of the port to which they are connected. If measurements are made via high-impedance input ports, an additional impedance $Z_1$ should be connected between ports 1/1'. The longitudinal impedances $Z_{L1}$ , and $Z_{L2}$ are nominally equal to $Z_1/4$ or $Z_2/4$ respectively. Different values, however, may be used. This may be necessary to properly simulate operating conditions of the item under test. In such cases the value $Z_{L1}$ and/or $Z_{L2}$ shall be specified by the Recommendation covering the item under test. + +FIGURE 9/G.117 + +## 4.3 Signal generating devices + +In addition to the six one-port measures already defined, an additional measure is required to control the amount of unwanted signal correlated with the wanted signal delivered by the device to the circuit it is connected to. This special measure is the output signal balance ratio (loss). + +#### 4.3.1 Output signal balance ratio (loss) (see Figure 10) + +![Circuit diagram for measuring output signal balance ratio. A signal source E_T is connected to a network. The network consists of a series inductor and a shunt resistor Z. The output voltage across Z is V_T. A second shunt resistor Z/4 is connected between the negative terminal of the source and ground. The voltage across Z/4 is V_L. The diagram is labeled T1208300-96/d10.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Circuit diagram for measuring output signal balance ratio. A signal source E\_T is connected to a network. The network consists of a series inductor and a shunt resistor Z. The output voltage across Z is V\_T. A second shunt resistor Z/4 is connected between the negative terminal of the source and ground. The voltage across Z/4 is V\_L. The diagram is labeled T1208300-96/d10. + +$$\text{Output signal balance ratio, } b = \frac{V_L}{V_T}$$ + +and + +$$\text{Output signal balance loss (OSB)} = 20 \log_{10} \left| \frac{1}{b} \right| = 20 \log_{10} \left| \frac{V_T}{V_L} \right| \text{ dB}$$ + +##### NOTES + +- 1 This measure is a generalized version of the quantities referred to as the unbalance of output e.m.f. +- 2 This measure is also related in a somewhat indirect and complicated fashion to the sensitivity coefficients for electromagnetic and electrostatic induction defined in [2], if the cable pair is considered as a simultaneous source of a transverse signal correlated with the induced longitudinal voltages. +- 3 The test object itself provides the source of signal. Hence a separate generator is not required. +- 4 The definition relates particularly to generators of transverse signals (e.g.: transmission oscillators) but can be readily extended to cover the case of a longitudinal signal generator (e.g.: a low-frequency signalling system using the earthed-phantom). In this case the ratio could be inverted so that the decibel expression remains positive. +- 5 The other quantities (return loss, longitudinal conversion loss, longitudinal impedance loss and the uncorrelated transverse and longitudinal output voltages) must be measured selectively in order that their values in working conditions be obtained. + +FIGURE 10/G.117 + +## 4.4 Signal receiving devices + +In addition to the six one-port measures already defined, additional measures are required for signal receiving devices to control their sensitivity to unwanted signals. Two cases are important. Firstly, there are receiving devices in which the response is a linear, continuous function of the wanted signal level, e.g. the indication of a level-measuring set. In this case unwanted signals give rise to *inaccuracy*. + +In the other kind of receiver such as data modems, group-delay distortion measuring sets, signalling receivers, unwanted signals cause errors or *misoperation*. Two additional measures are defined. + +### 4.4.1 Input longitudinal interference ratio (loss) (see Figure 11) + +![Circuit diagram for measuring input longitudinal interference ratio. A source impedance Z is connected in parallel with a short-circuited transmission line. A voltage source E_L is connected in series with a resistor Z/4 between the common line and ground. The receiving device is represented by a voltmeter V_l connected between the line and ground.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +The diagram shows a circuit for measuring the input longitudinal interference ratio. On the left, a source impedance $Z$ is connected in parallel with a short-circuited transmission line. A voltage source $E_L$ is connected in series with a resistor $Z/4$ between the common line and ground. The receiving device is represented by a voltmeter $V_l$ connected between the line and ground. The diagram is labeled T1208310-96/d11. + +Circuit diagram for measuring input longitudinal interference ratio. A source impedance Z is connected in parallel with a short-circuited transmission line. A voltage source E\_L is connected in series with a resistor Z/4 between the common line and ground. The receiving device is represented by a voltmeter V\_l connected between the line and ground. + +$$\text{Input longitudinal interference ratio} = s = \frac{V_l}{E_L}$$ + +and + +$$\text{Input longitudinal interference loss} = 20 \log_{10} \left| \frac{1}{s} \right| = 20 \log_{10} \left| \frac{E_L}{V_l} \right| \text{ dB}$$ + +in which $V_l$ is the voltage indicated by the measuring set being tested. + +##### NOTES + +- 1 This is a generalized version of the quantities referred to as the receiver signal balance ratio (Recommendation O.41 [4]). +- 2 The measuring instrument itself provides one of the voltages required by the definition. +- 3 This measure is related to the well-known *common-mode rejection ratio* but not in any simple fashion. In particular it is not 6 dB different. This is because when the longitudinal rejection ratio is measured, the input transverse terminals are short-circuited and there is no transverse signal to generate any additional longitudinal signal via the unbalance of the input impedance. +- 4 The concept could be extended to cover receivers which respond linearly to longitudinal signals, and here it is transverse signals that interfere. The designation would then be input *transverse* interference ratio (loss) with a correspondingly different circuit arrangement. + +FIGURE 11/G.117 + +#### 4.4.2 Longitudinal interference threshold voltage (level) (see Figure 12) + +![Circuit diagram for measuring longitudinal interference threshold voltage. A 'Test object with a threshold of misoperation or degradation of performance, e.g.: a signalling termination or a data modem' is shown. Its input terminals are connected to a parallel combination of a resistor Z and an inductor. The inductor's output is connected to a voltage source E_L through a resistor Z/4. The other input terminal of the test object is connected to ground. The diagram is labeled T1208320-96/d12.](5cab96b2d23174c25919840ecd50aa48_img.jpg) + +Circuit diagram for measuring longitudinal interference threshold voltage. A 'Test object with a threshold of misoperation or degradation of performance, e.g.: a signalling termination or a data modem' is shown. Its input terminals are connected to a parallel combination of a resistor Z and an inductor. The inductor's output is connected to a voltage source E\_L through a resistor Z/4. The other input terminal of the test object is connected to ground. The diagram is labeled T1208320-96/d12. + +Longitudinal interference threshold voltage = $E_L$ + +and + +$$\text{Longitudinal interference threshold level} = 20 \log_{10} \left| \frac{E_L}{1 \text{ volt}} \right| \text{ dBV}$$ + +in which $E_L$ is the voltage at which misoperation of the test device just occurs + +##### NOTES + +- 1 Other reference voltages than 1 volt may be used, for example, 0.775 V for 1 mW into 600 $\Omega$ (with the designation dB [3]). +- 2 “Misoperation” or the amount of degradation of performance would have to be defined. For a data modem it might have to be in terms of error ratio. +- 3 The threshold voltage may be specified as an rms value, or as an impulsive voltage as measured by an impulsive counter, or in terms of its waveshape (e.g.: square, triangular). +- 4 The concept could be extended to cover unwanted transverse signals affecting the operation of longitudinal receivers, with appropriate changes to the testing circuit and designation. + +FIGURE 12/G.117 + +# 5 Other measurement definitions + +## 5.1 Common-mode rejection ratio + +This is another quantity that is appropriate to signal receivers and is measured in accordance with the principle shown in Figure 13, the input terminals being short-circuited and then energized together. + +It is clear that this measure is similar to the input longitudinal interference ratio but since there is no transverse signal (by reason of the short circuit) no longitudinal/transverse conversion mechanism within the test-object is excited. In general, there is no simple relationship between the two measures, as can be seen from the generalized measuring instrument illustrated in Figure 14, in which the input impedance is unbalanced and the gain ratios of the two halves of the differential amplifier are also slightly different. Provided the value for $\epsilon$ is as in Figure 14 and $\Delta \ll 1$ , the various balance parameters are as indicated. This assumes the common mode rejection ratio is not twice the input longitudinal interference ratio, i.e. there is not a 6-dB difference between their decibel values. + +![Circuit diagram for Figure 13/G.117 showing a measuring set with a voltmeter V1, a ground connection, and an external voltage source EL.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +The diagram shows a measuring set represented by a rectangle containing a voltmeter labeled $V_1$ . The voltmeter has two input terminals. The lower input terminal is connected to a common ground point. The upper input terminal is connected to one side of an external voltage source $E_L$ . The other side of $E_L$ is also connected to the common ground point. A label 'T1208330-96/d13' is present near the ground symbol. + +Circuit diagram for Figure 13/G.117 showing a measuring set with a voltmeter V1, a ground connection, and an external voltage source EL. + +$$\text{Common-mode rejection ratio} = \left| \frac{E_L}{V_1} \right|$$ + +and + +$$\text{Common-mode rejection} = 20 \log_{10} \left| \frac{E_L}{V_1} \right| \text{ dB}$$ + +NOTE – $V_1$ is the voltage indicated by the measuring set being tested. + +FIGURE 13/G.117 + +![Circuit diagram for Figure 14/G.117 showing a measuring set with two amplifiers, resistors (1+Δ)Z and (1-Δ)Z, and an internal voltage source.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +The diagram shows a measuring set represented by a rectangle. Inside, there are two operational amplifiers. The top amplifier has a gain of $1 + \epsilon$ and its non-inverting input (+) is connected to a node between two resistors, $(1 + \Delta)Z$ and $(1 - \Delta)Z$ . The bottom amplifier has a gain of $1 - \epsilon$ and its non-inverting input (-) is connected to the same node. The inverting inputs of both amplifiers are connected together and to a common ground point. An internal voltage source is connected between the outputs of the two amplifiers. A label 'T1208340-96/d14' is present at the bottom right of the rectangle. + +Circuit diagram for Figure 14/G.117 showing a measuring set with two amplifiers, resistors (1+Δ)Z and (1-Δ)Z, and an internal voltage source. + +$$\begin{aligned} \text{Common mode rejection ratio} &= 2\epsilon \\ \text{Input longitudinal interference ratio} &= \epsilon + \frac{\Delta}{2} \quad (\epsilon, \Delta \ll 1) \\ \text{Longitudinal impedance ratio} &= 0.5 \quad (\Delta \ll 1) \\ \text{Longitudinal conversion ratio} &= \frac{\Delta}{2} \quad (\Delta \ll 1) \end{aligned}$$ + +FIGURE 14/G.117 + +A measuring set in which there is both a passive unbalance and an internal active unbalance + +# Annex A + +## Aspects of conversion from longitudinal to transversal signals at analogue ports in some practical cases + +(This annex forms an integral part of this Recommendation) + +## A.1 Introduction + +Cables for telecommunication purposes sometimes have to pass areas that have strong, disturbing electromagnetic fields which may cause significant longitudinal signals along the cables. For voiceband telephone signals, the established technique is to use well-balanced cables and equipment so that the conversion from longitudinal to transversal signals is sufficiently suppressed. In general, the cables have a much higher degree of balance than what is obtainable for terminal equipment. The governing factor is then the properties of the terminal equipment, i.e. the balance to Earth of that port which is connected to the cable. + +The balancing properties of an equipment port can be expressed in many ways. The most commonly used parameter appears to be the “Longitudinal Conversion Loss”, LCL. The general definition of LCL is given in clause 2 which in principle applies to all cases. However, in *equipment specifications*, LCL most often is understood to be a value which is obtained in a specific measuring setup according to Figure 4, where the transverse terminating impedance $Z$ is made 600 ohms resistive and the longitudinal source impedance $Z/4$ thus is 150 ohms resistive. + +The advantage of this latter definition is that LCL is obtained in a well-defined manner and that this LCL value gives a general indication of how well the port is balanced to Earth. However, the configuration in Figure 4 does not correspond too well with a realistic representation of actual, practical cases: + +- 1) The transverse terminating impedance nowadays is not always 600 ohms resistive but can be a complex, nominal impedance as given for instance in Recommendation Q.552. +- 2) The longitudinal source impedance is resistive only in exceptional cases but rather like a high capacitance. + +Thus, when a more accurate analysis of the actual longitudinal-to-transversal conversion is needed, either a special test setup, simulating actual conditions, has to be used and/or a more detailed circuit analysis has to be performed. In what follows, such an analysis will be made in order to illustrate the difference between a measured LCL and the actual conversion LCL. + +To distinguish the cases, the Longitudinal Conversion Loss measured in the 600/150 ohms test bridge will be designated $LCL_m$ , and the Longitudinal Conversion Loss in the actual circuit $LCL_c$ . + +## A.2 Calculation of the longitudinal conversion loss + +The unbalance properties of an equipment port or a network port can be described in many ways by equivalent circuits. The one shown in Figure A.1, employing an ideal choke with a tap, will be used here because it leads to simple expressions. (The factor $k$ is a measure of the degree of unbalance.) + +This equivalent circuit type can be used both for the circuit (cable or the test bridge), that introduces the longitudinal voltage, and for the terminating equipment, as Figure A.2 depicts. (Note that the cable and the test bridge are supposed to be perfectly balanced.) + +![Equivalent circuit diagram for unbalance-to-earth at a port. On the left, a rectangular box represents a port with two input terminals and a ground connection. An equivalence symbol (three horizontal lines) connects it to a circuit on the right. The right-hand circuit has a transverse impedance Z_t in parallel with a center-tapped inductor. The inductor's upper half is labeled (1 + 2k) and the lower half (1 - 2k). The center tap is connected to ground through a longitudinal impedance Z_l. The diagram is labeled T1207090-95/d15.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +Equivalent circuit diagram for unbalance-to-earth at a port. On the left, a rectangular box represents a port with two input terminals and a ground connection. An equivalence symbol (three horizontal lines) connects it to a circuit on the right. The right-hand circuit has a transverse impedance Z\_t in parallel with a center-tapped inductor. The inductor's upper half is labeled (1 + 2k) and the lower half (1 - 2k). The center tap is connected to ground through a longitudinal impedance Z\_l. The diagram is labeled T1207090-95/d15. + +- $Z_t$ Transverse impedance +- $Z_l$ Longitudinal impedance +- $k$ Transverse Conversion Factor + +FIGURE A.1/G.117 +**Equivalent circuit for the unbalance-to-earth at a port** + +![Equivalent circuit for conversion of longitudinal voltage E_l to transversal voltage V_t. The circuit consists of two parallel sections. The left section represents the cable/test bridge with transverse impedance Z_tc and a center-tapped inductor (windings labeled 1 and 1). Its center tap connects to ground through longitudinal impedance Z_lc and voltage source E_l. The right section represents the equipment with transverse impedance Z_te and a center-tapped inductor (windings labeled (1 + 2k) and (1 - 2k)). Its center tap connects to ground through longitudinal impedance Z_le. The output voltage V_t is measured across the equipment's transverse terminals. The diagram is labeled T1207100-95/d16.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Equivalent circuit for conversion of longitudinal voltage E\_l to transversal voltage V\_t. The circuit consists of two parallel sections. The left section represents the cable/test bridge with transverse impedance Z\_tc and a center-tapped inductor (windings labeled 1 and 1). Its center tap connects to ground through longitudinal impedance Z\_lc and voltage source E\_l. The right section represents the equipment with transverse impedance Z\_te and a center-tapped inductor (windings labeled (1 + 2k) and (1 - 2k)). Its center tap connects to ground through longitudinal impedance Z\_le. The output voltage V\_t is measured across the equipment's transverse terminals. The diagram is labeled T1207100-95/d16. + +- $Z_{te}, Z_{le}$ transverse resp. longitudinal impedance of the equipment +- $Z_{tc}, Z_{lc}$ transverse resp. longitudinal impedance of the cable or the test bridge + +FIGURE A.2/G.117 +**Equivalent circuit for conversion of the longitudinal voltage $E_l$ to the transversal voltage $V_t$** + +Using the equivalent circuit, the following expression for the Longitudinal Conversion Loss $LCL_c$ in the general case is derived: + +$$LCL_c = 20 \cdot \lg \left| \frac{1}{k} \left\{ (Z_{lc} + Z_{le}) \cdot \left( \frac{1}{Z_{tc}} + \frac{1}{Z_{te}} \right) + k^2 \right\} \right| \text{ dB} \quad (\text{A-1})$$ + +Note that this equation is valid for all values of $k$ , i.e. even if the port would be totally unbalanced. However, in general, the terminating equipment is reasonably well-balanced, i.e. $k$ is small, so that equation A-1 can be simplified to: + +$$LCL_c = 20 \cdot \lg \left| \frac{1}{k} (Z_{lc} + Z_{le}) \cdot \left( \frac{1}{Z_{tc}} + \frac{1}{Z_{te}} \right) \right| \text{ dB} \quad (\text{A-2})$$ + +In the measuring setup for the longitudinal conversion loss we have: + +$$Z_{lc} = 150 \text{ ohms}; \quad Z_{tc} = 600 \text{ ohms}; \quad (\text{A-3})$$ + +so that: + +$$LCL_m = 20 \cdot \lg \left| \frac{1}{k} (150 + Z_{le}) \cdot \left( \frac{1}{600} + \frac{1}{Z_{te}} \right) \right| \text{ dB} \quad (\text{A-4})$$ + +## A.3 The difference between $LCL_c$ and $LCL_m$ in a practical case – two examples + +The disturbing circuit is assumed to be a subscriber cable, perfectly balanced, and the terminating equipment the input analogue port of a digital exchange. The terminal equipment has a slight unbalance to Earth. + +The equipment transversal impedance $Z_{te}$ is complex, and can be represented by a resistance of 275 ohms and a parallel combination of a resistance of 780 ohms and a capacitance of 150 nF. This impedance is a sufficiently close match to the input transversal impedance of the cable circuit so that $Z_{tc} = Z_{te}$ . + +The equipment longitudinal impedance $Z_{le}$ is assumed to be 300 ohms resistive. + +In the first example the cable is terminated by a telephone set with a very high longitudinal impedance to Earth. Then the circuit, i.e. the cable, input longitudinal impedance $Z_{lc}$ can be represented by a capacitance $C_s$ in series with a small resistance. Here $C_s = 500 \text{ nF}$ and $R_s = 75 \text{ ohms}$ are chosen values as being typical for a subscriber line. + +In the second example the subscriber line is terminated by an equipment, perfectly balanced, but with a very low longitudinal impedance to Earth. Then $Z_{lc}$ can be considered as a pure resistance, three times higher than in the first case, i.e. $Z_{lc} = 225 \text{ ohms}$ . + +The difference ( $LCL_c - LCL_m$ ) for the two cases is shown in Figures A.3 and A.4 respectively. + +The first example: high longitudinal impedance to Earth at the far end. + +The second example: low longitudinal impedance to Earth at the far end. + +## A.4 Additional Insight into Longitudinal Conversion Loss + +A more complete analysis of LCL differences between actual longitudinal conversion loss circuits and longitudinal conversion loss test sets has been done. Two conclusions are noteworthy: + +- 1) The real difference between the test set and the actual longitudinal conversion loss is rather independent of the terminal input impedance and therefore this analysis applies to virtually all reasonable exchange input impedances including 600 ohms and 900 ohms + 2.16 $\mu\text{F}$ . +- 2) The difference between the actual longitudinal conversion loss and the longitudinal conversion loss as measured by the test set is compensated for by the lower LCL limits at lower frequencies as noted in Recommendation Q.553. Recommendation Q.553 requires a minimum of 40 dB LCL from 300 Hz to 600 Hz and 46 dB of LCL from 600 Hz to 3400 Hz. + +![Graph showing the difference between actual longitudinal conversion loss LCL_c and LCL_m in dB versus frequency in kHz. The y-axis ranges from -5 to 20 dB, and the x-axis ranges from 0.2 to 4 kHz. The curve starts at approximately 8.5 dB at 0.2 kHz, decreases to a minimum of about -1 dB at 1.2 kHz, and then slightly increases to about 0.5 dB at 4 kHz. The label T1207110-95/d17 is present at the bottom right.](5ed9189841659dfb01f809b8e3b21f74_img.jpg) + +| Frequency (kHz) | Difference (dB) | +|-----------------|-----------------| +| 0.2 | 8.5 | +| 0.5 | 2.5 | +| 1.0 | -0.5 | +| 1.2 | -1.0 | +| 2.0 | -0.5 | +| 3.0 | 0.0 | +| 4.0 | 0.5 | + +Graph showing the difference between actual longitudinal conversion loss LCL\_c and LCL\_m in dB versus frequency in kHz. The y-axis ranges from -5 to 20 dB, and the x-axis ranges from 0.2 to 4 kHz. The curve starts at approximately 8.5 dB at 0.2 kHz, decreases to a minimum of about -1 dB at 1.2 kHz, and then slightly increases to about 0.5 dB at 4 kHz. The label T1207110-95/d17 is present at the bottom right. + +FIGURE A.3/G.117 +**Difference between actual longitudinal conversion loss $LCL_c$ and $LCL_m$ , measured in the standard test bridge** + +![Graph showing the difference between actual longitudinal conversion loss LCL_c and LCL_m in dB versus frequency in kHz. The y-axis ranges from -5 to 20 dB, and the x-axis ranges from 0.2 to 4 kHz. The curve starts at approximately -1.5 dB at 0.2 kHz, increases to about 0 dB at 1.0 kHz, and then continues to increase to about 3.5 dB at 4 kHz. The label T1207120-95/d18 is present at the bottom right.](2a77eb32ef4c4d8a5c1758a53a908336_img.jpg) + +| Frequency (kHz) | Difference (dB) | +|-----------------|-----------------| +| 0.2 | -1.5 | +| 0.5 | -1.0 | +| 1.0 | 0.0 | +| 2.0 | 1.5 | +| 3.0 | 2.5 | +| 4.0 | 3.5 | + +Graph showing the difference between actual longitudinal conversion loss LCL\_c and LCL\_m in dB versus frequency in kHz. The y-axis ranges from -5 to 20 dB, and the x-axis ranges from 0.2 to 4 kHz. The curve starts at approximately -1.5 dB at 0.2 kHz, increases to about 0 dB at 1.0 kHz, and then continues to increase to about 3.5 dB at 4 kHz. The label T1207120-95/d18 is present at the bottom right. + +FIGURE A.4/G.117 +**Difference between actual longitudinal conversion loss $LCL_c$ and $LCL_m$ , measured in the standard test bridge** + +# References + +- [1] CCITT Recommendation O.9 (1988), *Measuring arrangements to assess the degree of unbalance about earth.* +- [2] CCITT *Directives concerning the protection of telecommunication lines against harmful effects from electric power and electrified railways lines*, ITU, Geneva, 1990. +- [3] ITU-R Recommendation V.574 (1990), *Use of the decibel and the neper in telecommunications.* +- [4] ITU-T Recommendation O.41 (1994), *Psophometer for use on telephone-type circuits.* \ No newline at end of file diff --git a/marked/G/T-REC-G.122-199303-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/G/T-REC-G.122-199303-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d14516f4f397b11b115d4116cab4574867bdad0c --- /dev/null +++ b/marked/G/T-REC-G.122-199303-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b36aa124ffa6f71f79d1df9874b274340d360c90a83de85f693821b13ca75f82 +size 28313 diff --git a/marked/G/T-REC-G.122-199303-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/G/T-REC-G.122-199303-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f96b12e3e86ab8f46b64cd5ee54e77ceae6675a --- /dev/null +++ b/marked/G/T-REC-G.122-199303-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ab3bffb73092afe0a4e4b49e6ddf7a3b5366bc7e256854c2dd046f73dcb1f30 +size 50932 diff --git a/marked/G/T-REC-G.122-199303-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/G/T-REC-G.122-199303-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd32aed01711cb295786b27e87f7c583040ea5ee --- /dev/null +++ b/marked/G/T-REC-G.122-199303-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d696decda187d0a21b5eb1c2644e9cea7f5d78d98b3f4ba55b74cae73ebc0dfc +size 20727 diff --git a/marked/G/T-REC-G.122-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.122-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dadba845dc75c3c0dc13323643e4cc7aa77618ee --- /dev/null +++ b/marked/G/T-REC-G.122-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:763504eea0996cfc68294f64c0fd91fad77b4c6261ee8c46028cd112ec1f02a4 +size 8295 diff --git a/marked/G/T-REC-G.122-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/G/T-REC-G.122-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..042627360fa90fe193469aa459eecba8c04c3114 --- /dev/null +++ b/marked/G/T-REC-G.122-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:833e1b7a220333279470d396270f4e6e47f43ddba138112c8b6a444dea722719 +size 40797 diff --git a/marked/G/T-REC-G.122-199303-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/G/T-REC-G.122-199303-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7428d87b0ac74126c1a9813d61fd70287012db0 --- /dev/null +++ b/marked/G/T-REC-G.122-199303-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d7675a74e22d1f8331f999a6a2fa0c3e015797ee68e994bf1dd8756277cdf2d +size 34815 diff --git a/marked/G/T-REC-G.122-199303-I_PDF-E/ca5566458a134032dd860e88fdaa0d2b_img.jpg b/marked/G/T-REC-G.122-199303-I_PDF-E/ca5566458a134032dd860e88fdaa0d2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74fcf265ec8e756b73a75c4b709dcde309b11631 --- /dev/null +++ b/marked/G/T-REC-G.122-199303-I_PDF-E/ca5566458a134032dd860e88fdaa0d2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85421f98369775aed680e3973271e6f404b689ad0dd142313cdc1387c1ac9384 +size 52725 diff --git a/marked/G/T-REC-G.122-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.122-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23bf1036ce62aaaf10ce110e2d82eb08a600cc33 --- /dev/null +++ b/marked/G/T-REC-G.122-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03488bdb9d4b627708a129827efbb25a6303b300cdc326ea91184c80b5090722 +size 17749 diff --git a/marked/G/T-REC-G.122-199303-I_PDF-E/raw.md b/marked/G/T-REC-G.122-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8ef3ff7045af567c22d57001e9bcdd90e69dd92b --- /dev/null +++ b/marked/G/T-REC-G.122-199303-I_PDF-E/raw.md @@ -0,0 +1,433 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**G.122** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/93) + +**TRANSMISSION SYSTEMS AND MEDIA +GENERAL CHARACTERISTICS OF NATIONAL +SYSTEMS FORMING PART OF +INTERNATIONAL CONNECTIONS** + +--- + +**INFLUENCE OF NATIONAL SYSTEMS +ON STABILITY AND TALKER ECHO +IN INTERNATIONAL CONNECTIONS** + +**ITU-T Recommendation G.122** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +ITU-T Recommendation G.122 was revised by the ITU-T Study Group XII (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). + +## --- NOTES + +1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. + +In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. + +2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +*Page* + +| | | | +|-----|------------------------------------------------------------------------------------------------------|----| +| 1 | Introduction ..... | 1 | +| 2 | Loss ( a-b ) to avoid instability during set-up, clear-down and changes in a connection ..... | 2 | +| 3 | Unweighted loss ( a-b ) on established connections ..... | 3 | +| 4 | Echo loss ( a-b ) on established connections..... | 3 | +| | Annex A – Measurement of stability loss ( a-b ) and echo loss ( a-b ) ..... | 4 | +| | Annex B – Explanation of terms associated with the path a-t-b ..... | 6 | +| B.1 | Return loss ..... | 6 | +| B.2 | Balance return loss..... | 6 | +| B.3 | Transmission loss of the path a-t-b ..... | 7 | +| B.4 | Stability and echo losses..... | 9 | +| B.5 | Overall loudness rating of the echo path (talker echo loudness rating, TELR) ..... | 10 | +| B.6 | Summary of useful terms ..... | 11 | +| | References ..... | 11 | + + + +# INFLUENCE OF NATIONAL SYSTEMS ON STABILITY AND TALKER ECHO IN INTERNATIONAL CONNECTIONS + +(Geneva, 1964; amended at Mar del Plata, 1968; Geneva, 1972, 1976 and 1980; Malaga-Torremolinos, 1984; Melbourne, 1988 and Helsinki, 1993) + +## 1 Introduction + +The information provided in this Recommendation applies to all national systems. + +Representations of a national system which extend up to the virtual analogue switching points are shown in Figure 1. + +![Figure 1/G.122: National system representation and virtual analogue switching point definition. The diagram shows two cases: 'National system partly 2-wire' and 'National system wholly 4-wire'. In the partly 2-wire case, a telephone handset is connected to a network of lines with 'X' marks representing switches. A point 't' marks the transition to a 4-wire section. The 4-wire section has two parallel lines with 'X' marks, leading to virtual switching points 'a' and 'b'. Point 'b' is at the top line, and point 'a' is at the bottom line. Above point 'b', an arrow points right labeled '3.5 dBr'. To the right of point 'a', an arrow points left labeled '-4 dBr (for analogue international circuit)' and '-3.5 dBr (for digital international circuit)'. The section between 'a' and 'b' is labeled 'National system' and the section to the right is 'International circuit'. In the wholly 4-wire case, a telephone handset is connected to a 4-wire network. The 4-wire section has two parallel lines with 'X' marks, leading to virtual switching points 'a' and 'b'. Point 'b' is at the top line, and point 'a' is at the bottom line. The section between 'a' and 'b' is labeled 'National system' and the section to the right is 'International circuit'. A dashed line with an arrow points from the handset to the 4-wire network. The text 'T1205550-93/d01' is at the bottom right.](ca5566458a134032dd860e88fdaa0d2b_img.jpg) + +Figure 1/G.122: National system representation and virtual analogue switching point definition. The diagram shows two cases: 'National system partly 2-wire' and 'National system wholly 4-wire'. In the partly 2-wire case, a telephone handset is connected to a network of lines with 'X' marks representing switches. A point 't' marks the transition to a 4-wire section. The 4-wire section has two parallel lines with 'X' marks, leading to virtual switching points 'a' and 'b'. Point 'b' is at the top line, and point 'a' is at the bottom line. Above point 'b', an arrow points right labeled '3.5 dBr'. To the right of point 'a', an arrow points left labeled '-4 dBr (for analogue international circuit)' and '-3.5 dBr (for digital international circuit)'. The section between 'a' and 'b' is labeled 'National system' and the section to the right is 'International circuit'. In the wholly 4-wire case, a telephone handset is connected to a 4-wire network. The 4-wire section has two parallel lines with 'X' marks, leading to virtual switching points 'a' and 'b'. Point 'b' is at the top line, and point 'a' is at the bottom line. The section between 'a' and 'b' is labeled 'National system' and the section to the right is 'International circuit'. A dashed line with an arrow points from the handset to the 4-wire network. The text 'T1205550-93/d01' is at the bottom right. + +NOTE – *a*, *b* are the virtual analogue switching points of the international circuit. + +FIGURE 1/G.122 + +### National system representation and virtual analogue switching point definition + +The transmission loss introduced between *a* and *b* by the national system, referred to as the loss (*a-b*), is important from three points of view: + +- it contributes to the margin that the international connection has against oscillation during the setting-up and clearing-down of the connection. A minimum loss over the band 0-4 kHz is the characteristic value; +- it contributes to the margin of stability during a communication. Again, a minimum loss in the band 0-4 kHz is the characteristic value, but in this case the subscribers' apparatus (telephone, modem, etc.) are assumed to be connected and in the operating condition; +- it contributes to the control of echoes and, in respect of the subjective effect of talker echo, a weighted sum of the loss (*a-b*) over the band 300-3400 Hz is the characteristic value. + +In addition, echoes circulating in any of the 4-wire loops in the national system or in the international 4-wire chain, give rise to listener echo, which can affect voice-band analogue data transmission. + +The requirements stated in this Recommendation represent network performance objectives. + +## 2 Loss (*a-b*) to avoid instability during set-up, clear-down and changes in a connection + +**2.1** Instability should be avoided during all normal conditions of set-up, clear-down and other changes in the composition (e.g. call-transfer) of a complete connection. To ensure adequate stability of international connections, the distribution (taken over many actual calls) of the loss (*a-b*) during the worst situation should be such that the risk of a loss (*a-b*) of 0 dB or less does not exceed 6 in 1000 calls when using the calculation method applied in 2.2. This requirement should be observed at any frequency in the band 0 to 4 kHz. + +### NOTES + +1 The signalling and switching systems have an influence on the loss (*a-b*) under set-up and clear-down conditions. For example, in some systems 4-wire registers control the set-up and do not establish the 4-wire path until the answer signal is successfully received. In others, circuits are released immediately if busy conditions are encountered. In these circumstances the risk of oscillation does not arise. + +2 Recommendation Q.32 gives information on methods of securing an adequate loss (*a-b*) of an incoming national system before the called-subscriber answers (i.e. while ringing tone is transmitted) or if busy or number unobtainable conditions are encountered. + +3 If there are no such arrangements as described in Notes 1 or 2 above then, in general, it would be safe to assume that there is no balance return loss provided by the called local telephone circuit (if 2-wire). In this case the necessary loss (*a-b*) must be provided by the transmission losses in the national system. + +4 The stability of international telephone connections at frequencies outside the band of effectively transmitted frequencies (i.e. below 300 Hz and above 3400 Hz) is governed by the following transmission losses at the frequencies of interest: + +- the balance return loss at the terminating units; +- the transmission losses of the terminating units; +- the transmission losses of the 4-wire circuits. + +5 Conditions which only last for a few tens of milliseconds can be left out of consideration because in such a short time oscillations cannot build up to a significant level. + +**2.2** The limit recommended in 2.1 may be met, for instance, by imposing the following simultaneous conditions on the national network: + +- 1) The sum of the nominal transmission losses in both directions of transmission *a-b* and *t-b* measured between the 2-wire input of the terminating set *t*, and one or other of the virtual switching points on the international circuit, *a* or *b* should not be less than $(4 + n)$ dB, where *n* is the number of analogue or mixed analogue-digital 4-wire circuits in the national chain. +- 2) The stability balance return loss at the terminating set *t*, should have a value not less than 2 dB for the terminal conditions encountered during normal operation. +- 3) The standard deviation of variations of transmission loss of a circuit should not exceed 1 dB (see 3/G.151). + +In a calculation to verify if these values are acceptable, it may be assumed that (see [1]): + +- there is no significant difference between nominal and mean value of the transmission losses of circuits; +- variations of losses for both directions of transmission of the same circuit are fully correlated; +- distributions are Gaussian. + +For the loss (*a-b*), it then results: + +Mean value: $2 + 4 + n = 6 + n$ dB + +Standard deviation: $\sqrt{4n}$ dB + +With $n = 4$ the mean value becomes 10 dB and the standard deviation 4 dB, resulting in a probability for values lower than 0 dB of $6 \cdot 10^{-3}$ . + +NOTE – There is no need for the two quantities $a-t$ and $t-b$ to be equal, so that differential gain can be used in the national network. This practice may be needed to meet the requirements of 2/G.121, but it implies that the transmission loss in terminal service of the 4-wire chain plus the terminating sets may be different according to the direction of transmission. The choice of the nominal value of the transmission loss $t-b$ should in all cases be made with an eye to 3/G.121 dealing with the minimum sending reference equivalent to be imposed in each national chain, to avoid any risk of overloading in the international network. + +## 3 Unweighted loss ( $a-b$ ) on established connections + +3.1 The objective is that the risk of the loss ( $a-b$ ) reaching low values at any frequency in the range 0-4 kHz should be as small as practicable. This requires restrictions on the distribution of values of stability loss ( $a-b$ ) for the population of actual international calls established over the national system. Such a distribution can be characterized by a mean value and a standard deviation. + +The objective will be obtained by a national system sharing a mean value of at least $(10 + n)$ dB together with a standard deviation not larger than $\sqrt{6.25 + 4n}$ dB in the band 0-4 kHz; where $n$ is the number of analogue or mixed analogue-digital 4-wire circuits in the national chain. Other distributions are acceptable as well, as long as they yield equivalent or better results calculated according to the convention of [1]. + +### NOTES + +1 See Note in 2.2. + +2 In the more conventional case of $a$ of Figure 1, the loss ( $a-b$ ) is calculated as the sum of circuit losses, terminating loss and stability balance return loss. In fact the loss ( $a-b$ ) at a given frequency is the sum of the circuit losses at that frequency plus the balance return loss at the same frequency. For planning purposes, it may be assumed that the stability loss is equal to or greater than the sum of the stability balance return loss plus the sum of the circuit losses at the reference frequency. This follows from the observation that the least circuit loss typically occurs in the vicinity of the reference frequency. + +3 Wholly digital circuits may be assumed to have a transmission loss with mean value and standard deviation equal to zero. Voice coders in circuits or in exchanges are expected to offer smaller variations in transmission loss than carrier circuits. For the variations in transmission loss of a coder-decoder combination, standard deviations in the order of 0.4 dB have been reported. + +4 The subscriber's apparatus (telephone, modem, etc.) in the local telephone circuit are assumed to be "off hook" or equivalent, and thus providing balance return loss. + +5 In practice, the distribution of stability balance return loss is distinctly skew, most of the standard deviations being provided by values above the mean. It could be unduly restrictive to assume a normal distribution. + +6 The CCITT manual cited in [2] describes some of the methods proposed, and in some cases successfully applied, by Administrations to improve balance return losses. + +3.2 The distribution of stability loss ( $a-b$ ) recommended in 3.1 above could, for example, be attained if, in addition to meeting the conditions of 2.2, the mean value of the stability balance return loss at the terminating set is not less than 6 dB and the standard deviation not larger than 2.5 dB. + +## 4 Echo loss ( $a-b$ ) on established connections + +4.1 In order to minimize the effects of echo on international connections it is recommended that the distribution of echo loss ( $a-b$ ) for the population of actual international calls established over the national system should have a mean value of not less than $15 + n$ dB with a standard deviation not exceeding $\sqrt{9 + 4n}$ , where $n$ is the number of analogue or mixed analogue-digital 4-wire circuits in the national chain. + +Other distributions are acceptable as well, as long as they yield equivalent or better results calculated according to the convention of Supplement No. 2 Recommendation G.131. + +### NOTES + +1 Echo suppressors and cancellers according to Recommendations G.164 and G.165, typically require 6 dB of signal loss ( $a-b$ ) for the *actual* signal converging the canceller or being controlled by the suppressor. This signal loss ( $a-b$ ) is the ratio of incident to reflected signal power on the return path. The value of signal loss ( $a-b$ ) will depend both upon the loss ( $a-b$ ) frequency response and the signal spectrum. Therefore, it is desirable from a performance point of view that the stability loss ( $a-b$ ) during an established connection should be at least 6 dB, since this will ensure proper operation for any signal (frequency spectrum) in the band 0-4 kHz. + +However it may not be practical to always achieve this level of performance, especially at the higher frequencies characteristic of voice-band data signals. For speech, typically the speech signal loss (*a-b*) will be at least 6 dB if the echo loss is 6 dB. However, for voice-band data signals a higher echo loss is required to ensure a data signal loss (*a-b*) of 6 dB. For some data signals an echo loss of at least 10 dB is required. It should be noted that some modems operating half-duplex on satellite circuits equipped with echo cancellers may require proper operation of the canceller to prevent long delay echoes that exceed the receiver squelch period from causing data transmission problems. + +2 See Note 2 in 3.1. In a similar manner for planning purposes it can be assumed that the echo loss is equal to or greater than the sum of the echo balance return loss and the circuit losses at the reference frequency. + +3 Recommendation G.131 provides guidance on the application of echo control devices. + +**4.2** The echo loss (*a-b*) is derived from the integral of the power transfer characteristic $A(f)$ weighted by a negative slope of 3 dB/octave starting at 300 Hz, extending to 3400 Hz, as follows: + +$$\text{Echo loss } L_e = 3.85 - 10 \log_{10} \left[ \int_{300}^{3400} \frac{A(f)}{f} df \right] \text{ dB}$$ + +where + +$$A(f) = 10^{-\frac{L_{ab}(f)}{10}} \text{ with } L_{ab} = \text{loss (a-b)}$$ + +### NOTES + +1 The above method replaces an earlier method in which the echo loss of the path *a-t-b* was provisionally defined as the expression in transmission units of the unweighted mean of the power ratios in the band 500-2500 Hz. The new method has been found to give better agreement with subjective opinion for individual connections. However, study has shown that echo path loss distributions for large samples of actual connections calculated by the two methods have almost identical means and standard deviations. Therefore, data gathered by the older method is still considered useful in planning studies. + +2 Evidence was presented which showed that a white noise signal is not necessarily optimum to measure the residual echo level after cancellation, because an echo canceller does not converge to quite the same condition as it does with a real speech signal. It may be better to use the conventional telephone signal (see Recommendation G.227) or better still, an artificial speech signal. A good compromise is the weighted noise signal based on the principle recommended above. + +3 Improved balance return losses at *t* can be obtained when the local exchange uses 4-wire switching and the local line is permanently associated with the 2-wire/4-wire conversion unit and its balance network (see Recommendation Q.552 for examples). When there is 2-wire switching, a compromise balance network must be used. + +4 There is evidence that a 4-wire handset telephone in normal use can contribute significant acoustic echo to the communication. Hence in some circumstances (low transmission loss, long delay times) echo control devices may be needed. + +**4.3** An example of how the recommendation quoted in 4.1 above can be achieved would be for the mean value of the sum of the transmission losses *a-t* and *t-b* not to be less than $(4 + n)$ dB with a standard deviation from the mean not exceeding $2\sqrt{n}$ dB, accompanied by an echo balance return loss at the terminating set *t*, of not less than 11 dB with a standard deviation not exceeding 3 dB. + +## Annex A + +## Measurement of stability loss (*a-b*) and echo loss (*a-b*) + +(This annex forms an integral part of this Recommendation) + +The stability loss (*a-b*) and the echo loss (*a-b*) as defined in 3.1 and 4.1 respectively, may be measured by apparatus at the international centre in accordance with the principle of Figure A.1. + +In respect of the echo measurement, the combined response of the send and receive filters must be such that the definition given in 4.2 of the text is effectively implemented, e.g. such that the difference between a measured echo loss and one calculated from the loss/frequency characteristic does not exceed 0.25 dB. + +The allocation of the total response between send and receive is not critical and any reasonable division may be used provided that + +- excessive interchannel interference is avoided in national transmission systems due to an unrestricted spectrum of the transmitted signal; +- unwanted signals that may give rise to errors, e.g. hum, circuit noise, carrier leak signals, are prevented from entering the receiver. + +Appropriate arrangements (not shown) are needed for automatic or manual access to the 4-wire switches at the international centre and also to ensure that due account is taken of the transmission levels at the actual switching points. + +As far as the stability measurement is concerned, if a sweep oscillator is used, attention must be paid to the risks of engendering false operation of national signalling systems. + +For both measurements anomalous results may be obtained if echo suppressors are encountered in the national extension. + +To measure the echo loss (*a-b*), the output of the send filter is first connected to the input of the receive filter and the appropriate level set and noted. The apparatus is then connected as in Figure A.1 and the new reading on the meter noted. The loss so indicated is the echo loss (*a-b*). + +![Diagram illustrating the principle of measuring the transmission loss of the path a-t-b. The diagram shows a 'National' section connected to an 'International' section via a 4-wire switch. On the 'National' side, there are two measurement paths. The top path, labeled 'Echo', consists of a 'Uniform spectrum signal generator' connected to a 'Weighting network' (1/f), then to a 'Send' filter, which connects to the switch. The return path goes from the switch through a 'Receive' filter to an 'R.m.s. or quasi-r.m.s. detector', which is connected to a meter. The bottom path, also labeled 'Echo', consists of a 'Sinusoidal oscillator' connected to the switch, then through a 'Receive' filter to another meter. A bracket on the left groups both meters under the label 'Echo'. A small text 'T1205560-93/d02' is visible in the bottom right corner of the diagram area.](0b87abe67b21a93777287649c33e755d_img.jpg) + +Diagram illustrating the principle of measuring the transmission loss of the path a-t-b. The diagram shows a 'National' section connected to an 'International' section via a 4-wire switch. On the 'National' side, there are two measurement paths. The top path, labeled 'Echo', consists of a 'Uniform spectrum signal generator' connected to a 'Weighting network' (1/f), then to a 'Send' filter, which connects to the switch. The return path goes from the switch through a 'Receive' filter to an 'R.m.s. or quasi-r.m.s. detector', which is connected to a meter. The bottom path, also labeled 'Echo', consists of a 'Sinusoidal oscillator' connected to the switch, then through a 'Receive' filter to another meter. A bracket on the left groups both meters under the label 'Echo'. A small text 'T1205560-93/d02' is visible in the bottom right corner of the diagram area. + +FIGURE A.1/G.122 + +Principle of measuring the transmission loss of the path *a-t-b* from the points of view of stability and of echo + +## Annex BExplanation of terms associated with the path *a-t-b* + +(Contribution of British Telecom and Australia) + +(This annex forms an integral part of this Recommendation) + +## B.1 Return loss + +This is a quantity associated with the degree of match between two impedances and is given by the expression: + +$$\text{Return loss of } Z_1 \text{ versus } Z_2 = 20 \log_{10} \left| \frac{Z_1 + Z_2}{Z_1 - Z_2} \right| \text{ dB}$$ + +The use of the expression “return loss” should be confined to 2-wire paths supporting signals in the two directions simultaneously. + +### B.2 Balance return loss + +A clear definition is given in the preamble of this Recommendation. Figure B.1 illustrates the definition. + +![Diagram illustrating the definition of balance return loss. A 4-wire network is shown with a diamond-shaped symbol representing the network. The input impedance on the left is labeled Z_H, and the output impedance on the right is labeled Z_TW. A terminating impedance Z_B is connected to the right side. A dashed vertical line separates the input and output. Text 'In general Z_H ≠ Z_B' is present. The diagram is labeled T1205570-93/d03.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +In general $Z_H \neq Z_B$ + +$Z_H$ + +$Z_B$ + +$Z_{TW}$ + +T1205570-93/d03 + +$$\text{Balance return loss} = 20 \log_{10} \left| \frac{Z_B + Z_{TW}}{Z_B - Z_{TW}} \right| \text{ dB}$$ + +Diagram illustrating the definition of balance return loss. A 4-wire network is shown with a diamond-shaped symbol representing the network. The input impedance on the left is labeled Z\_H, and the output impedance on the right is labeled Z\_TW. A terminating impedance Z\_B is connected to the right side. A dashed vertical line separates the input and output. Text 'In general Z\_H ≠ Z\_B' is present. The diagram is labeled T1205570-93/d03. + +FIGURE B.1/G.122 + +The 2-wire portion must be in the condition appropriate to the study, e.g. if speech echo is being studied the telephone set must be in the speaking condition. + +In the particular case (which occurs very often) in which the impedances presented by each of the paths in the 4-wire portion are also $Z_B$ (e.g. 600 ohms), then the terminating set presents an impedance of the 2-wire point which is substantially equal to $Z_B$ . Figure B.2 illustrates this case. + +The term “balance return loss” (*not* return loss) should always be used for the contribution to the loss of the path *a-t-b* attributable to the degree of match between $Z_B$ and $Z_{TW}$ . + +![Diagram of a bridge-tap configuration. A horizontal line represents the main path. A bridge-tap branches off this line, containing a diamond-shaped bridge component and a load impedance Z_B. The bridge-tap is terminated at its far end with another impedance Z_B. The input impedance of the bridge-tap is labeled Z_TW. The main path has an impedance Z_H on the left and Z_B on the right. A note indicates Z_H = Z_B for this case. The diagram is labeled T1205580-93/d04.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Diagram of a bridge-tap configuration. A horizontal line represents the main path. A bridge-tap branches off this line, containing a diamond-shaped bridge component and a load impedance Z\_B. The bridge-tap is terminated at its far end with another impedance Z\_B. The input impedance of the bridge-tap is labeled Z\_TW. The main path has an impedance Z\_H on the left and Z\_B on the right. A note indicates Z\_H = Z\_B for this case. The diagram is labeled T1205580-93/d04. + +FIGURE B.2/G.122 + +## B.3 Transmission loss of the path a-t-b + +There is room for confusion here because the concept can be applied to arrangements in which there is no physical point “*r*” at all, e.g. as in some laboratory simulations of long connections in which echo is introduced by a controlled unidirectional path bridging the two 4-wire paths. The point “*r*” is necessary in the Recommendation because practical public switched telephone networks are being dealt with. + +Thus in general two cases arise: + +*Case 1:* There does exist a point “*r*” (see Figure B.3). + +![Diagram illustrating the transmission loss of the path a-t-b. A bridge-tap with impedance Z_B branches from point 't' on a main line. The bridge-tap is terminated at point 'b' with an impedance Z_B. The input impedance of the bridge-tap is Z_TW. The loss from 't' to 'b' is labeled 'Loss'. At point 'a', a signal level of -4 dBr_i is indicated. The loss from 't' to 'a' is also labeled 'Loss'. The diagram is divided into a 'National system' (left of 'a') and an 'International chain' (right of 'a'). The diagram is labeled T1205590-93/d05.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +Diagram illustrating the transmission loss of the path a-t-b. A bridge-tap with impedance Z\_B branches from point 't' on a main line. The bridge-tap is terminated at point 'b' with an impedance Z\_B. The input impedance of the bridge-tap is Z\_TW. The loss from 't' to 'b' is labeled 'Loss'. At point 'a', a signal level of -4 dBr\_i is indicated. The loss from 't' to 'a' is also labeled 'Loss'. The diagram is divided into a 'National system' (left of 'a') and an 'International chain' (right of 'a'). The diagram is labeled T1205590-93/d05. + +FIGURE B.3/G.122 + +The transmission loss of the path $a-t-b$ may be calculated from + +$$\text{Loss } (a-t) + 20 \log_{10} \left| \frac{Z_B + Z_{TW}}{Z_B - Z_{TW}} \right| + \text{loss } (t-b)$$ + +The diagram is drawn in terms of the virtual switching points of the international circuit with their associated relative levels. The subscript $i$ in the abbreviation $\text{dBBr}_i$ signifies that these relative levels are with respect to a 0 $\text{dBBr}$ point of the international circuit. + +It is clear that any other convenient pair of relative levels (differing by 0.5 dB in the correct sense) can be used in practice, e.g. the actual switching levels used in an international centre. + +*Case 2:* There does not exist any “ $t$ ” (see Figure B.4). + +This relates particularly to laboratory testing arrangements. + +![Diagram of a 4-wire telephone circuit showing transmission loss components S, R, and E. The top wire (transmit) has a source at point 'b' and a loss component 'S dB'. The bottom wire (receive) has a load at point 'a' with a level of -4 dBBr and a loss component 'R dB'. A vertical dashed line between the wires represents a hybrid or switching point. At this point, a 'Sidetone' path is shown with a variable attenuator and a 'Echo' path is shown with a variable attenuator and a loss component 'E dB'. The diagram is labeled T1205600-93/d06.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +Diagram of a 4-wire telephone circuit showing transmission loss components S, R, and E. The top wire (transmit) has a source at point 'b' and a loss component 'S dB'. The bottom wire (receive) has a load at point 'a' with a level of -4 dBBr and a loss component 'R dB'. A vertical dashed line between the wires represents a hybrid or switching point. At this point, a 'Sidetone' path is shown with a variable attenuator and a 'Echo' path is shown with a variable attenuator and a loss component 'E dB'. The diagram is labeled T1205600-93/d06. + +FIGURE B.4/G.122 + +In this case the loss of the path $a-“t”-b$ may be calculated from: $(R + E + S)$ dB (assuming acoustic feedback at the 4-wire telephone to be negligible). + +In both cases the loss of “the path $a-t-b$ ” can in principle be directly measured by the principles described in Annex A, i.e. by injecting a signal at $a$ and measuring the result at $b$ , so that one may properly say for all cases + +$$\left\{ \begin{array}{l} \text{transmission loss} \\ \text{of the path } a-t-b \end{array} \right\} \equiv \left\{ \begin{array}{l} \text{transmission loss} \\ \text{between } a \text{ and } b \end{array} \right\}$$ + +or, more shortly + +$$\text{loss } (a-t-b) \equiv \text{loss } (a-b)$$ + +## B.4 Stability and echo losses + +So far the quantities dealt with are functions of frequency and yield a graph of attenuation/frequency distortion. When it is required to characterize such a graph with a single number, additional qualifying indications are, for example, stability loss ( $a-b$ ) and echo loss ( $a-b$ ). + +The text of this Recommendation gives the definitions of these single-number descriptions thus: the stability loss ( $a-b$ ) is the least value (measured or calculated) in the band 0-4 kHz (see 2.1 and 3.1), and the echo loss ( $a-b$ ) is a weighted integral of the loss/frequency function over the band 300-3400 Hz, as defined in 4.2. + +When the echo-path loss/frequency characteristic is available in graphical or tabular form, alternative techniques for the calculation of echo loss ( $a-b$ ) are preferable to that suggested for the field measurement given in Annex A. + +NOTE – When evaluating echo loss from graphical or tabulated data, sufficient frequency points should be taken to ensure that the influence of the shape of the amplitude/frequency characteristic is adequately preserved. The more irregular the shape, the more points should be taken for a given accuracy. + +### Graphical data (trapezoidal rule) + +If the loss/frequency characteristic of the echo-path is available in graphical form (or the data were suitably measured) the echo loss may be calculated by using the trapezoidal rule as follows: + +- 1) Divide the frequency band (300 to 3400 Hz) into $N$ sub-bands of equal width on a log-frequency scale. +- 2) Read off the echo loss at each of the $N + 1$ frequencies at the edges of the $N$ sub-bands, and express it as an output/input power ratio, $A_i$ . +- 3) Calculate the echo loss using the formula: + +$$L_e = -10 \log_{10} \left[ \frac{1}{N} \left( \frac{A_0}{2} + A_1 + A_2 \dots + A_{N-1} + \frac{A_N}{2} \right) \right]$$ + +#### Tabulated data + +When the loss/frequency data are only available at $N + 1$ discrete frequencies, which are non-uniformly spaced on a log-frequency scale, proceed as follows: + +An approximation to the formula for echo loss ( $a-b$ ) given in the text is: + +$$L_e = 3.24 - 10 \log_{10} \sum_{i=1}^N (A_i + A_{i-1}) (\log_{10} f_i - \log_{10} f_{i-1})$$ + +where + +$A_0$ is the output/input power ratio at frequency of $f_0 = 300$ Hz; + +$A_i$ the ratio at frequency $f_i$ ; and + +$A_N$ the ratio at frequency $f_N = 3400$ Hz. + +### NOTES + +1 The approximation involved is to assume that within the sub-band $f_{i-1}$ , to $f_i$ , the power ratio is constant and has the value $A(f) = (A_i + A_{i-1})/2$ . + +2 The constant 3.24 in the approximate formula arises from a combination of the constant 3.85 in the definition and other constants produced by the approximation. + +The sum of product terms in the approximation formula may be conveniently calculated as illustrated in Table B.1 + +TABLE B.1/G.122 + +| $f_i$ (Hz)
(1) | $\log_{10} f_i$
(2) | $\log_{10} f_i - \log_{10} f_{i-1}$
(3) | loss
(dB)
(4) | ratio
$A_i$
(5) | $A_i + A_{i-1}$
(6) | $(3) \times (6)$
(7) | +|-------------------|------------------------|--------------------------------------------|---------------------|-----------------------|------------------------|-------------------------| +| 300 | 2.477 | | $\infty$ | 0 | | | +| | | 0.222 | | | 0.124 | 0.0275 | +| 500 | 2.699 | | 9.05 | 0.124 | | | +| | | 0.204 | | | 0.402 | 0.0820 | +| 800 | 2.903 | | 5.56 | 0.278 | | | +| | | 0.097 | | | 0.636 | 0.0617 | +| 1000 | 3.000 | | 4.46 | 0.358 | | | +| | | 0.176 | | | 0.838 | 0.1475 | +| 1500 | 3.176 | | 3.19 | 0.48 | | | +| | | 0.125 | | | 0.970 | 0.1213 | +| 2000 | 3.301 | | 3.09 | 0.49 | | | +| | | 0.097 | | | 0.881 | 0.0855 | +| 2500 | 3.398 | | 4.08 | 0.391 | | | +| | | 0.079 | | | 0.571 | 0.0451 | +| 3000 | 3.477 | | 7.45 | 0.180 | | | +| | | 0.055 | | | 0.180 | 0.0099 | +| 3400 | 3.532 | | $\infty$ | 0 | | | +| Total | | | | | | 0.5804 | + +$$L_e = 3.24 - 10 \log_{10} 0.5804 = 5.6 \text{ dB}$$ + +### B.5 Overall loudness rating of the echo path (talker echo loudness rating, TELR) + +Recommendation G.131 is concerned with complete talker echo paths and it is convenient to characterize this path in terms of loudness rating (LR). By convention we may regard the echo balance return loss as the contribution it makes to the overall loudness rating (OLR) of the mouth-ear echo path. Naturally, as indicated in 2, the echo loss ( $a-b$ ), when this is already known, may be used instead of the sum of three quantities: the LR ( $a-t$ ), the echo balance return loss at $t$ (averaged according to 2) and the LR ( $t-b$ ). + +Hence the nominal overall loudness rating of the echo path may be calculated as illustrated in Figure B.5. + +Overall loudness rating of the echo path (talker echo loudness rating, TELR) (see Annex A/G.111): + +- = SLR + RLR of the talker's national system, +- + twice the LR of the international chain (i.e.: $2L_i$ ), +- + the echo loss ( $a-b$ ) of the listener's national system (i.e. averaged according to this Recommendation). + +![Diagram of a telephone network showing the echo path and loss components. A Talker is connected to a national system, which is connected to an international chain, which is connected to a Listener's national system. The diagram shows the signal path from the Talker to the Listener, and the echo path from the Listener back to the Talker. The echo loss (a-b) is indicated. The diagram also shows the SLR (Send Loudness Rating) and RLR (Receive Loudness Rating) components. The international chain is labeled with Li (loss in dB) for both the forward and backward paths. The echo path is labeled with points a, b, a', and b' at the interfaces. The overall RLR is shown as the sum of the Talker's national system RLR, twice the international chain loss Li, and the echo loss (a-b).](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +FIGURE B.5/G.122 + +Diagram of a telephone network showing the echo path and loss components. A Talker is connected to a national system, which is connected to an international chain, which is connected to a Listener's national system. The diagram shows the signal path from the Talker to the Listener, and the echo path from the Listener back to the Talker. The echo loss (a-b) is indicated. The diagram also shows the SLR (Send Loudness Rating) and RLR (Receive Loudness Rating) components. The international chain is labeled with Li (loss in dB) for both the forward and backward paths. The echo path is labeled with points a, b, a', and b' at the interfaces. The overall RLR is shown as the sum of the Talker's national system RLR, twice the international chain loss Li, and the echo loss (a-b). + +## B.6 Summary of useful terms + +**return loss:** Relates to a 2-wire bidirectional circuit; classical definition. + +**balance return loss:** Proportion of the loss at the $a-t-b$ path attributable to the degree of match between the 2-wire impedance and the balance impedance at the terminating unit. Applicable only if there is a point “ $t$ ”. + +**transmission loss of the path $a-t-b$ :** Can be regarded as the loss $(a-b)$ , whether there exists a physical point “ $t$ ” or not. + +**stability loss $(a-b)$ :** The least value of the loss $(a-b)$ in the band 0 to 4 kHz. + +**echo loss $(a-b)$ :** The loss $(a-b)$ averaged according to the definition in 2 of the text. + +**echo balance return loss:** A balance return loss averaged according to 2 of the text. + +**overall loudness rating of the echo path; talker echo loudness rating (TELR):** The sum of the send loudness rating and receive loudness rating of the talker’s national system, twice the LR of the international chain, and the echo loss $(a-b)$ of the listener’s national system. + +## References + +- [1] *Calculations of the stability of international connections established in accordance with the transmission and switching plan*, CCITT *Green Book*, Vol. III-2, Supplement No. 1, ITU, Geneva, 1973. +- [2] CCITT manual *Transmission planning of switched telephone networks*, ITU, Geneva, 1976. \ No newline at end of file diff --git a/marked/G/T-REC-G.136-199909-I_PDF-E/raw.md b/marked/G/T-REC-G.136-199909-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..113f2edbbd1b2f7a337c0e24d7b2fca5d6cfeb25 --- /dev/null +++ b/marked/G/T-REC-G.136-199909-I_PDF-E/raw.md @@ -0,0 +1,203 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.136** + +(09/99) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +International telephone connections and circuits – General +characteristics of the 4-wire chain formed by the +international circuits and national extension circuits + +--- + +**Application rules for automatic level control +devices** + +ITU-T Recommendation G.136 + +(Previously CCITT Recommendation) + +--- + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| General definitions | G.100–G.109 | +| General Recommendations on the transmission quality for an entire international telephone connection | G.110–G.119 | +| General characteristics of national systems forming part of international connections | G.120–G.129 | +| General characteristics of the 4-wire chain formed by the international circuits and national extension circuits | G.130–G.139 | +| General characteristics of the 4-wire chain of international circuits; international transit | G.140–G.149 | +| General characteristics of international telephone circuits and national extension circuits | G.150–G.159 | +| Apparatus associated with long-distance telephone circuits | G.160–G.169 | +| Transmission plan aspects of special circuits and connections using the international telephone connection network | G.170–G.179 | +| Protection and restoration of transmission systems | G.180–G.189 | +| Software tools for transmission systems | G.190–G.199 | +| INTERNATIONAL ANALOGUE CARRIER SYSTEM | | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TESTING EQUIPMENTS | | +| TRANSMISSION MEDIA CHARACTERISTICS | G.600 – G.699 | +| DIGITAL TRANSMISSION SYSTEMS | | +| TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +# **APPLICATION RULES FOR AUTOMATIC LEVEL CONTROL DEVICES** + +## **Summary** + +This Recommendation provides a set of general application guidelines for network based Automatic Level Control Devices. These network based ALC devices are expected to comply with Recommendation G.169 "Automatic Level Control Devices". + +### **Source** + +ITU-T Recommendation G.136 was prepared by ITU-T Study Group 12 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on 30 September 1999. + +### **Keywords** + +ALC, automatic level control, application rules, planning guidelines. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation the term *recognized operating agency (ROA)* includes any individual, company, corporation or governmental organization that operates a public correspondence service. The terms *Administration*, *ROA* and *public correspondence* are defined in the *Constitution of the ITU (Geneva, 1992)*. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2000 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | | Page | +|-----|-----------------------------------------------|-------------| +| 1 | Introduction..... | 1 | +| 2 | References..... | 1 | +| 3 | Effects of level control..... | 2 | +| 4 | Automatic Level Control devices ..... | 2 | +| 4.1 | Application guidelines ..... | 2 | +| 5 | Insertion of ALC devices in a connection..... | 3 | + + + +# **APPLICATION RULES FOR AUTOMATIC LEVEL CONTROL DEVICES** + +*(Geneva, 1999)* + +## **1 Introduction** + +This Recommendation applies only to network based Automatic Level Control (ALC) devices that are placed within networks. For the purposes of this Recommendation an ALC device is defined as any piece of signal processing equipment located in the digital transmission path which automatically adjusts the level of a signal towards a pre-determined value, or which modifies the frequency response or spectral content of the signal in such a way as to affect the overall level of the signal. + +In a communication system one of the significant transmission parameters that can affect perceived quality is the overall loudness rating of the connection. This loudness level is controlled by the characteristics of the originating terminal, the loss of the network which is comprised of: accesses, switches, circuits, and the terminating terminal. The purpose of the audio path associated with the end-to-end connection is to facilitate the transfer of intelligence. Transfer of intelligence by communication involves not just the content of what is said but is affected by the ability of the speaker to rapidly change the volume of the speech, to convey emotion for example. + +This Recommendation has been prepared to provide planning guidance for the placement of network based ALC devices that can arbitrarily change the signal level and bandwidth of a communication channel. + +This Recommendation provides guidelines which, if followed, should ensure that network implemented with ALC devices will result in implementations that continue to be aligned with published ITU- T Recommendations. + +## **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.101 (1996), *The transmission plan*. +- ITU-T Recommendation G.120 (1998), *Transmission characteristics of national networks*. +- ITU-T Recommendation G.121 (1993), *Loudness ratings (LRs) of national systems*. +- ITU-T Recommendation G.122 (1993), *Influence of national systems on stability and talker echo in international connections*. +- ITU-T Recommendation G.126 (1993), *Listener echo in telephone networks*. +- ITU-T Recommendation G.131 (1996), *Control of talker echo*. +- ITU-T Recommendation G.165 (1993), *Echo cancellers*. +- ITU-T Recommendation G.168 (1997), *Digital network echo cancellers*. +- ITU-T Recommendation G.169 (1999), *Automatic level control devices*. + +- ITU-T Recommendation P.310 (1996), *Transmission characteristics for telephone band (300-3400 Hz) digital telephones.* +- ITU-T Recommendation P.340 (1996), *Transmission characteristics of hands-free telephones.* +- ITU-T Recommendation P.342 (1996), *Transmission characteristics for telephone band (300-3400 Hz) digital loudspeaking and hands-free telephony terminals.* + +## 3 Effects of level control + +The design and implementation of the PSTN was shaped by international agreements which were formulated as ITU-T Recommendations relating to overall transmission performance and transmission planning guidance. In this regard the network related Recommendations, viz. G.101 – The transmission plan; G.121 – Loudness ratings (LRs) of national systems; G.120 – Transmission characteristics of national networks, and the terminal, viz. Recommendations P.310 – Transmission characteristics for telephone band (300-3400 Hz) digital telephones; P.340 – Transmission characteristics of hands-free telephones; P.342 – Transmission characteristics for telephone band (300-3400 Hz) digital loudspeaking and hands-free telephony terminals, have by default defined the range of acceptable end-to-end connection losses. The ITU-T has accepted the concept that customers may wish to modify the end-to-end connection loss and thus ITU-T Recommendations now make provision for the use of volume controls on terminal equipment, e.g. on telephone sets and automatic level control devices on audio conference bridges. Further, the placement of ALC devices should be consistent with the planning guidance provided in the following Recommendations, viz. G.122 – Influence of national systems on stability and talker echo in international connections, G.126 – Listener echo in telephone networks, G.131 – Control of talker echo, and G.175 – Transmission planning for private/public network interconnection of voice traffic. + +It is recognized that the use of ALC devices can change the real time dynamics of a conversation and as a result, the transmission impairments that result from ALC devices must be controlled. Further, it is recognized that unless the placement of ALC devices within networks is performed in an orderly fashion, the integrity of the networks can be compromised. The following guidelines present a set of rules which if followed should result in acceptable network implementations. + +## 4 Automatic Level Control devices + +Specific guidelines for deployment of ALCs may vary between national networks and even between networks within the same country. These guidelines are usually established in consideration of performance and customer expectations, competitive pressures, specific business goals, economic and technological constraints, etc. As a practical matter they must take into consideration the routing and the technology used to provide the connection. + +### 4.1 Application guidelines + +The following are a set of general application guidelines for Automatic Level Control devices which are compliant with Recommendation G.169. It is recognized that while there may be a need to develop application guidelines for ALC devices within national networks, that the generation of national guidelines is a national matter and thus is outside the scope of this Recommendation. + +- 1) An ALC device should only be placed on connections which are equipped with active echo cancellers, e.g. echo cancellers which are compliant with Recommendation G.165 – Echo cancellers or G.168 – Digital network echo cancellers. + +- 2) An ALC device should not be placed in the tail path of the echo canceller that is performing the echo control function for that connection. (When echo cancellers are tandemed only one of the echo cancellers is performing the echo cancelling functionality for that connection. The ALC device must not appear in the tail of the canceller that is performing the echo control function.) +- 3) ALC devices should never operate in tandem. +- 4) An ALC device should operate on signals received from other Administrations and should not modify a signal that is to be passed to another Administration, unless there is a bilateral agreement to do so. + +## **5 Insertion of ALC devices in a connection** + +An ALC device is a particular type of device that incorporates a speech processing function that acts upon a unidirectional speech signal. Thus, it is expected that ALC devices placed within the network will operate at a 4-wire point in the connection. This Recommendation is not intended to preclude any implementation scheme and recognizes that there may be implementation benefits if the ALC functionality is integrated into a device which also performs other speech processing functions, e.g. an echo canceller function. + + + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/G/T-REC-G.169-201105-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/marked/G/T-REC-G.169-201105-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c13f4dd57fa1adb18a92d74b7f1b165870d484e5 --- /dev/null +++ b/marked/G/T-REC-G.169-201105-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26273c403740892d44ebe12ef10fe88296d22f1beb40782d5101d3525a0b1e1d +size 26959 diff --git a/marked/G/T-REC-G.169-201105-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/G/T-REC-G.169-201105-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bde22255eaf32bd5dcec7e96bb85bd79a9c6495f --- /dev/null +++ b/marked/G/T-REC-G.169-201105-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de227a231eb9e5ab6c553ed7bcb15a6117d263af43cab11de3f8bcda6c13ec98 +size 27716 diff --git a/marked/G/T-REC-G.169-201105-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/G/T-REC-G.169-201105-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cde9ed0914914edcf0aca0cba8a4d7603c12143 --- /dev/null +++ b/marked/G/T-REC-G.169-201105-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a0251260082f8d52046a5ba308b315e8f74a59d9cb81fe6cff6d09f7ba1e129 +size 35301 diff --git a/marked/G/T-REC-G.169-201105-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/G/T-REC-G.169-201105-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be73f519ab42000990d81bd3dda4313c490e7115 --- /dev/null +++ b/marked/G/T-REC-G.169-201105-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cab6564bc9fe508322b84b83fbcdf2d5ed607fc42b501afb636da3eca634c6a6 +size 6702 diff --git a/marked/G/T-REC-G.169-201105-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/G/T-REC-G.169-201105-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43bb801e5d625dd34506c45f038afc866187f1b0 --- /dev/null +++ b/marked/G/T-REC-G.169-201105-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d54ecf84cc2a8a9543254f7ca95d8dee33286b9ad5a3fb7c286c2f89b7a7696 +size 64197 diff --git a/marked/G/T-REC-G.169-201105-I_PDF-E/c036e2540a94b31357ceb0002f0cacab_img.jpg b/marked/G/T-REC-G.169-201105-I_PDF-E/c036e2540a94b31357ceb0002f0cacab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67035e14d6bd54ff1b07405f496df5390b8da2bc --- /dev/null +++ b/marked/G/T-REC-G.169-201105-I_PDF-E/c036e2540a94b31357ceb0002f0cacab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a6b3f70040012d0fbf0b042f3be46621f67d77972572070217155c46c4f4c1d +size 16713 diff --git a/marked/G/T-REC-G.169-201105-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg b/marked/G/T-REC-G.169-201105-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c2ae8cd570b817da0ae13641d5f6b001ce1ba10 --- /dev/null +++ b/marked/G/T-REC-G.169-201105-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ab4fdc858f613ffb7a7cb261af4c3d988caa1af264a8c5e5faa6a6de113a928 +size 40745 diff --git a/marked/G/T-REC-G.169-201105-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/G/T-REC-G.169-201105-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0d39ab26ec02c92cdabb62ffcea5094f3a821a0 --- /dev/null +++ b/marked/G/T-REC-G.169-201105-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acd9de606bcae3fe9384679c123cc58fea1381f62bfd11c410055d10a5237549 +size 32675 diff --git a/marked/G/T-REC-G.169-201105-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.169-201105-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7b52ea4287d6402533d3db6e0e4bc17f880c222 --- /dev/null +++ b/marked/G/T-REC-G.169-201105-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c39a7b49fe04fdbcfa9e84a369fca16a12a6b1e434692ce623fb8f186df91924 +size 20688 diff --git a/marked/G/T-REC-G.172-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.172-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99138d38ec6676f0023e3605f9b4fe5e3951d147 --- /dev/null +++ b/marked/G/T-REC-G.172-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa65ab234ca7d71e8a87800bda77e2a00132c8ba26ed84ea2f9a86d51172b89d +size 7471 diff --git a/marked/G/T-REC-G.172-198811-I_PDF-E/5d92d5c9cc01a262b0389d138caa9aea_img.jpg b/marked/G/T-REC-G.172-198811-I_PDF-E/5d92d5c9cc01a262b0389d138caa9aea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..303e8eae2af1537f225d016d8a30725033eabc8a --- /dev/null +++ b/marked/G/T-REC-G.172-198811-I_PDF-E/5d92d5c9cc01a262b0389d138caa9aea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60ce1d6f8cf7aab20908b2e6653e05f4231d07ac638e9bb2d2cb998e98a4234d +size 42614 diff --git a/marked/G/T-REC-G.172-198811-I_PDF-E/7fb5215fd72210a2e4cce6df55550c89_img.jpg b/marked/G/T-REC-G.172-198811-I_PDF-E/7fb5215fd72210a2e4cce6df55550c89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04b8b4db9b828f2a0a61aabe2e527a5e7ff46d2e --- /dev/null +++ b/marked/G/T-REC-G.172-198811-I_PDF-E/7fb5215fd72210a2e4cce6df55550c89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a5ffbdc64e9aee8abf5e3d9b9abfb49c106a82f6e0d6d7fc52399899f9d0242 +size 30192 diff --git a/marked/G/T-REC-G.172-198811-I_PDF-E/e0d425c8e4eef259e4c52d81426d93fa_img.jpg b/marked/G/T-REC-G.172-198811-I_PDF-E/e0d425c8e4eef259e4c52d81426d93fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efa7f504ae0dab3b576bb26872314e4007e57151 --- /dev/null +++ b/marked/G/T-REC-G.172-198811-I_PDF-E/e0d425c8e4eef259e4c52d81426d93fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:321ce96227ad0f40676a7d265d040224f38edee586ff9cfd81483d1b973750c4 +size 56533 diff --git a/marked/G/T-REC-G.172-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.172-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..26dc46e690d39f4f4c66d086c99254c9575da51d --- /dev/null +++ b/marked/G/T-REC-G.172-198811-I_PDF-E/raw.md @@ -0,0 +1,127 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +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.172** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**TRANSMISSION SYSTEMS AND MEDIA +TRANSMISSION PLAN ASPECTS OF +SPECIAL CIRCUITS AND CONNECTIONS +USING THE INTERNATIONAL TELEPHONE +CONNECTION NETWORK** + +--- + +**TRANSMISSION PLAN ASPECTS OF +INTERNATIONAL CONFERENCE CALLS** + +**ITU-T Recommendation G.172** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation G.172 was published in Fascicle III.1 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. + +# **TRANSMISSION PLAN ASPECTS OF INTERNATIONAL CONFERENCE CALLS** + +*(Malaga-Torremolinos, 1984; amended at Melbourne, 1988)* + +The transmission considerations given here are applicable to conference calls set up and operated in accordance with Recommendation E.151. + +**1** In order to respect CCITT Recommendations concerning loudness ratings on international connections, high quality bridging equipment shall be used. This equipment shall be designed to provide a nominal transmission loss of 0 dB in the direction from whichever participant is for the moment active (speaking) to all inactive (listening) participants. This loss shall be measured between equal level switching points of national circuits or virtual switching points of international circuits. + +*Note* - Some conference bridges employ the use of automatic gain control (AGC) to minimize the contrast that exists between the speech levels of participants on connections having different losses, and the above consideration does not apply for such bridges. The transmission consideration for bridges with AGC is a subject for future study. + +**2** A modern conference bridge shall be used which employs techniques to avoid excessive transmission impairment from the accumulation of noise and echo at the output of the bridge in a multiport conference arrangement. + +In a conference connection with two bridges: one bridge has N1 ports including a talker and the other bridge has N2 ports, noise increases as the number of ports is increased, according to the approximate rule: $10 \log (N1 + N2 - 1)$ . + +Talker and listener echoes also increase as the number of ports is increased as shown in Figure 1/G.172. + +The multi-bridge configuration thus highlights the need for noise and echo control. + +*Note 1* - For example, a conference bridge which provides voice-activated switched loss or its equivalent may be used. In such a bridge, 15 dB of loss would be connected in each input to the bridge when the customer on that path is inactive. When a participant becomes active the loss is switched from his talking path to his listening path. This differential action protects the talker from echo and prevents a reduction of singing margin when the switch is operated. The loss which normally exists in the transmit path attenuates weak input signals such as noise before they enter the bridge. With this arrangement the level of the total signal reflected back to any active port will be the sum of the individual reflections from all other ports diminished by 30 dB. + +This bridge can be equipped with about 30 ports. + +*Note 2* - A description of a conference bridge employing voice-activated switched loss is available in Annex 2 to Question 6/XVI in Volume III-3 of the *Green Book*. The transmission requirements contained in that annex could be used for the design of bridging equipment. Requirements for the design of bridging equipment using other techniques to control level contrast and noise and echo accumulation are the subject of future study. + +![Graph (a) showing Talker echo level (dB) versus N2. The y-axis ranges from 10 to 30 dB, and the x-axis ranges from 0 to 30. Multiple curves are shown for different values of Ki (0 and 2) and N1 (1, 5, 10). The curves show that the talker echo level increases with N2 and is higher for smaller values of N1 and Ki.](5d92d5c9cc01a262b0389d138caa9aea_img.jpg) + +Graph (a) showing Talker echo level (dB) versus N2. The y-axis ranges from 10 to 30 dB, and the x-axis ranges from 0 to 30. Multiple curves are shown for different values of Ki (0 and 2) and N1 (1, 5, 10). The curves show that the talker echo level increases with N2 and is higher for smaller values of N1 and Ki. + +a) Talker echo level + +![Graph (b) showing Listener echo level (dB) versus N1 + N2. The y-axis ranges from 10 to 30 dB, and the x-axis ranges from 0 to 30. A single curve is shown for the condition N1 ≥ 1, N2 ≥ 1, and N1.N2 ≠ 1. The curve shows that the listener echo level increases with the sum of N1 and N2.](7fb5215fd72210a2e4cce6df55550c89_img.jpg) + +Graph (b) showing Listener echo level (dB) versus N1 + N2. The y-axis ranges from 10 to 30 dB, and the x-axis ranges from 0 to 30. A single curve is shown for the condition N1 ≥ 1, N2 ≥ 1, and N1.N2 ≠ 1. The curve shows that the listener echo level increases with the sum of N1 and N2. + +b) Listener echo level + +Ki Transmission loss between bridges + N1 Number of #1 bridge's subscribers + N2 Number of #2 bridge's subscribers + +FIGURE 1/G.172 + +## **Increased talker and listener echo levels in a conference with two bridges** + +3 Optimum operation of a conference bridge is obtained when its location is close to the center of the connection. This tends to equalize loss from the bridge to all conference locations on the connection, thus minimizing level contrast. Thus bridging equipment for international calls should be at high order transit centers. + +4 Bridging equipment should be 4-wire presented and 4-wire switched on both national and international circuits, wherever possible. + +5 Attention is called to Recommendation G.114 concerning mean one-way propagation time which recommends that connections with delays in excess of 400 ms should not be used except under the most exceptional circumstances. To comply with this recommendation, care should be taken in the selection of a connection diagram so as to avoid the use of more than a single satellite circuit. For some conferences, using a single star network, this could influence the choice of location for the conference bridge. For other conferences, the use of a multiple star network could be selected with a single satellite circuit, equipped with appropriate echo suppressors, linking the conference bridges. + +6 The conference connections should be carefully chosen so as to minimize the number of voice-activated switched loss devices in tandem to no more than two per conference leg. This includes customer premises conference equipment (such as loudspeaking telephones) and network equipment (such as echo suppressors), but excludes the bridging equipment. + +7 Whenever the conference involves a single person at a location using a subscriber handset the room noise should be limited to about 60 dB SPL(A)1) at the user position to provide good quality transmission. Figure 2/G.172 shows the mean opinion score of transmission quality versus room noise [1]. Failure of the customer to comply with this guideline may cause the conference to be unacceptable. + +8 When a conference involves more than a single person at each location it may be desirable to use conference rooms equipped with microphones and loudspeakers. To assure an adequate signal-to-noise ratio and freedom from the + +1) Sound pressure level relative to 20 μPa and using the A-weighting. See Recommendation P.54 for information concerning sound level measurements. + +effects of conference room reverberation, the microphone and loudspeaker placement guidelines contained in Supplement No. 4, Volume V should be followed2). + +![Line graph showing Mean opinion score (1-5) vs Room noise (30-80 dB SPL(A)). The curve shows a downward trend from 'Good' to 'Poor' as noise increases. CCITT - 82250](e0d425c8e4eef259e4c52d81426d93fa_img.jpg) + +The graph plots 'Mean opinion score' on the y-axis (ranging from 1 to 5) against 'Room noise' in dB SPL(A) on the x-axis (ranging from 30 to 80). The y-axis is labeled with qualitative terms: 'Excellent' (5), 'Good' (4), 'Fair' (3), 'Poor' (2), and 'Unsatisfactory' (1). The x-axis has major ticks every 10 units from 30 to 80. A curve with square markers shows a downward trend, indicating that as room noise increases, the mean opinion score decreases. The curve starts at approximately 3.9 at 37 dB SPL(A) and ends at approximately 1.8 at 72 dB SPL(A). The text 'CCITT - 82250' is located in the bottom right corner of the graph area. + +| Room noise (dB SPL(A)) | Mean opinion score | +|------------------------|--------------------| +| 37 | 3.9 | +| 40 | 3.8 | +| 45 | 3.6 | +| 55 | 3.4 | +| 60 | 3.2 | +| 67 | 2.6 | +| 72 | 1.8 | + +Line graph showing Mean opinion score (1-5) vs Room noise (30-80 dB SPL(A)). The curve shows a downward trend from 'Good' to 'Poor' as noise increases. CCITT - 82250 + +*Note* - This curve represents the opinion of customers listening over the telephone in room noise from 37 dB SPL(A) to 72 dB SPL(A). Each point is an average over all values of speech level and circuit noise given at that room noise level. + +FIGURE 2/G.172 +**Relationship of transmission quality to room noise** + +# Reference + +- [1] *Guidelines for improving telephone communications in noisy room environments*, Bell System Technical Reference, PUB 42902, February 1980, American Telephone and Telegraph Co. + +2) Another problem associated with hands-free conferencing is the likelihood of acoustic feedback between loudspeaker and microphone. While this feedback is today generally controlled using voice-activated switched loss in the conference room terminal equipment, note is taken of the fact that Study Group XV has proposed new studies to determine how to use echo cancellers to control the acoustic feedback. \ No newline at end of file diff --git a/marked/G/T-REC-G.224-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.224-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/G/T-REC-G.224-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/G/T-REC-G.224-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.224-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7d53b7900d856385ebed648350f0fb141bcf85f4 --- /dev/null +++ b/marked/G/T-REC-G.224-198811-I_PDF-E/raw.md @@ -0,0 +1,65 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**G.224** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **INTERNATIONAL ANALOGUE CARRIER SYSTEMS GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS** --- + +**MAXIMUM PERMISSIBLE VALUE FOR THE +ABSOLUTE POWER LEVEL (POWER +REFERRED TO ONE MILLIWATT) OF +A SIGNALLING PULSE** + +**ITU-T Recommendation G.224** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +- 1 ITU-T Recommendation G.224 was published in Fascicle III.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +### Recommendation G.224 + +#### MAXIMUM PERMISSIBLE VALUE FOR THE ABSOLUTE POWER LEVEL (POWER REFERRED TO ONE MILLIWATT) OF A SIGNALLING PULSE 1 + +The CCITT recommends that, for crosstalk reasons, the absolute power level of each component of a short duration signal should not exceed the values given in Table 1/G.224. + +TABLE 1/G.224 + +#### Maximum permissible value, at a zero relative level point + +| Signalling frequency (Hz) | Maximum permissible power for a signal at a zero relative level point (microwatts) | Corresponding absolute power level
Decibels referred to 1mW (dBm0) | +|---------------------------|------------------------------------------------------------------------------------|-----------------------------------------------------------------------| +| 800 | 750 | -1 | +| 1200 | 500 | -3 | +| 1600 | 400 | -4 | +| 2000 | 300 | -5 | +| 2400 | 250 | -6 | +| 2800 | 150 | -8 | +| 3200 | 150 | -8 | + +*Note 1* - If the signals are made up of two different frequency components transmitted simultaneously, the maximum permissible values for the absolute power levels are 3 dB below the above values. + +*Note 2* - The values given in this table result from a compromise between the characteristics of various channel filters now in existence. + +## Reference + +- [1] CCITT Recommendation *Maximum permissible value for the absolute power level of a signalling pulse*, Vol. VI, Rec. Q.16. + +1 This Recommendation applies both to national and to international signalling systems. \ No newline at end of file diff --git a/marked/G/T-REC-G.231-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.231-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/G/T-REC-G.231-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/G/T-REC-G.231-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.231-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4330a4a7e055406c8f8f834d6118171a345290b8 --- /dev/null +++ b/marked/G/T-REC-G.231-198811-I_PDF-E/raw.md @@ -0,0 +1,95 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**G.231** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **INTERNATIONAL ANALOGUE CARRIER SYSTEMS GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS** --- + +## **ARRANGEMENT OF CARRIER EQUIPMENT** + +**ITU-T Recommendation G.231** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +- 1 ITU-T Recommendation G.231 was published in Fascicle III.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## **ARRANGEMENT OF CARRIER EQUIPMENT** + +*(amended at Geneva, 1964; further amended)* + +### **1 Carrier-system racks (formerly Part A)** + +The CCITT, + +*considering* + +that countries not having a national industry for the construction of carrier systems must obtain them from different factories, and that the variations of the dimensions of the racks between different sources of supply do not allow of a simple and economical layout of the cables and efficient use of accommodation, + +*unanimously recommends* + +that in future the dimensions of carrier-system racks should meet the requirements as follows: + +- 1) *Space between suites* - The minimum space between suites should be such that it is possible to move test trolleys from place to place (between two suites), and also for maintenance staff to be able to work comfortably between two suites. A spacing of 75 cm at least seems reasonable. +- 2) *Overall height* - The overall height of a rack above the floor (not including the space provided for overhead cable runs) should not exceed 320 cm. + +In principle, 30 cm should be allowed for overhead cable runs, and also about 30 cm for access to these cables, which makes at the most 60 cm between the top of the rack and the ceiling; nevertheless, some Administrations consider that a total height of 40 cm between the top of the rack and the ceiling is sufficient in certain cases. In main repeater stations (or terminal equipment stations), where, in addition to cables connecting one rack to another, general distribution cables have to be allowed for, it is recommended that the height of the building between the floor and the ceiling should be at least 4 m to facilitate access to the various cables. + +- 3) *Thickness* - The thickness of a rack should not be greater than 45 cm. For racks which may be placed back to back the total suite thickness may be up to 52 cm, including all maintenance controls, cooling fins, etc., which may protrude from the nominal face of the equipment. + +### **2 Use of standard components in transmission equipment1) (formerly Part B)** + +While acknowledging that the International Electrotechnical Commission (IEC) is competent to devise standards for components or devices generally used in electrical engineering, the CCITT nevertheless reserves the right to issue recommendations dealing with such equipment and with transmission systems which, if components standardized by the IEC were used, may prove impossible to create. + +Furthermore, manufacturers and Administrations wishing to use components specified by the IEC or by another body will still be responsible for ensuring that the recommendations issued by the CCITT are met. + +--- + +1) This recommendation applies both to carrier systems and to audio equipment. + +Hence the CCITT *recommends* + +that Administrations and manufacturers should ensure that all components used in transmission systems and equipments (even if such components have been standardized by some other national or international body) are such that the requirements of CCITT recommendations will be complied with in the conditions of use envisaged, throughout the life of the equipment or systems, i.e. twenty years or more. + +### 3 **Power supply** (formerly Part C) + +Information on noise at the terminals of the battery power supply system is given in Supplement No. 13 [1]. + +For carrier system equipment, it is recommended that power supply equipment should provide a no-break supply when the power mains fail. + +*Note* - Much existing equipment has been designed in accordance with the old recommendation in Volume III of the *Blue Book* (1964) which is reproduced below: + +"In countries where the main power supply is unreliable and where it is the normal source of supply for the coaxial system, it is recommended that in each power-feeding station there should be equipment to transfer from the normal source of supply to a standby source or vice versa in such a manner that breaks in transmission on voice-frequency telegraph circuits or on telephone circuits with automatic signalling carried by the system do not exceed about 150 milliseconds." + +### 4 **Repeater station cabling2)** (formerly Part D) + +The Administrations mentioned in the list kept by the CCITT Secretariat are prepared to supply other Administrations and technical assistance experts working under the ITU with information on the national standards they apply to the wiring of repeater stations. However, they would warn users that cable specifications and wiring diagrams are not always the best way of giving them the information they desire. The documentation available is very bulky and requests for information should be reasonably precise, since it is essential to know exactly on what point information is required in order to decide what form the reply should take. + +A proper understanding of how wiring is done in repeater stations cannot be acquired from documents alone and the persons concerned should get in touch with the Administrations on the list in order to see the methods put into practice. + +Administrations are invited to supply information to keep this list, which is deposited with the CCITT Secretariat, constantly up to date. + +## **Reference** + +- [1] *Noise at the terminals of the battery supply*, Orange Book, Vol. III-3, Supplement No. 13, ITU, Geneva, 1977. + +--- + +2) This recommendation applies both to carrier systems and to audio equipment. \ No newline at end of file diff --git a/marked/G/T-REC-G.332-198811-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/G/T-REC-G.332-198811-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28e28a7100031295f707492e4d990137d6e097c8 --- /dev/null +++ b/marked/G/T-REC-G.332-198811-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f70c27dcaf54b5aaaf4d28e19f7243a83c866a3e263a5b22e37d04c12098495 +size 29479 diff --git a/marked/G/T-REC-G.332-198811-I_PDF-E/1a6d75c94d3fd49936527eadd25e9278_img.jpg b/marked/G/T-REC-G.332-198811-I_PDF-E/1a6d75c94d3fd49936527eadd25e9278_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..135c0bff472f139caf4d5c7c78567342e90023e6 --- /dev/null +++ b/marked/G/T-REC-G.332-198811-I_PDF-E/1a6d75c94d3fd49936527eadd25e9278_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c17ef968defc93ddc4b86a0902a92f9223a678de4c74d698482c2b588c593fa +size 70674 diff --git a/marked/G/T-REC-G.332-198811-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg b/marked/G/T-REC-G.332-198811-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca6924c00ce0ba914b7dfa5b79577bd981ffdedc --- /dev/null +++ b/marked/G/T-REC-G.332-198811-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75a2e89673bccd4d70301462f46911288214ce4a8a6d20d8e4f695a4165ff07c +size 38918 diff --git a/marked/G/T-REC-G.332-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.332-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/G/T-REC-G.332-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/G/T-REC-G.332-198811-I_PDF-E/5d92d5c9cc01a262b0389d138caa9aea_img.jpg b/marked/G/T-REC-G.332-198811-I_PDF-E/5d92d5c9cc01a262b0389d138caa9aea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c45d302c46417fc33d2607f10bb7a0bd86554f2f --- /dev/null +++ b/marked/G/T-REC-G.332-198811-I_PDF-E/5d92d5c9cc01a262b0389d138caa9aea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bae5293d9a547486719c0c5f8f4be3d9d915c2fad1f253926c0a9884fff85a0c +size 68354 diff --git a/marked/G/T-REC-G.332-198811-I_PDF-E/954ff3c220707f98bcb2c4b197bd7d9f_img.jpg b/marked/G/T-REC-G.332-198811-I_PDF-E/954ff3c220707f98bcb2c4b197bd7d9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec31f9488620e5026eb855ada63bfa846f17d3fe --- /dev/null +++ b/marked/G/T-REC-G.332-198811-I_PDF-E/954ff3c220707f98bcb2c4b197bd7d9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f28c977df0af7bf18b692552681ad49667024632557571a2ad19ddff99a67f8 +size 44319 diff --git a/marked/G/T-REC-G.332-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/G/T-REC-G.332-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ab8fd4112ccda37f18dfa3b95ccb3bc5ff86a05 --- /dev/null +++ b/marked/G/T-REC-G.332-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:578d1af55dc8247988a378497c0cecc443bf89d1a8593cd6a0cbd3af30c35c7c +size 37902 diff --git a/marked/G/T-REC-G.332-198811-I_PDF-E/dd0f5301a5a6dd7c319701302110de88_img.jpg b/marked/G/T-REC-G.332-198811-I_PDF-E/dd0f5301a5a6dd7c319701302110de88_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9eed1c6375728bf4d65a424599a3ac3fe003ef72 --- /dev/null +++ b/marked/G/T-REC-G.332-198811-I_PDF-E/dd0f5301a5a6dd7c319701302110de88_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83d3d50727d105ea5df69dd9a9e828e477834ed47108a45d90522ba8763b7b98 +size 69179 diff --git a/marked/G/T-REC-G.332-198811-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/G/T-REC-G.332-198811-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74ec15ab21086cacde7e2b3b6512f71568699ec0 --- /dev/null +++ b/marked/G/T-REC-G.332-198811-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d729f54ae7597801164df986bf50ac394a2a03e5eaa40915817aa0ae94beaae +size 12356 diff --git a/marked/G/T-REC-G.332-198811-I_PDF-E/f961cbef0f8217e216b553bed270315b_img.jpg b/marked/G/T-REC-G.332-198811-I_PDF-E/f961cbef0f8217e216b553bed270315b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..671c8250f0cdaa5713e78eef0b2aaa0285d93d89 --- /dev/null +++ b/marked/G/T-REC-G.332-198811-I_PDF-E/f961cbef0f8217e216b553bed270315b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ecf1533e488c60927240a71929eb43fccdfac364c61376ca0db37cb3600d823 +size 41606 diff --git a/marked/G/T-REC-G.332-198811-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/G/T-REC-G.332-198811-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1037e11f36b92ad9128d8e70b1a8e579b3f72360 --- /dev/null +++ b/marked/G/T-REC-G.332-198811-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b6774cb685d7780792383ff3bae11c1d07f6203c4d5c84b794aa8591ae97bb8 +size 52088 diff --git a/marked/G/T-REC-G.332-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.332-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..59701350cf59ed5c4d15af2872c75adc9ef3882b --- /dev/null +++ b/marked/G/T-REC-G.332-198811-I_PDF-E/raw.md @@ -0,0 +1,375 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**G.332** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **INTERNATIONAL ANALOGUE CARRIER SYSTEMS INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES** --- + +**12 MHz SYSTEMS ON STANDARDIZED +2.6/9.5 mm COAXIAL CABLE PAIRS** + +**ITU-T Recommendation G.332** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +1 ITU-T Recommendation G.332 was published in Fascicle III.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## **12 MHz SYSTEMS ON STANDARDIZED 2.6/9.5 mm COAXIAL CABLE PAIRS** + +*(Mar del Plata, 1968; amended at Geneva, 1980)* + +This Recommendation defines a coaxial cable system providing 2700 telephony channels in the frequency band 0.3 MHz to about 12.4 MHz which, according to the provisions of Recommendation J.73 [1], can alternatively be used to provide 1200 telephone channels in the frequency band 0.3 MHz to about 5.6 MHz and one TV-channel in the band of about 6 MHz to 12.3 MHz for the transmission of a vestigial sideband television signal with an effectively transmitted video-frequency band up to 5.5 MHz. The repeaters should be spaced at about 4.5 km. + +## **1 Arrangement of line frequencies for telephony** + +The arrangement of the line frequencies for telephony shall conform to Plans 1A, 1B or 2 described below. Plan 1A is to be preferred to Plan 1B. In international relations between countries using different modulation procedures (see Recommendation G.211) and in the absence of any special arrangement between the Administrations concerned including, if necessary, the Administrations of transit countries, Plans 1 are to be preferred to Plan 2. + +### **1.1 *Frequency arrangement of Plan 1A*** + +Plan 1A uses the first modulation procedure described in Recommendation G.211. + +The telephone channels should first be assembled into basic supermastergroups. Three supermastergroups are transmitted to line in accordance with the frequency arrangement of Figure 1/G.332. + +In this figure the virtual carrier frequencies of the two lower supermastergroups are shown. + +### **1.2 *Frequency arrangement of Plan 1B*** + +#### *Frequencies below 4287 kHz* + +For frequencies below 4287 kHz, Plan 1B uses the second modulation procedure described in Recommendation G.211. + +The telephone channels should first be assembled into supergroups. Fifteen supergroups are transmitted to line in accordance with the frequency arrangement of Figure 2/G.332 (frequencies below 4287 kHz). These fifteen supergroups comprise the basic 15-supergroup assembly (No. 1) described in Recommendation G.233; the carrier frequencies are shown in that Recommendation. Figure 3/G.332 gives further details of the frequency arrangement below 4287 kHz. + +#### *Frequencies above 4287 kHz* + +For frequencies above 4287 kHz, Plan 1B, uses the first modulation procedure described in Recommendation G.211. + +For frequencies above 4287 kHz, the frequency arrangement of Figure 2/G.332 is identical with that of Figure 1/G.332. + +![Diagram of basic supermastergroup frequency arrangement. It shows the hierarchy from Supermastergroup No. 1 to 9, Mastergroup No. 1 to 9, and Supergroup No. 1 to 8. The frequency scale ranges from 312 kHz to 12 388 kHz. Formulas for virtual carrier frequencies are given: (440 x 30 - 124 x 4) for the 12 704 kHz carrier and (440 x 38) for the 16 720 kHz carrier. CCITT - 45582 is noted at the bottom right.](5d92d5c9cc01a262b0389d138caa9aea_img.jpg) + +Diagram of basic supermastergroup frequency arrangement. It shows the hierarchy from Supermastergroup No. 1 to 9, Mastergroup No. 1 to 9, and Supergroup No. 1 to 8. The frequency scale ranges from 312 kHz to 12 388 kHz. Formulas for virtual carrier frequencies are given: (440 x 30 - 124 x 4) for the 12 704 kHz carrier and (440 x 38) for the 16 720 kHz carrier. CCITT - 45582 is noted at the bottom right. + +FIGURE 1/G.332 + +#### Plan 1A frequency arrangement for 12 MHz systems + +![Diagram of Plan 1A frequency arrangement for 12 MHz systems. It shows Supermastergroup No. 1 to 3, Mastergroup No. 1 to 9, and Supergroup No. 1 to 16. The frequency scale ranges from 312 kHz to 12 388 kHz. CCITT - 45571 is noted at the bottom right.](f961cbef0f8217e216b553bed270315b_img.jpg) + +Diagram of Plan 1A frequency arrangement for 12 MHz systems. It shows Supermastergroup No. 1 to 3, Mastergroup No. 1 to 9, and Supergroup No. 1 to 16. The frequency scale ranges from 312 kHz to 12 388 kHz. CCITT - 45571 is noted at the bottom right. + +FIGURE 2/G.332 + +#### Plan 1B frequency arrangement for 12 MHz system + +![Diagram of Plan 1B frequency arrangement for 12 MHz systems, focusing on frequencies below 4287 kHz. It shows Supergroup No. 1 to 16 with specific frequency values for each group. CCITT - 45581 is noted at the bottom right.](954ff3c220707f98bcb2c4b197bd7d9f_img.jpg) + +Diagram of Plan 1B frequency arrangement for 12 MHz systems, focusing on frequencies below 4287 kHz. It shows Supergroup No. 1 to 16 with specific frequency values for each group. CCITT - 45581 is noted at the bottom right. + +FIGURE 3/G.332 + +#### Plan 1B frequency arrangement for 12 MHz systems: frequencies below 4287 kHz + +### 1.3 Frequency arrangement of Plan 2 + +This plan uses the second modulation procedure described in Recommendation G.211. + +The telephone channels should be assembled into basic (No. 1) 15-supergroup assemblies. Three 15-supergroup assemblies are transmitted to line in accordance with the frequency arrangement shown in Figure 4/G.332. In this figure, the virtual carrier frequencies of 15-supergroup assemblies Nos. 2 and 3 are shown. + +## 2 Pilots and additional measuring frequencies + +### 2.1 Line-regulating pilots + +The CCITT recommends that 12 435 kHz be used for the main line-regulating pilot. + +In any regulated-line section crossing a frontier, it is recommended that in both directions of transmission the Administration on the sending side should permanently transmit one or two auxiliary line-regulating pilots at 308 and/or 4287 kHz, at the choice and request of the Administration on the receiving side so as to provide for additional regulation, for example. + +The frequency accuracy recommended for the pilots is $\pm 1 \times 10^{-5}$ . + +The power level of the main and auxiliary line-regulating pilots should be adjusted at the point of injection to have a value of -10 dBm0. The harmonics of the 308 and 4287 kHz pilot should each have a level not higher than -70 dBm0. + +Equipment should be designed in such a way that these pilots may be blocked at the end of a regulated-line section, so that their level shall be at least 40 dB below that of the pilots used on other sections. + +![Figure 4/G.332: Plan 2 frequency arrangement for 12 MHz systems. The diagram shows three 15-supergroup assemblies (1, 2, and 3) plotted against frequency in kHz. Assembly 1 is on the left, starting at 312 kHz. Assembly 2 is in the middle, starting at 4404 kHz. Assembly 3 is on the right, starting at 8620 kHz. Each assembly contains 15 subgroups, numbered 1 to 15. Various pilot and measuring frequencies are marked: 308 kHz (auxiliary pilot), 1552 kHz (measuring), 4287 kHz (auxiliary pilot), 6980 kHz (measuring), 8432 kHz (main pilot, labeled as 124 x 68), 8620 kHz (start of assembly 3), 11096 kHz (measuring), and 12435 kHz (main pilot, labeled as 124 x 102). Virtual carrier frequencies are indicated by dashed lines. The bottom axis shows subgroup numbers 1-15 for each assembly. The CCITT reference number 45592 is at the bottom right.](1a6d75c94d3fd49936527eadd25e9278_img.jpg) + +Figure 4/G.332: Plan 2 frequency arrangement for 12 MHz systems. The diagram shows three 15-supergroup assemblies (1, 2, and 3) plotted against frequency in kHz. Assembly 1 is on the left, starting at 312 kHz. Assembly 2 is in the middle, starting at 4404 kHz. Assembly 3 is on the right, starting at 8620 kHz. Each assembly contains 15 subgroups, numbered 1 to 15. Various pilot and measuring frequencies are marked: 308 kHz (auxiliary pilot), 1552 kHz (measuring), 4287 kHz (auxiliary pilot), 6980 kHz (measuring), 8432 kHz (main pilot, labeled as 124 x 68), 8620 kHz (start of assembly 3), 11096 kHz (measuring), and 12435 kHz (main pilot, labeled as 124 x 102). Virtual carrier frequencies are indicated by dashed lines. The bottom axis shows subgroup numbers 1-15 for each assembly. The CCITT reference number 45592 is at the bottom right. + +FIGURE 4/G.332 + +Plan 2 frequency arrangement for 12 MHz systems + +The following tolerances for the level of these pilots are recommended: + +- 1) The design of equipment should be such as to allow the error in the level of any pilot as transmitted, due to finite level adjustment steps, to be kept within $\pm 0.1$ dB. +- 2) The change in output level of the pilot generator with time (which is a factor included in equipment specifications) must not exceed $\pm 0.3$ dB during the interval between two maintenance adjustments, e.g. in one month. +- 3) To reduce pilot level variations with time, it is advisable to have a device to give an alarm when the variation at the generator output exceeds $\pm 0.5$ dB, the zero of the warning device being aligned as accurately as possible with the lining-up level of the transmitted pilot. + +The attention of Administrations is drawn to the difficulty which could result from an appreciable reduction in the absolute power level of the pilot sent to line; such a reduction is liable to cause "near singing", resulting from the operation of the automatic gain-control amplifiers. It would be desirable to make arrangements for overcoming this difficulty if it should arise. + +*Note* - When pre-emphasis and de-emphasis is applied on the line link, it is necessary to define the line pilot level with reference to a point, possibly hypothetical, at the input to or output from the line, at which the relative levels of all telephone channels are equal over the whole of the line-frequency band. When a part of the line-frequency band is to be used to provide a television channel, different pre-emphasis and de-emphasis networks may be required but this will not affect the definition of line pilot levels. Figures 5/G.332 and 6/G.332 show two hypothetical arrangements for the purpose of this definition. + +### 2.2 Frequency comparison pilots + +Administrations wishing to make an international frequency comparison shall choose the frequency 300, 808 or 1552 kHz for this purpose, when it is impossible to use 308 or 1800 kHz. International comparison of national standards is relatively rare. During a specified period of time, it will always be possible to use for such comparisons one of the frequencies mentioned above, even though it may normally be used as an additional measuring frequency. + +![Diagram illustrating the definition of line-regulating pilot levels on a line suitable for carrying both telephony and television. The diagram shows a transmission line between two points, A and B. At point A, telephony modulating equipment and television pre-emphasis are connected. A pilot signal is injected into the line. At point A', television modulating equipment is connected. At point B, the line connects to telephony demodulating equipment and television de-emphasis. A pilot signal is also shown at point B. The line itself is labeled 'Line terminals including pilot injection and pre-emphasis or de-emphasis networks for telephony'. The diagram also indicates 'Zero relative level' and 'n relative level' at point A, and 'm relative level' at point B.](1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg) + +Diagram illustrating the definition of line-regulating pilot levels on a line suitable for carrying both telephony and television. The diagram shows a transmission line between two points, A and B. At point A, telephony modulating equipment and television pre-emphasis are connected. A pilot signal is injected into the line. At point A', television modulating equipment is connected. At point B, the line connects to telephony demodulating equipment and television de-emphasis. A pilot signal is also shown at point B. The line itself is labeled 'Line terminals including pilot injection and pre-emphasis or de-emphasis networks for telephony'. The diagram also indicates 'Zero relative level' and 'n relative level' at point A, and 'm relative level' at point B. + +CCITT - 45600 + +*Note* - Between points A and B, the gain/frequency response of the high-frequency line is uniform for telephony. At these points, all telephone channels are at equal relative level. Between points A' and B', the gain/frequency response of the high-frequency line is uniform for television. + +FIGURE 5/G.332 + +**To illustrate the definition of line-regulating pilot levels on a line suitable for carrying both telephony and television** + +![Diagram of high-frequency line equipment for a 12-MHz 'mixed' system. The diagram shows two parallel transmission paths. The top path is for the telephony band, starting from 'From telephony multiplex equipment, or through-connection of telephony band' at point A, passing through 'Pre-emphasis', 'Phase equalizer', and a repeater. The bottom path is for the television band, starting from 'From television modulating equipment, or through-connection of television band' at point B, passing through 'De-emphasis', 'Phase equalizer', and a repeater. Both paths are labeled 'High-frequency line equipment' and 'CCITT - 48810'. A bracket on the right side of the repeaters is labeled 'Repeated line'.](fc46871d72c65d3381d9201646d23439_img.jpg) + +Diagram of high-frequency line equipment for a 12-MHz 'mixed' system. The diagram shows two parallel transmission paths. The top path is for the telephony band, starting from 'From telephony multiplex equipment, or through-connection of telephony band' at point A, passing through 'Pre-emphasis', 'Phase equalizer', and a repeater. The bottom path is for the television band, starting from 'From television modulating equipment, or through-connection of television band' at point B, passing through 'De-emphasis', 'Phase equalizer', and a repeater. Both paths are labeled 'High-frequency line equipment' and 'CCITT - 48810'. A bracket on the right side of the repeaters is labeled 'Repeated line'. + +FIGURE 6/G.332 + +**An example of high-frequency line equipment for a 12-MHz "mixed" system for simultaneous telephony and television transmission. The relative levels for telephony would be defined for the points A and B** + +A frequency of 300 kHz can be used for national comparisons when Administrations do not wish to use the 308 kHz pilot for this purpose. In this case, it is recommended that the 300 kHz be transmitted at a power level of -10 dBm0. The harmonics of the frequency comparison pilots should each have a level not higher than -70 dBm0. + +### 2.3 Additional measuring frequencies + +If the frequency allocation without mastergroups is used at frequencies below 4 MHz (Figures 3/G.332 and 4/G.332), the following frequencies *may* be used for additional measuring frequencies: + +560, 808, 1056, 1304, 1552, 1800, 2048, 2296, + +2544, 2792, 3040, 3288, 3536 and 3784 kHz. + +Any Administration using 12-MHz working on a line crossing a frontier should, at the request of any other Administration concerned, transmit or measure the measuring frequencies appearing in the following preferred list: + +560, 808, 1304, 1800, 2296, 2792 and 3536 kHz. + +Administrations should likewise transmit or measure, at the request of corresponding Administrations, any measuring frequency which may be used in other circumstances, namely: + +- at frequencies below 4 MHz, if frequency allocation with mastergroups indicated in Plan 1A (Figure 1/G.332) is used: + +560, 808, 1304, 1592 and 2912 kHz; + +- at frequencies above 4 MHz, if Plan 1A (Figure 1/G.332) or 1B (Figure 2/G.332) is used: + +5608, 6928, 82481), 8472, 9792 and 11 112 kHz. + +1) A frequency of 8248 kHz can be used as a radio-relay link line-regulating pilot. In such a case, the precautions shown in Recommendation G.423 should be applied. + +Plan 2 (Figure 4/G.332) is used under the conditions described in Recommendation G.211 for the application of the second modulation process, the additional frequencies above 4 MHz are: + +5392, 7128, 8248, 8472, 8864, 9608 and 11 344 kHz. + +All these frequencies are recapitulated in Table 1/G.332. + +TABLE 1/G.332 + +#### **Frequencies that are available for use as additional measuring frequencies on 12 MHz systems** + +| Frequency band | Frequency arrangement | Additional measuring frequency to be sent or measured on request | Other additional measuring frequencies which can be sent | +|----------------|-----------------------------------------------|------------------------------------------------------------------|----------------------------------------------------------| +| < 4 MHz | in supergroups (Figures 3/G.332 and 4/G.332) | 560, 808, 1034, 1800, 2296, 2792 and 3536 kHz | 1056, 1552, 2048, 2544, 3040, 3288 and 3784 kHz | +| | all mastergroups (Figures 1/G.332) | 560, 808, 1304, 1592 and 2912 kHz | | +| > 4 MHz | in mastergroups (Figures 1/G.332 and 2/G.332) | 5608, 6928, 8248 a) , 8472, 9792 and 11 112 kHz | | +| | in 15-supergroup assemblies (Figure 4/G.332) | 5392, 7128, 8248, 8472, 8864, 9608 and 11 344 kHz | | + +a) A frequency of 8248 kHz can be used as a radio-relay link line-regulating pilot. In such a case, the precautions shown in Recommendation G.423 should be applied. + +The absolute frequency variation of additional measuring frequencies below 4 MHz should never be outside limits of $\pm 40$ Hz from their nominal value. For frequencies above 4 MHz, the relative frequency variation referred to the nominal value should never exceed $\pm 1 \times 10^{-5}$ . + +The power level2) of the additional measuring frequencies should be adjusted at the point of injection to have a value of -10 dBm0. The harmonics of additional measuring frequencies below 6 MHz should each have a level at this point not higher than -70 dBm0. + +The additional measuring frequencies should not be permanently transmitted. They will only be transmitted for as long as is necessary for actual measurement purposes. + +Arrangements should be made in equipment for the 12-MHz system, so that the 308-kHz line-regulating pilot is protected from disturbances from a pilot or additional measuring frequency of the same frequency coming from a 4-MHz system when this protection is not already provided by the equipment of the 4-MHz system. + +*Note* - Some Administrations use new manual or automatic methods of equalizing attenuation distortion, e.g. equalizers based on the Cosine function, using frequencies which do not appear in the list of additional measuring frequencies recommended by the CCITT. + +Obviously, no additional measuring frequency which might leave the national network should be sent at the same frequency as one of the pilots recommended by the CCITT. + +## 3 Hypothetical reference circuit + +This hypothetical reference circuit is 2500 km long and is divided into nine sections of 280 km each. The three line frequency arrangement plans recommended in § 1 require modulation stages of different number to carry a voice signal in the line frequency position. This is bound to affect the constitution of the hypothetical reference circuit. In these circumstances, the CCITT recommends the hypothetical reference circuits represented in Figures 7/G.332 and 8/G.332. + +### 3.1 *Hypothetical reference circuit for the Plans 1A and 1B frequency allocations3)* + +This is shown in Figure 7/G.332. It has, for each direction of transmission, a total of: + +- two pairs of channel modulators, each pair including translation from the audio-frequency band to the basic group and vice versa; +- three pairs of group modulators, each pair including translation from the basic group to the basic supergroup and vice versa; +- five pairs of supergroup modulators, each pair including translation from the basic supergroup to the the basic mastergroup and vice versa; +- seven pairs of mastergroup modulators, each pair including translation from the basic mastergroup to the basic supermastergroup and vice versa; +- nine pairs of mastergroup modulators, each pair including translation from the basic mastergroup to the frequency band transmitted on the coaxial cable and vice versa. + +--- + +2) The Note of § 2.1 still applies. + +3) In the case of plan 1B, this hypothetical reference circuit is not valid for the frequency band 312-4028 kHz. + +![Diagram of a hypothetical reference circuit for 12 MHz systems (Plans 1A and 1B). The diagram shows a sequence of 10 stages, numbered 1 to 10, connected by lines. Each stage contains a different number of rectangular blocks representing transmitters (Tr). Stage 1 has 4 blocks, stage 2 has 2, stage 3 has 4, stage 4 has 6, stage 5 has 8, stage 6 has 10, stage 7 has 6, stage 8 has 4, stage 9 has 2, and stage 10 has 4. Below the stages is a legend with five types of transmitters: Channel Tr (1 block), Group Tr (2 blocks), Supergroup Tr (4 blocks), Mastergroup Tr (6 blocks), and Supermastergroup Tr (8 blocks). The text 'CCITT - 24510' is in the bottom right corner.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Diagram of a hypothetical reference circuit for 12 MHz systems (Plans 1A and 1B). The diagram shows a sequence of 10 stages, numbered 1 to 10, connected by lines. Each stage contains a different number of rectangular blocks representing transmitters (Tr). Stage 1 has 4 blocks, stage 2 has 2, stage 3 has 4, stage 4 has 6, stage 5 has 8, stage 6 has 10, stage 7 has 6, stage 8 has 4, stage 9 has 2, and stage 10 has 4. Below the stages is a legend with five types of transmitters: Channel Tr (1 block), Group Tr (2 blocks), Supergroup Tr (4 blocks), Mastergroup Tr (6 blocks), and Supermastergroup Tr (8 blocks). The text 'CCITT - 24510' is in the bottom right corner. + +FIGURE 7/G.332 + +#### **Diagram of a hypothetical reference circuit for 12 MHz systems (Plans 1A and 1B)** + +### 3.2 *Hypothetical reference circuit for the Plan 2 frequency allocation* + +This is shown in Figure 8/G.332. It has, for each direction of transmission, a total of: + +- two pairs of channel modulators, each pair including translation from the audio-frequency band to the basic group and vice versa; +- three pairs of group modulators, each pair including translation from the basic group to the basic supergroup and vice versa; +- six pairs of supergroup modulators, each pair including translation from the basic supergroup to the basic 15-supergroup assembly and vice versa; +- nine pairs of 15-supergroup modulators, each pair including translation from the basic 15-supergroup assembly to the frequency band transmitted on the coaxial cable and vice versa. + +![Diagram of a hypothetical reference circuit for 12 MHz systems (Plan 2). The diagram shows a sequence of 10 stages, numbered 1 to 10, connected by lines. Each stage contains a different number of rectangular blocks representing transmitters (Tr). Stage 1 has 4 blocks, stage 2 has 2, stage 3 has 2, stage 4 has 4, stage 5 has 6, stage 6 has 8, stage 7 has 6, stage 8 has 4, stage 9 has 2, and stage 10 has 4. Below the stages is a legend with four types of transmitters: Channel Tr (1 block), Group Tr (2 blocks), Supergroup Tr (4 blocks), and 15 supergroup Tr (6 blocks). The text 'CCITT - 24520' is in the bottom right corner.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +Diagram of a hypothetical reference circuit for 12 MHz systems (Plan 2). The diagram shows a sequence of 10 stages, numbered 1 to 10, connected by lines. Each stage contains a different number of rectangular blocks representing transmitters (Tr). Stage 1 has 4 blocks, stage 2 has 2, stage 3 has 2, stage 4 has 4, stage 5 has 6, stage 6 has 8, stage 7 has 6, stage 8 has 4, stage 9 has 2, and stage 10 has 4. Below the stages is a legend with four types of transmitters: Channel Tr (1 block), Group Tr (2 blocks), Supergroup Tr (4 blocks), and 15 supergroup Tr (6 blocks). The text 'CCITT - 24520' is in the bottom right corner. + +FIGURE 8/G.332 + +#### **Diagram of a hypothetical reference circuit for 12 MHz systems (Plan 2)** + +## **4 Design objectives for circuit noise** + +The objectives given in Recommendation G.222 are applicable to the hypothetical reference circuit for 12-MHz systems on coaxial cable, in the circumstances indicated in Recommendation G.223. + +In practice, it is sufficient to check for each telephone channel as defined by the hypothetical reference circuit, that the mean psophometric power at the end of the channel referred to a zero relative level point does not exceed 10 000 pW0p during any period of one hour. + +The subdivision of the total noise between basic noise and intermodulation noise is left entirely to the designer of the system, within the limits of 2500 pW0p for the terminal equipment and 7500 pW0p for the line. + +## 5 Matching of the impedance of a coaxial pair and the impedances of the repeaters + +- $Z_L$ is the characteristic impedance of the line (for any frequency $f$ effectively transmitted), this impedance being the ordinate for the frequency $f$ of a smooth curve, agreed by the Administrations concerned as being representative of the average impedance/frequency characteristic of the type of coaxial cable concerned; +- $Z_R$ is the worst value of the input impedance (for the frequency $f$ ) of the equipment of a repeater station, as seen from the line (see Figure 9/G.332); +- $Z_E$ is the worst value of the output impedance (for the frequency $f$ ) of the equipment of a repeater station, as seen from the line; +- $A = al$ the total image attenuation (at the frequency $f$ ) of the line between two adjacent repeater stations, $a$ being the average attenuation of the coaxial cable per unit length and $l$ the average length between two adjacent repeater stations. + +![Diagram of an elementary coaxial cable section between two repeater stations. The diagram shows two repeater units, each represented by a square box with a triangle symbol. A horizontal line representing the coaxial cable connects them. Above the left repeater, an arrow labeled Z_E points left (output impedance) and an arrow labeled Z_L points right (characteristic impedance). Above the right repeater, an arrow labeled Z_L points left (characteristic impedance) and an arrow labeled Z_R points right (input impedance). A double-headed arrow below the cable between the repeaters is labeled l, representing the length. The text 'CCITT - 39110' is in the bottom right corner.](e9314c83043183351ed74908e9bf2f90_img.jpg) + +Diagram of an elementary coaxial cable section between two repeater stations. The diagram shows two repeater units, each represented by a square box with a triangle symbol. A horizontal line representing the coaxial cable connects them. Above the left repeater, an arrow labeled Z\_E points left (output impedance) and an arrow labeled Z\_L points right (characteristic impedance). Above the right repeater, an arrow labeled Z\_L points left (characteristic impedance) and an arrow labeled Z\_R points right (input impedance). A double-headed arrow below the cable between the repeaters is labeled l, representing the length. The text 'CCITT - 39110' is in the bottom right corner. + +FIGURE 9/G.332 + +### Elementary coaxial cable section + +Then the factor $N$ is defined by the formula: + +$$N = 2A + 20 \log_{10} \left| \frac{Z_E + Z_L}{Z_E - Z_L} \right| + 20 \log_{10} \left| \frac{Z_L + Z_R}{Z_L - Z_R} \right| \quad (\text{dB})$$ + +The present Recommendation refers only to 12-MHz systems on 2.6/9.5-mm coaxial pairs having repeaters with a nominal spacing of about 4.5 km. + +The sum $N$ of the three terms defined above must in this case be equal to at least 48 dB at 300 kHz and to at least 55 dB at all frequencies above 800 kHz. Between 300 and 800 kHz the permissible limit in decibels varies linearly with the frequency. + +*Note* - The CCITT has defined the permissible limits for $N$ , as a sum of the three terms (see the above formula). It is recommended that Administrations concerned with a coaxial cable section crossing a frontier should agree on permissible values in this particular case for each of these three terms to meet the above condition, that is to say, agree on the use of as good a match as possible or of a methodical mismatch at the ends of the repeater section. + +## 6 Relative levels and interconnection in a frontier section + +### 6.1 Interconnection in a frontier section + +In an elementary cable section which crosses a frontier, the relative level at the input of the cable section (output of the repeater equipment) should be equal to -13 dBr at 12 435 kHz. + +*Note 1* - This recommendation is based on the assumption that the attenuation in the frontier section is approximately 37 to 38 dB. This should be taken into consideration in determining the actual length of the frontier section. + +*Note 2* - When the pre-emphasis curves of the two systems are different, Recommendation G.352 should be applied. + +### 6.2 *Relative levels in any elementary cable section* + +It has not been possible to standardize a single value. + +### 6.3 *Pre-emphasis* + +From the information supplied by various Administrations, the pre-emphasis generally lies between 9 and 12 dB. + +## 7 **Power-feeding and alarm systems** + +### 7.1 *Power feeding across a frontier* + +### 7.2 *Power-feeding systems* + +The text of Recommendation G.341, §§ 7.1 and 7.2, applicable to all 1.2/4.4-mm pair systems, still applies for 12-MHz transistor systems on 2.6/9.5-mm pairs. + +### 7.3 *Supervision and alarms in a frontier section (see Annex A)* + +## 8 **Use of 12 MHz systems for television transmission** + +### 8.1 *General* + +This § summarizes all the additional conditions recommended for the transmission of television on a 12 MHz system. The characteristics of the television signal are discussed in Recommendation J.73 [1]. + +### 8.2 *Circuit noise* + +When a 12 MHz system is used for a television transmission on the basis of a hypothetical reference circuit 2500 km in length, the mean value of the thermal line noise should not exceed 1 pW0p/km. Experience has shown that a mean value of 1.5 pW0p/km for the total line noise is sufficient when the noise is measured in normal telephony conditions. + +### 8.3 *Matching of repeater and line impedance* + +For the transmission of a television programme, it is recommended that number *N* defined in § 5 of the present Recommendation should be at least 70 dB in the band occupied by the television signal. + +### 8.4 *Arrangement of frequencies transmitted in line* + +The 12 MHz system provides a television channel and 1200 telephone channels. Figure 10/G.332 shows the frequency arrangement recommended for television transmission. The television channel is capable of transmitting the signals of all television systems defined by the CCIR with a video bandwidth not exceeding 5.5 MHz. + +![Three frequency spectrum diagrams (Plan 1A, Plan 1B, Plan 2) showing line frequency arrangements for a television signal at 5.5 MHz on a 12 MHz system. Each plan shows the placement of supergroups and mastergroups within the 312 kHz to 12435 kHz band, with constraints on total bandwidth (B ≤ 5,500 MHz) and guard band (r ≤ 0,500 MHz).](dd0f5301a5a6dd7c319701302110de88_img.jpg) + +The figure displays three frequency spectrum plans for a television signal at 5.5 MHz on a 12 MHz system. All plans share a common horizontal axis representing frequency in kHz, ranging from 312 to 12435. + +- Plan 1A:** Shows a 'Supermaster-group No. 1' from 316 kHz to 4188 kHz, and a 'Mastergroup No. 4' from 4332 kHz to 5564 kHz. A guard band 'r' is indicated between 5564 kHz and 6799 kHz. A signal block is shown from 6799 kHz to 12435 kHz, with a total bandwidth constraint $B \leq 5,500 \text{ MHz}$ . +- Plan 1B:** Shows an 'Assembly of 15 supergroups No. 1' from 312 kHz to 4028 kHz, and a 'Mastergroup No. 4' from 4332 kHz to 5564 kHz. A guard band 'r' is indicated between 5564 kHz and 6799 kHz. A signal block is shown from 6799 kHz to 12435 kHz, with a total bandwidth constraint $B \leq 5,500 \text{ MHz}$ . +- Plan 2:** Shows an 'Assembly of 15 supergroups No. 1' from 312 kHz to 4028 kHz, followed by a 'Supergroup No.' (labeled 16, 12) from 4404 kHz to 5636 kHz. A guard band 'r' is indicated between 5636 kHz and 6799 kHz. A signal block is shown from 6799 kHz to 12435 kHz, with a total bandwidth constraint $B \leq 5,500 \text{ MHz}$ . + +Common constraints across all plans include a guard band $r \leq 0,500 \text{ MHz}$ and a total bandwidth $B \leq 5,500 \text{ MHz}$ . The diagram is labeled CCITT - 47 091. + +Three frequency spectrum diagrams (Plan 1A, Plan 1B, Plan 2) showing line frequency arrangements for a television signal at 5.5 MHz on a 12 MHz system. Each plan shows the placement of supergroups and mastergroups within the 312 kHz to 12435 kHz band, with constraints on total bandwidth (B ≤ 5,500 MHz) and guard band (r ≤ 0,500 MHz). + +FIGURE 10/G.332 + +Plan of line frequency arrangement for the transmission of a television signal at 5.5 MHz on a 12 MHz system + +## ANNEX A + +(to Recommendation G.332) + +### Frequencies used for supervision or fault location + +The frequencies or frequency bands used in various countries for supervising or for locating faults are given in Table A-1/G.332 for information. + +TABLE A-1/G.332 + +| Country | Band (kHz) | +|-----------------|------------------------------------------| +| Belgium | 280 and 12 700 and 170 to 210 regulation | +| Japan | 13 000 to 13 180 | +| France | 12 700 to 12 800 | +| Netherlands | 280 and 170 to 210 for regulation | +| F.R. of Germany | 269 and $(13\ 300 \pm 75)$ | +| United Kingdom | $13\ 500 + 12,5$ | +| Sweden | 12 700 to 13 000 | + +*Note* - A fault-tracing system was used by the Chile Telephone Company using direct currents transmitted over interstitial pairs of the cable, which obviates any risk of interference with the systems mentioned above. + +## Reference + +- [1] CCITT Recommendation *Use of a 12-MHz system for the simultaneous transmission of telephony and television*, Vol. III, Rec. J.73. \ No newline at end of file diff --git a/marked/G/T-REC-G.343-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.343-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6b034e9cde9edcff0020bb05698c6d01d41eaad3 --- /dev/null +++ b/marked/G/T-REC-G.343-198811-I_PDF-E/raw.md @@ -0,0 +1,181 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt and the letters 'ITU'. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**G.343** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **INTERNATIONAL ANALOGUE CARRIER SYSTEMS INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES** + +--- + +**4 MHz SYSTEMS ON STANDARDIZED +1.2/4.4 mm COAXIAL CABLE PAIRS** + +**ITU-T Recommendation G.343** + +(Extract from the *Blue Book*) + +--- + +### NOTES + +- 1 ITU-T Recommendation G.343 was published in Fascicle III.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +### Recommendation G.343 + +### 4 MHz SYSTEMS ON STANDARDIZED 1.2/4.4 mm COAXIAL CABLE PAIRS + +(Geneva, 1964; further amended) + +### Preliminary note + +The present Recommendation describes a system designed to carry a maximum of 960 carrier telephone channels on a 1.2/4.4 mm coaxial pair (see Recommendation G.622). + +A system of this kind is produced by halving the length of the repeater section of a 1.3 MHz system (as described in Recommendation G.341) if this length is 8 km, corresponding to a nominal repeater spacing of 4 km for a 4 MHz system. + +### 1 Line frequencies + +The CCITT recommends the two plans in Figure 1/G.343. Plan 1 shows the supergroup allocations and Plan 2 the mastergroup allocations. + +It may be desirable to make provision for the through-connection of entire mastergroups or a supermastergroup to this system. This can be effected in accordance with the frequency arrangement of Plan 2 in Figure 1/G.343. + +Plan 2 uses the three lowest mastergroups in the 12 MHz system on a 2.6/9.5 mm coaxial pair. It permits, in particular, direct interconnection with a 12 MHz coaxial system using the Plan 1A frequency allocation shown in Figure 1/G.332 and with a radio-relay link of 900 or 1800 channels operated according to Recommendation G.423 (Figures 4/G.423 and 8/G.423). + +### 2 Pilots and additional measuring frequencies + +#### 2.1 Line-regulating pilots + +The frequencies recommended for the various cases indicated in § 1 above and shown in Figure 1/G.343 are as follows: + +*Plan 1* - The CCITT recommends the use of the following frequencies: + +- i) 60 kHz or 308 kHz for the lower line-regulating pilot; +- ii) 4092 kHz or 4287 kHz for the upper line-regulating pilot. + +However, each Administration, when so requested by another Administration, should permanently send a line-regulating pilot at 4287 kHz. + +*Plan 2* - The line-regulating pilots recommended in Recommendation G.332 for the 12 MHz system in the same frequency band. + +In every instance, the recommended stability is $\pm 1 \times 10^{-5}$ , the power level recommended is -10 dBm0, while the tolerances at this level are the same as in Recommendation G.332, § 2.1. The harmonics of the 60 and 308 kHz pilot should each have a level not higher than -70 dBm0. + +![Figure 1-C.043: Allocation of line frequencies in international 4 MHz carrier system on 1.2-4.4 mm coaxial pairs. The figure contains two sub-diagrams: (a) Supergroup allocation and (b) Mastergroup allocation. Both show frequency ranges in kHz on the x-axis and signal levels in dB on the y-axis. Diagram (a) shows 16 supergroups with frequencies ranging from 60 kHz to 4028 kHz. Diagram (b) shows 4 mastergroups with frequencies ranging from 60 kHz to 4028 kHz.](e94f3bbb6f7501b9a1344dd0210e5dd8_img.jpg) + +Figure 1-C.043 consists of two sub-diagrams, (a) and (b), illustrating the allocation of line frequencies in an international 4 MHz carrier system on 1.2-4.4 mm coaxial pairs. Both diagrams show frequency ranges in kHz on the x-axis and signal levels in dB on the y-axis. + +Diagram (a) is titled "Supergroup allocation" and shows 16 supergroups. The x-axis ranges from 60 kHz to 4028 kHz. The y-axis ranges from -10 dB to 70 dB. The diagram shows a sawtooth pattern of signal levels across the frequency range, with peaks at approximately 312, 504, 696, 888, 1080, 1272, 1464, 1656, 1848, 2040, 2232, 2424, 2616, 2808, 3000, 3192, 3384, 3576, 3768, 3960, and 4028 kHz. + +Diagram (b) is titled "Mastergroup allocation" and shows 4 mastergroups. The x-axis ranges from 60 kHz to 4028 kHz. The y-axis ranges from -10 dB to 70 dB. The diagram shows a sawtooth pattern of signal levels across the frequency range, with peaks at approximately 312, 1008, 1692, 2388, 3084, 3780, and 4028 kHz. + +Figure 1-C.043: Allocation of line frequencies in international 4 MHz carrier system on 1.2-4.4 mm coaxial pairs. The figure contains two sub-diagrams: (a) Supergroup allocation and (b) Mastergroup allocation. Both show frequency ranges in kHz on the x-axis and signal levels in dB on the y-axis. Diagram (a) shows 16 supergroups with frequencies ranging from 60 kHz to 4028 kHz. Diagram (b) shows 4 mastergroups with frequencies ranging from 60 kHz to 4028 kHz. + +FIGURE 1-C.043 +Allocation of line frequencies in international 4 MHz carrier system on 1.2-4.4 mm coaxial pairs + +#### 2.2 Frequency comparison pilots + +*Plan 1* - For a national routine frequency check as described in Recommendation G.225, a frequency of either 60 kHz or 308 kHz may be used for the frequency-comparison pilot. + +The power level of a frequency-comparison pilot should be adjusted at the output of the transmit amplifier, to a nominal value of -10 dBm0. The harmonics of the frequency-comparison pilots should each have a level not higher than -70 dBm0. + +The frequency 1800 kHz is provisionally reserved for international frequency comparisons, as required. However, if the Administrations concerned so desire, this frequency 1800 kHz may be used for the frequency-comparison pilot. + +Administrations concerned with an international carrier system on coaxial cable may agree to use (if they consider it desirable) one of the lower line-regulating pilots (either 60 or 308 kHz) for level control as well as for frequency checking. + +In any case, it is desirable that one of the following two solutions should always be applied, so as to allow the line-regulating pilots to be used at the same time for frequency checking: + +- provide, in each regulated-line section, a master oscillator which is regularly compared, directly or indirectly, with a national frequency standard; +- if there is no master oscillator in a regulated-line section, then beyond the junction between the two regulated-line sections considered, reintroduce the lower line-regulating pilot coming from the previous section, after its level has been stabilized. + +Generally speaking, it is possible for one pilot to have two or more functions if the Administrations concerned so decide. + +*Plan 2* - The same recommendation as for the 12-MHz system (Recommendation G.332, § 2.2). + +#### 2.3 *Additional measuring frequencies* + +*Plan 1* - Frequencies that may be used are the following: + +60, 308, 556, 808, 1056, 1304, 1552, 1800, 2048, +2296, 2544, 2792, 3040, 3288, 3536 and 3784 kHz. + +The recommended accuracy for the frequency of these signals is $\pm 40$ Hz. The power level of these additional measuring frequencies should be adjusted at the output of the transmit amplifier to have a nominal value of -10 dBm0. + +The harmonics of the additional measuring frequencies below 2.1 MHz should each have a level at this point not higher than -70 dBm0. + +*Plan 2* - The additional measuring frequencies recommended for the 12-MHz system in the same frequency band should be used (Recommendation G.332). + +### 3 **Hypothetical reference circuits** + +The hypothetical reference circuit depends on the line frequency arrangement. + +With the supergroup arrangement, the first hypothetical reference circuit for the 1.3 MHz system, described in Recommendation G.341, § 3.1, is to be used. + +With the mastergroup arrangement, the circuit to be used is: + +- either the second hypothetical reference circuit for the 1.3 MHz system, described in Recommendation G.341, § 3.2, +- or the first hypothetical reference circuit for the 12 MHz system, described in Recommendation G.332, § 3.1. + +### 4 **Noise** + +Recommendation G.341, § 4 applies. + +### 5 **Matching of the coaxial-pair impedance and repeater impedances** + +For an elementary cable section above 4 km in length the sum $N$ of the three terms defined in Recommendation G.332, § 5 must be at least equal to the following: + +- 50 dB at 60 kHz, +- 57 dB above 300 kHz, + +with linear variation from 50 dB to 57 dB in the 60-300 kHz band, in the case of a linear frequency scale. + +*Note* - These values are based on the assumption that the attenuation/frequency characteristic does not show any ripple exceeding $\pm 1$ dNp (about $\pm 1$ dB) at the end of a homogeneous section 280 km long. A relaxed condition was applied at 60 kHz, as it may be difficult at low frequencies to obtain a reflection coefficient for the repeater input and output impedances which is sufficiently small in relation to the impedance of the cable. + +### 6 Relative levels and interconnection + +#### 6.1 *Relative level at amplifier output* + +- at 4028 kHz: - 9 dBr, or +- at 4287 kHz: - 8.5 dBr. + +#### 6.2 *Pre-emphasis characteristic* + +This is defined by the formula: + +$$A = 10 \log_{10} \left[ 1 + \frac{a}{1 + \frac{b}{\left(\frac{f}{f_r} - \frac{f_r}{f}\right)^2}} \right] \text{ (dB)}$$ + +in which the constants are so selected as to give between 9 and 11 dB of pre-emphasis. + +Both of the sets of values below meet this requirement: + +- | | | | | +|----|-------------|------------|-----------------| +| 1) | $a = 10$ | $b = 3$ | $f_r = 4.7$ MHz | +| 2) | $a = 11.25$ | $b = 1.56$ | $f_r = 4.4$ MHz | + +#### 6.3 *Interconnection in a frontier section of two systems in which the elementary cable sections are of the same nominal length* (this is true of two 4 MHz systems, and also of two 6 MHz systems) + +As the relative line levels and the pre-emphasis characteristic are already covered by recommendations, the interconnection of two systems in a frontier section will not give rise to any great difficulty in this case. The Administration on the receiving side can receive the other Administration's line levels provided minor adjustments are made in the first main repeater station (for details, see Recommendation G.352). + +#### 6.4 *Interconnection of a 4 MHz and a 6 MHz system in a frontier section* + +In the absence of a special agreement between Administrations, the method described in Recommendation G.352 should be applied in this case. + +#### 6.5 *Interconnection at a main station* + +See Recommendation G.213. + +### 7 Power-feeding and alarm systems + +Recommendation G.341, § 7) also applies to systems conforming to the present Recommendation. \ No newline at end of file diff --git a/marked/G/T-REC-G.692-199810-I_PDF-E/183007754364096b2d89f42200cf870f_img.jpg b/marked/G/T-REC-G.692-199810-I_PDF-E/183007754364096b2d89f42200cf870f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4c4ce1717eae88ea462c925e3df32af33551e97 --- /dev/null +++ b/marked/G/T-REC-G.692-199810-I_PDF-E/183007754364096b2d89f42200cf870f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e86163731b05dbf94ad2c51148795c418bfdf577ef76235f0ace939e02978da8 +size 28245 diff --git a/marked/G/T-REC-G.692-199810-I_PDF-E/24b549c0c4b79c515b244625cf4f4978_img.jpg b/marked/G/T-REC-G.692-199810-I_PDF-E/24b549c0c4b79c515b244625cf4f4978_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb2c2d9b3ca237337578a7bc53e20e6248d2303d --- /dev/null +++ b/marked/G/T-REC-G.692-199810-I_PDF-E/24b549c0c4b79c515b244625cf4f4978_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b38b458c59ce132afda152b43fb3ee793de310df349d1511378a65977f86751 +size 52979 diff --git a/marked/G/T-REC-G.692-199810-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.692-199810-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff --- /dev/null +++ b/marked/G/T-REC-G.692-199810-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.692-199810-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg b/marked/G/T-REC-G.692-199810-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7e125669780b25c5451786a09384a2a50a5254c --- /dev/null +++ b/marked/G/T-REC-G.692-199810-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af8d48ea27318ce585b51ad497a2455ce431c7134e8cad4f98383521d475e60a +size 21661 diff --git a/marked/G/T-REC-G.692-199810-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.692-199810-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..673d70221e9852bdb4ffbb820efa599de41ee51c --- /dev/null +++ b/marked/G/T-REC-G.692-199810-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9939dcc18fb8d604cfc806e59c9491c9cde4a9c26f338b3ac0d4ddba77ee75b9 +size 36449 diff --git a/marked/G/T-REC-G.692-199810-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg b/marked/G/T-REC-G.692-199810-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbb841ff09c201c6dbb1ab1cc962cc7d028105d2 --- /dev/null +++ b/marked/G/T-REC-G.692-199810-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a906687ac063cce12d487572236dc73892294a83268bd3a541203d99483003b +size 52111 diff --git a/marked/G/T-REC-G.692-199810-I_PDF-E/7848a2560bb726462c09c09bf727d81d_img.jpg b/marked/G/T-REC-G.692-199810-I_PDF-E/7848a2560bb726462c09c09bf727d81d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21a7198d7c254454dca77438de805d9e5a05903a --- /dev/null +++ b/marked/G/T-REC-G.692-199810-I_PDF-E/7848a2560bb726462c09c09bf727d81d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bff2f1229243e7ae463a8676da3d0d744d16f460f0c9068826d4fff92fa8e58 +size 29911 diff --git a/marked/G/T-REC-G.692-199810-I_PDF-E/9ff1b32449ea068bba9647d71904bd59_img.jpg b/marked/G/T-REC-G.692-199810-I_PDF-E/9ff1b32449ea068bba9647d71904bd59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f884045099deaa96f33d137953a917c5089ca7f3 --- /dev/null +++ b/marked/G/T-REC-G.692-199810-I_PDF-E/9ff1b32449ea068bba9647d71904bd59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3d9c7b5056ad2838863d1a910053afa66068ea5ef9bf7537293c3a6b8a4c9b5 +size 17825 diff --git a/marked/G/T-REC-G.692-199810-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/G/T-REC-G.692-199810-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f99caba84a418a45533a2575e871e122ef68ea0 --- /dev/null +++ b/marked/G/T-REC-G.692-199810-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fec190a8ab3824bb6f09a6718aab4b469e8c3a6b6c2811896eb67b497079c85d +size 11202 diff --git a/marked/G/T-REC-G.692-199810-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/G/T-REC-G.692-199810-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..692a4076bc7bc258a259f8a828a2b72a9518c60c --- /dev/null +++ b/marked/G/T-REC-G.692-199810-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:578cc3551b05b498cef8bcf490bb6127874a89749c936874ab10a47917ce65f6 +size 18941 diff --git a/marked/G/T-REC-G.692-199810-I_PDF-E/raw.md b/marked/G/T-REC-G.692-199810-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0315381e88143e3f842ff708ca900661308ee62b --- /dev/null +++ b/marked/G/T-REC-G.692-199810-I_PDF-E/raw.md @@ -0,0 +1,1315 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.692** + +(10/98) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Transmission media characteristics – Characteristics of +optical components and sub-systems + +--- + +**Optical interfaces for multichannel systems +with optical amplifiers** + +ITU-T Recommendation G.692 + +(Previously CCITT Recommendation) + +--- + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| INTERNATIONAL ANALOGUE CARRIER SYSTEM | | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TESTING EQUIPMENTS | | +| TRANSMISSION MEDIA CHARACTERISTICS | | +| General | G.600–G.609 | +| Symmetric cable pairs | G.610–G.619 | +| Land coaxial cable pairs | G.620–G.629 | +| Submarine cables | G.630–G.649 | +| Optical fibre cables | G.650–G.659 | +| Characteristics of optical components and sub-systems | G.660–G.699 | +| DIGITAL TRANSMISSION SYSTEMS | | +| TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +# **OPTICAL INTERFACES FOR MULTICHANNEL SYSTEMS WITH OPTICAL AMPLIFIERS** + +## **Summary** + +This Recommendation specifies multichannel optical line system interfaces for the purpose of providing future transverse compatibility among such systems. + +This Recommendation defines interface parameters for systems of four, eight and sixteen channels operating at bit rates of up to STM-16 on fibres, as described in Recommendations G.652, G.653 and G.655 with nominal span lengths of 80 km, 120 km and 160 km and target distances between regenerators of up to 640 km. A frequency grid anchored at 193.1 THz with interchannel spacings at integer multiples of 50 GHz and 100 GHz is specified as the basis for selecting channel central frequencies. + +## **Source** + +ITU-T Recommendation G.692 was prepared by ITU-T Study Group 15 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 23rd of October 1998. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1999 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +# CONTENTS + +| | Page | | +|-------|-------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References ..... | 2 | +| 3 | Terminology ..... | 2 | +| 4 | Abbreviations ..... | 3 | +| 5 | Classification of optical interfaces ..... | 3 | +| 5.1 | Applications ..... | 3 | +| 5.1.1 | Application codes for systems without line amplifiers ..... | 4 | +| 5.1.2 | Application codes for systems with line amplifiers ..... | 4 | +| 5.2 | Implementation..... | 5 | +| 5.2.1 | Reference configurations..... | 5 | +| 5.2.2 | Optical supervisory channel implementations ..... | 6 | +| 6 | Parameter definitions..... | 7 | +| 6.1 | Individual transmitter outputs ..... | 7 | +| 6.1.1 | Spectral characteristics..... | 7 | +| 6.1.2 | Mean launched power ..... | 7 | +| 6.1.3 | Extinction ratio..... | 7 | +| 6.1.4 | Eye pattern mask..... | 7 | +| 6.1.5 | Central frequency ..... | 7 | +| 6.1.6 | Channel spacing ..... | 8 | +| 6.1.7 | Central frequency deviation ..... | 8 | +| 6.2 | Individual channel input ports..... | 8 | +| 6.3 | Optical interface at points MPI-S and S' ..... | 8 | +| 6.3.1 | Optical transmit-side crosstalk..... | 8 | +| 6.3.2 | Channel output power ..... | 8 | +| 6.3.3 | Total launched power..... | 8 | +| 6.3.4 | Channel optical signal-to-noise ratio ..... | 8 | +| 6.3.5 | Maximum channel power difference at point MPI-S or point S' ..... | 9 | +| 6.4 | Optical path ..... | 9 | +| 6.4.1 | Attenuation..... | 9 | +| 6.4.2 | Dispersion ..... | 9 | +| 6.4.3 | Reflections ..... | 10 | +| 6.5 | Optical line amplifier parameters ..... | 10 | +| 6.5.1 | Multichannel gain variation ..... | 10 | +| 6.5.2 | Multichannel gain tilt..... | 10 | +| 6.5.3 | Multichannel gain-change difference..... | 10 | + +| | Page | +|-----------------------------------------------------------------------------------------------------------|-------------| +| 6.5.4 Total received power..... | 10 | +| 6.5.5 Total launched power..... | 10 | +| 6.5.6 Signal spontaneous noise figure..... | 10 | +| 6.6 Optical interface at points MPI-R and R' ..... | 10 | +| 6.6.1 Mean channel input power ..... | 10 | +| 6.6.2 Mean total input power ..... | 10 | +| 6.6.3 Channel optical signal-to-noise ratio ..... | 10 | +| 6.6.4 Optical crosstalk at points MPI-R and R' ..... | 11 | +| 6.6.5 Maximum channel power difference at point MPI-R or at point R'..... | 11 | +| 6.7 Individual channel output ports..... | 11 | +| 6.7.1 Optical crosstalk at individual channel output ports ..... | 11 | +| 6.8 Individual receiver inputs..... | 11 | +| 6.8.1 Receiver sensitivity ..... | 11 | +| 6.8.2 Receiver overload..... | 11 | +| 6.8.3 Optical path penalty ..... | 11 | +| 6.8.4 Receiver reflectance..... | 11 | +| 6.8.5 Optical signal-to-noise ratio ..... | 11 | +| 6.8.6 Receiver wavelength range ..... | 12 | +| 6.9 Optical supervisory channel parameters..... | 12 | +| 6.9.1 Optical supervisory channel wavelength..... | 12 | +| 7 Optical interface parameter values ..... | 12 | +| Annex A – Nominal central frequencies ..... | 14 | +| Annex B – Alternative optical supervisory channel approaches ..... | 16 | +| B.1 OSC at 1480 nm ..... | 16 | +| B.2 OSC in 1310 nm band ..... | 16 | +| B.3 OSC within EDFA gain bandwidth..... | 16 | +| Appendix I – Methodology for derivation of optical power levels ..... | 17 | +| I.1 Channel power..... | 17 | +| I.1.1 Minimum channel power ..... | 17 | +| I.1.2 Maximum channel power..... | 18 | +| I.1.3 Maximum range for channel power ..... | 18 | +| I.2 Maximum total power ..... | 19 | +| Appendix II – Selection of the minimum channel spacing and grid reference frequency for the WDM plan..... | 19 | +| II.1 50 GHz/100 GHz spacing and 193.10 THz reference..... | 19 | + +| | Page | +|---------------------------------------------------------------------------------------------------------------------|-------------| +| II.2 Absolute frequency reference (AFR)..... | 19 | +| II.2.1 AFR accuracy..... | 20 | +| II.2.2 AFR stability ..... | 20 | +| Appendix III – Suggested channel frequency allocations for applications on G.652/G.655 fibres..... | 20 | +| Appendix IV – Suggested channel frequency allocations for applications on G.653 fibres... | 21 | +| Appendix V – A channel-allocation methodology for applications on G.653 fibre based on unequal channel spacing..... | 23 | +| V.1 How to determine unequally-spaced channel frequencies..... | 24 | +| V.1.1 Basic design conditions..... | 24 | +| V.1.2 Determination of frequency slot..... | 25 | +| V.1.3 Required optical bandwidth for unequally spaced frequency allocation..... | 26 | +| V.2 Unequally spaced channel frequency allocation with 25 GHz frequency slot..... | 27 | +| V.3 Unequally spaced channel frequency allocation with 50 GHz frequency slot ..... | 27 | +| V.4 Unequal channel frequency allocation with 100 GHz frequency slot..... | 28 | +| V.5 Impacts of unequal spacing on other parameters..... | 28 | +| V.5.1 Frequency deviation for unequal spacing with frequency offset..... | 28 | +| V.5.2 Power Levels..... | 28 | +| V.6 Bibliography ..... | 28 | +| Appendix VI – Use of pre-equalisation at MPI-S..... | 29 | +| Appendix VII – Extension of G.692 to include bidirectional WDM transmission ..... | 29 | +| Appendix VIII – Extension of G.692 to include 16- and 32- or more channel transmission.. | 30 | +| Appendix IX – Extension of G.692 to include STM-64 bit-rate ..... | 31 | + + + +# **OPTICAL INTERFACES FOR MULTICHANNEL SYSTEMS WITH OPTICAL AMPLIFIERS** + +*(Geneva, 1998)* + +# **1 Scope** + +This Recommendation applies to optical interfaces for multichannel optical line systems with optical amplifiers for terrestrial long-haul applications. This Recommendation defines and provides values for optical interface parameters of interoffice and long-haul systems with target lengths up to 160 km without line amplifiers and with target lengths up to 640 km with optical line amplifiers. Descriptions of system reference configurations and their constituent functional blocks are contained in Recommendation G.681. + +The purpose of this Recommendation is to provide optical amplifier specifications for SDH and optical amplifier equipment towards future realisation of transverse compatible multichannel systems. Not all specifications required to obtain full transverse compatible systems could be finalised at the present stage of development. However, because of industry interest and emerging implementations, this initial version is issued. A complete specification is left to future versions of this Recommendation. + +This Recommendation applies principally to point-to-point multichannel systems. Specific issues of optical add-drop are not considered. + +This Recommendation is envisioned to describe optical line systems that include the following features: + +- maximum number of channels: 4, 8, 16 , 32 or more; +- signal channel types: STM-4, STM-16, or STM-64; +- transmission over a single fibre: unidirectional or bidirectional. + +Given evolving technologies and markets, some aspects of the features described above are not fully characterised at this time, and are marked for further study. Some aspects of 16 and 32 channel systems, STM-64 and possibly bidirectional transmission are for further study. Some system aspects regarding bidirectional transmission (Appendix VII), regarding 16- and 32-channel transmission (Appendix VIII) and regarding STM-64 transmission (Appendix IX) are contained in the indicated appendices. + +This Recommendation has been prepared from the experience with Erbium-Doped (silica-based) Fibre Amplifiers (EDFA), operating in the 1550 nm wavelength region. Other optical amplifiers operating at different wavelength regions, including the 1310 nm region, are not intended to be excluded from this Recommendation. + +# 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.652 (1997), *Characteristics of a single-mode optical fibre cable.* +- ITU-T Recommendation G.653 (1997), *Characteristics of a dispersion-shifted single-mode optical fibre cable.* +- ITU-T Recommendation G.655 (1996), *Characterisation of a non-zero dispersion shifted single-mode optical fibre cable.* +- ITU-T Recommendation G.661 (1998), *Definition and test methods for the relevant generic parameters of optical amplifier devices and subsystems.* +- ITU-T Recommendation G.662 (1998), *Generic characteristics of optical amplifier devices and subsystems.* +- ITU-T Recommendation G.663 (1996), *Application related aspects of optical fibre amplifier devices and sub-systems.* +- ITU-T Recommendation G.671 (1996), *Transmission characteristics of passive optical components.* +- ITU-T Recommendation G.681 (1996), *Functional characteristics of interoffice and long-haul line systems using optical amplifiers, including optical multiplexing.* +- ITU-T Recommendation G.707 (1996), *Network node interface for the Synchronous Digital Hierarchy (SDH).* +- ITU-T Recommendation G.783 (1997), *Characteristics of Synchronous Digital Hierarchy (SDH) equipment functional blocks.* +- ITU-T Recommendation G.955 (1996), *Digital line systems based on the 1544 kbit/s and the 2048 kbit/s hierarchy on optical fibre cables.* +- ITU-T Recommendation G.957 (1995), *Optical interfaces for equipments and systems relating to the synchronous digital hierarchy.* +- IEC Publication 60825-1 (1993), *Safety of laser products – Part 1: Equipment classification, requirements and user's guide.* +- IEC Publication 61291-4 Ed.1.0 (working progress), *Performance specification template on optical amplifiers – Part 4: Optical fibre amplifiers for multichannel applications.* + +# 3 Terminology + +This Recommendation defines the following terms: + +**3.1 Optical Supervisory Channel (OSC):** A channel that is accessed at each optical line amplifier site that is used for maintenance purposes including (but not limited to) remote site alarm reporting, communication necessary for fault location, and orderwire. The Optical Supervisory Channel is not used to carry payload traffic. + +**3.2 main (optical) path:** The fibre plant between the MPI-S point of the transmitter equipment and the MPI-R point of the receiver equipment. The main path does not include any auxiliary paths. + +**3.3 main path interfaces:** The interfaces to the fibre plant specified in this Recommendation. + +# **4 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|-------|----------------------------------------| +| AFR | Absolute Frequency Reference | +| ASE | Amplified Spontaneous Emission | +| BER | Bit-Error Ratio | +| EDFA | Erbium-Doped Fibre Amplifier | +| FWM | Four-Wave Mixing | +| MPI | Multiple Path Interference | +| MPI-R | Main Path Interface at the Receiver | +| MPI-S | Main Path Interface at the Transmitter | +| NF | Noise Figure | +| OA | Optical Amplifier | +| OD | Optical Demultiplexer | +| OEO | Optical-Electrical-Optical Converter | +| OM | Optical Multiplexer | +| OSC | Optical Supervisory Channel | +| OSNR | Optical Signal-to-Noise Ratio | +| PMD | Polarisation Mode Dispersion | +| RX | Optical Receiver | +| SBS | Stimulated Brillouin Scattering | +| SDH | Synchronous Digital Hierarchy | +| SNR | Signal-to-Noise Ratio | +| SPM | Self Phase Modulation | +| STM-N | Synchronous Transport Module Level N | +| TX | Optical Transmitter | +| WDM | Wavelength Division Multiplexing | +| XPM | Cross-Phase Modulation | + +# **5 Classification of optical interfaces** + +## **5.1 Applications** + +This Recommendation addresses multichannel systems for terrestrial long-haul applications with total target distance and discrete amplifier spacing as described below. + +### 5.1.1 Application codes for systems without line amplifiers + +These applications consist of 4, 8 or 16 optical channels that are optically multiplexed together. Each channel may be STM-4 or STM-16, including a simultaneous mixture of different rate channels. The target distances for these systems are nominally 80 km, 120 km, and 160 km on G.652, G.653 and G.655 fibres. The application codes with G.653 fibre are for further study. The application codes for systems without line amplifiers are summarised in Table 1. + +The application codes in Table 1 are constructed in the following way: + +- nWx-y.z + +where, for each application code: + +- n is the maximum number of wavelengths. +- W is a letter indicating span distance, such as: + - L indicating long-haul; + - V indicating very long-haul; + - U indicating ultra long-haul. +- x is the maximum number of spans allowed within the application code (x = 1 for systems without line amplifiers. In this case it is not shown). +- y is the maximum bit-rate (STM level) of the wavelength signals. +- z is the fibre type, as follows: + - 2 indicating G.652 fibre. + - 3 indicating G.653 fibre. + - 5 indicating G.655 fibre. + +A bidirectional system is indicated by the addition of the letter B at the front of the Application code: + +- B-nWx-y.z + +**Table 1/G.692 – Application codes for multichannel systems without line amplifiers** + +| Application | Long-haul
(target distance 80 km) | Very long-haul
(target distance 120 km) | Ultra long-haul
(target distance 160 km) | +|--------------------|--------------------------------------|--------------------------------------------|---------------------------------------------| +| 4-channel systems | 4L-y.z | 4V-y.z | 4U-y.z | +| 8-channel systems | 8L-y.z | 8V-y.z | 8U-y.z | +| 16-channel systems | 16L-y.z | 16V-y.z | 16U-y.z d) | + +a) The target distances are to be used for classification only and not for specification. +b) y = 4 or 16. +c) z = 2, 3 or 5. +d) The feasibility of this application is for further study. + +### 5.1.2 Application codes for systems with line amplifiers + +These applications also consist of 4, 8 or 16 optical channels that are optically multiplexed together. The target spacings between line optical amplifiers are nominally 80 km and 120 km with total target distances before requiring regeneration of nominally 360 km to 640 km on G.652, G.653, and G.655 fibres. In order to limit the possible combinations of these distances, they are reduced to the applications shown in Table 2. + +The application codes for systems with line amplifiers are summarised in Table 2. + +**Table 2/G.692 – Application codes for multichannel systems with line amplifiers** + +| Application | Long-haul spans
(per span target distance 80 km) | | Very long-haul spans
(per span target distance 120 km) | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|----------|-----------------------------------------------------------|----------|------------------------| +| | Number of spans | 5 | 8 | 3 | 5 | +| 4-channel systems | | 4L5-y.z | 4L8-y.z | 4V3-y.z | 4V5-y.z | +| 8-channel systems | | 8L5-y.z | 8L8-y.z | 8V3-y.z | 8V5-y.z a) | +| 16-channel systems | | 16L5-y.z | 16L8-y.z | 16V3-y.z | 16V5-y.z a) | +| a) The feasibility of this application code is for further study.
b) The target distances are to be used for classification only and not for specification.
c) y = 4, or 16.
d) z = 2, 3, 5. | | | | | | + +Systems of the type nL5 and nV3 are not a subset of nL8 and nV5 systems, respectively, because nL8 and nV5 systems require different technologies (including lower noise OAS and more stringent dispersion requirements) which may be significantly more challenging and may not be achievable for all fibre types. + +The application codes are based on channel bit-rates of up to STM-16 per channel systems with higher bit-rates, such as STM-64, it will be necessary to re-evaluate application codes. The exact values are for further study. + +It should be noted that, for example, a 4-channel system cannot be upgraded to an 8-channel system. Such option is only given by under equipped 8-channel systems. That means if operators choose, for example, the option to upgrade a 4-channel system to 8 channels, they have not only to choose the central frequency deviation in line with an 8-channel system but also all other relevant parameters. + +## 5.2 Implementation + +### 5.2.1 Reference configurations + +Figure 1 illustrates the reference configuration for a G.692 system with the number of n channels, with reference points: + +- S1 ... Sn are reference points on the optical fibre at the output optical connectors of the transmitters for channels 1 ... n respectively. +- RM1 ... RMn are reference points on the optical fibre just before the OM/OA input optical connectors for channels 1 ... n respectively. +- MPI-S is a reference point on the optical fibre just after the OM/OA output optical connector. +- S' is a reference point just after the line OA output optical connector. +- R' is a reference point on the optical fibre just before the line OA input optical connector. +- MPI-R is a reference point on the optical fibre just before the OA/OD input optical connector. +- SD1 ... SDn are reference points at the OA/OD output optical connectors. +- R1 ... Rn are reference points at the inputs to the receiver optical connectors. + +![Figure 1/G.692 – Representation of optical line system interfaces. This diagram shows a multi-channel optical system. On the left, multiple transmitters (Tx1, Tx2, ..., TxN) are connected to an Optical Multiplexer/Optical Amplifier (OM/OA) at reference points f1, f2, ..., fn. The OM/OA has output reference points RM1, RM2, ..., RMn. The signal then passes through a series of components: an MPI-S (Multi-Point Interface - Sender) with reference points R' and S', an Optical Amplifier (OA) with reference points R' and S', another MPI-R (Multi-Point Interface - Receiver) with reference points S' and R', and an Optical Amplifier/Optical Demultiplexer (OA/OD) with reference points SD1, SD2, ..., SDn. Finally, the signals are received by multiple receivers (Rx1, Rx2, ..., RxN) at reference points R1, R2, ..., Rn. The diagram is labeled T1527240-97.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +Figure 1/G.692 – Representation of optical line system interfaces. This diagram shows a multi-channel optical system. On the left, multiple transmitters (Tx1, Tx2, ..., TxN) are connected to an Optical Multiplexer/Optical Amplifier (OM/OA) at reference points f1, f2, ..., fn. The OM/OA has output reference points RM1, RM2, ..., RMn. The signal then passes through a series of components: an MPI-S (Multi-Point Interface - Sender) with reference points R' and S', an Optical Amplifier (OA) with reference points R' and S', another MPI-R (Multi-Point Interface - Receiver) with reference points S' and R', and an Optical Amplifier/Optical Demultiplexer (OA/OD) with reference points SD1, SD2, ..., SDn. Finally, the signals are received by multiple receivers (Rx1, Rx2, ..., RxN) at reference points R1, R2, ..., Rn. The diagram is labeled T1527240-97. + +**Figure 1/G.692 – Representation of optical line system interfaces** + +NOTE 1 – The attenuation of the OSC hybrid possibly used to access the OSC is not part of the optical path power budget. + +NOTE 2 – When a combination of a G.957 compliant transmitter and an optical transponder, as shown in Figure 2, is used to realise the G.692 optical transmitter, the $S_n$ reference points, as defined in this Recommendation, are located just after the optical transponder output optical connectors. In this case, the interface between the G.957 compliant transmitter and the transponder is appropriately chosen from the set of specifications given for the S point of G.957. + +![Figure 2/G.692 – Possible implementation of a G.692 transmitter using a G.957 compliant transmitter and a transponder. This diagram shows a G.957 compliant transmitter (Tx G.957) connected to an Optical/Electrical/Optical (O/E/O) transponder. The connection point between the transmitter and the transponder is labeled S (G.957). The output of the transponder is labeled Sn (G.692). The diagram is labeled T1527250-97.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +Figure 2/G.692 – Possible implementation of a G.692 transmitter using a G.957 compliant transmitter and a transponder. This diagram shows a G.957 compliant transmitter (Tx G.957) connected to an Optical/Electrical/Optical (O/E/O) transponder. The connection point between the transmitter and the transponder is labeled S (G.957). The output of the transponder is labeled Sn (G.692). The diagram is labeled T1527250-97. + +**Figure 2/G.692 – Possible implementation of a G.692 transmitter using a G.957 compliant transmitter and a transponder** + +This Recommendation specifies the possibility of loss between reference points $S_n$ and $R_{Mn}$ . The minimum value of this loss is 0. Similarly, there may be loss between points $S_{Dn}$ and $R_n$ . It is also possible that the OM/OA and/or the OA/OD will not contain an OA. In addition, the possibility exists that the transmitters and the OM/OA (and likewise the OA/OD and the receivers) will be integrated; in this case, there will be no access to the interfaces at reference points $S_n$ , $R_{Mn}$ , $S_{Dn}$ and $R_n$ . + +### 5.2.2 Optical supervisory channel implementations + +Optical line systems described within this Recommendation that employ line amplifiers require an additional Optical Supervisory Channel (OSC). This channel shall be capable of being accessed at each amplifier. For optical line amplifiers implemented using Erbium-Doped Fibre Amplifier (EDFA) technology, the optical supervisory channel can be located outside the usable gain bandwidth of the EDFA ("out-of-band OSC") or alternatively, within the usable gain bandwidth ("in-band OSC"). There are design trade-offs associated with each of these possible choices. Subclause B.3 indicates the in-band OSC option. + +The nominal preferred wavelength for the out-of-band Optical Supervisory Channel (OSC) is 1510 nm. Components for the 1510 nm wavelength (e.g. laser diodes, filters, etc.) are currently of limited availability. Until these components are mature and readily available, alternative wavelengths + +of 1480 nm or a wavelength in the 1310 nm band may be used. These OSC alternatives are indicated in subclauses B.1 and B.2. + +The selection of the 1310 nm band may preclude the use of that band for alternative traffic. Two amplifiers operating with different OSC wavelengths will not, in general, be transversely compatible. + +# **6 Parameter definitions** + +Parameters applicable to this Recommendation are listed. Many of these parameters are defined in Recommendation G.957 and for these reference is made to G.957 for the definitions. Additional information pertaining to multichannel systems is included in addition to the G.957 definitions. + +The parameters of subclauses 6.4.1, 6.4.2, 6.4.3 and 6.8.3 are sufficient to define longitudinally compatible multichannel systems on each optical fibre type (G.652, G.653, G.655) and for application codes considered in this Recommendation. However, according to the intent of this Recommendation, all parameters defined in clause 6 are required to obtain transverse compatible systems. + +## **6.1 Individual transmitter outputs** + +These parameters apply to the outputs of the individual channel transmitters corresponding to points $S_n$ in Figures 1 and 2. + +### **6.1.1 Spectral characteristics** + +The spectral characteristics include maximum -20 dB width and minimum side modes suppression ratio as defined in Recommendation G.957. + +### **6.1.2 Mean launched power** + +The maximum and minimum mean launched power are defined in Recommendation G.957. + +### **6.1.3 Extinction ratio** + +The extinction ratio is defined in Recommendation G.957. + +### **6.1.4 Eye pattern mask** + +For further study. + +### **6.1.5 Central frequency** + +For channel spacings of 50 GHz on a fibre, the allowed channel frequencies are based on a 50 GHz grid with the reference frequency at 193.10 THz. For channel spacings of 100 GHz or more on a fibre, the allowed channel frequencies are based on a 100 GHz grid with the reference frequency at 193.10 THz. The table of the 50 and 100 GHz grid frequencies of the EDFA gain region is shown in Annex A. The endpoints are illustrative, not normative. + +Suggested channel central frequency choices for applications on G.652/G.655 fibres are contained in Appendix III, in Table III.1. + +Suggested channel central frequency choices for applications on G.653 fibres are contained in Appendix IV, in Table IV.1. + +### 6.1.6 Channel spacing + +The nominal channel spacing is the frequency difference between adjacent channels. The channel spacing may be equal or unequal. An unequal channel spacing may be used to mitigate FWM effects in G.653 fibres; a channel-allocation methodology is given in Appendix V. + +### 6.1.7 Central frequency deviation + +The central frequency deviation is defined as the difference between the nominal central frequency and the actual central frequency. + +Included in the central frequency deviation are all the processes which affect the instantaneous value of the source central frequency over a measurement interval appropriate to the channel bit-rate. These processes include source chirp, information bandwidth, broadening due to SPM, and effects due to temperature and ageing. + +Table 3 provides maximum end-of-life central frequency deviation to be associated with each channel spacing. + +**Table 3/G.692 – End-of-life central frequency deviation associated with each channel spacing** + +| Channel spacing
GHz (n) | 50 | 100 | $n \geq 200$ | +|--------------------------------------------------|-------------------|-------------------|--------------| +| Maximum Central Frequency
Deviation $\pm$ GHz | For further study | For further study | $n/5$ | + +For systems with unequal channel spacing, channels at boundaries between different channel spacings shall have the more restrictive of the two deviations. + +## 6.2 Individual channel input ports + +These parameters apply to the inputs of the OM/OA corresponding to points $R_{Mn}$ in Figure 1. + +## 6.3 Optical interface at points MPI-S and S' + +These parameters apply to the optical interface at points MPI-S and S' in Figure 1. + +### 6.3.1 Optical transmit-side crosstalk + +For further study. + +### 6.3.2 Channel output power + +The Channel Output Power is the mean launched optical channel power. This includes the ASE noise within the channel band. + +### 6.3.3 Total launched power + +The total Launched power is the maximum mean launched optical power at point MPI-S or at point S'. + +### 6.3.4 Channel optical signal-to-noise ratio + +For further study. + +### 6.3.5 Maximum channel power difference at point MPI-S or point S' + +The maximum difference in Channel Power is the difference between the largest value of channel launch power and the smallest value of channel launch power present at the same time within a given optical resolution bandwidth, independent of the number of channels, within the application. + +## 6.4 Optical path + +To ensure system performance for each of the applications listed in Table 1, it is necessary to specify characteristics of the optical path between reference points MPI-S and MPI-R as well as between R' and S' respectively as shown in Figure 1. + +### 6.4.1 Attenuation + +Attenuation is defined in Recommendation G.957. The attenuation ranges required for the target distances are based on the assumption of 0.28 dB/km installed fibre loss (including splices and cable margin) in the 1530-1565 nm range. This fibre loss assumption leads to 11 dB for a target distance of 40 km. Attenuation ranges for distances which are a multiple of 40 km are based on the appropriate multiple of 11 dB. In practice these values may not apply to all fibre cables, in which case the realistic distances that can be reached may be shorter. + +Table 4 contains the attenuation ranges for systems without optical line-amplifiers. Table 5 contains the attenuation ranges for systems with optical line-amplifiers. + +**Table 4/G.692 –Attenuation ranges for application codes without optical line-amplifiers** + +| Application code | nL-y.z | nV-y.z | nU-y.z | +|-------------------|-------------------|-------------------|-------------------| +| Attenuation Range | | | | +| – maximum | 22 dB | 33 dB | 44 dB | +| – minimum | For further study | For further study | For further study | + +**Table 5/G.692 – Attenuation ranges for application codes with optical line-amplifiers** + +| Application code | nLx-y.z | nVx-y.z | +|---------------------------------|-------------------|-------------------| +| Attenuation Range (between OAs) | | | +| – maximum | 22 dB | 33 dB | +| – minimum | For further study | For further study | + +### 6.4.2 Dispersion + +Dispersion includes the effects of chromatic dispersion, as defined in Recommendation G.957, and polarisation mode dispersion. The dispersion limits required for the target distances on G.652 fibre are based on the assumption of 20 ps/(nm.km). The dispersion limits required for G.655 fibre are for further study. + +Table 6 contains the dispersion ranges for systems without optical line-amplifiers and systems with optical line-amplifiers on G.652 fibre. + +**Table 6/G.692 – Maximum dispersion for applications on G.652 fibre** + +| Application code | L | V | U | nV3-y.2 | nL5-y.2 | nV5-y.2 | nL8-y.2 | +|----------------------------|----------|----------|----------|----------------|----------------|----------------|----------------| +| Maximum dispersion (ps/nm) | 1600 | 2400 | 3200 | 7200 | 8000 | 12 000 | 12 800 | + +NOTE – For STM-16 systems and dispersion values above 10 000 ps/nm, dispersion accommodation techniques might be required. Any loss associated with these techniques is considered not to be included in the attenuation ranges specified in 6.4.1. + +### **6.4.3 Reflections** + +Reflection parameters include minimum optical return loss and maximum discrete reflectance and are defined in Recommendation G.957. + +## **6.5 Optical line amplifier parameters** + +These parameters only apply to systems which include line amplifiers. + +### **6.5.1 Multichannel gain variation** + +This parameter is defined in IEC 61291-4. + +### **6.5.2 Multichannel gain tilt** + +This parameter is defined in IEC 61291-4. + +### **6.5.3 Multichannel gain-change difference** + +This parameter is defined in IEC 61291-4. + +### **6.5.4 Total received power** + +This parameter is the maximum mean input power present at point R' in Figure 1. + +### **6.5.5 Total launched power** + +This parameter is the maximum mean input power present at point S' in Figure 1. + +### **6.5.6 Signal spontaneous noise figure** + +This parameter is defined in G.661. + +## **6.6 Optical interface at points MPI-R and R'** + +These parameters apply to the optical interface at points MPI-R and R' in Figure 1. The maximum and minimum values of these parameters are specified independent of the number of channels present. + +### **6.6.1 Mean channel input power** + +The mean channel input power is the maximum and minimum mean input channel power measured at point MPI-R or at point R'. + +### **6.6.2 Mean total input power** + +The mean total input power is the maximum mean total input power measured at point MPI-R or at point R'. + +### **6.6.3 Channel optical signal-to-noise ratio** + +For further study. + +### **6.6.4 Optical crosstalk at points MPI-R and R'** + +For further study. + +### **6.6.5 Maximum channel power difference at point MPI-R or at point R'** + +Maximum difference in channel power is the difference between the largest value of channel input power and the smallest value of channel input power present at the same time within a given optical resolution bandwidth, independent of the number of channels, within the application. + +## **6.7 Individual channel output ports** + +These parameters apply to the outputs of the OA/OD corresponding to points $S_{Dn}$ in Figure 1. + +### **6.7.1 Optical crosstalk at individual channel output ports** + +Optical Crosstalk is defined as the ratio of the combined total disturbing power due to signal power from all other channels, operating under all specified conditions, relative to the nominal signal power level in the desired channel, at the single-channel signal output reference points $S_{D1} \dots S_{Dn}$ according to Figure 1, within the resulting bandwidth of the optical demultiplexer and optical receiver, expressed in dB. + +## **6.8 Individual receiver inputs** + +These parameters apply to the inputs of the individual channel receivers corresponding to point $R_n$ in Figure 1. + +### **6.8.1 Receiver sensitivity** + +Receiver sensitivity is defined as the minimum value of average received power at point $R_n$ to achieve a $1 \times 10^{-12}$ BER. It takes into account power penalties caused by use of a transmitter under standard operating conditions with worst-case values of extinction ratio, pulse rise and fall times, optical return loss at points $S_n$ , receiver connector degradations, crosstalk, optical amplifier noise, 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 optical path penalty. Ageing effects are not specified separately since they are typically a matter between a beginning-of-life, nominal temperature receiver and its end-of-life, worst-case counterpart are desired to be in the 2 to 4 dB range. The receiver sensitivities in this Recommendation are worst-case, end-of-life values. + +### **6.8.2 Receiver overload** + +Receiver overload is the maximum acceptable value of the received average power at point $R_n$ for a $1 \times 10^{-12}$ BER. + +### **6.8.3 Optical path penalty** + +To be defined. + +### **6.8.4 Receiver reflectance** + +The receiver reflectance is defined in Recommendation G.957. + +### **6.8.5 Optical signal-to-noise ratio** + +The minimum value of optical SNR required to obtain a $1 \times 10^{-12}$ BER. + +### 6.8.6 Receiver wavelength range + +The receiver wavelength range is defined as the acceptable range of wavelengths at point $R_n$ . This range must be wide enough to cover the entire range of central frequencies over the OA passband. + +## 6.9 Optical supervisory channel parameters + +### 6.9.1 Optical supervisory channel wavelength + +The optical supervisory channel wavelength is the wavelength on which the optical supervisory channel is transmitted. It is nominally $1510 \pm 10$ nm ( $198.5 \pm 1.4$ THz). Other wavelengths are described in Annex B. + +# 7 Optical interface parameter values + +Table 7 identifies parameters that are required at various interfaces (see Figure 1) within an optical communication system, in order to ensure transverse compatibility. In principle, there is one Table for each application code. However, at the present stage of development of this Recommendation, only a single Table template is shown. The relevant subclauses describing the parameter definitions and values are given in the Table 7. Where no value is given, the value is for further study. + +**Table 7/G.692 – Table Template for optical interfaces** + +| Application code | Value | Units | Note
(Subclause) | +|-------------------------------------------------------------|-------|-------|---------------------| +| Number of Channels | | | 5.1 | +| Bit-Rate/Format of Channels | | | 5.1 | +| Individual Transmitter Outputs | | | | +| Spectral Characteristics | | | 6.1.1 | +| Mean Launched Power | | dBm | 6.1.2 | +| Extinction Ratio | | | 6.1.3 | +| Eye Pattern mask | | | 6.1.4 | +| Central Frequency | | GHz | 6.1.5 | +| Channel Spacing | | GHz | 6.1.6 | +| Central Frequency Deviation | | GHz | 6.1.7 | +| Individual channel input ports | | | 6.2 | +| NOTE – Parameters are for further study | | | | +| Optical Interfaces at Points MPI-S and S' | | | | +| Optical Transmit-side Crosstalk | | dB | 6.3.1 | +| Channel Output Power | | dBm | 6.3.2 | +| Total Launched Power
– maximum | | dBm | 6.3.3 | +| Channel Signal-to-Noise Ratio | | dB | 6.3.4 | +| Maximum Channel Power Difference at Point MPI-S or Point S' | | dB | 6.3.5 | + +**Table 7/G.692 – Table Template for optical interfaces (concluded)** + +| Application code | Value | Units | Note
(Subclause) | +|-----------------------------------------------------------------------|-------|------------|---------------------| +| Optical Line Amplifier | | | | +| Multichannel Gain Variation | | dB | 6.5.1 | +| Multichannel Gain Tilt | | dB/dB | 6.5.2 | +| Multichannel Gain-change Difference | | dB | 6.5.3 | +| Total Received Power
– maximum | | dBm | 6.5.4 | +| Total Launched Power
– maximum | | dBm | 6.5.5 | +| Signal Spontaneous Noise Figure | | dB | 6.5.6 | +| Optical Path | | | | +| Attenuation | | dB | 6.4.1 | +| Dispersion | | ps/nm | 6.4.2 | +| Maximum Discrete Reflectance | | dB | 6.4.3 | +| Minimum Return Loss | | dB | 6.4.3 | +| Optical Interfaces at Points MPI-R and R' | | | | +| Mean channel input power
– maximum
– minimum | | dBm
dBm | 6.6.1 | +| Mean total input power
– maximum | | dBm | 6.6.2 | +| Channel Signal-to-Noise Ratio | | dB | 6.6.3 | +| Optical Signal Crosstalk | | dB | 6.6.4 | +| Maximum Channel Power Difference at Point MPI-R or at Point R' | | dB | 6.6.5 | +| Individual channel output ports | | | 6.7 | +| Optical Crosstalk at individual channel output ports | | dB | 6.7.1 | +| NOTE – Additional parameters not defined in 6.7 are for further study | | | | +| Individual receiver inputs | | | | +| Receiver Sensitivity | | dBm | 6.8.1 | +| Receiver Overload | | dBm | 6.8.2 | +| Optical Path Penalty | | dB | 6.8.3 | +| Receiver Reflectance | | dB | 6.8.4 | +| Optical Signal-to-Noise Ratio | | dB | 6.8.5 | +| Minimum Receiver Wavelength | | nm | 6.8.6 | +| Maximum Receiver Wavelength | | nm | 6.8.6 | + +# ANNEX A + +## Nominal central frequencies + +Table A.1 gives nominal central frequencies based on the 50 GHz minimum channel spacing anchored to the 193.10 THz reference. Note that the value of "c" (speed of light) that should be used for converting between frequency and wavelength is $2.99792458 \times 10^8$ m/s. + +**Table A.1/G.692 – Nominal central frequencies** + +| Nominal central frequencies (THz) for spacings of 50 GHz | Nominal central frequencies (THz) for spacings of 100 GHz and above | Nominal central wavelengths (nm) | +|-----------------------------------------------------------------|----------------------------------------------------------------------------|-----------------------------------------| +| 196.10 | 196.10 | 1528.77 | +| 196.05 | – | 1529.16 | +| 196.00 | 196.00 | 1529.55 | +| 195.95 | – | 1529.94 | +| 195.90 | 195.90 | 1530.33 | +| 195.85 | – | 1530.72 | +| 195.80 | 195.80 | 1531.12 | +| 195.75 | – | 1531.51 | +| 195.70 | 195.70 | 1531.90 | +| 195.65 | – | 1532.29 | +| 195.60 | 195.60 | 1532.68 | +| 195.55 | – | 1533.07 | +| 195.50 | 195.50 | 1533.47 | +| 195.45 | – | 1533.86 | +| 195.40 | 195.40 | 1534.25 | +| 195.35 | – | 1534.64 | +| 195.30 | 195.30 | 1535.04 | +| 195.25 | – | 1535.43 | +| 195.20 | 195.20 | 1535.82 | +| 195.15 | – | 1536.22 | +| 195.10 | 195.10 | 1536.61 | +| 195.05 | – | 1537.00 | +| 195.00 | 195.00 | 1537.40 | +| 194.95 | – | 1537.79 | +| 194.90 | 194.90 | 1538.19 | +| 194.85 | – | 1538.58 | +| 194.80 | 194.80 | 1538.98 | +| 194.75 | – | 1539.37 | +| 194.70 | 194.70 | 1539.77 | +| 194.65 | – | 1540.16 | + +**Table A.1/G.692 – Nominal central frequencies (continued)** + +| Nominal central frequencies (THz) for spacings of 50 GHz | Nominal central frequencies (THz) for spacings of 100 GHz and above | Nominal central wavelengths (nm) | +|-----------------------------------------------------------------|----------------------------------------------------------------------------|-----------------------------------------| +| 194.60 | 194.60 | 1540.56 | +| 194.55 | – | 1540.95 | +| 194.50 | 194.50 | 1541.35 | +| 194.45 | – | 1541.75 | +| 194.40 | 194.40 | 1542.14 | +| 194.35 | – | 1542.54 | +| 194.30 | 194.30 | 1542.94 | +| 194.25 | – | 1543.33 | +| 194.20 | 194.20 | 1543.73 | +| 194.15 | – | 1544.13 | +| 194.10 | 194.10 | 1544.53 | +| 194.05 | – | 1544.92 | +| 194.00 | 194.00 | 1545.32 | +| 193.95 | – | 1545.72 | +| 193.90 | 193.90 | 1546.12 | +| 193.85 | – | 1546.52 | +| 193.80 | 193.80 | 1546.92 | +| 193.75 | – | 1547.32 | +| 193.70 | 193.70 | 1547.72 | +| 193.65 | – | 1548.11 | +| 193.60 | 193.60 | 1548.51 | +| 193.55 | – | 1548.91 | +| 193.50 | 193.50 | 1549.32 | +| 193.45 | – | 1549.72 | +| 193.40 | 193.40 | 1550.12 | +| 193.35 | – | 1550.52 | +| 193.30 | 193.30 | 1550.92 | +| 193.25 | – | 1551.32 | +| 193.20 | 193.20 | 1551.72 | +| 193.15 | – | 1552.12 | +| 193.10 | 193.10 | 1552.52 | +| 193.05 | – | 1552.93 | +| 193.00 | 193.00 | 1553.33 | +| 192.95 | – | 1553.73 | +| 192.90 | 192.90 | 1554.13 | +| 192.85 | – | 1554.54 | + +**Table A.1/G.692 – Nominal central frequencies (concluded)** + +| Nominal central frequencies (THz) for spacings of 50 GHz | Nominal central frequencies (THz) for spacings of 100 GHz and above | Nominal central wavelengths (nm) | +|-----------------------------------------------------------------|----------------------------------------------------------------------------|-----------------------------------------| +| 192.80 | 192.80 | 1554.94 | +| 192.75 | – | 1555.34 | +| 192.70 | 192.70 | 1555.75 | +| 192.65 | – | 1556.15 | +| 192.60 | 192.60 | 1556.55 | +| 192.55 | – | 1556.96 | +| 192.50 | 192.50 | 1557.36 | +| 192.45 | – | 1557.77 | +| 192.40 | 192.40 | 1558.17 | +| 192.35 | – | 1558.58 | +| 192.30 | 192.30 | 1558.98 | +| 192.25 | – | 1559.39 | +| 192.20 | 192.20 | 1559.79 | +| 192.15 | – | 1560.20 | +| 192.10 | 192.10 | 1560.61 | + +NOTE – The endpoints of this table are illustrative only. Future evolutions of multichannel systems are anticipated to include frequencies beyond those limits. + +# ANNEX B + +## Alternative optical supervisory channel approaches + +Two amplifiers operating with different OSC wavelengths will not, in general, be transverse compatible. + +## **B.1 OSC at 1480 nm** + +The wavelength should be $1480 \pm 10$ nm ( $202.6 \pm 1.4$ THz). + +This approach is the same as for single channel systems. + +## **B.2 OSC in 1310 nm band** + +This approach is the same as for single channel systems. The boundaries of this wavelength range are for further study. + +## **B.3 OSC within EDFA gain bandwidth** + +The in-band OSC option is aimed for applications that are carrying several wavelengths through one or more line amplifiers at the greatest feasible distances between amplifiers, and with large channel capacity. For these applications, the EDFAs are making use of their maximum pump powers, while staying within the constraints of pump laser reliability. + +# APPENDIX I + +## Methodology for derivation of optical power levels + +This Appendix provides further information on the choice of maximum and minimum channel optical power, as well as the maximum total power. + +### I.1 Channel power + +#### I.1.1 Minimum channel power + +This Appendix describes a methodology which can be used to derive the end-of-life minimum channel optical power that is required to maintain a desired Optical Signal-to-Noise Ratio (OSNR). In order to relate the OSNR to a BER, the detection process must be taken into account, which will be different for amplified and non-amplified systems. The relationship to the BER is a receiver characteristic, which is not yet included in the design methodology. The resulting minimum channel optical output power is independent of the number of channels (i.e. wavelengths) and can be used for both single and multiple channel systems. This methodology is of principal interest for systems with line, but can also be applied to systems using pre-amplifiers. + +This Appendix describes how ASE effects limit the minimum channel optical power for both single and multiple channel optically amplified systems. + +The ASE power per unit frequency interval for an optical amplifier is given by: + +$$P_{ASE} = 2N_{SP}(G-1)h\nu \quad (I-1)$$ + +where $N_{SP} \geq 1$ is the spontaneous noise factor, $G$ is the internal gain, $h$ is Planck's constant and $\nu$ is the optical frequency. The external amplifier noise figure is given (in dB) by: + +$$NF = 10 \text{ Log} \left[ 2N_{SP} - \frac{2N_{SP} - 1}{G} \right] + \eta_{IN} \quad (I-2)$$ + +where $\eta_{IN}$ is the input coupling loss for the amplifier in dB. If we make the simplifying assumptions that the total output power (including accumulated ASE power) is equal after each amplifier, and that the gain $G \gg 1$ , then the optical signal-to-noise ratio is given approximately by: + +$$OSNR = P_{out} - L - NF - 10 \text{ Log } N - 10 \text{ Log}[h\nu\Delta\nu_0] \quad (I-3)$$ + +where $P_{out}$ is the output power (per channel) in dBm, $L$ is the span loss between amplifiers in dB, $NF$ is the external noise figure in dB, $\Delta\nu_0$ is the optical bandwidth, $N$ is the number of spans in the chain, and we have assumed that all the span losses are equal. In the 1.55 $\mu\text{m}$ band, $10 \text{ Log}(h\nu\Delta\nu_0) = -58 \text{ dBm}$ at 0.1 nm optical bandwidth. This approach could still be applied in a system where the span losses differ, by assuming that all losses are equal to or less than $L$ , and would yield a worst-case estimate of the OSNR. + +The above relationship provides a practical and useful prediction, since the OSNR at the input to the receiver (point $R_n$ in Figure 1) is the result of an r.m.s. average of $N$ effective noise sources, such that small differences in span losses on output powers tend to average out. The $G \gg 1$ assumption is true for most amplified systems. + +Equation (I-3) can be used to estimate the minimum optical power ( $P_{out}$ ) that is required to maintain a desired OSNR. This minimum output power would be measured at the output of the amplifiers as indicated by point $S'$ in Figure 1. Since it is a limit on the minimum power (per channel) and is independent of the number of channels, it can be used for both single and multiple channel systems. + +In the case where individual channel powers vary, if all channel powers are greater than or equal to the minimum power, then all OSNRs will also be greater than or equal to the minimum required value. + +In a real WDM system, the output powers channel will probably not be equal because of unequal gain, and the noise figures may also differ among the amplifiers and among the channels. In addition, the span losses will likely not be equal. Nevertheless, equation (I-3) is useful in the establishment of minimum channel optical power levels because only the worst-case needs to be considered (i.e. all span losses are equal to their highest value, and considering the channel with the lowest output power). + +#### **I.1.2 Maximum channel power** + +Limitations on maximum optical power levels can be based on either fibre non-linear effects or laser safety considerations. If the maximum total output power (including ASE) is fixed at the Class 3A laser limit, $P_{3A}$ , then the maximum nominal channel power, $P_{chmax}$ , is related to the channel number as given in: + +$$P_{chmax} = P_{3A} - 10 \text{ Log}(M), \quad (I-4)$$ + +where $M$ is the number of channels in operation. This equation is given for illustrative purposes, since output power may vary among individual channels as long as the total output power is less than $P_{3A}$ . This limitation would be valid for systems with and without line amplifiers as described in this Recommendation. + +In some cases, fibre non-linearities impose more restrictive limits on output power level than laser safety considerations. In particular, Self Phase Modulation (SPM), Cross-Phase Modulation (XPM) and Stimulated Brillouin Scattering (SBS) place limits on the maximum channel power. The limits on optical power level imposed by SPM and SBS are independent of the number of channels present and, in the case of SPM, only systems on G.652 and G.655 fibre will be affected. However, XPM affects only Multichannel systems and is more significant for systems that adopt narrow channel spacings. The impairments from XPM are more significant in G.652 fibre systems, relative to G.653 and G.655 fibre systems. Maximum permitted channel output powers due to SPM-imposed or XPM-imposed limitations will vary between application codes, and depends on the number of spans and the span target distance. + +The limits on maximum channel optical power introduced by SBS are for further study and are not considered here. Four-Wave Mixing (FWM) affects only Multichannel systems and does not present a practical limitation in G.652 or G.655 fibre systems. Stimulated Raman Scattering also does not present a practical limitation to the Multichannel systems on G.652 fibres as described in this Recommendation. The impact of Stimulated Raman Scattering on some Multichannel systems with unequal channel spacing using G.653 fibre is also for further study. + +#### **I.1.3 Maximum range for channel power** + +The three power level limits as defined in I.1.1 and I.1.2 define the maximum range for channel power levels. The minimum channel power is independent of the number of channels present, whereas the maximum channel power depends on the number of channels present. As an example, for eight channels present, the maximum level is determined by the safety limit, whereas for one channel present, the maximum level will be dictated by the SPM limit applicable for the application code. A relatively high channel power is obtained when only few channels are present, whereas the channel power would drop to a lower level when channels are being added. This, however, depends on the OFA implementation. + +### I.2 Maximum total power + +The total required output power from the optical amplifiers can be estimated by: + +$$P_{tot} = \sum P_{out} + N \cdot BW_{eff} \cdot h\nu \cdot 10^{(NF+L)/10} \quad (I-5)$$ + +Here, NF and L are given in dBs, and all other terms in linear units. The last term is the total accumulated ASE power and $BW_{eff}$ is the effective ASE bandwidth defined as total ASE power divided by the ASE power density. This bandwidth is about 20-30 nm for one amplifier, and about 15 nm for a chain of up to 10 amplifiers, as long as the signal gain is close to the maximum spectral gain of the amplifier. This approximation is sufficient as long as the total power is dominated by the signal power. + +# APPENDIX II + +## Selection of the minimum channel spacing and grid reference frequency for the WDM plan + +This Appendix contains a summary of the discussions leading to the 100 GHz, and subsequently 50 GHz, channel spacing and some information associated with choosing an Absolute Frequency Reference (AFR). + +### II.1 50 GHz/100 GHz spacing and 193.10 THz reference + +The grid reference frequency of 193.10 THz was chosen in part to not give preference to an Absolute Frequency Reference (AFR) based on any particular substance (selection of a particular AFR will vary for different applications). However, the value of 193.10 THz is in proximity of several AFR lines. + +A minimum channel spacing of 100 GHz, and subsequently 50 GHz, was chosen based on the following considerations: + +First, it was agreed that the channel spacing should be a multiple of 25 GHz. It was determined that a 100 GHz, and subsequently 50 GHz, minimum channel spacing provides the flexibility for meeting various G.692 application requirements. Multiples of the minimum channel spacing can meet these requirements with respect to usable EDFA gain spectrum and capacity. + +Technology limits (i.e. filter and source tolerances) for determining a minimum channel spacing were discussed. This approach tries to make the best use of technology and not impose limitations associated with specific applications. Minimum channel spacings based on this consideration were 125 GHz and 150 GHz. The choice of 100 GHz, and subsequently 50 GHz, as a minimum channel spacing in light of these technology projections suggests that these spacings may be achievable for only a subset of G.692 applications. + +### II.2 Absolute frequency reference (AFR) + +It is an optical frequency reference that provides an optical signal with frequency accuracy maintained at (\*) or better, and with frequency stability maintained at (\*) or better, both with verification to an ideal frequency standard such as each national standard or those recommended by the International Committee for Weights and Measures (CIPM), including an iodine-stabilised He-Ne and a methane stabilised He-Ne. + +AFR's can be used for the following applications: + +- 1) to calibrate WDM test equipment; +- 2) to provide a frequency reference for fabrication and calibration of WDM devices; + +- 3) to directly provide reference frequency to Multichannel systems; +- 4) to control and/or maintain optical-source frequencies. + +The requirements for an AFR can be expressed both in frequency and vacuum wavelength. + +NOTE – Numerical values indicated by (\*) are under study. + +#### II.2.1 AFR accuracy + +The long-term frequency offset of an AFR signal from its ideal frequency (where long term implies the period of the expected operation time of the AFR). + +NOTE – Frequency accuracy includes possible frequency changes due to temperature and humidity changes and other environmental changes. Setability, reproducibility and traceability to an ideal frequency standard are also included. + +#### II.2.2 AFR stability + +For further study. + +# APPENDIX III + +## Suggested channel frequency allocations for applications on G.652/G.655 fibres + +Table III.1 illustrates some suggested channel central frequency choices on either G.652 or G.655 fibres. + +**Table III.1/G.692 – Suggested channel central frequency choices for applications on G.652/G.655 fibres** + +| Frequency in THz | 100 GHz spacing (8 channels or more) | 200 GHz spacing (4 channels or more) | 400 GHz spacing (4 channels only) | | 500/400 GHz spacing (8 channels only) | 600 GHz spacing (4 channels only) | 1000 GHz spacing (4 channels only) | Wavelength in vacuum in nm | +|------------------|--------------------------------------|--------------------------------------|-----------------------------------|--|---------------------------------------|-----------------------------------|------------------------------------|----------------------------| +| 196.1 | * | * | | | | | | 1528.77 | +| 196.0 | * | | | | | | | 1529.55 | +| 195.9 | * | * | | | | | | 1530.33 | +| 195.8 | * | | | | | | | 1531.12 | +| 195.7 | * | * | | | | | | 1531.90 | +| 195.6 | * | | | | | | | 1532.68 | +| 195.5 | * | * | | | | * | * | 1533.47 | +| 195.4 | * | | | | | | | 1534.25 | +| 195.3 | * | * | | | * | | | 1535.04 | +| 195.2 | * | | | | | | | 1535.82 | +| 195.1 | * | * | | | | | | 1536.61 | +| 195.0 | * | | | | | | | 1537.40 | +| 194.9 | * | * | | | | * | | 1538.19 | +| 194.8 | * | | | | * | | | 1538.98 | +| 194.7 | * | * | | | | | | 1539.77 | +| 194.6 | * | | | | | | | 1540.56 | + +**Table III.1/G.692 – Suggested channel central frequency choices +for applications on G.652/G.655 fibres (concluded)** + +| Frequency
in THz | 100 GHz
spacing
(8 channels
or more) | 200 GHz
spacing
(4 channels
or more) | 400 GHz
spacing
(4 channels
only) | | 500/400
GHz
spacing
(8 channels
only) | 600 GHz
spacing
(4 channels
only) | 1000 GHz
spacing
(4 channels
only) | Wavelength
in vacuum
in nm | +|---------------------|-----------------------------------------------|-----------------------------------------------|--------------------------------------------|---|---------------------------------------------------|--------------------------------------------|---------------------------------------------|----------------------------------| +| 194.5 | * | * | | | | | * | 1541.35 | +| 194.4 | * | | | | | | | 1542.14 | +| 194.3 | * | * | | | * | * | | 1542.94 | +| 194.2 | * | | | | | | | 1543.73 | +| 194.1 | * | * | | | | | | 1544.53 | +| 194.0 | * | | | | | | | 1545.32 | +| 193.9 | * | * | * | | * | | | 1546.12 | +| 193.8 | * | | | | | | | 1546.92 | +| 193.7 | * | * | | * | | * | | 1547.72 | +| 193.6 | * | | | | | | | 1548.51 | +| 193.5 | * | * | * | | | | * | 1549.32 | +| 193.4 | * | | | | * | | | 1550.12 | +| 193.3 | * | * | | * | | | | 1550.92 | +| 193.2 | * | | | | | | | 1551.72 | +| 193.1 | * | * | * | | | * | | 1552.52 | +| 193.0 | * | | | | * | | | 1553.33 | +| 192.9 | * | * | | * | | | | 1554.13 | +| 192.8 | * | | | | | | | 1554.94 | +| 192.7 | * | * | * | | | | | 1555.75 | +| 192.6 | * | | | | | | | 1556.55 | +| 192.5 | * | * | | * | * | * | * | 1557.36 | +| 192.4 | * | | | | | | | 1558.17 | +| 192.3 | * | * | * | | | | | 1558.98 | +| 192.2 | * | | | | | | | 1559.79 | +| 192.1 | * | * | | | * | | | 1560.61 | + +# APPENDIX IV + +## **Suggested channel frequency allocations for applications on G.653 fibres** + +Table IV.1 illustrates some suggested channel central frequency choices for applications on G.653 fibre. Some applications may be limited by Four-Wave Mixing if equal channel spacing is used. One way to mitigate this limitation is to use unequal channel spacing. One method of unequal channel spacing is described in further detail in Appendix V. Another potential way to mitigate this limitation is to combine channel choices with bidirectional WDM transmission, as mentioned in Appendix VII. + +**Table IV.1/G.692 – Suggested channel central frequency choices +for 4- or 8-channel applications on G.653 fibres** + +| Frequency in THz | 100 GHz spacing (8 channels or more) | 200 GHz spacing (4 channels or more) | Alternate 200 GHz spacing (4 or 8 channels) 25 GHz offset | Alternate 200 GHz spacing (4 or 8 channels) 50 GHz offset | Wavelength in vacuum in nm | +|------------------|-------------------------------------------|--------------------------------------|-----------------------------------------------------------|-----------------------------------------------------------|----------------------------| +| | Unequal spacing on nominal frequency grid | | Unequal spacing by offset from nominal frequency grid | | | +| 196.1 | * | | | | 1528.77 | +| 196.0 | * | | | | 1529.55 | +| 195.9 | * | * | | | 1530.33 | +| 195.8 | * | | | | 1531.12 | +| 195.7 | * | * | | | 1531.90 | +| 195.6 | * | | | | 1532.68 | +| 195.5 | * | * | | | 1533.47 | +| 195.4 | * | | | | 1534.25 | +| 195.3 | * | * | | | 1535.04 | +| 195.2 | * | | | | 1535.82 | +| 195.1 | * | * | | | 1536.61 | +| 195.0 | * | | | | 1537.40 | +| 194.9 | * | * | | | 1538.19 | +| 194.8 | * | | | | 1538.98 | +| 194.7 | * | * | | | 1539.77 | +| 194.6 | * | | | | 1540.56 | +| 194.5 | * | * | | (194.45) | 1541.35 | +| 194.4 | * | | | | 1542.14 | +| 194.3 | * | * | | (194.2) | 1542.94 | +| 194.2 | * | | | | 1543.73 | +| 194.1 | * | * | | | 1544.53 | +| 194.0 | * | | | | 1545.32 | +| 193.9 | * | * | * | | 1546.12 | +| 193.8 | * | | | | 1546.92 | +| 193.7 | * | * | (193.675) | * | 1547.72 | +| 193.6 | * | | | | 1548.51 | +| 193.5 | * | * | (193.525) | | 1549.32 | +| 193.4 | * | | | | 1550.12 | +| 193.3 | * | * | (193.35) | * | 1550.92 | +| 193.2 | * | | | | 1551.72 | +| 193.1 | * | * | * | * | 1552.52 | +| 193.0 | * | | | | 1553.33 | +| 192.9 | * | * | * | | 1554.13 | +| 192.8 | * | | | | 1554.94 | + +**Table IV.1/G.692 – Suggested channel central frequency choices +for 4- or 8-channel applications on G.653 fibres (concluded)** + +| Frequency in THz | 100 GHz spacing (8 channels or more) | 200 GHz spacing (4 channels or more) | Alternate 200 GHz spacing (4 or 8 channels) 25 GHz offset | Alternate 200 GHz spacing (4 or 8 channels) 50 GHz offset | Wavelength in vacuum in nm | +|------------------|-------------------------------------------|--------------------------------------|-----------------------------------------------------------|-----------------------------------------------------------|----------------------------| +| | Unequal spacing on nominal frequency grid | | Unequal spacing by offset from nominal frequency grid | | | +| 192.7 | * | * | (192.625) | (192.75) | 1555.75 | +| 192.6 | * | | | | 1556.55 | +| 192.5 | * | * | * | (192.45) | 1557.36 | +| 192.4 | * | | | | 1558.17 | +| 192.3 | * | * | | * | 1558.98 | +| 192.2 | * | | | | 1559.79 | +| 192.1 | * | * | | | 1560.61 | + +# APPENDIX V + +## A channel-allocation methodology for applications on G.653 fibre based on unequal channel spacing + +### Introduction + +The transmission distance of multichannel systems over G.653 fibre is known to be severely restricted by Four-Wave Mixing (FWM) when channels are equally allocated in frequency. However, this restriction can be mitigated when, for example, the channels are unequally allocated. (See Appendix II, and 3.2/G.663 for further information). + +Figure V.1 a) shows an example of signal frequencies allocated at equal spacing and resultant FWM optical powers, in which some FWM optical powers overlap the signal optical power thus degrading the transmission performance. Figure V.1 b) shows an example for unequal spacing, where unwanted overlap is avoided. This Appendix provides a channel-allocation methodology for G.653 fibres based on unequal channel spacing. + +NOTE – The applicability of this methodology was confirmed up to 12 channels, although the text is described mostly for an 8-channel system. + +![Figure V.1/G.692 shows two diagrams illustrating FWM optical power generated by three signals. Diagram (a) shows FWM optical power generated by three equally spaced signals (CH1, CH2, CH3). Diagram (b) shows FWM optical power generated by three unequally spaced signals. Both diagrams plot optical frequency on the x-axis and signal power on the y-axis. In (a), the signals are equally spaced, and the FWM products (f113, f112, f213, f123, f223, f132, f312, f221, f231, f332, f321, f331) are shown as distinct peaks. In (b), the signals are unequally spaced, and the FWM products are shown as distinct peaks, with some products (f132, f312) and (f321, f231) appearing as doublets.](48a08e5cabec8b75386679d8a57dec3e_img.jpg) + +a) FWM optical power generated by three equally spaced signals + +b) FWM optical power generated by three unequally spaced signals + +T1527260-97 + +Figure V.1/G.692 shows two diagrams illustrating FWM optical power generated by three signals. Diagram (a) shows FWM optical power generated by three equally spaced signals (CH1, CH2, CH3). Diagram (b) shows FWM optical power generated by three unequally spaced signals. Both diagrams plot optical frequency on the x-axis and signal power on the y-axis. In (a), the signals are equally spaced, and the FWM products (f113, f112, f213, f123, f223, f132, f312, f221, f231, f332, f321, f331) are shown as distinct peaks. In (b), the signals are unequally spaced, and the FWM products are shown as distinct peaks, with some products (f132, f312) and (f321, f231) appearing as doublets. + +**Figure V.1/G.692 – An Example of signal frequencies and resultant FWM optical powers** + +### V.1 How to determine unequally-spaced channel frequencies + +#### V.1.1 Basic design conditions + +Firstly, it is necessary to meet the following two conditions. + +(1-1) Unequally-spaced channel frequencies should, as many as possible, be on the 100 GHz grid given in Annex A. If some channel frequencies cannot be on the grid, they should be within the range of the temperature control of lasers that meet the grid. + +Condition (1-1) aims to commonly use optical sources both in equally-spaced multichannel systems on G.652 and G.655 fibres and, in unequally-spaced multichannel systems on G.653 fibres. + +(1-2) Each unequally-spaced channel frequency should be chosen such that no new optical power generated by FWM fall into any optical signal channel. + +To meet (1-2), the channel spacing of any two channels must be different from that of any other pair of channels [1]. This is because the original signal frequencies $f_i$ , $f_j$ and $f_k$ and resultant FWM optical power frequency $f_{ijk}$ are linked by the following equation: + +$$f_{ijk} - f_i = f_j - f_k \quad (i, j \neq k) \quad (\text{V-1})$$ + +To practically select signal frequencies, "frequency slot"s denoted as " $f_s$ "s are to be used. In addition, each channel spacing is set to an integer multiple of $f_s$ ( $f_s \times n_i$ , $i = 1, 2, \dots, N - 1$ , where $N$ is the number of channels), while ensuring that all channel spacing is different. Then, $f_s$ is equal to the minimum frequency difference between FWM optical powers and optical signals. The set of the integers $n_i$ should be selected to minimise the optical bandwidth that accommodates all signals. + +Examples of sets of integers $n_i$ for 8-channel systems that satisfy condition (1-2) are shown in Table V.1 and in reference [1]. + +**Table V.1/G.692 – Sets of $n_i$ for unequally spaced 8-channel allocation** + +| Minimum $n_i$ | Sets of $n_i$ which minimise total optical bandwidth | Number of sets | Number of slots ( $\sum n_i$ ) | Examples | +|---------------|------------------------------------------------------|----------------|--------------------------------|--------------------| +| 1 | 1,2,3,5,6,7,10 | 2 | 34 | (1,3,5,6,7,10,2) | +| 2 | 2,3,4,5,7,8,10 | 2 | 39 | (2,4,10,3,8,7,5) | +| | 2,3,4,5,6,8,11 | 2 | | (3,6,11,5,2,8,4) | +| | 2,3,4,5,6,9,10 | 4 | | (2,6,5,10,4,3,9) | +| | 2,3,4,5,6,7,12 | 14 | | (3,7,12,2,6,5,4) | +| | 2,3,4,6,7,8,9 | 2 | | (3,2,8,4,7,9,6) | +| 3 | 3,4,5,6,7,8,10 | 10 | 43 | (3,6,7,4,8,10,5) | +| 4 | 4,5,6,7,8,9,10 | 76 | 49 | (8,9,7,6,5,10,4) | +| 5 | 5,6,7,8,9,10,11 | 206 | 56 | (9,6,7,10,8,11,5) | +| 6 | 6,7,8,9,10,11,12 | 506 | 63 | (6,7,8,9,10,12,11) | + +In addition to (1-1), (1-2), the following condition (1-3) needs to be considered. + +(1-3) Sum of the frequency differences between each unequally spaced frequency and the nearest grid frequency should be minimum. + +#### V.1.2 Determination of frequency slot + +To determine signal frequencies, the minimum value of frequency slot should be first found out. To understand how to clarify the optimum "minimum frequency slot" 10 Gbit/s, three-channel transmission is simulated as shown in Figure V.2 a). + +It is assumed that the three channels are externally modulated. The calculated penalty values against frequency slot are shown in Figure V.2 b) for the BER of $10^{-12}$ . The result indicates that frequency slot should be $>20$ GHz for penalties of $<0.5$ dB. + +![Diagram showing four optical channels (CH1, CH2, CH3, CH4) on an optical frequency axis. CH1, CH2, and CH3 are spaced by 1.2 nm, 1.0 nm, and 1.2 nm respectively. An 'Optical Filter' is shown for CH4, with a frequency difference 'fs' between the FWM optical power and the channel. The Zero-Dispersion Frequency is marked between CH2 and CH3.](183007754364096b2d89f42200cf870f_img.jpg) + +fs: Frequency difference between FWM light and channel 4 + +Diagram showing four optical channels (CH1, CH2, CH3, CH4) on an optical frequency axis. CH1, CH2, and CH3 are spaced by 1.2 nm, 1.0 nm, and 1.2 nm respectively. An 'Optical Filter' is shown for CH4, with a frequency difference 'fs' between the FWM optical power and the channel. The Zero-Dispersion Frequency is marked between CH2 and CH3. + +![Schematic of the experimental setup. Three lasers (LD1, LD2, LD3) are connected to an optical coupler. The output passes through a 20 km DSF (Dispersion Shifted Fibre). A fourth laser (LD4) is connected via an attenuator (ATT) to the main line. The signal then passes through another attenuator (ATT) and an optical pre-amplifier (Optical Pre-amp) before being received by a receiver.](399a5af4f606059626c92c92279d54b7_img.jpg) + +Schematic of the experimental setup. Three lasers (LD1, LD2, LD3) are connected to an optical coupler. The output passes through a 20 km DSF (Dispersion Shifted Fibre). A fourth laser (LD4) is connected via an attenuator (ATT) to the main line. The signal then passes through another attenuator (ATT) and an optical pre-amplifier (Optical Pre-amp) before being received by a receiver. + +| | | +|------------------------------------|-----------------------------------------| +| Fibre loss | 0.22 dB/km | +| Dispersion Slope | 0.07 ps/km/nm/nm | +| Non-linear Refractive Index, $n_2$ | $2.7 \times 10^{-20}$ m 2 /W | +| Effective Area, $A_{eff}$ | 50 μm 2 | + +a) + +![Graph showing Penalty at BER = 10^-12 versus fs [GHz] for different Optical Filter FWHM values (40 GHz, 60 GHz, 80 GHz). The penalty decreases as fs increases, and is lower for larger filter FWHM values. Fibre Input Power/CH = 6.0 dBm.](7848a2560bb726462c09c09bf727d81d_img.jpg) + +| fs [GHz] | Penalty (40 GHz FWHM) | Penalty (60 GHz FWHM) | Penalty (80 GHz FWHM) | +|----------|-----------------------|-----------------------|-----------------------| +| 5 | 3.4 | 3.1 | 3.0 | +| 10 | 0.8 | 0.7 | 0.6 | +| 15 | 0.4 | 0.5 | 0.6 | +| 20 | 0.2 | 0.3 | 0.4 | +| 30 | 0.1 | 0.2 | 0.3 | +| 40 | 0.1 | 0.1 | 0.2 | +| 50 | 0.1 | 0.1 | 0.1 | + +Graph showing Penalty at BER = 10^-12 versus fs [GHz] for different Optical Filter FWHM values (40 GHz, 60 GHz, 80 GHz). The penalty decreases as fs increases, and is lower for larger filter FWHM values. Fibre Input Power/CH = 6.0 dBm. + +b) + +**Figure V.2/G.692 – Penalty Versus fs** + +Furthermore, when each optical signal frequency fluctuates by $\Delta f$ , the frequency difference is reduced by $4\Delta f$ , in the worst case as is understood from Equation V-1. If the source frequency fluctuation is suppressed to less than 1 GHz by using a frequency stabilisation [2], the frequency difference between the optical signal and the nearest FWM optical power is reduced from 24 GHz to 20 GHz in the worst case as is understood from Equation V-1. Since the best frequency stability achievable with conventional technologies today is $\sim 1$ GHz, it is concluded that a quarter of the 100 GHz grid spacing, or 25 GHz, is suitable as the minimum frequency slot. + +#### V.1.3 Required optical bandwidth for unequally spaced frequency allocation + +The required optical bandwidth for each frequency slot is shown in Figure V.3. The required optical bandwidth can be calculated from Table V.1. + +![Figure V.3/G.692 – Required optical bandwidth. A line graph showing Required optical bandwidth [nm] on the y-axis (0 to 40) versus Minimum slot number (n1) on the x-axis (1 to 6). The graph includes lines for 100 GHz Slot, 50 GHz Slot, 25 GHz Slot, and EDFA Bandwidth. The 100 GHz Slot line increases from ~27 nm at n1=1 to ~40 nm at n1=4. The 50 GHz Slot line increases from ~13 nm at n1=1 to ~25 nm at n1=6. The 25 GHz Slot line increases from ~6 nm at n1=1 to ~12 nm at n1=6. The EDFA Bandwidth is a horizontal line at ~31 nm. A horizontal line at ~11.2 nm is labeled '200 GHz x 8'. A horizontal line at ~10 nm is labeled 'Minimum frequency spacing = 100 GHz'. The text 'T1527280-97' is in the bottom right corner.](24b549c0c4b79c515b244625cf4f4978_img.jpg) + +| Minimum slot number ( $n_1$ ) | 100 GHz Slot [nm] | 50 GHz Slot [nm] | 25 GHz Slot [nm] | EDFA Bandwidth [nm] | 200 GHz $\times$ 8 [nm] | +|-------------------------------|-------------------|------------------|------------------|---------------------|-------------------------| +| 1 | 27 | 13 | 6 | 31 | 11.2 | +| 2 | 31 | 15 | 7 | 31 | 11.2 | +| 3 | 34 | 17 | 8 | 31 | 11.2 | +| 4 | 40 | 20 | 9 | 31 | 11.2 | +| 5 | - | 22 | 11 | 31 | 11.2 | +| 6 | - | 25 | 12 | 31 | 11.2 | + +Figure V.3/G.692 – Required optical bandwidth. A line graph showing Required optical bandwidth [nm] on the y-axis (0 to 40) versus Minimum slot number (n1) on the x-axis (1 to 6). The graph includes lines for 100 GHz Slot, 50 GHz Slot, 25 GHz Slot, and EDFA Bandwidth. The 100 GHz Slot line increases from ~27 nm at n1=1 to ~40 nm at n1=4. The 50 GHz Slot line increases from ~13 nm at n1=1 to ~25 nm at n1=6. The 25 GHz Slot line increases from ~6 nm at n1=1 to ~12 nm at n1=6. The EDFA Bandwidth is a horizontal line at ~31 nm. A horizontal line at ~11.2 nm is labeled '200 GHz x 8'. A horizontal line at ~10 nm is labeled 'Minimum frequency spacing = 100 GHz'. The text 'T1527280-97' is in the bottom right corner. + +**Figure V.3/G.692 – Required optical bandwidth** + +### V.2 Unequally spaced channel frequency allocation with 25 GHz frequency slot + +The design conditions for an unequally spaced frequency allocation with 25 GHz slot are as follows: + +(2-1) The occupied optical bandwidth should be less than that of an 8-channel WDM system with 200 GHz equal channel spacing (11.2 nm) so that optical amplifiers with the same gain bandwidth can be used. + +(2-2) The minimum frequency spacing is 125 GHz. + +The widest minimum frequency spacing should be selected within the allowable optical bandwidth so as to reduce the pump depletion effect due to FWM. As shown in Figure V.3 GHz ( $25 \text{ GHz} \times 5$ ) is suitable for the minimum channel spacing in this case. + +(2-3) Channel spacing is determined according to $25 \text{ GHz} \times M$ ( $M = 5, 6, 7, 8, 9, 10, 11$ ) to put all channels in the optical bandwidth of 11.2 nm. An integral set which satisfies the design condition (1-2) and (1-3) is selected. There are 206 combinations that satisfy the design condition. + +(2-4) The maximum frequency difference between each unequally spaced frequency and the nearest 200 GHz grid frequency should be less than 75 GHz so that the unequally spaced frequencies can be tuned from the nearest 200 GHz grid frequency by controlling only the temperature. + +### V.3 Unequally spaced channel frequency allocation with 50 GHz frequency slot + +The design conditions for unequally spaced frequency allocation with the 50 GHz slot are as follows: + +(3-1) The optical signal wavelength should be less than 1560 nm, and occupied optical bandwidth should be less than 20 nm so that wideband $\text{Er}^{3+}$ doped optical fibre amplifiers can be used [3]. + +(3-2) The minimum frequency spacing is 150 GHz ( $50 \text{ GHz} \times 3$ ). + +As mentioned in (2-2) of subclause V.2, a minimum frequency spacing of more than 100 GHz is suitable. + +(3-3) Channel spacing is determined according to $50 \text{ GHz} \times M$ ( $M = 3, 4, 5, 6, 7, 8, 10$ ) to minimise optical total bandwidth and satisfy the design conditions shown in V.1. + +### V.4 Unequal channel frequency allocation with 100 GHz frequency slot + +The design conditions for an unequally spaced frequency allocation with 100 GHz slot are as follows: + +(4-1) All optical signal wavelengths should lie in the range from 1530 nm to 1561 nm so that $\text{Er}^{3+}$ doped fluoride fibre amplifiers can be used. + +(4-2) The optical signal should not fall into the wavelength range around 1549 nm because $\text{Er}^{3+}$ doped fluoride fibre amplifiers have a gain dip around this region. + +(4-3) The minimum frequency spacing is 200 GHz. + +There is no allocation that satisfies design conditions (4-1) and (4-2), if 100 GHz is selected as the minimum frequency spacing. Therefore, 200 GHz is more suitable as the minimum frequency spacing. + +(4-4) Channel spacing is determined according to $100 \text{ GHz} \times M$ [ $M = (2, 3, 4, 5, 7, 8, 10)$ , $(2, 3, 4, 5, 6, 8, 11)$ , $(2, 3, 4, 5, 6, 9, 10)$ , $(2, 3, 4, 5, 6, 7, 12)$ , $(2, 3, 4, 6, 7, 8, 9)$ ] to minimise optical total bandwidth and satisfy design condition (4-2) and (4-3). + +### V.5 Impacts of unequal spacing on other parameters + +#### V.5.1 Frequency deviation for unequal spacing with frequency offset + +As mentioned in subclause V.1, the minimum frequency slot should be more than 20 GHz when 10 Gbit/s is assumed as the transmission bit-rate. This means that the minimum frequency difference between an optical signal and the nearest FWM optical power should be more than 2.0 times the bit-rate when there is no frequency deviation. Furthermore, when each optical signal frequency fluctuates $\Delta f$ , the frequency difference is reduced by $4\Delta f$ . Therefore, allowable frequency deviation is given by: + +$$\Delta f \leq \frac{f_s - 2.0 B}{4} \quad (\text{V-1})$$ + +where $f_s$ is the frequency slot. + +When the transmission bit-rate is 2.5 Gbit/s, the allowable frequency deviation is as is shown in Table V.2. + +**Table V.2/G.692 – Allowable frequency deviation (2.5 Gbit/s)** + +| Frequency slot | 25 | 50 | 100 | +|-------------------------------|-----|----|-----| +| Maximum Central | | | | +| Frequency Deviation $\pm$ GHz | 4-5 | 11 | 23 | + +#### V.5.2 Power Levels + +Unequal spacing will lead to limitation of the maximum fibre input power. Details are for further study. + +### V.6 Bibliography + +- [1] FORGHERI (F.), TKACH (R.W.), CHRAPLYVY (A.R.), MARCUSE (D.): Reduction of Four-Wave Mixing Crosstalk in WDM Systems Using Unequally Spaced Channels, *IEEE Photon. Technol. Lett.*, Vol. 6, No. 6, pp. 754-756, 1994. + +- [2] ODA (K.), TOBA (H.), NOSU (K.): Long Term Laboratory Test of a Fully-Engineered 128 Channel Optical FDM Distribution System, in *ECOC'93, paper TuP4.3*, pp. 117-120, 1993. +- [3] KASHIWADA (T.), NAKAZATO (K.), OHNISHI (M.), KANAMORI (H.), NISHIMURA (M.): Spectral Gain Behavior of Er-doped Fibre with Extremely High Aluminum Concentration, *OAA '93, MA6-1*, 1993. + +# APPENDIX VI + +## Use of pre-equalisation at MPI-S + +Pre-equalisation can be used at interface MPI-S to increase the amount of line amplifier gain variation and gain tilt that can be tolerated by a system while still maintaining a certain level of maximum channel power difference. This in turn ensures that amplifier designs and wavelength plans are not overly constrained. + +Pre-equalisation partially compensates amplifier gain variation and gain tilt using the following scheme. The highest channel power at MPI-S is assigned to the channel that will undergo the least line amplifier gain, whereas the lowest channel power at MPI-S is assigned to the channel that will undergo the most channel line amplifier gain. Apart from specifying the maximum difference between any two channel powers at MPI-S, the channel power variation is also specified. This bounds the power variation at MPI-S of any particular channel and the channel dependent loss ranges associated with the optical paths between the transmitter interfaces $S_1-S_n$ and MPI-S. Pre-equalisation is most readily applicable to mitigating tolerances that have a systematic variation. + +If pre-equalisation is not used, the amount of channel power difference at the transmit interface MPI-S leads to a reduction in the amount of amplifier gain variation and gain tilt that can be tolerated by the system. Therefore, in this case, one has to minimise the amount of channel power difference at MPI-S. + +# APPENDIX VII + +## Extension of G.692 to include bidirectional WDM transmission + +Unidirectional WDM is the transmission of all optical channels on a fibre propagating simultaneously in the same direction (see Figure VII.1). Bidirectional WDM is the transmission of optical channels on a fibre propagating simultaneously in both directions (see Figure VII.2). + +![Diagram of Unidirectional WDM transmission showing multiple optical channels (λ1, λ2, λ3, ..., λN) entering a system from the left, passing through a rectangular block, and exiting to the right through another rectangular block. The channels are labeled on both sides of the blocks. A small label 'T1527290-97' is visible below the right block.](9ff1b32449ea068bba9647d71904bd59_img.jpg) + +The diagram illustrates unidirectional WDM transmission. On the left, multiple input lines labeled $\lambda 1$ , $\lambda 2$ , $\lambda 3$ , and $\lambda N$ (with vertical dots between $\lambda 3$ and $\lambda N$ ) enter a vertical rectangular block. A single horizontal line connects the right side of this block to the left side of a second vertical rectangular block. From the right side of the second block, multiple output lines emerge, also labeled $\lambda 1$ , $\lambda 2$ , $\lambda 3$ , and $\lambda N$ with corresponding vertical dots. Below the second block, the text 'T1527290-97' is present. + +Diagram of Unidirectional WDM transmission showing multiple optical channels (λ1, λ2, λ3, ..., λN) entering a system from the left, passing through a rectangular block, and exiting to the right through another rectangular block. The channels are labeled on both sides of the blocks. A small label 'T1527290-97' is visible below the right block. + +**Figure VII.1/G.692 – Unidirectional WDM** + +![Diagram of Bidirectional WDM showing two WDM components connected by a single fiber. On the left, multiple wavelengths (λ1, λ2, λ3, ..., λN) enter the first WDM component. On the right, the same wavelengths exit the second WDM component. Arrows indicate the direction of light flow: λ1, λ3, and λN enter from the left and exit to the right; λ2 and λN exit to the left and enter from the right. The diagram is labeled T1527300-97.](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +Diagram of Bidirectional WDM showing two WDM components connected by a single fiber. On the left, multiple wavelengths (λ1, λ2, λ3, ..., λN) enter the first WDM component. On the right, the same wavelengths exit the second WDM component. Arrows indicate the direction of light flow: λ1, λ3, and λN enter from the left and exit to the right; λ2 and λN exit to the left and enter from the right. The diagram is labeled T1527300-97. + +**Figure VII.2/G.692 – Bidirectional WDM** + +In general, bidirectional WDM can lead to a reduction in the number of fibres and line amplifiers required as compared to systems using unidirectional WDM. A further benefit of bidirectional WDM may be performance improvement with respect to Four-Wave Mixing (FWM), particularly when being deployed with G.653 fibres. + +Bidirectional WDM design must take into consideration several key systems issues. Care must be taken to optical reflections in order to avoid Multi Path Interference (MPI). Some additional considerations are types and values of crosstalk, values and interdependence of power levels for both directions of transmission, OSC transmission, and automatic power shutdown. Details are for further study. + +Full specification of bidirectional WDM in this Recommendation may require additional application codes to be defined, as well as a modification of some existing and addition of new parameter definitions. + +# APPENDIX VIII + +## Extension of G.692 to include 16- and 32- or more channel transmission + +With respect to market needs, the scope of G.692 has been extended to multichannel long-haul line systems with 16 and 32 or more channels. This extension has an impact on parameters and its values in the main part of G.692, for example, on: + +- number and allocation of frequencies needed; +- frequency spacings; +- achievable total distances; and +- maximum nominal optical channel power, + +which may lead to additional application codes. + +The suggested channel central frequencies in Tables III.1 and IV.1 can be used to allocate 16 or 32 channels, for example: + +- 16 channels with 100 GHz or 200 GHz spacing; or +- 32 channels with 100 GHz spacing. + +In addition to central frequencies and frequency spacings, other optical parameters and the associated values for 16- and 32- or more (possibly with 50 GHz spacing) channel systems must be defined, which are for further study. + +# APPENDIX IX + +## **Extension of G.692 to include STM-64 bit-rate** + +With respect to market requirements, the scope of G.692 has been extended to multichannel long-haul systems with STM-64 (10 Gbit/s) bit-rate. This extension has an impact on parameters and its values in the main part of G.692, for example, on: + +- achievable total distances of multichannel systems for STM-64; and +- dispersion accommodation technique, + +which may lead to additional application codes. + +STM-64 WDM systems on G.652 fibres require a dispersion accommodation technique for all STM-64 application codes. + + + +# 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.693-200911-I_PDF-E/raw.md b/marked/G/T-REC-G.693-200911-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..685b90ddcb133a47e80545f348e2978ca7755658 --- /dev/null +++ b/marked/G/T-REC-G.693-200911-I_PDF-E/raw.md @@ -0,0 +1,748 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.693** + +(11/2009) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Transmission media and optical systems characteristics – +Characteristics of optical systems + +# --- Optical interfaces for intra-office systems + +Recommendation ITU-T G.693 + +## 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.693** + +# **Optical interfaces for intra-office systems** + +## **Summary** + +Recommendation ITU-T G.693 provides parameters and values for optical interfaces of single channel intra-office systems of nominal 10 Gbit/s and 40 Gbit/s aggregate bit rate. Applications are specified with target distances of 0.6 and 2 km and various loss budgets for ITU-T G.652, ITU-T G.653 and ITU-T G.655 fibres. The latest version makes use of improved specifications for chromatic dispersion of these fibre types. + +## **Source** + +Recommendation ITU-T G.693 was approved on 13 November 2009 by ITU-T Study Group 15 (2009-2012) under Recommendation ITU-T A.8 procedures. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2010 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|--------------------------------------------------------------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Terms and definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Classification of optical interfaces..... | 2 | +| 5.1 Applications..... | 2 | +| 5.2 Nomenclature ..... | 3 | +| 6 Parameter definitions..... | 6 | +| 6.1 System operating wavelength range..... | 6 | +| 6.2 Transmitter ..... | 6 | +| 6.3 Optical path ..... | 8 | +| 6.4 Receiver ..... | 10 | +| 7 Optical parameter values ..... | 11 | +| 8 Optical engineering approach ..... | 20 | +| Appendix I – Optical crosstalk impact..... | 21 | +| Appendix II – Examples of system configurations using applications defined in this
Recommendation ..... | 22 | +| Appendix III – Differences in parameter values between ITU-T G.693 application codes
and equivalent ITU-T G.691 and ITU-T G.959.1 codes ..... | 23 | + + + +## Recommendation ITU-T G.693 + +# Optical interfaces for intra-office systems + +# 1 Scope + +The purpose of this Recommendation is to provide optical interface specifications to enable transverse (multivendor) compatibility of nominal 10 Gbit/s and 40 Gbit/s aggregate bit rate intra-office systems for link distances up to 2 km. This Recommendation defines links using optical fibres according to [ITU-T G.652], [ITU-T G.653] and [ITU-T G.655]. + +Parallel interface specifications may be included in future revisions. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.652] Recommendation ITU-T G.652 (2005), *Characteristics of a single-mode optical fibre and cable*. +- [ITU-T G.653] Recommendation ITU-T G.653 (2006), *Characteristics of a dispersion-shifted single-mode optical fibre and cable*. +- [ITU-T G.655] Recommendation ITU-T G.655 (2006), *Characteristics of a non-zero dispersion-shifted single-mode optical fibre and cable*. +- [ITU-T G.691] Recommendation ITU-T G.691 (2006), *Optical interfaces for single channel STM-64 and other SDH systems with optical amplifiers*. +- [ITU-T G.709] Recommendation ITU-T G.709/Y.1331 (2003), *Interfaces for the Optical Transport Network (OTN)*. +- [ITU-T G.957] Recommendation ITU-T G.957 (2006), *Optical interfaces for equipments and systems relating to the synchronous digital hierarchy*. +- [ITU-T G.959.1] Recommendation ITU-T G.959.1 (2008), *Optical transport network physical layer interfaces*. +- [ITU-T G.8251] Recommendation ITU-T G.8251 (2001), *The control of jitter and wander within the optical transport network (OTN)*. + +# 3 Terms and definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **completely standardized OTUk (OTUK)**: [ITU-T G.709]. +- 3.1.2 **optical tributary signal class NRZ 10G (NRZ 10G)**: [ITU-T G.959.1]. +- 3.1.3 **optical tributary signal class NRZ 40G (NRZ 40G)**: [ITU-T G.959.1]. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|--------------------------------| +| ASE | Amplified Spontaneous Emission | +| BER | Bit Error Ratio | +| DGD | Differential Group Delay | +| EX | Extinction ratio | +| FEC | Forward Error Correction | +| ffs | for further study | +| MLM | Multi-Longitudinal Mode | +| MPI | Main Path Interface | +| MPN | Mode Partition Noise | +| NA | Not Applicable | +| NRZ | Non-Return to Zero | +| ORL | Optical Return Loss | +| PMD | Polarization Mode Dispersion | +| PRBS | Pseudo-Random Binary Sequence | +| RMS | Root Mean Square | +| SDH | Synchronous Digital Hierarchy | +| SLM | Single-Longitudinal Mode | +| SMSR | Side Mode Suppression Ratio | +| VSR | Very Short Reach | +| WDM | Wavelength Division Multiplex | + +# 5 Classification of optical interfaces + +## 5.1 Applications + +This Recommendation defines optical interfaces for single-channel intra-office systems for link distances up to 2 km. These interface descriptions are intended to enable transverse (multivendor) compatibility. Figure 1 illustrates a system of the type considered in this Recommendation, and shows the reference points used to specify optical interface parameters. + +![Diagram of an optical link showing a Transmitter and a Receiver connected by a main optical path. Reference points MPI-S and MPI-R are marked on the path between the two components.](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) + +The diagram shows a 'Transmitter' block on the left and a 'Receiver' block on the right, connected by a horizontal line representing the optical path. A vertical tick mark on the transmitter side is labeled 'MPI-S', and another on the receiver side is labeled 'MPI-R'. A double-headed arrow below the line, spanning between these two points, is labeled 'Main optical path'. In the bottom right corner of the diagram area, the text 'G.693(05-06)\_F01' is present. + +Diagram of an optical link showing a Transmitter and a Receiver connected by a main optical path. Reference points MPI-S and MPI-R are marked on the path between the two components. + +NOTE – The main optical path includes fibre and connectors, and may include other passive optical devices such as photonic cross-connects. + +**Figure 1 – Optical link example showing reference points defined in this Recommendation** + +Parameters are specified for the transmitter at point MPI-S, for the receiver at point MPI-R, and for the main optical path between points MPI-S and MPI-R. + +The main optical path for systems described in this Recommendation may include passive optical devices, e.g., photonic cross-connects, which introduce significant attenuation. Thus, values of maximum attenuation may not be inferred from the target distances of applications. In this Recommendation, attenuation categories are used to distinguish among applications which have the same source and fibre type and target distance, and are intended for the same signal class, but have different values of maximum attenuation. Four attenuation categories are defined with maximum attenuation values of 4 dB, 6 dB, 12 dB and 16 dB, respectively. A fifth category is defined (with a maximum attenuation value for further study) in case the maximum attenuation value provided by the H category is too low to cover all applications. + +Appendix II shows examples of system configurations using applications defined in this Recommendation. + +## 5.2 Nomenclature + +Applications in this Recommendation are distinguished by application codes. Each code indicates the target distance, highest class of optical tributary signal supported, attenuation category and source and fibre type of the associated application. + +Application codes have the following structure: + +- W-yAz + +where: + +W indicates target distance: + +- VSR600, VSR1000 and VSR2000, indicating target distances of 0.6 km, 1 km and 2 km, respectively. + +y indicates highest class of optical tributary signal supported: + +- 2 indicating NRZ 10G. +- 3 indicating NRZ 40G. + +A indicates attenuation category: + +- R indicating maximum attenuation of 4 dB. +- L indicating maximum attenuation of 6 dB. +- M indicating maximum attenuation of 12 dB. +- H indicating maximum attenuation of 16 dB. +- V indicating maximum attenuation of ffs dB. + +The V category has been introduced in case the maximum attenuation value provided by the H category is too low to cover all applications. + +z indicates the source and fibre type: + +- 1 indicating nominally 1310 nm sources on ITU-T G.652 fibre; +- 2 indicating nominally 1550 nm sources on ITU-T G.652 fibre; +- 3 indicating nominally 1550 nm sources on ITU-T G.653 fibre; +- 5 indicating nominally 1550 nm sources on ITU-T G.655 fibre. + +For some application codes, the suffix F is added at the end of the code, to indicate that this application requires FEC bytes as specified in [ITU-T G.709] to be transmitted. + +Tables 1 and 2 summarize the application codes described in this Recommendation. + +**Table 1 – Classification of optical interfaces with 0.6 km target distance** + +| Target distancea) | 0.6 km | | | +|--------------------------------------------------------------|---------------|-------------|-------------------------------------------| +| Attenuation categorya) | R | M | | +| Source nominal wavelength (nm) | 1310 | 1310 | 1550 | +| Type of fibre | ITU-T G.652 | ITU-T G.652 | ITU-T G.652
ITU-T G.653
ITU-T G.655 | +| Application codes for optical tributary signal class NRZ 10G | VSR600-2R1 | VSR600-2M1 | VSR600-2M2
VSR600-2M3
VSR600-2M5 | +| Application codes for optical tributary signal class NRZ 40G | – | – | – | + +a) Target distances and attenuation categories are for classification and not for specification. + +**Table 2 – Classification of optical interfaces with 2 km target distance** + +| Target distancea) | 2 km | | | | | | | +|--------------------------------------------------------------|-----------------------------|-------------------------------------------------------------------------------------------|--------------|----------------------------------------------|-------------|-------------------------------------------|-------------------------------------------| +| Attenuation categorya) | R | | L | | M | | H | +| Source nominal wavelength (nm) | 1310 | 1550 | 1310 | 1550 | 1310 | 1550 | 1550 | +| Type of fibre | ITU-T G.652 | ITU-T G.652
ITU-T G.653
ITU-T G.655 | ITU-T G.652 | ITU-T G.652
ITU-T G.653
ITU-T G.655 | ITU-T G.652 | ITU-T G.652
ITU-T G.653
ITU-T G.655 | ITU-T G.652
ITU-T G.653
ITU-T G.655 | +| Application codes for optical tributary signal class NRZ 10G | VSR2000-2R1 | – | VSR2000-2L1F | VSR2000-2L2
VSR2000-2L3
VSR2000-2L5 | – | – | – | +| Application codes for optical tributary signal class NRZ 40G | VSR2000-3R1
VSR2000-3R1F | VSR2000-3R2
VSR2000-3R3
VSR2000-3R5
VSR2000-3R2F
VSR2000-3R3F
VSR2000-3R5F | VSR2000-3L1F | VSR2000-3L2F
VSR2000-3L3F
VSR2000-3L5F | VSR2000-3M1 | VSR2000-3M2
VSR2000-3M3
VSR2000-3M5 | VSR2000-3H2
VSR2000-3H3
VSR2000-3H5 | + +a) Target distances and attenuation categories are for classification and not for specification. + +# 6 Parameter definitions + +All parameter values are worst-case values, assumed to be met over the range of standard operating conditions (i.e., temperature and humidity ranges), and they include ageing effects. The parameters are specified relative to an optical section design objective of a bit error ratio (BER) not worse than $10^{-12}$ for any combination of parameters within the ranges given in the tables for each specified system. Except for application codes requiring FEC bytes to be transmitted (i.e., having a code with a suffix of F), achieving this BER objective shall not require the application of forward error correction. In the case of application codes requiring FEC bytes to be transmitted, the BER is required to be met only after the correction (if used) has been applied. + +The optical line coding used for system interfaces in this Recommendation is binary non-return to zero (NRZ). + +## 6.1 System operating wavelength range + +The operating wavelength range is the maximum allowable range for the source wavelength. Within this range, the source wavelength can be selected for different fibre-related impairments. The receiver must have the minimum operating wavelength range that corresponds to the maximum allowable range for the source wavelength. + +The operating wavelength range of fibre-optic transmission systems is basically determined by the attenuation and dispersion characteristics of the various fibre and source types. A detailed discussion of these aspects can be found in [ITU-T G.957]. + +NOTE – When a wavelength-fixed or tuneable filter to eliminate amplified spontaneous emission (ASE) is used before the receiver, the operating wavelength band may be limited, and the transverse compatibility may not be guaranteed. + +## 6.2 Transmitter + +### 6.2.1 Source type + +Depending on attenuation/dispersion characteristics and hierarchical level of each application code, feasible transmitter devices include multi-longitudinal mode (MLM) lasers and single-longitudinal mode (SLM) lasers. For each of the applications, this Recommendation indicates a nominal source type. It is understood that the indication of a nominal source type in this Recommendation is not a requirement and that SLM devices can be substituted for any application showing MLM as the nominal source type without any degradation in system performance. + +### 6.2.2 Spectral characteristics + +#### 6.2.2.1 Maximum RMS width + +The maximum root mean square (RMS) width or the standard deviation $\sigma$ (in nm) of the spectral distribution of a multi-longitudinal mode (MLM) laser considers all laser modes, which are not more than 20 dB down from the peak mode. Only a system with an MLM laser at 1310 nm requires this specification. + +#### 6.2.2.2 Maximum –20 dB width + +The maximum –20 dB spectral width (in nm) of an SLM laser is specified by the maximum full width of the central wavelength peak, measured 20 dB down from the maximum amplitude of the central wavelength under standard operating conditions. + +#### 6.2.2.3 Side mode suppression ratio + +The side mode suppression ratio (SMSR) is defined as the ratio of the largest peak of the total source spectrum to the second largest peak. The spectral resolution of the measurement shall be better (i.e., the optical filter bandwidth shall be less) than the maximum spectral width of the peak, as defined above. The second largest peak may be next to the main peak or far removed from it. + +NOTE – Within this definition, spectral peaks that are separated from the largest peak by the clock frequency are not considered to be side modes. + +The SMSR specification is intended to minimize the occurrence of BER degradations due to mode partition noise (MPN). Since MPN is a transient effect with low probability, SMSR measurements on PRBS or continuous signals may underestimate the MPN. The SMSR specification is relevant only to SLM laser sources. + +### 6.2.3 Maximum mean output power + +The maximum mean output power is the maximum value of the average power of a pseudo-random data sequence coupled into fibre by the transmitter. + +### 6.2.4 Minimum mean output power + +The minimum mean output power is the minimum value of the average power of a pseudo-random data sequence coupled into fibre by the transmitter. + +### 6.2.5 Extinction ratio + +The extinction ratio (EX) is defined as: + +$$EX = 10 \times \log_{10}(A/B)$$ + +In the above definition of EX, A is the average optical power level at the centre of a logical "1" and B is the average optical power level at the centre of a logical "0". The convention adopted for optical logic levels is: + +- emission of light for a logical "1"; +- no emission for a logical "0". + +### 6.2.6 Eye pattern mask + +In this Recommendation, general transmitter pulse shape characteristics including rise time, fall time, pulse overshoot, pulse undershoot, and ringing, all of which should be controlled to prevent excessive degradation of the receiver sensitivity, are specified in the form of a mask of the transmitter eye diagram at point MPI-S. For the purpose of an assessment of the transmit signal, it is important to consider not only the eye opening, but also the overshoot and undershoot limitations. The parameters specifying the mask of the transmitter eye diagram are shown in Figure 2. + +Acceptable transmitter eye diagrams must avoid crossing any of the hatched lines. The test arrangement is as specified for STM-64 in Annex A of [ITU-T G.691]. Filter tolerances for the NRZ 10G optical reference receiver are as specified for STM-64 in Annex A of [ITU-T G.691]. Filter tolerances for a NRZ 40G optical reference receiver are for further study. + +![Figure 2: Mask of the eye diagram for the optical transmit signal. The diagram shows a normalized eye diagram with a vertical axis from -y4 to 1+y3 and a horizontal axis from 0 to 1. Key levels are marked: 1+y3 (top boundary), 1 (mean level of logical '1'), y2, 0.5, y1, 0 (mean level of logical '0'), and -y4 (bottom boundary). A rectangular eye mask is defined by vertical lines at x2 and x3, and horizontal lines at y1 and y2. The area between y1 and y2, and between x2 and x3, is shaded with diagonal lines. The eye opening is the unshaded area within the mask.](7c1f9e78e0f033d391b687f1652f6e47_img.jpg) + +Figure 2: Mask of the eye diagram for the optical transmit signal. The diagram shows a normalized eye diagram with a vertical axis from -y4 to 1+y3 and a horizontal axis from 0 to 1. Key levels are marked: 1+y3 (top boundary), 1 (mean level of logical '1'), y2, 0.5, y1, 0 (mean level of logical '0'), and -y4 (bottom boundary). A rectangular eye mask is defined by vertical lines at x2 and x3, and horizontal lines at y1 and y2. The area between y1 and y2, and between x2 and x3, is shaded with diagonal lines. The eye opening is the unshaded area within the mask. + +| | NRZ 10G
1310 nm
region | NRZ 10G
1550 nm
region | NRZ 40G | +|-------------|------------------------------|------------------------------|---------| +| $x_3 - x_2$ | 0.2 | 0.2 | 0.2 | +| $y_1$ | 0.25 | 0.25 | 0.25 | +| $y_2$ | 0.75 | 0.75 | 0.75 | +| $y_3$ | 0.4 | 0.25 | 0.25 | +| $y_4$ | 0.25 | 0.25 | 0.25 | + +G.693(05-06)\_F02 + +NOTE – $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. + +**Figure 2 – Mask of the eye diagram for the optical transmit signal** + +## 6.3 Optical path + +To ensure system performance for each of the applications considered in Table 1, it is necessary to specify attenuation and dispersion characteristics of the optical path between points MPI-S and MPI-R. + +### 6.3.1 Maximum attenuation + +The maximum attenuation is the maximum path attenuation where the system in question operates under end-of-life conditions at a BER of $10^{-12}$ (or as given by the application code), under worst-case transmit-side signal and dispersion. Attenuation specifications are assumed to be worst-case values, including losses due to splices, connectors, optical attenuators (if used), other passive optical devices, e.g., photonic cross-connect and any additional cable margin to cover allowances for degradation of any connectors, optical attenuators or other passive optical devices between points MPI-S and MPI-R, if used. + +### 6.3.2 Minimum attenuation + +Minimum attenuation is the minimum path attenuation that allows the system in question, operating under worst-case transmit-side conditions, to achieve a BER no worse than $10^{-12}$ (or as given by the application code). + +### 6.3.3 Dispersion + +#### 6.3.3.1 Maximum chromatic dispersion at upper and lower wavelength limit + +These two parameters define the maximum uncompensated value of the main path chromatic dispersion that the system shall be able to tolerate. + +For wavelengths between the upper and lower wavelength limits, the maximum dispersion is linearly interpolated between the values given for the wavelength extremes. Where the maximum dispersion values are the same, this value is required to be met across the entire wavelength range. + +For ITU-T G.652 fibre, the required maximum dispersion tolerance at the upper and lower wavelength limits is set to a value equal to the target distance times the maximum dispersion coefficient for ITU-T G.652 fibre at those wavelengths. For ITU-T G.653 fibre, the required maximum dispersion tolerance is set to plus or minus a value equal to the target distance times the highest absolute value of the maximum dispersion coefficient for ITU-T G.653.B fibre at the upper or lower wavelength limits. For ITU-T G.655 fibre, the required maximum dispersion tolerance at the upper and lower wavelength limits is set to a value equal to the target distance times the maximum dispersion coefficient for ITU-T G.655.E fibre at those wavelengths. + +These are considered worst-case dispersion values for the relevant fibre types. + +The maximum chromatic dispersion value includes contributions from fibre and all other elements present in the optical path. In the case that these passive optical devices introduce additional chromatic dispersion, the achievable link distance may be reduced. Alternatively, an application with a higher chromatic dispersion tolerance may be used to overcome this restriction. + +The allowed penalty for the optical path considers all deterministic effects due to chromatic dispersion as well as the penalty due to the maximum differential group delay. + +#### 6.3.3.2 Maximum differential group delay + +Differential group delay (DGD) is the time difference between the fractions of a pulse that are transmitted in the two principal states of polarization of an optical signal. More information on this topic can be found in [ITU-T G.691]. + +In this Recommendation, the maximum differential group delay is defined to be the value of DGD that the system must tolerate with a maximum sensitivity degradation of 1 dB. + +### 6.3.4 Reflections + +Reflections are caused by refractive index discontinuities along the optical path. If not controlled, they can degrade system performance through their disturbing effect on the operation of the optical source or amplifier, or through multiple reflections which lead to interferometric noise at the receiver. In this Recommendation, reflections from the optical path are controlled by specifying the: + +- minimum optical return loss (ORL) of the cable plant at point MPI-S, including any connectors; and +- maximum discrete reflectance between points MPI-S and MPI-R. + +Reflectance denotes the reflection from any single discrete reflection point, whereas the return loss is the total returned power from the entire fibre, including both discrete reflections and distributed backscattering such as Rayleigh scattering. + +Measurement methods for reflections are described in Appendix I of [ITU-T G.957]. For the purpose of reflectance and return loss measurements, points MPI-S and MPI-R are assumed to coincide with the endface of each connector plug. It is recognized that this does not include the actual reflection performance of the respective connectors in the operational system. These reflections are assumed to have the nominal value of reflection for the specific type of connectors used. + +The maximum number of connectors, or other discrete reflection points which may be included in the optical path (e.g., for distribution frames, or WDM components), must be such as to allow the specified overall optical return loss to be achieved. If this cannot be done using connectors meeting the maximum discrete reflections cited in Tables 3 and 4, then connectors having better reflection performance must be employed. Alternatively, the number of connectors must be reduced. It may also be necessary to limit the number of connectors, or to use connectors having improved reflectance performance in order to avoid unacceptable impairments due to multiple reflections. + +In Tables 3 and 4, the value of $-27$ dB maximum discrete reflectance between points MPI-S and MPI-R is intended to minimize the effects of multiple reflections (e.g., interferometric noise). The value for maximum receiver reflectance is chosen to ensure acceptable penalties due to multiple reflections for all likely system configurations involving multiple connectors, etc. Systems employing fewer or higher performance connectors produce fewer multiple reflections and, consequently, are able to tolerate receivers exhibiting higher reflectance. + +## 6.4 Receiver + +### 6.4.1 Sensitivity + +Receiver sensitivity is defined as the minimum value of mean received power at point MPI-R to achieve a $1 \times 10^{-12}$ BER. This must be met with a transmitter with worst-case values of transmitter eye mask, extinction ratio, optical return loss at point MPI-S, receiver connector degradations and measurement tolerances. The definition of receiver sensitivity under worst-case conditions is further discussed in Annex A of [ITU-T G.691]. + +The receiver sensitivity does not have to be met in the presence of dispersion, optical crosstalk or reflections. These effects are specified separately in the allocation of maximum optical path penalty. + +NOTE – The receiver sensitivity does not have to be met in the presence of transmitter jitter in excess of the appropriate jitter generation limit (e.g., [ITU-T G.8251] for OTN optical tributary signals). + +The receiver sensitivities specified in Tables 3 and 4 are worst-case, end-of-life values. Start-of-life sensitivities must be adequate to account for receiver ageing and environmental conditions. + +### 6.4.2 Overload + +Receiver overload is the maximum acceptable value of the received average power at point MPI-R for a $1 \times 10^{-12}$ BER. + +### 6.4.3 Path penalty + +The path penalty is the apparent reduction of receiver sensitivity due to distortion of the signal waveform during its transmission over the path. It is manifested as a shift of the system's BER-curves towards higher input power levels. This corresponds to a positive path penalty. Negative path penalties may exist under some circumstances, but should be small (a negative path penalty indicates that a less than perfect transmitter eye has been partially improved by the path dependent distortions). Ideally, the BER-curves should only be translated, but shape variations are not uncommon, and may indicate the emergence of BER-floors. Since the path penalty is a change in the receiver's sensitivity, it is measured at a BER-level of $10^{-12}$ . + +For application codes requiring FEC bytes to be transmitted (i.e., having a code with a suffix of F), both receiver sensitivities (with and without the degradation due to the optical path) are measured after the error correction (if used) has been applied. + +A maximum path penalty of 1 dB for low-dispersion systems is allowed. The path penalties are not made proportional to the target distances to avoid operating systems with high penalties. + +The average value of the random dispersion penalties due to PMD is included in the allowed path penalty. In this respect, the transmitter/receiver combination is required to tolerate an actual DGD of 0.3 bit period with a maximum sensitivity degradation of 1 dB (with 50% of optical power in each principal state of polarization). For a well-designed receiver, this corresponds to a penalty of 0.1-0.2 dB for a DGD of 0.1 bit period. The actual DGD that may be encountered in operation is a randomly varying fibre/cable property, and cannot be specified in this Recommendation. This subject is further discussed in Appendix I of [ITU-T G.691]. + +Any additional sensitivity degradation due to optical crosstalk (e.g., caused by non-ideal switching) is assumed to be small enough to be included within the path penalty value. Cases where this is not true are for further study. Optical crosstalk penalty is further discussed in Appendix I. + +# 7 Optical parameter values + +Optical parameter values for applications shown in Tables 1 and 2 are given in Tables 3 to 6. Except for application codes requiring FEC bytes to be transmitted (i.e., having a code with a suffix of F), systems which comply with these values should not require forward error correction in order to satisfy BER objectives. In the case of application codes requiring FEC bytes to be transmitted, the BER is required to be met only after the correction (if used) has been applied. + +Tables 3 to 6 include columns in which more than one application code is shown in the heading. Where the row entries in these columns contain a single value, it applies to all of the application codes. Where the row contains multiple entries, the values apply to the application codes in the same order as they appear in the column heading. + +For those applications which were previously specified in [ITU-T G.691] or [ITU-T G.959.1], any differences between ITU-T G.693 parameter values and the values in the superseded [ITU-T G.691] and [ITU-T G.959.1] application codes are given in Appendix III. + +**Table 3 – Optical interface parameters specified for applications with 0.6 km target distance** + +| Application code | Unit | VSR600-2R1 | VSR600-2M1 | VSR600-2M2
VSR600-2M3
VSR600-2M5 | +|---------------------------------------------|------|------------|------------|----------------------------------------| +| ITU-T G.691 application code | | I-64.1r | | | +| ITU-T G.959.1 application code | | PII1-2D1r | | | +| Target distance | m | 600 | 600 | 600 | +| Bit rate/line coding of optical signals | – | NRZ 10G | NRZ 10G | NRZ 10G | +| Fibre type | – | G.652 | G.652 | G.652
G.653
G.655 | +| Transmitter at reference point MPI-S | | | | | +| Source type | | MLM | MLM | SLM | +| Operating wavelength range | nm | 1268-1360 | 1268-1360 | 1530-1565 | +| Maximum mean output power | dBm | –1 | +5 | +2 | +| Minimum mean output power | dBm | –6 | +2 | –1 | +| Spectral characteristics: | | | | | +| – maximum RMS width ( $\sigma$ ) | nm | 3 | 3 | NA | +| – maximum –20 dB width | nm | NA | NA | ffs | +| – minimum SMSR | dB | NA | NA | 30 | + +**Table 3 – Optical interface parameters specified for applications +with 0.6 km target distance** + +| Application code | Unit | VSR600-2R1 | VSR600-2M1 | VSR600-2M2
VSR600-2M3
VSR600-2M5 | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------|-----------------|----------------------------------------------------------------| +| Minimum EX | dB | 6 | 6 | 8.2 | +| Main optical path, MPI-S to MPI-R | | | | | +| Maximum attenuation | dB | 4 | 12 | 12 | +| Minimum attenuation | dB | 0 | 6 a) | 3 a) | +| Maximum chromatic dispersion at upper wavelength limit b) | ps/nm | ±3.4 | ±3.4 | 11.3 for G.652 c)
±2 for G.653
+6.1 for G.655 | +| Maximum chromatic dispersion at lower wavelength limit | ps/nm | ±3.4 | ±3.4 | 10.1 for G.652 c)
±2 for G.653
+5.0 for G.655 | +| Maximum DGD | ps | 30 | 30 | 30 | +| Minimum ORL of cable plant at MPI-S, including any connectors | dB | 14 | 14 | 14 | +| Maximum discrete reflectance between MPI-S and MPI-R | dB | -27 | -27 | -27 | +| Polarization-dependent loss | dB | ffs | ffs | ffs | +| Receiver at reference point MPI-R | | | | | +| Minimum sensitivity (BER of $1 \times 10^{-12}$ ) | dBm | -11 | -11 | -14 | +| Minimum overload | dBm | -1 | -1 | -1 | +| Maximum optical path penalty | dB | 1 | 1 | 1 | +| Maximum reflectance of receiver, measured at MPI-R | dB | -14 | -14 | -14 | +| a) This value of minimum attenuation is highly undesirable. A value of 0 dB is desired and should be sought as technology matures. | | | | | +| b) In the case that passive optical devices in the main optical path introduce additional chromatic dispersion, the achievable link distance may be reduced. Alternatively, an application with a higher chromatic dispersion tolerance may be used to overcome this restriction. | | | | | +| c) This application can also be used on ITU-T G.653 and ITU-T G.655 fibre. | | | | | + +**Table 4 – Optical interface parameters specified for applications with 2 km target distance and attenuation category R** + +| Application code | Unit | VSR2000-2R1 | VSR2000-3R1 d) | VSR2000-3R1F d, f) | VSR2000-3R2 e)
VSR2000-3R3 d)
VSR2000-3R5 d) | VSR2000-3R2F e, f)
VSR2000-3R3F d, f)
VSR2000-3R5F d, f) | +|------------------------------------------------|------|-------------|---------------------------|-------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| ITU-T G.691 application code | | I-64.1 | | | | | +| ITU-T G.959.1 application code | | P111-2D1 | | | | | +| Target distance | km | 2 | 2 | 2 | 2 | 2 | +| Bit rate/line coding of optical signals | – | NRZ 10G | NRZ 40G | NRZ OTU3
FEC enabled | NRZ 40G | NRZ OTU3
FEC enabled | +| Fibre type | – | G.652 | G.652 | G.652 | G.652
G.653
G.655 | G.652
G.653
G.655 | +| Transmitter at reference point MPI-S | | | | | | | +| Source type | | SLM | SLM | SLM | SLM | SLM | +| Operating wavelength range | nm | 1290-1330 | 1290-1330 | 1290-1330 | 1530-1565 | 1530-1565 | +| Maximum mean output power | dBm | –1 | +3 | +3 | +3 | +3 | +| Minimum mean output power | dBm | –6 | 0 | 0 | 0 | 0 | +| Spectral characteristics: | | | | | | | +| – maximum RMS width ( $\sigma$ ) | nm | NA | NA | NA | NA | NA | +| – maximum –20 dB width | nm | 1 | ffs | ffs | ffs | ffs | +| – minimum SMSR | dB | 30 | 35 | 35 | 35 | 35 | +| Minimum EX | dB | 6 | 8.2 | 8.2 | 8.2 | 8.2 | + +**Table 4 – Optical interface parameters specified for applications with 2 km target distance and attenuation category R** + +| Application code | Unit | VSR2000-2R1 | VSR2000-3R1 d) | VSR2000-3R1F d, f) | VSR2000-3R2 e)
VSR2000-3R3 d)
VSR2000-3R5 d) | VSR2000-3R2F e, f)
VSR2000-3R3F d, f)
VSR2000-3R5F d, f) | +|----------------------------------------------------------------------|-------|--------------|---------------------------|-------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| Main optical path, MPI-S to MPI-R | | | | | | | +| Maximum attenuation | dB | 4 | 4 | 4 | 4 | 4 | +| Minimum attenuation | dB | 0 | 0 | 0 | 0 | 0 | +| Maximum chromatic dispersion at upper wavelength limit a) | ps/nm | –6.6 to +5.3 | –6.6 to +5.3 | –6.6 to +5.3 | +38 for G.652 b)
–6.6 to +6.1 for G.653
+20.3 for G.655 | +38 for G.652 b)
–6.6 to +6.1 for G.653
+20.3 for G.655 | +| Maximum chromatic dispersion at lower wavelength limit | ps/nm | –6.6 to +5.3 | –6.6 to +5.3 | –6.6 to +5.3 | +34 for G.652 b)
–6.6 to +6.1 for G.653
+16.6 for G.655 | +34 for G.652 b)
–6.6 to +6.1 for G.653
+16.6 for G.655 | +| Maximum DGD | ps | 30 | 7.5 | 7.5 | 7.5 | 7.5 | +| Minimum ORL of cable plant at MPI-S, including any connectors | dB | 14 | 24 | 24 | 24 | 24 | +| Maximum discrete reflectance between MPI-S and MPI-R | dB | –27 | –27 | –27 | –27 | –27 | +| Polarization-dependent loss | dB | ffs | ffs | ffs | ffs | ffs | + +**Table 4 – Optical interface parameters specified for applications with 2 km target distance and attenuation category R** + +| Application code | Unit | VSR2000-2R1 | VSR2000-3R1 d) | VSR2000-3R1F d, f) | VSR2000-3R2 e)
VSR2000-3R3 d)
VSR2000-3R5 d) | VSR2000-3R2F e, f)
VSR2000-3R3F d, f)
VSR2000-3R5F d, f) | +|------------------------------------------------------|------|-------------|---------------------------|-------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| Receiver at reference point MPI-R | | | | | | | +| Minimum sensitivity
(BER of $1 \times 10^{-12}$ ) | dBm | -11 | -5 | -5 | -6 for G.652
-5 for G.653
-5 for G.655 | -6 for G.652
-5 for G.653
-5 for G.655 | +| Minimum overload | dBm | -1 | +3 | +3 | +3 | +3 | +| Maximum optical path penalty | dB | 1 | 1 c) | 1 c) | 2 c) for G.652
1 c) for G.653
1 c) for G.655 | 2 c) for G.652
1 c) for G.653
1 c) for G.655 | +| Maximum reflectance of receiver, measured at MPI-R | dB | -14 | -27 | -27 | -27 | -27 | + +a) In the case that passive optical devices in the main optical path introduce additional chromatic dispersion, the achievable link distance may be reduced. Alternatively, an application with a higher chromatic dispersion tolerance may be used to overcome this restriction. + +b) This application can also be used on ITU-T G.653 and ITU-T G.655 fibre. + +c) The method used to verify this penalty is for further study. + +d) A receiver in compliance with this application is required to operate in any of the application codes VSR2000-3R1, VSR2000-3R3 or VSR2000-3R5. It shall, as a minimum, operate over the wavelength range of 1290-1330 nm as well as the range 1530-1565 nm. + +e) A receiver in compliance with application VSR2000-3R2 will operate in either of the application codes VSR2000-3R3 or VSR2000-3R5. It will also operate in the application code VSR2000-3R1 if its operating wavelength range includes 1290-1330 nm. + +f) The BER for this application is required to be met only after the error correction (if used) has been applied. The BER at the input of the FEC decoder can, therefore, be significantly higher than $10^{-12}$ . + +**Table 5 – Optical interface parameters specified for applications with 2 km target distance and attenuation category L** + +| Application code | Unit | VSR2000-2L1F f) | VSR2000-2L2
VSR2000-2L3
VSR2000-2L5 | VSR2000-3L1F d, f) | VSR2000-3L2F e, f)
VSR2000-3L3F d, f)
VSR2000-3L5F d, f) | +|------------------------------------------------|------|----------------------------|-------------------------------------------|-------------------------------|-------------------------------------------------------------------------------------------------| +| ITU-T G.691 application code | | | I-64.2r | | | +| ITU-T G.959.1 application code | | | P111-2D2r | | | +| Target distance | km | 2 | 2 | 2 | 2 | +| Bit rate/line coding of optical signals | – | NRZ OTU2
FEC enabled | NRZ 10G | NRZ OTU3
FEC enabled | NRZ OTU3
FEC enabled | +| Fibre type | – | G.652 | G.652
G.653
G.655 | G.652 | G.652
G.653
G.655 | +| Transmitter at reference point MPI-S | | | | | | +| Source type | | SLM | SLM | SLM | SLM | +| Operating wavelength range | nm | 1290-1330 | 1530-1565 | 1290-1330 | 1530-1565 | +| Maximum mean output power | dBm | –1 | –1 | +3 | +3 | +| Minimum mean output power | dBm | –6 | –5 | 0 | 0 | +| Spectral characteristics: | | | | | | +| – maximum RMS width ( $\sigma$ ) | nm | NA | NA | NA | NA | +| – maximum –20 dB width | nm | 1 | ffs | ffs | ffs | +| – minimum SMSR | dB | 30 | 30 | 35 | 35 | +| Minimum EX | dB | 6 | 8.2 | 8.2 | 8.2 | + +**Table 5 – Optical interface parameters specified for applications with 2 km target distance and attenuation category L** + +| Application code | Unit | VSR2000-2L1F f) | VSR2000-2L2 | VSR2000-3L1F d, f) | VSR2000-3L2F e, f) | +|----------------------------------------------------------------------|-------|----------------------------|--------------------------------------------------------------------------|-------------------------------|--------------------------------------------------------------------------| +| | | | VSR2000-2L3 | | VSR2000-3L3F d, f) | +| | | | VSR2000-2L5 | | VSR2000-3L5F d, f) | +| Main optical path, MPI-S to MPI-R | | | | | | +| Maximum attenuation | dB | 6 | 6 | 6 | 6 | +| Minimum attenuation | dB | 0 | 0 | 0 | 0 | +| Maximum chromatic dispersion at upper wavelength limit a) | ps/nm | –6.6 to +5.3 | +38 for G.652 b)
–6.6 to +6.1 for G.653
+20.3 for G.655 | –6.6 to +5.3 | +38 for G.652 b)
–6.6 to +6.1 for G.653
+20.3 for G.655 | +| Maximum chromatic dispersion at lower wavelength limit | ps/nm | –6.6 to +5.3 | +34 for G.652 b)
–6.6 to +6.1 for G.653
+16.6 for G.655 | –6.6 to +5.3 | +34 for G.652 b)
–6.6 to +6.1 for G.653
+16.6 for G.655 | +| Maximum DGD | ps | 30 | 30 | 7.5 | 7.5 | +| Minimum ORL of cable plant at MPI-S, including any connectors | dB | 14 | 24 | 24 | 24 | +| Maximum discrete reflectance between MPI-S and MPI-R | dB | –27 | –27 | –27 | –27 | +| Polarization-dependent loss | dB | ffs | ffs | ffs | ffs | + +**Table 5 – Optical interface parameters specified for applications with 2 km target distance and attenuation category L** + +| Application code | Unit | VSR2000-2L1F f) | VSR2000-2L2
VSR2000-2L3
VSR2000-2L5 | VSR2000-3L1F d, f) | VSR2000-3L2F e, f)
VSR2000-3L3F d, f)
VSR2000-3L5F d, f) | +|----------------------------------------------------|------|----------------------------|-------------------------------------------|-------------------------------|-------------------------------------------------------------------------------------------------| +| Receiver at reference point MPI-R | | | | | | +| Minimum sensitivity (BER of $1 \times 10^{-12}$ ) | dBm | -13 | -13 | -7 | -8 for G.652
-7 for G.653
-7 for G.655 | +| Minimum overload | dBm | -1 | -1 | +3 | +3 | +| Maximum optical path penalty | dB | 1 | 2 | 1 c) | 2 c) for G.652
1 c) for G.653
1 c) for G.655 | +| Maximum reflectance of receiver, measured at MPI-R | dB | -14 | -27 | -27 | -27 | + +a) In the case that passive optical devices in the main optical path introduce additional chromatic dispersion, the achievable link distance may be reduced. Alternatively, an application with a higher chromatic dispersion tolerance may be used to overcome this restriction. + +b) This application can also be used on ITU-T G.653 and ITU-T G.655 fibre. + +c) The method used to verify this penalty is for further study. + +d) A receiver in compliance with this application is required to operate in any of the application codes VSR2000-3L1, VSR2000-3L3 or VSR2000-3L5. It shall, as a minimum, operate over the wavelength range of 1290-1330 nm as well as the range 1530-1565 nm. + +e) A receiver in compliance with application VSR2000-3L2 will operate in either of the application codes VSR2000-3L3 or VSR2000-3L5. It will also operate in the application code VSR2000-3L1 if its operating wavelength range includes 1290-1330 nm. + +f) The BER for this application is required to be met only after the error correction (if used) has been applied. The BER at the input of the FEC decoder can, therefore, be significantly higher than $10^{-12}$ . + +**Table 6 – Optical interface parameters specified for applications +with 2 km target distance and attenuation categories M and H** + +| Application code | Unit | VSR2000-3M1 | VSR2000-3M2
VSR2000-3M3
VSR2000-3M5 | VSR2000-3H2
VSR2000-3H3
VSR2000-3H5 | +|----------------------------------------------------------------------|-------|-----------------|--------------------------------------------------------------------------|--------------------------------------------------------------------------| +| ITU-T G.691 application code | | | | | +| ITU-T G.959.1 application code | | | | | +| Target distance | km | 2 | 2 | 2 | +| Bit rate/line coding of optical signals | – | NRZ 40G | NRZ 40G | NRZ 40G | +| Fibre type | – | G.652 | G.652
G.653
G.655 | G.652
G.653
G.655 | +| Transmitter at reference point
MPI-S
| | | | | +| Source type | | SLM | SLM | SLM | +| Operating wavelength range | nm | 1290-1330 | 1530-1565 | 1530-1565 | +| Maximum mean output power | dBm | +10 | +3 | +3 | +| Minimum mean output power | dBm | +8 | 0 | 0 | +| Spectral characteristics: | | | | | +| – maximum RMS width ( $\sigma$ ) | nm | NA | NA | NA | +| – maximum –20 dB width | nm | ffs | ffs | ffs | +| – minimum SMSR | dB | 35 | 35 | 35 | +| Minimum EX | dB | 8.2 | 7 | 7 | +| Main optical path, MPI-S to MPI-R | | | | | +| Maximum attenuation | dB | 12 | 12 | 16 | +| Minimum attenuation | dB | 8 a) | 3 a) | 3 | +| Maximum chromatic dispersion at upper wavelength limit b) | ps/nm | –6.6 to +5.3 | +38 for G.652 c)
–6.6 to +6.1 for G.653
+20.3 for G.655 | +38 for G.652 c)
–6.6 to +6.1 for G.653
+20.3 for G.655 | +| Maximum chromatic dispersion at lower wavelength limit | ps/nm | –6.6 to +5.3 | +34 for G.652 c)
–6.6 to +6.1 for G.653
+16.6 for G.655 | +34 for G.652 c)
–6.6 to +6.1 for G.653
+16.6 for G.655 | +| Maximum DGD | ps | 7.5 | 7.5 | 7.5 | +| Minimum ORL of cable plant at MPI-S, including any connectors | dB | 24 | 24 | 24 | +| Maximum discrete reflectance between MPI-S and MPI-R | dB | –27 | –27 | –27 | +| Polarization-dependent loss | dB | ffs | ffs | ffs | + +**Table 6 – Optical interface parameters specified for applications with 2 km target distance and attenuation categories M and H** + +| Application code | Unit | VSR2000-3M1 | VSR2000-3M2
VSR2000-3M3
VSR2000-3M5 | VSR2000-3H2
VSR2000-3H3
VSR2000-3H5 | +|-------------------------------------------------------|------|-----------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| Receiver at reference point MPI-R | | | | | +| Minimum sensitivity
(BER of $1 \times 10^{-12}$ ) | dBm | –5 | –14 for G.652
–13 for G.653
–13 for G.655 | –18 for G.652
–17 for G.653
–17 for G.655 | +| Minimum overload | dBm | +2 | 0 | 0 | +| Maximum optical path penalty | dB | 1 d) | 2 d) for G.652
1 d) for G.653
1 d) for G.655 | 2 d) for G.652
1 d) for G.653
1 d) for G.655 | +| Maximum reflectance of receiver,
measured at MPI-R | dB | –27 | –27 | –27 | + +a) This value of minimum attenuation is highly undesirable. A value of 0 dB is desired and should be sought as technology matures. + +b) In the case that passive optical devices in the main optical path introduce additional chromatic dispersion, the achievable link distance may be reduced. Alternatively, an application with a higher chromatic dispersion tolerance may be used to overcome this restriction. + +c) This application can also be used on ITU-T G.653 and ITU-T G.655 fibre. + +d) The method used to verify this penalty is for further study. + +# 8 Optical engineering approach + +For a worst-case design approach, the relationships among maximum/minimum mean output power, maximum/minimum attenuation, minimum overload, minimum sensitivity and maximum optical path penalty are shown in Figure 3 of [ITU-T G.957]. + +# Appendix I + +## Optical crosstalk impact + +(This appendix does not form an integral part of this Recommendation) + +Some of the applications in this Recommendation are intended to support the inclusion of a passive photonic cross-connect in the main optical path as depicted in Figure I.1. Photonic cross-connects may introduce non-negligible optical crosstalk due to non-ideal switching. + +![Figure I.1: Optical link example showing use of a passive photonic cross-connect (PXC) between MPI-S and MPI-R. The diagram shows a Transmitter connected to an MPI-S reference point, which is connected to a PXC. The PXC is connected to an MPI-R reference point, which is connected to a Receiver. The main optical path is indicated by a double-headed arrow between the MPI-S and MPI-R points. The diagram is labeled G.693(05-06)_FI.1.](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +The diagram illustrates an optical link configuration. On the left, a box labeled 'Transmitter' is connected to a vertical dashed line labeled 'MPI-S'. A solid horizontal line, representing the optical path, extends from the MPI-S line to a central box labeled 'PXC'. Inside the PXC box, there are three horizontal lines with vertical dots between them, indicating multiple optical paths. From the right side of the PXC box, another solid horizontal line extends to a second vertical dashed line labeled 'MPI-R'. From the MPI-R line, the path continues to a box labeled 'Receiver'. Below the diagram, a double-headed arrow spans the distance between the MPI-S and MPI-R lines, labeled 'Main optical path'. In the bottom right corner, the text 'G.693(05-06)\_FI.1' is present. + +Figure I.1: Optical link example showing use of a passive photonic cross-connect (PXC) between MPI-S and MPI-R. The diagram shows a Transmitter connected to an MPI-S reference point, which is connected to a PXC. The PXC is connected to an MPI-R reference point, which is connected to a Receiver. The main optical path is indicated by a double-headed arrow between the MPI-S and MPI-R points. The diagram is labeled G.693(05-06)\_FI.1. + +**Figure I.1 – Optical link example showing use of a passive photonic cross-connect (PXC) between MPI-S and MPI-R** + +Optical crosstalk is the ratio of the total disturbing power, under all specified conditions, to the power in the desired signal, at the MPI-R reference point in Figure I.1, within the optical bandwidth of the optical receiver, expressed in dB. + +Optical system performance may be affected by the level of optical crosstalk in the signal arriving at the receiver. Excessive optical crosstalk at the receiver will cause the performance of the system to deteriorate by an amount defined to be the crosstalk penalty. + +Further study is needed to quantify the allowable optical crosstalk penalty. + +# Appendix II + +## Examples of system configurations using applications defined in this Recommendation + +(This appendix does not form an integral part of this Recommendation) + +The applications defined in this Recommendation are characterized by relatively short target distances, i.e., less than or equal to 2 km. One consequence of this characteristic is that main optical path total attenuation will, in general, be dominated by the loss contributions of connectors and passive optical devices rather than by fibre loss. + +Figure II.1 shows configurations corresponding to several applications defined in this Recommendation, with different combinations of attenuation category and target distance. The figure illustrates that, in selecting an application, the choice of attenuation category is determined by the devices in the main optical path, e.g., whether or not a photonic cross-connect is present, while the choice of target distance is determined by the relative proximity of the equipments which the ITU-T G.693 interface interconnects. + +![Figure II.1: Examples of system configurations using applications defined in this Recommendation. The diagram shows four optical paths (Type A, Type B, Type C, Type D) between Building A and Building B. Type A uses ODFs only. Type B uses ODF, PXC, and ODF. Type C uses ODF and PXC. Type D uses ODF and PXC. A legend defines the components: T (G.693 transmitter), R (G.693 receiver), ODF (Optical Distribution Frame), and PXC (Photonic cross-connect). A table below defines the interface types, attenuation categories, and target distances.](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +**Legend:** + +- T G.693 transmitter +- R G.693 receiver +- ODF Optical Distribution Frame +- PXC Photonic cross-connect + +**Table:** + +| Interface | Attenuation Category(s) | Target Distance | +|-----------|-------------------------|-----------------| +| Type A | R (4 dB) | 0.6 km | +| Type B | M (12 dB) | 0.6 km | +| Type C | R (4 dB) or L (6 dB) | 2 km | +| Type D | M (12 dB) or H (16 dB) | 2 km | + +Figure II.1: Examples of system configurations using applications defined in this Recommendation. The diagram shows four optical paths (Type A, Type B, Type C, Type D) between Building A and Building B. Type A uses ODFs only. Type B uses ODF, PXC, and ODF. Type C uses ODF and PXC. Type D uses ODF and PXC. A legend defines the components: T (G.693 transmitter), R (G.693 receiver), ODF (Optical Distribution Frame), and PXC (Photonic cross-connect). A table below defines the interface types, attenuation categories, and target distances. + +Figure II.1 – Examples of system configurations using applications defined in this Recommendation + +## Appendix III + +## Differences in parameter values between ITU-T G.693 application codes and equivalent ITU-T G.691 and ITU-T G.959.1 codes + +(This appendix does not form an integral part of this Recommendation) + +Several application codes in this Recommendation are equivalent to application codes which were specified in previous versions of [ITU-T G.691] and [ITU-T G.959.1]. In some instances, the parameter values in this Recommendation differ from those in the equivalent ITU-T G.691 and ITU-T G.959.1 application codes, which are now superseded by this Recommendation. Tables III.1, III.2 and III.3 below indicate all such differences between ITU-T G.693 parameter values and corresponding values in the equivalent ITU-T G.691 and ITU-T G.959.1 application codes. + +**Table III.1 – Parameter value differences between VSR600-2R1 (this Recommendation), PII1-2D1r [ITU-T G.959.1] and I-64.1r [ITU-T G.691] application codes** + +| Application code/
Recommendation | Unit | VSR600-2R1/
G.693 | PII1-2D1r/
G.959.1 | I-64.1r/
G.691 | +|-------------------------------------|------|----------------------|-----------------------|-------------------| +| Operating wavelength range | nm | 1268-1360 | 1260-1360 | 1260-1360 | + +**Table III.2 – Parameter value differences between VSR2000-2R1 (this Recommendation) and PII1-2D1 [ITU-T G.959.1] application codes** + +| Application code/
Recommendation | Unit | VSR2000-2R1/
G.693 | PII1-2D1/
G.959.1 | +|-------------------------------------|-------|-----------------------|----------------------| +| Maximum chromatic dispersion | ps/nm | 6.6 | NA | + +**Table III.3 – Parameter value differences between VSR2000-2L2 (this Recommendation), PII1-2D2r [ITU-T G.959.1] and I-64.2r [ITU-T G.691]** + +| Application code/
Recommendation | Unit | VSR2000-2L2/
G.693 | PII1-2D2r/
G.959.1 | I-64.2r/
G.691 | +|-------------------------------------|------|-----------------------|-----------------------|--------------------| +| Operating wavelength range | nm | 1530-1565 | 1500-1580 | (same as
G.693) | +| Maximum attenuation | dB | 6 | 7 | 7 | +| Minimum sensitivity | dBm | -13 | -14 | -14 | + + + + + +# **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.698.5-202401-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.698.5-202401-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/G/T-REC-G.698.5-202401-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.698.5-202401-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/G/T-REC-G.698.5-202401-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5536f23794789a76da1c1498defca6f66966ad27 --- /dev/null +++ b/marked/G/T-REC-G.698.5-202401-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1196d9debcb9fe8269bfddeca90fa4d269660fd066dfd2b428b3b8915b3bcd13 +size 48216 diff --git a/marked/G/T-REC-G.698.5-202401-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/G/T-REC-G.698.5-202401-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c4ed03a4d81ac19c8a2463b115b92eabddc1745 --- /dev/null +++ b/marked/G/T-REC-G.698.5-202401-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e12ec7e5d6542b25a246301cdd673c3288f183350e7b0bd1d7ed6fb197e52e5b +size 45919 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0be41d051dba19cc7dbd75ba11d5fd39ef01ff43 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3eb3ce8b5ea851b42b8bb5828ed3a84be28ae2af34b57059e746507e098c04a7 +size 28297 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/035b1a67ac3f04ae2f5218c450186c9a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/035b1a67ac3f04ae2f5218c450186c9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a22c63e8c2a2f111f303dc9a1a712d93a08ec0cb --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/035b1a67ac3f04ae2f5218c450186c9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff37548a7efdeb2a61000c35a6359062da371fd747e80704c4e96cfbe2206c27 +size 23104 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/054a529346bd51a9f77b43a46b991748_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/054a529346bd51a9f77b43a46b991748_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf54df24b54430ff4ed910b9195c377726fb3f1f --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/054a529346bd51a9f77b43a46b991748_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c04679893bc31ceb3ed2f7697a8d51300096c2a0ff4e4dcd342fdfbe78aec48e +size 45002 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c18037a9976a3a0d3bd2683a50e67e8b481cc8c1 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4106e2d85cadc7835e60523854bd2dfe2b063f379ea11d481bd33b65d186efa5 +size 54601 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7956caf98497d061eb94bb008efe40cf38fdb85 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1c0eb0f1cc6061d4b17c4411da0d0785113872c4090e6b2d18790df2513a04b +size 55403 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/0ab0282f295c2fcf97b7197e7aeb1381_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/0ab0282f295c2fcf97b7197e7aeb1381_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..557d49c731ccc3696f1bf39b92028cfc57d269ee --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/0ab0282f295c2fcf97b7197e7aeb1381_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4f163b16f9809b6cb40356383221a134c9b53afac7c0c78d9bf4e42863bca6f +size 51865 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/0fdef87ff1fd322c626d1ff8df725749_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/0fdef87ff1fd322c626d1ff8df725749_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..519479f7724abfae2f9ec3ec429e276cefd76c9c --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/0fdef87ff1fd322c626d1ff8df725749_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc4e1265d851f7275ed688ec4d893c3e3434822a24c9d4f1cd4e9b703198a503 +size 38690 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/12280970bb3eea7f6fbdc08200d444c2_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/12280970bb3eea7f6fbdc08200d444c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a728aff3e7e1b88a11b61b5b29fe4fb0317c115 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/12280970bb3eea7f6fbdc08200d444c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a64d8b2cd1b3bde712019209ff60caae0966bee50d7abf3bc3985687ed25d782 +size 125533 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d6b171ef4e9cc4e7c8018992ab50ceaa37b5828 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:125c260084923b5201ce61cc5455e640166d9c3eecd3303d891e7b930a98a313 +size 57510 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b953db3cf79ff3599a39a35e811006cb4f1b7b6e --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2b2b7c0509e9d40578de32710ce67fd25325e3a61c728e46754e504fa6a1b45 +size 23287 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/1594605eb94cd26a95fcfdb0b8af86ca_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/1594605eb94cd26a95fcfdb0b8af86ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6dcc3921aaecf2b67b8433c737de5fcf26b3316 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/1594605eb94cd26a95fcfdb0b8af86ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a34b0c8a5580f295a7ca16a2f6d608eb59c7d36f1f9bcf74584ba6f43da7472d +size 113813 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/15d97ee42b0c3d8c1c45245583d67ff1_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/15d97ee42b0c3d8c1c45245583d67ff1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f393065493f95b039ce000d3b9dfc38386225037 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/15d97ee42b0c3d8c1c45245583d67ff1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a561f3599fa8736c8597d6880c204accc6d4455a3e1602d13c7d50c4425dc9fc +size 34914 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/180f1fb534ad2c1d918ede57612b3fb0_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/180f1fb534ad2c1d918ede57612b3fb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c52b39f4ff516523d610046cfc050829471c86b6 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/180f1fb534ad2c1d918ede57612b3fb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b59a37e928e73b0d2a036d64f552143dba77515336e81b007cd2892caf97f8a +size 27895 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/1b2e5b12ac4f5d7bb2fa18524982f2d8_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/1b2e5b12ac4f5d7bb2fa18524982f2d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cca9eeec99bf86d582889f18412daa01471d1700 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/1b2e5b12ac4f5d7bb2fa18524982f2d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:226d347bba3cf5270c0e3217031fea4bc24fa5e9a5f7d40c6ed62b7589161b31 +size 81393 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/1b54a9e1b22fff830f6767035580c39e_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/1b54a9e1b22fff830f6767035580c39e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0b7b8ca563a3e107716c058e4edc01e7e6b5b12 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/1b54a9e1b22fff830f6767035580c39e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1492cb63edc1750f3a99205c4f4e3ac9827071c1b1a53ccde4b4e92de87e359 +size 81557 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/1e8c50ad4fca7f315a407347dd5091cc_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/1e8c50ad4fca7f315a407347dd5091cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81d161cd931962ac6b17c8378f8d555f7ba93762 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/1e8c50ad4fca7f315a407347dd5091cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9275fccf7a2b574b1ebd539ff1a4169345157a28e4dca660231fc9baa746ae45 +size 25609 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/1f980b98800c29272e0e5ba2f6db4b98_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/1f980b98800c29272e0e5ba2f6db4b98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..961d56d53980efb21dd1a8b86b2acc2324b2c834 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/1f980b98800c29272e0e5ba2f6db4b98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a21e5f3cb326953f95963c761339e9f0b3008b2d712a1873138f18d5ad0d055 +size 66319 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/212c50c4e3d043c989037a01e13c1a98_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/212c50c4e3d043c989037a01e13c1a98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f80c2d8840ed3a7abf41eb608c2b910d628fc35d --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/212c50c4e3d043c989037a01e13c1a98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6666d31868c6efde58010f1e8b8902558726b8ba73d48e96c76c9a36bdc8d9fd +size 24011 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/21ea5add6a61cc951b5c43ddffefb3ff_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/21ea5add6a61cc951b5c43ddffefb3ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc8c322387d7b577443ab0f22b8ee3280f9f1504 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/21ea5add6a61cc951b5c43ddffefb3ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6ab4e525b49e8e6b2dad9ede5065211954606d6e2beaf26d574ca84ee03bf17 +size 103101 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/23d3bda7518a58981e82512f6f813765_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/23d3bda7518a58981e82512f6f813765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2f816b5c4a8a6b6bc04a95a8f311d0750a7b735 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/23d3bda7518a58981e82512f6f813765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87382ee5595ba3569f4cb3a6abd2cd0a5f048e93cdaa3e849ba0b1ceb084a3a8 +size 18557 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/24a89bcaba787f2bc1721356480a4a01_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/24a89bcaba787f2bc1721356480a4a01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e18f678acd5852a504205dfd7c347a2f41592da8 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/24a89bcaba787f2bc1721356480a4a01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7179624879ff5f822cae3336e605bf18589e952b75dbfff218ec7ace9dc5fb0 +size 49722 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/28e47e64ac18ca4d8924dab65cedc2d8_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/28e47e64ac18ca4d8924dab65cedc2d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9f4999b5cfefc5cfc02eff39c29ebf224ee31ce --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/28e47e64ac18ca4d8924dab65cedc2d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eba162368630cef0eca9c35a5548a05b0eeee47cf0f611879026a7dadd6419c6 +size 239640 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..415683df6ddd2876b7d83dcac33235fff47ef44f --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8577516bb854a56b7e46060b645fc8def9c24c79842ec4849825e768cebf7c37 +size 45701 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/2d51fdeaad10ae6f1707dd372d200e23_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/2d51fdeaad10ae6f1707dd372d200e23_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a53cffd2e151660bac1a150163a6aeb4d5874088 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/2d51fdeaad10ae6f1707dd372d200e23_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a82edd76e8908122ff032e4b64ebbd403529edbee553ba044760e5f5112e4780 +size 22393 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/2d548db0b26b7bf33244320322d5ee2c_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/2d548db0b26b7bf33244320322d5ee2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80b481ddc610306f90dce51067c06393b34bc602 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/2d548db0b26b7bf33244320322d5ee2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d114d29a4575715f648e5742c7d594c96b8fcb3a3e940c1af0e1b7bde9affc4 +size 45509 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/2e247f7862345a6a4b40283ed03dc643_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/2e247f7862345a6a4b40283ed03dc643_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c37dc98841244d582ce62e29190e37e6916cb18 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/2e247f7862345a6a4b40283ed03dc643_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6fdbd64365855ac931c9cd8f6087b21e4a045a699754d032e726e31d5d9e6c0 +size 79671 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..207f92942ba2468dd23619a04618e1dd2257c759 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98bd7984a78eed4c8d01ab03fac606ea18b87dec0dddc25a88d3c5aed50f0338 +size 49667 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37a76af6e2900acf0d7769b3ebe817ecc934fd9f --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4883c053af4ccb4d6a67d1c87f6fc6d8e1dee65b230066812d9832e196d59e90 +size 109543 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/3100b9f8708f586e472f3d9e44f10e52_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/3100b9f8708f586e472f3d9e44f10e52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a81b61fbea8cd267ad0701b8c3be548f88eda182 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/3100b9f8708f586e472f3d9e44f10e52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fadfe9f7599f60981ba659cbfa9aa90542332be61d77452d664342028fe2b52d +size 42327 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/330e22134db7091a48c4c2366006c0d4_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/330e22134db7091a48c4c2366006c0d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e768433da3cc2189d3206af749b64cbc2eeb1eab --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/330e22134db7091a48c4c2366006c0d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a4b5e17a3416ff7cc3e92e3f7eedddf7dcc2b81e10073a4ac9d8e62d4f15a4d +size 61072 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f64bf66b6431f49dbbed3d4c5a44d54524874770 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d848098405ce9a2997a5013d0ebd6ad905c4601a5a38d3286c1cae04f0e01ce +size 45341 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9e9230c0c538ed4758d53ab566138ab49eba1c6 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aea65c9a71b8aa661c34fe424c30bc3abc4847267cef7ab114b104643df9d140 +size 76687 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/3757cff99b0ef34e2262435d7f8f6dfd_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/3757cff99b0ef34e2262435d7f8f6dfd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..698659b16a68de781003295d1defb4e40fec1194 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/3757cff99b0ef34e2262435d7f8f6dfd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce58acb5d0855fb59967a1edd70ef4fc44d11d846e1694942c731112e250da63 +size 55537 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64f7ffee0c809f810e95c29b2bd3f78b90676bc6 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b1cd40e7c2f4e1f37e9f964d23b1625e350c12e54bbcbc4bec237384b7dc99a +size 23230 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/3af2fc22afa44863b4fdcb07aa719bc9_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/3af2fc22afa44863b4fdcb07aa719bc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbcca1401048acc2746cc6d930672199e8fc2c5a --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/3af2fc22afa44863b4fdcb07aa719bc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96b2d694db230177df85ef27f3cd6585cf828240d5a831c6c0bb1ab71bee7a77 +size 92457 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba8db1f4ef4f7947afa3cc77d69287bf06ad7cab --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85bd7c65bf1265f89b16ccaf4316be0da0b38f71303ed61209eabef79f412f17 +size 123998 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/3eb2af31c2e61e2595c8440d726f5d4e_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/3eb2af31c2e61e2595c8440d726f5d4e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d8893751cea133dd4c30d0ba5dab7682a9de044 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/3eb2af31c2e61e2595c8440d726f5d4e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4fa49edca377210f01f5c0d4826ae0a7eafc00e6f1d42925c1e698fbd31767c +size 9479 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/3f1b6583b85a3ffee7d3341f131a657c_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/3f1b6583b85a3ffee7d3341f131a657c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcb4af900a3878dc3c7e7e60d611d58e3fb243cc --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/3f1b6583b85a3ffee7d3341f131a657c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2eb5c0d35b567b850332fd1013ec8013936bcfbd719dae4b8798088453cd9564 +size 50513 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5dc5aab10885d7ee35c7e41890158d60cb4c002 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a11fb382e631cc6377a5067e91f310ee7b9c56c0c7f7cf0e904e02ac1b677e2 +size 113561 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24b6b141bcafb6049cb8d5856fa7300162d66fcd --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f4c68cca7e34160dac51f04f9bab6130690121d1068143ff1526400f1938edb +size 112253 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/42d1ffab6bbf720e8421aeace0808924_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/42d1ffab6bbf720e8421aeace0808924_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..173c0fe1aaa94a34f25e1cd1541cc5513e696fc3 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/42d1ffab6bbf720e8421aeace0808924_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88a3b4d8b65b7dd627e950e9998cf339b994b7928eb953d6ae9420f28ac8a202 +size 26548 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/47be3073a8fa63f06708058a046ad013_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/47be3073a8fa63f06708058a046ad013_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1eeb474f1c91192c20d315bba6c28562af447504 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/47be3073a8fa63f06708058a046ad013_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f82cc9b11cf6b35d8bd47da25d0c78734778645c516e92c799349676f9f4730c +size 75893 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/48090d8f1db2e826aaa740035aa12ecb_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/48090d8f1db2e826aaa740035aa12ecb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9474a420fa1477ea0350564b3198252366fae5a --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/48090d8f1db2e826aaa740035aa12ecb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5c3047d2f7e590351c30efb3e3d65a229233196f942cd5c33aada861d10b9ef +size 118211 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a04d227607fd944649d3ab937f61c9ecf3c914cf --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bf8e05b6483aa6fd4ce41a75fd8a9e501c73bf8ec6df48aed2906de394a256c +size 27020 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/4c63a0e17b54c7e61d512c276932114c_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/4c63a0e17b54c7e61d512c276932114c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38a82380a50e347b011586bb8ea2ab57fd0b19f4 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/4c63a0e17b54c7e61d512c276932114c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f64aa87290e3097bec996b640c2fa5ad42adb89c577b206b32a84c15c304e481 +size 52206 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6a66f8aa609c69cd50c486fbb6e5f3424158bfe --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bc6cca4fc5f6cf6f78280f0c6ea3b52a9c5e2fb242d8e238c62076a8e917647 +size 45426 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/524ed6dbe4bf1dd88e75c40fa79f3d4a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/524ed6dbe4bf1dd88e75c40fa79f3d4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24d226b30dbc963c034ce02941a2686b8c57ebb1 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/524ed6dbe4bf1dd88e75c40fa79f3d4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00eccf253f80ba673a062c1c273e2abf9539431593bee4d2d10de201e3a31916 +size 85148 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/53001b5ae3f65139f78db410bb41ae30_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/53001b5ae3f65139f78db410bb41ae30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b40dc2c4154bc8abe4d5a533d82805802cbc1169 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/53001b5ae3f65139f78db410bb41ae30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a419facb19a3af78918d86e2b65300c48d1c75dda9b5a01e33a272165ecbef25 +size 41682 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/537370c7a708dfe4aa0c89e075f215e4_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/537370c7a708dfe4aa0c89e075f215e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..495cfb724559423464ef81d4909ee3eb41c8f5a6 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/537370c7a708dfe4aa0c89e075f215e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a3f3f82b1b690796bbbe22d40d7349fe38d0f5136135718403bc218e4a0ba7e +size 96372 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/5432eacbc055292cc3b3da108863b835_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/5432eacbc055292cc3b3da108863b835_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c50e3cba91f4aed6185f4f1ee1e0aa3c17bca5c2 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/5432eacbc055292cc3b3da108863b835_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:411dc39a98e381b264c386f49689ec1a194847f6de0fac396006e4972c18d690 +size 14619 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/54f73f693f36dcbd300fa21ac4e410e8_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/54f73f693f36dcbd300fa21ac4e410e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcd43a79b69161424fc5e9f1baff0d847b47418d --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/54f73f693f36dcbd300fa21ac4e410e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e8d15eaec7c086ceb72a591e0ff9e47bb1a875d7f0ebbf66231a159ee2bb9db +size 149624 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/56f125e1bc127f7ac3d210407957413c_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/56f125e1bc127f7ac3d210407957413c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36470c6baf1c5aceceda0d29a04b4b20ba721390 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/56f125e1bc127f7ac3d210407957413c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db09721e80cbce576591d93968893615003ab86eaa293e8d9b012ca895fd2a82 +size 95407 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/57134800ac3a97b6212b27b93aa196ac_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/57134800ac3a97b6212b27b93aa196ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2050315954bef65a87e0cd96faca831a8879a13 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/57134800ac3a97b6212b27b93aa196ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9140f55aee4185969e345d51acd6cc0813d682877dfd623ed1055d09781a5479 +size 59255 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e07f9fcc887c3ab3270d0ce1fd6b9e547badd440 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae4912c00b1374ea03e6f68be44970891253d8494844471d6276ac5d006e2bdc +size 18815 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/5bd8085079508bb158cfc55b1007a459_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/5bd8085079508bb158cfc55b1007a459_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7615bd4952d931efe7e6d6d2163021239da4fb99 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/5bd8085079508bb158cfc55b1007a459_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19c53e0b2ee7a68c71cc6c55fb386340c44050d29a0a2ae8359bed1b5e6f75d2 +size 65747 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/5d450dd0c0bf1cda8a30b736d88d937a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/5d450dd0c0bf1cda8a30b736d88d937a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f2fc14da7ce3ff3baff376a2680b280be760150 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/5d450dd0c0bf1cda8a30b736d88d937a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a46bd44f6e63b54807825a97ea639c0f4f53a415e3b6317a2975163ea84f93d +size 8518 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/5dca16cd6224cb81fefbd38274e5eb80_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/5dca16cd6224cb81fefbd38274e5eb80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77a6623c690279fc4e40e1cae26902a4553929e7 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/5dca16cd6224cb81fefbd38274e5eb80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a681d82ba0ebad946a14c034c6f79980cd86099edc53aa3783bf1ad2e68746d0 +size 7858 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd92b3db429ce5f5ecb7bf14771bba7e52b0757e --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e12b8f650f751944e1bb5e6420ba2a442817f32f7081379d60baa5707234b60 +size 57435 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e6e3b0a34b1ee46ee9a4a2d22177cfa30b964ed --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f8f47b16305572fcbf07107bcd23ccd4f52a5d03b5bfc99e1180e9907a117ee +size 40827 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/6043644d04a0b251ad3e2ba078ae5ce4_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/6043644d04a0b251ad3e2ba078ae5ce4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82fcd480aee2955377a15cae9f8054b9562c859f --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/6043644d04a0b251ad3e2ba078ae5ce4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a1593baa08c517856867e16cfe958fd0663cd5857dda8e6f027e67eef07ca77 +size 84559 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/6059b0a3a051cc20b414d51a4e412f3e_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/6059b0a3a051cc20b414d51a4e412f3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a656e704c6358436522a35bf17a2b0e61af40d0c --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/6059b0a3a051cc20b414d51a4e412f3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb886b36c912735ed8ecc7920743522c02226fb5b3ceb52b5cb73e5d7a8525ae +size 118183 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77fde376f48b74287721af3ed0bb9a22a3c2998d --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27c52bccd3c7c19ad9ad68e6dab0664a6a19694ab9074d51ff85d14f736b858d +size 34744 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/62e9df3ad37499202f4095077606230f_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/62e9df3ad37499202f4095077606230f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e22f7969b99d394e59e7f285c507064e0ab85ce1 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/62e9df3ad37499202f4095077606230f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:529ceda0c042ba2266a802e5e330a80aab84f022152743a8d00b92ce3a54f353 +size 46202 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/669c88c4149a2add62ce1cbc7e8bb659_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/669c88c4149a2add62ce1cbc7e8bb659_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1db0483e5d480c0db6b1fde03b22bad9363c9a1 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/669c88c4149a2add62ce1cbc7e8bb659_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38eda12555060a81b59235c794344f908b98aa250b74252bd10a8bbc7611f7c8 +size 154702 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/6726e50ea08adfda77603ec4afa549e1_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/6726e50ea08adfda77603ec4afa549e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0e4729cebe1cbb5a2ed95fea1e0629b868dbec4 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/6726e50ea08adfda77603ec4afa549e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc9d57373273e42673ea96fd34094b87f6dd35339fd144df97a99f8e398e7989 +size 82786 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9c77f7909c9356a1f268f187528203afbb0bc98 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8040bc22b41051a682699c8786dfa658157e6fc4a8edd4c42614d53783324fd9 +size 41756 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/69d00e8adf9811292427fb2ce6712e39_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/69d00e8adf9811292427fb2ce6712e39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dd6a137b1f7b6773baa476b402ae9fada12b342 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/69d00e8adf9811292427fb2ce6712e39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:831ec2f1e920e6ba66683b4a40a1ef87cac251be7af5e50baa398d75df865d09 +size 50729 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..049b345fb575bce831e2a828eeeed86722d8db20 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9752106768a8f0c5670bb0268fea3ae56257326c4fbee488fa4088eac966c8c0 +size 59070 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/6f46eccb86e008f8bc7af8ea3ab806a7_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/6f46eccb86e008f8bc7af8ea3ab806a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6659526540d71bb29d94aa82b51e55a19cee610c --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/6f46eccb86e008f8bc7af8ea3ab806a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b72374b51e0ffe30fe512e1b85dc803a8c618d86364ed80bc320e89b05d33d1a +size 48765 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..549fcc2b3363e94f0afe4b5f224ea1e1fb02604f --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31754cf84c5b55378e90423e09772bc5f4a3004596a3d8d5a4b82d31cf0a5806 +size 116670 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/7188dd653353235466aea783783e26c8_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/7188dd653353235466aea783783e26c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f65c78f504c79048c2e5be1042d07c5f9684ca4 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/7188dd653353235466aea783783e26c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc20d5afdea7c48f3b9a750399a502e03d687eafd047365a15d5b134b22d54c0 +size 48564 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/73e9791d33fc9c524278fb216945435f_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/73e9791d33fc9c524278fb216945435f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fbf6293c47298c4d697f070feceffd0361f688f --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/73e9791d33fc9c524278fb216945435f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ad2f6be5e171111c13b074a4cf08efea3b3c8359a2f5ab470fafe6f18d93c85 +size 31961 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/742a5484e7dd016256ab99921bbd635d_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/742a5484e7dd016256ab99921bbd635d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1be0840dffd0c0eec7feceaba4cd143bbed64154 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/742a5484e7dd016256ab99921bbd635d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eac1b55db23bb2ecba1fc0f2f2d653073e2d86ccf8e86dd61ffa98e3eb7aa574 +size 49788 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..220406bb6ad22f85b284a8fc04ad630e25f8cd0c --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd0139f1eb417e608f1241c8d48a39daae7a285b238645dec89385e0e287842f +size 27156 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3960ee5b637743357e1c9235acdcd69d05e7fd1 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fe20ca69dec78269bd79e9b1c1fdaa8ea59ef1dffcb48a4ea1b222942d06cab +size 57995 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/7818b1bd115c04ee738bcf90f51d945b_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/7818b1bd115c04ee738bcf90f51d945b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df5be670e435c7a7288115a90d7a0ed22a6ac015 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/7818b1bd115c04ee738bcf90f51d945b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9156e77cf55b873e3080c2c43b617c8741e330a6a208b9a661fb901e22326259 +size 82622 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/7896390ac3d26645db5fc41aedc7d6f4_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/7896390ac3d26645db5fc41aedc7d6f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..086025f9e4c31dbd7bb51354ae4d7bc4915b6448 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/7896390ac3d26645db5fc41aedc7d6f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d92668bdc88093ad530ea0b435ce15fb0e13af32d0ef4f0995236b816b60d7f7 +size 106124 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..282b14ea79ee4eb3ec70a7dc818535583a432a93 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b19a11708e5b86adbb25ed638a600a73c68b1f2aeb048854eda1a852aa38f507 +size 108085 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/796d2e601722450d6456085e0a801e1e_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/796d2e601722450d6456085e0a801e1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11981256846cb2aa8a06ccd0e5d212f5571445f1 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/796d2e601722450d6456085e0a801e1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d45aefc54a6965d89892f1773a3da93786490261e56f4985380731c17d9f38a8 +size 61363 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c934739074986e3128341cf25d5d4ead04a1bb60 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04248fe9d7d8e0d8312287221c20f37602091bc5aa002fcaf322748644c38b58 +size 146285 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/7d541b1af37d2613847d8a95376efa0c_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/7d541b1af37d2613847d8a95376efa0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c8a8da21e03dab9a9b2295d9f92061af5d4f976 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/7d541b1af37d2613847d8a95376efa0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8be22ec70883e118d139b25928d0176671331fd23d0abf2b24a977bea1da73db +size 29467 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..908c81d22d82500549a5bd8282c8e651965037a4 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4ac0ccf4a79833a7e7de8c32071f6bd2013bbf63525ffb601e63bc5cad6bf13 +size 60174 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/7fe4241eea8865aa6d2686d711c13ba6_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/7fe4241eea8865aa6d2686d711c13ba6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f48acf830d21b34c121fd63517f23708d66aa71 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/7fe4241eea8865aa6d2686d711c13ba6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:479bed72f6d6f84bc332eb91859bd9002e3f15a07693cb852e75677520d65c98 +size 14891 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/7fee3dcb5487529210cd0dea013d08db_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/7fee3dcb5487529210cd0dea013d08db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fa328aaf7b8e140d8d58e172202bc24be9cfc83 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/7fee3dcb5487529210cd0dea013d08db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a28a3878011344b24a957f44d4d855e8cc7795f5fb747762e8132a6dc58905e +size 72991 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/826bf067afc22bf94cdd2faf3e595893_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/826bf067afc22bf94cdd2faf3e595893_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ed12960e705df4a73966e75a8c20d8cc4014188 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/826bf067afc22bf94cdd2faf3e595893_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d231cc5f4d1c8ce50535a31cd33d7215f57607becb4ae2e72563f8207991731 +size 138260 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/849a212bb698e5387989fe9100b12c7c_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/849a212bb698e5387989fe9100b12c7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34c95f233d2340f9fb479f913a6e268ca0e82c9e --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/849a212bb698e5387989fe9100b12c7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48f82de2e09c51145aba0c55478343c2bdb069ae79c53141aa4357aafdd8cd16 +size 39794 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f36bf3b720d218acb80be52ae2a62f143c92604 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9063a92ad18f418eba68198e550fc349fd1ffba586330a417d3749159ecf5d1f +size 47192 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/87f2c7d96e398885a4108ecbf1aa9499_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/87f2c7d96e398885a4108ecbf1aa9499_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb91fde85e1a92b1da39dcf0f9ddb8cd1285b73d --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/87f2c7d96e398885a4108ecbf1aa9499_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8898e20844fd35cf4c65cceee7de3cf0ed818a0e780c4cbc7f7e5deb848b83a1 +size 22383 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0dc955014dc9f4ce23c1d785faf412ff1674e66 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10840da34e66b508e1246835a9902a23ccd48b7f15bf98d21359eb4299ea9c1c +size 200515 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17a9d8925274b18c9e0d9ecc2b929b26e830d589 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dac9b0f3fe0dfcb2e14102305b9e07620991560c580847922f67ce59286dcf5 +size 62527 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/8b989840720118a1b720745e35a79346_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/8b989840720118a1b720745e35a79346_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a2ccfa5a6a5fecdc775cc9e41cb3a6be02992e3 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/8b989840720118a1b720745e35a79346_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:002c836f31b82ff8d99f9f62567c87d19f577d9058f6d2acb7d6b73673e3cafb +size 86690 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/8dd299498fe4924af215a1d179688e11_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/8dd299498fe4924af215a1d179688e11_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2130699c606233fbb3088079e89dadfdb267c3b --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/8dd299498fe4924af215a1d179688e11_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab1920b04ab050c4121c14d1a25775e06c99798175c31319801b3bd1df60b3fa +size 97756 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/928773233290b815ec292945af49f31f_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/928773233290b815ec292945af49f31f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ab46c07a4fe85a2eca0a9db43f416597dbb7a6d --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/928773233290b815ec292945af49f31f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d9e0dd58bec9c111b544cb67b8ec096be29df45dcb0fed62b1eb38fadd660da +size 37127 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/996e39b914f33cf1046ab1540d61973a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/996e39b914f33cf1046ab1540d61973a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e480b005586bec07cd7be93300bd3c4188a659a5 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/996e39b914f33cf1046ab1540d61973a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8833b4f2ef4f60f55e6341c337a408ce64c3fc0bdac0dce729ed3260eaa692b1 +size 58795 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea632df9369585f6a4ba5d04d2a2e3c6d00f9d8e --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dbf665fffcf20c958138b89ea7b991c7119416ccea07bd700f4e985db5fa391 +size 25462 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99ad644a71a4894bfedc0e2a66980eb5113bd26e --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9d23b6551735e11771e80f05390c145949e58526dee554a84967ccbd064676f +size 19502 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/9dc88fb2c48bc64047fc3e79814f1d47_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/9dc88fb2c48bc64047fc3e79814f1d47_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6066ebaab90d1369924b3ec1529d55bab95c63c --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/9dc88fb2c48bc64047fc3e79814f1d47_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:595600edbee289b126dc33012adfa9b0d25dec2445742c92610b98d62adc839e +size 116645 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/a04291a026e9ac4a7b644e556a0672b4_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/a04291a026e9ac4a7b644e556a0672b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39a466695214f63ac2d0c665c5277637ee5d0faf --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/a04291a026e9ac4a7b644e556a0672b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e48527aa4e0fe0f90e673503915660e3c9dc02af1a0669e2f6159a5068e440ed +size 11593 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d86a15cc0ff59e9c96eb9d9c4657a2ece023beb0 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c0ec4b4921f40379a12d4741e2c66f74ba8c415eb63a26cdf874d79b5c3d141 +size 101087 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93522d72fd2be2c47f62ccff1666ce10104f3410 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc6892d9ff6b9c6d5714d1c2adaacbcf5a243c0cd34d44c0bc784c31ff2f0cc7 +size 23131 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84d89822f4cb7cd4d83bf4bcf6cd08716626ad58 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b91095d26e3bbba8866769cb3b7a0edb4fec850405dcd7b731b6adf3c5a3d5cb +size 212284 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/a4b868a176f7e0448ee72483727e9f6f_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/a4b868a176f7e0448ee72483727e9f6f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74bffa4b56832041807ea4e88be3a8c914889d40 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/a4b868a176f7e0448ee72483727e9f6f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0791586f3c745b3e1829944cd58c86beaaba4508da421bc958e5a0e0f44d2d82 +size 37866 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d883238c9c22ee2939ec035a2145843a4ab1f870 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0de5559f7cb75adaa17295d2d1ba1f2d81e41a67e64d23b44ca4b5c745ff7a4d +size 51397 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/a63c7eab8da2ec07cbb94399fd60fc62_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/a63c7eab8da2ec07cbb94399fd60fc62_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97d86f5ac4964531fa8171313662bfffcbba0929 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/a63c7eab8da2ec07cbb94399fd60fc62_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17b48cbfec2113a8e4336a1fd94fcc816f3576e24eabfd7a2637b8014c0f8013 +size 52185 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/a66383962afcd0f0458f0d45c101fabf_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/a66383962afcd0f0458f0d45c101fabf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2f1a67262fb0d9997282ded9aa60bb8745fa996 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/a66383962afcd0f0458f0d45c101fabf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29f1a1f8c78dbaaa855f76699cf84d9cc0939eb592a9923b50fa29fa0c941e12 +size 50816 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/a6d1b7d9be84a290d618aee634d06d3d_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/a6d1b7d9be84a290d618aee634d06d3d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf80a7fb67fcf45c377fa499f8ac9922b77b3293 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/a6d1b7d9be84a290d618aee634d06d3d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69258b6ad54332335fef5b23fa4fd11d1a4ce0f7ced5b2b2db28acda1a0c74cf +size 63068 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/a9159a006d67a834a7b1a771c18191cc_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/a9159a006d67a834a7b1a771c18191cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..172f24a1ccbdf0ef6d47453afad4786f1aa9bbbf --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/a9159a006d67a834a7b1a771c18191cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4574bce08a5ec25e41424021f956448351fff2d546d9abf7f8db59903573c1c5 +size 49615 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a09a6d635f52052e4273c137c1b548f6088788b --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2872766257593a358575f80e81290b38f10ea764790d6f9fd9784dc4ac8e0017 +size 9354 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/b18f943d96bfcb2b1360a27b9e45e11e_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/b18f943d96bfcb2b1360a27b9e45e11e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85f654759c5616d1bfcdb691d82d480be599033f --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/b18f943d96bfcb2b1360a27b9e45e11e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:428e04a95810e939471415b6ac98d3365d3d272ea3d9f1dc23f0f01fba6b2403 +size 54310 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/b1a6ab9f3d33d6e8d64173bfa595b763_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/b1a6ab9f3d33d6e8d64173bfa595b763_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bbed490081a648e82090f67d2c265c6548576bf --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/b1a6ab9f3d33d6e8d64173bfa595b763_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d988bb11f1e2903205c55480b21a32ee8d9848365be7162770b2e5b0bc41766 +size 9873 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfaa0a3a4bf0f3afb059d254bbcdfa99b6119c42 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a348e29ec0059f0af6662322cbaf6e976aad0d7a9146211b340f157c50101032 +size 38368 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/b35ea3e304aad7d350a9902270413930_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/b35ea3e304aad7d350a9902270413930_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70505850ad40d2658515764f7f56c3bcdc53806b --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/b35ea3e304aad7d350a9902270413930_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6edbe8b253b82f22395ba7c7d2e5d63e0d9c26369921650a8142f61fd7637db8 +size 44886 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/b3bf81a327421e28bc8471691b77b252_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/b3bf81a327421e28bc8471691b77b252_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1133ad8e0950257e99fd0415fafccb1181fcb727 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/b3bf81a327421e28bc8471691b77b252_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86baac69e83aed146fb789abf361ef4098cfde6764d29010c207c77a904762af +size 38434 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/b4022f9f3b9a3b30ade5c100052cb16a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/b4022f9f3b9a3b30ade5c100052cb16a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e25f753155b5241782323cd5955bf092038af6a9 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/b4022f9f3b9a3b30ade5c100052cb16a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc7eec6c8d7ab85d8850048ed79b021a52ed4f0d5d63c283a24a6d429ae2c796 +size 33622 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/b437cd7078b36507e5d918fe6224e6dd_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/b437cd7078b36507e5d918fe6224e6dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3631601827aa710efd773cbd0b9a77e168864f1 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/b437cd7078b36507e5d918fe6224e6dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a297cbd202f449e79849a7c19027f64497d22935a2b6e3ac386e751ff5139599 +size 45714 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/b44a429660cbf47740ee6777db90e34f_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/b44a429660cbf47740ee6777db90e34f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7b44e9ba09c5c73f40b87a7053a8b74c896b54f --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/b44a429660cbf47740ee6777db90e34f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d79b9f6ee7488fe2392699defef5f38e80d01677d0a691e5e7a6ba5c3a15bdae +size 48943 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/b5ce6d659e1431289c2e79b01bf38a15_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/b5ce6d659e1431289c2e79b01bf38a15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb8a7c103e07664fcca6090f07e6618f9fda0baa --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/b5ce6d659e1431289c2e79b01bf38a15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2030dab4861dbabf73280087888b646e45117ee8c70e30999d821e8669cf8bae +size 87710 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/b855c771b0a7133300a578d48a2d79d9_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/b855c771b0a7133300a578d48a2d79d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d3f79db5eeb6447385bd45039625b591c0d583e --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/b855c771b0a7133300a578d48a2d79d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25c5f89c611d177fc28e8cb22735f70567d4f525623cf8448414b9ed92895f55 +size 185471 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22baa1cf74820caeea174859a748f20c79b9534f --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09a28349763c3a96cf8fce308066e08ea5c814f50d7bc27d387e9ec9d901d822 +size 126259 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/bae3da32cd7a91976285d7e4a3d3018a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/bae3da32cd7a91976285d7e4a3d3018a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea50f13483d9df60ef99ff689ad4c350d0e06489 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/bae3da32cd7a91976285d7e4a3d3018a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36906b27c5b998146d1b867e6dce6ffecf02b2b20ba1156dd845e9213122ff9d +size 55758 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/bd200589aacf1ff9a3d4e245938cbcc8_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/bd200589aacf1ff9a3d4e245938cbcc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c63829e0716c2cf5c831b81b20152e3d3ee5af6 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/bd200589aacf1ff9a3d4e245938cbcc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:137c325ffb26c5acf843d990aa9a567b11cbf8fa9825fcc329583714f8494f46 +size 75227 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/beda549cc2a4e2b9ac7f74fe9ed72b67_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/beda549cc2a4e2b9ac7f74fe9ed72b67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9102def4503b981dbb57cab1a6331f32cc5f1983 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/beda549cc2a4e2b9ac7f74fe9ed72b67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fe0ecbe3c45f47a9a8168a2822f3045cfe6f8d3186f0bab555b3e362f102366 +size 250809 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/c0438093a10a593c42106b1e5dbb4331_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/c0438093a10a593c42106b1e5dbb4331_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea6439c4336c705a6bf9daac813c475b1479f94a --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/c0438093a10a593c42106b1e5dbb4331_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f43ce5490f7d75b7269b4e9fa3a1ff7c6ca828381d54138d32f48ea7126d24d7 +size 96747 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/c24f22afc8106a8f9b76c759a1db6891_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/c24f22afc8106a8f9b76c759a1db6891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b11ae6937bdd1618c85ae843a3112c25078a0dd8 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/c24f22afc8106a8f9b76c759a1db6891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e31d7c9d4d2e06bef1e8b6f99b28cd6bca7d79a4a07a4b9962cfd632b17f9f35 +size 93534 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef7007d189684f81e067c826b3bf2cfb83f68cb3 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6f9437cc40b065fbf4a74e2a73b1ae75096db91cd92977c05fd9a50db0cbccd +size 172123 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/c71cc20c24544f057770d4066ecaadc4_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/c71cc20c24544f057770d4066ecaadc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ccb03714b19a0d2a9dd08b247d38db8c4126291 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/c71cc20c24544f057770d4066ecaadc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e8efe18fd76b5391432935c50a852fd59bba3812bfc00ecd558adc89a78981a +size 29376 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9954f81a53d4a957017b786a4e8111ad625f44c6 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb4e30bc47721a3d394f1c9a725e446504c8044d91e83196d3938d28544c07af +size 53444 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87e5a0a12516194ed4ba26f7c5c62fd96f7eb2a9 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0947955739ed2a7fe2fef433acc734ba3b1084811e1573deeb51584ec476486 +size 4071 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/c7973a89da29a4a59561e36561984333_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/c7973a89da29a4a59561e36561984333_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6af05a75dfd86dc903c3c0a247e829b257a51cd --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/c7973a89da29a4a59561e36561984333_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e98f56ab7b26947971c230f3e0e5a7ed9d5fc461752d18fc8077b62ca44ed314 +size 26261 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/c8363610940980ea7cd1611443c94ef5_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/c8363610940980ea7cd1611443c94ef5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..209066a77695590df41ebcc31858c5150403b854 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/c8363610940980ea7cd1611443c94ef5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:776bba014ff3fd94cea6f051279aebf8e4abc15a8788718f346189f038a50752 +size 115408 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/c916a9fb4d2c440522379dedf3f76119_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/c916a9fb4d2c440522379dedf3f76119_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d355abffc059f30d10fafb7360aabed9623a6bd9 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/c916a9fb4d2c440522379dedf3f76119_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6318744e6d2f84cf09a8cc2c8c6981ee9043e9e2560fc2a6b2150357c4622528 +size 21835 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51786cd1b477a552fdf7c3caaff3006cbb543427 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8631054c450ff394ffbd44f9a29498b09b984db6c4738a1b88b590b3474f2472 +size 155936 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/ca7e6c1823b101e869d4f177c147bea6_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/ca7e6c1823b101e869d4f177c147bea6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e41d8940798ff7fb6baa3d569f37545dd6a86f6a --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/ca7e6c1823b101e869d4f177c147bea6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a9019fad49df174bcc06c74cd74ec1be8a902f42a1c5fd4531dbcf2fb9b388e +size 263856 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26497ee20d752ccfaca3711f19e2b17ffe2d51dd --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1b964af0a32e114f322b365b41bea100eaa98dad6f45ee1d4d69de2f7e74f2f +size 46685 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/d01f4371bb8136148156771a18b9ea89_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/d01f4371bb8136148156771a18b9ea89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad36dbc8317415226a275bcf7b43fdaa84d8e895 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/d01f4371bb8136148156771a18b9ea89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d98894270b44061fcb9bdb23d288c47c5d7a987ebc740f92b3a866a2267a576 +size 20409 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4524bbaee8bfe11e985482ff83b0c232fa97d54d --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e3eca7be7e4ef8e8be235eb75cde57aa271c3f505a468d976d56b7e948dcfb6 +size 102645 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/d33f50868e9cfda1b1206833c4061e12_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/d33f50868e9cfda1b1206833c4061e12_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0fcb4598e5ac7d0ead2b9bc8e5726d2b198685c --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/d33f50868e9cfda1b1206833c4061e12_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b31490fa3d403a04fc103590feea8a74d1b60f70a06f431b2a81045a35b190e +size 41020 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/d4a6d3795fe79e002987abc462a30f61_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/d4a6d3795fe79e002987abc462a30f61_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eba3b6a702bebd12f54b23bb8d845af1053df77c --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/d4a6d3795fe79e002987abc462a30f61_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8850b35f3c8f7b4f2092808e3ab6d0c1068aeb9c8139b93dc55c460fe0875fb4 +size 19418 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/d6b0963170ed3d0ed9c5bfaccec452e3_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/d6b0963170ed3d0ed9c5bfaccec452e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12cdfabdb4d88c0167497f0db8a4f26a57ee1c72 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/d6b0963170ed3d0ed9c5bfaccec452e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8b35a1371d5db003bb226deb40d810bf2444ab49d5b2778b1e76bfc1e341f4e +size 117639 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/d72d5d32956ba002d9fe93678b8975d0_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/d72d5d32956ba002d9fe93678b8975d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc899ad7c2a4b17248434fd68065c3266bbdaa97 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/d72d5d32956ba002d9fe93678b8975d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c8a6f5c1612cad96a28352f696570a45e3265ef563a45c3df8ea8458523df24 +size 67039 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/dc7f3c8b7f8859a78d5705f104504e4c_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/dc7f3c8b7f8859a78d5705f104504e4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc198f336ed1d678e563fb2ced2739f2882322b1 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/dc7f3c8b7f8859a78d5705f104504e4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9c502af444b99118a14cac58b47579fb7f8636f38f08b93e8140d38c0569e71 +size 58619 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/ddd3dabf3c4bc1bf46fb74ec9330e3fa_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/ddd3dabf3c4bc1bf46fb74ec9330e3fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83a8c682f39e1114c4cf6764544d6814377d9cf5 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/ddd3dabf3c4bc1bf46fb74ec9330e3fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e34cca6ec3689435e5db7a6f29d1a5b90579bd7cb82ef9f4dba247fd81e20d0 +size 68179 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7685f77c86612aa585e75e6e1005756d62357d21 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6f32196a085eaa8723bdabe3be53a93cdd74dff4f2c820b4071f29ba0af3c3d +size 94718 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/df79d6dd5d005b721cf6bcab34d6e12d_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/df79d6dd5d005b721cf6bcab34d6e12d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6640efdffa910d5cc1c8301f48ec9183d8f31e7c --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/df79d6dd5d005b721cf6bcab34d6e12d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05f59ac73bb355d77cedb00900eb41f0de5c8dfddd3383702cbb87d412dd06d9 +size 76645 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5447076c14b41899346c6edfd2d7abba58b3469 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6d5a7c1a08d7c1ba0bd8802f4a5770a432c9bcf0932fbb38b7016f08c635f21 +size 66099 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9810298e0cb6c7e572d7f7fd0c10800971b4d6c --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fd46201930089fc144a08c31341bc007c844a1ffd39161a021184f50411bcb9 +size 65516 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/e2669d6c9c855db64fac0048acd0643b_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/e2669d6c9c855db64fac0048acd0643b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f9b90473b658b1b4462db950d544df77a78b6ed --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/e2669d6c9c855db64fac0048acd0643b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54769ffbf024ca163f04ad0aec5a1c1fd6c6122689da6a545807dc0a2b225267 +size 40980 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/e29078e7dcd6e581ecf7f35dc8220202_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/e29078e7dcd6e581ecf7f35dc8220202_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f75fcaba1e73e522cacae14bdb8586fc218a2055 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/e29078e7dcd6e581ecf7f35dc8220202_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba34c8b19e8dfccb6e21d3385dd66a3ab55914cc95e76e983b11a6919a049b7d +size 25243 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cb91e14176346dc82b88b4c1ad6f9f1e42ec58f --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60facfe0f1ff12c9fca76d60a0f779907f8c0e99d701324fc777ff52e2ce1fbe +size 45195 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b17d63041580a9e954cadaae3512dad54f0f77ef --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa16bfa3d68ef01eec83b13d04ebd57685a97320dde588b3395a4338c422c9da +size 79810 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/e33485d4301404e5a43a61e4cfb96fcc_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/e33485d4301404e5a43a61e4cfb96fcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a233e483c3874249d66b1eacf361388557acccf --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/e33485d4301404e5a43a61e4cfb96fcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:121363e424f4d69b57b326a61067081867c5621cd2a89dae6e10ec7d777792d7 +size 61052 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31120938fa2d8c846eb98bbaac1a2ff6d5993434 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb4a26327e3d7eff34d7aed17fb4054a6f6a6f1cd125d7632dea5205d144437d +size 154227 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/e492fe1061d82aa76cbf7114f57eb90c_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/e492fe1061d82aa76cbf7114f57eb90c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f82f77a3e662d3e59a7a8bec8a62875f7b32bbe1 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/e492fe1061d82aa76cbf7114f57eb90c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a57be1631a506dcdf67e1b488930db95e9bf8bf7ee29bf4d03896951cdd3869 +size 122179 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3845769302b92b272ffe986c531a29d9908d2b9c --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:402a21c04c0d19c8f871b2257b9c3091fd82959f3c1de67f36846663f3c16197 +size 58389 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/e8f5117fb031f413a836525061addd61_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/e8f5117fb031f413a836525061addd61_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6664d756cfd799e8ceff59ebe8e286103add03d1 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/e8f5117fb031f413a836525061addd61_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:701b35d4bccefc7d08af0809b9025a0fcfb06173c11621ed30116246ab82bd22 +size 52260 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..181914fc9bccce0500930bed8f6bf64fea9f545e --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc44b595aeaf8df5ff404d0be83a2fda35e11c06d2953dd4451ed048360745d7 +size 109012 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/ed48e24e36ea0501953177401c900f86_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/ed48e24e36ea0501953177401c900f86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28960e6cb8a3c8c2fa3db48ae81ba4987a8d7177 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/ed48e24e36ea0501953177401c900f86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4565705a43c3969031feb026d6e6beda7c511c9c8239cf85138e3d6d3806c1eb +size 55792 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/f117583d264d1fa4b9c67c44879bb3e7_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/f117583d264d1fa4b9c67c44879bb3e7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1661c2db696c9697cd8a627405f098a6df1857c1 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/f117583d264d1fa4b9c67c44879bb3e7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc00154e2394481eebad5eded91b5fbe0d8c16a0a6ed035f53f580dad9bd422b +size 32339 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/f2b561f8d2d2b8402379552179d9fbef_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/f2b561f8d2d2b8402379552179d9fbef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03dd86b3ce3e3a93e9def2423a30ee523db9eb6b --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/f2b561f8d2d2b8402379552179d9fbef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89e239a81950a40d55056d3e9b238235445e1084beb3057589e9aad56e462f02 +size 40514 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57f8200e5ae578bb2ab86e50807fdfcc75de6aa8 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8baf52a575e3e7fc428d4a5d280743d8b48526d435af275d0c6cd0786ce4a3d +size 132107 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/f43d225d8fed2845b8d7e5afecbfe636_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/f43d225d8fed2845b8d7e5afecbfe636_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d359b721b11260525feda229cfe81a76fd92dff4 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/f43d225d8fed2845b8d7e5afecbfe636_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7a9b3a87e99f1be0fc110623478f8011c78bca1c5051303eee72c5af414cf22 +size 43938 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..550ed5d868eefa549035acf8f2c027f3c3db5ca6 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f2bd388f8bb3698d140e9030447925d3ed763ec1b82db0ee7dbe0aff53ae601 +size 72772 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/fbdd4682fb49c08ff8415c854336a6ab_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/fbdd4682fb49c08ff8415c854336a6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dec907099f8b5e44b0dc9db7093ce327390a73ed --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/fbdd4682fb49c08ff8415c854336a6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1c8ce08d753a7e6c9a4ddecba235d5d45fd33d425aa0bdb866299c2194acd7f +size 27252 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/fd33a3e091898c76820cfaf041c23411_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/fd33a3e091898c76820cfaf041c23411_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e4c0bdf41ea1bfca6ecb45ae51e2d313d4e1a63 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/fd33a3e091898c76820cfaf041c23411_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef32ae468743b3a220cc8349a4b6604e359da0216a53f9d61d49fe894aeb7cb1 +size 20994 diff --git a/marked/G/T-REC-G.709-202006-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/G/T-REC-G.709-202006-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fd2741fc12a6843b602d8aac56822758a7d93c2 --- /dev/null +++ b/marked/G/T-REC-G.709-202006-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:668a966825d93700493716dedc6685ba6b6ca94bcb4fcd6e0c5bb2ee567cf516 +size 49787 diff --git a/marked/G/T-REC-G.726-199012-I_PDF-E/raw.md b/marked/G/T-REC-G.726-199012-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..575344bbbc1b4a7675de11a1f09fda3eb625c1d1 --- /dev/null +++ b/marked/G/T-REC-G.726-199012-I_PDF-E/raw.md @@ -0,0 +1,1992 @@ + + +![ITU logo: A globe with the letters ITU and a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with the letters ITU and a lightning bolt. + +INTERNATIONAL TELECOMMUNICATION UNION + +**CCITT** + +**G.726** + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +# **GENERAL ASPECTS OF DIGITAL TRANSMISSION SYSTEMS; TERMINAL EQUIPMENTS** --- + +**40, 32, 24, 16 kbit/s ADAPTIVE +DIFFERENTIAL PULSE CODE +MODULATION (ADPCM)** + +**Recommendation G.726** + +--- + +![CCITT logo: A globe with the letters CCITT.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +CCITT logo: A globe with the letters CCITT. + +Geneva, 1990 + +# FOREWORD + +The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT 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 Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). + +Recommendation G.726 was prepared by Study Group XV and was approved under the Resolution No. 2 procedure on the 14 of December 1990. + +## --- CCITT NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency. + +## Recommendation G.726 + +## 40, 32, 24, 16 kbit/s ADAPTIVE DIFFERENTIAL PULSE CODE MODULATION (ADPCM)1) + +## 1 General + +The characteristics below are recommended for the conversion of a 64 kbit/s A-law or $\mu$ -law pulse code modulation (PCM) channel to and from a 40, 32, 24 or 16 kbit/s channel. The conversion is applied to the PCM bit stream using an ADPCM transcoding technique. The relationship between the voice frequency signals and the PCM encoding/decoding laws is fully specified in Recommendation G.711. + +The principal application of 24 and 16 kbit/s channels is for overload channels carrying voice in Digital Circuit Multiplication Equipment (DCME). + +The principal application of 40 kbit/s channels is to carry data modem signals in DCME, especially for modems operating at greater than 4800 kbit/s. + +Sections 1.1 and 1.2 of this Recommendation provide an outline description of the ADPCM transcoding algorithm, §§ 2 and 3 provide the principles and functional descriptions of the ADPCM encoding and decoding algorithms respectively, whilst § 4 is the precise specification for the algorithm computations. Networking aspects and digital test sequences are addressed in Appendices I and II, respectively, to this Recommendation. + +Simplified block diagrams of both the ADPCM encoder and decoder are shown in Figure 1/G.726. + +In § 4, each sub-block in the encoder and decoder is precisely defined using one particular logical sequence. If other methods of computation are used, extreme care should be taken to ensure that they yield *exactly* the same value for the output processing variables. Any further departures from the processes detailed in § 4 will incur performance penalties which may be severe. + +*Note 1* – Prior to the definition of this Recommendation, other ADPCM algorithms of performance similar to the 40 kbit/s algorithm specified here have been incorporated in DCME designs and used in telecommunications networks. These algorithms may be considered by bilateral agreement for limited DCME applications under certain circumstances. Technical descriptions providing information on two such algorithm approaches can be found in COM XVIII No. 101 and COM XVIII No. 102 of the 1984-1988 Study Period. + +*Note 2* – The assignment of 16, 24, 32 and 40 kbit/s DCME channels and the associated selection of coding rates are beyond the scope of this Recommendation; see, for example, Recommendation G.763 (revised, 1990). + +*Note 3* – Signalling and multiplexing considerations are beyond the scope of this Recommendation; see, for example, Recommendations G.761 and G.763 (revised, 1990). + +--- + +1) This Recommendation completely replaces the text of Recommendations G.721 and G.723 published in Volume III.4 of the Blue Book. It should be noted that systems designed in accordance with the present Recommendation will be compatible with systems designed in accordance with the Blue Book version. + +![Simplified block diagrams of the ADPCM encoder and decoder. Part (a) shows the encoder where a 64 kbit/s PCM input is converted to uniform PCM, then a difference signal is calculated by subtracting a signal estimate from the input. This difference signal is quantized by an adaptive quantizer to produce the ADPCM output. The output is also processed by an inverse adaptive quantizer to produce a quantized difference signal, which is then added to the signal estimate to produce a reconstructed signal. This reconstructed signal is fed into an adaptive predictor to generate the next signal estimate. Part (b) shows the decoder where the ADPCM input is processed by an inverse adaptive quantizer to produce a quantized difference signal. This signal is added to a signal estimate to produce a reconstructed signal, which is then converted to PCM. The reconstructed signal is also fed into an adaptive predictor to generate the next signal estimate. Both the reconstructed signal and the quantized difference signal are fed into a synchronous coding adjustment block to produce the final 64 kbit/s output. The diagram is labeled T1508190-92.](2763901b7a1fd1b5d704cdc450d12ed0_img.jpg) + +``` + +graph TD + subgraph Encoder [a) Encoder] + E1[64 kbit/s PCM input] --> E2[Convert to uniform PCM] + E2 --> E3((+)) + E3 --> |Difference signal| E4[Adaptive quantizer] + E4 --> E5[ADPCM output] + E4 --> E6[Inverse adaptive quantizer] + E6 --> |Quantized difference signal| E7((+)) + E7 --> |Reconstructed signal| E8[Adaptive predictor] + E8 --> |Signal estimate| E3 + E8 --> |Signal estimate| E7 + end + + subgraph Decoder [b) Decoder] + D1[ADPCM input] --> D2[Inverse adaptive quantizer] + D2 --> |Quantized difference signal| D3((+)) + D3 --> |Reconstructed signal| D4[Convert to PCM] + D4 --> D5[Synchronous coding adjustment] + D5 --> D6[64 kbit/s output] + D3 --> D7[Adaptive predictor] + D7 --> |Signal estimate| D3 + D2 --> D5 + D4 --> D7 + end + +``` + +a) *Encoder* + +b) *Decoder* + +T1508190-92 + +Simplified block diagrams of the ADPCM encoder and decoder. Part (a) shows the encoder where a 64 kbit/s PCM input is converted to uniform PCM, then a difference signal is calculated by subtracting a signal estimate from the input. This difference signal is quantized by an adaptive quantizer to produce the ADPCM output. The output is also processed by an inverse adaptive quantizer to produce a quantized difference signal, which is then added to the signal estimate to produce a reconstructed signal. This reconstructed signal is fed into an adaptive predictor to generate the next signal estimate. Part (b) shows the decoder where the ADPCM input is processed by an inverse adaptive quantizer to produce a quantized difference signal. This signal is added to a signal estimate to produce a reconstructed signal, which is then converted to PCM. The reconstructed signal is also fed into an adaptive predictor to generate the next signal estimate. Both the reconstructed signal and the quantized difference signal are fed into a synchronous coding adjustment block to produce the final 64 kbit/s output. The diagram is labeled T1508190-92. + +FIGURE 1/G.726 + +### **Simplified block diagrams** + +### 1.1 *ADPCM encoder* + +Subsequent to the conversion of the A-law or $\mu$ -law PCM input signal to uniform PCM, a difference signal is obtained, by subtracting an estimate of the input signal from the input signal itself. An adaptive 31-, 15-, 7-, or 4-level quantizer is used to assign five, four, three or two binary digits, respectively, to the value of the difference signal for transmission to the decoder. An inverse quantizer produces a quantized difference signal from these same five, four, three or two binary digits, respectively. The signal estimate is added to this quantized difference signal to produce the reconstructed version of the input signal. Both the reconstructed signal and the quantized difference signal are operated upon by an adaptive predictor which produces the estimate of the input signal, thereby completing the feedback loop. + +### 1.2 *ADPCM decoder* + +The decoder includes a structure identical to the feedback portion of the encoder, together with a uniform PCM to A-law or $\mu$ -law conversion and a synchronous coding adjustment. + +The synchronous coding adjustment prevents cumulative distortion occurring on synchronous tandem codings (ADPCM-PCM-ADPCM, etc., digital connections) under certain conditions (see § 3.7). The synchronous coding adjustment is achieved by adjusting the PCM output codes in a manner which attempts to eliminate quantizing distortion in the next ADPCM encoding stage. + +## 2 ADPCM encoder principles + +Figure 2/G.726 is a block schematic of the encoder. For each variable to be described, $k$ is the sampling index and samples are taken at 125 $\mu$ s intervals. A fundamental description of each block is given below in §§ 2.1 to 2.8. + +![Block schematic of the ADPCM encoder (Figure 2/G.726). The diagram shows the signal flow from input PCM format conversion to the final ADPCM output, with feedback loops for adaptation and prediction. The input signal s(k) is converted to a uniform PCM signal s_l(k). This signal is then processed by a difference signal computation block to produce the difference signal d(k). The difference signal is quantized by an adaptive quantizer to produce the ADPCM output l(k). The quantized signal is then processed by an inverse adaptive quantizer to produce the reconstructed difference signal d_q(k). This signal is added to the signal estimate s_e(k) in a reconstructed signal calculator to produce the reconstructed signal s_r(k). The reconstructed signal is also processed by an adaptive predictor to produce the signal estimate s_e(k). The adaptive predictor also outputs a2(k). The quantized signal l(k) is also processed by a quantizer scale factor adaptation block to produce the scale factor y(k). The scale factor y(k) is then processed by an adaptation speed control block to produce the adaptation parameters a1(k) and a2(k). The adaptation parameters are also processed by a tone and transition detector to produce the transition parameters t_r(k) and t_d(k). The transition parameters are then processed by the adaptation speed control block to produce the adaptation parameters a1(k) and a2(k). The adaptation parameters are also processed by the quantizer scale factor adaptation block to produce the scale factor y(k). The scale factor y(k) is also processed by the difference signal computation block to produce the difference signal d(k). The signal estimate s_e(k) is also processed by the difference signal computation block to produce the difference signal d(k). The reconstructed signal s_r(k) is also processed by the adaptive predictor to produce the signal estimate s_e(k). The reconstructed signal s_r(k) is also processed by the tone and transition detector to produce the transition parameters t_r(k) and t_d(k). The transition parameters are also processed by the adaptation speed control block to produce the adaptation parameters a1(k) and a2(k). The adaptation parameters are also processed by the quantizer scale factor adaptation block to produce the scale factor y(k). The scale factor y(k) is also processed by the difference signal computation block to produce the difference signal d(k). The signal estimate s_e(k) is also processed by the difference signal computation block to produce the difference signal d(k).](e394c2b5c61344f6a12397f430086072_img.jpg) + +Block schematic of the ADPCM encoder (Figure 2/G.726). The diagram shows the signal flow from input PCM format conversion to the final ADPCM output, with feedback loops for adaptation and prediction. The input signal s(k) is converted to a uniform PCM signal s\_l(k). This signal is then processed by a difference signal computation block to produce the difference signal d(k). The difference signal is quantized by an adaptive quantizer to produce the ADPCM output l(k). The quantized signal is then processed by an inverse adaptive quantizer to produce the reconstructed difference signal d\_q(k). This signal is added to the signal estimate s\_e(k) in a reconstructed signal calculator to produce the reconstructed signal s\_r(k). The reconstructed signal is also processed by an adaptive predictor to produce the signal estimate s\_e(k). The adaptive predictor also outputs a2(k). The quantized signal l(k) is also processed by a quantizer scale factor adaptation block to produce the scale factor y(k). The scale factor y(k) is then processed by an adaptation speed control block to produce the adaptation parameters a1(k) and a2(k). The adaptation parameters are also processed by a tone and transition detector to produce the transition parameters t\_r(k) and t\_d(k). The transition parameters are then processed by the adaptation speed control block to produce the adaptation parameters a1(k) and a2(k). The adaptation parameters are also processed by the quantizer scale factor adaptation block to produce the scale factor y(k). The scale factor y(k) is also processed by the difference signal computation block to produce the difference signal d(k). The signal estimate s\_e(k) is also processed by the difference signal computation block to produce the difference signal d(k). The reconstructed signal s\_r(k) is also processed by the adaptive predictor to produce the signal estimate s\_e(k). The reconstructed signal s\_r(k) is also processed by the tone and transition detector to produce the transition parameters t\_r(k) and t\_d(k). The transition parameters are also processed by the adaptation speed control block to produce the adaptation parameters a1(k) and a2(k). The adaptation parameters are also processed by the quantizer scale factor adaptation block to produce the scale factor y(k). The scale factor y(k) is also processed by the difference signal computation block to produce the difference signal d(k). The signal estimate s\_e(k) is also processed by the difference signal computation block to produce the difference signal d(k). + +FIGURE 2/G.726 +Encoder block schematic + +### 2.1 Input PCM format conversion + +This block converts the input signal $s(k)$ from A-law or $\mu$ -law PCM to a uniform PCM signal $s_l(k)$ . + +### 2.2 Difference signal computation + +This block calculates the difference signal $d(k)$ from the uniform PCM signal $s_l(k)$ and the signal estimate $s_e(k)$ : + +$$d(k) = s_l(k) - s_e(k) \quad (2-1)$$ + +### 2.3 Adaptive quantizer + +A 31-, 15-, 7- or 4-level non-uniform adaptive quantizer is used to quantize the difference signal $d(k)$ for operating at 40, 32, 24 or 16 kbit/s, respectively. Prior to quantization, $d(k)$ is converted to a base 2 logarithmic representation and scaled by $y(k)$ which is computed by the scale factor adaptation block. The normalized input/output characteristic (infinite precision values) of the quantizer is given in Tables 1/G.726 through 4/G.726. + +#### 2.3.1 Operation at 40 kbit/s + +Five binary digits are used to specify the quantized level representing $d(k)$ (four for the magnitude and one for the sign). The 5-bit quantizer output $I(k)$ forms the 40 kbit/s output signal; $I(k)$ takes on one of 31 non-zero values, $I(k)$ is also fed to the inverse adaptive quantizer, the adaptation speed control and the quantizer scale factor adaptation blocks that operate on a 5-bit $I(k)$ having one of 32 possible values. $I(k) = 00000$ is a legitimate input to these blocks when used in the decoder, due to transmission errors. + +TABLE 1/G.726 + +##### **Quantizer normalized input/output characteristic for 40 kbit/s operation** + +| Normalized quantizer input range
$\log_2 d(k) - y(k)$ | $ I(k) $ | Normalized quantizer output
$\log_2 d_q(k) - y(k)$ | +|------------------------------------------------------------|----------|---------------------------------------------------------| +| $[4.31, +\infty)$ | 15 | 4.42 | +| $[4.12, 4.31)$ | 14 | 4.21 | +| $[3.91, 4.12)$ | 13 | 4.02 | +| $[3.70, 3.91)$ | 12 | 3.81 | +| $[3.47, 3.70)$ | 11 | 3.59 | +| $[3.22, 3.47)$ | 10 | 3.35 | +| $[2.95, 3.22)$ | 9 | 3.09 | +| $[2.64, 2.95)$ | 8 | 2.80 | +| $[2.32, 2.64)$ | 7 | 2.48 | +| $[1.95, 2.32)$ | 6 | 2.14 | +| $[1.54, 1.95)$ | 5 | 1.75 | +| $[1.08, 1.54)$ | 4 | 1.32 | +| $[0.52, 1.08)$ | 3 | 0.81 | +| $[-0.13, 0.52)$ | 2 | 0.22 | +| $[-0.96, -0.13)$ | 1 | -0.52 | +| $(-\infty, -0.96)$ | 0 | $-\infty$ | + +*Note* – In Tables 1/G.726 through 4/G.726, “[” indicates that the endpoint value is included in the range, and “)” or “)” indicates that the endpoint value is excluded from the range. + +#### 2.3.2 Operation at 32 kbit/s + +Four binary digits are used to specify the quantized level representing $d(k)$ (three for the magnitude and one for the sign). The 4-bit quantizer output $I(k)$ forms the 32 kbit/s output signal; it is also fed to the inverse adaptive quantizer, the adaptation speed control and the quantizer scale factor adaptation blocks. $I(k) = 0000$ is a legitimate input to these blocks when used in the decoder, due to transmission errors. + +TABLE 2/G.726 + +##### **Quantizer normalized input/output characteristic for 32 kbit/s operation** + +| Normalized quantizer input range
$\log_2 d(k) - y(k)$ | $ I(k) $ | Normalized quantizer output
$\log_2 d_q(k) - y(k)$ | +|------------------------------------------------------------|----------|---------------------------------------------------------| +| $[3.12, +\infty)$ | 7 | 3.32 | +| $[2.72, 3.12)$ | 6 | 2.91 | +| $[2.34, 2.72)$ | 5 | 2.52 | +| $[1.91, 2.34)$ | 4 | 2.13 | +| $[1.38, 1.91)$ | 3 | 1.66 | +| $[0.62, 1.38)$ | 2 | 1.05 | +| $[-0.98, 0.62)$ | 1 | 0.031 | +| $(-\infty, -0.98)$ | 0 | $-\infty$ | + +#### 2.3.3 *Operation at 24 kbit/s* + +Three binary digits are used to specify the quantized level representing $d(k)$ (two for the magnitude and one for the sign). The 3-bit quantizer output $I(k)$ forms the 24 kbit/s output signal, where $I(k)$ takes on one of seven non-zero values. $I(k)$ is also fed to the inverse adaptive quantizer, the adaptation speed control and the quantizer scale factor adaptation blocks, each of which is modified to operate on a 3-bit $I(k)$ having any of the eight possible values. $I(k) = 000$ is a legitimate input to these blocks when used in the decoder, due to transmission errors. + +TABLE 3/G.726 + +##### **Quantizer normalized input/output characteristic for 24 kbit/s operation** + +| Normalized quantizer input range
$\log_2 d(k) - y(k)$ | $ I(k) $ | Normalized quantizer output
$\log_2 d_q(k) - y(k)$ | +|------------------------------------------------------------|----------|---------------------------------------------------------| +| $[2.58, +\infty)$ | 3 | 2.91 | +| $[1.70, 2.58)$ | 2 | 2.13 | +| $[0.06, 1.70)$ | 1 | 1.05 | +| $(-\infty, -0.06)$ | 0 | $-\infty$ | + +#### 2.3.4 *Operation at 16 kbit/s* + +Two binary digits are used to specify the quantized level representing $d(k)$ (one for the magnitude and one for the sign). The 2-bit quantizer output $I(k)$ forms the 16 kbit/s output signal; it is also fed to the inverse adaptive quantizer, the adaptation speed control and the quantizer scale factor adaptation blocks. + +TABLE 4/G.726 + +##### **Quantizer normalized input/output characteristic for 16 kbit/s operation** + +| Normalized quantizer input range
$\log_2 d(k) - y(k)$ | $ I(k) $ | Normalized quantizer output
$\log_2 d_q(k) - y(k)$ | +|------------------------------------------------------------|----------|---------------------------------------------------------| +| $[2.04, +\infty)$ | 1 | 2.85 | +| $(-\infty, -2.04)$ | 0 | 0.91 | + +Unlike the quantizers described in § 2.3.1 for operation at 40 kbit/s, in § 2.3.2 for operation at 32 kbit/s and in § 2.3.3 for operation at 24 kbit/s, the quantizer for operation at 16 kbit/s is an even-level (4-level) quantizer. The even-level quantizer for the 16 kbit/s ADPCM has been selected because of its superior performance over a corresponding odd-level (3-level) quantizer. + +### 2.4 Inverse adaptive quantizer + +A quantized version $d_q(k)$ of the difference signal is produced by scaling, using $y(k)$ , specific values selected from the normalized quantizing characteristic given in Tables 1/G.726 through 4/G.726 and then transforming the result from the logarithmic domain. + +### 2.5 Quantizer scale factor adaptation + +This block computes $y(k)$ , the scaling factor for the quantizer and the inverse quantizer. The inputs are the 5-bit, 4-bit, 3-bit, 2-bit quantizer output $I(k)$ and the adaptation speed control parameter $a_I(k)$ . + +The basic principle used in scaling the quantizer is bimodal adaptation: + +- fast for signals (e.g. speech) that produce difference signals with large fluctuations; +- slow for signals (e.g. voiceband data, tones) that produce difference signals with small fluctuations. + +The speed of adaptation is controlled by a combination of fast and slow scale factors. + +The fast (unlocked) scale factor $y_u(k)$ is recursively computed in the base 2 logarithmic domain from the resultant logarithmic scale factor $y(k)$ : + +$$y_u(k) = (1 - 2^{-5}) y(k) + 2^{-5} W[I(k)], \quad (2-2)$$ + +where $y_u(k)$ is limited by $1.06 \leq y_u(k) \leq 10.00$ . + +For 40 kbit/s ADPCM, the discrete function $W(I)$ is defined as follows (infinite precision values): + +| | | | | | | | | | +|-----------|-------|-------|-------|-------|-------|-------|-------|------| +| $ I(k) $ | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | +| $W[I(k)]$ | 43.50 | 33.06 | 27.50 | 22.38 | 17.50 | 13.69 | 11.19 | 8.81 | + + + +| | | | | | | | | | +|-----------|------|------|------|------|------|------|------|------| +| $ I(k) $ | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| $W[I(k)]$ | 6.29 | 3.63 | 2.56 | 2.50 | 2.44 | 1.50 | 0.88 | 0.88 | + +For 32 kbit/s ADPCM, the discrete function $W(I)$ is defined as follows (infinite precision values): + +| | | | | | | | | | +|-----------|-------|-------|-------|------|------|------|------|-------| +| $ I(k) $ | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| $W[I(k)]$ | 70.13 | 22.19 | 12.38 | 7.00 | 4.00 | 2.56 | 1.13 | -0.75 | + +For 24 kbit/s ADPCM, the discrete function $W(I)$ is defined as follows (infinite precision values): + +| | | | | | +|-----------|-------|------|------|-------| +| $ I(k) $ | 3 | 2 | 1 | 0 | +| $W[I(k)]$ | 36.38 | 8.56 | 1.88 | -0.25 | + +For 16 kbit/s APDCM, the discrete function $W(I)$ is defined as follows (infinite precision values): + +| | | | +|-----------|-------|-------| +| $ I(k) $ | 1 | 0 | +| $W[I(k)]$ | 27.44 | -1.38 | + +The factor $(1 - 2^{-5})$ introduces finite memory into the adaptive process so that the states of the encoder and decoder converge following transmission errors. + +The slow (locked) scale factor $y_l(k)$ is derived from $y_u(k)$ with a low pass-filter operation: + +$$y_l(k) = (1 - 2^{-6}) y_l(k - 1) + 2^{-6} y_u(k) \quad (2-3)$$ + +The fast and slow scale factors are then combined to form the resultant scale factor: + +$$y(k) = a_l(k) y_u(k - 1) + [1 - a_l(k)] y_l(k - 1) \quad (2-4)$$ + +where $0 \leq a_l(k) \leq 1$ (see § 2.6). + +### 2.6 Adaptation speed control + +The controlling parameter $a_I(k)$ can assume values in the range $[0, 1]$ . It tends towards unity for speech signals and towards zero for voiceband data signals. It is derived from a measure of the rate-of-change of the difference signal values. + +Two measures of the average magnitude of $I(k)$ are computed: + +$$d_{ms}(k) = (1 - 2^{-5}) d_{ms}(k - 1) + 2^{-5} F[I(k)] \quad (2-5)$$ + +and + +$$d_{ml}(k) = (1 - 2^{-7}) d_{ml}(k - 1) + 2^{-7} F[I(k)] \quad (2-6)$$ + +For 40 kbit/s ADPCM, $F[I(k)]$ is defined by: + +| | | | | | | | | | +|-----------|----|----|----|----|----|----|---|---| +| $ I(k) $ | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | +| $F[I(k)]$ | 6 | 6 | 5 | 4 | 3 | 2 | 1 | 1 | + +| | | | | | | | | | +|-----------|---|---|---|---|---|---|---|---| +| $ I(k) $ | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| $F[I(k)]$ | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | + +For 32 kbit/s ADPCM, $F[I(k)]$ is defined by: + +| | | | | | | | | | +|-----------|---|---|---|---|---|---|---|---| +| $ I(k) $ | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| $F[I(k)]$ | 7 | 3 | 1 | 1 | 1 | 0 | 0 | 0 | + +For 24 kbit/s ADPCM, $F[I(k)]$ is defined by: + +| | | | | | +|-----------|---|---|---|---| +| $ I(k) $ | 3 | 2 | 1 | 0 | +| $F[I(k)]$ | 7 | 2 | 1 | 0 | + +For 16 kbit/s ADPCM, $F[I(k)]$ is defined by: + +$$\frac{|I(k)|}{F[I(k)]} \begin{array}{c|c|c} 1 & 1 & 0 \\ 7 & 7 & 0 \end{array}$$ + +Thus $d_{ms}(k)$ is a relatively short term average of $F[I(k)]$ and $d_{ml}(k)$ is a relatively long term average of $F[I(k)]$ . + +Using these two averages, the variable $a_p(k)$ is defined: + +$$a_p(k) = \begin{cases} (1 - 2^{-4})a_p(k - 1) + 2^{-3}, \text{ if } |d_{ms}(k) - d_{ml}(k)| \geq 2^{-3} d_{ml}(k) \\ (1 - 2^{-4})a_p(k - 1) + 2^{-3}, \text{ if } y(k) < 3 \\ (1 - 2^{-4})a_p(k - 1) + 2^{-3}, \text{ if } t_d(k) = 1 \\ 1, \text{ if } t_r(k) = 1 \\ (1 - 2^{-4})a_p(k - 1), \text{ otherwise} \end{cases} \quad (2-7)$$ + +Thus, $a_p(k)$ tends towards the value 2 if the difference between $d_{ms}(k)$ and $d_{ml}(k)$ is large (average magnitude of $I(k)$ changing) and $a_p(k)$ tends towards the value 0 if the difference is small (average magnitude of $I(k)$ relatively constant). $a_p(k)$ also tends towards 2 for idle channel (indicated by $y(k) < 3$ ) or partial band signals (indicated by $t_d(k) = 1$ as described in § 2.8). Note that $a_p(k)$ is set to 1 upon detection of a partial band signal transition (indicated by $t_r(k) = 1$ , see § 2.8). + +$a_p(k - 1)$ is then limited to yield $a_l(k)$ used in Equation (2-4) above: + +$$a_l(k) = \begin{cases} 1, & a_p(k - 1) > 1 \\ a_p(k - 1), & a_p(k - 1) \leq 1. \end{cases} \quad (2-8)$$ + +This asymmetrical limiting has the effect of delaying the start of a fast to slow state transition until the absolute value of $I(k)$ remains constant for some time. This tends to eliminate premature transitions for pulsed input signals such as switched carrier voiceband data. + +### 2.7 Adaptive predictor and reconstructed signal calculator + +The primary function of the adaptive predictor is to compute the signal estimate $s_e(k)$ from the quantized difference signal $d_q(k)$ . Two adaptive predictor structures are used, a sixth order section that models zeros and a second order section that models poles in the input signal. This dual structure effectively caters for the variety of input signals which might be encountered. + +The signal estimate is computed by: + +$$s_e(k) = \sum_{i=1}^2 a_i(k-1) s_r(k-i) + s_{ez}(k), \quad (2-9)$$ + +where + +$$s_{ez}(k) = \sum_{i=1}^6 b_i(k-1) d_q(k-i),$$ + +and the reconstructed signal is defined as + +$$s_r(k-i) = s_e(k-i) + d_q(k-i).$$ + +Both sets of predictor coefficients are updated using a simplified gradient algorithm: + +for the second order predictor: + +$$a_1(k) = (1 - 2^{-8})a_1(k-1) + (3 \cdot 2^{-8}) \operatorname{sgn}[p(k)] \operatorname{sgn}[p(k-1)], \quad (2-10)$$ + +$$\begin{aligned} a_2(k) = & (1 - 2^{-7})a_2(k-1) + 2^{-7} \{ \operatorname{sgn}[p(k)] \operatorname{sgn}[p(k-2)] \\ & - f[a_1(k-1)] \operatorname{sgn}[p(k)] \operatorname{sgn}[p(k-1)] \}, \end{aligned} \quad (2-11)$$ + +where + +$$p(k) = d_q(k) + s_{ez}(k),$$ + +$$f(a_1) = \begin{cases} 4a_1, & |a_1| \leq 2^{-1} \\ 2 \operatorname{sgn}(a_1), & |a_1| > 2^{-1}, \end{cases}$$ + +and $\operatorname{sgn}[0] = 1$ , except $\operatorname{sgn}[p(k-i)]$ is defined to be 0 only if $p(k-i) = 0$ and $i = 0$ ; + +with the stability constraints: + +$$|a_2(k)| \leq 0.75 \text{ and } |a_1(k)| \leq 1 - 2^{-4} - a_2(k).$$ + +If $t_r(k) = 1$ ( see § 2.8), then $a_1(k) = a_2(k) = 0$ . + +For the sixth order predictor: + +$$b_i(k) = (1 - 2^{-8})b_i(k-1) + 2^{-7} \operatorname{sgn}[d_q(k)] \operatorname{sgn}[d_q(k-i)], \quad (2-12A)$$ + +for $i = 1, 2, \dots, 6$ . + +For 40 kbit/s coding, the adaptive predictor is changed to decrease the leak factor used for zeros coefficient operation. In this case, Equation 2.12A becomes: + +$$b_i(k) = (1 - 2^{-9})b_i(k - 1) + 2^{-7} \operatorname{sgn}[d_q(k)] \operatorname{sgn}[d_q(k - i)]. \quad (2-12B)$$ + +If $t_r(k) = 1$ (see § 2.8), then $b_1(k) = b_2(k) = \dots = b_6(k) = 0$ . + +As above, $\operatorname{sgn}[0] = 1$ , except $\operatorname{sgn}[d_q(k - i)]$ is defined to be 0 only if $d_q(k - i) = 0$ and $i = 0$ . Note that $b_i(k)$ is implicitly limited to $\pm 2$ . + +### 2.8 Tone and transition detector + +In order to improve performance for signals originating from frequency shift keying (FSK) modems operating in the character mode, a two-step detection process is defined. First, partial band signal (e.g. tone) detection is invoked so that the quantizer can be driven into the fast mode of adaptation: + +$$t_d(k) = \begin{cases} 1, & a_2(k) < -0.71875 \\ 0, & \text{otherwise} \end{cases} \quad (2-13)$$ + +In addition, a transition from a partial band signal is defined so that the predictor coefficients can be set to zero and the quantizer can be forced into the fast mode of adaptation: + +$$t_r(k) = \begin{cases} 1, & a_2(k) < -0.71875 \text{ and } |d_q(k)| > 24 \cdot 2^{y_f(k)} \\ 0, & \text{otherwise} \end{cases} \quad (2-14)$$ + +## 3 ADPCM decoder principles + +Figure 3/G.726 is a block schematic of the decoder. A functional description of each block is given in §§ 3.1 to 3.7 below. + +### 3.1 Inverse adaptive quantizer + +The function of this block is described in § 2.4. + +### 3.2 Quantizer scale factor adaptation + +The function of this block is described in § 2.5. + +### 3.3 Adaptation speed control + +The function of this block is described in § 2.6. + +### 3.4 Adaptive predictor and reconstructed signal calculator + +The functions of this block are described in § 2.7. + +![Block diagram of an ADPCM decoder. The input ADPCM signal I(k) enters an 'Inverse adaptive quantizer' to produce d_q(k). d_q(k) goes to a 'Reconstructed signal calculator' which outputs s_r(k). s_r(k) goes to 'Output PCM format conversion' to produce s_p(k), which then goes to 'Synchronous coding adjustment' to produce the final output s_d(k). Feedback loops involve an 'Adaptive predictor' (taking d_q(k) and s_r(k) to produce s_e(k) and a_2(k)), 'Quantizer scale factor adaptation' (taking I(k) and y(k) to produce y(k) and y_l(k)), 'Adaptation speed control' (taking I(k), y(k), and a_1(k) to produce a_1(k)), and a 'Tone and transition detector' (taking a_2(k), y_l(k), and d_q(k) to produce t_r(k) and t_d(k)).](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +graph LR + Input[ADPCM input] -- I(k) --> IAQ[Inverse adaptive quantizer] + IAQ -- d_q(k) --> RSC[Reconstructed signal calculator] + RSC -- s_r(k) --> OPFC[Output PCM format conversion] + OPFC -- s_p(k) --> SCA[Synchronous coding adjustment] + SCA -- s_d(k) --> Output[Output] + + RSC -- s_r(k) --> AP[Adaptive predictor] + AP -- s_e(k) --> RSC + AP -- a_2(k) --> TTD[Tone and transition detector] + + IAQ -- d_q(k) --> AP + IAQ -- d_q(k) --> TTD + + Input -- I(k) --> QSFA[Quantizer scale factor adaptation] + QSFA -- y(k) --> IAQ + QSFA -- y_l(k) --> TTD + + Input -- I(k) --> ASC[Adaptation speed control] + ASC -- a_1(k) --> QSFA + + TTD -- t_r(k) --> ASC + TTD -- t_d(k) --> ASC + + SCA -.-> RSC + SCA -.-> AP + +``` + +Block diagram of an ADPCM decoder. The input ADPCM signal I(k) enters an 'Inverse adaptive quantizer' to produce d\_q(k). d\_q(k) goes to a 'Reconstructed signal calculator' which outputs s\_r(k). s\_r(k) goes to 'Output PCM format conversion' to produce s\_p(k), which then goes to 'Synchronous coding adjustment' to produce the final output s\_d(k). Feedback loops involve an 'Adaptive predictor' (taking d\_q(k) and s\_r(k) to produce s\_e(k) and a\_2(k)), 'Quantizer scale factor adaptation' (taking I(k) and y(k) to produce y(k) and y\_l(k)), 'Adaptation speed control' (taking I(k), y(k), and a\_1(k) to produce a\_1(k)), and a 'Tone and transition detector' (taking a\_2(k), y\_l(k), and d\_q(k) to produce t\_r(k) and t\_d(k)). + +FIGURE 3/G.726 +**Decoder block schematic** + +### 3.5 Tone and transition detector + +The function of this block is described in § 2.8. + +### 3.6 Output PCM format conversion + +This block converts the reconstructed uniform PCM signal $s_r(k)$ into an A-law or $\mu$ -law PCM signal $s_p(k)$ as required. + +### 3.7 Synchronous coding adjustment + +The synchronous coding adjustment prevents cumulative distortion occurring on synchronous tandem codings (ADPCM-PCM-ADPCM, etc. digital connections), when: + +- i) the transmission of the ADPCM and the intermediate 64 kbit/s PCM signals is error free, and, +- ii) the ADPCM and intermediate 64 kbit/s PCM bit streams are not disturbed by digital signal processing devices. + +If the coder and decoder have different initial conditions, as may occur after switching for example, then the synchronous tandeming may take time to establish. Furthermore, if this property is disturbed or not acquired initially then it may be recovered for those signals of sufficient level with spectra that occupy the majority of the 200 to 3400 Hz band (e.g. speech, 4800 bit/s voiceband data). + +When a decoder is synchronously connected to an encoder, the synchronous coding adjustment block estimates quantization in the encoder. If all state variables in both the decoder and the encoder have identical values and there are no transmission errors, the forced equivalence of both 4-bit quantizer output sequences for all values of $k$ guarantees the property of non-accumulation of distortion. + +This is accomplished by first converting the A-law or $\mu$ -law signal $s_p(k)$ to a uniform PCM signal $s_{tx}(k)$ and then computing a difference signal $d_x(k)$ : + +$$d_x(k) = s_{tx}(k) - s_e(k). \quad (3-1)$$ + +The difference signal $d_x(k)$ is then compared to the ADPCM quantizer decision interval determined by $I(k)$ and $y(k)$ . The signal $s_d(k)$ is then defined as follows: + +$$s_d(k) = \begin{cases} s_p^+(k), & d_x(k) < \text{lower interval boundary} \\ s_p^-(k), & d_x(k) \geq \text{upper interval boundary} \\ s_p(k), & \text{otherwise} \end{cases} \quad (3-2)$$ + +where + +$s_d(k)$ is the output PCM code word of the decoder, + +$s_{pp}^+(k)$ is the PCM code word that represents the next more positive PCM output level (when $s_p(k)$ represents the most positive output level, then $s_{pp}^+(k)$ : is constrained to be the value $s_p(k)$ ), + +$s_{pp}^-(k)$ is the PCM code word that represents the next more negative PCM output level (when $s_p(k)$ represents the most negative output level, then $s_{pp}^-(k)$ : is constrained to be the value $s_p(k)$ ). + +## 4 Computational details + +Sections 4.1 and 4.2 provide the computational details for each of the encoder and decoder elements. + +Proper timing for the encoder and decoder is obtained by executing all of the delay blocks simultaneously and proceeding to calculate the signals which can be derived using this information. For example, SE signal of Figure 9/G.726 is calculated using delay values and then SE signal is used as shown in Figure 4/G.726. + +Implementations of the algorithm may be confirmed with a reasonable level of confidence by using the digital test sequences described in Appendix II to this Recommendation. The sequences are given in terms of encoder PCM input words, ADPCM words and decoder PCM output words. + +### 4.1 Input and output signals + +Table 2/G.726 defines the input and output signals for the encoder and decoder. + +An optional signal R represents a reset function that sets all internal memory elements to a specified condition so that an encoder or decoder can be forced into a known state, for applications which require an immediate reset function (e.g. digital circuit multiplication equipment, in which case the reset is mandatory, not optional). + +TABLE 5/G.726 + +#### **Input and output signals** + +| ENCODER | | | | +|---------|-----------------------|----------------|----------------------------------------------| +| | Name | Number of bits | Description | +| Input | S | 8 | PCM input word | +| Input | LAW | 1 | PCM law select, 0 = $\mu$ -law,
1 = A-law | +| Input | R ( optional ) | 1 | Reset | +| Output | I | 5 | 40 kbit/s ADPCM word | +| Output | I | 4 | 32 kbit/s ADPCM word | +| Output | I | 3 | 24 kbit/s ADPCM word | +| Output | I | 2 | 16 kbit/s ADPCM word | +| DECODER | | | | +| | Name | Number of bits | Description | +| Input | I | 5 | 40 kbit/s ADPCM word | +| Input | I | 4 | 32 kbit/s ADPCM word | +| Input | I | 3 | 24 kbit/s ADPCM word | +| Input | I | 2 | 16 kbit/s ADPCM word | +| Input | LAW | 1 | PCM law select, 0 = $\mu$ -law,
1 = A-law | +| Input | R ( optional ) | 1 | Reset | +| Output | SD | 8 | Decoder PCM output word | + +### 4.2 *Description of variables and detailed specification of sub-blocks* + +This section contains a detailed expansion of all blocks in Figures 2/G.726 and 3/G.726 described in §§ 2 and 3. The expansions are illustrated in Figures 4/G.726 to 11/G.726 with the internal processing variables as defined in Table 6/G.726. A brief functional description and full specification is given for each sub-block. + +The notations used in the sub-block descriptions are as follows: + +$\ll n$ denotes an $n$ -bit shift left operation (zero fill), + +$\gg n$ denotes an $n$ -bit shift right operation (in the direction of the least significant bit and zero fill), + +& denotes the logical “and” operation, + ++ denotes arithmetic addition, + +– denotes arithmetic subtraction, + +\* denotes arithmetic multiplication, + +\*\* denotes the logical “exclusive or” operation, + +| +| delineates comments to equations. +| + +TABLE 6/G.726 + +#### Internal processing variables + +| Name | Bits | Binary representation | Optional reset values | Description | +|-------------------------------------------|-------|-----------------------|-----------------------|-----------------------------------------------------------------| +| A1 a) , A2 a) | 16 TC | S, 0,..., -14 | 0 | Delayed predictor second order coefficients | +| A1P, A2P | 16 TC | S, 0,..., -14 | | Second order predictor coefficients | +| A1R, A2R | 16 TC | S, 0,..., -14 | | Triggered second order predictor coefficients | +| A1T | 16 TC | S, 0,..., -14 | | Unlimited $a_1$ coefficient | +| A2T | 16 TC | S, 0,..., -14 | | Unlimited $a_2$ coefficient | +| AL | 7 SM | 0,..., -6 | | Limited speed control parameter | +| AP a) | 10 SM | 1,..., -8 | 0 | Delayed unlimited speed control parameter | +| APP | 10 SM | 1,..., -8 | | Unlimited speed control parameter | +| APR | 10 SM | 1,..., -8 | | Triggered unlimited speed control parameter | +| AX | 1 SM | 1 | | Speed control parameter update | +| B1 a) ,..., B6 a) | 16 TC | S, 0,..., -14 | 0 | Delayed sixth order predictor coefficients | +| B1P,..., B6P | 16 TC | S, 0,..., -14 | | Sixth order predictor coefficients | +| B1R,..., B6R | 16 TC | S, 0,..., -14 | | Triggered sixth order predictor coefficients | +| D | 16 TC | S, 14,..., 0 | | Difference signal, only in encoder | +| DL | 11 SM | 3,..., -7 | | Log 2 (difference signal), only in encoder | +| DLN | 12 TC | S, 3,..., -7 | | Log 2 (normalized difference), only in encoder | +| DLNX | 12 TC | S, 3,..., -7 | | Log 2 (normalized difference), only in decoder | +| DLX | 11 SM | 3,..., -7 | | Log 2 (difference signal), only in decoder | +| DML a) | 14 SM | 2,..., -11 | 0 | Delayed long term average of F(I) sequence | +| DMLP | 14 SM | 2,..., -11 | | Long term average of F(I) sequence | +| DMS a) | 12 SM | 2,..., -9 | 0 | Delayed short term average of F(I) sequence | +| DMSP | 12 SM | 2,..., -9 | | Short term average of F(I) sequence | +| DQ b) | 15 SM | S, 13,..., 0 | | Quantized difference signal (16, 24 or 32 kbit/s operation) | +| DQ b) | 16 SM | S, 14,..., 0 | | Quantized difference signal (16, 24, 32 or 40 kbit/s operation) | +| DQ0 | 11 FL | S, 4e, 6m | | Quantized difference signal with delay 0 | +| DQ1 a) ,..., DQ6 a) | 11 FL | S, 4e, 6m | 32 | Quantized difference signal with delays 1 to 6 | +| DQL | 12 TC | S, 3,..., -7 | | Log 2 (quantized difference signal) | + +a) Indicates variables that are set to specific values by the optional reset. When reset is invoked, the output of the DELAY sub-block (see § 4.2.4) is given in column 4. + +b) For 40 kbit/s ADPCM, DQ must be implemented as a 16 bit signed magnitude. For 16, 24 and 32 kbit/s, DQ may be implemented as a 15 or 16 bit signed magnitude. + +TC denotes two's complement      e denotes exponent bits + +SM denotes signed magnitude      m denotes mantissa bits + +FL denotes floating point S      denotes sign bit + +TABLE 6/G.726 (continued) + +| Name | Bits | Binary representation | Optional reset values | Description | +|---------------------------------------|-------|-----------------------|-----------------------|----------------------------------------------------| +| DQLN | 12 TC | S, 3,..., -7 | | Log 2 (normalized quantized difference) | +| DQS | 1 TC | S | | Sign bit of quantized difference signal | +| DS | 1 TC | S | | Sign bit of difference signal, only in encoder | +| DSX | 1 TC | S | | Sign bit of difference signal, only in decoder | +| DX | 16 TC | S, 14,..., 0 | | Difference signal, only in decoder | +| FI | 3 SM | 2,..., 0 | | Output of F(I) | +| PK0 | 1 TC | S | | Sign of DQ + SEZ with delay 0 | +| PK1 a) , PK2 a) | 1 TC | S | 0 | Sign of DQ + SEZ with delays 1 and 2 | +| SE | 15 TC | S, 13,..., 0 | | Signal estimate | +| SEZ | 15 TC | S, 13,..., 0 | | Sixth order predictor partial signal estimate | +| SIGPK | 1 TC | 0 | | Sgn[p(k)] flag | +| SL | 14 TC | S, 12,..., 0 | | Linear input signal, only in encoder | +| SLX | 14 TC | S, 12,..., 0 | | Quantized reconstructed, signal, only in decoder | +| SP | 8 | | | PCM reconstructed signal, only in decoder | +| SR | 16 TC | S, 14,..., 0 | | Reconstructed signal | +| SR0 | 11 FL | S, 4e, 6m | | Reconstructed signal with delay 0 | +| SR1 a) , SR2 a) | 11 FL | S, 4e, 6m | 32 | Reconstructed signal with delays 1 and 2 | +| TD a) | 1 TC | 0 | 0 | Delayed tone detect | +| TDP | 1 TC | 0 | | Tone detect | +| TDR | 1 TC | 0 | | Triggered tone detect | +| TR | 1 TC | 0 | | Transition detect | +| U1,...,U6 | 1 TC | S | | Sixth order predictor coefficient update sign bit | +| WA1,WA2 | 16 TC | S, 13,..., -1 | | Partial product of signal estimate | +| WB1,...,WB6 | 16 TC | S, 13,..., -1 | | Partial product of signal estimate | +| WI | 12 TC | S, 6,..., -4 | | Quantizer multiplier | +| Y | 13 SM | 3,..., -9 | | Quantizer scale factor | +| YL a) | 19 SM | 3,..., -15 | 34816 | Delayed slow quantizer scale factor | +| YLP | 19 SM | 3,..., -15 | | Slow quantizer scale factor | +| YU a) | 13 SM | 3,..., -9 | 544 | Delayed fast quantizer scale factor | +| YUP | 13 SM | 3,..., -9 | | Fast quantizer scale factor | +| YUT | 13 SM | 3,..., -9 | | Unlimited fast quantizer scale factor | + +a) Indicates variables that are set to specific values by the optional reset. When reset is invoked, the output of the DELAY sub-block (see § 4.2.4) is given in column 4. + +TC denotes two's complement            e denotes exponent bits +SM denotes signed magnitude            m denotes mantissa bits +FL denotes floating pointS                denotes sign bit + +#### 4.2.1 Input PCM format conversion and difference signal computation + +![Block diagram showing the input PCM format conversion and difference signal computation. An input block with 'S' and 'LAW' signals enters an 'EXPAND' block. The 'EXPAND' block outputs 'SL' and 'SE' signals, which enter a 'SUBTA' block. The 'SUBTA' block outputs the final signal 'D'. The diagram is labeled T1508220-92.](7f25db95ce3916c0e09803b861a2f7bc_img.jpg) + +Block diagram showing the input PCM format conversion and difference signal computation. An input block with 'S' and 'LAW' signals enters an 'EXPAND' block. The 'EXPAND' block outputs 'SL' and 'SE' signals, which enter a 'SUBTA' block. The 'SUBTA' block outputs the final signal 'D'. The diagram is labeled T1508220-92. + +FIGURE 4/G.726 + +##### Input PCM format conversion and difference signal computation + +##### EXPAND + +Input: S (SP in decoder), LAW + Output: SL (SLX in decoder) + Function: Convert either A-law or $\mu$ -law PCM to uniform PCM. + +Decode PCM code word, S, according to Recommendation G.711 using character signals (column 6, before inversion of even bits for A-law) and values at decoder output (see column 7). The values at decoder output, SS, must be represented in 13-bit signed magnitude form for A-law PCM and 14-bit signed magnitude form for $\mu$ -law PCM (the sign bit is equal to one for negative values). + +*Note* – For A-law S (and SP) includes even bit inversion (see Note 2 below Table 1/G.711). + +| | | | +|------------------|--------------------|------------| +| when $LAW = 0$ , | $SSS = SS \gg 13$ | $\mu$ -law | +| | $SSQ = SS \& 8191$ | | +| when $LAW = 1$ , | $SSS = SS \gg 12$ | | +| | $SSM = SS \& 4095$ | A-law | +| | $SSQ = SSM \ll 1$ | | + +then + +| | | +|--------------------------------------------------------------------------------------|---------------------| +| $SL = \begin{cases} SSQ, & SSS = 0 \\ (16384 - SSQ) \& 16383, & SSS = 1 \end{cases}$ | Convert signed | +| | magnitude | +| | to two's complement | + +##### SUBTA + +Inputs: SL (SLX in decoder), SE + Output: D (DX in decoder) + Function: Compute difference signal by subtracting signal estimate from input signal (or quantized reconstructed signal in decoder). + +$$SLS = SL \gg 13$$ + +$$SLI = \begin{cases} SL, & SLS = 0 \\ 49152 + SL, & SLS = 1 \end{cases} \quad \left| \begin{array}{c} | \\ | \text{ Sign extension} \\ | \end{array} \right.$$ + +$$SES = SE \gg 14$$ + +$$SEI = \begin{cases} SE, & SES = 0 \\ 32768 + SE, & SES = 1 \end{cases} \quad \left| \begin{array}{c} | \\ | \text{ Sign extension} \\ | \end{array} \right.$$ + +$$D = (SLI + 65536 - SEI) \& 65535$$ + +#### 4.2.2 Adaptive quantizer + +![Block diagram of an adaptive quantizer. The input D enters a LOG block. The output of LOG is DL, which enters a SUBTB block. The SUBTB block also receives an input Y from below. The output of SUBTB is DLN, which enters a QUAN block. The output of QUAN is I. A feedback loop labeled DS connects the output I back to the input of the LOG block. A label T1508230-92 is present below the QUAN block.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +Block diagram of an adaptive quantizer. The input D enters a LOG block. The output of LOG is DL, which enters a SUBTB block. The SUBTB block also receives an input Y from below. The output of SUBTB is DLN, which enters a QUAN block. The output of QUAN is I. A feedback loop labeled DS connects the output I back to the input of the LOG block. A label T1508230-92 is present below the QUAN block. + +FIGURE 5/G.726 +**Adaptive quantizer** + +##### LOG + +Input: D (DX in decoder) + Outputs: DL (DLX in decoder), DS (DSX in decoder) + Function: Convert difference signal from the linear to the logarithmic domain. + +$$DS = D \gg 15$$ + +$$DQM = \begin{cases} D, & DS = 0 \\ (65536 - D) \& 32767, & DS = 1 \end{cases} \quad \begin{array}{l} | \text{Convert D from two's} \\ | \text{complement to signed} \\ | \text{magnitude} \end{array}$$ + +$$EXP = \begin{cases} 14, & 16384 \leq DQM \\ 13, & 8192 \leq DQM \leq 16383 \\ \vdots, & \vdots \\ 1, & 2 \leq DQM \leq 3 \\ 0, & 0 \leq DQM \leq 1 \end{cases} \quad \begin{array}{l} | \\ | \\ | \\ | \text{Compute exponent} \\ | \\ | \\ | \end{array}$$ + +$$MANT = ((DQM \ll 7) \gg EXP) \& 127 \quad \begin{array}{l} | \text{Compute approximation} \\ | \log_2(1+x) = x \end{array}$$ + +$$DL = (EXP \ll 7) + MANT \quad \begin{array}{l} | \text{Combine 7 mantissa bits and} \\ | \text{4 exponent bits into one} \\ | \text{11-bit word} \end{array}$$ + +##### QUAN (encoder only) + +Inputs: DLN, DS + Output: I + Function: Quantize difference signal in logarithmic domain. + +TABLE 7/G.726 + +##### **Quantizer decision levels and 5-bit outputs for 40 kbit/s ADPCM** + +| DS | DLN | I | | +|----|-----------|-------|-----------------------------------| +| | | 12345 | | +| 0 | 553-2047 | 01111 | | +| 0 | 528- 552 | 01110 | | +| 0 | 502- 527 | 01101 | | +| 0 | 475- 501 | 01100 | | +| 0 | 445- 474 | 01011 | | +| 0 | 413- 444 | 01010 | | +| 0 | 378- 412 | 01001 | | +| 0 | 339- 377 | 01000 | | +| 0 | 298- 338 | 00111 | | +| 0 | 250- 297 | 00110 | | +| 0 | 198- 249 | 00101 | | +| 0 | 139- 197 | 00100 | | +| 0 | 68- 138 | 00011 | | +| 0 | 0- 67 | 00010 | -- Positive portion of interval | +| 0 | 4080-4095 | 00010 | -- Negative portion of interval | +| 0 | 3974-4079 | 00001 | | +| 0 | 2048-3973 | 11111 | | +| 1 | 2048-3973 | 11111 | | +| 1 | 3974-4079 | 11110 | | +| 1 | 4080-4095 | 11101 | -- Negative portion of interval | +| 1 | 0- 67 | 11101 | -- Positive portion of interval | +| 1 | 68- 138 | 11100 | | +| 1 | 139- 197 | 11011 | | +| 1 | 198- 249 | 11010 | | +| 1 | 250- 297 | 11001 | | +| 1 | 298- 338 | 11000 | | +| 1 | 339- 377 | 10111 | | +| 1 | 378- 412 | 10110 | | +| 1 | 413- 444 | 10101 | | +| 1 | 445- 474 | 10100 | | +| 1 | 475- 501 | 10011 | | +| 1 | 502- 527 | 10010 | | +| 1 | 528- 552 | 10001 | | +| 1 | 553-2047 | 10000 | | + +*Note – The I values are transmitted starting with bit 1.* + +TABLE 8/G.726 + +##### **Quantizer decision levels and 4-bit outputs for 32 kbit/s ADPCM** + +| DS | DLN | I | | +|----|-----------|------|-----------------------------------| +| | | 1234 | | +| 0 | 400-2047 | 0111 | | +| 0 | 349- 399 | 0110 | | +| 0 | 300- 348 | 0101 | | +| 0 | 246- 299 | 0100 | | +| 0 | 178- 245 | 0011 | | +| 0 | 80- 177 | 0010 | | +| 0 | 0- 79 | 0001 | -- Positive portion of interval | +| 0 | 3972-4095 | 0001 | -- Negative portion of interval | +| 0 | 2048-3971 | 1111 | | +| 1 | 2048-3971 | 1111 | | +| 1 | 3972-4095 | 1110 | -- Negative portion of interval | +| 1 | 0- 79 | 1110 | -- Positive portion of interval | +| 1 | 80- 177 | 1101 | | +| 1 | 178- 245 | 1100 | | +| 1 | 246- 299 | 1011 | | +| 1 | 300- 348 | 1010 | | +| 1 | 349- 399 | 1001 | | +| 1 | 400-2047 | 1000 | | + +*Note* – The I values are transmitted starting with bit 1. + +TABLE 9/G.726 + +##### **Quantizer decision levels and 3-bit outputs for 24 kbit/s ADPCM** + +| DS | DLN | I | | +|----|-----------|-----|-----------------------------------| +| | | 123 | | +| 0 | 331-2047 | 011 | | +| 0 | 218- 330 | 010 | | +| 0 | 8- 217 | 001 | | +| 0 | 0- 7 | 111 | -- Positive portion of interval | +| 0 | 2048-4095 | 111 | -- Negative portion of interval | +| 1 | 2048-4095 | 111 | -- Negative portion of interval | +| 1 | 0- 7 | 111 | -- Positive portion of interval | +| 1 | 8- 217 | 110 | | +| 1 | 218- 330 | 101 | | +| 1 | 331-2047 | 100 | | + +*Note* – The I values are transmitted starting with bit 1. + +TABLE 10/G.726 + +##### **Quantizer decision levels and 2-bit outputs for 16 kbit/s ADPCM** + +| DS | DLN | I | | +|----|-----------|----|-----------------------------------| +| | | 12 | | +| 0 | 261-2047 | 01 | -- Positive portion of interval | +| 0 | 0- 260 | 00 | -- Negative portion of interval | +| 0 | 2048-4095 | 00 | -- Negative portion of interval | +| 1 | 2048-4095 | 11 | -- Negative portion of interval | +| 1 | 0- 260 | 11 | -- Positive portion of interval | +| 1 | 261-2047 | 10 | | + +##### **SUBTB** + +Inputs: DL (DLX in decoder), Y + Output: DLN (DLNX in decoder) + Function: Scale logarithmic version of difference signal by subtracting scale factor. + +$$DLN = (DL + 4096 - (Y \gg 2)) \& 4095$$ + +#### 4.2.3 Inverse adaptive quantizer + +![Block diagram of the Inverse adaptive quantizer. The input Ie(k) enters a RECONST block, which outputs DQLN_FB. This signal enters an ADDA block along with input Y. The output of the ADDA block is DQL_FB, which enters an ANTILOG block. The ANTILOG block outputs DQ_FB. A feedback loop labeled DQS_FB connects the output of the ANTILOG block back to the RECONST block. The diagram is labeled T1508240-92.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +Block diagram of the Inverse adaptive quantizer. The input Ie(k) enters a RECONST block, which outputs DQLN\_FB. This signal enters an ADDA block along with input Y. The output of the ADDA block is DQL\_FB, which enters an ANTILOG block. The ANTILOG block outputs DQ\_FB. A feedback loop labeled DQS\_FB connects the output of the ANTILOG block back to the RECONST block. The diagram is labeled T1508240-92. + +FIGURE 6/G.726 +**Inverse adaptive quantizer** + +##### **ADDA** + +Inputs: DQLN, Y + Output: DQL + Function: Addition of scale factor to logarithmic version of quantized difference signal. + +$$DQL = (DQLN + (Y \gg 2)) \& 4095$$ + +##### ANTILOG + +Inputs: DQL, DQS + Output: DQ + Function: Convert quantized difference signal from the logarithmic to the linear domain. + +$$\begin{aligned} + DS &= DQL \gg 11 && | \text{Extract 4-bit exponent} \\ + DEX &= (DQL \gg 7) \& 15 \\ + DMN &= DQL \& 127 && | \text{Extract 7-bit mantissa} \\ + DQT &= (1 \ll 7) + DMN && | \text{Convert mantissa to linear using} \\ + DQMAG &= \begin{cases} (DQT \ll 7) \gg (14 - DEX), & DS = 0 \\ 0, & DS = 1 \end{cases} && | \text{approximation } 2^x = 1 + x \\ + DQ &= \begin{cases} (DQS \ll 14) + DQMAG: \text{ for 15 SM DQ} \\ (DQS \ll 15) + DQMAG: \text{ for 16 SM DQ} \end{cases} && | \text{Attach sign bit to signed} \\ + & && | \text{magnitude word} + \end{aligned}$$ + + +--- + +##### RECONST + +Input: I + Outputs: DQLN, DQS + Function: Reconstruction of quantized difference signal in the logarithmic domain. + +For 40 kbit/s ADPCM: + +$$DQS = I \gg 4$$ + +TABLE 11/G.726 + +##### **Quantizer output levels for 40 kbit/s ADPCM** + +| I | DQS | DQLN | +|-------|-----|------| +| 12345 | | | +| 01111 | 0 | 566 | +| 01110 | 0 | 539 | +| 01101 | 0 | 514 | +| 01100 | 0 | 488 | +| 01011 | 0 | 459 | +| 01010 | 0 | 429 | +| 01001 | 0 | 395 | +| 01000 | 0 | 358 | +| 00111 | 0 | 318 | +| 00110 | 0 | 274 | +| 00101 | 0 | 224 | +| 00100 | 0 | 169 | +| 00011 | 0 | 104 | +| 00010 | 0 | 28 | +| 00001 | 0 | 4030 | +| 00000 | 0 | 2048 | +| 11111 | 1 | 2048 | +| 11110 | 1 | 4030 | +| 11101 | 1 | 28 | +| 11100 | 1 | 104 | +| 11011 | 1 | 169 | +| 11010 | 1 | 224 | +| 11001 | 1 | 274 | +| 11000 | 1 | 318 | +| 10111 | 1 | 358 | +| 10110 | 1 | 395 | +| 10101 | 1 | 429 | +| 10100 | 1 | 459 | +| 10011 | 1 | 488 | +| 10010 | 1 | 514 | +| 10001 | 1 | 539 | +| 10000 | 1 | 566 | + +*Note 1* – The I values are received starting with bit 1. + +*Note 2* – It is possible for the decoder to receive the code word 00000 because of transmission disturbances (e.g., line bit errors). + +For 32 kbit/s ADPCM: + +$$DQS = I \gg 3$$ + +TABLE 12/G.726 + +##### **Quantizer output levels for 32 kbit/s ADPCM** + +| I | DQS | DQLN | +|------|-----|------| +| 1234 | | | +| 0111 | 0 | 425 | +| 0110 | 0 | 373 | +| 0101 | 0 | 323 | +| 0100 | 0 | 273 | +| 0011 | 0 | 213 | +| 0010 | 0 | 135 | +| 0001 | 0 | 4 | +| 0000 | 0 | 2048 | +| 1111 | 1 | 2048 | +| 1110 | 1 | 4 | +| 1101 | 1 | 135 | +| 1100 | 1 | 213 | +| 1011 | 1 | 273 | +| 1010 | 1 | 323 | +| 1001 | 1 | 373 | +| 1000 | 1 | 425 | + +*Note 1* – The I values are received starting with bit 1. + +*Note 2* – It is possible for the decoder to receive the code word 0000 because of transmission disturbances (e.g., line bit errors). + +For 24 kbit/s ADPCM: + +$$DQS = I \gg 2$$ + +TABLE 13/G.726 + +##### **Quantizer output levels for 24 kbit/s ADPCM** + +| I | DQS | DQLN | +|-----|-----|------| +| 123 | | | +| 011 | 0 | 373 | +| 010 | 0 | 273 | +| 001 | 0 | 135 | +| 000 | 0 | 2048 | +| 111 | 1 | 2048 | +| 110 | 1 | 135 | +| 101 | 1 | 273 | +| 100 | 1 | 373 | + +*Note 1* – The I values are received starting with bit 1. + +*Note 2* – It is possible for the decoder to receive the code word 000 because of transmission disturbance (e.g. line bit errors). + +For 16 kbit/s ADPCM: + +$$DQS = I \gg 1$$ + +TABLE 14/G.726 + +##### **Quantizer output levels for 16 kbit/s** + +| I | DQS | DQLN | +|----|-----|------| +| 12 | | | +| 01 | 0 | 365 | +| 00 | 0 | 116 | +| 11 | 1 | 116 | +| 10 | 1 | 365§ | + +*Note 1* – The I values are received starting with bit 1. + +#### 4.2.4 Quantizer scale factor adaptation + +![Block diagram of quantizer scale factor adaptation. Input Ic goes to FUNCTW block, output WI goes to FILTD block. FILTD block also receives feedback from output Y and produces YUT. YUT goes to LIMB block, output YUP goes to a DELAY block. DELAY block also receives input R and produces YU. YU goes to MIX block. YUP also goes to FILTE block, output YLP goes to another DELAY block. This DELAY block also receives input R and produces YL. YL goes to MIX block. MIX block also receives input AL and produces output Y. Output Y is fed back to FILTD block. Reference T1508250-92 is shown at the bottom right.](2bacc162a73d75c43a7f90715832bd13_img.jpg) + +Block diagram of quantizer scale factor adaptation. Input Ic goes to FUNCTW block, output WI goes to FILTD block. FILTD block also receives feedback from output Y and produces YUT. YUT goes to LIMB block, output YUP goes to a DELAY block. DELAY block also receives input R and produces YU. YU goes to MIX block. YUP also goes to FILTE block, output YLP goes to another DELAY block. This DELAY block also receives input R and produces YL. YL goes to MIX block. MIX block also receives input AL and produces output Y. Output Y is fed back to FILTD block. Reference T1508250-92 is shown at the bottom right. + +FIGURE 7/G.726 +Quantizer scale factor adaptation + +##### DELAY + +Inputs: x, R (optional) +Output: y +Function: Memory block. For the input x, the output is given by: + +$$y(k) = \begin{cases} x(k-1), & R = 0 \\ \text{optional reset value given in column 4 of Table 6/G.726, } R = 1 & | \text{ optional reset} \end{cases}$$ + +##### FILTD + +Inputs: WI, Y +Output: YUT +Function: Update of fast quantizer scale factor. + +$$DIF = ((WI \ll 5) + 131072 - Y) \& 131071, DIFS = DIF \gg 16 \quad | \text{ Compute difference}$$ + +$$DIFSX = \begin{cases} DIF \gg 5, & DIFS = 0 \\ (DIF \gg 5) + 4096, & DIFS = 1 \end{cases} \quad \begin{array}{l} | \text{ Time constant is } 1/32, \\ | \text{ Sign extension} \end{array}$$ + +$$YUT = (Y + DIFSX) \& 8191$$ + +##### FILTE + +Inputs: YUP, YL + Output: YLP + Function: Update of slow quantizer scale factor. + +$DIF = (YUP + ((1048576 - YL) \gg 6)) \& 16383$ | Compute difference + $DIFS = DIF \gg 13$ | Time constant is 1/64 + +$DIFSX = \begin{cases} DIF, & DIFS = 0 \\ DIF + 507904, & DIFS = 1 \end{cases}$ | Sign extension + +$YLP = (YL + DIFSX) \& 524287$ + +##### FUNCTW + +Input: I + Output: WI + Function: Map quantizer output into logarithmic version of scale factor multiplier. + +For 40 kbit/s ADPCM: + +$IS = I \gg 4$ + +$IM = \begin{cases} I \& 15, & IS = 0 \\ (31 - I) \& 15, & IS = 1 \end{cases}$ + +$WI = \begin{cases} 696, & IM = 15 \\ 529, & IM = 14 \\ 440, & IM = 13 \\ 358, & IM = 12 \\ 280, & IM = 11 \\ 219, & IM = 10 \\ 179, & IM = 9 \\ 141, & IM = 8 \\ 100, & IM = 7 \\ 58, & IM = 6 \\ 41, & IM = 5 \\ 40, & IM = 4 \\ 39, & IM = 3 \\ 24, & IM = 2 \\ 14, & IM = 1 \\ 14, & IM = 0 \end{cases}$ | Scale factor multipliers + +For 32 kbit/s ADPCM: + +$$IS = I \gg 3$$ + +$$IM = \begin{cases} I \& 7, & IS = 0 \\ (15 - I) \& 7, & IS = 1 \end{cases}$$ + +$$WI = \begin{cases} 1122, & IM = 7 \\ 355, & IM = 6 \\ 198, & IM = 5 \\ 112, & IM = 4 \\ 64, & IM = 3 \\ 41, & IM = 2 \\ 18, & IM = 1 \\ 4084, & IM = 0 \end{cases} \quad \text{Scale factor multipliers}$$ + +For 24 kbit/s ADPCM: + +$$IS = I \gg 2$$ + +$$IM = \begin{cases} I \& 3, & IS = 0 \\ (7 - I) \& 3, & IS = 1 \end{cases}$$ + +$$WI = \begin{cases} 582, & IM = 3 \\ 137, & IM = 2 \\ 30, & IM = 1 \\ 4092, & IM = 0 \end{cases} \quad \text{Scale factor multipliers}$$ + +For 16 kbit/s ADPCM: + +$$IS = I \gg 1$$ + +$$IM = \begin{cases} I \& 1, & IS = 0 \\ (3 - I) \& 1, & IS = 1 \end{cases}$$ + +$$WI = \begin{cases} 439, & IM = 1 \\ 4074, & IM = 0 \end{cases} \quad \text{Scale factor multipliers}$$ + +##### LIMB + +Input: YUT + Output: YUP + Function: Limit quantizer scale factor. + +$$GEUL = ((YUT + 11264) \& 16383) \gg 13$$ + +$$GELL = ((YUT + 15840) \& 16383) \gg 13$$ + +$$YUP = \begin{cases} 544, GELL = 1 & | \text{ Set lower limit to 1.06} \\ 5120, GEUL = 0 & | \text{ Set upper limit to 10.00} \\ YUT, \text{ otherwise} & \end{cases}$$ + + +--- + +##### MIX + +Inputs: AL, YU, YL + Output: Y + Function: Form linear combination of fast and slow quantizer scale factors. + +$$DIF = (YU + 16384 - (YL \gg 6)) \& 16383 \quad | \text{ Compute difference}$$ + +$$DIFS = DIF \gg 13 \quad |$$ + +$$DIFM = \begin{cases} DIF, & DIFS = 0 \\ (16384 - DIF) \& 8191, & DIFS = 1 \end{cases} \quad \begin{array}{l} | \text{ Compute magnitude} \\ | \text{ of difference} \\ | \end{array}$$ + +$$PROD = (DIFM * AL) \gg 6 \quad \begin{array}{l} | \text{ Compute magnitude} \\ | \text{ of product} \end{array}$$ + +$$PROD = \begin{cases} PROD, & DIFS = 0 \\ (16384 - PROD) \& 16383, & DIFS = 1 \end{cases} \quad \begin{array}{l} | \text{ Convert magnitude to} \\ | \text{ two's complement} \\ | \end{array}$$ + +$$Y = ((YL \gg 6) + PROD) \& 8191$$ + +#### 4.2.5 Adaptation speed control + +![Block diagram of the adaptation speed control system. The input Ic enters a FUNCTF block, producing FI. FI is split into two parallel paths: one through FILTA to produce DSMP, and another through FILTB to produce DMLP. Both DSMP and DMLP enter a SUBTC block. The SUBTC block also receives inputs Y, TDP, and AX. The output of SUBTC is APP, which enters a FILTC block. The output of FILTC is TRIGA, which receives input TR. The output of TRIGA is APR, which enters a DELAY block. The output of this DELAY block is AP, which enters a LIMA block to produce the final output AL. There are two feedback loops: one from the output of the first DELAY block (labeled R) back to the FILTA block (labeled DMS), and another from the output of the second DELAY block (labeled R) back to the FILTB block (labeled DML). A reference number T1508260-92 is shown near the LIMA block.](c76da2d73c064464051d1583fd80bb6b_img.jpg) + +Block diagram of the adaptation speed control system. The input Ic enters a FUNCTF block, producing FI. FI is split into two parallel paths: one through FILTA to produce DSMP, and another through FILTB to produce DMLP. Both DSMP and DMLP enter a SUBTC block. The SUBTC block also receives inputs Y, TDP, and AX. The output of SUBTC is APP, which enters a FILTC block. The output of FILTC is TRIGA, which receives input TR. The output of TRIGA is APR, which enters a DELAY block. The output of this DELAY block is AP, which enters a LIMA block to produce the final output AL. There are two feedback loops: one from the output of the first DELAY block (labeled R) back to the FILTA block (labeled DMS), and another from the output of the second DELAY block (labeled R) back to the FILTB block (labeled DML). A reference number T1508260-92 is shown near the LIMA block. + +FIGURE 8/G.726 +Adaptation speed control + +##### DELAY + +See § 4.2.4 for specification. + +##### FILTA + +Inputs: FI, DMS + Output: DMSP + Function: Update of short-term average of F(I). + +$$\begin{aligned} DIF &= ((FI \ll 9) + 8192 - DMS) \& 8191 && | \text{Compute difference} \\ DIFS &= DIF \gg 12 && | \end{aligned}$$ + +$$DIFSX = \begin{cases} DIF \gg 5, & DIFS = 0 \\ (DIF \gg 5) + 3840, & DIFS = 1 \end{cases} \quad \begin{aligned} &| \\ &| \text{Time constant is } 1/32, \\ &| \text{Sign extension} \\ &| \end{aligned}$$ + +$$DMSP = (DIFSX + DMS) \& 4095$$ + +##### FILTB + +Inputs: FI, DML + Output: DMLP + Function: Update of long-term average of F(I). + +$$DIF = ((FI \ll 11) + 32768 - DML) \& 32767 \quad | \text{ Compute difference}$$ + +$$DIFS = DIF \gg 14 \quad |$$ + +$$DIFSX = \begin{cases} DIF \gg 7, & DIFS = 0 \\ (DIF \gg 7) + 16128, & DIFS = 1 \end{cases} \quad \begin{array}{l} | \\ | \text{ Time constant is } 1/28, \\ | \text{ Sign extension} \\ | \end{array}$$ + +$$DMLP = (DIFSX + DML) \& 16383$$ + + +--- + +##### FILTC + +Inputs: AX, AP + Output: APP + Function: Low pass filter of speed control parameter. + +$$DIF = ((AX \ll 9) + 2048 - AP) \& 2047 \quad | \text{ Compute difference}$$ + +$$DIFS = DIF \gg 10 \quad |$$ + +$$DIFSX = \begin{cases} DIF \gg 4, & DIFS = 0 \\ (DIF \gg 4) + 896, & DIFS = 1 \end{cases} \quad \begin{array}{l} | \\ | \text{ Time constant is } 1/16, \\ | \text{ Sign extension} \\ | \end{array}$$ + +$$APP = (DIFSX + AP) \& 1023$$ + + +--- + +Input: I + Output: FI + Function: Map quantizer output into the F(I) function. + +For 40 kbit/s ADPCM: + +$$IS = I \gg 4$$ + +$$IM = \begin{cases} I \& 15, & IS = 0 \\ (31 - I) \& 15, & IS = 1 \end{cases}$$ + +$$FI = \begin{cases} 0, & 0 \leq IM \leq 4 \\ 1, & 5 \leq IM \leq 9 \\ 2, & IM = 10 \\ 3, & IM = 11 \\ 4, & IM = 12 \\ 5, & IM = 13 \\ 6, & IM = 14 \\ 6, & IM = 15 \end{cases}$$ + +For 32 kbit/s ADPCM: + +$$IS = I \gg 3$$ + +$$IM = \begin{cases} I \& 7, & IS = 0 \\ (15 - I) \& 7, & IS = 1 \end{cases}$$ + +$$FI = \begin{cases} 0, & 0 \leq IM \leq 2 \\ 1, & 3 \leq IM \leq 5 \\ 3, & IM = 6 \\ 7, & IM = 7 \end{cases}$$ + +For 24 kbit/s ADPCM: + +$$IS = I \gg 2$$ + +$$IM = \begin{cases} I \& 3, & IS = 0 \\ (7 - I) \& 3, & IS = 1 \end{cases}$$ + +$$FI = \begin{cases} 0, & IM = 0 \\ 1, & IM = 1 \\ 2, & IM = 2 \\ 7, & IM = 3 \end{cases}$$ + +For 16 kbit/s ADPCM: + +$$IS = I \gg 1$$ + +$$IM = \begin{cases} I \& 1, & IS = 0 \\ (3 - I) \& 1, & IS = 1 \end{cases}$$ + +$$FI = \begin{cases} 7, & IM = 1 \\ 0, & IM = 0 \end{cases}$$ + +##### LIMA + +Input: AP + Output: AL + Function: Limit speed control parameter. + +$$AL = \begin{cases} 64, & AP \geq 256 \\ AP \gg 2, & AP \leq 255 \end{cases}$$ + + +--- + +##### SUBTC + +Inputs: DMSP, DMLP, TDP, Y + Output: AX + Function: Compute magnitude of the difference of short and long term functions of quantizer output sequence and then perform threshold comparison for quantizing speed control parameter. + +$$\begin{aligned} DIF &= ((DMSP \ll 2) + 32768 - DMLP) \& 32767 && | \text{Compute difference} \\ DIFS &= DIF \gg 14 && | \end{aligned}$$ + +$$DIFM = \begin{cases} DIF, & DIFS = 0 \\ (32768 - DIF) \& 16383, & DIFS = 1 \end{cases} \quad \begin{aligned} &| \\ &| \text{Compute magnitude,} \\ &| \text{of difference} \\ &| \end{aligned}$$ + +$$DTHR = DMLP \gg 3$$ + +$$AX = \begin{cases} 0, & Y \geq 1536 \text{ and } DIFM < DTHR \text{ and } TDP = 0 \\ 1, & \text{otherwise} \end{cases}$$ + + +--- + +##### TRIGA + +Inputs: TR, APP +Output: APR +Function: Speed control trigger block. + +$$APR = \begin{cases} APP, & TR = 0 \\ 256, & TR = 1 \end{cases}$$ + +--- + +#### 4.2.6 Adaptive predictor and reconstructed signal calculator + +##### ACCUM + +Inputs: WA1, WA2, WB1, WB2, WB3, WB4, WB5, WB6 +Outputs: SE, SEZ +Function: Addition of predictor outputs to form the partial signal estimate (from the sixth order predictor) and the signal estimate. + +$$SEZI = ((((((((WB1 + WB2) \& 65535) + WB3) \& 65535) + WB4) \& 65535) + WB5) \& 65535) + WB6) \& 65535) \quad | \text{ Sum for partial signal estimate}$$ + +$$SEI = (((SEZI + WA2) \& 65535) + WA1) \& 65535) \quad | \text{ Complete sum for signal estimate}$$ + +$$SEZ = SEZI \gg 1$$ + +$$SE = SEI \gg 1$$ + +--- + +![Block diagram of an adaptive predictor and reconstructed signal calculator (FIGURE 9/G.726).](02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg) + +The diagram illustrates the signal processing flow for an adaptive predictor and reconstructed signal calculator. The main components and their connections are as follows: + +- Inputs:** $DQ_{FB}$ , $SEZ$ , $R$ , $SE$ , $TR$ , $SIGPK$ , $PK0$ , $PK1$ , $PK2$ . +- Top Processing Path:** + - $SEZ$ and $DQ_{FB}$ are inputs to **ADDC**. **ADDC** outputs $SIGPK$ , $PK0$ , and an intermediate signal. + - The intermediate signal from **ADDC** passes through a **DELAY** block (input $R$ ) to produce $PK1$ and another intermediate signal. + - This signal passes through another **DELAY** block (input $R$ ) to produce $PK2$ . + - $DQ_{FB}$ also branches to **FLOATA**, which outputs $DQ0$ . + - $DQ0$ passes through a **DELAY** block (input $R$ ) to produce $DQ1$ . + - $DQ1$ passes through a **DELAY** block (input $R$ ) to produce $DQ5$ . + - $DQ5$ passes through a **DELAY** block (input $R$ ) to produce $DQ6$ . +- Middle Processing Path:** + - $DQ_{FB}$ branches to **XOR**, which outputs $U1$ . + - $U1$ and $DQ_{FB}$ are inputs to **UPB**, which outputs $B1P$ . + - $B1P$ and $TR$ are inputs to **TRIGB**, which outputs $B1R$ . + - $B1R$ passes through a **DELAY** block (input $R$ ) to produce $B1$ . + - $B1$ and $DQ6$ are inputs to **FMULT**, which outputs $WB1$ and $WB6$ . +- Bottom Processing Path:** + - $DQ_{FB}$ branches to **ADDB** (input $SE$ ), which outputs $SR_{FB}$ . + - $SR_{FB}$ passes through **FLOATB** to produce $SR0$ . + - $SR0$ passes through a **DELAY** block (input $R$ ) to produce $SR1$ . + - $SR1$ passes through a **DELAY** block (input $R$ ) to produce $SR2$ . + - $SIGPK$ , $PK0$ , $PK1$ , and $PK2$ are inputs to **UPA2**, which outputs $A2T$ . + - $A2T$ passes through **LIMC** to produce $A2P$ . + - $A2P$ and $TR$ are inputs to **TRIGB**, which outputs $A2R$ . + - $A2R$ passes through a **DELAY** block (input $R$ ) to produce $A2$ . + - $A2$ and $SR2$ are inputs to **FMULT**, which outputs $WA2$ . + - $SIGPK$ , $PK0$ , $PK1$ , and $SR2$ are inputs to **UPA1**, which outputs $A1T$ . + - $A1T$ passes through **LIMD** to produce $A1P$ . + - $A1P$ and $TR$ are inputs to **TRIGB**, which outputs $A1R$ . + - $A1R$ passes through a **DELAY** block (input $R$ ) to produce $A1$ . + - $A1$ and $SR1$ are inputs to **FMULT**, which outputs $WA1$ . +- Accumulation:** + - $WB1$ , $WB6$ , $WA2$ , and $WA1$ are inputs to the **ACCUM** block. + - The **ACCUM** block outputs $SEZ$ and $SE$ . + +Block diagram of an adaptive predictor and reconstructed signal calculator (FIGURE 9/G.726). + +FIGURE 9/G.726 +Adaptive predictor and reconstructed signal calculator + +T1508270-92 + +##### ADDB + +Inputs: DQ, SE + Output: SR + Function: Addition of quantized difference signal and signal estimate to form reconstructed signal. + +$$DQS = \begin{cases} DQ \gg 14: \text{for 15 SM DQ} \\ DQ \gg 15: \text{for 16 SM DQ} \end{cases}$$ + +$$DQI = \begin{cases} DQ, & DQS = 0 \\ (65536 - (DQ \& 16383)) \& 65535, & DQS = 1: \text{for 15 SM DQ} \\ (65536 - (DQ \& 32767)) \& 65535, & DQS = 1: \text{for 16 SM DQ} \end{cases}$$ + +| Convert signed + | magnitude to + | two's complement + | + +$$SES = SE \gg 14$$ + +$$SEI = \begin{cases} SE, & SES = 0 \\ (1 \ll 15) + SE, & SES = 1 \end{cases}$$ + +| + | Sign extension + | + +$$SR = (DQI + SEI) \& 65535$$ + + +--- + +##### ADDC + +Inputs: DQ, SEZ + Output: PK0, SIGPK + Function: Obtain sign of addition of quantized difference signal and partial signal estimate. + +$$DQS = \begin{cases} (DQ \gg 14): \text{for 15 SM DQ} \\ (DQ \gg 15): \text{for 16 SM SQ} \end{cases}$$ + +$$DQI = \begin{cases} DQ, & DQS = 0 \\ (65536 - (DQ \& 16383)) \& 65535, & DQS = 1: \text{for 15 SM DQ} \\ (65536 - (DQ \& 32767)) \& 65535, & DQS = 1: \text{for 16 SM DQ} \end{cases}$$ + +| +| Convert signed +| magnitude to +| two's complement + +$$SEZS = SEZ \gg 14$$ + +$$SEZI = \begin{cases} SEZ, & SEZS = 0 \\ (1 \ll 15) + SEZ, & SEZS = 1 \end{cases}$$ + +| +| Sign extension +| + +$$DQSEZ = (DQI + SEZI) \& 65535$$ + +$$PK0 = DQSEZ \gg 15$$ + +$$SIGPK = \begin{cases} 1, & DQSEZ = 0 \\ 0, & \text{otherwise} \end{cases}$$ + +##### DELAY + +See § 4.2.4 for specification. + +##### FLOATA + +Input: DQ + Output: DQ0 + Function: Convert 15-bit or 16-bit signed magnitude to floating point. + +$$DQS = \begin{cases} DQ \gg 14: \text{for 15 SM DQ} \\ DQ \gg 15: \text{for 16 SM DQ} \end{cases}$$ + +$$MAG = \begin{cases} DQ \& 16383: \text{for 15 SM DQ} \\ DQ \& 32767: \text{for 16 SM DQ} \end{cases} \quad \begin{array}{l} | \text{Compute magnitude} \\ | \end{array}$$ + +$$EXP = \begin{cases} 15, & 16384 \leq MAG: \text{for 16 SM DQ} \\ 14, & 8192 \leq MAG \leq 16383: \text{for 16 SM DQ} \\ 14, & 8192 \leq MAG: \text{for 15 SM DQ} \\ 13, & 4096 \leq MAG \leq 8191 \\ \vdots, & \vdots \\ 2, & 2 \leq MAG \leq 3 \\ 1, & MAG = 1 \\ 0, & MAG = 0 \end{cases} \quad \begin{array}{l} | \\ | \\ | \\ | \\ | \text{Compute exponent} \\ | \\ | \\ | \\ | \\ | \end{array}$$ + +$$MANT = \begin{cases} 1 \ll 5, & MAG = 0 \\ (MAG \ll 6) \gg EXP, & \text{otherwise} \end{cases} \quad \begin{array}{l} | \text{Compute mantissa with a} \\ | 1 \text{ in the most} \\ | \text{significant bit} \end{array}$$ + +$$DQ0 = (DQS \ll 10) + (EXP \ll 6) + MANT \quad \begin{array}{l} | \text{Combine sign bit, 4 exponent} \\ | \text{bits and 6 mantissa bits} \\ | \text{into one 11-bit word} \end{array}$$ + +##### FLOATB + +Input: SR + Output: SR0 + Function: Convert 16-bit two's complement to floating point. + +$$SRS = SR \gg 15$$ + +$$MAG = \begin{cases} SR, & SRS = 0 \\ (65536 - SR) \& 32767, & SRS = 1 \end{cases} \quad \begin{array}{l} | \\ | \text{ Compute magnitude} \\ | \end{array}$$ + +$$EXP = \begin{cases} 15, & 16384 \leq MAG \\ 14, & 8192 \leq MAG \leq 16383 \\ \vdots, & \vdots \\ 2, & 2 \leq MAG \leq 3 \\ 1, & MAG = 1 \\ 0, & MAG = 0 \end{cases} \quad \begin{array}{l} | \\ | \\ | \\ | \\ | \text{ Compute exponent} \\ | \\ | \end{array}$$ + +$$MANT = \begin{cases} 1 \ll 5, & MAG = 0 \\ (MAG \ll 6) \gg EXP, & \text{otherwise} \end{cases} \quad \begin{array}{l} | \text{ Compute mantissa with a} \\ | \text{ 1 in the most} \\ | \text{ significant bit} \end{array}$$ + +$$SR0 = (SRS \ll 10) + (EXP \ll 6) + MANT \quad \begin{array}{l} | \text{ Combine sign bit, 4 exponent} \\ | \text{ bits and 6 mantissa bits} \\ | \text{ into one 11-bit word} \end{array}$$ + +##### FMULT + +Inputs: An or Bn, SRn or DQn + Output: WAn or WBn + Note: Equations are given for An, SRn and WAn. + The equations are also valid when substituting Bn for An, DQn for SRn and WBn for WAn. + Function: Multiply predictor coefficients with corresponding quantized difference signal or reconstructed signal. + Multiplication is done in floating point format. + +$$AnS = An \gg 15$$ + +$$AnMAG = \begin{cases} An \gg 2 & AnS = 0 \\ (16384 - (An \gg 2)) \& 8191 & AnS = 1 \end{cases} \quad \begin{array}{l} | \text{Convert two's} \\ | \text{complement to} \\ | \text{signed magnitude} \end{array}$$ + +$$AnEXP = \begin{cases} 13, & 4096 \leq AnMAG \\ 12, & 2048 \leq AnMAG \leq 4095 \\ \vdots & \vdots \\ 2, & 2 \leq AnMAG \leq 3 \\ 1, & AnMAG = 1 \\ 0, & AnMAG = 0 \end{cases} \quad \begin{array}{l} | \\ | \\ | \\ | \text{Compute exponent} \\ | \\ | \\ | \end{array}$$ + +$$AnMANT = \begin{cases} 1 \ll 5, & AnMAG = 0 \\ (AnMAG \ll 6) \gg AnEXP, & \text{otherwise} \end{cases} \quad \begin{array}{l} | \text{Compute mantissa with a} \\ | \text{1 in the most} \\ | \text{significant bit} \end{array}$$ + +$$SRnS = SRn \gg 10$$ + +$$SRnEXP = (SRn \gg 6) \& 15$$ + +$$SRnMANT = SRn \& 63$$ + +| Split floating point + | word into sign bit, + | exponent and mantissa + +$$WAnS = SRnS ** AnS$$ + +$$WAnEXP = SRnEXP + AnEXP$$ + +$$WAnMANT = ((SRnMANT * AnMANT) + 48) \gg 4$$ + +| Perform floating + | point multiplication + | + +$$WAnMAG = \begin{cases} (WAnMANT \ll 7) \gg (26 - WAnEXP), & WAnEXP \leq 26 \\ ((WAnMANT \ll 7) \ll (WAnEXP - 26)) \& 32767, & WAnEXP > 26 \end{cases} \quad \begin{array}{l} | \text{Convert} \\ | \text{floating} \\ | \text{point to} \\ | \text{magnitude} \end{array}$$ + +$$WAn = \begin{cases} WAnMAG, & WAnS = 0 \\ (65536 - WAnMAG) \& 65535, & WAnS = 1 \end{cases} \quad \begin{array}{l} | \text{Convert mag. to} \\ | \text{two's complement} \end{array}$$ + +##### LIMC + +Input: A2T + Output: A2P + Function: Limits on $a_2$ coefficient of second order predictor. + +$A2UL = 12288$ | Upper limit of +0.75 + +$A2LL = 53248$ | Lower limit of -0.75 + +$$A2P = \begin{cases} A2LL, & 32768 \leq A2T \leq A2LL \\ A2UL, & A2UL \leq A2T \leq 32767 \\ A2T, & \text{otherwise} \end{cases}$$ + + +--- + +##### LIMD + +Inputs: A1T, A2P + Output: A1P + Function: Limits on $a_1$ coefficient of second order predictor. + +$OME = 15360$ | $(1 - \epsilon)$ where + | $\epsilon = 1/16$ + +$A1UL = (OME + 65536 - A2P) \& 65535$ | Compute upper limit + +$A1LL = (A2P + 65536 - OME) \& 65535$ | Compute lower limit + +$$A1P = \begin{cases} A1LL, & 32768 \leq A1T \text{ and } A1T \leq A1LL \\ A1UL, & A1UL \leq A1T \text{ and } A1T \leq 32767 \\ A1T, & \text{otherwise} \end{cases}$$ + + +--- + +##### TRIGB + +Inputs: TR, AnP or BnP or TDP + Output: AnR or BnR or TDR + Note: Equation is given for AnP and AnR. Equation is also valid when substituting BnP and BnR or TDP and TDR for AnP and AnR respectively. + Function: Predictor trigger block. + +$$AnR = \begin{cases} AnP, & TR = 0 \\ 0, & TR = 1 \end{cases}$$ + + +--- + +##### UPA1 + +Inputs: PK0, PK1, A1, SIGPK + Output: A1T + Function: Update $a_1$ coefficient of second order predictor. + +$$PKS = PK0 ** PK1 \quad | \text{ 1-bit "exclusive or"}$$ + +$$UGA1 = \begin{cases} 192, & PKS = 0 \text{ and } SIGPK = 0 \\ 65344, & PKS = 1 \text{ and } SIGPK = 0 \\ 0, & SIGPK = 1 \end{cases} \quad |,| \text{ Gain} = \pm 3/256,|$$ + +$$A1S = A1 \gg 15$$ + +$$ULA1 = \begin{cases} (65536 - (A1 \gg 8)) \& 65535, & A1S = 0 \\ (65536 - ((A1 \gg 8) + 65280)) \& 65535, & A1S = 1 \end{cases} \quad \begin{matrix} | \\ | \text{ Leak factor} = 1/256 \\ | \end{matrix}$$ + +$$UA1 = (UGA1 + ULA1) \& 65535 \quad | \text{ Compute update}$$ + +$$A1T = (A1 + UA1) \& 65535 \quad |$$ + +Inputs: PK0, PK1, PK2, A1, A2, SIGPK + Output: A2T + Function: Update $a_2$ coefficient of second order predictor. + +$$PKS1 = PK0 ** PK1 \quad | \text{ 1-bit "exclusive or"}$$ + +$$PKS2 = PK0 ** PK2 \quad | \text{ 1-bit "exclusive or"}$$ + +$$UGA2A = \begin{cases} 16384, & PKS2 = 0 \\ 114688 & PKS2 = 1 \end{cases}$$ + +$$A1S = A1 \gg 15$$ + +If $A1S = 0$ then + +$$FA1 = \begin{cases} A1 \ll 2, & A1 \leq 8191 \\ 8191 \ll 2, & A1 \geq 8192 \end{cases} \quad \begin{array}{l} | \text{ Implement } f(a_1) \\ | \text{ with limiting} \\ | \text{ at } +1/2 \end{array}$$ + +If $A1S = 1$ , then + +$$FA1 = \begin{cases} (A1 \ll 2) \& 131071, & A1 \geq 57345 \\ 24577 \ll 2, & A1 \leq 57344 \end{cases} \quad \begin{array}{l} | \text{ Implement } f(a_1) \\ | \text{ with limiting} \\ | \text{ at } -1/2 \end{array}$$ + +$$FA = \begin{cases} FA1, & PKS1 = 1 \\ (131072 - FA1) \& 131071, & PKS1 = 0 \end{cases} \quad \begin{array}{l} | \text{ Attach sign to} \\ | \text{ result of } f(a_1) \\ | \end{array}$$ + +$$UGA2B = (UGA2A + FA) \& 131071 \quad |$$ + +$$UGA2S = UGA2B \gg 16 \quad |$$ + +$$UGA2 = \begin{cases} UGA2B \gg 7, & UGA2S = 0 \text{ and } SIGPK = 0 \\ (UGA2B \gg 7) + 64512, & UGA2S = 1 \text{ and } SIGPK = 0 \\ 0, & SIGPK = 1 \end{cases} \quad \begin{array}{l} | \\ | \\ | \text{ Gain calculation,} \\ | \text{ gain} = \pm 1/128 \\ | \\ | \\ | \end{array}$$ + +$$A2S = A2 \gg 15$$ + +$$ULA2 = \begin{cases} (65536 - (A2 \gg 7)) \& 65535, & A2S = 0 \\ (65536 - ((A2 \gg 7) + 65024)) \& 65535, & A2S = 1 \end{cases} \quad \begin{array}{l} | \\ | \text{ Leak factor is} \\ | \text{ 1/128} \\ | \end{array}$$ + +$$UA2 = (UGA2 + ULA2) \& 65535 \quad | \text{ Compute update}$$ + +$$A2T = (A2 + UA2) \& 65535 \quad |$$ + +Inputs: Un, Bn, DQ + Output: BnP + Function: Update for coefficients of sixth order predictor. + +For 40 kbit/s ADPCM (16 SM DQ): + +$$DQMAG = DQ \& 32767$$ + +$$UGBn = \begin{cases} 128, & Un = 0 \text{ and } DQMAG \neq 0 \\ 65408, & Un = 1 \text{ and } DQMAG \neq 0 \\ 0, & DQMAG = 0 \end{cases} \quad \left| \begin{array}{l} \\ \text{Gain} = \pm 1/128 \text{ or } 0 \\ \\ \end{array} \right.$$ + +$$BnS = Bn \gg 15$$ + +$$ULBn = \begin{cases} (65536 - (Bn \gg 9)) \& 65535, & BnS = 0 \\ (65536 - ((Bn \gg 9) + 65408)) \& 65535 & BnS = 1 \end{cases} \quad \left| \begin{array}{l} \\ \text{Leak factor} = 1/512 \\ \\ \end{array} \right.$$ + +$$\begin{aligned} UBn &= (UGBn + ULBn) \& 65535 \\ BnP &= (Bn + UBn) \& 65535 \end{aligned} \quad \left| \begin{array}{l} \text{Compute update} \\ \\ \end{array} \right.$$ + +For 32, 24 and 16 kbit/s ADPCM (15 or 16 SM DQ): + +$$DQMAG = \begin{cases} DQ \& 16383: \text{for } 15 \text{ SM } DQ \\ DQ \& 32767: \text{for } 16 \text{ SM } DQ \end{cases}$$ + +$$UGBn = \begin{cases} 128, & Un = 0 \text{ and } DQMAG \neq 0 \\ 65408, & Un = 1 \text{ and } DQMAG \neq 0 \\ 0, & DQMAG = 0 \end{cases} \quad \left| \begin{array}{l} \\ \text{Gain} = \pm 1/128 \text{ or } 0 \\ \\ \end{array} \right.$$ + +$$BnS = Bn \gg 15$$ + +$$ULBn = \begin{cases} (65536 - (Bn \gg 8)) \& 65535, & BnS = 0 \\ (65536 - ((Bn \gg 8) + 65280)) \& 65535 & BnS = 1 \end{cases} \quad \left| \begin{array}{l} \\ \text{Leak factor} = 1/256 \\ \\ \end{array} \right.$$ + +$$\begin{aligned} UBn &= (UGBn + ULBn) \& 65535 \\ BnP &= (Bn + UBn) \& 65535 \end{aligned} \quad \left| \begin{array}{l} \text{Compute update} \\ \\ \end{array} \right.$$ + +##### XOR + +Inputs: DQn, DQ + Output: Un + Function: One bit “exclusive or” of sign of difference signal and sign of delayed difference signal. + +$$DQS = \begin{cases} DQ \gg 14: \text{for 15 SM DQ} \\ DQ \gg 15: \text{for 16 SM DQ} \end{cases}$$ + +$$DQnS = DQn \gg 10$$ + +$$Un = DQS ** DQnS \quad | \text{ 1-bit “exclusive or”}$$ + +#### 4.2.7 Tone and transition detector + +![Block diagram of the Tone and transition detector. The input A2P enters a TONE block. The output of TONE connects to a TRIGB block, with a tap-off point labeled TDP. The TRIGB block has an input TR from above and an output TDR. TDR enters a DELAY block, which has an input R from above and an output TD. TD enters a TRANS block, which has inputs YL and DQ_FB from above and an output TR.](0f26e70157bd4c45f825795cdcd20fbd_img.jpg) + +``` + + graph LR + A2P[A2P] --> TONE[TONE] + TONE --> TRIGB[TRIGB] + TONE -- TDP --> TRIGB + TRIGB -- TR --> TRIGB + TRIGB -- TDR --> DELAY[DELAY] + DELAY -- R --> DELAY + DELAY -- TD --> TRANS[TRANS] + TRANS -- YL --> TRANS + TRANS -- DQ_FB --> TRANS + TRANS -- TR --> TR + +``` + +T1508280-92 + +Block diagram of the Tone and transition detector. The input A2P enters a TONE block. The output of TONE connects to a TRIGB block, with a tap-off point labeled TDP. The TRIGB block has an input TR from above and an output TDR. TDR enters a DELAY block, which has an input R from above and an output TD. TD enters a TRANS block, which has inputs YL and DQ\_FB from above and an output TR. + +FIGURE 10/G.726 +**Tone and transition detector** + +##### DELAY + +See § 4.2.4 for specification. + +##### TONE + +Input: A2P + Output: TDP + Function: Partial band signal detection. + +$$TDP = \begin{cases} 1, & 32768 \leq A2P \text{ and } A2P < 53760 \\ 0, & \text{otherwise} \end{cases}$$ + + +--- + +##### TRANS + +Inputs: TD, YL, DQ + Output: TR + Function: Transition detector. + +$$DQMAG = \begin{cases} DQ \& 16383: & \text{for 15 SM DQ} \\ DQ \& 32767: & \text{for 16 SM DQ} \end{cases}$$ + +$$YLINT = YL \gg 15$$ + +$$YLFRAC = (YL \gg 10) \& 31$$ + +$$THR 1 = (32 + YLFRAC) \ll YLINT$$ + +$$THR 2 = \begin{cases} 31 \ll 9, & YLINT > 8: \text{ for 15 SM DQ} \\ 31 \ll 10, & YLINT > 9: \text{ for 16 SM DQ} \\ THR 1, & \text{otherwise} \end{cases}$$ + +$$DQTHR = (THR 2 + (THR 2 \gg 1)) \gg 1$$ + +$$TR = \begin{cases} 1, & DQMAG > DQTHR \text{ and } TD = 1 \\ 0, & \text{otherwise} \end{cases}$$ + + +--- + +##### TRIGB + +See § 4.2.6 for specification. + +--- + +#### 4.2.8 Output PCM format conversion and synchronous coding adjustment + +![Block diagram of output PCM format conversion and synchronous coding adjustment. The signal flow is: SR_FF -> COMPRESS (input: LAW) -> SP -> EXPAND (input: LAW) -> DSX -> SUBTA (input: SE) -> DX -> LOG (input: SDX) -> DLX -> SUBTB (input: Y) -> DLNX -> SYNC (inputs: LAW, I(k)) -> SD. There is a feedback loop from the output SD back to the input of the COMPRESS block.](cc98b584f9b31fe69948e3fa65a3ba69_img.jpg) + +Block diagram of output PCM format conversion and synchronous coding adjustment. The signal flow is: SR\_FF -> COMPRESS (input: LAW) -> SP -> EXPAND (input: LAW) -> DSX -> SUBTA (input: SE) -> DX -> LOG (input: SDX) -> DLX -> SUBTB (input: Y) -> DLNX -> SYNC (inputs: LAW, I(k)) -> SD. There is a feedback loop from the output SD back to the input of the COMPRESS block. + +FIGURE 11/G.726 + +Output PCM format conversion and synchronous coding adjustment + +##### COMPRESS (decoder only) + +Inputs: SR, LAW + Output: SP + Function: Convert from uniform PCM to either A-law or μ-law PCM. + +$$IS = SR \gg 15$$ + +$$IM = \begin{cases} SR, & IS = 0 \\ (65536 - SR) \& 32767, & IS = 1 \end{cases} \quad \begin{array}{l} | \text{Convert two's} \\ | \text{complement to} \\ | \text{signed magnitude} \\ | \end{array}$$ + +$$IMAG = \begin{cases} IM, & LAW = 0 \\ IM \gg 1 & LAW = 1 \text{ and } IS = 0 \\ (IM + 1) \gg 1 & LAW = 1 \text{ and } IS = 1 \end{cases} \quad \begin{array}{l} | \mu\text{-law} \\ | \text{A-law} \\ | \end{array}$$ + +then quantize IMAG (see note below) according to Recommendation G.711 using decision values (column 5 of Tables 1a, 1b, 2a and 2b/G.711) in the following way: + +$$SP = \begin{cases} \text{character signal after even bit inversion deduced from Table 1a/G.711 (column 6),} & IS = 0 \text{ and } LAW = 1 \\ \text{character signal after even bit inversion deduced from Table 1b/G.711 (column 6),} & IS = 1 \text{ and } LAW = 1 \\ \text{character signal of Table 2a/G.711 (column 6),} & IS = 0 \text{ and } LAW = 0 \\ \text{character signal of Table 2b/G.711 (column 6),} & IS = 1 \text{ and } LAW = 0 \end{cases}$$ + +*Note* – When IMAG is outside the range defined by the virtual decision level, SP must be set equal to the maximum PCM code word. For the purpose of clarification, examples of conversion for both A-law (after even bit inversion) and $\mu$ -law in the vicinity of the origin are given in the table below: + +TABLE 15/G.726 + +**Conversion for A-law and $\mu$ -law examples** + +| IS | IMAG | PCM code word SP | | +|----|------|------------------|------------| +| | | A-law | $\mu$ -law | +| 0 | 3 | 11010100 | 11111101 | +| 0 | 2 | 11010100 | 11111110 | +| 0 | 1 | 11010101 | 11111110 | +| 0 | 0 | 11010101 | 11111111 | +| 1 | 1 | 01010101 | 01111110 | +| 1 | 2 | 01010101 | 01111110 | +| 1 | 3 | 01010100 | 01111101 | + +##### **EXPAND** + +See § 4.2.1 for specification. Substitute SP for S as input and SLX for SL as output. + +##### **LOG** + +See § 4.2.2 for specification. Substitute DX for D as input, DLX for DL and DSX for DS as outputs. + +##### **SUBTA** + +See § 4.2.1 for specification. Substitute SLX for SL as input and DX for D as output. + +##### **SUBTB** + +See § 4.2.2 for specification. Substitute DLX for DL as input and DLNX for DLN as output. + +##### SYNC (decoder only) + +Inputs: I, SP, DLNX, DSX, LAW + Output: SD + Function: Re-encode output PCM sample in decoder for synchronous tandem coding. + +For 40 kbit/s ADPCM: + +$$IS = I \gg 4$$ + +$$IM = \begin{cases} I + 16, & IS = 0 \\ I \& 15, & IS = 1 \end{cases}$$ + +$$SD = \begin{cases} SP^+, & ID < IM \\ SP, & ID = IM \\ SP^-, & ID > IM \end{cases}$$ + +where + +$SP^+$ = the PCM code word that represents the next more positive PCM output level (when SP represents the most positive PCM output level, then $SP^+$ is constrained to be SP). + +and + +$SP^-$ = the PCM code word that represents the next more negative PCM output level (when SP represents the most negative PCM output level, then $SP^-$ is constrained to be SP). + +For 32 kbit/s ADPCM: + +$$IS = I \gg 3$$ + +$$IM = \begin{cases} I + 8, & IS = 0 \\ I \& 7, & IS = 1 \end{cases}$$ + +ID is defined according to the following table: + +TABLE 16/G.726 + +##### **ID definition for 40 kbit/s ADPCM** + +| DSX | DLNX | ID | | +|-----|-----------|----|--------------------------------------------| +| 0 | 553-2047 | 31 | | +| 0 | 528- 552 | 30 | | +| 0 | 502- 527 | 29 | | +| 0 | 475- 501 | 28 | | +| 0 | 445- 474 | 27 | | +| 0 | 413- 444 | 26 | | +| 0 | 378- 412 | 25 | | +| 0 | 339- 377 | 24 | | +| 0 | 298- 338 | 23 | | +| 0 | 250- 297 | 22 | | +| 0 | 198- 249 | 21 | | +| 0 | 139- 197 | 20 | | +| 0 | 68- 138 | 19 | | +| 0 | 0- 67 | 18 | -- Positive portion of decision interval | +| 0 | 4080-4095 | 18 | -- Negative portion of decision interval | +| 0 | 3974-4079 | 17 | | +| 0 | 2048-3973 | 15 | | +| 1 | 2048-3973 | 15 | | +| 1 | 3974-4079 | 14 | | +| 1 | 4080-4095 | 13 | -- Negative portion of decision interval | +| 1 | 0- 67 | 13 | -- Positive portion of decision interval | +| 1 | 68- 138 | 12 | | +| 1 | 139- 197 | 11 | | +| 1 | 198- 249 | 10 | | +| 1 | 250- 297 | 9 | | +| 1 | 298- 338 | 8 | | +| 1 | 339- 377 | 7 | | +| 1 | 378- 412 | 6 | | +| 1 | 413- 444 | 5 | | +| 1 | 445- 474 | 4 | | +| 1 | 475- 501 | 3 | | +| 1 | 502- 527 | 2 | | +| 1 | 528- 552 | 1 | | +| 1 | 553-2047 | 0 | | + +ID is defined according to the following table: + +TABLE 17/G.726 + +##### **ID definition for 32 kbit/s ADPCM** + +| DSX | DLNX | ID | | +|-----|-----------|----|--------------------------------------------| +| 0 | 400- 2047 | 15 | | +| 0 | 349- 399 | 14 | | +| 0 | 300- 348 | 13 | | +| 0 | 246- 299 | 12 | | +| 0 | 178- 245 | 11 | | +| 0 | 80- 177 | 10 | | +| 0 | 0- 79 | 9 | -- Positive portion of decision interval | +| 0 | 3972-4095 | 9 | -- Negative portion of decision interval | +| 0 | 2048-3971 | 7 | | +| 1 | 2048-3971 | 7 | | +| 1 | 3972-4095 | 6 | -- Negative portion of decision interval | +| 1 | 0- 79 | 6 | -- Positive portion of decision interval | +| 1 | 80- 177 | 5 | | +| 1 | 178- 245 | 4 | | +| 1 | 246- 299 | 3 | | +| 1 | 300- 348 | 2 | | +| 1 | 349- 399 | 1 | | +| 1 | 400-2047 | 0 | | + +$$SD = \begin{cases} SP^+, & ID < IM \\ SP, & ID = IM, SP^-, \\ ID > IM \end{cases}$$ + +where + +$SP^+$ = the PCM code word that represents the next more positive PCM output level (when SP represents the most positive PCM output level, then $SP^+$ is constrained to be SP). + +and + +$SP^-$ = the PCM code word that represents the next more negative PCM output level (when SP represents the most negative PCM output level, then $SP^-$ is constrained to be SP). + +For 24 kbit/s ADPCM: + +$$IS = I \gg 2$$ + +$$IM = \begin{cases} I + 4, & IS = 0 \\ I \& 3, & IS = 1 \end{cases}$$ + +ID is defined according to the following table: + +TABLE 18/G.726 + +**ID definition for 24 kbit/s ADPCM** + +| DSX | DLNX | ID | | +|-----|-----------|----|--------------------------------------------| +| 0 | 331-2047 | 7 | | +| 0 | 218- 330 | 6 | | +| 0 | 8- 217 | 5 | | +| 0 | 0- 7 | 3 | -- Positive portion of decision interval | +| 0 | 2048-4095 | 3 | -- Negative portion of decision interval | +| 1 | 2048-4095 | 3 | -- Negative portion of decision interval | +| 1 | 0- 7 | 3 | -- Positive portion of decision interval | +| 1 | 8- 217 | 2 | | +| 1 | 218- 330 | 1 | | +| 1 | 331-2047 | 0 | | + +$$SD = \begin{cases} SP^+, ID < IM \\ SP, ID = IM \\ SP^-, ID > IM \end{cases}$$ + +where + +$SP^+$ = the PCM code word that represents the next more positive PCM output level (when SP represents the most positive PCM output level, then $SP^+$ is constrained to be SP). + +and + +$SP^-$ = the PCM code word that represents the next more negative PCM output level (when SP represents the most negative PCM output level, then $SP^-$ is constrained to be SP). + +For 16 kbit/s ADPCM: + +$$IS = 1 \gg 1$$ + +$$IM = \begin{cases} I + 2, IS = 0 \\ I \& 1, IS = 1 \end{cases}$$ + +ID is defined according to the following table: + +TABLE 19/G.726 + +##### **ID definition for 16 kbit/s ADPCM** + +| DSX | DLNX | ID | | +|-----|-----------|----|--------------------------------------------| +| 0 | 261-2047 | 3 | | +| 0 | 0- 260 | 2 | -- Positive portion of decision interval | +| 0 | 2048-4095 | 2 | -- Negative portion of decision interval | +| 1 | 2048-4095 | 1 | -- Negative portion of decision interval | +| 1 | 0- 260 | 1 | -- Positive portion of decision interval | +| 1 | 261-2047 | 0 | | + +For the purposes of clarification, examples of re-encoding for both A-law (after even bit inversion) and $\mu$ -law in the vicinity of the origin are given in the table below: + +TABLE 20/G.726 + +##### **Re-encoding for A-law and $\mu$ -law: ADPCM** + +| Comparison of ID and IM | A-law | | $\mu$ -law | | +|-------------------------|----------|----------|------------|----------| +| | SP | SD | SP | SD | +| ID > IM | 11010101 | 01010101 | 11111110 | 11111111 | +| ID = IM | " | 11010101 | " | 11111110 | +| ID < IM | " | 11010100 | " | 11111101 | +| ID > IM | 01010101 | 01010100 | 11111111 | 01111110 | +| ID = IM | " | 01010101 | " | 11111111 | +| ID < IM | " | 11010101 | " | 11111110 | +| ID > IM | 01010100 | 01010111 | 01111110 | 01111101 | +| ID = IM | " | 01010100 | " | 01111110 | +| ID < IM | " | 01010101 | " | 01111111 | + +*Note* – SP (and SD) represent character signals defined according to Tables 1/G.711 and 2/G.711. See sub-block COMPRESS (§ 4.2.8) for the exact representation of SP (and SD). + +## APPENDIX I + +(to Recommendation G.726) + +## Network aspects + +The purpose of this Appendix is to give a broad outline of the interaction of 16, 24, 32 and 40 kbit/s ADPCM with other devices that are found in the telephony network and also the effect of specific signals found in the network. Some general guidance is also offered. + +### I.1 *General transmission considerations* + +Both 24 and 16 kbit/s codings are intended for use with DCME overload channels. It is recommended that 32 kbit/s and 16 kbit/s or 24 kbit/s coding be alternated rapidly such that at least 3.5 to 3.7 bits/sample are used on average. The rate of alternation is for further study. The method of alternation is beyond the scope of this Recommendation. The effect on speech quality of this alternation is not expected to be significant. The use of 24 or 16 kbit/s coding for data transmission is not recommended. + +The 40 kbit/s coding is intended for use with DCME and packet circuit multiplication equipment (PCME) data modem channels, especially for modem operation at speeds of 7200, 9600 and 12 000 bit/s. + +Consideration will have to be given to appropriate corrective action with, for example, the use of bit stealing techniques for the provision of a limited speed signalling facility. Otherwise, serious performance degradation will occur. + +Conversely a 64 kbit/s channel which is conveyed by an ADPCM channel (or channels) will not exhibit bit integrity. + +### I.2 *Interaction with other processes* + +The synchronous coding adjustment is described in §§ 1.2 and 3.7 of this Recommendation. The favourable operation of this adjustment is dependent on the signals on the ADPCM path and on the intermediate 64 kbit/s path both being uncorrupted by other digital processes. For example, the use of digital pads, A-law to $\mu$ -law converters, echo cancellers or digital speech interpolation (DSI) at these intermediate points will inhibit the correct functioning of this adjustment. However, the performance will still be better than that achieved when an asynchronous connection is employed. + +The use of an ADPCM link to interconnect 64 kbit/s A-law PCM signals and 64 kbit/s $\mu$ -law signals has been found to be satisfactory for speech even though this will inhibit the correct operation of the synchronous coding adjustment between the ADPCM link so used and the subsequent ADPCM link. + +The interactions between ADPCM and processes such as DSI and echo cancellation (e.g. quantization noise in the echo path) are for further study. + +The effect of large d.c. offsets (arising from PCM encoders) on the performance of ADPCM for low level signals is for further study. + +### I.3 *Interaction with coding laws other than PCM* + +Interconnection with coding laws other than PCM is not the subject of the Recommendation and analogue interconnections may need to be employed. + +It follows that great care must be exercised when interconnection is made to coding laws which are not the subject of CCITT Recommendations. + +### I.4 *Encoder/decoder synchronization* + +The encoder and its respective decoder must always operate at the same bit rate (i.e 16, 24, 32 or 40 kbit/s), or otherwise severe mistracking may occur. + +### I.5 *Synchronous coding adjustment* + +The synchronous coding adjustment will work correctly when an ADPCM encoder/decoder pair is connected by a bit-transparent 64 kbit/s PCM path to another encoder/decoder pair operating at the same rate. When two encoder/decoder pairs are operating at different rates, the synchronous tandeming property is not guaranteed to be established. + +### I.6 *Speech performance* + +Under error free transmission conditions the perceived quality of speech over 32 kbit/s ADPCM links is only slightly lower than that over 64 kbit/s PCM links. This will only be significant when numbers of such links are used in tandem and not when single links are used. Hence the numbers of such 32 kbit/s ADPCM links must be controlled on an international connection. With transmission error ratios higher than $1 \cdot 10^{-4}$ the perceived quality of speech over 32 kbit/s ADPCM links is better than that over 64 kbit/s PCM links. Precise limits for the international portion of the connection and the national extensions may be found in Recommendation G.113. Preliminary tests indicate that for voice, the 40 kbit/s ADPCM coding performs approximately as well as 64 kbit/s PCM according to Recommendation G.711. + +### I.7 *Voice frequency telegraph performance* + +Twenty-four-channel voice frequency telegraph of Recommendation R.35 cannot be satisfactorily conveyed over 32 kbit/s ADPCM links and it is, therefore, desirable to implement routing rules to avoid this combination. + +### I.8 *Data performance* + +Voiceband data performance up to 2400 bit/s using, for example modems conforming to Recommendation V.21, V.22 *bis*, V.23 and V.26 *ter*, will not be subject to significant degradation over 32 kbit/s ADPCM links provided the numbers of such links do not exceed the limits of Recommendation G.113. + +Voiceband data performance at 4800 bit/s using, for example modems conforming to Recommendation V.27 *bis*, can be accommodated with 32 kbit/s ADPCM but will be subject to additional degradations over and above that expected from standard 64 kbit/s PCM links. More care will need to be exercised in using such a service. + +Voiceband data at speeds up to 12 000 bit/s can be accommodated by 40 kbit/s ADPCM. The performance of V.33 modems operating at 14 400 bit/s over 40 kbit/s ADPCM is for further study. + +### I.9 *Dual tone multi-frequency (DTMF) signalling* + +No major difficulties are likely to be experienced with DTMF signalling conveyed over 32 kbit/s or 40 kbit/s ADPCM links. The use of DTMF for end-to-end signalling is limited by the number of links in tandem. DTMF performance for 16 kbit/s or 24 kbit/s ADPCM is for further study. + +### I.10 *Facsimile* + +No degradation is to be expected when using 40 kbit/s ADPCM with Group 2 or Group 3 facsimile apparatus according to Recommendations T.3 or T.4 at rates up to 12 000 bit/s. Performance of Group 3 facsimile when using 40 kbit/s ADPCM at 14 400 bit/s is for further study. No serious degradation is to be expected when using 32 kbit/s ADPCM with Group 2 facsimile apparatus according to Recommendations T.3 or T.4 at rates up to 12 000 bit/s. + +# APPENDIX II (to Recommendation G.726) + +## **Digital test sequences for the verification of the algorithms in Recommendation G.726** + +This Appendix gives information on the digital test sequences which have been chosen to verify implementations of the algorithms in Rec. G.726. Copies of the sequences on flexible diskettes together with a detailed description can be ordered from the ITU sales services (Please refer to collective letter No. 11/XV, 1991). + +### II.1      *Purpose of digital test sequences* + +Digital sequences are used to verify the conformance of an implementation to a digital transcoding algorithm. The sequences are chosen to exercise the major arithmetic components and thus give a reasonable level of confidence of the compliance of an implementation with this Recommendation. Note that with a limited number of test sequences it is not possible to demonstrate 100% coverage of all states of the implementation. The more general issues involved in testing such algorithms are the subject of active research in the areas of VLSI testing and protocol conformance testing. + +### II.2      *Diskette interface and format* + +Copies of the digital test sequences are available from the ITU on four 5 1/4" diskettes. The diskettes were created under MS-DOS operating system (version 3.2 or newer), and 1.2 Mbyte high-density doubled-sided 96 tracks per inch 5 1/4 MS-DOS format. \ No newline at end of file diff --git a/marked/G/T-REC-G.733-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.733-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/G/T-REC-G.733-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/G/T-REC-G.733-198811-I_PDF-E/6bbc398f520a7bcc5491cab18d3e4cac_img.jpg b/marked/G/T-REC-G.733-198811-I_PDF-E/6bbc398f520a7bcc5491cab18d3e4cac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6baba2fd9423a64d513d41783b2f228f56f6ef6f --- /dev/null +++ b/marked/G/T-REC-G.733-198811-I_PDF-E/6bbc398f520a7bcc5491cab18d3e4cac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b852ab3143672c12b565ae6e55e69256917724c881d9dfd581e043eb6f797cf +size 25974 diff --git a/marked/G/T-REC-G.733-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.733-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f3649e1b96149dbdb44d38309de41be7d2aee49d --- /dev/null +++ b/marked/G/T-REC-G.733-198811-I_PDF-E/raw.md @@ -0,0 +1,157 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**G.733** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL ASPECTS OF DIGITAL TRANSMISSION +SYSTEMS** + +**TERMINAL EQUIPMENTS** + +--- + +**CHARACTERISTICS OF PRIMARY PCM +MULTIPLEX EQUIPMENT OPERATING +AT 1544 kbit/s** + +**ITU-T Recommendation G.733** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +- 1 ITU-T Recommendation G.733 was published in Fascicle III.4 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **CHARACTERISTICS OF PRIMARY PCM MULTIPLEX EQUIPMENT OPERATING AT 1544 kbit/s** + +*(Geneva, 1972; further amended)* + +## **1 General characteristics** + +### **1.1 *Fundamental characteristics*** + +The encoding law used is the $\mu$ -law as specified in Recommendation G.711. The sampling rate, load capacity and the code are also specified in that Recommendation. + +The number of quantized values is 255. Two character signals are reserved for zero value (11111111 and 01111111). + +In some networks the all-0 character signal (00000000) is eliminated to avoid loss of timing information to the digital line, resulting in 254 quantized values. + +### **1.2 *Bit rate*** + +The nominal bit rate is 1544 kbit/s. The tolerance on this rate is $\pm 50$ parts per million (ppm). + +### **1.3 *Timing signal*** + +It should be possible to derive the transmitting timing signal of a PCM multiplex equipment from an internal source, from the incoming digital signal and also from an external source. + +## **2 Frame structure** + +Refer to §§ 3.1.1 and 3.1.2 of Recommendation G.704 for frame structure and use of derived channel time slots. + +## **3 Loss and recovery of frame alignment** + +The strategy for the loss and recovery of frame alignment should be according to Recommendation G.706, § 2.1. + +## **4 Fault conditions and consequent actions** + +### **4.1 *Fault conditions*** + +The PCM multiplex equipment should detect the following conditions: + +4.1.1 Failure of power supply. + +4.1.2 Loss of incoming signals at 1544 kbit/s. + +4.1.3 Loss of frame alignment. + +4.1.4 Alarm indication received from the remote PCM multiplex equipment. + +### 4.2 *Consequent actions* + +Further to the detection of a fault condition, appropriate actions should be taken as specified in Table 1/G.733. The consequent actions are as follows: + +4.2.1 A service alarm indication should be generated to signify that the service provided by the PCM multiplex is no longer available. This indication should be forwarded to the switching and/or signalling equipment depending upon the arrangement provided. + +4.2.2 The service alarm described in § 4.2.1 above should be used to automatically remove the associated circuits from service and to restore them to service when frame alignment has been recovered. + +*Note* - The removal of the associated circuits described in § 4.2.2 above should be done in such a way that the circuits are not needlessly removed in the case of a brief isolated loss of frame alignment but are removed in the case of a permanent or intermittent loss of frame alignment. + +It is also important to minimize the impact of signalling errors which may occur during periods of loss of frame alignment. These functions should be provided in the PCM multiplex equipment or in the switching/signalling equipment. + +4.2.3 A prompt maintenance alarm indication should be generated to signify that performance is below acceptable standards and maintenance attention is required locally. + +4.2.4 An alarm indication to the remote end should be generated by either forcing bit 2 in every channel time slot to the value 0 or by modifying the S-bit as described in § 3.1.3.2.2 of Recommendation G.704 for the 12 frame multiframe or by sending a frame alignment alarm sequence (1111111100000000) as described in § 3.1.1.3 (A)-(3) of Recommendation G.704 for the 24-frame multiframe. + +4.2.5 Transmission should be suppressed at the analogue outputs. + +4.2.6 *Rapid indication of loss of frame alignment* + +An indication should be given to the Signalling System No. 6 equipment (digital version) when the PCM multiplex equipment (local end only) detects a loss of frame alignment. The average time to detect and give an indication of random bits in the frame alignment signal bit positions should not be greater than 3 ms. This indication will serve the same function as that provided by the data carrier failure alarm in the analogue version (see Recommendation Q.275 [1]). + +## 5 *Signalling* + +### 5.1 *Signalling arrangement* + +Refer to § 3.1.3 of Recommendation G.704. + +### 5.2 *Loss of multiframe alignment in case of channel associated signalling on 12 frame multiframe* + +Loss of multiframe alignment is assumed to have taken place when loss of frame alignment occurs. + +### 5.3 *Minimization of quantizing distortion in case of channel associated signalling* + +In the signalling frame only seven bits are available for encoding of voice frequencies. In order to minimize the quantizing distortion, the decoder output values are shifted slightly. All even numbered decoder output values $y_n$ are changed to be equal to the next higher decision value, i.e. $x_{n+1}$ . All odd numbered decoder output values $y_{n+1}$ are changed to be equal to the same numbered decision value, i.e. $x_{n+1}$ , as shown on Figure 1/G.733. + +When suppression of the all 0 character signal is required, the value of the seventh bit is forced to be 1 when all the other bits of the character signal have the value 0. + +TABLE 1/G.733 + +### Fault conditions and consequent actions for the PCM multiplex equipment + +| Equipment part | Fault conditions | Consequent actions | | | | +|-------------------------------|------------------------------------------------|------------------------------------|-------------------------------------|----------------------------------------------|-------------------------------------------------| +| | | Service alarm indication generated | Prompt maintenance alarm indication | Alarm indication to the remote end generated | Transmission suppressed at the analogue outputs | +| Multiplexer and demultiplexer | Failure of power supply | Yes | Yes | Yes (if practicable) | Optional | +| Demultiplexer only | Loss of incoming signals at 1544 kbit/s | Yes | Yes | Yes | Yes | +| | Loss of frame alignment | Yes | Yes | Yes | Yes | +| | Alarme indication received from the remote end | Optional | Yes | | Optional | + +Note 1 - A Yes in the table signifies that an action should be taken as a consequence of the relevant fault condition. An open space in the table signifies that the relevant action should not be taken as a consequence of the relevant fault condition, if 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 - Indications of additional fault conditions, such as codec failure and excessive bit errors, are left to the discretion of individual Administrations. + +![Seven-bit codec transfer characteristic graph showing a staircase-like relationship between Input (Decision value) on the x-axis and Output (Decoder output value) on the y-axis. The graph is symmetric about the origin, with levels labeled x1, x3, x5, x7 on the positive y-axis and -x1, -x3, -x5, -x7 on the negative y-axis. Decision values x2, x4, x6 and -x2, -x4, -x6 are marked on the x-axis.](6bbc398f520a7bcc5491cab18d3e4cac_img.jpg) + +The figure is a graph of the seven-bit codec transfer characteristic. The vertical axis represents the 'Output (Decoder output value)' and the horizontal axis represents the 'Input (Decision value)'. The graph shows a staircase function that is symmetric about the origin. The positive y-axis has labels $x_1, x_3, x_5, x_7$ and the negative y-axis has labels $-x_1, -x_3, -x_5, -x_7$ . The positive x-axis has labels $x_2, x_4, x_6$ and the negative x-axis has labels $-x_2, -x_4, -x_6$ . The function steps occur at these decision values. A small label 'T1810080-89' is present in the bottom right area of the graph. + +Seven-bit codec transfer characteristic graph showing a staircase-like relationship between Input (Decision value) on the x-axis and Output (Decoder output value) on the y-axis. The graph is symmetric about the origin, with levels labeled x1, x3, x5, x7 on the positive y-axis and -x1, -x3, -x5, -x7 on the negative y-axis. Decision values x2, x4, x6 and -x2, -x4, -x6 are marked on the x-axis. + +FIGURE 1/G.733 + +### Seven-bit codec transfer characteristic + +## 6 Interfaces + +Analogue: Refer to Recommendations G.712, G.713 and G.714. + +Digital: Refer to Recommendation G.703. + +## Reference + +- [1] CCITT Recommendation *Data channel failure detection*, Vol. VI, Rec. Q.275. \ No newline at end of file diff --git a/marked/G/T-REC-G.742-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.742-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6d4aa6fe7778ddc5d092f7daf06e8413d0a59114 --- /dev/null +++ b/marked/G/T-REC-G.742-198811-I_PDF-E/raw.md @@ -0,0 +1,218 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**G.742** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL ASPECTS OF DIGITAL TRANSMISSION +SYSTEMS** + +**TERMINAL EQUIPMENTS** + +--- + +**SECOND ORDER DIGITAL MULTIPLEX +EQUIPMENT OPERATING AT 8448 kbit/s +AND USING POSITIVE JUSTIFICATION** + +**ITU-T Recommendation G.742** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation G.742 was published in Fascicle III.4 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## **SECOND ORDER DIGITAL MULTIPLEX EQUIPMENT OPERATING AT 8448 kbit/s AND USING POSITIVE JUSTIFICATION** + +*(Geneva, 1972; further amended)* + +### **1 General** + +The second order digital multiplex equipment using positive justification, described below, is intended for use on digital paths between countries using 2048 kbit/s primary multiplex equipments. + +## **2 Bit rate** + +The nominal bit rate should be 8448 kbit/s. + +The tolerance on that rate should be $\pm 30$ parts per million (ppm). + +## **3 Frame structure** + +Table 1/G.742 gives: + +- the tributary bit rate and the number of tributaries; +- the number of bits per frame; +- the bit numbering scheme; +- the bit assignment; +- the bunched frame alignment signal. + +TABLE 1/G.742 +**8448-kbit/s multiplexing frame structure** + +| | | +|------------------------------------------------------------|--------------------------| +| Tributary bit rate (kbit/s) | 2048 | +| Number of tributaries | 4 | +| Frame structure | Bit number | +| Frame alignment signal (1111010000) | Set I
1 to 10 | +| Alarm indication to the remote digital multiplex equipment | 11 | +| Bit reserved for national use | 12 | +| Bits from tributaries | 13 to 212 | +| Justification control bits $C_{j1}$ (see Note) | Set II
1 to 4 | +| Bits from tributaries | 5 to 212 | +| Justification control bits $C_{j2}$ (see Note) | Set III
1 to 4 | +| Bits from tributaries | 5 to 212 | +| Justification control bits $C_{j2}$ (see Note) | Set IV
1 to 4 | +| Bits from tributaries available for justification | 5 to 8 | +| Bits from tributaries | 9 to 212 | +| Frame length | 848 bits | +| Bits per tributary | 206 bits | +| Maximum justification rate per tributary | 10 kbit/s | +| Nominal justification ratio | 0.424 | + +*Note* - $C_{ji}$ indicates the $i$ th justification control bit of the $j$ th tributary. + +## 4 Loss and recovery of frame alignment and consequent action + +Loss of frame alignment should be assumed to have taken place when four consecutive frame alignment signals have been incorrectly received in their predicted positions. + +When frame alignment is assumed to be lost, the frame alignment device should decide that such alignment has effectively been recovered when it detects the presence of three consecutive frame alignment signals. + +The frame alignment device having detected the appearance of a single correct frame alignment signal, should begin a new search for the frame alignment signal when it detects the absence of the frame alignment signal in one of the two following frames. + +*Note* - As it is not strictly necessary to specify the detailed frame alignment strategy, any suitable frame alignment strategy may be used provided the performance achieved is at least as efficient in all respects as that obtained by the above frame alignment strategy. + +### 5 Multiplexing method + +Cyclic bit interleaving in the tributary numbering order and positive justification is recommended. + +The justification control signal should be distributed and use the $C_{jn}$ -bits ( $n = 1, 2, 3$ , see Table 1/G.742). + +Positive justification should be indicated by the signal 111, no justification by the signal 000. Majority decision is recommended. + +Table 1/G.742 gives the maximum justification rate per tributary and the nominal justification ratio. + +## 6 Jitter + +### 6.1 Jitter transfer characteristic + +A 2048 kbit/s signal, modulated by sinusoidal jitter, should be subject to a muldex jitter transfer characteristic within the gain/frequency limits given in Figure 1/G.742. The equivalent binary content of the test signal should be 1000. + +![Figure 1/G.742: Jitter transfer characteristic graph. The y-axis is labeled '20 log J_out / J_in' in dB, with values 0.5 and -19.5. The x-axis is frequency in Hz, with markers f_0, f_5 (40 Hz), f_6 (400 Hz), and f_7 (100 kHz). The graph shows a shaded region representing the gain limits. From f_0 to f_5, the gain is constant at 0.5 dB. At f_5, the gain begins to decrease with a slope of 20 dB/decade. At f_6, the gain reaches -19.5 dB and remains constant until f_7. A dashed horizontal line is shown at approximately 0.2 dB.](6f1efa91fb9b476380af7a35db4f14bf_img.jpg) + +Figure 1/G.742: Jitter transfer characteristic graph. The y-axis is labeled '20 log J\_out / J\_in' in dB, with values 0.5 and -19.5. The x-axis is frequency in Hz, with markers f\_0, f\_5 (40 Hz), f\_6 (400 Hz), and f\_7 (100 kHz). The graph shows a shaded region representing the gain limits. From f\_0 to f\_5, the gain is constant at 0.5 dB. At f\_5, the gain begins to decrease with a slope of 20 dB/decade. At f\_6, the gain reaches -19.5 dB and remains constant until f\_7. A dashed horizontal line is shown at approximately 0.2 dB. + +*Note 1* - The frequency $f_0$ should be less than 20 Hz and as low as possible (e.g. 10 Hz), taking into account the limitations of measuring equipment. + +*Note 2* - To achieve accurate measurements, the use of a selective method is recommended with a bandwidth sufficiently small referred to the relevant measurement frequency, but not wider than 40 Hz. + +*Note 3* - The need to tolerate spurious responses greater than -19.5 dB in the frequency range $f_6$ to $f_7$ is for further study. + +FIGURE 1/G.742 + +### 6.2 Tributary output jitter + +The peak-to-peak jitter at a tributary output in the absence of input jitter should not exceed 0.25 UI when measured in the frequency range up to 100 kHz. + +When measured with an instrument incorporating a bandpass filter having a lower cutoff frequency of 18 kHz, a roll-off of 20 dB/decade and an upper limit of 100 kHz, the peak-to-peak output jitter should not exceed 0.05 UI with a probability of 99.9% during a measurement period of 10 s. + +*Note* - For interfaces meeting the national high Q option, detailed in Recommendation G.703, the lower cutoff frequency for the above measurement should be 700 Hz. + +### 6.3 Multiplex signal output jitter + +In the case where the transmitting timing signal is derived from an internal oscillator, the peak-to-peak jitter at + +the 8448 kbit/s output should not exceed 0.05 UI when it is measured within the frequency range from $f_1 = 20$ Hz to $f_4 = 400$ kHz. + +## 7 Digital interfaces + +The digital interfaces at 2048 kbit/s and 8448 kbit/s should be in accordance with Recommendation G.703. + +## 8 Timing signal + +If it is economically feasible, it may be desirable to be able to derive the multiplexer timing signal from an external source as well as from an internal source. + +### 9 Service digits + +Two bits per frame are available for service functions. Bit 11 of Set I is used to transmit an alarm indication to the remote multiplex equipment when specific fault conditions are detected in the multiplex equipment (see § 10 below). Bit 12 of Set I is reserved for national use. On the digital path crossing the border, this bit is fixed at 1. + +### 10 Fault conditions and consequent conditions + +#### 10.1 Fault conditions + +The digital multiplex equipment should detect the following fault conditions: + +10.1.1 Failure of power supply. + +10.1.2 Loss of an incoming signal at 2048 kbit/s at the input of the multiplexer. + +*Note* - Where separate circuits are used for the digital signal and the timing signal then loss of either or both should constitute loss of the incoming signal. + +10.1.3 Loss of the incoming signal at 8448 kbit/s at the input of the demultiplexer. + +*Note 1* - The detection of this fault condition is required only when it does not result in an indication of loss of frame alignment. + +*Note 2* - Where separate circuits are used for the digital signal and the timing signal, then loss of either or both should constitute loss of the incoming signal. + +10.1.4 Loss of frame alignment. + +10.1.5 Alarm indication received from the remote multiplex equipment at the 8448 kbit/s input of the demultiplexer (see § 10.2.2 below). + +#### 10.2 Consequent actions + +Further to the detection of a fault condition, appropriate actions should be taken as specified by Table 2/G.742. The consequent actions are as follows: + +10.2.1 Prompt maintenance alarm indication generated to signify that performance is below acceptable standards and maintenance attention is required locally. When the Alarm Indication Signal (AIS) (see Note 2 under § 10.2.5 below) at 8448 kbit/s is detected at the input of the demultiplexer, the prompt maintenance alarm indication associated with loss of frame alignment should be inhibited, while the rest of the consequent actions are in accordance with those associated in Table 2/G.742 with the fault condition. + +*Note* - The location and provision of any visual and/or audible alarm activated by this maintenance alarm indication is left to the discretion of each Administration. + +10.2.2 Alarm indication to the remote multiplex equipment generated by changing from the state 0 to the state 1 bit 11 of Set I at the 8448 kbit/s output of the multiplexer. + +10.2.3 AIS (see Notes 1 and 2 below) applied to all four 2048 kbit/s tributary outputs from the demultiplexer. + +10.2.4 AIS (see Notes 1 and 2 below) applied to the 8448 kbit/s output of the multiplexer. + +10.2.5 AIS (see Note 2 below) applied to the time slots of the 8448 kbit/s signal at the output of the multiplexer, corresponding to the relevant 2048 kbit/s tributary. + +The method of transmitting the AIS at the output port of the multiplexer in time slots corresponding to a faulty input tributary, should be such that the status of the justification control digits is controlled so as to ensure that the AIS is within the tolerance specified for that tributary. + +TABLE 2/G.742 + +#### **Fault conditions and consequent actions** + +| Equipment part | Fault condition (see § 10.1) | Consequent actions (see § 10.2) | | | | | +|-------------------------------|---------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------------------|------------------------|-------------------------|----------------------------------------------------| +| | | Prompt maintenance alarm indication generated | Alarm indication to the remote multiplex equipment generated | AIS applied | | | +| | | | | To all the tributaries | To the composite signal | To the relevant time slots of the composite signal | +| Multiplexer and demultiplexer | Failure of power supply | Yes | | Yes, if practicable | Yes, if practicable | | +| Multiplexer only | Loss of incoming signal on a tributary | Yes | | | | Yes | +| Demultiplexer only | Loss of incoming signal at 8448 kbit/s | Yes | Yes | Yes | | | +| | Loss of frame alignment | Yes | Yes | Yes | | | +| | Alarm indication received from the remote multiplex equipment | | | | | | + +*Note - A Yes in the table signifies that a certain action should be taken as a consequence of the relevant fault condition. An open space in the table signifies that the relevant action should not be taken as a consequence of the relevant fault condition, if 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 1* - The bit rate of the AIS at the output of the multiplexer equipment or at the output of the demultiplexer equipment should be in accordance with the interface specifications. + +*Note 2* - The equivalent binary content of the AIS at 2048 kbit/s and 8448 kbit/s is nominally a continuous stream of 1s. The strategy for detecting the presence of the AIS should be such that the AIS is detectable even in the presence of an error ratio $1 \cdot 10^{-3}$ . However, a signal, with all bits except the frame alignment signal in the 1s state, should not be mistaken for an AIS. + +#### 10.3 *Time requirements* + +The fault detection and the application of the consequent actions listed in §§ 10.2.2 to 10.2.5, including the detection of AIS, should be completed within a time limit of 1 ms. \ No newline at end of file diff --git a/marked/G/T-REC-G.7721.1-202508-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/G/T-REC-G.7721.1-202508-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25f8fbfaef317942ed3102c74b40a7d42f80608b --- /dev/null +++ b/marked/G/T-REC-G.7721.1-202508-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83cab7dcabfe939b223d97242d8523e461968d21f7c5432693c30a64f2d95521 +size 7050 diff --git a/marked/G/T-REC-G.7721.1-202508-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/G/T-REC-G.7721.1-202508-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdb66f10ef8a9bad87c9d27fb33607281b36495c --- /dev/null +++ b/marked/G/T-REC-G.7721.1-202508-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07d952dfa81c786dac00810073231f8503902e13c2297e2d0110c87910951143 +size 64085 diff --git a/marked/G/T-REC-G.7721.1-202508-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.7721.1-202508-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80752baadf0ff864e2fc213b6cf45f82e3a8044d --- /dev/null +++ b/marked/G/T-REC-G.7721.1-202508-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5948d96607334e8b44515f5f165c675b120de5b96aaa90a732916d994e16df6 +size 57880 diff --git a/marked/G/T-REC-G.7721.1-202508-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/G/T-REC-G.7721.1-202508-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bb90481f1ddc45b99763ae352e978759a306525 --- /dev/null +++ b/marked/G/T-REC-G.7721.1-202508-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8343f4e7f7531e38c0df0831a54dca18d31e298bc8b4314020603acd123860f9 +size 56910 diff --git a/marked/G/T-REC-G.774.10-200102-I_PDF-E/raw.md b/marked/G/T-REC-G.774.10-200102-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4d3a877038e2958f72373b087b330913a6d6022f --- /dev/null +++ b/marked/G/T-REC-G.774.10-200102-I_PDF-E/raw.md @@ -0,0 +1,1693 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.774.10** + +(02/2001) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital terminal equipments – Operations, administration +and maintenance features of transmission equipment + +--- + +**Synchronous Digital Hierarchy (SDH) – +Multiplex Section (MS) shared protection ring +management for the network element view** + +ITU-T Recommendation G.774.10 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TESTING EQUIPMENTS | G.500–G.599 | +| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 | +| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 | +| General | G.700–G.709 | +| Coding of analogue signals by pulse code modulation | G.710–G.719 | +| Coding of analogue signals by methods other than PCM | G.720–G.729 | +| Principal characteristics of primary multiplex equipment | G.730–G.739 | +| Principal characteristics of second order multiplex equipment | G.740–G.749 | +| Principal characteristics of higher order multiplex equipment | G.750–G.759 | +| Principal characteristics of transcoder and digital multiplication equipment | G.760–G.769 | +| Operations, administration and maintenance features of transmission equipment | G.770–G.779 | +| Principal characteristics of multiplexing equipment for the synchronous digital hierarchy | G.780–G.789 | +| Other terminal equipment | G.790–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Synchronous Digital Hierarchy (SDH) Multiplex Section (MS) shared protection ring management for the network element view** + +## **Summary** + +This Recommendation provides an information model for the Synchronous Digital Hierarchy (SDH) Network. This model describes the managed object classes and their properties for the configuration and post-configuration management of the protection switching function of SDH Multiplex Section (MS) Shared Protection Ring (SPR), as defined in ITU-T G.803 [12], ITU-T G.841 [15] and ITU-T G.842 [16]. These objects are useful to describe information exchanged across interfaces defined in ITU-T M.3010 [3] Telecommunications Management Network (TMN) architecture for the configuration and post-configuration management of the protection function. + +| History | | +|----------------|----------------------------------------| +| Issue | Notes | +| 2001 | Initial version of the Recommendation. | + +## **Source** + +ITU-T Recommendation G.774.10 was revised by ITU-T Study Group 15 (2001-2004) and approved under the WTSA Resolution 1 procedure on 9 February 2001. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +## CONTENTS + +###### Page + +| | | | +|-----|-----------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and Definitions ..... | 2 | +| 4 | Abbreviations..... | 2 | +| 5 | SDH MS shared protection ring (SPR) protection management ..... | 3 | +| 5.1 | SDH MS SPR protection management requirements ..... | 3 | +| 5.2 | SDH MS SPR information model overview..... | 4 | +| 6 | Managed object class definitions..... | 5 | +| 6.1 | auSquelchTable..... | 5 | +| 6.2 | msSPRProtectionGroup ..... | 5 | +| 6.3 | msSPRProtectionUnit ..... | 7 | +| 6.4 | nutTable ..... | 8 | +| 6.5 | ripTable..... | 8 | +| 6.6 | sdhMSSPRProtectionCoordinator ..... | 8 | +| 6.7 | sPRingManager..... | 9 | +| 6.8 | squelchTable ..... | 10 | +| 7 | Packages..... | 10 | +| 7.1 | changeSPRConfigurationPkg ..... | 10 | +| 7.2 | enhancedWtrSpanPkg..... | 11 | +| 7.3 | fourFiberPUPkg ..... | 11 | +| 7.4 | manualSPRConfigurationPkg..... | 11 | +| 7.5 | restoreExtraTrafficPkg..... | 11 | +| 7.6 | wtrSpanPkg..... | 12 | +| 8 | Attributes ..... | 12 | +| 8.1 | auTable..... | 12 | +| 8.2 | auNumber..... | 12 | +| 8.3 | currentSquelchingList..... | 13 | +| 8.4 | directionTable ..... | 13 | +| 8.5 | enhancedWaitToRestoreTimeSpan ..... | 13 | +| 8.6 | msSPRProtectionStatus ..... | 13 | +| 8.7 | nodeNumber..... | 16 | +| 8.8 | nutChannelList..... | 16 | +| 8.9 | nutTableId ..... | 16 | + +| | Page | +|-----------------------------------------------------------|-------------| +| 8.10 protectionGroupPointer ..... | 16 | +| 8.11 restoreExtraTraffic ..... | 17 | +| 8.12 ringId ..... | 17 | +| 8.13 ringMap ..... | 17 | +| 8.14 ringPU ..... | 17 | +| 8.15 ripChannelList ..... | 17 | +| 8.16 ripTableId ..... | 18 | +| 8.17 spanPU ..... | 18 | +| 8.18 sPRingApplication ..... | 18 | +| 8.19 sPRingManagerId ..... | 18 | +| 8.20 squelchTableId ..... | 18 | +| 8.21 waitToRestoreTimeSpan ..... | 19 | +| 9 Actions ..... | 19 | +| 9.1 changeSPRConfiguration ..... | 19 | +| 9.2 updateRipTable ..... | 19 | +| 9.3 updateSquelchTable ..... | 20 | +| 10 Notifications ..... | 20 | +| 11 Parameters ..... | 20 | +| 11.1 msSPRConfigurationError ..... | 20 | +| 11.2 msSPRLockoutTypeParameter ..... | 20 | +| 11.3 msSPRProtectionGroupConfigParameter ..... | 21 | +| 11.4 msSPRProtectionStatusParameter ..... | 21 | +| 12 Name Bindings ..... | 22 | +| 12.1 auSquelchTable-squelchTable ..... | 22 | +| 12.2 nutTable-sPRingManager ..... | 22 | +| 12.3 ripTable-sPRingManager ..... | 23 | +| 12.4 sPRingManager-managedElement ..... | 23 | +| 12.5 squelchTable-sPRingManager ..... | 23 | +| 12.6 Reuse of Existing Name Bindings ..... | 23 | +| 13 Supporting ASN.1 Productions ..... | 24 | +| Appendix I – Inheritance and containment diagrams ..... | 28 | +| Appendix II – Illustrations of MS SPR configuration ..... | 29 | + +## **Synchronous Digital Hierarchy (SDH) – Multiplex Section (MS) shared protection ring management for the network element view** + +# **1 Scope** + +This Recommendation addresses the configuration and post-configuration management of automatic protection switching within the multiplex section (MS) shared protection ring (SPR), high and low order path layers. It covers the protection functions as described in ITU-T G.841 [15] and ITU-T G.842 [16]. + +It identifies the Telecommunications Management Network (TMN) object classes required for the management of the MS SPR protection function for SDH network elements. These objects are relevant to information exchanged across standardized interfaces defined in ITU-T M.3010 [3] TMN architecture. + +## **Structure of this Recommendation** + +Clause 5 provides an overview of the SDH MS SPR protection information model. Clauses 6 to 13 describe the information model using the notation mechanisms defined in ITU-T X.722 [7]. Clause 13 contains the syntax definitions of the information carried in the protocol using Abstract Syntax Notation One (ASN.1) defined in ITU-T X.680 [8]. Containment and Inheritance are illustrated in Appendix I. + +# **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. + +- [1] ITU-T G.707/Y.1322 (2000), *Network node interface for the synchronous digital hierarchy (SDH)*. +- [2] ITU-T G.708 (1999), *Sub STM-0 network node interface for the synchronous digital hierarchy (SDH)*. +- [3] ITU-T M.3010 (2000), *Principles for a telecommunication management network*. +- [4] ITU-T M.3100 (1995), *Generic network information model*. +- [5] ITU-T G.783 (2000), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks*. +- [6] ITU-T G.784 (1999), *Synchronous digital hierarchy (SDH) management*. +- [7] ITU-T X.722 (1992), *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects, plus Amd.1 (1995), Amd.2 (1997) and Cor.1 (1996)*. +- [8] ITU-T X.680 (1997), *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation*. + +- [9] ITU-T X.720 (1992), *Information technology – Open Systems Interconnection – Structure of Management Information: Management information model, plus Amd.1 (1995) and Cor.1 (1994)*. +- [10] ITU-T G.774 (2001), *Synchronous digital hierarchy (SDH) – Management information model for the network element view*. +- [11] ITU-T G.774.1 (2001), *Synchronous digital hierarchy (SDH) – Bidirectional performance monitoring for the network element view*. +- [12] ITU-T G.803 (2000), *Architecture of transport networks based on the synchronous digital hierarchy (SDH)*. +- [13] ITU-T X.721 (1992), *Information technology – Open Systems Interconnection – Structure of management information – Definition of management information, plus Cor.1 (1994), Cor.2 (1996), Cor.3 (1998) and Cor.4 (2000)*. +- [14] ITU-T G.774.3 (2001), *Synchronous digital hierarchy (SDH) – Management of multiplex-section protection for the network element view*. +- [15] ITU-T G.841 (1998), *Types and characteristics of SDH network protection architectures*. +- [16] ITU-T G.842 (1997), *Interworking of SDH network protection architectures*. +- [17] ITU-T G.774.4 (2001), *Synchronous digital hierarchy (SDH) – Management of the subnetwork connection protection for the network element view*. +- [18] ITU-T G.774.9 (2001), *Synchronous digital hierarchy (SDH) – Configuration of linear multiplex section protection for the network element view*. + +# 3 Terms and Definitions + +This Recommendation uses the terms and definitions defined in ITU-T G.774, ITU-T G.784, ITU-T G.841, ITU-T G.842 and ITU-T M.3100. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|----------------------------------------------------------------------------------| +| AIS | Alarm Indication Signal | +| APDU | Application Protocol Data Unit | +| APS | Automatic Protection Switching | +| CMIP | Common Management Information Protocol | +| CMIS | Common Management Information Service | +| CTP | Connection Termination Point | +| ISO | International Organization for Standardization | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| LOF | Loss Of Frame | +| LOS | Loss Of Signal | +| MS | Multiplex Section | +| MSP | Multiplex Section Protection | +| NE | Network Element | + +| | | +|-------|---------------------------------------| +| OS | Operations System | +| OSI | Open Systems Interconnection | +| Pkg | Package | +| RDN | Relative Distinguished Name | +| RRP | Reliable Resource Pointer | +| SD | Signal Degrade | +| SDH | Synchronous Digital Hierarchy | +| SF | Signal Fail | +| SNCP | Subnetwork Connection Protection | +| SPR | Shared Protection Ring | +| STM-N | Synchronous Transport Module N | +| TMN | Telecommunications Management Network | +| TP | Termination Point | +| TTP | Trail Termination Point | +| URP | Unreliable Resource Pointer | +| WTR | Wait-to-Restore | + +# 5 SDH MS shared protection ring (SPR) protection management + +The SDH MS SPR model is based on those generic classes and modeling principles outlined in ITU-T M.3100 and on those common classes from ITU-T G.774.3. + +## 5.1 SDH MS SPR protection management requirements + +The management information model of the MS SPR protection shall support the following requirements: + +- According to the layer concept described in ITU-T G.805, it shall be possible to add/remove or modify a layer network inside the NE having no effect on the other layers. That is, the MS SPR protection sublayer has to be introduced inside the MS layer from the functional point of view without having any effect on Path layer. +- The establishment and dismiss of MS SPR protection has to be done without affecting traffic. +- The migration from already deployed network to a MS SPR has to be done without traffic cut, including migration from SNCP ring to 2F/4F MS SPR and migration from 2F to 4F ring. +- According to ITU-T G.841, the model should support any kind of path layer traffic, including unidirectional point-to-point, unidirectional point-to-multipoint (broadcast), and bidirectional. +- The existing capabilities of dynamic connection configuration (creation, deletion and modification) have to be maintained; especially in case of modifications that do not affect traffic. (Add/remove leg, add/remove Drop and Continue for dual homing application, RIP table.) +- Configure 2-Fiber or 4-Fiber MS SPR or Transoceanic application. +- The information model shall support bidirectional ring switch. + +- The information model shall support 4-Fiber bidirectional span switch. +- The information model shall support forced and manual switch. +- The information model shall support lock out of the protected and protecting facility. +- The information model shall support exercise of protection switch for maintenance activity. +- The information model shall support wait-to-restore time provisioning. +- Modifying the ring topology without impacting existing traffic as long as the node being removed is not involved in the traffic. +- Modifying the G.841 node ID (consequent change to ring map configuration) without causing spurious protection switch. This may happen because until the update are completed in all the nodes, the ring data may not be consistent. +- Changing a channel from NUT type to protected-type should not affect its traffic. +- Changing a channel from protected type to NUT type shall be allowed. If the channel is not in protection, the change shall not affect the traffic. +- Updating squelching information should not cause interruption to traffic. +- Configuration of a NE to support multiple MS SPR and the interconnection among these rings. + +## 5.2 SDH MS SPR information model overview + +The model provides a similar way to control and operate the MS SPR protection function as the other protection functions. The model defines two subclasses of the generic G.774.3 protection model: + +- **msSPRProtectionGroup**, which represents the association of unreliable resources for the purpose of automatic protection switching and which is the focal point for all management operation related to the MS SPR protection function. +- **msSPRProtectionUnit**, which represents the protected or the protecting unit and which represents the assignment of an unreliable resource to one reliable resource. The **msSPRProtectionUnit** is contained by a **msSPRProtectionGroup**. + +The model defines the following additional object classes specific for MS SPR: + +- **sdhMSSPRProtectionCoordinator**, which is used specifically to configure SDH MS SPR protection schemes. Only one instance can be created in one NE. When the **establishProtection** action is successfully performed, the following objects are created: one **msSPRProtectionGroup** instance, 4 **msSPRProtectionUnit** instances, one **sPRingManager** instance, and one **squelchTable** instance are created as specified by the action information. Deletion of **msSPR** protection schemes is accomplished via the **dismissProtection** action. When this action is successfully performed the **sPRingManager** and all associated objects are deleted. The **changeSPRConfiguration** action is used to migrate between two fiber and four fiber configurations, or to add or remove NUT or RIP capability, without deleting all the other objects associated with the protection scheme. The result of this action is that the protection group and associated units are deleted and recreated with the appropriate conditional packages present. +- **sPRingManager**, which is used to characterize a single shared protection ring, providing a pointer to the **msSPRProtectionGroup** object, and containing instances of any other objects needed to support the ring (e.g. **nutTable**, **ripTable**, **squelchTable**). +- **nutTable**, which contains information to identify the channels that have been provisioned for Non-preemptible Unprotected Traffic (NUT), and identifies which type of switching (span or ring) is prohibited by the NUT. + +- **ripTable**, which represents the RIP (Ring Interconnect on Protection) table in a secondary interconnection node. This table indicates the protection channels that are used to carry secondary circuits in dual-homed interconnection schemes, and the primary node, entry node, and exit node for each of those channels. +- **squelchTable** and **auSquelchTable**, which contain routing information to be used for squelching purposes. + +This model also reuses existing object classes from ITU-T G.774.4 for the service selector function of the interconnection nodes in MS SPR, including: + +- G.774.4 **snmpFabric**, which supports the interconnect function in MS SPR for the service selector function. +- G.774.4 **connectionProtectionGroupR1**, which is used for ring interconnection to choose between the signal coming in on the low speed side and the signal coming in on the high speed side from the other interconnection node. +- G.774.4 **connectionProtection**, which presents the protection unit (protected or protecting) and the assignment between an unreliable resource (high/low order path termination point) and a reliable resource (high/low order path termination point). + +# 6 Managed object class definitions + +### 6.1 auSquelchTable + +``` + +auSquelchTable MANAGED OBJECT CLASS +DERIVED FROM "Recommendation X.721 | ISO/IEC 10165-2":top; +CHARACTERIZED BY +"Recommendation M.3100":attributeValueChangeNotificationPackage, +auSquelchTablePkg PACKAGE +BEHAVIOUR auSquelchTableBeh; +ATTRIBUTES + auNumber GET, + auTable GET;; +REGISTERED AS {g774-10MObjectClass 1}; +auSquelchTableBeh BEHAVIOUR +DEFINED AS + "This object class represents routing information to be used for squelching +purposes. Each instance of this object identifies a single administrative unit +(AU) in the NE for both the east and west sides of the NE."; +``` + +### 6.2 msSPRProtectionGroup + +``` + +msSPRProtectionGroup MANAGED OBJECT CLASS +DERIVED FROM "Recommendation G.774-03":protectionGroupR1; +CHARACTERIZED BY + "Recommendation G.774-03": protectionSwitchExercisePkg, + msSPRProtectionGroupPkg PACKAGE + BEHAVIOUR msSPRProtectionGroupBeh; + ATTRIBUTES + "Recommendation X.721":administrativeState GET-REPLACE, + "Recommendation G.774-03":protectionGroupType + PERMITTED VALUES SDHMSSPRASN1.MSSPRProtectionGroupType, + "Recommendation G.774-03":revertive + PERMITTED VALUES SDHMSSPRASN1.True; + ACTIONS + "Recommendation G.774-03":invokeProtection mSSPRLockoutTypeParameter, + "Recommendation G.774-03":releaseProtection msSPRLockoutTypeParameter; + NOTIFICATIONS + "Recommendation G.774-03":protectionSwitchReportingR1 +``` + +``` + +msSPRProtectionStatusParameter;; +CONDITIONAL PACKAGES + "Recommendation M.3100":tmnCommunicationsAlarmInformationPackage +PRESENT IF "an instance supports reporting protection protocol failures via +communicationsAlarms", + "Recommendation M.3100":alarmSeverityAssignmentPointerPackage + PRESENT IF "the tmnCommunicationsAlarmInformationPackage is +present", + wtrSpanPkg + PRESENT IF "an instance represents a four fiber MS SPR with a +single wait to restore time for both high-speed spans and the +enhancedWtrSpanPkg is not present", + enhancedWtrSpanPkg + PRESENT IF "an instance represents a four fiber MS SPR with a +separate wait to restore time for each high-speed span and the +wtrSpanPkg is not present"; +REGISTERED AS {g774-10MObjectClass 2}; +msSPRProtectionGroupBeh BEHAVIOUR +DEFINED AS + "An msSPRProtectionGroup object instance contains four msSPRProtectionUnit +objects to define a MS Shared Protection Ring (SPR) protection switching +relationship for two or four fiber MS SPR architectures. If the ring has a four- +fiber architecture, either the wtrSpanPkg or enhancedWtrSpanPkg must be present. +The administrativeState attribute is used to manage the participation of the +protection group in the APS protocol. This capability can be used to avoid +spurious switches when a ring is being initialized or modified. When the +administrativeState is unlocked, the protection group participates fully in the +APS protocol. When the administrativeState is locked, the protection group does +not respond to incoming switch requests (either via K-bytes or management +request); the outgoing K-bytes shall be defaulted as specified in Recommendation +G.841. When the administrativeState is set to shuttingDown, the protectionGroup +shall transition to the locked administrativeState when all switches at the node +have cleared (i.e. when no protected traffic is using protecting bandwidth). +If the tmnCommunicationsAlarmPkg is present, a communicationsAlarm notification +shall be issued if the protection architecture cannot write or detect and process +the contents of the APS channel appropriately. The probableCause parameter of the +notification shall indicate msSPRApsChannelProcessingFailure. +If the tmnCommunicationsAlarmPkg is present, a communicationsAlarm notification +shall be issued if APS trouble defects are declared in an. APS trouble defects +include Default K Bytes, Inconsistent APS Codes, Node ID Mismatch, and Improper +APS Codes. The probableCause parameter of the notification shall indicate +msSPRDefaultKBytes, msSPRInconsistentApsCodes, msSPRNodeIdMismatch, or +msSPRImproperApsCodes. +The inherited protectionGroupType attribute shall always have the value "colon," +since a two-fiber MS SPR represents a 1:1 protection scheme, and a four fiber MS +SPR represents a 2:1 protection scheme. +The inherited waitToRestoreTime attribute specifies the Wait To Restore (WTR) +time for ring protection switches, since only ring switches are common to both +two and four fiber MS SPRs. If the MS SPR is four fiber, the +waitToRestoreTimeSpan attribute (in the wtrSpanPkg conditional package) or the +enhancedWaitToRestoreTimeSpan attribute (in the enhancedWtrSpanPkg conditional +package) specifies the WTR time for span switches. +The inherited revertive attribute specifies shall always have the value "True", +since MS SPRs are required to operate in the revertive mode. +The invokeProtection action, which is inherited from the protectionGroupR1 object +class, can be used to request a lockout (i.e., lockout of one or more protection +units in a msSPRProtectionGroup), a forced switch (span or ring), or a manual +switch (span or ring) on one or more msSPRProtectionUnit instances contained in +the msSPRProtectionGroup object. The msSPRProtectionUnit instances involved in +the protection switch must be indicated explicitly in the action argument. +The releaseProtection action inherited from the protectionGroupR1 object class +can be used to release a lockout (i.e., release lockout of one or more +protection units in a msSPRProtectionGroup), a forced switch (span or ring), or a +manual switch (span or ring) on one or more msSPRProtectionUnit instances + +``` + +contained in the **msSPRProtectionGroup** object. The **msSPRProtectionUnit** instances involved in the protection release must be indicated explicitly in the action argument. + +The **invokeExercise** action can be used to initiate an exercise (ring for two fiber, ring or span for four fiber). The **msSPRProtectionUnit** instances involved in the protection exercise must be indicated explicitly in the action argument. The **protectionSwitchReportingR1** notification is emitted from the **msSPRProtectionGroup** object to report any protection switching events as described in the **msSPRProtectionStatusParameter**, such as a protection switch (forced (span or ring) switch, manual (span or ring) switch, or automatic (span or ring) switch), protection release (release of forced (span or ring) switch, manual (span or ring) switch, or automatic (span or ring) switch), lockout, or release of lockout. + +A change in the value of the **administrativeState** or **operationalState** shall cause a **stateChange** notification (inherited) to be emitted. + +A change in the value of the following attributes, provided the attribute is present in the managed object, and the **attributeValueChange** notification is supported, shall cause an **attributeValueChange** notification: **waitToRestoreTime** (inherited), **waitToRestoreTimeSpan**, **enhancedWaitToRestoreTimeSpan**." + +### 6.3 msSPRProtectionUnit + +**msSPRProtectionUnit** MANAGED OBJECT CLASS +DERIVED FROM "Recommendation G.774-03":protectionUnit; +CHARACTERIZED BY + +"Recommendation G.774-03":lastAttemptResultPkg, +**msSPRProtectionUnitPkg** PACKAGE +BEHAVIOUR **msSPRProtectionUnitBeh**; +ATTRIBUTES + +"Recommendation G.774-03":reliableResourcePointer +PERMITTED VALUES **SDHMSSPRASN1.SDHMSResourcePointer** +GET, +"Recommendation G.774-03":unreliableResourcePointer +PERMITTED VALUES **SDHMSSPRASN1.SDHMSResourcePointer** +GET, +**msSPRProtectionStatus** GET, +**ringPU** GET;;; + +CONDITIONAL PACKAGES + +**fourFiberPUPkg** + +PRESENT IF "an instance supports a four fiber MS SPR", + +"Recommendation G.774-03":extraTrafficControlPkg + +PRESENT IF "extra traffic may be suspended and resumed"; + +REGISTERED AS {g774-10MObjectClass 3}; + +**msSPRProtectionUnitBeh** BEHAVIOUR + +DEFINED AS + +"This object class is specific to MS Shared Protection Ring (SPR) protection systems. Instances of this object class represent a relationship between a **protectedTTP** and an **unprotectedCTP**. If this is a protecting protection unit, the **reliableResourcePointer** points to a **protectedTTP** for extra traffic or NULL if there is no extra traffic. + +When a SPR node enters the pass through state (either full or partial), the **unprotectedCTP** upstream and downstream connectivity pointers managed by the two protecting **msSPRProtectionUnit** protection units (on either side of the node) shall be updated to point to each other. + +The **ringPU** attribute points to the **msSPRProtectionUnit** that would be involved in a ring switch (or release), or the associated **msSPRProtectionUnit** on the other (or opposite) side of the SPR node. This attribute is applicable to both two and four fiber SPRs. + +The **spanPU** attribute (in the **fourFiberPUPkg**) points to the **msSPRProtectionUnit** that would be involved in a span switch (or release), or the associated **msSPRProtectionUnit** on the same side of the SPR node. This attribute is applicable only to four fiber SPRs." + +### 6.4 nutTable + +**nutTable** MANAGED OBJECT CLASS +DERIVED FROM "Recommendation X.721 | ISO/IEC 10165-2":top; +CHARACTERIZED BY +    "Recommendation M.3100":attributeValueChangeNotificationPackage, +    **nutTablePkg** PACKAGE +        BEHAVIOUR **nutTableBeh**; +        ATTRIBUTES +            **nutTableId** GET, +            **nutChannelList** GET-REPLACE ADD-REMOVE; ; ; +REGISTERED AS {g774-10MObjectClass 4}; +**nutTableBeh** BEHAVIOUR +DEFINED AS +    "This object class contains information to identify the channels that have been provisioned for Non-preemptible Unprotected Traffic (NUT), and identifies which type of switching (span or ring) is prohibited by the NUT. In a 2-fiber ring, span switches are always unavailable, and the corresponding component of the syntax shall be absent. A change in the value of the **nutChannelList** attribute shall cause an **attributeValueChange** notification to be emitted."; + +### 6.5 ripTable + +**ripTable** MANAGED OBJECT CLASS +DERIVED FROM "Recommendation X.721 | ISO/IEC 10165-2":top; +CHARACTERIZED BY +    "Recommendation M.3100":attributeValueChangeNotificationPackage, +    **ripTablePkg** PACKAGE +        BEHAVIOUR **ripTableBeh**; +        ATTRIBUTES +            **ripTableId** GET, +            **ripChannelList** GET; +        ACTIONS +            **updateRipTable**; ; ; +REGISTERED AS {g774-10MObjectClass 5}; +**ripTableBeh** BEHAVIOUR +DEFINED AS +    "This object class represents the RIP table in a secondary interconnection node. This table indicates the protection channels that are used to carry secondary circuits in dual-homed interconnection schemes, and the primary node and terminating node for each of those channels. The table is updated as a result of the **updateRipTable** action. A change in the value of the **ripChannelList** shall cause an **attributeValueChange** notification to be emitted."; + +### 6.6 sdhMSSPRProtectionCoordinator + +**sdhMSSPRProtectionCoordinator** MANAGED OBJECT CLASS +DERIVED FROM "Recommendation G.774-09":protectionCoordinator; +CHARACTERIZED BY +    **sdhMSSPRProtectionCoordinatorPkg** PACKAGE +    BEHAVIOUR **sdhMSSPRProtectionCoordinatorBeh**; +    ACTIONS +        "Recommendation G.774-09":establishProtection +            **msSPRProtectionGroupConfigParameter** +            **msSPRConfigurationError**; ; ; +CONDITIONAL PACKAGES +    **changeSPRConfigurationPkg** PRESENT IF "the network element supports modification of SPR configuration (number of fibers, NUT, RIP, extra traffic) without traffic disruption"; +REGISTERED AS {g774-10MObjectClass 6}; +**sdhMSSPRProtectionCoordinatorBeh** BEHAVIOUR + +#### DEFINED AS + +"This object class is used specifically to configure SDH MSSPR protection schemes. Only one instance can be created in one NE. When the **establishProtection** action is successfully performed, the following objects are created: one **msSPRProtectionGroup** instance, 4 **msSPRProtectionUnit** instances, one **sPRingManager** instance, and one **squelchTable** instance are created as specified by the action information. If appropriate, an instance of **nutTable** and/or **ripTable** is also created. The **unreliableResourcePointer** of each **msSPRProtectionUnit** will point to the **unprotectedCTP** indicated by the **unreliableObjects** field of the action information. The **reliableResourcePointer** will point to the **protectedTTP** connected to the **unprotectedCTP**, unless the **protectionUnit** is protecting and extra traffic is not required or not supported (in this case the **reliableResourcePointer** is NULL). Since the **protectionGroupType** of **msSPRProtectionGroup** is always 'colon', the **protectionGroupType** field of the argument of the **establishProtection** action shall always be 'colon' or not present in the argument. Since the MS-SPR protection scheme is always revertive, the revertive field of the **establishProtection** action shall always be true; the **waitToRestoreTime** field shall specify the wait to restore time for ring switches. The priority field of the argument of the **establishProtection** action shall not be present in the argument. Additional information specific to the MS SPR is conveyed via the parameters attached to the **establishProtection** action. To avoid spurious protection switches, the **msSPRProtectionGroup** is created with the **administrativeState** set to locked. **UnprotectedCTPs** and **protectedTTPs** are always instantiated for multiplex sections that can potentially be included in a protection group irrespective of whether protection is actually present or not. When a section is not part of a protection group, the **crossConnectionObjectPointer** of the **unprotectedCTP** and **protectedTTP** point to the **managedElement**. When protection is established, the **crossConnectionObjectPointer** points to the associated **msSPRProtectionUnit**. When it is possible, **unprotectedCTPs** and **protectedTTPs** may be created/deleted as a result of the **establish/dismiss** actions. Deletion of **msSPR** protection schemes is accomplished via the **dismissProtection** action. When this action is successfully performed the **sPRingManager** and all associated objects are deleted. The **changeSPRConfiguration** action is used to migrate between two fiber and four fiber configurations, or to add or remove NUT or RIP capability, without deleting all the other objects associated with the protection scheme. The result of this action is that the protection group and associated units are deleted and recreated with the appropriate conditional packages present."; + +### 6.7 sPRingManager + +**sPRingManager** MANAGED OBJECT CLASS +DERIVED FROM "Recommendation X.721 | ISO/IEC 10165-2":top; +CHARACTERIZED BY +    "Recommendation M.3100":attributeValueChangeNotificationPackage, +    "Recommendation M.3100":createDeleteNotificationsPackage, +    **sPRingManagerPkg** PACKAGE +        BEHAVIOUR **sPRingManagerBeh**; +        ATTRIBUTES +            **sPRingManagerId** GET, +            **directionTable** GET, +            **nodeNumber** GET, +            **protectionGroupPointer** GET, +            **ringId** GET-REPLACE, +            **ringMap** GET, +            **sPRingApplication** GET;;; +CONDITIONAL PACKAGES +    **manualSPRConfigurationPkg** +        PRESENT IF "the direction table, node number, and ring map can be +        modified by a manager", +        **restoreExtraTrafficPkg** PRESENT IF "configuration of extra traffic +        restoration is supported"; + +REGISTERED AS {g774-10MObjectClass 7}; +sPRingManagerBeh BEHAVIOUR +DEFINED AS + +"This object class is used to characterize a single shared protection ring, providing a pointer to the **msSPRProtectionGroup** object, and containing instances of any other objects needed to support the ring (e.g. **nutTable**, **ripTable**, **squelchTable**). + +The **directionTable** attribute identifies the TTPs on the east and west sides of the node over the relevant ring. This table is used to assist in populating the **squelchTable**. + +The **nodeNumber** attribute indicates the node number within the ring for this node. The **ringMap** attribute indicates the sequence of nodes around the ring. The **ringId** provides an identifier that should be provisioned with the same value in each node on the ring. + +The **sPRingApplication** attribute indicates whether the ring operates in classic mode or transoceanic mode. + +A change in the value of the following attributes shall cause an **attributeValueChange** notification to be emitted: **directionTable**, **nodeNumber**, **ringId**, **ringMap**." + +### 6.8 squelchTable + +squelchTable MANAGED OBJECT CLASS +DERIVED FROM "Recommendation X.721 | ISO/IEC 10165-2":top; +CHARACTERIZED BY +"Recommendation M.3100":attributeValueChangeNotificationPackage, +"Recommendation M.3100":createDeleteNotificationsPackage, +squelchTablePkg PACKAGE +BEHAVIOUR squelchTableBeh; +ATTRIBUTES +squelchTableId GET, +currentSquelchingList GET; +ACTIONS +updateSquelchTable;;; +REGISTERED AS {g774-10MObjectClass 8}; +squelchTableBeh BEHAVIOUR +DEFINED AS + +"This object class serves as the head of the naming tree for each entry in the squelch table. Entries are managed as separate objects; the contents of these objects can be modified using the **updateSquelchTable** action. + +The **currentSquelchingList** holds information regarding which channels are currently being squelched. A change in the value of the **currentSquelchingList** attribute shall cause an **attributeValueChange** notification to be emitted." + +# 7 Packages + +## 7.1 changeSPRConfigurationPkg + +changeSPRConfigurationPkg PACKAGE +BEHAVIOUR changeSPRConfigurationPkgBeh; +ACTIONS changeSPRConfiguration; +REGISTERED AS {g774-10Package 1}; +changeSPRConfigurationPkgBeh BEHAVIOUR +DEFINED AS + +"This package provides an action that allows the manager to make changes to the SPR functions without disruption of existing service (provided that the requested changes are compatible with the existing service). The allowable changes are: migration from two-fiber to four-fiber operation and vice versa; enabling and disabling non-user preemptible traffic; enabling and disabling ring interworking on protection; and enabling and disabling extra traffic." + +## 7.2 enhancedWtrSpanPkg + +``` +enhancedWtrSpanPkg PACKAGE +BEHAVIOUR enhancedWtrSpanPkgBeh; +ATTRIBUTES + enhancedWaitToRestoreTimeSpan GET-REPLACE; +REGISTERED AS {g774-10Package 2}; +enhancedWtrSpanPkgBeh BEHAVIOUR +DEFINED AS +"This package provides additional information necessary to support four fiber MS +SPR protection architectures with separate wait to restore times for each span. +The enhancedWaitToRestoreTimeSpan attribute specifies the wait to restore time +for a span switch for each span. A change in the value of the +enhancedWaitToRestoreTimeSpan attribute shall cause an attributeValueChange +notification to be emitted."; +``` + +### 7.3 fourFiberPUPkg + +``` +fourFiberPUPkg PACKAGE +BEHAVIOUR fourFiberPUPkgBeh; +ATTRIBUTES +spanPU GET; +REGISTERED AS {g774-10Package 3}; +fourFiberPUPkgBeh BEHAVIOUR +DEFINED AS +"This package provides additional information necessary to support four fiber MS +SPR protection architectures. The spanPU attribute in this package indicates +which corresponding protection unit in the protection group will be involved in a +span switch or span switch release. "; +``` + +## 7.4 manualSPRConfigurationPkg + +``` +manualSPRConfigurationPkg PACKAGE + BEHAVIOUR manualSPRConfigurationPkgBeh; + ATTRIBUTES + directionTable GET-REPLACE, + nodeNumber GET-REPLACE, + ringMap GET-REPLACE; +REGISTERED AS {g774-10Package 4}; +manualSPRConfigurationPkgBeh BEHAVIOUR +DEFINED AS +"This package provides the ability to configure the values of the +directionTable, nodeNumber, and ringMap attributes. It is used when autodiscovery +of this information is not supported."; +``` + +### 7.5 restoreExtraTrafficPkg + +``` +restoreExtraTrafficPkg PACKAGE + BEHAVIOUR restoreExtraTrafficPkgBeh; + ATTRIBUTES + restoreExtraTraffic + DEFAULT VALUE SDHMSSPRASN1.booleanTrueDefault + GET-REPLACE; +REGISTERED AS {g774-10Package 5}; +restoreExtraTrafficPkgBeh BEHAVIOUR +DEFINED AS +"The restoreExtraTraffic attribute indicates whether extra traffic is to be +automatically re-established after the completion of a normal protection +switching session (i.e. after traffic is restored on the protected facility). The +value TRUE indicates that the automatic restoration should occur."; +``` + +## 7.6 wtrSpanPkg + +``` +wtrSpanPkg PACKAGE +BEHAVIOUR wtrSpanPkgBeh; +ATTRIBUTES +waitToRestoreTimeSpan GET-REPLACE; +REGISTERED AS {g774-10Package 6}; +wtrSpanPkgBeh BEHAVIOUR +DEFINED AS +"This package provides additional information necessary to support four fiber MS +SPR protection architectures with a single wait to restore time for both high- +speed spans. The waitToRestoreTimeSpan attribute specifies the wait to restore +time for a span switch. A change in the value of the waitToRestoreSpan attribute +shall cause an attributeValueChange notification to be emitted."; +``` + +# 8 Attributes + +## 8.1 auTable + +``` +auTable ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.SquelchTableEntry; +MATCHES FOR EQUALITY; +BEHAVIOUR auTableBeh; +REGISTERED AS {g774-10Attribute 1}; +auTableBeh BEHAVIOUR +DEFINED AS +"This attribute specifies the current squelch table for an individual AU. The +value of this attribute is updated automatically as a result of the +updateSquelchTable action. The table is divided into East and West, which can be +determined by referencing the directionTable attribute of the sPRingManager +object. +The aNode and zNode fields indicate the source and destination of the circuit, +respectively (or NULL if no circuit using the channel in that direction). +If an AU is part of a contiguously concatenated signal, but is not the first AU +in that concatenated signal, it shall still be represented in the AU Squelch +Table. The information for all of the concatenated channels shall be the same, +with the exception of the "concatenated" field; the first channel shall indicate +the number of concatenated AU channels, while all others simply indicate that +they are concatenated to a previous channel."; +``` + +### 8.2 auNumber + +``` +auNumber ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.NameType; +MATCHES FOR EQUALITY, ORDERING; +BEHAVIOUR auNumberBeh; +REGISTERED AS {g774-10Attribute 2}; +auNumberBeh BEHAVIOUR +DEFINED AS +"The auNumber attribute is an attribute type whose distinguished value can be +used as an RDN when naming an instance of the auSquelchTable managed object +class. This attribute identifies the AU number of the working AU in an STM-N +system. The value shall be the integer that represents the position of the AU in +temporal order. The first AU shall be numbered one. If M working AUs are +available, the range of possible values for this shall attribute be 1 through +M."; +``` + +### 8.3 currentSquelchingList + +``` +currentSquelchingList ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.CurrentSquelchingList; +MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION; +BEHAVIOUR currentSquelchingListBeh; +REGISTERED AS {g774-10Attribute 3}; +currentSquelchingListBeh BEHAVIOUR +DEFINED AS +"This attribute contains a list of termination points and their associated cross-connection objects that are currently being squelched. If the AU is not cross-connected (i.e. hardwired), the cross-connection object choice is not used. "; +``` + +### 8.4 directionTable + +``` +directionTable ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.DirectionTable; +MATCHES FOR EQUALITY; +BEHAVIOUR directionTableBeh; +REGISTERED AS {g774-10Attribute 4}; +directionTableBeh BEHAVIOUR +DEFINED AS +"This attribute specifies the direction table. It specifies msTTP object instances for both the East and West high speed sides of the sdhNE. East implies the side of the network element that is associated with the direction of the (n+1)th node in the ring indicated in the sequence of the ring map; West implies the side of the network element that is associated with the direction of the (n-1)th node in the ring indicated in the sequence of the ring map, where the nth node is the node in which the table resides. Note that n-1 and n+1 indicate the element in the sequence, not the actual number of the node. The last node in the sequence is the (n-1)th node of the first node in the sequence. Likewise, the first node in the sequence is the (n+1)th node to the last node in the sequence. "; +``` + +### 8.5 enhancedWaitToRestoreTimeSpan + +``` +enhancedWaitToRestoreTimeSpan ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.EnhancedWaitToRestoreSpan; +MATCHES FOR EQUALITY; +BEHAVIOUR enhancedWaitToRestoreTimeSpanBeh; +REGISTERED AS {g774-10Attribute 5}; +enhancedWaitToRestoreTimeSpanBeh BEHAVIOUR +DEFINED AS +"This attribute indicates the wait to restore time, in seconds, for a span switch. The value is specified separately for the east and west spans."; +``` + +### 8.6 msSPRProtectionStatus + +``` +msSPRProtectionStatus ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.MSSPRProtectionStatus; +MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION; +BEHAVIOUR msSPRProtectionStatusBeh; +REGISTERED AS {g774-10Attribute 6}; +msSPRProtectionStatusBeh BEHAVIOUR +DEFINED AS +"This attribute is used to indicate the status of the MS SPR protection switch in a msSPRProtectionUnit object instance. This attribute is set-valued because some requests are allowed to be pending. The following rule shall be followed: only one of the values lockout, forcedSwitch (span or ring), or manualSwitch (span or ring) can be present at the same time, either local or remote. It is also possible to have two or more pending automatic switch (span or ring) requests. The msSPRProtectionStatus attribute of a +``` + +**msSPRProtectionUnit** that provides protection is used to hold the protection request that is actually performed on that **msSPRProtectionUnit**. + +The following is a list of all the possible status values of the **msSPRProtectionStatus** attribute for a protected **msSPRProtectionUnit** object instance: + +- No Request: No switch request is present on the unit. +- Manual Ring Switch to Protecting Complete: The unit has completed a manual ring switch. +- Manual Span Switch to Protecting Complete: The unit has completed a manual span switch (Four-Fiber Rings only). +- Release failed: A switch has been released or pre-empted and a time-out occurs while waiting for a release of associated bridges, or the near-end switch. +- Automatic Ring Switch (SF) Pending: The unit has a Signal Fail condition present and the protecting unit for a ring switch is unavailable. +- Automatic Ring Switch (SD) Pending: The unit has a Signal Degrade condition present and the protecting unit for a ring switch is unavailable. +- Automatic Ring Switch (SF) Complete: The unit has completed an automatic ring switch to the protecting unit due to a Signal Fail condition. +- Automatic Span Switch (SF) Complete: The unit has completed an automatic span switch to the protecting unit due to a Signal Fail condition. +- Automatic Ring Switch (SD) Complete: The unit has completed an automatic ring switch to the protecting unit due to a Signal Degrade condition. +- Automatic Span Switch (SD) Complete: The unit has completed an automatic span switch to the protecting unit due to a Signal Degrade condition. +- Automatic Ring Switch (SF) Present, Operate Failed: An automatic ring switch (due to a Signal Fail condition) request is in progress and a time-out occurs while waiting for completion. +- Automatic Span Switch (SF) Present, Operate Failed: An automatic span switch (due to a Signal Fail condition) request is in progress and a time-out occurs while waiting for completion (Four-Fiber Ring only). +- Automatic Ring Switch (SD) Present, Operate Failed: An automatic ring switch (due to a Signal Degrade condition) request is in progress and a time-out occurs while waiting for completion. +- Automatic Span Switch (SD) Present, Operate Failed: An automatic span switch (due to a Signal Degrade condition) request is in progress and a time-out occurs while waiting for completion (Four-Fiber Ring only). +- Force Ring Switch Complete, Automatic Ring Switch (SF) Pending: The unit has completed a Force ring switch. Additionally, the unit has an automatic ring switch (SF) pending. +- Force Ring Switch Complete, Automatic Span Switch (SF) Pending: The unit has completed a Force ring switch. Additionally, the unit has an automatic span switch (SF) pending (Four-Fiber Ring only). +- Force Span Switch Complete, Automatic Ring Switch (SF) Pending: The unit has completed a Force span switch. Additionally, the unit has an automatic ring switch (SF) pending (Four- Fiber Ring only). +- Force Span Switch Complete, Automatic Span Switch (SF) Pending: The unit has completed a Force span switch. Additionally, the unit has an automatic span switch (SF) pending (Four-Fiber Ring only). +- Force Ring Switch Complete, Automatic Ring Switch (SD) Pending: The unit has completed a Force ring switch. Additionally, the unit has an automatic ring switch (SD) pending. +- Force Ring Switch Complete, Automatic Span Switch (SD) Pending: The unit has completed a Force ring switch. Additionally, the unit has an automatic span switch (SD) pending (Four-Fiber Ring only). +- Force Span Switch Complete, Automatic Ring Switch (SD) Pending: The unit has completed a Force span switch. Additionally, the unit has an automatic ring switch (SD) pending (Four-Fiber Ring only). +- Force Span Switch Complete, Automatic Span Switch (SD) Pending: The unit has completed a Force span switch. Additionally, the unit has an automatic span switch (SD) pending (Four-Fiber Ring only). +- Automatic Ring Switch Complete, Wait-to-Restore: The unit has completed an automatic ring switch to the protecting unit, and has entered the wait to restore state. + +- Automatic Span Switch Complete, Wait-to-Restore: The unit has completed an automatic span switch to the protecting unit (Four-Fiber Ring only), and has entered the wait to restore state. +- Force Ring Switch complete: The unit has completed a Force ring switch to the protecting unit. +- Force Span Switch complete: The unit has completed a Force span switch to the protecting unit (Four-Fiber Ring only). +- Protected Unit Lockout Completed: The unit has been locked out from the protecting unit. +- Protected Unit Lockout Complete, Operate Failed: The unit has been locked out from the protecting unit, and, the previously completed switch could not be released within the expected time-out. When the switch is released, the operate failed status is removed. + +The following allowable **msSERRProtectionStatus** values are associated with each protecting unit: + +- No Request: No switch request is present on the unit. +- Manual Ring Switch to Protecting Complete: The protected unit has completed a manual ring switch. +- Manual Span Switch to Protecting Complete: The protected unit has completed a manual span switch (Four-Fiber Rings only). +- Automatic Ring Switch (SF) Complete to Protecting Unit: The protected unit has completed an automatic ring switch to the protecting unit due to a Signal Fail condition. +- Automatic Span Switch (SF) Complete to Protecting Unit: The protected unit has completed an automatic span switch to the protecting unit due to a Signal Fail condition (Four-Fiber Ring only). +- Automatic Ring Switch (SD) Complete to Protecting Unit: The protected unit has completed an automatic ring switch to the protecting unit due to a Signal Degrade condition. +- Automatic Span Switch (SD) Complete to Protecting Unit: The protected unit has completed an automatic span switch to the protecting unit due to a Signal Degrade condition (Four-Fiber Ring only). +- Automatic Ring Switch Complete (SF) to Protecting Unit, Protecting Unit Signal Degraded: The protected unit has completed an automatic ring switch to the protecting unit. Additionally, the protecting unit has a Signal Degrade condition present. +- Automatic Span Switch Complete (SF) to Protecting Unit, Protecting Unit Signal Degraded: The protected unit has completed an automatic span switch to the protecting unit. Additionally, the protecting unit has a Signal Degrade condition present (Four-Fiber Ring only). +- Automatic Ring Switch Complete (SD) to Protecting Unit, Protecting Unit Signal Degraded: The protected unit has completed an automatic ring switch to the protecting unit. Additionally, the protecting unit has a Signal Degrade condition present. +- Automatic Span Switch Complete (SD) to Protecting Unit, Protecting Unit Signal Degraded: The protected unit has completed an automatic span switch to the protecting unit. Additionally, the protecting unit has a Signal Degrade condition present (Four-Fiber Ring only). +- Protecting Unit Full Pass-through: The protecting unit is in full pass-through mode as a result of a ring switch elsewhere in the ring. +- Protecting Unit K-byte Pass-through: The protecting unit is in K-byte pass-through mode as a result of span switches elsewhere in the ring. +- Protecting Unit SD Present: The protecting unit has a Signal Degrade condition present. This state may also be a result improper or inconsistent APS code, default K-Bytes, or node ID mismatch. +- Protecting Unit SF Present: The protecting unit has a Signal Fail condition present. This state may also be a result improper or inconsistent APS code, default K-Bytes, or node ID mismatch. +- Force Ring Switch Complete to Protecting Unit: The protected unit has completed a Force ring switch to the protecting unit. +- Force Span Switch Complete to Protecting Unit: The protected unit has completed a Force span switch to the protecting unit (Four-Fiber Ring only). + +- Force Ring Switch Complete to Protecting Unit, SD Present on Protecting Unit: The protected unit has completed a Force ring switch to the protecting unit. Additionally, there is a Signal Degrade present on the protecting unit. + - Force Span Switch Complete to Protecting Unit, SD Present on Protecting Unit: The protected unit has completed a Force span switch to the protecting unit. Additionally, there is a Signal Degrade present on the protecting unit (Four-Fiber Ring only). + - Protecting Unit Locked Out: The protecting unit has been locked out. + - Protecting Unit Locked Out, Release failed: A release of a lockout is in progress and a time-out occurs waiting for the lockout condition to clear. +- "; + +## 8.7 nodeNumber + +**nodeNumber ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.NodeNumber;** +**MATCHES FOR EQUALITY, ORDERING;** +**BEHAVIOUR nodeNumberBeh;** +**REGISTERED AS {g774-10Attribute 7};** +**nodeNumberBeh BEHAVIOUR** +**DEFINED AS** + "This attribute contains the node identifier. It is an integer with value ranging from 0 to 15. "; + +### 8.8 nutChannelList + +**nutChannelList ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.NutChannelList;** +**MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION;** +**BEHAVIOUR nutChannelListBeh;** +**REGISTERED AS {g774-10Attribute 8};** +**nutChannelListBeh BEHAVIOUR** +**DEFINED AS** + "This attribute identifies the channels that have been provisioned for non-preemptible unprotected traffic. The NUT function can be provisioned separately for ring and span switches, and can be provisioned for protected channels only, or for both protected and protecting channels."; + +### 8.9 nutTableId + +**nutTableId ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.NameType;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR nutTableIdBeh;** +**REGISTERED AS {g774-10Attribute 9};** +**nutTableIdBeh BEHAVIOUR** +**DEFINED AS** + "The **nutTableId** attribute is an attribute type whose distinguished value can be used as an RDN when naming an instance of the **nutTable** managed object class."; + +### 8.10 protectionGroupPointer + +**protectionGroupPointer ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.NameType;** +**MATCHES FOR EQUALITY;** +**REGISTERED AS {g774-10Attribute 10};** + +### 8.11 restoreExtraTraffic + +``` +restoreExtraTraffic ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.BooleanType; +MATCHES FOR EQUALITY; +BEHAVIOUR restoreExtraTrafficBeh; +REGISTERED AS {g774-10Attribute 11}; +restoreExtraTrafficBeh BEHAVIOUR +DEFINED AS +``` + +"This attribute indicates whether extra traffic will be restored immediately when a switch to protection is cleared."; + +### 8.12 ringId + +``` +ringId ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.RingId; +MATCHES FOR EQUALITY; +BEHAVIOUR ringIdBeh; +REGISTERED AS {g774-10Attribute 12}; +ringIdBeh BEHAVIOUR +DEFINED AS +``` + +"This attribute used for identifying the MS SPR protection ring associated with the NE. All NEs of the same protection ring shall have the same **ringId** value for the associated **ringMap**. "; + +### 8.13 ringMap + +``` +ringMap ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.Map; +MATCHES FOR EQUALITY; +BEHAVIOUR ringMapBeh; +REGISTERED AS {g774-10Attribute 13}; +ringMapBeh BEHAVIOUR +DEFINED AS +``` + +"This attribute contains ring map information. "; + +### 8.14 ringPU + +``` +ringPU ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.RelativeDistinguishedName; +MATCHES FOR EQUALITY; +BEHAVIOUR ringPUBeh; +REGISTERED AS {g774-10Attribute 14}; +ringPUBeh BEHAVIOUR +DEFINED AS +``` + +"This attribute identifies which protection unit will be associated with a ring switch or ring switch release in a MS SPR architecture. "; + +### 8.15 ripChannellList + +``` +ripChannellList ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.RipChannellList; +MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION; +BEHAVIOUR ripChannellListBeh; +REGISTERED AS {g774-10Attribute 15}; +ripChannellListBeh BEHAVIOUR +DEFINED AS +``` + +"The **ripChannellList** identifies the protection channels that are being used for RIP circuits. It also identifies the primary interconnection node and terminating node for each RIP circuit."; + +### 8.16 ripTableId + +``` +ripTableId ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.NameType; +MATCHES FOR EQUALITY; +BEHAVIOUR ripTableIdBeh; +REGISTERED AS {g774-10Attribute 16}; +ripTableIdBeh BEHAVIOUR +DEFINED AS +``` + +"The **ripTableId** attribute is an attribute type whose distinguished value can be used as an RDN when naming an instance of the **ripTable** managed object class." + +### 8.17 spanPU + +``` +spanPU ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.RelativeDistinguishedName; +MATCHES FOR EQUALITY; +BEHAVIOUR spanPUBeh; +REGISTERED AS {g774-10Attribute 17}; +spanPUBeh BEHAVIOUR +DEFINED AS +``` + +"This attribute identifies which protection unit will be associated with a span switch or span switch release in a MS SPR architecture." + +### 8.18 sPRingApplication + +``` +sPRingApplication ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.SPRingApplication; +MATCHES FOR EQUALITY; +BEHAVIOUR sPRingApplicationBeh; +REGISTERED AS {g774-10Attribute 18}; +sPRingApplicationBeh BEHAVIOUR +DEFINED AS +``` + +"This attribute indicates the application of the SPR scheme. This determines how the ring responds to failures. Possible values are classic or transoceanic." + +### 8.19 sPRingManagerId + +``` +sPRingManagerId ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.NameType; +MATCHES FOR EQUALITY, ORDERING, SUBSTRINGS; +BEHAVIOUR sPRingCoordinatorIdBeh; +REGISTERED AS {g774-10Attribute 19}; +sPRingCoordinatorIdBeh BEHAVIOUR +DEFINED AS +``` + +"This attribute used for naming instances of the **sPRingManager** object class. If the string choice of the syntax is used, then matching on substrings is permitted. If the number choice of the syntax is used, then matching on ordering is permitted." + +### 8.20 squelchTableId + +``` +squelchTableId ATTRIBUTE +WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.NameType; +MATCHES FOR EQUALITY, ORDERING, SUBSTRINGS; +BEHAVIOUR squelchTableIdBeh; +REGISTERED AS {g774-10Attribute 20}; +squelchTableIdBeh BEHAVIOUR +``` + +#### DEFINED AS + +"This attribute is used for naming instances of the **squelchTable** object class. If the string choice of the syntax is used, then matching on substrings is permitted. If the number choice of the syntax is used, then matching on ordering is permitted. "; + +## 8.21 **waitToRestoreTimeSpan** + +**waitToRestoreTimeSpan** ATTRIBUTE + WITH ATTRIBUTE SYNTAX SDHMSSPRASN1.WaitToRestoreSpan; + MATCHES FOR EQUALITY, ORDERING; + BEHAVIOUR **waitToRestoreTimeSpanBeh**; + REGISTERED AS {g774-10Attribute 21}; +**waitToRestoreTimeSpanBeh** BEHAVIOUR + DEFINED AS + +"This attribute specifies the amount of time, in seconds, to wait after a fault that caused a span switch in a four fiber MS SPR clears before restoring traffic to the protected protection unit that initiated the switching."; + +# 9 Actions + +## 9.1 **changeSPRConfiguration** + +**changeSPRConfiguration** ACTION + BEHAVIOUR **changeSPRConfigurationBeh**; + MODE CONFIRMED; + PARAMETERS +     **msSPRConfigurationError**, +     "Recommendation G.774-09":**removeProtectionError**; + WITH INFORMATION SYNTAX SDHMSSPRASN1.ChangeSPRConfigInfo; + REGISTERED AS {g774-10Action 1}; +**changeSPRConfigurationBeh** BEHAVIOUR + DEFINED AS + +"This action is used to change the following aspects of the configuration of a shared protection ring: + +Two fiber to four fiber and vice versa. For four fiber configurations, there is additionally a choice between normal mode (single wait to restore time for both spans) and enhanced mode (separate wait to restore time for east and west spans). + Enable or disable extra traffic + +Enable or disable Non-preemptible Unprotected Traffic (NUT) + +Enable or disable Ring Interworking on Protection (RIP) + +When the action is successfully performed, and either the number of fibers or the extra traffic configuration is changed, the existing protection group and contained protection units are deleted, and then recreated with the appropriate conditional packages present. No other objects related to the SPR or the traffic it carries are disturbed by this process. + +When the action is successfully performed, and the NUT or RIP configuration is changed, a **nutTable** and/or **ripTable** managed object instance is created or deleted as appropriate. No other objects related to the SPR or the traffic it carries are disturbed by this process. This action fails if the requested configuration is not supported by the network element or is otherwise invalid."; + +## 9.2 **updateRipTable** + +**updateRipTable** ACTION + BEHAVIOUR **updateRipTableBeh**; + MODE CONFIRMED; + WITH INFORMATION SYNTAX SDHMSSPRASN1.UpdateRIPTableInfo; + WITH REPLY SYNTAX SDHMSSPRASN1.UpdateRIPTableReply; + REGISTERED AS {g774-10Action 2}; +**updateRipTableBeh** BEHAVIOUR + +#### DEFINED AS + +"This action provides the means for updating the contents of the Ring Interworking on Protection (RIP) information in a node. The update fails if the primary or terminating node is not in the **ringMap**, or if the channel is not available for RIP (e.g. because it has already been provisioned for NUT)."; + +## 9.3 updateSquelchTable + +**updateSquelchTable ACTION** +**BEHAVIOUR** updateSquelchTableBeh; +**MODE** CONFIRMED; +**WITH INFORMATION SYNTAX** SDHMSSPRASN1.UpdateSquelchTableInfo; +**WITH REPLY SYNTAX** SDHMSSPRASN1.UpdateSquelchTableReply; +**REGISTERED AS** {g774-10Action 3}; +**updateSquelchTableBeh BEHAVIOUR** +**DEFINED AS** + +"This action provides the means for updating the contents of the squelch information in a node. An update fails if the **aNode** or **zNode** is not in the **ringMap**, if the network element does not support the **loAccess** configuration requested, or if the squelching information for the channel cannot be configured as requested because the channel is concatenated to another channel."; + +# 10 Notifications + +None. + +# 11 Parameters + +## 11.1 msSPRConfigurationError + +**msSPRConfigurationError PARAMETER** +**CONTEXT** SPECIFIC-ERROR; +**WITH SYNTAX** SDHMSSPRASN1.MSSPRConfigurationError; +**BEHAVIOUR** msSPRConfigurationErrorBeh; +**REGISTERED AS** {g774-10Parameter 1}; +**msSPRConfigurationErrorBeh BEHAVIOUR** +**DEFINED AS** + +"This parameter is included in the error parameter of the CMIP APDU when the **establishProtection** or **changeSPRConfiguration** action fails due to an error that is specific to MS-SPR configuration."; + +### 11.2 msSPRLockoutTypeParameter + +**msSPRLockoutTypeParameter PARAMETER** +**CONTEXT** ACTION-INFO; +**WITH SYNTAX** SDHMSSPRASN1.RingOrSpan; +**BEHAVIOUR** msSPRLockoutTypeBeh; +**REGISTERED AS** {g774-10Parameter 2}; +**msSPRLockoutTypeBeh BEHAVIOUR** +**DEFINED AS** + +"This parameter is used in the management extension field of the **invokeProtection** and **releaseProtection** actions to define whether a lockout applies to ring switching or span switching."; + +### 11.3 msSPRProtectionGroupConfigParameter + +``` +msSPRProtectionGroupConfigParameter PARAMETER +CONTEXT ACTION-INFO; +WITH SYNTAX SDHMSSPRASN1.MSSPRProtectionGroupConfigInfo; +BEHAVIOUR msSPRProtectionGroupConfigBeh; +REGISTERED AS {g774-10Parameter 3}; +``` + +``` +msSPRProtectionGroupConfigBeh BEHAVIOUR +DEFINED AS +``` + +"This parameter is used in the **specificPGConfiguration** field of the **establishProtection** action received by the **sdhMSSPRProtectionCoordinator** object when the establishment of a **msSPRProtectionGroup** is requested by the management system. + +The information in this parameter is used for provisioning the **msSPRProtectionGroup** and **sPRingManager** objects. The fields of the information syntax are use as follows: + +The **directionTable** information is used to initialize the **directionTable** attribute of the **sPRingManager**. + +The **directionTable** information is used in conjunction with the **protectionUnits** information in the **establishProtection** action information syntax to determine the value of the **spanPU** and **ringPU** attributes of the subordinate **protectionUnits**. + +The **extraTrafficConfig** information, if present, is used to determine which conditional packages are included in the **msSPRProtectionGroup**. If this field is absent, extra traffic is not supported. + +The **nutConfig** information, if present, is used to determine if NUT is supported. If the **nutChannelList** is present, an instance of **nutTable** is also created under the **sPRingManager** and populated with the information from this field. + +The **nodeNumber** and **ringMap** fields are used to populate the **nodeNumber** and **ringMap** attributes, respectively, of the **sPRingManager**. If the node does not support manual configuration of this data, the **nodeNumber** field shall be NULL and the **ringMap** field shall be absent. + +The **ringId** field is used to populate the **ringId** attribute of the **sPRingManager**. + +The **ringType** field is used to set the **sPRingApplication** attribute of the **sPRingManager**, and to control instantiation of the **spanSwitchPkg** and **enhancedSpanSwitchPkg** in the **msSPRProtectionGroup**, and the **fourFiberPU** package in the **msSPRProtectionUnit**. This field also provides the initial values for the **span wait to restore** attributes. + +The **ripConfig** field, if present, indicates if RIP is supported. If the **ripChannelList** is present an instance of **ripTable** is also created under the **sPRingManager** and populated with the information from this field."; + +### 11.4 msSPRProtectionStatusParameter + +``` +msSPRProtectionStatusParameter PARAMETER +CONTEXT EVENT-INFO; +WITH SYNTAX SDHMSSPRASN1.MSSPRProtectionStatusParameter; +BEHAVIOUR msSPRProtectionStatusParameterBeh; +REGISTERED AS {g774-10Parameter 4}; +``` + +``` +msSPRProtectionStatusParameterBeh BEHAVIOUR +DEFINED AS +``` + +"This parameter is included in the additional information field of the protection switch reporting notification. It includes a set of all changed protection status values and the associated protection units. + +This notification is sent by the protection group according to the following rules. There are several cases: + +The switch from protected to protecting or protecting to protected has been done without preempting an existing switch. In this case the old and new values of the Protection Status attribute of the protecting protection unit shall be reported in the notification by means of the **oldProtectionStatus** and **newProtectionStatus** parameters respectively. + +A switch is performed by preempting an existing one. In this case the old and new values of the Protection Status attribute of the protecting protection unit shall + +be reported in the notification by means of the **oldProtectionStatus** and **newProtectionStatus** parameters respectively. + +An auto-switch condition exists on a protection unit, but the auto-switch cannot be served due to the unavailability of the protection unit that otherwise protects it. In this case, the **oldProtectionStatus** and **newProtectionStatus** parameters refer to the protection status attribute value of the protection unit on which the auto-switch condition arises. The exception is when the protection unit is already forced or locked out, in which case no notification is sent. + +A protected protection unit has been locked out or released from lockout without modifying any existing switch. In this case the **oldProtectionStatus** and **newProtectionStatus** parameters refer to the protection status attribute value of the protected protection unit which has been locked out. + +A protecting protection unit has been locked out or released from lockout without modifying the existing switch. In this case the **oldProtectionStatus** and **newProtectionStatus** parameters refer to the protection status attribute value of the protecting protection unit which has been locked out. + +A protecting protection unit has move to or from the full passthrough or K-byte passthrough state. In this case the **oldProtectionStatus** and **newProtectionStatus** parameters refer to the protection status attribute value of the protecting protection unit that has changed state. + +The **protectionSwitchReportingR1** is not sent when the automatic switch condition is toggling between SD, SF and WTR condition. While in the lockout of forced switch state, no notification is sent except for ending of release failure."; + +# 12 Name Bindings + +## 12.1 auSquelchTable-squelchTable + +``` +auSquelchTable-squelchTable NAME BINDING +SUBORDINATE OBJECT CLASS auSquelchTable AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS squelchTable AND SUBCLASSES; +WITH ATTRIBUTE auNumber; +BEHAVIOUR auSquelchTable-squelchTableBeh; +REGISTERED AS {g774-10NameBinding 1}; +auSquelchTable-squelchTableBeh BEHAVIOUR +DEFINED AS +``` + +"An instance of subordinate object class is automatically instantiated as a result of the initial provisioning of squelching information for an AU channel via the **updateSquelchTable** action. "; + +### 12.2 nutTable-sPRingManager + +``` +nutTable-sPRingManager NAME BINDING +SUBORDINATE OBJECT CLASS nutTable AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS sPRingManager AND SUBCLASSES; +WITH ATTRIBUTE nutTableId; +BEHAVIOUR nutTable-sPRingManagerBeh; +REGISTERED AS {g774-10NameBinding 2}; +nutTable-sPRingManagerBeh BEHAVIOUR +DEFINED AS +``` + +"An instance of the subordinate object class is automatically instantiated when an MS SPR that supports NUT is established, or when the configuration of an existing MS SPR is modified to support NUT. The subordinate object class is deleted when the MS SPR is dismissed, or when the configuration is modified such that the MS SPR no longer supports NUT."; + +### 12.3 ripTable-sPRingManager + +``` +ripTable-sPRingManager NAME BINDING + SUBORDINATE OBJECT CLASS ripTable AND SUBCLASSES; + NAMED BY SUPERIOR OBJECT CLASS sPRingManager AND SUBCLASSES; + WITH ATTRIBUTE ripTableId; + BEHAVIOUR ripTable-sPRingManagerBeh; +REGISTERED AS {g774-10NameBinding 3}; +ripTable-sPRingManagerBeh BEHAVIOUR + DEFINED AS + "An instance of the subordinate object class is automatically instantiated +when an MS SPR that supports RIP is established, or when the configuration of an +existing MS SPR is modified to support RIP. The subordinate object class is +deleted when the MS SPR is dismissed, or when the configuration is modified such +that the MS SPR no longer supports RIP."; +``` + +### 12.4 sPRingManager-managedElement + +``` +sPRingManager-managedElement NAME BINDING + SUBORDINATE OBJECT CLASS sPRingManager AND SUBCLASSES; + NAMED BY SUPERIOR OBJECT CLASS + "Recommendation M.3100":managedElement AND SUBCLASSES; + WITH ATTRIBUTE sPRingManagerId; + BEHAVIOUR sPRingManager-managedElementBeh; +REGISTERED AS {g774-10NameBinding 4}; +sPRingManager-managedElementBeh BEHAVIOUR + DEFINED AS + "An instance of the subordinate object class is automatically instantiated +when an SPR is set up (e.g., via actions of a protectionCoordinator). The +instance is deleted when the SPR is removed."; +``` + +### 12.5 squelchTable-sPRingManager + +``` +squelchTable-sPRingManager NAME BINDING + SUBORDINATE OBJECT CLASS squelchTable AND SUBCLASSES; + NAMED BY SUPERIOR OBJECT CLASS + sPRingManager AND SUBCLASSES; + WITH ATTRIBUTE squelchTableId; + BEHAVIOUR squelchTable-sPRingManagerBeh; +REGISTERED AS {g774-10NameBinding 5}; +squelchTable-sPRingManagerBeh BEHAVIOUR + DEFINED AS + "Instances of the subordinate object class are automatically instantiated an MS- +SPR protection scheme is set up, and deleted when the protection scheme is +deleted."; +``` + +### 12.6 Reuse of Existing Name Bindings + +In addition to name bindings defined in this Recommendation, this model also reuses the following name bindings from other Recommendation: + +- ITU-T G.774.3: **protectionGroupR1-managedElement** +This name binding is reused for naming instances of the **msSPRProtectionGroup** object class to instances of the **sdhNE** object class. +- ITU-T G.774.3: **protectionUnit-protectionGroupR1** +This name binding is reused for naming instances of the **msSPRProtectionUnit** object class to instances of the **msSPRProtectionGroup** object class. +- ITU-T G.774.9: **protectionCoordinator-managedElement** +This name binding is reused for naming instances of the **sdhMSSPRProtectionCoordinator** object class to instances of the **managedElement** object class. + +# 13 Supporting ASN.1 Productions + +``` +SDHMSSPRASN1 {itu(0) recommendation(0) g(7) g774(774) hyphen(127) msspr(10) +informationModel(0) asn1Module(2) sdhmsspr(0) } +DEFINITIONS IMPLICIT TAGS ::= +BEGIN +-- EXPORTS everything -- +IMPORTS +RelativeDistinguishedName, RDNSequence +FROM InformationFramework {joint-iso-ccitt ds(5) modules(1) +informationFramework(1)} +ObjectInstance +FROM CMIP-1 { joint-iso-ccitt ms(9) cmip(1) modules(0) protocol(3) } +ManagementExtension, ProbableCause +FROM Attribute-ASN1Module { joint-iso-ccitt ms(9) smi(3) part2(2) asn1Module(2) 1 +} +NameType, PointerOrNull +FROM ASN1DefinedTypesModule { itu(0) recommendation(0) m(13) gnm(3100) +informationModel(0) asn1Modules(2) asn1DefinedTypesModule(0) } +AutoSwitchReason, booleanTrueDefault, FromAndToProtectionUnit, +ProtectionGroupType, RequestSource, SDHMSResourcePointer, SwitchStatus +FROM SDHProtASN1 { itu(0) recommendation(0) g(7) g774(774) hyphen(127) prot(03) +informationModel(0) asn1Module(2) sdhmsp(0) }; +sdhMSSPR OBJECT IDENTIFIER ::= { itu(0) recommendation(0) g(7) g774(774) +hyphen(127) msspr(10) informationModel(0) } +g774-10MObjectClass OBJECT IDENTIFIER ::= { sdhMSSPR managedObjectClass(3) } +g774-10Attribute OBJECT IDENTIFIER ::= { sdhMSSPR attribute(7) } +g774-10Action OBJECT IDENTIFIER ::= { sdhMSSPR action(9) } +g774-10NameBinding OBJECT IDENTIFIER ::= { sdhMSSPR nameBinding(6) } +g774-10Parameter OBJECT IDENTIFIER ::= { sdhMSSPR parameter(5) } +g774-10Package OBJECT IDENTIFIER ::= { sdhMSSPR package(4) } +g774-10StandardSpecificExtension OBJECT IDENTIFIER ::= { sdhMSSPR +standardSpecificExtension(0) } +-- The following value assignments are for the Protection Criteria in the +-- context of SDH. +-- These values shall always be assigned by this Recommendation in the context +-- of SDH. +mssprProtectionCriteria OBJECT IDENTIFIER ::= {g774-10StandardSpecificExtension +0 } +mssprExcessiveErrorCriteria OBJECT IDENTIFIER ::= { mssprProtectionCriteria 1 } +msSPRProbableCause OBJECT IDENTIFIER ::= {g774-10StandardSpecificExtension 1} +msSPRDefaultKBytes ProbableCause ::= globalValue : { msSPRProbableCause 1} +msSPRInconsistentAPSCodes ProbableCause ::= globalValue : { msSPRProbableCause 2} +msSPRNodeIdMismatch ProbableCause ::= globalValue : { msSPRProbableCause 3} +msSPRImproperAPSCodes ProbableCause ::= globalValue : { msSPRProbableCause 4} +msSPRApsChannelProcessingFailure ProbableCause ::= +globalValue : { msSPRProbableCause 5} +--default/initial value definitions +MSSPRProtectionGroupType ::= ProtectionGroupType (colon) +--supporting productions +BooleanType ::= BOOLEAN +ChangeSPRConfigInfo ::= SET OF CHOICE { + twoFiberToFourFiber SEQUENCE { + eastTPProtecting ObjectInstance, + westTPProtecting ObjectInstance, + spanSwitchOption CHOICE { + traditional WaitToRestoreSpan, + enhanced EnhancedWaitToRestoreSpan }}, + fourFiberToTwoFiber [0] NULL, + nutConfig [1] NutConfig, + ripConfig [2] RipConfig, + extraTrafficConfig [3] ExtraTrafficConfig +} +``` + +``` + +CurrentSquelchingList ::= SET OF SEQUENCE { + squelchedTP ObjectInstance, + associatedXC CHOICE { + squelchedXC RelativeDistinguishedName, + hardwired [0] NULL}} + +DirectionTable ::= SEQUENCE OF SEQUENCE { + westTP RDNSequence, + eastTP RDNSequence } + +EnhancedWaitToRestoreSpan ::= SEQUENCE { + wtrSpanEast INTEGER, + wtrSpanWest INTEGER } + +ExtraTrafficConfig ::= ENUMERATED { + noExtraTraffic (0), + extraTraffic (1), + extraTrafficWithRestoration (2) } + +LinkInfo ::= SEQUENCE { + localNEId ObjectInstance, + localPortId PointerOrNull, + remoteNEId ObjectInstance, + remotePortId PointerOrNull } + -- portId points to the service (preferred) msTPP; Null for Open Ring + +Map ::= SEQUENCE OF SEQUENCE { + nodeIdNumber INTEGER(0 .. 15), + linkInfo LinkInfo OPTIONAL} -- needed for two-node closed + ring + +MSSPRConfigurationError ::= ENUMERATED { + extraTrafficNotSupported (0), + manualProvisioningNotSupported (1), + nutNotSupported (2), + ringTypeNotSupported (3), + ripNotSupported (4), + duplicatedUnreliable (5), + ePdTPNotAvailable (6), -- east protected TP + ePgTPNotAvailable (7), -- east protecting TP + wPdTPNotAvailable (8), -- west protected TP + wPgTPNotAvailable (9), -- west protecting TP + invalidWTRTime (10) } + +MSSPRProtectionGroupConfigInfo ::= SEQUENCE { + directionTableDirectionTable, + extraTrafficConfig ExtraTrafficConfig OPTIONAL, + nodeNumber NodeOrNull, + nutConfig NutConfig OPTIONAL, + ringId RingId, + ringMap [0] Map OPTIONAL, + ringType [1] RingType, + ripConfig RipConfig OPTIONAL } + +MSSPRProtectionStatus ::= SET OF CHOICE { + noRequest [0] NULL, + manualSwitch [1] SEQUENCE { + requestSource [0] RequestSource OPTIONAL, + switchStatus [1] SwitchStatus, + relatedChannel FromAndToProtectionUnit OPTIONAL, + switchType [2] RingOrSpan}, + autoSwitch [2] SEQUENCE { + requestSource [0] RequestSource OPTIONAL, + switchStatus [1] SwitchStatus, + relatedChannel FromAndToProtectionUnit OPTIONAL, + autoSwitchReason [2] AutoSwitchReason, + switchType [3] RingOrSpan }, + forcedSwitch [3] SEQUENCE { + requestSource [0] RequestSource OPTIONAL, + switchStatus [1] SwitchStatus, + +``` + +``` + + relatedChannel FromAndToProtectionUnit OPTIONAL, + switchType [2] RingOrSpan}, +lockout [4] SEQUENCE { + requestSource [0] RequestSource OPTIONAL, + switchStatus [1] SwitchStatus, + switchType [2] RingOrSpan}, +releaseFailed [6] NULL, +protectionFailCond [7] ENUMERATED { + inconsistentApsCode (0), + nodeIdMismatch (1), + improperApsCode (2), + defaultKBytes (3), + signalDegradeProtect (4), + signalFailProtect (5)}, +passThrough [8] ENUMERATED { + full (0), + kByte (1)}} +MSSPRProtectionStatusParameter ::= SET OF SEQUENCE { + protectionUnit ObjectInstance, + oldProtectionStatus MSSPRProtectionStatus, + newProtectionStatus MSSPRProtectionStatus} +NodeNumber ::= INTEGER(0 .. 15) +NodeOrNull ::= CHOICE { + nodeNumber NodeNumber, + null NULL} +NutChannelList ::= SET OF SEQUENCE { + channel INTEGER, + affectedTraffic ENUMERATED { + workingOnly (0), + workingAndProtecting (1) }, + ringSwitchUnavailable UnavailableSide, + spanSwitchUnavailable UnavailableSide OPTIONAL } +NutConfig ::= CHOICE { + nutOff NULL, + nutOn NutChannelList } +RingId ::= PrintableString +RingOrSpan ::= ENUMERATED { + ring (0), + span (1)} +RingType ::= SEQUENCE { + application SPRingApplication, + fibers CHOICE { + twoFiber NULL, + fourFiber WaitToRestoreSpan, + enhancedFourFiber EnhancedWaitToRestoreSpan }} +RipChannelList ::= SET OF SEQUENCE { + channel INTEGER, + ripInformation RipTableEntry} +RipConfig ::= CHOICE { + ripOff NULL, + ripOn RipChannelList } +RipInformation ::= SEQUENCE { + primaryNode NodeOrNull, -- primary interconnection node + terminatingNode NodeOrNull } -- node where the traffic is added/dropped +RipTableEntry ::= SEQUENCE { + inEast RipInformation, + outEast RipInformation, + inWest RipInformation, + outWest RipInformation } +SPRingApplication ::= ENUMERATED { + classic(1), + transoceanic(2) } + +``` + +``` + +SquelchTableChannel ::= SEQUENCE { + aNode NodeOrNull, -- entry node of circuit + zNode NodeOrNull, -- exit node of circuit + loAccess BOOLEAN, -- TRUE implies low order access is present + concatenated CHOICE { + firstChannel INTEGER, -- number of concatenated channels + subsequentChannels NULL } OPTIONAL} +SquelchTableEntry ::= SEQUENCE { + inEast SquelchTableChannel, + outEast SquelchTableChannel, + inWest SquelchTableChannel, + outWest SquelchTableChannel, + additionalInfo SET OF ManagementExtension OPTIONAL } +True ::= BOOLEAN(TRUE) +UnavailableSide ::= SEQUENCE { + switchUnavailableEast BOOLEAN, + switchUnavailableWest BOOLEAN } +UpdateRIPFailed ::= CHOICE { + unknown [0] NULL, + nodeNotInRing [1] INTEGER(0..15), + channelNotAvailableForRIP [2] NULL } +UpdateRIPTableInfo ::= SEQUENCE OF SEQUENCE { + auChannelNumber INTEGER, + ripTableEntry RipTableEntry } +UpdateRIPTableReply ::= SEQUENCE OF CHOICE { + failed UpdateRIPFailed, + success SEQUENCE { + oldRipTable RipTableEntry, + newRipTable RipTableEntry } } +-- the ith entry in the reply corresponds to the ith entry in the information +syntax +UpdateSquelchFailed ::= CHOICE { + unknown [0] NULL, + nodeNotInRing [1] INTEGER(0..15), + concatenatedChannel [2] INTEGER, + loAccessNotSupported [3] NULL } +UpdateSquelchTableInfo ::= SEQUENCE OF SEQUENCE { + auChannelNumber INTEGER, + squelchTableEntry SquelchTableEntry } +UpdateSquelchTableReply ::= SEQUENCE OF CHOICE { + failed UpdateSquelchFailed, + success SEQUENCE { + oldSquelchTableEntry SquelchTableEntry, + newSquelchTableEntry SquelchTableEntry } } +-- the ith entry in the reply corresponds to the ith entry in the information +syntax +WaitToRestoreSpan ::= INTEGER +END + +``` + +# APPENDIX I + +## Inheritance and containment diagrams + +![Inheritance tree of MS shared protection ring diagram showing various network elements like sPRingManager, fabric, protectionUnit, and protectionGroupR1 under a 'top' node.](cfb98c691c1af5befe32ff9442eea511_img.jpg) + +This diagram illustrates the inheritance tree for the MS shared protection ring. At the top level is a box labeled 'top'. Below it, several boxes are connected via vertical lines, with some labeled with standards: 'X.721', 'M.3100', 'G.774.3', and 'G.774.3'. The elements include: + + +- sPRingManager** +- fabric** (labeled M.3100) +- protectionUnit** (labeled G.774.3) +- protectionGroupR1** (labeled G.774.3) +- Sub-elements of **protectionUnit**: **msSPR ProtectionUnit**, **connection Protection** (labeled G.774.4) +- Sub-elements of **protectionGroupR1**: **msSPR ProtectionGroup**, **connection ProtectionGroupR1** (labeled G.774.4) +- Other elements on the left: **squelchTable**, **auSquelchTable**, **nutTable**, **ripTable** +- Sub-element of **fabric**: **snep Fabric** (labeled G.774.4) + + A reference code 'T1541860-00' is located in the bottom right corner. + +Inheritance tree of MS shared protection ring diagram showing various network elements like sPRingManager, fabric, protectionUnit, and protectionGroupR1 under a 'top' node. + +Figure I.1/G.774.10 – Inheritance tree of MS shared protection ring + +![Containment tree of MS shared protection ring diagram showing elements like snep Fabric, sPRingManager, and msSPR ProtectionGroup under an 'sdhNE' node, with a legend for name bindings.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +This diagram illustrates the containment tree for the MS shared protection ring. At the top level is a box labeled 'sdhNE' (labeled G.774). Below it, elements are connected via vertical lines, with some labeled with standards: 'M.3100', 'G.774.3', and 'G.774.4'. The elements include: + + +- Sncp Fabric** (labeled M.3100) +- sPRingManager** +- msSPR ProtectionGroup** (labeled G.774.3) +- Sub-elements of **Sncp Fabric**: **sdhMSSPR ProtectionCoordinator**, **connection ProtectionGroupR1** (labeled G.774.4) +- Sub-element of **connection ProtectionGroupR1**: **connection Protection** (labeled G.774.4) +- Sub-elements of **sPRingManager**: **squelchTable**, **ripTable**, **nutTable** +- Sub-element of **squelchTable**: **auSquelchTable** +- Sub-element of **msSPR ProtectionGroup**: **msSPR ProtectionUnit** (labeled G.774.3) + + A legend at the bottom indicates: + + +- Solid arrow: Name Bindings defined in this Recommendation +- Dashed arrow: Name Bindings defined in other Recommendation + + A reference code 'T1541870-00' is located in the bottom right corner. + +Containment tree of MS shared protection ring diagram showing elements like snep Fabric, sPRingManager, and msSPR ProtectionGroup under an 'sdhNE' node, with a legend for name bindings. + +Figure I.2/G.774.10 – Containment tree of MS shared protection ring + +# APPENDIX II + +## Illustrations of MS SPR configuration + +This appendix provides informative illustration of the MS SPR information model. + +In an MS SPR NE, there will be one instance of the **sdhMSSPRProtectionCoordinator** object. In the MS SPR architecture, it is possible that a NE may participate in multiple protection rings. For each MS SPR ring, there is one instance of each of the following object classes: **sPRingManager**, **msSPRProtectionGroup**, **squelchTable**, **nutTable**, and **ripTable**. The association between the **sPRingManager** and the **msSPRProtectionGroup** objects is indicated by a pointer attribute "**protectionGroupPointer**" in the **sPRingManager** object. The **squelchTable**, **nutTable**, and **ripTable** objects are contained in **sPRingManager**. + +A single instance of the **msSPRProtectionGroup** (PG) object contains four instances of the **msSPRProtectionUnit** (PU) object in both two-fiber and four-fiber MS SPR nodes. There are two protected PUs and two protecting PUs. These are depicted in Figures II.1 and II.2. The functionality of these object classes is similar to those of SDH MS protection (ITU-T G.774.3). In the two-fiber case, only ring switching is available. Therefore, a protected PU is mated with a protection PU on the opposite side of the ring node (indicated with the **ringPU** attribute of the PUs). In the four-fiber case, the PUs also have a **spanPU** attribute which points to PU on the same side of the ring node for span switching that are available with four-fiber MS SPR. + +![Diagram of a Two-fiber MS SPR ring node. The diagram shows an sdhNE containing an msSPRProtectionGroup. Inside the group are two symmetrical sections. Each section has an 'ms TTP Bi' block at the top and 'UP CTP Bi' blocks. Within the msSPRProtectionGroup, there are 'PU' (msSPRProtectionUnit) blocks, 'aug Bi' blocks (labeled 1 and 8), and 'P TTP Bi' blocks. A central 'sncpFabric' (box with an X) is positioned between the two sections. Pointers include: D/UCP (downstream/upstream connectivity pointers) between ms TTP Bi and PU; UR (unreliable resource pointers) and CP (cross-connection object pointers) between UP CTP Bi and PU; RR (reliable resource pointers) between PU and aug Bi; and ringPU pointers that cross-connect the two PUs. The RR pointers from the lower PUs point to (NULL).](e451401f8fa77b466f401d5fce15b26c_img.jpg) + +Diagram of a Two-fiber MS SPR ring node. The diagram shows an sdhNE containing an msSPRProtectionGroup. Inside the group are two symmetrical sections. Each section has an 'ms TTP Bi' block at the top and 'UP CTP Bi' blocks. Within the msSPRProtectionGroup, there are 'PU' (msSPRProtectionUnit) blocks, 'aug Bi' blocks (labeled 1 and 8), and 'P TTP Bi' blocks. A central 'sncpFabric' (box with an X) is positioned between the two sections. Pointers include: D/UCP (downstream/upstream connectivity pointers) between ms TTP Bi and PU; UR (unreliable resource pointers) and CP (cross-connection object pointers) between UP CTP Bi and PU; RR (reliable resource pointers) between PU and aug Bi; and ringPU pointers that cross-connect the two PUs. The RR pointers from the lower PUs point to (NULL). + +T1541880-00 + +![sncpFabric symbol: a box with an X](1142ba0197b158bb198186fe8baccc32_img.jpg) + +| | | | | +|---------|-----------------------------|--------------|-----------------------------------------------------------------------| +| | sncpFabric | RR | reliableResourcePointer | +| PU | msSPRProtectionUnit | UR | unreliableResourcePointer | +| UPCTPBi | unprotectedCTPBidirectional | CP | crossConnectionObjectPointer | +| PTTPBi | protectedTTPBidirectional | D/UCP | downstreamConnectivityPointer (or upstreamConnectivityPointer) | + +sncpFabric symbol: a box with an X + +**Figure II.1/G.774.10 – Two-fiber MS SPR ring node** + + + +![Diagram of AU3 service selector at 2-fiber MS SPR primary node. The diagram shows a central 'sdhNE' box containing 'snepFabric' and 'UCP' (NULL). On the left, an 'STM-16' interface connects to a stack of 'augBi' objects (1 and 8), which in turn connect to 'au3 CPTBi' objects. These 'au3 CPTBi' objects connect to 'CP Bi - Pd' and 'CP Bi - Pg' objects within the 'UCP' box. The 'UCP' box also contains 'CPG', 'RR', and 'D/UCP' pointers. Below the 'UCP' box is an 'msTTPBi' box containing three 'au3 CPTBi' objects and an 'augBi' object. An 'STM-1' interface is shown at the bottom. Arrows indicate various pointers: 'DCP', 'CP', 'RR', 'UR', 'D/UCP', and '(NULL)'.](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +CPG connectionProtectionGroupR1 + CP Bi-Pd connectionProtection (protected) + CP Bi-Pg connectionProtection (protecting) + RR reliableResourcePointer + UR unreliableResourcePointer + CP crossConnectionObjectPointer + D/UCP downstreamConnectivityPointer (or upstreamConnectivityPointer) + +Diagram of AU3 service selector at 2-fiber MS SPR primary node. The diagram shows a central 'sdhNE' box containing 'snepFabric' and 'UCP' (NULL). On the left, an 'STM-16' interface connects to a stack of 'augBi' objects (1 and 8), which in turn connect to 'au3 CPTBi' objects. These 'au3 CPTBi' objects connect to 'CP Bi - Pd' and 'CP Bi - Pg' objects within the 'UCP' box. The 'UCP' box also contains 'CPG', 'RR', and 'D/UCP' pointers. Below the 'UCP' box is an 'msTTPBi' box containing three 'au3 CPTBi' objects and an 'augBi' object. An 'STM-1' interface is shown at the bottom. Arrows indicate various pointers: 'DCP', 'CP', 'RR', 'UR', 'D/UCP', and '(NULL)'. + +**Figure II.3/G.774.10 – AU3 service selector at 2-fiber MS SPR primary node** + +The **squelchTable**, **auSquelchTable**, and **sPRingManager** object classes represent the ring configuration information that an MS SPR node must maintain in order to communicate with other ring nodes on the APS signalling channel and to properly perform ring (and span) protection switches and squelching. The **sPRingManager** object describes the identity and relative order of the nodes, and the directionality of the TTPs around the ring, which must be common to all nodes on the ring. The **squelchTable** and **auSquelchTable** objects provide squelch-related information for each ring channel (AU) processed by the ring node. Each instance of the **auSquelchTable** object includes the following information for a particular ring channel: + +- entrance and exit node identifiers for the channel; +- an indication if the channel is part of a concatenated ring channel; +- an indication if lower-order VC access is provided on that channel in the ring. + +The above information is available for each direction of each channel on the east- and west-side of the node. Therefore it is able to reflect various connection configurations, such as + +- a bidirectional pass-through; +- an unidirection east to west pass-through, an unidirectional add to east and unidirectional drop from west; +- a bidirectional add/drop on the east side and a bidirectional add/drop on the west side; +- two unidirectional pass-through with different **aNode** and **zNode**. + +The **updateSquelchTable** action of the **squelchTable** object is used for updating the contents of the squelch information of a node. + +If there are multiple links between two nodes (e.g. in the case of a two-node closed ring), in order to unambiguously discover or provision the ring topology, there is a need to indicate the link termination (i.e. port Id) information in the ring map. The syntax of the **ringMap** attribute provides an optional field for such indication. + +The **nutTable** object classes is defined to support non-preemptible channel provisioning. As defined in ITU-T G.841, non-preemptible unprotected traffic (NUT) is unprotected traffic that is carried on channels with the MS SPR automatic protection switching mechanism disabled for certain high order (HO) VC channels (i.e. working channels and their corresponding protection channels). Support of non-preemptible channel provisioning requires that a NUT table be present at each node on the MS SPR. + +The **ripTable** object class is defined to support ring interworking on protection. As defined in ITU-T G.842, ring interworking on protection (RIP) is a mechanism to help alleviate bandwidth exhaustion between the primary and secondary interconnection nodes in a dual-homed interconnection scheme by using protection bandwidth for the secondary circuit. Support of ring interworking on protection requires that a RIP table be present at each secondary interconnection node on the MS SPR. + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/G/T-REC-G.774.6-200102-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.774.6-200102-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02618e1c9d69bb72ac37b909dab893cd21430aee --- /dev/null +++ b/marked/G/T-REC-G.774.6-200102-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6df3aeb5704678ae54ee7c4613ee4fb55ab0ed7fa77543d0714802f3cb0be873 +size 8357 diff --git a/marked/G/T-REC-G.774.6-200102-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/G/T-REC-G.774.6-200102-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca3d79257c41ac3241d1916174eb264db0de9564 --- /dev/null +++ b/marked/G/T-REC-G.774.6-200102-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78b00492d9d3c5ffb9d4492d1a97f960ca15961687d156ca8d9cfe95f445925e +size 70849 diff --git a/marked/G/T-REC-G.774.6-200102-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg b/marked/G/T-REC-G.774.6-200102-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c81a8317eb3add6c4f796c747dd1c28705b1abd --- /dev/null +++ b/marked/G/T-REC-G.774.6-200102-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a84449bc77bc8f2432b0ee01f5c244089328bee829f0599fbcbba5d5e827c19b +size 85342 diff --git a/marked/G/T-REC-G.774.6-200102-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/G/T-REC-G.774.6-200102-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..729b891e1dc4be9890520819eeadbbcb271c8f82 --- /dev/null +++ b/marked/G/T-REC-G.774.6-200102-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:730b6850818a60cd41cbbb1c0ebe8a974fbc38b4d7bc9bfc07e62b60b2983c2e +size 111502 diff --git a/marked/G/T-REC-G.774.6-200102-I_PDF-E/b44f89b176c971c7dd264c07bfef2c2a_img.jpg b/marked/G/T-REC-G.774.6-200102-I_PDF-E/b44f89b176c971c7dd264c07bfef2c2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40259ab925751fdfa74142296cd056b8090d1add --- /dev/null +++ b/marked/G/T-REC-G.774.6-200102-I_PDF-E/b44f89b176c971c7dd264c07bfef2c2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:393617c226787ea86e808c83902afe63852e409ed00b519602fa1b365d948917 +size 48726 diff --git a/marked/G/T-REC-G.774.6-200102-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg b/marked/G/T-REC-G.774.6-200102-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47cdad88d1abf8b8183546a289237596ff4eb59d --- /dev/null +++ b/marked/G/T-REC-G.774.6-200102-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:057afc3f34216f7d3d64f68d9bc2e85b01a6d31835216a21777416e000d37e62 +size 114439 diff --git a/marked/G/T-REC-G.774.6-200102-I_PDF-E/raw.md b/marked/G/T-REC-G.774.6-200102-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3778da35314bceadea5e1e30162f09d48b7d4790 --- /dev/null +++ b/marked/G/T-REC-G.774.6-200102-I_PDF-E/raw.md @@ -0,0 +1,2836 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**G.774.6** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(02/2001) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital terminal equipments – Operations, administration +and maintenance features of transmission equipment + +--- + +**Synchronous Digital Hierarchy (SDH) – +Unidirectional performance monitoring for the +network element view** + +ITU-T Recommendation G.774.6 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TESTING EQUIPMENTS | G.500–G.599 | +| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 | +| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 | +| General | G.700–G.709 | +| Coding of analogue signals by pulse code modulation | G.710–G.719 | +| Coding of analogue signals by methods other than PCM | G.720–G.729 | +| Principal characteristics of primary multiplex equipment | G.730–G.739 | +| Principal characteristics of second order multiplex equipment | G.740–G.749 | +| Principal characteristics of higher order multiplex equipment | G.750–G.759 | +| Principal characteristics of transcoder and digital multiplication equipment | G.760–G.769 | +| Operations, administration and maintenance features of transmission equipment | G.770–G.779 | +| Principal characteristics of multiplexing equipment for the synchronous digital hierarchy | G.780–G.789 | +| Other terminal equipment | G.790–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Synchronous Digital Hierarchy (SDH) – Unidirectional performance monitoring for the network element view** + +## **Summary** + +This Recommendation provides an information model for the performance monitoring of Synchronous Digital Hierarchy (SDH) network. This model describes the managed object classes and their properties for the performance monitoring function of unidirectional paths and sections, as defined in ITU-T G.784 and as related to SDH network elements. These objects are useful to describe information exchanged across interfaces defined in ITU-T M.3010 Telecommunications Management Network (TMN) architecture for the management of the performance monitoring function. + +| History | | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Issue | Notes | +| 2001 | First revision incorporated the changes documented in the Implementors Guide. The rsCurrentData , rsCurrentDataTR , rsHistoryData , msAdaptationCurrentData , and msAdaptationHistoryData were moved from ITU-T G.774.1 to this Recommendation for unidirectional performance monitoring. | +| 4/1997 | Initial version of the Recommendation. | + +## **Source** + +ITU-T Recommendation G.774.6 was revised by ITU-T Study Group 15 (2001-2004) and approved under the WTSA Resolution 1 procedure on 9 February 2001. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +# CONTENTS + +###### Page + +| | | | +|------|---------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References ..... | 1 | +| 3 | Terms and Definitions ..... | 3 | +| 4 | Abbreviations ..... | 3 | +| 5 | Performance management model ..... | 4 | +| 5.1 | Overview ..... | 4 | +| 5.2 | Requirements ..... | 4 | +| 5.3 | Model overview ..... | 6 | +| 5.4 | Other modelling considerations ..... | 6 | +| 6 | Managed object classes definitions ..... | 6 | +| 6.1 | SDH current data unidirectional ..... | 7 | +| 6.2 | Regenerator section current data ..... | 8 | +| 6.3 | Regenerator section current data threshold reset ..... | 8 | +| 6.4 | Multiplex section current data near-end ..... | 9 | +| 6.5 | Multiplex section current data near-end threshold reset ..... | 10 | +| 6.6 | Path termination current data near-end ..... | 10 | +| 6.7 | Path termination current data near-end threshold reset ..... | 11 | +| 6.8 | Multiplex section adaptation current data ..... | 11 | +| 6.9 | Multiplex section current data far-end ..... | 12 | +| 6.10 | Multiplex section current data far-end threshold reset ..... | 12 | +| 6.11 | Path termination current data far-end ..... | 13 | +| 6.12 | Path termination current data far-end threshold reset ..... | 14 | +| 6.13 | Regenerator section history data ..... | 14 | +| 6.14 | Multiplex section history data near-end ..... | 15 | +| 6.15 | Multiplex section adaptation history data ..... | 15 | +| 6.16 | Path termination history data near-end ..... | 15 | +| 6.17 | Multiplex section history data far-end ..... | 16 | +| 6.18 | Path termination history data far-end ..... | 16 | +| 7 | Package definitions ..... | 17 | +| 7.1 | Near-end unavailable second current data package ..... | 17 | +| 7.2 | Far-end unavailable second current data package ..... | 17 | +| 7.3 | Near-end unavailable second history data package ..... | 18 | +| 7.4 | Far-end unavailable second history data package ..... | 18 | + +| | Page | | +|------|-------------------------------------------------------------|----| +| 7.5 | Failure counts near-end package ..... | 18 | +| 7.6 | Errored seconds type A near-end package..... | 18 | +| 7.7 | Errored seconds type B near-end package..... | 19 | +| 7.8 | Failure counts far-end package ..... | 19 | +| 7.9 | Errored seconds type A far-end package ..... | 19 | +| 7.10 | Errored seconds type B far-end package ..... | 19 | +| 7.11 | Failure counts near-end history data package..... | 19 | +| 7.12 | Errored seconds type A near-end history data package..... | 20 | +| 7.13 | Errored seconds type B near-end history data package..... | 20 | +| 7.14 | Failure counts far-end history data package ..... | 20 | +| 7.15 | Errored seconds type A far-end history data package..... | 20 | +| 7.16 | Errored seconds type B far-end history data package ..... | 21 | +| 7.17 | Out of frame second current data package..... | 21 | +| 7.18 | Out of frame second history data package..... | 21 | +| 8 | Attributes definitions ..... | 21 | +| 8.1 | Near-end unavailable seconds..... | 21 | +| 8.2 | Far-end unavailable seconds ..... | 22 | +| 8.3 | Failure counts near-end..... | 22 | +| 8.4 | Errored seconds type A near-end ..... | 22 | +| 8.5 | Errored seconds type B near-end ..... | 22 | +| 8.6 | Failure counts far-end..... | 22 | +| 8.7 | Errored seconds type A far-end..... | 23 | +| 8.8 | Errored seconds type B far-end..... | 23 | +| 8.9 | Out of frame second ..... | 23 | +| 8.10 | Pointer justification count high ..... | 23 | +| 8.11 | Pointer justification count low ..... | 23 | +| 9 | Actions..... | 24 | +| 10 | Notifications..... | 24 | +| 11 | Parameters..... | 24 | +| 12 | Name binding definitions..... | 24 | +| 12.1 | MS current data near-end – MS TTP sink ..... | 24 | +| 12.2 | MS current data near-end threshold reset – MS TTP sink..... | 24 | +| 12.3 | RS current data – RS TTP sink ..... | 24 | +| 12.4 | RS current data threshold reset – RS TTP sink..... | 25 | +| 12.5 | MS current data far-end – MS TTP sink ..... | 25 | + +| | Page | +|--------------------------------------------------------------------------------------|-------------| +| 12.6 MS current data far-end threshold reset – MS TTP sink ..... | 25 | +| 12.7 Path termination current data near-end – AU4 supervised CTP SinkR1 ..... | 25 | +| 12.8 Path termination current data near-end – AU3 supervised CTP SinkR1 ..... | 26 | +| 12.9 Path termination current data near-end – TU3 supervised CTP SinkR1 ..... | 26 | +| 12.10 Path termination current data near-end – TU2 supervised CTP SinkR1 ..... | 26 | +| 12.11 Path termination current data near-end – TU12 supervised CTP SinkR1 ..... | 26 | +| 12.12 Path termination current data near-end – TU11 supervised CTP SinkR1 ..... | 27 | +| 12.13 Path termination current data far-end – AU4 supervised CTP SinkR1 ..... | 27 | +| 12.14 Path termination current data far-end – AU3 supervised CTP SinkR1 ..... | 27 | +| 12.15 Path termination current data far-end – TU3 supervised CTP SinkR1 ..... | 27 | +| 12.16 Path termination current data far-end – TU2 supervised CTP SinkR1 ..... | 28 | +| 12.17 Path termination current data far-end – TU12 supervised CTP SinkR1 ..... | 28 | +| 12.18 Path termination current data far-end – TU11 supervised CTP SinkR1 ..... | 28 | +| 12.19 Path termination current data near-end TR – AU4 supervised CTP SinkR1 ..... | 28 | +| 12.20 Path termination current data near-end TR – AU3 supervised CTP SinkR1 ..... | 29 | +| 12.21 Path termination current data near-end TR – TU3 supervised CTP SinkR1 ..... | 29 | +| 12.22 Path termination current data near-end TR – TU2 supervised CTP SinkR1 ..... | 29 | +| 12.23 Path termination current data near-end TR – TU12 supervised CTP SinkR1 ..... | 29 | +| 12.24 Path termination current data near-end TR – TU11 supervised CTP SinkR1 ..... | 30 | +| 12.25 Path termination current data far-end TR – AU4 supervised CTP SinkR1 ..... | 30 | +| 12.26 Path termination current data far-end TR – AU3 supervised CTP SinkR1 ..... | 30 | +| 12.27 Path termination current data far-end TR – TU3 supervised CTP SinkR1 ..... | 30 | +| 12.28 Path termination current data far-end TR – TU2 supervised CTP SinkR1 ..... | 31 | +| 12.29 Path termination current data far-end TR – TU12 supervised CTP SinkR1 ..... | 31 | +| 12.30 Path Termination current data far-end TR – TU11 supervised CTP SinkR1 ..... | 31 | +| 12.31 Path termination current data near-end – VC4 TTP SinkR1 ..... | 31 | +| 12.32 Path termination current data near-end – VC3 TTP SinkR1 ..... | 32 | +| 12.33 Path termination current data near-end – VC2 TTP SinkR1 ..... | 32 | +| 12.34 Path termination current data near-end – VC12 TTP SinkR1 ..... | 32 | +| 12.35 Path termination current data near-end – VC11 TTP SinkR1 ..... | 32 | +| 12.36 Path termination current data near-end threshold reset – VC4 TTP SinkR1 ..... | 33 | +| 12.37 Path termination current data near-end threshold reset – VC3 TTP SinkR1 ..... | 33 | +| 12.38 Path termination current data near-end threshold reset – VC2 TTP SinkR1 ..... | 33 | +| 12.39 Path termination current data near-end threshold reset – VC12 TTP SinkR1 ..... | 33 | +| 12.40 Path termination current data near-end threshold reset – VC11 TTP SinkR1 ..... | 34 | +| 12.41 Path termination current data far-end – VC4 TTP SinkR1 ..... | 34 | + +| | Page | +|-------------------------------------------------------------------------------------|-------------| +| 12.42 Path termination current data far-end – VC3 TTP SinkR1 ..... | 34 | +| 12.43 Path termination current data far-end – VC2 TTP SinkR1 ..... | 34 | +| 12.44 Path termination current data far-end – VC12 TTP SinkR1 ..... | 35 | +| 12.45 Path termination current data far-end – VC11 TTP SinkR1 ..... | 35 | +| 12.46 Path termination current data far-end threshold reset – VC4 TTP SinkR1 ..... | 35 | +| 12.47 Path termination current data far-end threshold reset – VC3 TTP SinkR1 ..... | 35 | +| 12.48 Path termination current data far-end threshold reset – VC2 TTP SinkR1 ..... | 36 | +| 12.49 Path termination current data far-end threshold reset – VC12 TTP SinkR1 ..... | 36 | +| 12.50 Path termination current data far-end threshold reset – VC11 TTP SinkR1 ..... | 36 | +| 12.51 MS adaptation current data – AU4 CTP source..... | 36 | +| 12.52 MS adaptation current data – AU3 CTP source..... | 37 | +| 13 Subordination rules..... | 37 | +| 14 Pointer constraints ..... | 37 | +| 15 Supporting ASN.1 productions ..... | 37 | +| Appendix I – Naming and inheritance diagrams ..... | 38 | + +# **Synchronous Digital Hierarchy (SDH) – Unidirectional performance monitoring for the network element view** + +# **1 Scope** + +SDH Performance Monitoring Functions are used to monitor specified performance events of specified Termination Points managed objects and to report these performance data, as well as Quality Of Service Alarms to its managing system according to a given schedule. + +ITU-T M.2120 defines maintenance of transport network, ITU-T G.784 defines the management of SDH-based network element. This Recommendation defines the object model based on ITU-T Q.822 according to the requirements described in ITU-T G.784 and ITU-T M.2120 with respect to unidirectional performance monitoring. This model uses generic mechanisms defined in ITU-T Q.822. The information model for bidirectional performance monitoring is covered by ITU-T G.774.1. This Recommendation reuses functionality of ITU-T G.774.1 wherever possible. + +## **Structure of this Recommendation** + +Clause 5.1 provides an overview of the unidirectional SDH performance monitoring information model. Clauses 6 to 15 describe the information model using the notation mechanisms defined in ITU-T X.722, Guidelines for the definition of managed objects. Clause 15 contains the syntax definitions of the information carried in the protocol using Abstract Syntax Notation One (ASN.1) defined in ITU-T X.680-X.683. Naming and inheritance are illustrated in Appendix I. + +## **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 G.707/Y.1322 (2000), *Network node interface for the synchronous digital hierarchy SDH*. +- ITU-T G.773 (1993), *Protocol suites for Q-interfaces for management of transmission systems*. +- ITU-T G.774 (2001), *Synchronous digital hierarchy (SDH) – Management information model for the network element view*. +- ITU-T G.783 (2000), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks*. +- ITU-T G.784 (1999), *Synchronous digital hierarchy (SDH) management*. +- ITU-T G.803 (2000), *Architecture of transport networks based on the synchronous digital hierarchy (SDH)*. +- ITU-T G.831 (2000), *Management capabilities of transport networks based on the synchronous digital hierarchy (SDH)*. + +- ITU-T G.958 (1994), *Digital line systems based on the synchronous digital hierarchy for use on optical fibre cables.* +- ITU-T M.60 (1993), *Maintenance terminology and definitions.* +- ITU-T M.2120 (2000), *PDH path, section and transmission system and SDH path and multiplex section fault detection and localization procedures.* +- ITU-T M.3010 (2000), *Principles for a telecommunication management network.* +- ITU-T M.3013 (2000), *Considerations for a telecommunications management network.* +- ITU-T M.3100 (1995), *Generic network information model.* +- ITU-T Q.811 (1997), *Lower layer protocol profiles for the Q3 and X interfaces.* +- ITU-T Q.812 (1997), *Upper layer protocol profiles for the Q3 and X interfaces.* +- ITU-T Q.822 (1994), *Stage 1, Stage 2 and Stage 3 description for the Q3-interface – Performance management.* +- ITU-T X.680 to X.683 (1997), *Information technology – Abstract Syntax Notation One (ASN.1).* +- ITU-T X.701 (1997), *Information technology – Open Systems Interconnection – Systems management overview.* +- ITU-T X.710 (1997), *Information technology – Open Systems Interconnection – Common management information service.* +- ITU-T X.711 (1997), *Information technology – Open Systems Interconnection – Common management information protocol: Specification.* +- ITU-T X.720 (1992), *Information technology – Open Systems Interconnection – Structure of Management Information: Management information model, plus Amd.1 (1995) and Cor.1 (1994).* +- ITU-T X.721 (1992), *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information, plus Cor.1 (1994), Cor.2 (1996), Cor.3 (1998), and Cor.4 (2000).* +- ITU-T X.722 (1992), *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects, plus Amd.1 (1995), Amd.2 (1997) and Cor.1 (1996).* +- ITU-T X.730 (1992), *Information technology – Open Systems Interconnection – Systems Management: Object management function, plus Amd.1 (1995) and Amd.1/Cor.1 (1996).* +- ITU-T X.731 (1992), *Information technology – Open Systems Interconnection – Systems Management: State management function, plus Amd.1 (1995), Cor.1 (1995) and Amd.1/Cor.1 (1996).* +- ITU-T X.733 (1992), *Information technology – Open Systems Interconnection – Systems Management: Alarm reporting function, plus Cor.1 (1994), Amd.1 (1995), Amd.1/Cor.1 (1996) and Cor.2 (1999).* +- ITU-T X.734 (1992), *Information technology – Open Systems Interconnection – Systems Management: Event report management function, plus Cor.1 (1994), Amd.1 (1995), Amd.1/Cor.1 (1996) and Cor.2 (1999).* +- ITU-T X.735 (1992), *Information technology – Open Systems Interconnection – Systems Management: Log control function, plus Amd.1 (1995) and Amd.1/Cor.1 (1996).* + +- ITU-T X.739 (1993), *Information technology – Open Systems Interconnection – Systems Management: Metric objects and attributes*. +- ANSI T1.231-1997, *Digital Hierarchy – Layer 1 in-Service Digital Transmission Performance Monitoring*. + +# 3 Terms and Definitions + +This Recommendation uses the terms and definitions defined in ITU-T G.774, ITU-T G.784 and ITU-T M.3100. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|------------------------------------------------| +| AIS | Alarm Indication Signal | +| BBE | Background Block Error | +| CSES | Consecutive Severely Errored Second | +| CTP | Connection Termination Point | +| EBER | Excessive Bit Error Ratio | +| ES | Errored Second | +| FEBBE | Far-End Background Block Error | +| FEEB | Far-End Errored Block | +| FEES | Far-End Errored Second | +| FESES | Far-End Severely Errored Second | +| ISO | International Organization for Standardization | +| ITU | International Telecommunication Union | +| LOF | Loss Of Frame | +| LOS | Loss Of Signal | +| MS | Multiplex Section | +| NCSES | Number of Consecutive Severely Errored Seconds | +| NE | Network Element | +| OS | Operations System | +| OSI | Open Systems Interconnection | +| Pkg | Package | +| QoS | Quality of Service | +| RDN | Relative Distinguished Name | +| RS | Regenerator Section | +| SDH | Synchronous Digital Hierarchy | +| SES | Severely Errored Second | +| SPI | Synchronous Physical Interface | +| STM-N | Synchronous Transport Module N | + +| | | +|-----|---------------------------------------| +| TMN | Telecommunications Management Network | +| TP | Termination Point | +| TR | Threshold Reset | +| TTP | Trail Termination Point | +| UAS | Unavailable Second | + +# 5 Performance management model + +### 5.1 Overview + +This clause provides Managed Objects required to support management of unidirectional performance monitoring in SDH Network Elements. + +This model defines subclasses of the generic **currentData** and **historyData** object classes from ITU-T Q.822 for each kind of monitoring point. For each type of monitoring point, two subclasses of **currentData** are defined. One is defined for either a 15-minute count or 1-day count period, and provides implicit clearing of threshold crossing alarms at the end of each granularity period. The other subclass is only relevant to 15-minute counting and performs explicit clearing of threshold alarms (Threshold Reset) at the end of a clear 15-minute period (refer to 2.3.4.2/M.2120). + +History information could either be collected as part of **historyData** instances or one of its subclasses or as an **eventRecord** or one of its subclasses contained in a log. Utilization of a log is not mandatory in this Recommendation. + +The threshold reset (TR) mechanism used in this Recommendation corresponds to the reset threshold report (RTR) of ITU-T G.784. + +## 5.2 Requirements + +The unidirectional SDH Performance Monitoring functions shall provide for: + +- the ability for a managing system to request the collection of the various Performance events relating to a given monitored entity for a given collection period; +- the ability for a managing system to suspend/resume the performance data collection for a given monitored entity (or set of entities); +- the ability for a managing system to instruct the NE to reset the performance monitoring counters for a given monitored entity (or set of entities); +- the scheduling of performance collection activity within specified time periods, for a given monitored entity (or set of entities); +- the ability for a managing system to request the performance monitoring counters for a given monitored entity (or set of entities); +- the ability for a managed system to send event reports to a managing system to notify the results of the performance data collection, at the end of the collection period; +- the ability for a managing system to instruct the NE to maintain Performance historical data for a specified duration, under specified conditions; +- the ability for a managing system to instruct the NE to remove specific Performance historical data; +- the ability for a managing system to instruct the NE to establish thresholding criteria for a given monitored entity (or set of entities); +- the ability for a managed system to send Quality Of Service Alarms upon threshold violation of a performance counter of a monitored entity. + +In order to fulfil the needs for maintenance-based collection and error performance-based collection, the following register sets are required for performance management evaluation: + +Starting and ending of a unidirectional unavailability period has to be reported by the instance of the managed object class that hold the 24-hour counts (near end or far end). + +#### **Maintenance-based collection for regenerator sections** + +The detailed definitions for the required parameters are included in ITU-T G.784. While the optional requirements are defined in either ITU-T G.784 or ANSI Standard T1.231. + +These requirements are covered by this Recommendation. + +Required Register sets are: + +- 17 (16+1) 15-minute near-end registers for BBE, ES, and SES; +- 2 (1+1) 24-hour near-end registers unidirectional for BBE, ES, and SES. + +Optional Register sets are: + +- 17 (16+1) 15-minute near-end registers for ESA, ESB, OFS (SEFS) and UAS; +- 2 (1+1) 24-hour near-end registers unidirectional for ESA, ESB, OFS (SEFS) and UAS. + +#### **Maintenance-based collection for paths and multiplex sections** + +The detailed definitions for the required parameters are included in ITU-T G.784, while the optional requirements are defined in either ITU-T G.784 or ANSI Standard T1.231. + +These requirements are covered by this Recommendation. + +Required Register sets are: + +- 17 (16+1) 15-minute near-end registers for BBE, ES, and SES; +- 17 (16+1) 15-minute far-end registers for BBE, ES, and SES; +- 2 (1+1) 24-hour near-end registers unidirectional for BBE, ES, and SES; +- 2 (1+1) 24-hour far-end registers unidirectional for BBE, ES, and SES. + +Optional Register sets are: + +- 17 (16+1) 15-minute near-end registers for ESA, ESB, FC and UAS; +- 17 (16+1) 15-minute far-end registers for ESA, ESB, FC and UAS; +- 2 (1+1) 24-hour near-end registers unidirectional for ESA, ESB, FC and UAS; +- 2 (1+1) 24-hour far-end registers unidirectional for ESA, ESB, FC and UAS. + +### **Error performance-based collection for paths only** + +These requirements are covered by ITU-T G.774.1. + +Register sets needed: + +- 2 (1+1) 24-hour near-end registers for BBE, ES and SES but bidirectional (ITU-T G.826) behaviour; +- 2 (1+1) 24-hour far-end registers for BBE, ES and SES but bidirectional (ITU-T G.826) behaviour; +- 2 (1+1) 24-hour bidirectional registers for UAS. + +## 5.3 Model overview + +ITU-T G.774.1 does not cover unidirectional unavailability of paths and multiplex sections, because the performance counters of the several **currentData** and **historyData** Managed Object Classes behave in the G.826 (the bidirectional) way. Therefore, it is necessary to have Managed Object Classes for the unidirectional performance monitoring feature to extend the G.774.1 information model. + +The unidirectional requirements are reflected in the Managed Object Classes defined in this Recommendation. + +In order to avoid redundant information duplication and unuseful implementation effort the CSES events are managed only in the **sdhCurrentData** subclass instances that have a 15-minute granularity period. + +### List of the managed object classes to fulfil the requirements for unidirectional performance monitoring + +**sdhCurrentDataUnidirectional** + +**msCurrentDataNearEnd, msCurrentDataNearEndTR** + +**pathTerminationCurrentDataNearEnd, pathTerminationCurrentDataNearEndTR** + +**msCurrentDataFarEnd, msCurrentDataFarEndTR** + +**pathTerminationCurrentDataFarEnd, pathTerminationCurrentDataFarEndTR** + +**msHistoryDataNearEnd** + +**pathTerminationHistoryDataNearEnd** + +**msHistoryDataFarEnd** + +**pathTerminationHistoryDataFarEnd** + +## 5.4 Other modelling considerations + +Since there is no far-end signalling in the regenerator section, the **rsCurrentData**, **rsCurrentDataTR** and **rsHistoryData** Managed Object Classes of ITU-T G.774.1 with the **uASCurrentDataPackage** and the **uASHistoryDataPackage** shall be used for near-end monitoring. + +No additional Managed Object Classes are needed to fulfil the requirement of monitoring 2 (1+1) 24-hour-registers for bidirectional performance data of paths. The ITU-T G.774.1 **pathTerminationCurrentData** with the **uASCurrentDataPackage** plus the **farEndCurrentDataPackage** and the **pathTerminationHistoryData** Managed Object Classes with the **uASHistoryDataPackage** plus the **farEndHistoryDataPackage** can be used. + +New **nameBindings** and new attributes (far-end unavailable seconds (**fEUAS**), near-end unavailable seconds (**nEUAS**)) are added wherever necessary. + +All the UAS counters are optional and therefore put in conditional packages. + +# 6 Managed object classes definitions + +NOTE – The following managed object classes have been moved to this Recommendation from the previous version of ITU-T G.774.1 for supporting unidirectional performance monitoring. + +### 6.1 SDH current data unidirectional + +``` +sdhCurrentDataUnidirectional MANAGED OBJECT CLASS +DERIVED FROM "Recommendation Q.822": currentData; +CHARACTERIZED BY + "Recommendation Q.822": zeroSuppressionPkg, + "Recommendation Q.822": thresholdPkg, +sdhCurrentDataUnidirectionalPackage PACKAGE + BEHAVIOUR sdhCurrentDataUnidirectionalBehaviour; + ATTRIBUTES + "Recommendation M.3100": currentProblemList GET;;; +CONDITIONAL PACKAGES + "Recommendation G.774.01": historyPackage PRESENT IF + "an instance does not support flexible assignment of the history length", + "Recommendation G.774.01": unavailableTimeAlarmPackage PRESENT IF + "starting and ending of unavailable period has to be reported and the + granularity period is 24 hours"; +REGISTERED AS {g774-6MObjectClass 1}; +``` + +``` +sdhCurrentDataUnidirectionalBehaviour BEHAVIOUR +DEFINED AS +``` + +"The **sdhCurrentDataUnidirectional** class is used to define generic characteristic for unidirectional SDH performance monitoring from which subclasses are defined in order to hold performance event counts for a specific monitoring point. Subclasses of this class are used in order to support performance monitoring of SDH trails at various layers as described in Recommendation G.805. The performance monitoring events ES, SES and BBE which are monitored by some of the subclasses of this subclass are defined in 4.1.1/G.826. The **granularityPeriod** attribute can only be assigned a value at creation time. + +This class can only contain one reference to an instance of the **thresholdData** object class in the **thresholdDataInstance** attribute. + +If a threshold is reached or crossed then the **currentProblemList** attribute shall indicate it with the probable cause Threshold crossed. Subclass of this class is used to monitor the near-end or far-end performance data of the trail. + +The unavailability conditions are kept separate for near-end and far-end monitoring. This means that only near-end conditions apply only to near-end unavailability and vice versa only far-end conditions apply only to far-end unavailability. + +For threshold reset subclasses of this object class the following rules apply: + +- No more than one QOS alarm shall be generated until there has been a 15-minute rectangular fixed window with less error count than the low error count threshold and no unavailable period exists. +- To provision the high and low threshold value, the **counterThresholdAttributList** attribute of the **Q.822-ThresholdDataInstance** is used. + +In this attribute all the thresholds (high and low) for each necessary counter are stored in a list. This means for example, that the high threshold for ES and the low threshold for ES are individually stored in the same list. It is up to the network element to recognize which is the high and which is the low one. + +If the **unavailableTimeAlarmPackage** is present and if an unavailable period starts, then a communication alarm shall be sent with a probable cause of Unavailable and the presence of this unavailable condition is indicated by the **currentProblemList** attribute. If an unavailable period is ending, then a communication alarm shall be sent with a probable cause of Unavailable and a + +severity of Cleared. An available condition is indicated by the absence of the unavailable condition in the current problem list. The unavailable condition has no effect on the **operationalState**. Each subclass of this class shall define the performance attributes required to hold the mandatory or optional performance events. These performance event counts are inhibited during unavailable time of its own direction (at the near end or at the far end). Attributes which are defined in a subclass of this class shall be included in history information using the **historyData**, or one of its subclasses, unless it is explicitly specified in the subclass of this class that a particular attribute be not included. Each subclass of this class shall indicate which subclass of the history data is used for history retention. The following conditional packages are not used in this class: **filterSuppressionPkg**, **observedManagedObjectPkg**. + +Concerning the subclasses of this class the following rule applies: + +If a subclass of this class has a granularity period of 15 minutes, it should be either an instance with the threshold reset functionality or an instance without this functionality instantiated (per termination point), but not both."; + +### 6.2 Regenerator section current data + +``` + +rsCurrentData MANAGED OBJECT CLASS +DERIVED FROM "Recommendation G.774.01":sdhCurrentData; +CHARACTERIZED BY +rsCurrentDataPackage PACKAGE + BEHAVIOUR rsCurrentDataBehaviour; + ATTRIBUTES + "Recommendation X.739": granularityPeriod REQUIRED VALUES + SDHPMASN1.SDHGranularityPeriod, + "Recommendation G.774.01":bBE REPLACE-WITH-DEFAULT GET, + "Recommendation G.774.01":eS REPLACE-WITH-DEFAULT GET, + "Recommendation G.774.01":sES REPLACE-WITH-DEFAULT GET;; + CONDITIONAL PACKAGES + oFSCurrentDataPackage PRESENT IF + "an instance supports it", + "Recommendation G.774.01":cSESCurrentDataPackage PRESENT IF + "an instance supports it", + "Recommendation G.774.01":uASCurrentDataPackage PRESENT IF + "an instance supports it"; +REGISTERED AS {g774-01MObjectClass 2}; + +rsCurrentDataBehaviour BEHAVIOUR +DEFINED AS +*Instances of the rsCurrentData managed object Class are used to hold the current +register counts for a regenerator section during a collection period. +This managed object class uses the rsHistoryData managed object class for history +retention. +A QOS alarm shall be sent as soon as a threshold is reached or crossed. At the +end of the granularity period the QOS alarm is implicitly cleared, providing +there are no other outstanding threshold crossing QOS alarms, "Threshold +crossing" removed from the currentProblemList (i.e. No Notification is Sent) and +a new QOS alarm shall be sent if the threshold is reached or crossed again during +the next granularity period. Only one threshold value per performance counter +will be supported. *; + +``` + +### 6.3 Regenerator section current data threshold reset + +``` + +rsCurrentDataTR MANAGED OBJECT CLASS +DERIVED FROM "Recommendation G.774.01":sdhCurrentData; +CHARACTERIZED BY + "Recommendation G.774.01":thresholdResetPackage, + rsCurrentDataTRPackage PACKAGE + BEHAVIOUR rsCurrentDataTRBehaviour; + +``` + +#### ATTRIBUTES + +"Recommendation X.739": granularityPeriod PERMITTED VALUES +SDHPMASN1.SDHPVGranularityPeriod, +"Recommendation G.774.01":bBE REPLACE-WITH-DEFAULT GET, +"Recommendation G.774.01":eS REPLACE-WITH-DEFAULT GET, +"Recommendation G.774.01":sES REPLACE-WITH-DEFAULT GET;;; + +#### CONDITIONAL PACKAGES + +oFSCurrentDataPackage PRESENT IF +"an instance supports it", +"Recommendation G.774.01":cSESCurrentDataPackage PRESENT IF +"an instance supports it", +"Recommendation G.774.01":uASCurrentDataPackage PRESENT IF +"an instance supports it"; +REGISTERED AS {g774-01MObjectClass 3}; + +#### rsCurrentDataTRBehaviour BEHAVIOUR + +#### DEFINED AS + +"Instances of the **rsCurrentDataTR** managed object Class are used to hold the current register counts for a regenerator section during a collection period. This managed object class uses the **rsHistoryData** managed object class for history retention"; + +### 6.4 Multiplex section current data near-end + +#### msCurrentDataNearEnd MANAGED OBJECT CLASS + +DERIVED FROM **sdhCurrentDataUnidirectional**; + +#### CHARACTERIZED BY + +#### msCurrentDataNearEndPackage PACKAGE + +BEHAVIOUR **msCurrentDataNearEndBehaviour**; + +#### ATTRIBUTES + +"Recommendation X.739": granularityPeriod REQUIRED VALUES +SDHPMUNIASN1.SDHGranularityPeriod, +"Recommendation G.774.01": bBE REPLACE-WITH-DEFAULT GET, +"Recommendation G.774.01": eS REPLACE-WITH-DEFAULT GET, +"Recommendation G.774.01": sES REPLACE-WITH-DEFAULT GET;;; + +#### CONDITIONAL PACKAGES + +nearEndUASCurrentDataPackage PRESENT IF +"an instance supports it", +"Recommendation G.774.01": cSESCurrentDataPackage PRESENT IF +"the granularity period is 15 minutes and an instance supports it", +failureCountsNearEndPackage PRESENT IF +"an instance supports it", +eSANearEndPackage PRESENT IF +"an instance supports it", +eSBNearEndPackage PRESENT IF +"an instance supports it"; +REGISTERED AS {g774-6MObjectClass 2} ; + +#### msCurrentDataNearEndBehaviour BEHAVIOUR + +#### DEFINED AS + +"Instances of the **msCurrentDataNearEnd** managed object Class are used to hold the current near-end register counts for a multiplex section trail termination point during a collection period. + +This managed object class uses the **msHistoryDataNearEnd** managed object class for history retention. + +A QOS alarm shall be sent as soon as a threshold is reached or crossed. At the end of the granularity period, the QOS alarm is implicitly cleared and, providing there are no other outstanding threshold crossing QOS alarms, threshold crossing is removed from the **currentProblemList** (i.e. No Notification is Sent) and a new QOS alarm shall be sent if the threshold is reached or crossed again during the next granularity period. Only one threshold value per performance counter will be supported."; + +### 6.5 Multiplex section current data near-end threshold reset + +``` +msCurrentDataNearEndTR MANAGED OBJECT CLASS +DERIVED FROM sdhCurrentDataUnidirectional; +CHARACTERIZED BY +"Recommendation G.774.01": thresholdResetPackage, +msCurrentDataNearEndTRPackage PACKAGE + BEHAVIOUR + msCurrentDataNearEndTRBehaviour; + ATTRIBUTES + "Recommendation X.739": granularityPeriod PERMITTED VALUES + SDHPMUNIASN1.SDHPVGranularityPeriod, + "Recommendation G.774.01": bBE REPLACE-WITH-DEFAULT GET, + "Recommendation G.774.01": eS REPLACE-WITH-DEFAULT GET, + "Recommendation G.774.01": sES REPLACE-WITH-DEFAULT GET;;; + CONDITIONAL PACKAGES + nearEndUASCurrentDataPackage PRESENT IF + "an instance supports it", + "Recommendation G.774.01": cSESCurrentDataPackage PRESENT IF + "the granularity period is 15 minutes and an instance supports it" ; + REGISTERED AS {g774-6MObjectClass 3} ; +``` + +``` +msCurrentDataNearEndTRBehaviour BEHAVIOUR +DEFINED AS +``` + +"Instances of the **msCurrentDataNearEndTR** managed object Class are used to hold the current near-end register counts for a multiplex section trail termination point during a collection period. + +Only the 15 minutes granularity period must be supported. + +This managed object class uses the **msHistoryDataNearEnd** managed object class for history retention. " ; + +### 6.6 Path termination current data near-end + +``` +pathTerminationCurrentDataNearEnd MANAGED OBJECT CLASS +DERIVED FROM sdhCurrentDataUnidirectional; +CHARACTERIZED BY +pathTerminationCurrentDataNearEndPackage PACKAGE + BEHAVIOUR pathTerminationCurrentDataNearEndBehaviour; + ATTRIBUTES + "Recommendation X.739": granularityPeriod REQUIRED VALUES + SDHPMUNIASN1.SDHGranularityPeriod, + "Recommendation G.774.01": bBE REPLACE-WITH-DEFAULT GET, + "Recommendation G.774.01": eS REPLACE-WITH-DEFAULT GET, + "Recommendation G.774.01": sES REPLACE-WITH-DEFAULT GET;;; + CONDITIONAL PACKAGES + nearEndUASCurrentDataPackage PRESENT IF + "an instance supports it", + "Recommendation G.774.01": cSESCurrentDataPackage PRESENT IF + "the granularity period is 15 minutes and an instance supports it", + failureCountsNearEndPackage PRESENT IF + "an instance supports it", + eSANearEndPackage PRESENT IF + "an instance supports it", + eSBNearEndPackage PRESENT IF + "an instance supports it"; + REGISTERED AS {g774-6MObjectClass 4} ; +``` + +``` +pathTerminationCurrentDataNearEndBehaviour BEHAVIOUR +DEFINED AS +``` + +"Instances of the **pathTerminationCurrentDataNearEnd** managed object Class are used + +to hold the current near end register counts for a Higher Order Path or Lower Order Path during a collection period. + +This managed object class uses the **pathTerminationHistoryDataNearEnd** managed object class for history retention. + +A QOS alarm shall be sent as soon as a threshold is reached or crossed. At the end of the granularity period, the QOS alarm is implicitly cleared and, providing there are no other outstanding threshold crossing QOS alarms, threshold crossing is removed from the **currentProblemList** (i.e. No Notification is Sent) and a new QOS alarm shall be sent if the threshold is reached or crossed again during the next granularity period. Only one threshold value per performance counter will be supported." + +### 6.7 Path termination current data near-end threshold reset + +``` +pathTerminationCurrentDataNearEndTR MANAGED OBJECT CLASS +DERIVED FROM sdhCurrentDataUnidirectional; +CHARACTERIZED BY +"Recommendation G.774.01": thresholdResetPackage, +pathTerminationCurrentDataNearEndTRPackage PACKAGE + BEHAVIOUR pathTerminationCurrentDataNearEndTRBehaviour; + ATTRIBUTES + "Recommendation X.739": granularityPeriod PERMITTED VALUES + SDHPMUNIASN1.SDHPVGranularityPeriod, + "Recommendation G.774.01": bBE REPLACE-WITH-DEFAULT GET, + "Recommendation G.774.01": eS REPLACE-WITH-DEFAULT GET, + "Recommendation G.774.01": sES REPLACE-WITH-DEFAULT GET;; + CONDITIONAL PACKAGES + nearEndUASCurrentDataPackage PRESENT IF + "an instance supports it", + "Recommendation G.774.01": cSESCurrentDataPackage PRESENT IF + "the granularity period is 15 minutes and an instance supports it"; +REGISTERED AS {g774-6MObjectClass 5} ; +``` + +``` +pathTerminationCurrentDataNearEndTRBehaviour BEHAVIOUR +DEFINED AS +"Instances of the pathTerminationCurrentDataNearEndTR managed object Class are +used to hold the current near-end register counts for a Higher Order Path or +Lower Order Path during a collection period. +``` + +Only the 15 minutes granularity period must be supported. + +This managed object class uses the **pathTerminationHistoryDataNearEnd** managed object class for history retention." + +### 6.8 Multiplex section adaptation current data + +``` +msAdaptationCurrentData MANAGED OBJECT CLASS +DERIVED FROM "Recommendation G.774.01":sdhCurrentData; +CHARACTERIZED BY +msAdaptationCurrentDataPackage PACKAGE + BEHAVIOUR msAdaptationCurrentDataBehaviour; + ATTRIBUTES + pJCHigh GET, + pJCLow GET;; +REGISTERED AS {g774-01MObjectClass 11}; +``` + +``` + +msAdaptationCurrentDataBehaviour BEHAVIOUR +DEFINED AS +"Instances of this class are used to hold the pointer justification event (PJE) counts. Positive and negative PJEs are counted separately one selectable outgoing AU within an STM-N signal after the AU has been resynchronized to the local clock."; +``` + +### 6.9 Multiplex section current data far-end + +``` + +msCurrentDataFarEnd MANAGED OBJECT CLASS +DERIVED FROM sdhCurrentDataUnidirectional; +CHARACTERIZED BY +msCurrentDataFarEndPackage PACKAGE + BEHAVIOUR msCurrentDataFarEndBehaviour; + ATTRIBUTES + "Recommendation X.739": granularityPeriod REQUIRED VALUES + SDHPMUNIASN1.SDHGranularityPeriod, + "Recommendation G.774.01": fEBBE REPLACE-WITH-DEFAULT GET, + "Recommendation G.774.01": fEES REPLACE-WITH-DEFAULT GET, + "Recommendation G.774.01": fESES REPLACE-WITH-DEFAULT GET;; + CONDITIONAL PACKAGES + farEndUASCurrentDataPackage PRESENT IF + "an instance supports it", + "Recommendation G.774.01": farEndCSESCurrentDataPackage PRESENT IF + "the granularity period is 15 minutes and an instance supports it", + failureCountsFarEndPackage PRESENT IF + "an instance supports it", + eSAFarEndPackage PRESENT IF + "an instance supports it", + eSBFarEndPackage PRESENT IF + "an instance supports it"; +REGISTERED AS {g774-6MObjectClass 6} ; +``` + +``` + +msCurrentDataFarEndBehaviour BEHAVIOUR +DEFINED AS +"Instances of the msCurrentDataFarEnd managed object Class are used to hold the current far-end register counts for a multiplex section trail termination point during a collection period. +``` + +This managed object class uses the **msHistoryDataFarEnd** managed object class for history retention. + +A QOS alarm shall be sent as soon as a threshold is reached or crossed. At the end of the granularity period, the QOS alarm is implicitly cleared and, providing there are no other outstanding threshold crossing QOS alarms, threshold crossing is removed from the **currentProblemList** (i.e. No Notification is Sent) and a new QOS alarm shall be sent if the threshold is reached or crossed again during the next granularity period. Only one threshold value per performance counter will be supported."; + +### 6.10 Multiplex section current data far-end threshold reset + +``` + +msCurrentDataFarEndTR MANAGED OBJECT CLASS +DERIVED FROM sdhCurrentDataUnidirectional; +CHARACTERIZED BY + "Recommendation G.774.01": thresholdResetPackage, + msCurrentDataFarEndTRPackage PACKAGE + BEHAVIOUR + msCurrentDataFarEndTRBehaviour; + ATTRIBUTES + "Recommendation X.739": granularityPeriod PERMITTED VALUES + SDHPMUNIASN1.SDHPVGranularityPeriod, + "Recommendation G.774.01": fEBBE REPLACE-WITH-DEFAULT GET, +``` + +``` + +"Recommendation G.774.01": fEES REPLACE-WITH-DEFAULT GET, +"Recommendation G.774.01": fESES REPLACE-WITH-DEFAULT GET;;; +CONDITIONAL PACKAGES +farEndUASCurrentDataPackage PRESENT IF +"an instance supports it", +"Recommendation G.774.01": farEndCSESCurrentDataPackage PRESENT IF +"the granularity period is 15 minutes and an instance supports it"; +REGISTERED AS {g774-6MObjectClass 7} ; + +msCurrentDataFarEndTRBehaviour BEHAVIOUR +DEFINED AS +"Instances of the msCurrentDataFarEnd managed object Class are used to hold the +current far-end register counts for a multiplex section trail termination point +during a collection period. + +``` + +Only the 15 minutes granularity period must be supported. + +This managed object class uses the **msHistoryDataFarEnd** managed object class for history retention." ; + +### 6.11 Path termination current data far-end + +``` + +pathTerminationCurrentDataFarEnd MANAGED OBJECT CLASS +DERIVED FROM sdhCurrentDataUnidirectional; +CHARACTERIZED BY +pathTerminationCurrentDataFarEndPackage PACKAGE +BEHAVIOUR pathTerminationCurrentDataFarEndBehaviour; +ATTRIBUTES +"Recommendation X.739": granularityPeriod REQUIRED VALUES +SDHPMUNIASN1.SDHGranularityPeriod, +"Recommendation G.774.01": feBBE REPLACE-WITH-DEFAULT GET, +"Recommendation G.774.01": feES REPLACE-WITH-DEFAULT GET, +"Recommendation G.774.01": feSES REPLACE-WITH-DEFAULT GET;;; +CONDITIONAL PACKAGES +farEndUASCurrentDataPackage PRESENT IF +"an instance supports it", +"Recommendation G.774.01": farEndCSESCurrentDataPackage PRESENT IF +"the granularity period is 15 minutes and an instance supports it", +failureCountsFarEndPackage PRESENT IF +"an instance supports it", +eSAFarEndPackage PRESENT IF +"an instance supports it", +eSBFarEndPackage PRESENT IF +"an instance supports it"; +REGISTERED AS {g774-6MObjectClass 8} ; + +``` + +``` + +pathTerminationCurrentDataFarEndBehaviour BEHAVIOUR +DEFINED AS +"Instances of the pathTerminationCurrentDataFarEnd managed object Class are used +to hold the current far end register counts for a Higher Order Path or Lower +Order Path during a collection period. + +``` + +This managed object class uses the **pathTerminationHistoryDataFarEnd** managed object class for history retention. + +A QOS alarm shall be sent as soon as a threshold is reached or crossed. At the end of the granularity period, the QOS alarm is implicitly cleared and, providing there are no other outstanding threshold crossing QOS alarms, threshold crossing is removed from the **currentProblemList** (i.e. No Notification is Sent) and a new QOS alarm shall be sent if the threshold is reached or crossed again during the next granularity period. Only one threshold value per performance counter will be supported."; + +### 6.12 Path termination current data far-end threshold reset + +``` +pathTerminationCurrentDataFarEndTR MANAGED OBJECT CLASS +DERIVED FROM sdhCurrentDataUnidirectional; +CHARACTERIZED BY +"Recommendation G.774.01": thresholdResetPackage, +pathTerminationCurrentDataFarEndTRPackage PACKAGE + BEHAVIOUR pathTerminationCurrentDataFarEndTRBehaviour; + ATTRIBUTES + "Recommendation X.739": granularityPeriod PERMITTED VALUES + SDHPMUNIASN1.SDHPVGranularityPeriod, + "Recommendation G.774.01": FEBBE REPLACE-WITH-DEFAULT GET, + "Recommendation G.774.01": FEES REPLACE-WITH-DEFAULT GET, + "Recommendation G.774.01": FESES REPLACE-WITH-DEFAULT GET; + CONDITIONAL PACKAGES + farEndUASCurrentDataPackage PRESENT IF + "an instance supports it", + "Recommendation G.774.01": farEndCSESCurrentDataPackage PRESENT IF + "the granularity period is 15 minutes and an instance supports it"; +REGISTERED AS {g774-6MObjectClass 9} ; +``` + +``` +pathTerminationCurrentDataFarEndTRBehaviour BEHAVIOUR +DEFINED AS +"Instances of the pathTerminationCurrentDataFarEndTR managed object Class are +used to hold the current far-end register counts for a Higher Order Path or Lower +Order Path during a collection period. +``` + +Only the 15 minutes granularity period must be supported. + +This managed object class uses the pathTerminationHistoryDataFarEnd managed object class for history retention."; + +### 6.13 Regenerator section history data + +``` +rsHistoryData MANAGED OBJECT CLASS +DERIVED FROM "Recommendation Q.822 ": historyData; +CHARACTERIZED BY +rsHistoryDataPackage PACKAGE + BEHAVIOUR rsHistoryDataBehaviour; + ATTRIBUTES + "Recommendation G.774.01": bBE GET, + "Recommendation G.774.01": eS GET, + "Recommendation G.774.01": sES GET ; + CONDITIONAL PACKAGES + ofSHistoryDataPackage PRESENT IF + "the containing rsCurrentData or rsCurrentDataTR instance contains the + ofSCurrentDataPackage", + "Recommendation G.774.01": uASHistoryDataPackage PRESENT IF + "the containing rsCurrentData contains the uASCurrentDataPackage"; +REGISTERED AS {g774-01MObjectClass 12}; +``` + +``` +rsHistoryDataBehaviour BEHAVIOUR +DEFINED AS +"Instances of this class are used to store the observed events of an +rsCurrentData or rsCurrentDataTR object at the end of an observation interval. An +instance of this managed object is contained by an rsCurrentData or +rsCurrentDataTR managed object instance."; +``` + +### 6.14 Multiplex section history data near-end + +``` +msHistoryDataNearEnd MANAGED OBJECT CLASS +DERIVED FROM "Recommendation Q.822":historyData; +CHARACTERIZED BY +msHistoryDataNearEndPackage PACKAGE + BEHAVIOUR + msHistoryDataNearEndBehaviour; + ATTRIBUTES + "Recommendation G.774.01": bBE GET, + "Recommendation G.774.01": eS GET, + "Recommendation G.774.01": sES GET;; + CONDITIONAL PACKAGES + nearEndUASHistoryDataPackage PRESENT IF + "the containing msCurrentDataNearEnd contains the + nearEndUASCurrentDataPackage", + failureCountsNearEndHistoryDataPackage PRESENT IF + "the containing msCurrentDataNearEnd contains the + failureCountsNearEndPackage", + eSANearEndHistoryDataPackage PRESENT IF + "the containing msCurrentDataNearEnd contains the eSANearEndPackage", + eSBNearEndHistoryDataPackage PRESENT IF + "the containing msCurrentDataNearEnd contains the eSBNearEndPackage"; +REGISTERED AS {g774-6MObjectClass 10} ; + +msHistoryDataNearEndBehaviour BEHAVIOUR +DEFINED AS +"Instances of this class are used to store the observed events of an +msCurrentDataNearEnd or msCurrentDataNearEndTR object at the end of an +observation interval. An instance of this managed object is contained by an +msCurrentDataNearEnd or msCurrentDataNearEndTR managed object instance"; +``` + +### 6.15 Multiplex section adaptation history data + +``` +msAdaptationHistoryData MANAGED OBJECT CLASS +DERIVED FROM "Recommendation Q.822": historyData; +CHARACTERIZED BY +msAdaptationHistoryDataPackage PACKAGE + BEHAVIOUR msAdaptationHistoryDataBehaviour; + ATTRIBUTES + pJCHigh GET, + pJCLow GET;; +REGISTERED AS {g774-01MObjectClass 18}; +msAdaptationHistoryDataBehaviour BEHAVIOUR +DEFINED AS +"Instances of this class are used to store the observed events of an +msAdaptationCurrentData object at the end of an observation interval. An instance +of this managed object is contained by an msAdaptationCurrentData managed object +instance."; +``` + +### 6.16 Path termination history data near-end + +``` +pathTerminationHistoryDataNearEnd MANAGED OBJECT CLASS +DERIVED FROM "Recommendation Q.822":historyData; +CHARACTERIZED BY +pathTerminationHistoryDataNearEndPackage PACKAGE + BEHAVIOUR pathTerminationHistoryDataNearEndBehaviour; + ATTRIBUTES + "Recommendation G.774.01": bBE GET, + "Recommendation G.774.01": eS GET, + "Recommendation G.774.01": sES GET;; +``` + +#### CONDITIONAL PACKAGES + +``` +nearEndUASHistoryDataPackage PRESENT IF +"the containing pathTerminationCurrentDataNearEnd contains the +nearEndUASCurrentDataPackage", +failureCountsNearEndHistoryDataPackage PRESENT IF +"the containing pathTerminationCurrentDataNearEnd contains the +failureCountsNearEndPackage", +eSANearEndHistoryDataPackage PRESENT IF +"the containing pathTerminationCurrentDataNearEnd contains the +eSANearEndPackage", +eSBNearEndHistoryDataPackage PRESENT IF +"the containing pathTerminationCurrentDataNearEnd contains the +eSBNearEndPackage"; +REGISTERED AS {g774-6MObjectClass 11} ; +``` + +#### pathTerminationHistoryDataNearEndBehaviour BEHAVIOUR DEFINED AS + +``` +"Instances of this class are used to store the observed events of a +pathTerminationCurrentDataNearEnd or pathTerminationCurrentDataNearEndTR object +at the end of an observation interval. An instance of this managed object is +contained by a pathTerminationCurrentDataNearEnd or +pathTerminationCurrentDataNearEndTR managed object instance"; +``` + +### 6.17 Multiplex section history data far-end + +``` +msHistoryDataFarEnd MANAGED OBJECT CLASS +DERIVED FROM "Recommendation Q.822":historyData; +CHARACTERIZED BY +``` + +#### msHistoryDataFarEndPackage PACKAGE + +#### BEHAVIOUR + +``` +msHistoryDataFarEndBehaviour; +``` + +#### ATTRIBUTES + +``` +"Recommendation G.774.01": FEBBE GET, +"Recommendation G.774.01": FEES GET, +"Recommendation G.774.01": FESES GET;;; +``` + +#### CONDITIONAL PACKAGES + +``` +farEndUASHistoryDataPackage PRESENT IF +"the containing msCurrentDataFarEnd contains the +farEndUASCurrentDataPackage", +failureCountsFarEndHistoryDataPackage PRESENT IF +"the containing msCurrentDataFarEnd contains the +failureCountsFarEndPackage", +eSAFarEndHistoryDataPackage PRESENT IF +"the containing msCurrentDataFarEnd contains the eSAFarEndPackage", +eSBFarEndHistoryDataPackage PRESENT IF +"the containing msCurrentDataFarEnd contains the eSBFarEndPackage"; +REGISTERED AS {g774-6MObjectClass 12} ; +``` + +#### msHistoryDataFarEndBehaviour BEHAVIOUR DEFINED AS + +``` +"Instances of this class are used to store the observed events of an +msCurrentDataFarEnd or msCurrentDataFarEndTR object at the end of an observation +interval. An instance of this managed object is contained by an +msCurrentDataFarEnd or msCurrentDataFarEndTR managed object instance"; +``` + +### 6.18 Path termination history data far-end + +``` +pathTerminationHistoryDataFarEnd MANAGED OBJECT CLASS +DERIVED FROM "Recommendation Q.822":historyData; +CHARACTERIZED BY +pathTerminationHistoryDataFarEndPackage PACKAGE +BEHAVIOUR pathTerminationHistoryDataFarEndBehaviour; +ATTRIBUTES +``` + +``` + +"Recommendation G.774.01": FEBBE GET, +"Recommendation G.774.01": FEES GET, +"Recommendation G.774.01": FESES GET; +CONDITIONAL PACKAGES +farEndUASHistoryDataPackage PRESENT IF +"the containing pathTerminationCurrentDataFarEnd contains the +farEndUASCurrentDataPackage", +failureCountsFarEndHistoryDataPackage PRESENT IF +"the containing pathTerminationCurrentDataFarEnd contains the +failureCountsFarEndPackage", +eSAFarEndHistoryDataPackage PRESENT IF +"the containing pathTerminationCurrentDataFarEnd contains the +eSAFarEndPackage", +eSBFarEndHistoryDataPackage PRESENT IF +"the containing pathTerminationCurrentDataFarEnd contains the +eSBFarEndPackage"; +REGISTERED AS {g774-6MObjectClass 13} ; + +pathTerminationHistoryDataFarEndBehaviour BEHAVIOUR +DEFINED AS +"Instances of this class are used to store the observed events of a +pathTerminationCurrentDataFarEnd or pathTerminationCurrentDataFarEndTR object at +the end of an observation interval. An instance of this managed object is +contained by a pathTerminationCurrentDataFarEnd or +pathTerminationCurrentDataFarEndTR managed object instance"; + +``` + +## 7 Package definitions + +### 7.1 Near-end unavailable second current data package + +``` + +nearEndUASCurrentDataPackage PACKAGE +BEHAVIOUR + nearEndUASCurrentDataPackageBehaviour; +ATTRIBUTES + nEUAS REPLACE-WITH-DEFAULT GET; +REGISTERED AS {g774-6Package 1}; + +nearEndUASCurrentDataPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to store the counter of one-second intervals pertaining to +an Unavailable Time at the near end."; + +``` + +### 7.2 Far-end unavailable second current data package + +``` + +farEndUASCurrentDataPackage PACKAGE +BEHAVIOUR + farEndUASCurrentDataPackageBehaviour; +ATTRIBUTES + fEUAS REPLACE-WITH-DEFAULT GET; +REGISTERED AS {g774-6Package 2}; + +farEndUASCurrentDataPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to store the counter of one-second intervals pertaining to +an Unavailable Time at the far end."; + +``` + +### 7.3 Near-end unavailable second history data package + +``` +nearEndUASHistoryDataPackage PACKAGE + BEHAVIOUR + nearEndUASHistoryDataPackageBehaviour; + ATTRIBUTES + nEUAS GET; + REGISTERED AS {g774-6Package 3}; + +nearEndUASHistoryDataPackageBehaviour BEHAVIOUR + DEFINED AS + "This package is used to store the corresponding current data counter of one + second intervals pertaining to an Unavailable Time at the near end at the end of + the granularity period."; +``` + +### 7.4 Far-end unavailable second history data package + +``` +farEndUASHistoryDataPackage PACKAGE + BEHAVIOUR + farEndUASHistoryDataPackageBehaviour; + ATTRIBUTES + fEUAS GET; + REGISTERED AS {g774-6Package 4}; + +farEndUASHistoryDataPackageBehaviour BEHAVIOUR + DEFINED AS + "This package is used to store the corresponding current data counter of one- + second intervals pertaining to an Unavailable Time at the far end at the end of + the granularity period."; +``` + +### 7.5 Failure counts near-end package + +``` +failureCountsNearEndPackage PACKAGE + BEHAVIOUR + failureCountsNearEndPackageBehaviour; + ATTRIBUTES + fCNearEnd REPLACE-WITH-DEFAULT GET; + REGISTERED AS {g774-6Package 5}; + +failureCountsNearEndPackageBehaviour BEHAVIOUR + DEFINED AS + "This package is used to store the corresponding failure counts at the near + end."; +``` + +### 7.6 Errored seconds type A near-end package + +``` +eSANearEndPackage PACKAGE + BEHAVIOUR + eSANearEndPackageBehaviour; + ATTRIBUTES + eSANearEnd REPLACE-WITH-DEFAULT GET; + REGISTERED AS {g774-6Package 6}; + +eSANearEndPackageBehaviour BEHAVIOUR + DEFINED AS + "This package is used to store the errored seconds of type A at the near end."; +``` + +### 7.7 Errored seconds type B near-end package + +``` +eSBNearEndPackage PACKAGE + BEHAVIOUR + eSBNearEndPackageBehaviour; + ATTRIBUTES + eSBNearEnd REPLACE-WITH-DEFAULT GET; +REGISTERED AS {g774-6Package 7}; + +eSBNearEndPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to store the errored seconds of type B at the near end."; +``` + +### 7.8 Failure counts far-end package + +``` +failureCountsFarEndPackage PACKAGE + BEHAVIOUR + failureCountsFarEndPackageBehaviour; + ATTRIBUTES + fCFarEnd REPLACE-WITH-DEFAULT GET; +REGISTERED AS {g774-6Package 8}; + +failureCountsFarEndPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to store the corresponding failure counts at the far end."; +``` + +### 7.9 Errored seconds type A far-end package + +``` +eSAFarEndPackage PACKAGE + BEHAVIOUR + eSAFarEndPackageBehaviour; + ATTRIBUTES + eSAFarEnd REPLACE-WITH-DEFAULT GET; +REGISTERED AS {g774-6Package 9}; + +eSAFarEndPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to store the errored seconds of type A at the far end."; +``` + +### 7.10 Errored seconds type B far-end package + +``` +eSBFarEndPackage PACKAGE + BEHAVIOUR + eSBFarEndPackageBehaviour; + ATTRIBUTES + eSBFarEnd REPLACE-WITH-DEFAULT GET; +REGISTERED AS {g774-6Package 10}; + +eSBFarEndPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to store the errored seconds of type B at the far end."; +``` + +### 7.11 Failure counts near-end history data package + +``` +failureCountsNearEndHistoryDataPackage PACKAGE + BEHAVIOUR + failureCountsNearEndHistoryDataPackageBehaviour; + ATTRIBUTES + fCNearEnd GET; +REGISTERED AS {g774-6Package 11}; +``` + +``` + +failureCountsNearEndHistoryDataPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to store the corresponding failure counts at the near end +at the end of the granularity period."; + +``` + +### 7.12 Errored seconds type A near-end history data package + +``` + +eSANearEndHistoryDataPackage PACKAGE +BEHAVIOUR + eSANearEndHistoryDataPackageBehaviour; +ATTRIBUTES + eSANearEnd GET; +REGISTERED AS {g774-6Package 12}; + +eSANearEndHistoryDataPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to store the corresponding errored seconds of type A at the +near end at the end of the granularity period."; + +``` + +### 7.13 Errored seconds type B near-end history data package + +``` + +eSBNearEndHistoryDataPackage PACKAGE +BEHAVIOUR + eSBNearEndHistoryDataPackageBehaviour; +ATTRIBUTES + eSBNearEnd GET; +REGISTERED AS {g774-6Package 13}; + +eSBNearEndHistoryDataPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to store the corresponding errored seconds of type B at the +near end at the end of the granularity period."; + +``` + +### 7.14 Failure counts far-end history data package + +``` + +failureCountsFarEndHistoryDataPackage PACKAGE +BEHAVIOUR + failureCountsFarEndHistoryDataPackageBehaviour; +ATTRIBUTES + fCFarEnd GET; +REGISTERED AS {g774-6Package 14}; + +failureCountsFarEndHistoryDataPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to store the corresponding failure counts at the far end at +the end of the granularity period."; + +``` + +### 7.15 Errored seconds type A far-end history data package + +``` + +eSAFarEndHistoryDataPackage PACKAGE +BEHAVIOUR + eSAFarEndHistoryDataPackageBehaviour; +ATTRIBUTES + eSAFarEnd GET; +REGISTERED AS {g774-6Package 15}; + +eSAFarEndHistoryDataPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to store the corresponding errored seconds of type A at the +far end at the end of the granularity period."; + +``` + +### 7.16 Errored seconds type B far-end history data package + +``` +eSBFarEndHistoryDataPackage PACKAGE + BEHAVIOUR + eSBFarEndHistoryDataPackageBehaviour; + ATTRIBUTES + eSBFarEnd GET; +REGISTERED AS {g774-6Package 16}; + +eSBFarEndHistoryDataPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to store the corresponding errored seconds of type B at the +far end at the end of the granularity period."; +``` + +### 7.17 Out of frame second current data package + +``` +oFSCurrentDataPackage PACKAGE + BEHAVIOUR + oFSCurrentDataPackageBehaviour; + ATTRIBUTES + oFS REPLACE-WITH-DEFAULT GET; +REGISTERED AS {g774-01Package 10}; + +oFSCurrentDataPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to store the counter of one second intervals containing one +or more Out of Frame."; +``` + +### 7.18 Out of frame second history data package + +``` +oFSHistoryDataPackage PACKAGE + BEHAVIOUR + oFSHistoryDataPackageBehaviour; + ATTRIBUTES + oFS GET; +REGISTERED AS {g774-01Package 11}; + +oFSHistoryDataPackageBehaviour BEHAVIOUR +DEFINED AS +"This package is used to record the corresponding current data attribute values +at the end of the granularity period."; +``` + +## 8 Attributes definitions + +### 8.1 Near-end unavailable seconds + +``` +nEUAS ATTRIBUTE + DERIVED FROM "Recommendation X.721": counter; + BEHAVIOUR nEUASBeh BEHAVIOUR + DEFINED AS + "The value of the nEUAS attribute represents the count of one-second +intervals pertaining to an UnavailableTime at the near end.";; +REGISTERED AS {g774-6Attribute 1}; +``` + +### 8.2 Far-end unavailable seconds + +``` +feuas ATTRIBUTE + DERIVED FROM "Recommendation X.721": counter; + BEHAVIOUR feuasBeh BEHAVIOUR + DEFINED AS + "The value of the feuas attribute represents the count of one-second +intervals pertaining to an UnavailableTime at the far end.";; +REGISTERED AS {g774-6Attribute 2}; +``` + +### 8.3 Failure counts near-end + +``` +fCNearEnd ATTRIBUTE + DERIVED FROM "Recommendation X.721": counter; + BEHAVIOUR fCNearEndBeh BEHAVIOUR + DEFINED AS + "This parameter is a count of the number of occurrences of near-end +failure events.";; +REGISTERED AS {g774-6Attribute 3}; +``` + +### 8.4 Errored seconds type A near-end + +``` +eSANearEnd ATTRIBUTE + DERIVED FROM "Recommendation X.721": counter; + BEHAVIOUR eSANearEndBeh BEHAVIOUR + DEFINED AS + "This parameter is a count of errored seconds of type A at the near +end. +";; +REGISTERED AS {g774-6Attribute 4}; +``` + +### 8.5 Errored seconds type B near-end + +``` +eSBNearEnd ATTRIBUTE + DERIVED FROM "Recommendation X.721": counter; + BEHAVIOUR eSBNearEndBeh BEHAVIOUR + DEFINED AS + "This parameter is a count of errored seconds of type B at the near +end. +";; +REGISTERED AS {g774-6Attribute 5}; +``` + +### 8.6 Failure counts far-end + +``` +fCFarEnd ATTRIBUTE + DERIVED FROM "Recommendation X.721": counter; + BEHAVIOUR fCFarEndBeh BEHAVIOUR + DEFINED AS + "This parameter is a count of the number of occurrences of far-end +failure events. +";; +REGISTERED AS {g774-6Attribute 6}; +``` + +### 8.7 Errored seconds type A far-end + +``` +eSAFarEnd ATTRIBUTE + DERIVED FROM "Recommendation X.721": counter; + BEHAVIOUR eSAFarEndBeh BEHAVIOUR + DEFINED AS + "This parameter is a count of the errored seconds of type A at the far +end. +";; +REGISTERED AS {g774-6Attribute 7}; +``` + +### 8.8 Errored seconds type B far-end + +``` +eSBFarEnd ATTRIBUTE + DERIVED FROM "Recommendation X.721": counter; + BEHAVIOUR eSBFarEndBeh BEHAVIOUR + DEFINED AS + "This parameter is a count of errored seconds of type B at the far end. +";; +REGISTERED AS {g774-6Attribute 8}; +``` + +### 8.9 Out of frame second + +``` +oFS ATTRIBUTE + DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2": counter; + BEHAVIOUR + oFSBeh BEHAVIOUR + DEFINED AS + "The value of the oFS attribute represents the count of seconds with at least one +Out Of Frame Event during the available time of the monitored resource during the +corresponding granularity period." +;; +REGISTERED AS {g774-01Attribute 14}; +``` + +### 8.10 Pointer justification count high + +``` +pJCHigh ATTRIBUTE + DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2": counter; + BEHAVIOUR + pJCHighBehaviour BEHAVIOUR + DEFINED AS + "The value of the pJCHigh attribute represents the positive PJE count on one +selectable outgoing AU within an STM-N signal after the AU has been +resynchronized to the local clock." +;; +REGISTERED AS {g774-01Attribute 23}; +``` + +### 8.11 Pointer justification count low + +``` +pJCLow ATTRIBUTE + DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2": counter; + BEHAVIOUR + pJCLowBehaviour BEHAVIOUR + DEFINED AS + "The value of the pJCLow attribute represents the negative PJE count on one +selectable outgoing AU within an STM-N signal after the AU has been +resynchronized to the local clock." +;; +REGISTERED AS {g774-01Attribute 24}; +``` + +## 9 Actions + +None. + +## 10 Notifications + +None. + +## 11 Parameters + +None. + +# 12 Name binding definitions + +### 12.1 MS current data near-end – MS TTP sink + +``` +msCurrentDataNearEnd-msTTPSink NAME BINDING + SUBORDINATE OBJECT CLASS msCurrentDataNearEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":msTTPSink AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739":scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 1}; +``` + +### 12.2 MS current data near-end threshold reset – MS TTP sink + +``` +msCurrentDataNearEndTR-msTTPSink NAME BINDING + SUBORDINATE OBJECT CLASS msCurrentDataNearEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":msTTPSink AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739":scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 2}; +``` + +### 12.3 RS current data – RS TTP sink + +``` +rsCurrentData-rsTTPSink NAME BINDING + SUBORDINATE OBJECT CLASS rsCurrentData AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774": rsTTPSink AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-01NameBinding 7}; +``` + +### 12.4 RS current data threshold reset – RS TTP sink + +``` +rsCurrentDataTR-rsTTPSink NAME BINDING + SUBORDINATE OBJECT CLASS rsCurrentDataTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774": rsTTPSink AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-01NameBinding 8}; +``` + +### 12.5 MS current data far-end – MS TTP sink + +``` +msCurrentDataFarEnd-msTTPSink NAME BINDING + SUBORDINATE OBJECT CLASS msCurrentDataFarEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774": msTTPSink AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 13}; +``` + +### 12.6 MS current data far-end threshold reset – MS TTP sink + +``` +msCurrentDataFarEndTR-msTTPSink NAME BINDING + SUBORDINATE OBJECT CLASS msCurrentDataFarEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774": msTTPSink AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 14}; +``` + +### 12.7 Path termination current data near-end – AU4 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataNearEnd-au4SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataNearEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05": au4SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 69}; +``` + +### 12.8 Path termination current data near-end – AU3 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataNearEnd-au3SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataNearEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":au3SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 70}; +``` + +### 12.9 Path termination current data near-end – TU3 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataNearEnd-tu3SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataNearEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu3SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 71}; +``` + +### 12.10 Path termination current data near-end – TU2 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataNearEnd-tu2SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataNearEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu2SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 72}; +``` + +### 12.11 Path termination current data near-end – TU12 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataNearEnd-tu12SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataNearEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu12SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 73}; +``` + +### 12.12 Path termination current data near-end – TU11 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataNearEnd-tu11SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataNearEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu11SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 74}; +``` + +### 12.13 Path termination current data far-end – AU4 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataFarEnd-au4SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataFarEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":au4SupervisedCTPSinkR1 + AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 75}; +``` + +### 12.14 Path termination current data far-end – AU3 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataFarEnd-au3SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataFarEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":au3SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 76}; +``` + +### 12.15 Path termination current data far-end – TU3 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataFarEnd-tu3SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataFarEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu3SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 77}; +``` + +### 12.16 Path termination current data far-end – TU2 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataFarEnd-tu2SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataFarEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu2SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 78}; +``` + +### 12.17 Path termination current data far-end – TU12 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataFarEnd-tu12SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataFarEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu12SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 79}; +``` + +### 12.18 Path termination current data far-end – TU11 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataFarEnd-tu11SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataFarEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu11SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 80}; +``` + +### 12.19 Path termination current data near-end TR – AU4 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataNearEndTR-au4SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataNearEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":au4SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 81}; +``` + +### 12.20 Path termination current data near-end TR – AU3 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataNearEndTR-au3SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataNearEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":au3SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 82}; +``` + +### 12.21 Path termination current data near-end TR – TU3 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataNearEndTR-tu3SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataNearEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu3SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 83}; +``` + +### 12.22 Path termination current data near-end TR – TU2 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataNearEndTR-tu2SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataNearEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu2SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 84}; +``` + +### 12.23 Path termination current data near-end TR – TU12 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataNearEndTR-tu12SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataNearEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu12SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 85}; +``` + +### 12.24 Path termination current data near-end TR – TU11 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataNearEndTR-tu11SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataNearEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu11SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 86}; +``` + +### 12.25 Path termination current data far-end TR – AU4 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataFarEndTR-au4SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataFarEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":au4SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 87}; +``` + +### 12.26 Path termination current data far-end TR – AU3 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataFarEndTR-au3SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataFarEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":au3SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 88}; +``` + +### 12.27 Path termination current data far-end TR – TU3 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataFarEndTR-tu3SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataFarEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu3SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 89}; +``` + +### 12.28 Path termination current data far-end TR – TU2 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataFarEndTR-tu2SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataFarEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu2SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 90}; +``` + +### 12.29 Path termination current data far-end TR – TU12 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataFarEndTR-tu12SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataFarEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu12SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 91}; +``` + +### 12.30 Path Termination current data far-end TR – TU11 supervised CTP SinkR1 + +``` +pathTerminationCurrentDataFarEndTR-tu11SupervisedCTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS pathTerminationCurrentDataFarEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774.05":tu11SupervisedCTPSinkR1 AND + SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 92}; +``` + +### 12.31 Path termination current data near-end – VC4 TTP SinkR1 + +``` +pathTerminationCurrentDataNearEnd-vc4TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataNearEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc4TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 49}; +``` + +### 12.32 Path termination current data near-end – VC3 TTP SinkR1 + +``` +pathTerminationCurrentDataNearEnd-vc3TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataNearEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc3TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 50}; +``` + +### 12.33 Path termination current data near-end – VC2 TTP SinkR1 + +``` +pathTerminationCurrentDataNearEnd-vc2TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataNearEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc2TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 51}; +``` + +### 12.34 Path termination current data near-end – VC12 TTP SinkR1 + +``` +pathTerminationCurrentDataNearEnd-vc12TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataNearEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc12TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 52}; +``` + +### 12.35 Path termination current data near-end – VC11 TTP SinkR1 + +``` +pathTerminationCurrentDataNearEnd-vc11TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataNearEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc11TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 53}; +``` + +### 12.36 Path termination current data near-end threshold reset – VC4 TTP SinkR1 + +``` +pathTerminationCurrentDataNearEndTR-vc4TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataNearEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc4TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 54}; +``` + +### 12.37 Path termination current data near-end threshold reset – VC3 TTP SinkR1 + +``` +pathTerminationCurrentDataNearEndTR-vc3TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataNearEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc3TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 55}; +``` + +### 12.38 Path termination current data near-end threshold reset – VC2 TTP SinkR1 + +``` +pathTerminationCurrentDataNearEndTR-vc2TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataNearEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc2TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 56}; +``` + +### 12.39 Path termination current data near-end threshold reset – VC12 TTP SinkR1 + +``` +pathTerminationCurrentDataNearEndTR-vc12TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataNearEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc12TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 57}; +``` + +### 12.40 Path termination current data near-end threshold reset – VC11 TTP SinkR1 + +``` +pathTerminationCurrentDataNearEndTR-vc11TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataNearEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc11TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 58}; +``` + +### 12.41 Path termination current data far-end – VC4 TTP SinkR1 + +``` +pathTerminationCurrentDataFarEnd-vc4TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataFarEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc4TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 59}; +``` + +### 12.42 Path termination current data far-end – VC3 TTP SinkR1 + +``` +pathTerminationCurrentDataFarEnd-vc3TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataFarEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc3TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 60}; +``` + +### 12.43 Path termination current data far-end – VC2 TTP SinkR1 + +``` +pathTerminationCurrentDataFarEnd-vc2TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataFarEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc2TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 61}; +``` + +### 12.44 Path termination current data far-end – VC12 TTP SinkR1 + +``` +pathTerminationCurrentDataFarEnd-vc12TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataFarEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc12TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 62}; +``` + +### 12.45 Path termination current data far-end – VC11 TTP SinkR1 + +``` +pathTerminationCurrentDataFarEnd-vc11TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataFarEnd AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc11TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 63}; +``` + +### 12.46 Path termination current data far-end threshold reset – VC4 TTP SinkR1 + +``` +pathTerminationCurrentDataFarEndTR-vc4TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataFarEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc4TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 64}; +``` + +### 12.47 Path termination current data far-end threshold reset – VC3 TTP SinkR1 + +``` +pathTerminationCurrentDataFarEndTR-vc3TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataFarEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc3TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 65}; +``` + +### 12.48 Path termination current data far-end threshold reset – VC2 TTP SinkR1 + +``` +pathTerminationCurrentDataFarEndTR-vc2TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataFarEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc2TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 66}; +``` + +### 12.49 Path termination current data far-end threshold reset – VC12 TTP SinkR1 + +``` +pathTerminationCurrentDataFarEndTR-vc12TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataFarEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc12TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 67}; +``` + +### 12.50 Path termination current data far-end threshold reset – VC11 TTP SinkR1 + +``` +pathTerminationCurrentDataFarEndTR-vc11TTPSinkR1 NAME BINDING + SUBORDINATE OBJECT CLASS + pathTerminationCurrentDataFarEndTR AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774":vc11TTPSinkR1 AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 68}; +``` + +### 12.51 MS adaptation current data – AU4 CTP source + +``` +msAdaptationCurrentData-au4CTPSource NAME BINDING + SUBORDINATE OBJECT CLASS msAdaptationCurrentData AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774": au4CTPSource AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 93}; +``` + +### 12.52 MS adaptation current data – AU3 CTP source + +``` +msAdaptationCurrentData-au3CTPSource NAME BINDING + SUBORDINATE OBJECT CLASS msAdaptationCurrentData AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation G.774": au3CTPSource AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.739": scannerId; + CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + DELETES-CONTAINED-OBJECTS; +REGISTERED AS {g774-6NameBinding 94}; +``` + +## 13 Subordination rules + +None. + +## 14 Pointer constraints + +None. + +## 15 Supporting ASN.1 productions + +``` +SDHPMUNIASN1 {itu-t(0) recommendation(0) g(7) g774(774) hyphen(127) pmUni(06) +informationModel(0) asn1Module(2) sdhpmUni (0)} +``` + +``` +DEFINITIONS IMPLICIT TAGS ::= +``` + +``` +BEGIN +``` + +``` +-- EXPORTS everything +``` + +``` +IMPORTS +``` + +``` +SDHGranularityPeriod, SDHPVGranularityPeriod FROM SDHPMASN1 {itu-t(0) +recommendation(0) g(7) g774(774) hyphen(127) pm(01) informationModel(0) +asn1Module(2) sdhpm (0)} +``` + +``` +TimePeriod FROM MetricModule {joint-iso-itu-t ms(9) function(2) part11(11) +asn1Module(2) 0}; +``` + +``` +sdhPMUni OBJECT IDENTIFIER ::= {itu-t(0) recommendation(0) g(7) g774(774) +hyphen(127) pmUni(06) informationModel(0)} +``` + +``` +g774-6MObjectClass OBJECT IDENTIFIER ::= {sdhPMUni managedObjectClass(3)} +``` + +``` +g774-6Attribute OBJECT IDENTIFIER ::= {sdhPMUni attribute(7)} +``` + +``` +g774-6NameBinding OBJECT IDENTIFIER ::= {sdhPMUni nameBinding(6)} +``` + +``` +g774-6Package OBJECT IDENTIFIER ::= {sdhPMUni package(4)} +``` + +``` + +sdhPM OBJECT IDENTIFIER ::= {itu-t(0) recommendation(0) g(7) g774(774) +hyphen(127) pm(01) informationModel(0) } +g774-01MObjectClass OBJECT IDENTIFIER ::= {sdhPM managedObjectClass(3)} +g774-01Attribute OBJECT IDENTIFIER ::= {sdhPM attribute(7)} +g774-01NameBinding OBJECT IDENTIFIER ::= {sdhPM nameBinding(6)} +g774-01Package OBJECT IDENTIFIER ::= {sdhPM package(4)} + +``` + +END -- end of SDHPMUNIASN1 + +# APPENDIX I + +### Naming and inheritance diagrams + +The naming and inheritance trees cover only the managed object classes of this Recommendation (see Figures I.1, I.2, I.3, I.4 and I.5). + +![Object name binding diagram for unidirectional performance monitoring. The diagram shows a hierarchy starting with 'sdh NE' at the top. It branches into 'rs TTP Sink', 'au3 CTP Source', and 'au4 CTP Source'. 'rs TTP Sink' branches into 'rs Current Data' and 'rs Current Data TR', which further branch into 'rs History Data'. 'au3 CTP Source' and 'au4 CTP Source' both lead to a common node 'ms Adaptation Current Data', which then branches into 'ms Adaptation History Data'.](b44f89b176c971c7dd264c07bfef2c2a_img.jpg) + +``` + +graph TD + sdhNE[sdh NE] --> rsTTPSink[rs TTP Sink] + sdhNE --> au3CTPSource[au3 CTP Source] + sdhNE --> au4CTPSource[au4 CTP Source] + rsTTPSink --> rsCurrentData[rs Current Data] + rsTTPSink --> rsCurrentDataTR[rs Current Data TR] + rsCurrentData --> rsHistoryData1[rs History Data] + rsCurrentDataTR --> rsHistoryData2[rs History Data] + au3CTPSource --> msAdaptationCurrentData[ms Adaptation Current Data] + au4CTPSource --> msAdaptationCurrentData + msAdaptationCurrentData --> msAdaptationHistoryData[ms Adaptation History Data] + +``` + +T1542260-00 + +Object name binding diagram for unidirectional performance monitoring. The diagram shows a hierarchy starting with 'sdh NE' at the top. It branches into 'rs TTP Sink', 'au3 CTP Source', and 'au4 CTP Source'. 'rs TTP Sink' branches into 'rs Current Data' and 'rs Current Data TR', which further branch into 'rs History Data'. 'au3 CTP Source' and 'au4 CTP Source' both lead to a common node 'ms Adaptation Current Data', which then branches into 'ms Adaptation History Data'. + +**Figure I.1/G.774.6 – Object name binding for the unidirectional performance monitoring** + +![Object name binding hierarchy for unidirectional performance monitoring (Figure I.2/G.774.6).](c1df61cc3717e878a48e530218403403_img.jpg) + +``` + +graph TD + sdhNE[sdhNE] --- msTPPSink[msTPPSink] + msTPPSink --- msCDNE[msCurrentData +NearEnd] + msTPPSink --- msCDNETR[msCurrentData +NearEndTR] + msTPPSink --- msCDFE[msCurrentData +FarEnd] + msTPPSink --- msCDFETR[msCurrentData +FarEndTR] + msCDNE --- msHDNE[msHistoryData +NearEnd] + msCDNETR --- msHDNETR[msHistoryData +NearEnd] + msCDFE --- msHDFE[msHistoryData +FarEnd] + msCDFETR --- msHDFETR[msHistoryData +FarEnd] + sdhNE --- vc4[vc4TTPSinkR1] + sdhNE --- vc3[vc3TTPSinkR1] + sdhNE --- vc2[vc2TTPSinkR1] + sdhNE --- vs12[vs12TTPSinkR1] + sdhNE --- vc11[vc11TTPSinkR1] + vc4 --- ptCDNE[pathTermination +CurrentData +NearEnd] + vc3 --- ptCDNETR[pathTermination +CurrentData +NearEndTR] + vc2 --- ptCDFE[pathTermination +CurrentData +FarEnd] + vs12 --- ptCDFETR[pathTermination +CurrentData +FarEndTR] + vc11 --- ptCDNE + vc11 --- ptCDNETR + vc11 --- ptCDFE + vc11 --- ptCDFETR + ptCDNE --- ptHDNE[pathTermination +HistoryData +NearEnd] + ptCDNETR --- ptHDNETR[pathTermination +HistoryData +NearEnd] + ptCDFE --- ptHDFE[pathTermination +HistoryData +FarEnd] + ptCDFETR --- ptHDFETR[pathTermination +HistoryData +FarEnd] + +``` + +T1526740-97 + +Object name binding hierarchy for unidirectional performance monitoring (Figure I.2/G.774.6). + +**Figure I.2/G.774.6 – Object name binding for the unidirectional performance monitoring** + +![Object name binding hierarchy for unidirectional performance monitoring (Figure I.3/G.774.6).](41aef1f5efab13d4f38f69e86c726062_img.jpg) + +``` + +graph TD + sdhNE[sdhNE] --- au4[au4 +Supervised +CTPSinkR1] + sdhNE --- au3[au3 +Supervised +CTPSinkR1] + sdhNE --- tu3[tu3 +Supervised +CTPSinkR1] + sdhNE --- tu2[tu2 +Supervised +CTPSinkR1] + sdhNE --- tu12[tu12 +Supervised +CTPSinkR1] + sdhNE --- tu11[tu11 +Supervised +CTPSinkR1] + au4 --- ptCDNE[pathTermination +CurrentData +NearEnd] + au3 --- ptCDNETR[pathTermination +CurrentData +NearEndTR] + tu3 --- ptCDFE[pathTermination +CurrentData +FarEnd] + tu2 --- ptCDFETR[pathTermination +CurrentData +FarEndTR] + tu12 --- ptCDNE + tu12 --- ptCDNETR + tu12 --- ptCDFE + tu12 --- ptCDFETR + tu11 --- ptCDNE + tu11 --- ptCDNETR + tu11 --- ptCDFE + tu11 --- ptCDFETR + ptCDNE --- ptHDNE[pathTermination +HistoryData +NearEnd] + ptCDNETR --- ptHDNETR[pathTermination +HistoryData +NearEnd] + ptCDFE --- ptHDFE[pathTermination +HistoryData +FarEnd] + ptCDFETR --- ptHDFETR[pathTermination +HistoryData +FarEnd] + +``` + +T1526750-97 + +Object name binding hierarchy for unidirectional performance monitoring (Figure I.3/G.774.6). + +**Figure I.3/G.774.6 – Object name binding for the unidirectional performance monitoring** + +![Object name binding diagram for unidirectional performance monitoring. It shows a hierarchy starting with 'sdhNE' at the top, branching into five 'vc' (Virtual Concatenation) nodes: 'vc4TTPSinkR1', 'vc3TTPSinkR1', 'vc2TTPSinkR1', 'vc12TTPSinkR1', and 'vc11TTPSinkR1'. Each 'vc' node branches into four 'pathTermination' nodes representing different data types and ends: 'pathTermination CurrentData NearEnd', 'pathTermination CurrentData NearEndTR', 'pathTermination CurrentData FarEnd', and 'pathTermination CurrentData FarEndTR'. Each of these further branches into a corresponding 'pathTermination HistoryData' node with the same end specifications.](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +``` + +graph TD + sdhNE[sdhNE] --> vc4[vc4TTPSinkR1] + sdhNE --> vc3[vc3TTPSinkR1] + sdhNE --> vc2[vc2TTPSinkR1] + sdhNE --> vc12[vc12TTPSinkR1] + sdhNE --> vc11[vc11TTPSinkR1] + vc4 --> pt4_1[pathTermination CurrentData NearEnd] + vc4 --> pt4_2[pathTermination CurrentData NearEndTR] + vc4 --> pt4_3[pathTermination CurrentData FarEnd] + vc4 --> pt4_4[pathTermination CurrentData FarEndTR] + vc3 --> pt3_1[pathTermination CurrentData NearEnd] + vc3 --> pt3_2[pathTermination CurrentData NearEndTR] + vc3 --> pt3_3[pathTermination CurrentData FarEnd] + vc3 --> pt3_4[pathTermination CurrentData FarEndTR] + vc2 --> pt2_1[pathTermination CurrentData NearEnd] + vc2 --> pt2_2[pathTermination CurrentData NearEndTR] + vc2 --> pt2_3[pathTermination CurrentData FarEnd] + vc2 --> pt2_4[pathTermination CurrentData FarEndTR] + vc12 --> pt12_1[pathTermination CurrentData NearEnd] + vc12 --> pt12_2[pathTermination CurrentData NearEndTR] + vc12 --> pt12_3[pathTermination CurrentData FarEnd] + vc12 --> pt12_4[pathTermination CurrentData FarEndTR] + vc11 --> pt11_1[pathTermination CurrentData NearEnd] + vc11 --> pt11_2[pathTermination CurrentData NearEndTR] + vc11 --> pt11_3[pathTermination CurrentData FarEnd] + vc11 --> pt11_4[pathTermination CurrentData FarEndTR] + pt4_1 --> ph4_1[pathTermination HistoryData NearEnd] + pt4_2 --> ph4_2[pathTermination HistoryData NearEnd] + pt4_3 --> ph4_3[pathTermination HistoryData FarEnd] + pt4_4 --> ph4_4[pathTermination HistoryData FarEnd] + pt3_1 --> ph3_1[pathTermination HistoryData NearEnd] + pt3_2 --> ph3_2[pathTermination HistoryData NearEnd] + pt3_3 --> ph3_3[pathTermination HistoryData FarEnd] + pt3_4 --> ph3_4[pathTermination HistoryData FarEnd] + pt2_1 --> ph2_1[pathTermination HistoryData NearEnd] + pt2_2 --> ph2_2[pathTermination HistoryData NearEnd] + pt2_3 --> ph2_3[pathTermination HistoryData FarEnd] + pt2_4 --> ph2_4[pathTermination HistoryData FarEnd] + pt12_1 --> ph12_1[pathTermination HistoryData NearEnd] + pt12_2 --> ph12_2[pathTermination HistoryData NearEnd] + pt12_3 --> ph12_3[pathTermination HistoryData FarEnd] + pt12_4 --> ph12_4[pathTermination HistoryData FarEnd] + pt11_1 --> ph11_1[pathTermination HistoryData NearEnd] + pt11_2 --> ph11_2[pathTermination HistoryData NearEnd] + pt11_3 --> ph11_3[pathTermination HistoryData FarEnd] + pt11_4 --> ph11_4[pathTermination HistoryData FarEnd] + +``` + +Object name binding diagram for unidirectional performance monitoring. It shows a hierarchy starting with 'sdhNE' at the top, branching into five 'vc' (Virtual Concatenation) nodes: 'vc4TTPSinkR1', 'vc3TTPSinkR1', 'vc2TTPSinkR1', 'vc12TTPSinkR1', and 'vc11TTPSinkR1'. Each 'vc' node branches into four 'pathTermination' nodes representing different data types and ends: 'pathTermination CurrentData NearEnd', 'pathTermination CurrentData NearEndTR', 'pathTermination CurrentData FarEnd', and 'pathTermination CurrentData FarEndTR'. Each of these further branches into a corresponding 'pathTermination HistoryData' node with the same end specifications. + +T1526760-97 + +**Figure I.4/G.774.6 – Object name binding for the unidirectional performance monitoring** + +![Inheritance tree diagram for unidirectional performance monitoring. It starts with 'top' at the root, labeled X.721. It branches into 'scanner' (X.739), 'current Data' (Q.822), 'threshold Data' (Q.822), and 'history Data' (Q.822). 'scanner' leads to 'current Data'. 'current Data' leads to 'sdh Current Data Unidirectional'. 'threshold Data' and 'history Data' both lead to a common set of nodes: 'rs Current Data', 'rs History Data', 'ms Current Data Near End', 'ms History Data Near End', 'ms Current Data Near End TR', 'ms History Data Far End', 'ms Current Data Far End', 'ms Adaptation Current Data', and 'ms Adaptation History Data'. 'sdh Current Data Unidirectional' leads to a list of 'path Termination' nodes: 'path Termination Current Data Near End', 'path Termination Current Data Near End TR', 'path Termination Current Data Far End', and 'path Termination Current Data Far End TR'. These are connected to the 'rs' and 'ms' nodes. 'history Data' also leads to 'path Termination History Data Near End' and 'path Termination History Data Far End'.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` + +graph TD + top[top] -- X.721 --> scanner[scanner] + top -- X.721 --> currentData[current Data] + top -- X.721 --> thresholdData[threshold Data] + top -- X.721 --> historyData[history Data] + scanner -- X.739 --> currentData + currentData -- Q.822 --> sdhCurrentDataUnidirectional[sdh Current Data Unidirectional] + thresholdData -- Q.822 --> rsCD[rs Current Data] + thresholdData -- Q.822 --> rsHD[rs History Data] + thresholdData -- Q.822 --> msCDNE[ms Current Data Near End] + thresholdData -- Q.822 --> msHDNE[ms History Data Near End] + thresholdData -- Q.822 --> msCDNETR[ms Current Data Near End TR] + thresholdData -- Q.822 --> msHDFE[ms History Data Far End] + thresholdData -- Q.822 --> msCDFE[ms Current Data Far End] + thresholdData -- Q.822 --> msADCD[ms Adaptation Current Data] + thresholdData -- Q.822 --> msADHD[ms Adaptation History Data] + historyData -- Q.822 --> ptHDNE[path Termination History Data Near End] + historyData -- Q.822 --> ptHDFE[path Termination History Data Far End] + sdhCurrentDataUnidirectional --> ptCDNE[path Termination Current Data Near End] + sdhCurrentDataUnidirectional --> ptCDNETR[path Termination Current Data Near End TR] + sdhCurrentDataUnidirectional --> ptCDFE[path Termination Current Data Far End] + sdhCurrentDataUnidirectional --> ptCDNETRTR[path Termination Current Data Far End TR] + ptCDNE --- rsCD + ptCDNETR --- rsCDNETR + ptCDFE --- msCDNE + ptCDNETRTR --- msCDNETR + ptCDNE --- msCDNE + ptCDNETR --- msCDNETR + ptCDFE --- msCDFE + ptCDNETRTR --- msADCD + +``` + +Inheritance tree diagram for unidirectional performance monitoring. It starts with 'top' at the root, labeled X.721. It branches into 'scanner' (X.739), 'current Data' (Q.822), 'threshold Data' (Q.822), and 'history Data' (Q.822). 'scanner' leads to 'current Data'. 'current Data' leads to 'sdh Current Data Unidirectional'. 'threshold Data' and 'history Data' both lead to a common set of nodes: 'rs Current Data', 'rs History Data', 'ms Current Data Near End', 'ms History Data Near End', 'ms Current Data Near End TR', 'ms History Data Far End', 'ms Current Data Far End', 'ms Adaptation Current Data', and 'ms Adaptation History Data'. 'sdh Current Data Unidirectional' leads to a list of 'path Termination' nodes: 'path Termination Current Data Near End', 'path Termination Current Data Near End TR', 'path Termination Current Data Far End', and 'path Termination Current Data Far End TR'. These are connected to the 'rs' and 'ms' nodes. 'history Data' also leads to 'path Termination History Data Near End' and 'path Termination History Data Far End'. + +T1542270-00 + +**Figure I.5/G.774.6 – Inheritance tree for the unidirectional performance monitoring** + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/G/T-REC-G.784-200803-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/G/T-REC-G.784-200803-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/G/T-REC-G.784-200803-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f24b214263bab4142643453a604fb5196f9397e2500c675cde79d53ce5e5d8e +size 3645 diff --git a/marked/G/T-REC-G.784-200803-I_PDF-E/34b047489058d6400b412cd0ae2334ba_img.jpg b/marked/G/T-REC-G.784-200803-I_PDF-E/34b047489058d6400b412cd0ae2334ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..404e5ef688578977d5cd52b37e8edcc4164949f9 --- /dev/null +++ b/marked/G/T-REC-G.784-200803-I_PDF-E/34b047489058d6400b412cd0ae2334ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4707d380ced3f552c5d60ede639a50d0a2e67fdc5833e1f091d1991a516d2ac4 +size 45882 diff --git a/marked/G/T-REC-G.784-200803-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg b/marked/G/T-REC-G.784-200803-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b6719d0b0280117322344fa4c7db340cc1999cf --- /dev/null +++ b/marked/G/T-REC-G.784-200803-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0de687d9fff7358f6ae59fddd79518b79f2ae822bd11775b98cce384d2ac4b9a +size 11083 diff --git a/marked/G/T-REC-G.784-200803-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/G/T-REC-G.784-200803-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b26a15fd116caef699fe760864ad4429af61ffd1 --- /dev/null +++ b/marked/G/T-REC-G.784-200803-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4339028702d69d51e3ce13b6134c6efd704d07eb5a2070ab59c4328d322a9b5 +size 120227 diff --git a/marked/G/T-REC-G.784-200803-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/G/T-REC-G.784-200803-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5cfbad89705090d91f4c481955347f7e2b536ab --- /dev/null +++ b/marked/G/T-REC-G.784-200803-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d8398ccef70af45452af7a2a50dd0a2d06b825fbcdb74f273bdfa7d28d10097 +size 161867 diff --git a/marked/G/T-REC-G.784-200803-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/G/T-REC-G.784-200803-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bcd7333b0b4cab180508a81640f68754b43091a --- /dev/null +++ b/marked/G/T-REC-G.784-200803-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ba8e7097a9c85e5a973ee8fd5dcd5a21103c128f239460513dbb620fc5a3bd4 +size 167466 diff --git a/marked/G/T-REC-G.784-200803-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg b/marked/G/T-REC-G.784-200803-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61ef10d2ce23ac908ac4e35d14764d3796b1c6f1 --- /dev/null +++ b/marked/G/T-REC-G.784-200803-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:837cdef3680d93542ac86f43d89b42051dc302c4c9bb62b986ace7ce5339228f +size 12029 diff --git a/marked/G/T-REC-G.784-200803-I_PDF-E/raw.md b/marked/G/T-REC-G.784-200803-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..26d82a33d282f2282eb5753bf4d841df9fb403d9 --- /dev/null +++ b/marked/G/T-REC-G.784-200803-I_PDF-E/raw.md @@ -0,0 +1,1599 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.784** + +(03/2008) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital terminal equipments – Principal characteristics of +multiplexing equipment for the synchronous digital +hierarchy + +# --- **Management aspects of synchronous digital hierarchy (SDH) transport network elements** + +Recommendation ITU-T G.784 + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600–G.699 | +| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 | +| General | G.700–G.709 | +| Coding of analogue signals | G.710–G.729 | +| Principal characteristics of primary multiplex equipment | G.730–G.739 | +| Principal characteristics of second order multiplex equipment | G.740–G.749 | +| Principal characteristics of higher order multiplex equipment | G.750–G.759 | +| Principal characteristics of transcoder and digital multiplication equipment | G.760–G.769 | +| Operations, administration and maintenance features of transmission equipment | G.770–G.779 | +| Principal characteristics of multiplexing equipment for the synchronous digital hierarchy | G.780–G.789 | +| Other terminal equipment | G.790–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | +| 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.784** + +# **Management aspects of synchronous digital hierarchy (SDH) transport network elements** + +## **Summary** + +Recommendation ITU-T G.784 addresses management aspects of synchronous digital hierarchy (SDH) network elements containing transport functions of one or more of the layer networks of the SDH transport network. The management of the SDH layer networks is separable from that of its client layer networks so that the same means of management can be used regardless of the client. The management functions for fault management, configuration management and performance monitoring are specified. + +The 2008 revision of this Recommendation has updated the management information to align with Recommendations ITU-T G.783, ITU-T G.781 and ITU-T G.7712/Y.1703, reorganized the clauses to align with the structure of Recommendation ITU-T G.7710/Y.1701, and replaced the generic text with pointers to Recommendation ITU-T G.7710/Y.1701. + +## **Source** + +Recommendation ITU-T G.784 was approved on 29 March 2008 by ITU-T Study Group 15 (2005-2008) under Recommendation ITU-T A.8 procedure. + +## **Keywords** + +Alarm reporting control, configuration management function, degraded performance, equipment management function, fault management functions, management application function, message communications function, performance management, performance monitoring functions, persistency, severity, thresholding. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|------|-----------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 3 | +| 3.1 | Terms defined elsewhere ..... | 3 | +| 3.2 | Terms defined in this Recommendation..... | 4 | +| 4 | Abbreviations and acronyms ..... | 5 | +| 5 | Conventions ..... | 10 | +| 6 | SDH management..... | 10 | +| 6.1 | SDH network management architecture..... | 10 | +| 6.2 | Synchronous equipment management function..... | 13 | +| 6.3 | Information flows over management points (MPs)..... | 14 | +| 7 | Fault (maintenance) management..... | 15 | +| 7.1 | Fault management applications ..... | 15 | +| 7.2 | Fault management functions..... | 17 | +| 8 | Configuration management ..... | 22 | +| 8.1 | Hardware ..... | 22 | +| 8.2 | Software..... | 22 | +| 8.3 | Protection switching ..... | 22 | +| 8.4 | Trail termination..... | 24 | +| 8.5 | Adaptation ..... | 25 | +| 8.6 | Connection..... | 26 | +| 8.7 | EXC/DEG thresholds ..... | 28 | +| 8.8 | Port mode and TP mode ..... | 28 | +| 8.9 | XXX_Reported..... | 29 | +| 8.10 | Alarm severity ..... | 29 | +| 8.11 | Alarm reporting control (ARC) ..... | 29 | +| 8.12 | PM thresholds..... | 29 | +| 8.13 | TCM activation..... | 29 | +| 8.14 | Synchronization provisioning and reporting ..... | 29 | +| 8.15 | Date and time..... | 29 | +| 9 | Account management ..... | 30 | +| 10 | Performance management ..... | 30 | +| 10.1 | Performance management applications ..... | 30 | +| 10.2 | Performance monitoring functions ..... | 36 | +| 11 | Security management..... | 36 | + +| | Page | +|---------------------------------------------------------------------------------|-------------| +| Annex A – Definitions of errored seconds types A and B and failure counts ..... | 37 | +| A.1    Introduction ..... | 37 | +| A.2    Errored seconds types A and B ..... | 37 | +| A.3    Failure counts ..... | 38 | +| Appendix I – Management information for CM ..... | 39 | +| Appendix II – Management information for PM ..... | 40 | + +# Management aspects of synchronous digital hierarchy (SDH) transport network elements + +# 1 Scope + +This Recommendation addresses management aspects of synchronous digital hierarchy (SDH) network elements containing transport functions of one or more of the layer networks of the SDH transport network. The management of the SDH layer networks is separable from that of its client layer networks so that the same means of management can be used regardless of the client. The management functions for fault management, configuration management and performance monitoring are specified. + +This Recommendation describes the management network organizational model for communication between an element management layer (EML) operations system and the SDH equipment management function within an SDH network element. + +The architecture described in this Recommendation for the management of SDH transport networks is based upon the following considerations: + +- SDH layer network entities (SLNEs) refer to trail termination, adaptation and connection functions as described in [ITU-T G.803], +- a network element may only contain SDH layer network entities, +- a network element may contain both SDH layer network entities (SLNEs) and client layer network entities (CLNEs), +- client layer entities are managed as part of their own logical domain (e.g., PDH management network), +- CLNEs and SLNEs may or may not share common message communications function (MCF) and management application function (MAF) depending on application, +- CLNEs and OLNEs may or may not share the same agent. + +The SDH management subnetwork (S.MSN) architecture, SDH embedded control channel (ECC) functions, and SDH ECC protocols are specified. Detailed message sets are for further study. + +The management of SDH equipment should be seen as a subset of the telecommunications management network (TMN) described in [ITU-T M.3000], and reference is made to [ITU-T Q.811] and [ITU-T Q.812] for the specification of protocol suites to be used at external (Q) management interfaces. + +This Recommendation specifies for fault management, performance monitoring and configuration management a library of basic equipment management function (EMF) building blocks and a set of rules by which they are combined in order to describe a digital transmission equipment's EMF functionality. The library defined in this Recommendation forms part of the set of libraries defined furthermore in [ITU-T G.783]. + +Not every function defined in this Recommendation is required for every application. Different subsets of functions may be assembled in different ways to provide a variety of different capabilities. Network operators and equipment suppliers may choose which functions must be implemented for each application. + +# 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.707] Recommendation ITU-T G.707/Y.1322 (2007), *Network node interface for the synchronous digital hierarchy (SDH)*. +- [ITU-T G.774] Recommendation ITU-T G.774 (1992), *Synchronous digital hierarchy (SDH) – Management information model for the network element view*. +- [ITU-T G.774.1] Recommendation ITU-T G.774.1 (2001), *Synchronous digital hierarchy (SDH) – Bidirectional performance monitoring for the network element view*. +- [ITU-T G.774.6] Recommendation ITU-T G.774.6 (1997), *Synchronous digital hierarchy (SDH) unidirectional performance monitoring for the network element view*. +- [ITU-T G.781] Recommendation ITU-T G.781 (1999), *Synchronization layer functions*. +- [ITU-T G.783] Recommendation ITU-T G.783 (2006), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks*. +- [ITU-T G.803] Recommendation ITU-T G.803 (2000), *Architecture of transport networks based on the synchronous digital hierarchy (SDH)*. +- [ITU-T G.805] Recommendation ITU-T G.805 (2000), *Generic functional architecture of transport networks*. +- [ITU-T G.806] Recommendation ITU-T G.806 (2006), *Characteristics of transport equipment – Description methodology and generic functionality*. +- [ITU-T G.826] Recommendation ITU-T G.826 (2002), *End-to-end error performance parameters and objectives for international, constant bit-rate digital paths and connections*. +- [ITU-T G.827] Recommendation ITU-T G.827 (2003), *Availability performance parameters and objectives for end-to-end international constant bit-rate digital paths*. +- [ITU-T G.7710] Recommendation ITU-T G.7710/Y.1701 (2007), *Common equipment management function requirements*. +- [ITU-T G.7712] Recommendation ITU-T G.7712/Y.1703 (2003), *Architecture and specification of data communication network*. +- [ITU-T G.7714] Recommendation ITU-T G.7714/Y.1705 (2005), *Generalized automatic discovery for transport entities*. +- [ITU-T G.7714.1] Recommendation ITU-T G.7714.1/Y.1705.1 (2003), *Protocol for automatic discovery in SDH and OTN networks*. +- [ITU-T M.20] Recommendation ITU-T M.20 (1992), *Maintenance philosophy for telecommunication networks*. +- [ITU-T M.2100] Recommendation ITU-T M.2100 (2003), *Performance limits for bringing-into-service and maintenance of international multi-operator PDH paths and connections*. + +- [ITU-T M.2101] Recommendation ITU-T M.2101 (2003), *Performance limits for bringing-into-service and maintenance of international multi-operator SDH paths and multiplex sections.* +- [ITU-T M.2120] Recommendation ITU-T M.2120 (2002), *International multi-operator paths, sections and transmission systems fault detection and localization procedures.* +- [ITU-T M.2140] Recommendation ITU-T M.2140 (2000), *Transport network event correlation.* +- [ITU-T M.3000] Recommendation ITU-T M.3000 (2000), *Overview of TMN Recommendations.* +- [ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network.* +- [ITU-T M.3013] Recommendation ITU-T M.3013 (2000), *Considerations for a telecommunications management network.* +- [ITU-T M.3100] Recommendation ITU-T M.3100 (2005), *Generic network information model.* +- [ITU-T M.3300] Recommendation ITU-T M.3300 (1998), *TMN F interface requirements.* +- [ITU-T M.3400] Recommendation ITU-T M.3400 (2000), *TMN management functions.* +- [ITU-T Q.811] Recommendation ITU-T Q.811 (2004), *Lower layer protocol profiles for the Q and X interfaces.* +- [ITU-T Q.812] Recommendation ITU-T Q.812 (2004), *Upper layer protocol profiles for the Q and X interfaces.* +- [ITU-T X.700] Recommendation ITU-T X.700 (1992), *Management framework for Open Systems Interconnection (OSI) For CCITT applications.* +- [ITU-T X.701] Recommendation ITU-T X.701 (1997) | ISO/IEC 10040:1998, *Information technology – Open Systems Interconnection – Systems management overview.* +- [ITU-T X.733] Recommendation ITU-T X.733 (1992) | ISO/IEC 10164-4:1992, *Information technology – Open Systems Interconnection – Systems Management: Alarm reporting function.* +- [ITU-T X.735] Recommendation ITU-T X.735 (1992) | ISO/IEC 10164-6:1993, *Information technology – Open Systems Interconnection – Systems Management: Log control function.* +- [ITU-T X.744] Recommendation ITU-T X.744 (1996) | ISO/IEC 10164-18:1997, *Information technology – Open Systems Interconnection – Systems Management: Software management function.* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent:** [ITU-T X.701] + +**3.1.2 alarm reporting:** [ITU-T M.3100] + +- 3.1.3 **alarm reporting control:** [ITU-T M.3100] +- 3.1.4 **atomic function (AF):** [ITU-T G.806] +- 3.1.5 **data communication channel (DCC):** [ITU-T G.707] +- 3.1.6 **data communication network (DCN):** [ITU-T G.7712] +- 3.1.7 **embedded control channel (ECC):** [ITU-T G.7712] +- 3.1.8 **F interface:** [ITU-T M.3300] +- 3.1.9 **local craft terminal:** [ITU-T G.7710] +- 3.1.10 **managed entity:** [ITU-T M.3100] +- 3.1.11 **managed object (MO):** [ITU-T X.700] +- 3.1.12 **managed object class (MOC):** [ITU-T X.701] +- 3.1.13 **management application function (MAF):** [ITU-T G.7710] +- 3.1.14 **management interface:** [ITU-T M.3100] +- 3.1.15 **management point (MP):** [ITU-T G.806] +- 3.1.16 **manager:** [ITU-T X.701] +- 3.1.17 **message communications function (MCF):** [ITU-T M.3013] +- 3.1.18 **network element (NE):** [ITU-T M.3010] +- 3.1.19 **network element function (NEF):** [ITU-T M.3010] +- 3.1.20 **operations system (OS):** [ITU-T M.3010] +- 3.1.21 **persistence interval:** [ITU-T M.3100] +- 3.1.22 **Q interface:** [ITU-T M.3010] +- 3.1.23 **qualified problem:** [ITU-T M.3100] +- 3.1.24 **reset threshold report:** [ITU-T M.3100] +- 3.1.25 **SDH management network (S.MN):** [ITU-T G.780] +- 3.1.26 **SDH management subnetwork (S.MSN):** [ITU-T G.780] +- 3.1.27 **SDH network element (S.NE):** [ITU-T G.780] +- 3.1.28 **threshold report:** [ITU-T M.3100] +- 3.1.29 **timed interval:** [ITU-T M.3100] +- 3.1.30 **workstation function (WF):** [ITU-T M.3010] + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 agent:** Part of the MAF which is capable of responding to network management operations issued by a manager and may perform operations on managed objects, issuing events on behalf of managed objects. The managed objects can reside within the entity or in another open system. Managed objects from other open systems are controlled by a distant agent via a local manager. All S.NEs will support at least an agent. Some S.NEs will provide managers and agents (being managed). Some S.NEs (e.g., regenerators) will only support an agent. + +**3.2.2 data communication channel (DCC):** Within an STM-N signal there are two DCC channels, comprising bytes D1-D3, giving a 192 kbit/s channel, and bytes D4-D12, giving a + +576 kbit/s channel. D1-D3 (DCCR) are accessible by all S.NEs whereas D4-D12 (DCCM), not being part of the regenerator section overhead, are not accessible at regenerators. It is recommended to have both DCCM and DCCR available in backbone STM-16 (and higher order) network sections. DCCM is used to forward data over the multiplex sections (using the OSI-routing protocols), and DCCR is used to forward data to the regenerators within the destination MS span. DCCM can be regarded as the backbone, while DCCR and LAN are used to interconnect this backbone to equipment that cannot be accessed through DCCM, e.g., regenerators and non-SDH equipment. + +DCCM and DCCR can be used to carry two independent, possibly proprietary management applications. An S.NE can choose to throughconnect DCCM on the physical level, or to terminate the DCCM and route the PDUs, while using the DCCR for interconnection within a subnetwork. + +**3.2.3 managed object (MO):** The management view of a resource within the telecommunication environment that may be managed via the agent. Examples of SDH managed objects are: equipment, receive port, transmit port, power supply, plug-in card, virtual container, multiplex section and regenerator section. + +**3.2.4 manager:** Part of the MAF which is capable of issuing network management operations (i.e., retrieve alarm records, set thresholds) and receiving events (i.e., alarms, performance). S.NEs may or may not include a manager while SDH OS/MDs will include at least one manager. + +**3.2.5 operations system function or mediation function (OSF/MF):** A telecommunications management network (TMN) entity that processes management information to monitor and control the SDH network. In the SDH sub-portion of the TMN, no distinction is made between the operations system function and the mediation function; this entity being a MAF containing at least a manager. + +**3.2.6 operations system or mediation device (OS/MD):** A stand-alone physical entity that supports OSF/MFs but does not support NEFs. It contains a message communication function (MCF) and a MAF. + +**3.2.7 trail segment:** A segment for which one end is a trail termination. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations: + +| | | +|------|-------------------------------------------| +| A | Agent | +| ACSE | Association Control Service Element | +| AcSL | Accepted Signal Label | +| AcTI | Accepted Trace Identifier | +| AF | Application Function | +| AF | Atomic Function | +| AIS | Alarm Indication Signal | +| AITS | Acknowledged Information Transfer Service | +| ALM | ALarM reporting | +| AP | Access Point | +| APDU | Application Protocol Data Unit | +| API | Access Point Identifier | +| APS | Automatic Protection Switching | + +| | | +|-------|-----------------------------------------------------------------------| +| ARC | Alarm Reporting Control | +| ASE | Application Service Element | +| ASN.1 | Abstract Syntax Notation One | +| CC | Connect Confirm | +| CLNE | Client Layer Network Entity | +| CLNP | Connectionless Network layer Protocol | +| CLNS | Connectionless Network layer Service | +| CLR | Clear | +| CMIP | Common Management Information Protocol | +| CMISE | Common Management Information Service Element | +| CMSN | Client Management Subnetwork | +| CONP | Connection Oriented Network-Layer Protocol | +| CP | Connection Point | +| CR | Connection Request | +| CSES | Consecutive Severely Errored Seconds | +| CV | Code Violation | +| DCC | Data Communications Channel | +| DCN | Data Communication Network | +| DEG | Degraded detect | +| DS | Defect Second | +| EB | Errored Block | +| EBC | Errored Block Count | +| ECC | Embedded Control Channel | +| EMF | Equipment Management Function | +| EML | Equipment Management Layer | +| ES | Errored Second | +| ESA | Errored Seconds type A | +| ESB | Errored Seconds type B | +| EXC | Excessive errors | +| EXER | Exercise | +| ExTI | Expected Trace Identifier | +| FBBE | Far-end Background Block Error | +| FC | Failure Counts | +| FCAPS | Fault, Configuration, Accounting, Performance and Security management | +| FDS | Far-end Defect Second | +| FEBC | Far-end Errored Block Count | +| FEBE | Far-End Block Error | + +| | | +|----------|--------------------------------------| +| FES | Far-end Errored Second | +| FFS | For Further Study | +| FLS | Frame Loss Second | +| FOP | Failure of Protocol | +| FSES | Far-end Severely Errored Second | +| FPME | Far-end Performance Monitoring Event | +| FSW | Forced Switch | +| FU | Functional Unit | +| GNE | Gateway Network Element | +| HO | Hold Off | +| IFU | Interworking Functional Unit | +| IP | Interworking Protocol | +| IS | Intermediate System | +| LAD | Layer Adjacency Discovery | +| LAN | Local Area Network | +| LCN | Local Communications Network | +| LCT | Local Craft Terminal | +| LO | Lockout of protection | +| LOF | Loss of Frame | +| LOM | Loss of Multiframe | +| LOP | Loss of Pointer | +| LOS | Loss of Signal | +| LOW | Lockout of Working | +| LTC | Loss of Tandem Connection | +| M | Manager | +| MAF | Management Application Function | +| MAINTREG | MAINTenance REGisters | +| MCF | Message Communications Function | +| MD | Mediation Device | +| MF | Mediation Function | +| MI | Management Information | +| MIB | Management Information Base | +| MO | Managed Object | +| MOC | Managed Object Class | +| MP | Management Point | +| MS | Multiplex Section | +| MSOH | Multiplex Section Overhead | + +| | | +|---------|----------------------------------------------------------| +| MSW | Manual Switch | +| NALM | No ALaRm reporting | +| NALM-CD | No ALaRm reporting, CountDown | +| NALM-NR | No ALaRm reporting, NotReady | +| NALM-QI | No ALaRm reporting, Qualified Inhibit | +| NALM-TI | No ALaRm reporting, Timed Inhibit | +| NBBE | Near-end Background Block Error | +| NDS | Near-end Defect Second | +| NE | Network Element | +| NEBC | Near-end Errored Block Count | +| NEF | Network Element Function | +| NEL | Network Element Layer | +| NES | Near-end Errored Second | +| NLR | Network Layer Relay | +| NPDU | Network Protocol Data Unit | +| NPME | Near-end Performance Monitoring Event | +| NSAP | Network Service Access Point | +| NSES | Near-end Severely Errored Second | +| OAM&P | Operations, Administration, Maintenance and Provisioning | +| ODI | Outgoing Defect Indication | +| OEI | Outgoing Error Indication | +| OFS | Out-of-Frame Second | +| OH | Overhead | +| OOF | Out of Frame | +| OS | Operations System | +| OSF | Operations System Function | +| OSF | Outgoing Signal Fail | +| OSI | Open Systems Interconnection | +| P | Protection | +| PDH | Plesiochronous Digital Hierarchy | +| PDU | Protocol Data Unit | +| PERFREG | PERFormance REGisters | +| PJC | Pointer Justification Count | +| PJE | Pointer Justification Event | +| PLM | PayLoad Mismatch | +| PMC | Performance Monitoring Clock | +| PMON | Performance Monitoring | + +| | | +|--------|-------------------------------------------| +| PPDU | Presentation Protocol Data Unit | +| PSN | Packet Switched Network | +| QoS | Quality of Service | +| RDI | Remote Defect Indication | +| REI | Remote Error Indication | +| ROSE | Remote Operations Service Element | +| RS | Regenerator Section | +| RSOH | Regenerator Section Overhead | +| RTC | Real Time Clock | +| RTR | Reset Threshold Report | +| SAPI | Service Access Point Identifier | +| SD | Signal Degrade | +| SDH | Synchronous Digital Hierarchy | +| SEMF | Synchronous Equipment Management Function | +| SES | Severely Errored Second | +| SF | Signal Fail | +| SLNE | SDH Layer Network Entity | +| S.MN | SDH Management Network | +| S.MSN | SDH Management Subnetwork | +| SND CF | SubNetwork Dependent Convergence Function | +| S.NE | SDH Network Element | +| SPDU | Session Protocol Data Unit | +| SSD | Server Signal Degrade | +| SSF | Server Signal Fail | +| STM | Synchronous Transport Module | +| SVC | Switched Virtual Circuit | +| TCP | Termination Connection Point | +| TEI | Terminal End-point Identifier | +| TI | Trace Identifier | +| TIM | Trace Identifier Mismatch | +| TMN | Telecommunications Management Network | +| TP | Termination Point | +| TPDU | Transport Protocol Data Unit | +| TR | Threshold Report | +| TSAP | Transport Service Access Point | +| TSD | Trail Signal Degrade | +| TSF | Trail Signal Fail | + +| | | +|------|---------------------------------------------| +| TSN | Time Slot Number | +| TTI | Trail Trace Identifier | +| TTP | Trail Termination Point | +| TxTI | Transmitted Trace Identifier | +| UAS | Unavailable Second | +| UAT | UnAvailable Time | +| UI | Unnumbered Information | +| UITS | Unacknowledged Information Transfer Service | +| UTC | Coordinated Universal Time | +| VC | Virtual Container | +| W | Working | +| WAN | Wide Area Network | +| WS | WorkStation | +| WTR | Wait to Restore | + +# 5 Conventions + +In this Recommendation, S.MN stands for SDH management network, S.MSN for SDH management subnetwork, and S.NE for SDH network element. + +# 6 SDH management + +## 6.1 SDH network management architecture + +The transport layer networks of the SDH transport network are described in [ITU-T G.803] and [ITU-T G.707]. The management of the SDH layer networks is separable from that of their client layer networks so that the same means of management can be used regardless of the client. + +See clause 6 of [ITU-T G.7710] for the generic management architecture. + +![Figure 6-1 – SDH management examples. The diagram is divided into two parts, (a) and (b), showing different management architectures. Part (a) shows a direct management path from the OS to NE2 via MD and NE1. Part (b) shows a more complex path where the MD is nested within NE1. Both parts include internal component details like OS-AF, MD-AF, MO, MCF, A, and M, and a detailed view of the Q-interface protocol stack.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +**a)** Management architecture showing the OS connected to MD, MD connected to NE1, and NE1 connected to NE2 via "Q" Interfaces. The OS contains OS-AF, M, and MCF. The MD contains MD-AF, A, M, and MCF. NE1 contains MO, A, and MCF. NE2 contains MO, A, and MCF. A detailed view below shows the Q-interface protocol stack for each component, with connections labeled a, b, and c. + +**b)** Management architecture showing the OS connected to MD, MD connected to NE1 (containing MD-AF), and NE1 connected to NE2 via "Q" Interfaces. The OS contains OS-AF, M, and MCF. The MD contains MD-AF, A, M, and MCF. NE1 contains MO, MD-AF, A, M, and MCF. NE2 contains MO, A, and MCF. A detailed view below shows the Q-interface protocol stack for each component, with connections labeled c, d, and e. + +Figure 6-1 – SDH management examples. The diagram is divided into two parts, (a) and (b), showing different management architectures. Part (a) shows a direct management path from the OS to NE2 via MD and NE1. Part (b) shows a more complex path where the MD is nested within NE1. Both parts include internal component details like OS-AF, MD-AF, MO, MCF, A, and M, and a detailed view of the Q-interface protocol stack. + +- OS Operations system +- MD Mediation device +- NE Network element +- OS-AF OS-application function +- MD-AF MD-application function +- MCF Message communications function +- A Agent +- M Manager +- MO Managed object + +T1508850-92 + +**Figure 6-1 – SDH management examples** + +Figure 6-1a illustrates examples of management communication using a Q interface implemented in the MCF where logically independent communications are provided over a single physical interface: + +- between a manager in the OS and two different agents; one in the MD and one in NE2 (interface a); +- between a manager in the MD and an agent in NE1; between a manager in the OS and an agent in NE2 (interface b). + +Figure 6-1b illustrates examples of management communication using Q interface protocols implemented in the MCF: + +- between a manager in the OS and an agent in the MD (interface c); +- between a manager in the MD and an agent in NE1 (interface d); +- between a manager in NE1 and an agent in NE2 (interface e). + +### **6.1.1 Relationship between TMN, S.MN and S.MSN** + +The SDH management network (S.MN) may be partitioned into SDH management subnetworks (S.MSNs). The inter-relationship between a management network, its subnetworks and a TMN as generically described in clause 6.1 of [ITU-T G.7710] is applicable to OTN. + +#### **6.1.1.1 Operations interfaces** + +##### **6.1.1.1.1 Q interface** + +For interconnection with the TMN, the S.MSN will communicate through a Q interface having a protocol suite, CONS1, CLNS2 or CLNS1 as defined in [ITU-T Q.811] and [ITU-T Q.812]. The selection of which of the three protocol suites to adopt is a network provider's decision. + +##### **6.1.1.1.2 F interface** + +See [ITU-T M.3300]. + +The following subclauses describe the S.MSN in more detail. + +### **6.1.2 Access to the S.MSN** + +See clause 6.1.2 of [ITU-T G.7710] for the generic requirements. + +### **6.1.3 S.MSN requirements** + +See clause 6.1.3 of [ITU-T G.7710] for the generic requirements. + +In addition, the S.MSN allows for the support of the following: + +S.NEs must support management communications functions. The message communications function of an S.NE initiates/terminates (in the sense of the lower protocol layers), routes/forwards, or otherwise processes management messages over ECCs, or over other data communications network interfaces. + +- i) All S.NEs are required to terminate the ECC (see clause 6.1.5). In OSI terms, this means that each S.NE must be able to perform the functions of an end system. +- ii) S.NEs may also be required to forward management messages between ports according to routing control information held in the S.NE. In OSI terms, this means that some S.NEs may be required to perform the functions of an intermediate system. +- iii) In addition to supporting interfaces for the DCC, S.NEs may also be required to support DCN interfaces (Q and F interfaces). + +The use of the data communication channels (DCC) for management communications is within the scope of this Recommendation, see clause 6.1.5. + +### **6.1.4 S.MSN data communications network for SDH management** + +See clause 6.1.4 of [ITU-T G.7710] for the generic requirements. + +### **6.1.5 Management of DCN** + +See clause 6.1.5 of [ITU-T G.7710] for the generic requirements. + +### **6.1.6 Remote log-in** + +See clause 6.1.6 of [ITU-T G.7710] for the generic requirements. + +### **6.1.7 Relationship between technology domains** + +See clause 6.1.7 of [ITU-T G.7710] for the generic requirements. + +## **6.2 Synchronous equipment management function** + +This clause provides an overview of the minimum functions which are required to support inter-vendor/network communications and single-ended maintenance of S.NEs within an S.MSN, or between communicating peer S.NEs across a network interface. Single-ended maintenance is the ability to access remotely located S.NEs to perform maintenance functions (see [ITU-T G.7710] for performance management applications). + +It should be noted that the management functions have been categorized according to the classifications given in [ITU-T M.3000]. + +Detailed specifications of the management functions, in terms of managed objects classes, attributes and message specification, are given in ITU-T G.774.x-series Recommendations. + +The synchronous equipment management function SEMF (see Figure 6-2) provides the means through which the synchronous network element function (NEF) is managed by an internal or external manager. If a network element (NE) contains an internal manager, this manager will be part of the SEMF. + +The SEMF interacts with the other atomic functions (refer to [ITU-T G.783]) by exchanging information across the MP reference points. See [ITU-T G.806] and [ITU-T G.783] for more information on atomic functions and on management points. The SEMF contains a number of functions that provide a data reduction mechanism on the information received across the MP reference points. The outputs of these functions are available to the agent via the network element resources and management applications functions (MAFs) which represent this information as managed objects. + +![Figure 6-2 – Synchronous equipment management function. This block diagram shows the internal architecture of a Network element function (NEF). On the left, 'Transport plane atomic functions' and an 'Equipment control function' are shown. The 'Transport plane atomic functions' send 'Management information' to the central 'Equipment management function (EMF)'. The 'Equipment control function' sends 'Control information' to the EMF and receives 'Management information' from it. The EMF contains a stack of management functions: 'Date and time functions', 'Fault management', 'Configuration management', 'Account management', 'Performance management', and 'Security management'. To the right of these is the 'Management application function (MAF)', which includes 'Date and time interface', 'Management plane interface', 'Control plane interface', and 'Local alarm interface'. Below the management functions is a 'MIB' (Management information base) containing five 'Managed object' (MO) icons. An 'Agent' is shown between the MIB and the MAF. The EMF connects to the 'Message communication function (MCF)' on the right. The MCF contains 'Date and time communication', 'Management plane communication', 'Control plane communication', and 'Local alarm communication'. External connections include: 'From external time source' to Date and time communication; 'To/from management plane (e.g. EMS, peer NE)' to Management plane communication; 'To/from control plane (e.g. EMS, peer NE)' to Control plane communication; 'To/from local craft terminal' to Control plane communication; and 'To local alarms' to Local alarm communication. A legend at the bottom right defines the MIB as a blue cylinder and MO as a circle with 'MO' inside. The code 'G.784(08)_F6-2' is in the bottom right corner.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +Figure 6-2 – Synchronous equipment management function. This block diagram shows the internal architecture of a Network element function (NEF). On the left, 'Transport plane atomic functions' and an 'Equipment control function' are shown. The 'Transport plane atomic functions' send 'Management information' to the central 'Equipment management function (EMF)'. The 'Equipment control function' sends 'Control information' to the EMF and receives 'Management information' from it. The EMF contains a stack of management functions: 'Date and time functions', 'Fault management', 'Configuration management', 'Account management', 'Performance management', and 'Security management'. To the right of these is the 'Management application function (MAF)', which includes 'Date and time interface', 'Management plane interface', 'Control plane interface', and 'Local alarm interface'. Below the management functions is a 'MIB' (Management information base) containing five 'Managed object' (MO) icons. An 'Agent' is shown between the MIB and the MAF. The EMF connects to the 'Message communication function (MCF)' on the right. The MCF contains 'Date and time communication', 'Management plane communication', 'Control plane communication', and 'Local alarm communication'. External connections include: 'From external time source' to Date and time communication; 'To/from management plane (e.g. EMS, peer NE)' to Management plane communication; 'To/from control plane (e.g. EMS, peer NE)' to Control plane communication; 'To/from local craft terminal' to Control plane communication; and 'To local alarms' to Local alarm communication. A legend at the bottom right defines the MIB as a blue cylinder and MO as a circle with 'MO' inside. The code 'G.784(08)\_F6-2' is in the bottom right corner. + +**Figure 6-2 – Synchronous equipment management function** + +Network element resources provide event processing and storage. The MAF processes the information provided to and by the S.NE resources. The agent converts this information to management messages and responds to management messages from the manager by performing the appropriate operations on the managed objects. + +This information to and from the agent is passed across the V reference point to the message communications function (MCF). + +## 6.3 Information flows over management points (MPs) + +The information flows described in this clause are functional. The existence of these information flows in the equipment will depend on the functionality provided by the S.NE and the options selected. + +The information flow over the MP reference points that arises from anomalies and defects detected in the atomic functions is described in specific detail for each atomic function in [ITU-T G.783]. + +The information flow over the MP reference points that arises from configuration and provisioning data is described in specific detail for each atomic function in [ITU-T G.783]. The information listed under Set refers to configuration and provisioning data that is passed from the SEMF to the atomic functions. The information listed under Get refers to status reports made in response to a request from the SEMF for such information. + +As an example, we may consider the higher order path trace. The higher order path termination may be provisioned for the higher order path trace ID that it should expect by a "Set\_Rx\_HO\_path\_trace\_ID" command received from the manager. If the higher order path trace that is received does not match the expected higher order path trace, this will give rise to a report of + +a mismatch of the higher order path trace across the hp\_nm reference point. Having received this mismatch indication, the S.NE stores it for access by the manager. + +# **7 Fault (maintenance) management** + +Fault management is a set of functions which enables the detection, isolation and correction of abnormal operation of the telecommunication network and its environment. It provides facilities for the performance of the maintenance phases from [ITU-T M.20]. The quality assurance measurements for fault management include component measurements for reliability, availability and survivability. + +## **7.1 Fault management applications** + +See [ITU-T G.7710] for a description of the basic fault management applications. + +### **7.1.1 Supervision** + +The supervision process describes the way in which the actual occurrence of a disturbance or fault is analysed for the purpose of providing an appropriate indication of performance and/or detected fault condition to maintenance personnel. The supervision philosophy is based on the concepts underlying the functional model of [ITU-T G.805] and [ITU-T G.803] and the alarm reporting function of [ITU-T X.733]. + +The five basic supervision categories are related to transmission, quality of service, processing, equipment and environment. These supervision processes are able to declare fault causes, which need further validation before the appropriate alarm is reported. See [ITU-T G.7710] for additional discussion of these categories. + +The S.NE shall indicate to the OS when a termination point is no longer able to supervise the signal (e.g., implementing equipment has a fault or loss of power). + +#### **7.1.1.1 Transmission supervision** + +See [ITU-T G.7710] for a description of transmission supervision. + +#### **7.1.1.2 Quality of service supervision** + +See [ITU-T G.7710] for a description of quality of service supervision. + +#### **7.1.1.3 Processing supervision** + +See [ITU-T G.7710] for a description of processing supervision. + +#### **7.1.1.4 Equipment supervision** + +See [ITU-T G.7710] for a description of equipment supervision. + +#### **7.1.1.5 Environment supervision** + +See [ITU-T G.7710] for a description of environment supervision. + +### **7.1.2 Validation** + +See [ITU-T G.7710] for a description of fault cause validation. + +### **7.1.3 Alarm handling** + +#### **7.1.3.1 Severity Assignment** + +See [ITU-T G.7710] for a description of severity categories. + +#### **7.1.3.2 Alarm reporting control** + +Alarm reporting control (ARC) provides an automatic in-service provisioning capability. + +The following ARC states may be specified for a managed entity: + +| | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ALM | ALarM reporting; alarm reporting is turned on. | +| NALM | No ALarM reporting; alarm reporting is turned off. | +| NALM-CD | No ALarM reporting, CountDown; this is a sub-state of NALM-QI and performs the persistence timing countdown function when the managed entity is qualified problem free. | +| NALM-NR | No ALarM reporting, NotReady; this is a sub-state of NALM-QI and performs a wait function until the managed entity is qualified problem free. | +| NALM-QI | No ALarM reporting, Qualified Inhibit; alarm reporting is turned off until the managed entity is qualified problem free for a specified persistence interval. | +| NALM-TI | No ALarM reporting, Timed Inhibit; alarm reporting is turned off for a specified timed interval. | + +Alarm reporting may be turned off (using NALM, NALM-TI or NALM-QI) on a per-managed entity basis to allow sufficient time for customer testing and other maintenance activities in an "alarm free" state. Once a managed entity is ready, alarm reporting is automatically turned on (to ALM). The managed entity may be automatically turned on either by using NALM-TI or NALM-QI and allowing the resource to transition out automatically, or by invoking first the NALM state from an EMS and, when maintenance activity is done, invoking the ALM state. This later automation is carried out by the EMS. For further details relating to ARC, see [ITU-T M.3100]. + +#### 7.1.3.3 Reportable failures + +See [ITU-T G.7710] for a description of reportable failures. + +#### 7.1.3.4 Alarm reporting + +Alarm surveillance is concerned with the detection and reporting of relevant events and conditions which occur in the network. In a network, events and conditions detected within the equipment and incoming signals should be reportable. In addition, a number of events external to the equipment should also be reportable. Alarms are indications that are automatically generated by an S.NE as a result of the declaration of a failure. The OS shall have the ability to define which events and conditions generate autonomous reports, and which shall be reported on request. + +The following alarm-related functions shall be supported: + +- autonomous reporting of alarms; +- request for reporting of all alarms; +- reporting of all alarms; +- allow or inhibit autonomous alarm reporting; +- reporting on request status of allow or inhibit alarm reporting; +- enabling and disabling (via MI\_XXX\_Reported) the declaration of AIS, RDI and ODI fault causes in the atomic functions. Refer to [ITU-T G.783]; +- control of the termination point mode of termination points. Refer to [ITU-T G.783]; +- optionally, control of the port mode of termination points. Refer to [ITU-T G.783]; +- reporting of protection switch events. + +##### 7.1.3.4.1 Local reporting + +See [ITU-T G.7710] for a description of local reporting. + +##### 7.1.3.4.2 TMN reporting + +See [ITU-T G.7710] for a description of TMN reporting. + +## 7.2 Fault management functions + +Figure 7-1 contains the functional model of fault management inside the SEMF. This model is consistent with the alarm flow functional model specified in [ITU-T M.3100]. It must be noted that it does not address configuration aspects relating to fault management, the full ARC functional model, nor does it define where all possible event report parameters get assigned. Figure 7-1 is intended only to illustrate which well-known functions are impacted by ARC, and which are not, and to provide a generalized alarm flow view. + +![Figure 7-1: Fault management within the SDH NEF. This functional block diagram shows the flow of fault information through various functions. On the left, 'Fault cause' enters the 'PRS' (Fault cause persistency) function, which outputs a 'Failure' with a 'cZZZ-value'. This 'Failure' is passed to 'SEV' (Severity assignment), which outputs 'fZZZ-value' and 'fZZZ-severity'. 'SEV' also receives an 'Alarm severity assignment profile' from the top. The output of 'SEV' is passed to 'ARC' (Alarm reporting condition), which outputs 'fZZZ-value', 'fZZZ-severity', and 'fZZZ-arc'. 'ARC' also receives 'ARC information' from the top. The output of 'ARC' is passed to 'REP' (Reportable failure), which outputs 'rZZZ-value' and 'rZZZ-severity'. 'REP' is connected to 'TEP' (Traffic event persistency), which also outputs 'rZZZ-value' and 'rZZZ-severity'. 'TEP' is connected to 'ASY' (Alarm synchronization), 'LOG' (Logging), and 'TAN' (TMN alarm event notifications). 'LOG' receives a 'Query' and sends a 'Report'. 'TAN' sends 'TMN alarm event notifications'. 'REP' also connects to 'UNA' (Unit alarms), 'NEA' (Network element alarms), 'STA' (Station alarms), 'CPL' (Current problem list), 'AST' (Alarm status), and 'OPS' (Operational state). 'UNA', 'NEA', 'STA', 'CPL', 'AST', and 'OPS' all output to 'Management application functions' on the right. 'NE-RTC' (Network element real time clock) from 'Date and time functions' at the bottom is input to 'PRS'. The entire 'Fault management' block is flanked by 'Atomic functions' on the left and 'Management application functions' on the right.](844077b3034f0030b404207db0ad76b4_img.jpg) + +Figure 7-1: Fault management within the SDH NEF. This functional block diagram shows the flow of fault information through various functions. On the left, 'Fault cause' enters the 'PRS' (Fault cause persistency) function, which outputs a 'Failure' with a 'cZZZ-value'. This 'Failure' is passed to 'SEV' (Severity assignment), which outputs 'fZZZ-value' and 'fZZZ-severity'. 'SEV' also receives an 'Alarm severity assignment profile' from the top. The output of 'SEV' is passed to 'ARC' (Alarm reporting condition), which outputs 'fZZZ-value', 'fZZZ-severity', and 'fZZZ-arc'. 'ARC' also receives 'ARC information' from the top. The output of 'ARC' is passed to 'REP' (Reportable failure), which outputs 'rZZZ-value' and 'rZZZ-severity'. 'REP' is connected to 'TEP' (Traffic event persistency), which also outputs 'rZZZ-value' and 'rZZZ-severity'. 'TEP' is connected to 'ASY' (Alarm synchronization), 'LOG' (Logging), and 'TAN' (TMN alarm event notifications). 'LOG' receives a 'Query' and sends a 'Report'. 'TAN' sends 'TMN alarm event notifications'. 'REP' also connects to 'UNA' (Unit alarms), 'NEA' (Network element alarms), 'STA' (Station alarms), 'CPL' (Current problem list), 'AST' (Alarm status), and 'OPS' (Operational state). 'UNA', 'NEA', 'STA', 'CPL', 'AST', and 'OPS' all output to 'Management application functions' on the right. 'NE-RTC' (Network element real time clock) from 'Date and time functions' at the bottom is input to 'PRS'. The entire 'Fault management' block is flanked by 'Atomic functions' on the left and 'Management application functions' on the right. + +G.784(08)\_F7-1 + +Figure 7-1 – Fault management within the SDH NEF + +### 7.2.1 Fault cause persistency function – PRS + +The defect correlations provide a data reduction mechanism on the fault and performance monitoring primitives' information presented at the MP reference points. + +The equipment management function within the network element performs a persistency check on the fault causes (that are reported across the MP reference points) before it declares a fault cause a failure. In addition to the transmission failures, hardware failures with signal transfer interruption are also reported at the input of the fault cause function for further processing. See Figure 7-2. + +#### Symbol + +![Diagram of the fault cause persistency function. An input 'cZZZ-value (Fault cause)' enters a block labeled 'PRS' through a multiplexer symbol 'MP'. The output is 'cZZZ-value (Failure)'. A reference code 'T1546190-02' is shown below the output.](73b5cce955ba9415a98791db7b0080ad_img.jpg) + +``` + +graph LR + Input["cZZZ-value +(Fault cause)"] -- MP --> PRS[PRS] + PRS --> Output["cZZZ-value +(Failure)"] + T1546190-02[T1546190-02] + +``` + +Diagram of the fault cause persistency function. An input 'cZZZ-value (Fault cause)' enters a block labeled 'PRS' through a multiplexer symbol 'MP'. The output is 'cZZZ-value (Failure)'. A reference code 'T1546190-02' is shown below the output. + +Figure 7-2 – Fault cause persistency function + +#### Inputs and outputs + +Table 7-1 – Inputs/outputs for the fault cause persistency function + +| Process (see [ITU-T G.783]) | Input | Output | +|-----------------------------|-----------------------------------------------|-----------------------------------------------| +| OSn-Xy.z_TT_Sk | cLOS | fLOS | +| ES1_TT_Sk | cLOS | fLOS | +| OSn/RSn_A_Sk | cLOF | fLOF | +| ES1/RS1_A_Sk | cLOF | fLOF | +| RSn_TT_Sk | cTIM
cSSF | fTIM
fSSF | +| MSn_TT_Sk | cEXC
cAIS
cDEG
cRDI
cSSF | fEXC
fAIS
fDEG
fRDI
fSSF | +| MSn/Sn_A_Sk | cAIS
cLOP | fAIS
fLOP | +| MSnP_C | cFOP | fFOP | +| MSnP_TT_Sk | cSSF | fSSF | +| MSnP2fsh_TT_Sk | cSSF | fSSF | +| MSnP4fsh_TT_Sk | cSSF | fSSF | +| Sn_TT_Sk | cTIM
cUNEQ
cEXC
cDEG
cRDI
cSSF | fTIM
fUNEQ
fEXC
fDEG
fRDI
fSSF | +| Snm1_TT_Sk | cTIM
cUNEQ
cEXC
cDEG
cRDI
cSSF | fTIM
fUNEQ
fEXC
fDEG
fRDI
fSSF | +| Snm2_TT_Sk | cTIM
cUNEQ
cEXC
cDEG
cRDI
cSSF | fTIM
fUNEQ
fEXC
fDEG
fRDI
fSSF | + +**Table 7-1 – Inputs/outputs for the fault cause persistency function** + +| Process (see [ITU-T G.783]) | Input | Output | +|-----------------------------|------------------------------------------------------------------|------------------------------------------------------------------| +| Sns_TT_Sk | cTIM
cUNEQ
cEXC
cDEG
cRDI
cSSF | fTIM
fUNEQ
fEXC
fDEG
fRDI
fSSF | +| Sn/Sm_A_Sk | cPLM
cLOM | fPLM
fLOM | +| Sn/Pqx_A_Sk | cPLM | fPLM | +| SnP_TT_Sk | cSSF | fSSF | +| SnD_TT_Sk | cLTC
cTIM
cUNEQ
cDEG
cRDI
cODI
cSSF
cIncAIS | fLTC
fTIM
fUNEQ
fDEG
fRDI
fODI
fSSF
fIncAIS | +| SnDm_TT_Sk | cLTC
cTIM
cUNEQ
cDEG
cRDI
cODI
cSSF
cIncAIS | fLTC
fTIM
fUNEQ
fDEG
fRDI
fODI
fSSF
fIncAIS | +| SnT_TT_Sk | cUNEQ
cDEG
cIncAIS | fUNEQ
fDEG
fIncAIS | +| SnTm_TT_Sk | cUNEQ
cDEG
cIncAIS | fUNEQ
fDEG
fIncAIS | +| Sn-Xv/Sn-X_A_Sk | cLOM
cSQM
cLOA | fLOM
fSQM
fLOA | +| Sn-X_TT_Sk | cSSF | fSSF | +| Sn-X_TT_Sk | cTIM
cUNEQ
cSSF
cLOM
cSQM
cLOA | fTIM
fUNEQ
fSSF
fLOM
fSQM
fLOA | +| Sm_TT_Sk | cTIM
cUNEQ
cEXC
cDEG
cRDI
cSSF | fTIM
fUNEQ
fEXC
fDEG
fRDI
fSSF | + +**Table 7-1 – Inputs/outputs for the fault cause persistency function** + +| Process (see [ITU-T G.783]) | Input | Output | +|-----------------------------|------------------------------------------------------------------|------------------------------------------------------------------| +| Smm1_TT_Sk | cTIM
cUNEQ
cEXC
cDEG
cRDI
cSSF | fTIM
fUNEQ
fEXC
fDEG
fRDI
fSSF | +| Smm2_TT_Sk | cTIM
cUNEQ
cEXC
cDEG
cRDI
cSSF | fTIM
fUNEQ
fEXC
fDEG
fRDI
fSSF | +| Sms_TT_Sk | cTIM
cUNEQ
cEXC
cDEG
cRDI
cSSF | fTIM
fUNEQ
fEXC
fDEG
fRDI
fSSF | +| Sm/Pqx_A_Sk | cPLM | fPLM | +| Sm/Pqs_A_Sk | cPLM | fPLM | +| SmP_TT_Sk | cSSF | fSSF | +| SmD_TT_Sk | cLTC
cTIM
cUNEQ
cDEG
cRDI
cODI
cSSF
cIncAIS | fLTC
fTIM
fUNEQ
fDEG
fRDI
fODI
fSSF
fIncAIS | +| SmDm_TT_Sk | cLTC
cTIM
cUNEQ
cDEG
cRDI
cODI
cSSF
cIncAIS | fLTC
fTIM
fUNEQ
fDEG
fRDI
fODI
fSSF
fIncAIS | +| Sm-X_TT_Sk | cSSF | fSSF | +| Sm/Sm-X_A_Sk | cLOM
cSQM
cLOA | fLOM
fSQM
fLOA | + +#### Process + +The equipment management function within the network element performs a persistency check on the fault causes before it declares a fault cause a failure. + +A transmission failure (fXXX) shall be declared if the fault cause persists continuously for $2.5 \pm 0.5$ s. The failure shall be cleared if the fault cause is absent continuously for $10 \pm 0.5$ s. + +The specific set of failures associated with each atomic function are listed in Table 7-1. + +NOTE – A complementary list is available in [ITU-T M.3100]. + +The failure declaration and clearing shall be time stamped. The time stamp shall indicate the time at which the fault cause is activated at the input of the fault cause persistency (i.e., defect-to-failure integration) function, and the time at which the fault cause is deactivated at the input of the fault cause persistency function. + +### **7.2.2 Severity assignment function – SEV** + +See [ITU-T G.7710] for a description of the severity assignment function. + +### **7.2.3 Alarm reporting control function – ARC** + +The alarm reporting control (ARC) function allows a management system to control the alarm reporting on a per-managed entity basis as defined in [ITU-T M.3100]. + +The alarms that can be controlled with this function are defined for each atomic function in [ITU-T G.783]. + +The ARC states that may be specified for a managed entity are defined in clause 7.1.3.2. For S.NE: + +- The ALM state is required for all managed entities that can detect alarms. +- In addition, at least one of the states: NALM, NALM-TI or NALM-QI must be supported. +- If NALM-QI is supported, then NALM-NR is required and NALM-CD is optional. + +### **7.2.4 Reportable failure function – REP** + +See [ITU-T G.7710] for a description of the reportable failure function. + +### **7.2.5 Unit alarms function – UNA** + +See [ITU-T G.7710] for a description of the unit alarm function. + +### **7.2.6 Network element alarm function – NEA** + +See [ITU-T G.7710] for a description of the network element alarm function. + +### **7.2.7 Station alarm function – STA** + +See [ITU-T G.7710] for a description of the station alarm function. + +### **7.2.8 TMN event pre-processing function – TEP** + +See [ITU-T G.7710] for a description of the TMN event pre-processing alarm function. + +### **7.2.9 Alarm synchronization function – ASY** + +See [ITU-T G.7710] for a description of the alarm synchronization function. + +### **7.2.10 Logging function – LOG** + +Alarm history management is concerned with the recording of alarms. Historical data shall be stored in registers in the S.NE. Each register contains all the parameters of an alarm message. + +Registers shall be readable on demand or periodically. The OS can define the operating mode of the registers as wrapping or stop when full. The OS may also flush the registers or stop recording at any time. + +NOTE – Wrapping is the deletion of the earliest record to allow a new record when a register is full. Flushing is the removal of all records in the register. See [ITU-T X.735] for additional details. + +See [ITU-T G.7710] for a description of the logging function. + +### **7.2.11 TMN alarm event notification function – TAN** + +See [ITU-T G.7710] for a description of the TMN alarm event notification function. + +### **7.2.12 Current problem list function – CPL** + +See [ITU-T G.7710] for a description of the current problem list function + +### **7.2.13 Alarm status function – AST** + +See [ITU-T G.7710] for a description of the alarm status function + +### **7.2.14 Operational state function – OPS** + +See [ITU-T G.7710] for a description of the operational state function. + +# **8 Configuration management** + +See [ITU-T G.7710] for the generic requirements for configuration management. SDH-specific specifications, if needed, are explicitly described. + +## **8.1 Hardware** + +See [ITU-T G.7710] for a description of equipment configuration. + +## **8.2 Software** + +See [ITU-T G.7710] for a description of software configuration. + +## **8.3 Protection switching** + +See [ITU-T G.7710] for a description of protection switching configuration. + +### **8.3.1 Linear STM-N MS protection** + +The functions which allow the user to provision the configuration of the protection scheme are: + +- establishment of protection, indicating the protection switching mode (uni-/bidirectional) operation mode (revertive/non-revertive), extra traffic (supported, not supported), the entities participating in the protection, their role (working/protection), and possibly their priority; +- modification of protection, adding or removing entities and/or modifying their protection characteristics; +- suppression of protection; +- wait-to-restore time; +- SF and SD priority; + +This information is conveyed between the EMF and an AF via the MI\_SWtype, MI\_OPERtype, MI\_EXTRAtraffic, MI\_WTRtime, MI\_SFpriority, MI\_SDpriority (see Table 8-1). + +**Table 8-1 – Linear MSP-related provisioning** + +| MI signal | Value range | Default value | +|----------------------------------------------------------------------------|-------------------------------|----------------------| +| Switching type (MI_SWtype) | Unidirectional, bidirectional | No default defined | +| Operation type (MI_OPERtype) | Revertive, non-revertive | No default defined | +| Extra traffic (MI_EXTRAtraffic) | True, false | No default defined | +| Wait-to-restore time (MI_WTRtime) | 0,1,...,12 minutes | 5 minutes | +| Priority of SF and SD conditions in 1:n MSP (MI_SFpriority, MI_SDPriority) | High, low | High | + +### **8.3.2 STM-N MS SPring protection** + +For further study. + +### **8.3.3 Linear 1+1 SNC protection** + +The functions which allow the user to provision the configuration of the protection scheme are: + +- establishment of protection, indicating the operation mode (revertive/non-revertive), SNC protection type (SNC/I, SNC/N), the entities participating in the protection, their role (working/protection); +- modification of protection, adding or removing entities and/or modifying their protection characteristics; +- suppression of protection; +- wait-to-restore time, hold-off time. + +This information is conveyed between the EMF and an AF via the MI\_OPERtype, MI\_WTRtime, MI\_HOtime, MI\_PROTtype (see Table 8-2). + +**Table 8-2 – Linear SNCP-related provisioning** + +| MI signal | Value range | Default value | +|-----------------------------------|----------------------------|----------------------| +| Operation type (MI_OPERtype) | Revertive, non-revertive | Non-revertive | +| Protection type (MI_PROTtype) | SNC/I, SNC/N | No default defined | +| Wait-to-restore time (MI_WTRtime) | 0,1,...,12 minutes | 5 minutes | +| Hold-off time (MI_HOtime) | 0, 100 ms, 200 ms,...,10 s | 0 | + +#### **8.3.3.1 Linear 1+1 VC trail protection** + +The functions which allow the user to provision the configuration of the protection scheme are: + +- establishment of protection, indicating the protection operation mode (revertive/non-revertive), the entities participating in the protection, their role (working/protection); +- modification of protection, adding or removing entities and/or modifying their protection characteristics; +- suppression of protection; +- wait-to-restore time, hold-off time. + +This information is conveyed between the EMF and an AF via the MI\_OPERtype, MI\_WTRtime, MI\_HOtime (see Table 8-3). + +**Table 8-3 – Protection-related provisioning** + +| MI signal | Value range | Default value | +|-----------------------------------|----------------------------|---------------| +| Operation type (MI_OPERtype) | Revertive, non-revertive | Non-revertive | +| Wait-to-restore time (MI_WTRtime) | 0,1,...,12 minutes | 5 minutes | +| Hold-off time (MI_HOtime) | 0, 100 ms, 200 ms,...,10 s | 0 | + +#### 8.3.3.2 Status and control + +The status and control information is conveyed between the EMF and an AF via the MI\_EXTCMD signal (see Table 8-4). + +**Table 8-4 – Protection-related control provisioning** + +| MI signal | Value range | Default value | +|------------------------------|-------------------------|---------------| +| External command (MI_EXTCMD) | CLR, LO, FSw, MSw, EXER | None | + +## 8.4 Trail termination + +See [ITU-T G.7710] for a description of trail termination management. + +### 8.4.1 Provisioning + +#### 8.4.1.1 Trail trace identifier + +The trail trace identifier (TTI) is defined in the regenerator section layer and the path layer and is transported in the Jx-bytes (x = J0, J1, J2) of the section and path overhead. + +The TTI may be used in two different applications for: + +- connection verification as defined in the 1999 version of this Recommendation to ensure proper connection between network elements; or +- optionally, if instructed by the management plane, for layer adjacency discovery (LAD) which allows discovery of the association between two TCPs in a particular layer network (see [ITU-T G.7714] for a description of the generalized automatic discovery mechanism). See [ITU-T G.7714.1] for a description of the protocol for automatic discovery in SDH networks and Amendment 1 to [ITU-T G.7714.1] for a description of the usage of the different discovery mechanisms. + +See [ITU-T G.7710] for a description of trace identifier management. + +TTI shall be supported as specified in Table 8-5. + +**Table 8-5 – Trace identifier related provisioning and reporting** + +| MI signal | Value range | Default value | +|------------------------|-----------------------------------------------|----------------| +| RSn_TT_So_MI_TxTI | According to [ITU-T G.707] | Not applicable | +| RSn_TT_Sk_MI_ExTI | According to [ITU-T G.707] | Not applicable | +| RSn_TT_Sk_MI_ExTImode | 16-byte, 1-byte
According to [ITU-T G.783] | 16-byte | +| RSn_TT_Sk_MI_TIMAISdis | True, false | False | +| RSn_TT_Sk_MI_TIMdis | True, false | True | +| Sn_TT_So_MI_TxTI | According to [ITU-T G.707] | Not applicable | +| Sn_TT_Sk_MI_ExTI | According to [ITU-T G.707] | Not applicable | + +**Table 8-5 – Trace identifier related provisioning and reporting** + +| MI signal | Value range | Default value | +|-------------------------|----------------------------|----------------| +| Sn_TT_Sk_MI_ExTImode | 16-byte, 1-byte | 16-byte | +| Sn_TT_Sk_MI_TIMAISdis | True, false | False | +| Sn_TT_Sk_MI_TIMdis | True, false | True | +| Snm1_TT_Sk_MI_ExTI | According to [ITU-T G.707] | Not applicable | +| Snm1_TT_Sk_MI_TIMdis | True, false | True | +| Snm2_TT_Sk_MI_ExTI | According to [ITU-T G.707] | Not applicable | +| Snm2_TT_Sk_MI_TIMdis | True, false | True | +| Sns_TT_So_MI_TxTI | According to [ITU-T G.707] | Not applicable | +| Sns_TT_Sk_MI_ExTI | According to [ITU-T G.707] | Not applicable | +| Sns_TT_Sk_MI_TIMdis | True, false | True | +| SnD_TT_So_MI_TxTI | According to [ITU-T G.707] | Not applicable | +| SnD_TT_Sk_MI_ExTI | According to [ITU-T G.707] | Not applicable | +| SnD_TT_Sk_MI_TIMdis | True, false | True | +| SnDm_TT_Sk_MI_ExTI | According to [ITU-T G.707] | Not applicable | +| SnDm_TT_Sk_MI_TIMdis | True, false | True | +| S4-Xc>S4-Xv_I_MI_TxTI | According to [ITU-T G.707] | Not applicable | +| S4-Xv>S4-Xc_I_MI_ExTI | According to [ITU-T G.707] | Not applicable | +| S4-Xv>S4-Xc_I_MI_TIMdis | True, false | True | +| Sm_TT_So_MI_TxTI | According to [ITU-T G.707] | Not applicable | +| Sm_TT_Sk_MI_ExTI | According to [ITU-T G.707] | Not applicable | +| Sm_TT_Sk_MI_TIMAISdis | True, false | False | +| Sm_TT_Sk_MI_TIMdis | True, false | True | +| Smm1_TT_Sk_MI_ExTI | According to [ITU-T G.707] | Not applicable | +| Smm1_TT_Sk_MI_TIMdis | True, false | True | +| Smm2_TT_Sk_MI_ExTI | According to [ITU-T G.707] | Not applicable | +| Smm2_TT_Sk_MI_TIMdis | True, false | True | +| Sms_TT_So_MI_TxTI | According to [ITU-T G.707] | Not applicable | +| Sms_TT_Sk_MI_ExTI | According to [ITU-T G.707] | Not applicable | +| Sms_TT_Sk_MI_TIMdis | True, false | True | +| SmD_TT_So_MI_TxTI | According to [ITU-T G.707] | Not applicable | +| SmD_TT_Sk_MI_ExTI | According to [ITU-T G.707] | Not applicable | +| SmD_TT_Sk_MI_TIMdis | True, false | True | +| SmDm_TT_Sk_MI_ExTI | According to [ITU-T G.707] | Not applicable | +| SmDm_TT_Sk_MI_TIMdis | True, false | True | + +## 8.5 Adaptation + +See [ITU-T G.7710] for a description of adaptation management. + +An access point that has multiple adaptation functions connected to it, thereby allowing different clients to be transported via the server signal, requires a mechanism for the selection of the active + +client. The activation/deactivation of adaptation functions is via MI\_Active signals. In the case where the access point is connected to only one adaptation function (i.e., it supports only one client signal) the MI\_Active signal is fixed as active. + +**Table 8-6 – Provisioning and reporting for adaptation functions** + +| MI signal | Value range | Default value | +|-----------------------------|-------------|---------------| +| MSn/Sn_A_So_MI_Active | True, false | False | +| MSn/Sn_A_So_MI_pPJE+ | FFS | FFS | +| MSn/Sn_A_So_MI_pPJE- | FFS | FFS | +| MSn/Sn_A_Sk_MI_Active | True, false | False | +| MSn/Sn_A_Sk_MI_AIS_Reported | True, false | False | +| Sn/Sm_A_So_MI_Active | True, false | False | +| Sn/Sm_A_Sk_MI_Active | True, false | False | +| Sn/Sm_A_Sk_MI_AcSL | FFS | FFS | +| Sn/Pqx_A_So_MI_Active | True, false | False | +| Sn/Pqx_A_Sk_MI_Active | True, false | False | +| Sn/Pqx_A_Sk_MI_AcSL | FFS | FFS | +| Sm/Pqx_A_So_MI_Active | True, false | False | +| Sm/Pqx_A_Sk_MI_Active | True, false | False | +| Sm/Pqx_A_Sk_MI_AcSL | FFS | FFS | +| Sm/Pqs_A_So_MI_Active | True, false | False | +| Sm/Pqx_A_Sk_MI_Active | True, false | False | +| Sm/Pqs_A_Sk_MI_AcSL | FFS | FFS | + +## 8.6 Connection + +See [ITU-T G.7710] for a description of connection management. + +This function allows a user to provision the operation of an SDH connection process. + +The MI signals listed in Table 8-7 are communicated from the EMF to the connection process through the management point. + +**Table 8-7 – Provisioning and reporting for connection functions** + +| MI signal | Value range | Default value | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------| +| For connection points W and P:
MSnP_C_MI_SFpriority
MSnP_C_MI_SDpriority

Per function:
MSnP_C_MI_SWtype
MSnP_C_MI_EXTRAtraffic
MSnP_C_MI_WTRTime
MSnP_C_MI_EXTCMD | FFS | FFS | + +**Table 8-7 – Provisioning and reporting for connection functions** + +| MI signal | Value range | Default value | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------| +| MSnP2fsh_CI_MI_EXTRAtraffic
MSnP2fsh_CI_MI_NUTraffic
MSnP2fsh_C_MI_WTRTime
MSnP2fsh_C_MI_EXT CMD
MSnP2fsh_C_MI_RingNodeID
MSnP2fsh_C_MI_RingMap | FFS | FFS | +| MSnP4fsh_CI_MI_EXTRAtraffic
MSnP4fsh_CI_MI_NUTraffic
MSnP4fsh_C_MI_WTRTime
MSnP4fsh_C_MI_EXT CMD
MSnP4fsh_C_MI_RingNodeID
MSnP4fsh_C_MI_RingMap | FFS | FFS | +| Per input and output connection point:
Sn_C_MI_ConnectionPortIds
Per matrix connection:
Sn_C_MI_ConnectionType
Sn_C_MI_Directionality
Per SNC protection group:
Sn_C_MI_PROTtype
Sn_C_MI_OPERtype
Sn_C_MI_WTRtime
Sn_C_MI_Hotime
Sn_C_MI_EXT CMD | FFS | FFS | +| For connection point P:
SnP_C_MI_OPERType
SnP_C_MI_WTRTime
SnP_C_MI_HOTime
SnP_C_MI_EXT CMD | FFS | FFS | +| Per input and output connection point:
Sm_C_MI_ConnectionPortIds
Per matrix connection:
Sm_C_MI_ConnectionType
Sm_C_MI_Directionality
Per SNC protection group:
Sm_C_MI_PROTtype
Sm_C_MI_OPERtype
Sm_C_MI_WTRtime
Sm_C_MI_HOTime
Sm_C_MI_EXT CMDODUk_C_MI_MatrixControl | FFS | FFS | +| For connection point P:
SmP_C_MI_OPERType
SmP_C_MI_WTRTime
SmP_C_MI_HOTime
SmP_C_MI_EXT CMD | FFS | FFS | + +The EMF shall support the following functions: + +- provisioning of the connection management information; +- retrieving the connection management information; + +- notifying the changes of the connection management information. + +## 8.7 EXC/DEG thresholds + +The thresholds of Poisson-based excessive and degraded defect detector processes, and the threshold and monitor period of the burst-based degraded defect process require provisioning. This information is communicated between the EMF and an AF via the MI\_EXC\_X, MI\_DEG\_X (Poisson case) and MI\_DEGTHR, MI\_DEGM (burst case) signals (see Table 8-8). + +**Table 8-8 – Error defect detection-related provisioning** + +| MI signal | Value range | Default value | +|-------------------------------------------------------------------------------------------------------------|-----------------------------------------------|---------------| +| Poisson-based excessive defect threshold selection (MI_EXC_X) | $10^{-3}, 10^{-4}, 10^{-5}$ | $10^{-3}$ | +| Poisson-based degraded defect threshold selection (MI_DEG_X) | $10^{-5}, 10^{-6}, 10^{-7}, 10^{-8}, 10^{-9}$ | $10^{-6}$ | +| Burst-based degraded defect interval threshold selection (MI_DEGTHR) | 0..100% or 0..N EBs (Note) | SES threshold | +| Burst-based degraded defect monitor period selection (MI_DEGM) | 2..10 | 7 | +| NOTE – The granularity for the degraded defect threshold selection is for further study. See [ITU-T G.783]. | | | + +The granularity of these signals is outside the scope of this Recommendation. Examples are: + +- global per network element; +- global per network layer in the network element; +- global per server/aggregate signal in the network element; +- individual per trail/signal in the network element. + +The two extremes are "provisioning per individual signal" and "provisioning per network element". The first example offers full flexibility with relatively high complexity in equipment and in management. The second example offers low complexity in equipment and in management with very limited flexibility. + +An equipment will support one or more of these options depending on the intended application of the equipment in the network. + +See also [ITU-T G.7710] for the generic requirements. + +## 8.8 Port mode and TP mode + +The TPmodes and Portmodes (see [ITU-T G.783]) of trail termination sink functions (i.e., the end-to-end path termination, non-intrusive monitor, supervisory-unequipped termination, end-to-end tandem connection termination, and tandem connection non-intrusive monitor) require provisioning. This information is communicated between the EMF and an AF via the MI\_Portmode and/or MI\_TPmode signals (see Table 8-9). + +When supported, the Portmode may change automatically from AUTO state to MON state on clearing of the port's LOS defect. + +**Table 8-9 – Port and termination point mode-related provisioning** + +| MI signal | Value range | Default value | +|--------------------------------------------|-------------------|---------------------------------------| +| Port mode control (MI_Portmode) | MON, (AUTO), NMON | AUTO (if supported)
otherwise NMON | +| Termination point mode control (MI_TPmode) | MON, NMON | NMON | + +## 8.9 XXX\_Reported + +The reporting of the following defects is an option: AIS, RDI, ODI. These defects are "secondary defects" in that they are the result of a consequent action on a "primary defect" in another network element. This is controlled by means of the parameters MI\_AIS\_Reported, MI\_RDI\_Reported and MI\_ODI\_Reported (see Table 8-10). + +**Table 8-10 – Consequential defect/failure related provisioning** + +| MI signal | Value range | Default value | +|-----------------|-------------|---------------| +| MI_AIS_Reported | True, false | False | +| MI_RDI_Reported | True, false | False | +| MI_ODI_Reported | True, false | False | + +See also clause 8.8 of [ITU-T G.7710] for the generic requirements. + +## 8.10 Alarm severity + +See clause 8.9 of [ITU-T G.7710] for a description of alarm severity. + +## 8.11 Alarm reporting control (ARC) + +See clause 8.10 of [ITU-T G.7710] for a description of alarm reporting control. + +## 8.12 PM thresholds + +See clause 8.11 of [ITU-T G.7710] for a description of PM thresholds configuration. + +## 8.13 TCM activation + +See clause 8.12 of [ITU-T G.7710] for a description of TCM activation configuration. + +## 8.14 Synchronization provisioning and reporting + +The management access (provisioning and reporting) to the synchronization atomic functions supported by the S.NEs is defined in [ITU-T G.781] and [ITU-T G.783]. + +## 8.15 Date and time + +See clause 8.13 of [ITU-T G.7710] for the generic requirements. + +### 8.15.1 Date and time applications + +[ITU-T G.7710] identifies four date and time applications. These are: + +- time-stamping; +- real time clock alignment with external time reference; +- performance monitoring clock signals; +- activity scheduling. + +The SDH NEF functional requirements for these applications are specified in the following clauses. + +#### **8.15.1.1 Time-stamping** + +See [ITU-T G.7710] for a description of the time-stamping application. + +#### **8.15.1.2 Performance monitoring clock signals** + +See [ITU-T G.7710] for a description of the PMC signal. + +#### **8.15.1.3 Activity scheduling** + +See [ITU-T G.7710] for a description of the activity scheduling. + +### **8.15.2 Date and time functions** + +See [ITU-T G.7710] for a description of the date and time functions. + +# **9 Account management** + +Account management is for further study. + +# **10 Performance management** + +See [ITU-T G.7710] for the generic requirements for performance management. SDH-specific management requirements are described below. + +NOTE – This clause defines the performance monitoring-related equipment specifications based on the network level specifications in [ITU-T M.2100], [ITU-T M.2101], [ITU-T M.2120], [ITU-T G.826] and [ITU-T G.827]. + +## **10.1 Performance management applications** + +See [ITU-T G.7710] for the generic description for performance management applications. + +### **10.1.1 Concepts of "near-end" and "far-end"** + +See [ITU-T G.7710] for a description of near-end and far-end concepts. + +### **10.1.2 Maintenance** + +See [ITU-T G.7710] for a description of performance management for maintenance. + +### **10.1.3 Bringing-into-service** + +See [ITU-T G.7710] for a description of bringing-into-service. + +### **10.1.4 Quality of service** + +See [ITU-T G.7710] for a description of quality of service. + +### **10.1.5 Availability** + +See [ITU-T G.7710] for a description of availability. + +### **10.1.6 Reporting** + +See [ITU-T G.7710] for the generic description of performance data collection. + +See [ITU-T G.7710] for a description of reporting. + +Performance data stored in the S.NE may be collected by the OS for analysis without affecting the content of the register. + +Performance data shall be reportable across the NE/OS interface on demand when requested by the OS. + +Performance data shall be reportable across the NE/OS interface automatically upon reaching or crossing a performance-monitoring threshold. + +Data collection may be performed periodically to support trend analysis to predict future failure or degraded conditions. On request of the OS, performance data of specific ports shall be reportable periodically. + +As soon as a threshold is reached or crossed in a 15-minute/24-hour period for a given performance measurement, a threshold report (TR) is generated. + +As an option for 15-minute periods, an alternative method of threshold reporting can be used. When, for the first time, a threshold is reached or crossed for a given performance measurement, a threshold report is generated. No threshold reports will be generated in subsequent 15-minute periods until a clear threshold is undercrossed for the performance measurement. Then, a reset threshold report (RTR) is generated. + +#### **10.1.6.1 Performance data collection** + +Counter-based performance data collection refers to the measurement counting associated with each of the performance measurements (BBE, ES, SES as defined in [ITU-T G.826]), and any additional performance parameter defined in this Recommendation. + +Two types of performance data collection are defined: + +- The collection as specified in [ITU-T M.2120], i.e., based on information of each direction of transport independently. This type is further referred to as performance data collection for maintenance purposes. +- The collection as specified in [ITU-T G.826], i.e., based on information of both directions of transport together. This type is further referred to as performance data collection for error performance assessment purposes. + +When performance data is collected for maintenance purposes, counts are taken over fixed time periods of 15 minutes and 24 hours. Counting is stopped during unavailable time (see 10.1.6.1.1). + +When performance data is collected for error performance assessment purposes, counts are taken over fixed time periods of 24 hours only. Counting is stopped during unavailable time (see 10.1.6.1.1). + +It shall be possible to reset an individual current register to zero by means of an external command. The modularity of this command shall be as specified in [ITU-T G.774.1] and [ITU-T G.774.6]. + +Gauge-based performance data collection refers to the measurement gauge crossings associated with each of the performance measurements and any additional performance parameter defined in this Recommendation. + +Performance history data are necessary to assess the recent performance of transmission systems. Such information can be used to sectionalize faults and to locate the source of intermittent errors. + +Historical data, in the form of performance measurement, may be stored in registers in the S.NE or in mediation devices associated with the S.NE. For specific applications, for example when only quality of service alarms are used, historical data may not be stored. + +All the history registers shall be time stamped. + +The history registers operate as follows: + +##### **15-minute registers** + +The history of the 15-minute monitoring is contained in a stack of 16 registers per monitored measurement. These registers are called the recent registers. + +Every 15 minutes, the contents of the current registers are moved to the first of the recent registers. When all 15-minute registers are used, the oldest information will be discarded. + +##### **24-hour registers** + +The history of the 24-hour monitoring is contained in a single register per monitored measurement. This register is called the recent register. + +Every 24 hours the contents of the current registers are moved to the recent register1. + +##### **10.1.6.1.1 Performance data collection during unavailable time** + +The onset and exit of unavailable time is defined in Annex A of [ITU-T G.826] and in [ITU-T M.2120]. + +Performance monitoring event counting for ES, SES and BBE shall be inhibited during unavailable time: + +- In the performance data collection process for maintenance purposes, the unavailability of a single direction (see clause A.1 of [ITU-T G.826]) shall inhibit the counting for that direction only. +- In the performance data collection process for error performance assessment purposes, the unavailability of the bidirectional path (see clause A.2 of [ITU-T G.826]) shall inhibit the counting for both directions simultaneously. + +##### **10.1.6.1.2 Availability data collection** + +When a period of unavailability occurs, the beginning and ending of this period should be stored in a log in the S.NE and, as a consequence, time stamped. The time stamp shall contain day, month, year, hour, minute, second information (refer to clause 5.3.8.2 of [ITU-T M.2120]). + +The S.NE should be able to store these data in a log (see [ITU-T G.774.1]). + +NOTE – The information in a log is not restricted to a single 24-hour period. For example, a log may contain periods of unavailability which are on the same day or on different days. + +As an option, an additional unavailable second (UAS) count may be provided. Each second in unavailable time is defined to be an unavailable second. UASs are counted in 15-minute and in 24-hour counters. + +In the performance data collection process for maintenance purposes, UAS counters exist per direction. + +In the performance data collection process for error performance assessment purposes, only one UAS counter for both directions exists. + +If a ten-second qualifying period preceding the entry/exit of unavailability spans a register boundary, unavailability shall be entered/exited independently of the register boundary. This shall result in the entry/exit of unavailability, and associated inhibiting, at the beginning of the ten-second qualifying period. + +--- + +1 This implies that all 24-hour data is discarded after 24 hours. + +The entry case is illustrated by: + +![](cc72b4769f15fe33763025416c1e274d_img.jpg) + +| | | +|-------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| Period A | Period B | +| - - - x 1 x 2 x 3 x 4 | x 5 x 6 x 7 x 8 x 9 x 10 x 11 x 12 | +| Register boundary | | + +"x" = SES, "-" = non-SES, x1 to x4 are in UAS register for period A, x5 to x12 are in UAS register for period B. + +#### 10.1.6.2 History storage suppression + +See [ITU-T G.7710] for a description of history storage suppression. + +### 10.1.7 Thresholding + +See [ITU-T G.7710] for a description of generic thresholding. + +Specific information is contained in [ITU-T M.2101] and [ITU-T M.2120]. The thresholding mechanism is applicable only for the maintenance-based collection. + +#### 10.1.7.1 Threshold setting + +The thresholds may be set in the S.NE via the OS. The OS shall be able to retrieve and change the settings of the 15-minute and 24-hour thresholds. + +The threshold values for measurements evaluated over the 15-minute period should be programmable with a range between 0 and a maximum value specified hereafter. + +The maximum values for the number of measurements are2: + +- 900 for the ES and SES measurements; +- $2^{16} - 1$ for the BBE event in the case of VC-11 up to VC-4 paths; +- $2^{24} - 1$ for the BBE event in the case of contiguous concatenated VC-4-Xc and STM-N ( $X \leq 16$ and $N \leq 16$ ); +- $2^{16} - 1$ for each positive and negative counts of AU PJE. + +The maximum values for the number of measurements evaluated over the 24-hour period shall be $2^{16} - 1$ . The threshold value should be programmable between 0 and $2^{16} - 1$ . + +#### 10.1.7.2 Threshold reporting + +As soon as a threshold is reached or crossed in a 15-minute/24-hour period for a given performance measurement, a threshold report (TR) is generated. + +As an option for 15-minute periods, an alternative method of threshold reporting can be used. When for the first time a threshold is reached or crossed for a given performance measurement, a threshold report is generated. No threshold reports will be generated in subsequent 15-minute periods until a clear threshold is undercrossed for the performance measurement. Then, a reset threshold report (RTR) is generated. + +--- + +2 The maximum values for BBE events for VCs and STM-Ns is smaller than the maximum number of BBEs that could theoretically be detected in a 15-minute period. + +#### 10.1.7.3 Evaluation for counters + +See [ITU-T G.7710] for a generic description. + +#### 10.1.7.4 Evaluation for gauges + +See [ITU-T G.7710] for a generic description. + +### 10.1.8 Additional monitored events + +Additional counts such as OFS, AU PJE, CSES, ESA, ESB and FC may be useful. Their implementation is optional (see Table 10-1). The OFS, AU PJE, ESA, ESB, and FC event counts may be stored in 15-minute and 24-hour registers, as detailed in clause 10.1.6. + +The out-of-frame second (OFS) is declared when the STM-N frame alignment process is in the OOF state at least once in the second. Refer to [ITU-T G.783]. The AF communicates this via the MI\_pOFS signal to the EMF. + +If AU PJE counters are provided, then positive and negative PJEs shall be counted separately on one selectable AU within an STM-N signal, after the AU has been resynchronized to the local clock. Refer to [ITU-T G.783]. The number of positive and negative outgoing PJEs per second is communicated from the AF to the EMF via the MI\_pPJE+ and MI\_pPJE- signals. + +The CSES event occurs when a sequence that contains X or more consecutive SES is detected. The sequence is terminated by an unavailable period or when a second that is not an SES is encountered. The S.NE should be able to store these time-stamped CSES data in a log (see [ITU-T G.774.1]); the time stamp shall indicate the time of the first SES in the sequence. The value of X may be configured by an OS in the range of 2 to 9. When a sequence of consecutive SESs is terminated by the entry into an unavailable period, the CSES event is not recorded. + +The following PM parameters may also be provided: errored seconds type A (ESA), errored seconds type B (ESB) and failure counts (FC). These parameters are defined in Annex A, and their implementation is optional per country. + +ESA and ESB can be used in addition to errored seconds (ESs) to delineate dribbling error patterns from short burst error patterns. At international boundaries, they are only used if there is mutual agreement among the network operators involved to provide these parameters, and if the participating countries also support them. + +Failure counts can be used to determine whether a UAS or SES count is the result of a single failure or multiple failures. At international boundaries, it is only used if there is mutual agreement among the network operators involved to provide this parameter, and if the participating countries also support it. + +**Table 10-1 – SDH additional monitored events** + +| Monitored events | RS | MS | Path higher order VC | Path lower order VC | +|------------------|----|----|----------------------|---------------------| +| OFS | O | | | | +| CSES | O | O | O | O | +| AU PJE | | | O | | +| ESA | | OC | OC | OC | + +**Table 10-1 – SDH additional monitored events** + +| Monitored events | RS | MS | Path higher order VC | Path lower order VC | +|---------------------------------------------------------------------|----|----|----------------------|---------------------| +| ESB | | OC | OC | OC | +| FC | | OC | OC | OC | +| O      Optional | | | | | +| OC    Optional per Country and per Carrier | | | | | +| AU PJE Administrative Unit Pointer Justification Event | | | | | +| OFS    Out-of-Frame Second | | | | | +| CSES Consecutive SES counts configurable in the range of 2 to 9 SES | | | | | +| ESA    Errored Seconds type A | | | | | +| ESB    Errored Seconds type B | | | | | +| FC     Failure Counts | | | | | + +### 10.1.9 Performance monitoring resource assignment + +Performance monitoring within a network element is a set of processes that can be completely absent, 100% present, or available for a limited percentage. Figure 10-1 illustrates that: + +- there is the set of trail termination sink functions within the network element (shown at the left side of the figure); +- a (sub)set of the termination sink functions is connected with the performance monitoring resource assignment function (a kind of "connection" function); +- there is a set of performance monitoring processes (right side of the figure) within the network element; +- within the limitations of this network element, connections can be made and removed between termination sink functions and performance monitoring processes. + +![Diagram illustrating performance monitoring resource assignment. On the left, multiple signal paths (pXXX signals) are shown entering a central 'Performance Monitoring Resource Assignment function' block. Some signals are connected to this function, while others are marked 'Not connected'. On the right, the function block is connected to multiple 'PMON' (Performance Monitoring) processes, labeled 1 through N. The diagram is labeled T1530440-99.](34b047489058d6400b412cd0ae2334ba_img.jpg) + +The diagram shows a central block labeled 'Performance Monitoring Resource Assignment function'. To its left, several signal paths, each labeled 'pXXX signals', are shown. Some of these paths have arrows pointing into the central block, indicating they are connected. One path at the bottom is labeled 'Not connected'. To the right of the central block, there is a vertical stack of blocks labeled 'PMON'. The top block is labeled '1' and the bottom block is labeled 'N', with a vertical dotted line between them. Arrows point from the central block to each 'PMON' block. The entire diagram is enclosed in a light gray rectangular area. At the bottom right of the diagram, the text 'T1530440-99' is present. + +Diagram illustrating performance monitoring resource assignment. On the left, multiple signal paths (pXXX signals) are shown entering a central 'Performance Monitoring Resource Assignment function' block. Some signals are connected to this function, while others are marked 'Not connected'. On the right, the function block is connected to multiple 'PMON' (Performance Monitoring) processes, labeled 1 through N. The diagram is labeled T1530440-99. + +**Figure 10-1 – Performance monitoring resource assignment** + +Several types of performance monitoring processing are specified differing in characteristics such as: unidirectional or bidirectional, near-end or far-end, terminating node or intermediate node. The SEMF may support one or more of these types. + +## **10.2 Performance monitoring functions** + +See [ITU-T G.7710] for generic requirements of performance monitoring functions. + +# **11 Security management** + +For further study. + +# Annex A + +## Definitions of errored seconds types A and B and failure counts + +(This annex forms an integral part of this Recommendation) + +## A.1 Introduction + +This annex provides definitions of the following optional performance management parameters: errored seconds type A (ESA), errored seconds type B (ESB) and failure counts (FC). + +## A.2 Errored seconds types A and B + +The optional ESA and ESB parameters can be used in addition to errored seconds (ES) and severely errored seconds (SESS) to help maintain quality of service by delineating dribbling error patterns from short burst error patterns. ESA and ESB separate errored seconds that have one error from those that have more than one error (but not enough errors to become SES). Two applications of ESA and ESB are provided below. + +### *Example 1: Proactive maintenance* + +To provide high quality service to customers, extra maintenance measures need to be employed. Waiting until a facility fails outright does not satisfy customers in general. Different types of facilities have distinct failure and error patterns, and in many cases the failures occur only after a protracted period of errored seconds. By monitoring these ESA, ESB and SES occurrences, and knowing the failure signature of a given facility, maintenance of the system can be scheduled in a timely manner well in advance of a hard failure. + +### *Example 2: Work lists* + +There are often more facility problems that occur than the available maintenance technical force can handle. Thus, a means is needed to determine which facility problems are worked first. The analysis of ESA, ESB and SES provides one of these means. For example, given two facilities with errors, one with type A and the other with type B, a technician would select the facility with type B errors to repair first because it is causing a more degraded service to a customer than the system with type A errored seconds. + +### *Definitions* + +ESA and ESB for both multiplex sections and VC path layers are defined below. + +**Errored seconds type A (ESA):** This parameter is a count of the 1-second intervals containing a single errored block, and none of the specific defects listed below: + +- OOF, LOS for regenerator sections. +- AIS for multiplex section near-end. +- RDI for multiplex section far-end. +- AIS, LOP for higher order and lower order virtual containers. +- RDI for higher order and lower order virtual containers. + +**Errored seconds type B (ESB):** This parameter is a count of the 1-second intervals containing more than a single errored block, less than the number of errored blocks that is required to declare an SES, and none of the specific defects listed below: + +- OOF, LOS for regenerator sections. +- AIS for multiplex section near-end. +- RDI for multiplex section far-end. + +- AIS, LOP for higher order and lower order virtual containers. +- RDI for higher order and lower order virtual containers. + +These two parameters follow the same rules as ESs with regard to count increments during unavailable time. + +## A.3 Failure counts + +The optional failure counts are used to determine whether a UAS or SES count is the result of a single failure or multiple failures. For example, during a 15-minute interval, 600 s of unavailable time are counted, and the failure count indicates 20 failures. In such a scenario, because the unavailable time is not due to a single failure, the maintenance craft considers the failure as more severe, and generally takes a more time-consuming fault analysis approach. + +## *Definitions* + +The failure counts and the corresponding failure events for both multiplex section and VC path layers are defined below. + +**Near-end failure count:** This parameter is a count of the number of occurrences of near-end failure events, and is incremented by one each time a near-end failure event begins. + +As an example, MS near-end failure events begin when an MS-AIS is declared, and path near-end failure events begin when a LOP or path-AIS is declared. + +**Far-end failure count:** This parameter is a count of the number of occurrences of far-end failure events, and is incremented by one each time an RDI event begins. + +Failure counts are incremented during unavailable time. + +# Appendix I + +## Management information for CM + +(This appendix does not form an integral part of this Recommendation) + +Regarding configuration management, the SDH network elements can be configured via the following management information (MI) signals that are defined per atomic function in [ITU-T G.783]: + +- \_MI\_AcSL +- \_MI\_AcSQ[1..X] +- \_MI\_AcTI +- \_MI\_AcTI[1..X] +- \_MI\_Active +- \_MI\_AIS\_Reported +- \_MI\_ConnectionPortIds +- \_MI\_ConnectionType +- \_MI\_Directionality +- \_MI\_EXTCMD +- \_MI\_ExTI +- \_MI\_ExTI[1..X] +- \_MI\_ExTImode +- \_MI\_EXTRAtraffic +- \_MI\_HOtime +- \_MI\_NUTraffic +- \_MI\_ODI\_Reported +- \_MI\_OPERTtype +- \_MI\_PortMode +- \_MI\_PROTtype +- \_MI\_RDI\_Reported +- \_MI\_RingMap +- \_MI\_RingNodeID +- \_MI\_SDpriority +- \_MI\_SFpriority +- \_MI\_SSF\_Reported +- \_MI\_SWtype +- \_MI\_TIEEn +- \_MI\_TIMAISdis +- \_MI\_TIMdis +- \_MI\_TIMdis[1..X] +- \_MI\_TPmode +- \_MI\_TxTI +- \_MI\_TxTI[2..X] +- \_MI\_WTRtime + +# Appendix II + +## Management information for PM + +(This appendix does not form an integral part of this Recommendation) + +Regarding performance management, the SDH network elements can be configured via the following management information (MI) signals that are defined per atomic function in [ITU-T G.783]: + +- \_MI\_1second +- \_MI\_DEG\_X +- \_MI\_DEGM +- \_MI\_DEGTHR +- \_MI\_Delay +- \_MI\_EXC\_X +- \_MI\_FEC +- \_MI\_M0\_Generated +- \_MI\_M0\_ignored +- \_MI\_M1\_ignored + +Regarding performance management, the SDH network elements can provide the performance data via the following management information (MI) signals that are defined per atomic function in [ITU-T G.783]: + +- \_MI\_pF\_DS +- \_MI\_pF\_EBC +- \_MI\_pFDS +- \_MI\_pFEBC +- \_MI\_pN\_DS +- \_MI\_pN\_EBC +- \_MI\_pNDS +- \_MI\_pNEBC +- \_MI\_pOF\_DS +- \_MI\_pOF\_EBC +- \_MI\_pOFS +- \_MI\_pON\_DS +- \_MI\_pON\_EBC +- \_MI\_pJE– +- \_MI\_pJE+ + + + +## **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.798-202309-I_PDF-E/0070d5ae6e586c9cfa20085d26d3eb2e_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/0070d5ae6e586c9cfa20085d26d3eb2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bccf23b1fe2bc0390a721f5608221b9e6e8bd504 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/0070d5ae6e586c9cfa20085d26d3eb2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf7475cbe022baf6c0a1acdb5adab35431e142b9a906d119d815dc9de56bd59d +size 12296 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/014daefdecf9d847ca82cb5b9f50731f_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/014daefdecf9d847ca82cb5b9f50731f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a720b840197ab10fa7ab110ba5f35dfb77f7da63 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/014daefdecf9d847ca82cb5b9f50731f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eda575e45ced907fa91b1f5a116432452ce51ab069d8f897064e250b8cc9c791 +size 15698 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78fdd2019bbc2b43a62adb7ff6f9b21d3bf2e99a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db51c084e0fc4fece87fd6182a4897edbed9c7805ad10d8f2860cb3849d8b257 +size 14653 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/031de8ea6c5568a02faffd59b5c337f7_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/031de8ea6c5568a02faffd59b5c337f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..681d9b9e3cbd7389e2f508ec210480df99119961 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/031de8ea6c5568a02faffd59b5c337f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:773ba9c227093c8372d764696642747028c3a01ad867d0c075cf4b4aaeed6671 +size 210070 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/04244205ef763574ac5ef2df0513c14d_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/04244205ef763574ac5ef2df0513c14d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5768e0e39db36c20c408eb90d4befbb25b701fc4 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/04244205ef763574ac5ef2df0513c14d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a1c542448ac2d07f175bbc7dd9b89fd24621510ec7c1d02f4bd0699bf9be862 +size 7506 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/0697b56d281df40b93c568be995cb884_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/0697b56d281df40b93c568be995cb884_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ebb5fcc7e227e75341f0fdee7facf5bb3c45eeb --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/0697b56d281df40b93c568be995cb884_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e894b5518fe1289b7cba251f29fd2507724687303650a0661845b6db29894374 +size 58578 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/06ab63c9cae7ba781705155c8911f0b7_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/06ab63c9cae7ba781705155c8911f0b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e0dd1167c94ea912b4592ae869fec29a14be615 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/06ab63c9cae7ba781705155c8911f0b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18be71a2f101ee8d150fe0d8bc6c0bde5c33eba488d273b487f49c05c44ad37e +size 28095 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/0823130a6e07569e2fdb6bbdfc355d39_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/0823130a6e07569e2fdb6bbdfc355d39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3df28f26707913fde8db2c12d71505159704c1b5 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/0823130a6e07569e2fdb6bbdfc355d39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6a0423074d8de509f2e3131a843229e79711da6eb843d7a23c7f422fe79affe +size 10262 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/08246879b7e3340f5c7af67ca43e48ff_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/08246879b7e3340f5c7af67ca43e48ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e20bd61bf12ccd8534fbecde080382b082d50dbf --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/08246879b7e3340f5c7af67ca43e48ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c888f72266622f9645ad42e06f6292b6970f265c8a534990d42f97afb454f66 +size 75964 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/088fd744940924d37de4d237e53bb684_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/088fd744940924d37de4d237e53bb684_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4b1fad350fc78e54f524e8376245f21598075f6 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/088fd744940924d37de4d237e53bb684_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4527cca557abc82b8e2c2a08a8f7b3006a7abb0fa63468a7d8bb6846155da16c +size 74449 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/09cac7f879d0ec76600a5aeae680b95b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/09cac7f879d0ec76600a5aeae680b95b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f2b3d3f1f02532a7c2918e585c16d123fbdd6c5 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/09cac7f879d0ec76600a5aeae680b95b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b792786eed1cf402410f28eb43209b75824cb4acba946b716756131e9b9c595 +size 21082 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/09e709f61c6ce948e16ddcc0f7efebcb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/09e709f61c6ce948e16ddcc0f7efebcb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2c972fb5a858e0bded9ce048302b5f011829b04 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/09e709f61c6ce948e16ddcc0f7efebcb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e9df3011a6a09d4dddab2bb876e12164aaa7d44b90675004cb94e6bdcf9d2e2 +size 7797 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/0af1ba85ab6e4e50befbef3d63e017dc_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/0af1ba85ab6e4e50befbef3d63e017dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b59ec36a13f444f4f1224c03df84c6b3551886e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/0af1ba85ab6e4e50befbef3d63e017dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04aa8c13f3d97458d740cbb07a5602941086aee96b92b2bfb1379469c4a7cbd1 +size 12770 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/0b733c1407312c5b063e9bb458ef99db_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/0b733c1407312c5b063e9bb458ef99db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bbec99b5e1656d4fb1f9de957cbe5487ff33e36 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/0b733c1407312c5b063e9bb458ef99db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b8019ebf424876d1652b82c7fe82128e29f7b03a800febe2aa70b6d7274b164 +size 89374 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a85ac15699552c1d2bc9cc4909ca28d8d8856d38 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d669aa2affae2e6dffa2aa34c414fb9334cf6427e4cb0770db96f22a75b4ee87 +size 42328 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/0bce130a8686477232911728d05b4b13_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/0bce130a8686477232911728d05b4b13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19f1f083b203aa90abe7d309c43e219a0eced54d --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/0bce130a8686477232911728d05b4b13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d8785d15606345789b3a20758ac168d1672532b2d32944912127f05844906f0 +size 186539 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/0c360dc1fae48be6b928e626f9e7569b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/0c360dc1fae48be6b928e626f9e7569b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a07a81e4a6def975b4e9debc4d0b5020ca4ad02 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/0c360dc1fae48be6b928e626f9e7569b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3a404ca1e018289182462686abd5fe6b904d050c37595591d261b405bd6e90f +size 130806 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/0fa5b60804100c3aead10404f9f226f9_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/0fa5b60804100c3aead10404f9f226f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..030619ec770d7c2cf106786294c6dbeae037188d --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/0fa5b60804100c3aead10404f9f226f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d718a70087bc06406e7af91eb6d56739f7f0770ea27147a32ebd3dcd851217a1 +size 29379 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/0fdef87ff1fd322c626d1ff8df725749_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/0fdef87ff1fd322c626d1ff8df725749_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fa7f29e35b3f167ea255c61c6d1d5c78cfadcbc --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/0fdef87ff1fd322c626d1ff8df725749_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57bea94a86a60fe303a49f1c09a6087c98eb00035ce80587d8dc2d2494dbc2ec +size 99054 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/10f4e3a2f3c016555ee12a5b556ba834_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/10f4e3a2f3c016555ee12a5b556ba834_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90d78380111009b8058f48455a0c54d39fc0fdc6 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/10f4e3a2f3c016555ee12a5b556ba834_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dcc2aa410b8de833a9ae00933b80627df1af10d947eebb727dd19fa447273f8 +size 67327 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/143c8ee1010bf7669caabfbed815df1b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/143c8ee1010bf7669caabfbed815df1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecc10e24999318d6981a24d5015213c9979abec6 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/143c8ee1010bf7669caabfbed815df1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf4bf809fc5e488e198d4f0a61a6d30e9be3330c3af71f3a0319be2371ba5573 +size 51853 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/14d497ab16a07c50b3215ffef2149ab9_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/14d497ab16a07c50b3215ffef2149ab9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8448225502923d12a7b30ed3e307dab6da5557e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/14d497ab16a07c50b3215ffef2149ab9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9a2286a49476efef4d44c8746b3739ff3fc819db55c6789a81e49d4c69a8758 +size 42258 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c958f8b9be468102786f9fa84d35e09767398daa --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70379b5be8dbdcbf3f52fce71fea7bbb26da6d26d093f4d023395ba3b46f5a3a +size 28438 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/1846b9e1673ade53caa7358696bc1794_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/1846b9e1673ade53caa7358696bc1794_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbc78ca6a12e736fc9b6fd8b1a037f578cf289e5 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/1846b9e1673ade53caa7358696bc1794_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5fe5be8b57906bb5e63ab8914b08f84f4c9abc8a15fabf7acda25ef73378847 +size 103465 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/189062b6daff39a4a33fb150b0aca878_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/189062b6daff39a4a33fb150b0aca878_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44e95d0ba86927f8d4d277f6307ce5da5bfd2e6c --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/189062b6daff39a4a33fb150b0aca878_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:092b26219b7287643960a2c2bd2c92e0229c82a6e216229bc3d04ec439625ed7 +size 20409 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/18e10a200cbafecb4114d25fa128b703_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/18e10a200cbafecb4114d25fa128b703_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..662221df7dfcc2fd6cc328419186a2595a3c6669 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/18e10a200cbafecb4114d25fa128b703_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:303b37e143cd2d038756178b65950080e5e09a7212fd863f5e13dbdc5312972d +size 8840 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/1a1c6e97fdffe8ffed7b997b7e682d3c_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/1a1c6e97fdffe8ffed7b997b7e682d3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff8b0fdcc4fed4339accd0212c3a0bb54dab7527 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/1a1c6e97fdffe8ffed7b997b7e682d3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d619bb15f4cb8c784b98779e44f17ad37aba89c6a806e8c57cbfe15d3c51d23 +size 154357 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/1b683c1801ad8e24cf113cede25b36f0_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/1b683c1801ad8e24cf113cede25b36f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75de017cf05b8c4cb8bd30caf76569cd739023af --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/1b683c1801ad8e24cf113cede25b36f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e001cff98c3daa2f6102e5d4597ddb976fdf69410ffebbe16aa836a46b0c0bcc +size 174372 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/1c453289f9bc736ca66bdaf7178601c3_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/1c453289f9bc736ca66bdaf7178601c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec37edf73e875444d4ecafc2c03916b6f4b6a160 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/1c453289f9bc736ca66bdaf7178601c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b8ad762d4f8e2c20cd379b6157536531ca04e4b6f2dcace43717e2596835f8b +size 14232 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/1cf7488717213a910c805cf83ee186ee_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/1cf7488717213a910c805cf83ee186ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acd93d3e510202b8660899e4e2bdec8e6607e574 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/1cf7488717213a910c805cf83ee186ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dca0858f3d7d23fa72466b9a8855a26cdb9fd8e2a9f3ae8136bf1c3340997818 +size 13223 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/1ff7740e14c18789657d277030fb69ce_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/1ff7740e14c18789657d277030fb69ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16d9469e48eb493337fee50c29de2f1576716388 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/1ff7740e14c18789657d277030fb69ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecda96722d5a0ebe538835b906656be659bec9a9747557c255d712c8c90df6f5 +size 10307 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/228db097d546afebf934a1befb86a0a6_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/228db097d546afebf934a1befb86a0a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7418edc973e45a93a244421f9a36a69b5b7508e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/228db097d546afebf934a1befb86a0a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9028edefb936b192839a1ef2a77d7b26d435e07ebcd1b2574e96d091378b2d19 +size 33154 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/236b5a83f488c361479b9b44e462f978_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/236b5a83f488c361479b9b44e462f978_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24034264767a6456aceede4d6ec5b565283264db --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/236b5a83f488c361479b9b44e462f978_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:999189bd541282c7eacfab59aab03714fa470d8a96cef0548e4be0419d5487ac +size 19960 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/238754529581b74f0696943d436494bb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/238754529581b74f0696943d436494bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf0f93ddff9275ec7d96c26d7d01ad3f4d8ece9f --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/238754529581b74f0696943d436494bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c43db2010725ad040ac61a506b3127057d8005d5e1f75a290486f6f83271a2e5 +size 28250 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3eb355fe5b6102f8fd3263dd00b04cf71deda01f --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c03ded7a63c67bfa03b5244ca6e8617dc79718c56ba0f7eba75fa91125c1e9a4 +size 80792 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/2576306a75b1ca6180aa172236c1ca07_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/2576306a75b1ca6180aa172236c1ca07_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3aef4798e9a496531d19b2a8b2dc0ea042b5cd7 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/2576306a75b1ca6180aa172236c1ca07_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:337e57e380e0da5c025eb765b5e1f3ef6383b931dd39a23c6c3e5ddf33a50ff8 +size 54717 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/25b2ef5bcf30bfa9a31d59f48fddb3a7_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/25b2ef5bcf30bfa9a31d59f48fddb3a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f50fa3c6203d5d6eab51dedc647ae90c6255a501 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/25b2ef5bcf30bfa9a31d59f48fddb3a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e81288d4c8276463c96480936553ce2ba9623e4babb58f427f51e51452ff1e82 +size 20068 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/27c0455a3b08749fed8057467366b0ce_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/27c0455a3b08749fed8057467366b0ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb9098244fb1873db647a8cd4ad5004775cd4b2d --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/27c0455a3b08749fed8057467366b0ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf301b85cd1132d9be3dc2be6496fe4d9fb0fbe56108df8c80d6cde407d69aad +size 13496 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8fcff86e828310710873266843cce3a51e146863 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:643d0d6e86a743d2de860a643d1df0b3ded93d1c3fd022d496e899662ccf9332 +size 106173 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/2b817d2912f95cb0ab93ff621a3f0a5b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/2b817d2912f95cb0ab93ff621a3f0a5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98aecb54e8697ccd085305b175497fbcbdd7952e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/2b817d2912f95cb0ab93ff621a3f0a5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eed7fe0d15200276e3625b163028889508dca6ec6a5ca0571441c5ab5e77f9e3 +size 14445 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/2bb36c10542436112c2e54d97771bf32_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/2bb36c10542436112c2e54d97771bf32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3b1bcd1ecb9021ce94a8a3358d8f20fd45f91f3 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/2bb36c10542436112c2e54d97771bf32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38a118fb0dcf942b5dffaa4a2c0dd3a0fc2dae53fbcbccbc01d4b2de70a6ec6c +size 45711 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/2fa686ed8033ac35efddee0c7be47d59_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/2fa686ed8033ac35efddee0c7be47d59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..453787c96f1c12c2fe0a6d836f0a420c6722385e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/2fa686ed8033ac35efddee0c7be47d59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff97b2e60d124c16f64af838942eceb92675ff2e784213a41f1f1c1f2872f72f +size 43506 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/2ffdb0621c4918479cd1ac7a531b1b92_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/2ffdb0621c4918479cd1ac7a531b1b92_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8349f98f80b3c3c8f383b3d2a0c8da74f5e2c39e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/2ffdb0621c4918479cd1ac7a531b1b92_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba912864c479d3fb6ff5d9bea3de5528dd97959d659f67df79d783fed6c466f0 +size 20961 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/30b76717cca15621840d1c16fff50f89_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/30b76717cca15621840d1c16fff50f89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74561f6ee64d351a7dbcbf58978ba6c6a3eee5d2 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/30b76717cca15621840d1c16fff50f89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0c778d3f3c3f84aa63c62383820b6b5a7bb8e4d0d895ff580afc6dd450f73ea +size 17553 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/32ce3ed5531f18aba05215c8f474bf49_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/32ce3ed5531f18aba05215c8f474bf49_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8fc3460033684da1502cc7374c85153254f9ce47 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/32ce3ed5531f18aba05215c8f474bf49_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6145a0d5fffee5890a97f796ce3dd320f7f5ccd93fdbdf0778f2cf98eccb25d0 +size 164574 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/33859177822cce0c1b03fd3d37de14f6_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/33859177822cce0c1b03fd3d37de14f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36fdc772f2a4a32a15d066eb11d72641122daa47 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/33859177822cce0c1b03fd3d37de14f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b41e283cb14548e448f4276b987786c72c977a514cf6cde8c9833fc6643799a9 +size 63869 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/3440b6ff4ee9fed9b432fee67868ae8e_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/3440b6ff4ee9fed9b432fee67868ae8e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..002e76f847927b392a3ccd9e111be26f88f5160a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/3440b6ff4ee9fed9b432fee67868ae8e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb0887929a98eaf8b511c72270cf7f13ee6135d648c633dd336992042c4bfd74 +size 23193 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/34f46103a0c07981b0b51490ea639e25_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/34f46103a0c07981b0b51490ea639e25_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5121c785111376b7dad2b340ba92db1f7aabb451 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/34f46103a0c07981b0b51490ea639e25_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcf948762430f7fc009ec963790919151cc2004773827734ae725ea661f3fb59 +size 9797 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3869199f85c772f43b9ca4a6b1371137e3455375 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b81ff969dfe12e32b8ee8a92d49f020f37bc0604a99ebb1a48f64046ce0e7ff +size 110031 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/385c524299e3256900f891bc068d62b6_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/385c524299e3256900f891bc068d62b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92467d03f7ed6a5cc7987f0237922228d0db7784 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/385c524299e3256900f891bc068d62b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5afb2f192df5b52cb3c50a056c112f6343920c3f13632fa4b5622eb60e80557 +size 92428 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/39729be7ec83c3de8e480061966e4505_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/39729be7ec83c3de8e480061966e4505_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82408549de65f7ae686348e286de6b4bceab90d9 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/39729be7ec83c3de8e480061966e4505_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e00247bd2ff29678e174b416028ef05df845abc4c95bc2df485640b353169119 +size 66635 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/3b330f29256259f2a9854f1c371ed269_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/3b330f29256259f2a9854f1c371ed269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8c6ea486fb37b4be185bc4dbb44c29828f9eb71 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/3b330f29256259f2a9854f1c371ed269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:587f121cfd78ece31060cf5bd536ec2b279b9545b02f63ec954b8c531ac959cb +size 14273 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db4b1224fc4837163f27498688b6aeb382be97f0 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c067eeb7e079da97ec17d611fe04ee596940a00f4411e2a868a2eda1fa7018b +size 74272 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/3c721884a92b102becb43b52f6110e47_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/3c721884a92b102becb43b52f6110e47_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..946ca891f11af2d8e344362c5fa6dd3fc9a2140b --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/3c721884a92b102becb43b52f6110e47_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21818165dada82588e1bf5f29382bad70dde3c35a5ac4b0553598a24d78ffe1a +size 69679 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/3d590ad29ecfe728f07432e6fcb59064_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/3d590ad29ecfe728f07432e6fcb59064_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5885cbe3736503516a72649751d615b966350ac --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/3d590ad29ecfe728f07432e6fcb59064_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db6ea48a89d12bc61e6cacfbebb00f8dfeecdbba15246f43df037ade3b44ee5c +size 24173 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/40b685b3ae31d84f5f9edf37cbb945bb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/40b685b3ae31d84f5f9edf37cbb945bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a19e3fe6c2311212f3ea052205c30df60c5f2a85 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/40b685b3ae31d84f5f9edf37cbb945bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bdc345091d87c1a3799acff176ef54b5d5fb1e79a6f902e8653ce2e63107e17 +size 102947 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/40c6fe38cf97a637027a6a1806b5546a_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/40c6fe38cf97a637027a6a1806b5546a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c95704b28d9d266126b21f43fe975d3a734d729 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/40c6fe38cf97a637027a6a1806b5546a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d530e7a9065dc38f4210b5feb7005d11c92ba7d3be4073d71d66d39beef06a98 +size 12812 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ad5ddd376b55f45e68e52cd4d7b7dd19965fe5a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f004aa2f144417f7c534fc7025a74b037dcd6aafcadc6dcbe606b39ad807eb4 +size 119356 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/43aeecf3cbc60c4418d560d8a4512ebb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/43aeecf3cbc60c4418d560d8a4512ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8566a2aae53b68b4945d197b6b50d3374f5823a9 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/43aeecf3cbc60c4418d560d8a4512ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11e7b6c2099e74dec3ba1d2941fc2ad1bd5e6428e2bbc2cdbd0e4535c9ded5b1 +size 93274 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/43b05bd1b6ee31fba18d3eb683903504_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/43b05bd1b6ee31fba18d3eb683903504_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..555d8e910f0ea720dcd863274b0176bcf0e598aa --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/43b05bd1b6ee31fba18d3eb683903504_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:757cdd0df89b3e5a200c9e07792b56038bf66ed4a62588b030e4bdfde5c1e6df +size 17379 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/43ff52fe5a7c6990f4f0d5e0ca55d4b4_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/43ff52fe5a7c6990f4f0d5e0ca55d4b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc14fd6f4c1a04b5f4dbf38b4d0c760707da85d0 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/43ff52fe5a7c6990f4f0d5e0ca55d4b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b20cdc53a705ba8e4737ba76b573c3134fdb2cd9c10ccb39f1071b37b796a9ee +size 19713 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/45b71f54324c8fd8c2830610b367dced_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/45b71f54324c8fd8c2830610b367dced_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0b1d39d28166c7ca21b5689e2dd7b381f30a3e1 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/45b71f54324c8fd8c2830610b367dced_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a002944552b2834a1426e90e5b89a941c0f865898c254b1242e5b579e8c62d4d +size 14110 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/47aaa88afec21e26eb33420078f4936a_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/47aaa88afec21e26eb33420078f4936a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f82f82ac6d324bf446924501c2e5d2cff9d0fa0 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/47aaa88afec21e26eb33420078f4936a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5559b743c6a24ddb4253d2f54f2094ec9c043b76100d1f053e23546ee2cae85f +size 109277 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/48090d8f1db2e826aaa740035aa12ecb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/48090d8f1db2e826aaa740035aa12ecb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77750ede5cec914ba9b056e67973a8213ffc631a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/48090d8f1db2e826aaa740035aa12ecb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ed3544c5e8316757b6bdcc0b5e65d14f6a539fbeed8bd45b24d18cfa485ee00 +size 67788 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/4834b6d862f59622ea6314c723c7572f_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/4834b6d862f59622ea6314c723c7572f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f43c79aa6ea2db0d1cdf9c6cdcf0fccfd761fd7f --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/4834b6d862f59622ea6314c723c7572f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e558b2b744409af7af77ccb7d9f636a4387e0d263483437399bcb086fb8d2531 +size 41381 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/48b17e34bf39cb8a801a634c791250c0_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/48b17e34bf39cb8a801a634c791250c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b1aa64ba678392f85385dc83685fdd1470aff0e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/48b17e34bf39cb8a801a634c791250c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54d87b5b5a08455fd84198293e69078cbc2d002495d8a97926e62241832d731f +size 39055 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf575afa363deb45c8c1304ede27cffe853daf9e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a94acdc30c75af86e39bd33316c1f7d2e2f2eb1736e5c0a093d34764e830a55 +size 11209 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d13eddae96b5a1480cbf1ecc56e923830c8b35a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e1bceb38ec2678de8fe8b3b3d59216181fcc120a946266d8f70b516faee17c7 +size 7973 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/4a390493f601ce1ac6b9201db4e28b5a_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/4a390493f601ce1ac6b9201db4e28b5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d0f41544d9d319d80ad8e99f8e311ce5b67e586 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/4a390493f601ce1ac6b9201db4e28b5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cc1fce1fa353f58f2113b0f927f9f184acfb2481a2ef55d3f6506404885abcf +size 11471 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/4a5c6fefcac9340ea7f9df373873cae9_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/4a5c6fefcac9340ea7f9df373873cae9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4032630732e3f6b72ef45ef78f3f6299f0e0d4e6 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/4a5c6fefcac9340ea7f9df373873cae9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4244955cac10ad72f986a5bab574f1e4650143fdef52364ed3f6b2e0420015a +size 84830 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/4afdd54473731079bf51f7d1acf72187_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/4afdd54473731079bf51f7d1acf72187_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58fa84a37b0ccef3d5e8a77ab6eadbee8674158e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/4afdd54473731079bf51f7d1acf72187_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af8f59534d4d6894cb06ad15ae5e5c5babb5e02d5e682fa490e8edbe412a6be7 +size 12827 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/4b4b9c9c016880edb872f25cefc85eb1_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/4b4b9c9c016880edb872f25cefc85eb1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e26e2def8be30e0e7aebaca7612693ee3e6267e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/4b4b9c9c016880edb872f25cefc85eb1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37ee1120b6cf722f667e607850c5d120440c7a66209e91d87dad044155cd2ba0 +size 13129 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/4b9e2f848d66a0b3c2d4553b965933c7_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/4b9e2f848d66a0b3c2d4553b965933c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7396ee22abb461914f80d83a788b7596a58cb38 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/4b9e2f848d66a0b3c2d4553b965933c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ef05a4bf49923442278e521dc670488c8b80e50c5723df21d88bea053b7c932 +size 66782 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/4df70569f4cc27db5625fc75bdff68cf_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/4df70569f4cc27db5625fc75bdff68cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e09a70752c3a7d9fca77d78f07b44518afe5af1 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/4df70569f4cc27db5625fc75bdff68cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d47ef5885b8ccff8946796edda60880ed5d3cf7e289b72094cfbda0c3dc21b0b +size 21274 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/4e09aad97504825adf16d63ace42b461_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/4e09aad97504825adf16d63ace42b461_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6378c54bf66e980fc412a5ce493719fd6b603b5f --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/4e09aad97504825adf16d63ace42b461_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9edf09debe3e96b7bd3135aa08b481997a8adee678362ee723ebc387ba836c1 +size 81072 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/4e716e2091c1c947b7a687ed4e6dae2f_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/4e716e2091c1c947b7a687ed4e6dae2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..517f7cf61dddb06f462cb78fbda42aee09b3b642 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/4e716e2091c1c947b7a687ed4e6dae2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4fe98ee338f282b862f9846987d7b85add80b35c2b69deda285990c2f97ce7b +size 32994 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/4eab0234f29827bae0c6e71fe650aa63_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/4eab0234f29827bae0c6e71fe650aa63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb61c4e99485cc67053b23007b98950a4d89a9df --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/4eab0234f29827bae0c6e71fe650aa63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:121098895c02fb0539e6ce7adebfbe6ad0b61a4cf461da414da1836418ae4c05 +size 30114 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/4eda1b9e9c4f581b9747ffacabeae936_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/4eda1b9e9c4f581b9747ffacabeae936_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a200be65fd723375ad076e3da03a72031726da3 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/4eda1b9e9c4f581b9747ffacabeae936_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cadc6638d20bd71e7038adb445f19a45cd5ea276c3283699e98c57e181799ab +size 135191 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/4ef412e08808c40e0beb7808d36b9379_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/4ef412e08808c40e0beb7808d36b9379_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a803ca3a02f7b71461d7f2daffbe8624ec83176b --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/4ef412e08808c40e0beb7808d36b9379_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d1a666acf0f79f9d5cf3f1d0eb1e405043673835c34e2f9adde95f4abaeefb7 +size 21472 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/5083128e335a383c042e15d2d8795c95_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/5083128e335a383c042e15d2d8795c95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f16232d051524ed0a7d7db69b6287c4c1cdb047 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/5083128e335a383c042e15d2d8795c95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed676e52e981a097cd0fcefe16542c1759531e9df9803030a913ac88235cfb32 +size 45305 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/50f72073c616cb3d3ca3af04a0c3a221_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/50f72073c616cb3d3ca3af04a0c3a221_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93cc6b47b19187e767a7b950ed34fa2ff763d00a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/50f72073c616cb3d3ca3af04a0c3a221_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efd8d1174ecd424b5aee563c115ca6393ab55ba2d53d1ee02df5a338d347b3ba +size 25777 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/51b3f989269d40b52bbf69c7a448bf52_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/51b3f989269d40b52bbf69c7a448bf52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd0fc1a6a7a99ddb64dbbb30b497a1f91acb277e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/51b3f989269d40b52bbf69c7a448bf52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2eddf30034f772d2e4dda3fd9d990903ad8e980caa444555ab5bab3a12268de0 +size 210319 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/539dff67945f344becfdd7bebd3b7d69_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/539dff67945f344becfdd7bebd3b7d69_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2380fd14b2642e774aaf6f81f57cd48e5311bb98 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/539dff67945f344becfdd7bebd3b7d69_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64911b9433c9f5d25cfe25ccc774e9971f037c704f681959df0f945b0f2b676b +size 79651 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/53c60f255aa58c330efd23c77dfdc762_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/53c60f255aa58c330efd23c77dfdc762_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e0fc8b798894398112e0d293ad8017f6bbe667f --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/53c60f255aa58c330efd23c77dfdc762_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9c2717b6c284c4722fe05c453d14a288cc4a789b7fddf1cc3d3473b34662790 +size 13997 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/5546020e0c70645fd46b8829e2e3c43b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/5546020e0c70645fd46b8829e2e3c43b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f82a5c8d7cc0fabc85c71e0f0cd7882ab705cb55 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/5546020e0c70645fd46b8829e2e3c43b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2854caec41823975e0829a2ab7e099d3cf5614316614bed1f85a774bc456aff3 +size 26864 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/5817c9e42aa8e99964a2845d4adee0d0_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/5817c9e42aa8e99964a2845d4adee0d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25c96d6521501118fb930fee963d9d5210aaf9fb --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/5817c9e42aa8e99964a2845d4adee0d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24e4594f4ac8c3cfc435eb752ffcfe8f646e279c7bfc2a326ef561a098bdddef +size 10512 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/5aa9a1f9f87b2e03c5a516b13ee62612_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/5aa9a1f9f87b2e03c5a516b13ee62612_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62aba0cd2cea95758214c5fde9a4b6b34d9f57f3 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/5aa9a1f9f87b2e03c5a516b13ee62612_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbffffb400f0c47a134c70261b62d1988f9992d81aa4cc41ce344691aae414ad +size 26934 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96e13328cfca669f9399c39a468c6d4d70950fe4 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecc8c4ee94a0420dfc3c38492f556ad52ca2f59315dc8371fd1f85eb004a0431 +size 27878 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/5b9a924d48ea39458bd16a3c89a576d5_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/5b9a924d48ea39458bd16a3c89a576d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..872daa4ec0bcbcdff3ede5e90cd6dff21201d7ac --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/5b9a924d48ea39458bd16a3c89a576d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fba0dce218892b39a8d75433350bd3879209468c918d7e2f33955d3f254f1e84 +size 9789 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/5bab55ee2db5fd011c7dc277224026d7_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/5bab55ee2db5fd011c7dc277224026d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28096cc4351b4afc028eda8b8385d81f1a695ce1 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/5bab55ee2db5fd011c7dc277224026d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c83543840e0f1f7f4b5d9e493cc195a9b167695913f02f7e1670a8a901382254 +size 128391 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/5cb3b242ac7ea1fa7007ebd51b80e5b9_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/5cb3b242ac7ea1fa7007ebd51b80e5b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc777910a4d08261a75b0fc7d1152ceee6902872 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/5cb3b242ac7ea1fa7007ebd51b80e5b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f30e2b7b431384cd75d612998f169267add0aadc7ebde6cb5a2af5b754988f42 +size 7642 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/5e90ca04dc493a9f9aabbdbb720d39d6_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/5e90ca04dc493a9f9aabbdbb720d39d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60861a430d36f9f3c99b2e2eee40085972d5a373 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/5e90ca04dc493a9f9aabbdbb720d39d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02fb25b3aeceefc7b22410b34f8b5ce1297607fe91acda337ecc1476a670ab24 +size 57592 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31818388be585a17d753db623b7bcdf43b72581d --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e06582e5535c4addeffe90ea27d7a8ff2d51551961ba2bf6f6c146a9c3de943 +size 68329 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/5f1f8e1973a0dd08d313a5aab38502ad_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/5f1f8e1973a0dd08d313a5aab38502ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a6f4aeb53466a0537cef11992b05554077eb426 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/5f1f8e1973a0dd08d313a5aab38502ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e6e17ecd81c2c43db51dc7ec8cf58c3689dafae590bdd0f6f8d593f2bfb7a6e +size 11203 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/600c8f9d34f98c395e29c266aebfbd8e_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/600c8f9d34f98c395e29c266aebfbd8e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e939946fdc958f44a4ef2f712cbc513d090e8d4 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/600c8f9d34f98c395e29c266aebfbd8e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88530eb8a11d283c40e24d212df0da0842b9bdade8bd388d144a57cd87f001df +size 139008 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/60590b20ec9994e388840f5fc4572e39_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/60590b20ec9994e388840f5fc4572e39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8aedf424b38b3fdfec325656ba3c39e0bd164a88 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/60590b20ec9994e388840f5fc4572e39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0196590a4940d7bd71f59a539fc7c1bac28383ff59d9ec9e4c1763ab30b7a7b +size 10725 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/625663deae3d429f79ae6d2781986e2c_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/625663deae3d429f79ae6d2781986e2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b9b584e997f50ac1ff8652590954df667bca730 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/625663deae3d429f79ae6d2781986e2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3053bbbee795fc1d308df2fc4ddff048f136d686a7e26c80b95fe6f33e47efec +size 16970 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/637fa2ec2e8639bc53dea306e19b7c05_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/637fa2ec2e8639bc53dea306e19b7c05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50f85914f2c9ee531b768da90b6ec380aad45b47 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/637fa2ec2e8639bc53dea306e19b7c05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64f9ae57d507dc6cd89fbb658e8978392a95f27def91a25c100bc22101cf7dc8 +size 86015 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/649f424fd35ea31f622163506a6148ed_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/649f424fd35ea31f622163506a6148ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11a417ba931f476f3b909688fc9067f7dd56c426 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/649f424fd35ea31f622163506a6148ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2059dac4010a35713bfeb9783894e297d8bee4a71dfde17506119b5225654749 +size 19457 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/64b6966c073f3c3789a8070dbd6106c5_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/64b6966c073f3c3789a8070dbd6106c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a467a0a63a45bba08bc83cf97e0e37efa43285f0 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/64b6966c073f3c3789a8070dbd6106c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76bfee97385a29d5acc5f95559b9c65f5be507995025191c974c747eb0b8cb5d +size 149970 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2824bdc4090881c5bab621216f0a75f778910a1d --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea5ed49f742ac8efe74e301e5829a7204374e3eef89d4b64e18c1fbd633f7762 +size 12576 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/66bf96eec8f739d5e7c9957a178e34e2_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/66bf96eec8f739d5e7c9957a178e34e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0018d5b1ebc534e5890e9144f62c718e1e6b6f4e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/66bf96eec8f739d5e7c9957a178e34e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f813d1d61efc063bb6765623a7b5d297a1399b0b0d2ddce15956e67e46571ebb +size 58347 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/66decd3c38c5f918f528096090219e15_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/66decd3c38c5f918f528096090219e15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aaff979045addd5fdd99f47b78927cb0d51f135e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/66decd3c38c5f918f528096090219e15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2d117bf0b85b06bd265a6722e652cce5b12c7416dda53af7b221930e2cff618 +size 9149 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/675b316a907e66765fd392b545e60854_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/675b316a907e66765fd392b545e60854_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcb9a4663dc78646a32d9f2b9fc93b1c77092064 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/675b316a907e66765fd392b545e60854_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:340587d195f76cb92e741c2123b641a09b8f06cf8e86a7e1534738ea5ebd7a8e +size 11698 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/67cbb5a621a69ab58534bb3376bbb724_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/67cbb5a621a69ab58534bb3376bbb724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3621e04fd6f1244e4483ad716b88e513fc1e8fc --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/67cbb5a621a69ab58534bb3376bbb724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bcdf042f5a8cdaf3846bd3d5339dde7e30b417cf1606124ab1b56ad73a31670 +size 9720 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/6d7989325053731fda7ae4de0e946b24_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/6d7989325053731fda7ae4de0e946b24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..616aa2ae1c0a80783a3722b5c6d97ba94fcd775f --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/6d7989325053731fda7ae4de0e946b24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c9e6675d55f9396bed8f2cfac343286eb1af506c8c17f2fb77879e99a62581c +size 34692 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/70fd9003b407d059f32275b212482817_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/70fd9003b407d059f32275b212482817_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab60c8581c5a9f7e561348c62355f12c9fb3a3d1 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/70fd9003b407d059f32275b212482817_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f03a26ad2e8e8b5bc82ec667c215d9bcebf9d9944b715a3b72998bc809f50ef7 +size 154091 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4dd0f2324cdaf76d9587b80738b047f9c2c1a4d6 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9046b0b07a3e22489fa5a6a2e639bd869c6093f8386bcd7380508126481aa2cf +size 26142 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/7450203d6606590615fbbeaf2f663b36_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/7450203d6606590615fbbeaf2f663b36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd14d2ffb4b75c1de61597135e8a7e55bc64cedf --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/7450203d6606590615fbbeaf2f663b36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a992793d216a3b35dd3506f4d219f93e31ca400af534b376ab1c9a1c1178540 +size 13001 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/74c3f93d2f82f78de6a3925bb8e15977_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/74c3f93d2f82f78de6a3925bb8e15977_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e04dcb595a58adb6b270d938810a0f9034208686 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/74c3f93d2f82f78de6a3925bb8e15977_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa8d40ab81e92148829ba54f64c293dee6af31a5fd5b02d92f292024025643c3 +size 47910 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/7a4168ad9aed51fc9c5f121a863b8dbb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/7a4168ad9aed51fc9c5f121a863b8dbb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f8e63d1a109febe0c5699b9eb6284d95c536a83 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/7a4168ad9aed51fc9c5f121a863b8dbb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b15fa9e1cc48b43452bddfb202c6f4353e6302f5913fd5d0abbcba4613170358 +size 87873 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/7ac0d7b4763471d7c6dee8a2ce125b6a_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/7ac0d7b4763471d7c6dee8a2ce125b6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56519634e1c8f5507243d5c3e4d9b275a19f4971 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/7ac0d7b4763471d7c6dee8a2ce125b6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b43613978b269a5062f75705c17d73df1ba90d386f3986201e514f5b69cf570f +size 31428 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/7c1f9e78e0f033d391b687f1652f6e47_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/7c1f9e78e0f033d391b687f1652f6e47_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..764ae611d3c58c39e9dce9bbda0127552118d28b --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/7c1f9e78e0f033d391b687f1652f6e47_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8845cac217e33bd4d02bc15a1f9ed21e90b8bf480d1e0992b62ddda5858f87d +size 77597 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/7c6fd006fc4d304794392d41fab4ee10_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/7c6fd006fc4d304794392d41fab4ee10_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b21d6591467b24d1d5451d55a7af5d513a30f4ad --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/7c6fd006fc4d304794392d41fab4ee10_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60e011af643600f958630e1a49161f50722e804bd74bc7bf32376a36b35a3e48 +size 6087 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/7d2489babb3bf789de160fddd90c535b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/7d2489babb3bf789de160fddd90c535b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bf5c2984011bd79b9f790f86d937770667c1003 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/7d2489babb3bf789de160fddd90c535b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c8b78be665d9a13ea64b9ae2f0a0651632ae6c8416c40a0ced1f88be48b8a6a +size 37588 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/7d78469417c76901ecf6e36600a721cb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/7d78469417c76901ecf6e36600a721cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b803510d9f5dc23cb387d05811c9a26acda7467a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/7d78469417c76901ecf6e36600a721cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab2512ca24417ed53a20b78b6e11e67c59eadea1b9a7f206d57e51b4a4325674 +size 25757 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9817673539c6d86e2083701cd1db48fef5569d5a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a98bb55f3a2a89f0b31988c3ca8c42441870f931f3094dcadc49479dd5bfa098 +size 15011 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/7e19e42b9cf476a0c228935fa4d635d5_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/7e19e42b9cf476a0c228935fa4d635d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50837fde1b645f3dac9db1abc5aa8569bf3983e2 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/7e19e42b9cf476a0c228935fa4d635d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc5ad367257ab15f9e53a16876f736bb7a6d0d378dea954b909836fa024ffa51 +size 24521 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/7e1f88e0cc7be8060240e12252a833d1_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/7e1f88e0cc7be8060240e12252a833d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8829181d178dfc74cfc510dcb839a2e416315f6f --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/7e1f88e0cc7be8060240e12252a833d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6770dbe332a9477447a6e79bb759676bfaae44a16aafb088a997e07b4f9aa73 +size 57028 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbca24dc48f4253d0a049f128f06d46df334960c --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:054c84adca6ca265ae77c2c0d4e40020bab605366298df89ebc091e8aaa5c2a5 +size 15909 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/81e0bc85cbb6bdb4779d4af6d86e80cd_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/81e0bc85cbb6bdb4779d4af6d86e80cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56cc9b3a2768682a702d18da162f003af4874644 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/81e0bc85cbb6bdb4779d4af6d86e80cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb9bd1545b6746a7ae52b1c4054b5e1ef1bbdaa1deafcb9ecb7533f9ace74adf +size 49969 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/82a7d47fd0aee910d598c30998c23e08_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/82a7d47fd0aee910d598c30998c23e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d132e0bc6756acc962a72e0552c983d1cce88a9d --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/82a7d47fd0aee910d598c30998c23e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b000c0c39691b4aded9ee9ad072bda1664b3eef1303a39cc7fb619b68c28add +size 33869 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/8453d7dc9225bb210abd09f5d0af3c9b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/8453d7dc9225bb210abd09f5d0af3c9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e55767f0c5a6a6a6cf5ba05d36d5e3509372c050 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/8453d7dc9225bb210abd09f5d0af3c9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a0f7c3d7ee104ccf9a7f13f1b0e4a6f895d820ea66fac9f9423d797def9f2b9 +size 110654 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abda52cbb1047d6649f89e40c898a1c33bed7267 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f3b7e07231c0f3e116c99c493bdda98ecd52313b6735faa6cea23815cf3162b +size 7190 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/87253027e8bb658bf7d211cb23248bcb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/87253027e8bb658bf7d211cb23248bcb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a68ee8fdc3454161687ea55de5af05b1bad3cc2a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/87253027e8bb658bf7d211cb23248bcb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:678bf45fecc1fe4b1673d18d13b72e1f52202d96b154ed05fcdb00cbdd52b51c +size 35926 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/8862d966c9597ffc01bd5013ca9885bb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/8862d966c9597ffc01bd5013ca9885bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..475782c84c15a0b3d7843a8b129c50dfb5aa59fe --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/8862d966c9597ffc01bd5013ca9885bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b2a38abc6b2b6e762b3c6ea48bc2f432e1163db516d0847fbca64ba16b60aea +size 24642 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/88fa0e6558e55b5d54f4d3029b21aabb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/88fa0e6558e55b5d54f4d3029b21aabb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afda49cb8ebeaedfd14f49131664b657c85a7e87 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/88fa0e6558e55b5d54f4d3029b21aabb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9baeaf3981b5b9a567805399b6c1605c6fcc90e849f50da2d52127be37e94a5d +size 15216 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/8b964751bc72fac53d873c674d3fa937_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/8b964751bc72fac53d873c674d3fa937_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aec4f7a14cfbef91842cace8f33298d8158fda31 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/8b964751bc72fac53d873c674d3fa937_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf700fc7f3ca73b2c7dbba0486acaa68bfa5fde0aba4a37ce250902db0698a23 +size 125443 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/8f0dbc9a3fca3bcfa8574edb6061b03c_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/8f0dbc9a3fca3bcfa8574edb6061b03c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d69ca4bdeabd313227498cc1e33c22c2717e2a64 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/8f0dbc9a3fca3bcfa8574edb6061b03c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:593a5d32ec61c9cbec0e9606a87e675827f07b93f5cd5d66d798a66e9d9de364 +size 10929 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/9271a5ab5252d6176287e699f600d2fb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/9271a5ab5252d6176287e699f600d2fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..261252a4eecbfe704db1d22604436ba8b0280311 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/9271a5ab5252d6176287e699f600d2fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a32c9c12219fb17e605df1401a87882983ea14b4e384e5d018659d2705131a42 +size 21919 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/96be3e8be94c247917bab0d91881b5dc_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/96be3e8be94c247917bab0d91881b5dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c752b7a3e3ccf67cd71f06f7d619b40616b808fd --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/96be3e8be94c247917bab0d91881b5dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bead476f10f0e5847e677a8d8ce6f4772322649e4d9cff94573ee5c46de5ee8 +size 12573 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/9947dd291b40f299948b56f3190ec7b0_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/9947dd291b40f299948b56f3190ec7b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b539fedbbab531b7165d3527981932b3483cc1cd --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/9947dd291b40f299948b56f3190ec7b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61d5de27b88c9df7b306d4442ce6a21f7610b3997753ed9969bfadc4a05a7f9d +size 9285 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9dc8ac1ccadada798e012c2024c17679ee129632 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc9f7ac54d8c0772fc10b5c67f806d2e8c7feb909229ae93e54f857a84d72c49 +size 33203 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/9a53cf0c36d7542a25d60835be986e5a_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/9a53cf0c36d7542a25d60835be986e5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e67f062e76231c510416c48d30038f047816543a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/9a53cf0c36d7542a25d60835be986e5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70f90a72b7df06e549b4157b031b534d6de2a3868bccf7a7a928ac7650c17dfa +size 13178 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/9af97997b7d3fbca90b8ddba0ea39c6c_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/9af97997b7d3fbca90b8ddba0ea39c6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5c5125ad1248715ff63c665346af94366c4b762 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/9af97997b7d3fbca90b8ddba0ea39c6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cff337e263c9bddd5236b3324c6b78ee65bdca0b2b1bec31b1ccb86764fb744 +size 88654 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/9c12d7993e786817c8c569e6f2d5a0a9_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/9c12d7993e786817c8c569e6f2d5a0a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94854d6edc5eef8e3f6ae4d16e2bb007915a8ebe --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/9c12d7993e786817c8c569e6f2d5a0a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19d2b5812ff2c9c441dec23ae00599edc51839262d9bd3417fb2c634f61bd3f6 +size 60671 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/9d47fe89bc71acebde670ea760ee6ffb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/9d47fe89bc71acebde670ea760ee6ffb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69db4c7332a994e4a1357e1f67392e373b02692c --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/9d47fe89bc71acebde670ea760ee6ffb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3b528f902eda5ac477f9330479b68833fd6870e1fe70251ce5342ca988b593b +size 64476 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/9e290fa7e4578ba0a8b8c5008c99b564_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/9e290fa7e4578ba0a8b8c5008c99b564_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4e92283ad379477b4ae182ef812a4ebeb78050a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/9e290fa7e4578ba0a8b8c5008c99b564_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:350f9ae35e6727e6cb8fd9ef116e01c63074cb66012b31ce0c5f551f699059f3 +size 162962 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/9ef8e686bf7d4fdc4504d136e1b350f0_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/9ef8e686bf7d4fdc4504d136e1b350f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cd4a8792feb1f003d36fd17602eb092d3dd5525 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/9ef8e686bf7d4fdc4504d136e1b350f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35c6252185d70d2f9481d06430971ec2447970f247e9e91d4cdc3b3e124f3ed8 +size 123969 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/9f1b05b6b77146b0d62dbc084ebbe162_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/9f1b05b6b77146b0d62dbc084ebbe162_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9a93f085b9282157c06f9ca925fd4d5b3225644 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/9f1b05b6b77146b0d62dbc084ebbe162_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b46df20b81b4fe604b415cd3b6d15253be1191b9b0790bf1b94ea68291411e36 +size 167287 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce4cd9b4ffa7380773395ef86cdd997a860883d1 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da8049fd230f1060e2e65dee141b475f3786f424b536ed33eaea3d1f8ff8f783 +size 121615 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/9fd6d80e1aab4be30024f5d67f3a4a53_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/9fd6d80e1aab4be30024f5d67f3a4a53_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..087e6d30dacb9a708ce1bc2f562a00c156ba4142 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/9fd6d80e1aab4be30024f5d67f3a4a53_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4df10a5d20ac23dbd610c8a76627128360e707e1e1a11d334eacb67baf5fe405 +size 171003 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/a02b188a5fd52c99f84255322873bf29_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/a02b188a5fd52c99f84255322873bf29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fc3c53d8b5e626ebb73d48733b76d9a128eb46e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/a02b188a5fd52c99f84255322873bf29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bf59f035e32813ba8b4f0d7b1fb062f65658fa0363406918647d99735372651 +size 8565 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/a265aba1737da6f0200faac85366b163_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/a265aba1737da6f0200faac85366b163_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3efca594bfad891176b141932e5085643d846da3 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/a265aba1737da6f0200faac85366b163_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e5cd1145bb04a724aa5b54e743827800d87a4e8255433d27276a82fd620aa05 +size 25618 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/a279b24bee8e82a60177168f08cce415_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/a279b24bee8e82a60177168f08cce415_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a45b098aff8e30df5dd27a182bb7b72830c63ec8 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/a279b24bee8e82a60177168f08cce415_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5b6834a2e4ad6c9be751b30eccc553e1d7e762c7c35b71affcf5a01b8212639 +size 118650 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f4ac94db53675c4cdcc6478d138f729245cb06f --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:123dbe206967ad82e57006927e50377f05d99eca5ad3977ecdfedb3d92392695 +size 72026 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/a70d42d1621bc4d20c0f9d2e396222c1_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/a70d42d1621bc4d20c0f9d2e396222c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a6eb159a559d37cd8f2e6b43599d97cd0454a2a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/a70d42d1621bc4d20c0f9d2e396222c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc6e8782cd893e8778dc0d5c1aa0d73dba796ca19d466f1e0890c0ee0a844afc +size 19854 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7780fae197fc0d8f7ccaf26093417162f348e349 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1da54e294e68f809279166525e00307900b8a78ae2e4428b695ce32cd5e554c1 +size 59581 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/a890c88f5a03b77a0de8feaac5313821_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/a890c88f5a03b77a0de8feaac5313821_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..697817262ef9de7a2ee686ea1e49fc3bbaa140e2 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/a890c88f5a03b77a0de8feaac5313821_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7a184608e8022fd3e62c5e01a386e08182cd9f90e38704cb9970de319fe4dc8 +size 63739 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/ac1b4040daa037941f51deeedbcd585a_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/ac1b4040daa037941f51deeedbcd585a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4202f39d00c23d675df1aa1bee4a1a1236b1b85 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/ac1b4040daa037941f51deeedbcd585a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:149f5b5f66d332fd141d38e52bb0da165ead3064a7d0a240d21f404a281204c4 +size 8733 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/ad4da36431850ac19ba59bb74ec29dc9_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/ad4da36431850ac19ba59bb74ec29dc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59bb5369e4a33511842d8d15d6819fb4ec498b64 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/ad4da36431850ac19ba59bb74ec29dc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a93ec14b630aa2c0d5bce0339f361351ba872ed39d54517c1cfe52b585297150 +size 13673 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/ad9b0c8d0d3fc421b0dbc2ecc61376f4_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/ad9b0c8d0d3fc421b0dbc2ecc61376f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64337f29531c4d0234e9c42d295cd5ff445c4764 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/ad9b0c8d0d3fc421b0dbc2ecc61376f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e298ad59af0fe2120ad30bb5f81594f0f969756078cb4735c57a4dec968f8e26 +size 58115 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/ade808c7cde5b576488a326d288f29eb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/ade808c7cde5b576488a326d288f29eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4538ede0ca5c48c997db65ebf85e044c57f5021b --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/ade808c7cde5b576488a326d288f29eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1926fcca1201dae328bf426abf02d21df2db9f1413358a7c428e7fddadab2d2c +size 82798 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1526cf115e7749129c424ef72b0f9e596acb124 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2559e7b6aa04f3e3880a61d8fe6a5d342d7b420ea44d87f31a41c2e8913190d3 +size 90698 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/af664ceebdaf69ac46f3af52f51df20e_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/af664ceebdaf69ac46f3af52f51df20e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c6c27875271d340f80c3385327351720cd0f236 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/af664ceebdaf69ac46f3af52f51df20e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:091fd41af0f1acc9ff05d2a396e7aed960eb5b4c0ff318ad2f794edeeb26da60 +size 17139 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61d0ce285a9f364333dbb614dd5b2c9859612e19 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edcaf0d0e24441fae0d9f518d7be25bd9ec62eace6d78dbd940f8b0325824ed3 +size 151899 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/af90aabfe3c8c65617da060d82bf99c5_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/af90aabfe3c8c65617da060d82bf99c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68079f3d64fa2bb5d233c585ab64a9982b4091e2 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/af90aabfe3c8c65617da060d82bf99c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7728c81292a15582774803093bd07a1c875276a3bb90a9dd017c4ce8f37692f1 +size 41048 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/b297f64b2487ded933870098ad287bce_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/b297f64b2487ded933870098ad287bce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db3cfd70e234faab9eea5dfb1d4a458cb209670f --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/b297f64b2487ded933870098ad287bce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60ae4249ad2a6c2f97ef8700dbd8ddef94b1916abb4b3ee387ee8d63e0b714e2 +size 27545 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/b4231d923aa1b23a3d9e7a2aa2942d1e_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/b4231d923aa1b23a3d9e7a2aa2942d1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d69d04e29a97326fd19eeff1003cec6b29e35a18 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/b4231d923aa1b23a3d9e7a2aa2942d1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27b98c24d65333bb3f2b50b4c0114427d948f781b816201088ed97d524b2a89f +size 20585 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b42c056fb60da3abd2cb31e40b445ab695f8b343 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4939caf74598e5c2676e5e0b35d0560800ca8db6a7e53882fe66c85c6cf9dac +size 12429 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/b49477e8f148b5ef044a2fd5a43528f6_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/b49477e8f148b5ef044a2fd5a43528f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ae06fb719d06a6354e0677bd5d84b1c8afa413e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/b49477e8f148b5ef044a2fd5a43528f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22f82ce4d8e22a75d1940944666937231fde758bb67ac540fd08b7e989939d12 +size 40914 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/b49ab452107df6572ea43e1be0912bd0_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/b49ab452107df6572ea43e1be0912bd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb0304d28895962491f817c2e37be19a7d21f21f --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/b49ab452107df6572ea43e1be0912bd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcc769822046424fb511d63d8dc373453a77d7d7fd4951f93097d2e647e95544 +size 105833 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/b55656f01d98097862b9e6d8461ec59b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/b55656f01d98097862b9e6d8461ec59b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c101395e1672c000fd4b68030321d9a1ccf85f6 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/b55656f01d98097862b9e6d8461ec59b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b63099b6f78b4f3c88dfe334bcd6781bf513ef859a3f47c4edc17701fe43ab4 +size 55777 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/b98b6c7cbdaae63ffe90f117e507e81a_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/b98b6c7cbdaae63ffe90f117e507e81a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd23c34e5b7dd123d03dbf666fc6b8b78c9371ff --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/b98b6c7cbdaae63ffe90f117e507e81a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:128c0a72f7890d6d1a89a57899e7845169eca2e289ad9b5e402e59243aa56612 +size 14377 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/bb0e323a672fa2f89e0132b1db61cfb3_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/bb0e323a672fa2f89e0132b1db61cfb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..808edbe39e3a45e37182b7185fc2be9c0f52a45c --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/bb0e323a672fa2f89e0132b1db61cfb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bff35f80cb2769bbcbfc9926e5eb35ca2f868bca5ca49578759c24c447b94b88 +size 30707 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/bb8035cd106b4d77b3615e90645f8e37_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/bb8035cd106b4d77b3615e90645f8e37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76871964c1208df9b9275d952765030845d31866 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/bb8035cd106b4d77b3615e90645f8e37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e7acce0b9e61a680ca290d480694fb9015d2f4cae65248013a9054bf3b112e7 +size 24969 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/bd0fe87fe6e236bc4778830b4f26d9e2_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/bd0fe87fe6e236bc4778830b4f26d9e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4761816751c805151a69d1c190318294cf68b291 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/bd0fe87fe6e236bc4778830b4f26d9e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:778e373153058e08b3c9ca1fd1efabe1e6a3c7481faf7e7744673bd634413d22 +size 60889 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/be9225da20b1fa284d0ed4b44fd633a3_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/be9225da20b1fa284d0ed4b44fd633a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcfca6efe212d07ac5732cd701d2021d0756a81e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/be9225da20b1fa284d0ed4b44fd633a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14bd6f7ca07576249359cb0dae9ab86b89ebd27a664ed9b2c81a97986fd4fc5c +size 12543 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/bef134816f55f50b735c92ac0c01da38_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/bef134816f55f50b735c92ac0c01da38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..edc7267a084b37bc37faaeb978b1df8a52e67b52 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/bef134816f55f50b735c92ac0c01da38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd17c8f94155d8b7d844dc4fe75edf46866b86ef69a1b7f62ce99ad78a11f655 +size 24960 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/c1b762c358fd423d6686563b3fde7750_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/c1b762c358fd423d6686563b3fde7750_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62af8491baeb6466ed3b537bd9ad2099f7aafd34 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/c1b762c358fd423d6686563b3fde7750_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33869ea987906df345e583b9ae9543651a7e31e8c1e6483fa639e0dd673b203b +size 129355 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/c1bf17571f9cedf76c4072121295d10e_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/c1bf17571f9cedf76c4072121295d10e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dd41d835383e7a5003287186c42c24c89bfc70c --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/c1bf17571f9cedf76c4072121295d10e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61b8af44e690940b36724f0f930120736c2b0f0b350eeca2f78b69e185be72f1 +size 23865 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/c2f36c545b190860d04e1d84e58d22cc_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/c2f36c545b190860d04e1d84e58d22cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52b190f20a06f4503ec43dcb72d514a09607f383 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/c2f36c545b190860d04e1d84e58d22cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88c5b3cd0c8d7dfe900ba013c08715a37ba2393fcca601f58729ffe0118bde79 +size 88065 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/c40bbeb66e1572660694c68dcb5734e1_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/c40bbeb66e1572660694c68dcb5734e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..934bb197e30c6ddfe357992651437c8590e4f9ee --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/c40bbeb66e1572660694c68dcb5734e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15435ea4f9aaceef4d41e120a547304c73b5c9bf44e2227703d48f2fd7702751 +size 16175 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/c425a7b76be3f887bb251606c2a7ce9a_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/c425a7b76be3f887bb251606c2a7ce9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f0312d6f87493323c7e266cf7fc653f52eda4a0 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/c425a7b76be3f887bb251606c2a7ce9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05dd98c37e7b3eaac65b40257269fc184facc7bac2a5bf6d4f303722aa8bcd01 +size 14619 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/c5945ab1332e6611e9e4d64bafdc3455_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/c5945ab1332e6611e9e4d64bafdc3455_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b40ebb8abe6b5f2bd1c99a634620d69ddae0192a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/c5945ab1332e6611e9e4d64bafdc3455_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f588163e27ae8a8d0319b10b666d9abd5da326e1b7779e58c03afe9dfa48492e +size 9910 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/c6e449481a4deebff8ada290c22a77d9_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/c6e449481a4deebff8ada290c22a77d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6f3c0f1fdd5c3409c88963016c867cd7c2ac429 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/c6e449481a4deebff8ada290c22a77d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eec6fd601a36ba73ae04a2c801cd5f532ed498825a369ced17898d69223a69a3 +size 18781 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/c79d10d97e1f525e9c85e96e91616923_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/c79d10d97e1f525e9c85e96e91616923_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2019b1c5fbd813af9be926452da5d96ec0ad6f41 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/c79d10d97e1f525e9c85e96e91616923_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfe01cc6fb6cad585fcdb41fc0372ea96f06d72fac6bdd9ad13e5e52f02d47c4 +size 13085 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/c8b66b38ad7369d0771b91b51c155b32_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/c8b66b38ad7369d0771b91b51c155b32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea9fb6cc744786d2aa4b68c6407f51d1782677f1 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/c8b66b38ad7369d0771b91b51c155b32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f2144352b3b9535786c64e4db19b7b6ce2876c0b8315f308f6d6e4b87587884 +size 33059 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/ca29ffd592187cc2b1719b98a5417521_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/ca29ffd592187cc2b1719b98a5417521_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba7759301b238a81d0f76f74903bef31932a2473 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/ca29ffd592187cc2b1719b98a5417521_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a871e8f5835474973fe190bd1d93e52bdd45d6a6ae6c11e632e1e51850b5e621 +size 155121 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/ca86f53f9735fe98b6c6003d1b759f64_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/ca86f53f9735fe98b6c6003d1b759f64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7da04b19571e0836134b284ecf48c4e161d4b5b --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/ca86f53f9735fe98b6c6003d1b759f64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d27ebf5b9dee11580d5967de95e5d24a01a398adfef5d1d1263ffcdd789b570c +size 64820 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/cacc4ff5c441e0eb6fbd5e14a083eb05_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/cacc4ff5c441e0eb6fbd5e14a083eb05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79f1c8626519ef3dea135f249d7a46a0a9b89b89 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/cacc4ff5c441e0eb6fbd5e14a083eb05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec469204cfbf9e5e8f503226bed84ec207b49cdf57f1132b6c6e64e80795c779 +size 22651 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1850e50ad817a6bd8c51a5e36399f5c2013e7bf9 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ad6b78ebec5ceed012e0cf0d1e4de9afee5e320f1520e1b7a669d08535f52f9 +size 56576 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/ce4432c76d20b370ebecb57e59afc2ee_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/ce4432c76d20b370ebecb57e59afc2ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cf2a45584401a0bdb3df80163d1bf208bc8e31d --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/ce4432c76d20b370ebecb57e59afc2ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1aface27b9246cad5ee0490dd881638756c4d49a30c29012c3cfe77eced4f650 +size 76461 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac78e32452c50d021914a5c8062c78e5891e89aa --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35f334ee1b6bb55dc6a38a12633d74230525f0aab429572ee1865b8d45b620b9 +size 14127 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aaf2adae0768f95589d37da846da9acc7ea480bb --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:411d6e6b6aa3bfc083c168324ab7834690e92532c0f93b5b0e80d16cc9aa7248 +size 45690 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..591bfe0da48aadd9bf3fda577a3b9746eaf85c0b --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:551128151bf88b3712deb1e7bdfe55df55c3b01274e4b7ce75e465ebd427a1a7 +size 115460 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d081abfd06a4b868f797e5669c6dff78_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d081abfd06a4b868f797e5669c6dff78_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07017003bf4aeccd99db323f653434deb5bd9354 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d081abfd06a4b868f797e5669c6dff78_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37359925511adff228f5eaa72d375aa9cfc77c4520126076ad88dacdb5980f37 +size 196068 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d11039755489421fdcdad3ed6edd05d8_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d11039755489421fdcdad3ed6edd05d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9bbbe0555abed45b4e1272817cde4e248d3a63d --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d11039755489421fdcdad3ed6edd05d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d6c654664882be5669567aa0483e7050bea4102d53fffd2a08598601ae0d237 +size 146332 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..056e90acb0c9d1449e96e84511e1df4a34c318d0 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:515b00cc43872f6d11dfcd7696d91d342c5c1dc1677a71fa542cdbb8257e37ea +size 12887 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d186ab1411a29b6f0938ab43178e9f0d_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d186ab1411a29b6f0938ab43178e9f0d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c91425b77e0025c0cf1d71a0786f52f9372e268a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d186ab1411a29b6f0938ab43178e9f0d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36dd5805f14cdb72663aafcc9445dad1965f8ebbf5d4b7535bd68849383a249c +size 56059 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e12477cf2bbf1d9204d8b61143dbb0858e0e977a --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee7e106b479e6e659ed96105079507de61a05abbee6c3c3d80f583910019f5a8 +size 105080 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d23fe5b7e93dc24c2ffa70b743025c5b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d23fe5b7e93dc24c2ffa70b743025c5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9af60b2cca59173b1f4e4c755f22cf4cbcb0e5d6 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d23fe5b7e93dc24c2ffa70b743025c5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:390427ba7b14b01f0134581de0975d7fe1fe13de0fc6f70eeab1e5770d10ddcd +size 55824 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d3253d5db64378db6e72b66b41067a5b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d3253d5db64378db6e72b66b41067a5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44d446d10fac4ff91d1a80e617ae4849bb8f340c --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d3253d5db64378db6e72b66b41067a5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a5169bab4bc7cb91783ef5115a3e80855ec3ce403ba7ab7e01534b5669bc712 +size 67807 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d3581354fc6f1b5e27d3c990e41cc805_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d3581354fc6f1b5e27d3c990e41cc805_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b43938bc7c84c89acb6f6007cb2d80752a758b01 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d3581354fc6f1b5e27d3c990e41cc805_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:071022cc4ba4a37cb6266a92f1f001f1038f13d932ed918a7e0291323522a7de +size 191755 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d5de4c1d2f0b71aa339b6b2118268fbb_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d5de4c1d2f0b71aa339b6b2118268fbb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81c8ac82e1c094bfbbb1bc9c57cfb10a510c7747 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d5de4c1d2f0b71aa339b6b2118268fbb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a21f4010911bdd77036db39b1072ce7a459d373bca1d7688e76f7a19dfe89a46 +size 131442 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d7a98a717edbc26ca1508aaab7a566f4_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d7a98a717edbc26ca1508aaab7a566f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb5e45d1abd729a69d53517052a40c086972ea35 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d7a98a717edbc26ca1508aaab7a566f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:130b4bed28b5fd668d25d76200f122eaa56d106fba2921d56fad66b8634985e0 +size 12737 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d884367c84ba50f250499f79c4b4b950_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d884367c84ba50f250499f79c4b4b950_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0e4db2fba41c6058562e00efd459892406cbca0 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d884367c84ba50f250499f79c4b4b950_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf549ce2915ddf53b3a3c1eefe2f50eeb8998b3cfc33c36df5ba42cb8749f11e +size 13011 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d94747f06bbc2d98d92f9ca113ab737e_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d94747f06bbc2d98d92f9ca113ab737e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98bcdf271c20bdd32820812833f7cf7a4fd6a7be --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d94747f06bbc2d98d92f9ca113ab737e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44345d26a1f7762866f5b0dd9c8a3f84a5a27a790a3f1cce0ff22310b9b783fb +size 73925 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d9862ac8473902e7dfe441c5e88d47d8_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d9862ac8473902e7dfe441c5e88d47d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6093fcb5c47758635cad3c23a36fd578671520e --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d9862ac8473902e7dfe441c5e88d47d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92124432cc801ac2ddd9e3ddb183c0c741b95b292043e24f8db4124840ad6cd4 +size 108906 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/d988db7a59b060ff3406236569343e4f_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/d988db7a59b060ff3406236569343e4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81a88f54dcd8a5c8810b71c5a42d76e4ad2760ef --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/d988db7a59b060ff3406236569343e4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:502cea8f584c172a471f2459b199686c7809ed47147687918b4754a9d3065338 +size 28754 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/db395493033edacd83e212049fd55715_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/db395493033edacd83e212049fd55715_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c27d89992bfcfd1262e5569a6b5684f510e75fc7 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/db395493033edacd83e212049fd55715_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f537ddd22f1fabce8b4559c8371cc1c1bb484ab10b105f61ed893ecc1a6dc41a +size 6603 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/dbfe5a97dc7e71fd9ae813d4bb865e29_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/dbfe5a97dc7e71fd9ae813d4bb865e29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dece9f9a25743a8f83c3b9398e4e6f25da319b25 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/dbfe5a97dc7e71fd9ae813d4bb865e29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6086d1bfd114f353d6f90e75d8904daffd0054248bb2a0ceb37b72d81cbcc1cb +size 23884 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/e09924f32278bb6a47909ae24bbea647_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/e09924f32278bb6a47909ae24bbea647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2be1dfdcf9551e34ec9655eaa8f8022fa5794fcb --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/e09924f32278bb6a47909ae24bbea647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf70e0e71a89a316fb9dc68ae3496a4d5bef95ea09e3b5f4a19d71d8d069312a +size 7652 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/e0eba715b26e99c0beececdd6112ee58_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/e0eba715b26e99c0beececdd6112ee58_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f837c2019f3b34e0053f733ae4fd06a96081096 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/e0eba715b26e99c0beececdd6112ee58_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a329c3a2334e7252fb4d4dbe273d1c1ff20fb7e8764c3d498c6d822dbe93da5 +size 33004 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d79b9181732edb1e6bddc117866e5c89d3f45498 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a47c3e4474b6481c7930e6da014bbf742b0a5259e58835b4b1ccf659be99f1a2 +size 96151 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/e96884b4726abd1ef715e32b100b05e6_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/e96884b4726abd1ef715e32b100b05e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a341038290d3a4bebe04cbace75c131a07b5e35 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/e96884b4726abd1ef715e32b100b05e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d503930588ecfd0bc7fdb68fe7befe6c5ff55989168ff85d4d7d18e882eb00d8 +size 6121 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/ea3fc2de81f3b1ff5c2f12cdeadcf831_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/ea3fc2de81f3b1ff5c2f12cdeadcf831_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b431bac6e964adbb597a1779c2b0f2c54b0abc00 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/ea3fc2de81f3b1ff5c2f12cdeadcf831_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb4ca0438362bc9c1d0bd446f6e21cb44070e848a4ab4a17c9c6a4876be5e712 +size 13765 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/ea4d1f05669860c1f910e6cb1e7a22b6_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/ea4d1f05669860c1f910e6cb1e7a22b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d817d59d96896e0f9d73d10930632552196252ba --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/ea4d1f05669860c1f910e6cb1e7a22b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcd14ab239d85a885bc0ea9532f7dd19f96a19f2b6c9971a9add6ee6793cc6d7 +size 108594 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/ea6b9ace0ed0694c2ce8dcdb8b5ea52b_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/ea6b9ace0ed0694c2ce8dcdb8b5ea52b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d6819c229f7cfd27fd6c7d106301f2cbb398ed2 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/ea6b9ace0ed0694c2ce8dcdb8b5ea52b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e42b7dca166f905d936ba24097f00680ffdadb8f90a1718363b931fce51bc5e9 +size 136890 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/ea72687397bac53eb690650f371bfd63_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/ea72687397bac53eb690650f371bfd63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c1b805df0c1cd7896f75c65d078ae38bd028c24 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/ea72687397bac53eb690650f371bfd63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d89f8d056b7a4e331460c6493c7fdb505ce2a12f6186bd73826d9e26debd3be +size 21277 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/eaa8ee2530516c47ef4dcc8a5db20fd0_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/eaa8ee2530516c47ef4dcc8a5db20fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c76729f85ffab56f447a96482ee00d2404146a51 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/eaa8ee2530516c47ef4dcc8a5db20fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d777421c8064ffb176549a27b1fe70191b8febc37d9712b3ba93d27e95fad4e +size 21500 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/eb8cac9fb65d601ab50405472e408156_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/eb8cac9fb65d601ab50405472e408156_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..214e2b0a903988bf54561e082904822c3ffbd2e5 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/eb8cac9fb65d601ab50405472e408156_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84b7eab012e4ef208f97b203854faba091f54c2a051c792d0d0a54ace490c760 +size 97070 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/ec27906099ab5da32f29b89d2764cf0c_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/ec27906099ab5da32f29b89d2764cf0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19b2fdc131a471038d640f048c5c1fe06b2793c3 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/ec27906099ab5da32f29b89d2764cf0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24961b74ca4453d0341f628a18112a0d0358f3644d0735c91dd6774481632226 +size 16720 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/efcb78ce7df315911219258bc2132f8c_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/efcb78ce7df315911219258bc2132f8c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6ae7940a10ec5bd3a5e799a39d84086689e09ae --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/efcb78ce7df315911219258bc2132f8c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24d5ddbe2eef950aeff40b3c8e093abbc83d84bf6833f2b6ce93ab47ad14c339 +size 24561 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/f2a6c46fa05d5588ce4c6e1a3ee194c7_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/f2a6c46fa05d5588ce4c6e1a3ee194c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ede21a12569ddab7c974c3416ae1e2103cba25bf --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/f2a6c46fa05d5588ce4c6e1a3ee194c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c926b8ad1815dcde23c390c157c8fb7aa8b69af1dc1f4f27a7cc3c0a3899aa36 +size 143171 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/f2e1a8f6118f3a062702aae017e04753_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/f2e1a8f6118f3a062702aae017e04753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fae22165ed8f614fdbee1d06699a94629877c799 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/f2e1a8f6118f3a062702aae017e04753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba0536da32909ea1881b84beb5fe1639a2198ad1b9743a877ef9c221eebc5902 +size 82552 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/f3d0615dd9e87088a29786cc6a1c8a35_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/f3d0615dd9e87088a29786cc6a1c8a35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b93865ba60ff979dc7da7297f00b9a4214b9ca3 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/f3d0615dd9e87088a29786cc6a1c8a35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4eed153d641ccdaa081fe4103afc6e64d9e3f5b20bc15695312acffabfdab84d +size 14225 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/f4b570ddd089f54943d46e9f8776f9f9_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/f4b570ddd089f54943d46e9f8776f9f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab855d312d8819a211dd937848173145324abe77 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/f4b570ddd089f54943d46e9f8776f9f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:259515982e315fa91daa073b02fe1f47f98dca064237ee7ffeb06efe47f5a2ec +size 22013 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/f512ae9c630f2fb53197fa77a1bda0e8_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/f512ae9c630f2fb53197fa77a1bda0e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c88b9f73ea25fd3c2c078013a28d4986727848f --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/f512ae9c630f2fb53197fa77a1bda0e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f2a2de94574e737f51cd415c4cf20616b02adf3dea0f1d0c7b6e94079406852 +size 152985 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..446ec93b9e8095abd00543970e79c3c8948bfe25 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b94e6b3a402711823bc805e005a012cef213d5464cab3de7dfd972868e15daa +size 7108 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/f6dcf82b673244b5b8c95616ca0d0556_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/f6dcf82b673244b5b8c95616ca0d0556_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8159f0d0f06896685d9e9a39fd44bfd4b10a3170 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/f6dcf82b673244b5b8c95616ca0d0556_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ae5746e8d801ddf5730e496610be8bd144779aa52e4ed3c3557a97a5f29e207 +size 108884 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/f863cb8837fe502a913bc2be8d1afd8a_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/f863cb8837fe502a913bc2be8d1afd8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a8828ad55b82802b03a4a8c58fd0d33b29a614d --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/f863cb8837fe502a913bc2be8d1afd8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:901984cb83d5404ba27ad97e52af9d585c42e13c95b43c71df28c38e982fe35a +size 14248 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/f88e403864388f59871586472847bbd0_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/f88e403864388f59871586472847bbd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2528b85af6924a443a35dfef110dbaaffd59f61f --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/f88e403864388f59871586472847bbd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bad2c364841ddad76a2c6823db94f72b91af8d0c18b432634fb8906badbef959 +size 26418 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/f98ddc2253ad41b4130f6042e77f1460_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/f98ddc2253ad41b4130f6042e77f1460_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45db8a65fa82b9f1e9423eedd05ec7bbc755eaab --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/f98ddc2253ad41b4130f6042e77f1460_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a25f1960856e5c6d72a243affcd08e6b7056c0c3828a4f329c96f67023487360 +size 20389 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c317372bcebd6114381b60897cbe02a0e7b9101 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e02b9fe8e169db601a2b4f6d8f93186e4c2555f1ebac5ee3adc598b54730f8e +size 39806 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/fd4b2ee19b709bcb11190893e23f8453_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/fd4b2ee19b709bcb11190893e23f8453_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b0d9fcd083d21e0f994bbd61f22eb0b7ddf76bd --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/fd4b2ee19b709bcb11190893e23f8453_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9882e087285f2840f4e9b5373968d0de65f53f13512ba29321dc7c2fa437bd6 +size 91185 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/fd6100880c96880a39d994338c9d5f36_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/fd6100880c96880a39d994338c9d5f36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c925b2afabf894dd2f703da76bfc1614586c7144 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/fd6100880c96880a39d994338c9d5f36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e93224f26b8b3b4e4d2c831927b1e6e9912cbc341c1688a9af388d2c77a09f3 +size 39037 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cb22186af99a7e179c5f4d881b80d73e1f001fc --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e5bc1cacad20d9ab66987d08244b611e81c2db1bf17056b6fdc70486364cfc4 +size 65794 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/ffd430265e73d833a0aa30a5dd8261e3_img.jpg b/marked/G/T-REC-G.798-202309-I_PDF-E/ffd430265e73d833a0aa30a5dd8261e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34809f7c60ca88e52b593fac739bb3c01b5cef98 --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/ffd430265e73d833a0aa30a5dd8261e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37ab39097dedc205ef422147deb4cf30bbcaa8fb2ce3183db5323f1152266082 +size 185077 diff --git a/marked/G/T-REC-G.798-202309-I_PDF-E/raw.md b/marked/G/T-REC-G.798-202309-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..32ff87f00a9a30a91a467d3d997eb52be074bf3d --- /dev/null +++ b/marked/G/T-REC-G.798-202309-I_PDF-E/raw.md @@ -0,0 +1,15298 @@ + + +# Recommendation + +## **ITU-T G.798 (09/2023)** + +SERIES G: Transmission systems and media, digital systems and networks + +Digital terminal equipments – Other terminal equipment + +--- + +# **Characteristics of optical transport network hierarchy equipment functional blocks** + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +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 | +| General | G.700-G.709 | +| Coding of voice and audio signals | G.710-G.729 | +| Principal characteristics of primary multiplex equipment | G.730-G.739 | +| Principal characteristics of second order multiplex equipment | G.740-G.749 | +| Principal characteristics of higher order multiplex equipment | G.750-G.759 | +| Principal characteristics of transcoder and digital multiplication equipment | G.760-G.769 | +| Operations, administration and maintenance features of transmission equipment | G.770-G.779 | +| Principal characteristics of multiplexing equipment for the synchronous digital hierarchy | G.780-G.789 | +| Other terminal equipment | G.790-G.799 | +| DIGITAL NETWORKS | G.800-G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900-G.999 | +| MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000-G.1999 | +| TRANSMISSION MEDIA CHARACTERISTICS | G.6000-G.6999 | +| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000-G.7999 | +| PACKET OVER TRANSPORT ASPECTS | G.8000-G.8999 | +| ACCESS NETWORKS | G.9000-G.9999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T G.798 + +# Characteristics of optical transport network hierarchy equipment functional blocks + +## Summary + +Recommendation ITU-T G.798 specifies both the components and the methodology that should be used in order to specify the optical transport network (OTN) functionality of network elements; it does not specify individual optical transport network equipment. + +Edition 7.0 of this Recommendation includes the text of Amendments 1, 2, 3 and 4, as well as Corrigenda 1 and 2 to Edition 6.0 of this Recommendation, the addition of the ODUkP to ETH adaptation function using Idle Mapping Procedure (IMP) and a number of editorial enhancements. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|---------------------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.798 | 2002-01-06 | 15 | 11.1002/1000/5604 | +| 1.1 | ITU-T G.798 (2002) Amd. 1 | 2002-06-13 | 15 | 11.1002/1000/6057 | +| 2.0 | ITU-T G.798 | 2004-06-13 | 15 | 11.1002/1000/7329 | +| 3.0 | ITU-T G.798 | 2006-12-14 | 15 | 11.1002/1000/8983 | +| 3.1 | ITU-T G.798 (2006) Amd. 1 | 2008-12-12 | 15 | 11.1002/1000/9669 | +| 3.2 | ITU-T G.798 (2006) Cor. 1 | 2009-01-13 | 15 | 11.1002/1000/9647 | +| 4.0 | ITU-T G.798 | 2010-10-22 | 15 | 11.1002/1000/10877 | +| 4.1 | ITU-T G.798 (2010) Cor. 1 | 2011-04-13 | 15 | 11.1002/1000/11117 | +| 4.2 | ITU-T G.798 (2010) Amd. 1 | 2011-07-22 | 15 | 11.1002/1000/11116 | +| 4.3 | ITU-T G.798 (2010) Cor. 2 | 2012-02-13 | 15 | 11.1002/1000/11488 | +| 4.4 | ITU-T G.798 (2010) Amd. 2 | 2012-04-06 | 15 | 11.1002/1000/11487 | +| 5.0 | ITU-T G.798 | 2012-12-22 | 15 | 11.1002/1000/11778 | +| 5.1 | ITU-T G.798 (2012) Amd. 1 | 2014-05-14 | 15 | 11.1002/1000/12179 | +| 5.2 | ITU-T G.798 (2012) Amd. 2 | 2015-01-13 | 15 | 11.1002/1000/12367 | +| 5.3 | ITU-T G.798 (2012) Cor. 1 | 2015-08-13 | 15 | 11.1002/1000/12529 | +| 5.4 | ITU-T G.798 (2012) Amd. 3 | 2017-01-12 | 15 | 11.1002/1000/13081 | +| 6.0 | ITU-T G.798 | 2017-12-07 | 15 | 11.1002/1000/13335 | +| 6.1 | ITU-T G.798 (2017) Cor. 1 | 2018-08-06 | 15 | 11.1002/1000/13524 | +| 6.2 | ITU-T G.798 (2017) Amd. 1 | 2018-08-22 | 15 | 11.1002/1000/13518 | +| 6.3 | ITU-T G.798 (2017) Amd. 2 | 2019-12-07 | 15 | 11.1002/1000/13996 | +| 6.4 | ITU-T G.798 (2017) Amd. 3 | 2021-01-13 | 15 | 11.1002/1000/14520 | +| 6.5 | ITU-T G.798 (2017) Cor. 2 | 2021-05-29 | 15 | 11.1002/1000/14621 | +| 6.6 | ITU-T G.798 (2017) Amd. 4 | 2022-05-22 | 15 | 11.1002/1000/14896 | +| 7.0 | ITU-T G.798 | 2023-09-06 | 15 | 11.1002/1000/15552 | + +## Keywords + +Atomic functions, equipment functional blocks, functional specification, optical transport network, OTN. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|-------------------------------------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 6 | +| 3 | Definitions ..... | 8 | +| 3.1 | Terms defined elsewhere ..... | 8 | +| 3.2 | Terms defined in this Recommendation..... | 10 | +| 4 | Abbreviations and acronyms ..... | 11 | +| 5 | Conventions ..... | 19 | +| 6 | Supervision ..... | 20 | +| 6.1 | Alarm reporting control..... | 20 | +| 6.2 | Defects..... | 20 | +| 6.3 | Consequent actions..... | 31 | +| 6.4 | Defect correlations..... | 31 | +| 6.5 | Performance filters ..... | 32 | +| 7 | Information flow across reference points ..... | 33 | +| 8 | Generic processes ..... | 34 | +| 8.1 | Blank clause..... | 34 | +| 8.2 | Alignment processes..... | 34 | +| 8.3 | Signal quality supervision ..... | 38 | +| 8.4 | Blank clause..... | 40 | +| 8.5 | Forward error correction (FEC) processing ..... | 40 | +| 8.6 | Trail trace identifier (TTI) processing..... | 42 | +| 8.7 | Payload structure indication (PSI) acceptance processes..... | 42 | +| 8.8 | Status information (STAT) acceptance process ..... | 44 | +| 8.9 | Generic AIS generation and detection..... | 44 | +| 8.10 | Generic layer fault processing..... | 44 | +| 8.11 | OTSi modulator and demodulator processes..... | 47 | +| 8.12 | FlexO maintenance signal information (MAINT) acceptance process ..... | 48 | +| 8.13 | FlexO instance signals interleaving processes ..... | 48 | +| 8.14 | FlexOsec processing for encryption and authentication of fixed-length
FlexO frame structures ..... | 48 | +| 9 | OTS-O layer functions..... | 53 | +| 9.1 | Connection functions..... | 53 | +| 9.2 | Termination functions ..... | 53 | +| 9.3 | Adaptation functions ..... | 58 | +| 10 | OMS-O layer functions ..... | 60 | +| 10.1 | Connection functions..... | 61 | +| 10.2 | Termination functions ..... | 61 | +| 10.3 | Adaptation functions ..... | 66 | + +| | | | +|---------|----------------------------------------------------------------------------------|-----| +| 10.4 | Sub-layer functions..... | 73 | +| 11 | OSC (layer) functions ..... | 73 | +| 11.1 | Connection functions..... | 76 | +| 11.2 | Termination functions ..... | 76 | +| 11.3 | Adaptation functions ..... | 77 | +| 12 | OTSiA and OCh (layer) functions..... | 81 | +| 12.1 | Connection functions..... | 83 | +| 12.2 | Termination functions ..... | 89 | +| 12.3 | Adaptation functions ..... | 99 | +| 12.4 | Sub-layer functions..... | 99 | +| 13 | OTU (layer) functions..... | 100 | +| 13.1 | Connection functions..... | 101 | +| 13.2 | Termination functions ..... | 101 | +| 13.3 | Adaptation functions ..... | 114 | +| 13.4 | Sub-layer functions..... | 127 | +| 14 | ODU (layer) functions ..... | 127 | +| 14.1 | Connection functions..... | 130 | +| 14.2 | Termination functions ..... | 140 | +| 14.3 | Adaptation functions ..... | 147 | +| 14.4 | COMMS functions ..... | 290 | +| 14.5 | Sub-layer functions..... | 297 | +| 14.6 | Blank clause..... | 318 | +| 15 | FlexO functions ..... | 318 | +| 15.1 | Connection functions..... | 321 | +| 15.2 | Termination functions ..... | 321 | +| 15.3 | Adaptation functions ..... | 328 | +| 15.4 | Compound functions ..... | 348 | +| 16 | OTSi adaptation functions ..... | 352 | +| 16.1 | OTSi to OTUk or OTUk-RS adaptation function (OTSi/OTUk_A or OTSi/OTUk-RS_A)..... | 352 | +| 16.2 | OTSi to OTUkV adaptation function (OTSi/OTUkV_A)..... | 361 | +| 16.3 | OTSiG to OTUk adaptation function (OTSiG/OTUk_A)..... | 364 | +| 16.4 | OTSiG to OTUkV adaptation function (OTSiG/OTUkV_A)..... | 371 | +| 16.5 | OTSi to OTUCn adaptation function (OTSi/OTUCn_A)..... | 374 | +| 16.6 | OTSiG to OTUCn adaptation function (OTSiG/OTUCn_A)..... | 376 | +| 16.7 | OTSi to FlexO-x adaptation function (OTSi/FlexO-x_A)..... | 378 | +| 16.8 | OTSiG to FlexO-x adaptation function (OTSiG/FlexO-x_A)..... | 404 | +| 16.9 | OTSi to OSC adaptation function (OTSi/OSC_A)..... | 412 | +| 17 | Media element ..... | 414 | +| Annex A | Optical section (OSx) and constant bit rate (CBRx) layer functions ..... | 417 | + +| | | | +|---------------|-------------------------------------------------------------------------------------------------------------|-----| +| A.1 | Connection functions..... | 418 | +| A.2 | Termination functions ..... | 418 | +| A.3 | Adaptation functions ..... | 421 | +| Annex B | Generic FlexE and FlexO supervision and processes..... | 434 | +| B.1 | Supervision ..... | 434 | +| B.2 | Generic processes ..... | 435 | +| Appendix I | Applications and functional diagrams ..... | 437 | +| I.1 | Transparent CBRx tributary interface port with optional SDH RS non-intrusive monitor on OTN equipment ..... | 437 | +| I.2 | OTU tributary interface port on OTN equipment ..... | 438 | +| I.3 | Selectable CBRx/OTUk tributary interface port on OTN equipment ..... | 440 | +| I.4 | OTU interface ports on non-OTN equipment ..... | 442 | +| I.5 | Multi-channel interface port with 3-R regeneration functionality for an ODUk connection function ..... | 443 | +| Appendix II | Blank appendix ..... | 445 | +| Appendix III | Performance of processes ..... | 446 | +| III.1 | Introduction ..... | 446 | +| III.2 | OTUk frame alignment process..... | 446 | +| III.3 | STAT acceptance process and related defect detection ..... | 448 | +| III.4 | OTU dIAE, OTU dBDI, ODU dBDI detection ..... | 449 | +| III.5 | PT acceptance process and ODUPdPLM detection ..... | 450 | +| III.6 | Generic AIS and OTUk-AIS (k = 1, 2, 3) detection..... | 451 | +| III.7 | OTU and ODUT dBIAE detection process ..... | 452 | +| Appendix IV | TTI processing examples ..... | 454 | +| IV.1 | Example 1 ..... | 454 | +| IV.2 | Example 2 ..... | 455 | +| Appendix V | Blank appendix ..... | 459 | +| Appendix VI | Blank appendix ..... | 460 | +| Appendix VII | Examples of media elements ..... | 461 | +| Appendix VIII | Trail protection of OTS-O/OMS-O layers in support of media layer protection ..... | 463 | +| VIII.1 | OxS-O trail protection sub-layer functions ..... | 463 | +| Appendix IX | Examples of compound adaptation functions without SM monitoring ..... | 470 | +| Bibliography | ..... | 472 | + + + +# Characteristics of optical transport network hierarchy equipment functional blocks + +# 1 Scope + +This Recommendation covers the functional requirements of optical transport network functionality within equipment. + +This Recommendation uses the specification methodology defined in [ITU-T G.806], in general for transport network equipment, and is based on the architecture of optical transport networks defined in [ITU-T G.872] and the interfaces for optical transport networks defined in [ITU-T G.709]. The description is generic and no particular physical partitioning of functions is implied. The input/output information flows associated with the functional blocks serve for defining the functions of the blocks and are considered to be conceptual, not physical. + +The functionality defined in this Recommendation can be applied at user-to-network interfaces (UNIs) and network node interfaces (NNIs) of the optical transport network. It is recognized that for interfaces used within optical subnetworks, aspects of the interface are optical technology dependent and subject to change as technology progresses. Therefore, optical-technology dependent aspects (for transverse compatibility) are not defined for functional blocks used for these interfaces to allow for technology changes. The overhead processing functionality necessary for operations and management of optical subnetworks is defined. + +Not every functional block defined in this Recommendation is required for every application. Different subsets of functional blocks from this Recommendation and others (e.g., [ITU-T G.783]) may be assembled in different ways according to the combination rules given in these Recommendations to provide a variety of different capabilities. Network operators and equipment suppliers may choose which functions must be implemented for each application. + +The internal structure of the implementation of this functionality (equipment design) need not be identical to the structure of the functional model, as long as all the details of the externally observable behaviour comply with the equipment functional specification (EFS). + +Equipment developed prior to the production of this Recommendation may not comply in all details with this Recommendation. + +Equipment which is normally stated to be compliant with this Recommendation may not fulfil all the requirements in the case that it is interworking with old equipment that is not compliant with this Recommendation. + +Figures 1-1, 1-2, 1-3, 1-4, and 1-5 present the set of atomic functions associated with traffic signal transport. The functions for the processing of communication channels (COMMS) are not shown in these figures in order to reduce the complexity of the figures. For the COMMS functions, refer to the specific layer network descriptions. + +![Figure 1-1: OTN atomic functions specific for the single and multi-channel interface. The diagram shows five configurations. The first three are 'Single-channel interfaces': 1) OTUk_(T)CP connects to OTSi/OTUk, which connects to OTSi and NC, which then connect to a Media element. 2) OTUCn_(T)CP connects to OTSiG/OTUCn, which connects to multiple OTSi (labeled 1 to m) and NC, which then connect to a Media element. 3) FlexO-x_(T)CP connects to OTSiG/FlexO-x, which connects to multiple OTSi (labeled 1 to m) and NC, which then connect to a Media element. The last two are 'Multi-channel interface': 4) OTUk_(T)CP connects to OTSi/OTUk, which connects to OTSi and NC, which then connect to a wide Media element. 5) OTUCn_(T)CP connects to OTSiG/OTUCn, which connects to multiple OTSi (labeled 1 to m) and NC, which then connect to the same wide Media element. A legend indicates 'NC = Not connected' and the diagram is labeled 'G.798(23)_F1-1'.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Figure 1-1: OTN atomic functions specific for the single and multi-channel interface. The diagram shows five configurations. The first three are 'Single-channel interfaces': 1) OTUk\_(T)CP connects to OTSi/OTUk, which connects to OTSi and NC, which then connect to a Media element. 2) OTUCn\_(T)CP connects to OTSiG/OTUCn, which connects to multiple OTSi (labeled 1 to m) and NC, which then connect to a Media element. 3) FlexO-x\_(T)CP connects to OTSiG/FlexO-x, which connects to multiple OTSi (labeled 1 to m) and NC, which then connect to a Media element. The last two are 'Multi-channel interface': 4) OTUk\_(T)CP connects to OTSi/OTUk, which connects to OTSi and NC, which then connect to a wide Media element. 5) OTUCn\_(T)CP connects to OTSiG/OTUCn, which connects to multiple OTSi (labeled 1 to m) and NC, which then connect to the same wide Media element. A legend indicates 'NC = Not connected' and the diagram is labeled 'G.798(23)\_F1-1'. + +**Figure 1-1 – OTN atomic functions specific for the single and multi-channel interface** + +![Figure 1-2: OTN atomic functions specific for the multi-channel interface with management. The diagram shows a multi-channel interface configuration. At the top, OTUk_(T)CP and OTUCn_(T)CP connect to a block labeled OTSi[G]/OTUk and OTSi[G]/OTUCn. This block connects to two OTSi blocks. These OTSi blocks connect to an OTSiG block (labeled 1 to m), which in turn connects to an OTSiA or OCh block. This block connects to a Media element. To the right, the OTSi[G]/OTUk and OTSi[G]/OTUCn block also connects to an OTSiG-O/OCh-O block, which connects to an OTSiA|OCh block. This OTSiA|OCh block connects to a dashed box labeled OMS-O/OTSiG/OCh-O. There are also dashed lines labeled AI_TSF-P and AI_TSF-O between the top block and the OTSiG-O/OCh-O block. The diagram is labeled 'Multi-channel interfaces' and 'G.798(23)_F1-2'.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) + +Figure 1-2: OTN atomic functions specific for the multi-channel interface with management. The diagram shows a multi-channel interface configuration. At the top, OTUk\_(T)CP and OTUCn\_(T)CP connect to a block labeled OTSi[G]/OTUk and OTSi[G]/OTUCn. This block connects to two OTSi blocks. These OTSi blocks connect to an OTSiG block (labeled 1 to m), which in turn connects to an OTSiA or OCh block. This block connects to a Media element. To the right, the OTSi[G]/OTUk and OTSi[G]/OTUCn block also connects to an OTSiG-O/OCh-O block, which connects to an OTSiA|OCh block. This OTSiA|OCh block connects to a dashed box labeled OMS-O/OTSiG/OCh-O. There are also dashed lines labeled AI\_TSF-P and AI\_TSF-O between the top block and the OTSiG-O/OCh-O block. The diagram is labeled 'Multi-channel interfaces' and 'G.798(23)\_F1-2'. + +**Figure 1-2 – OTN atomic functions specific for the multi-channel interface with management** + +NOTE 1 – OCh is used when the non-associated overhead is OCh-O; OTSiA is used when it is OTSiG-O. + NOTE 2 – An OTSiG has one or more members. A single-member OTSiG may be called 'OTSi'. + +![Diagram of OTN atomic functions for non-associated overhead information. The diagram shows a hierarchy of layers: OCh-O, OTSiG-O, OMS-O, OTS-O, and OSC. At the top, OCh-O and OTSiG-O layers are shown with their respective overhead (OCh-O_AP, AI_TSF, OCh-O_CP) and their connection to a central OTSiA | OCh layer. Below this, OMS-O layers are shown, with OMS-O_AP and OMS-O_CP overhead. The OMS-O layers are connected to OTS-O layers, which in turn are connected to OSC layers. The OSC layers have OSC_AP and OSC_CP overhead. The diagram also indicates signal flow from media elements in source and sink directions, with labels like OMS-P_LOS, OMS-O_RP, OTS-P_LOS, and OTS-O_RP.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +The diagram illustrates the OTN atomic functions for non-associated overhead information across multiple layers: + +- OCh-O Layer:** Shows overhead OCh-O\_AP, AI\_TSF, and OCh-O\_CP. It connects to the OTSiA | OCh layer. +- OTSiG-O Layer:** Shows overhead OTSiG-O\_AP, AI\_TSF, and OTSiG-O\_CP. It also connects to the OTSiA | OCh layer. +- OMS-O Layer:** Shows overhead OMS-O\_AP and OMS-O\_CP. It receives signals from the OTSiA | OCh layer and sends signals to the OTS-O layer. +- OTS-O Layer:** Shows overhead OTS-O\_CP. It receives signals from the OMS-O layer and sends signals to the OSC layer. +- OSC Layer:** Shows overhead OSC\_AP and OSC\_CP. It receives signals from the OTS-O layer. + +Signal flow is indicated from media elements in source and sink directions, with labels such as OMS-P\_LOS, OMS-O\_RP, OTS-P\_LOS, and OTS-O\_RP. + +Diagram of OTN atomic functions for non-associated overhead information. The diagram shows a hierarchy of layers: OCh-O, OTSiG-O, OMS-O, OTS-O, and OSC. At the top, OCh-O and OTSiG-O layers are shown with their respective overhead (OCh-O\_AP, AI\_TSF, OCh-O\_CP) and their connection to a central OTSiA | OCh layer. Below this, OMS-O layers are shown, with OMS-O\_AP and OMS-O\_CP overhead. The OMS-O layers are connected to OTS-O layers, which in turn are connected to OSC layers. The OSC layers have OSC\_AP and OSC\_CP overhead. The diagram also indicates signal flow from media elements in source and sink directions, with labels like OMS-P\_LOS, OMS-O\_RP, OTS-P\_LOS, and OTS-O\_RP. + +NOTE 1 – OMS-O trail protection functions are not shown + +G.798(17)-Cor.1(18)\_F1-3 + +**Figure 1-3 – OTN atomic functions specific for the non-associated overhead information** + +![Diagram of OTN atomic functions specific for FlexO showing data flow between SD_CP, OTUCn_(T)CPs, FlexO-SD, FlexO-n/OTUCn, FlexO, FCC_CP, FlexO-x/FCC, FlexO-x/FlexO, and FlexO-x.](d4af765160d04ecef538e5066006dc77_img.jpg) + +The diagram illustrates the OTN atomic functions specific for FlexO, showing data flow between various components: + +- SD\_CP** (Service Data Contract Point) connects to **FlexO/SD**. +- OTUCn\_(T)CPs** (OTUCn Transport Contract Points, indexed 1, 2, 3, ..., N) connect to **FlexO-n/OTUCni**. +- OTUCn\_(T)CP** connects to **FlexO-n/OTUCn**. +- FlexO/SD**, **FlexO-n/OTUCni**, and **FlexO-n/OTUCn** all connect to a common horizontal bus labeled **FlexO\_AP**. +- FlexO-n/OTUCn** also connects to a **FlexO** block. +- FCC\_CP** (Framer Contract Point) connects to **FlexO-x/FCC**. +- FlexO** connects to **FlexO-x/FlexO**. +- FlexO-x/SD**, **FlexO-n/OTUCni**, and **FlexO-n/OTUCn** all connect to another common horizontal bus labeled **FlexO-x\_AP**. +- FlexO-x/SD** connects to a **FlexO-x** block. +- FlexO-x/SD** and **FlexO-x/OTUCn** both connect to a dashed oval labeled **FlexO-x\_(T)CP**. +- FlexO-x/SD** and **FlexO-x/OTUCn** both connect to a dashed oval labeled **FlexO-x\_AP**. +- FlexO-x/SD** and **FlexO-x/OTUCn** both connect to a dashed oval labeled **FlexO-x\_RP**. +- FlexO-x/SD** and **FlexO-x/OTUCn** both connect to a dashed oval labeled **FlexO-x\_(T)CP**. +- FlexO-x/SD** and **FlexO-x/OTUCn** both connect to a dashed oval labeled **FlexO-x\_AP**. +- FlexO-x/SD** and **FlexO-x/OTUCn** both connect to a dashed oval labeled **FlexO-x\_RP**. +- FlexO-x/SD** and **FlexO-x/OTUCn** both connect to a dashed oval labeled **FlexO-x\_(T)CP**. + +Diagram of OTN atomic functions specific for FlexO showing data flow between SD\_CP, OTUCn\_(T)CPs, FlexO-SD, FlexO-n/OTUCn, FlexO, FCC\_CP, FlexO-x/FCC, FlexO-x/FlexO, and FlexO-x. + +G.798(17)-Amd.3(21)\_F1-4 + +Figure 1-4 – OTN atomic functions specific for FlexO + +![Diagram of OTUk/ODUk atomic functions showing the hierarchy of client signals, overhead processing, and the central ODUk multiplexing function.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +The diagram illustrates the atomic functions for OTUk and ODUk, organized into three main vertical sections: Client Signals (top), ODUk Processing (middle), and OTUk Processing (bottom). + +- Client Signals (Top):** + - Left side (downward flow):** FC-1200\_CP, ERS10G\_CP, MT\_CP (with ellipsis), SCC\_CP, ETH\_FP, ETH\_TFP. These connect to ODU2eP/FC-1200, ODU2P/ERS10G, ODUkP-hJ/MT, and ODUkP-hJ/ETH respectively. These then connect to RSn\_CP, CBRx\_CP, CBRx\_CP, and CBRx\_CP. These further connect to ODUkP/RSn, ODU0P/CBRx, ODUkP-g/CBRx, and ODUkP/CBRx. These then connect to ODUk\_CP (with ellipsis) and ODUkP-hJ/ODUj-21, and ODUkP/ODUjij. These then connect to COMMS\_CP. These then connect to ODUkP/PRBS, ODUkP/NULL, and ODUkP/COMMS. These then connect to the ODUk\_AP. + - Right side (upward flow):** ETH\_TFP, ETH\_FP, SCC\_CP, MT\_CP (with ellipsis), ERS10G\_CP, FC-1200\_CP. These connect to ODUkP-hJ/ETH, ODUkP-hJ/MT, ODU2P/ERS10G, and ODU2eP/FC-1200 respectively. These then connect to CBRx\_CP, CBRx\_CP, CBRx\_CP, and RSn\_CP. These further connect to ODUkP/CBRx, ODUkP-g/CBRx, ODU0P/CBRx, and ODUkP/RSn. These then connect to ODUk\_CP (with ellipsis) and ODUkP/ODUjij, and ODUkP-hJ/ODUj-21. These then connect to COMMS\_CP. These then connect to ODUkP/COMMS, ODUkP/NULL, and ODUkP/PRBS. These then connect to the ODUk\_AP. +- ODUk Processing (Middle):** + - The central element is an oval labeled **ODUk**. + - On the left, an **ODUkT** block connects to the central ODUk via **ODUkT\_AP**. Above it, an **ODUkT/ODUk** block connects via **ODUkT\_AP**. To the far left, an **ODUkT\_TCMC** block connects to the ODUkT block. Above the ODUkT/ODUk block, an **ODUkT non-intrusive monitor** is shown. + - On the right, an **ODUkT** block connects to the central ODUk via **ODUkT\_AP**. Above it, an **ODUkT/ODUk** block connects via **ODUkT\_AP**. To the far right, an **ODUkT\_TCMC** block connects to the ODUkT block. Above the ODUkT/ODUk block, an **ODUkP non-intrusive monitor** is shown. + - At the top of the ODUk oval, **ODUk\_TCP** and **ODUk\_CP** are indicated. + - Below the ODUk oval, **ODUkT\_TCMC** blocks connect via **ODUkT\_AP** to **ODUkT** blocks, which connect to **OTUk[V]/ODUk** blocks via **ODUkT\_AP**. + - There are dashed lines representing reverse paths: **ODUkT\_TCMC** to **ODUkT** (left), **ODUkT** to **ODUkT/ODUk** (left), **ODUkT** to **ODUkT/ODUk** (right), and **ODUkT/ODUk** to **ODUkT\_TCMC** (right). +- OTUk Processing (Bottom):** + - The **OTUk[V]/ODUk** blocks connect to **OTUk[V]** blocks via **OTUk[V]\_AP**. + - Between the **OTUk[V]/ODUk** and **OTUk[V]** blocks, **OTUk[V]\_CP** and **OTUk[V]\_RP** are indicated. + - At the bottom, **OTUk[V]** blocks connect to **OTUk[V]\_TCP** and **OTUk[V]\_CP**. + +Diagram of OTUk/ODUk atomic functions showing the hierarchy of client signals, overhead processing, and the central ODUk multiplexing function. + +G.798(23)\_F1-5 + +Figure 1-5 – OTUk/ODUk atomic functions + +![Figure 1-6 – OTUCn/ODUCn atomic functions](7c1f9e78e0f033d391b687f1652f6e47_img.jpg) + +The diagram illustrates the functional architecture of OTUCn and ODUCn atomic functions according to ITU-T standards. At the top, multiple adaptation functions (trapezoids) for ODUCnP/PRBS, ODUCnP/NULL, ODUCnP/COMMS, and ODUCnP/ODUk are shown, feeding into ODUCn\_AP (Access Points). Below these are termination functions (triangles) for ODUCnT non-intrusive monitor, ODUCnTm, and ODUCn. These connect to a central ODUCn connection point (circle) which also interfaces with ODUCn\_TCP and ODUCn\_CP. Below the central connection point, adaptation functions for OTUCn/ODUCn lead to OTUCn termination functions, which finally interface with OTUCn\_TCP and OTUCn\_CP at the bottom. Side blocks for ODUCnT\_TCMC are also present, indicating tandem connection monitoring. Arrows indicate the flow of signals and management information between these functional blocks. + +**Figure 1-6 – OTUCn/ODUCn atomic functions** + +Figure 1-6 – OTUCn/ODUCn atomic functions + +**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.664] Recommendation ITU-T G.664 (2012), *Optical safety procedures and requirements for optical transport systems.* +- [ITU-T G.691] Recommendation ITU-T G.691 (2006), *Optical interfaces for single channel STM-64 and other SDH systems with optical amplifiers.* +- [ITU-T G.694.1] Recommendation ITU-T G.694.1 (2020), *Spectral grids for WDM applications: DWDM frequency grid.* +- [ITU-T G.694.2] Recommendation ITU-T G.694.2 (2003), *Spectral grids for WDM applications: CWDM wavelength grid.* +- [ITU-T G.695] Recommendation ITU-T G.695 (2018), *Optical interfaces for coarse wavelength division multiplexing applications.* +- [ITU-T G.696.1] Recommendation ITU-T G.696.1 (2010), *Longitudinally compatible intra-domain DWDM applications.* +- [ITU-T G.697] Recommendation ITU-T G.697 (2016), *Optical monitoring for dense wavelength division multiplexing systems.* +- [ITU-T G.698.1] Recommendation ITU-T G.698.1 (2023), *Multichannel DWDM applications with single-channel optical interfaces.* + +6 Rec. ITU-T G.798 (09/2023) + +- [ITU-T G.698.2] Recommendation ITU-T G.698.2 (2018), *Amplified multichannel dense wavelength division multiplexing applications with single channel optical interfaces.* +- [ITU-T G.705] Recommendation ITU-T G.705 (2000), *Characteristics of plesiochronous digital hierarchy (PDH) equipment functional blocks.* +- [ITU-T G.707] Recommendation ITU-T G.707/Y.1322 (2007), *Network node interface for the synchronous digital hierarchy (SDH).* +- [ITU-T G.709] Recommendation ITU-T G.709/Y.1331 (2020), *Interfaces for the optical transport network.* +- [ITU-T G.709.1] Recommendation ITU-T G.709.1/Y.1331.1 (2018), *Flexible OTN short-reach interface.* +- [ITU-T G.709.2] Recommendation ITU-T G.709.2/Y.1331.2 (2018), *OTU4 long-reach interface.* +- [ITU-T G.709.3] Recommendation ITU-T G.709.3/Y.1331.3 (2020), *Flexible OTN long-reach interfaces.* +- [ITU-T G.709.4] Recommendation ITU-T G.709.4/Y.1331.4 (2020), *OTU25 and OTU50 short-reach interfaces.* +- [ITU-T G.780] Recommendation ITU-T G.780/Y.1351 (2010), *Terms and definitions for synchronous digital hierarchy (SDH) networks.* +- [ITU-T G.781] Recommendation ITU-T G.781 (2020), *Synchronization layer functions.* +- [ITU-T G.783] Recommendation ITU-T G.783 (2006), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks.* +- [ITU-T G.784] Recommendation ITU-T G.784 (2008), *Synchronous digital hierarchy (SDH) management.* +- [ITU-T G.805] Recommendation ITU-T G.805 (2000), *Generic functional architecture of transport networks.* +- [ITU-T G.806] Recommendation ITU-T G.806 (2012), *Characteristics of transport equipment – Description methodology and generic functionality.* +- [ITU-T G.807] Recommendation ITU-T G.807 (2020), *Generic functional architecture of the optical media network.* +- [ITU-T G.808] Recommendation ITU-T G.808 (2016), *Terms and definitions for network protection and restoration.* +- [ITU-T G.808.1] Recommendation ITU-T G.808.1 (2014), *Generic protection switching – Linear trail and subnetwork protection.* +- [ITU-T G.825] Recommendation ITU-T G.825 (2000), *The Control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH).* +- [ITU-T G.831] Recommendation ITU-T G.831 (2000), *Management capabilities of transport networks based on the synchronous digital hierarchy (SDH).* +- [ITU-T G.841] Recommendation ITU-T G.841 (1998), *Types and characteristics of SDH network protection architectures.* +- [ITU-T G.872] Recommendation ITU-T G.872 (2019), *Architecture of optical transport networks.* +- [ITU-T G.873.1] Recommendation ITU-T G.873.1 (2017), *Optical transport network: Linear protection.* + +- [ITU-T G.873.2] Recommendation ITU-T G.873.2 (2015), *ODUk shared ring protection*. +- [ITU-T G.874] Recommendation ITU-T G.874 (2020), *Management aspects of optical transport network elements*. +- [ITU-T G.957] Recommendation ITU-T G.957 (2006), *Optical interfaces for equipments and systems relating to the synchronous digital hierarchy*. +- [ITU-T G.959.1] Recommendation ITU-T G.959.1 (2018), *Optical transport network physical layer interfaces*. +- [ITU-T G.7041] Recommendation ITU-T G.7041/Y.1303 (2016), *Generic framing procedure*. +- [ITU-T G.7044] Recommendation ITU-T G.7044/Y.1347 (2011), *Hitless adjustment of ODUflex (GFP)*. +- [ITU-T G.8021] Recommendation ITU-T G.8021/Y.1341 (2022), *Characteristics of Ethernet transport network equipment functional blocks*. +- [ITU-T G.8023] Recommendation ITU-T G.8023 (2018), *Characteristics of equipment functional blocks supporting Ethernet physical layer and flex Ethernet interfaces*. +- [ITU-T G.8121] Recommendation ITU-T G.8121/Y.1381 (2018), *Characteristics of MPLS-TP equipment functional blocks*. +- [ITU-T G.8251] Recommendation ITU-T G.8251 (2022), *The control of jitter and wander within the optical transport network (OTN)*. +- [ITU-T O.150] Recommendation ITU-T O.150 (1996), *General requirements for instrumentation for performance measurements on digital transmission equipment*. +- [ITU-T O.151] Recommendation ITU-T O.151 (1992), *Error performance measuring equipment operating at the primary rate and above*. +- [IEEE 802.3] IEEE Std 802.3-2022, *IEEE standard for Ethernet*. +- [ETSI TR 101 290] ETSI TR 101 290 V1.3.1 (2014), *Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems*. +- [ETSI TR 101 891] ETSI TR 101 891 V1.1.1 (2001), *Digital Video Broadcasting (DVB); Professional Interfaces: Guidelines for the implementation and usage of the DVB Asynchronous Serial Interface (ASI)*. +- [OIF FlexE] OIF-FLEXE-02.2 (2021), *FlexE 2.2 Implementation Agreement*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +### 3.1.1 Terms defined in [ITU-T G.709] + +- completely standardized OTUk (OTUk). +- connection monitoring end point (CMEP) +- functionally standardized OTUk (OTUkV) +- ODUk path (ODUkP) +- ODUk TCM (ODUkT) +- optical channel (OCh) +- optical data unit (ODU) + +- optical payload unit (OPU) +- optical transport unit (OTU) +- optical transport network (OTN) +- optical tributary signal assembly (OTSiA) +- optical tributary signal group (OTSiG) +- optical tributary signal overhead (OTSiG-O) + +### **3.1.2 Terms defined in [ITU-T G.780]** + +- BIP-X +- switching +- bidirectional (protection) switching +- unidirectional (protection) switching + +### **3.1.3 Terms defined in [ITU-T G.805]** + +- access point (AP) +- adapted information (AI) +- characteristic information (CI) +- connection point (CP) +- network +- subnetwork +- subnetwork connection (SNC) + +### **3.1.4 Terms defined in [ITU-T G.806]** + +- adaptation function (A) +- compound function +- connection function (C) +- connection matrix (CM) +- defect +- fault cause +- function +- management information (MI) +- management point (MP) +- process +- remote information (RI) +- remote point (RP) +- server signal degrade (SSD) +- server signal fail (SSF) +- termination connection point (TCP) +- trail signal degrade (TSD) +- trail signal fail (TSF) +- trail termination function (TT) + +### **3.1.5 Terms defined in [ITU-T G.807]** + +- media layer access point (M-AP) + +- media layer adapted information (M-AI) + +### **3.1.6 Terms defined in [ITU-T G.808]** + +- APS channel +- APS protocol +- 1:n (protection) architecture +- 1+1 (protection) architecture +- bridge +- broadcast bridge +- permanent bridge +- selector +- selective selector +- non-revertive (protection) operation +- revertive (protection) operation +- protection +- protection class +- subnetwork connection protection +- protection group +- extra traffic signal +- normal traffic signal +- null signal +- traffic signal + +### **3.1.7 Terms defined in [ITU-T G.831]** + +- access point identifier (API) + +### **3.1.8 Terms defined in [ITU-T G.872]** + +- optical supervisory channel (OSC) + +### **3.1.9 Terms defined in [ITU-T G.959.1]** + +- optical tributary signal (OTSi) + +### **3.1.10 Terms defined in [ITU-T G.7044]** + +- GMP normal mode +- GMP special mode + +## **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 access function (AC):** An access function provides access (add, drop, drop and continue) at CPs to communication channels transported in the overhead. + +**3.2.2 CBRx:** A CBR signal with the approximate bit rate x. + +**3.2.3 TCM control function (TCMC):** A TCM control function is responsible for the activation/deactivation of a TCM trail. + +**3.2.4 TCM control information (TCMCI):** The TCMCI is the information that passes over a TCMCP for activation/deactivation of a TCM trail. + +**3.2.5 TCM control point (TCMCP):** A reference point where the output of an atomic function is bound to the input of the TCM control function, or where the output of the TCM control function is bound to the input of an atomic function. + +**3.2.6 tributary slot map:** The list of tributary slots to be added to (increase) or removed from (decrease) an ODUflex(GFP) during resizing. + +**3.2.7 tributary slot number:** The target capacity of a resized ODUflex(GFP), expressed in number of tributary slots. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------------|-----------------------------------------| +| 1second | one second pulse | +| 1+1u | 1+1 unidirectional protection | +| A | Adaptation function | +| AC | Access function | +| ACK | Acknowledge | +| AcMSI | Accepted Multiplex Structure Identifier | +| AcPT | Accepted Payload Type | +| AcSTAT | Accepted Status Field | +| AcTI | Accepted Trail Trace Identifier | +| AdminState | Administrative State | +| AI | Adapted Information | +| AIS | Alarm Indication Signal | +| AM | Alignment Marker | +| AMP | Asynchronous Mapping Procedure | +| AP | Access Point | +| API | Access Point Identifier | +| APS | Automatic Protection Switching | +| ARC | Alarm Reporting Control | +| ASI | Asynchronous Serial Interface for DVB | +| AT | Authentication Tag | +| BCH | Bose-Chaudhuri-Hocquengham | +| BDI | Backward Defect Indication | +| BDI-O | Backward Defect Indication Overhead | +| BDI-P | Backward Defect Indication Payload | +| BEI | Backward Error Indicator | +| BIAE | Backward Incoming Alignment Error | +| BIP | Bit Interleaved Parity | +| BOH | Basic Overhead area | + +| | | +|-----------------|-------------------------------------------------------------| +| BWR | Bandwidth Resize | +| C | Connection function | +| CBR | Constant Bit Rate signal | +| CBRx | Constant Bit Rate signal of bit rate [range] x | +| CC | Calendar Configuration | +| CCA | Client Calendar A | +| CCB | Client Calendar B | +| CDI | Client Defect Indication | +| CI | Characteristic Information | +| CID | Consecutive Identical Digits | +| CK | Clock | +| C m | number of m-bit client data entities | +| C n | number of n-bit client data entities | +| C nD | difference between C n and $(m/n \times C_m)$ | +| COMMS | Communications channel | +| CP | Connection Point | +| CP n | Connection Point normal | +| CP p | Connection Point protection | +| CP w | Connection Point working | +| CRC | Cyclic Redundancy Check | +| CS | Calendar Slot | +| CSACM | Calendar Slot Availability Count Mismatch | +| CST | Cipher Suite Type | +| CSTM | Cipher Suite Type Mismatch | +| CSUM | Calendar Slot Unavailibility Mismatch | +| CSF | Client Signal Fail | +| CSUM | Calendar Slot Unavailability Mismatch | +| CTRL | Control | +| D | Data | +| DAPI | Destination Access Point Identifier | +| DEG | Degraded defect | +| DEGM | Degraded defect consecutive one-second Monitoring intervals | +| DEGThr | Degraded defect one-second errored block count Threshold | +| DI | Defect Information | +| DMGSI | Demapping Granularity Switch Indication | +| DMod | Demodulation | +| DM p | Delay Measurement of ODUk path monitoring | + +| | | +|------------|---------------------------------------------------------------------| +| DMti | Delay Measurement of ODUk tandem connection monitoring instance (i) | +| DP | Defect Point | +| DS | Defect Second | +| DS-O | Defect Second Overhead | +| DS-P | Defect Second Payload | +| DVB | Digital Video Broadcast | +| EBC | Errored Block Count | +| EFS | Equipment Functional Specification | +| EMF | Equipment Management Function | +| EOH | Extended Overhead area | +| ERSy | Ethernet Reconciliation sublayer for PHY y | +| ETCy | Ethernet Coding sublayer for PHY y | +| ETH | Ethernet MAC layer | +| ExDAPI | Expected Destination Access Point Identifier | +| ExMSI | Expected Multiplex Structure Identifier | +| ExSAPI | Expected Source Access Point Identifier | +| ExtCMD | External Command | +| F | Far-end | +| FAS | Frame Alignment Signal | +| F_B | Far-end Block | +| FC | Fibre Channel | +| FCC | FlexO Communications Channel | +| FCWS | FEC code word start | +| FDI | Forward Defect Indication | +| FDI-O | Forward Defect Indicator Overhead | +| FDI-P | Forward Defect Indicator Payload | +| F_DS | Far-end Defect Second | +| F_EBC | Far-end Errored Block Count | +| FEC | Forward Error Correction | +| FECcorrErr | Forward Error Correction Corrected Errors | +| FECEn | Forward Error Correction Enabled | +| FlexESG | FlexE Sub-Group | +| FlexESGM | FlexE Sub-Group Member | +| FlexO-x | FlexO interface information structure of order x | +| FlexO-x-SC | FlexO interface signal of order x with Staircase FEC | +| FM | Fault Management | +| FMAP | FlexO Map | + +| | | +|-----------|-------------------------------------------| +| | FlexE Map | +| FMM | FlexO Map Mismatch | +| | FlexE Map Mismatch | +| FN | Frame Number | +| FOI | FlexO Interface | +| FOICx.k | FlexO Interface of order Cx with k lanes | +| FOP | Failure Of Protocol | +| FOP-NR | Failure Of Protocol No Response | +| FOP-PM | Failure Of Protocol Provisioning Mismatch | +| FS | Frame Start | +| FSS | Frequency Slot Structure | +| GCC | Generic Communication Channel | +| GCCAccess | Generic Communication Channel Access | +| GCCCont | Generic Communication Channel Continue | +| GID | Group Identification | +| GIDM | Group Identification Mismatch | +| GMP | Generic Mapping Procedure | +| HAO | Hitless Adjustment of ODUflex | +| HEC | Header Error Control | +| HoTime | Hold-off Time | +| IAE | Incoming Alignment Error | +| IF | In-Frame | +| IID | FlexO Instance Identification | +| ILA | In-Lane-Alignment | +| IM | In-Multiframe | +| IR | In Recovery | +| IV | Initialization Vector | +| KCC | Key exchange Communication Channel | +| KI | Key Index | +| LCK | Locked defect | +| LCR | Link Connection Resize | +| LCS | Loss of Character Synchronization | +| LFA | Loss of FEC word Alignment defect | +| LLM | Logical Lane Marker | +| LOA | Loss Of Alignment | +| LOCA | Loss Of Client Alignment defect | +| LOF | Loss Of Frame | + +| | | +|---------|-----------------------------------------| +| LOFLANE | Loss of Frame of logical Lane | +| LOFLOM | Loss Of Frame and Loss Of Multiframe | +| LOL | Loss of Lane alignment | +| LOM | Loss of Multiframe | +| LOR | Loss of Recovery | +| LOS | Loss Of Signal | +| LOS-O | Loss Of Signal Overhead | +| LOS-P | Loss Of Signal Payload | +| LSB | Least Significant Bit | +| LSS | Loss of pseudo-random bit sequence lock | +| LTC | Loss of Tandem Connection | +| m | non-intrusive monitor | +| M-AI | Media Layer Adapted Information | +| M-AP | Media Layer Access Point | +| MBAS | Multi Block Alignment Signal | +| MCP | Media Channel Point | +| ME | Maintenance Entity | +| MECI | Media Element Configuration Information | +| MECP | Media Element Configuration Point | +| MFAS | Multiframe Alignment Signal | +| MFI | Multiframe Indicator | +| MFS | Multiframe Start | +| MGSI | Mapping Granularity Switch Indication | +| MI | Management Information | +| Mod | Modulation | +| MP | Management Point | +| MSI | Multiplex Structure Identifier | +| MSIM | Multiplex Structure Identifier Mismatch | +| n | normal | +| N | Near-end | +| N/A | Not Applicable | +| NACK | Negative Acknowledge | +| N_B | Near-end Block | +| NC | Network Connection | +| NCS | Network Connectivity Status | +| N_DS | Near-end Defect Second | +| N_EBC | Near-end Errored Block Count | + +| | | +|-----------|-----------------------------------------------------------------| +| NJO | Negative Justification Opportunity byte | +| NNI | Network Node Interface | +| NOS | Not_Operational | +| OAM | Operation, Administration, Maintenance | +| OCh | Optical Channel | +| OCI | Open Connection Indication | +| OCTDk[V]m | OCh, OTU and ODU Tandem Connection Monitoring Compound function | +| OCTk[V]m | OCh and OTU non-intrusive monitor | +| ODCx | ODU clock of type "x", where "x" is "a", "b", "r", or "p" | +| ODU | Optical Data Unit | +| ODUi | Optical Data Unit of level i | +| ODU[i]j | Optical Data Unit of level j and i (i is optional; i < j) | +| ODUj | Optical Data Unit of level j | +| ODUj[i] | Optical Data Unit of level j or i (i is optional; i < j) | +| ODUk | Optical Data Unit of level k | +| ODUkP | Optical Data Unit of level k, Path | +| ODUKT | Optical Data Unit of level k, Tandem connection sub-layer | +| ODUP | Optical Data Unit, Path | +| ODUT | Optical Data Unit, Tandem connection sub-layer | +| OH | Overhead | +| OLA | Out-of-Lane-Alignment | +| OM | Optical Multiplexing | +| OMFI | OPU Multiframe Identifier | +| OMFS | OPU Multiframe Start | +| OMS-O | Optical Multiplex Section – Overhead | +| OMSnP | Optical Multiplex Section Protection sub-layer of level n | +| OOF | Out-Of-Frame | +| OOM | Out-Of-Multiframe | +| OOR | Out-Of-Recovery | +| OperType | Operation Type | +| OPM | Optical Parameter Monitor | +| OPU | Optical Payload Unit | +| OPUk | Optical Payload Unit of level k | +| OS | Optical Section | +| OSC | Optical Supervisory Channel | +| OSMC | OTN synchronization messaging channel | +| OSME | Optical Signal Maintenance Entity | + +| | | +|----------|----------------------------------------------------------------------------------------------------| +| OSn | Optical Section of order n | +| OSx | Optical Section of bit rate [range] x | +| OTL | Optical Transport Lane | +| OTLk.n | Optical Transport Lane of OTUk lane number n | +| OTN | Optical Transport Network | +| OTS | Optical Transmission Section | +| OTSi | Optical Tributary Signal | +| OTSiA | Optical Tributary Signal Assembly | +| OTSiG | Optical Tributary Signal Group | +| OTSiG-O | Optical Tributary Signal Group – Overhead | +| OTU | Optical Transmission Unit | +| OTUk | Optical Transmission Unit of level k | +| OTUkV | Optical Transmission Unit of level k, functionally standardized | +| OTU4-SC | Completely standardized 100G Optical Transport Unit for long-reach applications with Staircase FEC | +| p | protection; performance data | +| PCS | Physical Coding Sub-layer | +| PCSL | Physical Coding Sub-layer of Lane | +| PHY | Physical Layer | +| PID | Physical Identification | +| PJO | Positive Justification Opportunity byte | +| PLD | Payload | +| PLM | Payload Mismatch | +| PM | Performance Management | +| PMI | Payload Missing Indication | +| PMOH | Path Monitoring Overhead | +| ppm | parts per million | +| ProtType | Protection Type | +| PRBS | Pseudo-Random Bit Sequence | +| PSI | Payload Structure Indication | +| PT | Payload Type | +| PTI | Payload Type Identifier | +| RCOH | Resize Control Overhead | +| RCOHM | Resize Control Overhead Mismatch | +| RES | Reserved overhead | +| RI | Remote Information | +| RMF | Resize Multiframe | + +| | | +|-----------|-------------------------------------------------------------| +| RP | Resizing Protocol | +| RP | Remote Point | +| RPF | Remote Physical Layer Fault | +| RS | Regenerator Section | +| RSn | Regenerator Section of level n | +| SAPI | Source Access Point Identifier | +| SC FEC | Staircase FEC | +| SD | Synchronization Distribution | +| SDH | Synchronous Digital Hierarchy | +| SF | Signal Fail | +| Sk | Sink | +| SKI | Secure Key Information | +| SMOH | Section Monitoring Overhead | +| SNC | SubNetwork Connection | +| SNC/I | SubNetwork Connection with Inherent monitoring | +| SNC/N | SubNetwork Connection with Non-intrusive monitoring | +| SNC/S | SubNetwork Connection with Sub-layer monitoring | +| So | Source | +| SRP-n | Shared Ring Protection of n ODU per Lambda (n=1, p) | +| SSD | Server Signal Degraded | +| SSF | Server Signal Fail | +| SSF-O | SSF Overhead | +| SSF-P | SSF Payload | +| STAT | Status field | +| STM | Synchronous Transport Module | +| TCM | Tandem Connection Monitoring | +| TCMC | Tandem Connection Monitoring Control function | +| TCMCI | Tandem Connection Monitoring Control Information | +| TCMCP | Tandem Connection Monitoring Control Point | +| TCMOH | Tandem Connection Monitoring Overhead | +| TCP | Termination Connection Point | +| TIM | Trail trace Identifier Mismatch | +| TIMActDis | Trail trace Identifier Mismatch consequent Actions Disabled | +| TIMDetMo | Trail trace Identifier Mismatch Detection Mode | +| TPID | Tributary Port ID | +| TrPT | Transmitted Payload Type | +| TSCC | Tributary Slot Connectivity Check | + +| | | +|-------|--------------------------------------------| +| TSD | Trail Signal Degraded | +| TSE | Test Sequence Error | +| TSF | Trail Signal Fail | +| TSF-O | Trail Signal Fail Overhead | +| TSF-P | Trail Signal Fail Payload | +| TSGS | Tributary Slot Group Status | +| TSI | Transmitter Structure Identifier | +| TSMAP | Tributary Slot Map | +| TSNUM | Tributary Slot Number | +| TT | Trail Termination function | +| TTI | Trail Trace Identifier | +| TxMSI | Transmitted Multiplex Structure Identifier | +| TxTI | Transmitted Trail Identifier | +| UNI | User Network Interface | +| w | working | +| WA | Wavelength Assignment | +| WTR | Wait To Restore | +| xI | CI or MI or AI | + +# 5 Conventions + +For the basic methodology to describe transport network functionality of network elements, refer to clause 5 of [ITU-T G.806]. + +**OTU layer** is used whenever the specification applies to both the OTUk and OTUCn layers. + +**ODU layer** is used whenever the specification applies to both the ODUk and ODUCn layers. + +**ODUP layer** is used whenever the specification applies to both the ODUkP and ODUCnP layers. + +**ODUT layer** is used whenever the specification applies to both the ODUkT and ODUCnT layers. + +**x**: Gives the approximate bit rate for a CBR signal. It is used in the form "unit value, unit, [fractional unit value]". The currently defined unit value is "G" for gigabit/s. Examples for x are "40G" for 40 Gbit/s and "2G5" for 2.5 Gbit/s. + +**y** is used as a variable for the client layer in the adaptation functions, specifically: + +- Ethernet Reconciliation sublayer for PHY y (ERSy) indicates a reconciliation sublayer of an Ethernet PHY and Ethernet Coding sublayer for PHY y (ETCy) indicates a coding sublayer of an Ethernet PHY, with 'y' describing the PHY using IEEE nomenclature, minus the word BASE. For example, the coding sublayer for 1000BASE-X PHY would be ETC1000X. + +**[1..n]**: Suffix indicating the signal consists of an array of n elements indexed from 1 to n. + +**[i]**: Suffix indicating element #i in an array of signals. + +**OTSi/\_A** and **OTSiG/\_A** are used to refer to the M-AI/\_A function identified in [ITU-T G.807]. + +**OTSi\_AP** and **OTSi\_AI** are used to refer to the media layer access point (M-AP) and media layer adapted information (M-AI) identified in [ITU-T G.807]. + +NOTE – The management interfaces connecting the various atomic functions defined in this Recommendation are not restricted to the use of management systems only but are available also for example control plane functions. + +# 6 Supervision + +The generic supervision functions are defined in clause 6 of [ITU-T G.806]. Specific supervision functions for the OTN are defined in this clause. + +## 6.1 Alarm reporting control + +Trail termination point mode and port modes are not supported by OTN equipment; instead alarm reporting control (ARC) is used. Refer to [ITU-T G.874] for the OTN ARC functionality. + +## 6.2 Defects + +### 6.2.1 Continuity supervision (loss of continuity defect) + +Continuity supervision refers to the set of processes for monitoring the integrity of the continuity of a trail. Generic continuity supervision defects are described in clause 6.2.1 of [ITU-T G.806]. OTN-specific continuity supervision defects are described here. The continuity supervision requirements for the OTN are defined in [ITU-T G.872]. + +#### 6.2.1.1 Loss of optical signal defect (dLOS-P) + +Loss of optical signal (LOS-P) defect is monitored by an optical parameter monitor (OPM) function on the OMS optical signal maintenance entity (OSME), or OTS OSME. + +The purpose of this optical parameter monitor is to indicate either: + +- i) transmitter failure, i.e., failure of the optical signal of the OTSi; or +- ii) optical path break on the OMS\_ME or OTS\_ME. + +The specific detection process, including the detection time, is out of the scope of this Recommendation. + +NOTE – Monitoring of other optical parameters, defined in [ITU-T G.697], may be defined in the future. + +An additional hold-off time is defined for the dLOS-P activation at the OTS-O\_TT\_Sk and OMS-O\_TT\_Sk. This time is introduced in order to avoid false dLOS-P activation in case the payload signal is already missing at the related trail termination source. The PMI signal is used to signal this information from the trail termination source to the sink (see clauses 6.2.6.7 and 8.10). The hold-off time has to cover the propagation, processing and detection delay of the PMI signal between the source and the sink. The hold-off time depends on the specific implementation of the PMI signalling and LOS-P detection and is not configurable. Its value is for further study. + +#### 6.2.1.2 Loss of signal payload defect (dLOS-P) + +Loss of signal payload (LOS-P) defect is monitored at the OTSi or OTSiG to OTU or FlexO adaptation functions. + +The purpose of monitoring this parameter is to indicate either: + +- i) OTSi transmitter failure; or +- ii) OTSi optical path break (this could be a result of misconfigured or broken media elements in the optical path). + +The specific detection process, including the detection time, is for further study. + +#### 6.2.1.3 Loss of signal overhead defect (dLOS-O) + +Loss of signal overhead (LOS-O) defect is monitored at the OTSi to OSC adaptation function. + +The purpose of monitoring this parameter is to indicate either: + +- i) OSC transmitter failure; or +- ii) OSC optical path break (this could be a result of misconfigured or broken media elements in the optical path). + +The specific detection process, including the detection time, is for further study. + +#### 6.2.1.4 Open connection indication defect (dOCI) + +See clause 6.2.6.8. + +#### 6.2.1.5 Loss of tandem connection defect (dLTC) + +##### 6.2.1.5.1 dLTC at the ODUT layer + +dLTC shall be declared if the accepted STAT information (AcSTAT) is "000". dLTC shall be cleared if the accepted STAT information is not equal to "000". For the STAT information acceptance process, see clause 8.8. + +During signal fail conditions of the data signal, dLTC shall be set to false. For details on the signal fail conditions, see the specific atomic functions. + +### 6.2.2 Connectivity supervision/trail trace identifier mismatch defect (dTIM) + +For the generic connectivity supervision requirements of the OTN, refer to [ITU-T G.872]. + +#### 6.2.2.1 dTIM at the OTS-O, OTSiG-O, OTU, ODUT and ODUP layer + +The TTI mismatch process reports the trail trace identifier mismatch defect (dTIM). The process is based on the comparison of expected APIs (i.e., SAPI and DAPI) with the APIs in the incoming signal. The APIs are part of the 64-byte TTI as defined in [ITU-T G.709]. + +Depending on the topology, only the SAPI, the DAPI or both are taken into account for the mismatch detection. These topologies are: + +##### Point-to-point + +In a point-to-point topology, either unidirectional or bidirectional, only the SAPI is taken into account for the comparison at the trail termination sink as shown in Figure 6-1. + +![Diagram of a point-to-point configuration showing a transmitter (TxTI) and a receiver (ExSAPI) connected by a single line. The receiver is labeled G.798(10)_F6-1.](db395493033edacd83e212049fd55715_img.jpg) + +The diagram illustrates a point-to-point configuration. On the left, a label 'TxTI' is positioned above a triangle symbol representing a transmitter. On the right, a label 'ExSAPI' is positioned above a triangle symbol representing a receiver. A horizontal line with an arrow pointing from the transmitter to the receiver connects the two symbols. Below the receiver symbol, the text 'G.798(10)\_F6-1' is displayed. + +Diagram of a point-to-point configuration showing a transmitter (TxTI) and a receiver (ExSAPI) connected by a single line. The receiver is labeled G.798(10)\_F6-1. + +**Figure 6-1 – Point-to-point configuration** + +##### Point-to-multipoint + +In a point-to-multipoint topology, only the SAPI is taken into account for the comparison at the trail termination sink as shown in Figure 6-2. + +![Figure 6-2: Point-to-multipoint configuration diagram. A single TxTI input on the left enters a 'Broadcast' ellipse. Three arrows exit the ellipse to three separate 'ExSAPI' outputs on the right. The diagram is labeled G.798(10)_F6-2.](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +Figure 6-2: Point-to-multipoint configuration diagram. A single TxTI input on the left enters a 'Broadcast' ellipse. Three arrows exit the ellipse to three separate 'ExSAPI' outputs on the right. The diagram is labeled G.798(10)\_F6-2. + +**Figure 6-2 – Point-to-multipoint configuration** + +##### **Multipoint-to-point** + +In a multipoint-to-point topology, only the DAPI is taken into account for the comparison at the trail termination sink as shown in Figure 6-3. + +![Figure 6-3: Multipoint-to-point configuration diagram. Three inputs labeled TxTI-a, TxTI-b, and TxTI-c enter from the left. Arrows from these inputs converge into a 'One selected' ellipse. An arrow exits the ellipse to an 'ExDAPI' output on the right. The diagram is labeled G.798(10)_F6-3.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +Figure 6-3: Multipoint-to-point configuration diagram. Three inputs labeled TxTI-a, TxTI-b, and TxTI-c enter from the left. Arrows from these inputs converge into a 'One selected' ellipse. An arrow exits the ellipse to an 'ExDAPI' output on the right. The diagram is labeled G.798(10)\_F6-3. + +**Figure 6-3 – Multipoint-to-point configuration** + +In addition, the mismatch detection can be disabled. + +A functional decomposition of the TTI mismatch detection process is given in Figure 6-4. + +![Figure 6-4: TTI mismatch detection process functional decomposition diagram. A large grey box contains three main components: 'SAPI compare', 'Control', and 'DAPI compare'. 'RxTI[SAPI]' enters 'SAPI compare' from the left, and 'MI_ExSAPI' enters from the right. 'SAPI compare' sends a 'Match/mismatch' signal to 'Control'. 'RxTI[DAPI]' enters 'DAPI compare' from the left, and 'MI_ExDAPI' enters from the right. 'DAPI compare' sends a 'Match/mismatch' signal to 'Control'. 'Control' sends a 'dTIM' output to the right and receives a 'MI_TIMDetMo' input from the right. The diagram is labeled G.798(10)_F6-4.](5b6e139e89c6ce90107ea7d7d77620a0_img.jpg) + +Figure 6-4: TTI mismatch detection process functional decomposition diagram. A large grey box contains three main components: 'SAPI compare', 'Control', and 'DAPI compare'. 'RxTI[SAPI]' enters 'SAPI compare' from the left, and 'MI\_ExSAPI' enters from the right. 'SAPI compare' sends a 'Match/mismatch' signal to 'Control'. 'RxTI[DAPI]' enters 'DAPI compare' from the left, and 'MI\_ExDAPI' enters from the right. 'DAPI compare' sends a 'Match/mismatch' signal to 'Control'. 'Control' sends a 'dTIM' output to the right and receives a 'MI\_TIMDetMo' input from the right. The diagram is labeled G.798(10)\_F6-4. + +**Figure 6-4 – TTI mismatch detection process** + +The SAPI/DAPI compare process compares the SAPI/DAPI part of the TTI in the incoming signal (RxTI) (see clause 15.2 of [ITU-T G.709]) with the equivalent expected SAPI/DAPI values set via the MP (MI\_ExSAPI/DAPI). The comparison result is "match" if all 16 bytes are equal, and "mismatch" if one or more bytes are unequal. "match/mismatch" conditions shall be detected within 100 ms of changes to the RxTI, ExSAPI or ExDAPI in the absence of bit errors. A persistence check shall be used in order to prevent wrong/toggling dTIM information during bit errors. + +Based on the TIM detection mode set via the MP (MI\_TIMDetMo) the defect dTIM is generated as listed in Table 6-1 in the control process. + +During signal fail conditions of the data/overhead signal, dTIM shall be set to false. For details on the signal fail conditions, see the specific atomic functions. + +**Table 6-1 – dTIM generation** + +| MI_TIMDetMo | SAPI compare | DAPI compare | dTIM | +|--------------------|---------------------|---------------------|-------------| +| Off | Don't care | Don't care | Clear | +| SAPI | Match | Don't care | Clear | +| SAPI | Mismatch | Don't care | Raise | +| DAPI | Don't care | Match | Clear | +| DAPI | Don't care | Mismatch | Raise | +| SAPI + DAPI | Match | Match | Clear | +| SAPI + DAPI | Match | Mismatch | Raise | +| SAPI + DAPI | Mismatch | Match | Raise | +| SAPI + DAPI | Mismatch | Mismatch | Raise | + +### 6.2.3 Signal quality supervision + +#### 6.2.3.1 Blank clause + +NOTE – This clause is intentionally left blank. + +#### 6.2.3.2 Blank clause + +NOTE – This clause is intentionally left blank. + +#### 6.2.3.3 Blank clause + +NOTE – This clause is intentionally left blank. + +#### 6.2.3.4 OTU and ODU signal degrade defect (dDEG) + +The algorithm for the OTU, ODUP and ODUT dDEG detection is defined in clause 6.2.3.1.2 of [ITU-T G.806]. For case of OTU and ODUT dDEG, the current and previous errored second count is discarded (assumed as 0 errored blocks) if the defect dIAE was active at any time during the second. + +Bursty distribution of errors is assumed and only the degraded signal defect (dDEG) is supported. + +For the errored block definition and the number of blocks per one-second interval, see Table 6-2. + +#### 6.2.3.5 Blank clause + +NOTE – This clause is intentionally left blank. Its text is included in clause 6.2.3.4. + +### 6.2.4 Payload mismatch supervision (dPLM) + +#### 6.2.4.1 dPLM at the ODUP layer + +dPLM shall be declared if the accepted payload type (AcPT) is not equal to the expected payload type(s) as defined by the specific adaptation function. dPLM shall be cleared if the accepted payload type is equal to the expected payload type(s), as defined by the specific adaptation function. + +NOTE – An adaptation function may support more than one payload type. + +For the payload type acceptance process, see clauses 8.7.1.1. + +#### 6.2.4.2 dPLM at the FlexO layer + +For a FlexO group of n FlexO instances, dPLM shall be declared if the accepted payload type (AcPT) is not equal to the expected payload type(s), as defined by the specific adaptation function, in any of the n FlexO instances. dPLM shall be cleared if the accepted payload type is equal to the expected payload type(s), as defined by the specific adaptation function, in all of the n FlexO instances. + +NOTE – An adaptation function may support more than one payload type. + +For the payload type acceptance process, see clause 8.7.1.2. + +### 6.2.5 Alignment supervision + +#### 6.2.5.1 Loss of frame defect (dLOF) + +dLOF is generated based on the state of the frame alignment process defined in clause 8.2.1 for OTU, in clause 8.2.9 for OTU25(u) or OTU50(u) and in clause 8.2.8 for FlexO-x. + +If the frame alignment process is in the out-of-frame (OOF) state for 3 ms, dLOF shall be declared. To provide for the case of intermittent OOFs, the integrating timer shall not be reset to zero until an in-frame (IF) condition persists continuously for 3 ms. dLOF shall be cleared when the IF state persists continuously for 3 ms. + +#### 6.2.5.2 Loss of multiframe defect (dLOM) + +dLOM is generated based on the state of the multiframe alignment process defined in clause 8.2.2. + +If the multiframe alignment process is persistently in the out-of-multiframe (OOM) state for 3 ms, dLOM shall be declared. dLOM shall be cleared immediately when the multiframe alignment process is in the in-multiframe (IM) state. + +#### 6.2.5.3 Loss of frame and multiframe defect (dLOFLOM) + +dLOFLOM is generated based on the state of the frame and multiframe alignment process defined in clause 8.2.3. + +If the process is in the out-of-frame (OOF) state for 3 ms, dLOFLOM shall be declared. To provide for the case of intermittent OOFs, the integrating timer shall not be reset to zero until an in-frame (IF) condition persists continuously for 3 ms. dLOFLOM shall be cleared when the IF state persists continuously for 3 ms. + +#### 6.2.5.4 Blank clause + +NOTE – This clause is intentionally left blank. + +#### 6.2.5.5 Loss of lane alignment defect (dLOL) + +dLOL is generated for multilane interfaces based on the state of the lane alignment process of the multilane signals defined in clause 8.2.6. + +If the multilane alignment process is in the out-of-alignment (OLA) state, dLOL shall be declared. dLOL shall be cleared when the multilane alignment process is in the ILA state. + +#### **6.2.5.6 Loss of frame defect of logical lane (dLOFLANE)** + +The loss of frame defect of lane on a multilane signal dLOFLANE is generated based on the state of the frame alignment process defined in clause 8.2.5. + +If the frame alignment process is in the out-of-frame (OOF) state for 3 ms, dLOFLANE shall be declared. To provide for the case of intermittent OOFs, the integrating timer shall not be reset to zero until an in-frame (IF) condition persists continuously for 3 ms. dLOFLANE shall be cleared when the IF state persists continuously for 3 ms. + +#### **6.2.5.7 Loss of character synchronization (dLCS)** + +##### **6.2.5.7.1 Loss of character synchronization of 66b blocks (dLCS)** + +The defect dLCS is generated based on the lock state machine of 66b block synchronization defined in Figure 82-12 of [IEEE 802.3]. dLCS shall be cleared if the block synchronization process has achieved block lock (rx\_block\_lock is true); dLCS shall be declared if the block synchronization process has lost block lock (rx\_block\_lock is false). + +##### **6.2.5.7.2 Loss of character synchronization of 1027b blocks (dLCS)** + +The defect dLCS is generated based on the lock state machine of 1027b block synchronization defined in Annex F of [ITU-T G.709]. dLCS shall be cleared if the block synchronization process has achieved block lock (1027B\_block\_lock is true); dLCS shall be declared if the block synchronization process has lost block lock (1027B\_block\_lock is false). + +### **6.2.6 Maintenance signal supervision** + +#### **6.2.6.1 Forward defect indication payload defect (dFDI-P)** + +##### **6.2.6.1.1 dFDI-P at the OMS-O, OCh-O and OTSiG-O layer** + +The FDI-P maintenance signal is inserted into the non-associated overhead for the client layer maintenance entity(ies) in response to detection of defects in the media element for which the maintenance entity is providing monitoring. E.g., an OTS-O termination sink inserts OMS-P FDI in response to media element failures. + +Forward defect indication payload (FDI-P) defect is monitored at the OMS-O, OCh-O and OTSiG-O layers. The purpose of monitoring this parameter is to suppress downstream alarms at the client layer caused by upstream defects detected by the server layer, which interrupt the client payload signal. + +FDI-P defect (dFDI-P) shall be declared at the trail termination sink function within X ms of detecting the upstream defect causing the insertion of FDI-P into the appropriate portion of the OSC. + +FDI-P defect (dFDI-P) shall be cleared at the trail termination sink function within Y ms of detecting that the upstream defect, which caused the insertion of FDI-P, has cleared. + +X and Y are for further study. + +#### **6.2.6.2 Forward defect indication overhead defect (dFDI-O)** + +##### **6.2.6.2.1 dFDI-O at the OMS-O and OTSiG-O layer** + +The FDI-O maintenance signal is inserted into the non-associated overhead for the client layer maintenance entity(ies) in response to detection of defects in a server maintenance entity. E.g., an OTS-O termination sink inserts OMS-O FDI in response to OTS-O faults. + +Forward defect indication overhead (FDI-O) defect is monitored at the OMS-O, OCh-O and OTSiG-O layers. The purpose of monitoring this parameter is to suppress downstream alarms at the client layer caused by upstream defects detected by the server layer which interrupt the OSC. + +FDI-O defect (dFDI-O) shall be declared at the trail termination sink function within X ms of detecting the upstream defect causing the insertion of FDI-O into the appropriate portion of the OSC. + +FDI-O defect (dFDI-O) shall be cleared at the trail termination sink function within Y ms of detecting that the upstream defect, which caused the insertion of FDI-O, has cleared. + +X and Y are for further study. + +#### 6.2.6.3 Alarm indication signal defect (dAIS) + +##### 6.2.6.3.1 dAIS at OTUk layer (generic AIS; k = 1, 2, 3) + +The OTUk dAIS defect detection is identical to the CBR client signal dAIS detection defined in clause 6.2.6.3.3. + +NOTE – OTUk-AIS (k = 1, 2, 3) is defined to support a future server layer application. OTN equipment should be capable of detecting the presence of such signal, except in the case of OTSiG/OTUk\_A; it is not required to generate such a signal. + +##### 6.2.6.3.2 dAIS at OTUCn, ODUT and ODUP layer + +dAIS shall be declared if the accepted STAT information (AcSTAT) is "111". dAIS shall be cleared if the accepted STAT information is not equal to "111". For the STAT information acceptance process, see clause 8.8. + +##### 6.2.6.3.3 dAIS for CBR client signals (generic AIS) + +For the CBR dAIS detection, the reverse PN-11 process is applied to the data signal, as shown in Figure 6-5. At the output of this process (OUT), an all-ZEROs pattern will occur if the input data (IN) is the PN-11 generic AIS sequence. Note that an all-ZEROs output pattern will also occur in case of an all-ZEROs input pattern. Both the output (OUT) and input (IN) signals are constantly checked over an 8192-bit interval for the number of non ZERO bits (= ONE bits). If the number of ONE bits per interval at OUT is less than 256 and the number of ONE bits per interval at IN is above or equal to 256 in three consecutive intervals, dAIS is raised. If the number of ONE bits at OUT is above or equal to 256 or the number of ONE bits at IN is below 256 in three consecutive intervals, dAIS is cleared. + +NOTE – Generic AIS forwarded to SDH interfaces will lead to LOF in OSn/RSn\_A\_Sk functions not capable of detecting this AIS signal. In the case where an SDH input interface is connected to an STM-N output signal of a network-element terminating the OTN transport where this AIS signal is inserted, a dLOF defect could be interpreted as an AIS indication. + +![Figure 6-5: Inverse PN-11 process for generic AIS detection. The diagram shows an input signal (IN) entering a series of 11 D flip-flops (D Q) connected in sequence. A common clock signal is provided to all flip-flops. The output of the last flip-flop is labeled OUT. Above the flip-flops, there are two summation nodes (circles with a plus sign). The first summation node takes the output of the 11th flip-flop and a feedback signal from the output of the 10th flip-flop. The second summation node takes the output of the 10th flip-flop and a feedback signal from the output of the 9th flip-flop. The outputs of these two summation nodes are connected to the OUT signal line.](0fa5b60804100c3aead10404f9f226f9_img.jpg) + +The diagram illustrates the Inverse PN-11 process for generic AIS detection. An input signal (IN) enters a chain of 11 D flip-flops (D Q) connected in series. A common clock signal is provided to all flip-flops. The output of the 11th flip-flop is labeled OUT. Above the flip-flops, there are two summation nodes (circles with a plus sign). The first summation node takes the output of the 11th flip-flop and a feedback signal from the output of the 10th flip-flop. The second summation node takes the output of the 10th flip-flop and a feedback signal from the output of the 9th flip-flop. The outputs of these two summation nodes are connected to the OUT signal line. The diagram is labeled G.798(10)\_F6-5. + +Figure 6-5: Inverse PN-11 process for generic AIS detection. The diagram shows an input signal (IN) entering a series of 11 D flip-flops (D Q) connected in sequence. A common clock signal is provided to all flip-flops. The output of the last flip-flop is labeled OUT. Above the flip-flops, there are two summation nodes (circles with a plus sign). The first summation node takes the output of the 11th flip-flop and a feedback signal from the output of the 10th flip-flop. The second summation node takes the output of the 10th flip-flop and a feedback signal from the output of the 9th flip-flop. The outputs of these two summation nodes are connected to the OUT signal line. + +Figure 6-5 – Inverse PN-11 process for generic AIS detection + +#### 6.2.6.4 Backward defect indication payload defect (dBDI-P) + +##### 6.2.6.4.1 dBDI-P at OTS-O and OMS-O layer + +The BDI-P maintenance signal is inserted into the non-associated overhead for a maintenance entity by the source function in response to reception of the FDI-P maintenance signal by the corresponding sink function or detection of a defect in the media element that is being monitored by the maintenance entity. + +Backward defect indication payload defect (dBdi-P) is monitored at the OTS-O and OMS-O layers. The purpose of monitoring this parameter is to allow for single-ended supervision of the trail. + +BDI-P defect (dBdi-P) shall be declared at the trail termination sink function within X ms of detecting the far-end defect causing the insertion of BDI-P into the appropriate portion of the OSC. + +BDI-P defect (dBdi-P) shall be cleared at the trail termination sink function within Y ms of detecting that the far-end defect, which caused the insertion of BDI-P, has cleared. + +X and Y are for further study. + +During signal fail conditions of the overhead signal, dBdi-P shall be set to false. For details on the signal fail conditions, see the specific atomic functions. + +#### **6.2.6.5 Backward defect indication overhead defect (dBdi-O)** + +##### **6.2.6.5.1 dBdi-O at OTS-O and OMS-O layer** + +The BDI-O maintenance signal is inserted into the non-associated overhead of a maintenance entity by the source function in response to reception of FDI-O or detection of a server layer maintenance entity defect in the corresponding sink function. + +Backward defect indication overhead defect (dBdi-O) is monitored at the OTS-O and OMS-O layers. The purpose of monitoring this parameter is to allow for single-ended supervision of the trail. + +BDI-O defect (dBdi-O) shall be declared at the trail termination sink function within X ms of detecting the far-end defect causing the insertion of BDI-O into the appropriate portion of the OSC. + +BDI-O defect (dBdi-O) shall be cleared at the trail termination sink function within Y ms of detecting that the far-end defect, which caused the insertion of BDI-O, has cleared. + +X and Y are for further study. + +During signal fail conditions of the overhead signal, dBdi-O shall be set to false. For details on the signal fail conditions, see the specific atomic functions. + +#### **6.2.6.6 Backward defect indication defect (dBdi)** + +##### **6.2.6.6.1 dBdi at OTU, ODUT and ODUP layer** + +dBdi shall be declared if the BDI bit in the SM/TCMi/PM overhead field (byte 3, bit 5) in the first overhead instance is "1" for X consecutive frames. dBdi shall be cleared if the BDI bit in the SM/TCMi/PM overhead field is "0" for X consecutive frames. For OTUk, ODUkT and ODUkP X shall be 5; for OTUCn, ODUCnT and ODUCnP X shall be 15. + +During signal fail conditions of the data signal, dBdi shall be set to false. For details on the signal fail conditions, see the specific atomic functions. + +#### **6.2.6.7 Payload missing indication defect (dPMI)** + +##### **6.2.6.7.1 dPMI at the OTS-O and OMS-O layer** + +Payload missing indication (PMI) defect is monitored at the OTS-O and OMS-O layers. The purpose of monitoring this parameter is to suppress downstream loss of signal alarms at the trail termination sink due to upstream defects causing missing payload at the start of the trail. + +PMI defect (dPMI) shall be declared at the trail termination sink function within X ms of detecting the missing payload condition causing the insertion of PMI into the appropriate portion of the OSC. + +PMI defect (dPMI) shall be cleared at the trail termination sink function within Y ms of detecting that the missing payload condition, which caused the insertion of PMI, has cleared. + +X and Y are for further study. Values in the range of a few milliseconds are proposed, as PMI has to suppress the payload defect at the sink immediately. + +During signal fail conditions of the overhead signal, dPMI shall be set to false. For details on the signal fail conditions, see the specific atomic functions. + +NOTE – The defect PMI will not result in a fault cause. It is used to suppress LOS-P defects-related consequent actions, defect correlations and performance monitoring data at the OTS-O and OMS-O trail termination sink in case of an already missing payload at the trail termination source (see clauses 6.2.1.1 and 8.10). + +#### **6.2.6.8 Open connection indication defect (dOCI)** + +Open connection indication defect (dOCI) is monitored at the OCh-O, OTSiG-O and ODUk layers. The purpose of monitoring this parameter is to qualify a downstream loss of signal defect by indicating that the loss of signal defect is due to an output connection point not connected to an input connection point. + +##### **6.2.6.8.1 dOCI at the OCh-O and OTSiG-O layer** + +OCI defect (dOCI) shall be declared at the OCh-O and OTSiG-O trail termination sink function within X ms of the OTSiA|OCh connection function having received the command via the MP to disconnect the output OTSiG or OTSi and OTSiG-O or OCh-O CP from an input OTSiG or OTSi and OTSiG-O or OCh-O CP. + +OCI defect (dOCI) shall be cleared at the OCh-O and OTSiG-O trail termination sink function within Y ms of the OCh connection function detecting that the output OTSiG or OTSi and OTSiG-O or OCh-O CP, which the OCI corresponded to, is connected to an input OTSiG or OTSi and OTSiG-O or OCh-O CP. + +X and Y are for further study. + +During signal fail conditions of the overhead signal, dOCI shall be set to false. For details on the signal fail conditions, see the specific atomic functions. + +##### **6.2.6.8.2 dOCI at the ODUkP and ODUkT layer** + +dOCI shall be declared if the accepted STAT information (AcSTAT) is "110". dOCI shall be cleared if the accepted STAT information is not equal to "110". For the STAT information acceptance process, see clause 8.8. + +During signal fail conditions of the data signal, dOCI shall be set to false. For details on the signal fail conditions, see the specific atomic functions. + +NOTE – dOCI is not detected at the ODUCnP and ODUCnT layer. + +#### **6.2.6.9 Locked defect (dLCK)** + +##### **6.2.6.9.1 dLCK at the ODUP and ODUT layer** + +dLCK shall be declared if the accepted STAT information (AcSTAT) is "101". dLCK shall be cleared if the accepted STAT information is not equal to "101". For the STAT information acceptance process, see clause 8.8. + +During signal fail conditions of the data signal, dLCK shall be set to false. For details on the signal fail conditions, see the specific atomic functions. + +#### **6.2.6.10 Incoming alignment error defect (dIAE)** + +NOTE – The defect IAE will not result in a fault cause. It is used to suppress wrong PM data (EBC and DS) at the OTU and ODUT trail termination sink in case of an incoming frame slip to the trail (see clause 8.10). + +##### **6.2.6.10.1 dIAE at the OTUk layer** + +dIAE shall be declared if the IAE bit in the SM overhead field (byte 3, bit 6) is "1" for X consecutive frames. dIAE shall be cleared if the IAE bit in the SM overhead field is "0" for X consecutive frames. X shall be 5. + +During signal fail conditions of the data signal, dIAE shall be set to false. For details on the signal fail conditions, see the specific atomic functions. + +##### **6.2.6.10.2 dIAE at the OTUCn and ODUT layer** + +dIAE shall be declared if the accepted STAT information (AcSTAT) is "010". dIAE shall be cleared if the accepted STAT information is not equal to "010". For the STAT information acceptance process, see clause 8.8. + +During signal fail conditions of the data signal, dIAE shall be set to false. For details on the signal fail conditions, see the specific atomic functions. + +#### **6.2.6.11 Backward incoming alignment error defect (dBIAE)** + +NOTE – The defect BIAE will not result in a fault cause. It is used to suppress wrong far-end PM data (EBC and DS) at the OTU and ODUT trail termination sink in case of an incoming frame slip to the trail (see clause 8.10). + +##### **6.2.6.11.1 dBIAE at the OTU and ODUT layer** + +dBIAE shall be declared if the BEI/BIAE bits in the SM/TCM overhead field (byte 3, bits 1 to 4) in the first overhead instance are "1011" for X consecutive frames. dBIAE shall be cleared if the BEI/BIAE bits in the SM/TCM overhead field are not equal to "1011" for X consecutive frames. X shall be 3. + +During signal fail conditions of the data signal, dBIAE shall be set to false. For details on the signal fail conditions, see the specific atomic functions. + +### **6.2.7 Protocol supervision** + +#### **6.2.7.1 Protection protocol supervision** + +##### **6.2.7.1.1 ODU linear protection failure of protocol provisioning mismatch (dFOP-PM)** + +ODUk dFOP-PM shall be declared when the B bit of the transmitted and accepted APS protocol do not match. + +ODUk dFOP-PM shall be cleared when the B bit of the transmitted and accepted APS protocols do match. + +For a description of the APS protocol, see [ITU-T G.873.1]. + +##### **6.2.7.1.2 ODU linear protection failure of protocol no response defect (dFOP-NR)** + +ODUk dFOP-NR shall be declared when the requested signal and the bridge signal in the APS protocol do not match within 1 s. + +NOTE – The time after which a response on a bridge request is received depends on the transmission delay between the protection switching nodes (and the processing delay in the nodes). + +ODUk dFOP-NR shall be cleared when the requested signal and the bridge signal in the APS protocol match. + +For a description of the APS protocol, see [ITU-T G.873.1]. + +#### **6.2.7.2 Security protocol supervision** + +##### **6.2.7.2.1 FlexOsec decryption unlock and replay defect (dUnlockSec)** + +The defect dUnlockSec shall be generated based on the state of the lock process within the FlexOsec sink processes (see clause 8.14.2). If the process is in the out-of-lock (OOL) or pre-lock (PL) state, dUnlockSec shall be declared. dUnlockSec shall be cleared immediately when the process is in the in-lock (IL) state. + +### 6.2.8 Optical supervisory channel (OSC) related defects + +As the specific format of the OSC is outside the scope of [ITU-T G.709], no specific defects, except for dLOS-O (see clause 6.2.1.3), are defined in this Recommendation either. However, depending on the specific OSC format, additional defect detection (e.g., loss of alignment) is required. These defects will contribute to the TSF-P, SSF-P, FDI-P and BDI-P consequent actions. + +### 6.2.9 Multiplex structure identifier mismatch supervision defect (dMSIM) + +#### 6.2.9.1 dMSIM[i] at the ODUkP layer + +Refer to clause 8.7.2.1 for a description of AcMSI[i] and ExMSI[i]. + +The defect dMSIM shall be declared if the AcMSI is not equal to the ExMSI. dMSIM shall be cleared if the AcMSI is equal to the ExMSI. + +ExMSI is either a fixed value or configured via the management interface in the applicable atomic functions. + +For the AcMSI acceptance process, see clause 8.7.2.1. + +dMSIM shall be detected within 100 ms of changes to the AcMSI or the ExMSI. + +NOTE – The dMSIM defect as detected on an OPUk multiplex structure does not detect all possible wrong configurations on both sides of the link. For instance, if there are unallocated tributary slots that are carrying an ODUj with a tributary port that is also not allocated, such a mismatch will not lead to dMSIM defect detection. Also, in cases where timeslots in a received multiplexed signal are part of a client ODU structure, which are not configured to be allocated as timeslots at the ODUkP/ODUj adaptation sink for that client ODUj, this condition will not be detected and alarmed. The dLOFLOM defect will be detected in such cases. + +#### 6.2.9.2 dMSIM[i] at the ODUCnP and FlexO layers + +The dMSIM defect for ODU tributaries is based on comparing the AcMSI and ExMSI of all OPU instances. + +Upon accepting a new AcMSI value for an OPU instances the nMSIM anomalies for all tributary ports are initialized to false. The AcMSI are then compared to the ExMSI for all OPU instances. For each case where the AcMSI and ExMSI values pertaining to the same tributary slot are not equal, + +- a) if the tributary slot is allocated in the ExMSI value, the nMSIM anomaly of the tributary port subfield of the ExMSI value is set, +- b) if the tributary slot is allocated in the AcMSI value, the nMSIM anomaly of the tributary port subfield of the AcMSI value is set. + +The dMSIM defect of each tributary port shall be set to the corresponding nMSIM anomaly. + +``` + +for trib_port = 1 to number_of_trib_ports + nMSIM[trib_port] = false + +for opu = 1 to number_of_instances + for trib_slot = 1 to number_of_trib_slots + if AcMSI[opu][trib_slot] != ExMSI[opu][trib_slot] + if ExMSI[opu][trib_slot].allocated + nMSIM[ ExMSI[trib_slot].trib_port ] = true + if AcMSI[opu][trib_slot].allocated + nMSIM[ AcMSI[trib_slot].trib_port ] = true + +for trib_port = 1 to number_of_trib_ports + dMSIM[trib_port] = nMSIM[trib_port] + +``` + +For the AcMSI acceptance process, see clause 8.7.2.2. + +dMSIM shall be detected within 100 ms of changes to the AcMSI or the ExMSI. + +#### 6.2.9.3 dMSIM[i] at the OMS-O layer + +The defect dMSIM shall be declared if the AcMSI is not equal to the ExMSI. dMSIM shall be cleared if the AcMSI is equal to the ExMSI. + +The format of the AcMSI and ExMSI and the AcMSI acceptance process depends on the specific implementation. + +### 6.2.10 Client signal fail defect (dCSF) + +dCSF shall be declared if the CSF bit in the OPUk PSI overhead (bit 1 of the PSI[2] byte) is "1" for X consecutive 256-frame multiframes. dCSF shall be cleared if the CSF bit is "0" for X consecutive 256-frame multiframes. X shall be 3. + +### 6.2.11 Cipher Suite Type mismatch supervision (dCSTM) + +#### 6.2.11.1 dCSTM at the FlexO layer + +For a FlexO-*x* frame of *x* FlexO instances, dCSTM shall be declared if the accepted cipher suite type (AcCST) is not equal to the expected cipher suite type(s), as defined by the specific adaptation function, in any of the *x* FlexO instances. dCSTM shall be cleared if the accepted cipher suite type is equal to the expected cipher suite type(s), as defined by the specific adaptation function, in all of the *x* FlexO instances. + +NOTE – An adaptation function may support more than one cipher suite type. + +For the cipher suite type acceptance process, see clause 8.14.2. + +## 6.3 Consequent actions + +For consequent actions, see [ITU-T G.806] and the specific atomic functions. + +## 6.4 Defect correlations + +For the defect correlations, see the specific atomic functions. + +## 6.5 Performance filters + +### 6.5.1 One-second performance monitoring filters associated with counts + +#### 6.5.1.1 Errored block count (EBC) + +The one-second performance monitoring filters pN\_EBC and pF\_EBC are defined in clause 6.5 of [ITU-T G.806]. For the application of these filters, see the specific atomic functions. + +The OTN errored block definitions are given in Tables 6-2 and 6-3. + +During signal fail conditions of the data signal, no errored blocks shall be counted. For details on the signal fail conditions, see the specific atomic functions. + +**Table 6-2 – OTN near-end errored blocks definition** + +| Layer | Errored block definition | Number of blocks per second (Note 4) | +|---------------------------|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OTU
(Notes 1 and 3) | One or more errors detected by the OTU BIP-8 | OTU0: 10168
OTU1: 20421
OTU2: 82026
OTU3: 329492
OTU4: 856388
OTU25u: 205094
OTU25: 215823
OTU50u: 410187
OTU50: 431645
OTUCn: $n \times 860177$ | +| ODUT/P
(Notes 2 and 3) | One or more errors detected by the ODUT/P BIP-8 | ODU0 10168
ODU1: 20421
ODU2: 82026
ODU2e 84986
ODU3: 329492
ODU4: 856388
ODU25u: 205094
ODU25: 215823
ODU50u: 410187
ODU50: 431645
ODUflex: $ODUflex\_bit\_rate/122368$
ODUCn: $n \times 860177$ | + +NOTE 1 – The block size for OTUk, $k = 0, 1, 2, 3, 4$ is equal to the OTUk frame size, which is $4 \times 4080 \times 8 = 130\,560$ bits. The block size for OTU25 and OTU50 is equal to the OTU25 and OTU50 frame size, which is $4 \times 3824 \times 8 = 122\,368$ bits. The block size for OTUC is equal to the OTUC instance frame size, which is $4 \times 3824 \times 8 = 122\,368$ bits. An OTUCn has n OTUC instances and n blocks. + +NOTE 2 – The block size for ODUk, $k = 0, 1, 2, 2e, 3, 4, 25, 50, flex$ is equal to the ODUk frame size, which is $4 \times 3824 \times 8 = 122\,368$ bits. The block size for ODUC is equal to the ODUC instance frame size, which is $4 \times 3824 \times 8 = 122\,368$ bits. An ODUCn has n ODUC instances and n blocks. + +NOTE 3 – The EDC is BIP-8, and is computed over the OPU payload instance ( $4 \times 3808 \times 8$ bits) plus OPU overhead instance ( $4 \times 2 \times 8$ bits), for a total of $4 \times 3810 \times 8 = 121\,920$ bits. The EDC usage is $1 \times BIP-8$ . + +NOTE 4 – These values are rounded to the next larger integer value. + +**Table 6-3 – OTN far-end errored blocks definition** + +| Layer | Errored block definition | Number of blocks per second (Note) | +|-------------------------------------------------------------------|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OTU | One or more errors indicated by BEI in the OTU frame | OTU0: 10168
OTU1: 20421
OTU2: 82026
OTU3: 329492
OTU4: 856388
OTU25u: 205094
OTU25: 215823
OTU50u: 410187
OTU50: 431645
OTUCn: $n \times 860177$ | +| ODUT/P | One or more errors indicated by BEI in the ODUT/P frame | ODU0 10168
ODU1: 20421
ODU2: 82026
ODU2e: 84986
ODU3: 329492
ODU4: 856388
ODU25u: 205094
ODU25: 215823
ODU50u: 410187
ODU50: 431645
ODUflex: $ODUflex\_bit\_rate / 122368$
ODUCn: $n \times 860177$ | +| NOTE – These values are rounded to the next larger integer value. | | | + +#### 6.5.1.2 Defect second (DS) + +The one-second performance monitoring filters pN\_DS and pF\_DS are defined in clause 6.5 of [ITU-T G.806]. For the application of these filters, see the specific atomic functions. + +#### 6.5.1.3 FEC corrected errors (FECcorrErr) + +The number of bits corrected by the FEC (see clause 8.5) are counted over one second and reported to the MI at the end of the second. For the application of this filter, see the specific atomic functions. + +During signal fail conditions of the data signal, no corrected bits shall be counted. For details on the signal fail conditions, see the specific atomic functions. + +#### 6.5.1.4 Authentication failures (AuthCheckErr) + +The number of received frames that have failed integrity check (i.e., authentication failures, see clause 8.14.2) are counted over one second and reported to the MI at the end of the second. For the application of this filter, see the specific atomic functions. + +During signal fail conditions of the data signal, no authentication failure shall be counted. For details on the signal fail conditions, see the specific atomic functions. + +# 7 Information flow across reference points + +See clause 7 of [ITU-T G.806] for a generic description of information flow. For the OTN-specific information flow, see the description of the functions in clauses 9 and following. + +# 8 Generic processes + +Generic processes are defined in clause 8 of [ITU-T G.806]. This clause defines the specific process for the OTN. + +## 8.1 Blank clause + +NOTE – This clause is intentionally left blank. + +## 8.2 Alignment processes + +### 8.2.1 OTU frame alignment + +The OTU frame alignment shall be found by searching for the OA1, OA2 FAS bytes (see [ITU-T G.709]) contained in the OTU frame. + +The process has two states, out-of-frame (OOF) and in-frame (IF). + +In the OOF state, the framing pattern searched for shall be a 4-byte subset of the OA1 and OA2 bytes. The IF state shall be entered if this subset is found and confirmed one frame period later. + +In the IF state, the frame signal shall be continuously checked with the presumed frame start position for correct alignment. The framing pattern checked for shall be the OA1OA2OA2 pattern (bytes 3, 4 and 5 of the first row of the OTU frame). The OOF state shall be entered if this subset is not found at the correct position in five consecutive frames. + +The frame start shall be maintained during the OOF state. + +### 8.2.2 OTU and FlexO multiframe alignment + +The OTU multiframe alignment shall be found based on the MFAS byte of the first instance of the OTU overhead (see [ITU-T G.709]) contained in the OTU frame. The FlexO multiframe alignment shall be found based on the MFAS byte (see clause 9.2.1 of [ITU-T G.709.1]) contained in the FlexO frame. + +The process has two states, out-of-multiframe (OOM) and in-multiframe (IM). + +In the IM state, OOM shall be assumed when the received MFAS does not match with the expected multiframe number in five consecutive frames. + +In the OOM state, multiframe alignment shall be assumed to be recovered, the multiframe counter shall be set to the new MFAS, and the IM state shall be entered, when a valid MFAS sequence is found in two consecutive frames. The MFAS sequence is valid if the MFAS of the second frame is the increment of the MFAS of the first frame. + +The multiframe start shall be maintained during the OOM state. + +### 8.2.3 Frame and multiframe alignment for OTUC or extended ODUj + +The OTUC or extended ODUj frame and multiframe alignment shall be found by searching for the framing pattern (OA1, OA2 FAS bytes) and checking the multiframe sequence (MFAS byte) (see [ITU-T G.709]) contained in the OTUC or extended ODUj frame structure. + +The process has two states, out-of-frame (OOF) and in-frame (IF). + +In the OOF state, the framing pattern searched for shall be the full set of the OA1 and OA2 bytes. The IF state shall be entered if this set is found and confirmed one frame period later and an error-free multiframe sequence is found in the MFAS bytes of the two frames. + +In the IF state, the frame alignment signal shall be continuously checked with the presumed frame start position and the expected multiframe sequence. The framing pattern checked for shall be the OA1OA2 pattern (bytes 3 and 4 of the first row of the OTUC or extended ODUj frame structure). The OOF state shall be entered if this subset is not found at the correct position within five consecutive + +frames, or the received MFAS does not match the expected multiframe number within five consecutive frames. + +The frame and multiframe start shall be maintained during the OOF state. + +### 8.2.4 Blank clause + +NOTE – This clause is intentionally left blank. + +### 8.2.5 OTU logical lane frame alignment + +OTU logical lane frame alignment shall be found by searching for the OA1, OA2 FAS bytes within the logical lane. As specified in Annex C of [ITU-T G.709], the OTU logical lane frame alignment signal consists of three OA1 followed by N OA2 bytes and is present periodically every 16320 bytes. N = 3 for the four-logical-lane (OTU3) interface and N = 2 for the 20-logical-lane (OTU4) interface. + +The process has two states, out-of-frame (OOF) and in-frame (IF). + +In the OOF state, the framing pattern searched for shall be a 4-byte subset of the OA1 and OA2 bytes. The IF state shall be entered if this subset is found and confirmed a period of 16320 bytes later. + +In the IF state, the frame signal shall be continuously checked with the presumed frame start position for correct alignment. The framing pattern checked for shall be the OA1OA2OA2 pattern (bytes 3, 4 and 5 of the first row of the logical lane frame). The OOF state shall be entered if this subset is not found at the correct position in five consecutive periods of 16320 bytes. + +The frame start shall be maintained during the OOF state. + +NOTE – This process is identical to the OTUk frame alignment process. + +### 8.2.6 OTU logical lane alignment + +The OTU logical lane alignment process is used to establish alignment of the lanes of the OTU multilane interface. + +The bytes of the OTUk signals (k = 3, 4) are distributed to the logical lanes in 16-byte increments as specified in Annex C of [ITU-T G.709]. + +For the OTU3 with four logical lanes, the MFAS is reused as logical lane marker information. The MFAS sequence 00000000, 00000001, ..., 11111111 (i.e., 0 to 255) is inserted before distribution of the OTU3 bytes over the four logical lanes. After distribution of the OTU3 16-byte increments over the four logical lanes, each lane will carry a subset of the MFAS values of which the two least significant bits are constant (either 00, 01, 10, or 11) and identifies the logical lane number. + +- Logical lane 0 will carry the following MFAS values: 00000000 – 00000100 – 00001000 – 00001100 – 00010000 – 00010100 – ... – 11111100. +- Logical lane 1 will carry the following MFAS values: 00000001 – 00000101 – 00001001 – 00001101 – 00010001 – 00010101 – ... – 11111101. +- Logical lane 2 will carry the following MFAS values: 00000010 – 00000110 – 00001010 – 00001110 – 00010010 – 00010110 – ... – 11111110. +- Logical lane 3 will carry the following MFAS values: 00000011 – 00000111 – 00001011 – 00001111 – 00010011 – 00010111 – ... – 11111111. + +For the OTU4 with twenty logical lanes the LLM carries the logical lane marker information. The LLM sequence 00000000, 00000001, ..., 11101111 (i.e., 0 to 239) is inserted before the distribution of the OTU4 bytes over the twenty logical lanes. After the distribution of the OTU4 16-byte increments over the twenty logical lanes, each logical lane will carry a subset of the LLM values of which the modulo 20 value is constant and identifies the logical lane number. + +- Logical lane 0 will carry the following LLM values (0, 20, 40, 60, ..., 200, 220): 00000000 – 00010100 – ... – 11011100. + +- Logical lane 1 will carry the following LLM values (1, 21, 41, 61, ..., 201, 221): 00000001 – 00010101 – ... – 11011101. +- ... +- Logical lane 18 will carry the following LLM values (18, 38, 58, 78, ..., 218, 238): 00010010 – 00100110 – ... – 11101110. +- Logical lane 19 will carry the following LLM values (19, 39, 59, 79, ..., 219, 239): 00010011 – 00100111 – ... – 11101111. + +#### 8.2.6.1 OTU3 multilane alignment + +The process has two sub-processes: + +- logical lane marker recovery (per lane); +- multilane alignment (composite signal). + +The logical lane marker signal is located in bits 7 and 8 of the MFAS byte of the logical lane frame. These bits are scrambled with the scrambler given in clause 11.2 of [ITU-T G.709]. + +A logical lane marker recovery process is present per logical lane to recover the logical lane marker value. A new value of the logical lane marker is accepted when in five consecutive 16320-byte periods the same value is present in bits 7 and 8 of the MFAS byte, and the recovery process will enter the in-recovery (IR) state. In the IR state, recovery will be lost, and the out-of-recovery (OOR) state will be entered, when in each of five consecutive 16320-byte periods a value is received that is not the same as the accepted logical lane marker value. During an OOR period, the last accepted LLM value has to be maintained as a lane marker value. + +If the logical lane marker recovery process is in the out-of-recovery (OOR) state for 3 ms, LOR state shall be entered. LOR shall be left when the IR state persists continuously for 3 ms. + +The value of the logical lane marker is available after descrambling. + +Each of the four lanes shall have recovered a unique logical lane marker value in the range 0 to 3. + +If all four logical lanes have different values, the bytes of each logical lane shall be written into an elastic store with the indication of the start of the logical lane 16320-byte period boundary in line with the logical lane marker. + +If the bytes of the lane signals can be written consistently into the elastic store in the presence of a differential delay in line with the particular adaptation function without exceeding the buffering time, the in-multilane-alignment (ILA) state shall be entered. In this case, the differential delay can be compensated. + +If two or more logical lanes have the same logical lane marker value, or if one or more logical lane marker recovery processes are in the LOR state, or if the differential delay between two logical lanes exceeds the maximum delay that can be compensated in accordance to the related sink function, multilane alignment is not possible and the out-of-multilane-alignment (OLA) state is entered. + +#### 8.2.6.2 OTU4 multilane alignment + +The process has two sub-processes: + +- logical lane marker recovery (per lane); +- multilane alignment (composite signal). + +The logical lane marker signal is located in the LLM byte of the logical lane frame. + +A logical lane marker recovery process is present per logical lane to recover the logical lane marker value. A new value of the logical lane marker is accepted when in five consecutive 16320-byte periods the same value is present after modulo 20 operation of the LLM byte value, and the recovery process will enter the in-recovery (IR) state. In the IR state, recovery will be lost and the out-of-recovery + +(OOR) state be entered, when in each of five consecutive 16320-byte periods a value is received that is not the same as the accepted logical lane marker value. During an OOR period, the last accepted LLM value has to be maintained as lane marker value. + +If the logical lane marker recovery process is in the out-of-recovery (OOR) state for 3 ms, LOR state shall be entered. LOR shall be left when the IR state persists continuously for 3 ms. + +Each of the twenty logical lanes shall have recovered a unique logical lane marker value in the range 0 to 19. + +The process shall in addition decode the MFAS signal as coded in the 7th byte following the lane identification byte and identify the position of the virtual lane data in relation to the OTU4 multiframe. This position needs to be descrambled according to the scrambler defined in clause 11.2 of [ITU-T G.709]. + +If the lane identification and MFA identification for all lanes is detected consistently in line with the modulo 20 operation of the LLM byte position together with the MFA value, the data shall be written into the elastic store for realignment with the indication of the start of the logical lane 16320-byte period boundary in line with the logical lane marker. + +If the bytes of the logical lane signals can be written consistently into the elastic store in the presence of a differential delay in line with the particular adaptation function without exceeding the buffering time, the ILA state shall be entered. In this case the differential delay can be compensated. + +If two or more logical lanes have the same logical lane marker value, or if one or more logical lane marker recovery processes are in the LOR state, or if the differential delay between two logical lanes exceeds the maximum delay that can be compensated in accordance to the related sink function, multilane alignment is not possible and the out-of-multilane-alignment (OLA) state is entered. + +### 8.2.7 Block Synchronization + +#### 8.2.7.1 66B Block synchronization + +The process shall recover the 66b block from the payload bytes in the OPU frame through the 66b block synchronization lock state machine as described in Figure 82-12 of [IEEE 802.3]. The lock process looks for 64 consecutive valid sync headers in the initial data stream to declare lock. A valid sync header is either a 01 or a 10. Once in lock, the lock process looks for 65 invalid sync headers within a 1024 sync window to declare out of lock. An invalid sync header is a 11 or 00. In case the mapping procedure preserves the 2-bit alignment of each 66b block to the OPUflex payload boundary the SLIP step of the lock process may be optimized using 2-bit slips. + +### 8.2.8 Frame alignment for FlexO-*x* (*x* = 1, 2, 4) + +The FlexO-*x* frame alignment shall be found by searching for the alignment markers pattern (AM field) contained in the FlexO-*x* frame structure (see clauses 9.1.1, 9.1.3 and 9.1.5 of [ITU-T G.709.1]). + +The process has two states, out-of-frame (OOF) and in-frame (IF). + +In the OOF state, the alignment pattern searched for shall be the full set of the AM bits. The IF state shall be entered if this set is found and confirmed one frame period later. + +In the IF state, the frame alignment signal shall be continuously checked with the presumed frame start position. The framing pattern checked for shall be the first 40 bits of alignment pattern. The OOF state shall be entered if this subset is not found at the correct position within five consecutive frames. + +The frame start shall be maintained during the OOF state. + +### 8.2.9 Frame alignment for OTU25(u) or OTU50(u) + +The OTU25(u) or OTU50(u) frame alignment shall be found by searching for the framing pattern (OA1, OA2 FAS bytes). + +The process has two states, out-of-frame (OOF) and in-frame (IF). + +In the OOF state, the framing pattern searched for shall be the full set of the OA1 and OA2 bytes. The IF state shall be entered if this set is found and confirmed one frame period later. + +In the IF state, the frame alignment signal shall be continuously checked with the presumed frame start position. The framing pattern checked for shall be the OA1OA2 pattern (bytes 3 and 4 of the first row of the OTU25(u) or OTU50(u) frame structure). The OOF state shall be entered if this subset is not found at the correct position within five consecutive frames. + +The frame start shall be maintained during the OOF state. + +## **8.3 Signal quality supervision** + +### **8.3.1 Blank clause** + +NOTE – This clause is intentionally left blank. + +### **8.3.2 Blank clause** + +NOTE – This clause is intentionally left blank. + +### **8.3.3 Blank clause** + +NOTE – This clause is intentionally left blank. + +### **8.3.4 OTU, ODUT and ODUP signal quality supervision** + +A BIP-8 is used for each of these layers as defined in clause 15 of [ITU-T G.709]. + +#### **8.3.4.1 BIP-8 source processing** + +The BIP-8 shall be computed over the OPU area of the OTU frame (columns 15 to 3824). The computed BIP-8 is inserted in the BIP-8 byte position of the relevant overhead field of the 2nd following frame as shown in Figure 8-1. + +The OTUk/ODUk contains one instance of the OTU, ODU PM and ODU TCMi BIP-8 overhead fields. The OTUCn/ODUCn contains n instances of the OTU, ODU PM and ODU TCMi BIP-8 overhead fields, numbered 1 to n (BIP-8 #1 to BIP-8 #n). + +![Diagram illustrating BIP-8 source processing across three frames (Frame #i, Frame #i+1, Frame #i+2). It shows the OPU instance area (columns 15-3824) and the BIP-8 byte position (column 14). For Frame #i, the BIP-8 value is computed from the OPU instance. For Frame #i+1, the BIP-8 value is inserted into the frame. For Frame #i+2, the BIP-8 value is extracted from the frame. The diagram includes a 'Compute' block for Frame #i and an 'Insert' block for Frame #i+1.](c1df61cc3717e878a48e530218403403_img.jpg) + +The diagram shows three OTU frames: Frame #i, Frame #i+1, and Frame #i+2. Each frame has columns 1, ..., 14, 15, ..., 3824. Columns 15 to 3824 form the OPU instance. Column 14 contains the BIP-8 byte. In Frame #i, the BIP-8 value is computed from the OPU instance. In Frame #i+1, the BIP-8 value is inserted into the frame. In Frame #i+2, the BIP-8 value is extracted from the frame. The diagram includes a 'Compute' block for Frame #i and an 'Insert' block for Frame #i+1. + +Diagram illustrating BIP-8 source processing across three frames (Frame #i, Frame #i+1, Frame #i+2). It shows the OPU instance area (columns 15-3824) and the BIP-8 byte position (column 14). For Frame #i, the BIP-8 value is computed from the OPU instance. For Frame #i+1, the BIP-8 value is inserted into the frame. For Frame #i+2, the BIP-8 value is extracted from the frame. The diagram includes a 'Compute' block for Frame #i and an 'Insert' block for Frame #i+1. + +G.798(17)\_F8-1 + +**Figure 8-1 – BIP-8 source processing (SMOH used as example)** + +#### 8.3.4.2 BIP-8 sink processing + +The BIP-8 is computed over the OPU area of the OTU frame (columns 15 to 3824). The BIP-8 value generated by the TT\_So shall be extracted from the BIP-8 byte position of the relevant overhead field. The computed BIP-8 value of the 2nd preceding frame is compared with the BIP-8 value extracted from the current frame, as shown in Figure 8-2. Per OPU instance, if there is a mismatch between the two values, one near-end errored block is detected and the number of BIP violations (nBIPV) for that instance is forwarded to the companion TT\_So function. The near-end errored block (nN\_B) count is the sum of the errored blocks over all OPU instances. + +![Figure 8-2 – BIP-8 sink processing (SMOH used as example). The diagram illustrates the BIP-8 sink processing flow for multiple OPU instances. It shows the extraction of BIP-8 bytes from the payload, computation of BIP-8 values, XORing with the extracted bytes, and counting violations to identify errored blocks. The final output is the total number of errored blocks (nN_B).](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +The diagram shows the BIP-8 sink processing flow for multiple OPU instances (instance #1 to instance #n). The input consists of frames (Frame #i-2, Frame #i-1, Frame #i) with columns representing bytes (1, ..., 14, 15, ..., 3824). The payload area is labeled 'OPU instance #1' and 'OPU instance #n'. The processing steps are as follows: + +- Compute:** For each OPU instance, a BIP-8 value is computed from the payload. +- Extract:** The BIP-8 byte is extracted from the payload. +- XOR:** The extracted BIP-8 byte is XORed with the computed BIP-8 value. +- Number of BIP violations:** The result of the XOR operation is used to determine the number of BIP violations. +- ≥ 1:** If the number of BIP violations is greater than or equal to 1, it is an errored block. +- Σ:** The total number of errored blocks is summed across all OPU instances to produce the final output nN\_B. + +Reference: G.798(17)\_F8-2 + +Figure 8-2 – BIP-8 sink processing (SMOH used as example). The diagram illustrates the BIP-8 sink processing flow for multiple OPU instances. It shows the extraction of BIP-8 bytes from the payload, computation of BIP-8 values, XORing with the extracted bytes, and counting violations to identify errored blocks. The final output is the total number of errored blocks (nN\_B). + +Figure 8-2 – BIP-8 sink processing (SMOH used as example) + +## 8.4 Blank clause + +NOTE – This clause is intentionally left blank. + +## 8.5 Forward error correction (FEC) processing + +The FEC decoder shall report the number of corrected bits (nFECcorrErr). For further processing, see clause 6.5.1.3. + +### 8.5.1 No FEC + +The FEC encoder and decoder processes are null processes ignoring the FEC area and connecting their output signals to the corresponding input signals. + +### 8.5.2 RS(255,239,8) FEC for OTUk (k = 0, 1, 2, 3, 4) + +The RS(255,239,8) FEC algorithm is specified in Annex A of [ITU-T G.709]. + +Adaptation of the OTUk message data and FEC parity into the FEC frame is specified in Annex A of [ITU-T G.709]. + +The FEC encoder process shall generate the FEC code and insert it into the FEC area. + +The FEC decoder process shall extract the FEC data from the FEC area and perform error correction if FEC processing is enabled (i.e., FEC is mandatory or MI\_FECEn is true). Otherwise, if FEC is optional and MI\_FECEn is false, the FEC data is ignored, and no error correction is performed. The number of corrected bits shall be reported (nFECcorrErr). For further processing, see clause 6.5.1.3. + +### 8.5.3 Vendor-specific FEC for OTUk-v (k = 0, 1, 2, 3, 4) + +The FEC algorithm is vendor-specific. + +Adaptation of the OTUk message data and FEC parity into the FEC frame is specified in Annex A of [ITU-T G.709]. + +The FEC encoder process shall generate the FEC code and insert it into the FEC area. + +The FEC decoder process shall extract the FEC data from the FEC area and perform error correction if FEC processing is enabled (i.e., FEC is mandatory or MI\_FECEn is true). Otherwise, if FEC is optional and MI\_FECEn is false, the FEC data is ignored, and no error correction is performed. The number of corrected bits shall be reported (nFECcorrErr). For further processing, see clause 6.5.1.3. + +### **8.5.4 Staircase (SC) FEC for OTU4-SC and FlexO-*x*-SC (*x* = 1, 2, 4)** + +The SC FEC algorithm is specified in Annex A of [ITU-T G.709.2]. + +Adaptation of the OTU4-SC message data and FEC parity into the FEC frame is specified in Annex B of [ITU-T G.709.2]. Adaptation of the FlexO-1-SC message data and FEC parity into the FEC frame is specified in Annex B of [ITU-T G.709.3]. Adaptation of the FlexO-2-SC or FlexO-4-SC message data and FEC parity into the FEC frame is specified in Annex C of [ITU-T G.709.3]. + +The FEC encoder process shall generate the FEC code and insert it into the OTU4-SC or FlexO-*x*-SC FEC parity area. + +The FEC decoder process shall extract the FEC data from the FEC information and parity area and perform error correction. The number of corrected bits shall be reported (nFECcorrErr). For further processing, see clause 6.5.1.3. + +### **8.5.5 RS(544,514,10) FEC for FlexO-*x*-RS (*x* = 1, 2, 4)** + +The RS(544,514,10) FEC algorithm is specified in Annex A of [ITU-T G.709.1]. + +Adaptation of the FlexO-*x*-RS message data and FEC parity into the FEC frame is specified in clause 11.5 of [ITU-T G.709.1] for FlexO-1-RS, clause 12.5 of [ITU-T G.709.1] for FlexO-2-RS and clause 13.5 of [ITU-T G.709.1] for FlexO-4-RS. + +The FEC encoder process shall generate the FEC code and insert it into the FlexO-*x*-RS FEC area. + +The FEC decoder process shall extract the FEC data from the FEC area and perform error correction. The number of corrected bits shall be reported (nFECcorrErr). For further processing, see clause 6.5.1.3. + +### **8.5.6 RS(544,514,10) FEC for OTU*k*-RS (*k* = 25, 50u, 50)** + +The RS(544,514,10) FEC algorithm is specified in Annex A of [ITU-T G.709.4]. + +Adaptation of the OTU*k*-RS message data and FEC parity into the FEC frame is specified in clause 8.5 of [ITU-T G.709.4] for OTU25-RS and clause 9.5 of [ITU-T G.709.4] for OTU50(u)-RS. + +The FEC encoder process shall generate the FEC code and insert it into the OTU*k* FEC area. + +The FEC decoder process shall extract the FEC data from the FEC area and perform error correction if FEC processing is enabled (MI\_FECEn is true). Otherwise, the FEC data is ignored, and no error correction is performed. The number of corrected bits shall be reported (nFECcorrErr). For further processing, see clause 6.5.1.3. + +### **8.5.7 RS(528,514,10) FEC for OTU25u-RS** + +The RS(528,514,10) FEC algorithm is specified in Annex C of [ITU-T G.709.4]. + +Adaptation of the OTU25u message data and FEC parity into the FEC frame is specified in clause 8.5 of [ITU-T G.709.4]. + +The FEC encoder process shall generate the FEC code and insert it into the OTU*k* FEC area. + +The FEC decoder process shall extract the FEC data from the FEC area and perform error correction if FEC processing is enabled (MI\_FECEn is true). Otherwise, the FEC data is ignored, and no error correction is performed. The number of corrected bits shall be reported (nFECcorrErr). For further processing, see clause 6.5.1.3. + +### **8.5.8 Extended Hamming soft decision FEC for FlexO-*x*-DSH (*x* = 1, 2, 4)** + +The systematic (128,119) double-extended Hamming code algorithm for the FlexO-*x*-DSH is specified in clause 15.4.4 of [ITU-T G.709.3]. + +Adaptation of each 119-bit message data within the extended FlexO-*x*-SC FEC block group (FBG) structure and FEC parity into the 128-bit Hamming SD FEC blocks is specified in Annex D of [ITU-T G.709.3]. + +The FEC encoder process shall generate the FEC code and insert it into the FEC area. + +The soft decision FEC decoder process shall extract the FEC data from the FEC area and perform error correction. + +### **8.5.9 Extended BCH(256,239) soft decision OFEC code for FlexO-*x*-DO (*x* = 1, 2, 4)** + +The OFEC soft decision code algorithm for the FlexO-*x*-DO uses a spatially coupled TPC-like code with an extended BCH(256,239) constituent code as specified in clause 16.4.4 of [ITU-T G.709.3]. Adaptation of each message data within the OFBGz structure into the FEC codewords with parity bits is specified in clauses 16.4.3, 16.4.4 and Annex E of [ITU-T G.709.3]. + +The FEC encoder process shall generate the FEC code and insert it into the FEC area. + +The soft decision OFEC decoder process shall extract the FEC data from the FEC area and perform error correction (see Annex E of [ITU-T G.709.3]). The number of corrected bits shall be reported (nFECcorrErr). For further processing, see clause 6.5.1.3. + +## **8.6 Trail trace identifier (TTI) processing** + +On request via the management interface (MI\_GetAcTTI), the TTI shall be reported within 100 ms. It shall be an accepted TTI (AcTTI) instead of the received TTI (RxTTI). The acceptance process shall include a persistency check in order to avoid wrong/toggling TTI values during bit error conditions. + +For the TIM defect detection process, see clause 6.2.2.1. + +## **8.7 Payload structure indication (PSI) acceptance processes** + +### **8.7.1 Payload type (PT) acceptance process** + +#### **8.7.1.1 OPU PT** + +A new payload type is accepted (AcPT) if a new consistent value is received in the PSI[0] byte of the first instance of the OPU overhead in *X* consecutive multiframes. *X* shall be 3. + +#### **8.7.1.2 FlexO PT** + +A new payload type is accepted (AcPT) if a new value of the PT byte field of the FlexO overhead is received in an overhead frame with good CRC. + +### **8.7.2 Multiplex structure identifier (MSI) acceptance process** + +#### **8.7.2.1 ODUk multiplex structure identifier (MSI) acceptance process** + +The multiplex structure identifier (MSI) consists of 2, 4, 8, 16, 20, 32, 40 or 80 bytes, which are located in the multiframed PSI overhead as illustrated in Table 8-1. The MSI of an ODUk contains one byte per tributary slot. + +The MSI describes the allocation of tributary slots to ODTUs that contain the client ODUs. Each ODTU is identified by means of either a 2-tuple (*k* = 1, 2, 3), or (*k* = 4, 25u, 25, 50u, 50). + +An ODTU is carried in one or more tributary slots a, b, ..., n. The MSI byte(s) associated with this/those tributary slot(s) is/are configured with a common 2-tuple value in the adaptation source function. The value of these 2-tuples is the same for every MSI byte in this set. + +The adaptation sink function gets its ODTU to tributary slot allocation configured via the expected MSI (ExMSI) fields. The ExMSI fields with the same 2-tuple value specify in which tributary slots an ODTU is expected to be carried; e.g., A, B, ..., N ( $A < B < \dots < N$ ). + +A new multiplex structure identifier is accepted if a new consistent value is received in the MSI bytes of the PSI overhead for X consecutive multiframes. X shall be 3. + +**Table 8-1 – MSI bytes within PSI multiframe** + +| ODUk type | Payload type of tributary | Tributary slots | MSI bytes in PSI position range | +|-----------|---------------------------|-----------------|---------------------------------| +| ODU1 | 20 | TS[1..2] | PSI[2..3] | +| ODU2 | 20 | TS[1..4] | PSI[2..5] | +| ODU2 | 21 | TS[1..8] | PSI[2..9] | +| ODU3 | 20 | TS[1..16] | PSI[2..17] | +| ODU3 | 21 | TS[1..32] | PSI[2..33] | +| ODU4 | 21 | TS[1..80] | PSI[2..81] | +| ODU25(u) | 21 | TS[1..20] | PSI[2..21] | +| ODU50(u) | 21 | TS[1..40] | PSI[2..41] | + +For details on the ODUk MSI values, please refer to clause 19.4 of [ITU-T G.709]. + +#### 8.7.2.2 ODUCn multiplex structure identifier (MSI) acceptance process + +The ODUCn multiplex structure identifier (MSI) consists of 40 bytes per OPU instance, which are located in the PSI[2..41] bytes. The MSI of an ODUCn contains two bytes per tributary slot. + +A new multiplex structure identifier (AcMSI) for an OPU instance is accepted if a new consistent value is received in the MSI bytes of the PSI overhead of that OPU instance for 3 consecutive multi-frames. + +For details on the ODUCn MSI values, please refer to clause 20.4 of [ITU-T G.709]. + +#### 8.7.2.3 OMS-O multiplex structure identifier (MSI) acceptance process + +The format of the OMS-O MSI and the process for accepting a new value of the MSI are implementation specific. + +#### 8.7.2.4 FlexO multiplex structure identifier (MSI) acceptance process + +The multiplex structure identifier (MSI) of the n FlexO instances in a FlexO group consists of one byte per FlexO instance. + +A new multiplex structure identifier (AcMSI) for a FlexO instance is accepted if a new value of the MSI byte field of that FlexO instance is received in an overhead frame with good CRC. + +For details on the FlexO MSI values, please refer to clause F.3.1 of [ITU-T G.709.3]. + +### 8.7.3 Blank clause + +NOTE – This clause is intentionally left blank. + +## 8.8 Status information (STAT) acceptance process + +A new STAT value (AcSTAT) is accepted if a new consistent value is received in the STAT bits in the first OTU or ODU overhead instance in $X$ consecutive frames. For ODUk $X$ shall be 3; for OTUCn and ODUCn $X$ shall be 15. + +## 8.9 Generic AIS generation and detection + +Generic AIS including OTUk-AIS ( $k = 1, 2, 3$ ) is a PN-11 pseudo-random pattern as defined in [ITU-T G.709]. The pattern is generated by a pseudo-random generator. For the detection of generic AIS, the reverse process as shown in Figure 8-3 is used. As the flip-flops of the detector circuit are fed with the same data as the flip-flops of the generator circuit, data at point D1 is the same as data at G1 with a delay of 11 clock cycles. As the G1 data appears at the output of the generator ( $G_{out}$ ) and as such also at the input of the detector ( $D_{in}$ ) with a delay of 11 clock cycles, D1 and $D_{in}$ data is the same for each clock cycle. A PN-11 generic AIS pattern at the input of the detector ( $D_{in}$ ) should therefore result in an all-ZEROs pattern at point D2. The only other input pattern that will result in an all-ZEROs pattern at D2 is an all-ZEROs input pattern. + +The detection of an all-ZEROs pattern at D2 and a non-all-ZEROs pattern at $D_{in}$ is a criterion for the generic AIS defect. For the specific detection process, see clause 6.2.6.3.3. + +![Figure 8-3: Generic AIS generation and detection diagram. The top part shows a 'Generic AIS generator' with 11 D flip-flops (DQ) in series, clocked by 'Clock'. The output of the 11th flip-flop is labeled 'Gout' and 'Generic AIS'. This output is fed back through an XOR gate labeled 'G1' to the input of the first flip-flop. The bottom part shows a 'Generic AIS detector' with 11 D flip-flops (DQ) in series, also clocked by 'Clock'. The input is labeled 'Din'. The output of the 11th flip-flop is labeled 'D1'. 'Din' is also labeled at the input of the first flip-flop. Both 'D1' and 'Din' are inputs to an XOR gate labeled 'D2'. The output of 'D2' is fed into two parallel blocks: 'Non all ZEROs detection' and 'All ZEROs detection'. The outputs of these blocks are combined via an AND gate to produce the final output 'dAIS'. A small text 'G.798(17)-Cor.2(21)_F8-3' is in the bottom right corner.](aeb2a26a07219661191294dba528067a_img.jpg) + +Figure 8-3: Generic AIS generation and detection diagram. The top part shows a 'Generic AIS generator' with 11 D flip-flops (DQ) in series, clocked by 'Clock'. The output of the 11th flip-flop is labeled 'Gout' and 'Generic AIS'. This output is fed back through an XOR gate labeled 'G1' to the input of the first flip-flop. The bottom part shows a 'Generic AIS detector' with 11 D flip-flops (DQ) in series, also clocked by 'Clock'. The input is labeled 'Din'. The output of the 11th flip-flop is labeled 'D1'. 'Din' is also labeled at the input of the first flip-flop. Both 'D1' and 'Din' are inputs to an XOR gate labeled 'D2'. The output of 'D2' is fed into two parallel blocks: 'Non all ZEROs detection' and 'All ZEROs detection'. The outputs of these blocks are combined via an AND gate to produce the final output 'dAIS'. A small text 'G.798(17)-Cor.2(21)\_F8-3' is in the bottom right corner. + +**Figure 8-3 – Generic AIS generation and detection** + +## 8.10 Generic layer fault processing + +Layer fault processing is concerned with the detection of failures within a layer network, the generation of consequent actions (for suppression of unwanted downstream alarms and remote information for upstream single-ended maintenance), and the report of probable fault causes to the management system. + +Figure 8-4 illustrates in general the atomic functions connection, trail termination and adaptation of a layer which perform their specific fault-processing tasks. The connection function, if present, can interconnect the adaptation and trail termination functions according to the signal flow shown. Note that not all features are supported by all layers. For the specific fault processing, see the layer-specific functions. + +![Figure 8-4 – Generic layer fault processing diagram showing the flow of fault signals (SSF, FDI, AIS, LCK, IAE, PMI, BDI, BIAE) through various layers (Adaptation, Trail Termination, Connection) and components (Supervision process, Client-specific processes, Server-specific processes).](4162c218fc7881cd90fc9574e07d2327_img.jpg) + +The diagram illustrates the generic layer fault processing flow across four layers: Adaptation, Trail Termination, Connection, and another Adaptation layer. + +- Top Adaptation Layer:** + - Sink side (left):** Receives SSF from the layer below. It contains FDI AIS and LCK blocks, and two Supervision process blocks. Reports are sent from the supervision processes. It connects to the Trail Termination layer via TSF and TSD. + - Source side (right):** Receives input from above and contains LCK and IAE blocks. It connects to the Trail Termination layer via Source. + - Internal components:** Client-specific processes and Server-specific processes are shown between the supervision and adaptation blocks. +- Trail Termination Layer:** + - Sink side (left):** Receives from the Adaptation layer sink. It contains a Supervision process block that sends Reports and provides Remote information to the source side. It connects to the Connection layer via Sink. + - Source side (right):** Receives from the Adaptation layer source. It contains PMI, BDI, and BIAE blocks. It connects to the Connection layer via Source. +- Connection Layer:** + - Contains an OCI block. Arrows show the flow of signals between the Trail Termination layer and the bottom Adaptation layer. A dashed line labeled "No SSF" is also shown within this layer. +- Bottom Adaptation Layer:** + - Sink side (left):** Receives from the Connection layer. It contains FDI AIS and LCK blocks, and two Supervision process blocks. Reports are sent from the supervision processes. It connects to the layer below via TSF and TSD. + - Source side (right):** Receives from the Connection layer and contains LCK and IAE blocks. It connects to the layer below via Source. + - Internal components:** Client-specific processes and Server-specific processes are shown between the supervision and adaptation blocks. + +G.798(10)\_F8-4 + +Figure 8-4 – Generic layer fault processing diagram showing the flow of fault signals (SSF, FDI, AIS, LCK, IAE, PMI, BDI, BIAE) through various layers (Adaptation, Trail Termination, Connection) and components (Supervision process, Client-specific processes, Server-specific processes). + +**Figure 8-4 – Generic layer fault processing** + +In the sink direction, every layer receives a server signal fail indication (SSF) from its server layer, performs supervision of parameters pertaining to the layer, and generates a server signal fail indication to its client layer. In the optical layers, the payload and the overhead are separated; the monitoring for LOS is performed by the media element, while all other defect processing functions are performed by maintenance entity trail terminations that use non-associated overhead. Reports of probable fault causes are made to the management system. The signal fail state of the layer is forwarded/indicated via a forward defect indication (FDI) or an alarm indication signal (AIS). AIS is the term used when the signal is in the digital domain (ODU and OTU layer). FDI is the term used when the signal is in the optical domain; FDI is transported as a non-associated overhead in the OSC. + +The LCK maintenance signal is generated on the operator request in order to lock the signal from user access while the operator is, for example, performing set-up tests. In this case, the client signal is replaced by fixed data indicated as locked (LCK). It can be generated by the server layer adaptation sink and source functions. + +An open connection of a connection function generates the OCI maintenance signal in conjunction with a no SSF indication. + +The optical parameter monitors (OPM) in the media element monitor the optical payload signal to determine when the incoming signal is absent and relay this information to the OTS-O or OMS-O trail termination functions. Upon receiving the information that the incoming payload signal is absent (see Figure 8-5) this function inserts the payload missing indication (PMI) into the appropriate portion of the OSC. At the OTS-O or OMS-O trail termination sink, it is used to suppress the loss of payload signal defect-related actions (consequent actions, fault cause, PM data). + +![Diagram illustrating PMI processing. A 'Missing optical signal' enters the first 'Media element'. This element sends a 'LOS indication' to an 'OTS-O' block, which 'Inserts PMI in OSC'. The 'Media element' also outputs a signal to a second 'Media element', which is labeled 'LOS detected'. This second element sends its own 'LOS indication' to another 'OTS-O' block. The 'PMI' signal is shown being transmitted between the two 'OTS-O' blocks. The second 'OTS-O' block performs 'Hold off dLOS-P detection' and 'PMI suppresses actions related to dLOS-P'. The diagram is labeled G.798(17)_F8-5.](640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg) + +Diagram illustrating PMI processing. A 'Missing optical signal' enters the first 'Media element'. This element sends a 'LOS indication' to an 'OTS-O' block, which 'Inserts PMI in OSC'. The 'Media element' also outputs a signal to a second 'Media element', which is labeled 'LOS detected'. This second element sends its own 'LOS indication' to another 'OTS-O' block. The 'PMI' signal is shown being transmitted between the two 'OTS-O' blocks. The second 'OTS-O' block performs 'Hold off dLOS-P detection' and 'PMI suppresses actions related to dLOS-P'. The diagram is labeled G.798(17)\_F8-5. + +**Figure 8-5 – PMI processing** + +NOTE 1 – A hold-off time to delay detection of dLOS-P has to be used at the trail termination sink functions to allow for the activation of the payload missing indication. The hold-off time has to cover the propagation, processing and detection delay of the PMI signal between the source and sink. + +In digital layers (ODU, OTU), the maintenance signals (ODU-AIS, ODU-LCK, and ODU-OCI) provide a replacement of the layer characteristic information except some OH as defined in [ITU-T G.709]. In the optical layers, the maintenance signals FDI and OCI consist only of overhead transported as non-associated overhead in the OSC. + +The trail termination sink function detects trail-specific defects (continuity, connectivity and maintenance signals). It correlates the defects and incoming SSF in order to determine the probable cause in failure reports. It activates trail signal fail (TSF) and trail signal degraded (TSD) indication towards the layer adaptation sink function on these defects and triggers the insertion of backward defect indications (BDI) at the trail termination source of upstream direction. Similarly, the adaptation sink function combines the result of its measurements with the TSF indication to generate the SSF indication, forwards TSD as SSD, and presents appropriate failure reports to the layer manager. These processes aim to present only probable causes pertaining to maintenance actions required at that layer, i.e., to perform suitable alarm suppression. + +The adaptation function is split into server (common) and client-specific supervision processes. The common supervision applies to the compound signal and checks for the correct payload structure on ODUP. The client-specific supervision performs alignment supervision. Note that several client signals may be transported by the same server signal. + +The adaptation source function of the OTU layer and ODU TCM sub-layers generates an incoming alignment error (IAE), if it detects a frame slip (see Figure 8-6). At the trail termination sink function, the IAE information is detected and is used to suppress near-end and far-end performance monitoring data (DS and EBC) and DEG defect data. Furthermore, the collocated trail termination source will insert in upstream the BIAE in order to suppress the far-end performance monitoring data (DS and EBC) at the remote end. + +NOTE 2 – Suppression of the performance monitoring data is performed in the equipment management function. + +![Figure 8-6 – IAE processing diagram. This diagram illustrates the In-Service Alarm End (IAE) processing in an optical transport network. It shows four ODUkTm (Optical Data Unit k Tributary Module) blocks arranged in a 2x2 grid. The top-left block has an input labeled 'Frame slip' and an output labeled 'Near-/far-end DS/EBC suppressed by IAE'. The top-right block has an input labeled 'Near-/far-end DS/EBC suppressed by IAE' and an output labeled 'Frame slip'. The bottom-left block has an input labeled 'Far-end DS/EBC suppressed by BIAE' and an output labeled 'Far-end DS/EBC suppressed by BIAE'. The bottom-right block has an input labeled 'Far-end DS/EBC suppressed by BIAE' and an output labeled 'Near-/far-end DS/EBC suppressed by IAE'. Red dashed lines represent the IAE and BIAE signals. The top-left and top-right blocks are connected by a horizontal red dashed line labeled 'IAE'. The bottom-left and bottom-right blocks are connected by a horizontal red dashed line labeled 'BIAE'. The top-left and bottom-left blocks are connected by a vertical red dashed line labeled 'IAE'. The top-right and bottom-right blocks are connected by a vertical red dashed line labeled 'BIAE'. The text 'G.798(10)_F8-6' is located in the bottom right corner of the diagram.](89f8aefc01866631793087542316cef2_img.jpg) + +Figure 8-6 – IAE processing diagram. This diagram illustrates the In-Service Alarm End (IAE) processing in an optical transport network. It shows four ODUkTm (Optical Data Unit k Tributary Module) blocks arranged in a 2x2 grid. The top-left block has an input labeled 'Frame slip' and an output labeled 'Near-/far-end DS/EBC suppressed by IAE'. The top-right block has an input labeled 'Near-/far-end DS/EBC suppressed by IAE' and an output labeled 'Frame slip'. The bottom-left block has an input labeled 'Far-end DS/EBC suppressed by BIAE' and an output labeled 'Far-end DS/EBC suppressed by BIAE'. The bottom-right block has an input labeled 'Far-end DS/EBC suppressed by BIAE' and an output labeled 'Near-/far-end DS/EBC suppressed by IAE'. Red dashed lines represent the IAE and BIAE signals. The top-left and top-right blocks are connected by a horizontal red dashed line labeled 'IAE'. The bottom-left and bottom-right blocks are connected by a horizontal red dashed line labeled 'BIAE'. The top-left and bottom-left blocks are connected by a vertical red dashed line labeled 'IAE'. The top-right and bottom-right blocks are connected by a vertical red dashed line labeled 'BIAE'. The text 'G.798(10)\_F8-6' is located in the bottom right corner of the diagram. + +**Figure 8-6 – IAE processing** + +In the optical layer, the media operates independently of the OTS-O, OMS-O, OCh-O and OTSiG-O overhead layers that are superimposed upon the media. This independence results in the need for separate SSF, TSF, FDI and BDI signals for the payload and the overhead (all of which are carried in the overhead channel since the media is not capable of inserting maintenance signalling). + +NOTE 3 – If a SSF input is not connected to any output, it is considered as a no SSF. + +## 8.11 OTSi modulator and demodulator processes + +Specific parameters of the OTSi modulator and demodulator processes depend on the interface type. Refer to [ITU-T G.959.1], [ITU-T G.694.2], [ITU-T G.696.1], [ITU-T G.695], [ITU-T G.698.1], [ITU-T G.698.2] and [ITU-T G.694.1] for the currently standardized OTN interfaces and central frequencies. The parameters are managed, if applicable, by the MI\_nominalCentralFrequencyOrWavelength (both input and output), MI\_selectedApplicationIdentifier, and MI\_supportableApplicationIdentifierList management interfaces. + +![Figure 8-7 – OTSi modulator and demodulator processes diagram. This diagram shows a vertical stack of three components. At the top is 'OTSi_AP', connected by a double-headed vertical arrow to a central block labeled 'OTSi'. Below the 'OTSi' block is another double-headed vertical arrow connecting it to 'OTSi_CP'. The text 'G.798(17)_F8-7' is located at the bottom right of the diagram.](21327313f7b18a481da0c87a6472a80d_img.jpg) + +Figure 8-7 – OTSi modulator and demodulator processes diagram. This diagram shows a vertical stack of three components. At the top is 'OTSi\_AP', connected by a double-headed vertical arrow to a central block labeled 'OTSi'. Below the 'OTSi' block is another double-headed vertical arrow connecting it to 'OTSi\_CP'. The text 'G.798(17)\_F8-7' is located at the bottom right of the diagram. + +**Figure 8-7 – OTSi modulator and demodulator processes** + +**Optical carrier modulation (Mod):** This process performs modulation of an optical carrier with the payload (PLD) signal by means of a defined modulation scheme. The modulation scheme and optical parameters (e.g., operating wavelength) depend on the specific interface type. + +**Optical carrier demodulation (DMod):** This process demodulates the PLD signal from the optical carrier. The modulation scheme depends on the specific interface type. + +## 8.12 FlexO maintenance signal information (MAINT) acceptance process + +A new MAINT value (AcMAINT) is accepted if a new value of the FlexO Maintenance Signal Identification field of the FlexO overhead is received in an overhead frame with good CRC. + +## 8.13 FlexO instance signals interleaving processes + +### 8.13.1 $x$ FlexO instance signals interleaving to FlexO- $x$ ( $x = 1, 2, 4$ ) + +The function shall interleave the $x$ FlexO instance signals, 10-bit at a time and in a round-robin fashion from FlexO- $x\_CI\_D[1]$ to FlexO- $x\_CI\_D[x]$ into a FlexO- $x$ frame as described in clauses 11.1, 12.1 or 13.1 of [ITU-T G.709.1] for 100G FlexO-1, 200G FlexO-2, or 400G FlexO-4, respectively. + +NOTE – The $x$ FlexO instances are interleaved in ascending FlexO instance identification (IID) value, so that after interleaving, the first 10-bit block in the FlexO- $x$ frame belong to the FlexO instance with lowest IID value and the last 10-bit block in the FlexO- $x$ frame belong to the FlexO instance with highest IID value. + +### 8.13.2 FlexO- $x$ de-interleaving to $x$ FlexO instance signals ( $x = 1, 2, 4$ ) + +The function shall 10-bit de-interleave the FlexO- $x$ frame into $x$ FlexO instance signals as described in clauses 11.1, 12.1 or 13.1 of [ITU-T G.709.1] for 100G FlexO-1, 200G FlexO-2, or 400G FlexO-4, respectively. The de-interleaving process is initiated by the FlexO- $x$ frame start and round-robin, so that the first FlexO instance (with lowest FlexO IID) is output towards FlexO- $x\_CI\_D[1]$ and the last FlexO instance (with highest FlexO IID value) is output towards FlexO- $x\_CI\_D[x]$ . + +## 8.14 FlexOsec processing for encryption and authentication of fixed-length FlexO frame structures + +The FlexOsec encryption and authentication processes are performed per individual FlexO instance frame signal. + +### 8.14.1 FlexOsec source processing + +A process diagram for the FlexOsec source processes per FlexO instance signal is shown in Figure 8-8. + +![Figure 8-8 – FlexOsec source processes (per FlexO instance signal). The diagram shows the flow of data and control signals through various processing blocks. Inputs include FS (Frame Synchronization), D (Data), and CK (Cipher Key). The 'FlexOsec MF generator' takes FS and CK to produce SMFS. 'Insert CST' and 'Insert KI' take FS and CK to produce intermediate signals. 'Process KI' takes SMFS and SKI_KI to produce TxKI. 'Generate/insert FN' takes FN, FS, and SMFS to produce FN. 'Generate IV' takes IV and SKI_IV_Fixed_ID to produce IV. All these signals (TxKI, FN, IV, and SKI_key[0, 1, 2, 3]) are inputs to the 'Encryption and authentication processes' block, which outputs AT (ICV). Finally, 'Insert AT' takes AT (ICV) and FS to produce the final output D_SEC.](cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg) + +Figure 8-8 – FlexOsec source processes (per FlexO instance signal). The diagram shows the flow of data and control signals through various processing blocks. Inputs include FS (Frame Synchronization), D (Data), and CK (Cipher Key). The 'FlexOsec MF generator' takes FS and CK to produce SMFS. 'Insert CST' and 'Insert KI' take FS and CK to produce intermediate signals. 'Process KI' takes SMFS and SKI\_KI to produce TxKI. 'Generate/insert FN' takes FN, FS, and SMFS to produce FN. 'Generate IV' takes IV and SKI\_IV\_Fixed\_ID to produce IV. All these signals (TxKI, FN, IV, and SKI\_key[0, 1, 2, 3]) are inputs to the 'Encryption and authentication processes' block, which outputs AT (ICV). Finally, 'Insert AT' takes AT (ICV) and FS to produce the final output D\_SEC. + +**Figure 8-8 – FlexOsec source processes (per FlexO instance signal)** + +**Generic processes:** These generic processes are common to any type of cipher suite type code. + +- **FlexOsec MF generator:** The function shall generate 4-frame FlexOsec multi-frame starter identifier (SMFS) as described in clause 9.3.2.2 of [ITU-T G.709.1]. +- **Insert CST:** The function shall insert the appropriate cipher suite type code (corresponding to the specific FlexOsec encryption and authentication processes) into the cipher suite type (CST) byte position of the FlexOsec overhead in the extended overhead area, as defined in clause 9.3.2.4 and Table 9-6 of [ITU-T G.709.1]. +- **Process KI:** The function shall generate the 2-bit transmit key index value (TxKI) by sampling SKI\_KI 2-bit input value using the 4-frame FlexOsec multi-frame starter identifier (SMFS). It guarantees that TxKI is stable across that multi-frame, as defined in clause 9.3.2.3 of [ITU-T G.709.1]. TxKI is sampled again by SMFS to generate the 2-bit Key Index (KI) towards the encryption and authentication processes in order to select the current key among four possible keys. When it detects an increment of the TxKI value, this function triggers a key switching event at the next SMFS (i.e., next 4-frame FlexOsec multiframe boundary). +NOTE – The transmit KI value (TxKI) inserted in the current 4-frame FlexOsec multi-frame carries the Key Index (KI) value used by the encryption and authentication processes in the next 4-frame FlexOsec multi-frame. +- **Insert KI:** The function shall insert TxKI transmit key index value into the 2-bit KI field position of the FlexOsec overhead in the extended overhead area, as defined in clause 9.3.2.3 of [ITU-T G.709.1]. +- **Generate & Insert FN:** The function shall generate and insert the 64-bit frame number into the frame number (FN) field of the FlexOsec overhead in the extended overhead area, as defined in clause 9.3.2.2 of [ITU-T G.709.1]. FN is incremented every FlexO frame and the 4-frame FlexOsec multi-frame starter identifier corresponds to FN[63,64] = 00. FN is reset to zero when a key switching event is detected by KI process. + +- **Insert AT:** The function shall insert the 16-byte authentication tag resulting from the current FlexO frame specific authentication process (see clause 8.14.3) into the AT field of the FlexOsec overhead in the next FlexO frame extended overhead area, as defined in clause 9.3.2.1 of [ITU-T G.709.1]. + +**Specific processes:** These specific processes depend on the specific cipher suite type code. + +- **Generate IV:** See clause 8.14.3 for the encryption process with the cipher suite type code corresponding to the transmit CST value. +- **Encryption and authentication processes:** See clause 8.14.3 with the cipher suite type code corresponding to the transmit CST value. + +### 8.14.2 FlexOsec sink processing + +A process diagram for the FlexOsec sink processes per FlexO instance signal is shown in Figure 8-9. + +![Figure 8-9 – FlexOsec sink processes (per FlexO instance signal). This block diagram illustrates the data flow and processing steps for FlexOsec sink operations. At the top, a 'Selector' block receives inputs CK, FS, and D, and outputs MI_SquelchEn. Below it, a 'Squelch process' block contains 'Normal' and 'Delay buffer' sub-blocks, receiving CK, FS, and D, and outputting SquelchText and AuthCheckErr. A 'FlexOsec OH replace' block receives CK, FS, and D, and outputs CK, FS, and D. Below that, an 'Extract AT' block receives CK, FS, and D, and outputs RxAT. A 'Compare' block receives RxAT and AT (ICV), and outputs AuthCheckErr. A large 'Encryption and authentication processes' block receives CK, FS, and D, and outputs SKI_key[0, 1, 2, 3]. Below this, a 'Generate IV' block receives IV and outputs SKI_IV_Fixed_ID and SKI_KI. An 'Extract KI' block receives CK, FS, and D, and outputs RxKI. An 'Extract FN' block receives CK, FS, and D, and outputs TxFN. An 'Extract and process CST' block receives CK, FS, and D, and outputs AcCST. A central 'FN, KI lock and anti-replay process' block receives FN, KI, and FS, and outputs AuthCheckErr, dUnlockSec, and TSF (e.g., dLOL or (dLOF)). At the bottom, the final outputs are CK, FS, and D_SEC. The diagram is labeled G.798(17)-Amd.4(22)_F8-9.](1033dc9fde75540d224c907681b1b7aa_img.jpg) + +Figure 8-9 – FlexOsec sink processes (per FlexO instance signal). This block diagram illustrates the data flow and processing steps for FlexOsec sink operations. At the top, a 'Selector' block receives inputs CK, FS, and D, and outputs MI\_SquelchEn. Below it, a 'Squelch process' block contains 'Normal' and 'Delay buffer' sub-blocks, receiving CK, FS, and D, and outputting SquelchText and AuthCheckErr. A 'FlexOsec OH replace' block receives CK, FS, and D, and outputs CK, FS, and D. Below that, an 'Extract AT' block receives CK, FS, and D, and outputs RxAT. A 'Compare' block receives RxAT and AT (ICV), and outputs AuthCheckErr. A large 'Encryption and authentication processes' block receives CK, FS, and D, and outputs SKI\_key[0, 1, 2, 3]. Below this, a 'Generate IV' block receives IV and outputs SKI\_IV\_Fixed\_ID and SKI\_KI. An 'Extract KI' block receives CK, FS, and D, and outputs RxKI. An 'Extract FN' block receives CK, FS, and D, and outputs TxFN. An 'Extract and process CST' block receives CK, FS, and D, and outputs AcCST. A central 'FN, KI lock and anti-replay process' block receives FN, KI, and FS, and outputs AuthCheckErr, dUnlockSec, and TSF (e.g., dLOL or (dLOF)). At the bottom, the final outputs are CK, FS, and D\_SEC. The diagram is labeled G.798(17)-Amd.4(22)\_F8-9. + +**Figure 8-9 – FlexOsec sink processes (per FlexO instance signal)** + +**Generic processes:** These generic processes are common to any type of cipher suite type code. + +- **Extract & process CST:** The cipher suite type code is extracted from the CST byte position of the FlexOsec overhead in the FlexO frame extended overhead area, as defined in clause 9.3.2.4 of [ITU-T G.709.1]. A new CST value (AcCST) is accepted if a new consistent value is received in the CST in X consecutive frames. X shall be 15. +- **Extract KI:** The receive key index value (RxKI) is extracted from the 2-bit KI field position of the FlexOsec overhead in the FlexO frame extended overhead area, as defined in clause 9.3.2.3 of [ITU-T G.709.1]. +- **Extract FN:** The receive 64-bit frame number (RxFN) is extracted from the FN field of the FlexOsec overhead in the FlexO frame extended overhead area, as defined in clause 9.3.2.2 of [ITU-T G.709.1]. +- **FN, KI, lock & anti-replay process:** The process has three states, out-of-lock (OOL), pre-lock (PL), and in-lock (IL). + +In the OOL state, the authentication check failure (AuthCheckErr) is ignored, and the local FN 64-bit counter value is not incremented. A valid FlexOsec 4-frame multiframe is detected if an error-free multiframe sequence is found in the two LSBs of the extracted FN value from the receive FlexO frame, RxFN[63,64]. A new KI value (AcKI) is accepted during a valid FlexOsec 4-frame multiframe using a three out of four majority decision. To support anti-replay, the PL state shall be entered at the beginning of the FlexO frame following a valid FlexOsec multiframe, if the 64-bit RxFN value is greater than the local FN counter value or a new KI value (different from the prior one) has been accepted. + +In the PL state, the specific IV generation, decryption and authentication processes are performed over the current FlexO frame using the AcKI value from the prior FlexOsec 4-frame multiframe as KI and the RxFN value as FN, and per the specific and expected cipher suite type code processing (see clause 8.14.3). If the FlexO frame authentication passes (AuthCheckErr= 0) and an increment of the RxFN value is detected in the next FlexO frame, then the IL state shall be entered, the AcKI value is maintained, and the local FN counter is loaded with that RxFN value from the next FlexO frame. Otherwise, if authentication has failed (AuthCheckErr= 1) or no RxFN value increment is detected in the next FlexO frame, then the OOL state shall be re-entered. + +In the IL state, the local FN counter value increments every FlexO frame and is used as the FN value of the current FlexO frame for the specific IV generation, decryption and authentication processes (see clause 8.14), as well as to identify FlexOsec 4-frame multiframe boundaries. A new 2-bit KI value (AcKI) is accepted during a FlexOsec 4-frame multiframe using a three out of four majority decision of RxKI values extracted from at least three FlexO frames passing authentication. AcKI is used as the KI value over the next four FlexO frames (i.e., during next FlexOsec 4-frame multiframe) for the specific decryption and authentication processes (see clause 8.14). When an increment of AcKI is detected, it corresponds to a key switching event and the local FN counter is reset to value zero at the next FlexO frame boundary. The out-of-lock state is entered if authentication has failed (AuthCheckErr=1) in X consecutive frames or the RxFN value does not match with the local FN counter value (its expected value) in X consecutive frames passing authentication. X shall be 5. + +The OOL state shall be entered during TSF or when a loss of FlexO-x alignment is detected (e.g., dLOL or dLOF) within the specific atomic functions (see clause 16). + +The local FN 64-bit counter is set to the default value 0 (using MI\_ClearFNCounter) when a FlexOsec secure communication link is initially set-up by the EMF. + +NOTE – A detected key switching event triggers the generate IV, authentication and decryption processes to use a new cryptographic key corresponding to the newly accepted AcKI value, at the next FlexOsec 4-frame multiframe boundary. It is then expected that the old cryptographic key value (i.e., corresponding to prior AcKI value) is retired and not anymore selectable by these processes. + +- **Extract and process AT:** The receive 16-byte authentication tag (RxAT) is extracted from the AT field of the FlexOsec overhead in the current FlexO frame extended overhead area, as defined in clause 9.3.2.1 of [ITU-T G.709.1]. This extracted RxAT value is then compared with the 16-byte computed authentication tag (AT) resulting from the prior FlexO frame receive authentication specific process using the configured cipher suite type code (see clause 8.14.3). If there is a mismatch between the two values, one authentication failure is detected and reported (AuthChekErr). + - **FlexOsec OH replace:** After decryption and AT extraction, the 32-byte receive FlexOsec overhead is replaced with all-ZEROs in the FlexO frame extended overhead area. + - **Squelch process:** If the squelch processing is enabled (MI\_SquelchEn is true), the FlexO frame is buffered after decryption and authentication process, and after FlexOsec OH replacement. If this FlexO frame has failed authentication check (AuthChekErr is ONE), then the fields covered by authentication within its payload and overhead area are replaced with a repeating SquelchText = 0x04 byte pattern, as defined in clause 8.14.3 for the specific cipher suite type code in use (i.e., corresponding to the expected CST value). Squelching could be disabled (MI\_SquelchEn is false) to lower the receive latency, in which case the entire squelch process (including the FlexO frame buffer) is bypassed. +- Specific processes:** These specific processes depend on the specific cipher suite type code. +- **Generate IV:** See clause 8.14.3 for the decryption process using a specific cipher suite type code (i.e., corresponding to the expected CST value). + - **Decryption and authentication processes:** See clause 8.14.3 for the specific cipher suite type code in use (i.e., corresponding to the expected CST value). If an authentication failure is detected (AuthChekErr = 1) is detected + +### 8.14.3 FlexOsec encryption and authentication processes + +The receive authentication check shall report the per FlexO frame authentication failure (AuthCheckErr). For further processing, see clause 6.5.1.4. + +#### 8.14.3.1 GCM-AES-256 FlexOsec without OH encryption + +The GCM-AES-256 FlexOsec payload encryption algorithm with basic overhead area (BOH) and partial extended overhead area (EOH) authentication is specified in clause B.1 of [ITU-T G.709.1]. It corresponds to the cipher suite type (CST) code point value 000001, as defined in Table 9-6 of [ITU-T G.709.1]. + +The key is selected among four 256-bit key values SKI\_Key[0,1,2,3] input from the key exchange and agreement functions, using the 2-bit key index value (KI). For encryption at the source, KI is generated as described in clause 8.14.1. For decryption at the sink, KI is accepted from the incoming FlexOsec overhead as described in clause 8.14.2. + +The 96-bit initialization vector (IV) is generated on a FlexO frame-by-frame basis per clause B.1.3 of [ITU-T G.709.1] using a user configurable 32-bit fixed identifier SKI\_IV\_fixed\_ID from the key exchange and agreement functions, and the 64-bit Frame Number (FN) of that FlexO frame (See clause 8.14.1). For encryption at the source, FN is generated as described in clause 8.14.1. For decryption at the sink, FN is accepted and regenerated from the incoming FlexOsec overhead as described in clause 8.14.2. + +The encryption process is performed at the source for each transmitted FlexO frame using its payload area as PlainText, its generated IV and the selected Key, to replace the PlainText with CipherText. The authentication process is performed in parallel over that encrypted FlexO frame payload area, and its basic overhead (BOH) area plus a subset of its extended overhead (EOH) area as additional authenticated data, to create a 16-byte authentication tag (i.e., integrity check vector). + +The decryption process is performed at the sink for each received FlexO frame using its payload area as CipherText, its generated IV and the selected Key, to replace the CipherText with PlainText. The authentication process is performed in parallel over that received FlexO frame payload area, and its basic overhead (BOH) area plus a subset of its extended overhead (EOH) area as additional authenticated data, to regenerate a 16-byte authentication tag (i.e., integrity check vector). + +# 9 OTS-O layer functions + +Figure 9-1 illustrates the OTS-O layer network and client layer adaptation functions. The information crossing the OTS-O termination connection point (OTS-O\_TCP) is referred to as the OTS-O characteristic information (OTS-O\_CI). The information crossing the OTS-O access point (OTS-O\_AP) is referred to as the OTS-O adapted information (OTS-O\_AI). + +![Diagram of OTS-O layer network and client layer adaptation functions showing the hierarchy from OMS-O_CP down to OTS-O_TCP.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +The diagram illustrates the OTS-O layer hierarchy. At the top is OMS-O\_CP, which connects via a double-headed arrow to a trapezoidal block labeled OTS-O/OMS-O. Below this block is OTS-O\_AP, which connects via a double-headed arrow to a triangular block labeled OTS-O. At the bottom of the triangle is OTS-O\_TCP, which connects via a double-headed arrow to the label G.798(17)\_F9-1. + +Diagram of OTS-O layer network and client layer adaptation functions showing the hierarchy from OMS-O\_CP down to OTS-O\_TCP. + +Figure 9-1 – OTS-O layer network and client layer adaptation functions + +The OTS-O characteristic information (OTS-O\_CI) is a logical signal that contains the OTS-O information elements and the OTS-O adapted information. Figure 9-2 illustrates the overhead information elements that shall be supported across the OTS-O\_CP. + +The specific format is outside the scope of this Recommendation. + +![Diagram of information elements at the OTS-O_TCP showing OTS-O_CI and OTS-O_AI components.](ad555483986d7170a46ce72d164b5bc8_img.jpg) + +The diagram shows the structure of OTS-O characteristic information (OTS-O\_CI). It is divided into two main parts: OTS-O\_CI on the left and OTS-O\_AI on the right. OTS-O\_CI contains four stacked boxes labeled TTI, BDI-P, BDI-O, and PMI. OTS-O\_AI is a large shaded rectangular area. The label G.798(17)\_F9-2 is at the bottom right. + +Diagram of information elements at the OTS-O\_TCP showing OTS-O\_CI and OTS-O\_AI components. + +Figure 9-2 – Information elements at the OTS-O\_TCP + +## 9.1 Connection functions + +Not applicable. + +## 9.2 Termination functions + +### 9.2.1 OTS-O trail termination function (OTS-O\_TT) + +The OTS-O\_TT functions are responsible for the end-to-end supervision of the OTS-O trail. Figure 9-3 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Figure 9-3 – OTS-O_TT diagram showing two OTS-O triangles. The left triangle has an input OTS-O_AP at the top and an output OTS-O_TCP at the bottom. The right triangle has an output OTS-O_AP at the top and an input OTS-O_TCP at the bottom. A horizontal arrow labeled OTS-O_RP points from the right triangle to the left triangle. The text G.798(17)_F9-3 is at the bottom right.](7e14467740b2570a44379b347a697921_img.jpg) + +Figure 9-3 – OTS-O\_TT diagram showing two OTS-O triangles. The left triangle has an input OTS-O\_AP at the top and an output OTS-O\_TCP at the bottom. The right triangle has an output OTS-O\_AP at the top and an input OTS-O\_TCP at the bottom. A horizontal arrow labeled OTS-O\_RP points from the right triangle to the left triangle. The text G.798(17)\_F9-3 is at the bottom right. + +**Figure 9-3 – OTS-O\_TT** + +#### **9.2.1.1 OTS-O trail termination source function (OTS-O\_TT\_So)** + +The OTS-O\_TT\_So function adds overhead for the purpose of managing an OMS maintenance entity – including OTS-O TTI, PMI and BDI-P/O. + +The information flow and processing of the OTS-O\_TT\_So functions is defined with reference to Figures 9-4 and 9-5. + +##### **Symbol** + +![Figure 9-4 – OTS-O_TT_So function diagram showing an OTS-O triangle. Inputs include OTS-O_AP at the top, OTS-O_RP from the left, OTS-O_TT_So_MP from the right, and OTS-O_TT_So_DP from the right. The output is OTS-O_TCP at the bottom. The text G.798(17)_F9-4 is at the bottom right.](cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg) + +Figure 9-4 – OTS-O\_TT\_So function diagram showing an OTS-O triangle. Inputs include OTS-O\_AP at the top, OTS-O\_RP from the left, OTS-O\_TT\_So\_MP from the right, and OTS-O\_TT\_So\_DP from the right. The output is OTS-O\_TCP at the bottom. The text G.798(17)\_F9-4 is at the bottom right. + +**Figure 9-4 – OTS-O\_TT\_So function** + +##### **Interfaces** + +**Table 9-1 – OTS-O\_TT\_So inputs and outputs** + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------| +| OTS-O_AP:
OTS-O_AI_OH
OTS-O_RP:
OTS-O_RI_BDI-P
OTS-O_RI_BDI-O
OTS-O_TT_So_MP:
OTS-O_TT_So_MI_TxTI
OTS-O_TT_So_DP:
OTS-O_TT_So_DI_LOS-P | OTS-O_TCP:
OTS-O_CI_OH | + +##### **Processes** + +The processes associated with the OTS-O\_TT\_So function are as depicted in Figure 9-5. + +**TTI:** The trail trace identifier information (OTS-TTI) is inserted into the OTS-O portion of the OSC. Its value is derived from reference point OTS-O\_TT\_So\_MP. The trail trace format is described in clause 15.2 of [ITU-T G.709]. + +**BDI-P:** The BDI-P information (OTS-BDI-P) is inserted into the OTS-O portion of the OSC. Its value is derived from reference point OTS-O\_RP. Upon the declaration/clearing of aBDI-P at the termination sink function, the trail termination source function shall have inserted/removed the BDI-P indication within 50 ms. + +**BDI-O:** The BDI-O information (OTS-BDI-O) is inserted into the OTS-O portion of the OSC. Its value is derived from reference point OTS-O\_RP. Upon the declaration/clearing of aBDI-O at the termination sink function, the trail termination source function shall have inserted/removed the BDI-O indication within 50 ms. + +**PMI:** The PMI information (OTS-PMI) is inserted into the OTS-O portion of the OSC. Upon the declaration/clearing of aPMI, the function shall have inserted/removed the PMI indication. + +![Diagram of OTS-O_TT_So function showing internal components and interfaces.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +The diagram illustrates the internal structure of the OTS-O\_TT\_So function. It is a rectangular block with a vertical 'OTS\_OH insertion' component on the left. Four horizontal boxes represent internal functions: 'Insert PMI', 'Insert BDI-P', 'Insert BDI-O', and 'Insert TTI'. Arrows point from each of these boxes to the 'OTS\_OH insertion' component. External input 'dLOS-P' points to the 'Insert PMI' box. External outputs 'RI\_BDI-P', 'RI\_BDI-O', and 'MI\_TxTTI' point from the 'Insert BDI-P', 'Insert BDI-O', and 'Insert TTI' boxes respectively. These three external outputs are grouped by a bracket labeled 'OTS-O\_TT\_So\_RP'. The entire block is labeled 'OTS-O\_TT\_So' at the bottom. The top interface is labeled 'AI\_OH' and 'OTS-O\_AP'. The bottom interface is labeled 'CI\_OH' and 'OTS-O\_TCP'. A vertical label on the right side indicates the output path as 'OTS-O\_TT\_So\_DP'. A small reference 'G.798(17)\_F9-5' is present at the bottom right of the block. + +Diagram of OTS-O\_TT\_So function showing internal components and interfaces. + +Figure 9-5 – OTS-O\_TT\_So + +##### Defects + +dLOS-P ← OTS-P\_DI\_LOS + +Loss of signal information from the media element is received via the OTS-O\_DP. + +##### Consequent actions + +aPMI ← dLOS-P + +**Defect correlations:** None. + +NOTE – dLOS-P is not reported as fault cause, as it is not a failure condition of the trail itself. It is an incoming failure condition to the trail. It is used to generate PMI to the trail termination sink function (see clause 8.10). + +**Performance monitoring:** None. + +#### 9.2.1.2 OTS-O trail termination sink function (OTS-O\_TT\_Sk) + +The OTS-O\_TT\_Sk reports the state of the OTS-O trail. The OTS-O\_TT\_Sk function extracts OTS-O overhead, including TTI, BDI and PMI. It detects dTIM, dPMI, dBdi-P and dBdi-O defects, receives information about dLOS-P defects from the media element, counts during one-second periods defects to feed performance monitoring when connected, makes the TTI available to network management, and forwards the defect information as backward defect indications to the companion OTS-O\_TT\_So function. + +The information flow and processing of the OTS-O\_TT\_Sk function is defined with reference to Figures 9-6 and 9-7. + +##### Symbol + +![Diagram of the OTS-O function symbol. It is a triangle pointing downwards. Inputs from the left are OTS-O_TT_Sk_MP (top) and OTS-O_TT_Sk_DP (bottom). Input from the bottom is OTS-O_TCP. Output to the top is OTS-O_AP. Output to the right is OTS-O_RP. The label G.798(17)_F9-6 is at the bottom right.](0897c77315bfe37a098f6b4ea39570d2_img.jpg) + +Diagram of the OTS-O function symbol. It is a triangle pointing downwards. Inputs from the left are OTS-O\_TT\_Sk\_MP (top) and OTS-O\_TT\_Sk\_DP (bottom). Input from the bottom is OTS-O\_TCP. Output to the top is OTS-O\_AP. Output to the right is OTS-O\_RP. The label G.798(17)\_F9-6 is at the bottom right. + +Figure 9-6 – OTS-O\_TT\_Sk function + +##### Interfaces + +Table 9-2 – OTS-O\_TT\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OTS-O_TCP:
OTS-O_CI_OH
OTS-O_CI_SSF
OTS-O_TT_Sk_MP:
OTS-O_TT_Sk_MI_ExSAPI
OTS-O_TT_Sk_MI_ExDAPI
OTS-O_TT_Sk_MI_GetAcTI
OTS-O_TT_Sk_MI_TIMDetMo
OTS-O_TT_Sk_MI_TIMActDis
OTS-O_TT_Sk_MI_1second
OTS-O_TT_Sk_DP:
OTS-O_TT_Sk_DI_LOS-P | OTS-O_AP:
OTS-O_AI_OH
OTS-O_AI_TSF-P
OTS-O_AI_TSF-O
OTS-O_RP:
OTS-O_RI_BDI-P
OTS-O_RI_BDI-O
OTS-O_TT_Sk_MP:
OTS-O_TT_Sk_MI_AcTI
OTS-O_TT_Sk_MI_cTIM
OTS-O_TT_Sk_MI_cBDI
OTS-O_TT_Sk_MI_cBDI-P
OTS-O_TT_Sk_MI_cBDI-O
OTS-O_TT_Sk_MI_cLOS-P
OTS-O_TT_Sk_MI_pN_DS-P
OTS-O_TT_Sk_MI_pN_DS-O
OTS-O_TT_Sk_MI_pF_DS-P
OTS-O_TT_Sk_MI_pF_DS-O | + +##### Processes + +The processes associated with the OTS-O\_TT\_Sk function are as depicted in Figure 9-7. The specific implementation for extracting information elements from the OTS-O\_CI is outside the scope of this Recommendation. + +**TTI:** The trail trace identifier information (OTS-TTI) shall be recovered from the OTS-O portion of the OSC and processed as specified in clause 8.6. The accepted value of the TTI is available at the MP. The trail trace format is described in clause 15.2 of [ITU-T G.709]. + +**BDI-P:** The BDI-P information (OTS-BDI-P) shall be extracted from the OTS-O portion of the OSC. It shall be used for BDI-P defect detection. + +**BDI-O:** The BDI-O information (OTS-BDI-O) shall be extracted from the OTS-O portion of the OSC. It shall be used for BDI-O defect detection. + +**PMI:** The PMI information (OTS-PMI) shall be extracted from the OTS-O portion of the OSC. It shall be used for PMI defect detection. + +![Figure 9-7 – OTS-O_TT_Sk processes. A block diagram showing the internal processes of the OTS-O_TT_Sk function. The diagram is divided into three main sections: OTS-O_TT_Sk_RP, OTS-O_TT_Sk_MP, and OTS-O_TT_Sk_DP. The OTS-O_TT_Sk_RP section includes RI_BDI-O, RI_BDI-P, and MI_TIMActDis inputs. The OTS-O_TT_Sk_MP section includes MI_AcTI, MI_ExSAPI, MI_ExDAPI, MI_GetAcTI, MI_TIMDetMo, MI_cTIM, MI_cBDI-O, MI_cBDI-P, MI_cSSF, MI_cLOS-P, MI_cBDI, MI_pF_DS-O, MI_pF_DS-P, MI_1second, MI_pN_DS-O, and MI_pN_DS-P inputs. The OTS-O_TT_Sk_DP section includes DI_LOS-P input. The diagram shows various processing blocks: 'Consequent actions', 'Process TTI', 'Defect correlation', 'Performance monitoring', and 'LOS-P hold off'. These blocks interact with each other and with external interfaces: AI_TSF-P, AI_SSF-O, AI_OH, and OTS_OH access. The diagram also shows the relationship between OTS-O_TT_Sk and OTS-O_TCP (CI_SSF, CI_OH).](352d21d1e740e4a58cb17ab8656cfad8_img.jpg) + +The diagram illustrates the internal architecture of the OTS-O\_TT\_Sk function. It is organized into three vertical sections on the left, each with a bracket and label: **OTS-O\_TT\_Sk\_RP**, **OTS-O\_TT\_Sk\_MP**, and **OTS-O\_TT\_Sk\_DP**. + +- OTS-O\_TT\_Sk\_RP** (Top): Includes inputs RI\_BDI-O, RI\_BDI-P, and MI\_TIMActDis. RI\_BDI-O and RI\_BDI-P connect to a 'Consequent actions' block. MI\_TIMActDis connects to the same block. The 'Consequent actions' block outputs aTSF-P, aTSF-O, dTIM, CI\_SSF, dLOS-P, and dPMI. +- OTS-O\_TT\_Sk\_MP** (Middle): Includes two sub-sections. The top sub-section includes MI\_AcTI, MI\_ExSAPI, MI\_ExDAPI, MI\_GetAcTI, and MI\_TIMDetMo inputs, which connect to a 'Process TTI' block. 'Process TTI' outputs RxTTI to an 'Extract TTI' block. The bottom sub-section includes MI\_cTIM, MI\_cBDI-O, MI\_cBDI-P, MI\_cSSF, MI\_cLOS-P, MI\_cBDI, MI\_pF\_DS-O, MI\_pF\_DS-P, MI\_1second, MI\_pN\_DS-O, and MI\_pN\_DS-P inputs. MI\_cTIM, MI\_cBDI-O, MI\_cBDI-P, MI\_cSSF, MI\_cLOS-P, and MI\_cBDI connect to a 'Defect correlation' block. MI\_pF\_DS-O, MI\_pF\_DS-P, MI\_1second, MI\_pN\_DS-O, and MI\_pN\_DS-P connect to a 'Performance monitoring' block. 'Defect correlation' outputs dTIM, dBBDI-O, dBBDI-P, CI\_SSF, dLOS-P, and dPMI. 'Performance monitoring' outputs dBBDI-O, dBBDI-P, dPMI, aTSF-O, and aTSF-P. Both 'Extract TTI', 'Extract BDI-O', 'Extract BDI-P', and 'Extract PMI' blocks receive data from an 'OTS\_OH access' vertical bar and output to the 'Consequent actions' block. +- OTS-O\_TT\_Sk\_DP** (Bottom): Includes the DI\_LOS-P input, which connects to a 'LOS-P hold off' block. 'LOS-P hold off' outputs dLOS-P to the 'Consequent actions' block. + +External interfaces are shown at the top (AI\_TSF-P, AI\_SSF-O, AI\_OH) and bottom (CI\_SSF, CI\_OH) of the main processing area. The bottom interfaces are part of the **OTS-O\_TCP** layer. A reference G.798(17)\_F9-7 is noted in the bottom right. + +Figure 9-7 – OTS-O\_TT\_Sk processes. A block diagram showing the internal processes of the OTS-O\_TT\_Sk function. The diagram is divided into three main sections: OTS-O\_TT\_Sk\_RP, OTS-O\_TT\_Sk\_MP, and OTS-O\_TT\_Sk\_DP. The OTS-O\_TT\_Sk\_RP section includes RI\_BDI-O, RI\_BDI-P, and MI\_TIMActDis inputs. The OTS-O\_TT\_Sk\_MP section includes MI\_AcTI, MI\_ExSAPI, MI\_ExDAPI, MI\_GetAcTI, MI\_TIMDetMo, MI\_cTIM, MI\_cBDI-O, MI\_cBDI-P, MI\_cSSF, MI\_cLOS-P, MI\_cBDI, MI\_pF\_DS-O, MI\_pF\_DS-P, MI\_1second, MI\_pN\_DS-O, and MI\_pN\_DS-P inputs. The OTS-O\_TT\_Sk\_DP section includes DI\_LOS-P input. The diagram shows various processing blocks: 'Consequent actions', 'Process TTI', 'Defect correlation', 'Performance monitoring', and 'LOS-P hold off'. These blocks interact with each other and with external interfaces: AI\_TSF-P, AI\_SSF-O, AI\_OH, and OTS\_OH access. The diagram also shows the relationship between OTS-O\_TT\_Sk and OTS-O\_TCP (CI\_SSF, CI\_OH). + +Figure 9-7 – OTS-O\_TT\_Sk processes + +##### Defects + +The OTS-O\_TT\_Sk function shall detect dTIM, dBBDI-P, dBBDI-O and dPMI defects. + +**dLOS-P:** Loss of signal information from the media element is received via the DI\_LOS-P. + +NOTE 2 – A hold-off time has to be used for the activation of LOS-P. The hold-off time has to cover the propagation, processing and detection delay of the PMI signal between the source and sink. + +**dTIM:** See clause 6.2.2.1; dTIM shall be set to false during CI\_SSF. + +**dBBDI-P:** See clause 6.2.6.4.1; dBBDI-P shall be set to false during CI\_SSF. + +**dBBDI-O:** See clause 6.2.6.5.1; dBBDI-O shall be set to false during CI\_SSF. + +**dPMI:** See clause 6.2.6.7.1; dPMI shall be set to false during CI\_SSF. + +##### Consequent actions + +The OTS-O\_TT\_Sk function shall perform the following consequent actions. + +$aTSF-P \leftarrow (dLOS-P \text{ and (not } dPMI)) \text{ or } (dTIM \text{ and (not } TIMActDis))$ + +$aTSF-O \leftarrow CI\_SSF \text{ or } (dTIM \text{ and (not } TIMActDis))$ + +$aBDI-P \leftarrow (dLOS-P \text{ and (not } dPMI)) \text{ or } dTIM$ + +$aBDI-O \leftarrow CI\_SSF \text{ or } dTIM$ + +##### Defect correlations + +The OTS-O\_TT\_Sk function shall perform the following defect correlations. + +cBDI $\leftarrow$ dBDI-P and dBDI-O and (not CI\_SSF) and (not dTIM) + +cBDI-P $\leftarrow$ dBDI-P and (not CI\_SSF) and (not (dTIM and (not TIMActDis))) and (not dBDI-O) + +cBDI-O $\leftarrow$ dBDI-O and (not CI\_SSF) and (not (dTIM and (not TIMActDis))) and (not dBDI-P) + +cTIM $\leftarrow$ dTIM and (not CI\_SSF) + +cLOS-P $\leftarrow$ dLOS-P and (not dPMI) and (not CI\_SSF) + +##### Performance monitoring + +The OTS-O\_TT\_Sk function shall perform the following performance monitoring primitives. The performance monitoring primitives shall be reported to the EMF. + +pN\_DS-P $\leftarrow$ (dLOS-P and (not dPMI)) or dTIM + +pN\_DS-O $\leftarrow$ CI\_SSF or dTIM + +pF\_DS-P $\leftarrow$ dBDI-P + +pF\_DS-O $\leftarrow$ dBDI-O + +NOTE 4 – Performance monitoring primitives based on signal quality monitoring are for further study. Specific implementations are outside the scope of this Recommendation. + +## 9.3 Adaptation functions + +The OTS-O is server for the following clients: + +- optical multiplex section overhead (OMS-O). + +### 9.3.1 OTS-O to OMS-O adaptation function (OTS-O/OMS-O\_A) + +The OTS-O to OMS-O adaptation functions perform the adaptation between the OTS-O layer adapted information and the OMS-O layer characteristic information. + +#### 9.3.1.1 OTS-O to OMS-O adaptation source function (OTS-O/OMS-O\_A\_So) + +The information flow and processing of the OTS-O/OMS-O\_A\_So function is defined with reference to Figure 9-8. + +##### Symbol + +![Diagram of the OTS-O/OMS-O_A_So function symbol. It shows a vertical flow starting from a point labeled OMS-O_CP, entering a trapezoidal block labeled OTS-O/OMS-O, and exiting to a point labeled OTS-O_AP. Arrows indicate the downward direction of flow.](70a8d66363cce832376711b7ede4f94e_img.jpg) + +``` + +graph TD + OMS-O_CP --> OTS-O/OMS-O + OTS-O/OMS-O --> OTS-O_AP + +``` + +G.798(17)\_F9-8 + +Diagram of the OTS-O/OMS-O\_A\_So function symbol. It shows a vertical flow starting from a point labeled OMS-O\_CP, entering a trapezoidal block labeled OTS-O/OMS-O, and exiting to a point labeled OTS-O\_AP. Arrows indicate the downward direction of flow. + +**Figure 9-8 – OTS-O/OMS-O\_A\_So** + +##### Interfaces + +**Table 9-3 – OTS-O/OMS-O\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------|---------------------------------| +| OMS-O_CP:
OMS-O_CI_OH | OTS-O_AP:
OTS-O_AI_OH | + +##### Processes + +No information processing is required in the OTS-O/OMS-O\_A\_So, the OTS-O\_AI at its output being identical to the OMS-O\_CI at its input. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 9.3.1.2 OTS-O to OMS-O adaptation sink function (OTS-O/OMS-O\_A\_Sk) + +The information flow and processing of the OTS-O/OMS-O\_A\_Sk function is defined with reference to Figures 9-9 and 9-10. + +##### Symbol + +![Diagram of the OTS-O/OMS-O_A_Sk function symbol. It shows a trapezoidal block labeled 'OTS-O/OMS-O'. An arrow points into the block from the bottom, labeled 'OTS-O_AP'. An arrow points out of the block from the top, labeled 'OMS-O_CP'. Below the diagram is the text 'G.798(17)_F9-9'.](a02b188a5fd52c99f84255322873bf29_img.jpg) + +Diagram of the OTS-O/OMS-O\_A\_Sk function symbol. It shows a trapezoidal block labeled 'OTS-O/OMS-O'. An arrow points into the block from the bottom, labeled 'OTS-O\_AP'. An arrow points out of the block from the top, labeled 'OMS-O\_CP'. Below the diagram is the text 'G.798(17)\_F9-9'. + +**Figure 9-9 – OTS-O/OMS-O\_A\_Sk function** + +##### Interfaces + +**Table 9-4 – OTS-O/OMS-O\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------|---------------------------------------------------------------------| +| OTS-O_AP:
OTS-O_AI_OH
OTS-O_AI_TSF-P
OTS-O_AI_TSF-O | OMS-O_CP:
OMS-O_CI_OH
OMS-O_CI_SSF-P
OMS-O_CI_SSF-O | + +##### Processes + +The processes associated with the OTS-O/OMS-O\_A\_Sk function are as depicted in Figure 9-10. + +**FDI-O:** On declaration of aFDI-O, the function shall insert the FDI-O information (OMS-FDI-O) into the OMS-O portion of the OSC. Otherwise, the incoming OMS-FDI-O information is passed through. + +**FDI-P:** On declaration of aFDI-P, the function shall insert the FDI-P information (OMS-FDI-P) into the OMS-O portion of the OSC. Otherwise, the incoming OMS-FDI-P information is passed through. + +![Figure 9-10: OTS-O/OMS-O_A_Sk processes diagram. The diagram shows a shaded rectangular area representing the OMS-O_CP (top) and OTS-O_AP (bottom) boundary. Inside, there are two boxes: 'Insert FDI-O' and 'Insert FDI-P'. Arrows point from these boxes to a vertical box labeled 'OMS OH insertion'. Above the boxes, labels CI_OH, CI_SSF-O, and CI_SSF-P are present. Below the boxes, labels AI_OH, AI_SSF-O, and AI_TSF-P are present. Vertical arrows on the right are labeled aSSF-O and aSSF-P. The text G.798(17)_F9-10 is at the bottom right.](15de63f0b5df62e6ab9164f2a72e2e33_img.jpg) + +Figure 9-10: OTS-O/OMS-O\_A\_Sk processes diagram. The diagram shows a shaded rectangular area representing the OMS-O\_CP (top) and OTS-O\_AP (bottom) boundary. Inside, there are two boxes: 'Insert FDI-O' and 'Insert FDI-P'. Arrows point from these boxes to a vertical box labeled 'OMS OH insertion'. Above the boxes, labels CI\_OH, CI\_SSF-O, and CI\_SSF-P are present. Below the boxes, labels AI\_OH, AI\_SSF-O, and AI\_TSF-P are present. Vertical arrows on the right are labeled aSSF-O and aSSF-P. The text G.798(17)\_F9-10 is at the bottom right. + +**Figure 9-10 – OTS-O/OMS-O\_A\_Sk processes** + +**Defects:** None. + +##### **Consequent actions** + +The OTS-O/OMS-O\_A\_Sk function performs the following consequent actions. + +$$\text{aSSF-P} \leftarrow \text{AI\_TSF-P}$$ + +$$\text{aFDI-P} \leftarrow \text{AI\_TSF-P}$$ + +$$\text{aSSF-O} \leftarrow \text{AI\_TSF-O}$$ + +$$\text{aFDI-O} \leftarrow \text{AI\_TSF-O}$$ + +**Defect correlations:** None. + +**Performance monitoring:** None. + +# **10 OMS-O layer functions** + +Figure 10-1 illustrates the OMS-O layer network and client layer adaptation functions. The information crossing the OMS-O (termination) connection point (OMS-O\_CP/TCP) is referred to as the OMS-O characteristic information (OMS-O\_CI). The information crossing the OMS-O access point (OMS-O\_AP) is referred to as the OMS-O adapted information (OMS-O\_AI). + +![Figure 10-1: OMS-O layer network and client layer adaptation function diagram. The diagram shows three client layer connection points (OCh-O_CPs, OTSiG-O_CPs, OCh-O_CPs) at the top, each with vertical double-headed arrows. Below these are two trapezoidal shapes representing adaptation functions: 'OMS-O/OCh-O' and 'OMS-O/OTSiG | OCh-O'. These are connected to a central horizontal line labeled 'OMS-O_AP'. Below this line is a downward-pointing triangle labeled 'OMS-O', which is connected to 'OMS-O_TCP' at the bottom. The text G.798(17)_F10-1 is at the bottom right.](50f72073c616cb3d3ca3af04a0c3a221_img.jpg) + +Figure 10-1: OMS-O layer network and client layer adaptation function diagram. The diagram shows three client layer connection points (OCh-O\_CPs, OTSiG-O\_CPs, OCh-O\_CPs) at the top, each with vertical double-headed arrows. Below these are two trapezoidal shapes representing adaptation functions: 'OMS-O/OCh-O' and 'OMS-O/OTSiG | OCh-O'. These are connected to a central horizontal line labeled 'OMS-O\_AP'. Below this line is a downward-pointing triangle labeled 'OMS-O', which is connected to 'OMS-O\_TCP' at the bottom. The text G.798(17)\_F10-1 is at the bottom right. + +**Figure 10-1 – OMS-O layer network and client layer adaptation function** + +The OMS-O characteristic information (OMS-O\_CI) contains the logical information elements for maintenance and operational functions to support the OMS maintenance entity. Figure 10-2 illustrates the overhead information elements that shall be supported across the OMS-O\_CP. + +![Figure 10-2: OMS-O_CI information elements diagram. A box labeled OMS-O_CI contains six stacked elements: MSI, FDI-P, FDI-O, BDI-P, BDI-O, and PMI. To the right of this box is a large grey box labeled OMS-O_AI. The diagram is labeled G.798(17)_F10-2 at the bottom right.](b5b908b453ca50ed3b4cca88aef080fa_img.jpg) + +Figure 10-2: OMS-O\_CI information elements diagram. A box labeled OMS-O\_CI contains six stacked elements: MSI, FDI-P, FDI-O, BDI-P, BDI-O, and PMI. To the right of this box is a large grey box labeled OMS-O\_AI. The diagram is labeled G.798(17)\_F10-2 at the bottom right. + +Figure 10-2 – OMS-O\_CI information elements + +## 10.1 Connection functions + +Not applicable. + +## 10.2 Termination functions + +### 10.2.1 OMS-O trail termination function (OMS-O\_TT) + +The OMS-O\_TT functions are responsible for the end-to-end supervision of the OMS-O trail. Figure 10-3 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Figure 10-3: OMS-O_TT diagram. Two trapezoidal blocks labeled OMS-O are shown. The left block has an input OMS-O_AP at the top and an output OMS-O_TCP at the bottom. The right block has an output OMS-O_AP at the top and an input OMS-O_TCP at the bottom. A horizontal arrow labeled OMS-O_RP points from the right OMS-O block to the left OMS-O block. The diagram is labeled G.798(17)_F10-3 at the bottom right.](236f674770a03c918c0375a74fe950db_img.jpg) + +Figure 10-3: OMS-O\_TT diagram. Two trapezoidal blocks labeled OMS-O are shown. The left block has an input OMS-O\_AP at the top and an output OMS-O\_TCP at the bottom. The right block has an output OMS-O\_AP at the top and an input OMS-O\_TCP at the bottom. A horizontal arrow labeled OMS-O\_RP points from the right OMS-O block to the left OMS-O block. The diagram is labeled G.798(17)\_F10-3 at the bottom right. + +Figure 10-3 – OMS-O\_TT + +#### 10.2.1.1 OMS-O trail termination source function (OMS-O\_TT\_So) + +The OMS-O\_TT\_So function adds overhead for the purpose of managing an OMS maintenance entity – including OMS BDI-P/O and PMI. + +The information flow and processing of the OMS-O\_TT\_So function is defined with reference to Figures 10-4 and 10-5. + +##### Symbol + +![Symbol diagram for OMS-O function. A central triangle labeled 'OMS-O' has four input arrows pointing to it from the top (OMS-O_AP), left (OMS-O_TT_So_DP), and right (OMS-O_RP). An output arrow points downwards from the triangle to 'OMS-O_TCP'. The text 'G.798(17)_F10-4' is located to the right of the output arrow.](0af1ba85ab6e4e50befbef3d63e017dc_img.jpg) + +Symbol diagram for OMS-O function. A central triangle labeled 'OMS-O' has four input arrows pointing to it from the top (OMS-O\_AP), left (OMS-O\_TT\_So\_DP), and right (OMS-O\_RP). An output arrow points downwards from the triangle to 'OMS-O\_TCP'. The text 'G.798(17)\_F10-4' is located to the right of the output arrow. + +Figure 10-4 – OMS-O\_TT\_So function + +##### Interfaces + +Table 10-1 – OMS-O\_TT\_So inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------| +| OMS-O_AP:
OMS-O_AI_OH
OMS-O_RP:
OMS-O_RI_BDI-P
OMS-O_RI_BDI-O
OMS-O_TT_So_DP:
OMS-O_TT_So_DI_LOS-P | OMS-O_TCP:
OMS-O_CI_OH | + +##### Processes + +The processes associated with the OMS-O\_TT\_So function are as depicted in Figure 10-5. + +**BDI-P:** The BDI-P information is inserted into the OMS-O portion of the OSC. Its value is derived from reference point OMS-O\_RP. Upon the declaration/clearing of aBDI-P at the termination sink function, the trail termination source function shall have inserted/removed the BDI-P indication within 50 ms. + +**BDI-O:** The BDI-O information is inserted into the OMS-O portion of the OSC. Its value is derived from reference point OMS-O\_RP. Upon the declaration/clearing of aBDI-O at the termination sink function, the trail termination source function shall have inserted/removed the BDI-O indication within 50 ms. + +**PMI:** The PMI information is inserted into the OMS-O portion of the OSC Upon the declaration/clearing of aPMI, the function shall have inserted/removed the PMI indication. + +![Figure 10-5 – OMS-O_TT_So processes diagram. The diagram shows a shaded rectangular box representing the OMS-O_TT_So processes. At the top, 'AI_OH' points down into the box. At the bottom, 'CI_OH' points down out of the box. Inside the box, on the left, a vertical box labeled 'OMS OH insertion' has arrows pointing to three horizontal boxes: 'Insert PMI', 'Insert BDI-P', and 'Insert BDI-O'. These three boxes point to defect indicators on the right: 'dLOS-P', 'RI_BDI-P', and 'RI_BDI-O'. These three indicators are grouped by a bracket labeled 'OMS-O_TT_So_RP'. To the right of the bracket, the text 'OMS-O_TT_So_DP' is written vertically. The diagram is labeled 'G.798(17)_F10-5' at the bottom right of the box.](99698c448635861b7dc8d352f87a1b2b_img.jpg) + +Figure 10-5 – OMS-O\_TT\_So processes diagram. The diagram shows a shaded rectangular box representing the OMS-O\_TT\_So processes. At the top, 'AI\_OH' points down into the box. At the bottom, 'CI\_OH' points down out of the box. Inside the box, on the left, a vertical box labeled 'OMS OH insertion' has arrows pointing to three horizontal boxes: 'Insert PMI', 'Insert BDI-P', and 'Insert BDI-O'. These three boxes point to defect indicators on the right: 'dLOS-P', 'RI\_BDI-P', and 'RI\_BDI-O'. These three indicators are grouped by a bracket labeled 'OMS-O\_TT\_So\_RP'. To the right of the bracket, the text 'OMS-O\_TT\_So\_DP' is written vertically. The diagram is labeled 'G.798(17)\_F10-5' at the bottom right of the box. + +**Figure 10-5 – OMS-O\_TT\_So processes** + +##### **Defects** + +dLOS-P: Loss of signal information from the media element is received via the OMS-O\_DP. + +##### **Consequent actions** + +aPMI ← dLOS-P + +**Defect correlations:** None. + +NOTE – dLOS-P is not reported as fault cause, as it is not a failure condition of the trail itself. It is an incoming failure condition to the trail. It is used to generate PMI to the trail termination sink function (see clause 8.10). + +**Performance monitoring:** None. + +#### **10.2.1.2 OMS-O trail termination sink function (OMS-O\_TT\_Sk)** + +The OMS-O\_TT\_Sk reports the state of the OMS-O trail. The OMS-O\_TT\_Sk function extracts OMS-O monitoring overhead – including BDI, FDI-P, FDI-O and PMI. It detects dLOS-P, dPMI, dFDI-P, dFDI-O, dBDI-P and dBDI-O defects, receives information about dLOS-P defects from the media element, counts during one-second periods defects to feed performance monitoring when connected, and forwards the defect information as backward defect indications to the companion OMS-O\_TT\_So function. + +The information flow and processing of the OMS-O\_TT\_Sk function is defined with reference to Figures 10-6 and 10-7. + +##### **Symbol** + +![Figure 10-6 – OMS-O_TT_Sk function diagram. The diagram shows a triangle symbol labeled 'OMS-O'. Above the triangle, 'OMS-O_AP' points up. Below the triangle, 'OMS-O_TCP' points up. To the left of the triangle, 'OMS-O_TT_Sk_MP' and 'OMS-O_TT_Sk_DP' point right into the triangle. To the right of the triangle, an arrow points right to 'OMS-O_RP'. The diagram is labeled 'G.798(17)_F10-6' at the bottom right.](c425a7b76be3f887bb251606c2a7ce9a_img.jpg) + +Figure 10-6 – OMS-O\_TT\_Sk function diagram. The diagram shows a triangle symbol labeled 'OMS-O'. Above the triangle, 'OMS-O\_AP' points up. Below the triangle, 'OMS-O\_TCP' points up. To the left of the triangle, 'OMS-O\_TT\_Sk\_MP' and 'OMS-O\_TT\_Sk\_DP' point right into the triangle. To the right of the triangle, an arrow points right to 'OMS-O\_RP'. The diagram is labeled 'G.798(17)\_F10-6' at the bottom right. + +**Figure 10-6 – OMS-O\_TT\_Sk function** + +##### Interfaces + +**Table 10-2 – OMS-O\_TT\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OMS-O_TCP:
OMS-O_CI_OH
OMS-O_CI_SSF-P
OMS-O_CI_SSF-O
OMS-O_TT_Sk_MP:
OMS-O_TT_Sk_MI_1second
OMS-O_TT_Sk_DP:
OMS-O_TT_Sk_DI_LOS-P | OMS-O_AP:
OMS-O_AI_OH
OMS-O_AI_TSF-P
OMS-O_AI_TSF-O
OMS-O_RP:
OMS-O_RI_BDI-P
OMS-O_RI_BDI-O
OMS-O_TT_Sk_MP:
OMS-O_TT_Sk_MI_cSSF-P
OMS-O_TT_Sk_MI_cSSF-O
OMS-O_TT_Sk_MI_cSSF
OMS-O_TT_Sk_MI_cBDI
OMS-O_TT_Sk_MI_cBDI-P
OMS-O_TT_Sk_MI_cBDI-O
OMS-O_TT_Sk_MI_cLOS-P
OMS-O_TT_Sk_MI_pN_DS-P
OMS-O_TT_Sk_MI_pN_DS-O
OMS-O_TT_Sk_MI_pF_DS-P
OMS-O_TT_Sk_MI_pF_DS-O | + +##### Processes + +The processes associated with the OMS-O\_TT\_Sk function are depicted in Figure 10-7. The specific implementation for extracting information elements from the OMS\_CI is outside the scope of this Recommendation. + +**FDI-P:** The FDI-P information (OMS-FDI-P) shall be extracted from the OMS-O portion of the OSC. It shall be used for FDI-P defect detection. + +**FDI-O:** The FDI-O information (OMS-FDI-O) shall be extracted from the OMS-O portion of the OSC. It shall be used for FDI-O defect detection. + +**BDI-P:** The BDI-P information (OMS-BDI-P) shall be extracted from the OMS-O portion of the OSC. It shall be used for BDI-P defect detection. + +**BDI-O:** The BDI-O information (OMS-BDI-O) shall be extracted from the OMS-O portion of the OSC. It shall be used for BDI-O defect detection. + +**PMI:** The PMI information (OMS-PMI) shall be extracted from the OMS-O portion of the OSC. It shall be used for PMI defect detection. + +![Figure 10-7 – OMS-O_TT_Sk processes. A block diagram showing the internal processes of the OMS-O_TT_Sk function. It is divided into three main sections: OMS-O_TT_Sk_RP, OMS-O_TT_Sk_MP, and OMS-O_TT_Sk_DP. The diagram shows various input and output signals, including defect correlation, performance monitoring, and consequent actions. Inputs include RI_BDI-O, RI_BDI-P, MI_cSSF-O, MI_cSSF-P, MI_cBDI-O, MI_cBDI-P, MI_cSSF, MI_cBDI, MI_cLOS-P, MI_pF_DS-O, MI_pF_DS-P, MI_1second, MI_pN_DS-O, MI_pN_DS-P, and DI_LOS-P. Outputs include aTSF-P, aTSF-O, aBDI-P, aBDI-O, dFDI-P, dFDI-O, dPMI, dLOS-P, and CI_OH. Internal blocks include 'Consequent actions', 'Defect correlation', 'Performance monitoring', 'LOS-P hold off', and 'Extract' blocks for BDI-O, BDI-P, FDI-O, FDI-P, and PMI. The diagram also shows interactions with OMS-O_TCP and OMS-O_AP.](b20942bb14022381a243971ab9790dd9_img.jpg) + +Figure 10-7 – OMS-O\_TT\_Sk processes. A block diagram showing the internal processes of the OMS-O\_TT\_Sk function. It is divided into three main sections: OMS-O\_TT\_Sk\_RP, OMS-O\_TT\_Sk\_MP, and OMS-O\_TT\_Sk\_DP. The diagram shows various input and output signals, including defect correlation, performance monitoring, and consequent actions. Inputs include RI\_BDI-O, RI\_BDI-P, MI\_cSSF-O, MI\_cSSF-P, MI\_cBDI-O, MI\_cBDI-P, MI\_cSSF, MI\_cBDI, MI\_cLOS-P, MI\_pF\_DS-O, MI\_pF\_DS-P, MI\_1second, MI\_pN\_DS-O, MI\_pN\_DS-P, and DI\_LOS-P. Outputs include aTSF-P, aTSF-O, aBDI-P, aBDI-O, dFDI-P, dFDI-O, dPMI, dLOS-P, and CI\_OH. Internal blocks include 'Consequent actions', 'Defect correlation', 'Performance monitoring', 'LOS-P hold off', and 'Extract' blocks for BDI-O, BDI-P, FDI-O, FDI-P, and PMI. The diagram also shows interactions with OMS-O\_TCP and OMS-O\_AP. + +G.798(17)\_F10-7 + +Figure 10-7 – OMS-O\_TT\_Sk processes + +##### Defects + +The OMS-O\_TT\_Sk function shall detect dLOS-P, dFDI-P, dFDI-O, dBDI-P, dBDI-O and dPMI defects. + +**dLOS-P:** Loss of signal information from the media element is received via the OMS-O\_DP. + +NOTE 2 – A hold-off time has to be used for the activation of LOS-P. The hold-off time has to cover the propagation, processing and detection delay of the PMI signal between the source and sink. + +**dFDI-P:** See clause 6.2.6.1.1. + +**dFDI-O:** See clause 6.2.6.2.1. + +**dBDI-P:** See clause 6.2.6.4.1; dBDI-P shall be set to false during CI\_SSF-O and dFDI-O. + +**dBDI-O:** See clause 6.2.6.5.1; dBDI-O shall be set to false during CI\_SSF-O and dFDI-O. + +**dPMI:** See clause 6.2.6.7.1; dPMI shall be set to false during CI\_SSF-O and dFDI-O. + +##### Consequent actions + +The OMS-O\_TT\_Sk function shall perform the following consequent actions. + +$aTSF-P \leftarrow (dLOS-P \text{ and (not } dPMI)) \text{ or } dFDI-P \text{ or } CI\_SSF-P$ + +$aTSF-O \leftarrow dFDI-O \text{ or } CI\_SSF-O$ + +$aBDI-P \leftarrow (dLOS-P \text{ and (not } dPMI)) \text{ or } dFDI-P \text{ or } CI\_SSF-P$ + +$aBDI-O \leftarrow dFDI-O \text{ or } CI\_SSF-O$ + +##### Defect correlations + +The OMS-O\_TT\_Sk function shall perform the following defect correlations. + +cSSF $\leftarrow$ (CI\_SSF-P or dFDI-P) and (CI\_SSF-O or dFDI-O) + +cSSF-P $\leftarrow$ (CI\_SSF-P or dFDI-P) and (not cSSF) + +cSSF-O $\leftarrow$ (CI\_SSF-O or dFDI-O) and (not cSSF) + +cBDI $\leftarrow$ (dBDI-P and (not dFDI-O)) and (dBDI-O and (not dFDI-O)) + +cBDI-P $\leftarrow$ (dBDI-P and (not dFDI-O)) and (not cBDI) + +cBDI-O $\leftarrow$ (dBDI-O and (not dFDI-O)) and (not cBDI) + +cLOS-P $\leftarrow$ dLOS-P and (not dPMI) and (not dFDI-P) and (not CI\_SSF-P) + +##### Performance monitoring + +The OMS-O\_TT\_Sk function shall perform the following performance monitoring primitives. The performance monitoring primitives shall be reported to the EMF. + +pN\_DS-P $\leftarrow$ aTSF-P + +pN\_DS-O $\leftarrow$ aTSF-O + +pF\_DS-P $\leftarrow$ dBDI-P + +pF\_DS-O $\leftarrow$ dBDI-O + +NOTE 3 – Performance monitoring primitives based on signal quality monitoring are for further study. + +## 10.3 Adaptation functions + +The OMS is server for the following clients: + +- OCh-O +- OTSiG-O. + +### 10.3.1 OMS-O to OCh-O adaptation function (OMS-O/OCh-O\_A) + +The OMS-O to OCh-O adaptation functions perform the adaptation between the OMS-O layer adapted information and the characteristic information of n OCh-O layer signals. + +#### 10.3.1.1 OMS-O to OCh-O adaptation source function (OMS-O/OCh-O\_A\_So) + +The OMS-O/OCh-O\_A\_So function multiplexes the individual OCh-O\_CIs to the OMS-O\_AI. The information flow and processing of the OMS-O/OCh-O\_A\_So function is defined with reference to Figures 10-8 and 10-9. + +##### Symbol + +![Diagram of the OMS-O/OCh-O_A_So function. It shows n input signals labeled OCh-O_CPs (1, 2, ..., n) entering a trapezoidal block labeled OMS-O/OCh-O. An output signal labeled OMS-O_AP exits the block. Below the diagram is the text G.798(17)-Amd.2(19)_F10-8.](426116a38cef1a4b575e63bcd65c676d_img.jpg) + +``` +graph TD + subgraph " " + direction TB + CP1[1] --> Block + CP2[2] --> Block + CPn[n] --> Block + Block[OMS-O/OCh-O] --> AP[OMS-O_AP] + end + style Block fill:none,stroke:#000,stroke-width:1px + classDef labelText fill:none,stroke:none + CP1:::labelText + CP2:::labelText + CPn:::labelText + AP:::labelText +``` + +G.798(17)-Amd.2(19)\_F10-8 + +Diagram of the OMS-O/OCh-O\_A\_So function. It shows n input signals labeled OCh-O\_CPs (1, 2, ..., n) entering a trapezoidal block labeled OMS-O/OCh-O. An output signal labeled OMS-O\_AP exits the block. Below the diagram is the text G.798(17)-Amd.2(19)\_F10-8. + +**Figure 10-8 – OMS-O/OCh-O\_A\_So function** + +##### Interfaces + +**Table 10-3 – OMS-O/OCh-O\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------|---------------------------------| +| per OCh-O_CP:
OCh-O_CI_OH | OMS-O_AP:
OMS-O_AI_OH | +| NOTE – This function assumes a fixed frequency grid. | | + +##### Processes + +The processes associated with the OMS-O/OCh-O\_A\_So function are common processes for the compound (multiplexed) signal as depicted in Figure 10-9. + +##### Specific processes + +None. + +##### Common processes + +**Overhead multiplexing:** This process performs overhead multiplexing of the individual OCh-O signals. The specific multiplex function is outside the scope of this Recommendation. + +![Diagram of OMS-O/OCh-O_A_So processes showing overhead multiplexing of multiple OCh-O_CP signals into a single OMS-O_AP signal.](f4b570ddd089f54943d46e9f8776f9f9_img.jpg) + +The diagram illustrates the 'Overhead multiplexing' process. It shows multiple input signals, labeled OCh-O\_CP[1] and OCh-O\_CP[n], each with a CI\_OH component. These inputs are numbered 1, ..., n and enter a central box labeled 'Overhead multiplexing'. This box is situated within a larger grey area labeled 'Common processes'. An arrow points from the 'Overhead multiplexing' box to an output signal labeled AI\_OH, which is also labeled OMS-O\_AP. The diagram is identified by the code G.798(17)-Amd.2(19)\_F10-9. + +Diagram of OMS-O/OCh-O\_A\_So processes showing overhead multiplexing of multiple OCh-O\_CP signals into a single OMS-O\_AP signal. + +**Figure 10-9 – OMS-O/OCh-O\_A\_So processes** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 10.3.1.2 OMS-O to OCh-O adaptation sink function (OMS-O/OCh-O\_A\_Sk) + +The OMS-O/OCh-O\_A\_Sk function demultiplexes the OMS-O\_AI into the individual OCh-O\_CIs. Upon signal fail conditions, it generates FDI for the individual channels. + +The information flow and processing of the OMS-O/OCh-O\_A\_Sk function is defined with reference to Figures 10-10 and 10-11. + +##### Symbol + +![Symbol diagram for the OMS-O/OCh-O_A_Sk function. A trapezoidal block labeled 'OMS-O/OCh-O' has a single input arrow from below labeled 'OMS-O_AP'. Multiple output arrows point upwards from the top of the block, labeled 'OCh-O_CPs' with subscripts 1, 2, ..., n. Below the diagram is the text 'G.798(17)-Amd.2(19)_F10-10'.](b68ed2f7c90787b2fcfeb6be5640ecd4_img.jpg) + +Symbol diagram for the OMS-O/OCh-O\_A\_Sk function. A trapezoidal block labeled 'OMS-O/OCh-O' has a single input arrow from below labeled 'OMS-O\_AP'. Multiple output arrows point upwards from the top of the block, labeled 'OCh-O\_CPs' with subscripts 1, 2, ..., n. Below the diagram is the text 'G.798(17)-Amd.2(19)\_F10-10'. + +**Figure 10-10 – OMS-O/OCh-O\_A\_Sk function** + +##### Interfaces + +**Table 10-4 – OMS-O/OCh-O\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------|-------------------------------------------------------------------------| +| OMS-O_AP:
OMS-O_AI_OH
OMS-O_AI_TSF-P
OMS-O_AI_TSF-O | per OCh-O_CP:
OCh-O_CI_OH
OCh-O_CI_SSF-P
OCh-O_CI_SSF-O | +| NOTE – This function assumes a fixed frequency grid. | | + +##### Processes + +The processes associated with the OMS-O/OCh-O\_A\_Sk function are specific processes for each OCh-O signal and common processes for the compound (multiplexed) signal as depicted in Figure 10-11. + +##### Common processes + +**Overhead demultiplexing (OHDM):** This process performs the overhead demultiplexing and provides access to the individual OCh-O signals. The specific multiplex function is outside the scope of this Recommendation. + +##### OCh-O Specific processes + +**FDI-O:** On declaration of aFDI-O the function shall insert the FDI-O information (OCh-FDI-O) into each OCh-O. Otherwise, the incoming OCh-FDI-O information is passed through. + +**FDI-P:** On declaration of aFDI-P the function shall insert the FDI-P information (OCh-FDI-P) into each OCh-O. Otherwise, the incoming OCh-FDI-P information is passed through. + +![Diagram of OMS-O/OCh-O_A_Sk processes showing signal flow between OMS-O_AP and multiple OCh-O client ports (OCh-O_CP[1] to OCh-O_CP[n]).](3bf1696c3034743b5ab07a0b5e398347_img.jpg) + +The diagram illustrates the OMS-O/OCh-O\_A\_Sk processes. At the bottom, the OMS-O\_AP (Optical Multiplex Section Adaptation - Optical Payload) provides input signals: AI\_OH (Optical Overhead) and AI\_TSF-P (Payload Transport Signal - Payload). These signals enter a block labeled 'Common processes', which contains an 'Overhead multiplexing' unit. The output of this unit is split: one path goes to the 'OCh-O specific processes' for each client port, and the other path goes to an 'OCh-O OH insertion' block. The 'OCh-O OH insertion' block outputs CI\_OH (Optical Overhead). The 'OCh-O specific processes' for each port (OCh-O\_CP[1] to OCh-O\_CP[n]) receive the multiplexed overhead and the payload. They perform 'Insert FDI-O' and 'Insert FDI-P' actions, which are then processed by 'Consequent actions' blocks. The output of these blocks is aSSF-P (Payload Transport Signal - Payload) and aSSF-O (Optical Transport Signal - Overhead). These signals are then processed by 'CI\_SSF-P' and 'CI\_SSF-O' blocks, which output the final signals CI\_OH, CI\_SSF-P, and CI\_SSF-O for each client port. + +Diagram of OMS-O/OCh-O\_A\_Sk processes showing signal flow between OMS-O\_AP and multiple OCh-O client ports (OCh-O\_CP[1] to OCh-O\_CP[n]). + +Figure 10-11 – OMS-O/OCh-O\_A\_Sk processes + +**Defects:** None. + +##### **Consequent actions** + +The OMS-O/OCh-O\_A\_Sk function performs the following consequent actions. + +For each OCh-O client port #p: + +$$\text{aSSF-P}[p] \leftarrow \text{AI\_TSF-P}$$ + +$$\text{aFDI-P}[p] \leftarrow \text{AI\_TSF-P}$$ + +$$\text{aSSF-O}[p] \leftarrow \text{AI\_TSF-O}$$ + +$$\text{aFDI-O}[p] \leftarrow \text{AI\_TSF-O}$$ + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### **10.3.2 OMS-O to OTSiG-O and OCh-O adaptation function (OMS-O/OTSiG|OCh-O\_A)** + +The OMS-O to OTSiG-O adaptation functions perform the adaptation between the OMS-O layer adapted information and the characteristic information of n OTSiG-O and m OCh-O layer signals. This includes the optical payload and the overhead. + +#### 10.3.2.1 OMS-O to OTSiG-O and OCh-O adaptation source function (OMS-O/OTSiG|OCh-O\_A\_So) + +The OMS-O/OTSiG|OCh-O\_A\_So function multiplexes the individual OTSiG-O\_CIs and OCh-O\_CIs to the OMS-O\_AI. The information flow and processing of the OMS-O/OTSiG|OCh-O\_A\_So function is defined with reference to Figures 10-12 and 10-13. + +##### Symbol + +![Figure 10-12: Symbol diagram for the OMS-O/OTSiG|OCh-O_A_So function. The central block is labeled 'OMS-O/OTSiG|OCh-O'. Inputs from the top are OTSiG-O_CPs (labeled 1, 2, ..., n) and [OCh-O_CPs] (labeled 1, 2, ..., m). An input from the left is OMS-O/OTSiG|OCh-O_A_So_MP. An output to the right is OMS-O/OTSiG|OCh-O_A_So_MECP. An output pointing down is OMS-O_AP. A reference code G.798(17)-Amd.2(19)_F10-12 is shown in the bottom right.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +Figure 10-12: Symbol diagram for the OMS-O/OTSiG|OCh-O\_A\_So function. The central block is labeled 'OMS-O/OTSiG|OCh-O'. Inputs from the top are OTSiG-O\_CPs (labeled 1, 2, ..., n) and [OCh-O\_CPs] (labeled 1, 2, ..., m). An input from the left is OMS-O/OTSiG|OCh-O\_A\_So\_MP. An output to the right is OMS-O/OTSiG|OCh-O\_A\_So\_MECP. An output pointing down is OMS-O\_AP. A reference code G.798(17)-Amd.2(19)\_F10-12 is shown in the bottom right. + +Figure 10-12 – OMS-O/OTSiG|OCh-O\_A\_So function + +##### Interfaces + +Table 10-5 – OMS-O/OTSiG|OCh-O\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| +| per OTSiG-O_CP:
OTSiG-O_CI_OH
per OCh-O_CP:
OCh-O_CI_OH
OMS-O/OTSiG OCh-O_A_So_MP:
OMS-O/OTSiG OCh-O_A_So_MI_TxMSI
OMS-O/OTSiG OCh-O_A_So_MECP:
OMS-O/OTSiG OCh-O_A_So_MECl_TxFSS | OMS-O_AP:
OMS-O_AI_OH
OMS-O/OTSiG OCh-O_A_So_MECP:
OMS-O/OTSiG OCh-O_A_So_MECl_TxFSS | + +##### Processes + +The processes associated with the OMS-O/OTSiG|OCh-O\_A\_So function are common processes for the compound (multiplexed) signal as depicted in Figure 10-13. + +**MSI:** See clause 8.7.2.3. + +##### Specific processes + +None. + +##### Common processes + +**Overhead multiplexing:** This process performs overhead multiplexing of the individual OTSiG-O and OCh-O signals. The specific multiplex function is outside the scope of this Recommendation. + +![Figure 10-13: OMS-O/OTSiG|OCh-O_A_So processes diagram. The diagram shows a central 'Overhead multiplexing' block receiving inputs from multiple channels: OTSiG-O_CP[1] to OTSiG-O_CP[n] and OCh-O_CP[1] to OCh-O_CP[m]. Each channel has a corresponding CI_OH input. The 'Overhead multiplexing' block outputs to a 'Common processes' block, which in turn outputs to MECl_TxFSS. A 'Multiplex structure identifier (MSI)' block is connected to the 'Common processes' block and receives input from MI_TxMSI. The 'Common processes' block also outputs to AI_OH, which is part of the OMS-O_AP. The diagram is labeled G.798(17)-Amd.2(19)_F10-13.](c6212a3b14736d6a8c81ace75ae94ccf_img.jpg) + +Figure 10-13: OMS-O/OTSiG|OCh-O\_A\_So processes diagram. The diagram shows a central 'Overhead multiplexing' block receiving inputs from multiple channels: OTSiG-O\_CP[1] to OTSiG-O\_CP[n] and OCh-O\_CP[1] to OCh-O\_CP[m]. Each channel has a corresponding CI\_OH input. The 'Overhead multiplexing' block outputs to a 'Common processes' block, which in turn outputs to MECl\_TxFSS. A 'Multiplex structure identifier (MSI)' block is connected to the 'Common processes' block and receives input from MI\_TxMSI. The 'Common processes' block also outputs to AI\_OH, which is part of the OMS-O\_AP. The diagram is labeled G.798(17)-Amd.2(19)\_F10-13. + +Figure 10-13 – OMS-O/OTSiG|OCh-O\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 10.3.2.2 OMS-O to OTSiG-O and OCh-O adaptation sink function (OMS-O/OTSiG|OCh-O\_A\_Sk) + +The OMS-O/OTSiG|OCh-O\_A\_Sk function demultiplexes the OMS-O\_AI into the individual OTSiG-O\_CIs and OCh-O\_CIs. Upon signal fail conditions, it generates FDI for the individual channels. + +The information flow and processing of the OMS-O/OTSiG|OCh-O\_A\_Sk function is defined with reference to Figures 10-14 and 10-15. + +##### Symbol + +![Figure 10-14: OMS-O/OTSiG|OCh-O_A_Sk function diagram. The diagram shows a central block labeled 'OMS-O/OTSiG|OCh-O'. It receives an input from OMS-O_AP at the bottom. On the left, it has a bidirectional connection to OMS-O/OTSiG|OCh-O_A_Sk_MP. On the right, it has a bidirectional connection to OMS-O/OTSiG|OCh-O_A_Sk_MECP. Above the central block, there are two groups of outputs: OTSiG-O_CPs (labeled 1, 2, ..., n) and [OCh-O_CPs] (labeled 1, 2, ..., m). The diagram is labeled G.798(17)-Amd.2(19)_F10-14.](f88e403864388f59871586472847bbd0_img.jpg) + +Figure 10-14: OMS-O/OTSiG|OCh-O\_A\_Sk function diagram. The diagram shows a central block labeled 'OMS-O/OTSiG|OCh-O'. It receives an input from OMS-O\_AP at the bottom. On the left, it has a bidirectional connection to OMS-O/OTSiG|OCh-O\_A\_Sk\_MP. On the right, it has a bidirectional connection to OMS-O/OTSiG|OCh-O\_A\_Sk\_MECP. Above the central block, there are two groups of outputs: OTSiG-O\_CPs (labeled 1, 2, ..., n) and [OCh-O\_CPs] (labeled 1, 2, ..., m). The diagram is labeled G.798(17)-Amd.2(19)\_F10-14. + +Figure 10-14 – OMS-O/OTSiG|OCh-O\_A\_Sk function + +##### Interfaces + +**Table 10-6 – OMS-O/OTSiG|OCh-O\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OMS-O_AP:
OMS-O_AI_OH
OMS-O_AI_TSF-P
OMS-O_AI_TSF-O
OMS-O/OTSiG OCh-O_A_Sk_MP:
OMS-O/OTSiG OCh-
O_A_Sk_MI_ExMSI[1..(n+m)]
OMS-O/OTSiG OCh-O_A_Sk_MECP:
OMS-O/OTSiG OCh-O_A_Sk_MECI_RxFSS | per OTSiG-O_CP:
OTSiG-O_CI_OH
OTSiG-O_CI_SSF-P
OTSiG-O_CI_SSF-O
per OCh-O_CP:
OCh-O_CI_OH
OCh-O_CI_SSF-P
OCh-O_CI_SSF-O
OMS-O/OTSiG OCh-O_A_Sk_MP:
OMS-O/OTSiG OCh-
O_A_Sk_MI_AcMSI[1..(n+m)]
OMS-O/OTSiG OCh-
O_A_Sk_MI_cMSIM[1..(n+m)]
OMS-O/OTSiG OCh-O_A_Sk_MECP:
OMS-O/OTSiG OCh-O_A_Sk_MECI_RxFSS | + +##### Processes + +The processes associated with the OMS-O/OTSiG|OCh-O\_A\_Sk function are specific processes for each OTSiG-O signal and for each OCh-O signal and common processes for the compound (multiplexed) signal as depicted in Figure 10-15. + +##### Common processes + +**Overhead demultiplexing (OHDM):** This process performs the overhead demultiplexing and provides access to the individual OTSiG-O and OCh-O signals. The specific multiplex function is outside the scope of this Recommendation. + +**MSI:** See clause 8.7.2.3. + +##### OTSiG-O Specific processes + +**FDI-O:** On declaration of aFDI-O the function shall insert the FDI-O information (OTSiG-FDI-O) into each OTSiG-O. Otherwise, the incoming OTSiG-FDI-O information is passed through. + +**FDI-P:** On declaration of aFDI-P the function shall insert the FDI-P information (OTSiG-FDI-P) into each OTSiG-O. Otherwise, the incoming OTSiG-FDI-P information is passed through. + +##### OCh-O Specific processes + +**FDI-O:** On declaration of aFDI-O the function shall insert the FDI-O information (OCh-FDI-O) into each OCh-O. Otherwise, the incoming OCh-FDI-O information is passed through. + +**FDI-P:** On declaration of aFDI-P the function shall insert the FDI-P information (OCh-FDI-P) into each OCh-O. Otherwise, the incoming OCh-FDI-P information is passed through. + +![Figure 10-15 – OMS-O/OTSiG|OCh-O_A_Sk processes. This block diagram illustrates the internal structure of the OMS-O/OTSiG|OCh-O_A_Sk function. At the top, four client ports are shown: OTSiG-O_CP[1], OTSiG-O_CP[n], OCh-O_CP[1], and OCh-O_CP[m]. Each port connects to a corresponding 'specific processes' block (OTSiG-O or OCh-O). These blocks contain 'Insert FDI-O', 'Insert FDI-P', and 'Consequent actions' sub-processes, which output various overhead signals (CI_OH, CI_SSF-P, CI_SSF-O). Below these, a central 'Overhead multiplexing' block (labeled 1...n and 1...m) receives inputs from the specific processes and outputs a 'Multiplex structure'. This structure is processed by 'Common processes', which include 'Extract MSI' and 'MSI process' blocks. The 'MSI process' outputs MI_cSIM[1..(n+m)], MI_cSIUM, MI_ExMSI[1..(n+m)], and MI_AcMSI[1..(n+m)]. A 'Defect correlation' block receives inputs from the 'Overhead multiplexing' and 'Common processes' and outputs MI_cSIM[1..(n+m)] and MI_cSIUM. The entire function is bounded by external interfaces: OMS-O/OTSiG|OCh-O_A_Sk_MECP on the left, OMS-O/OTSiG|OCh-O_A_Sk_MP on the right, and OMS-O_AP at the bottom. Internal signals include MECl_RxFSS, AL_TSF-P, and AL_TSF-O.](e404de9a69c05473fbd6af28ee32311b_img.jpg) + +Figure 10-15 – OMS-O/OTSiG|OCh-O\_A\_Sk processes. This block diagram illustrates the internal structure of the OMS-O/OTSiG|OCh-O\_A\_Sk function. At the top, four client ports are shown: OTSiG-O\_CP[1], OTSiG-O\_CP[n], OCh-O\_CP[1], and OCh-O\_CP[m]. Each port connects to a corresponding 'specific processes' block (OTSiG-O or OCh-O). These blocks contain 'Insert FDI-O', 'Insert FDI-P', and 'Consequent actions' sub-processes, which output various overhead signals (CI\_OH, CI\_SSF-P, CI\_SSF-O). Below these, a central 'Overhead multiplexing' block (labeled 1...n and 1...m) receives inputs from the specific processes and outputs a 'Multiplex structure'. This structure is processed by 'Common processes', which include 'Extract MSI' and 'MSI process' blocks. The 'MSI process' outputs MI\_cSIM[1..(n+m)], MI\_cSIUM, MI\_ExMSI[1..(n+m)], and MI\_AcMSI[1..(n+m)]. A 'Defect correlation' block receives inputs from the 'Overhead multiplexing' and 'Common processes' and outputs MI\_cSIM[1..(n+m)] and MI\_cSIUM. The entire function is bounded by external interfaces: OMS-O/OTSiG|OCh-O\_A\_Sk\_MECP on the left, OMS-O/OTSiG|OCh-O\_A\_Sk\_MP on the right, and OMS-O\_AP at the bottom. Internal signals include MECl\_RxFSS, AL\_TSF-P, and AL\_TSF-O. + +**Figure 10-15 – OMS-O/OTSiG|OCh-O\_A\_Sk processes** + +##### Defects: + +For each OTSiG-O or OCh-O client port #p: + +**dMSIM[p]:** See clause 6.2.9.3. + +##### Consequent actions + +The OMS-O/OTSiG|OCh-O\_A\_Sk function performs the following consequent actions. + +For each OTSiG-O or OCh-O client port #p: + +$aSSF-P[p] \leftarrow AI\_TSF-P \text{ or } dMSIM[p]$ + +$aFDI-P[p] \leftarrow AI\_TSF-P \text{ or } dMSIM[p]$ + +$aSSF-O[p] \leftarrow AI\_TSF-O \text{ or } dMSIM[p]$ + +$aFDI-O[p] \leftarrow AI\_TSF-O \text{ or } dMSIM[p]$ + +**Defect correlations:** None. + +**Performance monitoring:** None. + +## 10.4 Sub-layer functions + +For further study. + +# 11 OSC (layer) functions + +The supervision of the optical layer (as represented by the media element) is provided by non-associated overhead carried in an optical supervisory channel (OSC). This overhead is broken into multiple layers, in support of monitoring individual optical signals, an aggregated optical signal between a pair of optical multiplexers, and an aggregate optical signal between a pair of optical line amplifiers. This is analogous to the SDH concepts of a multiplex section and a regenerator section. + +The overhead for monitoring a single optical tributary signal is called Optical channel overhead (OCh-O). The overhead for monitoring a set of one or more optical tributary signals supporting one OTU is called Optical tributary signal group overhead (OTSiG-O). The overhead for monitoring the connection between a pair of optical multiplexers is called Optical Multiplex Section overhead (OMS-O). The overhead for monitoring the connection between an optical multiplexer and an optical amplifier, or a pair of optical amplifiers, is called Optical Transmission Section overhead (OTS-O). Figure 11-1 illustrates the relationship of the media element, the OSC, and the supervisory layers supporting the OTS and OMS maintenance entities. + +![Diagram illustrating the relationship of OSC and supervisory layers to media element. The diagram shows two main paths: one for OTU_TCP and one for OTUk_TCP, both converging on a central Media element. The OTU_TCP path includes layers OTSiG-O, OTSiG, OTSiA, and OTSi. The OTUk_TCP path includes layers OCh-O, OCh, and OTSi. Both paths lead to a common section labeled OTSiA | OCh. Below this, the diagram shows the hierarchy of supervisory layers: OMS-O, OTS-O, OSC, and OTSi, connected by various interfaces like OMS-P LOS, OTS-P LOS, and TCP layers.](e9f6a9e6beb9ae97b392bf38b93ad748_img.jpg) + +The diagram illustrates the relationship between the Media element and various supervisory layers. At the top, two paths are shown: + + +- OTU\_TCP path:** OTU\_TCP → OTSiA/OTU (1 to n) → OTSi (1 to n) → OTSiG → OTSiA → OTSi → Media element. +- OTUk\_TCP path:** OTUk\_TCP → OCh/OTUk → OTSi → OCh-O → OCh → Media element. + + Both paths converge at a section labeled **OTSiA | OCh**. Below this, the diagram shows the hierarchy of supervisory layers: + + +- From the Media element, an **OMS-P LOS** signal goes to **OMS-O**. +- From the Media element, an **OTS-P LOS** signal goes to **OTS-O**. +- The **Media element** is also connected to a section labeled **OTSIG-O\_CP or OCh-O\_CP**. +- From **OTSIG-O\_CP or OCh-O\_CP**, the signal goes to **OMS-O/OTSiG | OCh-O**. +- From **OMS-O/OTSiG | OCh-O**, the signal goes to **OMS-O**. +- From **OMS-O**, the signal goes to **OMS-O\_TCP**. +- From **OMS-O\_TCP**, the signal goes to **OTS-O/OMS-O**. +- From **OTS-O/OMS-O**, the signal goes to **OTS-O**. +- From **OTS-O**, the signal goes to **OTS-O\_TCP**. +- From **OTS-O\_TCP**, the signal goes to **OSC-O/OTS-O**. +- From **OSC-O/OTS-O**, the signal goes to **OSC**. +- From **OSC**, the signal goes to **OSC\_TCP**. +- From **OSC\_TCP**, the signal goes to **OTSi/OSC**. +- From **OTSi/OSC**, the signal goes to **OTSi**. +- Finally, the **OTSi** signal goes to the **WDM signal**. + + Additionally, there are labels for **AI\_TSF** and **OTSiG-O\_TCP** and **OCh-O\_TCP** associated with the top paths. + +Diagram illustrating the relationship of OSC and supervisory layers to media element. The diagram shows two main paths: one for OTU\_TCP and one for OTUk\_TCP, both converging on a central Media element. The OTU\_TCP path includes layers OTSiG-O, OTSiG, OTSiA, and OTSi. The OTUk\_TCP path includes layers OCh-O, OCh, and OTSi. Both paths lead to a common section labeled OTSiA | OCh. Below this, the diagram shows the hierarchy of supervisory layers: OMS-O, OTS-O, OSC, and OTSi, connected by various interfaces like OMS-P LOS, OTS-P LOS, and TCP layers. + +G.798(17)-Cor.1(18)\_F11-1 + +Figure 11-1 – Relationship of OSC and supervisory layers to media element + +Figure 11-2 illustrates the OSC layer network and client layer adaptation functions. The information crossing the OSC termination connection point (OSC\_TCP) is referred to as the OSC characteristic information (OSC\_CI). The information crossing the OSC access point (OSC\_AP) is referred to as the OSC adapted information (OSC\_AI). + +![Figure 11-2: OSC layer network and client layer adaptation functions diagram. It shows three client layers (OTS-O, COMMS, SD) connected to an OSC layer via their respective connection points (OTS-O_CP, COMMS_CP, SD_CP). The OSC layer is connected to the OSC_TCP at the bottom via the OSC_AP.](dbfe5a97dc7e71fd9ae813d4bb865e29_img.jpg) + +The diagram illustrates the adaptation functions at the OSC layer. At the top, three client layers are shown: OTS-O, COMMS, and SD. Each client layer has a connection point (OTS-O\_CP, COMMS\_CP, SD\_CP) that connects to a corresponding OSC client adaptation block (OSC/OTS-O, OSC/COMMS, OSC/SD). These blocks are connected to a central OSC layer. The OSC layer has an access point (OSC\_AP) at the top and a termination connection point (OSC\_TCP) at the bottom. + +Figure 11-2: OSC layer network and client layer adaptation functions diagram. It shows three client layers (OTS-O, COMMS, SD) connected to an OSC layer via their respective connection points (OTS-O\_CP, COMMS\_CP, SD\_CP). The OSC layer is connected to the OSC\_TCP at the bottom via the OSC\_AP. + +G.798(17)\_F11-2 + +**Figure 11-2 – OSC layer network and client layer adaptation functions** + +The OSC adapted information is a logical signal that contains the OTS-O, OMS-O, OCh-O and OTSiG-O logical information elements. The OSC\_AI may also contain general management communications and an OTN synchronization message channel (OSMC). + +The specific OSC\_AI format is outside the scope of this Recommendation. In addition, vendor-specific overhead might be supported via the OSC\_AI. This is outside the scope of this Recommendation. + +![Figure 11-3: OSC adapted information diagram. It shows the hierarchical structure of the OSC adapted information, starting with the OSC layer containing OSMC and COMMS. The OTS-O layer contains TTI, BDI-P, BDI-O, and PMI. The OMS-O layer contains MSI, FDI-P, FDI-O, BDI-P, BDI-O, and PMI. The OTSiG-O[n] layer contains OTSiG-O[2], OTSiG-O[1], TSI, TTI, FDI-P, FDI-O, OCI, BDI-P, and BDI-O. The OCh-O[n] layer contains OCh-O[2], OCh-O[1], FDI-P, FDI-O, and OCI.](c2f36c545b190860d04e1d84e58d22cc_img.jpg) + +The diagram shows the structure of the OSC adapted information. The OSC layer contains OSMC and COMMS. The OTS-O layer contains TTI, BDI-P, BDI-O, and PMI. The OMS-O layer contains MSI, FDI-P, FDI-O, BDI-P, BDI-O, and PMI. The OTSiG-O[n] layer contains OTSiG-O[2], OTSiG-O[1], TSI, TTI, FDI-P, FDI-O, OCI, BDI-P, and BDI-O. The OCh-O[n] layer contains OCh-O[2], OCh-O[1], FDI-P, FDI-O, and OCI. + +Figure 11-3: OSC adapted information diagram. It shows the hierarchical structure of the OSC adapted information, starting with the OSC layer containing OSMC and COMMS. The OTS-O layer contains TTI, BDI-P, BDI-O, and PMI. The OMS-O layer contains MSI, FDI-P, FDI-O, BDI-P, BDI-O, and PMI. The OTSiG-O[n] layer contains OTSiG-O[2], OTSiG-O[1], TSI, TTI, FDI-P, FDI-O, OCI, BDI-P, and BDI-O. The OCh-O[n] layer contains OCh-O[2], OCh-O[1], FDI-P, FDI-O, and OCI. + +G.798(17)\_F11-3 + +**Figure 11-3 – OSC adapted information** + +## 11.1 Connection functions + +Not applicable. + +## 11.2 Termination functions + +### 11.2.1 OSC trail termination function (OSC\_TT) + +The OSC\_TT functions are responsible for the end-to-end supervision of the OSC trail. Figure 11-4 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Diagram of OSC_TT function showing two unidirectional OSC blocks. The left block has an input OSC_AP at the top, an OSC block in the middle, and an output OSC_TCP at the bottom. The right block has an input OSC_TCP at the bottom, an OSC block in the middle, and an output OSC_AP at the top. The diagram is labeled G.798(17)_F11-4.](4a390493f601ce1ac6b9201db4e28b5a_img.jpg) + +Diagram illustrating the OSC\_TT function. It consists of two unidirectional OSC blocks. The left block shows an input OSC\_AP entering the OSC block from the top, and an output OSC\_TCP exiting from the bottom. The right block shows an input OSC\_TCP entering the OSC block from the bottom, and an output OSC\_AP exiting from the top. The diagram is labeled G.798(17)\_F11-4. + +Diagram of OSC\_TT function showing two unidirectional OSC blocks. The left block has an input OSC\_AP at the top, an OSC block in the middle, and an output OSC\_TCP at the bottom. The right block has an input OSC\_TCP at the bottom, an OSC block in the middle, and an output OSC\_AP at the top. The diagram is labeled G.798(17)\_F11-4. + +Figure 11-4 – OSC\_TT + +#### 11.2.1.1 OSC trail termination source function (OSC\_TT\_So) + +The information flow and processing of the OSC\_TT\_So functions is defined with reference to Figure 11-5. The OSC\_TT\_So function generates an optical signal. + +##### Symbol + +![Diagram of OSC_TT_So function showing a single OSC block. An input OSC_AP enters the OSC block from the top, and an output OSC_TCP exits from the bottom. The diagram is labeled G.798(17)_F11-5.](747516f5861a0ddf31e3851da8e34b95_img.jpg) + +Diagram illustrating the OSC\_TT\_So function. It shows a single OSC block. An input OSC\_AP enters the OSC block from the top, and an output OSC\_TCP exits from the bottom. The diagram is labeled G.798(17)\_F11-5. + +Diagram of OSC\_TT\_So function showing a single OSC block. An input OSC\_AP enters the OSC block from the top, and an output OSC\_TCP exits from the bottom. The diagram is labeled G.798(17)\_F11-5. + +Figure 11-5 – OSC\_TT\_So function + +##### Interfaces + +Table 11-1 – OSC\_TT\_So inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------|-------------------------------------------| +| OSC_AP:
OSC_AI_OH
OSC_AI_CK | OSC_TCP:
OSC_CI_OH
OSC_CI_CK | + +##### Processes + +The specific processes are outside the scope of this Recommendation. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 11.2.1.2 OSC trail termination sink function (OSC\_TT\_Sk) + +The OSC\_TT\_Sk reports the state of the OSC trail. + +The information flow and processing of the OSC\_TT\_Sk function is defined with reference to Figure 11-6. + +##### Symbol + +![Diagram of the OSC_TT_Sk function symbol. It shows a triangle labeled 'OSC'. An arrow points from 'OSC_TCP' at the bottom to the triangle. An arrow points from the triangle to 'OSC_AP' at the top. A double-headed arrow points from 'OSC_TT_Sk_MP' on the left to the triangle. The text 'G.798(17)_F11-6' is at the bottom right.](b71ad9fc874230de9ba4480e12a216f7_img.jpg) + +G.798(17)\_F11-6 + +Diagram of the OSC\_TT\_Sk function symbol. It shows a triangle labeled 'OSC'. An arrow points from 'OSC\_TCP' at the bottom to the triangle. An arrow points from the triangle to 'OSC\_AP' at the top. A double-headed arrow points from 'OSC\_TT\_Sk\_MP' on the left to the triangle. The text 'G.798(17)\_F11-6' is at the bottom right. + +**Figure 11-6 – OSC\_TT\_Sk function** + +##### Interfaces + +**Table 11-2 – OSC\_TT\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------|----------------------------------------------------------| +| OSC_TCP:
OSC_CI_OH
OSC_CI_CK
OSC_CI_SSF | OSC_AP:
OSC_AI_OH
OSC_AI_CK
OSC_AI_TSF-O | + +##### Processes + +The specific processes are outside the scope of this Recommendation. + +**Defects:** None. + +##### Consequent actions + +The OSC\_TT\_Sk function shall perform the following consequent action: + +aTSF-O ← CI\_SSF + +**Defect correlations:** None. + +**Performance monitoring:** None. + +## 11.3 Adaptation functions + +The OSC is server for the following clients: + +- optical transport section overhead (OTS-O); +- general management communications (COMMS); +- OTN synchronization distribution channel. + +### 11.3.1 OSC to OTS-O adaptation function (OSC/OTS-O\_A) + +The OSC to OTS-O adaptation functions perform the adaptation between the OSC layer adapted information and the OTS-O layer characteristic information. + +#### 11.3.1.1 OSC to OTS-O adaptation source function (OSC/OTS-O\_A\_So) + +The information flow and processing of the OSC/OTS-O\_A\_So function is defined with reference to Figures 11-7 and 11-8. + +##### Symbol + +![Symbol diagram for OSC/OTS-O_A_So function. It shows a downward flow from OTS-O_CP to a trapezoidal block labeled OSC/OTS-O, which then outputs to OSC_AP. The reference G.798(17)_F11-7 is noted at the bottom right.](64323b705244afc70bf77babdacb6ce5_img.jpg) + +OTS-O\_CP + +OSC/OTS-O + +OSC\_AP + +G.798(17)\_F11-7 + +Symbol diagram for OSC/OTS-O\_A\_So function. It shows a downward flow from OTS-O\_CP to a trapezoidal block labeled OSC/OTS-O, which then outputs to OSC\_AP. The reference G.798(17)\_F11-7 is noted at the bottom right. + +Figure 11-7 – OSC/OTS-O\_A\_So function + +##### Interfaces + +Table 11-3 – OSC/OTS-O\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|--------------------------|----------------------| +| OTS-O_CP:
OTS-O_CI_OH | OSC_AP:
OSC_AI_OH | + +##### Processes + +The processes associated with the OSC/OTS-O\_A\_So function are depicted in Figure 11-8. + +![Process diagram for OSC/OTS-O_A_So. It shows a rectangular block divided into two vertical sections. The left section is labeled OTS-O_CP and CI_OH. The right section is labeled AI_OH and OSC_AP. A downward arrow is shown in the right section. The reference G.978(17)_F11-8 is noted at the bottom right.](34f46103a0c07981b0b51490ea639e25_img.jpg) + +OTS-O\_CP + +CI\_OH + +AI\_OH + +OSC\_AP + +G.978(17)\_F11-8 + +Process diagram for OSC/OTS-O\_A\_So. It shows a rectangular block divided into two vertical sections. The left section is labeled OTS-O\_CP and CI\_OH. The right section is labeled AI\_OH and OSC\_AP. A downward arrow is shown in the right section. The reference G.978(17)\_F11-8 is noted at the bottom right. + +Figure 11-8 – OSC/OTS-O\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 11.3.1.2 OSC to OTS-O adaptation sink function (OSC/OTS-O\_A\_Sk) + +The information flow and processing of the OSC/OTS-O\_A\_Sk function is defined with reference to Figure 11-9 and 11-10. + +##### Symbol + +![Symbol diagram for OSC/OTS-O_A_Sk function. It shows a trapezoidal block labeled 'OSC/OTS-O'. An arrow labeled 'OSC_AP' points into the block from below, and an arrow labeled 'OTS-O_CP' points out of the block from the top. The reference code 'G.798(17)_F11-9' is shown below the diagram.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +Symbol diagram for OSC/OTS-O\_A\_Sk function. It shows a trapezoidal block labeled 'OSC/OTS-O'. An arrow labeled 'OSC\_AP' points into the block from below, and an arrow labeled 'OTS-O\_CP' points out of the block from the top. The reference code 'G.798(17)\_F11-9' is shown below the diagram. + +Figure 11-9 – OSC/OTS-O\_A\_Sk function + +##### Interfaces + +Table 11-4 – OSC/OTS-O\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|---------------------------------------------|---------------------------------------------------| +| OSC_AP:
OSC_AI_OH
OSC_AI_TSF-O | OTS-O_CP:
OTS-O_CI_OH
OTS-O_CI_SSF-O | + +##### Processes + +The processes associated with the OSC/OTS-O\_A\_Sk function are depicted in Figure 11-10. + +![Process diagram for OSC/OTS-O_A_Sk. It shows a rectangular block with two vertical arrows pointing upwards. The left arrow is labeled 'AI_OH' at the bottom and 'CI_OH' at the top. The right arrow is labeled 'AI_TSF-O' at the bottom and 'CI_SSF-O' at the top. The label 'aSSF' is written vertically between the arrows. Below the block, the labels 'OSC_AP' and 'G.978(17)_F11-10' are present.](d15e2d3e8dd9157eb7f0cc120097484a_img.jpg) + +Process diagram for OSC/OTS-O\_A\_Sk. It shows a rectangular block with two vertical arrows pointing upwards. The left arrow is labeled 'AI\_OH' at the bottom and 'CI\_OH' at the top. The right arrow is labeled 'AI\_TSF-O' at the bottom and 'CI\_SSF-O' at the top. The label 'aSSF' is written vertically between the arrows. Below the block, the labels 'OSC\_AP' and 'G.978(17)\_F11-10' are present. + +Figure 11-10 – OSC/OTS-O\_A\_Sk processes + +**Defects:** None. + +##### Consequent actions + +The OSC/OTS-O\_A\_Sk function performs the following consequent actions. + +$aSSF \leftarrow AI\_TSF-O$ + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 11.3.2 OSC to COMMS adaptation function (OSC/COMMS\_A) + +The OSC to COMMS adaptation functions provide access to the Communication Channel overhead in the OSC for generic data communication. The format of the OSC Communication Channel overhead is outside the scope of this Recommendation. + +#### 11.3.2.1 OSC to COMMS adaptation source function (OSC/COMMS\_A\_So) + +The OSC/COMMS\_A\_So function maps the communication channel data into the OSC Communication Channel overhead. + +The information flow and processing of the OSC/COMMS\_A\_So functions is defined with reference to Figure 11-11. + +##### Symbol + +![Diagram of the OSC/COMMS_A_So function symbol. It shows an input labeled COMMS_CP entering a trapezoidal block labeled OSC/COMMS from the top. An output labeled OSC_AP exits the block from the bottom. The diagram is labeled G.798(17)_F11-11.](b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg) + +``` +graph TD; COMMS_CP --> OSC_COMMS[OSC/COMMS]; OSC_COMMS --> OSC_AP; +``` + +Diagram of the OSC/COMMS\_A\_So function symbol. It shows an input labeled COMMS\_CP entering a trapezoidal block labeled OSC/COMMS from the top. An output labeled OSC\_AP exits the block from the bottom. The diagram is labeled G.798(17)\_F11-11. + +Figure 11-11 – OSC/COMMS\_A\_So function + +##### Interfaces + +Table 11-5 – OSC/COMMS\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------|----------------------------------------------------------------| +| COMMS_CP:
COMMS_CI_D
OSC_AP:
OSC_AI_CK
OSC_AI_FS | COMMS_CP:
COMMS_CI_CK
OSC_AP:
OSC_AI_OH | + +##### Processes + +The function shall insert the COMMS data into the OSC Communication Channel overhead. The specific processes are outside the scope of this Recommendation. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 11.3.2.2 OSC to COMMS adaptation sink function (OSC/COMMS\_A\_Sk) + +The OSC/COMMS\_A\_Sk extracts the COMMS data from the OSC Communication Channel overhead. + +The information flow and processing of the OSC/COMMS\_A\_Sk functions is defined with reference to Figure 11-12. + +##### Symbol + +![Symbol diagram for OSC/COMMS_A_Sk function. It shows a trapezoidal block labeled 'OSC/COMMS'. An arrow labeled 'OSC_AP' points into the block from below, and an arrow labeled 'COMMS_CP' points out of the block from the top. The reference 'G.798(17)_F11-12' is shown below the block.](dae88eec6d1005984029b794ff8b7a9e_img.jpg) + +Symbol diagram for OSC/COMMS\_A\_Sk function. It shows a trapezoidal block labeled 'OSC/COMMS'. An arrow labeled 'OSC\_AP' points into the block from below, and an arrow labeled 'COMMS\_CP' points out of the block from the top. The reference 'G.798(17)\_F11-12' is shown below the block. + +Figure 11-12 – OSC/COMMS\_A\_Sk function + +##### Interfaces + +Table 11-6 – OSC/COMMS\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|---------------------------------------------------------------------|---------------------------------------------------------------| +| OSC_AP:
OSC_AI_CK
OSC_AI_OH
OSC_AI_FS
OSC_AI_TSF | COMMS_CP:
COMMS_CI_CK
COMMS_CI_D
COMMS_CI_SSF | + +##### Processes + +The function shall extract the COMMS data from the OSC communication channel overhead. The specific processes are outside the scope of this Recommendation. + +**Defects:** None. + +##### Consequent actions + +The function shall perform the following consequent actions: + +aSSF ← AI\_TSF + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 11.3.3 OSC to synchronization distribution adaptation functions + +OSC to synchronization distribution (SD) adaptation functions are given in clause 8.11 of [ITU-T G.781]. + +# 12 OTSiA and OCh (layer) functions + +Figure 12-1 illustrates the OTSiG-O|OCh-O layer network and connectivity to the OTSi|OTSiG to OTUk[V]|OTUCn|FlexO|OSC adaptation functions. + +![Figure 12-1: OTSiG-O and OCh-O layer network and client layer adaptation functions. This complex block diagram illustrates the functional architecture of optical transport network layers. At the top, multiple client layer inputs are shown: OTSi/OTUk, OTSiG/OTUk, OTSi/OTUCn, and OTSiG/OTUCn. These feed into OTSi blocks, which then connect to OCh-O and OTSiG-O adaptation functions. The diagram shows multiple parallel paths for these signals, labeled with '1...n' to indicate multiple instances. These paths converge into a central 'Media element' block. To the right of the media element, a vertical stack of monitoring and overhead processing blocks is shown, including OMS-P LOS, OMS-O, OTS-P LOS, OTS-O, OSC/OTS-O, OSC, OTSi/OSC, and OTSi. Various signal types like OTSiA, OCh, and OTSiG are labeled throughout the interconnection network. The label 'MOTUm' is at the bottom of the media element, and 'G.798(17)_F12-1' is in the bottom right corner.](d1ad05f1189b0d80188fee24ae33c112_img.jpg) + +Figure 12-1: OTSiG-O and OCh-O layer network and client layer adaptation functions. This complex block diagram illustrates the functional architecture of optical transport network layers. At the top, multiple client layer inputs are shown: OTSi/OTUk, OTSiG/OTUk, OTSi/OTUCn, and OTSiG/OTUCn. These feed into OTSi blocks, which then connect to OCh-O and OTSiG-O adaptation functions. The diagram shows multiple parallel paths for these signals, labeled with '1...n' to indicate multiple instances. These paths converge into a central 'Media element' block. To the right of the media element, a vertical stack of monitoring and overhead processing blocks is shown, including OMS-P LOS, OMS-O, OTS-P LOS, OTS-O, OSC/OTS-O, OSC, OTSi/OSC, and OTSi. Various signal types like OTSiA, OCh, and OTSiG are labeled throughout the interconnection network. The label 'MOTUm' is at the bottom of the media element, and 'G.798(17)\_F12-1' is in the bottom right corner. + +**Figure 12-1 – OTSiG-O and OCh-O layer network and client layer adaptation functions** + +The OCh-O characteristic information (OCh-O\_CI) contains the logical information elements for maintenance and operational functions to support the OCh maintenance entity. Figure 12-2 illustrates the overhead information elements that shall be supported across the OCh-O\_CP. + +![Figure 12-2: Information elements at OCh-O_CP/TCP. A rectangular box labeled 'OCh-O_CI' contains three vertically stacked smaller boxes labeled 'FDI-P', 'FDI-O', and 'OCI'. Below the main box is the reference 'G.798(17)_F12-2'.](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +Figure 12-2: Information elements at OCh-O\_CP/TCP. A rectangular box labeled 'OCh-O\_CI' contains three vertically stacked smaller boxes labeled 'FDI-P', 'FDI-O', and 'OCI'. Below the main box is the reference 'G.798(17)\_F12-2'. + +G.798(17)\_F12-2 + +**Figure 12-2 – Information elements at OCh-O\_CP/TCP** + +The OTSiG-O characteristic information (OTSiG-O\_CI) contains the logical information elements for maintenance and operational functions to support the OTSiA maintenance entity. Figure 12-3 illustrates the overhead information elements that shall be supported across the OTSiG-O\_CP. + +![Diagram showing information elements at OTSiG-O_CP/TCP. A vertical stack of seven boxes is shown, labeled from top to bottom: TSI, TTI, FDI-P, FDI-O, OCI, BDI-P, and BDI-O. To the left of the stack is the label OTSiG-O_CI. Below the diagram is the text G.798(17)_F12-3.](811d62d08ce934a2a7e5bd877abff7ad_img.jpg) + +G.798(17)\_F12-3 + +Diagram showing information elements at OTSiG-O\_CP/TCP. A vertical stack of seven boxes is shown, labeled from top to bottom: TSI, TTI, FDI-P, FDI-O, OCI, BDI-P, and BDI-O. To the left of the stack is the label OTSiG-O\_CI. Below the diagram is the text G.798(17)\_F12-3. + +**Figure 12-3 – Information elements at OTSiG-O\_CP/TCP** + +## 12.1 Connection functions + +### 12.1.1 OTSiA|OCh connection function (OTSiA|OCh\_C) + +The OTSiA|OCh connection function represents an abstraction of two separate functions. The connection of the OTSiG or OTSi occurs inside a media element; the connection of the overhead is done via the OTSiG|OCh-O\_C. The MI\_MatrixControl signal configures both the OTSiG|OTSi and OTSiG|OCh-O. + +The information flow and processing of the OTSiA|OCh\_C function is defined with reference to Figures 12-4 and 12-5. The OTSiA|OCh\_C function connects media channel points (for the purpose to forward OTSiG or OTSi) and OCh-O or OTSiG-O connection points (for the purpose to forward OCh-O or OTSiG-O characteristic information) from its input ports to its output ports. As the process does not affect the nature of characteristic information, the reference points on either side of the OTSiA|OCh\_C function are the same as illustrated in Figure 12-4. + +The connection process is unidirectional and, as such, no differentiation in sink and source is required. In addition, the OTSiA|OCh\_C function supports the following subnetwork connection protection scheme: + +- 1+1 unidirectional SNC/N. + +Other protection schemes are for further study. + +NOTE 1 – The protection processes have a dedicated sink and source behaviour. + +##### Symbol + +![Diagram of the OTSiA|OCh_C function symbol. The central element is an oval labeled 'OTSiA|OCh_C'. Above and below this oval are horizontal lines of pink circles labeled 'Media channel points'. Above the top line of points is a pink rectangular box labeled 'Zero or more OTSi per MCP'. Above this box are input arrows labeled 'OTSiGs' and 'OTSis', each with a sub-label 'l' and 'm'. Below the bottom line of points is another pink rectangular box labeled 'Zero or more OTSi per MCP'. Below this box are output arrows labeled 'OTSiGs' and 'OTSis', each with a sub-label 'l' and 'm'. To the right of the central oval, there are input arrows labeled 'OTSiG-O_CP' and 'OCh_O_CP', and output arrows labeled 'OTSiG-O_CPs' and 'OCh_O_CPs'. An arrow points from the right side of the oval to a label 'OTSiA|OCh_C_MP'. A small text 'G.798(17)-Amd.2(19)_F12-4' is at the bottom right.](66bf96eec8f739d5e7c9957a178e34e2_img.jpg) + +Diagram of the OTSiA|OCh\_C function symbol. The central element is an oval labeled 'OTSiA|OCh\_C'. Above and below this oval are horizontal lines of pink circles labeled 'Media channel points'. Above the top line of points is a pink rectangular box labeled 'Zero or more OTSi per MCP'. Above this box are input arrows labeled 'OTSiGs' and 'OTSis', each with a sub-label 'l' and 'm'. Below the bottom line of points is another pink rectangular box labeled 'Zero or more OTSi per MCP'. Below this box are output arrows labeled 'OTSiGs' and 'OTSis', each with a sub-label 'l' and 'm'. To the right of the central oval, there are input arrows labeled 'OTSiG-O\_CP' and 'OCh\_O\_CP', and output arrows labeled 'OTSiG-O\_CPs' and 'OCh\_O\_CPs'. An arrow points from the right side of the oval to a label 'OTSiA|OCh\_C\_MP'. A small text 'G.798(17)-Amd.2(19)\_F12-4' is at the bottom right. + +Figure 12-4 – OTSiA|OCh\_C function + +##### Interfaces + +Table 12-1 – OTSiA|OCh\_C function inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Per MCP
Zero or more OTSi_CI
Per OTSiG-O_CP:
OTSiG-O_CI_OH
OTSiG-O_CI_SSF-P
OTSiG-O_CI_SSF-O
OTSiG-O_CI_TSF-P (Note)
Per OCh-O_CP:
OCh-O_CI_OH
OCh-O_CI_SSF-P
OCh-O_CI_SSF-O
OCh-O_CI_TSF-P (Note)
OTSiA OCh_C_MP:
OTSiA OCh_C_MI_MatrixControl
Per protection group:
OTSiA OCh_C_MI_OperType
OTSiA OCh_C_MI_WTR
OTSiA OCh_C_MI_HoTime
OTSiA OCh_C_MI_ExtCMD
OTSiA OCh_C_MI_TSF-ODis | Per MCP
Zero or more OTSi_CI
Per OTSiG-O_CP:
OTSiG-O_CI_OH
OTSiG-O_CI_SSF-P
OTSiG-O_CI_SSF-O
Per OCh-O_CP:
OCh-O_CI_OH
OCh-O_CI_SSF-P
OCh-O_CI_SSF-O

OTSiA OCh_C_MP:
For further study | +| NOTE – In case of SNC/N protection. | | + +##### Processes + +The processes associated with the OTSi|OCh\_C function are as depicted in Figure 12-5. + +OTSi|OCh\_CI is routed between input and output media channel points and overhead and maintenance signal connection points by means of one or more matrix media channel connections and an overhead and maintenance signal a matrix connection. Connection points may be allocated within a protection group. + +NOTE 2 – Neither the number of input/output signals to the connection function, nor the connectivity, is specified in this Recommendation. That is a property of individual network elements. Examples of connectivity are given in Appendix I of [ITU-T G.806]. + +**Routing:** The function shall be able to connect a specific input with a specific output by means of establishing a matrix overhead/maintenance signal channel/connection (MOMSC) and/or a matrix media channel (MMC) between the specified input and output, and it shall be able to remove an established MOMSC and/or MMC as defined by MI\_MatrixControl. + +The matrix control in this case refers to both the configuration of the media element to achieve the desired payload connectivity and/or the configuration of the OTSi|OCh-O\_C to achieve the desired overhead and maintenance signal connectivity. + +Three cases are supported: + +- 1) **MMC** only command; +*this is the first portion of case 1 of [ITU-T G.872]. i.e., pre-configure matrix media channels* +- 2) **MOMSC** only command; +*this is the second portion of case 1 of [ITU-T G.872]. i.e., configure the overhead connectivity (given that there already exist the pre-configure matrix media channels)* +- 3) **MMC+MOMSC** command; +*this is case 2 of [ITU-T G.872], i.e., configure both the matrix media channels and overhead connectivity at the same time* + +by the following commands: + +- Command: Establish MMC + - Pre-condition: no MMC, no MOMSC + - Post-condition: MMC created, no MOMSC +- Command: Remove MMC + - Pre-condition: MMC exist, no MOMSC + - Post-condition: MMC removed, no MOMSC +- Command: Establish MOMSC + - Pre-condition: MMC exist, no MOMSC + - Post-condition: MMC exist, MOMSC created +- Command: Remove MOMSC + - Pre-condition: MMC exist, MOMSC exist + - Post-condition: MMC exist, MOMSC removed +- Command: Establish MMC + MOMSC + - Pre-condition: no MMC, no MOMSC + - Post-condition: MMC created, MOMSC created +- Command: Remove MMC + MOMSC + - Pre-condition: MMC exist, MOMSC exist + +- Post-condition: MMC removed, MOMSC removed + +Each (matrix) connection in the OTSiA|OCh\_C function should be characterized by the: + +- type of connection: unprotected, 1+1 unidirectional protected; +- traffic direction: unidirectional, bidirectional; +- input and output media channel points and/or overhead and maintenance signal connection points: set of media channel points and/or overhead and maintenance signal connection points. + +NOTE 3 – Broadcast connections are handled as separate connections to the same CP. + +NOTE 4 – For the case a network element supports 1+1 protected matrix connections in its OTSiA|OCh\_C function, this function may contain at any moment in time either all unprotected matrix connections, or all 1+1 protected matrix connections, or a mixture of unprotected and 1+1 protected matrix connections. The actual set of matrix connections and associated connection types and directions are operational parameters controlled by network management. + +Provided no protection switching action is activated/required, the following changes to (the configuration of) a connection shall be possible without disturbing the CI passing the connection: + +- addition and removal of protection; +- addition and removal of connections to/from a broadcast connection; +- change of WTR time; +- change of operation type; +- change of hold-off time. + +**Open connection indication (OCI):** If an output of the connection function is not connected to an input, the OCI maintenance signal is generated for the outgoing signal (CI\_OH). CI\_SSF-P and CI\_SSF-O are false. + +![Figure 12-5 – OTSiA|OCh-O_C function processes. The diagram illustrates the internal structure of an OTSiA|OCh-O_C function. On the left, OTSiGs and OTSis are shown entering and exiting a 'Media element' through 'Media channel points'. A 'Coordination To/from media element' is indicated. The central part is a 'Matrix connection' block, which is part of the OTSiA|OCh_C_MP function. This block has multiple input and output ports. Each port is associated with a set of signals: CI_OH, CI_SSF-P, and CI_SSF-O. The matrix connection itself is shown as a large rectangle with 'OCI' (Open Connection Indication) blocks at the input and output. The signals are labeled 'x-O_CP' at the top and bottom of the matrix connection. The diagram also shows 'Zero or more OTSi per MCP' (Media Channel Point) labels at the top and bottom of the media element. The overall structure shows the flow of signals through the matrix connection within the OTSiA|OCh_C_MP function.](4a5c6fefcac9340ea7f9df373873cae9_img.jpg) + +Figure 12-5 – OTSiA|OCh-O\_C function processes. The diagram illustrates the internal structure of an OTSiA|OCh-O\_C function. On the left, OTSiGs and OTSis are shown entering and exiting a 'Media element' through 'Media channel points'. A 'Coordination To/from media element' is indicated. The central part is a 'Matrix connection' block, which is part of the OTSiA|OCh\_C\_MP function. This block has multiple input and output ports. Each port is associated with a set of signals: CI\_OH, CI\_SSF-P, and CI\_SSF-O. The matrix connection itself is shown as a large rectangle with 'OCI' (Open Connection Indication) blocks at the input and output. The signals are labeled 'x-O\_CP' at the top and bottom of the matrix connection. The diagram also shows 'Zero or more OTSi per MCP' (Media Channel Point) labels at the top and bottom of the media element. The overall structure shows the flow of signals through the matrix connection within the OTSiA|OCh\_C\_MP function. + +Figure 12-5 – OTSiA|OCh-O\_C function processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 12.1.1.1 Subnetwork connection protection process + +NOTE – This process is active in the OTSiA|OCh\_C function as many times as there are 1+1 protected matrix connections. + +The basic subnetwork connection protection mechanism is identical to the SDH subnetwork connection process described in [ITU-T G.841]. + +SNC protection with non-intrusive monitoring (SNC/N) is supported. + +Figure 12-6 gives the atomic functions involved in SNC/N protection. The working and protection OTSiG-O or OCh-O CI coming from an OMS-O/OTSiG|OCh-O\_A function are monitored by an OTSiG-O or OCh-O non-intrusive monitor, which provides the TSF-P protection switching criteria. + +![Diagram of SNC/N protection atomic functions showing signal flow between OTSiA|OCh_C, Media element, and OMS-O/OTSiG|OCh-O functions.](107cbeda15ddd53da92c2f677b441c93_img.jpg) + +The diagram illustrates the atomic functions for SNC/N protection. At the top, a central oval represents the **OTSiA|OCh\_C** function. Above it, under the heading **Normal (protected)**, are two sets of input signals labeled **1** and **m**, with text indicating they are **OTSiG or OTSia)** and **OTSiA or OCh**. Below the central oval, on the left, is a **Media element** block. To its left, **Working OTSiG or OTSia)** signals (labeled **1** and **m**) enter the media element. To its right, **Protection OTSiG or OTSia)** signals (also labeled **1** and **m**) exit the media element. Below the media element, four trapezoidal blocks represent **OMS-O/OTSiG|OCh-O** functions. The first and third blocks have downward-pointing arrows, while the second and fourth have upward-pointing arrows. Between the second and third blocks, a **Working x-O\_CI** signal is shown entering the second block. Between the third and fourth blocks, a **Protection x-O\_CI** signal is shown exiting the fourth block. Both **Working x-O\_CI** and **Protection x-O\_CI** signals pass through a non-intrusive monitor block labeled **x-Om**. Above each **x-Om** block is a **TSF-P** (Traffic Switching Function - Protection) block, connected by dashed lines. At the bottom, a note states **a) m equals 1 for OTSi**. Another note at the bottom right indicates **x = OTSiG or OCh**. The diagram is identified by the code **G.798(17)\_F12-6**. + +Diagram of SNC/N protection atomic functions showing signal flow between OTSiA|OCh\_C, Media element, and OMS-O/OTSiG|OCh-O functions. + +**Figure 12-6 – SNC/N protection atomic functions** + +The protection functions at both ends operate the same way, by monitoring working and protection subnetwork connections for defects, evaluating the system status taking into consideration the priorities of defect conditions and of external switch requests, and switching the appropriate channel to the protected (sub)network connection. + +The signal flow associated with the OTSiA|OCh\_C SNC protection process is described with reference to Figure 12-7. The protection process receives control parameters and external switch requests at the MP reference point. The report of status information at the MP reference point is for further study. + +![Diagram of SNC/N protection process showing signal flow between two nodes. Each node has a 'Normal (protected)' block containing 'Working' and 'Protection' sub-blocks. Signals from OTSiG or OTSi (with m parallel paths) enter the 'Normal (protected)' block and are distributed to both 'Working' and 'Protection' sub-blocks. The 'Working' sub-blocks output signals to OTSiG or OTSi (with m parallel paths). The 'Protection' sub-blocks output signals to x-O_CP (where x = OTSiG or OCh). A 'Coordination' link connects the two nodes. The right node also receives an OTSiA | OCh_C_MP signal. A note indicates 'a) m equals 1 for OTSi'.](ca86f53f9735fe98b6c6003d1b759f64_img.jpg) + +a) m equals 1 for OTSi + +G.798(17)\_F12-7 + +Diagram of SNC/N protection process showing signal flow between two nodes. Each node has a 'Normal (protected)' block containing 'Working' and 'Protection' sub-blocks. Signals from OTSiG or OTSi (with m parallel paths) enter the 'Normal (protected)' block and are distributed to both 'Working' and 'Protection' sub-blocks. The 'Working' sub-blocks output signals to OTSiG or OTSi (with m parallel paths). The 'Protection' sub-blocks output signals to x-O\_CP (where x = OTSiG or OCh). A 'Coordination' link connects the two nodes. The right node also receives an OTSiA | OCh\_C\_MP signal. A note indicates 'a) m equals 1 for OTSi'. + +**Figure 12-7 – SNC/N protection process** + +##### *Source direction* + +For 1+1 architecture, the CI coming from the normal (protected) OTSiG or OTSi and OTSiG-O or OCh-O CP is bridged permanently to both the working and protection OTSiG or OTSi and OTSiG-O or OCh-O CP. + +##### *Sink direction* + +For a 1+1 architecture, the CI coming either from the working or protection OTSiG or OTSi and OTSiG-O or OCh-O CP is switched to the normal (protected) OTSiG or OTSi and OTSiG-O or OCh-O CP. A switchover from working to protection OTSiG or OTSi and OTSiG-O or OCh-O CP, or vice versa, is initiated by the switch initiation criteria defined below. + +##### *Switch initiation criteria* + +Automatic protection switching is based on the defect conditions of the working and protection (sub)network connections. These condition(s) are for SNC/N trail signal fail payload (TSF-P) and trail signal fail overhead (TSF-O). The use of TSF-O as protection switching criteria can be disabled (MI\_TSF-ODis). The priority of TSF-P shall be equal to signal fail as defined in [ITU-T G.841]. The priority of TSF-O shall be equal to signal degrade as defined in [ITU-T G.841]. + +In order to allow interworking between nested protection schemes, a hold-off timer is provided. The hold-off timer delays switch initiation in case of signal fail in order to allow a nested protection to react and clear the fault condition. The hold-off timer is started by the activation of signal fail and runs for the hold-off time. Protection switching is only initiated if signal fail is still present at the end of the hold-off time. The hold-off time shall be provisionable between 0 and 10 s in steps of 100 ms. + +Protection switching can also be initiated by external switch commands received via the MP. + +Depending on the mode of operation, internal states (e.g., wait to restore) may also initiate a switch over. See the switch initiation criteria described in [ITU-T G.841]. + +##### *Switching time* + +Refer to [ITU-T G.841]. + +##### Switch restoration + +In the revertive mode of operation, the protected signal shall be switched back from the protection (sub)network connection to the working (sub)network connection when the working (sub)network connection has recovered from the fault. + +To prevent frequent operation of the protection switch due to an intermittent fault, a failed working (sub)network connection must become fault-free for a certain period of time before it is used again. This period, called wait to restore (WTR) period should be of the order of 5-12 minutes and should be capable of being set. + +In the non-revertive mode of operation, no switchback to the working (sub)network connection is performed when it has recovered from the fault. + +Protection switching notifications to the MP are for further study. + +## 12.2 Termination functions + +### 12.2.1 OTSiG-O trail termination function (OTSiG-O\_TT) + +The OTSiG-O\_TT functions are responsible for the end-to-end supervision of the OTSiG-O trail. Figure 12-8 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Diagram of OTSiG-O Trail Termination (TT) function showing sink and source components.](02dfdcd208dbdc8fa4f645885e59dd17_img.jpg) + +The diagram illustrates the OTSiG-O Trail Termination (TT) function as a combination of two unidirectional functions. On the left, a downward-pointing triangle labeled 'OTSiG-O' represents the sink function, with an input arrow from the top and an output arrow pointing to 'OTSiG-O\_TCP' at the bottom. On the right, an upward-pointing triangle labeled 'OTSiG-O' represents the source function, with an input arrow from 'OTSiG-O\_TCP' at the bottom and an output arrow pointing to 'OTSiG-O\_AP' at the top. The reference code 'G.798(17)\_F12-8' is located at the bottom right of the diagram. + +Diagram of OTSiG-O Trail Termination (TT) function showing sink and source components. + +Figure 12-8 – OTSiG-O\_TT + +#### 12.2.1.1 OTSiG-O trail termination source function (OTSiG-O\_TT\_So) + +The OTSiG-O\_TT\_So function adds overhead for the purpose of managing an OTSiG maintenance entity – including OTSiG-O TTI, OCI, TSI, FDI-P/O and BDI-P/O. + +The information flow and processing of the OTSiG-O\_TT\_So function is defined with reference to Figures 12-9 and 12-10. + +##### Symbol + +![Symbol for OTSiG-O Trail Termination Source (TT_So) function.](66decd3c38c5f918f528096090219e15_img.jpg) + +The diagram shows the symbol for the OTSiG-O Trail Termination Source (TT\_So) function. It consists of a downward-pointing triangle labeled 'OTSiG-O'. An input arrow labeled 'OTSiG-O\_TT\_So\_RP' enters the triangle from the right. An output arrow points from the bottom vertex of the triangle to 'OTSiG-O\_TCP'. The reference code 'G.798(17)\_F12-9' is located at the bottom right of the diagram. + +Symbol for OTSiG-O Trail Termination Source (TT\_So) function. + +Figure 12-9 – OTSiG-O\_TT\_So function + +##### Interfaces + +**Table 12-2 – OTSiG-O\_TT\_So inputs and outputs** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| OTSiG-O_RP:
OTSiG-O_RI_BDI-O
OTSiG-O_RI_BDI-P
OTSiG-O_TT_So_MP:
OTSiG-O_TT_So_MI_TxTI
OTSiG-O_TT_So_MI_TxTSI | OTSiG-O_TCP:
OTSiG-O_CI_OH | + +##### Processes + +The processes associated with the OTSiG-O\_TT\_So function are as depicted in Figure 12-10. + +**TTI:** The trail trace identifier information (OTSiG-TTI) is inserted into the OTSiG-O portion of the OSC. Its value is derived from reference point OTSiG-O\_TT\_So\_MP. The trail trace format is described in clause 15.2 of [ITU-T G.709]. + +**TSI:** The transmitter structure identifier information (OTSiG-TSI) is inserted into the OTSiG-O portion of the OSC. Its value is derived from reference point OTSiG-O\_TT\_So\_MP. + +**BDI-P:** The BDI-P information (OTSiG-BDI-P) is inserted into the OTSiG-O portion of the OSC. Its value is derived from reference point OTSiG-O\_TT\_So\_RP. Upon the declaration/clearing of aBDI-P at the termination sink function, the trail termination source function shall have inserted/removed the BDI-P indication within 50 ms. + +**BDI-O:** The BDI-O information (OTSiG-BDI-O) is inserted into the OTSiG-O portion of the OSC. Its value is derived from reference point OTSiG-O\_TT\_So\_RP. Upon the declaration/clearing of aBDI-O at the termination sink function, the trail termination source function shall have inserted/removed the BDI-O indication within 50 ms. + +The FDI-P, FDI-O and OCI information elements shall be set to false. + +![Diagram of OTSiG-O_TT_So processes showing overhead insertion steps and their associated reference points.](987a8ea27d373fa66433e6b8cb2e98ab_img.jpg) + +The diagram illustrates the 'Overhead insertion' process within the OTSiG-O\_TT\_So function. A central vertical bar labeled 'Overhead insertion' has arrows pointing to it from seven boxes: 'Insert BDI-P', 'Insert BDI-O', 'Insert OCI', 'Insert FDI-P', 'Insert FDI-O', 'Insert TTI', and 'Insert TSI'. These boxes are grouped into two sets by curly braces on the right. The top set, containing BDI-P, BDI-O, OCI, FDI-P, and FDI-O, is associated with the reference point 'OTSiG-O\_TT\_So\_RP' and has input arrows from 'RI\_BDI-P' and 'RI\_BDI-O'. The bottom set, containing TTI and TSI, is associated with the reference point 'OTSiG-O\_TT\_So\_MP' and has input arrows from 'MI\_TxTTI' and 'MI\_TxTSI'. An arrow points from the bottom of the 'Overhead insertion' bar to 'CI\_OH'. Below the diagram, the label 'OTSiG-O\_TCP' is present. In the bottom right corner, the text 'G.798(17)-Cor.1(18)\_F12-10' is visible. + +Diagram of OTSiG-O\_TT\_So processes showing overhead insertion steps and their associated reference points. + +**Figure 12-10 – OTSiG-O\_TT\_So processes** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 12.2.1.2 OTSiG-O trail termination sink function (OTSiG-O\_TT\_Sk) + +The OTSiG-O\_TT\_Sk function extracts the OTSiG-O overhead – including the FDI-P, FDI-O and OCI signals – from the OTSiG-O signal at its OTSiG-O\_TCP, detects for OCI, FDI-P and FDI-O defects. + +##### Symbol + +![Symbol diagram for OTSiG-O_TT_Sk function. A central triangle labeled 'OTSiG-O' has four interfaces: OTSiG-O_AP at the top (output), OTSiG-O_TT_Sk_MP on the left (input), OTSiG-O_TT_Sk_RP on the right (output), and OTSiG-O_TCP at the bottom (input).](014daefdecf9d847ca82cb5b9f50731f_img.jpg) + +G.798(17)-Amd.3(21)\_F12-11 + +Symbol diagram for OTSiG-O\_TT\_Sk function. A central triangle labeled 'OTSiG-O' has four interfaces: OTSiG-O\_AP at the top (output), OTSiG-O\_TT\_Sk\_MP on the left (input), OTSiG-O\_TT\_Sk\_RP on the right (output), and OTSiG-O\_TCP at the bottom (input). + +**Figure 12-11 – OTSiG-O\_TT\_Sk function** + +##### Interfaces + +**Table 12-3 – OTSiG-O\_TT\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OTSiG-O_TCP:
OTSiG-O_CI_OH
OTSiG-O_CI_SSF-P
OTSiG-O_CI_SSF-O
OTSiG-O_TT_Sk_MP:
OTSiG-O_TT_Sk_MI_ExSAPI
OTSiG-O_TT_Sk_MI_ExDAPI
OTSiG-O_TT_Sk_MI_GetAcTI
OTSiG-O_TT_Sk_MI_TIMDetMo
OTSiG-O_TT_Sk_MI_TIMActDis
OTSiG-O_TT_Sk_MI_1second | OTSiG-O_AP:
OTSiG-O_AI_TSF-P
OTSiG-O_AI_TSF-O
OTSiG-O_RP:
OTSiG-O_RI_BDI-P
OTSiG-O_RI_BDI-O
OTSiG-O_TT_Sk_MP:
OTSiG-O_TT_Sk_MI_AcTI
OTSiG-O_TT_Sk_MI_cTIM
OTSiG-O_TT_Sk_MI_cBDI
OTSiG-O_TT_Sk_MI_cBDI-P
OTSiG-O_TT_Sk_MI_cBDI-O
OTSiG-O_TT_Sk_MI_cOCI
OTSiG-O_TT_Sk_MI_cSSF
OTSiG-O_TT_Sk_MI_cSSF-P
OTSiG-O_TT_Sk_MI_cSSF-O
OTSiG-O_TT_Sk_MI_pN_DS-P
OTSiG-O_TT_Sk_MI_pN_DS-O
OTSiG-O_TT_Sk_MI_pF_DS-P
OTSiG-O_TT_Sk_MI_pF_DS-O | + +##### Processes + +The processes associated with the OTSiG-O\_TT\_Sk function are as depicted in Figure 12-12. The specific implementation for extracting information elements from the OTSiG-O\_CI is outside the scope of this Recommendation. + +**TTI:** The trail trace identifier information (OTSiG-TTI) shall be recovered from the OTSiG-O portion of the OSC and processed as specified in clause 8.6. The accepted value of the TTI is available at the MP. The trail trace format is described in clause 15.2 of [ITU-T G.709]. + +**BDI-P:** The BDI-P information (OTSiG-BDI-P) shall be extracted from the OTSiG-O portion of the OSC. It shall be used for BDI-P defect detection. + +**BDI-O:** The BDI-O information (OTSiG-BDI-O) shall be extracted from the OTSiG-O portion of the OSC. It shall be used for BDI-O defect detection. + +**FDI-P:** The FDI-P information (OTSiG-O-FDI-P) shall be extracted from the OTSiG-O portion of the OSC. It shall be used for FDI-P defect detection. + +**FDI-O:** The FDI-O information (OTSiG-O-FDI-O) shall be extracted from the OTSiG-O portion of the OSC. It shall be used for FDI-O defect detection. + +**OCI:** The OCI information (OTSiG-O-OCI) shall be extracted from the OTSiG-O portion of the OSC. It shall be used for OCI defect detection. + +**TSI:** The TSI information (OTSiG-O-TSI) shall be extracted from the OTSiG-O portion of the OSC. + +![Diagram of OTSiG-O_TT_Sk processes showing internal components and their interactions. The diagram is divided into three main sections: OTSiG-O_TT_Sk_RP (top), OTSiG-O_TT_Sk_MP (middle), and OTSiG-O_TCP (bottom). OTSiG-O_TT_Sk_RP includes RI_BDI-O, RI_BDI-P, and Consequent actions. OTSiG-O_TT_Sk_MP includes MI_TIMActDis, MI_AcTI, MI_ExSAPI, MI_ExDAPI, MI_GetAcTI, MI_TIMDetMo, Process TTI, Extract TTI, Defect correlation, Performance monitoring, and OTSiG OH access. OTSiG-O_TCP includes CI_SSF-P, CI_SSF-O, and CI_OH. Arrows show data flow between these components and external signals like AI_TSF-P, AI_SSF-O, dTIM, dOCI, dFDI-O, dFDI-P, dBDI-O, dBDI-P, CI_SSF-O, and CI_SSF-P.](9faa3512b2ff7973283e76192e91bf65_img.jpg) + +``` + +graph TD + subgraph OTSiG-O_TT_Sk_RP + RI_BDI_O[RI_BDI-O] + RI_BDI_P[RI_BDI-P] + ConsActions[Consequent actions] + end + + subgraph OTSiG-O_TT_Sk_MP + MI_Signals[MI_TIMActDis +MI_AcTI +MI_ExSAPI +MI_ExDAPI +MI_GetAcTI +MI_TIMDetMo] + ProcessTTI[Process TTI] + ExtractTTI[Extract TTI] + DefectCorr[Defect correlation] + PerfMon[Performance monitoring] + OHAccess[OTSiG OH access] + end + + subgraph OTSiG-O_TCP + CI_SSF_P[CI_SSF-P] + CI_SSF_O[CI_SSF-O] + CI_OH[CI_OH] + end + + OHAccess --> ExtractTTI + OHAccess --> ExtractBDI_O[Extract BDI-O] + OHAccess --> ExtractBDI_P[Extract BDI-P] + OHAccess --> ExtractFDI_O[Extract FDI-O] + OHAccess --> ExtractFDI_P[Extract FDI-P] + OHAccess --> ExtractOCI[Extract OCI] + + ExtractTTI --> ProcessTTI + ProcessTTI --> dTIM + ExtractBDI_O --> dBDI_O + ExtractBDI_P --> dBDI_P + ExtractFDI_O --> dFDI_O + ExtractFDI_P --> dFDI_P + ExtractOCI --> dOCI + + dTIM --> DefectCorr + dBDI_O --> DefectCorr + dBDI_P --> DefectCorr + dFDI_O --> DefectCorr + dFDI_P --> DefectCorr + dOCI --> DefectCorr + + DefectCorr --> MI_cSignals[MI_cSSF-O +MI_cSSF-P +MI_cBDI-O +MI_cBDI-P +MI_cSSF +MI_cBDI +MI_cTIM +MI_cOCI] + + dBDI_O --> PerfMon + dBDI_P --> PerfMon + PerfMon --> MI_pfSignals[MI_pF_DS-O +MI_pF_DS-P +MI_1second +MI_pN_DS-O +MI_pN_DS-P] + + ConsActions --> AI_TSF_P[AI_TSF-P] + ConsActions --> AI_SSF_O[AI_SSF-O] + +``` + +Diagram of OTSiG-O\_TT\_Sk processes showing internal components and their interactions. The diagram is divided into three main sections: OTSiG-O\_TT\_Sk\_RP (top), OTSiG-O\_TT\_Sk\_MP (middle), and OTSiG-O\_TCP (bottom). OTSiG-O\_TT\_Sk\_RP includes RI\_BDI-O, RI\_BDI-P, and Consequent actions. OTSiG-O\_TT\_Sk\_MP includes MI\_TIMActDis, MI\_AcTI, MI\_ExSAPI, MI\_ExDAPI, MI\_GetAcTI, MI\_TIMDetMo, Process TTI, Extract TTI, Defect correlation, Performance monitoring, and OTSiG OH access. OTSiG-O\_TCP includes CI\_SSF-P, CI\_SSF-O, and CI\_OH. Arrows show data flow between these components and external signals like AI\_TSF-P, AI\_SSF-O, dTIM, dOCI, dFDI-O, dFDI-P, dBDI-O, dBDI-P, CI\_SSF-O, and CI\_SSF-P. + +G.798(17)-Amd.3(21)\_F12-12 + +Figure 12-12 – OTSiG-O\_TT\_Sk processes + +##### Defects + +The function shall detect for dFDI-P, dFDI-O and dOCI. + +**dFDI-P:** See clause 6.2.6.1.1. + +**dFDI-O:** See clause 6.2.6.2.1. + +**dOCI:** See clause 6.2.6.8.1; dOCI shall be set to false during CI\_SSF-O and dFDI-O. + +**dTIM:** See clause 6.2.2.1; dTIM shall be set to false during CI\_SSF-O and dFDI-O. + +**dBDI-P:** See clause 6.2.6.4.1; dBDI-P shall be set to false during CI\_SSF-O and dFDI-O. + +**dBDI-O:** See clause 6.2.6.5.1; dBDI-O shall be set to false during CI\_SSF-O and dFDI-O. + +##### Consequent actions + +The function shall perform the following consequent actions: + +$aTSF\text{-}P \leftarrow CI\_SSF\text{-}P \text{ or } dOCI \text{ or } dFDI\text{-}P \text{ or } (dTIM \text{ and } (\text{not } TIMActDis))$ + +$aTSF\text{-}O \leftarrow CI\_SSF\text{-}O \text{ or } dFDI\text{-}O \text{ or } (dTIM \text{ and } (\text{not } TIMActDis))$ + +$aBDI\text{-}P \leftarrow CI\_SSF\text{-}P \text{ or } dFDI\text{-}P \text{ or } dTIM$ + +$aBDI\text{-}O \leftarrow CI\_SSF\text{-}O \text{ or } dFDI\text{-}O \text{ or } dTIM$ + +##### **Defect correlations** + +The function shall perform the following defect correlations to determine the most probable fault cause. This fault cause shall be reported to the EMF. + +$\text{cOCI} \leftarrow \text{dOCI and (not CI\_SSF-P) and (not CI\_SSF-O) and (not FDI-O) and (not FDI-P)}$ + +$\text{cSSF} \leftarrow \text{(CI\_SSF-P or dFDI-P) and (CI\_SSF-O or dFDI-O)}$ + +$\text{cSSF-P} \leftarrow \text{(CI\_SSF-P or dFDI-P) and (not cSSF)}$ + +$\text{cSSF-O} \leftarrow \text{(CI\_SSF-O or dFDI-O) and (not cSSF)}$ + +$\text{cBDI} \leftarrow \text{dBDI-P and dBDI-O and (not CI\_SSF) and (not dTIM)}$ + +$\text{cBDI-P} \leftarrow \text{dBDI-P and (not CI\_SSF) and (not (dTIM and (not TIMActDis))) and (not dBDI-O)}$ + +$\text{cBDI-O} \leftarrow \text{dBDI-O and (not CI\_SSF) and (not (dTIM and (not TIMActDis))) and (not dBDI-P)}$ + +$\text{cTIM} \leftarrow \text{dTIM and (not CI\_SSF)}$ + +##### **Performance monitoring** + +The OTSiG-O\_TT\_Sk function shall perform the following performance monitoring primitives. The performance monitoring primitives shall be reported to the EMF. + +$\text{pN\_DS-P} \leftarrow \text{CI\_SSF-P or dTIM}$ + +$\text{pN\_DS-O} \leftarrow \text{CI\_SSF-O or dTIM}$ + +$\text{pF\_DS-P} \leftarrow \text{dBDI-P}$ + +$\text{pF\_DS-O} \leftarrow \text{dBDI-O}$ + +NOTE – Performance monitoring primitives based on signal quality monitoring are for further study. Specific implementations are outside the scope of this Recommendation. + +### 12.2.2 OCh-O trail termination function (OCh-O\_TT) + +The OCh-O\_TT functions are responsible for the end-to-end supervision of the OCh-O trail. Figure 12-13 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Diagram of OCh-O trail termination function (OCh-O_TT) showing two unidirectional functions (sink and source) combined into a bidirectional function.](4afdd54473731079bf51f7d1acf72187_img.jpg) + +``` + +graph TD + subgraph Sink + A1[ ] --> B1[OCh-O] + B1 --> C1[OCh-O_TCP] + end + subgraph Source + C2[OCh-O_TCP] --> B2[OCh-O] + B2 --> A2[OCh-O_AP] + end + style B1 fill:none,stroke:#000,stroke-width:1px + style B2 fill:none,stroke:#000,stroke-width:1px + style A1 height:0px,width:0px + +``` + +The diagram illustrates the OCh-O trail termination function (OCh-O\_TT) as a combination of two unidirectional functions. On the left, a unidirectional sink function is shown as an inverted triangle labeled 'OCh-O' with an input arrow from the top and an output arrow pointing down to 'OCh-O\_TCP'. On the right, a unidirectional source function is shown as an inverted triangle labeled 'OCh-O' with an input arrow from 'OCh-O\_TCP' pointing up into the triangle and an output arrow pointing up to 'OCh-O\_AP'. Below the diagrams is the reference code G.798(17)\_F12-13. + +Diagram of OCh-O trail termination function (OCh-O\_TT) showing two unidirectional functions (sink and source) combined into a bidirectional function. + +**Figure 12-13 – OCh-O\_TT** + +#### 12.2.2.1 OCh-O trail termination source function (OCh-O\_TT\_So) + +The information flow and processing of the OCh-O\_TT\_So function is defined with reference to Figure 12-14. + +##### Symbol + +![Symbol for OCh-O_TT_So function](7c6fd006fc4d304794392d41fab4ee10_img.jpg) + +The diagram shows a downward-pointing triangle labeled "OCh-O". An arrow points from the bottom vertex of the triangle to the text "OCh-O\_TCP". Below the text "OCh-O\_TCP" is the reference code "G.798(17)\_F12-14". + +Symbol for OCh-O\_TT\_So function + +Figure 12-14 – OCh-O\_TT\_So function + +##### Interfaces + +Table 12-4 – OCh-O\_TT\_So inputs and outputs + +| Input(s) | Output(s) | +|----------|---------------------------| +| | OCh-O_TCP:
OCh-O_CI_OH | + +##### Processes + +The function shall generate the logical OCh-O signal. The FDI-P, FDI-O and OCI information elements shall be set to false. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 12.2.2.2 OCh-O trail termination sink function (OCh-O\_TT\_Sk) + +The OCh-O\_TT\_Sk function extracts the OCh-O overhead – including the FDI-P, FDI-O and OCI signals – from the OCh-O signal at its OCh-O\_TCP, detects for OCI, FDI-P and FDI-O defects. + +##### Symbol + +![Symbol for OCh-O_TT_Sk function](8f0dbc9a3fca3bcfa8574edb6061b03c_img.jpg) + +The diagram shows a downward-pointing triangle labeled "OCh-O". An arrow points from the bottom vertex of the triangle to the text "OCh-O\_TCP". An arrow points from the left side of the triangle to the text "OCh-O\_TT\_Sk\_MP". An arrow points from the top vertex of the triangle to the text "OCh-O\_AP". Below the text "OCh-O\_TCP" is the reference code "G.798(17)\_F12-15". + +Symbol for OCh-O\_TT\_Sk function + +Figure 12-15 – OCh-O\_TT\_Sk function + +##### Interfaces + +**Table 12-5 – OCh-O\_TT\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OCh-O_TCP:
OCh-O_CI_OH
OCh-O_CI_SSF-P
OCh-O_CI_SSF-O | OCh-O_AP:
OCh-O_AI_TSF-P
OCh-O_AI_TSF-O
OCh-O_TT_Sk_MP:
OCh-O_TT_Sk_MI_cOCI
OCh-O_TT_Sk_MI_cSSF
OCh-O_TT_Sk_MI_cSSF-P
OCh-O_TT_Sk_MI_cSSF-O | + +##### Processes + +The processes associated with the OCh-O\_TT\_Sk function are as depicted in Figure 12-16. The specific implementation for extracting information elements from the OCh-O\_CI is outside the scope of this Recommendation. + +**FDI-P:** The FDI-P information (OCh-O-FDI-P) shall be extracted from the OCh-O portion of the OSC. It shall be used for FDI-P defect detection. + +**FDI-O:** The FDI-O information (OCh-O-FDI-O) shall be extracted from the OCh-O portion of the OSC. It shall be used for FDI-O defect detection. + +**OCI:** The OCI information (OCh-O-OCI) shall be extracted from the OCh-O portion of the OSC. It shall be used for OCI defect detection. + +![Figure 12-16 – OCh-O_TT_Sk processes. This block diagram shows the internal processes of the OCh-O_TT_Sk function. Inputs from OCh-O_TCP (CI_SSF-P, CI_SSF-O, CI_OH) enter from the bottom. CI_SSF-P and CI_SSF-O feed into 'Extract FDI-O' and 'Extract FDI-P' respectively. CI_OH feeds into 'Extract OCI'. These three extraction blocks feed into an 'Overhead access' block. The 'Overhead access' block feeds into a 'Defect correlation' block. The 'Defect correlation' block outputs MI_cSSF-O, MI_cSSF-P, MI_cSSF, and MI_cOCI to OCh-O_TT_Sk_MP on the left. The 'Defect correlation' block also outputs CI_SSF-O, CI_SSF-P, dFDI-O, dFDI-P, and dOCI. CI_SSF-O and CI_SSF-P feed into 'Consequent actions'. dFDI-O, dFDI-P, and dOCI feed into 'Consequent actions' via intermediate blocks. 'Consequent actions' outputs aTSF-P and aTSF-O to OCh-O_AP at the top. A small note G.798(17)_F12-16 is in the bottom right.](da5a8f834706c8119a47c5eb732feabe_img.jpg) + +Figure 12-16 – OCh-O\_TT\_Sk processes. This block diagram shows the internal processes of the OCh-O\_TT\_Sk function. Inputs from OCh-O\_TCP (CI\_SSF-P, CI\_SSF-O, CI\_OH) enter from the bottom. CI\_SSF-P and CI\_SSF-O feed into 'Extract FDI-O' and 'Extract FDI-P' respectively. CI\_OH feeds into 'Extract OCI'. These three extraction blocks feed into an 'Overhead access' block. The 'Overhead access' block feeds into a 'Defect correlation' block. The 'Defect correlation' block outputs MI\_cSSF-O, MI\_cSSF-P, MI\_cSSF, and MI\_cOCI to OCh-O\_TT\_Sk\_MP on the left. The 'Defect correlation' block also outputs CI\_SSF-O, CI\_SSF-P, dFDI-O, dFDI-P, and dOCI. CI\_SSF-O and CI\_SSF-P feed into 'Consequent actions'. dFDI-O, dFDI-P, and dOCI feed into 'Consequent actions' via intermediate blocks. 'Consequent actions' outputs aTSF-P and aTSF-O to OCh-O\_AP at the top. A small note G.798(17)\_F12-16 is in the bottom right. + +**Figure 12-16 – OCh-O\_TT\_Sk processes** + +##### Defects + +The function shall detect for dFDI-P, dFDI-O and dOCI. + +**dFDI-P:** See clause 6.2.6.1.1. + +**dFDI-O:** See clause 6.2.6.2.1. + +**dOCI:** See clause 6.2.6.8.1; dOCI shall be set to false during CI\_SSF-O and dFDI-O. + +##### Consequent actions + +The function shall perform the following consequent actions: + +$a\text{TSF-P} \leftarrow \text{CI\_SSF-P or dOCI or dFDI-P}$ + +$a\text{TSF-O} \leftarrow \text{CI\_SSF-O or dFDI-O}$ + +##### Defect correlations + +The function shall perform the following defect correlations to determine the most probable fault cause. This fault cause shall be reported to the EMF. + +$c\text{OCI} \leftarrow \text{dOCI and (not CI\_SSF-P) and (not CI\_SSF-O) and (not FDI-O) and (not FDI-P)}$ + +$c\text{SSF} \leftarrow (\text{CI\_SSF-P or dFDI-P}) \text{ and } (\text{CI\_SSF-O or dFDI-O})$ + +$c\text{SSF-P} \leftarrow (\text{CI\_SSF-P or dFDI-P}) \text{ and (not cSSF)}$ + +$c\text{SSF-O} \leftarrow (\text{CI\_SSF-O or dFDI-O}) \text{ and (not cSSF)}$ + +##### Performance monitoring + +For further study. + +### 12.2.3 OTSiA|OCh non-intrusive monitor function + +As the functionality of the OTSiG-O and OCh-O non-intrusive monitor functions is identical to the OTSiG-O\_TT\_Sk and OCh-O\_TT\_Sk functions (see clauses 12.2.1.2 and 12.2.2.2), no dedicated non-intrusive monitoring functions OTSiGm\_TT\_Sk or OChm\_TT\_Sk are defined. For OTSiA and OCh non-intrusive monitoring, the OTSiG-O\_TT\_Sk and OCh-O\_TT\_Sk functions can be connected as shown in Figure 12-17. + +NOTE – Figure 12-17 shows the OCh case. The same principle can be applied for OTSiA. + +The TSF and TSD outputs can be connected to an OCh\_C connection function and used as protection switching trigger criteria for SNC/N protection. + +![Diagram showing the connection of OTSiG-O_TT_Sk and OCh-O_TT_Sk functions as non-intrusive monitors. A central oval labeled 'OCh' has two input arrows from the top labeled 'OCh_CP' and two output arrows to the bottom labeled 'OCh_CP'. Below the 'OCh' oval are two trapezoidal blocks labeled 'OMS/OCh'. To the left, an arrow points from the 'OMS/OCh' block to a triangular block labeled 'OCh', which then points to the 'OCh' oval. To the right, an arrow points from the 'OCh' oval to another triangular block labeled 'OCh', which then points to a dashed box labeled 'TSF'. Below this 'TSF' box is another dashed box labeled 'TSD'. The diagram is labeled G.798(10)_F12-17.](5546020e0c70645fd46b8829e2e3c43b_img.jpg) + +Diagram showing the connection of OTSiG-O\_TT\_Sk and OCh-O\_TT\_Sk functions as non-intrusive monitors. A central oval labeled 'OCh' has two input arrows from the top labeled 'OCh\_CP' and two output arrows to the bottom labeled 'OCh\_CP'. Below the 'OCh' oval are two trapezoidal blocks labeled 'OMS/OCh'. To the left, an arrow points from the 'OMS/OCh' block to a triangular block labeled 'OCh', which then points to the 'OCh' oval. To the right, an arrow points from the 'OCh' oval to another triangular block labeled 'OCh', which then points to a dashed box labeled 'TSF'. Below this 'TSF' box is another dashed box labeled 'TSD'. The diagram is labeled G.798(10)\_F12-17. + +**Figure 12-17 – Connection of OTSiG-O\_TT\_Sk and OCh-O\_TT\_Sk functions as non-intrusive monitor** + +### 12.2.4 Combined OTSiA|OCh and OTUk[V] non-intrusive monitor function (OCTk[V]m) + +As the OCh and OTUk[V] terminations are always collocated in an OTN network, a combined OCh and OTUk[V] non-intrusive monitor is defined as a compound function OCTk[V]m. The OCTk[V]m compound function is the combination of a OTSiG-O|OCh-O\_TT\_Sk (see clause 12.2.1.2 + +or 12.2.2.2), OTSi/OTUk[V]\_A\_Sk (see clauses 16.1.2 and 16.2.2) and OTUk[V]\_TT\_Sk (see clauses 13.2.1.2 and 13.2.2.2) as shown in Figure 12-18. For the OTSi/OTUk\_A, either an OTSi/OTUk-a\_A\_Sk with FEC or an OTSi/OTUk-b\_A\_Sk without FEC can be used (see clause 16.1.2). This depends on the specific application and OTUk signal. + +For non-intrusive monitoring, the OCTk[V]m function can be connected as shown in Figure 12-19. The OCTk[V]m function can be connected to any OCh\_CP in this manner. + +![Figure 12-18: OCTk[V]m compound function diagram. The diagram shows the internal structure of the OCTk[V]m function. On the left, an 'x-O' block (representing OTSiG-O or OCh-O) and an 'OTSi' block are connected to their respective client ports, 'x-O_CP' and 'OTSi_CP'. These are then connected to an 'OTSi/OTUk[V]' block via 'OTSi_AP'. This block is connected to an 'OTUk[V]_CP', which in turn connects to an 'OTUk[V]' block. A large arrow points to the right, showing the simplified representation of the 'OCTk[V]m' function. This function has two input ports: 'x-O_CP' and 'OTSi_CP'.](238754529581b74f0696943d436494bb_img.jpg) + +x = OTSiG-O or OCh-O +G.798(17)\_F12-18 + +Figure 12-18: OCTk[V]m compound function diagram. The diagram shows the internal structure of the OCTk[V]m function. On the left, an 'x-O' block (representing OTSiG-O or OCh-O) and an 'OTSi' block are connected to their respective client ports, 'x-O\_CP' and 'OTSi\_CP'. These are then connected to an 'OTSi/OTUk[V]' block via 'OTSi\_AP'. This block is connected to an 'OTUk[V]\_CP', which in turn connects to an 'OTUk[V]' block. A large arrow points to the right, showing the simplified representation of the 'OCTk[V]m' function. This function has two input ports: 'x-O\_CP' and 'OTSi\_CP'. + +**Figure 12-18 – OCTk[V]m compound function** + +![Figure 12-19: Connection OCTk[V]m compound function (non-intrusive monitor) diagram. This diagram shows the OCTk[V]m function connected within an OTSiA|OCh domain. At the top is an oval labeled 'OTSiA|OCh'. Below it, two 'OCTk[V]m' blocks are shown. Each block has an input port 'x-O_CP' connected to a line. These lines are connected to 'OMS-O/OTSiG-O' blocks. The 'OMS-O/OTSiG-O' blocks are connected to the 'OTSiA|OCh' domain. A dashed arrow labeled 'TSF' points from the 'OCTk[V]m' block to the 'OTSiA|OCh' domain. The diagram also shows 'OTSi' lines entering and leaving the domain. A label 'x = OTSiG-O or OCh-O' is present in the center.](af90aabfe3c8c65617da060d82bf99c5_img.jpg) + +G.798(17)-Amd.4(22)\_F12-19 + +Figure 12-19: Connection OCTk[V]m compound function (non-intrusive monitor) diagram. This diagram shows the OCTk[V]m function connected within an OTSiA|OCh domain. At the top is an oval labeled 'OTSiA|OCh'. Below it, two 'OCTk[V]m' blocks are shown. Each block has an input port 'x-O\_CP' connected to a line. These lines are connected to 'OMS-O/OTSiG-O' blocks. The 'OMS-O/OTSiG-O' blocks are connected to the 'OTSiA|OCh' domain. A dashed arrow labeled 'TSF' points from the 'OCTk[V]m' block to the 'OTSiA|OCh' domain. The diagram also shows 'OTSi' lines entering and leaving the domain. A label 'x = OTSiG-O or OCh-O' is present in the center. + +**Figure 12-19 – Connection OCTk[V]m compound function (non-intrusive monitor)** + +### 12.2.5 Combined OTSiA|OCh, OTUk[V] and ODUkT non-intrusive monitor function (OCTDk[V]m) + +To support detection of bit errors in a serial compound ODUk link connection carried through an OCh domain with 3R regeneration, it is necessary to deploy ODUk tandem connection monitoring between the ODUk connection points at the endpoints of the ODUk serial compound link connection. For this purpose, a combined OCh, OTUk[V] and ODUkT non-intrusive monitor is defined as a compound function OCTDk[V]m. The OCTDk[V]m compound function is the combination of OTSiG-O|OCh-O\_TT\_Sk (see clause 12.2.1.2 or 12.2.2.2), OTSi/OTUk[V]\_A\_Sk (see clauses 16.1.2 and 16.2.2), OTUk[V]\_TT\_Sk (see clauses 13.2.1.2 and 13.2.2.2), OTUk[V]/ODUk\_A (see clauses 13.3.1 and 13.3.2) and ODUkT\_TT (see clause 14.5.1.1) as shown in Figure 12-20. For + +the OTSi/OTUk\_A, either an OTSi/OTUk-a\_A\_Sk with FEC or an OTSi/OTUk-b\_A\_Sk without FEC can be used (see clause 16.1.2). This depends on the specific application and of the OTUk signal. For non-intrusive monitoring, the OCTDk[V]m function can be connected as shown in Figure 12-21. The OCTDk[V]m function can be connected to any OCh\_CP in this manner. + +![Figure 12-20: OCTDk[V]m compound function diagram. The diagram shows a signal flow from bottom to top: x-O_CP enters an x-O triangle, and OTSi_CP enters an OTSi triangle. These combine into an OTSi/OTUk[V] rectangle. Above it, an OTUk[V] triangle receives OTUk[V]_CP. This is followed by an OTUk[V]_AP and an OTUk[V]/ODUk rectangle, which finally connects to an ODUk triangle via an ODUk_CP. To the right, an arrow points to the OCTDk[V]m compound function, which is shown as a triangle receiving x-O_CP and OTSi_CP. Below the diagram, text indicates x = OTSiG-O or OCh-O and G.798(17)_F12-20.](48b17e34bf39cb8a801a634c791250c0_img.jpg) + +Figure 12-20: OCTDk[V]m compound function diagram. The diagram shows a signal flow from bottom to top: x-O\_CP enters an x-O triangle, and OTSi\_CP enters an OTSi triangle. These combine into an OTSi/OTUk[V] rectangle. Above it, an OTUk[V] triangle receives OTUk[V]\_CP. This is followed by an OTUk[V]\_AP and an OTUk[V]/ODUk rectangle, which finally connects to an ODUk triangle via an ODUk\_CP. To the right, an arrow points to the OCTDk[V]m compound function, which is shown as a triangle receiving x-O\_CP and OTSi\_CP. Below the diagram, text indicates x = OTSiG-O or OCh-O and G.798(17)\_F12-20. + +Figure 12-20 – OCTDk[V]m compound function + +![Figure 12-21: Connection OCTDk[V]m compound function (non-intrusive monitor) diagram. The diagram shows a large oval at the top labeled OTSiA | OCh. Below it, two OCTDk[V]m triangles are shown. Each triangle receives an x-O_CP signal. The left OCTDk[V]m triangle is connected to an OTSi input and an OMS-O/OTSiG-O rectangle. The right OCTDk[V]m triangle is connected to an OMS-O/OTSiG-O rectangle and an OTSi output. A dashed arrow labeled TSF points from the right OCTDk[V]m triangle up to the OTSiA | OCh oval. Text in the center indicates x = OTSiG-O or OCh-O. At the bottom right, G.798(17)-Amd.4(22)_F12-21 is noted.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +Figure 12-21: Connection OCTDk[V]m compound function (non-intrusive monitor) diagram. The diagram shows a large oval at the top labeled OTSiA | OCh. Below it, two OCTDk[V]m triangles are shown. Each triangle receives an x-O\_CP signal. The left OCTDk[V]m triangle is connected to an OTSi input and an OMS-O/OTSiG-O rectangle. The right OCTDk[V]m triangle is connected to an OMS-O/OTSiG-O rectangle and an OTSi output. A dashed arrow labeled TSF points from the right OCTDk[V]m triangle up to the OTSiA | OCh oval. Text in the center indicates x = OTSiG-O or OCh-O. At the bottom right, G.798(17)-Amd.4(22)\_F12-21 is noted. + +Figure 12-21 – Connection OCTDk[V]m compound function (non-intrusive monitor) + +## 12.3 Adaptation functions + +See OTSi adaptation functions in clause 16. + +## 12.4 Sub-layer functions + +Not applicable. + +# 13 OTU (layer) functions + +A completely standardized OTUk and OTUCn and a functionally standardized OTUkV are defined. Figure 13-1 illustrates the OTU layer network and client layer adaptation functions. The information crossing the OTU (trail) connection point (OTUk[V]\_CP/TCP or OTUCn\_CP/TCP) is referred to as the OTU characteristic information (OTUk[V]\_CI or OTUCn\_CI). The information crossing the OTU access point (OTUk[V]\_AP or OTUCn\_AP) is referred to as the OTU adapted information (OTUk[V]\_AI or OTUCn\_AI). + +![Figure 13-1: OTU layer network and client layer adaptation functions. The diagram shows two side-by-side vertical stacks of layers. The left stack represents OTUk[V] and the right stack represents OTUCn. Both stacks show the adaptation from client layer connection points (CP) through the OTU layer to the TCP layer. The OTUk[V] stack includes ODuk_CP, COMMS_CP, OTUk[V]_AP, OTUk[V], and OTUk[V]_TCP. The OTUCn stack includes ODUCn_CP, COMMS_CP, OTUCn_AP, OTUCn, and OTUCn_TCP. A reference label G.798(17)-Amd.2(19)_F13-1 is present.](3d1817e8551f9c226a5f561108d3b3f9_img.jpg) + +Figure 13-1: OTU layer network and client layer adaptation functions. The diagram shows two side-by-side vertical stacks of layers. The left stack represents OTUk[V] and the right stack represents OTUCn. Both stacks show the adaptation from client layer connection points (CP) through the OTU layer to the TCP layer. The OTUk[V] stack includes ODuk\_CP, COMMS\_CP, OTUk[V]\_AP, OTUk[V], and OTUk[V]\_TCP. The OTUCn stack includes ODUCn\_CP, COMMS\_CP, OTUCn\_AP, OTUCn, and OTUCn\_TCP. A reference label G.798(17)-Amd.2(19)\_F13-1 is present. + +Figure 13-1 – OTU layer network and client layer adaptation functions + +The OTUk characteristic information (OTUk\_CI) is the unscrambled OTUk frame without FEC code and with one (n=1) instance of defined OTU overhead, together with a frame and multi-frame start. The OTUCn characteristic information (OTUCn\_CI) is the unscrambled OTUCn frame with n instances of defined OTU overhead, together with a frame and multi-frame start. + +NOTE – The OTUCn frame does not contain a FEC area. + +The OTU overhead consists of the SM, GCC0, OSMC and RES overhead fields as shown in Figure 13-2. The OTUk overhead additionally includes the OSMC field. The GCC0 overhead is optional and set to all-ZEROs if not used. The RES overhead is set to all-ZEROs. + +![Figure 13-2: OTU overhead at the OTU_CP/TCP. This is a grid diagram showing the overhead structure. Columns are numbered 1 to 16, and rows are numbered 1 to 4. Row 1 contains 'Frame alignment overhead' (columns 1-7), 'SM' (columns 8-10), and 'GCC0' (columns 11-12). Rows 2 and 3 are labeled 'ODU overhead' and span columns 1-14. Row 4 contains 'OPU overhead' in columns 15-16. Below the grid, a callout shows the 'OTUk frame structure' with 'OSMC' (column 13) and 'RES' (column 14). Another callout shows the 'OTU frame structure #1..#n in OTUCn' with 'RES' (columns 13-14). A reference label G.798(17)_F13-2 is present.](b49477e8f148b5ef044a2fd5a43528f6_img.jpg) + +Figure 13-2: OTU overhead at the OTU\_CP/TCP. This is a grid diagram showing the overhead structure. Columns are numbered 1 to 16, and rows are numbered 1 to 4. Row 1 contains 'Frame alignment overhead' (columns 1-7), 'SM' (columns 8-10), and 'GCC0' (columns 11-12). Rows 2 and 3 are labeled 'ODU overhead' and span columns 1-14. Row 4 contains 'OPU overhead' in columns 15-16. Below the grid, a callout shows the 'OTUk frame structure' with 'OSMC' (column 13) and 'RES' (column 14). Another callout shows the 'OTU frame structure #1..#n in OTUCn' with 'RES' (columns 13-14). A reference label G.798(17)\_F13-2 is present. + +Figure 13-2 – OTU overhead at the OTU\_CP/TCP + +The OTUkV characteristic information (OTUkV\_CI) is the OTUkV frame with valid SM and GCC0 overhead. The OTUkV frame format is outside the scope of this Recommendation. + +The OTUk adapted information (OTUk\_AI) consists of the ODUk\_CI adapted to the OTUk frame, together with a frame and multiframe start. In case of COMMS access at the OTUk\_AP, it also includes the OTUk GCC overhead (GCC0). + +The OTUCn adapted information (OTUCn\_AI) consists of the ODUCn\_CI adapted to the OTUCn frame, together with a frame and multiframe start. In case of COMMS access at the OTUCn\_AP, it also includes the OTUCn GCC overhead (GCC0). + +The OTUkV adapted information (OTUkV\_AI) consists of the ODUk\_CI adapted to the OTUkV frame. The OTUkV frame format and the ODUk\_CI mapping are outside the scope of this Recommendation. In case of COMMS access at the OTUkV\_AP, it also includes the OTUkV GCC overhead. + +## 13.1 Connection functions + +Not applicable. + +## 13.2 Termination functions + +### 13.2.1 OTU trail termination function (OTU\_TT) + +The OTU\_TT function terminates the section monitoring (SM) overhead of the OTU overhead to determine the status of the OTU trail. Figure 13-3 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Figure 13-3 – OTU_TT diagram showing two bidirectional OTU trail termination functions. The left side shows OTUk[V] termination with ODUk[V]_AP at the top, OTUk[V]_TCP at the bottom, and OTUk[V]_RP between them. The right side shows OTUCn termination with OTUCn_AP at the top, OTUCn_TCP at the bottom, and OTUCn_RP between them. Both diagrams show signal flow from AP to RP and from RP to TCP.](2e3b1ae09da2cba02f0bb8a531f1515e_img.jpg) + +The diagram illustrates two bidirectional OTU trail termination functions. On the left, for OTUk[V], an ODUk[V]\_AP signal enters from the top into an OTUk[V] block. Below this block, an OTUk[V]\_RP signal is shown entering from the right. Below the OTUk[V] block, an OTUk[V]\_TCP signal exits downwards. On the right, for OTUCn, an OTUCn\_AP signal enters from the top into an OTUCn block. Below this block, an OTUCn\_RP signal is shown entering from the right. Below the OTUCn block, an OTUCn\_TCP signal exits downwards. The labels OTUk[V]\_RP and OTUCn\_RP are positioned between the two blocks in each pair, indicating the direction of signal flow. + +Figure 13-3 – OTU\_TT diagram showing two bidirectional OTU trail termination functions. The left side shows OTUk[V] termination with ODUk[V]\_AP at the top, OTUk[V]\_TCP at the bottom, and OTUk[V]\_RP between them. The right side shows OTUCn termination with OTUCn\_AP at the top, OTUCn\_TCP at the bottom, and OTUCn\_RP between them. Both diagrams show signal flow from AP to RP and from RP to TCP. + +Figure 13-3 – OTU\_TT + +#### 13.2.1.1 OTU trail termination source function (OTU\_TT\_So) + +The OTU\_TT\_So function computes the BIP-8[1..n] and adds section monitoring overhead (SMOH) – including the TTI, BIP-8[1..n], BDI, BEI[1..n] and IAE signals – in the SM overhead fields to the OTU signal at its OTU\_AP. The OTUCn signal has n SM overhead fields; the OTUk signal has one (n=1) SM overhead field. + +The information flow and processing of the OTU\_TT\_So function is defined with reference to Figures 13-4 and 13-5. + +##### Symbol + +![Diagram showing the OTU_TT_So function symbol for OTUk and OTUCn. Both symbols are inverted triangles with inputs OTUk_AP (top), OTUk_TT_So_MP (left), and OTUk_RP (right) entering from the top, left, and right respectively. The output OTUk_TCP exits from the bottom. A label 'k = 1, 2, 3, 4' is below the OTUk symbol. The OTUCn symbol is identical but for n. A small note G.798(17)-Amd.1(18)_F13-4 is at the bottom right.](bef134816f55f50b735c92ac0c01da38_img.jpg) + +Diagram showing the OTU\_TT\_So function symbol for OTUk and OTUCn. Both symbols are inverted triangles with inputs OTUk\_AP (top), OTUk\_TT\_So\_MP (left), and OTUk\_RP (right) entering from the top, left, and right respectively. The output OTUk\_TCP exits from the bottom. A label 'k = 1, 2, 3, 4' is below the OTUk symbol. The OTUCn symbol is identical but for n. A small note G.798(17)-Amd.1(18)\_F13-4 is at the bottom right. + +Figure 13-4 – OTU\_TT\_So function + +##### Interfaces + +Table 13-1 – OTU\_TT\_So inputs and outputs + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------| +| OTU_AP:
OTU_AI_CK
OTU_AI_D
OTU_AI_FS
OTU_AI_MFS
OTU_AI_IAE
OTU_RP:
OTU_RI_BDI
OTU_RI_BEI[1..n]
OTU_RI_BIAE
OTU_TT_So_MP:
OTU_TT_So_MI_TxTI
OTU_TT_So_MI_Mode | OTU_TCP:
OTU_CI_CK
OTU_CI_D
OTU_CI_FS
OTU_CI_MFS | + +##### Processes + +The processes associated with the OTU\_TT\_So function are as depicted in Figure 13-5. + +**Mode:** If the MI\_Mode has the value OPERATIONAL, the following processes shall be performed. If the MI\_Mode has the value TRANSPARENT, all information shall be passed through transparently and the following processes shall not be performed. + +**SMOH-TTI:** If the MI\_Mode is OPERATIONAL, the trail trace identifier is inserted in the TTI byte position of the SM field in the first OTU overhead instance. Its value is derived from reference point OTU\_TT\_So\_MP. The trail trace format is described in clause 15.2 of [ITU-T G.709]. + +**SMOH-BDI:** If the MI\_Mode is OPERATIONAL, the backward defect indication is inserted in the BDI bit position of the SM field in the first OTU overhead instance. Its value is derived from reference point OTU\_RP. Upon the declaration/clearing of aBDI at the termination sink function, the trail termination source function shall have inserted/removed the BDI indication within 50 ms. + +**SMOH-BEI/BIAE:** If the MI\_Mode is OPERATIONAL, if RI\_BIAE is true, the value "1011" is inserted into the BEI/BIAE bits of the SM field in all OTU overhead instances. If RI\_BIAE is false, the number of errors indicated in RI\_BEI[i] is encoded in the BEI/BIAE bits of the SM field in OTU overhead instance #i. Upon the detection of incoming alignment error or a number of errors at the termination sink function, the trail termination source function shall have inserted the value in the BEI/BIAE bits within 50 ms. + +**SMOH-BIP-8:** If the MI\_Mode is OPERATIONAL, the calculated BIP-8[i] is inserted into the BIP-8 byte of the SM field in OTU overhead instance #i. For the BIP-8 calculation, see clause 8.3.4.1. + +**SMOH-IAE:** If the MI\_Mode is OPERATIONAL, the incoming alignment error information AI\_IAE is inserted into the IAE bit position of the SM field in the first OTU overhead instance. Upon the declaration of AI\_IAE, the function shall insert the IAE indication for the next 16 multiframes ( $16 \times 256$ frames). Each new declaration of AI\_IAE restarts the 16 multiframe insertion time. + +**SMOH-RES:** The RES field is reserved for future international standardization. If the MI\_Mode is OPERATIONAL, the value shall be fixed to 00. + +![Diagram of OTU_TT_So processes showing the flow of data from OTU_AP to OTU_TCP through various insertion blocks.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +The diagram illustrates the OTU\_TT\_So processes. At the top, the **OTU\_AP** provides inputs: **AI\_D**, **AI\_CK**, **AI\_FS**, **AI\_MFS**, and **AI\_IAE**. **AI\_D** and **AI\_CK** are passed through to the bottom. **AI\_FS** and **AI\_MFS** are used by the **Compute BIP-8** block, which outputs **BIP-8[1..n]**. **AI\_IAE** is used by the **Insert IAE** block. The **Compute BIP-8** block feeds into the **Insert BIP-8** block. The **Insert BIP-8**, **Insert IAE**, **Insert BEI/BIAE**, **Insert BDI**, **Insert RES**, and **Insert TTI** blocks are all part of the **SMOH insertion** process. The **SMOH insertion** block outputs to the bottom as **CI\_D**, **CI\_CK**, **CI\_FS**, and **CI\_MFS**, which are part of the **OTU\_TCP**. On the right side, the **RI\_BEI[1..n]**, **RI\_BIAE**, **RI\_BDI**, **MI\_TxTI**, and **MI\_Mode** signals are shown, corresponding to the **OTU\_RP** and **OTU\_TT\_So\_MP** sections. The diagram is labeled G.798(17)-Amd.1(18)\_F13-5. + +Diagram of OTU\_TT\_So processes showing the flow of data from OTU\_AP to OTU\_TCP through various insertion blocks. + +Figure 13-5 – OTU\_TT\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 13.2.1.2 OTU trail termination sink function (OTU\_TT\_Sk) + +The OTU\_TT\_Sk function reports the state of the OTU trail. It computes the BIP-8[1..n], extracts section monitoring overhead (SMOH) – including the TTI, BIP-8[1..n], IAE, BDI and BEI[1..n] signals and for OTUCn the STAT field – in the SM overhead fields from the OTU signal at its OTU\_TCP, detects for TIM, DEG and BDI defects, counts during one-second periods errors (detected via the BIP-8) and defects to feed performance monitoring when connected, makes the TTI available to network management, and forwards the error and defect information as backward indications to the companion OTU\_TT\_So function. The OTUCn signal has n SM overhead fields; the OTUK signal has one (n=1) SM overhead field. + +The information flow and processing of the OTU\_TT\_Sk function is defined with reference to Figures 13-6 and 13-7. + +##### Symbol + +![Figure 13-6 – OTU_TT_Sk function. The diagram shows two identical processing paths for OTUk and OTUCn. Each path consists of two OTU blocks. The bottom OTU block takes OTU_TCP as input and produces OTU_TT_Sk_MP (bidirectional), OTU_RP, and ODUCn_AP (for OTUCn) as outputs. The top OTU block takes OTU_TT_Sk_MP (bidirectional), OTU_RP, and ODUCn_AP as inputs and produces OTUk_AP as output. The bottom OTU block is labeled with 'k = 1, 2, 3, 4'.](4c1ea859b93043f2fa17a8fe72fb6176_img.jpg) + +Figure 13-6 – OTU\_TT\_Sk function. The diagram shows two identical processing paths for OTUk and OTUCn. Each path consists of two OTU blocks. The bottom OTU block takes OTU\_TCP as input and produces OTU\_TT\_Sk\_MP (bidirectional), OTU\_RP, and ODUCn\_AP (for OTUCn) as outputs. The top OTU block takes OTU\_TT\_Sk\_MP (bidirectional), OTU\_RP, and ODUCn\_AP as inputs and produces OTUk\_AP as output. The bottom OTU block is labeled with 'k = 1, 2, 3, 4'. + +Figure 13-6 – OTU\_TT\_Sk function + +##### Interfaces + +Table 13-2 – OTU\_TT\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OTU_TCP:
OTU_CI_CK
OTU_CI_D
OTU_CI_FS
OTU_CI_MFS
OTU_CI_SSF
OTU_TT_Sk_MP:
OTU_TT_Sk_MI_ExSAPI
OTU_TT_Sk_MI_ExDAPI
OTU_TT_Sk_MI_GetAcTI
OTU_TT_Sk_MI_TIMDetMo
OTU_TT_Sk_MI_TIMActDis
OTU_TT_Sk_MI_DEGThr
OTU_TT_Sk_MI_DEGM
OTU_TT_Sk_MI_1second
OTU_TT_Sk_MI_Mode | OTU_AP:
OTU_AI_CK
OTU_AI_D
OTU_AI_FS
OTU_AI_MFS
OTU_AI_TSF
OTU_AI_TSD
OTU_RP:
OTU_RI_BDI
OTU_RI_BEI[1..n]
OTU_RI_BIAE
OTU_TT_Sk_MP:
OTU_TT_Sk_MI_AcTI
OTU_TT_Sk_MI_cTIM
OTU_TT_Sk_MI_cDEG
OTU_TT_Sk_MI_cBDI
OTU_TT_Sk_MI_cSSF
OTU_TT_Sk_MI_pN_EBC
OTU_TT_Sk_MI_pN_DS
OTU_TT_Sk_MI_pF_EBC
OTU_TT_Sk_MI_pF_DS
OTU_TT_Sk_MI_pBIAE
OTU_TT_Sk_MI_pIAE | + +##### Processes + +The processes associated with the OTU\_TT\_Sk function are as depicted in Figure 13-7. + +**Mode:** If the MI\_Mode has the value OPERATIONAL, the following processes shall be performed. MI\_Mode OPERATIONAL initiates the consequent actions aAIS, aTSF and aTSD, in case of defects. If the MI\_Mode has the value TRANSPARENT, all information shall be passed through transparently and the following processes shall not be performed. + +**SMOH-BIP-8:** If MI\_Mode has the value OPERATIONAL, the BIP-8[1..n] shall be processed as defined in clause 8.3.4.2. The BIP-8[1..n] is extracted from the BIP-8[1..n] bytes of the SM fields in the n SM overhead instances of the OTU signal at the OTU\_TCP. + +**SMOH-TTI:** If MI\_Mode is OPERATIONAL, the trail trace identifier shall be recovered from the TTI byte position of the SM field in the first OTU overhead instance of the OTU signal at the OTU\_TCP and processed as specified as defined in clause 8.6. The accepted value of the TTI is available at the MP (MI\_AcTI). + +**SMOH-BDI:** If MI\_Mode is OPERATIONAL, the backward defect indication shall be recovered from the BDI bit position of the SM field in the first OTU overhead instance of the OTU signal at the OTU\_TCP. It shall be used for BDI defect detection. + +**SMOH-BEI/BIAE:** If MI\_Mode is OPERATIONAL, the BEI[1..n] shall be recovered from the BEI/BIAE bits in the SM fields of the n SM overhead instances in the OTU signal at the OTU\_TCP. They shall be used to determine if far-end errored blocks (nF\_B) have occurred. One nF\_B has occurred per BEI/BIAE[i] value between 1 [0001] and 8 [1000]; otherwise, no nF\_B has occurred. + +**SMOH-IAE:** For the case of OTUk and if MI\_Mode is OPERATIONAL, the incoming alignment error information shall be recovered from IAE bit position of the SM field in the first OTU overhead instance of the OTU signal at the OTU\_TCP. It shall be used for IAE defect detection. + +**SMOH-RES:** RES in the SM field in the OTU signal at the OTU\_TCP is reserved for future international standardization. For this version of this Recommendation, its value shall be ignored. + +**SMOH-STAT:** For OTUCn and if MI\_Mode is OPERATIONAL, the status information shall be recovered from the STAT bits in the SM field of the first OTU overhead instance in the OTUCn signal at the OTUCn\_TCP as defined in clause 8.8. Is shall be used for AIS and IAE defect detection. + +![Figure 13-7 – OTU_TT_Sk processes. A detailed block diagram showing the internal processes of an OTU_TT_Sk. At the top, OTU_AP provides signals AI_TSD, AI_TSF, AI_MFS, AI_FS, AI_CK, and AI_D. At the bottom, OTU_TCP provides signals CI_SSF, CI_MFS, CI_FS, CI_CK, and CI_D. On the left, OTU_RP and OTU_TT_Sk_MP provide various management and monitoring inputs. The central part of the diagram contains several functional blocks: 'Consequent actions', 'Process TTI', 'Defect correlation', 'Performance monitoring', 'Process errors', 'Extract TTI', 'Extract RES', 'OTUCn only Process STAT', 'Extract STAT', 'Extract BDI', 'Extract BEI/BIAE', 'OTUk only Extract IAE', 'Extract BIP-8', 'Compute BIP-8', and 'Compare'. A vertical 'SMOH access' block on the right interacts with several 'Extract' blocks. Arrows indicate the flow of data and control signals between these components and the external interfaces.](f2a6c46fa05d5588ce4c6e1a3ee194c7_img.jpg) + +Figure 13-7 – OTU\_TT\_Sk processes. A detailed block diagram showing the internal processes of an OTU\_TT\_Sk. At the top, OTU\_AP provides signals AI\_TSD, AI\_TSF, AI\_MFS, AI\_FS, AI\_CK, and AI\_D. At the bottom, OTU\_TCP provides signals CI\_SSF, CI\_MFS, CI\_FS, CI\_CK, and CI\_D. On the left, OTU\_RP and OTU\_TT\_Sk\_MP provide various management and monitoring inputs. The central part of the diagram contains several functional blocks: 'Consequent actions', 'Process TTI', 'Defect correlation', 'Performance monitoring', 'Process errors', 'Extract TTI', 'Extract RES', 'OTUCn only Process STAT', 'Extract STAT', 'Extract BDI', 'Extract BEI/BIAE', 'OTUk only Extract IAE', 'Extract BIP-8', 'Compute BIP-8', and 'Compare'. A vertical 'SMOH access' block on the right interacts with several 'Extract' blocks. Arrows indicate the flow of data and control signals between these components and the external interfaces. + +G.798(17)-Amd.1(18)\_F13-7 + +Figure 13-7 – OTU\_TT\_Sk processes + +##### Defects + +If the MI\_Mode has the value OPERATIONAL, the function shall detect dAIS, dTIM, dDEG, dBDI, dBIAE and dIAE defects. If the MI\_Mode is TRANSPARENT, all defects are cleared. + +**dAIS:** See clause 6.2.6.3.2 for OTUCn; for OTUk[V] dAIS shall be assumed false. + +**dTIM:** See clause 6.2.2.1; dTIM shall be set to false during CI\_SSF. + +**dDEG:** See clause 6.2.3.4. + +NOTE 1 – IAE suppresses the one-second near-end errored block count, which is the input for the dDEG detection. This avoids wrong dDEG declaration due to alignment errors already incoming in an OTUk trail. + +**dBDI:** See clause 6.2.6.6.1; dBDI shall be set to false during CI\_SSF. + +**dIAE:** See clauses 6.2.6.10.1 for OTUk and 6.2.6.10.2 for OTUCn; dIAE shall be set to false during CI\_SSF and dTIM. + +**dBIAE:** See clause 6.2.6.11.1; dBIAE shall be set to false during CI\_SSF and dTIM. + +##### Consequent actions + +The function shall perform the following consequent actions: + +aBDI $\leftarrow$ (CI\_SSF or dAIS or dTIM) and MI\_Mode == OPERATIONAL + +aBIAE $\leftarrow$ dIAE and MI\_Mode == OPERATIONAL + +aTSF $\leftarrow$ CI\_SSF or ((dAIS or (dTIM and (not TIMActDis)))) and MI\_Mode == OPERATIONAL + +aTSD $\leftarrow$ dDEG and MI\_Mode == OPERATIONAL + +For each OTU overhead instance #i: + +aBEI[i] $\leftarrow$ nBIPV[i] and MI\_Mode == OPERATIONAL + +##### Defect correlations + +The function shall perform the following defect correlations to determine the most probable fault cause. This fault cause shall be reported to the EMF. + +cTIM $\leftarrow$ dTIM and (not CI\_SSF) and (not dAIS) + +cDEG $\leftarrow$ dDEG and (not CI\_SSF) and (not dAIS) and (not (dTIM and (not TIMActDis)))) + +cBDI $\leftarrow$ dBDI and (not CI\_SSF) and (not dAIS) and (not (dTIM and (not TIMActDis)))) + +cSSF $\leftarrow$ CI\_SSF or dAIS + +##### Performance monitoring + +If the MI\_Mode has the value OPERATIONAL, the function shall perform the following performance monitoring primitives processing. The performance monitoring primitives shall be reported to the EMF. + +pN\_DS $\leftarrow$ CI\_SSF or dAIS or dTIM + +pF\_DS $\leftarrow$ dBDI + +pN\_EBC $\leftarrow \sum nN\_B$ + +NOTE 2 – During CI\_SSF and dAIS, no errored blocks shall be counted. + +pF\_EBC $\leftarrow \sum nF\_B$ + +NOTE 3 – During CI\_SSF and dAIS, no errored blocks shall be counted. + +pBIAE $\leftarrow$ dBIAE + +NOTE 4 – pBIAE is activated at the end of a second if dBIAE was active once during the second. + +pIAE $\leftarrow$ dIAE + +NOTE 5 – pIAE is activated at the end of a second if dIAE was active once during the second. + +NOTE 6 – pIAE and pBIAE are used for the suppression of the PM data in the equipment management functions (see [ITU-T G.874]). If pBIAE is active, the F\_DS and F\_EBC values of the previous and current second have to be discarded (EBC = 0 and DS = false). If pIAE is active, the N/F\_DS and N/F\_EBC values of the previous and current second have to be discarded (EBC = 0 and DS = false). The previous second has to be included due to the delay of the IAE information coming from the remote source. + +### 13.2.2 OTUkV trail termination function (OTUkV\_TT) + +The OTUkV\_TT function terminates the section monitoring (SM) overhead of the OTUkV overhead to determine the status of the OTUkV trail. Figure 13-8 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Diagram of the OTUkV_TT function showing two OTUkV blocks connected by an OTUkV_RP signal.](88fa0e6558e55b5d54f4d3029b21aabb_img.jpg) + +The diagram shows two OTUkV blocks, each represented by a triangle. The left block has an input OTUkV\_AP at its top vertex and an output OTUkV\_TCP at its bottom vertex. The right block has an output OTUkV\_AP at its top vertex and an input OTUkV\_TCP at its bottom vertex. A horizontal line labeled OTUkV\_RP connects the right block to the left block. A label G.798(10)\_F13-8 is positioned near the right block's bottom input. + +Diagram of the OTUkV\_TT function showing two OTUkV blocks connected by an OTUkV\_RP signal. + +Figure 13-8 – OTUkV\_TT + +#### 13.2.2.1 OTUkV trail termination source function (OTUkV\_TT\_So) + +The OTUkV\_TT\_So function computes the signal quality supervision code and adds section monitoring overhead (SMOH) – including the TTI, signal quality supervision code, BDI, BEI signals – in the SM overhead to the OTUkV signal at its OTUk\_AP. In case of frame synchronous mapping of the ODUk client signal, an IAE signal has to be added to the SM overhead. + +The information flow and processing of the OTUkV\_TT\_So function is defined with reference to Figures 13-9 and 13-10. + +##### Symbol + +![Diagram of the OTUkV_TT_So function showing an OTUkV block with multiple inputs and outputs.](ad4da36431850ac19ba59bb74ec29dc9_img.jpg) + +The diagram shows a single OTUkV block, represented by a triangle. It has an input OTUkV\_AP at its top vertex. On its left side, there is an input OTUkV\_TT\_So\_MP. On its right side, there is an input OTUkV\_RP. At its bottom vertex, there is an output OTUkV\_TCP. Next to the bottom output is the label $k = 1, 2, 3, 4$ . A label G.798(10)\_F13-9 is positioned below the bottom output. + +Diagram of the OTUkV\_TT\_So function showing an OTUkV block with multiple inputs and outputs. + +Figure 13-9 – OTUkV\_TT\_So function + +##### Interfaces + +**Table 13-3 – OTUkV\_TT\_So inputs and outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| OTUkV_AP:
OTUkV_AI_CK
OTUkV_AI_D
OTUkV_AI_FS
OTUkV_AI_MFS (Note 1)
OTUkV_AI_IAE (Note 2)
OTUkV_RP:
OTUkV_RI_BDI
OTUkV_RI_BEI
OTUkV_RI_BIAE (Note 2)
OTUkV_TT_So_MP:
OTUkV_TT_So_MI_TxTI | OTUkV_TCP:
OTUkV_CI_CK
OTUkV_CI_D
OTUkV_CI_FS
OTUkV_CI_MFS (Note 1) | +| NOTE 1 – If OTUkV has a multiframe. | | +| NOTE 2 – In case of frame synchronous mapping of ODUk client signal. | | + +##### Processes + +The processes associated with the OTUkV\_TT\_So function are as depicted in Figure 13-10. + +**SMOH-TTI:** The trail trace identifier is inserted in the TTI byte position of the SM field. Its value is derived from reference point OTUk\_TT\_So\_MP. The trail trace format is described in clause 15.2 of [ITU-T G.709]. + +**SMOH-BDI:** The backward defect indication is inserted in the BDI field of the SMOH. Its value is derived from reference point OTUk\_RP. Upon the declaration/clearing of aBDI at the termination sink function, the trail termination source function shall have inserted/removed the BDI indication within 50 ms. The BDI coding is outside the scope of this Recommendation. + +**SMOH-BEI:** The number of errors indicated in RI\_BEI is encoded in the BEI field of the SMOH. Upon the detection of a number of errors at the termination sink function, the trail termination source function shall have inserted that value in the BEI bits within 50 ms. The BEI coding is outside the scope of this Recommendation. + +**SMOH-signal quality supervision:** The calculated signal quality supervision code is inserted into the signal quality supervision field of the SMOH. The signal supervision code is outside the scope of this Recommendation. + +**SMOH-IAE:** If a frame synchronous mapping for the ODUk is used, the incoming alignment error information AI\_IAE is inserted into the IAE field of the SMOH. Upon the declaration of AI\_IAE, the function shall insert the IAE indication for the next 16 multiframes. Each new declaration of AI\_IAE restarts the 16 multiframe insertion time. The IAE coding is outside the scope of this Recommendation. + +**SMOH-BIAE:** If a frame synchronous mapping for the ODUk is used, the backward incoming error information RI\_BIAE is inserted into the BIAE field of the SMOH. Upon the detection of the incoming alignment error at the termination sink function, the trail termination source function shall have inserted that value in the BIAE fields within 50 ms. The BIAE coding is outside the scope of this Recommendation. + +The format of the OTUkV frame and overhead is outside the scope of this Recommendation. + +![Figure 13-10 – OTUkV_TT_So processes. This block diagram illustrates the signal processing flow for the OTUkV_TT_So function. At the top, input signals AI_D, AI_CK, AI_FS, AI_MFS, and AI_IAE enter the OTUkV_AP block. AI_D, AI_CK, AI_FS, and AI_MFS are processed through a 'Compute BIP8' block and then into a 'SMOH insertion' block. AI_IAE is processed through an 'Insert IAE' block. The 'SMOH insertion' block outputs CI_D, CI_CK, CI_FS, and CI_MFS signals to the OTUkV_TCP block. The 'Compute BIP8' block also feeds into an 'Insert BIP8' block. The 'Insert BIP8' block feeds into an 'Insert BDI' block, which in turn feeds into an 'Insert BEI' block. The 'Insert BEI' block feeds into an 'Insert BIAE' block, which feeds into an 'Insert TTI' block. The 'Insert TTI' block feeds into the 'Insert IAE' block. The 'Insert IAE' block feeds into the 'SMOH insertion' block. The 'SMOH insertion' block also receives feedback from the 'Insert BDI', 'Insert BEI', 'Insert BIAE', and 'Insert TTI' blocks. The 'SMOH insertion' block outputs RI_BDI, RI_BEI, RI_BIAE, and MI_TxTI signals to the OTUkV_RP and OTUkV_TT_So_MP blocks. The diagram is labeled G.798(10)_F13-10.](9dc88fb2c48bc64047fc3e79814f1d47_img.jpg) + +Figure 13-10 – OTUkV\_TT\_So processes. This block diagram illustrates the signal processing flow for the OTUkV\_TT\_So function. At the top, input signals AI\_D, AI\_CK, AI\_FS, AI\_MFS, and AI\_IAE enter the OTUkV\_AP block. AI\_D, AI\_CK, AI\_FS, and AI\_MFS are processed through a 'Compute BIP8' block and then into a 'SMOH insertion' block. AI\_IAE is processed through an 'Insert IAE' block. The 'SMOH insertion' block outputs CI\_D, CI\_CK, CI\_FS, and CI\_MFS signals to the OTUkV\_TCP block. The 'Compute BIP8' block also feeds into an 'Insert BIP8' block. The 'Insert BIP8' block feeds into an 'Insert BDI' block, which in turn feeds into an 'Insert BEI' block. The 'Insert BEI' block feeds into an 'Insert BIAE' block, which feeds into an 'Insert TTI' block. The 'Insert TTI' block feeds into the 'Insert IAE' block. The 'Insert IAE' block feeds into the 'SMOH insertion' block. The 'SMOH insertion' block also receives feedback from the 'Insert BDI', 'Insert BEI', 'Insert BIAE', and 'Insert TTI' blocks. The 'SMOH insertion' block outputs RI\_BDI, RI\_BEI, RI\_BIAE, and MI\_TxTI signals to the OTUkV\_RP and OTUkV\_TT\_So\_MP blocks. The diagram is labeled G.798(10)\_F13-10. + +Figure 13-10 – OTUkV\_TT\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 13.2.2.2 OTUkV trail termination sink function (OTUkV\_TT\_Sk) + +The OTUkV\_TT\_Sk function reports the state of the OTUkV trail. It computes the signal quality supervision code, extracts section monitoring overhead (SMOH) – including the TTI, signal quality supervision, BDI and BEI signals – in the SM overhead field from the OTUkV signal at its OTUkV\_TCP, detects for TIM, DEG and BDI defects, counts during one-second periods errors (detected via the signal quality supervision) and defects to feed performance monitoring when connected, makes the TTI available to network management, and forwards the error and defect information as backward indications to the companion OTUkV\_TT\_So function. In case of frame synchronous mapping of the ODUk client signal, an IAE signal has to be extracted from the SM overhead. + +The information flow and processing of the OTUkV\_TT\_Sk function is defined with reference to Figures 13-11 and 13-12. + +##### Symbol + +![Symbol diagram for the OTUkV_TT_Sk function. It shows a central triangle labeled 'OTUkV'. An arrow points up from the top vertex to 'OTUkV_AP'. An arrow points down from 'OTUkV_TCP' to the bottom vertex, with 'k = 1, 2, 3, 4' written next to it. A double-headed arrow points left from the left vertex to 'OTUkV_TT_Sk_MP'. An arrow points right from the right vertex to 'OTUkV_RP'. Below the diagram is the text 'G.798(10)_F13-11'.](708e7ef81dbf726e558047afe57d6ff7_img.jpg) + +Symbol diagram for the OTUkV\_TT\_Sk function. It shows a central triangle labeled 'OTUkV'. An arrow points up from the top vertex to 'OTUkV\_AP'. An arrow points down from 'OTUkV\_TCP' to the bottom vertex, with 'k = 1, 2, 3, 4' written next to it. A double-headed arrow points left from the left vertex to 'OTUkV\_TT\_Sk\_MP'. An arrow points right from the right vertex to 'OTUkV\_RP'. Below the diagram is the text 'G.798(10)\_F13-11'. + +Figure 13-11 – OTUkV\_TT\_Sk function + +##### Interfaces + +Table 13-4 – OTUkV\_TT\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OTUkV_TCP:
OTUkV_CI_CK
OTUkV_CI_D
OTUkV_CI_FS
OTUkV_CI_MFS (Note 1)
OTUkV_CI_SSF
OTUkV_TT_Sk_MP:
OTUkV_TT_Sk_MI_ExSAPI
OTUkV_TT_Sk_MI_ExDAPI
OTUkV_TT_Sk_MI_GetAcTI
OTUkV_TT_Sk_MI_TIMDetMo
OTUkV_TT_Sk_MI_TIMActDis
OTUkV_TT_Sk_MI_DEGThr
OTUkV_TT_Sk_MI_DEGM
OTUkV_TT_Sk_MI_1second | OTUkV_AP:
OTUkV_AI_CK
OTUkV_AI_D
OTUkV_AI_FS
OTUkV_AI_MFS (Note 1)
OTUkV_AI_TSF
OTUkV_AI_TSD
OTUkV_RP:
OTUkV_RI_BDI
OTUkV_RI_BEI
OTUkV_RI_BIAE (Note 2)
OTUkV_TT_Sk_MP:
OTUkV_TT_Sk_MI_AcTI
OTUkV_TT_Sk_MI_cTIM
OTUkV_TT_Sk_MI_cDEG
OTUkV_TT_Sk_MI_cBDI
OTUkV_TT_Sk_MI_cSSF
OTUkV_TT_Sk_MI_pN_EBC
OTUkV_TT_Sk_MI_pN_DS
OTUkV_TT_Sk_MI_pF_EBC
OTUkV_TT_Sk_MI_pF_DS
OTUkV_TT_Sk_MI_pBIAE (Note 2)
OTUkV_TT_Sk_MI_pIAE (Note 2) | +| NOTE 1 – If OTUkV has a multiframe. | | +| NOTE 2 – In case of frame synchronous mapping of ODUk client signal. | | + +##### Processes + +The processes associated with the OTUkV\_TT\_Sk function are as depicted in Figure 13-12. + +**SMOH-signal quality supervision:** The signal quality supervision code is extracted from the signal quality field of the SMOH. The signal supervision code is outside the scope of this Recommendation. + +**SMOH-TTI:** The trail trace identifier shall be recovered from TTI field of the SMOH as defined in clause 8.6. The accepted value of the TTI is available at the MP (MI\_AcTI). + +**SMOH-BDI:** The backward defect indication shall be recovered from BDI field of the SMOH. It shall be used for BDI defect detection. The BDI code is outside the scope of this Recommendation. + +**SMOH-BEI:** The BEI shall be recovered from the BEI field in the SMOH. It shall be used to determine if a far-end errored block (nF\_B) has occurred. The BEI code is outside the scope of this Recommendation. + +**SMOH-IAE:** If a frame synchronous mapping for the ODUk client layer is used, the incoming alignment error information shall be recovered from the IAE field of the SMOH. It shall be used for IAE defect detection. The IAE code is outside the scope of this Recommendation. + +The format of the OTUkV frame and overhead is outside the scope of this Recommendation. + +![Figure 13-12 – OTUkV_TT_Sk processes. This block diagram illustrates the internal processes of the OTUkV_TT_Sk function. At the top, the OTUkV_AP layer provides inputs: AI_TSD, AI_TSF, AI_MFS, AI_FS, AI_CK, and AI_D. Below this, the diagram is divided into several functional blocks. On the left, a vertical label 'OTUkV_TT_Sk_MP and OTUkV_RP' spans the middle section. The 'Consequent actions' block receives inputs from RI_BDI, RI_BIAE, and MI_TIMActDis, and outputs aTSD, aTSF, CI_SSF, dTIM, dDEG, and dIAE. The 'Process TTI' block receives MI_AcTI, MI_ExSAPI, MI_ExDAPI, MI_GetAcTI, and MI_TIMDetMo, and outputs RxTI to an 'Extract TTI' block. The 'Defect correlations' block receives MI_cTIM, MI_cDEG, MI_cBDI, and MI_cSSF, and outputs dTIM, dDEG, dBDI, and CI_SSF. The 'Performance monitoring' block receives MI_pIAE, MI_pN_BIAE, MI_pN_EBC, MI_pN_DS, MI_pF_EBC, MI_pF_DS, MI_lsecond, and nN_B, and outputs aTSF, dBIAE, dBBDI, and nF_B to 'Extract IAE', 'Extract BDI', and 'Extract BEI' blocks respectively. A 'Process errors' block receives dDEG and nBIPV, and outputs nN_B to a 'Compare' block. The 'Compare' block also receives inputs from 'Extract BIP8' and 'Compute BIP8' blocks. A vertical 'SMOH access' block on the right provides data to the 'Extract' blocks and receives data from the 'Compute BIP8' block. At the bottom, the OTUkV_TCP layer provides inputs: CI_SSF, CI_MFS, CI_FS, CI_CK, and CI_D. The diagram is labeled G.798(10)_F13-12 in the bottom right corner.](c1b762c358fd423d6686563b3fde7750_img.jpg) + +Figure 13-12 – OTUkV\_TT\_Sk processes. This block diagram illustrates the internal processes of the OTUkV\_TT\_Sk function. At the top, the OTUkV\_AP layer provides inputs: AI\_TSD, AI\_TSF, AI\_MFS, AI\_FS, AI\_CK, and AI\_D. Below this, the diagram is divided into several functional blocks. On the left, a vertical label 'OTUkV\_TT\_Sk\_MP and OTUkV\_RP' spans the middle section. The 'Consequent actions' block receives inputs from RI\_BDI, RI\_BIAE, and MI\_TIMActDis, and outputs aTSD, aTSF, CI\_SSF, dTIM, dDEG, and dIAE. The 'Process TTI' block receives MI\_AcTI, MI\_ExSAPI, MI\_ExDAPI, MI\_GetAcTI, and MI\_TIMDetMo, and outputs RxTI to an 'Extract TTI' block. The 'Defect correlations' block receives MI\_cTIM, MI\_cDEG, MI\_cBDI, and MI\_cSSF, and outputs dTIM, dDEG, dBDI, and CI\_SSF. The 'Performance monitoring' block receives MI\_pIAE, MI\_pN\_BIAE, MI\_pN\_EBC, MI\_pN\_DS, MI\_pF\_EBC, MI\_pF\_DS, MI\_lsecond, and nN\_B, and outputs aTSF, dBIAE, dBBDI, and nF\_B to 'Extract IAE', 'Extract BDI', and 'Extract BEI' blocks respectively. A 'Process errors' block receives dDEG and nBIPV, and outputs nN\_B to a 'Compare' block. The 'Compare' block also receives inputs from 'Extract BIP8' and 'Compute BIP8' blocks. A vertical 'SMOH access' block on the right provides data to the 'Extract' blocks and receives data from the 'Compute BIP8' block. At the bottom, the OTUkV\_TCP layer provides inputs: CI\_SSF, CI\_MFS, CI\_FS, CI\_CK, and CI\_D. The diagram is labeled G.798(10)\_F13-12 in the bottom right corner. + +**Figure 13-12 – OTUkV\_TT\_Sk processes** + +##### Defects + +The function shall detect dTIM, dDEG, dBBDI and, if a frame synchronous mapping for the ODUk client layer is used, it shall detect dIAE defects. + +**dTIM:** See clause 6.2.2.1; dTIM shall be set to false during CI\_SSF. + +**dDEG:** See clause 6.2.3.4. + +NOTE 1 – IAE (if supported) suppresses the one-second near-end errored block count, which is the input for the dDEG detection. This avoids wrong dDEG declaration due to alignment errors already incoming in an OTUkV trail. + +**dBDI:** The dBDI detection depends on the specific frame structure and is outside the scope of this Recommendation; dBDI shall be set to false during CI\_SSF. + +**dIAE:** The dIAE detection depends on the specific frame structure and is outside the scope of this Recommendation; dIAE shall be set to false during CI\_SSF and dTIM. + +**dBIAE:** The dBIAE detection depends on the specific frame structure and is outside the scope of this Recommendation; dTIM shall be set to false during CI\_SSF and dTIM. + +NOTE 2 – IAE and BIAE are only required in case of frame synchronous mapping of the ODUk into the OTUkV. + +##### Consequent actions + +The function shall perform the following consequent actions: + +aBDI $\leftarrow$ CI\_SSF or dTIM + +aBEI $\leftarrow$ nBIPV + +aBIAE $\leftarrow$ dIAE + +aTSF $\leftarrow$ CI\_SSF or (dTIM and (not TIMActDis)) + +aTSD $\leftarrow$ dDEG + +##### Defect correlations + +The function shall perform the following defect correlations to determine the most probable fault cause. This fault cause shall be reported to the EMF. + +cTIM $\leftarrow$ dTIM and (not CI\_SSF) + +cDEG $\leftarrow$ dDEG and (not CI\_SSF) and (not (dTIM and (not TIMActDis))) + +cBDI $\leftarrow$ dBDI and (not CI\_SSF) and (not (dTIM and (not TIMActDis))) + +cSSF $\leftarrow$ CI\_SSF + +##### Performance monitoring + +The function shall perform the following performance monitoring primitives processing. The performance monitoring primitives shall be reported to the EMF. + +pN\_DS $\leftarrow$ CI\_SSF or dTI + +pF\_DS $\leftarrow$ dBDI + +pN\_EBC $\leftarrow \sum nN\_B$ + +NOTE 3 – During CI\_SSF, no errored blocks shall be counted. + +pF\_EBC $\leftarrow \sum nF\_B$ + +NOTE 4 – During CI\_SSF, no errored blocks shall be counted. + +pBIAE $\leftarrow$ dBIAE + +NOTE 5 – pBIAE is activated at the end of a second if dBIAE was active once during the second. + +pIAE $\leftarrow$ dIAE + +NOTE 6 – pIAE is activated at the end of a second if dIAE was active once during the second. + +NOTE 7 – pBIAE and pIAE are only defined in case of frame synchronous mapping of the ODUk into the OTUkV. + +NOTE 8 – pIAE and pBIAE are used for the suppression of the PM data in the equipment management functions (see [ITU-T G.874]). If pBIAE is active, the F\_DS and F\_EBC values of the previous and current second have to be discarded (EBC = 0 and DS = false). If pIAE is active, the N/F\_DS and N/F\_EBC values of the previous and current second have to be discarded (EBC = 0 and DS = false). The previous second has to be included due to the delay of the IAE information coming from the remote source. + +## 13.3 Adaptation functions + +### 13.3.1 OTU to ODU adaptation function (OTU/ODU\_A) + +The OTU to ODU adaptation functions perform the adaptation between the OTU layer adapted information and the characteristic information of an ODU layer signal. + +#### 13.3.1.1 OTU to ODU adaptation source function (OTU/ODU\_A\_So) + +The OTU/ODU\_A\_So function creates the OTU signal and maps the ODU signal frame synchronous into this OTU signal as defined in [ITU-T G.709]. Additionally, the OTUk/ODUk\_A\_So function provides access to the ODUk SM APS overhead if it is OPERATIONAL. + +The information flow and processing of the OTU/ODU\_A\_So functions is defined with reference to Figures 13-13 and 13-14. + +##### Symbol + +![Diagram showing the OTU/ODU_A_So function symbol. It consists of two identical trapezoidal blocks. The left block is labeled 'OTUk/ODUk' and has an input 'ODUk_CP' from the top and 'OTUk/ODUk_A_So_MP' from the left. Its output is 'OTUk_AP' at the bottom, with a label 'k = 0, 1, 2, 3, 4, 25u, 25, 50u, 50' next to it. The right block is labeled 'OTUCn/ODUCn' and has an input 'ODUCn_CP' from the top and 'OTUCn/ODUCn_A_So_MP' from the left. Its output is 'OTUCn_AP' at the bottom. Below the right block is the text 'G.798(17)-Amd.4(22)_F13-13'.](a265aba1737da6f0200faac85366b163_img.jpg) + +Diagram showing the OTU/ODU\_A\_So function symbol. It consists of two identical trapezoidal blocks. The left block is labeled 'OTUk/ODUk' and has an input 'ODUk\_CP' from the top and 'OTUk/ODUk\_A\_So\_MP' from the left. Its output is 'OTUk\_AP' at the bottom, with a label 'k = 0, 1, 2, 3, 4, 25u, 25, 50u, 50' next to it. The right block is labeled 'OTUCn/ODUCn' and has an input 'ODUCn\_CP' from the top and 'OTUCn/ODUCn\_A\_So\_MP' from the left. Its output is 'OTUCn\_AP' at the bottom. Below the right block is the text 'G.798(17)-Amd.4(22)\_F13-13'. + +Figure 13-13 – OTU/ODU\_A\_So function + +##### Interfaces + +Table 13-5 – OTU/ODU\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| ODU_CP:
ODU_CI_CK
ODU_CI_D
ODU_CI_FS
ODU_CI_MFS
ODU_CI_APS
OTU/ODU_A_So_MP:
OTU/ODU_A_So_MI_AdminState
OTU/ODU_A_So_MI_Mode
OTU/ODU_A_So_MI_APS_EN (Note)
OTU/ODU_A_So_MI_APS_LVL (Note) | OTU_AP:
OTU_AI_CK
OTU_AI_D
OTU_AI_FS
OTU_AI_MFS
OTU_AI_IAE | +| NOTE – For OTUk/ODUk_A_So only. | | + +##### Processes + +The processes associated with the OTU/ODU\_A\_So function are as depicted in Figure 13-14. + +**ODU-LCK:** The function shall generate the ODU-LCK signal as defined in clause 16.5 of [ITU-T G.709]. The clock, frame start and multiframe start are defined by the incoming ODUk signal. + +**Mode:** If the MI\_Mode has the value OPERATIONAL, the following processes shall be performed. If the MI\_Mode has the value TRANSPARENT, all information shall be passed through transparently and the following processes shall not be performed. + +**Selector:** If MI\_Mode is OPERATIONAL, the normal signal may be replaced by the ODU-LCK signal. ODU-LCK signal is selected if the MI\_AdminState is LOCKED. + +**ODUk server layer APS:** If MI\_Mode is OPERATIONAL and APS is enabled (MI\_APS\_EN is true), the OTUk/ODUk\_A\_So function shall insert the CI\_APS value into the ODUk APS/PCC[MI\_APS\_LVL] field, which is available once per eight ODUk frames when MFAS bits 6, 7, 8 is equal to MI\_APS\_LVL. + +NOTE 1 – The ODUk SM APS information may be present in the case where the ODUk signal contains an ODU-AIS, ODU-LCK or ODU-OCI maintenance signal. The ODU-LCK maintenance signal may be inserted in this adaptation source function. ODUk SNC/I protection is unable to detect the insertion of such ODU-LCK and will not perform a protection switch. + +**OTU clock generation:** For k = 0, 1, 2, 3, 4, the function shall generate the OTUk clock (AI\_CK) by multiplying the incoming ODUk clock (CI\_CK) by 255/239 to the OTUk frequency as listed in Table 7-1 of [ITU-T G.709]. For k = 25, 25u, 50, 50u, the OTUk clock (AI\_CK) shall be the ODUk clock (CI\_CK). The OTUCn clock (AI\_CK) shall be the ODUCn clock (CI\_CK). + +For the case that an ODU signal is not terminated in the network element (e.g., it is through connected from an OTU input to an OTU output), the clock parameters and jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCr clock), apply. Otherwise, the clock requirements are defined in the ODUP/client adaptation functions. + +NOTE 2 – The OTU/ODU\_A\_Sk and So clocks are concentrated in a single ODCr clock in [ITU-T G.8251]. + +The function shall generate the OTU frame start reference signals (AI\_FS), which is derived from the incoming ODU frame start (CI\_FS). + +The function shall generate the OTU multiframe start reference signals (AI\_MFS), which is derived from the incoming ODU multiframe start (CI\_MFS). + +**Incoming alignment error (IAE):** If the incoming ODU frame start (CI\_FS) position is not at the expected frame start position, the incoming alignment error IAE shall be activated. IAE shall be deactivated if the incoming ODU frame start (CI\_FS) position is at the expected frame start position. The expected frame start position is based on the previous incoming ODU frame start. + +**Mapping:** The function shall map the incoming ODU frame (CI\_D) into the OTU frame (AI\_D) as defined in clause 11.1 of [ITU-T G.709]. + +![Figure 13-14: OTU/ODU_A_So processes block diagram. The diagram shows the internal structure of the OTU/ODU_A_So function. On the left, the vertical label 'OTU/ODU_A_So_MP' is present. Inputs include 'MI_AdminState', 'MI_Mode', 'MI_APS_EN', and 'MI_APS_LVL'. These connect to an 'APS' block (labeled 'OTUk/ODUk only') and a 'Select normal/LCK' block. The 'Select normal/LCK' block also receives 'D_normal' and 'D_LCK' from a 'Generator ODU-LCK' block. The 'APS' block connects to a 'Mapping' block. The 'Mapping' block outputs 'AI_D'. The 'Generator ODU-LCK' block also connects to 'OTU clock, FS and MFS generation' and 'IAE detection' blocks. These two blocks output 'AI_CK', 'AI_MFS', 'AI_FS', and 'AI_IAE' respectively. The vertical label 'OTU_AP' is at the bottom. The horizontal labels 'CI_APS', 'CI_D', 'ODU_CP', 'CI_CK', 'CI_MFS', and 'CI_FS' are at the top. A reference 'G.798(17)-Amd.1(18)_F13-14' is at the bottom right.](fda85db2e355bb8e3edcd5a74bf3d673_img.jpg) + +Figure 13-14: OTU/ODU\_A\_So processes block diagram. The diagram shows the internal structure of the OTU/ODU\_A\_So function. On the left, the vertical label 'OTU/ODU\_A\_So\_MP' is present. Inputs include 'MI\_AdminState', 'MI\_Mode', 'MI\_APS\_EN', and 'MI\_APS\_LVL'. These connect to an 'APS' block (labeled 'OTUk/ODUk only') and a 'Select normal/LCK' block. The 'Select normal/LCK' block also receives 'D\_normal' and 'D\_LCK' from a 'Generator ODU-LCK' block. The 'APS' block connects to a 'Mapping' block. The 'Mapping' block outputs 'AI\_D'. The 'Generator ODU-LCK' block also connects to 'OTU clock, FS and MFS generation' and 'IAE detection' blocks. These two blocks output 'AI\_CK', 'AI\_MFS', 'AI\_FS', and 'AI\_IAE' respectively. The vertical label 'OTU\_AP' is at the bottom. The horizontal labels 'CI\_APS', 'CI\_D', 'ODU\_CP', 'CI\_CK', 'CI\_MFS', and 'CI\_FS' are at the top. A reference 'G.798(17)-Amd.1(18)\_F13-14' is at the bottom right. + +Figure 13-14 – OTU/ODU\_A\_So processes + +**Defects:** None. + +##### **Consequent actions** + +The function shall perform the following consequent actions: + +aIAE ← IAE + +**Defect Correlations:** None. + +**Performance monitoring:** None. + +#### **13.3.1.2 OTU to ODU adaptation sink function (OTU/ODU\_A\_Sk)** + +The OTU/ODU\_A\_Sk extracts the ODU signal from the OTU. It may insert ODU-AIS under signal fail conditions. Additionally, the OTUk/ODUk\_A\_Sk function provides access to the ODUk SM APS overhead if it is OPERATIONAL. + +The information flow and processing of the OTU/ODU\_A\_Sk functions is defined with reference to Figures 13-15 and 13-16. + +##### **Symbol** + +![Figure 13-15: OTUk/ODUk_A_Sk function symbol diagram. It shows two trapezoidal symbols representing the function. The left symbol is labeled 'OTUk/ODUk' and has an input 'OTUk/ODUk_A_Sk_MP' on the left, an input 'OTUk_AP' at the bottom (with parameter 'k = 1, 2, 3, 4, 25u, 25, 50u, 50'), and an output 'ODUk_CP' at the top. The right symbol is labeled 'OTUCn/ODUCn' and has an input 'OTUCn/ODUCn_A_Sk_MP' on the left, an input 'OTUCn_AP' at the bottom, and an output 'ODUCn_CP' at the top. A reference 'G.798(17)-Amd.4(22)_F13-15' is at the bottom right.](7d78469417c76901ecf6e36600a721cb_img.jpg) + +Figure 13-15: OTUk/ODUk\_A\_Sk function symbol diagram. It shows two trapezoidal symbols representing the function. The left symbol is labeled 'OTUk/ODUk' and has an input 'OTUk/ODUk\_A\_Sk\_MP' on the left, an input 'OTUk\_AP' at the bottom (with parameter 'k = 1, 2, 3, 4, 25u, 25, 50u, 50'), and an output 'ODUk\_CP' at the top. The right symbol is labeled 'OTUCn/ODUCn' and has an input 'OTUCn/ODUCn\_A\_Sk\_MP' on the left, an input 'OTUCn\_AP' at the bottom, and an output 'ODUCn\_CP' at the top. A reference 'G.798(17)-Amd.4(22)\_F13-15' is at the bottom right. + +Figure 13-15 – OTUk/ODUk\_A\_Sk function + +##### Interfaces + +**Table 13-6 – OTU/ODU\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| OTU_AP:
OTU_AI_CK
OTU_AI_D
OTU_AI_FS
OTU_AI_MFS
OTU_AI_TSF
OTU_AI_TSD
OTU/ODUk_A_Sk_MP:
OTU/ODU_A_Sk_MI_AdminState
OTU/ODU_A_Sk_MI_Mode
OTU/ODU_A_Sk_MI_APS_EN (Note)
OTU/ODU_A_Sk_MI_APS_LVL (Note) | ODU_CP:
ODU_CI_CK
ODU_CI_D
ODU_CI_FS
ODU_CI_MFS
ODU_CI_SSF
ODU_CI_SSD
ODU_CI_APS | +| NOTE – For OTUk/ODUk_A_So only. | | + +##### Processes + +The processes associated with the OTUk/ODUk\_A\_Sk function are as depicted in Figure 13-16. + +**ODU clock, FS and MFS signal generation:** For k= 0 ,1, 2, 3, 4, the function shall generate the ODUk clock (CI\_CK) by dividing the incoming OTUk clock (AI\_CK) down by a factor of 239/255 to the particular ODUk clock as listed in Table 7-2 of [ITU-T G.709]. For k = 25, 25u ,50, 50u, the ODUk clock (AI\_CK) shall be the OTUk clock (CI\_CK). The ODUk clock (AI\_CK) shall be the OTUk clock (CI\_CK). + +For the case that an ODU signal is not terminated in the network element (e.g., it is through connected from an OTU input to an OTU output), the clock parameters and jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCr clock), apply. Otherwise, the clock requirements are defined in the ODUP/client adaptation functions. + +NOTE 1 – The OTU/ODU\_A\_Sk and So clocks are concentrated in a single ODCr clock in [ITU-T G.8251]. + +The function shall generate the ODU frame start reference signals (CI\_FS), which is derived from the incoming OTU frame start (AI\_FS). + +The function shall generate the ODU multiframe start reference signals (CI\_MFS), which is derived from the incoming OTU multiframe start (AI\_MFS). + +**Extract ODU from OTU:** The function shall extract the ODU frame (CI\_D) from the incoming OTU frame (AI\_D) as defined in clause 11.1 and 11.3 of [ITU-T G.709]. + +**ODUk server layer APS:** When APS is enabled (MI\_APS\_EN is true), the OTUk/ODUk\_A\_Sk function shall extract the information from the ODUk APS/PCC[MI\_APS\_LVL] field, which is available once per eight ODUk frames when the value of the MFAS bits 6, 7, 8 is equal to MI\_APS\_LVL, and apply the extracted information to the CI\_APS. + +NOTE 2 – The ODUk SM APS information may be present in the case where the ODUk signal contains an ODU-AIS, ODU-LCK or ODU-OCI maintenance signal. The ODU-LCK maintenance signal may have been inserted in the far-end adaptation source function. ODUk SNC/I protection is unable to detect the insertion of such ODU-LCK and will not perform a protection switch. + +**ODU-LCK, ODU-AIS:** The function shall generate the ODU-LCK and ODU-AIS signals as defined in [ITU-T G.709]. The clock, frame start and multiframe start shall be independent from the incoming clock. The clock has to be within the frequency range as given in Table 7-2 of + +[ITU-T G.709]. Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +**Mode:** If the MI\_Mode has the value OPERATIONAL, the following processes shall be performed. If the MI\_Mode has the value TRANSPARENT, all information shall be passed through transparently and the following processes shall not be performed. + +**Selector:** If MI\_Mode is OPERATIONAL, the normal signal may be replaced by either the ODU-AIS or the ODU-LCK signal. ODU-LCK signal is selected if the MI\_AdminState is LOCKED. ODU-AIS is selected if MI\_AdminState is not LOCKED and aAIS is true. If MI\_Mode has the value TRANSPARENT, the normal signal is always selected. + +![Figure 13-16 – OTU/ODU_A_Sk processes. This block diagram illustrates the internal logic for OTU/ODU_A_Sk. On the left, the 'OTU/ODU_A_Sk_MP' block receives inputs: MI_AdminState, MI_Mode, MI_APS_EN, and MI_APS_LVL. It connects to a 'Consequent actions' block which outputs aTSD, aTSF, and aAIS. The 'Consequent actions' block also receives AI_TSD and AI_TSF. The 'Consequent actions' block connects to a 'Select normal/AIS/LCK' block. This block has three outputs: AIS, LCK, and Normal. The 'AIS' and 'LCK' outputs are connected to 'Generate ODU-AIS' and 'Generate ODU-LCK' blocks respectively. The 'Normal' output is connected to an 'ODU data demapping, clock (ODCr), FS and MFS generation' block. The 'APS' block (containing OTUK/ODUk only) receives CI_APS and connects to the 'Select normal/AIS/LCK' block. The 'APS' block also receives inputs from the 'Consequent actions' block. The 'ODU data demapping, clock (ODCr), FS and MFS generation' block outputs D, CK, FS, and MFS. These are connected to the 'OTU_AP' block which outputs AI_D, AI_CK, AI_FS, and AI_MFS. The 'OTU_AP' block also receives inputs from the 'Consequent actions' block. The 'OTU/ODU_A_Sk_MP' block also outputs CI_TSD, CI_TSF, CI_APS, CI_D, CI_CK, CI_FS, and CI_MFS.](24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg) + +Figure 13-16 – OTU/ODU\_A\_Sk processes. This block diagram illustrates the internal logic for OTU/ODU\_A\_Sk. On the left, the 'OTU/ODU\_A\_Sk\_MP' block receives inputs: MI\_AdminState, MI\_Mode, MI\_APS\_EN, and MI\_APS\_LVL. It connects to a 'Consequent actions' block which outputs aTSD, aTSF, and aAIS. The 'Consequent actions' block also receives AI\_TSD and AI\_TSF. The 'Consequent actions' block connects to a 'Select normal/AIS/LCK' block. This block has three outputs: AIS, LCK, and Normal. The 'AIS' and 'LCK' outputs are connected to 'Generate ODU-AIS' and 'Generate ODU-LCK' blocks respectively. The 'Normal' output is connected to an 'ODU data demapping, clock (ODCr), FS and MFS generation' block. The 'APS' block (containing OTUK/ODUk only) receives CI\_APS and connects to the 'Select normal/AIS/LCK' block. The 'APS' block also receives inputs from the 'Consequent actions' block. The 'ODU data demapping, clock (ODCr), FS and MFS generation' block outputs D, CK, FS, and MFS. These are connected to the 'OTU\_AP' block which outputs AI\_D, AI\_CK, AI\_FS, and AI\_MFS. The 'OTU\_AP' block also receives inputs from the 'Consequent actions' block. The 'OTU/ODU\_A\_Sk\_MP' block also outputs CI\_TSD, CI\_TSF, CI\_APS, CI\_D, CI\_CK, CI\_FS, and CI\_MFS. + +G.798(17)-Amd.1(18)\_F13-16 + +Figure 13-16 – OTU/ODU\_A\_Sk processes + +**Defects:** None. + +##### Consequent actions + +The function shall perform the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF and (not MI\_AdminState = LOCKED) + +aAIS $\leftarrow$ AI\_TSF and (not MI\_AdminState = LOCKED) + +aSSD $\leftarrow$ AI\_TSD and (not MI\_AdminState = LOCKED) + +On declaration of aAIS, the function shall output an all-ONEs pattern/signal within two frames. On clearing aAIS, the all-ONEs pattern/signal shall be removed within two frames, with normal data being output. The AIS clock, frame start and multiframe start shall be independent from the incoming clock, frame start and multiframe start. The AIS clock has to be the frequency range as given in Table 7-2 of [ITU-T G.709]. Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock) apply. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 13.3.2 OTUkV to ODUk adaptation function (OTUkV/ODUk\_A) + +The OTUkV to ODUk adaptation functions perform the adaptation between the OTUkV layer adapted information and the characteristic information of an ODUk layer signal. + +#### 13.3.2.1 OTUkV to ODUk adaptation source function (OTUkV/ODUk\_A\_So) + +The OTUkV/ODUk\_A\_So function creates the OTUkV signal and maps the ODUk signal into this OTUkV. It provides access to the ODUk SM APS overhead. + +The information flow and processing of the OTUkV/ODUk\_A\_So functions is defined with reference to Figures 13-17 and 13-18. + +##### Symbol + +![Diagram of the OTUkV/ODUk_A_So function symbol. It shows a central block labeled 'OTUkV/ODUk'. An input 'ODUk_CP' enters from the top. An input 'OTUkV/ODUk_A_So_MP' enters from the left. An output 'OTUkV_AP' exits from the bottom, with a label 'k = 1, 2, 3, 4' next to it. The diagram is labeled 'G.798(10)_F13-17'.](85680f3dcbe15424dd54fa3fd9e1c90d_img.jpg) + +Diagram of the OTUkV/ODUk\_A\_So function symbol. It shows a central block labeled 'OTUkV/ODUk'. An input 'ODUk\_CP' enters from the top. An input 'OTUkV/ODUk\_A\_So\_MP' enters from the left. An output 'OTUkV\_AP' exits from the bottom, with a label 'k = 1, 2, 3, 4' next to it. The diagram is labeled 'G.798(10)\_F13-17'. + +Figure 13-17 – OTUkV/ODUk\_A\_So function + +##### Interfaces + +Table 13-7 – OTUkV/ODUk\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------| +| ODUk_CP:
ODUk_CI_CK
ODUk_CI_D
ODUk_CI_FS
ODUk_CI_MFS
ODUk_CI_APS
OTUkV/ODUk_A_So_MP:
OTUkV/ODUk_A_So_MI_AdminState
OTUkV/ODUk_A_So_MI_APS_EN
OTUkV/ODUk_A_So_MI_APS_LVL | OTUkV_AP:
OTUkV_AI_CK
OTUkV_AI_D
OTUkV_AI_FS
OTUkV_AI_MFS (Note 1)
OTUkV_AI_IAE (Note 2) | +| NOTE 1 – If the OTUkV has a multiframe. | | +| NOTE 2 – In case of frame synchronous mapping of ODUk client signal. | | + +##### Processes + +The processes associated with the OTUkV/ODUk\_A\_So function are as depicted in Figure 13-18. + +**ODU-LCK:** The function shall generate the ODU-LCK signal as defined in clause 16.5 of [ITU-T G.709]. The clock, frame start and multiframe start are defined by the incoming ODUk signal. + +**Selector:** The normal signal may be replaced by the ODU-LCK signal. ODU-LCK signal is selected if the MI\_AdminState is LOCKED. + +**ODUk server layer APS:** When APS is enabled (MI\_APS\_EN is true), the function shall insert the CI\_APS value into the ODUk APS/PCC[MI\_APS\_LVL] field, which is available once per eight ODUk frames when MFAS bits 6, 7, 8 is equal to MI\_APS\_LVL. + +NOTE 1 – The ODUk SM APS information may be present in the case where the ODUk signal contains an ODU-AIS, ODU-LCK or ODU-OCI maintenance signal. The ODU-LCK maintenance signal may be inserted + +in this adaptation source function. ODuk SNC/I protection is unable to detect the insertion of such ODU-LCK and will not perform a protection switch. + +**OTUkV signal generation:** The function shall generate the OTUkV clock and frame start. The specific generation processes are outside the scope of this Recommendation. + +**Incoming alignment error:** In case of frame synchronous mapping of the ODuk in the OTUkV, IAE has to be generated. If the incoming ODuk frame start (CI\_FS) position is not at the expected frame start position, incoming alignment error (IAE) shall be activated. IAE shall be deactivated if the incoming ODuk frame start (CI\_FS) position is at the expected frame start position. The expected frame start position is based on the previous incoming ODuk frame start. + +**Mapping:** The function shall map the incoming ODuk frame (CI\_D) into the OTUkV frame (AI\_D). The specific mapping process is outside the scope of this Recommendation. + +![Figure 13-18 – OTUkV/ODUk_A_So processes. This block diagram illustrates the internal components and signal flow of the OTUkV/ODUk_A_So adaptation source function. Inputs include CI_D (client data), CI_FS (client frame start), CI_MFS (client multi-frame start), and control signals MI_APS_EN, MI_APS_LVL, and MI_AdminState. The diagram shows an ODUk-LCK generator receiving CI_D and CI_FS to produce D_normal and D_LCK signals. These are processed by a 'Select normal/LCK' block. CI_D is also processed by an APS block and a Mapping block. CI_FS and CI_MFS are used by an 'OTUk Vclock, FS and MFS generation' block to produce AI_CK, AI_FS, and AI_MFS. An IAE (Incoming Alignment Error) block is shown with a dashed border, receiving CI_FS and CI_MFS to produce a_IAE. The final outputs are AI_D (adapted data), AI_CK, AI_FS, AI_MFS, and AI_IAE, collectively labeled as OTUkV_AP. A reference label G.798(12)_F13-18 is present in the bottom right.](a890c88f5a03b77a0de8feaac5313821_img.jpg) + +Figure 13-18 – OTUkV/ODUk\_A\_So processes. This block diagram illustrates the internal components and signal flow of the OTUkV/ODUk\_A\_So adaptation source function. Inputs include CI\_D (client data), CI\_FS (client frame start), CI\_MFS (client multi-frame start), and control signals MI\_APS\_EN, MI\_APS\_LVL, and MI\_AdminState. The diagram shows an ODUk-LCK generator receiving CI\_D and CI\_FS to produce D\_normal and D\_LCK signals. These are processed by a 'Select normal/LCK' block. CI\_D is also processed by an APS block and a Mapping block. CI\_FS and CI\_MFS are used by an 'OTUk Vclock, FS and MFS generation' block to produce AI\_CK, AI\_FS, and AI\_MFS. An IAE (Incoming Alignment Error) block is shown with a dashed border, receiving CI\_FS and CI\_MFS to produce a\_IAE. The final outputs are AI\_D (adapted data), AI\_CK, AI\_FS, AI\_MFS, and AI\_IAE, collectively labeled as OTUkV\_AP. A reference label G.798(12)\_F13-18 is present in the bottom right. + +**Figure 13-18 – OTUkV/ODUk\_A\_So processes** + +**Defects:** None. + +##### **Consequent actions** + +The function shall perform the following consequent actions: + +$$aIAE \leftarrow IAE$$ + +NOTE 2 – aIAE is only required in case of frame synchronous mapping of the ODuk client signal. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### **13.3.2.2 OTUkV to ODuk adaptation sink function (OTUkV/ODUk\_A\_Sk)** + +The OTUkV/ODUk\_A\_Sk extracts the ODuk signal from the OTUkV. It may insert ODU-AIS under signal fail conditions. It provides access to the ODuk SM APS overhead. + +The information flow and processing of the OTUkV/ODUk\_A\_Sk functions is defined with reference to Figures 13-19 and 13-20. + +##### Symbol + +![Figure 13-19 – OTUkV/ODUk_A_Sk function symbol diagram. A central block labeled 'OTUkV/ODUk' has an input 'OTUkV_AP' from the bottom, with 'k = 1, 2, 3, 4' indicated. It has an output 'ODUk_CP' from the top. A dashed arrow labeled 'OTUkV/ODUk_A_Sk_MP' points to the block from the left. The diagram is labeled 'G.798(10)_F13-19'.](be9225da20b1fa284d0ed4b44fd633a3_img.jpg) + +Figure 13-19 – OTUkV/ODUk\_A\_Sk function symbol diagram. A central block labeled 'OTUkV/ODUk' has an input 'OTUkV\_AP' from the bottom, with 'k = 1, 2, 3, 4' indicated. It has an output 'ODUk\_CP' from the top. A dashed arrow labeled 'OTUkV/ODUk\_A\_Sk\_MP' points to the block from the left. The diagram is labeled 'G.798(10)\_F13-19'. + +Figure 13-19 – OTUkV/ODUk\_A\_Sk function + +##### Interfaces + +Table 13-8 – OTUkV/ODUk\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OTUkV_AP:
OTUkV_AI_CK
OTUkV_AI_D
OTUkV_AI_FS
OTUkV_AI_MFS (Note 1)
OTUkV_AI_TSF
OTUkV_AI_TSD
OTUkV/ODUk_A_Sk_MP:
OTUkV/ODUk_A_Sk_MI_AdminState
OTUkV/ODUk_A_Sk_MI_APS_EN
OTUkV/ODUk_A_Sk_MI_APS_LVL | ODUk_CP:
ODUk_CI_CK
ODUk_CI_D
ODUk_CI_FS
ODUk_CI_MFS
ODUk_CI_SSF
ODUk_CI_SSD
ODUk_CI_APS
OTUkV/ODUk_A_Sk_MP:
OTUkV/ODUk_A_Sk_MI_cLOA
(Note 2) | +| NOTE 1 – If the OTUkV has a multiframe. | | +| NOTE 2 – If loss of alignment supervision is performed. | | + +##### Processes + +The processes associated with the OTUkV/ODUk\_A\_Sk function are as depicted in Figure 13-20. + +**Demapping:** The function shall extract the ODUk signal, including clock, frame start, multiframe start and data from the OTUkV. The specific demapping processes are outside the scope of this Recommendation. + +**ODUk server layer APS:** When APS is enabled (MI\_APS\_EN is true), the function shall extract the information from the ODUk APS/PCC[MI\_APS\_LVL] field, which is available once per eight ODUk frames when the value of the MFAS bits 6, 7, 8 is equal to MI\_APS\_LVL, and apply the extracted information to the CI\_APS. + +NOTE – The ODUk SM APS information may be present in the case where the ODUk signal contains an ODU-AIS, ODU-LCK or ODU-OCI maintenance signal. The ODU-LCK maintenance signal may have been inserted in the far-end adaptation source function. ODUk SNC/I protection is unable to detect the insertion of such ODU-LCK and will not perform a protection switch. + +**ODU-LCK, ODU-AIS:** The function shall generate the ODU-LCK and ODU-AIS signals as defined in [ITU-T G.709]. The clock, frame start and multiframe start shall be independent from the incoming clock. The clock has to be within the frequency range as given in Table 7-2 of [ITU-T G.709]. Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +**Selector:** The normal signal may be replaced by either the ODU-AIS or the ODU-LCK signal. ODU-LCK signal is selected if the MI\_AdminState is LOCKED. ODU-AIS is selected if MI\_AdminState is not LOCKED and aAIS is true. + +![Figure 13-20 – OTUkV/ODUk_A_Sk processes. This block diagram illustrates the internal logic of the OTUkV/ODUk_A_Sk function. At the top, the ODUk_CP section includes inputs CI_SSD, CI_SSF, CI_APS, CI_MFS, CI_FS, CI_CK, and CI_D. CI_SSD and CI_SSF lead to 'Consequent actions', which outputs aSSD, aSSF, and aAIS. MI_AdminState and aAIS feed into 'Select normal/AIS/LCK', which outputs LCK, AIS, and Normal signals. 'Generate ODUk-LCK' and 'Generate ODUk-AIS' blocks also feed into the selection logic. MI_APS_EN and MI_APS_LVL feed into an APS block. MI_LOA feeds into 'Defect correlations' and 'Alignment detection' blocks. The bottom section, OTUkV_AP, includes inputs AI_TSD, AI_TSF, AI_MFS, AI_FS, AI_CK, and AI_D. AI_TSD and AI_TSF feed into 'Defect correlations' and 'Alignment detection'. 'ODUk data demapping, clock (ODCr), FS and MFS generation' block receives MFS, FS, CK, and D inputs and feeds into the APS block. The APS block outputs CI_APS. The diagram is labeled G.798(12)_F13-20.](52fe5bc3ba967e0e8f56f1a3ab9d9c3e_img.jpg) + +Figure 13-20 – OTUkV/ODUk\_A\_Sk processes. This block diagram illustrates the internal logic of the OTUkV/ODUk\_A\_Sk function. At the top, the ODUk\_CP section includes inputs CI\_SSD, CI\_SSF, CI\_APS, CI\_MFS, CI\_FS, CI\_CK, and CI\_D. CI\_SSD and CI\_SSF lead to 'Consequent actions', which outputs aSSD, aSSF, and aAIS. MI\_AdminState and aAIS feed into 'Select normal/AIS/LCK', which outputs LCK, AIS, and Normal signals. 'Generate ODUk-LCK' and 'Generate ODUk-AIS' blocks also feed into the selection logic. MI\_APS\_EN and MI\_APS\_LVL feed into an APS block. MI\_LOA feeds into 'Defect correlations' and 'Alignment detection' blocks. The bottom section, OTUkV\_AP, includes inputs AI\_TSD, AI\_TSF, AI\_MFS, AI\_FS, AI\_CK, and AI\_D. AI\_TSD and AI\_TSF feed into 'Defect correlations' and 'Alignment detection'. 'ODUk data demapping, clock (ODCr), FS and MFS generation' block receives MFS, FS, CK, and D inputs and feeds into the APS block. The APS block outputs CI\_APS. The diagram is labeled G.798(12)\_F13-20. + +**Figure 13-20 – OTUkV/ODUk\_A\_Sk processes** + +##### Defects + +Depending on the ODUk mapping defect, detection might be necessary (e.g., loss of alignment). + +##### Consequent actions + +The function shall perform the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF and (not MI\_AdminState = LOCKED) + +aAIS $\leftarrow$ AI\_TSF and (not MI\_AdminState = LOCKED) + +aSSD $\leftarrow$ AI\_TSD and (not MI\_AdminState = LOCKED) + +Depending on the ODUk mapping, additional defects might contribute to aSSF and aAIS (e.g., loss of alignment). + +On declaration of aAIS, the function shall output an all-ONEs pattern/signal within two frames. On clearing aAIS, the all-ONEs pattern/signal shall be removed within two frames, with normal data being output. The AIS clock, frame start and multiframe start shall be independent from the incoming clock, frame start and multiframe start. The AIS clock has to be within the frequency range as given in Table 7-2 of [ITU-T G.709]. Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +##### Defect correlations + +Depending on the ODUk mapping, defect correlations might be necessary (e.g., loss of alignment). + +**Performance monitoring:** None. + +### 13.3.3 OTU to COMMS adaptation function (OTU/COMMS\_A) + +The OTU to COMMS adaptation functions provide access to the GCC0 overhead in the OTU for generic data communication. + +#### 13.3.3.1 OTU to COMMS adaptation source function (OTU/COMMS\_A\_So) + +The OTU/COMMS\_A\_So function maps the generic communication channel data into the OTU GCC0 overhead. + +The information flow and processing of the OTU/COMMS\_A\_So functions is defined with reference to Figures 13-21 and 13-22. + +##### Symbol + +![Figure 13-21 – OTU/COMMS_A_So function. The diagram shows two symbols for the OTU/COMMS_A_So function. The left symbol is labeled 'OTUk/COMMS' and has an input 'COMMS_CP' pointing down to it, and an output 'OTUk_AP' pointing down from it. The output is labeled with 'k = 0, 1, 2, 3, 4, 25u, 25, 50u, 50'. The right symbol is labeled 'OTUCn/COMMS' and has an input 'COMMS_CP' pointing down to it, and an output 'OTUCn_AP' pointing down from it. Below the right symbol is the text 'G.798(17)-Amd.4(22)_F13-21'.](649f424fd35ea31f622163506a6148ed_img.jpg) + +Figure 13-21 – OTU/COMMS\_A\_So function. The diagram shows two symbols for the OTU/COMMS\_A\_So function. The left symbol is labeled 'OTUk/COMMS' and has an input 'COMMS\_CP' pointing down to it, and an output 'OTUk\_AP' pointing down from it. The output is labeled with 'k = 0, 1, 2, 3, 4, 25u, 25, 50u, 50'. The right symbol is labeled 'OTUCn/COMMS' and has an input 'COMMS\_CP' pointing down to it, and an output 'OTUCn\_AP' pointing down from it. Below the right symbol is the text 'G.798(17)-Amd.4(22)\_F13-21'. + +Figure 13-21 – OTU/COMMS\_A\_So function + +##### Interfaces + +Table 13-9 – OTU/COMMS\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------|---------------------------------------------------------------| +| COMMS_CP:
COMMS_CI_D
OTU_AP:
OTU_AI_CK
OTU_AI_FS | COMMS_CP:
COMMS_CI_CK
OTU_AP:
OTU_AI_D | + +##### Processes + +The processes associated with the OTU/COMMS\_A\_So function are as depicted in Figure 13-22. + +**COMMS clock generation:** The function shall generate the COMMS clock (CI\_CK) by dividing the incoming OTUk clock (OTUk\_AI\_CK) by a factor of 8160 or the OTUCn clock (OTUCn\_AI\_CK) by a factor of 7648). + +**Mapping:** The function shall map the incoming COMMS data (CI\_D) into the GCC0 overhead of the OTU frame (AI\_D). The bit rate of the COMMS data is defined by the outgoing COMMS clock (CI\_CK) and is in the range given in Table 7-10 of [ITU-T G.709]. + +Table 13-10 – Intentionally left blank + +The insertion of the COMMS data follows the transmission order of the GCC bits and bytes. + +![Figure 13-22: OTU/COMMS_A_So processes diagram. A grey box labeled COMMS_CP contains two white boxes: 'Mapping' and 'COMMS clock generation'. External inputs AI_FS, AI_D, and AI_CK enter from the bottom (labeled OTU_AP). AI_D and AI_CK enter the 'Mapping' box, while AI_FS enters the 'COMMS clock generation' box. The 'Mapping' box outputs CI_D and CI_CK to the top. The 'COMMS clock generation' box also outputs CI_CK to the top. Reference G.798(17)_F13-22 is shown at the bottom right.](4ef412e08808c40e0beb7808d36b9379_img.jpg) + +Figure 13-22: OTU/COMMS\_A\_So processes diagram. A grey box labeled COMMS\_CP contains two white boxes: 'Mapping' and 'COMMS clock generation'. External inputs AI\_FS, AI\_D, and AI\_CK enter from the bottom (labeled OTU\_AP). AI\_D and AI\_CK enter the 'Mapping' box, while AI\_FS enters the 'COMMS clock generation' box. The 'Mapping' box outputs CI\_D and CI\_CK to the top. The 'COMMS clock generation' box also outputs CI\_CK to the top. Reference G.798(17)\_F13-22 is shown at the bottom right. + +Figure 13-22 – OTU/COMMS\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### **13.3.3.2 OTU to COMMS adaptation sink function (OTU/COMMS\_A\_Sk)** + +The OTU/COMMS\_A\_Sk extracts the COMMS data from the OTU GCC0 overhead. + +The information flow and processing of the OTU/COMMS\_A\_Sk functions is defined with reference to Figures 13-23 and 13-24. + +##### **Symbol** + +![Figure 13-23: OTU/COMMS_A_Sk function symbols. Two trapezoidal symbols represent the function. The left symbol is labeled 'OTUk/COMMS' and has an input OTUk_AP with parameter k = 0, 1, 2, 3, 4, 25u, 25, 50u, 50, and an output COMMS_CP. The right symbol is labeled 'OTUCn/COMMS' and has an input OTUCn_AP and an output COMMS_CP. Reference G.798(17)-Amd.4(22)_F13-23 is shown at the bottom right.](43ff52fe5a7c6990f4f0d5e0ca55d4b4_img.jpg) + +Figure 13-23: OTU/COMMS\_A\_Sk function symbols. Two trapezoidal symbols represent the function. The left symbol is labeled 'OTUk/COMMS' and has an input OTUk\_AP with parameter k = 0, 1, 2, 3, 4, 25u, 25, 50u, 50, and an output COMMS\_CP. The right symbol is labeled 'OTUCn/COMMS' and has an input OTUCn\_AP and an output COMMS\_CP. Reference G.798(17)-Amd.4(22)\_F13-23 is shown at the bottom right. + +Figure 13-23 – OTU/COMMS\_A\_Sk function + +##### **Interfaces** + +Table 13-11 – OTU/COMMS\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|--------------------------------------------------------------------|---------------------------------------------------------------| +| OTU_AP:
OTU_AI_CK
OTU_AI_D
OTU_AI_FS
OTU_AI_TSF | COMMS_CP:
COMMS_CI_CK
COMMS_CI_D
COMMS_CI_SSF | + +##### Processes + +The processes associated with the OTUk/COMMS\_A\_Sk function are as depicted in Figure 13-24. + +**COMMS clock generation:** The function shall generate the COMMS clock (CI\_CK) by dividing the incoming OTUk clock (OTUk\_AI\_CK) by a factor of 8160 or the OTUCn clock (OTUCn\_AI\_CK) by a factor of 7648). + +**Demapping:** The function shall extract the COMMS data (CI\_D) from the GCC0 overhead of the OTU frame (AI\_D). The bit rate of the COMMS data is defined by the outgoing COMMS clock (CI\_CK) and is in the range given in Table 7-10 of [ITU-T G.709]. + +The extraction of the COMMS data follows the transmission order of the GCC bits and bytes. + +![Figure 13-24: OTUk/COMMS_A_Sk processes diagram. The diagram shows a grey rectangular box labeled 'COMMS_CP' at the top. Inside this box are two white rectangular blocks: 'Demapping' on the left and 'COMMS clock generation' on the right. Below the box, four input labels are shown: 'AI_FS', 'AI_D', 'AI_CK', and 'AI_TSF'. Arrows point from these inputs into the box. 'AI_FS' and 'AI_D' point to the 'Demapping' block. 'AI_CK' points to the 'COMMS clock generation' block. 'AI_TSF' points to the right side of the box, labeled 'aSSF'. Above the box, three output labels are shown: 'CI_D', 'CI_CK', and 'CI_SSF'. Arrows point from the 'Demapping' block to 'CI_D'. Arrows point from the 'COMMS clock generation' block to 'CI_CK'. An arrow points from the right side of the box (labeled 'aSSF') to 'CI_SSF'. At the bottom center, the label 'OTU_AP' is present. At the bottom right, the label 'G.798(17)_F13-24' is present.](efcb78ce7df315911219258bc2132f8c_img.jpg) + +Figure 13-24: OTUk/COMMS\_A\_Sk processes diagram. The diagram shows a grey rectangular box labeled 'COMMS\_CP' at the top. Inside this box are two white rectangular blocks: 'Demapping' on the left and 'COMMS clock generation' on the right. Below the box, four input labels are shown: 'AI\_FS', 'AI\_D', 'AI\_CK', and 'AI\_TSF'. Arrows point from these inputs into the box. 'AI\_FS' and 'AI\_D' point to the 'Demapping' block. 'AI\_CK' points to the 'COMMS clock generation' block. 'AI\_TSF' points to the right side of the box, labeled 'aSSF'. Above the box, three output labels are shown: 'CI\_D', 'CI\_CK', and 'CI\_SSF'. Arrows point from the 'Demapping' block to 'CI\_D'. Arrows point from the 'COMMS clock generation' block to 'CI\_CK'. An arrow points from the right side of the box (labeled 'aSSF') to 'CI\_SSF'. At the bottom center, the label 'OTU\_AP' is present. At the bottom right, the label 'G.798(17)\_F13-24' is present. + +**Figure 13-24 – OTUk/COMMS\_A\_Sk processes** + +**Defects:** None. + +##### Consequent actions + +The function shall perform the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 13.3.4 OTUkV to COMMS adaptation function (OTUkV/COMMS\_A) + +The OTUkV to COMMS adaptation functions provide access to the GCC overhead in the OTUkV for generic data communication. The format of the OTUkV GCC overhead is outside the scope of this Recommendation. + +#### 13.3.4.1 OTUkV to COMMS adaptation source function (OTUkV/COMMS\_A\_So) + +The OTUkV/COMMS\_A\_So function maps the generic communication channel data into the OTUkV GCC overhead. + +The information flow and processing of the OTUkV/COMMS\_A\_So functions is defined with reference to Figure 13-25. + +##### Symbol + +![Symbol diagram for OTUkV/COMMS_A_So function. It shows an input COMMS_CP entering a trapezoidal block labeled OTUkV/COMMS. An output arrow labeled k = 1, 2, 3, 4 exits the block and points to OTUkV_AP. The reference G.798(17)_F13-25 is shown below the output.](67cbb5a621a69ab58534bb3376bbb724_img.jpg) + +COMMS\_CP + +OTUkV/COMMS + +k = 1, 2, 3, 4 + +OTUkV\_AP + +G.798(17)\_F13-25 + +Symbol diagram for OTUkV/COMMS\_A\_So function. It shows an input COMMS\_CP entering a trapezoidal block labeled OTUkV/COMMS. An output arrow labeled k = 1, 2, 3, 4 exits the block and points to OTUkV\_AP. The reference G.798(17)\_F13-25 is shown below the output. + +Figure 13-25 – OTUkV/COMMS\_A\_So function + +##### Interfaces + +Table 13-12 – OTUkV/COMMS\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------|-------------------------------------------------------------------| +| COMMS_CP:
COMMS_CI_D
OTUkV_AP:
OTUkV_AI_CK
OTUkV_AI_FS | COMMS_CP:
COMMS_CI_CK
OTUkV_AP:
OTUkV_AI_D | + +##### Processes + +The function shall insert the COMMS data into the OTUkV GCC overhead. The specific processes are outside the scope of this Recommendation. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 13.3.4.2 OTUkV to COMMS adaptation sink function (OTUkV/COMMS\_A\_Sk) + +The OTUkV/COMMS\_A\_Sk extracts the COMMS data from the OTUkV GCC overhead. + +The information flow and processing of the OTUkV/COMMS\_A\_Sk functions is defined with reference to Figure 13-26. + +##### Symbol + +![Symbol diagram for OTUkV/COMMS_A_Sk function. It shows an input OTUkV_AP entering a trapezoidal block labeled OTUkV/COMMS. An output arrow labeled k = 1, 2, 3, 4 exits the block and points to COMMS_CP. The reference G.798(17)_F13-26 is shown below the input.](18fb2f2a7bdbb03074578da43004abaa_img.jpg) + +COMMS\_CP + +OTUkV/COMMS + +k = 1, 2, 3, 4 + +OTUkV\_AP + +G.798(17)\_F13-26 + +Symbol diagram for OTUkV/COMMS\_A\_Sk function. It shows an input OTUkV\_AP entering a trapezoidal block labeled OTUkV/COMMS. An output arrow labeled k = 1, 2, 3, 4 exits the block and points to COMMS\_CP. The reference G.798(17)\_F13-26 is shown below the input. + +Figure 13-26 – OTUkV/COMMS\_A\_Sk function + +##### Interfaces + +**Table 13-13 – OTUkV/COMMS\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------|---------------------------------------------------------------| +| OTUkV_AP:
OTUkV_AI_CK
OTUkV_AI_D
OTUkV_AI_FS
OTUkV_AI_TSF | COMMS_CP:
COMMS_CI_CK
COMMS_CI_D
COMMS_CI_SSF | + +##### Processes + +The function shall extract the COMMS data from the OTUkV GCC overhead. The specific processes are outside the scope of this Recommendation. + +**Defects:** None. + +##### Consequent actions + +The function shall perform the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 13.3.5 OTUk to synchronization distribution adaptation functions + +OTUk to synchronization distribution (SD) adaptation functions are given in clause 8.10 of [ITU-T G.781]. + +## 13.4 Sub-layer functions + +Not applicable. + +# 14 ODU (layer) functions + +Figure 14-1 illustrates the ODU layer network and client layer adaptation functions. The information crossing the ODU connection point (ODUk\_CP or ODUCn\_CP) is referred to as the ODU characteristic information (ODUk\_CI or ODUCn\_CI). The information crossing the ODUP access point (ODUkP\_AP or ODUCnP\_AP) is referred to as the ODUP adapted information (ODUkP\_AI). + +The tandem connection monitoring (TCM) sub-layer ODUT and the related functions (ODUkT\_TT, ODUT/ODU\_A and ODUTm) are optional. Up to six TCM sub-layers can be terminated within one NE. The figure shows a generic example for the connection of the ODUT functions. They can be connected to any ODU\_CP. It is not required to connect them via an ODU\_C function; they can be directly inserted without a connection function. + +The COMMS access functions (ODU/COMMS\_AC and ODUP/COMMS\_A) are optional. The figure shows a generic example for the connection of the ODU/COMMS\_AC functions. They can be inserted into any ODU\_CP (including TCPs) independent of sink or source processing. It is not required to connect them via an ODU\_C function; they can be directly inserted without a connection function. + +![](031de8ea6c5568a02faffd59b5c337f7_img.jpg) + +The diagram illustrates the ODU layer network and client layer adaptation functions, divided into ODUk (top half) and ODUCn (bottom half) sections. It shows the mapping and multiplexing of various client signals into ODU containers. + +### ODUk Layer (Top Section) + +- Client Interfaces (Top):** FC-1200\_CP, ERS10G\_CP, MT\_CP, SCC\_CP, ETH\_FP, ETH\_TFP. +- Adaptation Functions:** ODU2P/FC-1200, ODU2P/ERS10G, ODUkP[-h]/MT, ODUkP[-h]/ETH. +- Intermediate Layers:** RSn\_CP, CBRx\_CP, ODUkP/RSn, ODU0P/CBRx, ODUk-g/CBRx, ODUkP/CBRx. +- Multiplexing:** ODUk\_CP leading to ODUkP[-h]/ODUj-21 and ODUkP/ODU[i]j. +- Overhead/Management:** COMMS\_CP with ODUkP/PRBS, ODUkP/NULL, ODUkP/COMMS. +- Core:** ODUk connection point (oval) with ODUkT/ODUk termination, ODUkT non-intrusive monitor, and ODUkT\_AP/RP reference points. + +### ODUCn Layer (Bottom Section) + +- Management:** COMMS\_CP and ODUk\_CP leading to ODUCnP/PRBS, ODUCnP/NULL, ODUCnP/COMMS, ODUCnP/ODUk. +- Core:** ODUCn\_TCP (oval) with ODUCnT/ODUCn termination, ODUCnT non-intrusive monitor, and ODUCnT\_AP/RP reference points. +- Lower Adaptation:** ODUCn/COMMS adaptation functions leading to ODUCn\_CP. + +Reference markers: G.798(17)-Amd.1(18)\_F14-1a and G.798(17)\_F14-1b. + +**Figure 14-1 – ODU layer network and client layer adaptation functions** + +128 + +**Rec. ITU-T G.798 (09/2023)** + +The ODuk characteristic information (ODuk\_CI) is the ODuk frame as defined in [ITU-T G.709] with one instance (n = 1) of valid ODU overhead, together with a frame and multiframe start. The ODUCn characteristic information (ODUCn\_CI) is the ODUCn frame as defined in [ITU-T G.709] with n instances of valid ODU overhead, together with a frame and multiframe start. + +The ODU overhead is shown in Figure 14-2. TCM1..6 overhead is only used if one or more ODUT trails cross the CP; otherwise, it is set to all-ZEROs. APS/PCC overhead is only used in case of an ODU protection scheme with APS support; otherwise, it is set to all-ZEROs. GCC1, GCC2 and EXP overhead are optional. If they are not used, they are set to all-ZEROs. The RES overhead is set to all-ZEROs. PM and TCM overheads are for delay measurement of ODU path (DMp) and TCM (DMti) sections. + +![Diagram of ODuk overhead structure showing columns 1-16 and rows 1-4. Row 1 contains Frame alignment overhead (columns 1-7) and OTU overhead (columns 8-14). Rows 2-4 contain OPU overhead. Row 2: RES (col 1), EXP (col 3), TCM6 (col 4-5), TCM5 (col 6-7), TCM4 (col 8-9), EXP (col 10). Row 3: TCM3 (col 1-2), TCM2 (col 3-4), TCM1 (col 5-6), PM (col 7-8), EXP (col 9). Row 4: GCC1 (col 1), GCC2 (col 2), RES (col 3-14). Below the grid, two boxes show ODU frame structures: Structure #1 includes PM and TCM, APS/PCC, and RES; Structure #2 to #n includes RES and RES. Source: G.789(17)_F14-2.](4c63a0e17b54c7e61d512c276932114c_img.jpg) + +G.789(17)\_F14-2 + +Diagram of ODuk overhead structure showing columns 1-16 and rows 1-4. Row 1 contains Frame alignment overhead (columns 1-7) and OTU overhead (columns 8-14). Rows 2-4 contain OPU overhead. Row 2: RES (col 1), EXP (col 3), TCM6 (col 4-5), TCM5 (col 6-7), TCM4 (col 8-9), EXP (col 10). Row 3: TCM3 (col 1-2), TCM2 (col 3-4), TCM1 (col 5-6), PM (col 7-8), EXP (col 9). Row 4: GCC1 (col 1), GCC2 (col 2), RES (col 3-14). Below the grid, two boxes show ODU frame structures: Structure #1 includes PM and TCM, APS/PCC, and RES; Structure #2 to #n includes RES and RES. Source: G.789(17)\_F14-2. + +**Figure 14-2 – ODuk overhead at ODuk\_CP** + +The ODukP adapted information (ODukP\_AI) consists of the client layer CI adapted to the OPuk frame as defined in [ITU-T G.709] and one (n=1) instance of OPU overhead as shown in Figure 14-3, together with a frame and multiframe start. The mapping-specific overhead depends on the client mapping scheme. In case of COMMS access at the ODukP\_AP, it also includes the ODuk GCC overhead (GCC1/2). In the case of ODuk client signal protection (e.g., ODuj CL-SNCG/I, non-OTN client SNC/I or ODU SRP-p), it also includes the ODuk PM APS overhead (APS/PCC at level 000). + +The ODUCnP adapted information (ODUCnP\_AI) consists of the client layer CI adapted to the OPUCn frame as defined in [ITU-T G.709] and n instances of OPU overhead as shown in Figure 14-3, together with a frame and multiframe start. The mapping-specific overhead depends on the client mapping scheme. In case of COMMS access at the ODUCnP\_AP, it also includes the ODUCn GCC overhead (GCC1/2). In the case of ODUCn client signal protection (e.g., ODuj CL-SNCG/I, or ODU SRP-p), it also includes the ODUCn PM APS overhead (APS/PCC). + +![Diagram of OPU overhead at ODU_AP showing a 16-column by 4-row frame structure. Row 1-3 are mapping specific overhead. Row 4 contains GCC1, GCC2, APS/PCC, and PSI. Below the frame, a table shows MEAS[6:8] values (000-111) for ODuk and ODUCn paths.](143c8ee1010bf7669caabfbed815df1b_img.jpg) + +The diagram illustrates the OPU overhead structure at the ODU\_AP. It consists of a frame with 16 columns and 4 rows. Rows 1, 2, and 3 are designated as 'Mapping specific overhead'. Row 4 is divided into four sections: GCC1 (columns 1-2), GCC2 (columns 3-4), APS/PCC (columns 5-8), and PSI (columns 15-16). Below the frame, a table shows the 'MEAS[6:8]' values (000 through 111) for two paths: ODuk and ODUCn. The ODuk path is associated with the first MEAS value (000), and the ODUCn path is associated with the second MEAS value (001). The remaining MEAS values (010 through 111) are listed in the table but are not explicitly associated with a path in this diagram. + +| MEAS[6:8] | ODuk | ODUCn | +|-----------|--------------|---------| +| 000 | APS/PCC path | | +| 001 | | APS/PCC | +| 010 | | | +| 011 | | | +| 100 | | | +| 101 | | | +| 110 | | | +| 111 | | | + +Diagram of OPU overhead at ODU\_AP showing a 16-column by 4-row frame structure. Row 1-3 are mapping specific overhead. Row 4 contains GCC1, GCC2, APS/PCC, and PSI. Below the frame, a table shows MEAS[6:8] values (000-111) for ODuk and ODUCn paths. + +Figure 14-3 – OPU overhead at ODU\_AP + +## 14.1 Connection functions + +### 14.1.1 ODUk connection function (ODU\_C) + +The information flow and processing of the ODU\_C function is defined with reference to Figures 14-4 and 14-5. The ODU\_C function connects ODUk characteristic information from its input ports to its output ports. As the process does not affect the nature of characteristic information, the reference points on either side of the ODU\_C function are the same as illustrated in Figure 14-4. + +NOTE 1 – The ODUCn is excluded from the ODU\_C function. + +The connection process is unidirectional and as such no differentiation in sink and source is required. + +In addition, the ODU\_C function supports the following subnetwork connection protection schemes: + +- 1+1 unidirectional SNC/N, SNC/I and SNC/S protection without an APS protocol. +- 1+1 unidirectional SNC/N, SNC/I and SNC/S protection with an APS protocol. +- 1+1 bidirectional SNC/N, SNC/I and SNC/S protection with an APS protocol. +- 1:n unidirectional SNC/I and SNC/S protection with an APS protocol. +- 1:n bidirectional SNC/I and SNC/S protection with an APS protocol. + +The protection functionality is described in clause 14.1.1.1. + +NOTE 2 – The protection processes have a dedicated sink and source behaviour. + +##### Symbol + +![Diagram of the ODU_C function symbol. A central oval is labeled 'ODUk'. Above the oval, three vertical arrows point down to it, labeled 'ODUk_CP' at the top, with three dots between them. Below the oval, three vertical arrows point down from it, also labeled 'ODUk_CP' at the bottom, with three dots between them. To the left of the oval, a horizontal double-headed arrow points to it, labeled 'ODUk_C_MP'. To the right of the oval, the text 'G.798(10)_F14-4' is present.](56587d8256f60b3022273b5d8a90dfa8_img.jpg) + +Diagram of the ODU\_C function symbol. A central oval is labeled 'ODUk'. Above the oval, three vertical arrows point down to it, labeled 'ODUk\_CP' at the top, with three dots between them. Below the oval, three vertical arrows point down from it, also labeled 'ODUk\_CP' at the bottom, with three dots between them. To the left of the oval, a horizontal double-headed arrow points to it, labeled 'ODUk\_C\_MP'. To the right of the oval, the text 'G.798(10)\_F14-4' is present. + +Figure 14-4 – ODU\_C function + +##### Interfaces + +Table 14-1 – ODU\_C function inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| per ODUk_CP:
ODUk_CI_D
ODUk_CI_CK
ODUk_CI_FS
ODUk_CI_MFS
ODUk_CI_SSF
ODUk_CI_SSD (for SNC/S and SNC/I protection)
ODUk_AI_TSF (for SNC/N protection)
ODUk_AI_TSD (for SNC/N protection)
ODUk_CI_APS (for SNC/I and SNC/S protection)
ODUk_CI_RP
ODUk_CI_TSCC
per ODU_PP: (for CL_SNCG/I protection)
ODU_PI_APS
ODU_PI_TSF
ODU_PI_TSD
ODUk_C_MP:
ODUk_C_MI_MatrixControl
per protection group (for SNC protection):
ODUk_C_MI_ProfType
ODUk_C_MI_OperType
ODUk_C_MI_WTR
ODUk_C_MI_HoTime
ODUk_C_MI_ExtCMD
ODUk_C_MI_APSChannel (for SNC protection with APS protocol)
ODUk_C_MI_SDEnable | per ODUk_CP:
ODUk_CI_D
ODUk_CI_CK
ODUk_CI_FS
ODUk_CI_MFS
ODUk_CI_SSF
ODUk_CI_APS (for SNC/I and SNC/S protection)
ODUk_CI_RP
ODUk_CI_TSCC
per ODU_PP: (for CL_SNCG/I protection)
ODU_PI_APS
ODUk_C_MP:
per protection group (for SNC protection with APS protocol):
ODUk_C_MI_cFOP-PM
ODUk_C_MI_cFOP-NR | + +##### Processes + +The processes associated with the ODU\_C function are as depicted in Figure 14-5. + +ODU\_CI is routed between input and output connection points by means of a matrix connection. Connection points may be allocated within a protection group. + +NOTE 3 – Neither the number of input/output signals to the connection function, nor the connectivity, is specified in this Recommendation. That is a property of individual network elements. + +**Routing:** The function shall be able to connect a specific input with a specific output by means of establishing a matrix connection between the specified input and output. It shall be able to remove an established matrix connection. + +Each (matrix) connection in the ODU\_C function should be characterized by the: + +- Type of connection: unprotected. +- Traffic direction: unidirectional, bidirectional. +- Input and output connection points: set of connection points. + +NOTE 4 – Broadcast connections are handled as separate connections to the same CP. + +The following changes to (the configuration of) a connection shall be possible without disturbing the CI passing the connection: + +- addition and removal of protection; +- addition and removal of connections to/from a broadcast connection; +- change of WTR time; +- change of operation type; +- change of hold-off time; +- change of APS channel. + +**Open connection indication (OCI):** If an output of the connection function is not connected to an input, an ODU-OCI signal as defined in clause 16.5 of [ITU-T G.709] is generated for this output. The clock of the OCI signal has to be within the minimum and maximum clock frequencies specified for the ODU signals that are given in Table 7-2 of [ITU-T G.709]. The jitter and wander requirements as defined in Annex A of [ITU-T G.8251] (ODCa clock) apply. CI\_SSF is false. CI\_RP is to be set to the default value "0" and CI\_TSCC is to be set to the default value "0" for indicating that no resize operation is active. + +**Alarm indication signal (AIS):** If in a protection switch operation as defined in [ITU-T G.873.1] or [ITU-T G.873.1] extra traffic is pre-empted and to be squelched, or ODU squelching to prevent misconnection is to be executed, an ODU-AIS signal as defined in clause 16.5 of [ITU-T G.709] is generated for this output. The clock of the AIS signal has to be within the minimum and maximum clock frequencies specified for the ODU signals that are given in Table 7-2 of [ITU-T G.709]. The jitter and wander requirements as defined in Annex A of [ITU-T G.8251] (ODCa clock) apply. CI\_SSF is true. CI\_RP is to be set to the default value "0" and CI\_TSCC is to be set to the default value "0" for indicating no resize operation active. + +![Figure 14-5 – ODU_C function processes diagram. The diagram shows the internal structure of the ODU_C function. At the top, a bracket labeled 'ODUk_CPs' spans over a series of input signals: CL_D, CL_Ck, CL_FS, CL_SSF, CL_TSCC, CL_SSD/AL_TSF/AL_TSD, CL_RP, and CL_TSCC. These inputs connect to a central 'Matrix connection' block. Below the matrix connection, there are three functional blocks: 'OCI', 'OCI', and 'AIS'. Each block has multiple output signals pointing downwards, which are grouped by a bracket labeled 'ODUk_CPs'. The signals include CL_D, CL_Ck, CL_FS, CL_SSF, CL_TSCC, CL_SSD/AL_TSF/AL_TSD, CL_RP, and CL_TSCC. To the right of the matrix connection, another bracket labeled 'ODU_PPs' spans over input signals: PI_APS, PI_TSF, and PI_TSD. These also connect to the matrix connection. Below the matrix connection, there are output signals for PI_APS, PI_TSF, and PI_TSD, grouped by a bracket labeled 'ODU_PPs'. On the far left, a vertical label 'ODU_C_MP' with a double-headed arrow indicates the overall function boundary. A small note 'G.798(17)-Amd.4(22)_F14-5' is in the bottom right corner.](3ce6b213ec556257e32ff7451182369d_img.jpg) + +Figure 14-5 – ODU\_C function processes diagram. The diagram shows the internal structure of the ODU\_C function. At the top, a bracket labeled 'ODUk\_CPs' spans over a series of input signals: CL\_D, CL\_Ck, CL\_FS, CL\_SSF, CL\_TSCC, CL\_SSD/AL\_TSF/AL\_TSD, CL\_RP, and CL\_TSCC. These inputs connect to a central 'Matrix connection' block. Below the matrix connection, there are three functional blocks: 'OCI', 'OCI', and 'AIS'. Each block has multiple output signals pointing downwards, which are grouped by a bracket labeled 'ODUk\_CPs'. The signals include CL\_D, CL\_Ck, CL\_FS, CL\_SSF, CL\_TSCC, CL\_SSD/AL\_TSF/AL\_TSD, CL\_RP, and CL\_TSCC. To the right of the matrix connection, another bracket labeled 'ODU\_PPs' spans over input signals: PI\_APS, PI\_TSF, and PI\_TSD. These also connect to the matrix connection. Below the matrix connection, there are output signals for PI\_APS, PI\_TSF, and PI\_TSD, grouped by a bracket labeled 'ODU\_PPs'. On the far left, a vertical label 'ODU\_C\_MP' with a double-headed arrow indicates the overall function boundary. A small note 'G.798(17)-Amd.4(22)\_F14-5' is in the bottom right corner. + +**Figure 14-5 – ODU\_C function processes** + +**Defects:** See clause 14.1.1.1 for protection-specific defects. + +**Consequent actions:** None. + +**Defect correlations:** See clause 14.1.1.1 for protection-specific defect correlations. + +**Performance monitoring:** None. + +#### 14.1.1.1 Subnetwork connection protection process + +NOTE 1 – This process is active in the ODU\_C function as many times as there are 1+1 and 1:N protected matrix connections. + +The generic subnetwork connection protection mechanism is defined in [ITU-T G.808.1] with OTN-specific extensions in [ITU-T G.873.1]. + +SNC protection with non-intrusive monitoring (SNC/N), with inherent monitoring (SNC/I) and with sub-layer monitoring based on TCM (SNC/S), are supported. SNC/I is limited to a single OTUk[V] or HO ODUk server layer trail for the working and protection subnetwork connection between the source and sink protection switch (e.g., no intermediate OTUk termination/3R regeneration or HO ODUk termination is allowed). + +NOTE 2 – The limitation to a single server layer trail for SNC/I protection is given by the use of signal degrade (SD) as protection switching criteria. SD is only available from the OTUk[V] or HO ODUk trail that is locally terminated and not from further upstream OTUk[V] or HO ODUk trails. Furthermore, FDI/AIS, which provides information about defects in upstream OTUk[V] or HO ODUk trails, is not detected in the OTUk[V]/ODUk\_A\_Sk, ODUkP/ODU[i]j\_A\_Sk or the ODUkP/ODUj-21\_A\_Sk. + +Figure 14-6 gives the atomic functions involved in SNC/N protection. The working and protection ODU\_CI coming from either an OTUk[V]/ODUk\_A, ODUkT/ODUk\_A, ODUkP/ODU[i]j\_A, ODUkP[-h]/ODUj-21\_A or ODUCnP/ODUk\_A function are monitored by a ODUkP or ODUkT non-intrusive monitor, which provide the TSF and TSD protection switching criteria. The MI\_APS\_EN and MI\_APS\_LVL of the OTUk[V]/ODUk\_A, ODUkP/ODU[i]j\_A, ODUkP[-h]/ODUj-21\_A or ODUCnP/ODUk\_A functions should be set to provide access to the corresponding ODUk PM or TCM APS channel. The ODUkT/ODUk\_A functions provide access to the ODUk TCM APS channel. + +Figure 14-7 gives the atomic functions involved in SNC/I protection. The trail termination sink of an OTUk[V] or ODUP server layer provides the TSF and TSD protection switching criteria via the OTUk[V]/ODUk\_A, ODUkP/ODU[i]j\_A, ODUkP[-h]/ODUj-21\_A or ODUCnP/ODUk\_A functions (SSF and SSD). The MI\_APS\_EN and MI\_APS\_LVL of the OTUk[V]/ODUk\_A, + +ODUkP/ODU[i]j\_A, ODUkP[-h]/ODUj-21\_A or ODUCnP/ODUk\_A functions should be set to provide access to the ODUk SM APS channel. + +Figure 14-8 gives the atomic functions involved in SNC/S protection. The trail termination sink of an ODUkT TCM sub-layer provides the TSF and TSD protection switching criteria via the ODUkT/ODUk\_A function (SSF and SSD). The ODUkT/ODUk\_A functions provide access to the ODUk TCM APS channel. + +![Diagram of SNC/N protection atomic functions showing a central ODUk layer connected to Working and Protection ODUk CPs, which are further connected to OTUk sub-layers with various control signals like TSF, TSD, SSF, and APS.](1684f5f8c34bd0ef6e933664d88b9d86_img.jpg) + +The diagram illustrates the atomic functions for SNC/N protection. At the top, a central oval represents the **ODUk** layer. Above it, an arrow labeled **Normal (protected) ODUk CP** points down into the ODUk layer. Below the ODUk layer, there are two main paths: **Working ODUk CP** and **Protection ODUk CP**. Each path consists of a trapezoidal block labeled **ODUkT/ODUk OTUk[V]/ODUk ODUkP/ODU[j]j ODUkP/ODUj-21**. To the left of the Working path, a triangle labeled **ODUkTm ODUkP** receives **SSF** and **TSF, TSD** signals. Below the Working path, another trapezoidal block labeled **OTUk[V]/ODUk OTUk ODUk** is connected. The Protection path similarly has a triangle labeled **ODUkTm ODUkP** receiving **SSF** and **TSF, TSD** signals. Below the Protection path, a trapezoidal block labeled **OTUk[V]/ODUk OTUk ODUk** is connected. At the bottom, arrows point to labels **G.798(10)\_F14-6**. + +Diagram of SNC/N protection atomic functions showing a central ODUk layer connected to Working and Protection ODUk CPs, which are further connected to OTUk sub-layers with various control signals like TSF, TSD, SSF, and APS. + +Figure 14-6 – SNC/N protection atomic functions + +![Diagram of SNC/I protection atomic functions showing multiple Working ODUk CPs (1 to N) and one Protection ODUk CP connected to a central ODUk layer, with associated OTUk sub-layers and control signals.](024914144d624b7f5dc22aaa5c3967b9_img.jpg) + +The diagram illustrates the atomic functions for SNC/I protection. At the top, a central oval represents the **ODUk** layer. Above it, multiple arrows labeled **Normal (protected) ODUk CP** (numbered 1 to N) point down into the ODUk layer. To the right, an arrow labeled **Extra traffic ODUk CP** points down into the ODUk layer. Below the ODUk layer, there are multiple **Working ODUk CP** blocks (numbered 1 to N) and one **Protection ODUk CP** block. Each Working ODUk CP block is a trapezoid labeled **OTUk[V]/ODUk OTUk[V]/ODUk ODUkP/ODU[j]j ODUkP/ODUj-21**. Below each Working ODUk CP block is a triangle labeled **OTUk[V]/ODUk OTUk ODUk**. The Protection ODUk CP block is a trapezoid labeled **OTUk[V]/ODUk OTUk[V]/ODUk ODUkP/ODU[j]j ODUkP/ODUj-21**. Below it is a triangle labeled **OTUk[V]/ODUk OTUk ODUk**. Control signals **SSF**, **SSD**, **TSF**, **TSD**, and **APS** are shown between the ODUk layer and the sub-layers. At the bottom, arrows point to labels **G.798(12)\_F14-7**. + +Diagram of SNC/I protection atomic functions showing multiple Working ODUk CPs (1 to N) and one Protection ODUk CP connected to a central ODUk layer, with associated OTUk sub-layers and control signals. + +Figure 14-7 – SNC/I protection atomic functions + +![Figure 14-8: SNC/S protection atomic functions diagram. It shows a top-level ODUk layer with multiple 'Normal (protected) ODUk CP' (1 to N) and 'Extra traffic ODUk CP' connections. Below this, there are 'Working ODUk CP' (1 to N) and 'Protection ODUk CP' components. Each working component is connected to an 'ODUkT/ODUk' block, which is further connected to an 'ODUkT' block. Each protection component is connected to an 'ODUkT/ODUk' block, which is connected to an 'ODUkT' block. Control signals like SSF, SSD, TSF, TSD, and APS are shown between the layers. A reference code 'G.798(12)_F14-8' is at the bottom right.](845e014e3b8677eb735d0e21f21206be_img.jpg) + +Figure 14-8: SNC/S protection atomic functions diagram. It shows a top-level ODUk layer with multiple 'Normal (protected) ODUk CP' (1 to N) and 'Extra traffic ODUk CP' connections. Below this, there are 'Working ODUk CP' (1 to N) and 'Protection ODUk CP' components. Each working component is connected to an 'ODUkT/ODUk' block, which is further connected to an 'ODUkT' block. Each protection component is connected to an 'ODUkT/ODUk' block, which is connected to an 'ODUkT' block. Control signals like SSF, SSD, TSF, TSD, and APS are shown between the layers. A reference code 'G.798(12)\_F14-8' is at the bottom right. + +**Figure 14-8 – SNC/S protection atomic functions** + +The signal flow associated with the ODU\_C SNC protection process is described with reference to Figures 14-9 to 14-13. The protection process receives control parameters and external switch requests at the MP reference point. The report of status information at the MP reference point is for further study. + +![Figure 14-9: 1+1 unidirectional SNC/N protection process without APS protocol diagram. It shows a 'Normal ODUk_CP' input branching into a 'Permanent bridge' and a 'Control' block. The 'Permanent bridge' outputs to 'Working ODUk_CP' and 'Protection ODUk_CP'. The 'Control' block outputs to a 'Selector' and receives 'TSF, TSD' signals. The 'Selector' outputs to 'Working ODUk_CP' and 'Protection ODUk_CP'. Management interface signals (MI_ProfType, MI_OperType, MI_WTR, MI_HoldOffTime, MI_ExtCMD, MI_SDEnable) are shown on the left. A reference code 'G.798-Amd.1(11)_F14-9' is at the bottom right.](61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg) + +Figure 14-9: 1+1 unidirectional SNC/N protection process without APS protocol diagram. It shows a 'Normal ODUk\_CP' input branching into a 'Permanent bridge' and a 'Control' block. The 'Permanent bridge' outputs to 'Working ODUk\_CP' and 'Protection ODUk\_CP'. The 'Control' block outputs to a 'Selector' and receives 'TSF, TSD' signals. The 'Selector' outputs to 'Working ODUk\_CP' and 'Protection ODUk\_CP'. Management interface signals (MI\_ProfType, MI\_OperType, MI\_WTR, MI\_HoldOffTime, MI\_ExtCMD, MI\_SDEnable) are shown on the left. A reference code 'G.798-Amd.1(11)\_F14-9' is at the bottom right. + +**Figure 14-9 – 1+1 unidirectional SNC/N protection process without APS protocol** + +![Figure 14-10: 1+1 unidirectional SNC/S and SNC/I protection process without APS protocol diagram. It is similar to Figure 14-9 but the 'Control' block receives 'SSF, SSD' signals instead of 'TSF, TSD'. A reference code 'G.798-Amd.1(11)_F14-10' is at the bottom right.](0850300da6b28250eb47881da35cabad_img.jpg) + +Figure 14-10: 1+1 unidirectional SNC/S and SNC/I protection process without APS protocol diagram. It is similar to Figure 14-9 but the 'Control' block receives 'SSF, SSD' signals instead of 'TSF, TSD'. A reference code 'G.798-Amd.1(11)\_F14-10' is at the bottom right. + +**Figure 14-10 – 1+1 unidirectional SNC/S and SNC/I protection process without APS protocol** + +![Figure 14-11: 1+1 SNC/N protection process with APS protocol. This block diagram shows the signal flow and control logic for 1+1 SNC/N protection. On the left, a 'Normal ODUk_CP' input splits into a 'Permanent bridge' and a 'Control' block. The 'Permanent bridge' outputs to 'Working ODUk_CP' and 'Protection ODUk_CP'. The 'Control' block receives inputs from 'MI_ProtType', 'MI_OperType', 'MI_WTR', 'MI_HoldOffTime', 'MI_ExtCMD', and 'MI_SDEnable'. It also receives 'APS protocol' and 'TSF TSD' signals. The 'Control' block sends 'dFOP-PM' and 'dFOP-NR' signals to a 'Selector' block. The 'Selector' block outputs to 'MI_cFOP-PM' and 'MI_cFOP-NR'. The 'Selector' block also receives 'APS protocol' and 'TSF' signals. The 'MI_APSChannel' is connected to the 'APS protocol insertion' and 'APS protocol acceptance' blocks. The 'APS protocol insertion' block receives 'APS protocol' from the 'Control' block and sends it to the 'Permanent bridge'. The 'APS protocol acceptance' block receives 'APS protocol' from the 'Selector' block and sends it to the 'Control' block.](5ee80a63ec53c60d7306b5a44984afcf_img.jpg) + +Figure 14-11: 1+1 SNC/N protection process with APS protocol. This block diagram shows the signal flow and control logic for 1+1 SNC/N protection. On the left, a 'Normal ODUk\_CP' input splits into a 'Permanent bridge' and a 'Control' block. The 'Permanent bridge' outputs to 'Working ODUk\_CP' and 'Protection ODUk\_CP'. The 'Control' block receives inputs from 'MI\_ProtType', 'MI\_OperType', 'MI\_WTR', 'MI\_HoldOffTime', 'MI\_ExtCMD', and 'MI\_SDEnable'. It also receives 'APS protocol' and 'TSF TSD' signals. The 'Control' block sends 'dFOP-PM' and 'dFOP-NR' signals to a 'Selector' block. The 'Selector' block outputs to 'MI\_cFOP-PM' and 'MI\_cFOP-NR'. The 'Selector' block also receives 'APS protocol' and 'TSF' signals. The 'MI\_APSChannel' is connected to the 'APS protocol insertion' and 'APS protocol acceptance' blocks. The 'APS protocol insertion' block receives 'APS protocol' from the 'Control' block and sends it to the 'Permanent bridge'. The 'APS protocol acceptance' block receives 'APS protocol' from the 'Selector' block and sends it to the 'Control' block. + +**Figure 14-11 – 1+1 SNC/N protection process with APS protocol** + +![Figure 14-12: 1+1 SNC/S and SNC/I protection process with APS protocol. This block diagram shows the signal flow and control logic for 1+1 SNC/S and SNC/I protection. It is similar to Figure 14-11 but uses 'SSF SSD' instead of 'TSF TSD'. The 'Control' block receives 'SSF SSD' signals from the 'Selector' block. The 'Selector' block sends 'SSF' signals to the 'Control' block. The 'MI_APSChannel' is connected to the 'APS protocol insertion' and 'APS protocol acceptance' blocks. The 'APS protocol insertion' block receives 'APS protocol' from the 'Control' block and sends it to the 'Permanent bridge'. The 'APS protocol acceptance' block receives 'APS protocol' from the 'Selector' block and sends it to the 'Control' block.](4b9e2f848d66a0b3c2d4553b965933c7_img.jpg) + +Figure 14-12: 1+1 SNC/S and SNC/I protection process with APS protocol. This block diagram shows the signal flow and control logic for 1+1 SNC/S and SNC/I protection. It is similar to Figure 14-11 but uses 'SSF SSD' instead of 'TSF TSD'. The 'Control' block receives 'SSF SSD' signals from the 'Selector' block. The 'Selector' block sends 'SSF' signals to the 'Control' block. The 'MI\_APSChannel' is connected to the 'APS protocol insertion' and 'APS protocol acceptance' blocks. The 'APS protocol insertion' block receives 'APS protocol' from the 'Control' block and sends it to the 'Permanent bridge'. The 'APS protocol acceptance' block receives 'APS protocol' from the 'Selector' block and sends it to the 'Control' block. + +**Figure 14-12 – 1+1 SNC/S and SNC/I protection process with APS protocol** + +![Figure 14-13: 1:N SNC/S and SNC/I protection process with APS protocol. This block diagram shows the signal flow and control logic for 1:N SNC/S and SNC/I protection. On the left, 'Normal ODUk_CP' (labeled 1) and 'Extra traffic ODUk_CP' (labeled N) inputs go to a 'Bridge' block. The 'Bridge' block outputs to 'Working ODUk_CP' (labeled 1) and 'Protection ODUk_CP' (labeled N). The 'Bridge' block also has an 'OCI' block. The 'Control' block receives inputs from 'MI_ProtType', 'MI_OperType', 'MI_WTR', 'MI_HoldOffTime', 'MI_ExtCMD', and 'MI_SDEnable'. It also receives 'APS protocol' and 'SSF, SSD' signals. The 'Control' block sends 'dFOP-PM' and 'dFOP-NR' signals to a 'Selector' block. The 'Selector' block outputs to 'MI_cFOP-PM' and 'MI_cFOP-NR'. The 'Selector' block also receives 'APS protocol' and 'SSF' signals. The 'MI_APSChannel' is connected to the 'APS protocol insertion' and 'APS protocol acceptance' blocks. The 'APS protocol insertion' block receives 'APS protocol' from the 'Control' block and sends it to the 'Bridge'. The 'APS protocol acceptance' block receives 'APS protocol' from the 'Selector' block and sends it to the 'Control' block. The 'AIS' block is connected to the 'Selector' block.](d3253d5db64378db6e72b66b41067a5b_img.jpg) + +Figure 14-13: 1:N SNC/S and SNC/I protection process with APS protocol. This block diagram shows the signal flow and control logic for 1:N SNC/S and SNC/I protection. On the left, 'Normal ODUk\_CP' (labeled 1) and 'Extra traffic ODUk\_CP' (labeled N) inputs go to a 'Bridge' block. The 'Bridge' block outputs to 'Working ODUk\_CP' (labeled 1) and 'Protection ODUk\_CP' (labeled N). The 'Bridge' block also has an 'OCI' block. The 'Control' block receives inputs from 'MI\_ProtType', 'MI\_OperType', 'MI\_WTR', 'MI\_HoldOffTime', 'MI\_ExtCMD', and 'MI\_SDEnable'. It also receives 'APS protocol' and 'SSF, SSD' signals. The 'Control' block sends 'dFOP-PM' and 'dFOP-NR' signals to a 'Selector' block. The 'Selector' block outputs to 'MI\_cFOP-PM' and 'MI\_cFOP-NR'. The 'Selector' block also receives 'APS protocol' and 'SSF' signals. The 'MI\_APSChannel' is connected to the 'APS protocol insertion' and 'APS protocol acceptance' blocks. The 'APS protocol insertion' block receives 'APS protocol' from the 'Control' block and sends it to the 'Bridge'. The 'APS protocol acceptance' block receives 'APS protocol' from the 'Selector' block and sends it to the 'Control' block. The 'AIS' block is connected to the 'Selector' block. + +**Figure 14-13 – 1:N SNC/S and SNC/I protection process with APS protocol** + +For the description of the protection processes including bridge and selector control, APS acceptance and transmission, see [ITU-T G.873.1]. + +A permanent bridge, as defined in [ITU-T G.808.1], shall be used for the 1+1 protection. A broadcast bridge, as defined in [ITU-T G.808.1], shall be used for the 1:N protection. It permanently connects the normal traffic signal to the working transport entity. In case no normal or extra traffic signal is connected to the protection transport entity, an ODU-OCI signal, as defined in clause 16.5 of [ITU-T G.709], is generated for the protection transport entity. The clock of the OCI signal has to be within the minimum and maximum frequencies of the specified ODU signal in Table 7-2 of [ITU-T G.709]. The jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. CI\_SSF is false. In the case where the extra traffic signal of a 1:N protection configuration carried by the protection entity is pre-empted by a protection switch, an ODU-AIS signal is to be connected to the extra traffic ODU\_CP output. The clock of the ODU-AIS signal has to be within the minimum and maximum frequencies of the specified ODU signal in Table 7-2 of [ITU-T G.709]. The jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +A selective selector, as defined in [ITU-T G.808.1], shall be used. + +MI\_ProtType configures the protection type as defined in clause 9.4 of [ITU-T G.873.1]. + +NOTE 3 – Only a subset or a single protection type can be supported. In the latter case, the configuration is not needed. + +MI\_OperType configures between revertive and non-revertive operation as defined in clause 8.3 of [ITU-T G.873.1]. + +NOTE 4 – Only a single operation type can be supported. In this case, the configuration is not needed. + +MI\_HoTime configures the hold-off time as defined in clause 9.12 of [ITU-T G.873.1]. + +MI\_WTR configures the wait to restore (WTR) time as defined in clause 15 of [ITU-T G.808.1]. + +MI\_ExtCMD configures the protection group commands as defined in clause 7 of [ITU-T G.873.1]. + +MI\_APSChannel configures the APS channel (see clause 15.8.2.4 of [ITU-T G.709]) in case an APS protocol is used. + +If MI\_SDEnable is true, the SSD/TSD signal is used as trigger for the protection. If it is false, SSD/TSD is not used as trigger for the protection. It applies to all working and the protection signals in common. + +##### *Protection switching performance* + +See clause 6.2 of [ITU-T G.873.1]. + +##### **Defects** + +The function shall detect dFOP-PM and dFOP-NR defects in case the APS protocol is used. + +**dFOP-PM:** See clause 6.2.7.1.1. + +**dFOP-NR:** See clause 6.2.7.1.2. + +**Consequent actions:** None. + +##### **Defect correlations** + +cFOP-PM ← dFOP-PM and (not CI\_SSF/TSF) + +cFOP-NR ← dFOP-NR and (not CI\_SSF/TSF) + +In the case of SNC/S and SNC/I, CI\_SSF of the protection signal is used. In the case of SNC/N, CI\_TSF of the protection signal is used. + +**Performance monitoring:** None. + +#### 14.1.1.2 Compound link subnetwork connection group protection process + +NOTE 1 – This process is active in the ODU\_C function as many times as there are 1+1 and 1:1 protected matrix connection groups. + +The generic compound link subnetwork connection group with an inherent monitoring protection mechanism is defined in [ITU-T G.808.1] with OTN-specific extensions in [ITU-T G.873.1]. + +CL-SNCG protection with inherent monitoring (CL-SNCG/I) is supported. CL-SNCG/I is limited to a single HO ODUk server layer trail for the working and protection subnetwork connection groups between the source and sink protection switch (e.g., no intermediate HO ODUk termination is allowed). + +Figure 14-14 gives the atomic functions involved in CL-SNCG/I protection. The trail termination sink of an ODUkP server layer provides the TSF and TSD protection switching criteria. + +![Diagram of CL-SNCG/I protection atomic functions showing signal flow between unprotected and protected ODU_CIs through ODU and ODUkP layers.](2bcc7de24074ca97717d10c8c4bfe3ba_img.jpg) + +The diagram illustrates the atomic functions for CL-SNCG/I protection. At the top, an oval labeled 'ODU' contains two sections: 'Unprotected ODU\_CI' on the left and 'Protected ODU\_CI' on the right, both with multiple input/output arrows. Below the 'Unprotected ODU\_CI' section, there are two trapezoidal blocks labeled 'ODUkP/ODUj-21'. The left one has inputs 'U' and 'W' and an output 'ODUkP'. The right one has inputs 'U' and 'W' and an output 'ODUkP'. Between these two blocks is a vertical line labeled 'TSF/TSD'. Below the 'Protected ODU\_CI' section, there are two similar trapezoidal blocks labeled 'ODUkP/ODUj-21'. The left one has inputs 'U' and 'P' and an output 'ODUkP'. The right one has inputs 'U' and 'P' and an output 'ODUkP'. Between these two blocks is a vertical line labeled 'TSF/TSD'. Vertical lines labeled 'PI\_APS' connect the 'ODUkP/ODUj-21' blocks to the 'ODUkP' blocks. At the bottom, four triangular blocks labeled 'ODUkP' are shown, with arrows indicating signal flow between them and the blocks above. A small label 'G.798(12)\_F 14-14' is in the bottom right corner. + +Diagram of CL-SNCG/I protection atomic functions showing signal flow between unprotected and protected ODU\_CIs through ODU and ODUkP layers. + +**Figure 14-14 – CL-SNCG/I protection atomic functions** + +The signal flow associated with the ODU\_C CL-SNCG/I protection process is described with reference to Figures 14-15, 14-16 and 14-17. The protection process receives control parameters and external switch requests at the MP reference point. The report of status information at the MP reference point is for further study. + +For the description of the protection processes including bridge and selector control, APS acceptance and transmission, see [ITU-T G.873.1]. + +A permanent bridge, as defined in [ITU-T G.808.1], shall be used for 1+1 protection. A broadcast bridge, as defined in [ITU-T G.808.1], shall be used for 1:1 protection. It permanently connects the normal traffic signals to the working transport entity group. + +A selective selector, as defined in [ITU-T G.808.1], shall be used. + +![Figure 14-15: 1+1 unidirectional CL-SNCG/I protection process without APS protocol. The diagram shows a 'Normal ODUj_CPs' input at the top left entering a 'Permanent bridge'. The bridge has two outputs: 'Working ODUj_CPs' and 'Protection ODUj_CPs'. A 'Control' block receives 'MI_ProtType', 'MI_OperType', 'MI_WTR', 'MI_HoldOffTime', 'MI_ExtCMD', and 'MI_SDEnable' as inputs and sends 'TSF/TSD' signals to a 'Selector'. The 'Selector' also receives 'Normal ODUj_CPs' from the top right and outputs 'Working ODUj_CPs' and 'Protection ODUj_CPs'. A label 'G.798(12)_F14-15' is at the bottom right.](8181865f1fd5e629dbe12ed89d22dc83_img.jpg) + +Figure 14-15: 1+1 unidirectional CL-SNCG/I protection process without APS protocol. The diagram shows a 'Normal ODUj\_CPs' input at the top left entering a 'Permanent bridge'. The bridge has two outputs: 'Working ODUj\_CPs' and 'Protection ODUj\_CPs'. A 'Control' block receives 'MI\_ProtType', 'MI\_OperType', 'MI\_WTR', 'MI\_HoldOffTime', 'MI\_ExtCMD', and 'MI\_SDEnable' as inputs and sends 'TSF/TSD' signals to a 'Selector'. The 'Selector' also receives 'Normal ODUj\_CPs' from the top right and outputs 'Working ODUj\_CPs' and 'Protection ODUj\_CPs'. A label 'G.798(12)\_F14-15' is at the bottom right. + +**Figure 14-15 – 1+1 unidirectional CL-SNCG/I protection process without APS protocol** + +![Figure 14-16: 1+1 CL-SNCG/I protection process with APS protocol. This diagram is similar to Figure 14-15 but includes an 'APS' (Automatic Protection Switching) protocol. A box labeled 'APS acceptance' is connected to the 'Control' block and the 'Selector'. The 'Control' block also receives 'dFOP-PM' and 'dFOP-NR' signals and sends 'SF' and 'SD' signals. The 'Selector' outputs 'cFOP-PM' and 'cFOP-NR' signals. A label 'G.798(12)_F14-16' is at the bottom right.](e5eedb1e90a22814f090917b3411be8f_img.jpg) + +Figure 14-16: 1+1 CL-SNCG/I protection process with APS protocol. This diagram is similar to Figure 14-15 but includes an 'APS' (Automatic Protection Switching) protocol. A box labeled 'APS acceptance' is connected to the 'Control' block and the 'Selector'. The 'Control' block also receives 'dFOP-PM' and 'dFOP-NR' signals and sends 'SF' and 'SD' signals. The 'Selector' outputs 'cFOP-PM' and 'cFOP-NR' signals. A label 'G.798(12)\_F14-16' is at the bottom right. + +**Figure 14-16 – 1+1 CL-SNCG/I protection process with APS protocol** + +![Figure 14-17: 1:1 CL-SNCG/I protection process with APS protocol. The diagram shows a 'Broadcast bridge' instead of a 'Permanent bridge'. The 'Broadcast bridge' receives 'Normal ODUj_CPs' and outputs 'Working ODUj_CPs' and 'Protection ODUj_CPs'. The 'Control' block and 'APS acceptance' box are present, along with 'dFOP-PM', 'dFOP-NR', 'SF', 'SD', and 'APS' signals. The 'Selector' outputs 'cFOP-PM' and 'cFOP-NR' signals. A label 'G.798(12)_F14-17' is at the bottom right.](48090d8f1db2e826aaa740035aa12ecb_img.jpg) + +Figure 14-17: 1:1 CL-SNCG/I protection process with APS protocol. The diagram shows a 'Broadcast bridge' instead of a 'Permanent bridge'. The 'Broadcast bridge' receives 'Normal ODUj\_CPs' and outputs 'Working ODUj\_CPs' and 'Protection ODUj\_CPs'. The 'Control' block and 'APS acceptance' box are present, along with 'dFOP-PM', 'dFOP-NR', 'SF', 'SD', and 'APS' signals. The 'Selector' outputs 'cFOP-PM' and 'cFOP-NR' signals. A label 'G.798(12)\_F14-17' is at the bottom right. + +**Figure 14-17 – 1:1 CL-SNCG/I protection process with APS protocol** + +MI\_ProtType configures the protection type as defined in clause 9.4 of [ITU-T G.873.1]. + +NOTE 2 – Only a subset or a single protection type can be supported. In the latter case, the configuration is not needed. + +MI\_OperType is configured between revertive and non-revertive operation as defined in clause 8.3 of [ITU-T G.873.1]. + +NOTE 3 – Only a single operation type can be supported. In this case configuration is not needed. + +MI\_HoTime configures the hold-off time as defined in clause 9.12 of [ITU-T G.873.1]. + +MI\_WTR configures the wait to restore (WTR) time as defined in clause 15 of [ITU-T G.808.1]. + +MI\_ExtCMD configures the protection group command as defined in clause 7 of [ITU-T G.873.1]. + +If MI\_SDEnable is true, the TSD signal is used as a trigger for protection. If it is false, TSD is not used as a trigger for protection. It applies to all working and the protection signals in common. + +##### *Protection switching performance* + +See clause 6.2 of [ITU-T G.873.1]. + +##### **Defects** + +The function shall detect dFOP-PM and dFOP-NR defects in case the APS protocol is used. + +**dFOP-PM:** See clause 6.2.7.1.1. + +**dFOP-NR:** See clause 6.2.7.1.2. + +**Consequent actions:** None. + +##### **Defect correlations** + +cFOP-PM $\leftarrow$ dFOP-PM and (not CI\_TSF) + +cFOP-NR $\leftarrow$ dFOP-NR and (not CI\_TSF) + +##### **Performance monitoring:** + +None. + +#### **14.1.1.3 Shared ODU ring protection process** + +NOTE – Two different protection architectures are defined in [ITU-T G.873.2], SRP-1 and SRP-P. + +Details of the processes are for further study. + +## **14.2 Termination functions** + +### **14.2.1 ODUP trail termination function (ODUP\_TT)** + +The ODUP\_TT function terminates the path monitoring (PM) overhead of the ODU overhead to determine the status of the ODU trail. Figure 14-18 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Diagram of ODUP_TT function showing two pairs of ODU functions. The left pair consists of two ODUkP triangles. The left triangle has an input ODUPk_AP at the top and an output ODUPk_TCP at the bottom. The right triangle has an output ODUPk_AP at the top and an input ODUPk_TCP at the bottom. A horizontal arrow labeled ODUPk_RP points from the right triangle to the left triangle. The right pair consists of two ODUCnP triangles. The left triangle has an input ODUCnP_AP at the top and an output ODUCnP_TCP at the bottom. The right triangle has an output ODUCnP_AP at the top and an input ODUCnP_TCP at the bottom. A horizontal arrow labeled ODUCnP_RP points from the right triangle to the left triangle. A small text 'G.798(17)_F14-18' is at the bottom right.](55c1c9a102f0828aa242f4e934dbcac5_img.jpg) + +G.798(17)\_F14-18 + +Diagram of ODUP\_TT function showing two pairs of ODU functions. The left pair consists of two ODUkP triangles. The left triangle has an input ODUPk\_AP at the top and an output ODUPk\_TCP at the bottom. The right triangle has an output ODUPk\_AP at the top and an input ODUPk\_TCP at the bottom. A horizontal arrow labeled ODUPk\_RP points from the right triangle to the left triangle. The right pair consists of two ODUCnP triangles. The left triangle has an input ODUCnP\_AP at the top and an output ODUCnP\_TCP at the bottom. The right triangle has an output ODUCnP\_AP at the top and an input ODUCnP\_TCP at the bottom. A horizontal arrow labeled ODUCnP\_RP points from the right triangle to the left triangle. A small text 'G.798(17)\_F14-18' is at the bottom right. + +**Figure 14-18 – ODUP\_TT** + +#### 14.2.1.1 ODUP trail termination source function (ODUP\_TT\_So) + +The ODUP\_TT\_So function computes the BIP-8[1..n] and adds path monitoring overhead (PMOH) – including the TTI, BIP-8[1..n], DMp, BDI and BEI[1..n] signals – in the PM overhead field to the ODU signal at its ODUP\_AP. The ODUCn signal has n PM overhead fields; the ODUk signal has one (n=1) PM overhead field. + +The information flow and processing of the ODUP\_TT\_So function is defined with reference to Figures 14-19 and 14-20. + +##### Symbol + +![Figure 14-19 – ODUP_TT_So function. The diagram shows two functional blocks, ODUkP and ODUCnP, each represented by a downward-pointing triangle. For the ODUkP block, the input ODUP_AP enters from the top, and two other inputs, ODUPk_TT_So_MP and ODUPk_RP, enter from the left and right respectively. The output is ODUPk_TCP exiting from the bottom. The ODUCnP block follows the same structure but with 'n' subscripts on the signals. A label 'G.798(17)_F14-19' is present in the bottom right corner of the diagram area.](3d590ad29ecfe728f07432e6fcb59064_img.jpg) + +Figure 14-19 – ODUP\_TT\_So function. The diagram shows two functional blocks, ODUkP and ODUCnP, each represented by a downward-pointing triangle. For the ODUkP block, the input ODUP\_AP enters from the top, and two other inputs, ODUPk\_TT\_So\_MP and ODUPk\_RP, enter from the left and right respectively. The output is ODUPk\_TCP exiting from the bottom. The ODUCnP block follows the same structure but with 'n' subscripts on the signals. A label 'G.798(17)\_F14-19' is present in the bottom right corner of the diagram area. + +Figure 14-19 – ODUP\_TT\_So function + +##### Interfaces + +Table 14-2 – ODUP\_TT\_So inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| ODUP_AP:
ODUP_AI_CK
ODUP_AI_D
ODUP_AI_FS
ODUP_AI_MFS
ODUP_AI_RP
ODUP_AI_TSCC
ODUP_RP:
ODUP_RI_BDI
ODUP_RI_BEI[1..n]
ODUP_RI_DM
ODUP_TT_So_MP:
ODUP_TT_So_MI_TxTI
ODUP_TT_So_MI_DM_Source
ODUP_TT_So_MI_DMValue | ODU_TCP:
ODU_CI_CK
ODU_CI_D
ODU_CI_FS
ODU_CI_MFS
ODU_CI_RP
ODU_CI_TSCC | + +##### Processes + +The processes associated with the ODUP\_TT\_So function are as depicted in Figure 14-20. + +**PMOH-TTI:** The trail trace identifier is inserted in the TTI byte position of the PM field in the first ODU overhead instance. Its value is derived from reference point ODUP\_TT\_So\_MP. The trail trace format is described in clause 15.2 of [ITU-T G.709]. + +**PMOH-BDI:** The backward defect indication is inserted in the BDI bit position of the PM field in the first ODU overhead instance. Its value is derived from reference point ODUP\_RP. Upon the + +declaration/clearing of aBDI at the termination sink function, the trail termination source function shall have inserted/removed the BDI indication within 50 ms. + +**PMOH-BEI:** The number of errors indicated in RI\_BEI[i] is encoded in the BEI bits of the PM field in ODU overhead instance #i. Upon the detection of a number of errors at the termination sink function, the trail termination source function shall have inserted that value in the BEI bits within 50 ms. + +**PMOH-BIP-8:** See clause 8.3.4.1. The calculated BIP-8[i] is inserted into the BIP-8 byte of the PM field in ODU overhead instance #i. + +**PMOH-DMp:** If MI\_DM\_Source is false, then the value of the DMp bit field in the first ODU overhead instance is determined by the RI\_DM. If MI\_DM\_Source is true, then the value of the DMp field in the first ODU overhead instance bit is set to MI\_DMValue. + +NOTE – Equipment developed prior to Edition 4.0 of this Recommendation will not support the ODU DMp processing. + +![Figure 14-20 – ODUP_TT_So processes. This block diagram illustrates the internal processing of the ODUP_TT_So function. At the top, the ODUP_AP interface provides inputs: AI_D, AI_CK, AI_FS, AI_MFS, AI_RP, and CI_TSCC. AI_D is connected to a 'Compute BIP-8' block, which outputs 'BIP-8[1..n]'. This output is then processed by an 'Insert BIP-8' block. A vertical 'PMOH insertion' block on the left side of the diagram connects to several processing blocks: 'Insert BIP-8', 'Insert BEI', 'Insert BDI', 'Process/insert DMp', and 'Insert TTI'. The 'Insert BEI' block receives 'RI_BEI[1..n]' from the ODUP_RP interface. The 'Insert BDI' block receives 'RI_BDI' from the ODUP_RP interface. The 'Process/insert DMp' block receives 'RI_DM', 'MI_DM_Source', and 'MI_DMValue' from the ODUP_TT_So_MP interface. The 'Insert TTI' block receives 'MI_TxTI' from the ODUP_TT_So_MP interface. All five blocks ('Insert BIP-8', 'Insert BEI', 'Insert BDI', 'Process/insert DMp', 'Insert TTI') output to the PMOH insertion block. The PMOH insertion block then outputs to the ODUP_TCP interface, which provides outputs: CI_D, CI_CK, CI_FS, CI_MFS, CI_RP, and CI_TSCC. The diagram is labeled G.798(17)_F14-20.](9d47fe89bc71acebde670ea760ee6ffb_img.jpg) + +Figure 14-20 – ODUP\_TT\_So processes. This block diagram illustrates the internal processing of the ODUP\_TT\_So function. At the top, the ODUP\_AP interface provides inputs: AI\_D, AI\_CK, AI\_FS, AI\_MFS, AI\_RP, and CI\_TSCC. AI\_D is connected to a 'Compute BIP-8' block, which outputs 'BIP-8[1..n]'. This output is then processed by an 'Insert BIP-8' block. A vertical 'PMOH insertion' block on the left side of the diagram connects to several processing blocks: 'Insert BIP-8', 'Insert BEI', 'Insert BDI', 'Process/insert DMp', and 'Insert TTI'. The 'Insert BEI' block receives 'RI\_BEI[1..n]' from the ODUP\_RP interface. The 'Insert BDI' block receives 'RI\_BDI' from the ODUP\_RP interface. The 'Process/insert DMp' block receives 'RI\_DM', 'MI\_DM\_Source', and 'MI\_DMValue' from the ODUP\_TT\_So\_MP interface. The 'Insert TTI' block receives 'MI\_TxTI' from the ODUP\_TT\_So\_MP interface. All five blocks ('Insert BIP-8', 'Insert BEI', 'Insert BDI', 'Process/insert DMp', 'Insert TTI') output to the PMOH insertion block. The PMOH insertion block then outputs to the ODUP\_TCP interface, which provides outputs: CI\_D, CI\_CK, CI\_FS, CI\_MFS, CI\_RP, and CI\_TSCC. The diagram is labeled G.798(17)\_F14-20. + +Figure 14-20 – ODUP\_TT\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.2.1.2 ODUP trail termination sink function (ODUP\_TT\_Sk) + +The ODUP\_TT\_Sk function reports the state of the ODU trail (path). It computes the BIP-8[1..n], extracts path monitoring overhead (PMOH) – including the TTI, BIP-8[1..n], BDI, BEI[1..n], DMp and STAT signals – in the PM overhead fields from the ODU signal at its ODUP\_TCP, detects for AIS, OCI, LCK, TIM, DEG and BDI defects, counts during one-second periods errors (detected via the BIP-8), counts number of frames for delay measurement and defects to feed performance monitoring when connected, makes the TTI available to network management, and forwards the error + +and defect information as backward indications to the companion ODUP\_TT\_So function. The ODUCn signal has n PM overhead fields; the ODUK signal has one (n=1) PM overhead field. + +NOTE 1 – The ODUP\_TT\_Sk function extracts and processes the PM overhead irrespective of the presence of one or more levels of tandem connection overhead in the TCM fields. + +The information flow and processing of the ODUP\_TT\_Sk function is defined with reference to Figures 14-21 and 14-22. + +##### Symbol + +![Figure 14-21 shows two functional block diagrams for ODUP_TT_Sk functions. The left diagram is for ODUPkP, showing inputs ODUPkP_TT_Sk_MP (left), ODUPk_TCP (bottom), and output ODUPk_AP (top) and ODUPk_RP (right). The right diagram is for ODUPnCnP, showing inputs ODUPnCnP_TT_Sk_MP (left), ODUPnCn_TCP (bottom), and output ODUPnCn_AP (top) and ODUPnCn_RP (right).](c1bf17571f9cedf76c4072121295d10e_img.jpg) + +Figure 14-21 shows two functional block diagrams for ODUP\_TT\_Sk functions. The left diagram is for ODUPkP, showing inputs ODUPkP\_TT\_Sk\_MP (left), ODUPk\_TCP (bottom), and output ODUPk\_AP (top) and ODUPk\_RP (right). The right diagram is for ODUPnCnP, showing inputs ODUPnCnP\_TT\_Sk\_MP (left), ODUPnCn\_TCP (bottom), and output ODUPnCn\_AP (top) and ODUPnCn\_RP (right). + +Figure 14-21 – ODUP\_TT\_Sk functions + +##### Interfaces + +Table 14-3 – ODUP\_TT\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODU_TCP:
ODU_CI_CK
ODU_CI_D
ODU_CI_FS
ODU_CI_MFS
ODU_CI_SSF
ODU_CI_RP
ODU_CI_TSCC
ODUP_TT_Sk_MP:
ODUP_TT_Sk_MI_ExSAPI
ODUP_TT_Sk_MI_ExDAPI
ODUP_TT_Sk_MI_GetAcTI
ODUP_TT_Sk_MI_TIMDetMo
ODUP_TT_Sk_MI_TIMActDis
ODUP_TT_Sk_MI_DEGThr
ODUP_TT_Sk_MI_DEGM
ODUP_TT_Sk_MI_1second
ODUP_TT_Sk_MI_DM_Source
ODUP_TT_Sk_MI_DMValue | ODUP_AP:
ODUP_AI_CK
ODUP_AI_D
ODUP_AI_FS
ODUP_AI_MFS
ODUP_AI_TSF
ODUP_AI_TSD
ODUP_AI_RP
ODUP_AI_TSCC
ODUP_RP:
ODUP_RI_BDI
ODUP_RI_BEI[1..n]
ODUP_RI_DM
ODUP_TT_Sk_MP:
ODUP_TT_Sk_MI_AcTI
ODUP_TT_Sk_MI_cOCI (Note)
ODUP_TT_Sk_MI_cLCK
ODUP_TT_Sk_MI_cTIM
ODUP_TT_Sk_MI_cDEG
ODUP_TT_Sk_MI_cBDI
ODUP_TT_Sk_MI_cSSF
ODUP_TT_Sk_MI_pN_EBC
ODUP_TT_Sk_MI_pN_DS
ODUP_TT_Sk_MI_pF_EBC
ODUP_TT_Sk_MI_pF_DS
ODUP_TT_Sk_MI_pN_delay | +| NOTE – For ODUPkP_TT_Sk only. | | + +##### Processes + +The processes associated with the ODUP\_TT\_Sk function are as depicted in Figure 14-22. + +**PMOH-BIP-8:** See clause 8.3.4.2. The BIP-8[1..n] is extracted from the BIP-8 byte of the PM fields in the n PM overhead instances of the ODU signal at the ODU\_TCP. + +**PMOH-TTI:** The trail trace identifier shall be recovered from the TTI byte position of the PM field in the first ODU overhead instance of the ODU signal at the ODU\_TCP and processed as specified in clause 8.6. The accepted value of the TTI is available at the MP (MI\_AcTI). + +**PMOH-BDI:** The backward defect indication shall be recovered from the BDI bit position of the PM field in the first ODU overhead instance of the ODU signal at the ODU\_TCP. It shall be used for BDI defect detection. + +**PMOH-BEI:** The BEI[1..n] shall be recovered from the BEI bits in the PM fields of the n PM overhead instances in the ODU signal at the ODU\_TCP. It shall be used to determine if a far-end errored block (nF\_B) has occurred. One nF\_B has occurred per BEI[i] value between 1 [0001] and 8 [1000]; otherwise, no nF\_B has occurred. + +**PMOH-DMp:** If MI\_DM\_Source is false, then the value of the incoming DMp bit (RxDMp) is output to RI\_DM. If MI\_DM\_Source is true and MI\_DMValue toggles, then a count of CI\_FS transitions is started and the RxDMp value is monitored. A change of value of RxDMp, from (NOT MI\_DMValue) to MI\_DMValue, validated by a 3-frame persistency check, stops the counting. The delay frame count (nN\_delay) is represented by the count minus the persistency check. + +NOTE 3 – Equipment developed prior to Edition 4.0 of this Recommendation will not support the DMp processing. + +**PMOH-STAT:** The status information shall be recovered from the STAT bits in the PM field of the first ODU overhead instance in the ODU signal at the ODU\_TCP as defined in clause 8.8. It shall be used for AIS, OCI and LCK defect detection. + +![Figure 14-22 – ODUP_TT_Sk processes. A block diagram showing the internal processes of an ODUP_TT_Sk (Optical Data Unit Path - Tandem Termination) node. The diagram is divided into three main horizontal sections: ODUP_AP (top), ODUP_TT_Sk_MP (middle), and ODUP_TCP (bottom). The ODUP_AP section contains 'Consequent actions' which receive inputs from AI_TSD (aTSD), AI_TSF (aTSF), AI_FSF (CI_FSF), AI_MFS (CI_MFS), AI_CK (CI_CK), and AI_D (CI_D). It outputs RI_BEI[1..n] (nBIPV[1..n]), RI_DM (RxDMp), and RI_BDI. The ODUP_TT_Sk_MP section contains several processing blocks: 'Process TTI' (receiving MI_TIMActDis, MI_ExSAPI, MI_ExDAPI, MI_TIMDetMo, MI_GetAcTI, MI_AcTI and outputting dTIM, RxTI), 'Defect correlation' (receiving dTIM, dDEG, dBDI, dLCK, dOCI, dAIS, CI_SSF and outputting MI_cTIM, MI_cDEG, MI_cBDI, MI_cLCK, MI_cOCI, MI_cSSF), 'Process DMP' (receiving MI_DM_Source, MI_DMValue, nN_delay, RxDMp and outputting dBDI), 'Performance monitoring' (receiving nN_delay, dBDI, nF_B, aTSF and outputting MI_pN_Delay, MI_1second, MI_pF_DS, MI_pF_EBC, MI_pN_DS, MI_pN_EBC), and 'Process errors' (receiving MI_DEGThr, MI_DEGM and outputting dDEG). There are also 'Extract' blocks: 'Extract TTI', 'Extract STAT' (receiving dLCK, dOCI, dAIS), 'Extract DMp' (receiving RxDMp), 'Extract BDI' (receiving dBDI), 'Extract BEI' (receiving nF_B), 'Extract BIP-8' (receiving nBIPV[1..n]), and 'Compute BIP-8' (receiving nN_B). A vertical 'PMOH access' block on the right connects to several 'Extract' blocks. The ODUP_TCP section contains 'Compare' (receiving nN_B, nBIPV[1..n] and outputting dBDI). Various other signals like AI_TSCC, AI_RP, AI_FS are shown at the top and bottom. Reference G.798(23)_F14-22 is at the bottom right.](f512ae9c630f2fb53197fa77a1bda0e8_img.jpg) + +Figure 14-22 – ODUP\_TT\_Sk processes. A block diagram showing the internal processes of an ODUP\_TT\_Sk (Optical Data Unit Path - Tandem Termination) node. The diagram is divided into three main horizontal sections: ODUP\_AP (top), ODUP\_TT\_Sk\_MP (middle), and ODUP\_TCP (bottom). The ODUP\_AP section contains 'Consequent actions' which receive inputs from AI\_TSD (aTSD), AI\_TSF (aTSF), AI\_FSF (CI\_FSF), AI\_MFS (CI\_MFS), AI\_CK (CI\_CK), and AI\_D (CI\_D). It outputs RI\_BEI[1..n] (nBIPV[1..n]), RI\_DM (RxDMp), and RI\_BDI. The ODUP\_TT\_Sk\_MP section contains several processing blocks: 'Process TTI' (receiving MI\_TIMActDis, MI\_ExSAPI, MI\_ExDAPI, MI\_TIMDetMo, MI\_GetAcTI, MI\_AcTI and outputting dTIM, RxTI), 'Defect correlation' (receiving dTIM, dDEG, dBDI, dLCK, dOCI, dAIS, CI\_SSF and outputting MI\_cTIM, MI\_cDEG, MI\_cBDI, MI\_cLCK, MI\_cOCI, MI\_cSSF), 'Process DMP' (receiving MI\_DM\_Source, MI\_DMValue, nN\_delay, RxDMp and outputting dBDI), 'Performance monitoring' (receiving nN\_delay, dBDI, nF\_B, aTSF and outputting MI\_pN\_Delay, MI\_1second, MI\_pF\_DS, MI\_pF\_EBC, MI\_pN\_DS, MI\_pN\_EBC), and 'Process errors' (receiving MI\_DEGThr, MI\_DEGM and outputting dDEG). There are also 'Extract' blocks: 'Extract TTI', 'Extract STAT' (receiving dLCK, dOCI, dAIS), 'Extract DMp' (receiving RxDMp), 'Extract BDI' (receiving dBDI), 'Extract BEI' (receiving nF\_B), 'Extract BIP-8' (receiving nBIPV[1..n]), and 'Compute BIP-8' (receiving nN\_B). A vertical 'PMOH access' block on the right connects to several 'Extract' blocks. The ODUP\_TCP section contains 'Compare' (receiving nN\_B, nBIPV[1..n] and outputting dBDI). Various other signals like AI\_TSCC, AI\_RP, AI\_FS are shown at the top and bottom. Reference G.798(23)\_F14-22 is at the bottom right. + +Figure 14-22 – ODUP\_TT\_Sk processes + +##### Defects + +The function shall detect dAIS, dOCI, dLCK, dTIM, dDEG and dBDI defects. + +**dAIS:** See clause 6.2.6.3.2. + +**dOCI:** For ODUkP, see clause 6.2.6.8.2; dOCI shall be set to false during CI\_SSF. For ODUCnP dOCI shall be assumed false. + +**dLCK:** See clause 6.2.6.9.1; dLCK shall be set to false during CI\_SSF. + +**dTIM:** See clause 6.2.2.1; dTIM shall be set to false during CI\_SSF. + +**dDEG:** See clause 6.2.3.4. + +**dBDI:** See clause 6.2.6.6.1; dBDI shall be set to false during CI\_SSF. + +##### Consequent actions + +The function shall perform the following consequent actions: + +$$\text{aBDI} \leftarrow \text{CI\_SSF or dAIS or dOCI or dLCK or dTIM}$$ +$$\text{aTSF} \leftarrow \text{CI\_SSF or dAIS or dOCI or dLCK or (dTIM and (not TIMActDis))}$$ +$$\text{aTSD} \leftarrow \text{dDEG}$$ + +For each PM overhead instance #i: + +$$\text{aBEI}[i] \leftarrow \text{nBIPV}[i]$$ + +##### Defect correlations + +The function shall perform the following defect correlations to determine the most probable fault cause (see clause 6.4 of [ITU-T G.806]). This fault cause shall be reported to the EMF. + +$$\text{cOCI} \leftarrow \text{dOCI and (not CI\_SSF)}$$ +$$\text{cLCK} \leftarrow \text{dLCK and (not CI\_SSF)}$$ +$$\text{cTIM} \leftarrow \text{dTIM and (not CI\_SSF) and (not dAIS) and (not dOCI) and (not dLCK)}$$ +$$\text{cDEG} \leftarrow \text{dDEG and (not CI\_SSF) and (not dAIS) and (not dOCI) and (not dLCK) and (not (dTIM and (not TIMActDis)))}$$ +$$\text{cBDI} \leftarrow \text{dBDI and (not CI\_SSF) and (not dAIS) and (not dOCI) and (not dLCK) and (not (dTIM and (not TIMActDis)))}$$ +$$\text{cSSF} \leftarrow \text{CI\_SSF or dAIS}$$ + +##### Performance monitoring + +The function shall perform the following performance monitoring primitives processing (see clause 6.5 of [ITU-T G.806]). The performance monitoring primitives shall be reported to the EMF. + +$$\text{pN\_DS} \leftarrow \text{CI\_SSF or dAIS or dOCI or dLCK or dTIM}$$ +$$\text{pF\_DS} \leftarrow \text{dBDI}$$ +$$\text{pN\_EBC} \leftarrow \sum \text{nN\_B}$$ + +NOTE 4 – During CI\_SSF, dAIS, dLCK and dOCI, no errored blocks shall be counted. + +$$\text{pF\_EBC} \leftarrow \sum \text{nF\_B}$$ + +NOTE 5 – During CI\_SSF, dAIS, dLCK and dOCI, no errored blocks shall be counted. + +$$\text{pN\_delay} \leftarrow \text{nN\_delay}$$ + +NOTE 6 – This count is triggered by the ODUP\_TT\_Sk\_MI\_DMValue toggle event, which is equal to the ODUP\_TT\_So\_MI\_DMValue toggle event. + +NOTE 7 – This value is a snapshot value. + +NOTE 8 – This value is invalid if a STAT field indicating AIS, OCI, LCK, LTC, or BDI is received during the measurement. + +### 14.2.2 ODUP non-intrusive monitor function + +As the functionality of the ODUP non-intrusive monitor function is identical to the ODUP\_TT\_Sk function (see clause 14.2.1.2), no dedicated ODUP non-intrusive monitoring function ODUPm\_TT\_Sk is defined. For ODUP non-intrusive monitoring, the ODUP\_TT\_Sk function is connected to the ODU\_CP as shown in Figure 14-23. The ODUP\_TT\_Sk function can be connected to any ODU\_CP in this manner. + +The unused outputs (e.g., ODU\_RI, ODU\_AI\_CK/D/FS/MFS) are left open. The TSF and TSD outputs of an ODUkP non-intrusive monitor can be connected to an ODU\_C connection function and used as protection switching trigger criteria for SNC/N protection; for an ODUCnP non-intrusive monitor the TSF and TSD output are also left open. + +![Figure 14-23: Connection of ODUP_TT_Sk function as non-intrusive monitor (examples). The diagram shows two examples of ODU_C connection functions. The left example shows an ODU_C connected to multiple ODUkP and ODUkT components, with ODUkP non-intrusive monitors connected to the ODU_C and receiving TSF and TSD signals. The right example shows an ODUCnP connected to multiple ODUCnT components, with ODUCnP non-intrusive monitors connected to the ODUCnP.](61474739fd197587cfea52af9b6a3885_img.jpg) + +Figure 14-23: Connection of ODUP\_TT\_Sk function as non-intrusive monitor (examples). The diagram shows two examples of ODU\_C connection functions. The left example shows an ODU\_C connected to multiple ODUkP and ODUkT components, with ODUkP non-intrusive monitors connected to the ODU\_C and receiving TSF and TSD signals. The right example shows an ODUCnP connected to multiple ODUCnT components, with ODUCnP non-intrusive monitors connected to the ODUCnP. + +G.798(17)\_F14-23 + +**Figure 14-23 – Connection of ODUP\_TT\_Sk function as non-intrusive monitor (examples)** + +## 14.3 Adaptation functions + +### 14.3.1 ODUkP to CBRx adaptation function using AMP and BMP (ODUkP/CBRx\_A) + +The ODUkP to CBRx adaptation functions perform the adaptation between the ODUkP ( $k = 1, 2, 2e, 3, \text{flex}$ ) layer adapted information and the characteristic information of a CBRx signal. Parameter $x$ defines the bit rate or bit-rate range of the CBR signal. The $x$ values are listed in Tables 14-4 and 14-5. Support for other bit rates and bit-rate ranges are for further study. + +**Table 14-4 – Defined values for $x$ for bit synchronous mapping** + +| $x$ | Bit rate | Clock range | +|--------------------------|---------------------------------------------------------------|--------------------------------------------------------------------| +| 2G5 | 2 488 320 kbit/s $\pm 20$ ppm | 2 488 320 kHz $\pm 20$ ppm | +| 10G | 9 953 280 kbit/s $\pm 20$ ppm | 9 953 280 kHz $\pm 20$ ppm | +| 10G3 | 10 312 500 kbit/s $\pm 100$ ppm | 10 312 500 kHz $\pm 100$ ppm | +| 40G | 39 813 120 kbit/s $\pm 20$ ppm | 39 813 120 kHz $\pm 20$ ppm | +| Any other rate above 2G5 | Client rate with a tolerance up to a maximum of $\pm 100$ ppm | Client frequency with a tolerance up to a maximum of $\pm 100$ ppm | + +**Table 14-5 – Defined values for x for asynchronous mapping** + +| x | Bit rate | Clock range | +|------------|--------------------------------|-----------------------------| +| 2G5 | 2 488 320 kbit/s $\pm$ 20 ppm | 2 488 320 kHz $\pm$ 20 ppm | +| 2G5 (Note) | 2 488 320 kbit/s $\pm$ 32 ppm | 2 488 320 kHz $\pm$ 32 ppm | +| 10G | 9 953 280 kbit/s $\pm$ 20 ppm | 9 953 280 kHz $\pm$ 20 ppm | +| 10G (Note) | 9 953 280 kbit/s $\pm$ 32 ppm | 9 953 280 kHz $\pm$ 32 ppm | +| 40G | 39 813 120 kbit/s $\pm$ 20 ppm | 39 813 120 kHz $\pm$ 20 ppm | + +NOTE – The 2G5 and 10G signals with 32 ppm tolerance represent the CM-GPON and CM-XGPON signals. + +Two different source functions are defined. The ODUkP/CBRx-a\_A\_So provides asynchronous mapping, while the ODUkP/CBRx-b\_A\_So provides bit synchronous mapping. In the sink direction, the ODUkP/CBRx\_A\_Sk can handle both (bit synchronous and asynchronous) mappings. + +#### **14.3.1.1 ODUkP to CBRx asynchronous mapping adaptation source function (ODUkP/CBRx-a\_A\_So) (x = 2G5, 10G, 40G)** + +The ODUkP/CBRx-a\_A\_So function creates the ODUk signal from a free-running clock. It asynchronously maps the $4^{(k-1)} \times 2\,488\,320$ kbit/s constant bit-rate client signal from the CBRx\_CP into the payload of the OPUk (k = 1, 2, 3), adds OPUk overhead (RES, PT, JC) and default ODUk overhead. + +The information flow and processing of the ODUkP/CBRx-a\_A\_So function are defined with reference to Figures 14-24 and 14-25. + +##### **Symbol** + +![Block diagram of the ODUkP/CBRx-a_A_So function. An input labeled CBRx_CP enters a trapezoidal block labeled ODUkP/CBRx-a. The input is associated with x = 2G5, 10G, 40G. The output is labeled ODUkP_AP and is associated with k = 1, 2, 3. A reference code G.798(17)_F14-24 is shown below the diagram.](48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg) + +Block diagram of the ODUkP/CBRx-a\_A\_So function. An input labeled CBRx\_CP enters a trapezoidal block labeled ODUkP/CBRx-a. The input is associated with x = 2G5, 10G, 40G. The output is labeled ODUkP\_AP and is associated with k = 1, 2, 3. A reference code G.798(17)\_F14-24 is shown below the diagram. + +**Figure 14-24 – ODUkP/CBRx-a\_A\_So function** + +##### **Interfaces** + +**Table 14-6 – ODUkP/CBRx-a\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------|------------------------------------------------------------------------------| +| CBRx_CP:
CBRx_CI_CK
CBRx_CI_D
CBRx_CI_SSF | ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_MFS | + +##### Processes + +- **Clock and (multi)frame start signal generation:** The function shall generate a local ODUk clock (ODUKP\_AI\_CK) of $(239/(239 - k)) \times 4^{(k-1)} \times 2\,488\,320\text{ kHz} \pm 20\text{ ppm}$ from a free-running oscillator. The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUk signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +- **Mapping, frequency justification and bit rate adaptation:** The function shall provide an elastic store (buffer) process. The data signal CBRx\_CI shall be written into the buffer under the control of the associated input clock. The data shall be read out of the buffer and written onto the D and N/PJO bytes in the OPUk frame under the control of the ODUk clock and justification decisions as defined in clause 17.1 of [ITU-T G.709]. + +A justification decision shall be performed each frame. Each justification decision results in a corresponding positive, negative or no justification action. Upon a positive justification action, the reading of one data byte out of the buffer shall be cancelled once. No CBRx data shall be written onto the PJO and NJO byte. Upon a negative justification action, one extra data byte shall be read once out of the buffer. CBRx data shall be written onto the PJO and NJO byte. If neither a positive nor a negative justification action is to be performed, CBRx data shall be written onto the PJO byte and no CBRx data shall be written onto the NJO byte. + +The justification decisions determine the phase error introduced by the function. + +*Buffer size:* In the presence of jitter as specified by [ITU-T G.825] and a frequency within the range $4^{(k-1)} \times 2\,488\,320\text{ kHz} \pm 20\text{ ppm}$ , this mapping process shall not introduce any errors. The maximum buffer hysteresis, and therefore the maximum phase error introduced, shall be as listed in Table 14-7. + +**Table 14-7 – Maximum buffer hysteresis** + +| Mapping | Maximum buffer hysteresis | +|------------|---------------------------| +| 2G5 → ODU1 | 2 bytes | +| 10G → ODU2 | 8 bytes | +| 40G → ODU3 | 32 bytes | + +- **JC bits:** The function shall generate the justification control (JC) bits based on the justification decision performed in the current frame according to the specification in clause 17.1 of [ITU-T G.709]. It shall insert the justification control bits in the appropriate JC bit positions in the JC bytes of the current frame. +- **PT:** The function shall insert code "0000 0010" into the PT byte position of the PSI overhead as defined in clause 15.9.2.1 of [ITU-T G.709]. + - **RES:** The function shall insert all-ZEROs into the RES bytes and reserved bits within the JC bytes. + - **CSF:** The function shall signal the failure of the client signal to the far end by use of Bit 1 of the PSI[2] byte of the payload structure identifier as defined in clause 17.1 of [ITU-T G.709]. + +All other bits of the ODUk overhead should be sourced as "0"s, except the PMOH STAT field which should be set to the value "normal path signal" (001). + +NOTE – Equipment developed prior to Edition 4.0 of this Recommendation will not support the CSF processing. + +![Figure 14-25 – ODUkP/CBRx-a_A_So processes. This block diagram illustrates the internal architecture of the ODUkP/CBRx-a_A_So adaptation function. At the top, the CBRx_CP input provides three signals: CI_D (data), CI_CK (clock), and CI_SSF (synchronization signal). CI_D and CI_CK are fed into an 'Elastic store' block, which has write (WR) and read (RD) ports. The Elastic store's output is connected to a 'Justification control and JC generation' block. This block also receives CI_SSF and generates a Justification Control (JC) signal back to the Elastic store. The Justification control block outputs a 'Free-running clock generator (ODCa)' signal labeled CK. The CK signal is divided by 122368 to produce a Frequency Synchronization (FS) signal, which is further divided by 256 to produce a Master Frequency Synchronization (MFS) signal. The Elastic store's output is also processed by a series of blocks: 'Insert PT', 'Insert CSF' (which also receives CI_SSF), 'Insert RES', and a block stating 'ODUk OH is set to all-0's, except PM STAT = 001'. The final output of these blocks is the ODUkP_AP signal, which consists of AI_D (data), AI_CK (clock), AI_FS (frequency synchronization), and AI_MFS (master frequency synchronization). The diagram is labeled G.798(17)_F14-25.](5cc9a312ebe733ae244e3b93cfea67e1_img.jpg) + +Figure 14-25 – ODUkP/CBRx-a\_A\_So processes. This block diagram illustrates the internal architecture of the ODUkP/CBRx-a\_A\_So adaptation function. At the top, the CBRx\_CP input provides three signals: CI\_D (data), CI\_CK (clock), and CI\_SSF (synchronization signal). CI\_D and CI\_CK are fed into an 'Elastic store' block, which has write (WR) and read (RD) ports. The Elastic store's output is connected to a 'Justification control and JC generation' block. This block also receives CI\_SSF and generates a Justification Control (JC) signal back to the Elastic store. The Justification control block outputs a 'Free-running clock generator (ODCa)' signal labeled CK. The CK signal is divided by 122368 to produce a Frequency Synchronization (FS) signal, which is further divided by 256 to produce a Master Frequency Synchronization (MFS) signal. The Elastic store's output is also processed by a series of blocks: 'Insert PT', 'Insert CSF' (which also receives CI\_SSF), 'Insert RES', and a block stating 'ODUk OH is set to all-0's, except PM STAT = 001'. The final output of these blocks is the ODUkP\_AP signal, which consists of AI\_D (data), AI\_CK (clock), AI\_FS (frequency synchronization), and AI\_MFS (master frequency synchronization). The diagram is labeled G.798(17)\_F14-25. + +**Figure 14-25 – ODUkP/CBRx-a\_A\_So processes** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### **14.3.1.2 ODUkP to CBRx bit synchronous mapping adaptation source function (ODUkP/CBRx-b\_A\_So)** + +The ODUkP/CBRx-b\_A\_So function creates the ODUk signal from a clock, derived from the incoming CBRx\_CI clock. It bit synchronously maps the $4^{(k-1)} \times 2\,488\,320\text{ kbit/s} \pm 20\text{ ppm}$ ( $k = 1, 2, 3$ ) or $10\,312\,500\text{ kbit/s} \pm 100\text{ ppm}$ ( $k = 2e$ ) or other CBR signals greater than $2\,488\,320\text{ kbit/s} \pm 100\text{ ppm}$ ( $k = \text{flex}$ ) constant bit-rate client signal from the CBRx\_CP into the payload of the OPUk ( $k = 1, 2, 2e, 3, \text{flex}$ ), adds OPUk overhead (PT, JC, RES) and default ODUk overhead. + +The information flow and processing of the ODUkP/CBRx-b\_A\_So function are defined with reference to Figures 14-26 and 14-27. + +##### Symbol + +![Symbol diagram for ODUkP/CBRx-b_A_So function. It shows an input CBRx_CP entering a trapezoidal block labeled ODUkP/CBRx-b, with an output ODUkP_AP exiting the block. The reference G.798(17)_F14-26 is noted below the block.](dc075f714892571abc5f74f1a76b80dc_img.jpg) + +G.798(17)\_F14-26 + +Symbol diagram for ODUkP/CBRx-b\_A\_So function. It shows an input CBRx\_CP entering a trapezoidal block labeled ODUkP/CBRx-b, with an output ODUkP\_AP exiting the block. The reference G.798(17)\_F14-26 is noted below the block. + +**Figure 14-26 – ODUkP/CBRx-b\_A\_So function** + +##### Interfaces + +**Table 14-8 – ODUkP/CBRx-b\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------|------------------------------------------------------------------------------| +| CBRx_CP:
CBRx_CI_CK
CBRx_CI_D
CBRx_CI_SSF | ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_MFS | + +##### Processes + +- **Clock and (multi)frame start signal generation:** The function shall generate the ODUk (AI\_CK) clock by multiplying the incoming CBRx clock (CI\_CK) by factor as specified in Table 14-9 below. The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCb clock), apply. + +**Table 14-9 – Bit synchronous mapping parameters** + +| ODUk | Multiplication factor | CBR clock frequency | CBR client jitter specification in | +|---------|-----------------------|--------------------------------------------------------------------|------------------------------------| +| ODU1 | 239/238 | 2 488 320 kHz $\pm$ 20 ppm | [ITU-T G.825] | +| ODU2 | 239/237 | 9 953 280 kHz $\pm$ 20 ppm | [ITU-T G.825] | +| ODU2e | 239/237 | 10 312 500 kHz $\pm$ 100 ppm | [IEEE 802.3] | +| ODU3 | 239/236 | 39 813 120 kHz $\pm$ 20 ppm | [ITU-T G.825] | +| ODUflex | 239/238 | Client frequency with a tolerance up to a maximum of $\pm$ 100 ppm | Client specific | + +During failure conditions of the incoming CBR clock signal (CI\_CK), the ODUk clock shall stay within its limits as defined in [ITU-T G.8251] and no frame phase discontinuity shall be introduced. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUk signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +- **Mapping, frequency justification and bit-rate adaptation:** The function shall provide an elastic store (buffer) process. The data signal CBRx\_CI shall be written into the buffer under the control of the associated input clock. The data shall be read out of the buffer and written onto the D and PJO bytes in the OPUk frame under the control of the ODUk clock as defined in clause 17.2 of [ITU-T G.709] (k = 1, 2, 2e, 3) and clause 17.9 of [ITU-T G.709] (k = flex). + +Neither negative nor positive justification is to be performed. No data shall be written onto the NJO byte and data shall always be written onto the PJO byte. + +*Buffer size:* In the presence of jitter as specified by the relevant standard as listed in Table 14-9, this mapping process shall not introduce any errors. + +Following a step in frequency of the CI\_CK signal (for example, due to removal of AIS (generic AIS or Local Fault)), there will be a maximum recovery time of X seconds after which this process shall not generate any bit errors. The value of X is for further study; a value of 1 second has been proposed. + +- **JC bits:** The function shall generate the fixed justification control (JC) bits "00" according to clause 17.2 of [ITU-T G.709]. It shall insert the justification control bits in the appropriate JC bit positions in the JC bytes. +- **RES:** The function shall insert all-ZEROs into the RES bytes and Reserved bits within the JC bytes. + - **PT:** The function shall insert the appropriate payload type code into the PT byte position of the PSI overhead as defined in clause 15.9.2.1 of [ITU-T G.709]. + - **Client signal fail:** The function shall insert client signal fail indication CSF under the control of CBR\_CI\_SSF into Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +All other bits of the ODUk overhead should be sourced as "0"s, except the PMOH STAT field which should be set to the value "normal path signal" (001). + +NOTE – Equipment developed prior to Edition 4.0 of this Recommendation will not support the CSF processing. + +![Block diagram of ODUkP/CBRx-b_A_So processes. The diagram shows the mapping of client data (CI_D) and clock (CI_CK) into an ODUk payload. CI_D is written to an Elastic store (WR), and CI_CK is used to generate the ODU clock (ODCb). The Elastic store output (RD) is mapped into the ODUk payload. The ODUk payload is generated by inserting PT, CSF (controlled by CI_SSF), and RES bytes, and setting the ODUk OH to all-0's except for PM STAT = 001. The ODUk payload is then mapped into the AI_D, AI_CK, AI_FS, and AI_MFS signals. The diagram also shows the generation of the ODUk clock (ODCb) from the CI_CK signal, and the generation of the ODUk payload structure identifier (PSI) from the PT, CSF, and RES bytes. The ODUk payload is then mapped into the AI_D, AI_CK, AI_FS, and AI_MFS signals. The diagram is labeled CBRx_CP at the top and ODUkP_AP at the bottom. The text G.798(17)_F14-27 is in the bottom right corner.](33859177822cce0c1b03fd3d37de14f6_img.jpg) + +Block diagram of ODUkP/CBRx-b\_A\_So processes. The diagram shows the mapping of client data (CI\_D) and clock (CI\_CK) into an ODUk payload. CI\_D is written to an Elastic store (WR), and CI\_CK is used to generate the ODU clock (ODCb). The Elastic store output (RD) is mapped into the ODUk payload. The ODUk payload is generated by inserting PT, CSF (controlled by CI\_SSF), and RES bytes, and setting the ODUk OH to all-0's except for PM STAT = 001. The ODUk payload is then mapped into the AI\_D, AI\_CK, AI\_FS, and AI\_MFS signals. The diagram also shows the generation of the ODUk clock (ODCb) from the CI\_CK signal, and the generation of the ODUk payload structure identifier (PSI) from the PT, CSF, and RES bytes. The ODUk payload is then mapped into the AI\_D, AI\_CK, AI\_FS, and AI\_MFS signals. The diagram is labeled CBRx\_CP at the top and ODUkP\_AP at the bottom. The text G.798(17)\_F14-27 is in the bottom right corner. + +Figure 14-27 – ODUkP/CBRx-b\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.3.1.3 ODUkP to CBRx adaptation sink function (ODUkP/CBRx\_A\_Sk) + +The ODUkP/CBRx\_A\_Sk recovers the constant bit-rate client signal from the OPUk payload using the justification control information (JC overhead) to determine if a data or stuff byte is present within the NJO and PJO bytes. It extracts the OPUk overhead (PT, JC, and RES) and monitors the reception of the correct payload type. Under signal fail condition, generic-AIS shall be generated. + +The information flow and processing of the ODUkP/CBRx\_A\_Sk function are defined with reference to Figures 14-28 and 14-29. + +##### Symbol + +![Symbol diagram for the ODUkP/CBRx_A_Sk function. A central trapezoidal block is labeled 'ODUkP/CBRx'. An arrow labeled 'ODUkP_AP' points into the block from the bottom. An arrow labeled 'CBRx_CP' points out of the block from the top. An arrow labeled 'ODUkP/CBRx_A_Sk_MP' points out of the block from the left. The text 'G.798(17)_F14-28' is located below the block.](0070d5ae6e586c9cfa20085d26d3eb2e_img.jpg) + +G.798(17)\_F14-28 + +Symbol diagram for the ODUkP/CBRx\_A\_Sk function. A central trapezoidal block is labeled 'ODUkP/CBRx'. An arrow labeled 'ODUkP\_AP' points into the block from the bottom. An arrow labeled 'CBRx\_CP' points out of the block from the top. An arrow labeled 'ODUkP/CBRx\_A\_Sk\_MP' points out of the block from the left. The text 'G.798(17)\_F14-28' is located below the block. + +**Figure 14-28 – ODUkP/CBRx\_A\_Sk function** + +##### Interfaces + +**Table 14-10 – ODUkP/CBRx\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_TSF | CBRx_CP:
CBRx_CI_CK
CBRx_CI_D
CBRx_CI_SSF
ODUkP/CBRx_A_Sk_MP:
ODUkP/CBRx_A_Sk_MI_cPLM
ODUkP/CBRx_A_Sk_MI_cCSF
ODUkP/CBRx_A_Sk_MI_AcPT | + +##### Processes + +- **PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. +- **RES:** The value in the RES bytes shall be ignored. +- **JC:** The function shall interpret the justification control information in the JC byte as defined in clauses 17.2 and 17.9 of [ITU-T G.709] in order to determine the justification action (positive, negative, none) for the current frame. RES bits in the JC shall be ignored. + +– **Demapping, CBR clock generation:** The function shall provide an elastic store (buffer) process. The CBR data shall be written into the buffer from the D, PJO and NJO byte in the OPUk frame. The information extraction of the PJO and NJO bytes shall be under the control of the justification control information. The CBRx data (CI\_D) shall be read out of the buffer under the control of the CBRx clock (CI\_CK). + +Upon a positive justification action, the writing of one data byte into the buffer shall be cancelled once. No CBRx data shall be read from the PJO and NJO byte. Upon a negative justification action, one extra data byte shall be written into the buffer once. CBRx data shall be read from the PJO and NJO byte. If neither a positive nor a negative justification action is to be performed, CBRx data shall be read from the PJO byte and no CBRx data shall be read from the NJO byte. + +**Client signal fail:** The function shall extract the CSF signal indicating the failure of the client signal out of the Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +*Smoothing and jitter limiting process:* The function shall provide for a clock smoothing and elastic store (buffer) process. The data signal shall be written into the buffer under the control of the associated (gapped) input clock. The data signal shall be read out of the buffer under the control of a smoothed (equally spaced) clock. The rate is determined by the signal at the input of the remote ODUkP/CBRx\_A\_So. + +The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCp clock), apply. + +*Buffer size:* In the presence of jitter as specified by the relevant standard as listed in Table 14-9, this justification process shall not introduce any errors. + +Following a step in frequency of the signal transported by the ODUkP\_AI (for example due to removal of a replacement signal with a frequency offset), there will be a maximum recovery time of X seconds after which this process shall not generate any bit errors. The value of X is for further study; a value of 1 second has been proposed. + +NOTE – Equipment developed prior to Edition 4.0 of this Recommendation will not support the CSF processing. + +![Figure 14-29 – ODUkP/CBRx_A_Sk processes. This block diagram illustrates the internal components and signal flow of the ODUkP/CBRx_A_Sk process. The process is divided into two main sections: CBRx_CP (top) and ODUkP_AP (bottom). Inputs include CI_D, CI_CK, CI_SSF, AI_D, AI_MFS, AI_CK, AI_FS, and AI_TSF. The CBRx_CP section contains a 'Replacement signal insertion' block, a 'Replacement signal generator' block, an 'Elastic store' (with WR and RD ports), a 'CBR clock generator (ODCp)' block, and a 'Consequent actions' block. The ODUkP_AP section contains 'Extract JC', 'Extract CSF', and 'Extract PT' blocks, a 'Justification action' block, a 'PT process' block, and a 'Defect correlations' block. Signal flow includes data paths from the input sections through the elastic store and extraction blocks, and control paths for clock and defect detection. Output signals include CI_D, CI_CK, CI_SSF, MI_cPLM, MI_cCSF, MI_AcPT, and ODUkP/CBRx_A_Sk_MP.](40d0aaaa3afa0a9fabe637941ca250bb_img.jpg) + +Figure 14-29 – ODUkP/CBRx\_A\_Sk processes. This block diagram illustrates the internal components and signal flow of the ODUkP/CBRx\_A\_Sk process. The process is divided into two main sections: CBRx\_CP (top) and ODUkP\_AP (bottom). Inputs include CI\_D, CI\_CK, CI\_SSF, AI\_D, AI\_MFS, AI\_CK, AI\_FS, and AI\_TSF. The CBRx\_CP section contains a 'Replacement signal insertion' block, a 'Replacement signal generator' block, an 'Elastic store' (with WR and RD ports), a 'CBR clock generator (ODCp)' block, and a 'Consequent actions' block. The ODUkP\_AP section contains 'Extract JC', 'Extract CSF', and 'Extract PT' blocks, a 'Justification action' block, a 'PT process' block, and a 'Defect correlations' block. Signal flow includes data paths from the input sections through the elastic store and extraction blocks, and control paths for clock and defect detection. Output signals include CI\_D, CI\_CK, CI\_SSF, MI\_cPLM, MI\_cCSF, MI\_AcPT, and ODUkP/CBRx\_A\_Sk\_MP. + +**Figure 14-29 – ODUkP/CBRx\_A\_Sk processes** + +##### Defects + +The function shall detect for dPLM and dCSF defects. + +- **dPLM:** See clause 6.2.4.1. The expected payload type values are defined in clause 15.9.2.1 of [ITU-T G.709]; "0000 0010" is used for asynchronous CBRx mapping, other applicable values are used for bit synchronous CBRx mapping. +- **dCSF:** See clause 6.2.10. + +##### Consequent actions + +aSSF $\leftarrow$ AI\_TSF or dPLM + +aAIS $\leftarrow$ AI\_TSF or dPLM + +On declaration of aAIS, the function shall output a replacement signal as defined in clauses 17.2 and 17.9 of [ITU-T G.709] within two frames. On clearing aAIS, the replacement pattern/signal shall be removed within two frames and normal data being output. The replacement signal clock shall be independent from the incoming clock. The replacement signal clock has to be within the range specified by Table 14-9. Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCp clock), apply. + +##### Defect correlations + +cPLM $\leftarrow$ dPLM and (not AI\_TSF) + +cCSF $\leftarrow$ dCSF and (not dPLM) and (not AI\_TSF) + +**Performance monitoring:** None. + +### 14.3.2 Blank clause + +NOTE – This clause is intentionally left blank. + +### 14.3.3 ODU2P to 10G Ethernet Reconciliation sublayer adaptation functions (ODU2P/ERS10G\_A) + +The ODU2P to 10G Ethernet Reconciliation sublayer adaptation functions perform the adaptation between the ODU2P and the characteristic information of an ERS10G signal. + +The ERS10G characteristic information is a stream of ERS10G\_CI\_D traffic units, complemented with the ERS10G\_CI\_SSF signal. The ERS10G\_CI\_D traffic units carry either an Ethernet data frame, including the preamble, or an ordered set, as defined in clause 7.9 of [ITU-T G.704]. The ordered sets may carry local fault or remote fault indications. The ERS10G\_CP reference point is located within the reconciliation sublayer (see Figure 44-1 of [IEEE 802.3]). + +NOTE – There is no Ethernet MAC termination function in these adaptation functions. Consequently, since no error checking is performed on the Ethernet MAC frames, errored MAC frames are forwarded at both the ingress and egress to the GFP adaptation functions. + +#### 14.3.3.1 ODU2P to 10G Ethernet Reconciliation sublayer adaptation source function (ODU2P/ERS10G\_A\_So) + +The ODU2P/ERS10G\_A\_So function creates the ODU2P signal from a free running clock. It maps the ERS10G\_CI information into the extended payload of the OPU2P, adds OPU2P overhead (RES, PT) and default ODU2P overhead. + +##### Symbol + +![Symbol diagram for ODU2P/ERS10G_A_So function. It shows a trapezoidal block labeled 'ODU2P/ERS10G'. An arrow labeled 'ERS10G_CP' points into the top of the block. An arrow labeled 'ODU2P/ERS10G_A_So_MP' points into the left side of the block. An arrow labeled 'ODU2P_AP' points out from the bottom of the block. Below the block is the text 'G.798(17)-Amd.1(18)_F14-29.1'.](27c0455a3b08749fed8057467366b0ce_img.jpg) + +Symbol diagram for ODU2P/ERS10G\_A\_So function. It shows a trapezoidal block labeled 'ODU2P/ERS10G'. An arrow labeled 'ERS10G\_CP' points into the top of the block. An arrow labeled 'ODU2P/ERS10G\_A\_So\_MP' points into the left side of the block. An arrow labeled 'ODU2P\_AP' points out from the bottom of the block. Below the block is the text 'G.798(17)-Amd.1(18)\_F14-29.1'. + +**Figure 14-29.1 – ODU2P/ERS10G\_A\_So symbol** + +##### Interfaces + +**Table 14-10.1 – ODU2P/ERS10G\_A\_So interfaces** + +| Inputs | Outputs | +|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------| +| ERS10G_CP:
ERS10G_CI_D
ERS10G_CI_SSF
ODU2P/ERS10G_A_So_MP:
ODU2P/ERS10G_A_So_MI_CSFEnable | ODU2P_AP:
ODU2P_AI_D
ODU2P_AI_CK
ODU2P_AI_FS
ODU2P_AI_MFS | +| NOTE – ERS10G_CI_D is composed of preamble, payload and order set information in [ITU-T G.704]. | | + +##### Processes + +A process diagram of this function is shown in Figure 14-29.2. + +![Functional block diagram of the ODU2P/ERS10G_A_So process. The diagram is contained within a grey box labeled 'ODU2P/ERS10G_A_So_MP' on the left. At the top, inputs 'CI_D' and 'CI_SSF' enter from 'ERS10G_CP'. Inside the box, there are four stacked processing blocks: 1. 'ERS10G specific GFP-F processes' receiving 'FCSEnable = false' and 'MI_CSFenable'. 2. 'Common GFP-F processes' receiving 'CMuxConfig' and 'CMuxActive = false'. 3. 'ODU2P specific GFP-F processes'. 4. Another 'ODU2P specific GFP-F processes' block. Data flows downward between blocks via 'GFP_FS', 'GFP_Frame', 'D', 'CK', and 'FS' signals. At the bottom, outputs 'AI_D', 'AI_CK', 'AI_FS', and 'AI_MFS' exit to 'ODU2P_AP'. A reference code 'G.798(17)-Amd.1(18)_F14-29.2' is at the bottom right.](54f73f693f36dcbd300fa21ac4e410e8_img.jpg) + +Functional block diagram of the ODU2P/ERS10G\_A\_So process. The diagram is contained within a grey box labeled 'ODU2P/ERS10G\_A\_So\_MP' on the left. At the top, inputs 'CI\_D' and 'CI\_SSF' enter from 'ERS10G\_CP'. Inside the box, there are four stacked processing blocks: 1. 'ERS10G specific GFP-F processes' receiving 'FCSEnable = false' and 'MI\_CSFenable'. 2. 'Common GFP-F processes' receiving 'CMuxConfig' and 'CMuxActive = false'. 3. 'ODU2P specific GFP-F processes'. 4. Another 'ODU2P specific GFP-F processes' block. Data flows downward between blocks via 'GFP\_FS', 'GFP\_Frame', 'D', 'CK', and 'FS' signals. At the bottom, outputs 'AI\_D', 'AI\_CK', 'AI\_FS', and 'AI\_MFS' exit to 'ODU2P\_AP'. A reference code 'G.798(17)-Amd.1(18)\_F14-29.2' is at the bottom right. + +**Figure 14-29.2 – ODU2P/ERS10G\_A\_So process** + +###### *Ethernet specific GFP-F source process:* + +The Ethernet frames are inserted into the client payload information field of the GFP-F frames according to clause 7.9.2 of [ITU-T G.7041]. + +The UPI values for frame-mapped Ethernet shall be inserted for data or ordered sets respectively (Table 6-3 of [ITU-T G.7041]). The rest of the fields except the UPI field in the type header are static as: + +- PTI = 000 (Client data) +- PFI = 0 (No FCS) +- EXI = 0000 (Null extension header) + +GFP client management frames (PTI = 100) are inserted if CI\_SSF is input and GFP pFCS generation is disabled (FCSEnable=false). + +###### *Common GFP source process:* + +See clause 8.5.3.1 of [ITU-T G.806]. GFP channel multiplexing is not supported (CMuxActive=false). + +###### *ODU2P specific GFP source process:* + +See clause 8.5.2.1 of [ITU-T G.806]. The GFP frames are mapped into the extended ODU2 payload area according to clause 17.4.1 of [ITU-T G.709]. OPU CSF may be generated if CI\_SSF is input. + +###### *ODU2P specific source process:* + +See clause 11.5.1.1 (k=2). + +**Defects:** None. + +##### **Consequent actions** + +The function shall perform the following consequent actions: + +aCSF-LOS $\leftarrow$ CI\_SSF and CSFEnable +aCSF-OPU $\leftarrow$ CI\_SSF and CSFEnable + +**Defect correlations:** None. + +**Performance monitoring:** For further study. + +#### 14.3.3.2 ODU2P to 10G Ethernet Reconciliation Sublayer adaptation sink function (ODU2P/ERS10G\_A\_Sk) + +The ODU2P/ERS10G\_A\_Sk extracts ERS10G\_CI information from the extended ODU2P payload area, delivering ERS10G\_CI to ERS10G\_TCP. It extracts the OPU2P overhead (PT and RES) and monitors the reception of the correct payload type. + +##### Symbol + +![Symbol diagram for ODU2P/ERS10G_A_Sk. A trapezoidal block labeled 'ODU2P/ERS10G' has an input arrow from below labeled 'ODU2P_AP', an output arrow from the top labeled 'ERS10G_CP', and a bidirectional input arrow from the right labeled 'ODU2P/ERS10G_A_Sk_MP'.](675b316a907e66765fd392b545e60854_img.jpg) + +Symbol diagram for ODU2P/ERS10G\_A\_Sk. A trapezoidal block labeled 'ODU2P/ERS10G' has an input arrow from below labeled 'ODU2P\_AP', an output arrow from the top labeled 'ERS10G\_CP', and a bidirectional input arrow from the right labeled 'ODU2P/ERS10G\_A\_Sk\_MP'. + +G.798(17)-Amd.1(18)\_F14-29.3 + +**Figure 14-29.3 – ODU2P/ERS10G\_A\_Sk symbol** + +##### Interfaces + +**Table 14-10.2 – ODU2P/ERS10G\_A\_Sk interfaces** + +| Inputs | Outputs | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODU2P_AP:
ODU2P_AI_D
ODU2P_AI_CK
ODU2P_AI_FS
ODU2P_AI_MFS
ODU2P_AI_TSF
ODU2P/ERS10G_A_Sk_MP:
ODU2P/ERS10G_A_Sk_MI_CSF_Reported | ERS10G_CP:
ERS10G_CI_D
ERS10G_CI_SSF
ODU2P/ERS10G_A_Sk_MP:
ODU2P/ERS10G_A_Sk_MI_AcPT
ODU2P/ERS10G_A_Sk_MI_AcEXI
ODU2P/ERS10G_A_Sk_MI_AcUPI
ODU2P/ERS10G_A_Sk_MI_cPLM
ODU2P/ERS10G_A_Sk_MI_cLFD
ODU2P/ERS10G_A_Sk_MI_cUPM
ODU2P/ERS10G_A_Sk_MI_cEXM
ODU2P/ERS10G_A_Sk_MI_cCSF | + +##### Processes + +A process diagram of this function is shown in Figure 14-29.4. + +![Figure 14-29.4 – ODU2P/ERS10G_A_Sk process diagram. The diagram shows a vertical stack of four process blocks within a grey container labeled 'ODU2P/ERS10G_A_Sk_MP'. From top to bottom: 'ERS10G specific GFP-F processes', 'Common GFP-F processes', 'ODU2P specific GFP-F processes', and 'ODU2P specific GFP-F processes'. Inputs from the bottom (ODU2P_AP) include AI_D, AI_CK, AI_FS, AI_MFS, and AI_TSF. The bottom block outputs D, CK, and FS to the block above. The third block outputs GFP_Frame/FS/SF to the second block. The second block has inputs FCSdiscard=false, CMuxConfig, and CMuxActive=false, and outputs cEXM and AcEXI. The top block outputs CI_D and CI_SSF to the top (ERS10G_CP) and has outputs AcUPI, cUPM, cCSF, and MI_CSF_Reported. A reference code G.798(17)-Amd.1(18)_F14-29.4 is at the bottom right.](10f4e3a2f3c016555ee12a5b556ba834_img.jpg) + +Figure 14-29.4 – ODU2P/ERS10G\_A\_Sk process diagram. The diagram shows a vertical stack of four process blocks within a grey container labeled 'ODU2P/ERS10G\_A\_Sk\_MP'. From top to bottom: 'ERS10G specific GFP-F processes', 'Common GFP-F processes', 'ODU2P specific GFP-F processes', and 'ODU2P specific GFP-F processes'. Inputs from the bottom (ODU2P\_AP) include AI\_D, AI\_CK, AI\_FS, AI\_MFS, and AI\_TSF. The bottom block outputs D, CK, and FS to the block above. The third block outputs GFP\_Frame/FS/SF to the second block. The second block has inputs FCSdiscard=false, CMuxConfig, and CMuxActive=false, and outputs cEXM and AcEXI. The top block outputs CI\_D and CI\_SSF to the top (ERS10G\_CP) and has outputs AcUPI, cUPM, cCSF, and MI\_CSF\_Reported. A reference code G.798(17)-Amd.1(18)\_F14-29.4 is at the bottom right. + +**Figure 14-29.4 – ODU2P/ERS10G\_A\_Sk process** + +###### *Ethernet specific GFP-F sink process:* + +The Ethernet frames are extracted from the client payload information field of the GFP-F frames according to clause 7.9 of [ITU-T G.7041]. + +See clause 8.5.4.1.2 of [ITU-T G.806]. GFP pFCS checking, GFP p\_FCSerror, p\_FDis are not supported (FCSdiscard=false). The UPI value for frame-mapped Ethernet shall be expected for data or ordered sets respectively (Table 6-3 of [ITU-T G.7041]). + +Client signal fail from GFP-F or OPU may generate LF as included ERS10G\_CI\_D. + +###### *Common GFP sink process:* + +See clause 8.5.3.2 of [ITU-T G.806]. GFP channel multiplexing is not supported (MI\_CMuxActive=false). + +###### *ODU2 specific GFP sink process:* + +See clause 8.5.2.2 of [ITU-T G.806]. The GFP frames are demapped from the extended ODU2 payload area according to clause 17.4.1 of [ITU-T G.709]. + +###### *ODU2P specific sink process:* + +See clause 11.5.1.2 (k=2). + +##### Defects + +dPLM – See clause 6.2.4.1 of [ITU-T G.798]. + +dLFD – See clause 6.2.5.2 of [ITU-T G.806]. + +dUPM – See clause 6.2.4.3 of [ITU-T G.806]. + +dEXM – See clause 6.2.4.4 of [ITU-T G.806]. + +dCSF-LOS – See clause 8.6.4.2 of [ITU-T G.8021]. + +dCSF-OPU – For further study. + +##### Consequent actions + +The function shall perform the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF or dPLM or dLFD or dUPM or dEXM or dCSF-LOS + +##### Defect correlations + +The function shall perform the following defect correlations to determine the most probable fault cause (see clause 6.4 of [ITU-T G.806]). This fault cause shall be reported to the EMF. + +cPLM $\leftarrow$ dPLM and (not AI\_TSF) + +cLFD $\leftarrow$ dLFD and (not dPLM) and (not AI\_TSF) + +cUPM $\leftarrow$ dUPM and (not dEXM) and (not dPLM) and (not dLFD) and (not AI\_TSF) + +cEXM $\leftarrow$ dEXM and (not dPLM) and (not dLFD) and (not AI\_TSF) + +cCSF $\leftarrow$ (dCSF-LOS or dCSF-OPU) and (not dEXM) and (not dUPM) and (not dPLM) and (not dLFD) and (not AI\_TSF) and CSF\_Reported. + +##### Performance monitoring + +For further study. + +### 14.3.4 ODUP to NULL adaptation function (ODUP/NULL\_A) + +The ODUP to NULL adaptation functions perform the adaptation of a NULL test signal as defined in clause 17.5.1 of [ITU-T G.709] into the ODUP. The NULL signal is an all-ZEROs pattern. + +#### 14.3.4.1 ODUP to NULL adaptation source function (ODUP/NULL\_A\_So) + +The ODUP/NULL\_A\_So function creates the ODU signal from a free-running clock. It maps the NULL signal into the payload of the OPU, adds OPU overhead (RES, PT) and default ODU overhead. + +The information flow and processing of the ODUP/NULL\_A\_So function is defined with reference to Figures 14-30 and 14-31. + +##### Symbol + +![Diagram of the ODUP/NULL_A_So function symbol. It shows two identical trapezoidal blocks. The left block has an input 'ODUKP/NULL_A_So_MP' entering from the left and an output 'ODUKP_AP' exiting from the bottom. A label 'k = 0, 1, 2, 2e, 3, 4, flex' is next to the output arrow. The right block has an input 'ODUCnP/NULL_A_So_MP' entering from the left and an output 'ODUCnP_AP' exiting from the bottom. A label 'G.798(17)_F14-30' is next to the output arrow.](26c5c426f93cf66d35d87228668dac68_img.jpg) + +The diagram illustrates the symbol for the ODUP/NULL\_A\_So function. It consists of two trapezoidal blocks. The left block is labeled 'ODUKP/NULL' and has an input 'ODUKP/NULL\_A\_So\_MP' entering from the left and an output 'ODUKP\_AP' exiting from the bottom. A label 'k = 0, 1, 2, 2e, 3, 4, flex' is next to the output arrow. The right block is labeled 'ODUCnP/NULL' and has an input 'ODUCnP/NULL\_A\_So\_MP' entering from the left and an output 'ODUCnP\_AP' exiting from the bottom. A label 'G.798(17)\_F14-30' is next to the output arrow. + +Diagram of the ODUP/NULL\_A\_So function symbol. It shows two identical trapezoidal blocks. The left block has an input 'ODUKP/NULL\_A\_So\_MP' entering from the left and an output 'ODUKP\_AP' exiting from the bottom. A label 'k = 0, 1, 2, 2e, 3, 4, flex' is next to the output arrow. The right block has an input 'ODUCnP/NULL\_A\_So\_MP' entering from the left and an output 'ODUCnP\_AP' exiting from the bottom. A label 'G.798(17)\_F14-30' is next to the output arrow. + +Figure 14-30 – ODUP/NULL\_A\_So function + +##### Interfaces + +**Table 14-11 – ODUP/NULL\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------| +| ODUP/NULL_A_So_MP:
ODUP/NULL_A_So_MI_Nominal_Bitrate_and_Tolerance | ODUP_AP:
ODUP_AI_CK
ODUP_AI_D
ODUP_AI_FS
ODUP_AI_MFS | + +##### Processes + +**Clock and (multi)frame start signal generation:** The function shall generate a local ODU clock (ODUP\_AI\_CK) with a clock frequency within the minimum to maximum values of the specified ODU signal as given in Table 7-2 of [ITU-T G.709] and provisioned by the MI\_Nominal\_Bitrate\_and\_Tolerance from a free-running oscillator. The jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODU signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +**Insert NULL signal:** The function shall insert an all-ZEROs pattern into the OPU payload area as defined in clause 17.5.1 of [ITU-T G.709]. + +**PT:** The function shall insert code "1111 1101" into the PT byte position of the PSI overhead as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**RES:** The function shall insert all-ZEROs into the RES bytes. + +All other bits of the ODUk overhead should be sourced as "0"s, except the ODU-PM STAT field which should be set to the value "normal path signal" (001). + +![Block diagram of ODUP/NULL_A_So processes. The diagram shows the internal logic for generating various signals. A 'Free-running clock generator (ODCa)' takes 'MI_Nominal_Bitrate_and_Tolerance' as input and outputs 'CK'. 'CK' is divided by 122368 to produce 'FS' and by 256 to produce 'MFS'. 'FS' and 'MFS' are used to control an 'Insert NULL signal' block and an 'ODUk OH is set to all-0's, except PM STAT = 001' block. These blocks also output 'AI_D'. The 'Insert NULL signal' block also outputs 'Payload type (PT)' and 'RES'. All these signals (AI_D, AI_MFS, AI_FS, AI_CK) are grouped under the label 'ODUP_AP'.](2576306a75b1ca6180aa172236c1ca07_img.jpg) + +The diagram illustrates the internal processes of the ODUP/NULL\_A\_So function. At the top right, a 'Free-running clock generator (ODCa)' receives 'MI\_Nominal\_Bitrate\_and\_Tolerance' and outputs a clock signal 'CK'. This 'CK' signal is fed into two frequency dividers: one labeled '1/122368' which outputs 'FS', and another labeled '1/256' which outputs 'MFS'. The 'FS' and 'MFS' signals are connected to an 'Insert NULL signal' block and an 'ODUk OH is set to all-0's, except PM STAT = 001' block. These blocks output 'AI\_D', 'Payload type (PT)', and 'RES' signals. The 'AI\_D', 'AI\_MFS', 'AI\_FS', and 'AI\_CK' signals are grouped together at the bottom under the label 'ODUP\_AP'. The diagram is labeled 'G.798(17)\_F14-31' and has a vertical label 'ODUP/NULL\_A\_So\_MP' on the right side. + +Block diagram of ODUP/NULL\_A\_So processes. The diagram shows the internal logic for generating various signals. A 'Free-running clock generator (ODCa)' takes 'MI\_Nominal\_Bitrate\_and\_Tolerance' as input and outputs 'CK'. 'CK' is divided by 122368 to produce 'FS' and by 256 to produce 'MFS'. 'FS' and 'MFS' are used to control an 'Insert NULL signal' block and an 'ODUk OH is set to all-0's, except PM STAT = 001' block. These blocks also output 'AI\_D'. The 'Insert NULL signal' block also outputs 'Payload type (PT)' and 'RES'. All these signals (AI\_D, AI\_MFS, AI\_FS, AI\_CK) are grouped under the label 'ODUP\_AP'. + +**Figure 14-31 – ODUP/NULL\_A\_So processes** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.3.4.2 ODUP to NULL adaptation sink function (ODUP/NULL\_A\_Sk) + +The ODUP/NULL\_A\_Sk extracts the OPU overhead (PT and RES) and monitors the reception of the correct payload type. + +The information flow and processing of the ODUP/NULL\_A\_Sk function is defined with reference to Figures 14-32 and 14-33. + +##### Symbol + +![Diagram of ODUP/NULL_A_Sk function symbols. Two trapezoidal blocks represent the functions. The left block is labeled 'ODUKP/NULL' and has an input 'ODUKP_AP' from below and an output 'ODUKP/NULL_A_Sk_MP' to the left. Above the input is 'k = 0, 1, 2, 2e, 3, 4, flex'. The right block is labeled 'ODUCnP/NULL' and has an input 'ODUCnP_AP' from below and an output 'ODUCnP/NULL_A_Sk_MP' to the left. Below the right block is the text 'G.798(17)_F14-32'.](f98ddc2253ad41b4130f6042e77f1460_img.jpg) + +Diagram illustrating the ODUP/NULL\_A\_Sk function symbols. The left symbol shows the ODUkP/NULL function with input ODUkP\_AP and output ODUkP/NULL\_A\_Sk\_MP. The right symbol shows the ODUCnP/NULL function with input ODUCnP\_AP and output ODUCnP/NULL\_A\_Sk\_MP. The parameter k is defined as 0, 1, 2, 2e, 3, 4, flex. + +Diagram of ODUP/NULL\_A\_Sk function symbols. Two trapezoidal blocks represent the functions. The left block is labeled 'ODUKP/NULL' and has an input 'ODUKP\_AP' from below and an output 'ODUKP/NULL\_A\_Sk\_MP' to the left. Above the input is 'k = 0, 1, 2, 2e, 3, 4, flex'. The right block is labeled 'ODUCnP/NULL' and has an input 'ODUCnP\_AP' from below and an output 'ODUCnP/NULL\_A\_Sk\_MP' to the left. Below the right block is the text 'G.798(17)\_F14-32'. + +**Figure 14-32 – ODUP/NULL\_A\_Sk function** + +##### Interfaces + +**Table 14-12 – ODUP/NULL\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| ODUP_AP:
ODUP_AI_CK
ODUP_AI_D
ODUP_AI_FS
ODUP_AI_MFS
ODUP_AI_TSF | ODUP/NULL_A_Sk_MP:
ODUP/NULL_A_Sk_MI_cPLM
ODUP/NULL_A_Sk_MI_AcPT | + +##### Processes + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. + +**RES:** The value in the RES bytes shall be ignored. + +**Payload:** The value in the OPU payload area shall be ignored. + +![Figure 14-33: ODUP/NULL_A_Sk processes diagram. The diagram shows a block diagram of the ODUP/NULL_A_Sk processes. Inputs AI_D, AI_CK, AI_FS, and AI_MFS are grouped under the label ODUP_AP. These inputs feed into a block labeled 'Extract PT'. The output of 'Extract PT' feeds into a block labeled 'PT process'. The 'PT process' block also receives AI_TSF as an input. The output of 'PT process' is labeled MI_AcPT. The 'PT process' block also feeds into a block labeled 'Defect correlations'. This block also receives AI_TSF and dPLM as inputs. The output of 'Defect correlations' is labeled MI_cPLM. The entire process is labeled ODUP/NULL_A_Sk_MP on the right side. The reference G.798(17)_F14-33 is shown at the bottom right of the diagram.](6762c05f927b2b9c2404c465ef0a8d01_img.jpg) + +Figure 14-33: ODUP/NULL\_A\_Sk processes diagram. The diagram shows a block diagram of the ODUP/NULL\_A\_Sk processes. Inputs AI\_D, AI\_CK, AI\_FS, and AI\_MFS are grouped under the label ODUP\_AP. These inputs feed into a block labeled 'Extract PT'. The output of 'Extract PT' feeds into a block labeled 'PT process'. The 'PT process' block also receives AI\_TSF as an input. The output of 'PT process' is labeled MI\_AcPT. The 'PT process' block also feeds into a block labeled 'Defect correlations'. This block also receives AI\_TSF and dPLM as inputs. The output of 'Defect correlations' is labeled MI\_cPLM. The entire process is labeled ODUP/NULL\_A\_Sk\_MP on the right side. The reference G.798(17)\_F14-33 is shown at the bottom right of the diagram. + +**Figure 14-33 – ODUP/NULL\_A\_Sk processes** + +##### Defects + +The function shall detect dPLM. + +**dPLM:** See clause 6.2.4.1. The expected payload type is "1111 1101" (NULL test signal mapping) as defined in [ITU-T G.709]. + +**Consequent actions:** None. + +##### Defect correlations + +cPLM $\leftarrow$ dPLM and (not AI\_TSF) + +**Performance monitoring:** None. + +### 14.3.5 ODUP to PRBS adaptation function (ODUP/PRBS\_A) + +The ODUP to PRBS adaptation functions perform the adaptation of a PRBS test signal as defined in clause 17.5.2 of [ITU-T G.709] into the ODUP. The PRBS signal is a $2^{31} - 1$ pseudo-random test sequence as specified in clause 5.8 of [ITU-T O.150]. + +#### 14.3.5.1 ODUP to PRBS adaptation source function (ODUP/PRBS\_A\_So) + +The ODUP/PRBS\_A\_So function creates the ODUP signal from a free-running clock. It maps the PRBS signal into the payload of the OPU, adds OPU overhead (RES, PT) and default ODU overhead. + +The information flow and processing of the ODUP/PRBS\_A\_So function is defined with reference to Figures 14-34 and 14-35. + +##### Symbol + +![Figure 14-34: ODUP/PRBS_A_So function diagram. The diagram shows two symbols for the ODUP/PRBS_A_So function. The left symbol is labeled ODUP/PRBS and takes an input ODUP/PRBS_A_So_MP. It has an output labeled ODUP/AP. Below the output, there is a list of values for k: k = 0, 1, 2, 2c, 3, 4, flex. The right symbol is labeled ODUCn/PRBS and takes an input ODUCn/PRBS_A_So_MP. It has an output labeled ODUCn/AP. Below the output, there is a reference G.798(17)-Amd.4(22)_F14-34.](9271a5ab5252d6176287e699f600d2fb_img.jpg) + +Figure 14-34: ODUP/PRBS\_A\_So function diagram. The diagram shows two symbols for the ODUP/PRBS\_A\_So function. The left symbol is labeled ODUP/PRBS and takes an input ODUP/PRBS\_A\_So\_MP. It has an output labeled ODUP/AP. Below the output, there is a list of values for k: k = 0, 1, 2, 2c, 3, 4, flex. The right symbol is labeled ODUCn/PRBS and takes an input ODUCn/PRBS\_A\_So\_MP. It has an output labeled ODUCn/AP. Below the output, there is a reference G.798(17)-Amd.4(22)\_F14-34. + +**Figure 14-34 – ODUP/PRBS\_A\_So function** + +##### Interfaces + +**Table 14-13 – ODUP/PRBS\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------| +| ODUP/PRBS_A_So_MP:
ODUP/PRBS_A_So_MI_Nominal_Bitrate_and_Tolerance | ODUP_AP:
ODUP_AI_CK
ODUP_AI_D
ODUP_AI_FS
ODUP_AI_MFS | + +##### Processes + +**Clock and (multi)frame start signal generation:** The function shall generate a local ODU clock with a clock frequency within the minimum to maximum values of the specified ODU signal as given in Table 7-2 of [ITU-T G.709] provisioned by the MI\_Nominal\_Bitrate\_and\_Tolerance from a free-running oscillator. The jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODU signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +**Generate and insert PRBS signal:** The function shall generate the PRBS signal and insert it into the OPU payload area as defined in clause 17.5.2 of [ITU-T G.709]. Each OPU instance contains one PRBS signal. + +**PT:** The function shall insert code "1111 1110" into the PT byte position of the PSI overhead as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**RES:** The function shall insert all-ZEROs into the RES bytes. + +All other bits of the ODU overhead should be sourced as "0"s, except the ODU-PM STAT field which should be set to the value "normal path signal" (001). + +![Block diagram of ODUP/PRBS_A_So processes. A 'Free-running clock generator (ODCa)' receives 'MI_Nominal_Bitrate_and_Tolerance' and outputs 'CK'. 'CK' is input to 'Generate and insert PRBS signal', 'Payload type (PT)', 'RES', and 'ODUk OH is set to all-0's, except PM STAT = 001'. 'Generate and insert PRBS signal' outputs 'AI_D'. 'Payload type (PT)', 'RES', and 'ODUk OH is set to all-0's, except PM STAT = 001' are inputs to a '1/122368' divider. The '1/122368' divider outputs 'FS' to 'AI_FS' and 'AI_MFS'. 'AI_FS' and 'AI_MFS' are inputs to a '1/256' divider. The '1/256' divider outputs 'MFS' to 'AI_MFS'. The outputs 'AI_D', 'AI_MFS', 'AI_FS', and 'AI_CK' are grouped as 'ODUP_AP'. The diagram is labeled 'G.798(17)_F14-35' and 'ODUP/PRBS_A_So_MP'.](b55656f01d98097862b9e6d8461ec59b_img.jpg) + +Block diagram of ODUP/PRBS\_A\_So processes. A 'Free-running clock generator (ODCa)' receives 'MI\_Nominal\_Bitrate\_and\_Tolerance' and outputs 'CK'. 'CK' is input to 'Generate and insert PRBS signal', 'Payload type (PT)', 'RES', and 'ODUk OH is set to all-0's, except PM STAT = 001'. 'Generate and insert PRBS signal' outputs 'AI\_D'. 'Payload type (PT)', 'RES', and 'ODUk OH is set to all-0's, except PM STAT = 001' are inputs to a '1/122368' divider. The '1/122368' divider outputs 'FS' to 'AI\_FS' and 'AI\_MFS'. 'AI\_FS' and 'AI\_MFS' are inputs to a '1/256' divider. The '1/256' divider outputs 'MFS' to 'AI\_MFS'. The outputs 'AI\_D', 'AI\_MFS', 'AI\_FS', and 'AI\_CK' are grouped as 'ODUP\_AP'. The diagram is labeled 'G.798(17)\_F14-35' and 'ODUP/PRBS\_A\_So\_MP'. + +**Figure 14-35 – ODUP/PRBS\_A\_So processes** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.3.5.2 ODUP to PRBS adaptation sink function (ODUP/PRBS\_A\_Sk) + +The ODUP/PRBS\_A\_Sk recovers the PRBS test signal from the OPU payload area and monitors test sequence errors (TSEs) in the PRBS sequence. It extracts the OPU overhead (PT and RES) and monitors the reception of the correct payload type. + +The information flow and processing of the ODUP/PRBS\_A\_Sk function is defined with reference to Figures 14-36 and 14-37. + +##### Symbol + +![Diagram of ODUP/PRBS_A_Sk function symbols. Two trapezoidal blocks represent the function. The left block is labeled 'ODUPkP/PRBS' and has an input 'ODUPkP_AP' from below (with 'k = 0, 1, 2, 2e, 3, 4, flex') and an output 'ODUPkP/PRBS_A_Sk_MP' to the left. The right block is labeled 'ODUPnP/PRBS' and has an input 'ODUPnP_AP' from below and an output 'ODUPnP/PRBS_A_Sk_MP' to the left. A reference code 'G.798(17)_F14-36' is at the bottom right.](09cac7f879d0ec76600a5aeae680b95b_img.jpg) + +Diagram illustrating the ODUP/PRBS\_A\_Sk function symbols. Two trapezoidal blocks represent the function. The left block is labeled "ODUPkP/PRBS" and has an input "ODUPkP\_AP" from below (with "k = 0, 1, 2, 2e, 3, 4, flex") and an output "ODUPkP/PRBS\_A\_Sk\_MP" to the left. The right block is labeled "ODUPnP/PRBS" and has an input "ODUPnP\_AP" from below and an output "ODUPnP/PRBS\_A\_Sk\_MP" to the left. A reference code "G.798(17)\_F14-36" is at the bottom right. + +Diagram of ODUP/PRBS\_A\_Sk function symbols. Two trapezoidal blocks represent the function. The left block is labeled 'ODUPkP/PRBS' and has an input 'ODUPkP\_AP' from below (with 'k = 0, 1, 2, 2e, 3, 4, flex') and an output 'ODUPkP/PRBS\_A\_Sk\_MP' to the left. The right block is labeled 'ODUPnP/PRBS' and has an input 'ODUPnP\_AP' from below and an output 'ODUPnP/PRBS\_A\_Sk\_MP' to the left. A reference code 'G.798(17)\_F14-36' is at the bottom right. + +**Figure 14-36 – ODUP/PRBS\_A\_Sk function** + +##### Interfaces + +**Table 14-14 – ODUP/PRBS\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| ODUP_AP:
ODUP_AI_CK
ODUP_AI_D
ODUP_AI_FS
ODUP_AI_TSF
ODUP/PRBS_A_Sk_MP:
ODUP/PRBS_A_Sk_MI_1second | ODUP/PRBS_A_Sk_MP:
ODUP/PRBS_A_Sk_MI_cPLM
ODUP/PRBS_A_Sk_MI_AcPT
ODUP/PRBS_A_Sk_MI_cLSS
ODUP/PRBS_A_Sk_MI_pN_TSE | + +##### Processes + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. + +**RES:** The value in the RES bytes shall be ignored. + +**TSE check:** Test sequence errors (TSEs) are bit errors in the PRBS data stream extracted from each of the OPU payload instances and shall be detected whenever the PRBS detector is in lock and the received data bit does not match the expected value. + +![Figure 14-37 – ODUP/PRBS_A_Sk processes. This block diagram illustrates the internal components and signal flow of the ODUP/PRBS_A_Sk function. On the left, a 'TSE check' block receives inputs from 'AI_D', 'AI_CK', 'AI_FS', and 'AI_MFS' (grouped as 'ODUP_AP'). It outputs 'nTSE' to a 'Performance monitoring' block and 'dLSS' to a 'Defect correlations' block. Below the TSE check, an 'Extract PT' block receives the same 'ODUP_AP' inputs and outputs to a 'PT process' block. The 'PT process' block outputs 'AI_TSF' to the 'Defect correlations' block and 'MI_AcPT' to the right. The 'Performance monitoring' block outputs 'MI_1second' and 'MI_pN_TSE' to the right. The 'Defect correlations' block outputs 'MI_cLSS' and 'MI_cPLM' to the right. All output signals ('MI_1second', 'MI_pN_TSE', 'MI_cLSS', 'MI_cPLM', 'MI_AcPT') are grouped under the label 'ODUP/PRBS_A_Sk_MP'. A bracket at the bottom groups 'AI_D', 'AI_CK', 'AI_FS', 'AI_MFS', and 'AI_TSF' under the label 'ODUP_AP'. The diagram is labeled 'G.798(17)_F14-37'.](2fa686ed8033ac35efddee0c7be47d59_img.jpg) + +Figure 14-37 – ODUP/PRBS\_A\_Sk processes. This block diagram illustrates the internal components and signal flow of the ODUP/PRBS\_A\_Sk function. On the left, a 'TSE check' block receives inputs from 'AI\_D', 'AI\_CK', 'AI\_FS', and 'AI\_MFS' (grouped as 'ODUP\_AP'). It outputs 'nTSE' to a 'Performance monitoring' block and 'dLSS' to a 'Defect correlations' block. Below the TSE check, an 'Extract PT' block receives the same 'ODUP\_AP' inputs and outputs to a 'PT process' block. The 'PT process' block outputs 'AI\_TSF' to the 'Defect correlations' block and 'MI\_AcPT' to the right. The 'Performance monitoring' block outputs 'MI\_1second' and 'MI\_pN\_TSE' to the right. The 'Defect correlations' block outputs 'MI\_cLSS' and 'MI\_cPLM' to the right. All output signals ('MI\_1second', 'MI\_pN\_TSE', 'MI\_cLSS', 'MI\_cPLM', 'MI\_AcPT') are grouped under the label 'ODUP/PRBS\_A\_Sk\_MP'. A bracket at the bottom groups 'AI\_D', 'AI\_CK', 'AI\_FS', 'AI\_MFS', and 'AI\_TSF' under the label 'ODUP\_AP'. The diagram is labeled 'G.798(17)\_F14-37'. + +**Figure 14-37 – ODUP/PRBS\_A\_Sk processes** + +##### Defects + +The function shall detect dPLM and dLSS. + +**dPLM:** See clause 6.2.4.1. The expected payload type is "1111 1110" (PRBS test signal mapping) as defined in [ITU-T G.709]. + +**dLSS:** The function shall detect the loss of PRBS lock (dLSS) according to the criteria defined in clause 2.6 of [ITU-T O.151]. + +**Consequent actions:** None. + +##### Defect correlations + +cPLM $\leftarrow$ dPLM and (not AI\_TSF) + +cLSS $\leftarrow$ dLSS and (not AI\_TSF) and (not dPLM) + +##### Performance monitoring + +pN\_TSE $\leftarrow$ Sum of test sequence errors (TSEs) within one second period. + +### 14.3.6 ODUkP to RSn adaptation function (ODUkP/RSn\_A) + +The ODUkP to RSn adaptation functions perform the adaptation between the ODUkP ( $k = 1, 2, 3$ ) layer adapted information and the characteristic information of a RSn signal ( $n = 16, 64, 256$ ). + +Two different source functions are defined. The ODUkP/RSn-a\_A\_So provides asynchronous mapping, while the ODUkP/RSn-b\_A\_So provides bit synchronous mapping. In the sink direction, the ODUkP/RSn\_A\_Sk can handle both (bit synchronous and asynchronous) mappings. + +NOTE 1 – The source functions are identical with the ODUkP/CBRx adaptation source functions, except for the different CI at the CP (CBRx\_CI replaced by RSn\_CI). In the sink direction, the function provides framing on the SDH signal and generic AIS supervision. In the ODUkP/CBR\_A\_Sk function, no such functionality is available. + +NOTE 2 – The ODUkP/RSn\_A functions are only intended to be used together with RSn\_TT functions (see [ITU-T G.783]). The direct interconnection of ODUkP/RSn\_A functions with any other (server layer)/RS\_A functions at the RSn\_CP is not intended. The ODUkP/RSn functions are only used if further SDH processing is performed (e.g., RS termination). For example, Figure I.1 shows the ODUkP/RSn\_A\_Sk together with a RS\_TT\_Sk for non-intrusive monitoring, and Figure I.4 shows the use of the ODUkP/RSn\_A functions at OTN interfaces on SDH equipment. For transparent mapping of constant bit-rate signals, the ODUkP/CBRx\_A functions shall be used as shown in Figure I.1. + +#### 14.3.6.1 ODUkP to RSn asynchronous mapping adaptation source function (ODUkP/RSn-a\_A\_So) + +The ODUkP/RSn-a\_A\_So function creates the ODUk signal from a free-running clock. It asynchronously maps the STM-N ( $N = 4^{(k+1)}$ ) client signal from the RSn\_CP into the payload of the OPUk ( $k = 1, 2, 3$ ), adds OPUk overhead (RES, PT, JC) and default ODUk overhead. + +The information flow and processing of the ODUkP/RSn-a\_A\_So function is defined with reference to Figures 14-38 and 14-39. + +##### Symbol + +![Diagram of the ODUkP/RSn-a_A_So function symbol. An input arrow labeled 'RSn_CP' points to a trapezoidal block labeled 'ODUkP/RSn-a'. Above the input arrow is the parameter 'n = 16, 64, 256'. Below the block is an output arrow labeled 'ODUkP_AP'. To the right of the output arrow is the parameter 'k = 1, 2, 3'. At the bottom right of the diagram is the text 'G.798(17)_F14-38'.](c5945ab1332e6611e9e4d64bafdc3455_img.jpg) + +Diagram of the ODUkP/RSn-a\_A\_So function symbol. An input arrow labeled 'RSn\_CP' points to a trapezoidal block labeled 'ODUkP/RSn-a'. Above the input arrow is the parameter 'n = 16, 64, 256'. Below the block is an output arrow labeled 'ODUkP\_AP'. To the right of the output arrow is the parameter 'k = 1, 2, 3'. At the bottom right of the diagram is the text 'G.798(17)\_F14-38'. + +Figure 14-38 – ODUkP/RSn-a\_A\_So function + +##### Interfaces + +Table 14-15 – ODUkP/RSn-a\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|-----------------------------------------|------------------------------------------------------------------------------| +| RSn_CP:
RSn_CI_CK
RSn_CI_D | ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_MFS | + +##### Processes + +**Clock and (multi)frame start signal generation:** The function shall generate a local ODUk clock (ODUkP\_AI\_CK) of " $239/(239 - k) \times 4^{(k-1)} \times 2\,488\,320\text{ kHz} \pm 20\text{ ppm}$ " from a free-running oscillator. The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUk signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +**Mapping, frequency justification and bit-rate adaptation:** The function shall provide an elastic store (buffer) process. The data signal RSn\_CI shall be written into the buffer under the control of the associated input clock. The data shall be read out of the buffer and written onto the D and N/PJO bytes in the OPUk frame under the control of the ODUk clock and justification decisions as defined in clause 17.2 of [ITU-T G.709]. + +A justification decision shall be performed each frame. Each justification decision results in a corresponding positive, negative or no justification action. Upon a positive justification action, the reading of one data byte out of the buffer shall be cancelled once. No RSn data shall be written onto the PJO and NJO bytes. Upon a negative justification action, one extra data byte shall be read once out of the buffer. RSn data shall be written onto the PJO and NJO bytes. If neither a positive nor a + +negative justification action is to be performed, RSn data shall be written onto the PJO byte and no RSn data shall be written onto the NJO byte. + +The justification decisions determine the phase error introduced by the function. + +**Buffer size:** In the presence of jitter as specified by [ITU-T G.825] and a frequency within the range $4^{(k-1)} \times 2\,488\,320\text{ kHz} \pm 20\text{ ppm}$ , this mapping process shall not introduce any errors. The maximum buffer hysteresis, and therefore the maximum phase error introduced, shall be as listed in Table 14-7. + +**JC bits:** The function shall generate the justification control (JC) bits based on the justification decision performed in the current frame according to the specification in clause 17.2 of [ITU-T G.709]. It shall insert the justification control bits in the appropriate JC bit positions in the JC bytes of the current frame. + +**PT:** The function shall insert code "0000 0010" into the PT byte position of the PSI overhead as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**RES:** The function shall insert all-ZEROs into the RES bytes and reserved bits within the JC bytes. + +All other bits of the ODUk overhead should be sourced as "0"s, except the PMOH STAT field which should be set to the value "normal path signal" (001). + +![Block diagram of ODUkP/RSn-a_A_So processes. The diagram shows the mapping of RSn_CP data into ODUkP_AP. Inputs include CI_D, CI_CK, and RSn_CP. CI_D and CI_CK enter an Elastic store. RSn_CP enters a Justification control and JC generation block. The Elastic store outputs WR and RD signals to the Justification control. The Justification control outputs JC bits to the Elastic store and AI_D, AI_CK, AI_FS, and AI_MFS signals to the ODUkP_AP. A Free-running clock generator (ODCa) provides CK to a 1/122368 divider, which outputs FS to a 1/256 divider, which outputs MFS to the ODUkP_AP. The ODUkP_AP also includes Insert PT, Insert RES, and a block stating 'ODUk OH is set to all-0's, except PM STAT = 001'.](9c12d7993e786817c8c569e6f2d5a0a9_img.jpg) + +The diagram illustrates the ODUkP/RSn-a\_A\_So processes. At the top, the RSn\_CP input is shown. On the left, CI\_D and CI\_CK inputs enter an Elastic store. The Elastic store has write (WR) and read (RD) ports. The WR port is connected to the Justification control and JC generation block, which also receives the RSn\_CP input. The RD port is connected to the Justification control. The Justification control outputs JC bits back to the Elastic store and also outputs AI\_D, AI\_CK, AI\_FS, and AI\_MFS signals to the ODUkP\_AP. A Free-running clock generator (ODCa) provides a clock (CK) to a 1/122368 divider, which outputs a frequency signal (FS) to a 1/256 divider, which in turn outputs a multi-frequency signal (MFS) to the ODUkP\_AP. The ODUkP\_AP block includes functions for Insert PT, Insert RES, and setting the ODUk OH to all-0's, except for the PM STAT field which is set to 001. + +Block diagram of ODUkP/RSn-a\_A\_So processes. The diagram shows the mapping of RSn\_CP data into ODUkP\_AP. Inputs include CI\_D, CI\_CK, and RSn\_CP. CI\_D and CI\_CK enter an Elastic store. RSn\_CP enters a Justification control and JC generation block. The Elastic store outputs WR and RD signals to the Justification control. The Justification control outputs JC bits to the Elastic store and AI\_D, AI\_CK, AI\_FS, and AI\_MFS signals to the ODUkP\_AP. A Free-running clock generator (ODCa) provides CK to a 1/122368 divider, which outputs FS to a 1/256 divider, which outputs MFS to the ODUkP\_AP. The ODUkP\_AP also includes Insert PT, Insert RES, and a block stating 'ODUk OH is set to all-0's, except PM STAT = 001'. + +Figure 14-39 – ODUkP/RSn-a\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 14.3.6.2 ODUkP to RSn bit synchronous mapping adaptation source function (ODUkP/RSn-b\_A\_So) + +The ODUkP/RSn-b\_A\_So function creates the ODUk signal from a clock, derived from the incoming RSn\_CI clock. It bit synchronously maps the STM-N ( $N = 4^{(k+1)}$ ) client signal from the RSn\_CP into the payload of the OPUk, adds OPUk overhead (PT, JC, RES) and default ODUk overhead. + +The information flow and processing of the ODUkP/RSn-b\_A\_So function is defined with reference to Figures 14-40 and 14-41. + +#### Symbol + +![Symbol diagram for the ODUkP/RSn-b_A_So function. It shows an input RSn_CP entering a trapezoidal block labeled 'ODUkP/RSn-b'. Above the input arrow, 'n = 16, 64, 256' is specified. Below the output arrow, 'k = 1, 2, 3' is specified. The output is labeled ODUkP_AP. At the bottom right of the block, the reference 'G.798(17)_F14-40' is shown.](f79cb254efa2e37d7facb055cf90086e_img.jpg) + +Symbol diagram for the ODUkP/RSn-b\_A\_So function. It shows an input RSn\_CP entering a trapezoidal block labeled 'ODUkP/RSn-b'. Above the input arrow, 'n = 16, 64, 256' is specified. Below the output arrow, 'k = 1, 2, 3' is specified. The output is labeled ODUkP\_AP. At the bottom right of the block, the reference 'G.798(17)\_F14-40' is shown. + +Figure 14-40 – ODUkP/RSn-b\_A\_So function + +#### Interfaces + +Table 14-16 – ODUkP/RSn-b\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|-----------------------------------------|------------------------------------------------------------------------------| +| RSn_CP:
RSn_CI_CK
RSn_CI_D | ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_MFS | + +#### Processes + +**Clock and (multi)frame start signal generation:** The function shall generate the ODUk (AI\_CK) clock by multiplying the incoming RSn clock (CI\_CK) by a factor of $239/(239 - k)$ . The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCb clock), apply. + +NOTE 1 – The ODUk clock is $"239/(239 - k) \times 4^{(k-1)} \times 2\,488\,320\text{ kHz} \pm 20\text{ ppm}"$ . + +NOTE 2 – The incoming RSn CK (CI\_CK) signal has to be within the range of $4^{(k-1)} \times 2\,488\,320\text{ kHz} \pm 20\text{ ppm}$ . + +During failure conditions of the incoming RS clock signal (CI\_CK), the ODUk clock shall stay within its limits as defined in [ITU-T G.8251] and no frame phase discontinuity shall be introduced. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUk signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +**Mapping, frequency justification and bit-rate adaptation:** The function shall provide an elastic store (buffer) process. The data signal RSn\_CI shall be written into the buffer under the control of the associated input clock. The data shall be read out of the buffer and written onto the D and PJO bytes in the OPUk frame under the control of the ODUk clock, as defined in clause 17.2 of [ITU-T G.709]. + +Neither negative nor positive justification is to be performed. No data shall be written onto the NJO byte and data shall always be written onto the PJO byte. + +**Buffer size:** In the presence of jitter as specified by [ITU-T G.825] and a frequency within the range $4^{(k-1)} \times 2\,488\,320\text{ kHz} \pm 20\text{ ppm}$ , this mapping process shall not introduce any errors. + +Following a step in frequency of the $4^{(k-1)} \times 2\,488\,320\text{ kbit/s}$ CI\_CK signal (for example, due to the removal of AIS (RS-AIS)), there will be a maximum recovery time of X seconds after which this process shall not generate any bit errors. The value of X is for further study; a value of one second has been proposed. + +**JC bits:** The function shall generate the fixed justification control (JC) bits "00" according to clause 17.2 of [ITU-T G.709]. It shall insert the justification control bits in the appropriate JC bit positions in the JC bytes. + +**RES:** The function shall insert all-ZEROs into the RES bytes and reserved bits within the JC bytes. + +**PT:** The function shall insert code "0000 0011" into the PT byte position of the PSI overhead as defined in clause 15.9.2.1 of [ITU-T G.709]. + +All other bits of the ODUk overhead should be sourced as "0"s, except the PMOH STAT field which should be set to the value "normal path signal" (001). + +![Figure 14-41 – ODUkP/RSn-b_A_So processes. This block diagram illustrates the mapping process from client signals to ODUkP overhead. At the top, CI_D and CI_CK signals enter an 'Elastic store' block. CI_CK also feeds into an 'ODU clock generator locked to CBRx clock (ODCb)'. The Elastic store has 'WR' (write) and 'RD' (read) ports. The 'RD' port output goes to an 'AI_D' output and also through a series of blocks: 'Justification control' (receiving 'JC' input), 'Insert PT', 'Insert RES', and 'ODUk OH is set to all-0's, except PM STAT = 001'. The 'Justification control' block also receives 'CK' from the ODU clock generator and sends 'JC' to the Elastic store. The 'ODU clock generator' also feeds into a frequency divider '1/122368', which outputs 'FS'. 'FS' feeds into another frequency divider '1/256', which outputs 'MFS'. 'CK', 'FS', and 'MFS' all feed into the 'AI_CK', 'AI_FS', and 'AI_MFS' outputs respectively. The entire process is labeled 'RSn_CP' at the top and 'ODUkP_AP' at the bottom. A reference code 'G.798(17)-Amd.3(21)_F14-41' is in the bottom right.](0697b56d281df40b93c568be995cb884_img.jpg) + +Figure 14-41 – ODUkP/RSn-b\_A\_So processes. This block diagram illustrates the mapping process from client signals to ODUkP overhead. At the top, CI\_D and CI\_CK signals enter an 'Elastic store' block. CI\_CK also feeds into an 'ODU clock generator locked to CBRx clock (ODCb)'. The Elastic store has 'WR' (write) and 'RD' (read) ports. The 'RD' port output goes to an 'AI\_D' output and also through a series of blocks: 'Justification control' (receiving 'JC' input), 'Insert PT', 'Insert RES', and 'ODUk OH is set to all-0's, except PM STAT = 001'. The 'Justification control' block also receives 'CK' from the ODU clock generator and sends 'JC' to the Elastic store. The 'ODU clock generator' also feeds into a frequency divider '1/122368', which outputs 'FS'. 'FS' feeds into another frequency divider '1/256', which outputs 'MFS'. 'CK', 'FS', and 'MFS' all feed into the 'AI\_CK', 'AI\_FS', and 'AI\_MFS' outputs respectively. The entire process is labeled 'RSn\_CP' at the top and 'ODUkP\_AP' at the bottom. A reference code 'G.798(17)-Amd.3(21)\_F14-41' is in the bottom right. + +**Figure 14-41 – ODUkP/RSn-b\_A\_So processes** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.3.6.3 ODUkP to RSn adaptation sink function (ODUkP/RSn\_A\_Sk) + +The ODUkP/RSn\_A\_Sk recovers the STM-N ( $N = 4^{(k+1)}$ ) client signal from the OPUk payload using the justification control information (JC overhead) to determine if a data or stuff byte is present within + +the NJO and PJO bytes. It extracts the OPUk overhead (PT, JC, RES) and monitors the reception of the correct payload type. It detects generic AIS and recovers the frame start of the STM-N signal. Under signal fail condition, a logical all-ONEs (AIS) signal shall be generated. + +The information flow and processing of the ODUkP/RSn\_A\_Sk function is defined with reference to Figures 14-42 and 14-43. + +### Symbol + +![Figure 14-42: ODUkP/RSn_A_Sk function symbol diagram. A trapezoidal block labeled 'ODUkP/RSn' has an input 'ODUkP_AP' at the bottom with parameter 'k = 1, 2, 3'. It has an output 'RSn_CP' at the top with parameter 'n = 16, 64, 256'. It also has an output 'ODUkP/RSn_A_Sk_MP' on the left side. The diagram is labeled 'G.798(17)_F14-42'.](d884367c84ba50f250499f79c4b4b950_img.jpg) + +Figure 14-42: ODUkP/RSn\_A\_Sk function symbol diagram. A trapezoidal block labeled 'ODUkP/RSn' has an input 'ODUkP\_AP' at the bottom with parameter 'k = 1, 2, 3'. It has an output 'RSn\_CP' at the top with parameter 'n = 16, 64, 256'. It also has an output 'ODUkP/RSn\_A\_Sk\_MP' on the left side. The diagram is labeled 'G.798(17)\_F14-42'. + +Figure 14-42 – ODUkP/RSn\_A\_Sk function + +### Interfaces + +Table 14-17 – ODUkP/RSn\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_MFS
ODUkP_AI_TSF | RSn_CP:
RSn_CI_CK
RSn_CI_D
RSn_CI_FS
RSn_CI_SSF
ODUkP/RSn_A_Sk_MP:
ODUkP/RSn_A_Sk_MI_cPLM
ODUkP/RSn_A_Sk_MI_AcPT
ODUkP/RSn_A_Sk_MI_cLOF | + +### Processes + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. + +**RES:** The value in the RES bytes shall be ignored. + +**JC:** The function shall interpret the justification control information in the JC byte as defined in clause 17.2 of [ITU-T G.709] in order to determine the justification action (positive, negative, none) for the current frame. RES bits in the JC shall be ignored. + +**Demapping, CBR clock generation:** The function shall provide an elastic store (buffer) process. The CBR data shall be written into the buffer from the D, PJO and NJO bytes in the OPUk frame. The information extraction of the PJO and NJO bytes shall be under the control of the justification control information. The RSn data (CI\_D) shall be read out of the buffer under the control of the RSn clock (CI\_CK). + +Upon a positive justification action, the writing of one data byte into the buffer shall be cancelled once. No RSn data shall be read from the PJO and NJO bytes. Upon a negative justification action, one extra data byte shall be written into the buffer once. RSn data shall be read from the PJO and NJO bytes. If neither a positive nor a negative justification action is to be performed, RSn data shall be read from the PJO byte and no RSn data shall be read from the NJO byte. + +**Smoothing and jitter limiting process:** The function shall provide for a clock smoothing and elastic store (buffer) process. The $4^{(k-1)} \times 2\,488\,320$ kbit/s ( $k = 1, 2, 3$ ) data signal shall be written into the buffer under the control of the associated (gapped) input clock (with a frequency accuracy within $\pm 20$ ppm). The data signal shall be read out of the buffer under the control of a smoothed (equally spaced) $4^{(k-1)} \times 2\,488\,320$ kbit/s $\pm 20$ ppm clock (the rate is determined by the 2.5 Gbit/s, 10 Gbit/s, 40 Gbit/s signal at the input of the remote ODUkP/RSn\_A\_So). + +The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCp clock), apply. + +**Buffer size:** In the presence of jitter as specified by [ITU-T G.825] and a frequency within the range $4^{(k-1)} \times 2\,488\,320$ kbit/s $\pm 20$ ppm, this justification process shall not introduce any errors. + +Following a step in frequency of the $4^{(k-1)} \times 2\,488\,320$ kbit/s signal transported by the ODUkP\_AI (for example due to removal of generic-AIS signal with a frequency offset), there will be a maximum recovery time of X seconds after which this process shall not generate any bit errors. The value of X is for further study; a value of one second has been proposed. + +**Frame alignment:** The function shall perform frame alignment on the STM-N frame as described in clause 8.2.1 of [ITU-T G.783]. + +![Figure 14-43 – ODUkP/RSn_A_Sk processes. This block diagram illustrates the internal functions of the ODUkP/RSn_A_Sk processing block. The block is divided into two main sections: RSn_CP (top) and ODUkP_AP (bottom). Inputs include CI_FS, CI_D, CI_CK, and CI_SSF. The RSn_CP section contains an AIS insertion block, an AIS generator, a frame alignment block, and a generic AIS supervision block. The ODUkP_AP section contains an elastic store (with WR and RD ports), a CBR clock generator (ODCp), a defect correlations block, an extract JC block, an extract PT block, and a PT process block. Various signals like dLOF, dPLM, dAIS, AI_TSF, and aAIS are shown as outputs or internal signals. The diagram is labeled G.798(17)_F14-43.](9af97997b7d3fbca90b8ddba0ea39c6c_img.jpg) + +Figure 14-43 – ODUkP/RSn\_A\_Sk processes. This block diagram illustrates the internal functions of the ODUkP/RSn\_A\_Sk processing block. The block is divided into two main sections: RSn\_CP (top) and ODUkP\_AP (bottom). Inputs include CI\_FS, CI\_D, CI\_CK, and CI\_SSF. The RSn\_CP section contains an AIS insertion block, an AIS generator, a frame alignment block, and a generic AIS supervision block. The ODUkP\_AP section contains an elastic store (with WR and RD ports), a CBR clock generator (ODCp), a defect correlations block, an extract JC block, an extract PT block, and a PT process block. Various signals like dLOF, dPLM, dAIS, AI\_TSF, and aAIS are shown as outputs or internal signals. The diagram is labeled G.798(17)\_F14-43. + +**Figure 14-43 – ODUkP/RSn\_A\_Sk processes** + +## Defects + +The function shall detect dPLM, dAIS and dLOF. + +**dPLM:** See clause 6.2.4.1. The expected payload types are "0000 0010" (asynchronous CBRx mapping) and "0000 0011" (bit synchronous CBRx mapping) as defined in [ITU-T G.709]. + +**dAIS:** See clause 6.2.6.3.3. + +**dLOF:** See clause 6.2.5.1 of [ITU-T G.783]. + +### Consequent actions + +aSSF $\leftarrow$ AI\_TSF or dPLM or dAIS or dLOF + +aAIS $\leftarrow$ AI\_TSF or dPLM or dAIS or dLOF + +On declaration of aAIS, the function shall output a logical all-ONEs (AIS) signal within two STM-N frames. On clearing aAIS, the logical all-ONEs (AIS) signal shall be removed within two STM-N frames, with normal data being output. The AIS clock shall be independent from the incoming clock. The AIS clock has to be within $4^{(k-1)} \times 2\,488\,320\text{ kHz} \pm 20\text{ ppm}$ . The jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCp clock), apply. + +### Defect correlations + +cPLM $\leftarrow$ dPLM and (not AI\_TSF) + +cLOF $\leftarrow$ dLOF and (not dAIS) and (not dPLM) and (not AI\_TSF) + +NOTE – dAIS is not reported as fault cause as it is a secondary alarm and will result in aSSF, which is reported as cSSF fault cause in the RSn\_TT\_Sk that directly follows this function. + +**Performance monitoring:** None. + +## 14.3.7 ODU0P to client adaptation function (ODU0P/CBRx\_A) ( $0 \leq x \leq 1.25\text{G}$ ) + +### 14.3.7.1 ODU0P to CBRx adaptation source function (ODU0P/CBRx\_A\_So) ( $0 \leq x \leq 1.25\text{G}$ ) + +The ODU0P to CBRx adaptation source function is specified in clause 14.3.8.1 with $k=0$ . + +### 14.3.7.2 ODU0P to CBRx adaptation sink function (ODU0P/CBRx\_A\_Sk) ( $0 \leq x \leq 1.25\text{G}$ ) + +The ODU0P to CBRx adaptation sink function is specified in clause 14.3.8.2 with $k=0$ . + +## 14.3.8 ODUkP to CBRx adaptation function using GMP (ODUkP/CBRx-g\_A) + +The ODUkP/CBRx-g\_A performs the adaptation between the ODUkP layer adapted information and the characteristic information of the indicated client signals transported as constant bit-rate streams. + +Parameter $x$ defines the bit rate or bit-rate range of the CBR signal. The values of $x$ are given in Table 14-18 as described in clause 17.7 of [ITU-T G.709]. + +**Table 14-18 – Defined values for $x$ for ODUk clients** + +| $x$ | PT | Maximum buffer hysteresis (bytes) | Bit rate (kbit/s) | Clock tolerance (ppm) | ODUk type | +|----------------------|------|-----------------------------------|-------------------|-----------------------|-----------| +| 155M | 0x0A | 1 | 155 520 | 20 | 0 | +| 622M | 0x0B | 1 | 622 080 | 20 | 0 | +| ETC1000X
(Note 1) | 0x07 | 1 | 1 171 875 | 100 | 0 | +| FC-100 | 0x0C | 1 | 1 062 500 | 100 | 0 | +| SBCON/ESCON | 0x1A | 1 | 200 000 | 200 | 0 | +| DVB-ASI | 0x1B | 1 | 270 000 | 100 | 0 | + +**Table 14-18 – Defined values for x for ODUk clients** + +| x | PT | Maximum buffer hysteresis (bytes) | Bit rate (kbit/s) | Clock tolerance (ppm) | ODUk type | +|---------------------|------|-----------------------------------|-------------------|-----------------------|-----------| +| SDI | 0x15 | 1 | 270 000 | ± 2.8 | 0 | +| FC-200 | 0x0D | 2 | 2 125 000 | ± 100 | 1 | +| 1.5G SDI | 0x16 | 2 | 1 485 000/1.001 | ± 10 | 1 | +| 1.5G SDI | 0x17 | 2 | 1 485 000 | ± 10 | 1 | +| ETC40GR
(Note 2) | 0x07 | 32 | 40 117 188 | ± 100 | 3 | +| ETC100GR | 0x07 | 80 | 103 125 000 | ± 100 | 4 | + +NOTE 1 – The original bit rate and clock range of the associated 1000BASE-X Ethernet client signal is 1 250 000 kbit/s ± 100 ppm. The bit rate and clock range in this table are for the CBR stream that is produced after mapping the client signal into a GFP-T. + +NOTE 2 – The original bit rate and clock range of the associated 40GBASE-R Ethernet client signal is 41 250 000 kbit/s ± 100 ppm. The bit rate and clock range in this table are for the CBR stream that is produced after transcoding. + +The ODUkP/CBRx-g\_A source function always provides asynchronous mapping. + +#### 14.3.8.1 ODUkP to CBRx adaptation source function using GMP (ODUkP/CBRx-g\_A\_So) + +The ODUkP/CBRx-g\_A\_So function creates the ODUk signal from a free-running clock. It asynchronously maps the constant bit-rate client signal from the CBRx\_CP into the payload area of the OPUk using a sigma-delta based data and stuff distribution as defined in Annex D of [ITU-T G.709], and adds OPUk overhead (RES, PT, JC) and default ODUk overhead. + +The information flow of the ODUkP/CBRx-g\_A\_So function is defined with reference to Figure 14-44 and the processing of the ODUkP/CBRx-g\_A\_So function is defined with reference to Figures 14-44 and 14-45. + +#### Symbol + +![Diagram of the ODUkP/CBRx-g_A_So function symbol. It shows an input CBRx_CP entering a trapezoidal block labeled ODUkP/CBRx-g. The block has an output ODUkP/CBRx-g_A_So_MP pointing to the left and a downward output ODUkP_AP. The diagram is labeled G.798(17)_F14-44.](69161330e28765ad34d95262a79d7b7d_img.jpg) + +``` + +graph TD + CBRx_CP[CBRx_CP] --> ODUkP_CBRx_g[ODUkP/CBRx-g] + ODUkP_CBRx_g --> ODUkP_CBRx_g_A_So_MP[ODUkP/CBRx-g_A_So_MP] + ODUkP_CBRx_g --> ODUkP_AP[ODUkP_AP] + style ODUkP_CBRx_g shape:trapezoid + style ODUkP_CBRx_g_A_So_MP fill:none,stroke:none + style ODUkP_AP fill:none,stroke:none + subgraph G.798(17)_F14-44 + end + +``` + +Diagram of the ODUkP/CBRx-g\_A\_So function symbol. It shows an input CBRx\_CP entering a trapezoidal block labeled ODUkP/CBRx-g. The block has an output ODUkP/CBRx-g\_A\_So\_MP pointing to the left and a downward output ODUkP\_AP. The diagram is labeled G.798(17)\_F14-44. + +**Figure 14-44 – ODUkP/CBRx-g\_A\_So function** + +## Interfaces + +**Table 14-19 – ODUkP/CBRx-g\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| CBRx_CP:
CBRx_CI_CK
CBRx_CI_D
CBRx_CI_SSF | ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_MFS
ODUkP/CBRx-g_A_So_MP:
ODUkP/CBRx-g_A_So_MI_pN_PCS_BIP (Note 1) | +| NOTE 1 – Only applicable for ETC40GR and ETC100GR clients. | | + +## Processes + +**Clock and (multi)frame start signal generation:** The function shall generate a local ODUk clock (ODUkP\_AI\_CK) as given in Table 7-2 of [ITU-T G.709] from a free-running oscillator. The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUk signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +**Mapping, frequency justification and bit-rate adaptation:** The function shall provide an elastic store (buffer) process. The data signal shall be written into the buffer under the control of the associated input clock. The data shall be read out of the buffer and written onto the D bytes in the OPUk frame under the control of the sigma/delta based data/stuff distribution algorithm as defined in Annex D of [ITU-T G.709]. + +As per Annex D of [ITU-T G.709], the amount of data, in n-bit words, to be transmitted in the subsequent frame is determined. The $C_m(t)$ value encoded in JC1/2/3 represents the number of m-bit words that are mapped into the subsequent frame and the $\sum C_{nD}(t)$ value encoded in the JC4/5/6 represents in, n-bit words, the accumulated remainder that could not be transmitted. + +For ETC1000X clients, the data signal shall be synchronously transcoded into a GFP-T signal in which each GFP-T frame contains one superblock and in which the 65B\_PAD character and GFP Idle frames are not used, under the control of the associated input clock, and then the synchronous GFP-T like signal shall be written into the buffer under a synchronous input clock. This sub-process is depicted in Figure 14-47. + +For ETC40GR clients, the data signal ETC40GR\_CI\_D shall be synchronously transcoded under the control of the associated input clock, and then the synchronously transcoded signal shall be written into the buffer under a synchronous input clock as defined in clause 17.7.4.1 of [ITU-T G.709]. + +**Buffer size:** In the presence of jitter as described for each client in [ITU-T G.8251], this mapping process shall not introduce any errors. The maximum buffer hysteresis, and therefore the maximum phase error introduced, shall be as listed in Table 14-18. + +**Lane processing:** For multilane Ethernet interfaces, lane reordering is needed. The process is depicted in Figure 14-46 and described in clauses 17.7.4.1 and 17.7.5.1 of [ITU-T G.709]. + +### Incoming PCS BIP monitoring and mask insertion and OTN section BIP generation + +- For ETC40GR multilane interfaces, an error mask is to be calculated over the PCSL BIP of the incoming signal. For the OTN section, a BIP has to be calculated on the descrambled + +datastream and after error control block insertion. The "OTN BIP" and the error mask will be transmitted together in the transcoded lane marker. See Annex E of [ITU-T G.709] and Figure 14-46a. + +- For ETC100GR multilane interfaces, the incoming PCSL BIP will be transparently transmitted, errored 66B blocks will not be replaced with error control blocks and the scrambled PCS data will be passed through transparently. See Annex E of [ITU-T G.709] and Figure 14-46b. + +**PCS BIP monitoring:** The BIP violations of the PCS lanes shall be counted and presented to the management interface. + +**JC bytes:** The function shall insert the justification control (JC) bytes. As specified in clause 17.7 of [ITU-T G.709], $C_m(t)$ and $\sum C_{nD}(t)$ values are determined every frame as specified in Annex D of [ITU-T G.709] and inserted into the JC1/2/3 and JC4/5/6 OPU overhead locations respectively. The value of n for the $\sum C_{nD}$ justification information is specified in clause 17.7 of [ITU-T G.709]. + +**PT:** The function shall insert the appropriate payload type code into the PT byte position of the PSI overhead, as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**Client signal fail:** The function shall signal the failure of the client signal to the far end by use of the Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +**RES:** The function shall insert all-ZEROs into the RES bytes and reserved bits within the JC bytes. + +All other bits of the ODUk overhead should be sourced as "0"s, except the PMOH STAT field which should be set to the value "normal path signal" (001). + +![Functional block diagram of ODUkP/CBRx-g_A_So. The diagram shows a large grey box representing the function. Inputs from the top include CI_D, CI_CK, and CI_SSF (part of CBRx_CP). CI_D and CI_CK enter a 'Lane processing and transcoding (client specific)' block. This block outputs data (D) and clock (CK) to an 'Elastic store'. The Elastic store has a circular buffer representation with WR (write) and RD (read) pointers. The WR and RD signals are fed into a 'Sigma-delta based justification control and JC generation' block. This block also receives a JC signal. A 'Free-running clock generator (ODCa)' provides a clock (CK) which is divided by 122368 to produce FS, and then by 256 to produce MFS. These timing signals (CK, FS, MFS) are output at the bottom as AI_CK, AI_FS, and AI_MFS. The data from the elastic store is processed through several insertion blocks: 'Insert PT', 'Insert CSF' (which also takes CI_SSF), 'Insert RES', and 'ODUk OH is set to all-0's, except PM STAT = 001'. The final data output is AI_D at the bottom. A management interface signal MI_pN_PCS_BIP is shown on the right side. The entire block is labeled ODUkP/CBRx-g_A_So_MP on the right and ODUkP_AP at the bottom. Reference G.798(17)_F14-45 is noted.](f2e1a8f6118f3a062702aae017e04753_img.jpg) + +Functional block diagram of ODUkP/CBRx-g\_A\_So. The diagram shows a large grey box representing the function. Inputs from the top include CI\_D, CI\_CK, and CI\_SSF (part of CBRx\_CP). CI\_D and CI\_CK enter a 'Lane processing and transcoding (client specific)' block. This block outputs data (D) and clock (CK) to an 'Elastic store'. The Elastic store has a circular buffer representation with WR (write) and RD (read) pointers. The WR and RD signals are fed into a 'Sigma-delta based justification control and JC generation' block. This block also receives a JC signal. A 'Free-running clock generator (ODCa)' provides a clock (CK) which is divided by 122368 to produce FS, and then by 256 to produce MFS. These timing signals (CK, FS, MFS) are output at the bottom as AI\_CK, AI\_FS, and AI\_MFS. The data from the elastic store is processed through several insertion blocks: 'Insert PT', 'Insert CSF' (which also takes CI\_SSF), 'Insert RES', and 'ODUk OH is set to all-0's, except PM STAT = 001'. The final data output is AI\_D at the bottom. A management interface signal MI\_pN\_PCS\_BIP is shown on the right side. The entire block is labeled ODUkP/CBRx-g\_A\_So\_MP on the right and ODUkP\_AP at the bottom. Reference G.798(17)\_F14-45 is noted. + +**Figure 14-45 – ODUkP/CBRx-g\_A\_So function** + +![Figure 14-46a: Lane processing and timing transparent process of the ODUkP/CBRx-g_A_So function for ETC40GR clients. The diagram shows a signal flow starting from an ETC40GR interface (CI) through a 'Lane reordering' block. The output of 'Lane reordering' is split: one path goes to 'Extract PCSL BIP', which then connects to 'Descramble'. The 'Descramble' output goes to a large dashed box labeled 'Transcode Ctrl/Data' and 'Timing transparent transcode'. Inside this box, the signal goes through 'Transcode lane marker + Insert PCS error mask and OTN PCSL BIP', which then connects to 'Scramble Non-flag/parity'. The 'Scramble Non-flag/parity' output is split into 'Data' and 'Clock' (CI). Another path from 'Lane reordering' goes to 'Calculate PCSL BIP', which then connects to a summation node (+). The output of the summation node is labeled 'PCS error mask' and goes to the 'Transcode lane marker' block. A third path from 'Lane reordering' goes to 'Monitor PCSL BIP'.](7e1f88e0cc7be8060240e12252a833d1_img.jpg) + +Figure 14-46a: Lane processing and timing transparent process of the ODUkP/CBRx-g\_A\_So function for ETC40GR clients. The diagram shows a signal flow starting from an ETC40GR interface (CI) through a 'Lane reordering' block. The output of 'Lane reordering' is split: one path goes to 'Extract PCSL BIP', which then connects to 'Descramble'. The 'Descramble' output goes to a large dashed box labeled 'Transcode Ctrl/Data' and 'Timing transparent transcode'. Inside this box, the signal goes through 'Transcode lane marker + Insert PCS error mask and OTN PCSL BIP', which then connects to 'Scramble Non-flag/parity'. The 'Scramble Non-flag/parity' output is split into 'Data' and 'Clock' (CI). Another path from 'Lane reordering' goes to 'Calculate PCSL BIP', which then connects to a summation node (+). The output of the summation node is labeled 'PCS error mask' and goes to the 'Transcode lane marker' block. A third path from 'Lane reordering' goes to 'Monitor PCSL BIP'. + +G.798(17)-Amd.1(18)\_F14-46a + +**Figure 14-46a – Lane processing and timing transparent process of the ODUkP/CBRx-g\_A\_So function for ETC40GR clients** + +![Figure 14-46b: Lane processing process of the ODUkP/CBRx-g_A_So function for ETC100GR clients. The diagram shows a signal flow starting from an ETC100GR interface (CI) through a 'Lane reordering' block. The output of 'Lane reordering' is split: one path goes directly to 'Data' and 'Clock' (CI). Another path goes to 'Extract PCSL BIP', which then connects to 'Calculate PCSL BIP'. The 'Calculate PCSL BIP' output goes to a summation node (+). The output of the summation node goes to 'Monitor PCSL BIP'.](e67401bb970e10780dd4086d67c8195f_img.jpg) + +Figure 14-46b: Lane processing process of the ODUkP/CBRx-g\_A\_So function for ETC100GR clients. The diagram shows a signal flow starting from an ETC100GR interface (CI) through a 'Lane reordering' block. The output of 'Lane reordering' is split: one path goes directly to 'Data' and 'Clock' (CI). Another path goes to 'Extract PCSL BIP', which then connects to 'Calculate PCSL BIP'. The 'Calculate PCSL BIP' output goes to a summation node (+). The output of the summation node goes to 'Monitor PCSL BIP'. + +G.798(17)-Amd.1(18)\_F14-46b + +**Figure 14-46b – Lane processing process of the ODUkP/CBRx-g\_A\_So function for ETC100GR clients** + +***ETC1000X -specific GFP-T source processes*** + +See clause 8.5.4.2.1 of [ITU-T G.806]. 65B\_PAD insertion is disabled (RAdisable=true). GFP pFCS generation is disabled (FCSenable=false). The UPI value for transparent gigabit Ethernet shall be inserted (Table 6-3 of [ITU-T G.704]). The Ethernet codeword information is inserted into the client payload information field of the GFP-T frames according to clause 8 of [ITU-T G.704]. + +***Common GFP-T source processes*** + +See clause 8.5.3.1 of [ITU-T G.806]. GFP channel multiplexing is not supported (CMuxActive=false). + +![Timing transparent transcoding process for ETC1000X clients diagram](bb8035cd106b4d77b3615e90645f8e37_img.jpg) + +``` + +graph TD + ETC1000X_CP[ETC1000X_CP] -- CI_CK --> ETC1000X_Specific[ETC1000X specific GFP-T processes] + ETC1000X_CP -- CI_D --> ETC1000X_Specific + RAdisable_true[RAdisable=true] -.-> ETC1000X_Specific + ETC1000X_Specific -- GFP_FS --> Common[Common GFP-T processes] + ETC1000X_Specific -- GFP_Frame --> Common + Common -- CK --> CK_out[CK to buffer] + Common -- Data --> Data_out[Data] + +``` + +G.798(17)-Amd.1(18)\_F14-47 + +Timing transparent transcoding process for ETC1000X clients diagram + +**Figure 14-47 – Timing transparent transcoding process for ETC1000X clients** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** + +The function shall perform the following performance monitoring primitives processing (see clause 6.5 of [ITU-T G.806]). The performance monitoring primitives shall be reported to the EMF. + +$$pN\_PCS\_BIP \leftarrow \sum nPCSL\_BIP$$ + +**14.3.8.2 ODUkP to CBRx adaptation sink function using GMP (ODUkP/CBRx-g\_A\_Sk)** + +The ODUkP/CBRx-g\_A\_Sk recovers the constant bit-rate client signal from the OPUk payload using the justification control information (JC overhead) of the previous frame to determine the number of client data byte blocks that were sent during the current frame, and the location of these data byte blocks within the payload area from the sigma-delta justification. It extracts the OPUk overhead (PT, JC, and RES) and monitors the reception of the correct payload type. Under signal fail condition, generic replacement signals, as given in Table 14-20, shall be inserted. + +**Table 14-20 – Defined replacement signals and jitter specification references for ODUk clients** + +| Client | PT | Replacement signal | Bit rate | Jitter standard | +|----------|------|--------------------|--------------------------------|-----------------------------------------| +| 155M | 0x0A | Generic-AIS | 155 520 kbit/s $\pm$ 20 ppm | [ITU-T G.825] | +| 622M | 0x0B | Generic-AIS | 622 080 kbit/s $\pm$ 20 ppm | [ITU-T G.825] | +| ETC1000X | 0x07 | Link fault | 1 250 000 kbit/s $\pm$ 100 ppm | [IEEE 802.3] | +| FC-100 | 0x0C | NOS | 1 062 500 kbit/s $\pm$ 100 ppm | [b-ANSI INCITS 352] | +| SBCON | 0x1A | NOS | 200 000 kbits $\pm$ 200 ppm | [b-ANSI INCITS 296] | +| DVB-ASI | 0x1B | Generic-AIS | 270 000 kbit/s $\pm$ 100 ppm | [ETSI TR 101 891],
[ETSI TR 101 290] | +| FC-200 | 0x0D | NOS | 2 125 000 (kbit/s) $\pm$ 100 | [b-ANSI INCITS 352] | +| ETC40GR | 0x07 | Local fault | 40 117 188 (kbit/s) $\pm$ 100 | [IEEE 802.3] | +| ETC100GR | 0x07 | Local fault | 103 125 000 (kbit/s) $\pm$ 100 | [IEEE 802.3] | + +The information flow and processing of the ODUkP/CBRx-g\_A\_Sk function is defined with reference to Figures 14-48, 14-49, 14-50 and 14-51. + +### Symbol + +![Figure 14-48: ODUkP/CBRx-g_A_Sk function symbol diagram. A trapezoidal block labeled 'ODUkP/CBRx-g' has an input arrow from the bottom labeled 'ODUkP_AP' and an output arrow pointing left labeled 'ODUkP/CBRx-g_A_Sk_MP'. A reference label 'G.798(17)_F14-48' is at the bottom right.](b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg) + +Figure 14-48: ODUkP/CBRx-g\_A\_Sk function symbol diagram. A trapezoidal block labeled 'ODUkP/CBRx-g' has an input arrow from the bottom labeled 'ODUkP\_AP' and an output arrow pointing left labeled 'ODUkP/CBRx-g\_A\_Sk\_MP'. A reference label 'G.798(17)\_F14-48' is at the bottom right. + +Figure 14-48 – ODUkP/CBRx-g\_A\_Sk function + +### Interfaces + +Table 14-21 – ODUkP/CBRx-g\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_MFS
ODUkP_AI_TSF | CBRx_CP:
CBRx_CI_CK
CBRx_CI_D
CBRx_CI_SSF
ODUkP/CBRx-g_A_Sk_MP:
ODUkP/CBRx-g_A_Sk_MI_cPLM
ODUkP/CBRx-g_A_Sk_MI_AcPT
ODUkP/CBRx-g_A_Sk_MI_cCSF
ODUkP/CBRx-g_A_Sk_MI_cLCS (Note)
ODUkP/CBRx-g_A_Sk_MI_pN_PCS_BIP (Note) | +| NOTE – Only applicable for ETC40GR and ETC100GR clients. | | + +### Processes + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. + +**RES:** The value in the RES bytes shall be ignored. + +**JC:** The function shall interpret the justification control information in the JC bytes, as defined in clause 17.7 of [ITU-T G.709], from the current multiframe in order to determine the number of payload bytes for the following multiframe. RES bits in the JC shall be ignored. The function shall extract the $\sum C_{nD}(t)$ with n as per clause 17.7 of [ITU-T G.709]. + +**Lane processing and transcoding:** For multilane Ethernet interfaces, lane processing and transcoding (transcoding for ETC40GR) is needed. The process is depicted in Figures 14-50 and 14-51, and described in clauses 17.7.4.1 and 17.7.5.1 of [ITU-T G.709]. + +### BIP correction: + +- For ETC40GR multilane interfaces, the PCSL BIP error mask is to be extracted and an OTN BIP error mask is calculated before scrambling. Both error masks are used for calculating an adjusted PCSL BIP which will be inserted. See Annex E of [ITU-T G.709] and Figure 14-50. +- For ETC100GR multilane interfaces, the incoming PCSL BIP will be transparently transmitted. See Annex E of [ITU-T G.709] and Figure 14-51. + +**Client signal fail:** The function shall extract the CSF signal indicating the failure of the client signal out of Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +**Demapping, CBR clock generation:** The function shall provide an elastic store (buffer) process. The CBR data shall be written into the buffer from the data-bearing D bytes in the OPUk frames. The information extraction of the payload area shall be under the control of the sigma-delta based data/stuff distribution. The CBRx data (CI\_D) shall be read out of the buffer under the control of the CBRx clock (CI\_CK). + +The locations of the data and stuff bytes are determined based on the count value sent in the JC bytes of the immediately preceding frame, as defined in clause 17.7 of [ITU-T G.709]. When a stuff m-bit block is encountered in the payload area, the writing of one m-bit block into the buffer shall be cancelled once. For the GMP justification process, refer to Annex D of [ITU-T G.709]. + +*Smoothing and jitter limiting process:* The function shall provide for a clock smoothing and elastic store (buffer) process. The data signal shall be written into the buffer under the control of the associated (gapped) input clock. The data signal shall be read out of the buffer under the control of a smoothed (equally spaced) clock at a rate and frequency accuracy determined by the client signal rate at the input of the remote ODUkP/CBRx\_a\_So. The clock generation process for reading the data out of the buffer shall use the $\sum C_{nD}$ justification information with n as per clause 17.7 of [ITU-T G.709]. + +The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCp clock), apply. + +*Buffer size:* In the presence of jitter as specified for client signals in the standards given in Table 14-20, this justification process shall not introduce any errors. + +Following a step in frequency of the signal transported by the ODUkP\_AI (for example, due to reception of CBRx\_CI from a new CBR\_TT\_So at the far end or removal of the client replacement signal with a frequency offset), there will be a maximum recovery time of X seconds after which this process shall not generate any bit errors. The value of X is for further study; a value of 1 second has been proposed. + +NOTE 1 – Equipment developed prior to Edition 4.0 of this Recommendation will not support the CSF processing. + +![Block diagram of ODUkP/CBRx-g_A_Sk processes showing internal components and external interfaces.](29aa6165ccf449dee0b4335676fa7b1a_img.jpg) + +The diagram illustrates the internal architecture of the ODUkP/CBRx-g\_A\_Sk processes. It is divided into two main functional areas: **CBRx\_CP** (top) and **ODUkP\_AP** (bottom). + +- CBRx\_CP (CBRx Clock Processing):** + - Inputs: **CI\_D**, **CI\_CK**, and **CI\_SSF**. + - Internal components: **Replacement signal insertion**, **Replacement signal generator**, **Lane processing and transcoding (if needed)**, **Elastic store** (with **WR** and **RD** ports), **CBR clock generator (ODCp)**, **Consequent actions**, and **Defect correlations**. + - Outputs: **dLCS**, **MI\_pN\_PCS\_BIP**, **MI\_cPLM**, **MI\_cCSF**, and **MI\_cLCS**. + - Control signals: **aAIS**, **dPLM**, **AI\_TSF**, and **CK**. +- ODUkP\_AP (ODUkP Adaptation Processing):** + - Inputs: **AI\_D**, **AI\_MFS**, **AI\_CK**, **AI\_FS**, and **AI\_TSF**. + - Internal components: **Justification action**, **Sigma-delta justification control**, **Extract JC**, **Extract CSF**, **Extract PT**, and **PT process**. + - Outputs: **dCSF**, **dPLM**, and **MI\_AcPT**. + +External interface labels on the right side of the diagram include **ODUkP/CBRx-g\_A\_Sk\_MP**. + +Reference code: G.798(17)\_F14-49 + +Block diagram of ODUkP/CBRx-g\_A\_Sk processes showing internal components and external interfaces. + +Figure 14-49 – ODUkP/CBRx-g\_A\_Sk processes + +![Figure 14-50: Lane processing and timing transparent process of the ODUkP/CBRx-g_A_Sk function for ETC40GR clients. The diagram shows a sequence of processing blocks: 1027B block sync (receiving Data, Clock, and CI; outputting dLCS), Descramble Non-flag/parity, Timing transparent trans-decode, and Lane distribution. The output of Lane distribution goes to an ETC40GR interface via an Insert PCSL BIP block, with a CI input. A feedback loop from the Lane distribution output goes to an Extract PCS error Mask and OTN PCSL BIP block. This block outputs an OTN PCSL BIP and a PCS error mask. The OTN PCSL BIP is added (+) to the output of a Calculate expected OTN PCSL BIP block. The result is an OTN BIP error mask, which is added (+) to the output of a Calculate PCSL BIP block. The final result is sent to a Monitor PCSL BIP block. A Scramble Non SH block is also shown, receiving input from the Extract PCS error Mask and OTN PCSL BIP block and outputting to the Insert PCSL BIP block.](3c721884a92b102becb43b52f6110e47_img.jpg) + +Figure 14-50: Lane processing and timing transparent process of the ODUkP/CBRx-g\_A\_Sk function for ETC40GR clients. The diagram shows a sequence of processing blocks: 1027B block sync (receiving Data, Clock, and CI; outputting dLCS), Descramble Non-flag/parity, Timing transparent trans-decode, and Lane distribution. The output of Lane distribution goes to an ETC40GR interface via an Insert PCSL BIP block, with a CI input. A feedback loop from the Lane distribution output goes to an Extract PCS error Mask and OTN PCSL BIP block. This block outputs an OTN PCSL BIP and a PCS error mask. The OTN PCSL BIP is added (+) to the output of a Calculate expected OTN PCSL BIP block. The result is an OTN BIP error mask, which is added (+) to the output of a Calculate PCSL BIP block. The final result is sent to a Monitor PCSL BIP block. A Scramble Non SH block is also shown, receiving input from the Extract PCS error Mask and OTN PCSL BIP block and outputting to the Insert PCSL BIP block. + +G.798(17)-Amd.1(18)\_F14-50 + +**Figure 14-50 – Lane processing and timing transparent process of the ODUkP/CBRx-g\_A\_Sk function for ETC40GR clients** + +![Figure 14-51: Lane processing process of the ODUkP/CBRx-g_A_Sk function for ETC100GR clients. The diagram shows a sequence of processing blocks: 66B block sync (receiving Data, Clock, and CI; outputting dLCS), and Lane distribution. The output of Lane distribution goes to an ETC100GR interface via a CI input. A feedback loop from the Lane distribution output goes to an Extract PCSL BIP block. This block outputs to a Calculate PCSL BIP block. The output of the Calculate PCSL BIP block is added (+) to the output of the Extract PCSL BIP block. The final result is sent to a Monitor PCSL BIP block.](7c19fc92dc74a74ec346d46bc39a3946_img.jpg) + +Figure 14-51: Lane processing process of the ODUkP/CBRx-g\_A\_Sk function for ETC100GR clients. The diagram shows a sequence of processing blocks: 66B block sync (receiving Data, Clock, and CI; outputting dLCS), and Lane distribution. The output of Lane distribution goes to an ETC100GR interface via a CI input. A feedback loop from the Lane distribution output goes to an Extract PCSL BIP block. This block outputs to a Calculate PCSL BIP block. The output of the Calculate PCSL BIP block is added (+) to the output of the Extract PCSL BIP block. The final result is sent to a Monitor PCSL BIP block. + +G.798(17)-Amd.1(18)\_F14-51 + +**Figure 14-51 – Lane processing process of the ODUkP/CBRx-g\_A\_Sk function for ETC100GR clients** + +For ETC1000X clients, the function shall also provide a GFP-T extraction process. This synchronous transcoding sub-process is depicted in Figure 14-52. + +![Timing transparent transcoding process for ETC1000X clients diagram](25b2ef5bcf30bfa9a31d59f48fddb3a7_img.jpg) + +The diagram illustrates the timing transparent transcoding process for ETC1000X clients. It shows three main components: ETC1000X\_CP at the top, ETC1000X specific GFP-T processes in the middle, and Common GFP-T processes at the bottom. Inputs to the Common GFP-T processes are CK from buffer and Data. The Common GFP-T processes output GFP\_FS and GFP\_Frame to the ETC1000X specific GFP-T processes. The ETC1000X specific GFP-T processes output CI\_CK and CI\_D to the ETC1000X\_CP. + +``` + +graph TD + subgraph ETC1000X_CP + CI_CK[CI_CK] + CI_D[CI_D] + end + ETC1000X_specific[ETC1000X specific GFP-T processes] + Common[Common GFP-T processes] + CK[CK from buffer] + Data[Data] + + CK --> Common + Data --> Common + Common -- GFP_FS --> ETC1000X_specific + Common -- GFP_Frame --> ETC1000X_specific + ETC1000X_specific -- CI_CK --> CI_CK + ETC1000X_specific -- CI_D --> CI_D + +``` + +Timing transparent transcoding process for ETC1000X clients diagram + +G.798(17)-Amd.1(18)\_F14-52 + +**Figure 14-52 – Timing transparent transcoding process for ETC1000X clients** + +NOTE 2 – No detection and alarming as well as PM of the GFP related defects and indicators is required as the GFP process is used as mapping only and due to the 1/1 relation to the ODU0 all errors are visible on the ODU layer already. This means a detection of the related GFP defined indicators does not add any additional information about the cause of degradation. + +#### ***ETC1000X-specific GFP-T sink processes*** + +See clause 8.5.4.2.2 of [ITU-T G.806]. GFP pFCS checking and GFP p\_FCSError are not supported (FCSdiscard=false). The UPI value for transparent gigabit Ethernet shall be expected (Table 6-3 of [ITU-T G.704]). GFP performance monitoring (p\_FDis, p\_CRC16Error) is not supported. The Ethernet codeword information is extracted from the client payload information field of the GFP-T frames according to clause 8 of [ITU-T G.704]. + +#### ***Common GFP-T sink processes*** + +See clause 8.5.3.2 of [ITU-T G.806]. GFP channel multiplexing is not supported (CMuxActive=false). GFP performance monitoring (p\_FDis) is not supported. + +#### **Defects** + +The function shall detect dPLM. + +**dPLM:** See clause 6.2.4.1. The expected payload types are defined in clause 15.9.2.1 of [ITU-T G.709]. + +**dCSF:** See clause 6.2.10. + +**dLCS:** For ETC100GR clients, see clause 6.2.5.7.1; for ETC40GR clients, see clause 6.2.5.7.2; for other clients dLCS shall be assumed false. + +#### **Consequent actions** + +aSSF ← AI\_TSF or dPLM or dLCS + +aAIS ← AI\_TSF or dPLM or dLCS + +NOTE – The state of the determination process of the Cm and its contribution to AIS consequent action are for further study. + +On declaration of aAIS, the function shall output a client replacement signal as defined in Table 14-20 within two frames. On clearing aAIS, the client replacement signal shall be removed within two frames and normal data being output. The client replacement signal clock start shall be independent from the incoming clock. The client replacement signal clock has to be within the frequency, jitter, and wander tolerance specifications of the associated client signal. + +## Defect correlations + +cPLM $\leftarrow$ dPLM and (not AI\_TSF) + +cCSF $\leftarrow$ dCSF and (not dPLM) and (not AI\_TSF) + +cLCS $\leftarrow$ dLCS and (not dCSF) and (not dPLM) and (not AI\_TSF) + +## Performance monitoring + +The function shall perform the following performance monitoring primitives processing (see clause 6.5 of [ITU-T G.806]). The performance monitoring primitives shall be reported to the EMF. + +pN\_PCS\_BIP $\leftarrow \sum n$ PCSL\_BIP + +### 14.3.9 ODUkP to ODU[i]j adaptation function (ODUkP/ODU[i]j\_A) + +The ODUkP to ODU[i]j adaptation functions perform the adaptation between the ODUkP ( $k = 1, 2, 3$ ) layer adapted information and the characteristic information of ODUj ( $j = 0, 1, 2; j < k$ ) [and ODUi ( $i = 1; i < j$ )] signals. + +![Diagram of the ODUkP/ODU[i]j_A function. A central trapezoidal block is labeled 'ODUkP/ODU[i]j'. Above it, multiple tributary ports are shown, labeled 'Tributary ports' and numbered 1, 2, ..., n, 1, 2, ..., m. These ports are associated with 'ODUj_CPs' and '[ODUi_CPs]'. Arrows point from these ports down into the central block. Below the central block, an arrow points down to a label 'ODUkP_AP'. To the right of the central block, the text 'G.798(17)_F14-53' is present.](625663deae3d429f79ae6d2781986e2c_img.jpg) + +Diagram of the ODUkP/ODU[i]j\_A function. A central trapezoidal block is labeled 'ODUkP/ODU[i]j'. Above it, multiple tributary ports are shown, labeled 'Tributary ports' and numbered 1, 2, ..., n, 1, 2, ..., m. These ports are associated with 'ODUj\_CPs' and '[ODUi\_CPs]'. Arrows point from these ports down into the central block. Below the central block, an arrow points down to a label 'ODUkP\_AP'. To the right of the central block, the text 'G.798(17)\_F14-53' is present. + +Figure 14-53 – ODUkP/ODU[i]j\_A function + +Five different types of functions are possible: + +- the ODU1P/ODU0\_A performs multiplexing/demultiplexing of 2 ODU0 into an ODU1; +- the ODU2P/ODU1\_A performs multiplexing/demultiplexing of 4 ODU1 into an ODU2; +- the ODU3P/ODU1\_A performs multiplexing/demultiplexing of 16 ODU1 into an ODU3; +- the ODU3P/ODU2\_A performs multiplexing/demultiplexing of 4 ODU2 into an ODU3; +- the ODU3P/ODU12\_A performs multiplexing/demultiplexing of ODU1 and ODU2 into an ODU3. + +The maximum number of tributary ports depends on the specific function type as listed in Table 14-22. Note that for the ODU3P/ODU12\_A function, only a subset of the tributary signals can be active and transported via the ODU3 at one time. The number of active ODU1 ports plus four times the number of active ODU2 ports is limited to 16. The multiplex structure identifier (MSI) defines the configuration in this case. + +Note that the ODU3P/ODU12\_A function can interwork with the ODU2P/ODU1\_A, ODU3P/ODU1\_A and ODU3P/ODU2\_A functions as it supports all related multiplex structures. + +**Table 14-22 – ODUkP/ODU[i]j\_A tributary ports** + +| Function type | n ports | m ports | +|---------------|---------|---------| +| ODU1P/ODU0_A | 2 ODU0 | – | +| ODU2P/ODU1_A | 4 ODU1 | – | +| ODU3P/ODU1_A | 16 ODU1 | – | +| ODU3P/ODU2_A | 4 ODU2 | – | +| ODU3P/ODU12_A | 16 ODU1 | 4 ODU2 | + +#### 14.3.9.1 ODUkP to ODU[i]j adaptation source function (ODUkP/ODU[i]j\_A\_So) + +The ODUkP/ODU[i]j\_A\_So function creates the ODUk signal from a free-running clock. It asynchronously maps the $n \times \text{ODUj}$ [and $m \times \text{ODUi}$ ] client signal from the ODUj\_ [and ODUi] CPs into ODTUjk[/ik] including justification control (JC) information. The ODTUjk[/ik] are multiplexed into the payload area of the OPUk. It adds OPUk overhead (RES, PT, MSI) and default ODUk overhead. It provides access to ODUk PM APS overhead. It provides access to the ODUj [/i] APS overhead. + +The information flow and processing of the ODUkP/ODU[i]j\_A\_So function is defined with reference to Figures 14-54, 14-55 and 14-56. + +##### Symbol + +![Diagram of the ODUkP/ODU[i]j_A_So function symbol. The symbol is a trapezoid labeled 'ODUkP/ODU[i]j'. Inputs from the top are tributary ports labeled 1, 2, ..., n for 'ODUj_CPs' and 1, 2, ..., m for '[ODUi_CPs]'. Inputs from the left are 'ODUkP/ODU[i]j_A_So_MP' and 'ODUk_PP'. The output at the bottom is 'ODUkP_AP'. A reference label 'G.798(17)_F14-54' is present near the bottom right of the symbol.](4df70569f4cc27db5625fc75bdff68cf_img.jpg) + +Diagram of the ODUkP/ODU[i]j\_A\_So function symbol. The symbol is a trapezoid labeled 'ODUkP/ODU[i]j'. Inputs from the top are tributary ports labeled 1, 2, ..., n for 'ODUj\_CPs' and 1, 2, ..., m for '[ODUi\_CPs]'. Inputs from the left are 'ODUkP/ODU[i]j\_A\_So\_MP' and 'ODUk\_PP'. The output at the bottom is 'ODUkP\_AP'. A reference label 'G.798(17)\_F14-54' is present near the bottom right of the symbol. + +**Figure 14-54 – ODUkP/ODU[i]j\_A\_So function** + +## Interfaces + +**Table 14-23 – ODUkP/ODU[i]j\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------| +| n × ODUj_CP:
ODUj_CI_CK
ODUj_CI_D
ODUj_CI_FS
ODUj_CI_MFS
ODUj_CI_APS
m × ODUi_CP: (Note)
ODUi_CI_CK
ODUi_CI_D
ODUi_CI_FS
ODUi_CI_MFS
ODUi_CI_APS
ODUk_PP:
ODUk_PI_APS
ODUkP/ODU[i]j_A_So_MP:
ODU3P/ODU12_A_So_MI_TxMSI (Note)
ODUkP/ODU[i]j_A_So_MI_AdminState [1..(n+m)]
ODUkP/ODU[i]j_A_So_MI_APS_EN [1..(n+m)]
ODUkP/ODU[i]j_A_So_MI_APS_LVL[1..(n+m)] | ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_MFS | +| NOTE – For ODU3P/ODU12_A_So only. | | + +## Processes + +The processes associated with the ODUkP/ODU[i]j\_A\_So function are specific processes for each ODUj[i]/\_CP and common processes for the compound (multiplexed) signal as depicted in Figures 14-55 and 14-56. + +![Block diagram of ODUkP/ODU[i]j_A_So processes showing client-specific processes, a multiplexer, and a multiplex structure with various control signals and a clock generator.](d9862ac8473902e7dfe441c5e88d47d8_img.jpg) + +The diagram illustrates the ODUkP/ODU[i]j\_A\_So processes. At the top, multiple client-specific processes are shown, labeled ODUj\_CP[1] ... ODUj\_CP[n] and ODUi\_CP[1] ... ODUi\_CP[m]. Each process has input signals CL\_MFS, CL\_FS, CL\_CK, CL\_D, and CL\_APS, and output signals MI\_AdminState, MI\_APS\_EN, and MI\_APS\_LVL. These processes are connected to a central Multiplexer. The Multiplexer outputs signals MFS, FS, CK, D, and TS# to the Multiplex structure. The Multiplex structure contains several components: Multiplex structure identifier (MSI), Payload type (PT), RES, ODUk PM APS, and a block for ODUk OH (set to all-0's, except PM STAT = 001). The MSI is connected to MI\_TxMSI. The ODUk PM APS is connected to PI\_APS. The ODUk OH block is connected to a clock generator (ODCa) via a 1/256 divider and a 1/122368 divider. The clock generator outputs AI\_D, AI\_MFS, AI\_FS, and AI\_CK signals. The entire system is labeled ODUkP/ODU[i]j\_A\_So\_MP on the right. The bottom section is labeled ODUk\_PP and the overall output section is labeled ODUkP\_AP. The diagram is identified by the code G.798(17)\_F14-55. + +Block diagram of ODUkP/ODU[i]j\_A\_So processes showing client-specific processes, a multiplexer, and a multiplex structure with various control signals and a clock generator. + +Figure 14-55 – ODUkP/ODU[i]j\_A\_So processes + +![Figure 14-56 – ODUkP/ODUj[i]j_A_So client specific processes. This block diagram illustrates the internal processing of client signals within an ODUj_CP[p] container. The container is divided into two main sections: CI_MFS, CI_FS, CI_CK on the left, and CI_D, CI_APS on the right. The CI_MFS, CI_FS, and CI_CK signals are inputs to an 'ODU-LCK generator'. The output of the generator is split into 'LCK' and 'Normal' paths, which are then combined by a 'Select normal/LCK' block. This block also receives an external 'MI_AdminState[p]' signal. The output of the 'Select normal/LCK' block is fed into the 'FAS/MFAS insertion' block. The 'CI_D' signal is also input to the 'FAS/MFAS insertion' block. The output of the 'FAS/MFAS insertion' block is split into 'CK' and 'D' paths. The 'CK' path is input to an 'Elastic store' (represented by a circular buffer icon). The 'D' path is input to the 'Elastic store' via a 'WR' (write) signal. The 'Elastic store' has 'WR' and 'RD' (read) signals. The 'RD' signal is input to a 'Justification control and JC generation' block. This block also receives 'JC' (justification control) signals from the 'Elastic store'. The output of the 'Justification control and JC generation' block is fed into the 'ODUj APS' block. The 'ODUj APS' block also receives external 'MI_APS_EN[p]' and 'MI_APS_LVL[p]' signals. The output of the 'ODUj APS' block is fed into the 'CI_APS' signal. The entire process is labeled 'G.798(17)_F14-56'.](bd0fe87fe6e236bc4778830b4f26d9e2_img.jpg) + +Figure 14-56 – ODUkP/ODUj[i]j\_A\_So client specific processes. This block diagram illustrates the internal processing of client signals within an ODUj\_CP[p] container. The container is divided into two main sections: CI\_MFS, CI\_FS, CI\_CK on the left, and CI\_D, CI\_APS on the right. The CI\_MFS, CI\_FS, and CI\_CK signals are inputs to an 'ODU-LCK generator'. The output of the generator is split into 'LCK' and 'Normal' paths, which are then combined by a 'Select normal/LCK' block. This block also receives an external 'MI\_AdminState[p]' signal. The output of the 'Select normal/LCK' block is fed into the 'FAS/MFAS insertion' block. The 'CI\_D' signal is also input to the 'FAS/MFAS insertion' block. The output of the 'FAS/MFAS insertion' block is split into 'CK' and 'D' paths. The 'CK' path is input to an 'Elastic store' (represented by a circular buffer icon). The 'D' path is input to the 'Elastic store' via a 'WR' (write) signal. The 'Elastic store' has 'WR' and 'RD' (read) signals. The 'RD' signal is input to a 'Justification control and JC generation' block. This block also receives 'JC' (justification control) signals from the 'Elastic store'. The output of the 'Justification control and JC generation' block is fed into the 'ODUj APS' block. The 'ODUj APS' block also receives external 'MI\_APS\_EN[p]' and 'MI\_APS\_LVL[p]' signals. The output of the 'ODUj APS' block is fed into the 'CI\_APS' signal. The entire process is labeled 'G.798(17)\_F14-56'. + +**Figure 14-56 – ODUkP/ODUj[i]j\_A\_So client specific processes** + +### Specific processes + +The specific processes are performed independently for each ODUj [and ODUi] client signal that is multiplexed into the ODUk. The specific processes perform the mapping of the ODUj[i] into an ODTUjk[ik]. + +**FAS/MFAS insertion:** The function shall extend the ODUj[i] with the frame alignment overhead (FAS and MFAS) in row one, bytes 1 to 7, as described in clause 15.6.2 of [ITU-T G.709]. Bytes 8 to 14 of row one are set to all-ZEROs. + +**Mapping, frequency justification and bit-rate adaptation:** The function shall provide an elastic store (buffer) process for the ODUj[i] client signal. The data signal ODUj[i]\_CI shall be written into the buffer under the control of the associated input clock. The data shall be read out of the buffer and written onto the D, NJO, PJO1 and PJO2 bytes of the selected ODTUjk[ik] frame under the control of the ODUk clock and justification decisions, as defined in clause 19.5 of [ITU-T G.709]. + +A justification decision shall be performed every second frame for the ODTU01, every fourth frame for the ODTU12, every sixteenth frame for the ODTU13 and four times every sixteen frames for the ODTU23. Each justification decision results in a corresponding double positive, positive, negative or no justification action. Upon a double positive justification action, the reading of two data bytes out of the buffer shall be cancelled once. No ODUj[i] data shall be written onto the PJO2, PJO1 or NJO bytes. Upon a positive justification action, the reading of one data byte out of the buffer shall be cancelled once. No ODUj[i] data shall be written onto the PJO1 or NJO bytes and data shall be written onto the PJO2 byte. Upon a negative justification action, one extra data byte shall be read once out of the buffer. ODUj[i] data shall be written onto the PJO2, PJO1 and NJO bytes. If no justification action is to be performed, ODUj[i] data shall be written onto the PJO2 and PJO1 bytes. + +and no ODUj[i] data shall be written onto the NJO byte. The ODUk frame that contains the PJO2, PJO1 and NJO bytes depends on the time slot(s) of the ODTUjk[i/k]. + +The justification decisions determine the phase error introduced by the function. + +*Buffer size:* In the presence of jitter as specified by [ITU-T G.8251] and a frequency within the range $239/(239 - j[i]) \times 4^{(j[i]-1)} \times 2\,488\,320\text{ kHz} \pm 20\text{ ppm}$ ( $j = 1, 2; i = 1$ ) and $1\,244\,160\text{ kHz} \pm 20\text{ ppm}$ ( $j = 0$ ), this mapping process shall not introduce any errors. The maximum buffer hysteresis, and therefore the maximum phase error introduced, shall be as listed in Table 14-24. + +**Table 14-24 – Maximum buffer hysteresis** + +| Mapping | Maximum buffer hysteresis | +|---------------------|---------------------------| +| ODU0 → ODU1 | 1 byte | +| ODU1 → ODU2 or ODU3 | 2 bytes | +| ODU2 → ODU3 | 8 bytes | + +**JC:** The function shall generate the justification control bits based on the justification decision (double positive, positive, negative, none) according to the specification in clause 19.5 of [ITU-T G.709]. It shall insert the justification control bits in bit 7 and 8 of all three JC bytes of the frame in which the justification is performed. The remaining (RES) bits of the JC byte shall be set to all-ZEROs. The ODUk frame that contains the JC bytes depends on the time slot(s) of the ODTUjk[i/k]. + +**ODUj[i] server layer APS:** When APS is enabled for tributary signal #p (MI\_APS\_EN[p] is true), the function shall insert the CI\_APS value into the ODU APS/PCC[MI\_APS\_LVL[p]] field, which is available once per eight ODU frames when the value of the MFAS bits 6, 7, 8 is equal to MI\_APS\_LVL[p]. + +**NOTE –** The ODUj[i] server layer section APS information may be present in the case where the ODUj[i] signal contains an ODU-AIS, ODU-LCK or ODU-OCI maintenance signal. The ODU-LCK maintenance signal may be inserted in this adaptation source function. ODUj[i] SNC/I protection is unable to detect the insertion of such ODU-LCK and will not perform a protection switch. + +**ODU-LCK:** The function shall generate the ODU-LCK signal as defined in clause 16.5 of [ITU-T G.709]. The clock, frame start and multiframe start are defined by the incoming ODUk signal. + +**Selector:** The normal signal for a tributary signal #p may be replaced by the ODU-LCK signal. ODU-LCK signal is selected if the MI\_AdminState [p] is LOCKED. + +### Common processes + +**Clock and (multi)frame start signal generation:** The function shall generate a local ODUk clock (ODUKP\_AI\_CK) of $239/(239 - k) \times 4^{(k-1)} \times 2\,488\,320\text{ kHz} \pm 20\text{ ppm}$ from a free-running oscillator. The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUk signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +**Multiplexing:** The function assigns the individual ODTUjk[i/k] to specific time slots of the OPUk payload area as defined by the multiplex structure (see clauses 19.3 and 19.4.1 of [ITU-T G.709]). + +**MSI:** The function shall insert the TxMSI into the MSI byte positions of the PSI overhead as defined in clause 19.4 of [ITU-T G.709]. The TxMSI value, and as such the multiplex structure, is either fixed or configurable via MI\_TxMSI as shown in Table 14-25. + +**PT:** The function shall insert code "0010 0000" (ODU multiplex structure) into the PT byte position of the PSI overhead as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**ODUk PM APS:** The function shall insert the PI\_APS value into the ODUk path APS/PCC field, which is available once per eight ODUk frames when MFAS bits 6, 7, 8 are 000. + +**RES:** The function shall insert all-ZEROs into the RES bytes. + +All other bits of the ODUk overhead should be sourced as "0"s, except the PMOH STAT field which should be set to the value "normal path signal" (001). + +**Table 14-25 – Multiplex structure configuration and TxMSI values** + +| Function | Multiplex structure | TxMSI value for fixed multiplex structure | +|---------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODU1P/ODU0_A | Fixed
2 ODU0 → ODU1 | 11 000000
11 000001 | +| ODU2P/ODU1_A | Fixed
4 ODU1 → ODU2 | 00 000000
00 000001
00 000010
00 000011 | +| ODU3P/ODU1_A | Fixed
16 ODU1 → ODU3 | 00 000000
00 000001
00 000010
00 000011
00 000100
00 000101
00 000110
00 000111
00 001000
00 001001
00 001010
00 001011
00 001100
00 001101
00 001110
00 001111 | +| ODU3P/ODU2_A | Fixed
4 ODU2 → ODU3 | 01 000000
01 000001
01 000010
01 000011
01 000000
01 000001
01 000010
01 000011
01 000000
01 000001
01 000010
01 000011
01 000000
01 000001
01 000010
01 000011 | +| ODU3P/ODU12_A | Configured via MI_TxMSI | – | + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.3.9.2 ODUkP to ODU[i]j adaptation sink function (ODUkP/ODU[i]j\_A\_Sk) + +The ODUkP/ODU[i]j\_A\_Sk function extracts the OPUk overhead (PT, MSI, RES) and monitors the reception of the correct payload type. It demultiplexes the individual ODTUjk[/ik] from the payload area of the OPUk and recovers the $n \times \text{ODUj}$ [and $m \times \text{ODUi}$ ] client signals using the justification control information (JC overhead). It determines the frame and multiframe structure of the ODUj[/i]. It provides access to ODUk PM APS overhead. It provides access to the ODUj [/i] APS overhead. + +The information flow and processing of the ODUkP/ODU[i]j\_A\_Sk function is defined with reference to Figures 14-57, 14-58 and 14-59. + +#### Symbol + +![Diagram of the ODUkP/ODU[i]j_A_Sk function symbol. The symbol is a trapezoid labeled 'ODUkP/ODU[i]j'. On the left, two input arrows are labeled 'ODUkP/ODU[i]j_A_Sk_MP' and 'ODUk_PP'. On the right, an input arrow is labeled 'ODUkP_AP'. Above the symbol, multiple output arrows represent tributary ports. These are grouped into two sets: 'ODUj_CPs' with ports 1, 2, ..., n; and '[ODUi_CPs]' with ports 1, 2, ..., m. The label 'Tributary port' is above the first two ports. A reference label 'G.798(17)_F14-57' is at the bottom right of the symbol.](e579f4085bfb7766ce76d03036f97e36_img.jpg) + +``` + +graph TD + subgraph Symbol + F[ODUkP/ODU[i]j] + end + MP([ODUkP/ODU[i]j_A_Sk_MP]) <--> F + PP([ODUk_PP]) --> F + AP([ODUkP_AP]) --> F + F --> CPj1([ODUj_CPs 1]) + F --> CPj2([ODUj_CPs 2]) + F --> CPjn([ODUj_CPs n]) + F --> CPi1([ODUi_CPs 1]) + F --> CPi2([ODUi_CPs 2]) + F --> CPim([ODUi_CPs m]) + +``` + +Diagram of the ODUkP/ODU[i]j\_A\_Sk function symbol. The symbol is a trapezoid labeled 'ODUkP/ODU[i]j'. On the left, two input arrows are labeled 'ODUkP/ODU[i]j\_A\_Sk\_MP' and 'ODUk\_PP'. On the right, an input arrow is labeled 'ODUkP\_AP'. Above the symbol, multiple output arrows represent tributary ports. These are grouped into two sets: 'ODUj\_CPs' with ports 1, 2, ..., n; and '[ODUi\_CPs]' with ports 1, 2, ..., m. The label 'Tributary port' is above the first two ports. A reference label 'G.798(17)\_F14-57' is at the bottom right of the symbol. + +**Figure 14-57 – ODUkP/ODU[i]j\_A\_Sk function** + +## Interfaces + +Table 14-26 – ODUkP/ODU[i]j\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_MFS
ODUkP_AI_TSF
ODUkP_AI_TSD
ODUkP/ODU[i]j_A_Sk_MP:
ODU3P/ODU12_A_Sk_MI_ExMSI[1..(n+m)]
ODUkP/ODU[i]j_A_Sk_MI_AdminState[1..(n+m)]
ODUkP/ODU[i]j_A_Sk_MI_APS_EN[1..(n+m)]
ODUkP/ODU[i]j_A_Sk_MI_APS_LVL[1..(n+m)] | n × ODUj_CP:
ODUj_CI_CK
ODUj_CI_D
ODUj_CI_FS
ODUj_CI_MFS
ODUj_CI_SSF
ODUj_CI_SSD
ODUj_CI_APS
m × ODUi_CP: (Note)
ODUi_CI_CK
ODUi_CI_D
ODUi_CI_FS
ODUi_CI_MFS
ODUi_CI_SSF
ODUj_CI_SSD
ODUi_CI_APS
ODUk_PP:
ODUk_PI_APS
ODUk_PI_TSF
ODUk_PI_TSD
ODUkP/ODU[i]j_A_Sk_MP:
ODUkP/ODU[i]j_A_Sk_MI_cPLM
ODUkP/ODU[i]j_A_Sk_MI_cMSIM[1..(n+m)]
ODUkP/ODU[i]j_A_Sk_MI_AcPT
ODUkP/ODU[i]j_A_Sk_MI_AcMSI[1..(n+m)]
ODUkP/ODU[i]j_A_Sk_MI_cLOFLOM [1..(n+m)] | +| NOTE – For ODU3P/ODU12_A_Sk only. | | + +## Processes + +The processes associated with the ODUkP/ODU[i]j\_A\_Sk function are specific processes for each ODUj[i]j\_CP and common processes for the compound (multiplexed) signal as depicted in Figures 14-58 and 14-59. + +![Figure 14-58 – ODUkP/ODU[i]j_A_Sk processes. This block diagram illustrates the internal architecture of an ODUkP/ODU[i]j_A_Sk sink adaptation function. It shows the demultiplexing of an ODUk signal into multiple ODUj signals. The process includes MSI (Multiplex Structure Identifier) extraction and processing, PT (Payload Type) extraction and processing, and ODUk Path Monitoring APS (Automatic Protection Switching) processing. Defect correlations are performed to generate management information (MI) signals. The diagram details the flow of various signals including Adaptation Information (AI), Characteristic Information (CI), and Management Information (MI).](d5de4c1d2f0b71aa339b6b2118268fbb_img.jpg) + +``` + +graph TD + subgraph ODUkP_AP + AI_MFS --> MFS_bus + AI_FS --> FS_bus + AI_CK --> CK_bus + AI_D --> D_bus + AI_TSF --> TSF_bus + AI_TSD --> TSD_bus + end + + MFS_bus --> Demux + FS_bus --> Demux + CK_bus --> Demux + D_bus --> Demux + + D_bus --> Extract_MSI + Extract_MSI --> MSI_proc + MSI_proc --> MI_ExMSI + MSI_proc --> MI_AcMSI + MSI_proc --> dMSIM_bus + + D_bus --> Extract_PT + Extract_PT --> PT_proc + PT_proc --> MI_AcPT + PT_proc --> dPLM_signal + + D_bus --> ODUk_PM_APS + ODUk_PM_APS --> PI_APS + TSF_bus --> PI_TSF + TSD_bus --> PI_TSD + + Demux --> Client_Proc_1 + Demux --> Client_Proc_N + + dMSIM_bus --> Client_Proc_1 + dMSIM_bus --> Client_Proc_N + dPLM_signal --> Client_Proc_1 + dPLM_signal --> Client_Proc_N + TSF_bus --> Client_Proc_1 + TSF_bus --> Client_Proc_N + TSD_bus --> Client_Proc_1 + TSD_bus --> Client_Proc_N + + subgraph Defect_Correlations + AI_TSF_in --> DC + dPLM_in --> DC + DC --> MI_PLM + DC --> MI_cMSIM + DC --> MI_cLOFLOM + end + + Client_Proc_1 --> CI_ODUj_1 + Client_Proc_N --> CI_ODUj_N + +``` + +The diagram illustrates the internal architecture of an ODUkP/ODU[i]j\_A\_Sk process. At the top, multiple client-specific processes are shown, each with inputs like AI\_TSD, AI\_TSF, and dPLM, and outputs like dMSIM[1], MI\_cMSIM[1], MI\_cLOFLOM[1], MI\_AdminState[1], MI\_APS\_EN[1], and MI\_APS\_LVL[1]. These are connected to a central Demultiplexer. Below the demultiplexer, there are three parallel processing paths: 'Extract MSI' leading to an 'MSI process' which outputs MI\_ExMSI[1..(n+m)] and MI\_AcMSI[1..(n+m)]; 'Extract PT' leading to a 'PT process' which outputs MI\_AcPT; and 'ODUk PM APS' which outputs PI\_APS, PI\_TSF, and PI\_TSD. A 'Defect correlations' block receives AI\_TSF and dPLM inputs and outputs MI\_PLM, MI\_cMSIM[1..(n+m)], MI\_cLOFLOM[1..(n+m)], MI\_AdminState[1..(n+m)], MI\_APS\_EN[1..(n+m)], and MI\_APS\_LVL[1..(n+m)]. The bottom section shows the ODUkP\_AP layer with inputs AI\_MFS, AI\_FS, AI\_CK, AI\_D, AI\_TSF, and AI\_TSD. The entire diagram is labeled with G.798(17)\_F14-58 and includes various signal labels like CI\_MFS, CI\_FS, CI\_CK, CI\_D, CI\_APS, CI\_SSF, and CI\_SSD at the top. + +Figure 14-58 – ODUkP/ODU[i]j\_A\_Sk processes. This block diagram illustrates the internal architecture of an ODUkP/ODU[i]j\_A\_Sk sink adaptation function. It shows the demultiplexing of an ODUk signal into multiple ODUj signals. The process includes MSI (Multiplex Structure Identifier) extraction and processing, PT (Payload Type) extraction and processing, and ODUk Path Monitoring APS (Automatic Protection Switching) processing. Defect correlations are performed to generate management information (MI) signals. The diagram details the flow of various signals including Adaptation Information (AI), Characteristic Information (CI), and Management Information (MI). + +**Figure 14-58 – ODUkP/ODU[i]j\_A\_Sk processes** + +![Figure 14-59 – ODUkP/ODU[i]j_A_Sk client specific processes. This block diagram illustrates the internal processes of an ODU client. At the top, a bracket labeled 'ODUj_CP[p]' groups four output signals: 'CI_MFS', 'CI_FS', 'CI_CK', and 'CI_D'. Below this, a 'Select normal/AIS/LCK' block contains 'Normal', 'AIS', and 'LCK' options, with 'Generate AIS' and 'Generate LCK' blocks feeding into it. To the right, 'Consequent actions' blocks receive 'aAIS', 'aSSF', and 'aSSD' signals and output 'AI_TSD' and 'AI_TSF' signals. Further right, 'dPLM', 'dMSIM[p]', and 'dLOFLOM' signals feed into 'Defect correlations', which output 'dPLM', 'dMSIM[p]', 'MI_cMSIM[p]', and 'MI_cLOFLOM[p]' signals. The central part of the diagram shows 'Frame/multi-frame alignment' receiving 'MFS', 'FS', 'CK', and 'D' signals. Below it, an 'Elastic store' block with 'RD' (read) and 'WR' (write) ports is connected to 'Clock generation (ODCp)'. 'Justification control' and 'Extract JC' blocks are also connected to the 'Elastic store'. At the bottom, input signals 'MFS', 'FS', 'CK', 'D', 'TS#', and 'Active' are shown. Various management interfaces are labeled on the right, such as 'MI_AdminState[p]', 'MI_APS_EN[p]', 'MI_APS_LVL[p]', and 'AI_TSF'. A small label 'G.798(17)_F14-59' is at the bottom right of the diagram area.](0fdef87ff1fd322c626d1ff8df725749_img.jpg) + +Figure 14-59 – ODUkP/ODU[i]j\_A\_Sk client specific processes. This block diagram illustrates the internal processes of an ODU client. At the top, a bracket labeled 'ODUj\_CP[p]' groups four output signals: 'CI\_MFS', 'CI\_FS', 'CI\_CK', and 'CI\_D'. Below this, a 'Select normal/AIS/LCK' block contains 'Normal', 'AIS', and 'LCK' options, with 'Generate AIS' and 'Generate LCK' blocks feeding into it. To the right, 'Consequent actions' blocks receive 'aAIS', 'aSSF', and 'aSSD' signals and output 'AI\_TSD' and 'AI\_TSF' signals. Further right, 'dPLM', 'dMSIM[p]', and 'dLOFLOM' signals feed into 'Defect correlations', which output 'dPLM', 'dMSIM[p]', 'MI\_cMSIM[p]', and 'MI\_cLOFLOM[p]' signals. The central part of the diagram shows 'Frame/multi-frame alignment' receiving 'MFS', 'FS', 'CK', and 'D' signals. Below it, an 'Elastic store' block with 'RD' (read) and 'WR' (write) ports is connected to 'Clock generation (ODCp)'. 'Justification control' and 'Extract JC' blocks are also connected to the 'Elastic store'. At the bottom, input signals 'MFS', 'FS', 'CK', 'D', 'TS#', and 'Active' are shown. Various management interfaces are labeled on the right, such as 'MI\_AdminState[p]', 'MI\_APS\_EN[p]', 'MI\_APS\_LVL[p]', and 'AI\_TSF'. A small label 'G.798(17)\_F14-59' is at the bottom right of the diagram area. + +**Figure 14-59 – ODUkP/ODU[i]j\_A\_Sk client specific processes** + +### Common processes + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. + +**MSI:** The function shall extract the MSI from the PSI overhead as defined in clause 8.7.2.1. The accepted MSI for a tributary signal #p (AcMSI[p]) is available at the MP (MI\_AcMSI[p]). The multiplex structure is defined by ExMSI[p], which is either fixed or is configurable via MI\_ExMSI[p] as shown in Table 14-27. + +**RES:** The value in the RES bytes shall be ignored. + +**ODUk PM APS:** The function shall extract the information from the ODUk path APS/PCC field, which is available once per eight ODUk frames when MFAS bits 6, 7, 8 are 000 and apply this to the PI\_APS. + +**Demultiplexing:** The function activates the ODTUjk[/ik] and assigns the time slots of the ODUk payload area to the individual ODTUjk[/ik] as defined by the multiplex structure (see clauses 19.3 and 19.4.1 of [ITU-T G.709]). + +**Table 14-27 – Multiplex structure configuration and ExMSI values** + +| Function | Multiplex structure | ExMSI value for fixed multiplex structure | +|---------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODU1P/ODU0_A | Fixed
2 ODU0 → ODU1 | 11 000000
11 000001 | +| ODU2P/ODU1_A | Fixed
4 ODU1 → ODU2 | 00 000000
00 000001
00 000010
00 000011 | +| ODU3P/ODU1_A | Fixed
16 ODU1 → ODU3 | 00 000000
00 000001
00 000010
00 000011
00 000100
00 000101
00 000110
00 000111
00 001000
00 001001
00 001010
00 001011
00 001100
00 001101
00 001110
00 001111 | +| ODU3P/ODU2_A | Fixed
4 ODU2 → ODU3 | 01 000000
01 000001
01 000010
01 000011
01 000000
01 000001
01 000010
01 000011
01 000000
01 000001
01 000010
01 000011
01 000000
01 000001
01 000010
01 000011 | +| ODU3P/ODU12_A | Configured via MI_ | – | + +### Specific processes + +The specific processes are performed independently for each ODUj [and ODUi] client signal that is multiplexed into the ODUk. The specific processes recover the ODUj[/i] from the ODTUjk[/ik]. + +**JC:** The function shall interpret the justification control information in bits 7 and 8 of the JC bytes as defined in clause 19.5 of [ITU-T G.709] in order to determine the justification action (double positive, positive, negative, none) for the current frame. A two out of three majority decision is used. RES bits + +in the JC bytes shall be ignored. The ODUk frame that contains the JC bytes depends on the time slot(s) of the ODTUjk[/ik]. + +**Demapping, CBR clock generation:** The function shall provide an elastic store (buffer) process. The ODUj[/i] data shall be written into the buffer from the D, NJO, PJO1 and PJO2 bytes in the ODTUjk[/ik] frame. The information extraction of the PJO2, PJO1 and NJO bytes shall be under the control of the justification control information. The ODUj[/i] data (CI\_D) shall be read out of the buffer under the control of the ODUj[/i] clock (CI\_CK). + +Upon a double positive justification action, the writing of two data bytes into the buffer shall be cancelled once. No ODUj[/i] data shall be read from the PJO2, PJO1 or NJO bytes. Upon a positive justification action, the writing of one data byte into the buffer shall be cancelled once. No ODUj[/i] data shall be read from the PJO1 or NJO bytes and data shall be read from the PJO2 byte. Upon a negative justification action, one extra data byte shall be written into the buffer once. ODUj[/i] data shall be read from the PJO2, PJO1 and NJO bytes. If no justification action is to be performed, ODUj[/i] data shall be read from the PJO2 and PJO1 bytes and no ODUj[/i] data shall be read from the NJO bytes. The ODUk frame that contains the PJO2, PJO1 and NJO bytes depends on the time slot(s) of the ODTUjk[/ik]. + +*Smoothing and jitter limiting process:* The function shall provide for a clock smoothing and elastic store (buffer) process. The $239/(239 - j[i]) \times 4^{(j[i]-1)} \times 2\ 488\ 320$ kbit/s (j = 1, 2; i = 1) and 1 244 160 kHz ± 20 ppm (j = 0) data signal shall be written into the buffer under the control of the associated (gapped) input clock (with a frequency accuracy within ± 20 ppm). The data signal shall be read out of the buffer under the control of a smoothed (equally spaced) $239/(239 - j[i]) \times 4^{(j[i]-1)} \times 2\ 488\ 320$ kbit/s ± 20 ppm (j = 1, 2; i = 1) and 1 244 160 kHz ± 20 ppm (j = 0) clock (the rate is determined by the ODUj[/i] signal at the input of the remote ODUkP/ODU[i]j\_A\_So). + +The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCp clock), apply. + +**Buffer size:** In the presence of jitter as specified by [ITU-T G.8251] and a frequency within the range $239/(239 - j[i]) \times 4^{(j[i]-1)} \times 2\ 488\ 320$ kbit/s ± 20 ppm (j = 1, 2; i = 1) and 1 244 160 kHz ± 20 ppm (j = 0), this justification process shall not introduce any errors. + +Following a step in frequency of the $239/(239 - j[i]) \times 4^{(j[i]-1)} \times 2\ 488\ 320$ kbit/s (j = 1, 2; i = 1) and 1 244 160 kHz ± 20 ppm (j = 0) signal transported (for example, due to reception of ODUj[/i]\_CI from a new ODUj[/i]\_TT\_So at the far end or removal of a ODU AIS signal with a frequency offset), there will be a maximum recovery time of X seconds after which this process shall not generate any bit errors. The value of X is for further study; a value of one second has been proposed. + +**Frame and multiframe alignment:** The function shall perform frame and multiframe alignment as described in clause 8.2.3. + +**ODUj[/i]-LCK, ODUj[/i]-AIS:** The function shall generate the ODUj[/i]-LCK and ODUj[/i]-AIS signals as defined in [ITU-T G.709]. The clock, frame start and multiframes start shall be independent from the incoming clock. The clock has to be within $239/(239 - j[i]) \times 4^{(j[i]-1)} \times 2\ 488\ 320$ kHz ± 20 ppm (j = 1, 2; i = 1) and 1 244 160 kHz ± 20 ppm (j = 0). Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +**Selector:** The normal signal for a tributary signal #p may be replaced by either the ODUj[/i]-AIS or ODUj[/i]-LCK signal. ODUj[/i]-LCK is selected if the corresponding MI\_AdminState[p] signal is LOCKED. ODUj[/i]-AIS is selected if the corresponding MI\_AdminState[p] signal is not LOCKED and aAIS is true. + +**ODUj[i] server layer APS:** When APS is enabled for tributary signal #p (MI\_APS\_EN[p] is true), the function shall extract the information from the ODU APS/PCC[MI\_APS\_LVL[p]] field, which is available once per eight ODU frames when the value of the MFAS bits 6, 7, 8 is equal to MI\_APS\_LVL[p], and apply the extracted information to the CI\_APS. + +NOTE – The ODUj[i] server layer section APS information may be present in the case where the ODUj[i] signal contains an ODU-AIS, ODU-LCK or ODU-OCI maintenance signal. The ODU-LCK maintenance signal may have been inserted in the far-end adaptation source function. ODUj[i] SNC/I protection is unable to detect the insertion of such ODU-LCK and will not perform a protection switch. + +### Defects + +The function shall detect dPLM, dMSIM and dLOFLOM. + +**dPLM:** See clause 6.2.4.1. The expected payload type is "0010 0000" (ODU multiplex structure) as defined in [ITU-T G.709]. + +For each ODUj[i] tributary port #p: + +**dMSIM[p]:** See clause 6.2.9.1. dMSIM is detected per active ODUj[i]. + +**dLOFLOM[p]:** See clause 6.2.5.3. dLOFLOM is detected per active ODUj[i]. + +### Consequent actions + +$PI\_TSF \leftarrow AI\_TSF$ + +$PI\_TSD \leftarrow AI\_TSD$ + +For each ODUj[i] tributary port #p: + +$aSSF \leftarrow ((AI\_TSF \text{ or } dPLM \text{ or } dMSIM[p] \text{ or } dLOFLOM[p]) \text{ and } (\text{not } MI\_AdminState[p] = \text{LOCKED}))$ + +$aSSD \leftarrow AI\_TSD \text{ and } (\text{not } MI\_AdminState[p] = \text{LOCKED})$ + +$aAIS \leftarrow ((AI\_TSF \text{ or } dPLM \text{ or } dMSIM[p] \text{ or } dLOFLOM[p]) \text{ and } (\text{not } MI\_AdminState[p] = \text{LOCKED}))$ + +On declaration of aAIS, the function shall output an all-ONEs pattern/signal within two frames. On clearing aAIS, the all-ONEs pattern/signal shall be removed within two frames, with normal data being output. The AIS clock, frame start and multiframe start shall be independent from the incoming clock, frame start and multiframe start. The AIS clock has to be within $239/(239 - j[i]) \times 4^{(i-1)} \times 2\,488\,320 \text{ kHz} \pm 20 \text{ ppm}$ ( $j = 1, 2; i = 1$ ) and $1\,244\,160 \text{ kHz} \pm 20 \text{ ppm}$ ( $j = 0$ ). Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +### Defect correlations + +$cPLM \leftarrow dPLM \text{ and } (\text{not } AI\_TSF)$ + +For each ODUj[i] tributary port #p: + +$cMSIM[p] \leftarrow dMSIM[p] \text{ and } (\text{not } dPLM) \text{ and } (\text{not } AI\_TSF)$ + +$cLOFLOM[p] \leftarrow dLOFLOM[p] \text{ and } (\text{not } dPLM) \text{ and } (\text{not } AI\_TSF)$ + +**Performance monitoring:** None. + +### 14.3.10 ODUkP to ODUj payload type 21 adaptation function (ODUkP/ODUj-21\_A) + +The ODUkP to ODUj payload type 21 adaptation functions perform the adaptation between the ODUkP ( $k = 2, 3, 4, 25u, 25, 50u, 50$ ) layer adapted information and the characteristic information of ODUj ( $j = 0, 1, 2, 2e, 3, \text{flex}$ ) signals. + +![Diagram of the ODUkP/ODUj-21_A function. A central trapezoidal block labeled 'ODUkP/ODUj-21' has multiple tributary ports at the top, labeled 'Tributary port' and 'ODUj_CPs' with sub-labels 1, 2, ..., n. Each port has a double-headed vertical arrow. At the bottom, a single double-headed vertical arrow points to a label 'ODUkP_AP'. The text 'G.798(17)_F14-60' is in the bottom right corner.](32fef1546b300cd971dacf02ca1d21d7_img.jpg) + +Diagram of the ODUkP/ODUj-21\_A function. A central trapezoidal block labeled 'ODUkP/ODUj-21' has multiple tributary ports at the top, labeled 'Tributary port' and 'ODUj\_CPs' with sub-labels 1, 2, ..., n. Each port has a double-headed vertical arrow. At the bottom, a single double-headed vertical arrow points to a label 'ODUkP\_AP'. The text 'G.798(17)\_F14-60' is in the bottom right corner. + +**Figure 14-60 – ODUkP/ODUj-21\_A function** + +Three different types of functions are possible: + +- the ODU2P/ODUj-21\_A performs multiplexing/demultiplexing of any LO ODU with a bit rate less than the OPU2 payload bit rate into an OPU2; +- the ODU3P/ODUj-21\_A performs multiplexing/demultiplexing of any LO ODU with a bit rate less than the OPU3 payload bit rate into an OPU3; +- the ODU4P/ODUj-21\_A performs multiplexing/demultiplexing of any LO ODU with a bit rate less than the OPU4 payload bit rate into an OPU4; +- the ODU25(u)P/ODUj-21\_A performs multiplexing/demultiplexing of any LO ODU with a bit rate less than the OPU25(u) payload bit rate into an OPU25(u); +- the ODU50(u)P/ODUj-21\_A performs multiplexing/demultiplexing of any LO ODU with a bit rate less than the OPU50(u) payload bit rate into an OPU50(u). + +Tributary ports are dynamically created and deleted under the control of management. Each tributary port is associated with one ODUj connection point on one hand, and M OPUk tributary slots on the other hand. The multiplex structure identifier (MSI) carries the configuration of tributary ports to tributary slots. + +**14.3.10.1 ODUkP to ODUj payload type 21 adaptation source function (ODUkP/ODUj-21\_A\_So)** + +The ODUkP/ODUj-21\_A\_So function creates the ODUk signal from a free-running clock. It asynchronously maps the ODUj client signal from the $n \times$ ODUj CPs into ODTUjk or ODTUk.M including justification control (JC) information. The ODTUjk and ODTUk.M are multiplexed into the tributary slots of the OPUk. It adds OPUk overhead (RES, PT, MSI, OMFI) and default ODUk overhead. It provides access to ODUk PM APS overhead. It provides access to the ODUj APS overhead. + +The information flow and processing of the ODUkP/ODUj-21\_A\_So function is defined with reference to Figures 14-61 and 14-62. + +**Symbol** + +![Diagram of the ODUkP/ODUj-21_A_So function. A central trapezoidal block labeled 'ODUkP/ODUj-21' has multiple tributary ports at the top, labeled 'Tributary port' and 'ODUj_CPs' with sub-labels 1, 2, ..., n. Each port has a double-headed vertical arrow. On the left, two double-headed horizontal arrows point to labels 'ODUkP/ODUj-21_A_So_MP' and 'ODUkP_PP'. On the right, two double-headed horizontal arrows point to labels 'ODUkP/ODUj-21_A_So_RP' and 'ODUk_TP'. At the bottom, a single double-headed vertical arrow points to a label 'ODUkP_AP'. The text 'G.798(17)_F14-61' is in the bottom right corner.](8862d966c9597ffc01bd5013ca9885bb_img.jpg) + +Diagram of the ODUkP/ODUj-21\_A\_So function. A central trapezoidal block labeled 'ODUkP/ODUj-21' has multiple tributary ports at the top, labeled 'Tributary port' and 'ODUj\_CPs' with sub-labels 1, 2, ..., n. Each port has a double-headed vertical arrow. On the left, two double-headed horizontal arrows point to labels 'ODUkP/ODUj-21\_A\_So\_MP' and 'ODUkP\_PP'. On the right, two double-headed horizontal arrows point to labels 'ODUkP/ODUj-21\_A\_So\_RP' and 'ODUk\_TP'. At the bottom, a single double-headed vertical arrow points to a label 'ODUkP\_AP'. The text 'G.798(17)\_F14-61' is in the bottom right corner. + +**Figure 14-61 – ODUkP/ODUj-21\_A\_So function** + +## Interfaces + +**Table 14-28 – ODUP/ODUj-21\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n × ODUj_CP:
ODUj_CI_CK
ODUj_CI_D
ODUj_CI_FS
ODUj_CI_MFS
ODUj_CI_APS
ODUk_PP:
ODUk_PI_APS
ODUk_TP:
ODUk_TI_CK
ODUP/ODUj-21_A_So_MP:
ODUP/ODUj-21_A_So_MI_TxMSI
ODUP/ODUj-21_A_So_MI_AutoPayloadtype (Note)
ODUP/ODUj-21_A_So_MI_ODUType_Rate[1..n]
ODUP/ODUj-21_A_So_MI_AdminState[1..n]
ODUP/ODUj-21_A_So_MI_APS_EN[1..n]
ODUP/ODUj-21_A_So_MI_APS_LVL[1..n]
ODUP/ODUj-21_A_So_RP:
ODUP/ODUj-21_A_So_RI_AcPT (Note) | ODUP_AP:
ODUP_AI_CK
ODUP_AI_D
ODUP_AI_FS
ODUP_AI_MFS
ODUP/ODUj-21_A_So_RP:
ODUP/ODUj-21_A_So_RI_TrPT (Note)
ODUP/ODUj-21_A_So_MP:
ODUP/ODUj-21_A_So_MI_TrPT (Note) | +| NOTE – For ODU2P/ODUj-21_A_So and ODU3P/ODUj-21_A_So only. | | + +## Processes + +The processes associated with the ODUP/ODUj-21\_A\_So function are specific processes for each ODUj\_CP and common processes for the compound (multiplexed) signal as depicted in Figures 14-62 and 14-63. + +![Block diagram of ODUkP/ODUj-21_A_So processes showing client processes, multiplexing, and clock generation.](773bb1698c96c3aea54d138ddcc7cfd5_img.jpg) + +The diagram illustrates the ODUkP/ODUj-21\_A\_So processes. At the top, multiple client processes (ODUj\_CP[1] to ODUj\_CP[n]) are shown. Each client process has inputs: CL\_MFS, CL\_FS, CL\_CK, CL\_D, and CL\_APS. It has outputs: MI\_AdminState[i], MI\_APS\_EN[i], MI\_APS\_LVL[i], and MI\_ODUType\_Rate[i] (for i=1 to n). These outputs are connected to a central 'Multiplexer' block. The Multiplexer also receives inputs: OMFS, MFS, FS, CK, D, and TS# from each client process. The Multiplexer outputs a 'Multiplex structure' which is then processed by several functional blocks: 'Multiplex structure identifier (MSI)', 'Payload type (PT)', 'RES', and 'ODUk PM APS'. These blocks output signals: MI\_TxMSI, MI\_AUTOpayloadtype, MI\_TrPT, RI\_TrPT, RI\_AcPT, and PI\_APS. Below these, an 'OMFI' block (optional) receives 'for k = 4, 25(u), 50(u)' and outputs OMFS. A clock generation section includes a 'Free-running clock generator' outputting TI\_CK, an 'ODCa clock generator' outputting ODCa\_CK, and frequency dividers (1/256 and 1/122368) that produce MFS and FS signals. A block 'ODUk OH is set to all-0's, except PM STAT = 001' is also present. The bottom of the diagram shows the aggregated signals: AI\_D, AI\_MFS, AI\_FS, and AI\_CK, which are grouped as 'ODUkP\_AP'. On the right, several signal groups are bracketed: 'ODUkP/ODUj-21\_A\_So\_MP' (containing MI and RI signals), 'ODUk\_PP' (containing PI\_APS), and 'ODUk\_TP' (containing TI\_CK and ODCa\_CK). The reference 'G.798(17)-Amd.3(21)\_F14-62' is noted at the bottom right. + +Block diagram of ODUkP/ODUj-21\_A\_So processes showing client processes, multiplexing, and clock generation. + +Figure 14-62 – ODUkP/ODUj-21\_A\_So processes + +![Figure 14-63 – ODUkP/ODUj-21_A_So client specific processes. This block diagram illustrates the internal processing of an ODUj client signal. At the top, the ODUj_CP[p] signal is split into five inputs: CI_MFS, CI_FS, CI_CK, CI_D, and CI_APS. CI_MFS, CI_FS, and CI_CK feed into an 'ODU-LCK generator'. The generator outputs 'LCK' and 'Normal' signals to a 'Select normal/LCK' block. This block also receives 'MI_AdminState[p]'. The 'Select normal/LCK' block outputs to a 'FAS/MFAS insertion' block. CI_D and CI_APS feed into an 'ODUj APS' block, which also receives 'MI_APS_EN[p]' and 'MI_APS_LVL[p]'. The 'ODUj APS' block outputs to the 'FAS/MFAS insertion' block. The 'FAS/MFAS insertion' block outputs 'CK' and 'D' signals to an 'Elastic store' block. The 'Elastic store' block has 'WR' (write) and 'RD' (read) ports. 'WR' is controlled by 'MI_ODUType_Rate[p]' and 'JC' (justification control) signals. The 'Elastic store' block outputs 'D' and 'TS#' signals. The entire process is enclosed in a grey box labeled 'ODUj_CP[p]' at the top. Below the box, the text 'G.798(17)-Amd.3(21)_F14-63' is present.](39729be7ec83c3de8e480061966e4505_img.jpg) + +Figure 14-63 – ODUkP/ODUj-21\_A\_So client specific processes. This block diagram illustrates the internal processing of an ODUj client signal. At the top, the ODUj\_CP[p] signal is split into five inputs: CI\_MFS, CI\_FS, CI\_CK, CI\_D, and CI\_APS. CI\_MFS, CI\_FS, and CI\_CK feed into an 'ODU-LCK generator'. The generator outputs 'LCK' and 'Normal' signals to a 'Select normal/LCK' block. This block also receives 'MI\_AdminState[p]'. The 'Select normal/LCK' block outputs to a 'FAS/MFAS insertion' block. CI\_D and CI\_APS feed into an 'ODUj APS' block, which also receives 'MI\_APS\_EN[p]' and 'MI\_APS\_LVL[p]'. The 'ODUj APS' block outputs to the 'FAS/MFAS insertion' block. The 'FAS/MFAS insertion' block outputs 'CK' and 'D' signals to an 'Elastic store' block. The 'Elastic store' block has 'WR' (write) and 'RD' (read) ports. 'WR' is controlled by 'MI\_ODUType\_Rate[p]' and 'JC' (justification control) signals. The 'Elastic store' block outputs 'D' and 'TS#' signals. The entire process is enclosed in a grey box labeled 'ODUj\_CP[p]' at the top. Below the box, the text 'G.798(17)-Amd.3(21)\_F14-63' is present. + +**Figure 14-63 – ODUkP/ODUj-21\_A\_So client specific processes** + +### Specific processes + +The specific processes are performed independently for each ODUj client signal that is multiplexed into the OPUk. The specific processes perform the mapping of the ODUj into an ODTUjk or ODTUk.M. + +**FAS/MFAS insertion:** The function shall extend the ODUj with the frame alignment overhead (FAS and MFAS) in row one bytes 1 to 7 as described in clause 15.6.2 of [ITU-T G.709]. Bytes 8 to 14 of row one are set to all-ZEROs. + +**Mapping, frequency justification and bit-rate adaptation:** The function shall provide an elastic store (buffer) process for the ODUj client signal. The data signal ODUj\_CI shall be written into the buffer under the control of the associated input clock. + +Two justification methods, as described below, are provided, AMP (*ODTUjk*) and GMP (*ODTUk.M*). The ODU type and rate, as configured via the MI\_ODUType\_Rate[p] input for tributary port #p, determine the mapping method and in the case of GMP mapping, the base value and ranges for the parameters Cn and Cm. + +*ODTUjk:* The data shall be read out of the buffer and written onto the D, NJO, PJO1 and PJO2 bytes of the selected ODTUjk frame under the control of the ODUk clock and the asynchronous mapping procedure (AMP) justification decisions as defined in clause 19.5 of [ITU-T G.709]. + +A justification decision shall be performed two times per OPUk multiframe (jk = 12, 13) and eight times per OPUk multiframe (jk = 23). Justification decisions are taken at the beginning of the OPUk frame carrying an instance of the ODTUjk justification overhead. Each justification decision results + +in a corresponding double positive, positive, negative or no justification action in this OPuk frame. Upon a double positive justification action, the reading of two data bytes out of the buffer shall be cancelled once. No ODUj data shall be written onto the PJO2, PJO1 or NJO bytes. Upon a positive justification action, the reading of one data byte out of the buffer shall be cancelled once. No ODUj data shall be written onto the PJO1 or NJO bytes and data shall be written onto the PJO2 byte. Upon a negative justification action, one extra data byte shall be read once out of the buffer. ODUj data shall be written onto the PJO2, PJO1 and NJO bytes. If no justification action is to be performed, ODUj data shall be written onto the PJO2 and PJO1 bytes and no ODUj data shall be written onto the NJO byte. The OPuk frame that contains the PJO2, PJO1 and NJO bytes depends on the tributary slots occupied by the ODTUjk. + +The justification decisions determine the phase error introduced by the function. + +*ODTUk.M*: The data shall be read out of the buffer and written onto groups of M successive bytes of the ODTUk.M payload area under the control of the ODUk clock and the GMP data/stuff control mechanism as defined in clause 19.6 of [ITU-T G.709]. + +*Buffer size*: In the presence of jitter as specified by [ITU-T G.8251] and a frequency within the range specified in Table 7-2 of [ITU-T G.709], this mapping process shall not introduce any errors. The maximum buffer hysteresis, and therefore the maximum phase error introduced, shall be as listed in Table 14-29. + +**Table 14-29 – Maximum buffer hysteresis** + +| Mapping | Maximum buffer hysteresis | +|----------------|------------------------------------| +| ODUj → ODTUk.M | M bytes | +| ODUj → ODTUjk | 2 bytes (j = 1)
8 bytes (j = 2) | + +**ODTUjk JC**: The function shall generate the justification control bits based on the justification decision according to the specification in clause 19.5 of [ITU-T G.709]. It shall insert the justification control bits in bit 7 and 8 of all three JC bytes of the frame in which the justification is performed. The remaining (RES) bits of the JC byte shall be set to all-ZEROs. The ODUk frame that contains the JC bytes depends on the time slot(s) of the ODTUjk. + +**ODTUK.M JC1/JC2/JC3, JC4/JC5/JC6**: The function shall generate the GMP $C_m$ and GMP $\sum C_{nd}$ information and insert this into the JC1/JC2/JC3 and JC4/JC5/JC6 bytes, respectively, according to the specification in clause 19.6 and Annex D of [ITU-T G.709]. + +**ODU-LCK**: The function shall generate the ODU-LCK signal as defined in clause 16.5 of [ITU-T G.709]. The clock, frame start and multiframe start are defined by the incoming ODUk signal. + +**ODUj server layer APS**: When APS is enabled for tributary signal #p (MI\_APS\_EN[p] is true), the function shall insert the CI\_APS value into the ODU APS/PCC[MI\_APS\_LVL[p]] field, which is available once per eight ODU frames when the value of the MFAS bits 6, 7, 8 is equal to MI\_APS\_LVL[p]. + +**NOTE** – The ODUj server layer section APS information may be present in the case where the ODUj signal contains an ODU-AIS, ODU-LCK or ODU-OCI maintenance signal. The ODU-LCK maintenance signal may be inserted in this adaptation source function. ODUj SNC/I protection is unable to detect the insertion of such ODU-LCK and will not perform a protection switch. + +**Selector**: The normal signal for a tributary signal #p may be replaced by the ODU-LCK signal. The ODU-LCK signal is selected if the MI\_AdminState[p] is LOCKED. + +## Common processes + +**Clock and (multi)frame start signal generation:** The function shall generate a local ODUk clock (ODUKP\_AI\_CK) with a frequency as listed in Table 7-2 of [ITU-T G.709] from the synchronization timing information clock input (TI\_CK) or, if the TI\_CK is absent, a free-running oscillator. The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUk signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +**OPU multiframe (OMFI) start signal generation for OPUk with k = 4, 25(u), 50(u):** For k = 4, 25(u), 50(u) in addition to MFAS, a dedicated OPU multiframe indicator is used for the multiplexing of LO ODUs into the OPU payload area. This multiframe structure is locked to the lsb bits of the OMFI byte, as shown in Tables 19-4, 19-5 and 19-6 of [ITU-T G.709], and to be inserted into the OPU overhead. The function shall generate an OPU multiframe and the related start signal (OMFS) dividing the frame signal sequence by the maximum number of tributary slots TSmax. The OMFI start signal may optionally be phase aligned to the ODU multiframe signal. In this case, the OMFI = 0 position is aligned with MFAS = 0 position every 1280 frame periods. See clause 19.4.4 of [ITU-T G.709]. + +**Multiplexing:** The function assigns the individual ODTUjk or ODTUk.M to specific time slots of the OPUk payload area as defined by the multiplex structure (see clauses 19.3 and 19.4.1 of [ITU-T G.709]). + +**MSI:** The function shall insert the TxMSI into the MSI byte positions of the PSI overhead as defined in clauses 19.4.1.4, 19.4.1.5, 19.4.1.6 of [ITU-T G.709]. The TxMSI value, and as such the multiplex structure, is configurable via MI\_TxMSI. + +**PT:** The function shall insert code "0010 0001" (ODU multiplex structure supporting ODTUk.ts or ODTUk.ts and ODTUjk) into the PT byte position of the PSI overhead as defined in clause 15.9.2.1 of [ITU-T G.709] for k = 4. + +**Autonomous payload type for k = 2, 3:** For k = 2, 3 the transmitted PT code shall default to code "0010 0001". This code must be replaced by code "0010 0000" under the control of the PT = 21-to-PT = 20 interworking process described hereafter. When MI\_AutoPayloadtype is activated, the function shall adapt a PT21 supporting port to a PT20 structure. + +If the corresponding adaptation sink provides the information of a PT = 20 at the RI\_AcPT, the function shall fall back to PT = 20 under the following conditions: The MI\_AutoPayloadtype is true and the HO ODU source is either not provisioned for any traffic signal structure, or the HO ODU2 source configured for one or more ODU1 signals to be mapped into TS1/TS5 and/or TS2/TS6 and/or TS3/TS7 and/or TS4/TS8, or the HO ODU3 source is configured to support one or more ODU1 signals mapped into TS1/TS17, TS2/TS18, Tsi/TS16+I and/or one or more ODU2 signals mapped into Tsa/TS16+a/TSb/TS16+b/TSc/TS16+c/TSd/TS16+16 and no other ODU type signals. In this case, the function shall insert PT20 into the PSI positions. + +The default value of the MI\_AutoPayloadtype activation shall be "true". + +In the situation where a PT 21 capable port which has been operating in the PT20 mode is taken out of service or receives PT21, the port shall subsequently fall back to a PT21 structure. + +NOTE 1 – Equipment developed prior to Edition 4.0 of this Recommendation may implement a different setting in respect of the default value of the MI\_AutoPayloadtype. + +In the case the ODU2 or ODU3 adaptation source is configured for either ODU0, or an ODUflex, or an ODU2e, or for an ODU1 in TSi/TSj with j<>4+I (for ODU2) or j<>16+I (for ODU3) then PT21 + +is to be inserted. The transmitted PT shall be reported at the ODUkP/ODUj-21\_A\_So\_RI\_TrPT to the corresponding adaptation sink function and the ODUkP/ODUj-21\_A\_So\_MI\_TrPT. + +NOTE 2 – The change to PT20 or PT21 means a full adaptation to the related signal structure including the default OH byte insertion. + +**RES:** The function shall insert all-ZEROs into the RES bytes. + +**ODUk PM APS:** The function shall insert the PI\_APS value into the ODUk path APS/PCC field, which is available once per eight ODUk frames when MFAS bits 6, 7, 8 are 000. + +All other bits of the ODUk overhead should be sourced as "0"s, except the PMOH STAT field which should be set to the value "normal path signal" (001). + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.3.10.2 ODUkP to ODUj payload type 21 adaptation sink function (ODUkP/ODUj-21\_A\_Sk) + +The ODUkP/ODUj-21\_A\_Sk function extracts the OPUk overhead (PT, MSI, RES and OMFI) and monitors the reception of the correct payload type. It demultiplexes the individual ODTUjk and ODTUk.M from the payload area of the OPUk and recovers the $n \times$ ODUj signals using the justification control information (JC, JC1/2/3/4/5/6 overhead). It determines the frame and multiframe structure of the ODUj. It provides access to ODUk PM APS overhead. + +The information flow and processing of the ODUkP/ODUj-21\_A\_Sk function is defined with reference to Figures 14-64, 14-65 and 14-66. + +#### Symbol + +![Diagram of the ODUkP/ODUj-21_A_Sk function symbol. The central block is labeled 'ODUkP/ODUj-21'. It has four input arrows: 'ODUkP/ODUj-21_A_Sk_MP' from the top left, 'ODUkP_PP' from the bottom left, 'ODUkP_AP' from the bottom, and 'ODUkP/ODUj-21_A_Sk_RP' from the right. It has multiple output arrows pointing upwards labeled 'Tributary port 1', '2', '...', 'n', and 'ODUj_CPs'.](cacc4ff5c441e0eb6fbd5e14a083eb05_img.jpg) + +The diagram shows a central trapezoidal block labeled "ODUkP/ODUj-21". To its left, two arrows point into the block: "ODUkP/ODUj-21\_A\_Sk\_MP" (top) and "ODUkP\_PP" (bottom). Below the block, an arrow points into it labeled "ODUkP\_AP". To its right, an arrow points out of the block labeled "ODUkP/ODUj-21\_A\_Sk\_RP". Above the block, multiple arrows point out of it, labeled "Tributary port 1", "2", "...", and "n". Above these arrows, the label "ODUj\_CPs" is present. A small text "G.798(17)\_F14-64" is located at the bottom right of the diagram. + +Diagram of the ODUkP/ODUj-21\_A\_Sk function symbol. The central block is labeled 'ODUkP/ODUj-21'. It has four input arrows: 'ODUkP/ODUj-21\_A\_Sk\_MP' from the top left, 'ODUkP\_PP' from the bottom left, 'ODUkP\_AP' from the bottom, and 'ODUkP/ODUj-21\_A\_Sk\_RP' from the right. It has multiple output arrows pointing upwards labeled 'Tributary port 1', '2', '...', 'n', and 'ODUj\_CPs'. + +**Figure 14-64 – ODUkP/ODUj-21\_A\_Sk function** + +## Interfaces + +**Table 14-30 – ODUkP/ODUj-21\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_MFS
ODUkP_AI_TSF
ODUkP_AI_TSD
ODUkP/ODUj-21_A_Sk_MP:
ODUkP/ODUj-21_A_Sk_MI_ExMSI[1..n]
ODUkP/ODUj-21_A_Sk_MI_AdminState[1..n]
ODUkP/ODUj-
21_A_Sk_MI_Nominal_Bitrate_and_Tolerance[1..n]
ODUkP/ODUj-21_A_Sk_MI_ODUType[1..n]
ODUkP/ODUj-21_A_Sk_MI_APS_EN[1..n]
ODUkP/ODUj-21_A_Sk_MI_APS_LVL[1..n]
ODUkP/ODUj-21_A_Sk_RP:
ODUkP/ODUj-21_A_Sk_RI_TrPT (Note) | n × ODUj_C P:
ODUj_CI_CK
ODUj_CI_D
ODUj_CI_FS
ODUj_CI_MFS
ODUj_CI_SSF
ODUj_CI_SSD
ODUj_CI_APS
ODUk_PP:
ODUk_PI_APS
ODUk_PI_TSF
ODUk_PI_TSD
ODUkP/ODUj-21_A_Sk_MP:
ODUkP/ODUj-21_A_Sk_MI_cPLM
ODUkP/ODUj-21_A_Sk_MI_cLOOMFI
ODUkP/ODUj-21_A_Sk_MI_cMSIM
ODUkP/ODUj-21_A_Sk_MI_AcPT
ODUkP/ODUj-21_A_Sk_MI_AcMSI[1..n]
ODUkP/ODUj-21_A_Sk_MI_cLOFLOM[1..n]
ODUkP/ODUj-21_A_Sk_RP:
ODUkP/ODUj-21_A_Sk_RI_AcPT (Note) | +| NOTE – For ODU2P/ODUj-21_A_Sk and ODU3P/ODUj-21_A_Sk only. | | + +## Processes + +The processes associated with the ODUkP/ODUj-21\_A\_Sk function are specific processes for each ODUj\_CP and common processes for the compound (multiplexed) signal as depicted in Figures 14-65 and 14-66. + +![Block diagram of ODUkP/ODUj-21_A_Sk processes showing Client specific processes, Demultiplexer, MSI process, PT process, ODUk PM APS, and OMFI process with various input and output signals.](eda1a0f033926f48febc095bce470c58_img.jpg) + +The diagram illustrates the internal processes of an ODUkP/ODUj-21\_A\_Sk system. At the top, multiple 'Client specific processes' are shown for ODUj\_CP[1] and ODUj\_CP[n]. Each client process has inputs: AI\_TSD, AI\_TSF, dPLM, dLOOMFI, dMSIM[1..n], MI\_cMSIM[1..n], MI\_cLOFLOM[1..n], MI\_AdminState[1..n], MI\_APS\_EN[1..n], MI\_APS\_LVL[1..n], MI\_Nominal\_Bitrate\_and\_Tolerance[1..n], and MI\_ODUType[1..n]. These clients output signals: CI\_MFS, CI\_FS, CI\_CK, CI\_D, CI\_APS, CI\_SSF, and CI\_SSD. All client outputs feed into a central 'Demultiplexer'. + +The Demultiplexer outputs are: OMFS, MFS, FS, CK, D, and TS#. These signals are distributed to several processing blocks: + +- Extract MSI** receives CK and D, and outputs to an **MSI process**. The MSI process outputs MI\_ExMSI[1..n] and MI\_AcMSI[1..n], and feeds into a **Multiplex structure**. The Multiplex structure also receives inputs from other processes and outputs dMSIM[1..n] back to the clients. +- Extract PT** receives CK and D, and outputs to a **PT process**. The PT process outputs MI\_AcPT, RI\_AcPT, and RI\_TrPT, and feeds into the Multiplex structure. It also receives dPLM from the ODUk PM APS block. +- ODUk PM APS** receives CK and D, and outputs dPLM to the PT process and PI\_APS, PI\_TSF, and PI\_TSD to the right. +- Extract OMFI** (for k = 4, 25(u), 50(u)) receives CK and D, and outputs to an **OMFI process**. The OMFI process outputs OMFS and dLOOMFI to the right. It also feeds into the Multiplex structure. + +On the right side, a **Defect correlations** block receives AI\_TSF, dLOOMFI, and dPLM, and outputs MI\_cLOOMFI, MI\_cPLM, MI\_cMSIM[1..n], MI\_cLOFLOM[1..n], MI\_AdminState[1..n], MI\_APS\_EN[1..n], MI\_APS\_LVL[1..n], MI\_Nominal\_Bitrate\_and\_Tolerance[1..n], and MI\_ODUType[1..n] back to the clients. + +At the bottom, the **ODUkP\_AP** block provides inputs: AL\_MFS, AL\_FS, AL\_CK, AL\_D, AL\_TSF, and AL\_TSD to the Extract MSI, Extract PT, ODUk PM APS, and Extract OMFI blocks. + +Labels on the far right indicate the output groups: **ODUkP/ODUj-21\_A\_Sk\_MP** for the top client-related outputs, **ODUkP-k/ODUj-21\_A\_Sk\_RP** for the MSI and PT related outputs, and **ODUk\_PP** for the APS and TSF/TSD related outputs. + +Reference G.798(17)-Amd.3(21)\_F14-65 is noted at the bottom right of the diagram. + +Block diagram of ODUkP/ODUj-21\_A\_Sk processes showing Client specific processes, Demultiplexer, MSI process, PT process, ODUk PM APS, and OMFI process with various input and output signals. + +Figure 14-65 – ODUkP/ODUj-21\_A\_Sk processes + +![Block diagram of ODUj_CP[p] client specific processes. The diagram shows various functional blocks like 'Select normal/AIS/LCK', 'Generate AIS', 'Generate LCK', 'Frame/multi-frame alignment', 'Elastic store', 'Clock generation (ODCp)', 'Justification control', 'Extract JC', 'ODUj APS', 'Consequent actions', and 'Defect correlations'. It includes input and output signals such as OMFS, MFAS, FS, CK, D, TS#, Active, CI_MFS, CI_FS, CI_CK, CI_D, CI_APS, CI_SSF, CI_SSD, and various management and alarm signals like MI_AdminState[p], MI_Nominal_Bitrate_and_Tolerance[p], MI_APS_EN[p], MI_APS_LVL[p], dLOFLOM, dPLM, dLOOMFI, dMSIM[p], MI_cMSIM[p], MI_cLOFLOM[p], AI_TSD, and AI_TSF. A reference label G.798(17)-Amd.3(21)_F14-66 is present.](a279b24bee8e82a60177168f08cce415_img.jpg) + +G.798(17)-Amd.3(21)\_F14-66 + +Block diagram of ODUj\_CP[p] client specific processes. The diagram shows various functional blocks like 'Select normal/AIS/LCK', 'Generate AIS', 'Generate LCK', 'Frame/multi-frame alignment', 'Elastic store', 'Clock generation (ODCp)', 'Justification control', 'Extract JC', 'ODUj APS', 'Consequent actions', and 'Defect correlations'. It includes input and output signals such as OMFS, MFAS, FS, CK, D, TS#, Active, CI\_MFS, CI\_FS, CI\_CK, CI\_D, CI\_APS, CI\_SSF, CI\_SSD, and various management and alarm signals like MI\_AdminState[p], MI\_Nominal\_Bitrate\_and\_Tolerance[p], MI\_APS\_EN[p], MI\_APS\_LVL[p], dLOFLOM, dPLM, dLOOMFI, dMSIM[p], MI\_cMSIM[p], MI\_cLOFLOM[p], AI\_TSD, and AI\_TSF. A reference label G.798(17)-Amd.3(21)\_F14-66 is present. + +**Figure 14-66 – ODUkP/ODUj-21\_A\_Sk client specific processes** + +**Common processes** + +**OPU multiframe (OMFI) reception for OPUk with k = 4, 25(u), 50(u):** For k = 4, 25(u), 50(u) in addition to MFAS, a dedicated OPU multiframe indicator is used for the multiplexing of LO ODUs into the OPU payload area. This multiframe structure is locked to the lsb bits of the OMFI byte, as shown in Tables 19-4, 19-5 and 19-6 of [ITU-T G.709]. The function shall detect OPU multiframe by searching for the framing pattern in the bits indicated above. The process has two states, out-of-multiframe (OOM) and in-multiframe (IM). The IM state shall be entered if this set is found and confirmed one frame period later and an error-free multiframe sequence is found in the byte positions of the two frames. In the IM state, the frame alignment signal shall be continuously checked with the presumed OMFI frame start position and the expected multiframe sequence. The OOM state shall be entered if this subset is not found at the correct position in five consecutive frames or the received OMFI does not match with the expected multiframe number in five consecutive frames. The OPU multiframe start (OMFS) shall be maintained during the OOM state of the OMFI detection process. The defect dLOOMFI shall be generated based on the state of the OMFI alignment process. + +If the OMFI alignment process is persistently in the out-of-multiframe (OOM) state for 3 ms, dLOOMFI shall be declared. dLOOMFI shall be cleared immediately when the OMFI alignment process is in the in-multiframe (IM) state. + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. + +**Autonomous payload type for k = 2, 3:** The accepted PT is provisioned to the RP (RI\_AcPT) for automatic PT adaptation. The PLM detection shall be based on the comparison of the accepted PT with the provided PT on the RP at the RI\_TrPT input. + +**MSI:** The function shall extract the MSI from the PSI overhead as defined in clause 8.7.2.1. The accepted MSI for a tributary signal #p (AcMSI[p]) is available at the MP (MI\_AcMSI[p]). The multiplex structure is defined by ExMSI[p], which is either fixed or is configurable via MI\_ExMSI[p]. + +**RES:** The value in the RES bytes shall be ignored. + +**ODUk PM APS:** The function shall extract the information from the ODUk path APS/PCC field, which is available once per eight ODUk frames when MFAS bits 6, 7, 8 are 000 and apply this to the PI\_APS. + +**Demultiplexing:** The function activates the ODTUjk or ODTUk.M and assigns the time slots of the ODUk payload area to the individual ODTUjk or ODTUk.M as defined by the multiplex structure (see clauses 19.3 and 19.4.1 of [ITU-T G.709]). + +### Specific processes + +The specific processes are performed independently for each ODUj client signal that is multiplexed into the OPUk. The specific processes recover the ODUj from the ODTUjk or ODTUk.M. + +Two justification methods as described below are provided, AMP (*ODTUjk*) and GMP (*ODTUk.M*). The ODU type, as configured via the MI\_ODUType [p] input for tributary port #p, determines the mapping method. In the case of GMP mapping, the ODU rate, as configured via the MI\_Nominal\_Bitrate\_and\_Tolerance[p] input for tributary port #p, determines the base value and ranges for the parameters $C_n$ and $C_m$ . + +**ODTUjk JC:** The function shall interpret the justification control information in bits 7 and 8 of the JC bytes as defined in clause 19.5 of [ITU-T G.709] in order to determine the justification action (double positive, positive, negative, none) for the current frame. A two out of three majority decision is used. RES bits in the JC bytes shall be ignored. The ODUk frame that contains the JC bytes depends on the time slot(s) of the ODTUjk. + +**ODTUk.ts JC1/2/3 and JC4/5/6:** The function shall interpret the GMP overhead information in the JC1/2/3 and JC4/5/6 bytes as defined in clause 19.6 of [ITU-T G.709] in order to determine the number of M-byte ODUj entities in the next ODTUk.M multiframe. The OPUk frame that contains the JC1/2/3 and JC4/5/6 bytes depends on the last tributary slot that is occupied by the ODTUk.M. + +**Demapping, CBR clock generation:** The function shall provide an elastic store (buffer) process. + +*ODTUjk:* The ODUj data shall be written into the buffer from the D, NJO, PJO1 and PJO2 bytes in the ODTUjk frame. The information extraction of the PJO2, PJO1 and NJO bytes shall be under the control of the justification control information. + +Upon a double positive justification action, the writing of two data bytes into the buffer shall be cancelled once. No ODUj data shall be read from the PJO2, PJO1 or NJO bytes. Upon a positive justification action, the writing of one data byte into the buffer shall be cancelled once. No ODUj data shall be read from the PJO1 or NJO bytes and data shall be read from the PJO2 byte. Upon a negative justification action, one extra data byte shall be written into the buffer once. ODUj data shall be read from the PJO2, PJO1 and NJO bytes. If no justification action is to be performed, ODUj data shall be + +read from the PJO2 and PJO1 bytes and no ODUj data shall be read from the NJO bytes. The OPUk frame that contains the PJO2, PJO1 and NJO bytes depends on the tributary slots occupied by the ODTUjk. + +*ODTUk.M:* The ODUj data shall be extracted from the groups of M successive bytes of the ODTUk.M payload area under the control of the GMP data/stuff control mechanism as defined in clause 19.6 of [ITU-T G.709] and be written into the buffer. The $C_n$ information associated with the ODUj is computed from the GMP $C_m$ and $\Sigma C_{ND}$ parameters carried within the JC1/2/3 and JC 4/5/6 overhead of the ODTUk.M as specified in clause 19.6 of [ITU-T G.709]. For the GMP data/stuff control mechanism, refer to Annex D of [ITU-T G.709]. + +The ODUj data (CI\_D) shall be read out of the buffer under the control of the ODUj clock (CI\_CK). + +*Smoothing and jitter limiting process:* The function shall provide for a clock smoothing and elastic store (buffer) process. The ODUj data signal shall be written into the buffer under the control of the associated (gapped) OPUk input clock (with a frequency accuracy within $\pm 20$ ppm). The data signal shall be read out of the buffer under the control of a smoothed (equally spaced) ODUj clock (the rate is determined by the ODUj signal at the input of the remote ODUkP/ODUj-21\_A\_So). + +The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCp clock), apply. + +*Buffer size:* In the presence of jitter as specified by [ITU-T G.8251] and a frequency within the tolerance range specified for the ODUj signal in Table 7-2 of [ITU-T G.709], this justification process shall not introduce any errors. + +Following a step in frequency of the ODUj signal transported (for example, due to reception of ODUj\_CI from a new ODUj\_TT\_So at the far end or removal of a ODU-AIS signal with a frequency offset), there will be a maximum recovery time of X seconds after which this process shall not generate any bit errors. The value of X is for further study; a value of one second has been proposed. + +**Frame and multiframe alignment:** The function shall perform frame and multiframe alignment as described in clause 8.2.3. + +**ODU-LCK, ODU-AIS:** The function shall generate the ODU-LCK and ODU-AIS signals as defined in [ITU-T G.709]. The clock, frame start and multiframe start shall be independent from the incoming clock. The clock has to be within the ODUj frequency tolerance range as specified in Table 7-2 of [ITU-T G.709] provisioned by the MI\_Nominal\_Bitrate\_and\_Tolerance[p] from a free-running oscillator. Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +**Selector:** The normal signal for a tributary signal #p may be replaced by either the ODU-AIS or ODU-LCK signal. ODU-LCK is selected if the corresponding MI\_AdminState[p] signal is LOCKED. ODU-AIS is selected if the corresponding MI\_AdminState[p] signal is not LOCKED and aAIS is true. + +**ODUj server layer APS:** When APS is enabled for tributary signal #p (MI\_APS\_EN[p] is true), the function shall extract the information from the ODU APS/PCC[MI\_APS\_LVL[p]] field, which is available once per eight ODU frames when the value of the MFAS bits 6, 7, 8 is equal to MI\_APS\_LVL[p], and apply the extracted information to the CI\_APS. + +NOTE 1 – The ODUj server layer section APS information may be present in the case where the ODUj signal contains an ODU-AIS, ODU-LCK or ODU-OCI maintenance signal. The ODU-LCK maintenance signal may have been inserted in the far-end adaptation source function. ODUj SNC/I protection is unable to detect the insertion of such ODU-LCK and will not perform a protection switch. + +## Defects + +The function shall detect dPLM, dMSIM, dLOOMFI and dLOFLOM. + +**dPLM:** See clause 6.2.4.1. The expected payload type is the provided PT on the RP at the RI\_TrPT input (ODU multiplex structure supporting ODTUk.ts or ODTUk.ts and ODTUjk), as defined in [ITU-T G.709]. + +**dLOOMFI:** dLOOMFI is detected per OPUk with k = 4, 25(u), 50(u). See the OPU multiframe (OMFI) detection process for OPUk with k = 4, 25(u), 50(u). + +For each ODUj tributary port #p: + +**dMSIM[p]:** See clause 6.2.9.1. dMSIM is detected per active ODUj. + +**dLOFLOM[p]:** See clause 6.2.5.3. dLOFLOM is detected per active ODUj. + +#### Consequent actions + +$PI\_TSF \leftarrow AI\_TSF$ + +$PI\_TSD \leftarrow AI\_TSD$ + +For each ODUj tributary port #p: + +$aSSF[p] \leftarrow ((AI\_TSF \text{ or } dPLM \text{ or } dLOOMFI \text{ or } dMSIM[p] \text{ or } dLOFLOM[p]) \text{ and } (\text{not } MI\_AdminState[p] = \text{LOCKED}))$ + +$aSSD[p] \leftarrow AI\_TSD \text{ and } (\text{not } MI\_AdminState[p] = \text{LOCKED})$ + +$aAIS[p] \leftarrow ((AI\_TSF \text{ or } dPLM \text{ or } dLOOMFI \text{ or } dMSIM[p] \text{ or } dLOFLOM[p]) \text{ and } (\text{not } MI\_AdminState[p] = \text{LOCKED}))$ + +NOTE 2 – The state of the determination process of the $C_m$ and its contribution to AIS consequent action are for further study. + +On declaration of aAIS, the function shall output an all-ONEs pattern/signal within two frames. On clearing aAIS, the all-ONEs pattern/signal shall be removed within two frames, with normal data being output. The AIS clock, frame start and multiframe start shall be independent from the incoming clock, frame start and multiframe start. The clock has to be within the ODUj frequency tolerance range as specified in Table 7-2 of [ITU-T G.709] provisioned by the MI\_Nominal\_Bitrate\_and\_Tolerance from a free-running oscillator. Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock) apply. + +#### Defect correlations + +$cPLM \leftarrow dPLM \text{ and } (\text{not } AI\_TSF)$ + +For ODUk with k = 4, 25(u), 50(u): + +$cLOOMFI \leftarrow dLOOMFI \text{ and } (\text{not } AI\_TSF)$ + +For each ODUj tributary port #p: + +$cMSIM[p] \leftarrow dMSIM[p] \text{ and } (\text{not } dPLM) \text{ and } (\text{not } dLOOMFI) \text{ and } (\text{not } AI\_TSF)$ + +$cLOFLOM[p] \leftarrow dLOFLOM[p] \text{ and } (\text{not } dPLM) \text{ and } (\text{not } dLOOMFI) \text{ and } (\text{not } AI\_TSF)$ + +**Performance monitoring:** None. + +### 14.3.11 ODUkP to ETH adaptation functions (ODUkP/ETH\_A; k = 0, 1, 2, 3, 4, flex) + +#### 14.3.11.1 ODUkP to ETH adaptation source function (ODUkP/ETH\_A\_So) + +The ODUkP/ETH\_A\_So function creates the ODUk signal from a free running clock. It maps the ETH\_CI information into the payload of the OPUk, adds OPUk overhead (RES, PT) and default ODUk overhead. + +#### Symbol + +![Symbol diagram for ODUkP/ETH_A_So function. The central block is labeled 'ODUkP/ETH'. Inputs from the top are 'ETH_TFP' and 'ETH_FP'. Input from the left is 'ODUkP/ETH_A_So_MP'. Outputs to the right are 'ETH_TF_PP' and 'ETH_F_PP'. Output from the bottom is 'ODUkP_AP'. Reference G.798(17)-Amd.1(18)_F14-66.1 is shown at the bottom right.](43b05bd1b6ee31fba18d3eb683903504_img.jpg) + +Symbol diagram for ODUkP/ETH\_A\_So function. The central block is labeled 'ODUkP/ETH'. Inputs from the top are 'ETH\_TFP' and 'ETH\_FP'. Input from the left is 'ODUkP/ETH\_A\_So\_MP'. Outputs to the right are 'ETH\_TF\_PP' and 'ETH\_F\_PP'. Output from the bottom is 'ODUkP\_AP'. Reference G.798(17)-Amd.1(18)\_F14-66.1 is shown at the bottom right. + +Figure 14-66.1 – ODUkP/ETH\_A\_So symbol + +#### Interfaces + +Table 14-30.1 – ODUkP/ETH\_A\_So interfaces + +| Inputs | Outputs | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF
ETH_CI_SSFrdi
ETH_CI_SSFfdi
ODUkP/ETH_A_So_MP:
ODUkP/ETH_A_So_MI_CSFEnable
ODUkP/ETH_A_So_MI_CSFrdifdiEnable | ODUkP_AP:
ODUkP_AI_D
ODUkP_AI_CK
ODUkP_AI_FS
ODUkP_AI_MFS
ETH_TF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_D
ETH_PI_P
ETH_PI_DE | + +#### Processes + +A process diagram of this function is shown in Figure 14-66.2. + +![Figure 14-66.2 – ODUkP/ETH_A_So process diagram. The diagram shows a vertical flow of data and control signals within a grey-shaded area. At the top, three input signals (ETH_CI_SSF (ETH_FP), ETH_CI_D/P/DE (ETH_TFP), and ETH_CI_D/P/DE SSF/SSFrdi/SSFfdi (ETH_FP)) enter 'Client-specific processes'. An output signal (ETH_PI_D/P/DE (ETHF_PP)) exits to the right. Below 'Client-specific processes' is '802.3 MAC FCS generation', which outputs 'ETH_CI' and 'MAC_Frame'. Below that is 'ETH specific GFP-F processes', which receives 'MAC_Frame' and control signals (FCSEnable = false, MI_CSFenable, MI_CSFrdifdiEnable). It outputs 'GFP_FS' and 'GFP_Frame'. Below that is 'Common GFP-F processes', which receives 'GFP_FS' and 'GFP_Frame' and control signals (CMuxConfig, CMuxActive = false). It outputs 'GFP_FS' and 'GFP_Frame'. Below that is 'ODUkP specific GFP-F processes', which receives 'GFP_FS' and 'GFP_Frame' and outputs 'ODUkP_AI_D'. Below that is 'ODUkP specific processes', which receives 'ODUkP_AI_D' and control signal 'ODUkP_AI_CK/FS'. Finally, it outputs 'ODUkP_AI_D/CK/FS/MFS' at the bottom. A reference code 'G.798(17)-Amd.4(22)_F14-66.2' is at the bottom right.](fd4b2ee19b709bcb11190893e23f8453_img.jpg) + +Figure 14-66.2 – ODUkP/ETH\_A\_So process diagram. The diagram shows a vertical flow of data and control signals within a grey-shaded area. At the top, three input signals (ETH\_CI\_SSF (ETH\_FP), ETH\_CI\_D/P/DE (ETH\_TFP), and ETH\_CI\_D/P/DE SSF/SSFrdi/SSFfdi (ETH\_FP)) enter 'Client-specific processes'. An output signal (ETH\_PI\_D/P/DE (ETHF\_PP)) exits to the right. Below 'Client-specific processes' is '802.3 MAC FCS generation', which outputs 'ETH\_CI' and 'MAC\_Frame'. Below that is 'ETH specific GFP-F processes', which receives 'MAC\_Frame' and control signals (FCSEnable = false, MI\_CSFenable, MI\_CSFrdifdiEnable). It outputs 'GFP\_FS' and 'GFP\_Frame'. Below that is 'Common GFP-F processes', which receives 'GFP\_FS' and 'GFP\_Frame' and control signals (CMuxConfig, CMuxActive = false). It outputs 'GFP\_FS' and 'GFP\_Frame'. Below that is 'ODUkP specific GFP-F processes', which receives 'GFP\_FS' and 'GFP\_Frame' and outputs 'ODUkP\_AI\_D'. Below that is 'ODUkP specific processes', which receives 'ODUkP\_AI\_D' and control signal 'ODUkP\_AI\_CK/FS'. Finally, it outputs 'ODUkP\_AI\_D/CK/FS/MFS' at the bottom. A reference code 'G.798(17)-Amd.4(22)\_F14-66.2' is at the bottom right. + +**Figure 14-66.2 – ODUkP/ETH\_A\_So process** + +The client-specific processes, and associated MI and PI signals, are specified in clause 9.5 of [ITU-T G.8021]. + +*802.3 MAC FCS generation:* + +See clause 8.6.1 of [ITU-T G.8021]. + +*Ethernet specific GFP-F source process:* + +See clause 8.5.4.1.1 of [ITU-T G.806]. GFP pFCS generation is disabled (FCSEnable=false). The UPI value for frame-mapped Ethernet shall be inserted (Table 6-3 of [ITU-T G.7041]). The Ethernet frames are inserted into the client payload information field of the GFP-F frames according to clause 7.1 of [ITU-T G.7041]. + +*Common GFP source process:* + +See clause 8.5.3.1 of [ITU-T G.806]. GFP channel multiplexing is not supported (CMuxActive=false). + +*ODUkP specific GFP source process:* + +See clause 8.5.2.1 of [ITU-T G.806]. The GFP frames are mapped into the ODUk payload area according to clause 17.4 of [ITU-T G.709]. + +*ODUkP specific source process:* + +A process diagram for the ODUkP specific source process is shown in Figure 14-66.3. + +![Figure 14-66.3 – ODUkP specific source process diagram. The diagram shows the internal components and signal flow of the ODUkP source process. On the left, input signals D, SSF, FS, and CK enter a large grey box labeled 'ODUkP_AP'. Inside, there are four stacked blocks: 'Insert PT', 'Insert CSF' (with an external SSF input), 'Insert RES', and 'ODUk OH is set to all-0's, except PM STAT = 001'. The output of these blocks is labeled 'AI_D'. At the top right, a 'Free-running clock generator (ODCa)' receives 'CK' and outputs 'CK'. This 'CK' signal is divided by 122368 to produce 'FS', which is then divided by 256 to produce 'MFS'. The 'AI_D' signal is combined with 'CK', 'FS', and 'MFS' to produce the final output signals 'AI_D', 'AI_CK', 'AI_FS', and 'AI_MFS' at the bottom. A reference label 'G.798(17)-Amd.3(21)_F14-66.3' is present at the bottom right of the diagram.](a4a23a6cfd603aea55a02bae13456e8e_img.jpg) + +Figure 14-66.3 – ODUkP specific source process diagram. The diagram shows the internal components and signal flow of the ODUkP source process. On the left, input signals D, SSF, FS, and CK enter a large grey box labeled 'ODUkP\_AP'. Inside, there are four stacked blocks: 'Insert PT', 'Insert CSF' (with an external SSF input), 'Insert RES', and 'ODUk OH is set to all-0's, except PM STAT = 001'. The output of these blocks is labeled 'AI\_D'. At the top right, a 'Free-running clock generator (ODCa)' receives 'CK' and outputs 'CK'. This 'CK' signal is divided by 122368 to produce 'FS', which is then divided by 256 to produce 'MFS'. The 'AI\_D' signal is combined with 'CK', 'FS', and 'MFS' to produce the final output signals 'AI\_D', 'AI\_CK', 'AI\_FS', and 'AI\_MFS' at the bottom. A reference label 'G.798(17)-Amd.3(21)\_F14-66.3' is present at the bottom right of the diagram. + +**Figure 14-66.3 – ODUkP specific source process** + +*Clock and (multi)frame start signal generation:* + +The function shall generate a local ODUk clock (ODUkP\_AI\_CK) with a clock rate within the minimum to maximum clock rate of the specified ODU signal as given in Table 14-2 of [ITU-T G.798]. The jitter and wander requirements as defined in Annex A of [ITU-T G.8251] (ODCa clock) apply. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUk signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +PT: The payload type information is derived directly from the adaptation function type. The value for GFP mapping shall be inserted into the PT byte position of the PSI overhead as defined in clause 15.9.2.1.1 of [ITU-T G.709]. + +RES: The function shall insert all-zeros into the RES bytes. + +CSF: The function shall signal the failure of the client signal to the far end by use of the Bit 1 of the PSI[2] byte of the payload structure identifier as defined in clause 17.1 of [ITU-T G.709]. + +All other bits of the ODUk overhead should be sourced as "0"s, except the ODUk-PM STAT field which should be set to the value "normal path signal" (001). + +*Counter processes:* + +For further study. + +**Defects:** None. + +### Consequent actions + +The function shall perform the following consequent actions: + +aCSF-RDI $\leftarrow$ CI\_SSFrdi and CSFrdifdiEnable and CSFEnable + +aCSF-FDI $\leftarrow$ CI\_SSFfdi and CSFrdifdiEnable and CSFEnable + +aCSF-LOS $\leftarrow$ CI\_SSF and CSFEnable + +aCSF-OPU $\leftarrow$ CI\_SSF and CSFEnable + +**Defect correlations:** None. + +### Performance monitoring + +For further study. + +#### 14.3.11.2 ODUkP to ETH adaptation sink function (ODUkP/ETH\_A\_Sk) + +The ODUkP/ETH\_A\_Sk extracts ETH\_CI information from the ODUkP payload area, delivering ETH\_CI to ETH\_TFP and ETH\_FP. It extracts the OPUk overhead (PT and RES) and monitors the reception of the correct payload type. + +### Symbol + +![Symbol diagram for ODUkP/ETH_A_Sk function. The function is represented by a trapezoidal block labeled 'ODUkP/ETH'. It has two input arrows on the left labeled 'ETHF_PP' and 'ETHF_PP'. It has two output arrows pointing upwards labeled 'ETH_TFP' and 'ETH_FP'. It has one input arrow pointing upwards from below labeled 'ODUkP_AP'. It has one output arrow pointing to the right labeled 'ODUkP/ETH_A_Sk_MP'. A reference code 'G.798(17)-Amd.1(18)_F14-66.4' is shown in the bottom right corner of the diagram area.](f2a96e73ee1821c72d24ae4e0a4d7c46_img.jpg) + +G.798(17)-Amd.1(18)\_F14-66.4 + +Symbol diagram for ODUkP/ETH\_A\_Sk function. The function is represented by a trapezoidal block labeled 'ODUkP/ETH'. It has two input arrows on the left labeled 'ETHF\_PP' and 'ETHF\_PP'. It has two output arrows pointing upwards labeled 'ETH\_TFP' and 'ETH\_FP'. It has one input arrow pointing upwards from below labeled 'ODUkP\_AP'. It has one output arrow pointing to the right labeled 'ODUkP/ETH\_A\_Sk\_MP'. A reference code 'G.798(17)-Amd.1(18)\_F14-66.4' is shown in the bottom right corner of the diagram area. + +**Figure 14-66.4 – ODUkP/ETH\_A\_Sk symbol** + +## Interfaces + +Table 14-30.2 – ODUkP/ETH\_A\_Sk interfaces + +| Inputs | Outputs | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUkP_AP:
ODUkP_AI_D
ODUkP_AI_CK
ODUkP_AI_FS
ODUkP_AI_MFS
ODUkP_AI_TSF
ETH_TTF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE
ETHF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE
ODUkP/ETH_A_Sk_MP:
ODUkP/ETH_A_Sk_MI_CSF_Reported
ODUkP/ETH_A_Sk_MI_MAC_Length
ODUkP/ETH_A_Sk_MI_CSFrdifdiEnable | ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF
ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF
ETH_CI_SSFrdi
ETH_CI_SSFfdi
ODUkP/ETH_A_Sk_MP:
ODUkP/ETH_A_Sk_MI_AcPT
ODUkP/ETH_A_Sk_MI_AcEXI
ODUkP/ETH_A_Sk_MI_AcUPI
ODUkP/ETH_A_Sk_MI_cPLM
ODUkP/ETH_A_Sk_MI_cLFD
ODUkP/ETH_A_Sk_MI_cUPM
ODUkP/ETH_A_Sk_MI_cEXM
ODUkP/ETH_A_Sk_MI_cCSF
ODUkP/ETH_A_Sk_MI_pFCSError | + +## Processes + +A process diagram of this function is shown in Figure 14-66.5. + +![Diagram of the ODUkP/ETH_A_Sk process showing data flow from client-specific processes down to ODUkP specific processes, with associated management interfaces (MI) and physical interfaces (PI).](bae1bd2b5dec0c7f0717e710ad5a3412_img.jpg) + +The diagram illustrates the ODUkP/ETH\_A\_Sk process, showing the flow of data and management signals through various processing stages: + +- Client-specific processes:** The top-level process. It receives **ETH\_PI\_D/P/DE (ETHF\_PP)** from the left and **ETH\_CI\_D/P/DE (ETH\_TFP)** and **ETH\_CI\_D/P/DE (ETH\_FP)** from the top. It outputs **ETH\_PI\_D/P/DE (ETHF\_PP)** to the right and **ETH\_CI\_D/P/DE (ETH\_TFP)** and **ETH\_CI\_D/P/DE (ETH\_FP)** to the top. It is associated with **MI\_pFCSerrors** and **MI\_MAC\_Length**. +- 802.3 MAC FCS check:** Receives **SF** and **MAC Frame** from the process below. It outputs **SF** and **MAC Frame** to the process above. It is associated with **MI\_pFCSerrors**. +- MAC Length check:** Receives **SF** and **MAC Frame** from the process below. It outputs **SF** and **MAC Frame** to the process above. It is associated with **MI\_MAC\_Length**. +- ETH specific GFP-F processes:** Receives **SF** and **MAC Frame** from the process below. It outputs **SF** and **MAC Frame** to the process above. It is associated with **MI\_AcUPI** (left), **MI\_cUPM** (right), and **FCSdiscard = false** (dashed line). +- Common GFP-F processes:** Receives **GFP\_Frame/FS/SF** from the process below. It outputs **GFP\_Frame/FS/SF** to the process above. It is associated with **MI\_AcEXI** (left), **MI\_cEXM** (right), **CMuxConfig** (dashed line), and **CMuxActive = false** (dashed line). +- ODUkP specific GFP-F processes:** Receives **GFP\_Frame/FS/SF** from the process below. It outputs **GFP\_Frame/FS/SF** to the process above. It is associated with **MI\_cLFD** (right) and **MI\_CSFrdifdiEnable** (left). +- ODUkP specific processes:** The bottom-level process. It receives **ODUkP\_AI\_D/CK/FS/MFS/TSF** from the bottom. It outputs **ODUkP\_AI\_D/CK/FS/TSF** to the bottom. It is associated with **MI\_AcPT** (left), **MI\_cPLM** (right), and **MI\_cCSF** (right). + +Reference: G.798(17)-Amd.4(22)\_F14-66.5 + +Diagram of the ODUkP/ETH\_A\_Sk process showing data flow from client-specific processes down to ODUkP specific processes, with associated management interfaces (MI) and physical interfaces (PI). + +**Figure 14-66.5 – ODUkP/ETH\_A\_Sk process** + +The client-specific processes, and associated MI and PI signals, are specified in clause 9.5 of [ITU-T G.8021]. + +*802.3 MAC FCS check process:* + +See clause 8.6.2 of [ITU-T G.8021]. + +*MAC length check process:* + +See clause 8.5 of [ITU-T G.8021]. + +*Ethernet specific GFP-F sink process:* + +See clause 8.5.4.1.2 of [ITU-T G.806]. GFP pFCS checking, GFP p\_FCSerror, p\_FDis are not supported (FCSdiscard=false). The UPI value for frame-mapped Ethernet shall be expected (Table 6-3 of [ITU-T G.7041]). The Ethernet frames are extracted from the client payload information field of the GFP-F frames according to clause 7.1 of [ITU-T G.7041]. + +*Common GFP sink process:* + +See clause 8.5.3.2 of [ITU-T G.806]. GFP channel multiplexing is not supported (MI\_CMuxActive=false). + +*ODUkP specific GFP sink process:* + +See clause 8.5.2.2 of [ITU-T G.806]. The GFP frames are demapped from the ODUk payload area according to clause 17.4 of [ITU-T G.709]. + +ODUkP specific sink process: + +![Diagram of the ODUkP specific sink process. The diagram shows the flow of signals from the ODUkP_AP input to various management interfaces. The input ODUkP_AP is split into four main paths: AI_D, AI_CK, AI_FS, and AI_MFS. AI_D and AI_CK are direct outputs. AI_FS and AI_MFS are processed by 'Extract CSF' and 'Extract PT' blocks. 'Extract CSF' outputs dCSF, which is then processed by 'Defect correlations' along with AI_TSF and dPLM to produce MI_cCSF and MI_cPLM. 'Extract PT' outputs to 'PT process', which produces MI_AcPT and dPLM. dPLM is also processed by 'Defect correlations'. MI_Active is an input to 'Defect correlations'. The diagram is labeled ODUkP_AP and G.798(17)-Amd.1(18)_F14-66.6.](ff86a9199e2ee52e0a198605699d277d_img.jpg) + +Diagram of the ODUkP specific sink process. The diagram shows the flow of signals from the ODUkP\_AP input to various management interfaces. The input ODUkP\_AP is split into four main paths: AI\_D, AI\_CK, AI\_FS, and AI\_MFS. AI\_D and AI\_CK are direct outputs. AI\_FS and AI\_MFS are processed by 'Extract CSF' and 'Extract PT' blocks. 'Extract CSF' outputs dCSF, which is then processed by 'Defect correlations' along with AI\_TSF and dPLM to produce MI\_cCSF and MI\_cPLM. 'Extract PT' outputs to 'PT process', which produces MI\_AcPT and dPLM. dPLM is also processed by 'Defect correlations'. MI\_Active is an input to 'Defect correlations'. The diagram is labeled ODUkP\_AP and G.798(17)-Amd.1(18)\_F14-66.6. + +Figure 14-66.6 – ODUkP specific sink process + +PT: The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1 of [ITU-T G.798]. The payload type value for GFP mapping in clause 15.9.2.1.1 of [ITU-T G.709] shall be expected. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. + +RES: The value in the RES bytes shall be ignored. + +CSF: The function shall extract the CSF signal indicating the failure of the client signal out of the Bit 1 of the PSI[2] byte of the payload structure identifier as defined in clause 17.1 of [ITU-T G.709]. + +#### Defects + +dPLM – See clause 6.2.4.1 of [ITU-T G.798]. + +dLFD – See clause 6.2.5.2 of [ITU-T G.806]. + +dUPM – See clause 6.2.4.3 of [ITU-T G.806]. + +dEXM – See clause 6.2.4.4 of [ITU-T G.806]. + +dCSF-LOS – See clause 8.6.4.2 of [ITU-T G.8021]. + +dCSF-RDI – See clause 8.6.4.2 of [ITU-T G.8021]. + +dCSF-FDI – See clause 8.6.4.2 of [ITU-T G.8021]. + +#### Consequent actions + +The function shall perform the following consequent actions: + +aSSF ← AI\_TSF or dPLM or dLFD or dUPM or dEXM or dCSF-LOS + +aSSFrdfi ← dCSF-RDI and CSFrdifdiEnable + +aSSFfdi ← dCSF-FDI and CSFrdifdiEnable + +#### Defect correlations + +The function shall perform the following defect correlations to determine the most probable fault cause (see clause 6.4 of [ITU-T G.806]). This fault cause shall be reported to the EMF. + +cPLM $\leftarrow$ dPLM and (not AI\_TSF) +cLFD $\leftarrow$ dLFD and (not dPLM) and (not AI\_TSF) +cUPM $\leftarrow$ dUPM and (not dEXM) and (not dPLM) and (not dLFD) and (not AI\_TSF) +cEXM $\leftarrow$ dEXM and (not dPLM) and (not dLFD) and (not AI\_TSF) +cCSF $\leftarrow$ (dCSF-LOS or dCSF-OPU or dCSF-FDI) and (not dEXM) and (not dUPM) and (not dPLM) and (not dLFD) and (not AI\_TSF) and CSF\_Reported + +### Performance monitoring + +The function shall perform the following performance monitoring primitives processing. The performance monitoring primitives shall be reported to the EMF. + +pFCSErrors: count of FrameCheckSequenceErrors per second. + +NOTE – This primitive is calculated by the MAC FCS Check process. + +### 14.3.12 HAO-capable ODUk to ETH adaptation functions (ODUkP-h/ETH\_A; k = flex) + +#### 14.3.12.1 HAO-capable ODUk to ETH adaptation source function (ODUkP-h/ETH\_A\_So) + +The ODUkP-h/ETH\_A\_So function creates the ODUk signal from a free-running clock. It maps the ETH\_CI information into the payload of the OPUk (k = flex), adds the OPUk overhead (CSF, RCOH, RES, PT) and default ODUk overhead. + +#### Symbol + +![Symbol diagram for ODUkP-h/ETH_A_So function. The central block is labeled 'ODUkP-h/ETH'. Inputs from the top are ETH_TFP and ETH_FP. Inputs from the left are ODUkP-h/ETH_A_So_MP and ETH_RP. Outputs to the right are ETHTF_PP and ETHF_PP. Output to the bottom is ODUkP_AP. Reference G.798(17)_F14-67 is shown at the bottom right.](40e222d90fe6d142ea9c2c893d7de5df_img.jpg) + +Symbol diagram for ODUkP-h/ETH\_A\_So function. The central block is labeled 'ODUkP-h/ETH'. Inputs from the top are ETH\_TFP and ETH\_FP. Inputs from the left are ODUkP-h/ETH\_A\_So\_MP and ETH\_RP. Outputs to the right are ETHTF\_PP and ETHF\_PP. Output to the bottom is ODUkP\_AP. Reference G.798(17)\_F14-67 is shown at the bottom right. + +Figure 14-67 – ODUkP-h/ETH\_A\_So symbol + +#### Interfaces + +Table 14-31 – ODUkP-h/ETH\_A\_So interfaces + +| Inputs | Outputs | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE

ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF
ETH_CI_SSFrdi
ETH_CI_SSFfdi | ODUkP_AP:
ODUkP_AI_Data
ODUkP_AI_Clock
ODUkP_AI_FrameStart
ODUkP_AI_MultiframeStart
ODUkP_(A/M)I_RP
ODUkP_(A/M)I_TSCC

ETHTF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE | + +**Table 14-31 – ODUkP-h/ETH\_A\_So interfaces** + +| Inputs | Outputs | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------| +| ODUkP_RP:
ODUkP_RI_RP
ODUkP_RI_TSCC
ODUkP_RI_NCS

ODUkP-h/ETH_A_So_MP:
ODUkP-h/ETH_A_So_MI_CSFEnable
ODUkP-h/ETH_A_So_MI_CSFrdifdiEnable
ODUkP-h/ETH_A_So_MI_INCREASE
ODUkP-h/ETH_A_So_MI_DECREASE
ODUkP-h/ETH_A_So_MI_TSNUM
ODUkP-h/ETH_A_So_MI_ODUflexRate | ETHF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ODUkP-h/ETH_A_So_MP:
ODUkP-h/ETH_A_So_MI_ADJSTATE | +| NOTE – (A/M)I_xxx indicates that the xxx signal may either be an AI_xxx or an MI_xxx signal. | | + +**Processes** + +A process diagram of this function is shown in Figure 14-68. + +![Figure 14-68 – ODUkP-h/ETH_A_So process diagram showing the flow of data and control signals through various processing blocks.](4d9c52be1198628362ec7871f6e0f530_img.jpg) + +The diagram illustrates the ODUkP-h/ETH\_A\_So process flow. It shows the following components and signal paths: + +- External Inputs:** + - ETH\_CI\_SSF (ETH\_FP) and ETH\_CI\_D/P/DE (ETH\_TFP) enter from the top. + - ETH\_CI\_D/P/DE SSF/SSFrdi/SSFfdi (ETH\_FP) enters from the top right. + - MI\_CSFenable and MI\_CSFrdifdiEnable enter from the left. + - FCSEnable = false, CMuxConfig, and CMuxActive = false enter from the left. +- Internal Process Flow:** + - Inputs enter a large grey box containing several process blocks. + - Top level: **Client-specific processes** receive inputs and output **ETH\_PI\_D/P/DE (ETHF\_PP)** to the right. + - Below this, **802.3 MAC FCS generation** receives **ETH\_CI** and outputs a **MAC Frame**. + - The **MAC Frame** and other inputs enter **ETH specific GFP-F processes**. + - Output from this block is **GFP\_FS** and **GFP\_Frame**. + - These enter **Common GFP-F processes**. + - Output is again **GFP\_FS** and **GFP\_Frame**. + - These enter **ODUkP specific GFP-F processes**. + - Output is **ODUkP\_AI\_D**. + - This enters the bottom **ODUkP specific processes** block, which also receives **ODUkP\_AI\_CK/FS**. + - The final output from the bottom block is **ODUkP\_AI\_D/CK/FS/MFS**. +- External Output:** + - ODUkP\_AI\_D/CK/FS/MFS** exits from the bottom of the grey box. + +G.798(17)-Amd.4(22)\_F14-68 + +Figure 14-68 – ODUkP-h/ETH\_A\_So process diagram showing the flow of data and control signals through various processing blocks. + +**Figure 14-68 – ODUkP-h/ETH\_A\_So process** + +The client-specific processes, and associated MI and PI signals, are specified in clause 9.5 of [ITU-T G.8021]. + +### 802.3 MAC FCS generation: + +See clause 8.6.1 of [ITU-T G.802.1]. + +### Ethernet specific GFP-F source process: + +See clause 8.5.4.1.1 of [ITU-T G.806]. GFP pFCS generation is disabled (FCSenable=false). The UPI value for frame-mapped Ethernet shall be inserted (Table 6-3 of [ITU-T G.704]). The Ethernet frames are inserted into the client payload information field of the GFP-F frames according to clause 7.1 of [ITU-T G.704]. + +### Common GFP source process: + +See clause 8.5.3.1 of [ITU-T G.806]. GFP channel multiplexing is not supported (CMuxActive=false). + +### ODUkP specific GFP source process: + +See clause 8.5.2.1 of [ITU-T G.806]. The GFP frames are mapped into the ODUk payload area according to clause 17.4 of [ITU-T G.709]. + +### ODUkP specific source process: + +![Block diagram of the ODUkP-h (k=flex) specific source process. The diagram shows the internal components and signal flow for generating the ODUkP signal. On the left, input signals D, SSF, and FS CK enter the process. The D signal is processed through a series of blocks: 'Insert RCOH', 'Insert PT', 'Insert CSF', 'Insert RES', and 'ODUk OH is set to all-0's, except PM STAT = 001'. The SSF signal is used in the 'Insert CSF' block. The FS CK signal is fed into an 'Adjustable free-running clock generator (ODCa)'. The ODCa generates a CK signal, which is divided by 122368 to produce an FS signal, and then by 256 to produce an MFS signal. These signals (CK, FS, MFS) are fed into a 'BWR generator'. The BWR generator also receives control signals: MI_ODUflexRate, MI_INCREASE, MI_DECREASE, MI_TSNUM, MI_ADJSTATE, RI_RP, RI_TSCC, and RI_NCS. It outputs NCS and BWR_IND signals. The BWR_IND signal is fed back to the 'Insert RCOH' and 'Insert CSF' blocks. The final output signals are AI_D, AI_CK, AI_FS, AI_MFS, xL_RP, xL_TSCC, and x = A/M. The diagram is labeled G.798(23)_F14-69.](ade808c7cde5b576488a326d288f29eb_img.jpg) + +Block diagram of the ODUkP-h (k=flex) specific source process. The diagram shows the internal components and signal flow for generating the ODUkP signal. On the left, input signals D, SSF, and FS CK enter the process. The D signal is processed through a series of blocks: 'Insert RCOH', 'Insert PT', 'Insert CSF', 'Insert RES', and 'ODUk OH is set to all-0's, except PM STAT = 001'. The SSF signal is used in the 'Insert CSF' block. The FS CK signal is fed into an 'Adjustable free-running clock generator (ODCa)'. The ODCa generates a CK signal, which is divided by 122368 to produce an FS signal, and then by 256 to produce an MFS signal. These signals (CK, FS, MFS) are fed into a 'BWR generator'. The BWR generator also receives control signals: MI\_ODUflexRate, MI\_INCREASE, MI\_DECREASE, MI\_TSNUM, MI\_ADJSTATE, RI\_RP, RI\_TSCC, and RI\_NCS. It outputs NCS and BWR\_IND signals. The BWR\_IND signal is fed back to the 'Insert RCOH' and 'Insert CSF' blocks. The final output signals are AI\_D, AI\_CK, AI\_FS, AI\_MFS, xL\_RP, xL\_TSCC, and x = A/M. The diagram is labeled G.798(23)\_F14-69. + +**Figure 14-69 – ODUkP-h (k=flex) specific source process** + +### Adjustable clock and (multi)frame start signal generation: + +The function shall generate a local ODUk clock (ODUkP\_AI\_CK) with a clock rate within the minimum to maximum clock rate of the ODUflex signal as given in Table 7-2 of [ITU-T G.709]. The jitter and wander requirements as defined in Annex A of [ITU-T G.825] (ODCa clock) apply. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUk signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +PT: The payload type information is derived directly from the adaptation function type. The value for "GFP mapping" shall be inserted into the PT byte position of the PSI overhead as defined in clause 15.9.2.1.1 of [ITU-T G.709]. The PT value of a hao-capable adaptation function should remain the same as a non-hao-capable one. + +RES: The function shall insert all-ZEROs into the RES bytes. + +CSF: The function shall signal the failure of the client signal to the far end by use of Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +All other bits of the ODUk overhead should be sourced as "0"s, except the PMOH STAT field which should be set to the value "normal path signal" (001). + +*Counter processes:* + +For further study. + +**RCOH generator:** This process inserts the NCS generated by the HAO process into the NCS field of the RCOH in OPUflex. + +**BWR\_Generator:** This process is used for BWR protocol adjustment processing and the generation of the BWR protocol overhead. It contains the following processes as shown in Figure 14-70. + +*Adjustment activation:* When MI\_INCREASE or MI\_DECREASE is true, the BWR protocol is activated and RI processing is started. + +*Rate adjustment control:* Generates ODUflex clock control signal. The original ODUflex clock rate will gradually change to the new ODUflex clock rate so that no GMP buffer overflow or underflow will occur in the ODUflex network connection. Refer to [ITU-T G.7044]. + +![Figure 14-70 – BWR_Generator process block diagram. The diagram shows a large grey box representing the BWR_Generator process. Inside, there are three main components: 'Adjustment activation', 'RI processing', and 'Rate adjustment control'. 'Adjustment activation' receives 'CK', 'FS', and 'MFS' inputs from the top and 'MI_INCREASE' and 'MI_DECREASE' inputs from the right. It outputs to 'RI processing'. 'RI processing' receives 'RI_RP', 'RI_TSCC', and 'RI_NCS' inputs from the left and an input from 'Adjustment activation'. It outputs 'NCS' and 'BWR_IND' to the left, 'MI_ADJSTATE' to the right, and 'xl_RP' and 'xl_TSCC' to the bottom. 'Rate adjustment control' receives an input from 'RI processing' and 'MI_TSNUM' from the right. It outputs 'ODUflex clock control information' to the bottom. The 'BWR_generator' label is at the bottom right of the box. The diagram is labeled G.798(17)_F14-70.](40043f81129f46859efbb0379984a286_img.jpg) + +Figure 14-70 – BWR\_Generator process block diagram. The diagram shows a large grey box representing the BWR\_Generator process. Inside, there are three main components: 'Adjustment activation', 'RI processing', and 'Rate adjustment control'. 'Adjustment activation' receives 'CK', 'FS', and 'MFS' inputs from the top and 'MI\_INCREASE' and 'MI\_DECREASE' inputs from the right. It outputs to 'RI processing'. 'RI processing' receives 'RI\_RP', 'RI\_TSCC', and 'RI\_NCS' inputs from the left and an input from 'Adjustment activation'. It outputs 'NCS' and 'BWR\_IND' to the left, 'MI\_ADJSTATE' to the right, and 'xl\_RP' and 'xl\_TSCC' to the bottom. 'Rate adjustment control' receives an input from 'RI processing' and 'MI\_TSNUM' from the right. It outputs 'ODUflex clock control information' to the bottom. The 'BWR\_generator' label is at the bottom right of the box. The diagram is labeled G.798(17)\_F14-70. + +**Figure 14-70 – BWR\_Generator process** + +*RI processing:* This performs BWR protocol processing according to the RI\_RP, RI\_TSCC, RI\_NCS signals received from the BWR\_Receiver process. + +- When RI processing is activated, xl\_RP and xl\_TSCC (x is A or M) signals are set to one (1). +- The value of the NCS signal is set to ACK(1) when receiving RI\_RP=1 and the value of RI\_TSCC is changed from 0 to 1. + +- Rate adjustment control is activated when receiving RI\_RP=1 and RI\_TSCC=1 and RI\_NCS=ACK(1). +- BWR\_IND is set to "1" x $\mu$ s before the ODUflex signal's bit rate adjustment starts, and is set to "0" y $\mu$ s before the ODUflex signal's bit rate adjustment is completed. x is almost equal to y and shall be in the range of 125 to 250 $\mu$ s. +- The value of xI\_TSCC signal is set to 0 when rate adjustment is completed. +- The value of the NCS signal is set to NACK(0) when receiving RI\_RP=1 and the value of RI\_TSCC is changed from 1 to 0. +- The value of the RP signal is set to 0 when receiving RI\_NCS=NACK(0) and sending NCS=NACK(0). +- The completion of the resize process is reported to the NMS when receiving RI\_RP=0. + +### Defects + +None. + +### Consequent actions + +aCSF-RDI $\leftarrow$ CI\_SSFrdi and CSFrdifdiEnable and CSFEnable + +aCSF-FDI $\leftarrow$ CI\_SSFfdi and CSFrdifdiEnable and CSFEnable + +aCSF-LOS $\leftarrow$ CI\_SSF and CSFEnable + +aCSF-OPU $\leftarrow$ CI\_SSF and CSFEnable + +### Defect correlations + +None. + +### Performance monitoring + +For further study. + +### 14.3.12.2 HAO-capable ODUk to ETH adaptation sink function (ODUkP-h/ETH\_A\_Sk) + +The ODUkP-h/ETH\_A\_Sk extracts ETH\_CI information from the ODUkP payload area, delivering ETH\_CI to ETH\_TFP and ETH\_FP. It extracts the OPUk overhead (PT, RCOH, CSF and RES) and monitors the reception of the correct payload type. + +### Symbol + +![Symbol diagram for ODUkP-h/ETH_A_Sk. The central block is labeled 'ODUkP-h/ETH'. It has two input arrows on the left labeled 'ETHF_PP' and 'ETHF_PP'. It has two output arrows on top labeled 'ETH_TFP' and 'ETH_FP'. It has one output arrow on the right labeled 'ODUkP-h/ETH_A_Sk_MP'. It has one input arrow on the bottom labeled 'ODUkP_AP'. The text 'G.798(17)_F14-71' is located at the bottom right of the diagram.](592c06cc12480f3bcfcbe826668abfa4_img.jpg) + +Symbol diagram for ODUkP-h/ETH\_A\_Sk. The central block is labeled 'ODUkP-h/ETH'. It has two input arrows on the left labeled 'ETHF\_PP' and 'ETHF\_PP'. It has two output arrows on top labeled 'ETH\_TFP' and 'ETH\_FP'. It has one output arrow on the right labeled 'ODUkP-h/ETH\_A\_Sk\_MP'. It has one input arrow on the bottom labeled 'ODUkP\_AP'. The text 'G.798(17)\_F14-71' is located at the bottom right of the diagram. + +Figure 14-71 – ODUkP-h/ETH\_A\_Sk symbol + +## Interfaces + +Table 14-32 – ODUkP-h/ETH\_A\_Sk interfaces + +| Inputs | Outputs | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUkP_AP:
ODUkP_AI_Data
ODUkP_AI_ClocK
ODUkP_AI_FrameStart
ODUkP_AI_MultiframeStart
ODUkP_AI_TSF
ODUkP_(A/M)I_RP
ODUkP_(A/M)I_TSCC

ETHTF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ETHF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ODUkP-h/ETH_A_Sk_MP:
ODUkP-h/ETH_A_Sk_MI_CSF_Reported
ODUkP-h/ETH_A_Sk_MI_MAC_Length
ODUkP-h/ETH_A_Sk_MI_CSFdifdiEnable
ODUkP-h/ETH_A_Sk_MI_INCREASE
ODUkP-h/ETH_A_Sk_MI_DECREASE | ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF

ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF
ETH_CI_SSFrdi
ETH_CI_SSFfdi

ODUkP_RP:
ODUkP_RI_RP
ODUkP_RI_TSCC
ODUkP_RI_NCS

ODUkP-h/ETH_A_Sk_MP:
ODUkP-h/ETH_A_Sk_MI_AcPT
ODUkP-h/ETH_A_Sk_MI_AcEXI
ODUkP-h/ETH_A_Sk_MI_AcUPI
ODUkP-h/ETH_A_Sk_MI_cPLM
ODUkP-h/ETH_A_Sk_MI_cLFD
ODUkP-h/ETH_A_Sk_MI_cUPM
ODUkP-h/ETH_A_Sk_MI_cEXM
ODUkP-h/ETH_A_Sk_MI_cCSF
ODUkP-h/ETH_A_Sk_MI_pFCSErrors | + +## Processes + +A process diagram of this function is shown in Figure 14-72. + +![Diagram of the ODUkP-h/ETH_A_Sk process stack. The stack consists of several layers: Client-specific processes (top), 802.3 MAC FCS check, MAC length check, ETH specific GFP-F processes, Common GFP-F processes, ODUkP specific GFP-F processes, and ODUkP specific processes (bottom). Data flows upwards through the stack, with various signals and parameters like SF, MAC Frame, GFP_Frame/FS/SF, and ODUkP_AI_D/CK/FS/MFS/TSF being passed between layers. External signals include ETH_CI_D/P/DE/SSF (ETH_TFP), ETH_CI_D/P/DE/SSF/SSFrdi/SSFrdi (ETH_FP), ETH_PI_D/P/DE (ETHF_PP), MI_pFCSErrors, MI_MAC_Lenght, MI_cUPM, MI_cEXM, MI_cLFD, MI_cPLM, MI_cCSF, MI_AcUPI, MI_AcEXI, MI_CSFrdifdiEnable, CMuxConfig, CMuxActive = false, FCSdiscard = false, and MI_AcPT. The diagram is labeled G.798(17)-Amd.4(22)_F14-72.](79e6576a312f8ddac8c706d78fae4bcf_img.jpg) + +Diagram of the ODUkP-h/ETH\_A\_Sk process stack. The stack consists of several layers: Client-specific processes (top), 802.3 MAC FCS check, MAC length check, ETH specific GFP-F processes, Common GFP-F processes, ODUkP specific GFP-F processes, and ODUkP specific processes (bottom). Data flows upwards through the stack, with various signals and parameters like SF, MAC Frame, GFP\_Frame/FS/SF, and ODUkP\_AI\_D/CK/FS/MFS/TSF being passed between layers. External signals include ETH\_CI\_D/P/DE/SSF (ETH\_TFP), ETH\_CI\_D/P/DE/SSF/SSFrdi/SSFrdi (ETH\_FP), ETH\_PI\_D/P/DE (ETHF\_PP), MI\_pFCSErrors, MI\_MAC\_Lenght, MI\_cUPM, MI\_cEXM, MI\_cLFD, MI\_cPLM, MI\_cCSF, MI\_AcUPI, MI\_AcEXI, MI\_CSFrdifdiEnable, CMuxConfig, CMuxActive = false, FCSdiscard = false, and MI\_AcPT. The diagram is labeled G.798(17)-Amd.4(22)\_F14-72. + +**Figure 14-72 – ODUkP-h/ETH\_A\_Sk process** + +The client-specific processes, and associated MI and PI signals, are specified in clause 9.5 of [ITU-T G.8021]. + +*802.3 MAC FCS check process:* + +See clause 8.6.2 of [ITU-T G.8021]. + +*MAC length check process:* + +See clause 8.5 of [ITU-T G.8021]. + +*Ethernet specific GFP-F sink process:* + +See clause 8.5.4.1.2 of [ITU-T G.806]. GFP pFCS checking, GFP p\_FCSError, p\_FDis are not supported (FCSdiscard=false). The UPI value for frame-mapped Ethernet shall be expected (Table 6-3 of [ITU-T G.7041]). The Ethernet frames are extracted from the client payload information field of the GFP-F frames according to clause 7.1 of [ITU-T G.7041]. + +*Common GFP sink process:* + +See clause 8.5.3.2 of [ITU-T G.806]. GFP channel multiplexing is not supported (MI\_CMuxActive=false). + +*ODUkP specific GFP sink process:* + +See clause 8.5.2.2 of [ITU-T G.806]. The GFP frames are demapped from the ODUk payload area according to clause 17.4 of [ITU-T G.709]. + +ODUkP specific sink process: + +![Figure 14-73 – ODUkP (k=flex) specific sink process. This block diagram shows the internal components of an ODUkP sink. On the left, external signals MI_INCREASE, MI_DECREASE, RI_RP, RI_TSCC, and RI_NCS enter a 'BWR receiver' block. The 'BWR receiver' outputs NCS to three parallel extraction blocks: 'Extract RCOH', 'Extract CSF', and 'Extract PT'. 'Extract RCOH' outputs NCS, 'Extract CSF' outputs dCSF, and 'Extract PT' outputs to a 'PT process' block. The 'PT process' outputs MI_AcPT and dPLM. A 'Defect correlations' block receives dPLM, dCSF, and AI_TSF as inputs and outputs MI_cPLM and MI_cCSF. External signals D, CK, and FS enter from the top, while AI_D, AI_MFS, AI_CK, AI_FS, and AI_TSF enter from the bottom. The entire process is labeled ODUkP_AP and G.798(23)_F14-73.](5e90ca04dc493a9f9aabbdbb720d39d6_img.jpg) + +Figure 14-73 – ODUkP (k=flex) specific sink process. This block diagram shows the internal components of an ODUkP sink. On the left, external signals MI\_INCREASE, MI\_DECREASE, RI\_RP, RI\_TSCC, and RI\_NCS enter a 'BWR receiver' block. The 'BWR receiver' outputs NCS to three parallel extraction blocks: 'Extract RCOH', 'Extract CSF', and 'Extract PT'. 'Extract RCOH' outputs NCS, 'Extract CSF' outputs dCSF, and 'Extract PT' outputs to a 'PT process' block. The 'PT process' outputs MI\_AcPT and dPLM. A 'Defect correlations' block receives dPLM, dCSF, and AI\_TSF as inputs and outputs MI\_cPLM and MI\_cCSF. External signals D, CK, and FS enter from the top, while AI\_D, AI\_MFS, AI\_CK, AI\_FS, and AI\_TSF enter from the bottom. The entire process is labeled ODUkP\_AP and G.798(23)\_F14-73. + +Figure 14-73 – ODUkP (k=flex) specific sink process + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The payload type value for "GFP mapping" in clause 15.9.2.1.1 of [ITU-T G.709] shall be expected. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. The PT value of a hao-capable adaptation function should remain the same as a non-hao-capable one. + +**CSF:** The function shall extract the CSF signal indicating the failure of the client signal out of Bit 1 of the PSI[2] byte of the payload structure identifier as defined in [ITU-T G.709], clause 17.1. + +**RES:** The value in the RES bytes shall be ignored. + +**RCOH receiver:** This process extracts the NCS from the RCOH overhead area, and then forwards it to BWR\_Receiver. + +**BWR\_Receiver:** This process extracts and detects the BWR protocol overhead, with the exception of the BWR\_IND signal. It is shown in Figure 14-74. + +When MI\_INCREASE or MI\_DECREASE is true, the BWR protocol is activated and starts to receive AI\_RP/MI\_RP, AI\_TSCC/MI\_TSCC from the BWR\_RELAY\_Receiver process and the NCS from the extract NCS process. Then the detected values of the RP, TSCC and NCS are sent to the BWR generator. + +![Figure 14-74 – BWR_Receiver process. This block diagram shows the internal components of a BWR receiver. External signals NCS, xI_RP, CK, FS, and MFS enter from the top. MI_INCREASE and MI_DECREASE enter from the right. The 'BWR OH detecting processing' block receives NCS, xI_RP, CK, FS, MFS, MI_INCREASE, and MI_DECREASE. It outputs to the 'Forwarding processing' block. The 'Forwarding processing' block outputs RI_RP, RI_TSCC, and RI_NCS to the left. The entire process is labeled BWR_receiver and G.798(17)_F14-74.](d988db7a59b060ff3406236569343e4f_img.jpg) + +Figure 14-74 – BWR\_Receiver process. This block diagram shows the internal components of a BWR receiver. External signals NCS, xI\_RP, CK, FS, and MFS enter from the top. MI\_INCREASE and MI\_DECREASE enter from the right. The 'BWR OH detecting processing' block receives NCS, xI\_RP, CK, FS, MFS, MI\_INCREASE, and MI\_DECREASE. It outputs to the 'Forwarding processing' block. The 'Forwarding processing' block outputs RI\_RP, RI\_TSCC, and RI\_NCS to the left. The entire process is labeled BWR\_receiver and G.798(17)\_F14-74. + +Figure 14-74 – BWR\_Receiver process + +## Defects + +dPLM – See clause 6.2.4.1. + +dLFD – See clause 6.2.5.2 of [ITU-T G.806]. +dUPM – See clause 6.2.4.3 of [ITU-T G.806]. +dEXM – See clause 6.2.4.4 of [ITU-T G.806]. +dCSF-LOS – See clause 8.6.4.2 of [ITU-T G.8021]. +dCSF-RDI – See clause 8.6.4.2 of [ITU-T G.8021]. +dCSF-FDI – See clause 8.6.4.2 of [ITU-T G.8021]. +dCSF-OPU – See clause 6.2.10. + +### Consequent actions + +The function shall perform the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF or dPLM or dLFD or dUPM or dEXM or dCSF-LOS +aSSRdi $\leftarrow$ dCSF-RDI and CSFrdifdiEnable +aSSRfdi $\leftarrow$ dCSF-FDI and CSFrdifdiEnable + +### Defect correlations + +The function shall perform the following defect correlations to determine the most probable fault cause (see clause 6.4 of [ITU-T G.806]). This fault cause shall be reported to the EMF. + +cPLM $\leftarrow$ dPLM and (not AI\_TSF); +cLFD $\leftarrow$ dLFD and (not dPLM) and (not AI\_TSF); +cUPM $\leftarrow$ dUPM and (not dEXM) and (not dPLM) and (not dLFD) and (not AI\_TSF); +cEXM $\leftarrow$ dEXM and (not dPLM) and (not dLFD) and (not AI\_TSF) +cCSF $\leftarrow$ (dCSF-LOS or dCSF-OPU or dCSF-FDI) and (not dEXM) and (not dUPM) and (not dPLM) and (not dLFD) and (not AI\_TSF) and CSF\_Reported + +### Performance monitoring + +The function shall perform the following performance monitoring primitives processing. The performance monitoring primitives shall be reported to the EMF. + +pFCSErrors: count of FrameCheckSequenceErrors per second. + +NOTE – This primitive is calculated by the MAC FCS check process. + +### 14.3.13 HAO-capable ODUkP-h to ODUj payload type 21 adaptation function (ODUkP-h/ODUj-21\_A) + +The HAO-capable ODUkP to ODUj payload type 21 adaptation functions perform the adaptation between the ODUkP ( $k = 2, 3, 4, 25u, 25, 50u, 50$ ) layer adapted information and the characteristic information of ODUj ( $j = 0, 1, 2, 2e, 3, flex$ ) signals. + +![Diagram of HAO-capable ODUkP-h/ODUj-21_A function. A central trapezoidal block labeled 'ODUkP-h/ODUj-21' has multiple tributary ports (1, 2, ..., n) at the top, each connected to an 'ODUj_CP'. Below the block, a single connection point is labeled 'ODUkP_AP'. The text 'G.798(17)_F14-75' is at the bottom right.](c79d10d97e1f525e9c85e96e91616923_img.jpg) + +Diagram of HAO-capable ODUkP-h/ODUj-21\_A function. A central trapezoidal block labeled 'ODUkP-h/ODUj-21' has multiple tributary ports (1, 2, ..., n) at the top, each connected to an 'ODUj\_CP'. Below the block, a single connection point is labeled 'ODUkP\_AP'. The text 'G.798(17)\_F14-75' is at the bottom right. + +**Figure 14-75 – HAO-capable ODUkP-h/ODUj-21\_A function** + +Three different types of functions are possible: + +- the ODU2P-h/ODUj-21\_A performs multiplexing/demultiplexing of any LO ODU with a bit rate less than the OPU2 payload bit rate into an OPU2; +- the ODU3P-h/ODUj-21\_A performs multiplexing/demultiplexing of any LO ODU with a bit rate less than the OPU3 payload bit rate into an OPU3; +- the ODU4P-h/ODUj-21\_A performs multiplexing/demultiplexing of any LO ODU with a bit rate less than the OPU4 payload bit rate into an OPU4; +- the ODU25(u)P-h/ODUj-21\_A performs multiplexing/demultiplexing of any LO ODU with a bit rate less than the OPU25(u) payload bit rate into an OPU25(u); +- the ODU50(u)P-h/ODUj-21\_A performs multiplexing/demultiplexing of any LO ODU with a bit rate less than the OPU50(u) payload bit rate into an OPU50(u). + +Tributary ports are dynamically created and deleted under the control of management. Each tributary port is associated with one ODUj connection point on one side, and the M OPUk tributary slots on the other. The multiplex structure identifier (MSI) carries the configuration of tributary ports to tributary slots. + +**14.3.13.1 HAO-capable ODUkP to ODUj payload type 21 adaptation source function (ODUkP-h/ODUj\_A\_So)** + +The HAO-capable ODUkP/ODUj-21\_A\_So function creates the ODUk signal from a free-running clock. It asynchronously maps the ODUj client signal from the $n \times$ ODUj CPs into ODTUjk or ODTUk.M including the justification control (JC) information. The ODTUjk and ODTUk.M are multiplexed into the tributary slots of the OPUk. It adds the OPUk overhead (RES, PT, MSI, OMFI) and default ODUk overhead. It provides access to the ODUk PM APS overhead. + +The information flow and processing of the HAO-capable ODUkP/ODUj-21\_A\_So function is defined with reference to Figures 14-76, 14-77 and 14-78. + +**Symbol** + +![Diagram of ODUkP-h/ODUj-21_A_So function. A central trapezoidal block labeled 'ODUkP-h/ODUj-21' has multiple tributary ports (1, 2, ..., n) at the top, each connected to an 'ODUj_CP'. On the left side, there are two input arrows labeled 'ODUkP-h/ODUj-21_A_So_MP' and 'ODUkP_PP'. On the right side, there are two output arrows labeled 'ODUkP-h/ODUj-21_A_So_RP' and 'ODUk_TP'. Below the block, a single connection point is labeled 'ODUkP_AP'. The text 'G.798(17)_F14-76' is at the bottom right.](abf91c0fe8bc45562f2bc9adc2d5d58a_img.jpg) + +Diagram of ODUkP-h/ODUj-21\_A\_So function. A central trapezoidal block labeled 'ODUkP-h/ODUj-21' has multiple tributary ports (1, 2, ..., n) at the top, each connected to an 'ODUj\_CP'. On the left side, there are two input arrows labeled 'ODUkP-h/ODUj-21\_A\_So\_MP' and 'ODUkP\_PP'. On the right side, there are two output arrows labeled 'ODUkP-h/ODUj-21\_A\_So\_RP' and 'ODUk\_TP'. Below the block, a single connection point is labeled 'ODUkP\_AP'. The text 'G.798(17)\_F14-76' is at the bottom right. + +**Figure 14-76 – ODUkP-h/ODUj-21\_A\_So function** + +## Interfaces + +Table 14-33 – ODUkP-h/ODUj-21\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n x ODUj_CP:
ODUj_CI_CK
ODUj_CI_D
ODUj_CI_FS
ODUj_CI_MFS
ODUj_CI_APS
ODUj-21_(C/M)I_RP
ODUj-21_(C/M)I_TSCC
ODUk_PP:
ODUk_PI_APS
ODUk_TP:
ODUk_TI_CK
ODUkP-h/ODUj-21_A_So_MP:
ODUkP-h/ODUj-21_A_So_MI_TxMSI
ODUkP-h/ODUj-21_A_So_MI_AUTOpayloadtype (Note 2)
ODUkP-h/ODUj-21_A_So_MI_ODUType_Rate[1..n]
ODUkP-h/ODUj_A_So_MI_AdminState[1..n]
ODUkP-h/ODUj_A_So_MI_APS_EN[1..n]
ODUkP-h/ODUj_A_So_MI_APS_LVL[1..n]
ODUkP-h/ODUj-21_A_So_MI_INCREASE
ODUkP-h/ODUj-21_A_So_MI_DECREASE
ODUkP-h/ODUj-21_A_So_MI_TSMAP
ODUkP-h/ODUj-21_A_So_MI_TPID
ODUkP-h/ODUj-21_A_So_RP:
ODUkP-h/ODUj-21_A_So_RI_AcPT (Note 2)
ODUkP-h/ODUj-21_A_So_RI_RP
ODUkP-h/ODUj-21_A_So_RI_CTRL
ODUkP-h/ODUj-21_A_So_RI_TSGS
ODUkP-h/ODUj-21_A_So_RI_TPID | ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_MFS
ODUkP-h/ODUj-21_A_So_RP:
ODUkP-h/ODUj-21_A_So_RI_TrPT (Note 2)
ODUkP-h/ODUj-21_A_So_MP:
ODUkP-h/ODUj-21_A_So_MI_TrPT (Note 2)
ODUkP-h/ODUj-21_A_So_MI_ADJSTATE | +| NOTE 1 – (C/M)I_xxx indicates that the xxx signal may either be a CI_xxx or a MI_xxx signal. | | +| NOTE 2 – For ODU2P-h/ODUj-21_A_So and ODU3P-h/ODUj-21_A_So only. | | + +## Processes + +The processes associated with the HAO-capable ODUkP-h/ODUj-21\_A\_So function are specific processes for each ODUj\_CP and common processes for the compound (multiplexed) signal as depicted in Figures 14-77 and 14-78. + +![Figure 14-77 – ODUkP-h/ODUj-21_A_So processes. This block diagram illustrates the internal structure of the ODUkP-h/ODUj-21_A_So processes. At the top, multiple client-specific processes (ODUj_CP[1] to ODUj_CP[n]) are shown, each with inputs like CI_MFS, CI_FS, CI_CK, CI_D, and CI_APS. These connect to a central 'Multiplexer' block. The multiplexer outputs are labeled OMFS, MFS, FS, CK, and TS#. Below the multiplexer, the 'Multiplex structure identifier (MSI)' is generated, taking inputs from the multiplexer and MGSI. The 'Payload type (PT)' and 'RES' fields are also processed. The 'ODUk PM APS' field is generated from the multiplexer outputs. A block for 'for k = 4, 25(u), 50(u)' contains an 'OMFI' block and a '1/80' divider. The 'ODUk OH is set to all-0's, except PM STAT = 001' block is also present. An 'RCOH generator' block produces various overhead signals. At the bottom, the 'ODUkP_AP' section includes 'AI_D', 'AI_MFS', 'AI_FS', and 'AI_CK' signals. On the right, a 'HAO process (if needed)' block is shown with various input and output signals. The entire diagram is labeled with 'G.798(17)-Amd.3(21)_F14-77'.](9e290fa7e4578ba0a8b8c5008c99b564_img.jpg) + +The diagram illustrates the internal structure of the ODUkP-h/ODUj-21\_A\_So processes. At the top, multiple client-specific processes (ODUj\_CP[1] to ODUj\_CP[n]) are shown, each with inputs like CI\_MFS, CI\_FS, CI\_CK, CI\_D, and CI\_APS. These connect to a central 'Multiplexer' block. The multiplexer outputs are labeled OMFS, MFS, FS, CK, and TS#. Below the multiplexer, the 'Multiplex structure identifier (MSI)' is generated, taking inputs from the multiplexer and MGSI. The 'Payload type (PT)' and 'RES' fields are also processed. The 'ODUk PM APS' field is generated from the multiplexer outputs. A block for 'for k = 4, 25(u), 50(u)' contains an 'OMFI' block and a '1/80' divider. The 'ODUk OH is set to all-0's, except PM STAT = 001' block is also present. An 'RCOH generator' block produces various overhead signals. At the bottom, the 'ODUkP\_AP' section includes 'AI\_D', 'AI\_MFS', 'AI\_FS', and 'AI\_CK' signals. On the right, a 'HAO process (if needed)' block is shown with various input and output signals. The entire diagram is labeled with 'G.798(17)-Amd.3(21)\_F14-77'. + +Signals and blocks include: +- ODUj\_CP[1] ... ODUj\_CP[n] +- CI\_MFS, CI\_FS, CI\_CK, CI\_D, CI\_APS +- MI\_AdminState[1..n], MI\_APS\_EN[1..n], MI\_APS\_LVL[1..n], MI\_ODUType\_Rate[1..n], BWR\_IND, MGSI, GMP\_MODE, CK\_Control +- Multiplexer (OMFS, MFS, FS, CK, D, TS#) +- Multiplex structure identifier (MSI) +- Payload type (PT) +- RES +- ODUk PM APS +- OMFI, $\frac{1}{80}$ +- ODUk OH is set to all-0's, except PM STAT = 001 +- $\frac{1}{256}$ , $\frac{1}{122368}$ +- ODCa clock generator, Free-running clock generator +- RCOH generator (MI\_INCREASE, MI\_DECREASE, MI\_TSMAP, RP, TSCC, CTRL, TSGS, TPID) +- HAO process (if needed) (RP, CTRL, TSGS, TPID, TSCC, CK, FS, (O)MFS, BWR\_IND) +- RI\_RP, RI\_CTRL, RI\_TSGS, RI\_TPID, MI\_INCREASE, MI\_DECREASE, MI\_TSMAP, MI\_TPID, MI\_ADJSTATE +- MI\_TxMSI, MI\_AUTOPayloadtype, MI\_TrPT, RI\_TrPT, RI\_AcPT, RI\_RP, RI\_CTRL, RI\_TSGS, RI\_TPID, PI\_APS, TI\_CK +- AI\_D, AI\_MFS, AI\_FS, AI\_CK (ODUkP\_AP) + +Figure 14-77 – ODUkP-h/ODUj-21\_A\_So processes. This block diagram illustrates the internal structure of the ODUkP-h/ODUj-21\_A\_So processes. At the top, multiple client-specific processes (ODUj\_CP[1] to ODUj\_CP[n]) are shown, each with inputs like CI\_MFS, CI\_FS, CI\_CK, CI\_D, and CI\_APS. These connect to a central 'Multiplexer' block. The multiplexer outputs are labeled OMFS, MFS, FS, CK, and TS#. Below the multiplexer, the 'Multiplex structure identifier (MSI)' is generated, taking inputs from the multiplexer and MGSI. The 'Payload type (PT)' and 'RES' fields are also processed. The 'ODUk PM APS' field is generated from the multiplexer outputs. A block for 'for k = 4, 25(u), 50(u)' contains an 'OMFI' block and a '1/80' divider. The 'ODUk OH is set to all-0's, except PM STAT = 001' block is also present. An 'RCOH generator' block produces various overhead signals. At the bottom, the 'ODUkP\_AP' section includes 'AI\_D', 'AI\_MFS', 'AI\_FS', and 'AI\_CK' signals. On the right, a 'HAO process (if needed)' block is shown with various input and output signals. The entire diagram is labeled with 'G.798(17)-Amd.3(21)\_F14-77'. + +**Figure 14-77 – ODUkP-h/ODUj-21\_A\_So processes** + +![Figure 14-78 – ODUkP-h/ODUj-21_A_So client specific processes. This block diagram illustrates the internal processes of an ODUj client signal. At the top, the ODUj_CP[p] signal is shown with its components: CL_MFS, CL_FS, CL_CK, CL_D, and CL_APS. The diagram shows the flow of data and control signals through various functional blocks: an OPUflex RCOH receiver, an ODU-LCK generator, a 'Select normal/LCK' block, an ODUj APS block, a FAS/MFAS insertion block, an Elastic store (buffer), and a Justification control and JC generation block. External control signals include BWR_IND, MI_AdminState[p], MI_APS_EN[p], MI_APS_LVL[p], MGSI, GMP_MODE, CK_Control, and MI_ODUType_Rate[p]. Input signals at the bottom are OMFS, MFS, FS, CK, D, and TS#.](169044aee9e8adb39eed822364eed8aa_img.jpg) + +G.798(17)-Amd.3(21)\_F14-78 + +Figure 14-78 – ODUkP-h/ODUj-21\_A\_So client specific processes. This block diagram illustrates the internal processes of an ODUj client signal. At the top, the ODUj\_CP[p] signal is shown with its components: CL\_MFS, CL\_FS, CL\_CK, CL\_D, and CL\_APS. The diagram shows the flow of data and control signals through various functional blocks: an OPUflex RCOH receiver, an ODU-LCK generator, a 'Select normal/LCK' block, an ODUj APS block, a FAS/MFAS insertion block, an Elastic store (buffer), and a Justification control and JC generation block. External control signals include BWR\_IND, MI\_AdminState[p], MI\_APS\_EN[p], MI\_APS\_LVL[p], MGSI, GMP\_MODE, CK\_Control, and MI\_ODUType\_Rate[p]. Input signals at the bottom are OMFS, MFS, FS, CK, D, and TS#. + +**Figure 14-78 – ODUkP-h/ODUj-21\_A\_So client specific processes** + +### Specific processes + +The specific processes are performed independently for each ODUj client signal that is multiplexed into the OPUk. The specific processes perform the mapping of the ODUj into an ODTUjk or ODTUk.M. + +**FAS/MFAS insertion:** The function shall extend the ODUj with the frame alignment overhead (FAS and MFAS) in row one bytes 1 to 7, as described in clause 15.6.2 of [ITU-T G.709]. Bytes 8 to 14 of row one are set to all-ZEROs. + +**Mapping, frequency justification and bit rate adaptation:** The function shall provide an elastic store (buffer) process for the ODUj client signal. The data signal ODUj\_CI shall be written into the buffer under the control of the associated input clock. + +Two justification methods as described below are provided, AMP (*ODTUjk*) and GMP (*ODTUk.M*). The ODU type and rate, as configured via the MI\_ODUType\_Rate[p] input for tributary port #p, determine the mapping method and in the case of GMP mapping, the base value and ranges for the parameters Cn and Cm. + +*ODTUjk:* The data shall be read out of the buffer and written onto the D, NJO, PJO1 and PJO2 bytes of the selected ODTUjk frame under the control of the ODUk clock and the AMP justification decisions, as defined in clause 19.5 of [ITU-T G.709]. + +A justification decision shall be performed two times per OPUk multiframe (jk=12, 13) and eight times per OPUk multiframe (jk=23). Justification decisions are taken at the beginning of the OPUk frame carrying an instance of the ODTUjk justification overhead. Each justification decision results in a corresponding double positive, positive, negative or no justification action in this OPUk frame. Upon a double positive justification action, the reading of two data bytes out of the buffer shall be cancelled once. No ODUj data shall be written onto the PJO2, PJO1 or NJO bytes. Upon a positive justification action, the reading of one data byte out of the buffer shall be cancelled once. No ODUj data shall be written onto the PJO1 or NJO bytes and data shall be written onto the PJO2 byte. Upon a negative justification action, one extra data byte shall be read once out of the buffer. ODUj data shall be written onto the PJO2, PJO1 and NJO bytes. If no justification action is to be performed, ODUj data shall be written onto the PJO2 and PJO1 bytes and no ODUj data shall be written onto the NJO byte. The OPUk frame that contains the PJO2, PJO1 and NJO bytes depends on the tributary slots occupied by the ODTUjk. + +The justification decisions determine the phase error introduced by the function. + +*ODTUk.M:* The data shall be read out of the buffer and written onto groups of M successive bytes of the ODTUk.M payload area under the control of the ODUk clock and the GMP data/stuff control mechanism, as defined in clause 19.6 of [ITU-T G.709]. + +*Buffer size:* In the presence of jitter as specified by [ITU-T G.8251] and a frequency within the range specified in Table 7-2 of [ITU-T G.709], this mapping process shall not introduce any errors. The maximum buffer hysteresis, and therefore the maximum phase error introduced, shall be as listed in Table 14-34. + +**Table 14-34 – Maximum buffer hysteresis** + +| Mapping | Maximum buffer hysteresis | +|----------------|------------------------------------| +| ODUj → ODTUk.M | 4*M bytes | +| ODUj → ODTUjk | 2 bytes (j = 1)
8 bytes (j = 2) | + +**ODTUjk JC:** The function shall generate the justification control bits based on the justification decision according to the specification in clause 19.5 of [ITU-T G.709]. It shall insert the justification control bits in bit 7 and 8 of all three JC bytes of the frame in which the justification is performed. The remaining (RES) bits of the JC byte shall be set to all-ZEROs. The ODUk frame that contains the JC bytes depends on the time slot(s) of the ODTUjk. + +**ODTUk.M JC1/JC2/JC3, JC4/JC5/JC6:** The function shall generate the GMP $C_m$ and GMP $\Sigma C_{nD}$ information and insert this into the JC1/JC2/JC3 and JC4/JC5/JC6 bytes respectively, according to the specification in clause 19.6 and Annex D of [ITU-T G.709]. + +The function shall generate the GMP $C_m$ information (without the GMP $\Sigma C_{nD}$ information) and insert this into the JC1/JC2/JC3 bytes during the GMP special mode, as defined in clauses 7.1.2 and 7.2.2 of [ITU-T G.7044]. + +**ODUj server layer APS:** When APS is enabled for tributary signal #p (MI\_APS\_EN[p] is true), the function shall insert the CI\_APS value into the ODU APS/PCC[MI\_APS\_LVL[p]] field, which is available once per eight ODU frames when the value of the MFAS bits 6, 7, 8 is equal to MI\_APS\_LVL[p]. + +NOTE – The ODUj server layer section APS information may be present in the case where the ODUj signal contains an ODU-AIS, ODU-LCK or ODU-OCI maintenance signal. The ODU-LCK maintenance signal may be inserted in this adaptation source function. ODUj SNC/I protection is unable to detect the insertion of such ODU-LCK and will not perform a protection switch. + +**ODU-LCK:** The function shall generate the ODU-LCK signal as defined in clause 16.5 of [ITU-T G.709]. The clock, frame start and multiframe start are defined by the incoming ODUk signal. + +**Selector:** The normal signal for a tributary signal #p may be replaced by the ODU-LCK signal. The ODU-LCK signal is selected if the MI\_AdminState[p] is LOCKED. + +**OPUflex RCOH Receiver:** This function shall monitor the OPUflex RCOH overhead and extract the BWR\_IND signal as defined in clause 6.2.7 of [ITU-T G.7044]. + +**RCOH generator:** When MI\_INCREASE or MI\_DECREASE is true, this process inserts the RP, TSCC, CTRL, TSGS and TPID in the RCOH fields of the tributary slots identified in the MI\_TSMAP. + +### Common processes + +**Clock and (multi)frame start signal generation:** The function shall generate a local ODUk clock (ODUKP\_AI\_CK) with a frequency as listed in Table 7-2 of [ITU-T G.709] from the synchronization timing information clock input (TI\_CK) or, if the TI\_CK is absent, a free-running oscillator. The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock) apply. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUk signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +**OPU multiframe (OMFI) start signal generation for OPUk with k=4, 25(u), 50(u):** For k = 4, 25(u), 50(u) in addition to MFAS, a dedicated OPU multiframe indicator is used for the multiplexing of LO ODUs into the OPU payload area. This multiframe structure is locked to the lsb bits of the OMFI byte as shown in Tables 19-4, 19-5 and 19-6 of [ITU-T G.709], and to be inserted into the OPU overhead. The function shall generate an OPU multiframe and the related start signal (OMFS) dividing the frame signal sequence by the maximum number of tributary slots TSmax. The OMFI start signal may optionally be phase aligned to the ODU multiframe signal. In this case the OMFI = 0 position is aligned with MFAS = 0 position every 1280 frame periods See clause 19.4.4 of [ITU-T G.709]. + +**Multiplexing:** The function assigns the individual ODTUjk or ODTUk.M to specific time slots of the OPUk payload area as defined by the multiplex structure (see clauses 19.3 and 19.4.1 of [ITU-T G.709]). + +**MSI:** The function shall insert TxMSI into the MSI byte positions of the PSI overhead as defined in clauses 19.4.1.4, 19.4.1.5, 19.4.1.6 of [ITU-T G.709]. The TxMSI value, and as such the multiplex structure, is configurable via MI\_TxMSI. *During the HAO process, the TxMSI value should be configured X resizing multiframes prior to the re-enabling of dMSIM[p] detection; as defined in clause 14.3.10.2. X shall be 3.* + +**PT:** The function shall insert code "0010 0001" (ODU multiplex structure supporting ODTUk.ts or ODTUk.ts and ODTUjk) into the PT byte position of the PSI overhead, as defined in clause 15.9.2.1 of [ITU-T G.709] for k = 4. + +**Autonomous payload type for k = 2, 3:** For k = 2, 3 the transmitted PT code shall default to code "0010 0001". This code must be replaced by code "0010 0000" under the control of the PT = 21-to-PT = 20 interworking process described hereafter. When MI\_AutoPayloadtype is activated the function shall adapt a PT21 supporting port to a PT20 structure. If the corresponding adaptation sink provides the information of a PT = 20 at the RI\_AcPT, the function shall fall back to PT = 20 under the following conditions: The MI\_AutoPayloadtype is true and the HO ODU source is either not provisioned for any traffic signal structure, or the HO ODU2 source configured for one or more ODU1 signals is to be mapped into TS1/TS5 and/or TS2/TS6 and/or TS3/TS7 and/or TS4/TS8, or the HO ODU3 source is configured to support one or more ODU1 signals mapped into TS1/TS17, TS2/TS18, TSi/TS16+I and/or one or more ODU2 signals mapped into + +TSa/TS16+a/TSb/TS16+b/TSc/TS16+c/TSd/TS16+d and no other ODU type signals. In this case, the function shall insert PT20 into the PSI positions. The default value of the MI\_AUTO payload type activation shall be "true". In the situation where a PT 21 capable port which has been operating in the PT20 mode is taken out of service or receives PT21, the port shall subsequently fall back to a PT21 structure. + +In the case where the ODU2 or ODU3 adaptation source is configured for either ODU0, or ODUflex, or ODU2e, or for an ODU1 in TSi/TSj with $j < 4+i$ (for ODU2) or $j < 16+i$ (for ODU3), then PT21 is to be inserted. The transmitted PT shall be reported at the ODUkP-h/ODUj-21\_A\_So\_RI\_TrPT to the corresponding adaptation sink function and the ODUkP-h/ODUj-21\_A\_So\_MI\_TrPT. + +NOTE – The change to PT20 or PT21 means a full adaptation to the related signal structure including the default OH byte insertion. + +**HAO processes:** The HAO process includes LCR\_Generator and BWR\_RELAY\_Generator processes. + +**LCR\_Generator:** This process is used for LCR protocol adjustment processing and generation of the LCR protocol overhead. + +*Tributary slot (TS) adjustment activation:* When the MI\_INCREASE or MI\_DECREASE signal's value changes from false to true, the link connection resize (LCR) protocol is activated. + +- For the case where MI\_INCREASE is true and MI\_DECREASE is false, the *CTRL* field is set to ADD(01) and the *TSGS* bit is set to NACK(0). +- For the case where MI\_DECREASE is true and MI\_INCREASE is false, the *CTRL* field is set to REMOVE(10) and the *TSGS* bit is set to NACK(0). +- In any other case, the *CTRL* field is set to IDLE(00) and the *TSGS* bit is set to NACK(0). + +**Table 14-35 – Significance of the control fields during LCR generator processing** + +| MI_INC | MI_DEC | RMF boundary | CTRL | TSGS | +|--------|--------|--------------|------|------| +| 0 | 0 | 0 | 00 | NACK | +| 0 | 0 | 1 | 00 | NACK | +| 0 | 1 | 0 | 10 | NACK | +| 0 | 1 | 1 | 10 | NACK | +| 1 | 0 | 0 | 01 | NACK | +| 1 | 0 | 1 | 01 | NACK | +| 1 | 1 | 0 | N/A | N/A | +| 1 | 1 | 1 | N/A | N/A | + +![Figure 14-79: LCR Generator and BWR_RELAY_generator processes block diagram. The diagram shows a large 'HAO process' block containing two main sub-processes: 'LCR_generator' and 'BWR_RELAY_generator'. The 'LCR_generator' sub-process includes 'TS adjustment activation', 'RI processing', 'TS switch processing', and 'TS adjustment completion process'. The 'BWR_RELAY_generator' sub-process includes 'xI process', 'GMP mode process', 'RP relay process', 'TSCC relay process', and 'Ramp follow process'. External inputs include MI_INCREASE, MI_DECREASE, MI_TSMAP, MI_TPID, CK, FS, MFS, OPU4 MFS, xI_RP, xI_TSCC (X = C or M), and BWR_IND. External outputs include CTRL, TSGS, TPID, MI_ADJUSTATE, RP, GMP_MODE, TSCC, and CK_Control. Internal signals include LCR reactive indication, TSCC relay indication, and TS adjustment completion indication. The diagram is labeled G.798(17)_F14-79.](1846b9e1673ade53caa7358696bc1794_img.jpg) + +Figure 14-79: LCR Generator and BWR\_RELAY\_generator processes block diagram. The diagram shows a large 'HAO process' block containing two main sub-processes: 'LCR\_generator' and 'BWR\_RELAY\_generator'. The 'LCR\_generator' sub-process includes 'TS adjustment activation', 'RI processing', 'TS switch processing', and 'TS adjustment completion process'. The 'BWR\_RELAY\_generator' sub-process includes 'xI process', 'GMP mode process', 'RP relay process', 'TSCC relay process', and 'Ramp follow process'. External inputs include MI\_INCREASE, MI\_DECREASE, MI\_TSMAP, MI\_TPID, CK, FS, MFS, OPU4 MFS, xI\_RP, xI\_TSCC (X = C or M), and BWR\_IND. External outputs include CTRL, TSGS, TPID, MI\_ADJUSTATE, RP, GMP\_MODE, TSCC, and CK\_Control. Internal signals include LCR reactive indication, TSCC relay indication, and TS adjustment completion indication. The diagram is labeled G.798(17)\_F14-79. + +**Figure 14-79 – LCR Generator and BWR\_RELAY\_generator processes** + +*Remote information (RI) processing:* This performs LCR protocol processing according to the RI\_RP, RI\_CTRL, RI\_TSGS, RI\_TPID signals received from the LCR\_Receiver process. + +Increase case: + +- The *TSGS* signal is set to ACK(1) when receiving RI\_RP=1 and RI\_CTRL=ADD(01). +- The *TS switch processing* is activated when receiving RI\_RP=1 and RI\_CTRL=ADD(01) and RI\_TSGS=ACK(1). +- The *TS adjustment completion* process is activated when receiving RI\_RP=1 and RI\_CTRL=NORM(11) and RI\_TSGS=ACK(1). +- The *TSCC relay indication* signal is generated and sent to the BWR\_RELAY\_generator process when receiving RI\_RP=1 and RI\_CTRL=IDLE(00) and RI\_TSGS=NACK(0). + +Decrease case: + +- The *TSCC relay indication* signal is generated and sent to the BWR\_RELAY\_generator process and the LCR protocol is put on hold when receiving RI\_RP=1 and RI\_CTRL=REMOVE(10). +- The *TSGS* signal is set to ACK(1) when the *LCR reactive indication* signal is valid. +- The *TS switch processing* process is activated when receiving RI\_RP=1 and RI\_CTRL=NORM(11) and RI\_TSGS=ACK(1). +- The *TS adjustment completion* process is activated when receiving RI\_RP=1 and RI\_CTRL=NORM(11) and RI\_TSGS=ACK(1). +- The *TS adjustment completion indication* signal is generated and sent to the BWR\_Generator\_Relay process when receiving RI\_RP=1 and RI\_CTRL=IDLE(00) and RI\_TSGS=NACK(0). + +**Table 14-36 – Significance of the control fields during RI processing** + +| RI_RP | RI_TSGS | RI_CTRL | INCREASE | DECREASE | +|-------|---------|---------|-------------------------------------------|-------------------------------------------------------------| +| 0 | 0 | 00 | | | +| 0 | 0 | 01 | | | +| 0 | 0 | 10 | | | +| 0 | 0 | 11 | | | +| 0 | 1 | 00 | | | +| 0 | 1 | 01 | | | +| 0 | 1 | 10 | | | +| 0 | 1 | 11 | | | +| 1 | 0 | 00 | TSCC relay indication | TS adjustment completion indication | +| 1 | 0 | 01 | TSGS = ACK | | +| 1 | 0 | 10 | | TSCC relay indication | +| 1 | 0 | 11 | | | +| 1 | 1 | 00 | | | +| 1 | 1 | 01 | TSGS = ACK
TS switch processing | | +| 1 | 1 | 10 | | TSCC relay indication
TS switch processing | +| 1 | 1 | 11 | TS adjustment completion | TS adjustment completion | + +Output adjustment state signal (*MI\_ADJSTATE*). + +*TS switch processing:* + +- The *CTRL* signal is set to NORM(11) and the *TSGS* signal is set to ACK(1) when MFAS is 0 (k = 2, 3) or MFAS and OMFI are both 0 (k = 4). +- The *mapping granularity switch indication* (MGSI) signal is generated and sent towards the mapping process. +- The related MSI overhead bytes are to be updated according to the renewed TS information at the resize multiframe boundary (see [ITU-T G.7044] clauses 7.1.2 and 7.2.2). + +**Table 14-37 – Significance of the control fields during TS switch processing** + +| TS adjustment completion | TS switch | RMF boundary | CTRL | TSGS | MGSI | +|--------------------------|-----------|--------------|------|------|------| +| 0 | 0 | 0 | | | | +| 0 | 0 | 1 | | | | +| 0 | 1 | 0 | FFS | FFS | 1 | +| 0 | 1 | 1 | 11 | ACK | 1 | +| 1 | 0 | 0 | FFS | FFS | | +| 1 | 0 | 1 | 00 | NACK | | +| 1 | 1 | 0 | N/A | N/A | 1 | +| 1 | 1 | 1 | N/A | N/A | 1 | + +*TS adjustment completion processing:* The *CTRL* signal is set to IDLE and the *TSGS* signal is set to NACK(0) when MFAS is 0 (k = 2, 3) or OMFI and MFAS are both 0 (k = 4). + +**BWR Generator Relay process:** This process forwards the RP signal and TSCC signal of the BWR protocol, determines the status of GMP mode and triggers the resize ramp follow mode according to the transition of the BWR\_IND bit to prevent buffer overflow or underflow in the downstream nodes. + +*xI process (x=C or M):* This process detects the input xI\_RP and xI\_TSCC from BWR\_Generator or BWR\_RELAY\_receiver. + +- In the decrease case, the *LCR reactive indication* signal is set to TRUE when xI\_RP=1 and the value of xI\_TSCC changes from 1 to 0 and the GMP source is in normal mode. +- In the increase case, this process is not deployed. + +*GMP mode process:* The *GMP MODE* signal is set to "special mode" when the *TSCC relay indication* signal is true. The *GMP MODE* signal is set to "normal mode" when the value of the xI\_TSCC signal changes from 1 to 0. + +*TSCC relay process:* The value of the xI\_TSCC signal is passed through to the *TSCC signal* when TSCC relay indication signal has the value True and the GMP MODE is set to special mode; otherwise TSCC is 0. + +*RP relay process:* When MI\_INCREASE or MI\_DECREASE is true, the RP signal is set to 1. The value of xI\_RP is passed through to the RP signal (RP = xI\_RP) when TS adjustment completion indication is true; otherwise RP = 1. + +*Ramp Follow process:* This process detects the BWR\_IND signal from OPUflex RCOH monitor. Once the process detects the transition of BWR\_IND signal from "0" to "1", the ODUflex source shall start ramp follow mode. When the process detects the transition of BWR\_IND signal from "1" to "0", the ODUflex source shall stop ramp follow mode as defined in clauses 7.1.1 and 7.2.1 of [ITU-T G.7044]. The CK\_control signal is generated and sent to Justification control and JC generation process to control the ODUflex mapping clock. + +**RES:** The function shall insert all-ZEROs into the RES bytes. + +**ODUk PM APS:** The function shall insert the PI\_APS value into the ODUk Path APS/PCC field, which is available once per eight ODUk frames when MFAS bits 6,7,8 are 000. + +All other bits of the ODUk overhead should be sourced as "0"s, except the PMOH STAT field which should be set to the value "normal path signal" (001). + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### **14.3.13.2 HAO-capable ODUkP to ODUj payload type 21 adaptation sink function (HAO-capable ODUkP-h/ODUj-21\_A\_Sk)** + +The HAO-capable ODUkP-h/ODUj-21\_A\_Sk function extracts the OPUk overhead (PT, MSI, RES and OMFI) and monitors the reception of the correct payload type. It demultiplexes the individual ODTUjk and ODTUk.M from the payload area of the OPUk and recovers the $n \times$ ODUj signals using the justification control information (JC, JC1/2/3/4/5/6 overhead). It determines the frame and multiframe structure of the ODUj. It provides access to ODUk PM APS Overhead. It provides access to ODUj APS overhead. + +The information flow and processing of the HAO-capable ODUkP-h/ODUj-21\_A\_Sk function is defined with reference to Figures 14-80, 14-81 and 14-82. + +## Symbol + +![Diagram of the HAO-capable ODUkP-h/ODUj-21_A_Sk function symbol. The symbol is a trapezoid labeled 'ODUkP-h/ODUj-21'. Inputs include 'ODUkP_PP' from the left, 'ODUkP-h/ODUj-21_A_Sk_MP' from the left, and 'ODUkP_AP' from the bottom. Outputs include 'ODUkP-h/ODUj-21_A_Sk_RP' to the right and 'Tributary port' outputs labeled 1, 2, ..., n, collectively labeled 'ODUj_CPs'.](3440b6ff4ee9fed9b432fee67868ae8e_img.jpg) + +Diagram of the HAO-capable ODUkP-h/ODUj-21\_A\_Sk function symbol. The symbol is a trapezoid labeled 'ODUkP-h/ODUj-21'. Inputs include 'ODUkP\_PP' from the left, 'ODUkP-h/ODUj-21\_A\_Sk\_MP' from the left, and 'ODUkP\_AP' from the bottom. Outputs include 'ODUkP-h/ODUj-21\_A\_Sk\_RP' to the right and 'Tributary port' outputs labeled 1, 2, ..., n, collectively labeled 'ODUj\_CPs'. + +Figure 14-80 – HAO-capable ODUkP-h/ODUj-21\_A\_Sk function + +## Interfaces + +Table 14-38 – ODUkP-h/ODUj-21\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_MFS
ODUkP_AI_TSF
ODUkP_AI_TSD
ODUkP-h/ODUj-21_A_Sk_MP:
ODUkP-h/ODUj-21_A_Sk_MI_ExMSI[1..n]
ODUkP-h/ODUj-21_A_Sk_MI_AdminState[1..n]
ODUkP-h/ODUj-21_A_Sk_MI_APS_EN[1..n]
ODUkP-h/ODUj-21_A_Sk_MI_APS_LVL[1..n]
ODUkP-h/ODUj-21_A_Sk_MI_Nominal_Bitrate_and_Tolerance[1..n]
ODUkP-h/ODUj-21_A_Sk_MI_ODUType[1..n]
ODUkP-h/ODUj-21_A_Sk_MI_INCREASE
ODUkP-h/ODUj-21_A_Sk_MI_DECREASE
ODUkP-h/ODUj-21_A_Sk_MI_TSMAP
ODUkP-h/ODUj-21_A_Sk_MI_TPID
ODUkP-h/ODUj-21_A_Sk_RP:
ODUkP-h/ODUj-21_A_Sk_RI_TrPT (Note) | n × ODUj_CP:
ODUj_CI_CK
ODUj_CI_D
ODUj_CI_FS
ODUj_CI_MFS
ODUj_CI_SSF
ODUj_CI_SSD
ODUj_CI_APS
ODUj-21_(C/M)I_RP
ODUj-21_(C/M)I_TSCC
ODUk_PP:
ODUk_PI_APS
ODUk_PI_TSF
ODUk_PI_TSD
ODUkP-h/ODUj-21_A_Sk_MP:
ODUkP-h/ODUj-21_A_Sk_MI_cPLM
ODUkP-h/ODUj-21_A_Sk_MI_cLOOMFI
ODUkP-h/ODUj-21_A_Sk_MI_cMSIM[1..n]
ODUkP-h/ODUj-21_A_Sk_MI_AcPT
ODUkP-h/ODUj-21_A_Sk_MI_AcMSI[1..n]
ODUkP-h/ODUj-21_A_Sk_MI_cLOFLOM[1..n]
ODUkP-h/ODUj-21_A_Sk_MI_cRCOHM
ODUkP-h/ODUj-21_A_Sk_RP:
ODUkP-h/ODUj-21_A_Sk_RI_AcPT (Note)
ODUkP-h/ODUj-21_A_Sk_RI_RP
ODUkP-h/ODUj-21_A_Sk_RI_CTRL
ODUkP-h/ODUj-21_A_Sk_RI_TSGS
ODUkP-h/ODUj-21_A_Sk_RI_TPID | + +NOTE – For ODU2P-h/ODUj-21\_A\_Sk and ODU3P-h/ODUj-21\_A\_Sk only. + +## Processes + +The processes associated with the HAO-capable ODUkP-h/ODUj-21\_A\_Sk function are specific processes for each ODUj\_CP and common processes for the compound (multiplexed) signal as depicted in Figures 14-81 and 14-82. + +![Figure 14-81 – ODUkP-h/ODUj-21_A_Sk processes. This functional block diagram shows the internal architecture of the ODUkP-h/ODUj-21_A_Sk sink function. At the top, multiple ODUj_CP[1] to ODUj_CP[n] interfaces receive signals like CI_MFS, CI_FS, CI_CK, CI_D, CI_APS, CI_SSF, and CI_SSD. These feed into 'Client specific processes' blocks which interact with a 'Demultiplexer'. The demultiplexer handles signals like OMFS, MFS, FS, CK, D, TS#, and Active. Below the demultiplexer, there are blocks for 'Extract MSI' and 'Extract PT' feeding into 'MSI process' blocks. There is also an 'ODUk PM APS' block. For specific values of k (4, 25(u), 50(u)), there is an 'Extract OMFI' and 'OMFI process' loop. A 'Defect correlations' block monitors signals like dRCOHM, dPLM, dLOOMFI, and AI_TSF. A 'HAO process (if needed)' block handles hitless adjustment of ODUflex. An 'RCOH monitor' block is shown at the bottom left. Various MI (Management Information) and RI (Remote Information) signals are shown on the right side, including MI_cMSIM, MI_AdminState, RI_RP, RI_CTRL, etc. The bottom of the diagram shows the ODUkP_AP interface with signals AI_MFS, AI_FS, AI_CK, AI_D, AI_TSF, and AI_TSD.](87f2c7d96e398885a4108ecbf1aa9499_img.jpg) + +G.798(17)-Amd.3(21)\_F14-81 + +Figure 14-81 – ODUkP-h/ODUj-21\_A\_Sk processes. This functional block diagram shows the internal architecture of the ODUkP-h/ODUj-21\_A\_Sk sink function. At the top, multiple ODUj\_CP[1] to ODUj\_CP[n] interfaces receive signals like CI\_MFS, CI\_FS, CI\_CK, CI\_D, CI\_APS, CI\_SSF, and CI\_SSD. These feed into 'Client specific processes' blocks which interact with a 'Demultiplexer'. The demultiplexer handles signals like OMFS, MFS, FS, CK, D, TS#, and Active. Below the demultiplexer, there are blocks for 'Extract MSI' and 'Extract PT' feeding into 'MSI process' blocks. There is also an 'ODUk PM APS' block. For specific values of k (4, 25(u), 50(u)), there is an 'Extract OMFI' and 'OMFI process' loop. A 'Defect correlations' block monitors signals like dRCOHM, dPLM, dLOOMFI, and AI\_TSF. A 'HAO process (if needed)' block handles hitless adjustment of ODUflex. An 'RCOH monitor' block is shown at the bottom left. Various MI (Management Information) and RI (Remote Information) signals are shown on the right side, including MI\_cMSIM, MI\_AdminState, RI\_RP, RI\_CTRL, etc. The bottom of the diagram shows the ODUkP\_AP interface with signals AI\_MFS, AI\_FS, AI\_CK, AI\_D, AI\_TSF, and AI\_TSD. + +Figure 14-81 – ODUkP-h/ODUj-21\_A\_Sk processes + +![Block diagram of ODUj_CP[p] client specific processes. The diagram shows the internal structure of an ODUj client, including OPUflex RCOH monitor, Select normal/AIS/LCK, Generate AIS/LCK, ODUj APS, Frame/multi-frame alignment, Elastic store, Clock generation (ODCp), Justification control, Extract JC, and Defect correlation. It also shows various input and output signals like OMFI, MFAS, FS, CK, D, TS#, Active, CL_MFS, CL_FS, CL_CK, CL_D, CL_APS, CL_SSF, CL_SSD, BWR_IND, MI_AdminState[p], AI_TSD, AI_TSF, MI_APS_EN[p], MI_APS_LVL[p], dPLM, dLOOMFI, dMSIM[p], MI_cMSIM[p], MI_cLOFLOM[p], DMGSI, GMP_MODE, CK_Control, MI_Nominal_Bitrate_and_Tolerance[p], and MI_ODUType[p].](b35608e925cb6a7c0aa0db30d2db9d66_img.jpg) + +The diagram illustrates the internal processes of an ODUj client, labeled as ODUj\_CP[p]. At the top, a bracket groups several output signals: CL\_MFS, CL\_FS, CL\_CK, CL\_D, CL\_APS, CL\_SSF, and CL\_SSD. Below this, the diagram is divided into several functional blocks. On the left, an 'OPUflex RCOH monitor' block receives inputs from the top signals and outputs 'BWR\_IND'. Below it, a 'Select normal/AIS/LCK' block contains sub-blocks 'Normal', 'AIS', and 'LCK', which receive inputs from 'Generate AIS' and 'Generate LCK' blocks. These generation blocks are influenced by 'MI\_Nominal\_Bitrate\_and\_Tolerance[p]'. The 'Select normal/AIS/LCK' block outputs 'MI\_AdminState[p]'. In the center, an 'ODUj APS' block receives inputs from 'MI\_APS\_EN[p]' and 'MI\_APS\_LVL[p]'. Below the APS block, a 'Frame/multi-frame alignment' block receives 'MFAS', 'FS', 'CK', and 'D' inputs and outputs 'D' and 'CK' signals. These signals go to an 'Elastic store' block, which has 'RD' (Read) and 'WR' (Write) ports. The 'Elastic store' is connected to a 'Clock generation (ODCp)' block. The 'Clock generation' block outputs 'dLOFLOM' and 'AI\_TSF' signals. Below the clock generation, there are 'Justification control' and 'Extract JC' blocks, which receive inputs from 'MI\_Nominal\_Bitrate\_and\_Tolerance[p]' and 'MI\_ODUType[p]'. On the right, a 'Defect correlation' block receives inputs from 'dLOFLOM', 'dPLM', 'dLOOMFI', 'dMSIM[p]', 'MI\_cMSIM[p]', 'MI\_cLOFLOM[p]', 'DMGSI', 'GMP\_MODE', and 'CK\_Control'. It outputs 'aAIS', 'aSSF', and 'aSSD' signals to a 'Consequent actions' block, which in turn outputs 'AI\_TSD' and 'AI\_TSF' signals. At the bottom, input signals include OMFI, MFAS, FS, CK, D, TS#, and Active. A reference label 'G.798(17)-Amd.3(21)\_F14-82' is present at the bottom right of the diagram area. + +Block diagram of ODUj\_CP[p] client specific processes. The diagram shows the internal structure of an ODUj client, including OPUflex RCOH monitor, Select normal/AIS/LCK, Generate AIS/LCK, ODUj APS, Frame/multi-frame alignment, Elastic store, Clock generation (ODCp), Justification control, Extract JC, and Defect correlation. It also shows various input and output signals like OMFI, MFAS, FS, CK, D, TS#, Active, CL\_MFS, CL\_FS, CL\_CK, CL\_D, CL\_APS, CL\_SSF, CL\_SSD, BWR\_IND, MI\_AdminState[p], AI\_TSD, AI\_TSF, MI\_APS\_EN[p], MI\_APS\_LVL[p], dPLM, dLOOMFI, dMSIM[p], MI\_cMSIM[p], MI\_cLOFLOM[p], DMGSI, GMP\_MODE, CK\_Control, MI\_Nominal\_Bitrate\_and\_Tolerance[p], and MI\_ODUType[p]. + +Figure 14-82 – ODUkP-h/ODUj-21\_A\_Sk client specific processes + +### Common processes + +**OPU multiframe (OMFI) reception for OPUk with k=4, 25(u), 50(u):** For k = 4, 25(u), 50(u) in addition to MFAS, a dedicated OPU multiframe indicator is used for the multiplexing of LO ODUs into the OPU payload area. This multiframe structure is locked to the lsb bits of the OMFI byte as shown in Tables 19-4, 19-5 and 19-6 of [ITU-T G.709]. The function shall detect an OPU multiframe by searching for the framing pattern in the bits indicated above. The process has two states, out-of-multiframe (OOM) and in-multiframe (IM). The IM state shall be entered if this set is found and confirmed one frame period later and an error-free multiframe sequence is found in the byte positions of the two frames. In the IM state, the frame alignment signal shall be continuously checked with the presumed OMFI frame start position and the expected multiframe sequence. The OOM state shall be entered if this subset is not found at the correct position in five consecutive frames or the received OMFI does not match with the expected multiframe number in five consecutive frames. The OPU4 + +multiframe start (OMFS) shall be maintained during the OOM state of the OMFI detection process. The defect dLOOMFI shall be generated based on the state of the OMFI alignment process. If the OMFI alignment process is persistently in the out-of-multiframe (OOM) state for 3 ms, dLOOMFI shall be declared. dLOOMFI shall be cleared immediately when the OMFI alignment process is in the in-multiframe (IM) state. + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. + +**Autonomous payload type for k = 2, 3:** The accepted PT is provisioned to the RP (RI\_AcPT) for automatic PT adaptation. The PLM detection shall be based on the comparison of the accepted PT with the provided PT on the RP at the RI\_TrPT input. + +**MSI:** The function shall extract the MSI from the PSI overhead as defined in clause 8.7.2.1. The accepted MSI for a tributary signal #p (AcMSI[p]) is available at the MP (MI\_AcMSI[p]). The multiplex structure is defined by ExMSI[p], which is either fixed or is configurable via MI\_ExMSI[p]. During the HAO process, ExMSI[p] updates should be configured at the resizing multiframe boundary with signals [NORM, (TPID#), ACK]. + +**RES:** The value in the RES bytes shall be ignored. + +**ODUk PM APS:** The function shall extract the information from the ODUk path APS/PCC field, which is available once per eight ODUk frames when MFAS bits 6,7,8 are 000 and apply this to the PI\_APS. + +**Demultiplexing:** The function activates the ODTUjk or ODTUk.M and assigns the time slots of the ODUk payload area to the individual ODTUjk or ODTUk.M, as defined by the multiplex structure (see clauses 19.3 and 19.4.1 of [ITU-T G.709]) and clauses 7.1 and 7.2 of [ITU-T G.7044]). + +### Specific processes + +The specific processes are performed independently for each ODUj client signal that is multiplexed into the OPUk. The specific processes recover the ODUj from the ODTUjk or ODTUk.M. + +Two justification methods as described below are provided, AMP (*ODTUjk*) and GMP (*ODTUk.M*). The ODU type, as configured via the MI\_ODUType [p]input for tributary port #p, determines the mapping method. In the case of GMP mapping, the ODU rate, as configured via the MI\_Nominal\_Bitrate\_and\_Tolerance[p] input for tributary port #p, determines the base value and ranges for the parameters $C_n$ and $C_m$ . + +**ODTUjk JC:** The function shall interpret the justification control information in bits 7 and 8 of the JC bytes as defined in clause 19.5 of [ITU-T G.709], in order to determine the justification action (double positive, positive, negative, none) for the current frame. A two out of three majority decision is used. RES bits in the JC bytes shall be ignored. The ODUk frame that contains the JC bytes depends on the time slot(s) of the ODTUjk. + +**ODTUk.ts JC1/2/3 and JC4/5/6:** The function shall interpret the GMP overhead information in the JC1/2/3 and JC4/5/6 bytes as defined in clause 19.6 of [ITU-T G.709] and in clauses 7.1.2 and 7.2.2 of [ITU-T G.7044], in order to determine the number of M-byte ODUj entities in the next ODTUk.M multiframe. The OPUk frame that contains the JC1/2/3 and JC4/5/6 bytes depends on the last tributary slot that is occupied by the ODTUk.M. + +**Demapping, CBR clock generation:** The function shall provide an elastic store (buffer) process. + +*ODTUjk:* The ODUj data shall be written into the buffer from the D, NJO, PJO1 and PJO2 bytes in the ODTUjk frame. The information extraction of the PJO2, PJO1 and NJO bytes shall be under the control of the justification control information. + +Upon a double positive justification action, the writing of two data bytes into the buffer shall be cancelled once. No ODUj data shall be read from the PJO2, PJO1 or NJO bytes. Upon a positive + +justification action, the writing of one data byte into the buffer shall be cancelled once. No ODUj data shall be read from the PJO1 or NJO bytes and data shall be read from the PJO2 byte. Upon a negative justification action, one extra data byte shall be written into the buffer once. ODUj data shall be read from the PJO2, PJO1 and NJO bytes. If no justification action is to be performed, ODUj data shall be read from the PJO2 and PJO1 bytes and no ODUj data shall be read from the NJO bytes. The OPUk frame that contains the PJO2, PJO1 and NJO bytes depends on the tributary slots occupied by the ODTUjk. + +*ODTUk.M:* The ODUj data shall be extracted from the groups of M successive bytes of the ODTUk.M payload area under the control of the GMP data/stuff control mechanism as defined in clause 19.6 of [ITU-T G.709] and clauses 7.1 and 7.2 [ITU-T G.7044] and be written into the buffer. The $C_n$ information associated with the ODUj is computed from the GMP $C_m$ and $\sum C_{nD}$ parameters carried within the JC1/2/3 and JC 4/5/6 overhead of the ODTUk.M, as specified in clause 19.6 of [ITU-T G.709]. For the GMP data/stuff control mechanism refer to Annex D of [ITU-T G.709]. + +The ODUj data (CI\_D) shall be read out of the buffer under the control of the ODUj clock (CI\_CK). + +*Smoothing and jitter limiting process:* The function shall provide for a clock smoothing and elastic store (buffer) process. The ODUj data signal shall be written into the buffer under the control of the associated (gapped) OPUk input clock (with a frequency accuracy within $\pm 20$ ppm). The data signal shall be read out of the buffer under the control of a smoothed (equally spaced) ODUj clock (the rate is determined by the ODUj signal at the input of the remote ODUkP-h/ODUj-21\_A\_So). + +The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCp clock) apply. + +*Buffer size:* In the presence of jitter as specified by [ITU-T G.8251] and a frequency within the tolerance range specified for the ODUj signal in Table 7-2 of [ITU-T G.709], this justification process shall not introduce any errors. + +Following a step in frequency of the ODUj signal transported (for example, due to receiving ODUj\_CI from a new ODUj\_TT\_So at the far end or removal of an ODU-AIS signal with a frequency offset), there will be a maximum recovery time of X seconds after which this process shall not generate any bit errors. The value of X is for further study; a value of one second has been proposed. + +**RCOH receiver:** When MI\_INCREASE or MI\_DECREASE is true, this process extracts RP, TSCC, CTRL, TPID and TSGS signals from the RCOH overhead for the set of M tributary slots configured via MI\_TSMAP. The values of the RCOH fields for each of the TS in TSMAP are compared. If the values are the same and the received TPID value matches the MI\_TPID, those values are forwarded to the HAO process. If the values are not the same, a RCOH mismatch defect (dRCOHM) is detected. When MI\_INCREASE or MI\_DECREASE is false, this process is disabled and RP, TSCC, CTRL, TPID and TSGS signals are all set to 0. + +**OPUflex RCOH Receiver:** This function shall monitor the OPUflex RCOH overhead and extract the BWR\_IND signal as defined in clause 6.2.7 of [ITU-T G.7044]. + +**Frame and multiframe alignment:** The function shall perform frame and multiframe alignment as described in clause 8.2.3. + +**ODU-LCK, ODU-AIS:** The function shall generate the ODU-LCK and ODU-AIS signals as defined in [ITU-T G.709]. The clock, frame start and multiframe start shall be independent from the incoming clock. The clock has to be within the ODUj frequency tolerance range as specified in Table 7-2 of [ITU-T G.709] provisioned by the MI\_Nominal\_Bitrate\_and\_Tolerance[n] from a free-running oscillator. Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock) apply. + +**Selector:** The normal signal for a tributary signal #p may be replaced by either the ODU-AIS or ODU-LCK signal. ODU-LCK is selected if the corresponding MI\_AdminState[p] signal is LOCKED. ODU-AIS is selected if the corresponding MI\_AdminState[p] signal is not LOCKED and aAIS is true. + +**ODUj server layer APS:** When APS is enabled for tributary signal #p (MI APS\_EN[p] is true), the function shall extract the information from the ODU APS/PCC[MI APS\_LVL[p]] field, which is available once per eight ODU frames when the value of the MFAS bits 6, 7, 8 is equal to MI APS\_LVL[p], and apply the extracted information to the CI APS. + +NOTE – The ODUj server layer section APS information may be present in the case where the ODUk signal contains an ODU-AIS, ODU-LCK or ODU-OCI maintenance signal. The ODU-LCK maintenance signal may have been inserted in the far-end adaptation source function. ODUj SNC/I protection is unable to detect the insertion of such ODU-LCK and will not perform a protection switch. + +## HAO processes + +The HAO process includes the LCR\_Receiver and BWR\_RELAY\_Receiver processes. + +![Figure 14-83 – LCR_Receiver and BWR_Receiver_Relay processes. This block diagram shows the internal structure of the HAO process. It is divided into two main sub-processes: LCR_receiver and BWR_RELAY_receiver. The LCR_receiver contains 'LCR OH detecting processing' and 'TS switch processing'. Inputs to the LCR_receiver include MI_INCREASE, MI_DECREASE, MI_TSMAP, MI_TPID, CK, FS, MFS, OPU4 MFS, TPID, TSGS, CTRL, and RP. Outputs from the LCR_receiver include RI_RP, RI_CTRL, RI_TSGS, RI_TPID, and DMGSI. The BWR_RELAY_receiver contains 'Ramp follow process', 'GMP mode process', 'RP forwarding processing', and 'TSCC forwarding processing'. Inputs to the BWR_RELAY_receiver include CK_Control, BWR_IND, (C/M)_RP, and TSCC. Outputs from the BWR_RELAY_receiver include GMP_MODE. The entire HAO process is shown within a larger system context.](f92133ff7727978a12d89b8426245b85_img.jpg) + +Figure 14-83 – LCR\_Receiver and BWR\_Receiver\_Relay processes. This block diagram shows the internal structure of the HAO process. It is divided into two main sub-processes: LCR\_receiver and BWR\_RELAY\_receiver. The LCR\_receiver contains 'LCR OH detecting processing' and 'TS switch processing'. Inputs to the LCR\_receiver include MI\_INCREASE, MI\_DECREASE, MI\_TSMAP, MI\_TPID, CK, FS, MFS, OPU4 MFS, TPID, TSGS, CTRL, and RP. Outputs from the LCR\_receiver include RI\_RP, RI\_CTRL, RI\_TSGS, RI\_TPID, and DMGSI. The BWR\_RELAY\_receiver contains 'Ramp follow process', 'GMP mode process', 'RP forwarding processing', and 'TSCC forwarding processing'. Inputs to the BWR\_RELAY\_receiver include CK\_Control, BWR\_IND, (C/M)\_RP, and TSCC. Outputs from the BWR\_RELAY\_receiver include GMP\_MODE. The entire HAO process is shown within a larger system context. + +Figure 14-83 – LCR\_Receiver and BWR\_Receiver\_Relay processes + +**LCR\_Receiver:** This process completes the receiving LCR protocol. It contains the following sub-processes: + +*LCR OH detecting processing:* When MI\_INCREASE or MI\_DECREASE is true, the LCR protocol would be activated and RCOH information (RP, CTRL, TPID, TSGS) would be detected. This information is then sent to LCR\_Generator. + +*TS switch processing:* When CTRL is detected as NORM, the *demapping granularity switch indication* (DMGSI) signal would be generated towards the demapping processing. + +**BWR\_Receiver\_Relay:** This process forwards the RP signal and TSCC signal of the BWR protocol, determines the status of GMP mode and triggers the resize ramp follow mode according to the transition of the BWR\_IND bit to prevent buffer overflow or underflow in the downstream nodes. It contains the following sub-processes: + +*GMP mode process:* Change of TSCC from 0 to 1 is used to trigger the GMP process into special mode. Change of TSCC from 1 to 0 is used to trigger the GMP process into normal mode. + +*TSCC forwarding process:* This passes through TSCC=1 when the *GMP process is set into special mode*, that is (C/M)I\_TSCC=TSCC(1). This passes through TSCC=0 when *GMP has also been set into normal mode*, that is (C/M)I\_TSCC=TSCC(0). The initial value of CI\_TSCC is 0. + +*RP forwarding process:* RP is passed through to either a BWR\_RELAY\_Generator process or a BWR\_Receiver process ((C/M)I\_RP=RP). + +*Ramp follow process:* This process detects the BWR\_IND signal from the OPUflex RCOH monitor. Once the process detects the transition of the BWR\_IND signal from "0" to "1", the ODUflex source shall start the ramp follow mode. When the process detects the transition of the BWR\_IND signal from "1" to "0", the ODUflex source shall stop the ramp follow mode, as defined in clauses 7.1.1 and 7.2.1 of [ITU-T G.7044]. The CK\_control signal is generated and sent to the clock generator process to control the ODUflex demapping clock. + +## Defects + +The function shall detect dPLM, dMSIM, dLOOMFI and dLOFLOM. + +**dPLM:** See clause 6.2.4.1. The expected payload type is the provided PT on the RP at the RI\_TrPT input (ODU multiplex structure supporting ODTUk.ts or ODTUk.ts and ODTUjk) as defined in [ITU-T G.709]. + +**dLOOMFI:** dLOOMFI is detected per OPUk with k = 4, 25(u), 50(u). See the OPU multiframe (OMFI) detection process for OPUk with k = 4, 25(u), 50(u). + +**dRCOHM:** RCOH mismatch defect. The values of the RCOH fields for each of the TS in TSMAP are compared. If the values are not the same, a RCOH mismatch defect (dRCOHM) is raised. If the values are the same and the received TPID value matches the MI\_TPID, those values are forwarded to the HAO process and the dRCOHM is cleared. + +For each ODUj tributary port #p: + +**dMSIM[p]:** See clause 6.2.9.1. dMSIM[p] is detected per active ODUj. During the HAO process, the detection of dMSIM[p] is disabled at the next resize multiframe boundary after receiving RP = 1, as defined in clause 6.2.6 of [ITU-T G.7044]. The detection of dMSIM[p] is enabled at the next resize multiframe boundary after receiving RP=0, as defined in clause 6.2.6 of [ITU-T G.7044]. + +**dLOFLOM[p]:** See clause 6.2.5.3. dLOFLOM is detected per active ODUj. + +## Consequent actions + +PI\_TSF $\leftarrow$ AI\_TSF + +PI\_TSD $\leftarrow$ AI\_TSD + +For each ODUj tributary port #p: + +aSSF[p] $\leftarrow$ ((AI\_TSF or dPLM or dLOOMFI or dMSIM[p] or dLOFLOM[p]) and (not MI\_AdminState[p]=LOCKED)) + +aSSD[p] $\leftarrow$ AI\_TSD and (not MI\_AdminState[p] = LOCKED) + +aAIS[p] $\leftarrow$ ((AI\_TSF or dPLM or dMSIM[p] or dLOOMFI or dLOFLOM[p]) and (not MI\_AdminState[p] = LOCKED)) + +NOTE – The state of the determination process of the Cm and its contribution to AIS consequent action are for further study. + +On declaration of aAIS, the function shall output an all-ONEs pattern/signal within 2 frames. On clearing aAIS, the all-ONEs pattern/signal shall be removed within 2 frames, with normal data being output. The AIS clock, frame start and multiframe start shall be independent from the incoming clock, frame start and multiframe start. The clock has to be within the ODUj frequency tolerance range as specified in Table 7-2 of [ITU-T G.709] provisioned by the MI\_Nominal\_Bitrate\_and\_Tolerance + +from a free-running oscillator. Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock) apply. + +#### Defect correlations + +cPLM $\leftarrow$ dPLM and (not AI\_TSF) + +cRCOHM $\leftarrow$ dRCOHM and (not AI\_TSF) + +For ODUk with k=4, 25(u), 50(u) + +cLOOMFI $\leftarrow$ dLOOMFI and (not AI\_TSF) + +For each ODUj tributary port #p: + +cMSIM[p] $\leftarrow$ dMSIM[p] and (not dPLM) and (not dLOOMFI) and (not AI\_TSF) + +cLOFLOM[p] $\leftarrow$ dLOFLOM[p] and (not dPLM) and (not dLOOMFI) and (not AI\_TSF) + +**Performance monitoring:** None. + +#### 14.3.14 HAO capable ODUk to MPLS-TP Adaptation functions (ODUkP-h/MT\_A; k=ODUflex) + +See [ITU-T G.8121] for this adaptation function. + +#### 14.3.15 ODU2eP to FC-1200 client adaptation function (ODU2eP/FC-1200\_A) + +The ODU2eP to FC-1200 adaptation functions perform the adaptation between the ODU2eP layer adapted information and the characteristic information of a FC-1200 signal. As described in clause 17.8.2 of [ITU-T G.709], a timing transparent adaptation with compression factor 50/51 is used to produce a signal with a rate of approximately 10 312 500 kbit/s that is mapped into the OPU2e. + +##### 14.3.15.1 ODU2eP to FC-1200 client adaptation source function (ODU2eP/FC-1200\_A\_So) + +The ODU2eP/FC-1200\_A\_So function creates the ODU2e signal from a clock, derived from the incoming FC-1200\_CI clock. It byte synchronously maps the transcoded constant bit-rate client signal from the FC-1200\_CP into the payload area of the OPU2e as defined in clause 17.8.2 of [ITU-T G.709], and adds OPU2e overhead (RES, PT) and default ODU2e overhead. + +The information flow of the ODU2eP/FC-1200\_A\_So function is defined with reference to Figure 14-84 and the processing of the ODU2eP/FC-1200\_A\_So function is defined with reference to Figure 14-85. + +#### Symbol + +![Diagram of the ODU2eP/FC-1200_A_So function symbol. It shows an input 'FC-1200_CP' entering a trapezoidal block labeled 'ODU2eP/FC-1200', which then outputs 'ODU2eP_AP'.](18e10a200cbafecb4114d25fa128b703_img.jpg) + +``` +graph TD; A[FC-1200_CP] --> B[ODU2eP/FC-1200]; B --> C[ODU2eP_AP]; +``` + +G.798(17)\_F14-84 + +Diagram of the ODU2eP/FC-1200\_A\_So function symbol. It shows an input 'FC-1200\_CP' entering a trapezoidal block labeled 'ODU2eP/FC-1200', which then outputs 'ODU2eP\_AP'. + +**Figure 14-84 – ODU2eP/FC-1200\_A\_So function** + +## Interfaces + +**Table 14-39 – ODU2eP/FC-1200\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| FC-1200_CP:
FC-1200_CI_CK
FC-1200_CI_D
FC-1200_CI_SSF | ODU2eP_AP:
ODU2eP_AI_CK
ODU2eP_AI_D
ODU2eP_AI_FS
ODU2eP_AI_MFS | + +## Processes + +**Clock and (multi)frame start signal generation:** The function shall generate a local ODU2e clock (ODU2eP\_AI\_CK) by multiplying the incoming FC-1200 clock (CI\_CK) by a factor of $239/237 \times 50/51$ . The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCb clock), apply. + +During failure conditions of the incoming CBR clock signal (CI\_CK), the ODU2e clock shall stay within its limits as defined in [ITU-T G.8251] and no frame phase discontinuity shall be introduced. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODU2e signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +**Timing transparent transcoding:** The function shall compress the FC-1200 signal by a factor 50/51 through timing transparent transcoding. The result is a stream of equal length GFP data frames without GFP idle frames. + +**66B block synchronization:** The function shall recover 66B block synchronization. + +**66B to 513B transcoding:** The function shall transcode the 66B symbols to 513B symbols as specified in Annex B of [ITU-T G.709]. + +**Superblock construction and CRC-24 generation:** The process constructs a superblock from eight received 513B data words as defined in clause 17.8.2 of [ITU-T G.709]. A CRC-24 is calculated over the 65 bytes of "control" information located in the superblock and inserted at the end of the superblock as defined in clause 17.8.2 of [ITU-T G.709]. + +**Superblock mapping:** Seventeen superblocks are grouped together and prepended with 16 bytes of fixed stuff bytes into the payload information field of the GFP frame. + +**pFCS generation:** The FCS is calculated over the payload information field of a frame and inserted into the pFCS fields of the frame as defined in clause 6.1.2.2.1 of [ITU-T G.7041]. + +**Type header generation:** The type header of the GFP data frame is generated by setting the PTI field to "000", the PFI field to "1", the EXI field to "0000" and the UPI field to 0001 0101" (Transparent transcoded FC-1200) as defined in Table 6-3 of [ITU-T G.7041]. The tHEC of the payload header is generated as defined in clause 6.1.2.1.2 of [ITU-T G.7041]. + +**Payload scrambler:** The GFP payload area is scrambled as defined in clause 6.1.2.3 of [ITU-T G.7041]. + +**Core header generation:** The core header of the GFP data frame is generated as specified in clause 8.5.3.1 of [ITU-T G.806]. The length of the GFP payload area is always 8800 bytes. + +**Mapping:** The function shall provide an elastic store (buffer) process. The transcoded FC-1200 signal consists of a stream of GFP data frames. The data bytes of the GFP stream shall be written into the buffer under control of the associated input clock. The data bytes of the GFP stream shall be read out + +of the buffer and written byte-synchronously onto the D bytes in the OPU2e frame under control of the ODU2e clock as defined in clause 17.8.2 of [ITU-T G.709]. + +*Buffer size:* In the presence of jitter as specified by [b-ANSI INCITS 364], this mapping process shall not introduce any errors. + +Following a step in frequency of the CI\_CK signal (for example, due to removal of the ingress replacement signal), there will be a maximum recovery time of X seconds after which this process shall not generate any bit errors. The value of X is for further study; a value of 1 second has been proposed. + +**PT:** The function shall insert payload type code "0000 1000" (FC-1200 into OPU2e mapping) into the PT byte position of the PSI overhead as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**Client signal fail:** The function shall signal the failure of the client signal to the far end by use of the Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +NOTE – Equipment developed prior to Edition 4.0 of this Recommendation will not support the CSF processing. + +**RES:** The function shall insert all-0's into the RES bytes and reserved bits within the JC bytes. + +All other bits of the ODU2e overhead should be sourced as "0"s, except the ODU2e-PM STAT field which should be set to the value "normal path signal" (001). + +![Diagram of an elastic store with a circular buffer and WR/RD pointers.](1a05c3cbf9fd7b2a8873cad13d10cdb6_img.jpg) + +**FC-1200\_CP** + +**CI\_D CI\_CK** **CI\_SSF** + +Timing transparent transcoding + +66B block synchronization + +66B\_Data      66B\_CK + +66B to 513B transcoding + +513B\_Data      513B\_CK + +Superblock construction and +CRC-24 generation + +SB\_Data      SB\_FS + +Superblock mapping + +GFP\_Frame      GFP\_FS + +pFCS generation + +GFP\_Frame      GFP\_FS + +Type header generation + +GFP\_Frame      GFP\_FS + +Payload scrambler + +GFP\_Frame      GFP\_FS + +Core header generation (PLI, +cHEC, scrambler) + +GFP\_Frame      GFP\_FS + + + +Elastic store + +ODU clock generator locked +to FC-1200 clock (ODCb) + + + +Justification control + +CK + +$\frac{1}{122368}$ + +FS + +$\frac{1}{256}$ + +MFS + + + +Insert PT + +Insert CSF ← CI\_SSF + +Insert RES + +ODUk OH is set to all-0's, +except PM STAT = 001 + + + +**AI\_D** +**AI\_CK** +**AI\_FS** +**AI\_MFS** + +**ODU2eP\_AP** + +G.798(17)\_F14-85 + +Diagram of an elastic store with a circular buffer and WR/RD pointers. + +**Figure 14-85 – ODU2eP/Client\_A\_So function** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.3.15.2 ODU2eP to FC-1200 client adaptation sink function (ODU2eP/FC-1200\_A\_Sk) + +The ODU2eP/FC-1200\_A\_Sk recovers the FC-1200 client signal from the OPU2e payload. It extracts the OPU2e overhead (PT and RES) and monitors the reception of the correct payload type. Under signal fail condition the replacement signal as defined in clause 17.8.2 of [ITU-T G.709] shall be inserted. + +The information flow of the ODU2eP/FC-1200\_A\_Sk function is defined with reference to Figure 14-86 and the processing of the ODU2eP/FC-1200\_A\_Sk function is defined with reference to Figure 14-87. + +##### Symbol + +![Diagram of the ODU2eP/FC-1200_A_Sk function symbol. A central trapezoidal block labeled 'ODU2eP/FC-1200' has an input arrow from below labeled 'ODU2eP_AP' and an output arrow pointing left labeled 'ODU2eP/FC-1200_A_Sk_MP'. Above the block, an arrow points up to 'FC-1200_CP'. The diagram is labeled G.798(17)_F14-86.](40c6fe38cf97a637027a6a1806b5546a_img.jpg) + +Diagram of the ODU2eP/FC-1200\_A\_Sk function symbol. A central trapezoidal block labeled 'ODU2eP/FC-1200' has an input arrow from below labeled 'ODU2eP\_AP' and an output arrow pointing left labeled 'ODU2eP/FC-1200\_A\_Sk\_MP'. Above the block, an arrow points up to 'FC-1200\_CP'. The diagram is labeled G.798(17)\_F14-86. + +**Figure 14-86 – ODU2eP/Client\_A\_Sk function** + +##### Interfaces + +**Table 14-40 – ODU2eP/Client\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODU2eP_AP:
ODU2eP_AI_CK
ODU2eP_AI_D
ODU2eP_AI_FS
ODU2eP_AI_MFS
ODU2eP_AI_TSF | FC-1200_CP:
FC-1200_CI_CK
FC-1200_CI_D
FC-1200_CI_SSF
ODU2eP/FC-1200_A_Sk_MP:
ODU2eP/FC-1200_A_Sk_MI_cPLM
ODU2eP/FC-1200_A_Sk_MI_cCSF
ODU2eP/FC-1200_A_Sk_MI_cLFD
ODU2eP/FC-1200_A_Sk_MI_AcPT | + +##### Processes + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. + +**RES:** The value in the RES bytes shall be ignored. + +**Client signal fail:** The function shall extract the CSF signal indicating the failure of the client signal out of bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +**NOTE** – Equipment developed prior to Edition 4.0 of this Recommendation will not support the CSF processing. + +**Timing transparent transcoding:** The function shall uncompress the FC-1200 signal by a factor 51/50 through timing transparent transcoding. The result is a stream of 66B symbols. + +*GFP frame delineation:* The function shall delineate the GFP data frame as specified in clause 8.5.2.2 of [ITU-T G.806]. + +*Payload descrambler:* The GFP payload area is descrambled as defined in clause 6.1.2.3 of [ITU-T G.7041]. + +*tHEC check:* The tHEC of the payload header shall be processed as defined in clause 8.5.3.2 of [ITU-T G.806]. + +*PTI and UPI:* The function shall ignore the PTI and UPI fields. + +*pFCS supervision:* The function shall ignore the FCS field. + +*Superblock demapping:* The prepended 16 bytes of fixed stuff are stripped and the 17 superblocks are extracted from the payload information field of the GFP frame. + +*CRC-24 supervision and superblock destruction:* This process checks the CRC-24 of a received superblock for errors. If an error is detected all 66B symbols of the superblock are replaced by 66B error control blocks. + +*513B to 66B transcoding:* The function shall transcode the 513B symbols to 66B symbols as specified in Annex B of [ITU-T G.709]. + +**CBR clock generation:** The function shall provide an elastic store (buffer) process. The 66B symbols resulting from the timing transparent transcoding shall be written into the buffer. The FC-1200 data (CI\_D) shall be read out of the buffer under control of the FC-1200 clock (CI\_CK). + +*Smoothing and jitter limiting process:* The function shall provide for a clock smoothing and elastic store (buffer) process. The data bytes shall be written into the buffer under control of the associated (gapped) input clock. The data signal shall be read out of the buffer under control of a smoothed (equally spaced) clock at a rate and frequency accuracy determined by the client signal rate at the input of the remote ODU2eP/FC-1200\_a\_So. + +The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCp clock), apply. + +*Buffer size:* In the presence of jitter as specified by [b-ANSI INCITS 364] and an ODU2e frequency within the range $10\,399\,525.316\text{ kbit/s} \pm 100\text{ ppm}$ , this justification process shall not introduce any errors. + +Following a step in frequency of the signal transported by the ODU2eP\_AI (for example, due to reception of FC-1200\_CI from a new CBR\_TT\_So at the far end or removal of the replacement signal with a frequency offset), there will be a maximum recovery time of X seconds after which this process shall not generate any bit errors. The value of X is for further study; a value of 1 second has been proposed. + +![Block diagram of ODU2eP/Client_A_Sk processes showing data flow from FC-1200_CP and ODU2eP_AP through various processing stages including transcoding, supervision, and defect detection.](70fd9003b407d059f32275b212482817_img.jpg) + +The diagram illustrates the internal processes of an ODU2eP/Client\_A\_Sk. At the top, the **FC-1200\_CP** interface provides **CI\_D** and **CI\_CK** signals. These pass through a **Replacement signal generator** and a **Replacement signal insertion** block, which also receives an **aAIS** signal. The **CI\_SSF** signal is output from the **Consequent actions** block. Below the insertion block, the data and clock signals enter an **Elastic store** (with **WR** and **RD** ports). The **Elastic store** outputs **WR** and **RD** signals to a **CBR clock generator (ODCp)**, which provides a **CK** signal. The data from the **Elastic store** is then processed through a series of stages within a **Timing transparent transcoding** block: **66B\_Data** and **66B\_CK** are processed through **513B to 66B transcoding** to produce **513B\_Data** and **513B\_CK**. These are followed by **CRC-24 supervision and superblock de-construction** (outputting **SB\_Data** and **SB\_FS**), **Superblock demapping** (outputting **GFP\_Frame** and **GFP\_FS**), **pFCS supervision** (outputting **GFP\_Frame** and **GFP\_FS**), **PTI and UPI supervision** (outputting **GFP\_Frame** and **GFP\_FS**), **tHEC check** (outputting **GFP\_Frame** and **GFP\_FS**), **Payload descrambler** (outputting **GFP\_Frame** and **GFP\_FS**), and **GFP frame delineation** (outputting **D** and **CK**). The **Demapping** block receives **AI\_CK** and **AI\_FS** signals and outputs **AI\_D**, **AI\_MFS**, **AI\_CK**, and **AI\_FS** signals. Below the transcoding block, the **Extract CSF** block outputs **dCSF**, and the **Extract PT** block outputs **dPLM** to a **PT process** block, which outputs **MI\_AcPT**. The **Defect correlations** block receives **dLFD**, **dPLM**, **dCSF**, and **AI\_TSF** signals and outputs **MI\_cLFD**, **MI\_cPLM**, and **MI\_cCSF** signals. The **Consequent actions** block also receives **dPLM**, **dLFD**, and **AI\_TSF** signals. The **ODU2eP\_AP** interface provides **AI\_D**, **AI\_MFS**, **AI\_CK**, **AI\_FS**, and **AI\_TSF** signals. The diagram is labeled **ODU2eP/FC-1200\_A\_Sk\_MP** on the right and **G.798(17)\_F14-87** at the bottom right. + +Block diagram of ODU2eP/Client\_A\_Sk processes showing data flow from FC-1200\_CP and ODU2eP\_AP through various processing stages including transcoding, supervision, and defect detection. + +**Figure 14-87 – ODU2eP/Client\_A\_Sk processes** + +**Defects** + +The function shall detect for dPLM, dLFD, and dCSF defects. + +**dPLM:** See clause 6.2.4.1. The expected payload type is "0000 1000" (FC-1200 into OPU2e mapping) as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**dCSF:** See clause 6.2.10. + +**dLFD:** See clause 6.2.5.2 of [ITU-T G.806]. + +### Consequent actions + +aSSF $\leftarrow$ AI\_TSF or dPLM or dLFD + +aAIS $\leftarrow$ AI\_TSF or dPLM or dLFD + +On declaration of aAIS the function shall output a replacement signal as defined in clause 17.8.2 of [ITU-T G.709] within two frames. On clearing of aAIS the replacement signal shall be removed within two frames and normal data being output. The replacement signal clock shall be independent from the incoming clock. The replacement signal clock has to be within the frequency, jitter, and wander tolerance specifications of the FC-1200 client signal as defined in [b-ANSI INCITS 364]. + +### Defect correlations + +cPLM $\leftarrow$ dPLM and (not AI\_TSF) + +cLFD $\leftarrow$ dLFD and (not dPLM) and (not AI\_TSF) + +cCSF $\leftarrow$ dCSF and (not dPLM) and (not AI\_TSF) + +**Performance monitoring:** None. + +### 14.3.16 ODUCnP to ODUk adaptation function (ODUCnP/ODUk\_A) + +The ODUCnP to ODUk adaptation functions perform the adaptation between the ODUCnP layer adapted information and the characteristic information of ODUk ( $k = 0, 1, 2, 2e, 3, 4, \text{flex}$ ) signals. + +![Diagram of the ODUCnP/ODUk_A function. A central trapezoidal block is labeled 'ODUCnP/ODUk'. Above the block, 'Tributary port' is labeled with arrows pointing to ports 1, 2, ..., m. Above these ports, 'ODUk_CP's' is labeled. To the right of the block, an arrow labeled 'ODUCnP_TI' points into the block. Below the block, an arrow labeled 'ODUCnP_AP' points out. The diagram is labeled 'G.798(17)_F14-88' in the bottom right corner.](ce0669b928f93ab068d8874de19c133a_img.jpg) + +The diagram illustrates the ODUCnP/ODUk\_A function. A central trapezoidal block represents the adaptation function. Above the block, multiple tributary ports are shown, labeled 1, 2, ..., m. Each port has a bidirectional arrow connecting it to the block. Above these ports, the label 'ODUk\_CP's' indicates the client signals. To the right of the block, an arrow labeled 'ODUCnP\_TI' points into the block, representing the incoming signal. Below the block, an arrow labeled 'ODUCnP\_AP' points out, representing the adapted signal. The diagram is identified by the code 'G.798(17)\_F14-88' in the bottom right corner. + +Diagram of the ODUCnP/ODUk\_A function. A central trapezoidal block is labeled 'ODUCnP/ODUk'. Above the block, 'Tributary port' is labeled with arrows pointing to ports 1, 2, ..., m. Above these ports, 'ODUk\_CP's' is labeled. To the right of the block, an arrow labeled 'ODUCnP\_TI' points into the block. Below the block, an arrow labeled 'ODUCnP\_AP' points out. The diagram is labeled 'G.798(17)\_F14-88' in the bottom right corner. + +**Figure 14-88 – ODUCnP/ODUk\_A function** + +Tributary ports are dynamically created and deleted under the control of management. Each tributary port is associated with one ODUk connection point on one hand, and $M$ OPUCn tributary slots on the other hand. The multiplex structure identifier (MSI) carries the configuration of tributary ports to tributary slots. + +#### 14.3.16.1 ODUCnP to ODUk adaptation source function (ODUCnP/ODUk\_A\_So) + +The ODUCnP/ODUk\_A\_So function creates the ODUCn signal from a free-running clock or a external synchronization clock. It asynchronously maps the ODUk client signal from the $m \times$ ODUk CPs into ODTUCn.M including justification control (JC) information. The ODTUCn.M is multiplexed into the tributary slots of the OPUCn. It adds OPUCn overhead (RES, PT, MSI, OMFI) and default ODUCn overhead. It provides access to ODUCn APS overhead. It provides access to the ODUk APS overhead. + +The information flow and processing of the ODUCnP/ODUk\_A\_So function is defined with reference to Figures 14-88 and 14-89. + +### Symbol + +![Diagram of the ODUCnP/ODUk_A_So function symbol. The symbol is a trapezoid labeled 'ODUCnP/ODUk'. Inputs include 'Tributary port' (1, 2, ..., m) and 'ODUk_CPs' entering from the top; 'ODUCn_PP' entering from the left; 'ODUCnP/ODUk_A_So_MP' entering from the left via a double-headed arrow; and 'ODUCn_TP' entering from the right. The output is 'ODUCnP_AP' exiting from the bottom. A reference label 'G.798(17)_F14-89' is present at the bottom right.](0603e0bad64a10c96372bbcf8c5d0d14_img.jpg) + +Diagram of the ODUCnP/ODUk\_A\_So function symbol. The symbol is a trapezoid labeled 'ODUCnP/ODUk'. Inputs include 'Tributary port' (1, 2, ..., m) and 'ODUk\_CPs' entering from the top; 'ODUCn\_PP' entering from the left; 'ODUCnP/ODUk\_A\_So\_MP' entering from the left via a double-headed arrow; and 'ODUCn\_TP' entering from the right. The output is 'ODUCnP\_AP' exiting from the bottom. A reference label 'G.798(17)\_F14-89' is present at the bottom right. + +Figure 14-89 – ODUCnP/ODUk\_A\_So function + +### Interfaces + +Table 14-41 – ODUCnP/ODUk\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| m × ODUk_CP:
ODUk_CI_CK
ODUk_CI_D
ODUk_CI_FS
ODUk_CI_MFS
ODUk_CI_APS
ODUCn_PP:
ODUCn_PI_APS
ODUCn_TP:
ODUCn_TI_CK
ODUCnP/ODUk_A_So_MP:
ODUCnP/ODUk_A_So_MI_TxMSI
ODUCnP/ODUk_A_So_MI_Nominal_Bitrate_and_Tolerance[1..m]
ODUCnP/ODUk_A_So_MI_AdminState[1..m]
ODUCnP/ODUk_A_So_MI_APS_EN[1..m]
ODUCnP/ODUk_A_So_MI_APS_LVL[1..m] | ODUCnP_AP:
ODUCnP_AI_CK
ODUCnP_AI_D
ODUCnP_AI_FS
ODUCnP_AI_MFS | + +### Processes + +The processes associated with the ODUCnP/ODUk\_A\_So function are specific processes for each ODUk\_CP and common processes for the compound (multiplexed) signal as depicted in Figures 14-90 and 14-91. + +![Block diagram of ODUCnP/ODUk_A_So processes showing client processes, multiplexing, and clock generation.](8b964751bc72fac53d873c674d3fa937_img.jpg) + +The diagram illustrates the internal processes of an ODUCnP/ODUk\_A\_So system. At the top, multiple client processes, labeled **ODUk\_CP[1]** through **ODUk\_CP[m]**, are shown. Each client process has input signals **CL\_MFS**, **CL\_FS**, **CL\_CK**, **CL\_D**, and **CL\_APS**. Each client process outputs management and control signals: **MI\_AdminState**, **MI\_APS\_EN**, **MI\_APS\_LVL**, and **MI\_Nominal\_Bitrate\_and\_Tolerance**. These are grouped as **MI\_AdminState[1..m]**, **MI\_APS\_EN[1..m]**, **MI\_APS\_LVL[1..m]**, and **MI\_Nominal\_Bitrate\_and\_Tolerance[1..m]**. The client processes also output data signals: **OMFS**, **MFS**, **FS**, **CK**, **D**, and **TS#**. + +The data signals from all client processes are fed into a **Multiplexer**. The multiplexer outputs a **Multiplex structure** which includes: **Multiplex structure identifier (MSI)**, **Payload type (PT)**, **RES**, and **ODUCn PM APS**. The MSI signal is also labeled as **MI\_TxMSI**. The PM APS signal is labeled as **PI\_APS**. + +Below the multiplexer, the **ODUCn PM APS** signal is processed by an **OMFI** block (which is **optional**) and a $\frac{1}{20}$ divider to produce **OPMFS**. The **OMFI** block also outputs **MFS** and **FS** signals. The **MFS** signal is also labeled as **AI\_MFS** and the **FS** signal as **AI\_FS**. The **CK** signal is also labeled as **AI\_CK**. These three signals (**AI\_MFS**, **AI\_FS**, **AI\_CK**) are grouped as **ODUCnP\_AP**. + +The **MFS** signal is also fed into a $\frac{1}{256}$ divider, and the **FS** signal into a $\frac{1}{122368}$ divider. The outputs of these dividers are fed into an **ODCa clock generator**. The **ODCa clock generator** also receives a **TI\_CK** signal and outputs a **TI\_CK** signal. The **ODCa clock generator** is also labeled as **ODUCn\_TP**. + +A **Free-running clock generator** is also shown, which outputs a **CK** signal to the **ODCa clock generator**. + +On the left side, a block indicates that **ODUCn OH is set to all-0's, except PM STAT = 001**. + +On the right side, a large bracket groups the client process outputs and the multiplexer outputs as **ODUCnP/ODUk\_A\_So\_MP**. Other brackets on the right label the **PI\_APS** signal as **ODUCn\_PP** and the **ODCa clock generator** as **ODUCn\_TP**. + +The diagram is labeled **G.798(17)\_F14-90** at the bottom right. + +Block diagram of ODUCnP/ODUk\_A\_So processes showing client processes, multiplexing, and clock generation. + +Figure 14-90 – ODUCnP/ODUk\_A\_So processes + +![Block diagram of ODUkP_CP[p] client specific processes. The diagram shows the flow of signals CI_MFS, CI_FS, CI_CK, CI_D, and CI_APS through various functional blocks: ODU-LCK generator, LCK/Normal selection, FAS/MFAS insertion, Elastic store, and Justification control and JC generation. External inputs include MI_AdminState[p], MI_APS_EN[p], MI_APS_LVL[p], and MI_Nominal_Bitrate_and_Tolerance[p]. Output signals include OMFS, MFS, FS, CK, D, TS#, and Active. Reference G.798(17)-Amd.3(21)_F14-91 is noted at the bottom.](ba596ecf0bd3f3520b7b5c2c857a9ec3_img.jpg) + +G.798(17)-Amd.3(21)\_F14-91 + +Block diagram of ODUkP\_CP[p] client specific processes. The diagram shows the flow of signals CI\_MFS, CI\_FS, CI\_CK, CI\_D, and CI\_APS through various functional blocks: ODU-LCK generator, LCK/Normal selection, FAS/MFAS insertion, Elastic store, and Justification control and JC generation. External inputs include MI\_AdminState[p], MI\_APS\_EN[p], MI\_APS\_LVL[p], and MI\_Nominal\_Bitrate\_and\_Tolerance[p]. Output signals include OMFS, MFS, FS, CK, D, TS#, and Active. Reference G.798(17)-Amd.3(21)\_F14-91 is noted at the bottom. + +**Figure 14-91 – ODUCnP/ODUk\_A\_So client specific processes** + +### Specific processes + +The specific processes are performed independently for each ODUk client signal that is multiplexed into the OPUCn. The specific processes perform the mapping of the ODUk into an ODTUCn.M. + +**FAS/MFAS insertion:** The function shall extend the ODUk with the frame alignment overhead (FAS and MFAS) in row one bytes 1 to 7 as described in clause 15.6.2 of [ITU-T G.709]. Bytes 8 to 14 of row one are set to all-ZEROs. + +**Mapping, frequency justification and bit-rate adaptation:** The function shall provide an elastic store (buffer) process for the ODUk client signal. The data signal ODUk\_CI shall be written into the buffer under the control of the associated input clock. + +Justification methods GMP (*ODTUCn.M*), as described below, is provided, The ODU rate, as configured via the ODUCnP/ODUk\_A\_So\_MI\_Nominal\_Bitrate\_and\_Tolerance[p] input for tributary port #p, determines the base value and ranges for the parameters Cn and Cm. + +*ODTUCn.M:* The data shall be read out of the buffer and written onto groups of 16M successive bytes of the ODTUCn.M payload area under the control of the ODUCn clock and the GMP data/stuff control mechanism as defined in clause 20.5 of [ITU-T G.709]. The 16-byte word alignment of the extended ODUk is preserved through the mapping procedure; i.e., the position of the first 16 overhead bytes of the ODUk is always located after an integer number of 16-byte words from the start of the ODTUCn.M structure. + +**Buffer size:** In the presence of jitter as specified by [ITU-T G.8251] and a frequency within the range specified in Table 7-2 of [ITU-T G.709], this mapping process shall not introduce any errors. The maximum buffer hysteresis, and therefore the maximum phase error introduced, is for further study. + +**ODTUCn.M JC1/JC2/JC3, JC4/JC5/JC6:** The function shall generate the GMP $C_m$ and GMP $\sum C_{nD}$ information and insert this into the JC1/JC2/JC3 and JC4/JC5/JC6 bytes, respectively, according to the specification in clause 20.5 and Annex D of [ITU-T G.709]. + +**ODUk server layer APS:** When APS is enabled for tributary signal #p (MI\_APS\_EN[p] is true), the function shall insert the CI\_APS value into the ODU APS/PCC[MI\_APS\_LVL[p]] field, which is available once per eight ODU frames when the value of the MFAS bits 6, 7, 8 are equal to MI\_APS\_LVL[p]. + +**NOTE –** The ODUk server layer section APS information may be present in the case where the ODUk signal contains an ODU-AIS, ODU-LCK or ODU-OCI maintenance signal. The ODU-LCK maintenance signal may be inserted in this adaptation source function. ODUk SNC/I protection is unable to detect the insertion of such ODU-LCK and will not perform a protection switch. + +**ODU-LCK:** The function shall generate the ODU-LCK signal as defined in clause 16.5 of [ITU-T G.709]. The clock, frame start and multiframe start are defined by the incoming ODUk signal. + +**Selector:** The normal signal for a tributary signal #p may be replaced by the ODU-LCK signal. The ODU-LCK signal is selected if the MI\_AdminState[p] is LOCKED. + +#### Common processes + +**Clock and (multi)frame start signal generation:** The function shall generate a local ODUCn clock (ODUCnP\_AI\_CK) of " $n \times 239/226 \times 40 \times 2\,488\,320\text{ kHz} \pm 20\text{ ppm}$ " from the synchronization timing information clock input (TI\_CK) or, if the TI\_CK is absent, a free-running oscillator. The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUCn signal. The AI\_FS signal shall be active once per $n \times 122\,368$ clock cycles. AI\_MFS shall be active once every 256 frames. + +**OPU multiframe (OMFI) start signal generation for OPUCn:** For OPUCn in addition to MFAS, a dedicated 20-frame OPU multiframe indicator is used for the multiplexing of LO ODUs into the OPUCn. This multiframe structure is locked to bits 4, 5, 6, 7 and 8 of the OMFI byte, as shown in Table 20-1 of [ITU-T G.709], and to be inserted into the OPU overhead. The function shall generate OPUCn multiframe and the related start signal (OMFS) dividing the frame signal sequence by 20. The OMFI start signal may optionally be phase aligned to the ODU multiframe signal. In this case, the OMFI = 0 position is aligned with MFAS = 0 position every 1280 frame periods. See clause 20.4.4 of [ITU-T G.709]. + +**Multiplexing:** The function assigns the individual ODTUCn.M to specific time slots of the OPUCn payload area as defined by the multiplex structure (see clauses 20.3 and 20.4.1 of [ITU-T G.709]). + +**MSI:** The function shall insert the TxMSI into the MSI byte positions of the PSI overhead as defined in clauses 20.4.1.4, 20.4.1.5, 20.4.1.6 of [ITU-T G.709]. The TxMSI value, and as such the multiplex structure, is configurable via MI\_TxMSI. + +**PT:** The function shall insert code "0010 0010" (ODU multiplex structure supporting ODTUCn.ts) into the PT byte position of the PSI overhead as defined in clause 15.13.2.1 of [ITU-T G.709]. + +**ODUCn APS:** The function shall insert the PI\_APS value into the ODUCn path APS/PCC field, which is available once per ODUCn frame. + +**RES:** The function shall insert all-ZEROs into the RES bytes. + +All other bits of the ODUCn overhead should be sourced as "0"s, except the PMOH STAT field which should be set to the value "normal path signal" (001). + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.3.16.2 ODUCnP to ODuk adaptation sink function (ODUCnP/ODuk\_A\_Sk) + +The ODUCnP/ODuk\_A\_Sk function extracts the OPUCn overhead (PT, MSI, RES and OMFI) and monitors the reception of the correct payload type. It demultiplexes the individual ODTUCn.M from the payload area of the OPUCn and recovers the $m \times$ ODuk signals using the justification control information (JC, JC1/2/3/4/5/6 overhead). It determines the frame and multiframe structure of the ODuk. It provides access to ODUCn APS overhead. + +The information flow and processing of the ODUCnP/ODuk\_A\_Sk function is defined with reference to Figures 14-92 and 14-93. + +#### Symbol + +![Diagram of the ODUCnP/ODuk_A_Sk function symbol. The central block is labeled 'ODUCnP/ODuk'. It has four input ports: 'ODUCnP/ODuk_A_Sk_MP' (left, double-headed arrow), 'ODUCn_PP' (left, single-headed arrow), 'ODUCn_TP' (right, single-headed arrow), and 'ODUCnP_AP' (bottom, single-headed arrow). It has multiple output ports labeled 'Tributary port' with sub-labels '1', '2', '...', and 'm'. Above these output ports is the label 'ODuk_CPs'. The diagram is labeled 'G.798(17)_F14-92' in the bottom right corner.](b4231d923aa1b23a3d9e7a2aa2942d1e_img.jpg) + +The diagram shows a central trapezoidal block labeled "ODUCnP/ODuk". To its left, there are two input ports: "ODUCnP/ODuk\_A\_Sk\_MP" with a double-headed arrow and "ODUCn\_PP" with a single-headed arrow pointing into the block. To its right, there is one input port: "ODUCn\_TP" with a single-headed arrow pointing into the block. Below the block, there is one input port: "ODUCnP\_AP" with a single-headed arrow pointing into the block. Above the block, there are multiple output ports labeled "Tributary port" with sub-labels "1", "2", "...", and "m". Above these output ports is the label "ODuk\_CPs". The diagram is labeled "G.798(17)\_F14-92" in the bottom right corner. + +Diagram of the ODUCnP/ODuk\_A\_Sk function symbol. The central block is labeled 'ODUCnP/ODuk'. It has four input ports: 'ODUCnP/ODuk\_A\_Sk\_MP' (left, double-headed arrow), 'ODUCn\_PP' (left, single-headed arrow), 'ODUCn\_TP' (right, single-headed arrow), and 'ODUCnP\_AP' (bottom, single-headed arrow). It has multiple output ports labeled 'Tributary port' with sub-labels '1', '2', '...', and 'm'. Above these output ports is the label 'ODuk\_CPs'. The diagram is labeled 'G.798(17)\_F14-92' in the bottom right corner. + +**Figure 14-92 – ODUCnP/ODuk\_A\_Sk function** + +## Interfaces + +**Table 14-42 – ODUCnP/ODUk\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUCnP_AP:
ODUCnP_AI_CK
ODUCnP_AI_D
ODUCnP_AI_FS
ODUCnP_AI_MFS
ODUCnP_AI_TSF
ODUCnP_AI_TSD
ODUCnP/ODUk_A_Sk_MP:
ODUCnP/ODUk_A_Sk_MI_ExMSI
ODUCnP/ODUk_A_Sk_MI_AdminState[1..m]
ODUCnP/ODUk_A_Sk_MI_Nominal_Bitrate_and_Tolerance[1..m]
ODUCnP/ODUk_A_Sk_MI_APS_EN[1..m]
ODUCnP/ODUk_A_Sk_MI_APS_LVL[1..m] | m × ODUk_CP:
ODUk_CI_CK
ODUk_CI_D
ODUk_CI_FS
ODUk_CI_MFS
ODUk_CI_SSF
ODUk_CI_SSD
ODUk_CI_APS
ODUCnP_PP:
ODUCnP_PI_APS
ODUCnP_PI_TSF
ODUCnP_PI_TSD
ODUCnP/ODU[i]j_A_Sk_MP:
ODUCnP/ODUk_A_Sk_MI_cPLM
ODUCnP/ODUk_A_Sk_MI_cLOOMFI
ODUCnP/ODUk_A_Sk_MI_cMSIM[1..m]
ODUCnP/ODUk_A_Sk_MI_AcPT
ODUCnP/ODUk_A_Sk_MI_AcMSI
ODUCnP/ODUk_A_Sk_MI_cLOFLOM[1..m] | + +## Processes + +The processes associated with the ODUCnP/ODUk\_A\_Sk function are specific processes for each ODUk\_CP and common processes for the compound (multiplexed) signal as depicted in Figure 14-93. + +![Block diagram of ODUCnP/ODUk_A_Sk processes showing signal flow from multiple client processes through a demultiplexer and various processing blocks to output interfaces.](29a5f4072e91dc4857fce0ace805e0d4_img.jpg) + +The diagram illustrates the internal architecture of ODUCnP/ODUk\_A\_Sk processes. At the top, multiple client-specific processes are shown, labeled ODUk\_CP[1] through ODUk\_CP[m]. Each client process has a set of input signals (AI\_TSD, AI\_TSF, dPLM, dLOOMFI, dMSIM[i], MI\_cMSIM[i], MI\_cLOFLOM[i], MI\_AdminState[i], MI\_APS\_EN[i], MI\_APS\_LVL[i], MI\_Nominal\_Bitrate\_and\_Tolerance[i]) and output signals (CL\_MFS, CL\_FS, CL\_CK, CL\_D, CL\_APS, CL\_SSF, CL\_SSD). The outputs from all client processes are fed into a central 'Demultiplexer' block. The demultiplexer has a 'Multiplex structure' output and several processing paths. One path goes through 'Extract MSI' and 'MSI process' to produce MI\_ExMSI and MI\_AcMSI. Another path goes through 'Extract PT' and 'PT process' to produce MI\_AcPT. A third path goes through 'ODUCn PM APS' to produce PI\_APS. A fourth path goes through 'Extract OMFI' and 'OMFI process' to produce OMFS. A 'Defect correlations' block receives AI\_TSF and dPLM from the client processes and produces MI\_cLOOFMI, MI\_cPLM, MI\_cMSIM[1..m], MI\_cLOFLOM[1..m], MI\_AdminState[1..m], MI\_APS\_EN[1..m], MI\_APS\_LVL[1..m], and MI\_Nominal\_Bitrate\_and\_Tolerance[1..m]. The bottom section, labeled ODUCnP\_AP, shows the final output interfaces: AI\_MFS, AI\_FS, AI\_CK, AI\_D, AI\_TSF, and AI\_TSD. The right side of the diagram is divided into two main output groups: ODUCnP/ODUk\_A\_Sk\_MP and ODUCnP\_PP. The ODUCnP/ODUk\_A\_Sk\_MP group includes MI\_cLOOFMI, MI\_cPLM, MI\_cMSIM[1..m], MI\_cLOFLOM[1..m], MI\_AdminState[1..m], MI\_APS\_EN[1..m], MI\_APS\_LVL[1..m], MI\_Nominal\_Bitrate\_and\_Tolerance[1..m], MI\_ExMSI, MI\_AcMSI, and MI\_AcPT. The ODUCnP\_PP group includes PI\_APS, PI\_TSF, and PI\_TSD. The diagram is labeled G.798(17)\_F14-93. + +Block diagram of ODUCnP/ODUk\_A\_Sk processes showing signal flow from multiple client processes through a demultiplexer and various processing blocks to output interfaces. + +Figure 14-93 – ODUCnP/ODUk\_A\_Sk processes + +![Block diagram of ODUCnP/ODUk_A_Sk client specific processes. The diagram shows the internal architecture of the client-specific processes, including signal flow from input (OMFS, MFAS, FS, CK, D, TS#, Active) through various functional blocks like Elastic store, Clock generation (ODCp), Justification control, Extract JC, Frame/multi-frame alignment, dLOFLOM detection, Defect correlations, ODuk APS, Generate AIS, Generate LCK, Select normal/AIS/LCK, and Consequent actions. Output signals include CI_MFS, CI_FS, CI_CK, CI_D, CI_APS, CI_SSF, and CI_SSD. Management interfaces (MI) and alarm signals (AI) are also shown.](36a1eab8868d8db81c6b28fbd0d5730f_img.jpg) + +The diagram illustrates the internal processes of an ODUCnP/ODUk\_A\_Sk client. At the bottom, input signals (OMFS, MFAS, FS, CK, D, TS#, Active) enter the system. The 'Elastic store' block receives 'D' and 'CK' signals and has 'RD' (Read) and 'WR' (Write) ports. The 'WR' port is connected to 'Clock generation (ODCp)', which in turn connects to 'Justification control' and 'Extract JC'. The 'Justification control' connects to 'Frame/multi-frame alignment'. The 'Elastic store' also connects to 'Frame/multi-frame alignment' via 'RD' and 'CK' signals. The 'Frame/multi-frame alignment' block outputs 'D' and 'CK' signals to 'dLOFLOM detection'. The 'dLOFLOM detection' block outputs 'dLOFLOM' to 'Defect correlations'. The 'Defect correlations' block receives 'AI\_TSF' and various management information (MI) signals: 'dPLM', 'dLOOMFI', 'dMSIM[p]', 'MI\_cMSIM[p]', and 'MI\_cLOFLOM[p]'. It also outputs 'aAIS', 'aSSF', and 'aSSD' to 'Consequent actions'. The 'Consequent actions' block receives 'MI\_AdminState[p]', 'AI\_TSD', and 'AI\_TSF' signals. The 'Consequent actions' block also connects to 'Generate AIS' and 'Generate LCK' blocks. These blocks receive 'MI\_Nominal\_Bitrate\_and\_Tolerance[p]' and output signals to 'Select normal/AIS/LCK'. The 'Select normal/AIS/LCK' block outputs 'Normal', 'AIS', and 'LCK' signals. These signals are then processed by 'ODUk APS', which receives 'MI\_APS\_EN[p]' and 'MI\_APS\_LVL[p]' signals. The 'ODUk APS' block outputs 'CI\_APS' signal. Finally, the 'Select normal/AIS/LCK' block outputs 'CI\_MFS', 'CI\_FS', 'CI\_CK', and 'CI\_D' signals. The 'Consequent actions' block also outputs 'CI\_SSF' and 'CI\_SSD' signals. The entire process is labeled 'ODUk\_CP[p]' at the top. A reference 'G.798(17)-Amd.3(21)\_F14-94' is noted at the bottom right of the diagram. + +Block diagram of ODUCnP/ODUk\_A\_Sk client specific processes. The diagram shows the internal architecture of the client-specific processes, including signal flow from input (OMFS, MFAS, FS, CK, D, TS#, Active) through various functional blocks like Elastic store, Clock generation (ODCp), Justification control, Extract JC, Frame/multi-frame alignment, dLOFLOM detection, Defect correlations, ODuk APS, Generate AIS, Generate LCK, Select normal/AIS/LCK, and Consequent actions. Output signals include CI\_MFS, CI\_FS, CI\_CK, CI\_D, CI\_APS, CI\_SSF, and CI\_SSD. Management interfaces (MI) and alarm signals (AI) are also shown. + +**Figure 14-94 – ODUCnP/ODUk\_A\_Sk client specific processes** + +### Common processes + +**OPU multiframe (OMFI) reception for OPUCn:** For OPUCn in addition to MFAS, a dedicated 20-frame OPU multiframe indicator is used for the multiplexing of LO ODUs into the OPUCn. This multiframe structure is locked to bits 4, 5, 6, 7 and 8 of the OMFI byte, as shown in Table 20-1 of [ITU-T G.709]. The function shall detect OPU multiframe by searching for the framing pattern in the bits indicated above. The process has two states, out-of-multiframe (OOM) and in-multiframe (IM). The IM state shall be entered if this set is found and confirmed one frame period later and an error-free multiframe sequence is found in the byte positions of the two frames. In the IM state, the frame alignment signal shall be continuously checked with the presumed OMFI frame start position and the expected multiframe sequence. The OOM state shall be entered if this subset is not found at the correct position in five consecutive frames or the received OMFI does not match with the expected multiframe number in five consecutive frames. The OPUCn multiframe start (OMFS) shall be maintained during the OOM state of the OMFI detection process. The defect dLOOMFI shall be generated based on the state of the OMFI alignment process. + +If the OMFI alignment process is persistently in the out-of-multiframe (OOM) state for 3 ms, dLOOMFI shall be declared. dLOOMFI shall be cleared immediately when the OMFI alignment process is in the in-multiframe (IM) state. + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. The PLM detection shall be based on the comparison of the accepted PT with the value 0x22. + +**MSI:** The function shall extract the MSI from the PSI overhead as defined in clause 8.7.2.2. The accepted MSI (AcMSI) is available at the MP (MI\_AcMSI). The multiplex structure is defined by ExMSI, which is configurable via MI\_ExMSI. + +**RES:** The value in the RES bytes shall be ignored. + +**ODUCn APS:** The function shall extract the information from the ODUCn APS/PCC field and apply this to the PI\_APS. + +**Demultiplexing:** The function activates the ODTUCn.M and assigns the time slots of the ODUCn payload area to the individual ODTUCn.M as defined by the multiplex structure (see clauses 20.3 and 20.4.1 of [ITU-T G.709]). + +### Specific processes + +The specific processes are performed independently for each ODUk client signal that is multiplexed into the OPUCn. The specific processes recover the ODUk from the ODTUCn.M. + +Justification method GMP (*ODTUCn.M*) as described below is provided. The ODU rate, as configured via the MI\_Nominal\_Bitrate\_and\_Tolerance[p] input for tributary port #p, determines the base value and ranges for the parameters $C_n$ and $C_m$ . + +**ODTUCn.ts JC1/2/3 and JC4/5/6:** The function shall interpret the GMP overhead information in the JC1/2/3 and JC4/5/6 bytes as defined in clause 20.5 of [ITU-T G.709] in order to determine the number of 16M-byte ODUk entities in the next ODTUCn.M multiframe. The OPUCn frame that contains the JC1/2/3 and JC4/5/6 bytes depends on the last tributary slot that is occupied by the ODTUCn.M. + +**Demapping, CBR clock generation:** The function shall provide an elastic store (buffer) process. + +*ODTUCn.M:* The ODUk data shall be extracted from the groups of 16M successive bytes of the ODTUCn.M payload area under the control of the GMP data/stuff control mechanism as defined in clause 20.5 of [ITU-T G.709] and be written into the buffer. The $C_n$ information associated with the ODUk is computed from the GMP $C_m$ and $\Sigma C_{nD}$ parameters carried within the JC1/2/3 and JC 4/5/6 overhead of the ODTUCn.M as specified in clause 20.5 of [ITU-T G.709]. For the GMP data/stuff control mechanism, refer to Annex D of [ITU-T G.709]. + +The ODUk data (CI\_D) shall be read out of the buffer under the control of the ODUk clock (CI\_CK). + +*Smoothing and jitter limiting process:* The function shall provide for a clock smoothing and elastic store (buffer) process. The ODUk data signal shall be written into the buffer under the control of the associated (gapped) OPUCn input clock (with a frequency accuracy within ± 20 ppm). The data signal shall be read out of the buffer under the control of a smoothed (equally spaced) ODUk clock (the rate is determined by the ODUk signal at the input of the remote ODUCnP/ODUk\_A\_So). + +The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCp clock), apply. + +*Buffer size:* In the presence of jitter as specified by [ITU-T G.8251] and a frequency within the tolerance range specified for the ODUk signal in Table 7-2 of [ITU-T G.709], this justification process shall not introduce any errors. + +Following a step in frequency of the ODUk signal transported (for example, due to reception of ODUk\_CI from a new ODUk\_TT\_So at the far end or removal of a ODU-AIS signal with a frequency offset), there will be a maximum recovery time of X seconds after which this process shall not generate any bit errors. The value of X is for further study; a value of one second has been proposed. + +**Frame and multiframe alignment:** The function shall perform frame and multiframe alignment as described in clause 8.2.3. + +NOTE 1 – The 16-byte word alignment of the extended ODUk is preserved through the mapping procedure; e.g., the position of the first 16 OH bytes of the ODUk is always located after an integer number of 16-byte words from the start of the ODTUCn.M structure. + +**ODU-LCK, ODU-AIS:** The function shall generate the ODU-LCK and ODU-AIS signals as defined in [ITU-T G.709]. The clock, frame start and multiframe start shall be independent from the incoming clock. The clock has to be within the ODUk frequency tolerance range as specified in Table 7-2 of [ITU-T G.709] provisioned by the MI\_Nominal\_Bitrate\_and\_Tolerance[p] from a free-running oscillator. Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +**Selector:** The normal signal for a tributary signal #p may be replaced by either the ODU-AIS or ODU-LCK signal. ODU-LCK is selected if the corresponding MI\_AdminState[p] signal is LOCKED. ODU-AIS is selected if the corresponding MI\_AdminState[p] signal is not LOCKED and aAIS is true. + +**ODUk server layer APS:** When APS is enabled for tributary signal #p (MI\_APS\_EN[p] is true), the function shall extract the information from the ODU APS/PCC[MI\_APS\_LVL[p]] field, which is available once per eight ODU frames when the value of the MFAS bits 6, 7, 8 is equal to MI\_APS\_LVL[p], and apply the extracted information to the CI\_APS. + +NOTE – The ODUk server layer section APS information may be present in the case where the ODUk signal contains an ODU-AIS or ODU-LCK maintenance signal. The ODU-LCK maintenance signal may have been inserted in the far-end adaptation source function. ODUk SNC/I protection is unable to detect the insertion of such ODU-LCK and will not perform a protection switch. + +## Defects + +The function shall detect dPLM, dMSIM, dLOOMFI and dLOFLOM. + +**dPLM:** See clause 6.2.4.1. The expected payload type is "0010 0010" (ODU multiplex structure supporting ODTUCn.ts) as defined in [ITU-T G.709]. + +**dLOOMFI:** dLOOMFI is detected per OPUCn. See the OPU multiframe (OMFI) detection process for OPUCn. + +For each ODUk tributary port #p: + +**dMSIM[p]:** See clause 6.2.9.2. dMSIM is detected per active ODUk. + +**dLOFLOM[p]:** See clause 6.2.5.3. dLOFLOM is detected per active ODUk. + +## Consequent actions + +PI\_TSF $\leftarrow$ AI\_TSF + +PI\_TSD $\leftarrow$ AI\_TSD + +For each ODUk tributary port #p: + +aSSF[p] $\leftarrow$ ((AI\_TSF or dPLM or dLOOMFI or dMSIM[p] or dLOFLOM[p]) and (not MI\_AdminState[p] = LOCKED)) + +aSSD[p] $\leftarrow$ AI\_TSD and (not MI\_AdminState[p] = LOCKED) + +$aAIS[p] \leftarrow ((AI\_TSF \text{ or } dPLM \text{ or } dLOOMFI \text{ or } dMSIM[p] \text{ or } dLOFLOM[p]) \text{ and } (\text{not } MI\_AdminState[p] = \text{LOCKED}))$ + +NOTE – The state of the determination process of the $C_m$ and its contribution to AIS consequent action are for further study. + +On declaration of $aAIS$ , the function shall output an all-ONEs pattern/signal within two frames. On clearing $aAIS$ , the all-ONEs pattern/signal shall be removed within two frames, with normal data being output. The AIS clock, frame start and multiframe start shall be independent from the incoming clock, frame start and multiframe start. The clock has to be within the ODUk frequency tolerance range as specified in Table 7-2 of [ITU-T G.709] provisioned by the $MI\_Nominal\_Bitrate\_and\_Tolerance[p]$ from a free-running oscillator. Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock) apply. + +#### Defect correlations + +$cPLM \leftarrow dPLM \text{ and } (\text{not } AI\_TSF)$ + +$cLOOMFI \leftarrow dLOOMFI \text{ and } (\text{not } AI\_TSF)$ + +For each ODUk tributary port #p: + +$cMSIM[p] \leftarrow dMSIM[p] \text{ and } (\text{not } dPLM) \text{ and } (\text{not } dLOOMFI) \text{ and } (\text{not } AI\_TSF)$ + +$cLOFLOM[p] \leftarrow dLOFLOM[p] \text{ and } (\text{not } dPLM) \text{ and } (\text{not } dLOOMFI) \text{ and } (\text{not } AI\_TSF)$ + +**Performance monitoring:** None. + +#### 14.3.17 ODUflexP to FlexE client adaptation function using IMP (ODUflexP/FlexEC\_A) + +The ODUflexP/FlexEC\_A performs the adaptation between the ODUflexP layer adapted information and the characteristic information of the indicated FlexE client signals transported as flexible bit-rate streams. + +The bit rates of FlexEC are 10, 40 and $n \times 25$ Gbit/s ( $n \geq 1$ ) given in Table 14-43 as described in clause 17.11 of [ITU-T G.709]. + +**Table 14-43 – Defined FlexEC for ODUflex clients** + +| FlexEC bit rate | Bit rate | Clock tolerance | +|-----------------|----------------------------------|-----------------| +| 10G | 10 312 500 (kbit/s) | $\pm 100$ ppm | +| 40G | 41 250 000 (kbit/s) | $\pm 100$ ppm | +| $n \times 25G$ | $n \times 25\ 781\ 250$ (kbit/s) | $\pm 100$ ppm | + +##### 14.3.17.1 ODUflexP to FlexE client adaptation source function using IMP (ODUflexP/FlexEC\_A\_So) + +The ODUflexP/FlexEC\_A\_So function creates the ODUflex signal from the FlexE client clock or a local clock. It maps the flexible bit-rate client signal from the FlexEC\_CP into the payload area of the OPUflex using IMP as defined in clause 17.11 of [ITU-T G.709], and adds OPUflex overhead (PT, CSF and RES) and default ODUflex overhead. + +The information flow of the ODUflexP/FlexEC\_A\_So function is defined with reference to Figure 14-95 and the processing of the ODUflexP/FlexEC\_A\_So function is defined with reference to Figure 14-96. + +## Symbol + +![Symbol diagram for the ODUflexP/FlexEC_A_So function. It shows a trapezoidal block labeled 'ODUflexP/FlexEC'. An arrow labeled 'FlexEC_CP' points into the top of the block, and an arrow labeled 'ODUflexP_AP' points out from the bottom. Below the block is the reference code 'G.798(17)_F14-95'.](ac1b4040daa037941f51deeedbcd585a_img.jpg) + +Symbol diagram for the ODUflexP/FlexEC\_A\_So function. It shows a trapezoidal block labeled 'ODUflexP/FlexEC'. An arrow labeled 'FlexEC\_CP' points into the top of the block, and an arrow labeled 'ODUflexP\_AP' points out from the bottom. Below the block is the reference code 'G.798(17)\_F14-95'. + +**Figure 14-95 – ODUflexP/FlexEC\_A\_So function** + +## Interfaces + +**Table 14-44 – ODUflexP/FlexEC\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------| +| FlexEC_CP:
FlexEC_CI_CK
FlexEC_CI_D
FlexEC_CI_SSF | ODUflexP_AP:
ODUflexP_AI_CK
ODUflexP_AI_D
ODUflexP_AI_FS
ODUflexP_AI_MFS | + +## Processes + +**Clock generation:** The function shall generate an ODUflex clock (ODUflexP\_AI\_CK) – according to one of the methods described in clause 12.2.6 of [ITU-T G.709] – with a bit rate as specified in Table 7-2 of [ITU-T G.709]. The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (in case of methods 1 and 2 ODCa clock, in case of method 3 ODCb clock), apply. + +**FS & MFS generation:** The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUflex signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +**Bit-rate adaptation, scrambler, mapping and frequency justification:** The function shall provide an elastic store (buffer) process. The data signal of 66b blocks shall be written into the buffer under the control of the associated input clock. The adjusted data signal of 66b blocks shall be read out of the buffer, scrambled and be written onto the OPUflex payload under the control of IMP as defined in clause 17.11 of [ITU-T G.709]. The 66b blocks are aligned so that the first bit of the sync header appears in one of the bit positions 1, 3, 5, or 7 of a byte in the OPUflex payload. *Scrambler:* The function shall scramble 66b block stream after rate adaptation and before mapping into the OPUflex. + +*Buffer size:* In the presence of bit rate differences between OPUflex and FlexEC signals, this mapping process shall not insert or delete a 66b block between a Start (0x78) and Terminate (0x87/0x99/0xAA/0xB4/0xCC/0xD2/0xE1/0xFF) control block. + +**PT:** The function shall insert the payload type code "0001 1101" (0x1D) into the PT byte position of the PSI overhead, as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**Client signal fail:** The function shall signal the failure of the client signal to the far end by use of the Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +**RES:** The function shall insert all-ZEROs into the RES bytes and reserved bits within the JC bytes. + +All other bits of the ODUflex overhead should be sourced as "0"s, except the ODUflex-PM STAT field which should be set to the value "normal path signal" (001). + +![Block diagram of the ODUflexP/FlexEC_A_So function. The diagram shows the internal processing of a FlexE client signal (CI_D, CI_CK, CI_SSF) through rate adaptation, scrambling, and elastic store. The elastic store is controlled by a Justification control (IMP) block. The IMP block also receives inputs from a clock generator (which is fed by a free-running clock generator ODCa) and a frequency synthesizer (1/122368). The output of the elastic store is processed by an Insert PT, Insert CSF, and Insert RES block, and then an ODU OH is set to all-0's, except PM STAT = 001. The final output is AI_D, AI_CK, AI_FS, and AI_MFS. The diagram is labeled FlexEC_CP at the top and ODUflexP_AP at the bottom. A reference G.798(17)-Amd.2(19)_F14-96 is also present.](6f7f18cd6ddcabd5553b75ef3dc97d15_img.jpg) + +Block diagram of the ODUflexP/FlexEC\_A\_So function. The diagram shows the internal processing of a FlexE client signal (CI\_D, CI\_CK, CI\_SSF) through rate adaptation, scrambling, and elastic store. The elastic store is controlled by a Justification control (IMP) block. The IMP block also receives inputs from a clock generator (which is fed by a free-running clock generator ODCa) and a frequency synthesizer (1/122368). The output of the elastic store is processed by an Insert PT, Insert CSF, and Insert RES block, and then an ODU OH is set to all-0's, except PM STAT = 001. The final output is AI\_D, AI\_CK, AI\_FS, and AI\_MFS. The diagram is labeled FlexEC\_CP at the top and ODUflexP\_AP at the bottom. A reference G.798(17)-Amd.2(19)\_F14-96 is also present. + +Figure 14-96 – ODUflexP/FlexEC\_A\_So function + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.3.17.2 ODUflexP to FlexE client adaptation sink function using IMP (ODUflexP/FlexEC\_A\_Sk) + +The ODUflexP/FlexEC\_A\_Sk recovers the FlexE client signal from the OPUflex payload using the justification control of IMP. It extracts the OPUflex overhead (PT and CSF) and monitors the reception of the correct payload type. Under signal fail condition, a replacement signal as specified in clause 17.11 of [ITU-T G.709] shall be inserted. + +The information flow and processing of the ODUflexP/FlexEC\_A\_Sk function is defined with reference to Figures 14-97 and 14-98. + +## Symbol + +![Symbol diagram for the ODUflexP/FlexEC_A_Sk function. A central trapezoidal block labeled 'ODUflexP/FlexEC' has three connections: an input arrow from the bottom labeled 'ODUflexP_AP', an output arrow pointing up labeled 'FlexEC_CP', and an output arrow pointing left labeled 'ODUflexP/FlexEC_A_Sk_MP'. A small reference code 'G.798(17)_F14-97' is located below the block.](9707839366bb5cf01a4a5b4abd8c1264_img.jpg) + +Symbol diagram for the ODUflexP/FlexEC\_A\_Sk function. A central trapezoidal block labeled 'ODUflexP/FlexEC' has three connections: an input arrow from the bottom labeled 'ODUflexP\_AP', an output arrow pointing up labeled 'FlexEC\_CP', and an output arrow pointing left labeled 'ODUflexP/FlexEC\_A\_Sk\_MP'. A small reference code 'G.798(17)\_F14-97' is located below the block. + +**Figure 14-97 – ODUflexP/FlexEC\_A\_Sk function** + +## Interfaces + +**Table 14-45 – ODUflexP/FlexEC\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUflexP_AP:
ODUflexP_AI_CK
ODUflexP_AI_D
ODUflexP_AI_FS
ODUflexP_AI_MFS
ODUflexP_AI_TSF | FlexEC_CP:
FlexEC_CI_CK
FlexEC_CI_D
FlexEC_CI_SSF
ODUflexP/FlexEC_A_Sk_MP:
ODUflexP/FlexEC_A_Sk_MI_cPLM
ODUflexP/FlexEC_A_Sk_MI_AcPT
ODUflexP/FlexEC_A_Sk_MI_cCSF
ODUflexP/FlexEC_A_Sk_MI_cLCS | + +## Processes + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. + +**Client signal fail:** The function shall extract the CSF signal indicating the failure of the client signal out of Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +**Demapping:** The function shall extract the client data from the payload bytes in the OPUflex frames. The information extraction of the payload area shall be under the control of IMP. + +**Block synchronization:** See clause 8.2.7.1 for mapping procedures preserving the 2-bit alignment. + +**Descrambler:** The function shall descramble the 66b block stream before the rate adaptation. + +**Rate adaptation and FlexEC clock generation:** The function shall provide an elastic store (buffer) process. It writes the descrambled 66b block data stream into the buffer. The information extraction of the payload area shall be under the control of IMP. The FlexEC data (CI\_D) shall be read out of the buffer under the control of the FlexEC clock (CI\_CK). + +**FlexE client clock generation:** The function shall provide for a FlexEC clock generation process which generates a clock with a bit rate as specified in Table 14-43. + +**Buffer size:** In the presence of bit rate differences between OPUflex and FlexEC signals, this demapping process shall not insert or delete a 66b block between a Start (0x78) and Terminate (0x87/0x99/0xAA/0xB4/0xCC/0xD2/0xE1/0xFF) control block. + +**Replacement signal generation:** The function shall provide for an FlexEC replacement signal and clock generation process that generates a stream of local fault sequence ordered sets as specified in clause 17.11 of [ITU-T G.709] with a bit rate as specified in Table 14-43. + +![Figure 14-98 – ODUflexP/FlexEC_A_Sk processes. This block diagram illustrates the internal architecture of the ODUflexP/FlexEC_A_Sk process. At the bottom, the ODUflexP_AP interface provides inputs AI_D, AI_MFS, AI_CK, AI_FS, and AI_TSF. AI_D and AI_MFS feed into an Elastic store (with WR and RD ports). AI_CK and AI_FS feed into an ETCflex clock generator (IMP) and the Elastic store. AI_TSF feeds into a PT process and Defect correlations. The Elastic store's WR output goes to the IMP and a Block synchronization block. The Block synchronization block outputs dLCS to a Descrambler and the Selector. The Descrambler's output goes to the Selector. The Selector outputs CI_D, CI_CK, and CI_SSF to the FlexEC_CP. The IMP outputs CK to the Descrambler and Defect correlations. The Defect correlations block receives dLCS, dPLM, dCSF, and AI_TSF as inputs and outputs MI_cLCS, MI_cPLM, and MI_cCSF. The Extract CSF block receives AI_D and AI_MFS and outputs dCSF. The Extract PT block receives AI_D and AI_MFS and outputs dPLM. The PT process receives dPLM and AI_TSF and outputs MI_AcPT. The Replacement signal generator receives aAIS from the Consequent actions block and outputs CI_CK to the Selector. The Consequent actions block receives dLCS, dPLM, dCSF, and AI_TSF and outputs aAIS to the Replacement signal generator. The entire process is labeled ODUflexP/FlexEC_A_Sk_MP on the right side.](eb8cac9fb65d601ab50405472e408156_img.jpg) + +Figure 14-98 – ODUflexP/FlexEC\_A\_Sk processes. This block diagram illustrates the internal architecture of the ODUflexP/FlexEC\_A\_Sk process. At the bottom, the ODUflexP\_AP interface provides inputs AI\_D, AI\_MFS, AI\_CK, AI\_FS, and AI\_TSF. AI\_D and AI\_MFS feed into an Elastic store (with WR and RD ports). AI\_CK and AI\_FS feed into an ETCflex clock generator (IMP) and the Elastic store. AI\_TSF feeds into a PT process and Defect correlations. The Elastic store's WR output goes to the IMP and a Block synchronization block. The Block synchronization block outputs dLCS to a Descrambler and the Selector. The Descrambler's output goes to the Selector. The Selector outputs CI\_D, CI\_CK, and CI\_SSF to the FlexEC\_CP. The IMP outputs CK to the Descrambler and Defect correlations. The Defect correlations block receives dLCS, dPLM, dCSF, and AI\_TSF as inputs and outputs MI\_cLCS, MI\_cPLM, and MI\_cCSF. The Extract CSF block receives AI\_D and AI\_MFS and outputs dCSF. The Extract PT block receives AI\_D and AI\_MFS and outputs dPLM. The PT process receives dPLM and AI\_TSF and outputs MI\_AcPT. The Replacement signal generator receives aAIS from the Consequent actions block and outputs CI\_CK to the Selector. The Consequent actions block receives dLCS, dPLM, dCSF, and AI\_TSF and outputs aAIS to the Replacement signal generator. The entire process is labeled ODUflexP/FlexEC\_A\_Sk\_MP on the right side. + +**Figure 14-98 – ODUflexP/FlexEC\_A\_Sk processes** + +### Defects + +The function shall detect dPLM, dCSF and dLCS. + +**dPLM:** See clause 6.2.4.1. The expected payload type is "0001 1101" as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**dCSF:** See clause 6.2.10. + +**dLCS:** See clause 6.2.5.7.1. + +### Consequent actions + +aSSF $\leftarrow$ AI\_TSF or dPLM or dLCS + +aAIS $\leftarrow$ AI\_TSF or dPLM or dLCS + +For FlexE clients, on declaration of aAIS, the function shall output the FlexE client replacement signal within two ODUflex frames. On clearing aAIS, the replacement signal shall be removed within two ODUflex frames and normal data being output. + +## Defect correlations + +cPLM $\leftarrow$ dPLM and (not AI\_TSF) + +cCSF $\leftarrow$ dCSF and (not dPLM) and (not AI\_TSF) + +cLCS $\leftarrow$ dLCS and (not dPLM) and (not AI\_TSF) + +Performance monitoring: None. + +### 14.3.18 ODUflexP to FlexE sub-group adaptation function using BGMP (ODUflexP/FlexESG\_A) + +The ODUflexP/FlexESG\_A performs the adaptation between the ODUflexP layer adapted information and the characteristic information of the FlexE partial rate (sub)group signals (FlexESGM\_CI). + +#### 14.3.18.1 ODUflexP to FlexE sub-group adaptation source function using BGMP (ODUflexP/FlexESG\_A\_So) + +The ODUflexP/FlexESG\_A\_So function creates the ODUflex signal from the FlexE partial rate (sub)group signal clock. It maps the flexible bit-rate client signal from the FlexE partial rate (sub)group into the payload area of the OPUflex using BGMP as defined in clause 17.12 of [ITU-T G.709], and adds OPUflex overhead (PT, PSI, JC and CSF) and default ODUflex overhead. + +The information flow of the ODUflexP/FlexESG\_A\_So function is defined with reference to Figure 14-99 and the processing of the ODUflexP/FlexESG\_A\_So function is defined with reference to Figure 14-100. + +## Symbol + +![Diagram of the ODUflexP/FlexESG_A_So function symbol. The symbol is a trapezoid labeled 'ODUflexP/FlexESG'. It has multiple inputs from the top labeled 'FlexESGM_CPs' with subscripts 1, 2, ..., p. It has one input from the left labeled 'ODUflexP/FlexESG_A_So_MP'. It has one output from the bottom labeled 'ODUflexP_AP'. Below the output label is the text 'G.798(17)-Amd.4(22)_F14-F99'.](ec27906099ab5da32f29b89d2764cf0c_img.jpg) + +Diagram illustrating the ODUflexP/FlexESG\_A\_So function symbol. The symbol is a trapezoid labeled "ODUflexP/FlexESG". Inputs from the top are labeled "FlexESGM\_CPs" with subscripts 1, 2, ..., p. An input from the left is labeled "ODUflexP/FlexESG\_A\_So\_MP". The output from the bottom is labeled "ODUflexP\_AP". Below the output label is the text "G.798(17)-Amd.4(22)\_F14-F99". + +Diagram of the ODUflexP/FlexESG\_A\_So function symbol. The symbol is a trapezoid labeled 'ODUflexP/FlexESG'. It has multiple inputs from the top labeled 'FlexESGM\_CPs' with subscripts 1, 2, ..., p. It has one input from the left labeled 'ODUflexP/FlexESG\_A\_So\_MP'. It has one output from the bottom labeled 'ODUflexP\_AP'. Below the output label is the text 'G.798(17)-Amd.4(22)\_F14-F99'. + +Figure 14-99 – ODUflexP/FlexESG\_A\_So function + +## Interfaces + +**Table 14-46 – ODUflexP/FlexESG\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| p × FlexESGM_CP:
FlexESGM_CI_CK
FlexESGM_CI_D
FlexESGM_CI_FS
FlexESGM_CI_MFS
FlexESGM_CI_CRCerr
FlexESGM_CI_SSF
ODUflexP/FlexESG_A_So_MP:
ODUflexP/FlexESG_A_So_MI_ExGID
ODUflexP/FlexESG_A_So_MI_ExFMAP
ODUflexP/FlexESG_A_So_MI_CS_n[1..p] | ODUflexP_AP:
ODUflexP_AI_CK
ODUflexP_AI_D
ODUflexP_AI_FS
ODUflexP_AI_MFS
ODUflexP/FlexESG_A_So_MP:
ODUflexP/FlexESG_A_Sk_MI_AcGID[1..p]
ODUflexP/FlexESG_A_Sk_MI_AcFMAP[1..p]
ODUflexP/FlexESG_A_Sk_MI_AcIID[1..p]
ODUflexP/FlexESG_A_So_MI_AcCC[1..p]
ODUflexP/FlexESG_A_So_MI_AcCCA[1..p]
ODUflexP/FlexESG_A_So_MI_AcCCB[1..p]
ODUflexP/FlexESG_A_So_MI_cFMM
ODUflexP/FlexESG_A_So_MI_cGIDM
ODUflexP/FlexESG_A_So_MI_cLOL
ODUflexP/FlexESG_A_So_MI_cCSUM | + +## Processes + +**FlexE OH Monitor:** The function shall monitor the overhead of FlexE group interface (GID, PID, MAP and Client Calendar) from each of the p FlexESGM\_CI signals as defined in clause 7.3 of [OIF FlexE IA]. + +- **FlexE GID:** The GID fields shall be read from the FlexE overhead and processed as specified in clause B.2.2.1. The accepted GID values are available at the MP (MI\_AcGID[i]) and are used for dGIDM defect detection. +- **FlexE IID:** The PID fields shall be read from the FlexE overhead and processed as specified in clause B.2.2.2. The accepted IID values are available at the MP (MI\_AcIID[i]) and are used for dFMM defect detection. +- **FlexE MAP:** The FlexE MAP fields shall be read from the FlexE overhead and processed as specified in clause B.2.2.3. The accepted MAP values are available at the MP (MI\_AcFMAP[i]) and are used for dFMM defect detection. + +**Clock generation:** The function shall generate an ODUflex clock (ODUflexP\_AI\_CK) as given in Table 7-2 of [ITU-T G.709] from the incoming client. The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCb clock), apply. During failure conditions of an incoming FlexESGM signal (CI\_CK), the ODUflex clock shall stay within its limits as defined in [ITU-T G.8251] and no frame phase discontinuity shall be introduced. + +**FS & MFS generation:** The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUflex signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +**FlexESG Deskew:** The function shall compensate the skew between p FlexESGM signals as described in clause 17.12 of [ITU-T G.709]. The alignment process shall establish the delay compensation, compensating the differential delay between the FlexE Instances as given in clause 6.4 of [OIF FlexE IA]. The compensation between the FlexE Instances is achieved by an elastic store per + +FlexE Instance. Each elastic store shall be capable of compensating at least 300 ns of absolute differential delay between the FlexE Instances. + +**FlexE OH client calendar:** The calendar information shall be read from the calendar configuration in use (C), client calendar A and B, calendar switch request (CR) and calendar switch acknowledge (CA) overheads as defined in clauses 6.4, 7.3.2 and 7.3.4 of [OIF FlexE IA]. + +- *Calendar configuration in use overhead (C):* The "calendar configuration in use" overhead from each member shall be accepted (AcCC[i]) by majority vote of the 3 C overhead bits. Furthermore, it shall confirm the accepted "AcCC" by unanimity of n FlexE Instances of the FlexE group. +- *Client calendar A and B overheads:* The "client calendar A" and "client calendar B" overhead fields from each member shall be read and the calendar slot information shall be accepted in overhead frames with good CRC ( AcCCA[i] and AcCCB[i]). + +**Crunching:** The function shall remove the FlexE (sub)group calendar slots indicated by MI\_CS\_n[1..p] if and only if these calendar slots are marked as unavailable calendar slots in the active FlexE client calendar overhead as described in clause 17.12 of [ITU-T G.709]. + +**Padding:** The function shall add $n_i-1$ padding blocks between the overhead block and the first sub-calendar block in each of the p FlexESGM signals as described in clause 17.12 of [ITU-T G.709]. + +**Interleaving:** The function shall interleave the p crunched and padded FlexESGM signals into a 66b block stream as described in clause 17.12 of [ITU-T G.709]. This 66b block stream is referred to as a FlexE sub-group signal which includes n available calendar slots with $n = n_1 + n_2 + \dots + n_p$ . $n_i$ (i = 1..p) represents the number of FlexE calendar slots that are available (to be transferred). + +**Replacement signal generator:** The function shall provide for a FlexE sub-group replacement signal that generates a stream of local fault sequence ordered sets as specified in clause 17.12 of [ITU-T G.709]. + +**Selector:** The function shall select between the interleaved FlexE sub-group signal and the replacement signal. During a signal fail condition of an incoming FlexESGM signal, it shall select the replacement signal to be mapped into the OPUflex payload as described in clause 17.12 of [ITU-T G.709]. + +**Scrambler:** The function shall scramble the 66b block stream before mapping into the OPUflex as described in clause 17.12 of [ITU-T G.709]. + +**Mapping, frequency justification and bit-rate adaptation:** The function shall provide an elastic store (buffer) process. The scrambled data signal shall be written into the buffer under the control of the associated input clock. The scrambled data shall be read out of the buffer and then be written onto the OPUflex payload under the control of BGMP as defined in clause 17.12 of [ITU-T G.709]. + +*Buffer size:* In the presence of jitter, this mapping process shall not introduce any errors. + +**JC:** The function shall insert the justification control information in the JC bytes (the Cm value and the calculated CRC-8 value), as defined in clause 17.12 of [ITU-T G.709]. + +**PT:** The function shall insert the payload type code "0001 1101" (0x1E) into the PT byte position of the PSI overhead, as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**PSI[3..3+p]:** The function shall insert the values of p, $n_1$ to $n_p$ in the PSI[3] to PSI[3+p] fields, as defined in clause 17.12 of [ITU-T G.709]. + +**Client signal fail:** The function shall signal the failure of the client signal to the far end by use of the Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +**RES:** The function shall insert all-ZEROs into the RES bytes. + +All other bits of the ODUflex overhead should be sourced as "0"s, except the ODUflex-PM STAT field which should be set to the value "normal path signal" (001). + +![Figure 14-100 – ODUflexP/FlexESG_A_So function block diagram. The diagram shows the internal processing of the ODUflexP/FlexESG_A_So function. On the left, multiple FlexESGM_CP inputs (CI_D, CI_CK, CI_FS, CI_MFS, CI_SSF, CI_CRCerr) are processed through 'Extract GID', 'Extract IID', 'Extract MAP', and 'Extract sub-calendar' blocks to produce AcGID, AcIID, AcFMAP, AcCC, AcCCA, and AcCCB signals. These are followed by a 'FlexESG deskew' block. Below that, 'Crunching' and 'Padding' blocks process the signals. A 'Clock generator' provides CK, FS, and MFS signals. The data then goes through 'Interleaving', a 'Selector' (controlled by aAIS), and a 'Scrambler'. The scrambled data is stored in an 'Elastic store' (with WR and RD ports) controlled by a 'Justification control (BGMP)'. The BGMP also controls 'Insert PSI[3..3+p]', 'Insert PT', 'Insert CSF', and 'Insert RES' blocks. A block 'ODU OH is set to all-0's, except PM STAT = 001' is also present. The final output is ODUflexP_AP (AI_D, AI_CK, AI_FS, AI_MFS). On the right, various detection blocks (dGIDM, dFMM, dCSUM) process the signals to generate MI_ExGID, MI_ExFMAP, MI_CS_n[1..p], MI_AcGID[1..p], MI_AcIID[1..p], MI_AcFMAP[1..p], MI_AcCC[1..p], MI_AcCCA[1..p], MI_AcCCB[1..p], MI_cLOL, MI_cFMM, MI_cGIDM, and MI_cCSUM signals. These are then processed by a 'Defect correlations' block and a 'Consequent actions' block. The vertical label on the far right is ODUflexP/FlexESG_A_So_MP. The bottom right corner has the text G.798(17)-Amd.4(22)_F14-100.](32ce3ed5531f18aba05215c8f474bf49_img.jpg) + +Figure 14-100 – ODUflexP/FlexESG\_A\_So function block diagram. The diagram shows the internal processing of the ODUflexP/FlexESG\_A\_So function. On the left, multiple FlexESGM\_CP inputs (CI\_D, CI\_CK, CI\_FS, CI\_MFS, CI\_SSF, CI\_CRCerr) are processed through 'Extract GID', 'Extract IID', 'Extract MAP', and 'Extract sub-calendar' blocks to produce AcGID, AcIID, AcFMAP, AcCC, AcCCA, and AcCCB signals. These are followed by a 'FlexESG deskew' block. Below that, 'Crunching' and 'Padding' blocks process the signals. A 'Clock generator' provides CK, FS, and MFS signals. The data then goes through 'Interleaving', a 'Selector' (controlled by aAIS), and a 'Scrambler'. The scrambled data is stored in an 'Elastic store' (with WR and RD ports) controlled by a 'Justification control (BGMP)'. The BGMP also controls 'Insert PSI[3..3+p]', 'Insert PT', 'Insert CSF', and 'Insert RES' blocks. A block 'ODU OH is set to all-0's, except PM STAT = 001' is also present. The final output is ODUflexP\_AP (AI\_D, AI\_CK, AI\_FS, AI\_MFS). On the right, various detection blocks (dGIDM, dFMM, dCSUM) process the signals to generate MI\_ExGID, MI\_ExFMAP, MI\_CS\_n[1..p], MI\_AcGID[1..p], MI\_AcIID[1..p], MI\_AcFMAP[1..p], MI\_AcCC[1..p], MI\_AcCCA[1..p], MI\_AcCCB[1..p], MI\_cLOL, MI\_cFMM, MI\_cGIDM, and MI\_cCSUM signals. These are then processed by a 'Defect correlations' block and a 'Consequent actions' block. The vertical label on the far right is ODUflexP/FlexESG\_A\_So\_MP. The bottom right corner has the text G.798(17)-Amd.4(22)\_F14-100. + +Figure 14-100 – ODUflexP/FlexESG\_A\_So function + +**Defects:** The function shall detect dFMM, dGIDM, dLOL and dCSUM. + +**dGIDM:** See clause B.1.1.2.1. dGIDM shall be set to false during $\sum CI\_TSF[i]$ . + +**dFMM:** See clause B.1.1.2.2. dFMM shall be set to false during $\sum CI\_TSF[i]$ or dGIDM. + +**dLOL:** If the alignment process, i.e., the FlexESG deskew process, is in the out-of-alignment state, dLOL shall be set to true. dLOL shall be set to false when the alignment process is in the in-multilane-alignment state; dLOL shall be set to false during CI\_SSF or dGIDM or dFMM. + +**dCSUM:** The calendar slot unavailability mismatch defect dCSUM is set "1" if one or more of the calendar slots listed as unavailable in MI\_CS\_n[1..p] are not carrying the value 0xFFFF (i.e., unavailable) within the active accepted Client Calendar overhead in the FlexE (sub)group. Otherwise, dCSUM is set "0". dCSUM shall be set to false during CI\_SSF or dLOL or dGIDM or dFMM. + +dCSUM shall be detected within 100 ms of changes to the active accepted calendar configuration (AcCCA or AcCCB) or the MI\_CS\_n[1..p]. + +**Consequent actions:** + +aAIS $\leftarrow$ dCSUM or dLOL or dFMM or dGIDM or $\sum$ CI\_SSF[i] + +**Defect correlations:** + +cGIDM $\leftarrow$ dGIDM and (not CI\_SSF) + +cFMM $\leftarrow$ dFMM and (not dGIDM) and (not CI\_SSF) + +cLOL $\leftarrow$ dLOL and (not dFMM) and (not dGIDM) and (not CI\_SSF) + +cCSUM $\leftarrow$ dCSUM and (not dLOL) and (not dFMM) and (not dGIDM) and (not CI\_SSF) + +**Performance monitoring:** None. + +**14.3.18.2 ODUflexP to FlexE sub-group adaptation sink function using BGMP (ODUflexP/FlexESG\_A\_Sk)** + +The ODUflexP/FlexESG\_A\_Sk recovers the FlexE partial rate (sub)group signal from the OPUflex payload using the justification control of BGMP. It extracts the OPUflex overhead (PT, CSF, PSI and JC) and monitors the reception of the correct overhead. Under signal fail condition, a replacement signal as specified in clause 17.12 of [ITU-T G.709] shall be inserted. + +The information flow and processing of the ODUflexP/FlexESG\_A\_Sk function is defined with reference to Figures 14-101 and 14-102. + +**Symbol** + +![Diagram of the ODUflexP/FlexESG_A_Sk function symbol. A central trapezoidal block is labeled 'ODUflexP/FlexESG'. An input arrow labeled 'ODUflexP_AP' points into the bottom of the block. An output arrow labeled 'ODUflexP/FlexESG_A_Sk_MP' points out from the left side of the block. Multiple output arrows labeled '1', '2', '...', and 'p' point out from the top of the block. Above these arrows is the label 'FlexESGM_CPs'. Below the diagram is the text 'G.798(17)-Amd.4(22)_F14-F101'.](491e41fb7612d41cb9c24448ce144eda_img.jpg) + +Diagram of the ODUflexP/FlexESG\_A\_Sk function symbol. A central trapezoidal block is labeled 'ODUflexP/FlexESG'. An input arrow labeled 'ODUflexP\_AP' points into the bottom of the block. An output arrow labeled 'ODUflexP/FlexESG\_A\_Sk\_MP' points out from the left side of the block. Multiple output arrows labeled '1', '2', '...', and 'p' point out from the top of the block. Above these arrows is the label 'FlexESGM\_CPs'. Below the diagram is the text 'G.798(17)-Amd.4(22)\_F14-F101'. + +**Figure 14-101 – ODUflexP/FlexESG\_A\_Sk function** + +## Interfaces + +**Table 14-47 – ODUflexP/FlexESG\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUflexP_AP:
ODUflexP_AI_CK
ODUflexP_AI_D
ODUflexP_AI_FS
ODUflexP_AI_MFS
ODUflexP_AI_TSF
ODUflexP/FlexESG_A_Sk_MP:
ODUflexP/FlexESG_A_Sk_MI_CS_n[1..p] | p × FlexESGM_CP:
FlexESGM_CI_CK
FlexESGM_CI_D
FlexESGM_CI_FS
FlexESGM_CI_MFS
FlexESGM_CI_SSF
ODUflexP/FlexESG_A_Sk_MP:
ODUflexP/FlexESG_A_Sk_MI_AcPT
ODUflexP/FlexESG_A_Sk_MI_cPLM
ODUflexP/FlexESG_A_Sk_MI_cCSF
ODUflexP/FlexESG_A_Sk_MI_cCSACM
ODUflexP/FlexESG_A_Sk_MI_cLCS
ODUflexP/FlexESG_A_Sk_MI_cLOF
ODUflexP/FlexESG_A_Sk_MI_cLOM | + +## Processes + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. + +**PSI[3..3+p]:** The function shall extract the PSI[3] to PSI[3+p] bytes from the PSI overhead as defined in clause 17.12 of [ITU-T G.709] and compare the p, n1 to np values in these bytes with the configured values MI\_CS\_n[1..p]. + +**Client signal fail:** The function shall extract the CSF signal indicating the failure of the client signal out of Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +**JC:** The function shall interpret the justification control information in the JC bytes and get the corresponding Cm value (948 or 949), as defined in clause 17.12 of [ITU-T G.709]. + +**Demapping, rate adaptation and FlexESG clock generation:** The function shall provide an elastic store (buffer) process. The data shall be demapped from the payload bytes in the OPUflex frames and then be written into the buffer. The information extraction of the payload area shall be under the control of BGMP with the extracted Cm value. The FlexESG signal data shall be read out of the buffer under the control of the recovered FlexESG clock. + +*Smoothing and jitter limiting process:* The function shall provide for a clock smoothing and elastic store (buffer) process. The data signal shall be written into the buffer under the control of the associated (gapped) input clock. The data signal shall be read out of the buffer under the control of a smoothed (equally spaced) clock at a rate and frequency accuracy determined by the client signal rate at the input of the remote ODUflexP/FlexESG\_A\_So. + +*FlexESG clock generation:* The function shall provide for a FlexESG clock generation process which generates a clock with a FlexESG signal bit rate ( $100\text{GE\_bit\_rate} \times n/20 \text{ kbit/s} \pm 100 \text{ ppm}$ ) as specified in clause 17.12 of [ITU-T G.709] based on the input clock AI\_CK. + +*Buffer size:* In the presence of bit rate differences between OPUflex and FlexE partial rate (sug)group signals, this demapping process shall not introduce any errors. + +**Block Synchronization:** See clause 8.2.7.1 for mapping procedures preserving the 2-bit alignment. + +**Descrambler:** The function shall descramble the 66b block stream from the payload bytes in the OPUflex frames as described in clause 17.12 of [ITU-T G.709]. + +**FlexESG Frame alignment:** The function shall recover the interleaved FlexE sub-group frame start by searching for the $p$ instances of the FlexE overhead block 1 in the FlexESG frame every $1024 \times n \times 8$ blocks as described in clause 17.12 of [ITU-T G.709]. The number of calendar slots interleaved into FlexESG signal $n$ equals the sum $\sum n_i$ where $n_i$ represents the number of calendar slots in the $i^{th}$ FlexE member that are to be transferred. + +NOTE – The FlexE block 1 is encoded as a special ordered set. The sync header is 10, the control block type is 0x4B (ordered set), and the "O" code is 0x5. + +The process has two states, out-of-frame (OOF) and in-frame (IF). The frame alignment start shall be maintained during the OOF state. + +In the OOF state, the frame alignment shall be assumed to be recovered and the IF state shall be entered, when $p$ consecutive valid FlexE blocks 1 are found in two consecutive FlexESG overhead frames. + +In the IF state, OOF shall be entered when the $p$ consecutive FlexE blocks 1 of the FlexESG overhead frame has mismatches on the sync header, control block type or O code fields for 5 occurrences. + +**FlexE Multi-frame alignment:** The function shall recover the common multi-frame start of the $p$ FlexESGM signals by performing multi-frame alignment on the first instance of the FlexE overhead block 1 in the FlexE sub-group frame. See clause B.2.1.2. + +**De-interleaving:** The function shall de-interleave the $p$ FlexESGM signals from the interleaved FlexESG group signal as described in clause 17.12 of [ITU-T G.709]. + +**Depadding:** The function shall delete the $n_i-1$ padding blocks inserted between the overhead block and the first sub-calendar block in the $i^{th}$ FlexESGM signal as described in clause 17.12 of [ITU-T G.709]. + +**FlexE clock generation:** The function shall provide for a FlexESGM clock generation process which generates a clock with a bit rate $(100GE\_rate \times (16k-1)/16k)$ as specified in clause 6.2 of [OIF Flex IA] based on the recovered FlexESG clock "CLK" or the input clock AI\_CK. + +**Decrunching:** The function shall identify the removed unavailable calendar slots and insert them into the $p$ FlexESGM signals as described in clause 17.12 of [ITU-T G.709]. + +**FlexE replacement signal generation:** The function shall provide for a FlexESGM replacement signal and clock generation process that generates a stream of local fault sequence ordered sets as specified in clause 17.12 of [ITU-T G.709]. + +**Selector:** The function shall select the FlexESGM signal or the replacement signal. During a signal fail condition of the incoming ODUflex/OPUflex signal or a CSF condition is present in the OPUflex overhead, it shall select the replacement signal as described in clause 17.12 of [ITU-T G.709]. + +![Block diagram of ODUflexP/FlexESG_A_Sk processes showing signal flow from input (AI_D, AI_CK, AI_FS, AI_MFS, AI_TSF) through various processing stages (Extract JC, Extract PSI, Extract CSF, Extract PT, Elastic store, Block synchronization, Descrambler, FlexESG frame alignment, FlexESG multi-frame alignment, De-interleaving, Depadding, Decrunching, Selector) to output (FlexESGM_CP[1] to FlexESGM_CP[p]).](28583b06f211df822423d245dfad776f_img.jpg) + +The diagram illustrates the ODUflexP/FlexESG\_A\_Sk processes. At the bottom, input signals AI\_D, AI\_CK, AI\_FS, AI\_MFS, and AI\_TSF enter the system. AI\_D, AI\_CK, AI\_FS, and AI\_MFS are processed through 'Extract JC', 'Extract PSI[3..3+p]', 'Extract CSF', and 'Extract PT' blocks. 'Extract JC' feeds into 'Justification control'. 'Extract PSI[3..3+p]' feeds into 'CSACM process'. 'Extract CSF' outputs dCSF. 'Extract PT' feeds into 'PT process'. 'Justification control' feeds into 'Elastic store'. 'Elastic store' has 'WR' (write) and 'RD' (read) ports. 'WR' feeds into 'FlexESG clock generator (BGMP)'. 'RD' feeds into 'Block synchronization'. 'FlexESG clock generator (BGMP)' also receives AI\_CK and AI\_FS. 'Block synchronization' outputs dLCS and CK. 'Block synchronization' feeds into 'Descrambler'. 'Descrambler' outputs D, CK, and BS. 'Descrambler' feeds into 'FlexESG frame alignment'. 'FlexESG frame alignment' outputs D, CK, and BS. 'FlexESG frame alignment' feeds into 'FlexESG multi-frame alignment'. 'FlexESG multi-frame alignment' outputs D, CK, FS, and MFS. 'FlexESG multi-frame alignment' feeds into 'De-interleaving'. 'De-interleaving' feeds into 'Depadding' blocks. 'Depadding' blocks feed into 'Decrunching' blocks. 'Decrunching' blocks feed into a 'Selector'. A 'Replacement signal generator' and 'FlexESGM clock generator' also feed into the 'Selector'. The 'Selector' outputs FlexESGM\_CP[1] to FlexESGM\_CP[p]. On the right side, 'Consequent actions' and 'Defect correlations' blocks receive various signals (dLOM, dLOF, dCSACM, dLCS, dPLM, dCSF, AI\_TSF) and output MI signals: MI\_cLOM, MI\_cLOF, MI\_cCSACM, MI\_cLCS, MI\_cPLM, MI\_cCSF, and MI\_AcPT. The diagram is labeled G.798(17)-Amd.4(22)\_F14-102 and ODUflexP/FlexESG\_A\_Sk\_MP. + +Block diagram of ODUflexP/FlexESG\_A\_Sk processes showing signal flow from input (AI\_D, AI\_CK, AI\_FS, AI\_MFS, AI\_TSF) through various processing stages (Extract JC, Extract PSI, Extract CSF, Extract PT, Elastic store, Block synchronization, Descrambler, FlexESG frame alignment, FlexESG multi-frame alignment, De-interleaving, Depadding, Decrunching, Selector) to output (FlexESGM\_CP[1] to FlexESGM\_CP[p]). + +Figure 14-102 – ODUflexP/FlexESG\_A\_Sk processes + +## Defects + +The function shall detect dPLM, dCSF, dCSACM, dLCS, dLOF and dLOM. + +**dPLM:** See clause 6.2.4.1. The expected payload type is "0001 1110" as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**dCSF:** See clause 6.2.10. + +**dCSACM:** The calendar slot availability count mismatch defect dCSACM is set "1" if the extracted $p$ , $n_1$ to $n_p$ values from the PSI[3] to PSI[3+p] bytes are different from the configured values MI\_CS\_n[1..p]. Otherwise, dCSACM is set "0". + +dCSACM shall be detected within 100 ms of changes to the accepted PSI[3..3+p] or the MI\_CS\_n[1..p] values. + +**dLCS:** See clause 6.2.5.7.1. + +**dLOF:** The loss of the interleaved FlexESG frame defect dLOF is generated based on the state of the FlexESG frame alignment process. If the FlexESG frame alignment process is in the out-of-frame (OOF) state for 3 ms, dLOF shall be declared. To provide for the case of intermittent OOFs, the integrating timer shall not be reset to zero until an in-frame (IF) condition persists continuously for 3 ms. dLOF shall be cleared when the IF state persists continuously for 3 ms. + +**dLOM:** The loss of the interleaved FlexESG multi-frame defect dLOM is generated based on the state of the FlexESG multi-frame alignment process. See clause B.1.1.1.2. + +## Consequent actions + +aSSF $\leftarrow$ AI\_TSF or dPLM or dCSF or dLCS or dLOF or dLOM + +aAIS $\leftarrow$ AI\_TSF or dPLM or dCSF or dLCS or dLOF or dLOM + +For FlexE partial rate (sub)group signal, on declaration of aAIS, the function shall output the FlexESGM replacement signal within X ms. On clearing aAIS, the replacement signal shall be removed within Y ms and normal data being output. The values for X and Y are for further study. The replacement signal clock has to be within the frequency, jitter, and wander tolerance specifications of the FlexE signal. + +## Defect correlations + +cPLM $\leftarrow$ dPLM and (not AI\_TSF) + +cCSF $\leftarrow$ dCSF and (not dPLM) and (not AI\_TSF) + +cCSACM $\leftarrow$ dCSACM and (not dCSF) and (not dPLM) and (not AI\_TSF) + +cLCS $\leftarrow$ dLCS and (not dCSACM) and (not dCSF) and (not dPLM) and (not AI\_TSF) + +cLOF $\leftarrow$ dLOF and (not dLCS) and (not dCSACM) and (not dCSF) and (not dPLM) and (not AI\_TSF) + +cLOM $\leftarrow$ dLOM and (not dLOF) and (not dLCS) and (not dCSACM) and (not dCSF) and (not dPLM) and (not AI\_TSF) + +**Performance monitoring:** None. + +### 14.3.19 ODUkP to MPLS-TP adaptation functions (ODUkP/MT\_A; $k = 0, 1, 2, 3, 4, \text{flex}$ ) + +ODUkP to MPLS-TP adaptation using GFP mapping is given in clause 11.2.1 of [ITU-T G.8121]. + +### 14.3.20 ODUFlexP to ETCy adaptation function using BMP (ODUFlexP/ETCy\_A) + +The ODUFlexP/ETCy\_A performs the adaptation between the ODUFlexP layer adapted information and the characteristic information of the indicated ETCy client signals transported as constant bit-rate streams. + +Parameter 'y' denotes the different ETCy signal and the values of 'y' are given in Table 14-47.1. + +**Table 14-47.1 – Defined values for y for ETCy clients** + +| ETCy | Characteristic information | Bit rate | +|----------|--------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| ETC25GR | Stream of scrambled 64b/66b codewords of the 25GBASE-R PCS, as defined in clauses 49 and 107 of [IEEE 802.3] | $25\ 781\ 250\ \text{kbit/s} \pm 100\ \text{ppm}$ | +| ETC50GR | Stream of scrambled 64b/66b codewords of the 50GBASE-R PCS, as defined in clauses 82 and 133 of [IEEE 802.3] | $51\ 562\ 500\ \text{kbit/s} \pm 100\ \text{ppm}$ | +| ETC200GR | Stream of unscrambled 64b/66b codewords of the 200GBASE-R PCS, as defined in clause 119 of [IEEE 802.3] | $206\ 250\ 000 \times \frac{20479}{20480}\ \text{kbit/s} \pm 100\ \text{ppm}$ | +| ETC400GR | Stream of unscrambled 64b/66b codewords of the 400GBASE-R PCS, as defined in clause 119 of [IEEE 802.3] | $412\ 500\ 000 \times \frac{20479}{20480}\ \text{kbit/s} \pm 100\ \text{ppm}$ | + +The ODUFlexP/ETCy\_A source function always provides BMP mapping. + +#### 14.3.20.1 ODUFlexP to ETCy adaptation source function using BMP (ODUFlexP/ETCy\_A\_So) + +The ODUFlexP/ETCy\_A\_So function creates the ODUFlex signal from ETCy client clock or a local clock. It maps the constant bit-rate client signal from the ETCy\_CP into the payload area of the OPUflex using BMP as defined in clause 17.13 of [ITU-T G.709], and adds OPUflex overhead (PT, CSF and RES) and default ODUFlex overhead. + +The information flow of the ODUFlexP/ETCy\_A\_So function is defined with reference to Figure 14-102.1 and the processing of the ODUFlexP/ETCy\_A\_So function is defined with reference to Figure 14-102.2. + +##### Symbol + +![Diagram of the ODUFlexP/ETCy_A_So function symbol. It shows an input 'ETCy_CP' entering a trapezoidal block labeled 'ODUFlexP/ETCy', which outputs 'ODUFlexP_AP'. Below the diagram is the reference code 'G.798(17)-Amd.1(18)_F14-102.1'.](f96a0911100a9ea2097d9d2e88a9ca3e_img.jpg) + +``` + +graph TD + ETCy_CP[ETCy_CP] --> ODUFlexP_ETCy[ODUFlexP/ETCy] + ODUFlexP_ETCy --> ODUFlexP_AP[ODUFlexP_AP] + +``` + +G.798(17)-Amd.1(18)\_F14-102.1 + +Diagram of the ODUFlexP/ETCy\_A\_So function symbol. It shows an input 'ETCy\_CP' entering a trapezoidal block labeled 'ODUFlexP/ETCy', which outputs 'ODUFlexP\_AP'. Below the diagram is the reference code 'G.798(17)-Amd.1(18)\_F14-102.1'. + +**Figure 14-102.1 – ODUFlexP/ETCy\_A\_So function** + +## Interfaces + +**Table 14-47.2 – ODUflexP/ETCy\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| +| ETCy_CP:
ETCy_CI_CK
ETCy_CI_D
ETCy_CI_AM_SF[2:0] (Note)
ETCy_CI_FEC_DEG (Note)
ETCy_CI_SSF | ODUflexP_AP:
ODUflexP_AI_CK
ODUflexP_AI_D
ODUflexP_AI_FS
ODUflexP_AI_MFS | +| NOTE – The input signal is only used in the case of ETC200GR and ETC400GR supported by a single optical link in OTN. | | + +## Processes + +**Clock generation:** The function shall generate a local ODUflex clock (ODUflexP\_AI\_CK) by multiplying the incoming ETCy clock (CI\_CK) by a factor of 239/238. The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCb clock), apply. + +**FS & MFS generation:** The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUflex signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +**Rate compensation:** The function shall include a rate compensation process as specified hereafter: + +- For ETC25GR and ETC50GR, the process shall transparently pass the 64b/66b code blocks at its input to the output. +- For ETC200GR, the process shall compensate the incoming signal by inserting 16 rate compensation (RC) blocks every $(16 \times 20479)$ valid 64b/66b blocks as described in clause 17.3.2 of [ITU-T G.709]. The resulting nominal bit-rate of the rate compensated 64b/66b block stream is $206\,250\,000\text{ kbit/s} \pm 100\text{ ppm}$ . +- For ETC400GR, the process shall compensate the incoming signal by inserting 32 rate compensation (RC) blocks every $(32 \times 20479)$ valid 64b/66b blocks as described in clause 17.3.2 of [ITU-T G.709]. The resulting nominal bit-rate of the rate compensated 64b/66b block stream is $412\,500\,000\text{ kbit/s} \pm 100\text{ ppm}$ . + +### Scrambler: + +- For ETC200GR and ETC400GR, the process shall scramble the rate compensated 64b/66b block stream as described in clause 17.3 of [ITU-T G.709] and in clause 119.2.4.3 of [IEEE 802.3]. +- For ETC25GR and ETC50GR, the process shall transparently pass the scrambled 64b/66b code blocks at its input to the output. + +**Mapping:** The function shall provide an elastic store (buffer) process. The data signal of the scrambled 64b/66b blocks shall be written into the buffer under the control of the associated input clock. The adjusted data signal of 64b/66b blocks shall be read out of the buffer and be written onto the OPUflex payload under the control of BMP as defined in clause 17.13 of [ITU-T G.709]. During writing onto the OPUflex payload, the 64b/66b blocks must begin at bit positions 1, 3, 5, or 7 of a byte in the OPUflex payload, keeping the 2-bit alignment of each 66b block through the mapping process. + +*Buffer size:* In the presence of bit rate differences between OPUflex and ETCy signals, this mapping process shall not introduce any errors. + +**PT:** The function shall insert the payload type code "0011 0000" (0x30 for ETC25GR), "0011 0011" (0x33 for ETC50GR), "0011 0001" (0x31 for ETC200GR) or "0011 0010" (0x32 for ETC400GR) into the PT byte position of the PSI overhead, as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**Client signal fail:** The function shall signal the failure of the client signal to the far end by use of the Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +**CDI:** The function shall insert 3-bit Client Defect Indication in the PSI overhead as defined in clause K.2 of [ITU-T G.709]. Bit 2 of the PSI[2] shall be set to the reserved status information. Bit 3 of the PSI[2] byte shall be set to the Local Degrade status information or'ed with the FEC degraded input. Bit 4 of the PSI[2] byte shall be set to the Remote Degrade status information. + +| | +|--------------------------------------------------------------------------------| +| Bit 2 of the PSI[2] $\leftarrow$ CDI[0] $\leftarrow$ CI_AM_SF[0] | +| Bit 3 of the PSI[2] $\leftarrow$ CDI[1] $\leftarrow$ CI_AM_SF[1] or CI_FEC_DEG | +| Bit 4 of the PSI[2] $\leftarrow$ CDI[2] $\leftarrow$ CI_AM_SF[2] | + +NOTE – This process is only supported in the case of such service carried over a single optical link (supported by one OTSiA trail) in the OTN. + +**RES:** The function shall insert all-ZEROs into the RES bytes and reserved bits within the JC bytes. + +All other bits of the ODUflex overhead should be sourced as "0"s, except the ODUflex-PM STAT field which should be set to the value "normal path signal" (001). + +![Block diagram of the ODUflexP/ETCy_A_So function. The diagram shows the signal flow from ET_Cy_CP inputs (CI_D, CI_CK, CI_AM_SF[2:0], CI_FEC_DEG, CI_SSF) through various processing blocks (Rate compensation, Scrambler, Elastic store, CDI, Insert PT, Insert CSF, Insert RES, ODU OH generation) to ODUflexP_AP outputs (AI_D, AI_CK, AI_FS, AI_MFS). An ODU clock generator locked to ET_Cy clock (ODCb) provides the CK signal. Frequency dividers (1/122368 and 1/256) generate FS and MFS signals from the CK signal.](381b701baf194171a242aa2b1741f4a9_img.jpg) + +``` + +graph TD + subgraph ETCy_CP + CI_D + CI_CK + CI_AM_SF_top[CI_AM_SF[2:0]] + CI_FEC_DEG_top[CI_FEC_DEG] + CI_SSF_top[CI_SSF] + end + + CI_D --> RC[Rate compensation] + CI_CK --> RC + RC --> Scrambler + Scrambler --> ES[Elastic store WR/RD] + + CI_CK --> ODCb[ODU clock generator locked to ETCy clock ODCb] + ODCb --> CK_bus[CK] + CK_bus --> ES + CK_bus --> Div1[1/122368] + Div1 --> FS_bus[FS] + FS_bus --> ES + FS_bus --> Div2[1/256] + Div2 --> MFS_bus[MFS] + + ES --> CDI + CI_AM_SF_top --> CDI + CI_FEC_DEG_top --> CDI + + CDI --> IPT[Insert PT] + IPT --> ICSF[Insert CSF] + CI_SSF_top --> ICSF + ICSF --> IRES[Insert RES] + IRES --> ODUOH[ODU OH is set to all-0s, except PM STAT = 001] + + ODUOH --> AI_D + CK_bus --> AI_CK + FS_bus --> AI_FS + MFS_bus --> AI_MFS + + subgraph ODUflexP_AP + AI_D + AI_CK + AI_FS + AI_MFS + end + +``` + +The diagram illustrates the ODUflexP/ETCy\_A\_So function. At the top, the **ETCy\_CP** section provides inputs: **CI\_D** and **CI\_CK** to a **Rate compensation** block, which then feeds into a **Scrambler**. The **Scrambler** output goes to an **Elastic store** block with **WR** (write) and **RD** (read) ports. The **Elastic store** output is connected to a vertical bus. On this bus, from top to bottom, are blocks for **CDI** (receiving **CI\_AM\_SF[2:0]** and **CI\_FEC\_DEG**), **Insert PT**, **Insert CSF** (receiving **CI\_SSF**), **Insert RES**, and a block stating **ODU OH is set to all-0's, except PM STAT = 001**. The bus then splits into four outputs at the bottom: **AI\_D**, **AI\_CK**, **AI\_FS**, and **AI\_MFS**. A separate path from **CI\_CK** goes to an **ODU clock generator locked to ETCy clock (ODCb)**, which outputs **CK**. This **CK** signal is divided by $\frac{1}{122368}$ to produce **FS**, which is further divided by $\frac{1}{256}$ to produce **MFS**. The **ODUflexP\_AP** label is at the bottom center, and the reference code **G.798(17)-Amd.1(18)\_F14-102.2** is at the bottom right. + +Block diagram of the ODUflexP/ETCy\_A\_So function. The diagram shows the signal flow from ET\_Cy\_CP inputs (CI\_D, CI\_CK, CI\_AM\_SF[2:0], CI\_FEC\_DEG, CI\_SSF) through various processing blocks (Rate compensation, Scrambler, Elastic store, CDI, Insert PT, Insert CSF, Insert RES, ODU OH generation) to ODUflexP\_AP outputs (AI\_D, AI\_CK, AI\_FS, AI\_MFS). An ODU clock generator locked to ET\_Cy clock (ODCb) provides the CK signal. Frequency dividers (1/122368 and 1/256) generate FS and MFS signals from the CK signal. + +**Figure 14-102.2 – ODUflexP/ETCy\_A\_So function** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.3.20.2 ODUflexP to ETCy adaptation sink function using BMP (ODUflexP/ETCy\_A\_Sk) + +The ODUflexP/ETCy\_A\_Sk recovers the ETCy client signal from the OPUflex payload using the justification control of BMP. It extracts the OPUflex overhead (PT and CSF) and monitors the reception of the correct payload type. Under signal fail condition, a replacement signal as specified in clause 17.13 of [ITU-T G.709] shall be inserted. + +The information flow and processing of the ODUflexP/ETCy\_A\_Sk function is defined with reference to Figures 14-102.3 and 14-102.4. + +## Symbol + +![Symbol diagram for ODUflexP/ETCy_A_Sk function. A trapezoidal block labeled 'ODUflexP/ETCy' has an input arrow from the bottom labeled 'ODUflexP_AP'. It has an output arrow pointing up labeled 'ETCy_CP'. It also has a bidirectional arrow on the right labeled 'ODUflexP/ETCy_A_Sk_MP'.](9704c16b28b4ab44f3edc6e729b9a8b4_img.jpg) + +Symbol diagram for ODUflexP/ETCy\_A\_Sk function. A trapezoidal block labeled 'ODUflexP/ETCy' has an input arrow from the bottom labeled 'ODUflexP\_AP'. It has an output arrow pointing up labeled 'ETCy\_CP'. It also has a bidirectional arrow on the right labeled 'ODUflexP/ETCy\_A\_Sk\_MP'. + +G.798(17)-Amd.1(18)\_F14-102.3 + +**Figure 14-102.3 – ODUflexP/ETCy\_A\_Sk function** + +## Interfaces + +**Table 14-47.3 – ODUflexP/ETCy\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUflexP_AP:
ODUflexP_AI_CK
ODUflexP_AI_D
ODUflexP_AI_FS
ODUflexP_AI_MFS
ODUflexP_AI_TSF
ODUflexP_AI_FEC_DEG (Note) | ETCy_CP:
ETCy_CI_CK
ETCy_CI_D
ETCy_CI_AM_SF[2:0] (Note)
ETCy_CI_SSF
ODUflexP/ETCy_A_Sk_MP:
ODUflexP/ETCy_A_Sk_MI_cPLM
ODUflexP/ETCy_A_Sk_MI_AcPT
ODUflexP/ETCy_A_Sk_MI_cCSF
ODUflexP/ETCy_A_Sk_MI_cLCS
ODUflexP/ETCy_A_Sk_MI_cLRC | + +NOTE – AI\_FEC\_DEG and CI\_AM\_SF signal are only used in the case of ETC200GR and ETC400GR supported by a single optical link in OTN. + +## Processes + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. + +**Client signal fail:** The function shall extract the CSF signal indicating the failure of the client signal out of Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +**CDI:** The function shall extract 3-bit Client Defect Indication information from the PSI overhead as defined in clause K.2 of [ITU-T G.709]. A new AcCDI value is accepted if a new consistent 3-bit value is received in the CDI field (bits 2, 3 and 4) of the OPU PSI[2] overhead byte in 5 consecutive frames. + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $CI\_AM\_SF[0] \leftarrow AcCDI[0] \text{ and (not aAIS)}$ $CI\_AM\_SF[1] \leftarrow AcCDI[1] \text{ or AI\_FEC\_DEG or aAIS}$ $CI\_AM\_SF[2] \leftarrow AcCDI[2] \text{ and (not aAIS)}$ | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE – This process is only supported in the case of such service carried over a single optical link (supported by one OTSiA trail) in the OTN. + +**Demapping and ETcy clock generation:** The function shall provide an elastic store (buffer) process. The data shall be demapped from the payload bytes in the OPUflex frames and then be written into the buffer. The information extraction of the payload area shall be under the control of BMP. The signal data shall be read out of the buffer under the control of the recovered ETcy clock. + +**Smoothing and jitter limiting process:** The function shall provide for a clock smoothing and elastic store (buffer) process. The data signal shall be written into the buffer under the control of the associated (gapped) input clock. The data signal shall be read out of the buffer under the control of a smoothed (equally spaced) clock at a rate and frequency accuracy determined by the client signal rate at the input of the remote ODUflexP/ETcy\_A\_So. + +**ETcy clock generation:** The function shall provide for an ETcy clock generation process which generates a clock with an ETcy signal bit rate (e.g., $25\,781\,250\text{ kbit/s} \pm 100\text{ ppm}$ for ETC25GR, $51\,562\,500\text{ kbit/s} \pm 100\text{ ppm}$ for ETC50GR, $206\,250\,000\text{ kbit/s} \pm 100\text{ ppm}$ for ETC200GR and $412\,500\,000\text{ kbit/s} \pm 100\text{ ppm}$ for ETC400GR) as specified in clause 17.13 of [ITU-T G.709] based on the input clock AI\_CK. + +**Buffer size:** In the presence of bit rate differences between OPUflex and ETcy signals, this demapping process shall not introduce any errors. + +**Block Synchronization:** The function shall recover the 66b block through the 66b block synchronization lock state machine as described in Figure 82-12 of [IEEE 802.3]. The lock process looks for 64 consecutive valid sync headers in the initial data stream to declare lock. A valid sync header is either a 01 or a 10. Once in lock, the lock process looks for 65 invalid sync headers within a 1024 sync window to declare out of lock. An invalid sync header is an 11 or 00. Due to the 66b blocks keep the 2-bit alignment with OPUflex payload boundary during the mapping process, so the slip step of the lock process may be optimized using 2-bit. + +**Descrambler:** + +- For ETC200GR and ETC400GR, the process shall descramble the 66b block stream as described in clause 17.13 of [ITU-T G.709] and in clause 119.2.5.6 of [IEEE 802.3]. +- For ETC25GR and ETC50GR, the process shall transparently pass the scrambled 64b/66b code blocks at its input to the output. + +**Rate compensation:** The function shall include a rate compensation process as specified hereafter: + +- For ETC25GR and ETC50GR signals, the process shall directly pass transparently the input 66b block stream to the output. +- For ETC200GR and ETC400GR signals, RC block alignment and RC block removal processes shall be performed as described in Figure 14-102.5. + +**RC block alignment:** The function shall locate the start of Z consecutive RC blocks as described in clause 17.13.2 of [ITU-T G.709]; $Z = 16$ for ETC200GR and $Z = 32$ for ETC400GR. The process has two states, out-of-alignment (OOA) and in-alignment (IA). In the OOA state, the RC block pattern searched for may be a subset of RC0 and RC1 blocks within the Z consecutive RC blocks, for example a 4-block subset including the RC0/RC1 transition. The IA state shall be entered if this subset is found and confirmed at the next expected position. In the IA state, the Z RC blocks shall be continuously checked at the presumed position for correct RC alignment. The RC pattern checked for shall be the RC0/RC0/RC1/RC1 pattern. The OOA state shall be entered if this subset is not found at the correct position in two or more consecutive periods. The RC block alignment shall be maintained during the OOA state. + +**RC block removal:** The function shall remove all RC blocks from the 64b/66b block stream as described in clause 17.3.2 of [ITU-T G.709]. + +**Replacement signal generation:** The function shall provide for an ETcy replacement signal and clock generation process that generates a stream of local fault sequence ordered sets as specified in clause 17.13 of [ITU-T G.709] with a bit rate as specified in Table 14-47.1. + +**Selector:** The function shall select the demapped ETcy signal or the replacement signal. During a signal fail condition of the incoming ODUflex/OPUflex signal or a CSF condition is present in the OPUflex overhead, it shall select the replacement signal as described in clause 17.13 of [ITU-T G.709]. + +![Block diagram of ODUflexP/ETCy_A_Sk processes showing signal flow from input AI_D to output CI_D through various processing blocks like Elastic store, Descrambler, Rate compensation, Selector, and Consequent actions.](47aaa88afec21e26eb33420078f4936a_img.jpg) + +The diagram illustrates the internal processes of the ODUflexP/ETCy\_A\_Sk function. It is divided into two main functional areas: ODUflexP and ETCy\_A\_Sk\_MP. + +- ODUflexP\_AP (Input Side):** Inputs include AI\_D, AI\_MFS, AI\_CK, AI\_FS, AI\_FEC\_DEG, and AI\_TSF. AI\_D and AI\_MFS are processed through 'Extract CDI', 'Extract CSF', and 'Extract PT' blocks. 'Extract CDI' outputs CDI and AI\_FEC\_DEG to the 'CDI process'. 'Extract CSF' outputs dCSF. 'Extract PT' outputs to the 'PT process', which also receives dPLM and outputs MI\_AcPT. AI\_CK and AI\_FS are inputs to the 'Elastic store' (with WR and RD ports) and the 'Clock generator (BMP)'. AI\_FEC\_DEG and AI\_TSF are inputs to the 'Consequent actions' block. +- ODUflexP/ETCy\_A\_Sk\_MP (Processing Side):** The 'Elastic store' outputs to a 'Block synchronization' block, which outputs dLCS. The 'Block synchronization' block also receives CK from the 'Clock generator (BMP)'. The signal then passes through a 'Descrambler' and a 'Rate compensation' block, which outputs dLRC. The 'Rate compensation' block also receives dLRC from the 'Replacement signal generator'. The signal then enters a 'Selector' block. The 'Selector' block also receives aAIS from the 'Consequent actions' block and outputs CI\_D and CI\_CK. The 'Consequent actions' block receives inputs from 'Defect correlations' (dLRC, dLCS, dCSF, dPLM, AI\_TSF) and outputs CI\_SSF and CI\_AM\_SF[2:0]. The 'Defect correlations' block also receives AM\_SF[2:0] from the 'CDI process' and outputs MI\_cLRC, MI\_cLCS, MI\_cCSF, and MI\_cPLM. The 'Clock generator (BMP)' outputs CK to the 'Elastic store' and 'Block synchronization' block. + +Block diagram of ODUflexP/ETCy\_A\_Sk processes showing signal flow from input AI\_D to output CI\_D through various processing blocks like Elastic store, Descrambler, Rate compensation, Selector, and Consequent actions. + +Figure 14-102.4 – ODUflexP/ETCy\_A\_Sk processes + +![Diagram of the rate compensation process for ETC200GR and ETC400GR. It shows two stacked blocks: 'RC block removal' on top and 'RC block alignment' on the bottom. Inputs D, BS, and CK enter the 'RC block alignment' block from below. An output labeled 'dLRC' exits the 'RC block alignment' block to the right. Arrows indicate signal flow between the blocks and the inputs/outputs. Below the diagram is the text 'G.798(17)-Amd.1(18)_F14-102.5'.](2b817d2912f95cb0ab93ff621a3f0a5b_img.jpg) + +Diagram of the rate compensation process for ETC200GR and ETC400GR. It shows two stacked blocks: 'RC block removal' on top and 'RC block alignment' on the bottom. Inputs D, BS, and CK enter the 'RC block alignment' block from below. An output labeled 'dLRC' exits the 'RC block alignment' block to the right. Arrows indicate signal flow between the blocks and the inputs/outputs. Below the diagram is the text 'G.798(17)-Amd.1(18)\_F14-102.5'. + +**Figure 14-102.5 – Rate compensation process for ETC200GR and ETC400GR** + +## Defects + +The function shall detect dPLM, dCSF, dLCS and dLRC. + +**dPLM:** See clause 6.2.4.1. The expected payload type is "0011 0000" (0x30 for ETC25GR), "0011 0011" (0x33 for ETC50GR), "0011 0001" (0x31 for ETC200GR) or "0011 0010" (0x32 for ETC400GR) as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**dCSF:** See clause 6.2.10. + +**dLCS:** See clause 6.2.5.7.1. + +**dLRC (loss of RC blocks):** The defect dLRC is generated based on the state of the RC block alignment process. If the process is in the out-of-alignment (OOA) state for 3 ms, dLRC shall be declared; dLRC shall be cleared when the IA state persists continuously for 3 ms. + +## Consequent actions + +aSSF $\leftarrow$ AI\_TSF or dPLM or dLCS or dLRC + +aAIS $\leftarrow$ AI\_TSF or dPLM or dLCS or dLRC + +For ETCy clients, on declaration of aAIS, the function shall output the ETCy replacement signal within X ms. On clearing aAIS, the replacement signal shall be removed within Y ms and normal data being output. The values for X and Y are for further study. + +## Defect correlations + +cPLM $\leftarrow$ dPLM and (not AI\_TSF) + +cCSF $\leftarrow$ dCSF and (not dPLM) and (not AI\_TSF) + +cLCS $\leftarrow$ dLCS and (not dPLM) and (not AI\_TSF) + +cLRC $\leftarrow$ dLRC and (not dLCS) and (not dPLM) and (not AI\_TSF) + +**Performance monitoring:** None. + +### **14.3.21 ODUkP to ETH client adaptation function using IMP (ODUkP/ETH-imp\_A; k = 0, 1, 2, 3, 4, flex)** + +The ODUkP/ETH-imp\_A performs the adaptation between the ODUkP layer adapted information and the characteristic information of the ETH client signal. + +### 14.3.21.1 ODUkP to ETH client adaptation source function using IMP (ODUkP/ETH-imp\_A\_So) + +The ODUkP/ETH-imp\_A\_So function creates the ODUk signal from a free running clock. It maps the ETH\_CI information into the payload area of the OPUk using IMP as defined in clause 17.11 of [ITU-T G.709], adds OPUk overhead (RES, PT) and default ODUk overhead. + +The information flow of the ODUkP/ETH-imp\_A\_So function is defined with reference to Figures 14-102.6 and 14-102.7. + +#### Symbol + +![Diagram of the ODUkP/ETH-imp_A_So function symbol. The central block is labeled 'ODUkP/ETH-imp'. Inputs from the top are ETH_TFP and ETH_FP. Inputs from the left are ODUkP/ETH-imp_A_So_MP (bidirectional), ETH_RP, and ETH_TP. The output at the bottom is ODUkP_AP. Outputs to the right are ETHTF_PP and ETHF_PP. A small label G.798(23)_F14-F102.6 is at the bottom right.](236b5a83f488c361479b9b44e462f978_img.jpg) + +Diagram of the ODUkP/ETH-imp\_A\_So function symbol. The central block is labeled 'ODUkP/ETH-imp'. Inputs from the top are ETH\_TFP and ETH\_FP. Inputs from the left are ODUkP/ETH-imp\_A\_So\_MP (bidirectional), ETH\_RP, and ETH\_TP. The output at the bottom is ODUkP\_AP. Outputs to the right are ETHTF\_PP and ETHF\_PP. A small label G.798(23)\_F14-F102.6 is at the bottom right. + +Figure 14-102.6 – ODUkP/ETH-imp\_A\_So function + +#### Interfaces + +Table 14-47.4 – ODUkP/ETH-imp\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------|------------------------------------| +| ETH_TFP: | ODUkP_AP: | +| ETH_CI_D | ODUkP_AI_CK | +| ETH_CI_P | ODUkP_AI_D | +| ETH_CI_DE | ODUkP_AI_FS | +| | ODUkP_AI_MFS | +| ETH_FP: | ETHTF_PP: | +| ETH_CI_D | ETH_PI_D | +| ETH_CI_P | ETH_PI_P | +| ETH_CI_DE | ETH_PI_DE | +| ETH_RP: | ETHF_PP: | +| ETH_RI | ETH_PI_D | +| ETH_TP: | ETH_PI_P | +| ETH_TI_CK | ETH_PI_DE | +| ODUkP/ETH-imp_A_So_MP: | ODUkP/ETH-imp_A_So_MP: | +| ODUkP/ETH-imp_A_So_MI_[IEEE 802.3] | ODUkP/ETH-imp_A_So_MI_[IEEE 802.3] | + +#### Processes + +The processes associated with the ODUkP/ETH-imp\_A\_So function are as depicted in Figure 14-102.7. + +The client-specific processes, and associated MI and PI signals, are defined in clause 9.5 of [ITU-T G.8021]. + +**[IEEE 802.3] processes:** The [IEEE 802.3] processes represent the whole functionality of the PHY above the PMA in the IEEE 802.3 model. This includes the reconciliation sublayer and the process of 64B/66B encoding, as well as MAC FCS generation and frame counting. + +NOTE – This Recommendation defines these processes by reference to [IEEE 802.3] and intentionally does not provide details, as this functionality is well understood from the IEEE work. + +**Clock generation:** The function shall generate an ODUk clock (ODUkP\_AI\_CK) – according to one of the methods described in clause 12.2.6 of [ITU-T G.709] – with a bit rate as specified in Table 7-2 of [ITU-T G.709]. The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (in case of methods 1 and 2 ODCa clock, in case of method 3 ODCb clock), apply. + +**FS & MFS generation:** The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the ODUk signal. The AI\_FS signal shall be active once per 122 368 clock cycles. AI\_MFS shall be active once every 256 frames. + +**Bit-rate adaptation, scrambler, mapping and frequency justification:** The function shall provide an elastic store (buffer) process. The data signal of 66b blocks shall be written into the buffer under the control of the associated input clock. The adjusted data signal of 66b blocks shall be read out of the buffer, scrambled and be written onto the OPUk payload under the control of IMP as defined in clause 17.11 of [ITU-T G.709]. The 66b blocks are aligned so that the first bit of the sync header appears in one of the bit positions 1, 3, 5, or 7 of a byte in the OPUk payload. + +*Scrambler:* The function shall scramble 66b block stream after rate adaptation and before mapping into the OPUk. + +*Rate adaptation:* The mapping process shall not insert or delete a 66b block between a Start (0x78) and Terminate (0x87/0x99/0xAA/0xB4/0xCC/0xD2/0xE1/0xFF) control block. + +**PT:** The function shall insert the payload type code "0001 1101" (0x1D) into the PT byte position of the PSI overhead, as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**Client signal fail:** The function shall signal the failure of the client signal to the far end by use of the Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +**RES:** The function shall insert all-ZEROs into the RES bytes and reserved bits within the JC bytes. + +All other bits of the ODUk overhead should be sourced as "0"s, except the ODUk-PM STAT field which should be set to the value "normal path signal" (001). + +![Figure 14-102.7 – ODUkP/ETH-imp_A_So function block diagram. The diagram shows the internal processing of an ODUkP/ETH-imp_A_So function. At the top, two inputs, ETH_CI (ETH_TP) and ETH_CI (ETH_TFP), enter a 'Client-specific processes' block. This block outputs two signals, ETH_PI (ETH_TF_PP) and ETH_PI (ETHF_PP), to the right. Below the client-specific processes is a yellow '[IEEE 802.3] processes' block, which is connected to an external 'MI_[IEEE 802.3]' interface on the left. This block receives two signals, ETH_RI and ETH_TI_CK, from the right. The output of the [IEEE 802.3] processes goes to a 'Rate adaptation' block, which then feeds into a 'Scrambler' block. The output of the scrambler goes to an 'Elastic store' block, which has 'WR' (write) and 'RD' (read) ports. The 'WR' port is connected to the 'Scrambler' and the 'RD' port is connected to a 'Justification control (IMP)' block. The 'IMP' block also receives 'CK' (clock) from a 'Clock generator' block. The 'Clock generator' is connected to a 'Free-running clock generator (ODCa)' block. The 'IMP' block outputs 'FS' (frame sync) to a '1/122368' divider block, which in turn outputs 'MFS' (multi-frame sync) to a '1/256' divider block. The 'Elastic store' block also outputs 'AI_D' (data) to the bottom. The 'IMP' block outputs 'AI_CK' (clock) to the bottom. The 'IMP' block also outputs 'CI_SSF' (client signal signal fail) to an 'Insert CSF' block. The 'Insert CSF' block outputs 'Insert PT' (payload type) to an 'Insert RES' (residual) block. The 'Insert RES' block outputs 'ODU OH is set to all-0's, except PM STAT = 001' to the bottom. The bottom outputs are labeled AI_D, AI_CK, AI_FS, and AI_MFS. The entire diagram is labeled ODUkP_AP and G.798(23)_F14-102.7.](b49ab452107df6572ea43e1be0912bd0_img.jpg) + +Figure 14-102.7 – ODUkP/ETH-imp\_A\_So function block diagram. The diagram shows the internal processing of an ODUkP/ETH-imp\_A\_So function. At the top, two inputs, ETH\_CI (ETH\_TP) and ETH\_CI (ETH\_TFP), enter a 'Client-specific processes' block. This block outputs two signals, ETH\_PI (ETH\_TF\_PP) and ETH\_PI (ETHF\_PP), to the right. Below the client-specific processes is a yellow '[IEEE 802.3] processes' block, which is connected to an external 'MI\_[IEEE 802.3]' interface on the left. This block receives two signals, ETH\_RI and ETH\_TI\_CK, from the right. The output of the [IEEE 802.3] processes goes to a 'Rate adaptation' block, which then feeds into a 'Scrambler' block. The output of the scrambler goes to an 'Elastic store' block, which has 'WR' (write) and 'RD' (read) ports. The 'WR' port is connected to the 'Scrambler' and the 'RD' port is connected to a 'Justification control (IMP)' block. The 'IMP' block also receives 'CK' (clock) from a 'Clock generator' block. The 'Clock generator' is connected to a 'Free-running clock generator (ODCa)' block. The 'IMP' block outputs 'FS' (frame sync) to a '1/122368' divider block, which in turn outputs 'MFS' (multi-frame sync) to a '1/256' divider block. The 'Elastic store' block also outputs 'AI\_D' (data) to the bottom. The 'IMP' block outputs 'AI\_CK' (clock) to the bottom. The 'IMP' block also outputs 'CI\_SSF' (client signal signal fail) to an 'Insert CSF' block. The 'Insert CSF' block outputs 'Insert PT' (payload type) to an 'Insert RES' (residual) block. The 'Insert RES' block outputs 'ODU OH is set to all-0's, except PM STAT = 001' to the bottom. The bottom outputs are labeled AI\_D, AI\_CK, AI\_FS, and AI\_MFS. The entire diagram is labeled ODUkP\_AP and G.798(23)\_F14-102.7. + +Figure 14-102.7 – ODUkP/ETH-imp\_A\_So function + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.3.21.2 ODUkP to ETH-imp client adaptation sink function using IMP (ODUkP/ETH-imp\_A\_Sk) + +The ODUkP/ETH-imp\_A\_Sk extracts ETH\_CI information from the ODUkP payload area using the justification control of IMP, delivering ETH\_CI to ETH\_TFP and ETH\_FP. It extracts the OPUk overhead (PT and RES) and monitors the reception of the correct payload type. + +The information flow and processing of the ODUkP/ETH-imp\_A\_Sk function is defined with reference to Figures 14-102.8 and 14-102.9. + +## Symbol + +![Diagram of the ODUkP/ETH-imp_A_Sk function symbol. The central block is labeled 'ODUkP/ETH-imp'. Inputs from the left are 'ETH_TFP' and 'ETH_PP'. Inputs from the bottom are 'ODUkP_AP'. Outputs to the top are 'ETH_TFP' and 'ETH_PP'. Outputs to the right are 'ODUkP/ETH-imp_A_Sk_MP' and 'ETH_RP'. A reference label 'G.798(23)_F14-F102.8' is at the bottom right.](c6e449481a4deebff8ada290c22a77d9_img.jpg) + +Diagram of the ODUkP/ETH-imp\_A\_Sk function symbol. The central block is labeled 'ODUkP/ETH-imp'. Inputs from the left are 'ETH\_TFP' and 'ETH\_PP'. Inputs from the bottom are 'ODUkP\_AP'. Outputs to the top are 'ETH\_TFP' and 'ETH\_PP'. Outputs to the right are 'ODUkP/ETH-imp\_A\_Sk\_MP' and 'ETH\_RP'. A reference label 'G.798(23)\_F14-F102.8' is at the bottom right. + +Figure 14-102.8 – ODUkP/ETH-imp\_A\_Sk function + +## Interfaces + +Table 14-47.5 – ODUkP/ETH-imp\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUkP_AP:
ODUkP_AI_CK
ODUkP_AI_D
ODUkP_AI_FS
ODUkP_AI_MFS
ODUkP_AI_TSF

ETH_TF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ETHF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ODDUkP/ETH-imp_A_Sk_MP:
ODUkP/ETH-imp_A_Sk_MI_[IEEE 802.3] | ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF

ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF

ETH_RP:
ETH_RI

ODUkP/ETH-imp_A_Sk_MP:
ODUkP/ETH-imp_A_Sk_MI_[IEEE 802.3]
ODUkP/ETH-imp_A_Sk_MI_cPLM
ODUkP/ETH-imp_A_Sk_MI_AcPT
ODUkP/ETH-imp_A_Sk_MI_cCSF
ODUkP/ETH-imp_A_Sk_MI_cLCS | + +## Processes + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.1.1. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. + +**Client signal fail:** The function shall extract the CSF signal indicating the failure of the client signal out of Bit 1 of the PSI[2] byte of the payload structure identifier, as defined in clause 17.1 of [ITU-T G.709]. + +**Demapping:** The function shall extract the client data from the payload bytes in the OPUk frames. The information extraction of the payload area shall be under the control of IMP. + +**Block Synchronization:** See clause 8.2.7.1 for mapping procedures preserving the 2-bit alignment. + +**Descrambler:** The function shall descramble the 66b block stream before the rate adaptation. + +**Rate adaptation and PCS clock generation:** The function shall provide an elastic store (buffer) process. It writes the descrambled 66b block data stream into the buffer. The information extraction of the payload area shall be under the control of IMP. The client PCS data shall be read out of the buffer under the control of the PCS clock. + +*PCS clock generation:* The function shall provide for a client PCS clock (CK) generation process which generates a clock with a bit rate as specified in Table 14-43. + +*Buffer size:* The demapping process shall not insert or delete a 66b block between a Start (0x78) and Terminate (0x87/0x99/0xAA/0xB4/0xCC/0xD2/0xE1/0xFF) control block. + +**Replacement signal generation:** The function shall provide for a PCS replacement signal and clock generation process that generates a stream of local fault sequence ordered sets as specified in clause 17.11 of [ITU-T G.709] with a bit rate as specified in Table 7-2 of [ITU-T G.709]. + +The client-specific processes, and associated MI and PI signals, are defined in clause 9.5 of [ITU-T G.8021]. + +**[IEEE 802.3] processes:** The [IEEE 802.3] processes represent the whole functionality of the PHY layer above the PMA; this includes 64B/66B decoding and the reconciliation sublayer, as well as the MAC length check, MAC frame check and frame counting. + +NOTE – This Recommendation defines these processes by reference to [IEEE 802.3] and intentionally does not provide details, as this functionality is well understood from the IEEE work. + +![Block diagram of ODUkP/ETH-imp_A_Sk processes showing signal flow from client-specific processes and IEEE 802.3 processes through various adaptation and synchronization stages to output interfaces like ETH_CI and ODUkP/ETH-imp_A_Sk_MP.](5bab55ee2db5fd011c7dc277224026d7_img.jpg) + +The diagram illustrates the internal processes of the ODUkP/ETH-imp\_A\_Sk function. At the top, 'Client-specific processes' receive 'MI signals (See [ITU-T G.8021])' and output 'ETH\_CI (ETH\_TP)', 'ETH\_CI (ETH\_TFP)', 'ETH\_CI\_CLK', and 'ETH\_CI\_SSF'. Below them, '[IEEE 802.3] processes' receive 'MI\_[IEEE 802.3]' and output 'ETH\_PI (ETHHTF\_PP)', 'ETH\_PI (ETHF\_PP)', and 'ETH\_RI'. Both process blocks feed into a 'Selector'. The 'Selector' output goes to 'Rate adaptation' and 'Replacement signal generator'. 'Rate adaptation' feeds into 'Descrambler', which in turn feeds into 'Block synchronization'. 'Block synchronization' feeds into 'Elastic store' (with write 'WR' and read 'RD' ports) and 'PCS clock generator (IMP)'. The 'Elastic store' feeds into 'Extract CSF' (outputting 'dCSF') and 'Extract PT' (outputting 'MI\_AcPT'). 'Extract PT' feeds into 'PT process', which outputs 'dPLM'. All defect signals ('dLCS', 'dPLM', 'dCSF', 'AI\_TSF') are fed into 'Defect correlations', which output 'MI\_cLCS', 'MI\_cPLM', and 'MI\_cCSF'. 'Consequent actions' block receives 'aAIS' from 'Replacement signal generator' and defect signals, outputting 'dLCS', 'dPLM', 'dCSF', and 'AI\_TSF'. The entire internal structure is labeled 'ODUkP/ETH-imp\_A\_Sk\_MP' on the right. External input signals at the bottom are 'AI\_D', 'AI\_MFS', 'AI\_CK', 'AI\_FS', and 'AI\_TSF', collectively labeled 'ODUkP\_AP'. + +Block diagram of ODUkP/ETH-imp\_A\_Sk processes showing signal flow from client-specific processes and IEEE 802.3 processes through various adaptation and synchronization stages to output interfaces like ETH\_CI and ODUkP/ETH-imp\_A\_Sk\_MP. + +Figure 14-102.9 – ODUkP/ETH-imp\_A\_Sk processes + +### Defects + +The function shall detect dPLM, dCSF and dLCS. + +**dPLM:** See clause 6.2.4.1. The expected payload type is "0001 1101" as defined in clause 15.9.2.1 of [ITU-T G.709]. + +**dCSF:** See clause 6.2.10. + +**dLCS:** See clause 6.2.5.7.1. + +The definition of the client related defects used by the ODUkP/ETH-imp\_A\_Sk is outside the scope of this Recommendation. + +### Consequent actions + +aSSF $\leftarrow$ AI\_TSF or dPLM or dLCS + +aAIS $\leftarrow$ AI\_TSF or dPLM or dLCS + +On declaration of aAIS, the function shall output the PCS client replacement signal within two ODUk frames. On clearing aAIS, the replacement signal shall be removed within two ODUk frames and normal data being output. + +### Defect correlations + +cPLM $\leftarrow$ dPLM and (not AI\_TSF) + +cCSF $\leftarrow$ dCSF and (not dPLM) and (not AI\_TSF) + +cLCS $\leftarrow$ dLCS and (not dPLM) and (not AI\_TSF) + +**Performance monitoring:** None. + +## 14.4 COMMS functions + +Two types of COMMS functions are defined for the ODU: the ODUP/COMMS adaptation function (ODUP/COMMS\_A) that provides access to the ODU GCC1/2 overhead at the ODUP access point (ODUP\_AP), and the ODU/COMMS access function (ODU/COMMS\_AC) that provides access to the ODU GCC1/2 at ODU (termination) connection points (ODU\_CP/TCPs), as shown in Figure 14-103. The ODUP/COMMS\_A function supports transport of the COMMS data over an ODUP trail including the trail supervision, while the ODU/COMMS\_AC function supports transport of COMMS data over a ODU subnetwork connection. + +NOTE – COMMS subnetwork connections are independent of TCM subnetwork connections. + +![Figure 14-103 – ODU GCC access. The diagram consists of two parts, (a) and (b). Part (a) shows COMMS (GCC) access at ODUP access points. It features two identical vertical stacks. Each stack has a yellow trapezoidal block labeled 'ODUP/COMMS' at the top, connected to a 'COMMS_CP' line. Below it is a white triangle labeled 'ODUP' connected to an 'ODUP_AP' line. Below that is another white triangle labeled 'ODUP' connected to an 'ODUP_TCP' line. A dashed line labeled 'ODU network connection' connects the two 'ODUP_TCP' lines. A solid line labeled 'COMMS connection' connects the two 'ODUP/COMMS' blocks. Part (b) shows COMMS (GCC) access at ODU connection points. It features two identical yellow pentagonal blocks labeled 'ODU/COMMS' in the center. Each block is connected to an 'ODU_CP' line on its left and right. To the left of the first block is an 'ODU_NC' (dashed line with circles) connected to another 'ODU_CP' line. To the right of the second block is an 'ODU_TCP' line. A solid line labeled 'COMMS connection' connects the two 'ODU/COMMS' blocks. A 'COMMS_CP' line is connected to the top of each 'ODU/COMMS' block. An 'ODUP' triangle is connected to the 'ODU_TCP' line on the right.](539dff67945f344becfdd7bebd3b7d69_img.jpg) + +Figure 14-103 – ODU GCC access. The diagram consists of two parts, (a) and (b). Part (a) shows COMMS (GCC) access at ODUP access points. It features two identical vertical stacks. Each stack has a yellow trapezoidal block labeled 'ODUP/COMMS' at the top, connected to a 'COMMS\_CP' line. Below it is a white triangle labeled 'ODUP' connected to an 'ODUP\_AP' line. Below that is another white triangle labeled 'ODUP' connected to an 'ODUP\_TCP' line. A dashed line labeled 'ODU network connection' connects the two 'ODUP\_TCP' lines. A solid line labeled 'COMMS connection' connects the two 'ODUP/COMMS' blocks. Part (b) shows COMMS (GCC) access at ODU connection points. It features two identical yellow pentagonal blocks labeled 'ODU/COMMS' in the center. Each block is connected to an 'ODU\_CP' line on its left and right. To the left of the first block is an 'ODU\_NC' (dashed line with circles) connected to another 'ODU\_CP' line. To the right of the second block is an 'ODU\_TCP' line. A solid line labeled 'COMMS connection' connects the two 'ODU/COMMS' blocks. A 'COMMS\_CP' line is connected to the top of each 'ODU/COMMS' block. An 'ODUP' triangle is connected to the 'ODU\_TCP' line on the right. + +a) COMMS (GCC) access at ODUP access points + +b) COMMS (GCC) access at ODU connection points + +G.798(17)\_F14-103 + +**Figure 14-103 – ODU GCC access** + +#### 14.4.1 ODUP to COMMS adaptation function (ODUP/COMMS\_A) + +The ODUP to COMMS adaptation functions provide access to the GCC1/2 overhead in the ODU for generic data communication. + +##### 14.4.1.1 ODUP to COMMS adaptation source function (ODUP/COMMS\_A\_So) + +The ODUP/COMMS\_A\_So function maps the generic communication channel data into the ODU GCC1/2 overhead. + +The information flow and processing of the ODUP/COMMS\_A\_So functions is defined with reference to Figures 14-104 and 14-105. + +#### Symbol + +![Figure 14-104 shows two block diagrams for the ODUP/COMMS_A_So function. The left diagram is for ODUkP and the right is for ODUCnP. Both show COMMS_CP and ODUkP/COMMS_A_So_MP as inputs to a trapezoidal block labeled ODUkP/COMMS or ODUCnP/COMMS. The output is ODUkP_AP or ODUCnP_AP, with a label 'k = 0, 1, 2, 2e, 3, 4, flex' between the block and the output. A reference 'G.798(17)_F14-104' is at the bottom right.](e5df094ac4c47bcbef86dece9332a417_img.jpg) + +Figure 14-104 shows two block diagrams for the ODUP/COMMS\_A\_So function. The left diagram is for ODUkP and the right is for ODUCnP. Both show COMMS\_CP and ODUkP/COMMS\_A\_So\_MP as inputs to a trapezoidal block labeled ODUkP/COMMS or ODUCnP/COMMS. The output is ODUkP\_AP or ODUCnP\_AP, with a label 'k = 0, 1, 2, 2e, 3, 4, flex' between the block and the output. A reference 'G.798(17)\_F14-104' is at the bottom right. + +Figure 14-104 – ODUP/COMMS\_A\_So function + +#### Interfaces + +Table 14-48 – ODUP/COMMS\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------| +| COMMS_CP:
COMMS_CI_D
ODUP_AP:
ODUP_AI_CK
ODUP_AI_FS
ODUP/COMMS_A_So_MP:
ODUP/COMMS_A_So_MI_GCCAccess | COMMS_CP:
COMMS_CI_CK
ODUP_AP:
ODUP_AI_D | + +#### Processes + +The processes associated with the ODUP/COMMS\_A\_So function are as depicted in Figure 14-105. + +**COMMS clock generation:** The function shall generate the COMMS clock (CI\_CK) by dividing the incoming ODUP clock (AI\_CK) by a factor of 7648 if one GCC overhead is accessed, or by a factor of 3824 if both GCC overheads are accessed. + +**Mapping:** Depending on the MI\_GCCAccess configuration, the function shall map the incoming COMMS (CI\_D) data only into GCC1 (MI\_GCCAccess = "GCC1") or only into GCC2 (MI\_GCCAccess = "GCC2") or into both GCC1 and GCC2 overhead (MI\_GCCAccess = "GCC1+GCC2") of the ODU frame. The bit rate of the COMMS data is defined by the outgoing COMMS clock (CI\_CK) and is in the range as given in Table 7-10 of [ITU-T G.709]. + +Table 14-49 – Intentionally left blank + +The insertion of the COMMS data follows the transmission order of the GCC bits and bytes. + +![Figure 14-105: ODUP/COMMS_A_So processes diagram. A grey box labeled 'ODUP_AP' contains two sub-processes: 'Mapping' and 'COMMS clock generation'. Inputs from 'COMMS_CP' include 'CI_D' and 'CI_CK'. Inputs from 'ODUP_AP' include 'AI_FS', 'AI_D', and 'AI_CK'. The 'Mapping' process outputs to 'COMMS_CP' and 'ODUP_AP'. The 'COMMS clock generation' process outputs to 'COMMS_CP' and 'ODUP_AP'. A vertical label on the right is 'ODUP/COMMS_A_So_MP'. A reference 'G.798(17)_F13-105' is at the bottom right.](7ac0d7b4763471d7c6dee8a2ce125b6a_img.jpg) + +Figure 14-105: ODUP/COMMS\_A\_So processes diagram. A grey box labeled 'ODUP\_AP' contains two sub-processes: 'Mapping' and 'COMMS clock generation'. Inputs from 'COMMS\_CP' include 'CI\_D' and 'CI\_CK'. Inputs from 'ODUP\_AP' include 'AI\_FS', 'AI\_D', and 'AI\_CK'. The 'Mapping' process outputs to 'COMMS\_CP' and 'ODUP\_AP'. The 'COMMS clock generation' process outputs to 'COMMS\_CP' and 'ODUP\_AP'. A vertical label on the right is 'ODUP/COMMS\_A\_So\_MP'. A reference 'G.798(17)\_F13-105' is at the bottom right. + +Figure 14-105 – ODUP/COMMS\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +**14.4.1.2 ODUP to COMMS adaptation sink function (ODUP/COMMS\_A\_Sk)** + +The ODUP/COMMS\_A\_Sk extracts the COMMS data from the ODU GCC overhead. + +**Symbol** + +The information flow and processing of the ODUP/COMMS\_A\_Sk functions is defined with reference to Figures 14-106 and 14-107. + +![Figure 14-106: ODUP/COMMS_A_Sk function diagram. Two trapezoidal symbols represent the functions. The left symbol is 'ODUPkP/COMMS' with input 'ODUPkP/COMMS_A_Sk_MP' and 'ODUPkP_AP' (labeled k = 0, 1, 2, 2e, 3, 4, flex), and output 'COMMS_CP'. The right symbol is 'ODUCnP/COMMS' with input 'ODUCnP/COMMS_A_Sk_MP' and 'ODUCnP_AP', and output 'COMMS_CP'. A reference 'G.798(17)_F14-106' is at the bottom right.](5aa9a1f9f87b2e03c5a516b13ee62612_img.jpg) + +Figure 14-106: ODUP/COMMS\_A\_Sk function diagram. Two trapezoidal symbols represent the functions. The left symbol is 'ODUPkP/COMMS' with input 'ODUPkP/COMMS\_A\_Sk\_MP' and 'ODUPkP\_AP' (labeled k = 0, 1, 2, 2e, 3, 4, flex), and output 'COMMS\_CP'. The right symbol is 'ODUCnP/COMMS' with input 'ODUCnP/COMMS\_A\_Sk\_MP' and 'ODUCnP\_AP', and output 'COMMS\_CP'. A reference 'G.798(17)\_F14-106' is at the bottom right. + +Figure 14-106 – ODUP/COMMS\_A\_Sk function + +**Interfaces** + +Table 14-50 – ODUP/COMMS\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| ODUP_AP:
ODUP_AI_CK
ODUP_AI_D
ODUP_AI_FS
ODUP_AI_TSF
ODUP/COMMS_A_Sk_MP:
ODUP/COMMS_A_Sk_MI_GCCAccess | COMMS_CP:
COMMS_CI_CK
COMMS_CI_D
COMMS_CI_SSF | + +## Processes + +The processes associated with the ODUP/COMMS\_A\_Sk function are as depicted in Figure 14-107. + +**COMMS clock generation:** The function shall generate the COMMS clock (CI\_CK) by dividing the incoming ODUP clock (AI\_CK) by a factor of 7648 if one GCC overhead is accessed, or by a factor of 3824 if both GCC overheads are accessed. + +**Demapping:** Depending on the MI\_GCCAccess configuration, the function shall extract the COMMS (CI\_D) data only from GCC1 (MI\_GCCAccess = "GCC1") or only from GCC2 (MI\_GCCAccess = "GCC2") or from both GCC1 and GCC2 overhead (MI\_GCCAccess = "GCC1+GCC2") of the ODU frame. The bit rate of the COMMS data is defined by the outgoing COMMS clock (CI\_CK) and is in the range as given in Table 7-10 of [ITU-T G.709]. + +The extraction of the COMMS data follows the transmission order of the GCC bits and bytes. + +![Figure 14-107 – ODUP/COMMS_A_Sk processes. This block diagram shows the internal components of the ODUP/COMMS_A_Sk function. The main container is labeled 'ODUP_AP' at the bottom and 'COMMS_CP' at the top. Inside, there are two sub-blocks: 'Demapping' on the left and 'COMMS clock generation' on the right. Inputs from the bottom are AI_FS, AI_D, AI_CK, and AI_TSF. AI_CK connects to the clock generation block. AI_D connects to the Demapping block. AI_TSF connects to a label 'aSSF' on the right. AI_FS also connects to the 'aSSF' label. The Demapping block outputs CI_D. The clock generation block outputs CI_CK. A configuration input MI_GCCAccess enters from the right and connects to the Demapping block. A vertical label 'ODUP/COMMS_A_Sk_MP' is on the far right. A reference 'G.798(17)_F13-107' is at the bottom right.](e0eba715b26e99c0beececdd6112ee58_img.jpg) + +Figure 14-107 – ODUP/COMMS\_A\_Sk processes. This block diagram shows the internal components of the ODUP/COMMS\_A\_Sk function. The main container is labeled 'ODUP\_AP' at the bottom and 'COMMS\_CP' at the top. Inside, there are two sub-blocks: 'Demapping' on the left and 'COMMS clock generation' on the right. Inputs from the bottom are AI\_FS, AI\_D, AI\_CK, and AI\_TSF. AI\_CK connects to the clock generation block. AI\_D connects to the Demapping block. AI\_TSF connects to a label 'aSSF' on the right. AI\_FS also connects to the 'aSSF' label. The Demapping block outputs CI\_D. The clock generation block outputs CI\_CK. A configuration input MI\_GCCAccess enters from the right and connects to the Demapping block. A vertical label 'ODUP/COMMS\_A\_Sk\_MP' is on the far right. A reference 'G.798(17)\_F13-107' is at the bottom right. + +Figure 14-107 – ODUP/COMMS\_A\_Sk processes + +**Defects:** None. + +### Consequent actions + +The function shall perform the following consequent action: + +aSSF $\leftarrow$ AI\_TSF + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 14.4.2 ODU to COMMS access function (ODU/COMMS\_AC) + +The ODU to COMMS access functions provide access to the GCC1/2 overhead in the ODU for generic data communication at ODU\_CPs (including TCPs). As the functions act on the ODU signal that passes through the CP, they are inserted into an expanded ODU\_CP as shown in Figure 14-108. They can be inserted into any ODU\_CP, independently of sink or source processing. A ODU/COMMS\_AC\_Sk and So function can be used at the same CP for extraction of the COMMS data from the GCC and insertion of new COMMS data. + +![Diagram showing the expansion of an ODU CP for COMMS access. A vertical line on the left has two small circles. Dashed lines connect these circles to a diamond-shaped block labeled 'ODU/COMMS'. The top of the block is connected to a terminal labeled 'COMMS_CP'. The bottom of the block is connected to another terminal.](5772ffa3b9089a69e25df5ec289ead55_img.jpg) + +Diagram showing the expansion of an ODU CP for COMMS access. A vertical line on the left has two small circles. Dashed lines connect these circles to a diamond-shaped block labeled 'ODU/COMMS'. The top of the block is connected to a terminal labeled 'COMMS\_CP'. The bottom of the block is connected to another terminal. + +G.798(17)\_F14-108 + +Figure 14-108 – ODU\_CP expansion for COMMS access + +**14.4.2.1 ODU to COMMS access source function (ODU/COMMS\_AC\_So)** + +The ODU/COMMS\_AC\_So function maps the generic communication channel data into the GCC1/2 overhead of the ODU signal that passes through the function. + +The information flow and processing of the ODU/COMMS\_AC\_So functions is defined with reference to Figures 14-109 and 14-110. + +**Symbol** + +![Diagram showing two instances of the ODU/COMMS_AC_So function. The left instance is labeled 'ODUk/COMMS' and has an input 'ODUk_CP' at the top, an input 'ODUk/COMMS_AC_So_MP' on the left, and an output 'COMMS_CP' at the top right. The bottom output is labeled 'ODUk_CP'. Below the block is the text 'k = 0, 1, 2, 2e, 3, 4, flex'. The right instance is labeled 'ODUCn/COMMS' and has an input 'ODUCn_CP' at the top, an input 'ODUCn/COMMS_AC_So_MP' on the left, and an output 'COMMS_CP' at the top right. The bottom output is labeled 'ODUCn_CP'. A reference code 'G.798(17)_F14-109' is at the bottom right.](dfb76390c9b698db558781fdba549ab3_img.jpg) + +Diagram showing two instances of the ODU/COMMS\_AC\_So function. The left instance is labeled 'ODUk/COMMS' and has an input 'ODUk\_CP' at the top, an input 'ODUk/COMMS\_AC\_So\_MP' on the left, and an output 'COMMS\_CP' at the top right. The bottom output is labeled 'ODUk\_CP'. Below the block is the text 'k = 0, 1, 2, 2e, 3, 4, flex'. The right instance is labeled 'ODUCn/COMMS' and has an input 'ODUCn\_CP' at the top, an input 'ODUCn/COMMS\_AC\_So\_MP' on the left, and an output 'COMMS\_CP' at the top right. The bottom output is labeled 'ODUCn\_CP'. A reference code 'G.798(17)\_F14-109' is at the bottom right. + +Figure 14-109 – ODU/COMMS\_AC\_So function + +**Interfaces** + +Table 14-51 – ODU/COMMS\_AC\_So inputs and outputs + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| COMMS_CP:
COMMS_CI_D
ODU_CP:
ODU_CI_D
ODU_CI_CK
ODU_CI_FS
ODU_CI_MFS
ODU_CI_SSF
ODU_CI_RP
ODU_CI_TSCC
ODU/COMMS_AC_So_MP:
ODU/COMMS_AC_So_MI_GCCAccess | COMMS_CP:
COMMS_CI_CK
ODU_CP:
ODU_CI_D
ODU_CI_CK
ODU_CI_FS
ODU_CI_MFS
ODU_CI_SSF
ODU_CI_RP
ODU_CI_TSCC | + +**Processes** + +The processes associated with the ODU/COMMS\_AC\_So function are as depicted in Figure 14-110. + +**COMMS clock generation:** The function shall generate the COMMS clock (COMMS\_CI\_CK) by dividing the incoming ODU clock (ODU\_CI\_CK) by a factor of 7648 if one GCC overhead is accessed, or by a factor of 3824 if both GCC overheads are accessed. + +**Mapping:** Depending on the MI\_GCCAccess configuration, the function shall map the incoming COMMS (CI\_D) data only into GCC1 (MI\_GCCAccess = "GCC1") or only into GCC2 (MI\_GCCAccess = "GCC2") or into both GCC1 and GCC2 overhead (MI\_GCCAccess = "GCC1+GCC2") of the ODU frame. The bit rate of the COMMS data is defined by the outgoing COMMS clock (CI\_CK) and is in the range as given in Table 7-10 of [ITU-T G.709]. + +The insertion of the COMMS data follows the transmission order of the GCC bits and bytes. + +![Diagram of ODU/COMMS_AC_So processes showing signal flow from ODU_CP to COMMS_CP and back to ODU_CP. It includes blocks for Mapping and COMMS clock generation, with inputs like CI_TSCC, CI_RP, CI_SSF, CI_MFS, CI_FS, CI_CK, and CI_D, and outputs like CI_D and CI_CK. A configuration input MI_GCCAccess is also shown.](81e0bc85cbb6bdb4779d4af6d86e80cd_img.jpg) + +The diagram illustrates the ODU/COMMS\_AC\_So processes. It shows the flow of signals between the ODU\_CP (Optical Data Unit Client Port) and the COMMS\_CP (Communications Client Port). On the left, the ODU\_CP section lists inputs: CI\_TSCC, CI\_RP, CI\_SSF, CI\_MFS, CI\_FS, CI\_CK, and CI\_D. These signals enter a central grey box. Inside, the CI\_D signal is split: one path goes to a 'Mapping' block, and another goes to a 'COMMS clock generation' block. The 'Mapping' block outputs a CI\_D signal to the COMMS\_CP section. The 'COMMS clock generation' block outputs a CI\_CK signal to the COMMS\_CP section. A configuration input MI\_GCCAccess is shown entering the 'COMMS clock generation' block. On the right, the COMMS\_CP section lists outputs: CI\_D and CI\_CK. Below the grey box, the ODU\_CP section lists outputs: CI\_TSCC, CI\_RP, CI\_SSF, CI\_MFS, CI\_FS, CI\_CK, and CI\_D. The diagram is labeled G.798(17)\_F13-110 and ODU/COMMS\_A\_So\_MP. + +Diagram of ODU/COMMS\_AC\_So processes showing signal flow from ODU\_CP to COMMS\_CP and back to ODU\_CP. It includes blocks for Mapping and COMMS clock generation, with inputs like CI\_TSCC, CI\_RP, CI\_SSF, CI\_MFS, CI\_FS, CI\_CK, and CI\_D, and outputs like CI\_D and CI\_CK. A configuration input MI\_GCCAccess is also shown. + +**Figure 14-110 – ODU/COMMS\_AC\_So processes** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.4.2.2 ODU to COMMS access sink function (ODU/COMMS\_AC\_Sk) + +The ODU/COMMS\_AC\_Sk extracts the COMMS data from the ODU GCC overhead. + +The information flow and processing of the ODU/COMMS\_AC\_Sk functions is defined with reference to Figures 14-111 and 14-112. + +## Symbol + +![Figure 14-111 shows two symbols for the ODU/COMMS_AC_Sk function. The left symbol is for ODUk/COMMS, with an input OD uk/COMMS_AC_Sk_MP and an output OD uk_CP. It also has an input OD uk_CP and an output COMMS_CP. The right symbol is for ODUCn/COMMS, with an input ODUCn/COMMS_AC_Sk_MP and an output ODUCn_CP. It also has an input ODUCn_CP and an output COMMS_CP. The parameter k is defined as 0, 1, 2, 2e, 3, 4, flex.](4eab0234f29827bae0c6e71fe650aa63_img.jpg) + +G.798(17)\_F14-111 + +Figure 14-111 shows two symbols for the ODU/COMMS\_AC\_Sk function. The left symbol is for ODUk/COMMS, with an input OD uk/COMMS\_AC\_Sk\_MP and an output OD uk\_CP. It also has an input OD uk\_CP and an output COMMS\_CP. The right symbol is for ODUCn/COMMS, with an input ODUCn/COMMS\_AC\_Sk\_MP and an output ODUCn\_CP. It also has an input ODUCn\_CP and an output COMMS\_CP. The parameter k is defined as 0, 1, 2, 2e, 3, 4, flex. + +**Figure 14-111 – ODU/COMMS\_AC\_Sk function** + +## Interfaces + +**Table 14-52 – ODU/COMMS\_AC\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODU_CP:
ODU_CI_CK
ODU_CI_D
ODU_CI_FS
ODU_CI_MFS
ODU_CI_SSF
ODU_CI_RP
ODU_CI_TSCC
ODU/COMMS_AC_Sk_MP:
ODU/COMMS_AC_Sk_MI_GCCAccess
ODU/COMMS_AC_Sk_MI_GCCCont | COMMS_CP:
COMMS_CI_CK
COMMS_CI_D
COMMS_CI_SSF
ODU_CP:
ODU_CI_CK
ODU_CI_D
ODU_CI_FS
ODU_CI_MFS
ODU_CI_SSF
ODU_CI_RP
ODU_CI_TSCC | + +## Processes + +The processes associated with the ODU/COMMS\_AC\_Sk function are as depicted in Figure 14-112. + +**COMMS clock generation:** The function shall generate the COMMS clock (COMMS\_CI\_CK) by dividing the incoming ODU clock (ODU\_CI\_CK) by a factor of 7648 if one GCC overhead is accessed, or by a factor of 3824 if both GCC overheads are accessed. + +**Demapping:** Depending on the MI\_GCCAccess configuration, the function shall extract the COMMS (CI\_D) data only from GCC1 (MI\_GCCAccess = "GCC1") or only from GCC2 (MI\_GCCAccess = "GCC2") or from both GCC1 and GCC2 overhead (MI\_GCCAccess = "GCC1+GCC2") of the ODU frame. The bit rate of the COMMS data is defined by the outgoing COMMS clock (CI\_CK) and is in the range as given in Table 7-10 of [ITU-T G.709]. + +The extraction of the COMMS data follows the transmission order of the GCC bits and bytes. + +![Figure 14-112 – ODU/COMMS_AC_Sk processes. This block diagram shows the internal structure of an ODU/COMMS_AC_Sk_MP. It is divided into two main sections: ODU_CP and COMMS_CP. The ODU_CP section contains a 'Demapping' block that receives inputs from CI_TSCC, CI_RP, CI_SSF, CI_MFS, CI_FS, CI_CK, and CI_D. The COMMS_CP section contains a 'COMMS clock generation' block that receives inputs from CI_D, CI_CK, and CI_SSF. Both blocks are connected to MI_GCCAccess and MI_GCCCont. The diagram is labeled G.798(17)_F13-112.](ad9b0c8d0d3fc421b0dbc2ecc61376f4_img.jpg) + +The diagram illustrates the internal architecture of an ODU/COMMS\_AC\_Sk\_MP. It is split into two primary functional areas: ODU\_CP and COMMS\_CP. The ODU\_CP area includes a 'Demapping' block. The COMMS\_CP area includes a 'COMMS clock generation' block. Various input signals (CI\_TSCC, CI\_RP, CI\_SSF, CI\_MFS, CI\_FS, CI\_CK, CI\_D) are shown entering the system from the top and bottom. Output signals (MI\_GCCAccess, MI\_GCCCont) exit the system to the right. The diagram is identified by the label G.798(17)\_F13-112. + +Figure 14-112 – ODU/COMMS\_AC\_Sk processes. This block diagram shows the internal structure of an ODU/COMMS\_AC\_Sk\_MP. It is divided into two main sections: ODU\_CP and COMMS\_CP. The ODU\_CP section contains a 'Demapping' block that receives inputs from CI\_TSCC, CI\_RP, CI\_SSF, CI\_MFS, CI\_FS, CI\_CK, and CI\_D. The COMMS\_CP section contains a 'COMMS clock generation' block that receives inputs from CI\_D, CI\_CK, and CI\_SSF. Both blocks are connected to MI\_GCCAccess and MI\_GCCCont. The diagram is labeled G.798(17)\_F13-112. + +**Figure 14-112 – ODU/COMMS\_AC\_Sk processes** + +**Defects:** None. + +**Consequent actions** + +The function shall perform the following consequent action: + +$$\text{aSSF} \leftarrow \text{CI\_SSF}$$ + +**Defect correlations:** None. + +**Performance monitoring:** None. + +**14.5 Sub-layer functions** + +**14.5.1 ODU tandem connection sub-layer (ODUT) functions** + +Up to six independent ODUT sub-layers can pass through or can be terminated at an ODU\_CP as defined in [ITU-T G.709]. For an ODUT sub-layer termination, the ODU\_CP is expanded as defined in [ITU-T G.805]. + +The ODUT\_TT, ODUT/ODU\_A and ODUT\_TCMC functions are always combined together and can be located at any ODU\_CP as shown in Figure 14-113. For the location of the ODUTm\_TT function, see Figure 14-119. + +NOTE – In accordance with [ITU-T G.709], nesting and cascading are the default operational configurations. Overlapping is an additional configuration for testing purposes only. Overlapped monitored connections must be operated in a non-intrusive mode in which the maintenance signals ODU-AIS and ODU-LCK are not generated. For the case where one of the endpoints in an overlapping monitored connection is located inside a SNC protected domain while the other endpoint is located outside the protected domain, the SNC protection should be forced to working when the endpoint of the overlapping monitored connection is located on the working connection, and forced to protection when the endpoint is located on the protection connection. + +![Diagram showing the location of ODUT functions (ODUT_TT, ODUT/ODU_A, ODUT_TCMC) for ODUk and ODUCn layers. The diagram is divided into two main sections: the top section for ODUk and the bottom section for ODUCn. Each section shows a central ODUk or ODUCn node connected to various functional blocks representing different layer boundaries and processing points. Labels include ODUkP, ODUkT, ODUkT/ODUk, ODUk_TCMC, ODUk_AP, ODUk_RP, OTUk[V]/ODUk, ODUCnP, ODUCnT, ODUCnT/ODUCn, ODUCn_TCMC, ODUCn_AP, ODUCn_RP, and OTUCn/ODUCn. Arrows indicate the flow of data and control signals between these components.](1a1c6e97fdffe8ffed7b997b7e682d3c_img.jpg) + +The diagram illustrates the functional architecture for ODUk and ODUCn layers, showing the placement of various processing and termination functions. + +**ODUk Layer (Top Section):** + +- A central oval node is labeled **ODUk**. +- Two dashed triangles at the top are labeled **ODUkP**. Arrows point from these triangles to trapezoidal blocks labeled **ODUkT/ODUk**. +- Each **ODUkT/ODUk** block is connected to a rectangular block labeled **ODUk\_TCMC**. +- From each **ODUk\_TCMC** block, an arrow points down to a trapezoidal block labeled **ODUkT**. +- From each **ODUkT** block, an arrow points down to a dashed triangle labeled **OTUk[V]/ODUk**. +- Labels **ODUk\_TCMC**, **ODUk\_AP**, and **ODUk\_RP** are placed near the top **ODUk\_TCMC** block. +- Labels **ODUk\_CP** are placed near the top and bottom of the central **ODUk** oval. +- On the left, a separate structure shows two **ODUkT/ODUk** blocks connected to a central **ODUk\_TCMC** block, with arrows pointing to **ODUkT** blocks and then to a dashed triangle labeled **OTUk[V]/ODUk**. Labels **ODUk\_TCMC**, **ODUk\_AP**, and **ODUk\_RP** are also present here. +- On the right, two dashed triangles labeled **OTUk[V]/ODUk** are shown with dashed arrows pointing to them from the top **ODUkT/ODUk** blocks. + +**ODUCn Layer (Bottom Section):** + +- A central oval node is labeled **ODUCn**. +- Two dashed triangles at the top are labeled **ODUCnP**. Arrows point from these triangles to trapezoidal blocks labeled **ODUCnT/ODUCn**. +- Each **ODUCnT/ODUCn** block is connected to a rectangular block labeled **ODUCn\_TCMC**. +- From each **ODUCn\_TCMC** block, an arrow points down to a trapezoidal block labeled **ODUCnT**. +- From each **ODUCnT** block, an arrow points down to a dashed triangle labeled **OTUCn/ODUCn**. +- Labels **ODUCn\_TCMC**, **ODUCn\_AP**, and **ODUCn\_RP** are placed near the top **ODUCn\_TCMC** block. +- Labels **ODUCn\_CP** are placed near the top and bottom of the central **ODUCn** oval. +- On the right, two dashed triangles labeled **OTUCn/ODUCn** are shown with dashed arrows pointing to them from the top **ODUCnT/ODUCn** blocks. + +Diagram showing the location of ODUT functions (ODUT\_TT, ODUT/ODU\_A, ODUT\_TCMC) for ODUk and ODUCn layers. The diagram is divided into two main sections: the top section for ODUk and the bottom section for ODUCn. Each section shows a central ODUk or ODUCn node connected to various functional blocks representing different layer boundaries and processing points. Labels include ODUkP, ODUkT, ODUkT/ODUk, ODUk\_TCMC, ODUk\_AP, ODUk\_RP, OTUk[V]/ODUk, ODUCnP, ODUCnT, ODUCnT/ODUCn, ODUCn\_TCMC, ODUCn\_AP, ODUCn\_RP, and OTUCn/ODUCn. Arrows indicate the flow of data and control signals between these components. + +G.798(17)\_F14-113 + +**Figure 14-113 – Location of ODUT\_TT, ODUT/ODU\_A and ODUT\_TCMC functions** + +### 14.5.1.1 ODUT trail termination function (ODUT\_TT) + +The ODUT\_TT function terminates a level of tandem connection monitoring (TCM) overhead of the ODU overhead to determine the status of an ODU TCM sub-layer trail. + +Figure 14-114 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Figure 14-114: ODUT_TT function diagram showing two unidirectional functions (ODUKT and ODUCnT) combined into a bidirectional function. Each function has an AP (Access Point) input, a TCP (Tandem Connection Point) output, and a RP (Retrieval Point) input from the opposite direction.](bb0e323a672fa2f89e0132b1db61cfb3_img.jpg) + +The diagram illustrates the ODUT\_TT function as a combination of two unidirectional functions. On the left, the ODUkT function is shown: it has an ODUkT\_AP input at the top, an ODUk\_TCP output at the bottom, and an ODUkT\_RP input from the right. On the right, the ODUCnT function is shown: it has an ODUCnT\_AP input at the top, an ODUCn\_TCP output at the bottom, and an ODUCnT\_RP input from the left. The two functions are connected by their respective RP inputs, forming a bidirectional monitoring path. The reference G.798(17)\_F14-114 is noted at the bottom right. + +Figure 14-114: ODUT\_TT function diagram showing two unidirectional functions (ODUKT and ODUCnT) combined into a bidirectional function. Each function has an AP (Access Point) input, a TCP (Tandem Connection Point) output, and a RP (Retrieval Point) input from the opposite direction. + +Figure 14-114 – ODUT\_TT + +#### 14.5.1.1.1 ODUT trail termination source function (ODUT\_TT\_So) + +The ODUT\_TT\_So function computes the BIP-8[1..n] and adds tandem connection monitoring overhead (TCMOH) – including the TTI, BIP-8[1..n], DMi, i = 1 to 6 bits, BDI and BEI[1..n] signals – in a selected TCMOH field to the ODU signal at its ODUT\_AP if it is OPERATIONAL; otherwise, in TRANSPARENT mode, the TCMOH field signal is passed through transparently. The ODUCn signal has n TCM overhead fields per TCM level; the ODUk signal has one (n = 1) TCM overhead field per TCM level. + +The information flow and processing of the ODUT\_TT\_So function is defined with reference to Figures 14-115 and 14-116. + +#### Symbol + +![Figure 14-115: ODUT_TT_So function diagram showing the source function components. It includes inputs for ODUkT_AP, ODUkT_TT_So_MP, and ODUkT_TT_So_TCMCP, and outputs for ODUk_TCP. The same structure is shown for ODUCnT.](b297f64b2487ded933870098ad287bce_img.jpg) + +The diagram shows the ODUT\_TT\_So function components. On the left, the ODUkT function is shown with an ODUkT\_AP input at the top, an ODUk\_TCP output at the bottom, an ODUkT\_RP input from the right, an ODUkT\_TT\_So\_MP input from the left, and an ODUkT\_TT\_So\_TCMCP input from the left. Below the ODUkT\_TT\_So\_MP input, the parameter k is defined as k = 0, 1, 2, 2e, 3, 4, flex. On the right, the ODUCnT function is shown with similar inputs: ODUCnT\_AP, ODUCn\_TCP, ODUCnT\_RP, ODUCnT\_TT\_So\_MP, and ODUCnT\_TT\_So\_TCMCP. The reference G.798(17)\_F14-115 is noted at the bottom right. + +Figure 14-115: ODUT\_TT\_So function diagram showing the source function components. It includes inputs for ODUkT\_AP, ODUkT\_TT\_So\_MP, and ODUkT\_TT\_So\_TCMCP, and outputs for ODUk\_TCP. The same structure is shown for ODUCnT. + +Figure 14-115 – ODUT\_TT\_So function + +## Interfaces + +**Table 14-53 – ODUT\_TT\_So inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| ODUT_AP:
ODUT_AI_CK
ODUT_AI_D
ODUT_AI_FS
ODUT_AI_MFS
ODUT_AI_RP
ODUT_AI_TSCC
ODUT_RP:
ODUT_RI_BDI
ODUT_RI_BEI[1..n]
ODUT_RI_BIAE
ODUT_RI_DM
ODUT_TT_So_MP:
ODUT_TT_So_MI_TxTI
ODUT_TT_So_MI_DM_Source
ODUT_TT_So_MI_DMValue
ODUT_TT_So_TCMCP:
ODUT_TT_So_TCMCI_Mode
ODUT_TT_So_TCMCI_Level | ODUTCP:
ODU_CI_CK
ODU_CI_D
ODU_CI_FS
ODU_CI_MFS
ODU_CI_RP
ODU_CI_TSCC | + +## Processes + +The processes associated with the ODUT\_TT\_So function are as depicted in Figure 14-116. + +**Mode:** If the TCMCI\_Mode has the value OPERATIONAL, the following processes shall be performed. If the TCMCI\_Mode has the value TRANSPARENT, all information shall be passed through transparently and the following processes shall not be performed. + +**TCMOH-TTI:** If TCMCI\_Mode is OPERATIONAL, the trail trace identifier is inserted in the TTI byte position of the TCM[TCMCI\_Level] field in the first ODU overhead instance. Its value is derived from reference point ODUT\_TT\_So\_MP. The trail trace format is described in clause 15.2 of [ITU-T G.709]. + +**TCMOH-BDI:** If TCMCI\_Mode is OPERATIONAL, the backward defect indication is inserted in the BDI bit position of the TCM[TCMCI\_Level] field in the first ODU overhead instance. Its value is derived from reference point ODUT\_RP. Upon the declaration/clearing of aBDI at the termination sink function, the trail termination source function shall have inserted/removed the BDI indication within 50 ms. + +**TCMOH-BEI/BIAE:** If TCMCI\_Mode is OPERATIONAL, if RI\_BIAE is true the value "1011" is inserted into the BEI/BIAE bits of the TCM[TCMCI\_Level] field in all ODU overhead instances. If RI\_BIAE is false, the number of errors indicated in RI\_BEI[i] is encoded in the BEI/BIAE bits of the TCM[TCMCI\_Level] field in ODU overhead instance #i. Upon the detection of incoming alignment error or a number of errors at the termination sink function, the trail termination source function shall have inserted the values in the BEI/BIAE bits within 50 ms. + +**TCMOH-BIP-8:** If TCMCI\_Mode is OPERATIONAL, the calculated BIP-8 is inserted into the BIP-8 byte of the TCM[TCMCI\_Level] field. For the BIP-8 calculation, see clause 8.3.4.1. + +**TCMOH-DMti:** If TCMCI\_Mode is OPERATIONAL and if MI\_DM\_Source is false, then the value of the DMti bit is determined by the RI\_DM. If MI\_DM\_Source is true, then the value of the DMti bit is set to MI\_DMValue. + +NOTE – Equipment developed prior to Edition 4.0 of this Recommendation will not support the DMti processing. + +![Figure 14-116 – ODUT_TT_So processes. This block diagram illustrates the processing flow for the ODUT_TT_So function. At the top, the ODUT_AP interface provides inputs: AI_D, AI_CK, AI_FS, AI_MFS, AI_RP, and AI_TSCC. AI_D is connected to a 'Compute BIP-8' block, which outputs BIP-8[1..n]. This output is then processed by an 'Insert BIP-8' block. The 'Insert BIP-8' block is part of a vertical stack of processing blocks: 'Insert BEI/BIAE', 'Insert BDI', 'Process/insert DMti', and 'Insert TTI'. These blocks are influenced by various input signals: RI_BEI[1..n], RI_BIAE, RI_BDI, RI_DM, MI_DM_Source, MI_DMValue, MI_TxTI, TCMCI_Level, and TCMCI_Mode. These inputs are grouped into two main categories: ODUT_RP and ODUT_TT_So_MP. The ODUT_TT_So_MP category includes RI_DM, MI_DM_Source, MI_DMValue, MI_TxTI, TCMCI_Level, and TCMCI_Mode. The output of the 'Insert TTI' block is processed by a 'TCMOH[TCMCI_Level] insertion' block. The final output is the ODU_TCP interface, which provides outputs: CI_D, CI_CK, CI_FS, CI_MFS, CI_RP, and CI_TSCC. The diagram is labeled G.798(17)_F14-116.](ce4432c76d20b370ebecb57e59afc2ee_img.jpg) + +Figure 14-116 – ODUT\_TT\_So processes. This block diagram illustrates the processing flow for the ODUT\_TT\_So function. At the top, the ODUT\_AP interface provides inputs: AI\_D, AI\_CK, AI\_FS, AI\_MFS, AI\_RP, and AI\_TSCC. AI\_D is connected to a 'Compute BIP-8' block, which outputs BIP-8[1..n]. This output is then processed by an 'Insert BIP-8' block. The 'Insert BIP-8' block is part of a vertical stack of processing blocks: 'Insert BEI/BIAE', 'Insert BDI', 'Process/insert DMti', and 'Insert TTI'. These blocks are influenced by various input signals: RI\_BEI[1..n], RI\_BIAE, RI\_BDI, RI\_DM, MI\_DM\_Source, MI\_DMValue, MI\_TxTI, TCMCI\_Level, and TCMCI\_Mode. These inputs are grouped into two main categories: ODUT\_RP and ODUT\_TT\_So\_MP. The ODUT\_TT\_So\_MP category includes RI\_DM, MI\_DM\_Source, MI\_DMValue, MI\_TxTI, TCMCI\_Level, and TCMCI\_Mode. The output of the 'Insert TTI' block is processed by a 'TCMOH[TCMCI\_Level] insertion' block. The final output is the ODU\_TCP interface, which provides outputs: CI\_D, CI\_CK, CI\_FS, CI\_MFS, CI\_RP, and CI\_TSCC. The diagram is labeled G.798(17)\_F14-116. + +Figure 14-116 – ODUT\_TT\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 14.5.1.1.2 ODUT trail termination sink function (ODUT\_TT\_Sk) + +The ODUT\_TT\_Sk function reports the state of the ODU monitored tandem connection. It computes the BIP-8[1..n], extracts tandem connection monitoring overhead (TCMOH) – including the TTI, BIP-8[1..n], DMti, BDI and BEI[1..n] signals – in a selected TCMOH field from the ODU signal at its ODU\_TCP, detects for AIS, OCI, LCK, TIM, DEG and BDI defects, counts during one-second periods errors (detected via the BIP-8), counts numbers of frames for delay measurement and defects to feed performance monitoring when it is OPERATIONAL or MONITOR. The ODUCn signal has n TCM overhead fields per TCM level; the ODUk signal has one (n = 1) TCM overhead field per TCM level. + +The information flow and processing of the ODUT\_TT\_Sk function is defined with reference to Figures 14-117 and 14-118. + +## Symbol + +![Figure 14-117 shows two symbols for the ODUT_TT_Sk function. The left symbol is for ODUKT and the right is for ODUCnT. Both are represented by a triangle pointing downwards. Inputs from the bottom are ODUk_TCP (left) and ODUCn_TCP (right). Inputs from the left are ODUkT_TT_Sk_MP (left) and ODUCnT_TT_Sk_MP (right). Inputs from the right are ODUkT_TT_Sk_TCMCP (left) and ODUCnT_TT_Sk_TCMCP (right). Outputs to the top are ODUkT_AP (left) and ODUCnT_AP (right). Outputs to the right are ODUkT_RP (left) and ODUCnT_RP (right). A note 'k = 0, 1, 2, 2e, 3, 4, flex' is present near the left symbol. A reference 'G.798(17)_F14-117' is present near the right symbol.](06ab63c9cae7ba781705155c8911f0b7_img.jpg) + +Figure 14-117 shows two symbols for the ODUT\_TT\_Sk function. The left symbol is for ODUKT and the right is for ODUCnT. Both are represented by a triangle pointing downwards. Inputs from the bottom are ODUk\_TCP (left) and ODUCn\_TCP (right). Inputs from the left are ODUkT\_TT\_Sk\_MP (left) and ODUCnT\_TT\_Sk\_MP (right). Inputs from the right are ODUkT\_TT\_Sk\_TCMCP (left) and ODUCnT\_TT\_Sk\_TCMCP (right). Outputs to the top are ODUkT\_AP (left) and ODUCnT\_AP (right). Outputs to the right are ODUkT\_RP (left) and ODUCnT\_RP (right). A note 'k = 0, 1, 2, 2e, 3, 4, flex' is present near the left symbol. A reference 'G.798(17)\_F14-117' is present near the right symbol. + +Figure 14-117 – ODUT\_TT\_Sk function + +## Interfaces + +Table 14-54 – ODUT\_TT\_Sk inputs and outputs + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODU_TCP:
ODU_CI_CK
ODU_CI_D
ODU_CI_FS
ODU_CI_MFS
ODU_CI_SSF
ODU_CI_RP
ODU_CI_TSCC
ODUT_TT_Sk_MP:
ODUT_TT_Sk_MI_ExSAPI
ODUT_TT_Sk_MI_ExDAPI
ODUT_TT_Sk_MI_GetAcTI
ODUT_TT_Sk_MI_TIMDetMo
ODUT_TT_Sk_MI_TIMActDis
ODUT_TT_Sk_MI_DEGThr
ODUT_TT_Sk_MI_DEGM
ODUT_TT_Sk_MI_1second
ODUT_TT_Sk_MI_DM_Source
ODUT_TT_Sk_MI_DMValue
ODUT_TT_Sk_MI_LTCAct_Enable
ODUT_TT_Sk_TCMCP:
ODUT_TT_Sk_TCMCI_Mode
ODUT_TT_Sk_TCMCI_Level | ODUT_AP:
ODUT_AI_CK
ODUT_AI_D
ODUT_AI_FS
ODUT_AI_MFS
ODUT_AI_TSF
ODUT_AI_TSD
ODUT_AI_AIS
ODUT_AI_RP
ODUT_AI_TSCC
ODUT_RP:
ODUT_RI_BDI
ODUT_RI_BEI[1..n]
ODUT_RI_BIAE
ODUT_RI_DM
ODUT_TT_Sk_MP:
ODUT_TT_Sk_MI_AcTI
ODUT_TT_Sk_MI_cOCI (Note)
ODUT_TT_Sk_MI_cLCK
ODUT_TT_Sk_MI_cLTC
ODUT_TT_Sk_MI_cTIM
ODUT_TT_Sk_MI_cDEG
ODUT_TT_Sk_MI_cBDI
ODUT_TT_Sk_MI_cSSF
ODUT_TT_Sk_MI_pN_EBC
ODUT_TT_Sk_MI_pN_DS
ODUT_TT_Sk_MI_pF_EBC
ODUT_TT_Sk_MI_pF_DS
ODUT_TT_Sk_MI_pBIAE
ODUT_TT_Sk_MI_pIAE
ODUT_TT_Sk_MI_pN_delay | +| NOTE – For ODUKT_TT_Sk only. | | + +## Processes + +The processes associated with the ODUT\_TT\_Sk function are as depicted in Figure 14-118. + +**Mode:** If the TCMCI\_Mode has the value OPERATIONAL or MONITOR, the following processes shall be performed. TCMCI\_Mode OPERATIONAL initiates the consequent actions aAIS, aTSF and aTSD, in case of defects. TCMCI\_Mode MONITOR does not initiate the consequent actions aAIS, aTSF and aTSD in case of defects. If the TCMCI\_Mode has the value TRANSPARENT, all information shall be passed through transparently and the following processes shall not be performed. + +**TCMOH-BIP-8:** If the TCMCI\_Mode has the value OPERATIONAL or MONITOR, the BIP-8[1..n] shall be processed as defined in clause 8.3.4.2. The BIP-8[1..n] is extracted from the BIP-8 byte of the TCM[TCMCI\_Level] fields in the n TCM overhead instances of the ODU signal at the ODU\_TCP. + +**TCMOH-TTI:** If the TCMCI\_Mode has the value OPERATIONAL or MONITOR, the trail trace identifier shall be recovered from the TTI byte position of the TCM[TCMCI\_Level] field in the first ODU overhead instance of the ODU signal at the ODU\_TCP as specified in clause 8.6. The accepted value of the TTI is available at the MP (MI\_AcTI). + +**TCMOH-BDI:** If the TCMCI\_Mode has the value OPERATIONAL or MONITOR, the backward defect indication shall be recovered from the BDI bit position of the TCM[TCMCI\_Level] field in the first ODU overhead instance of the ODU signal at the ODU\_TCP. It shall be used for BDI defect detection. + +**TCMOH-BEI/BIAE:** If the TCMCI\_Mode has the value OPERATIONAL or MONITOR, the BEI[1..n] shall be recovered from the BEI/BIAE bits in the TCM[TCMCI\_Level] field of the n TCM overhead instances in the ODU signal at the ODU\_TCP. It shall be used to determine if a far-end errored block (nF\_B) has occurred. One nF\_B has occurred per BEI/BIAE[i] value between 1 [0001] and 8 [1000]; otherwise, no nF\_B has occurred. The BEI/BIAE information is also used for BIAE defect detection. + +**TCMOH-STAT:** If the TCMCI\_Mode has the value OPERATIONAL or MONITOR, the status information shall be recovered from the STAT bits in the TCM[TCMCI\_Level] field in the first ODU overhead instance of the ODU signal at the ODU\_TCP as defined in clause 8.8 (→ AcSTAT). It shall be used for AIS, OCI, LCK, LTC and IAE defect detection. + +NOTE 2 – During incoming frame jump events of the TCM-Trail, transient defects may trigger cases where wrong bytes are read and accepted under particular conditions for STAT byte processing. These wrong bytes may lead to transient consequent actions which are neither visible in alarming (due to F4 filtering) nor in performance monitoring (due to the use of the IAE defect to suppress wrong PM data (EBC and DS)). Such possible transient consequent action could also lead to cases where a high number of subsequent NEs could be affected by the frame jump in such TCM trails (for example triggering a protection switch). The classical defined means to overcome such switch on transient defect conditions is the use of an appropriate hold-off time. + +**TCMOH-DMti:** If the TCMCI\_Mode has the value OPERATIONAL and if MI\_DM\_Source is false then the value of the incoming DMti bit (RxDMti) is output to RI\_DM. If MI\_DM\_Source is true and MI\_DMValue toggles, then a count of CI\_FS transitions is started and the RxDMti value is monitored. A change of value of RxDMti, from (NOT MI\_DMValue) to MI\_DMValue, validated by a 3 frame persistency check, stops the counting. The delay frame count (nN\_delay) is represented by the count minus the persistency check. + +NOTE 3 – Equipment developed prior to Edition 4.0 of this Recommendation will not support DMti processing. + +![Figure 14-118 – ODUT_TT_Sk processes. This is a complex block diagram showing the internal processes of an ODUT_TT_Sk. At the top, the 'ODUT_AP' layer has inputs AI_TSCC, AI_RP, AI_TSD, AI_TSF, AI_AIS, AI_MFS, AI_FS, AI_CK, and AI_D. Below this is the 'ODUT_TT_Sk_MP' layer containing several functional blocks: 'Process TTI' (handling MI_TTIMActDis, MI_ExSAPI, MI_ExDAPI, MI_TIMDetMo, MI_GetAcTI, MI_AcTI, dTIM, RxTI), 'Defect correlation' (handling MI_cTIM, MI_cDEG, MI_cBDI, MI_cLTC, MI_cLCK, MI_cOCI, MI_cSSF, dTIM, dDEG, dBDCI, dLTC, dLCK, dOCI, dAIS, CI_SSF), 'Process DMti' (handling MI_DM_Source, MI_DMValue, nN_delay, RxDMti), 'Performance monitoring' (handling MI_pN_Delay, MI_1second, MI_pF_DS, MI_pBIAE, MI_pF_EBC, aTSF, dIAE, nN_B), 'Process errors' (handling MI_DEGThr, MI_DEGM, dDEG), 'Extract TTI', 'Extract STAT', 'Extract DMti', 'Extract BDI', 'Extract BEI/BIAE', 'Extract BIP-8', and 'Compute BIP-8'. A central 'Consequent actions' block receives inputs from various processes and outputs aTSD, aTSF, aAIS, dDEG, dLCK, dOCI, dAIS, dIAE, dLTC, and CI_SSF. A vertical 'TCM[TCMCI_Level] OH access' block on the right interacts with 'Extract STAT', 'Extract DMti', 'Extract BDI', 'Extract BEI/BIAE', and 'Compute BIP-8'. At the bottom, the 'ODU_TCP' layer has inputs CI_TSCC, CI_RP, CI_SSF, CI_MFS, CI_FS, CI_CK, and CI_D. Various signals like nBIPV[1..n], RxDMti, dBDI, dBIAE, nF_B, nN_B, and nN_delay are shown between blocks. External interfaces on the left are labeled ODUT_RP and ODUT_TT_Sk_MP, and on the right are ODUT_TT_Sk_TCMCP and TCMCI_Mode/Level.](793b6344c79e3e858d29ef190b2c014f_img.jpg) + +Figure 14-118 – ODUT\_TT\_Sk processes. This is a complex block diagram showing the internal processes of an ODUT\_TT\_Sk. At the top, the 'ODUT\_AP' layer has inputs AI\_TSCC, AI\_RP, AI\_TSD, AI\_TSF, AI\_AIS, AI\_MFS, AI\_FS, AI\_CK, and AI\_D. Below this is the 'ODUT\_TT\_Sk\_MP' layer containing several functional blocks: 'Process TTI' (handling MI\_TTIMActDis, MI\_ExSAPI, MI\_ExDAPI, MI\_TIMDetMo, MI\_GetAcTI, MI\_AcTI, dTIM, RxTI), 'Defect correlation' (handling MI\_cTIM, MI\_cDEG, MI\_cBDI, MI\_cLTC, MI\_cLCK, MI\_cOCI, MI\_cSSF, dTIM, dDEG, dBDCI, dLTC, dLCK, dOCI, dAIS, CI\_SSF), 'Process DMti' (handling MI\_DM\_Source, MI\_DMValue, nN\_delay, RxDMti), 'Performance monitoring' (handling MI\_pN\_Delay, MI\_1second, MI\_pF\_DS, MI\_pBIAE, MI\_pF\_EBC, aTSF, dIAE, nN\_B), 'Process errors' (handling MI\_DEGThr, MI\_DEGM, dDEG), 'Extract TTI', 'Extract STAT', 'Extract DMti', 'Extract BDI', 'Extract BEI/BIAE', 'Extract BIP-8', and 'Compute BIP-8'. A central 'Consequent actions' block receives inputs from various processes and outputs aTSD, aTSF, aAIS, dDEG, dLCK, dOCI, dAIS, dIAE, dLTC, and CI\_SSF. A vertical 'TCM[TCMCI\_Level] OH access' block on the right interacts with 'Extract STAT', 'Extract DMti', 'Extract BDI', 'Extract BEI/BIAE', and 'Compute BIP-8'. At the bottom, the 'ODU\_TCP' layer has inputs CI\_TSCC, CI\_RP, CI\_SSF, CI\_MFS, CI\_FS, CI\_CK, and CI\_D. Various signals like nBIPV[1..n], RxDMti, dBDI, dBIAE, nF\_B, nN\_B, and nN\_delay are shown between blocks. External interfaces on the left are labeled ODUT\_RP and ODUT\_TT\_Sk\_MP, and on the right are ODUT\_TT\_Sk\_TCMCP and TCMCI\_Mode/Level. + +Figure 14-118 – ODUT\_TT\_Sk processes + +### Defects + +If the TCMCI\_Mode has the value OPERATIONAL or MONITOR, the function shall detect dLTC, dAIS, dOCI, dLCK, dTIM, dDEG, dIAE, dBIAE and dBDCI defects. If the TCMCI\_Mode is TRANSPARENT, all defects are cleared. + +**dLTC:** See clause 6.2.1.5.1; dLTC shall be set to false during CI\_SSF. + +**dAIS:** See clause 6.2.6.3.2. + +**dOCI:** For ODUk, see clause 6.2.6.8.2; dOCI shall be set to false during CI\_SSF. For ODUCn dOCI shall be assumed false. + +**dLCK:** See clause 6.2.6.9.1; dLCK shall be set to false during CI\_SSF. + +**dTIM:** See clause 6.2.2.1; dTIM shall be set to false during CI\_SSF and dAIS. + +**dDEG:** See clause 6.2.3.4. + +NOTE 4 – IAE suppresses the one-second near-end errored block count, which is the input for the dDEG detection. This avoids wrong dDEG declaration due to alignment errors already incoming in an OTUk trail. + +**dBIDI:** See clause 6.2.6.6.1; dBIDI shall be set to false during CI\_SSF and dAIS. + +**dIAE:** See clause 6.2.6.10.2; dIAE shall be set to false during CI\_SSF, dAIS and dTIM. + +**dBIAE:** See clause 6.2.6.11.1; dBIAE shall be set to false during CI\_SSF, dAIS and dTIM. + +### Consequent actions + +The function shall perform the following consequent actions (see clause 6.3 of [ITU-T G.806]): + +aBDI        ←        (CI\_SSF or dAIS or dLTC or dOCI or dLCK or dTIM) and TCMCI\_Mode +                          ≠ TRANSPARENT + +aBIAE      ←        dIAE and TCMCI\_Mode ≠ TRANSPARENT + +aTSF        ←        CI\_SSF or ((dAIS or (dLTC and LTCAct\_Enable) or dOCI or dLCK or (dTIM +                          and (not TIMActDis)))) and TCMCI\_Mode == OPERATIONAL + +aTSD        ←        dDEG and TCMCI\_Mode == OPERATIONAL + +aAIS        ←        (dOCI or (dLTC and LTCAct\_Enable) or dLCK or (dTIM and +                          (not TIMActDis))) and TCMCI\_Mode == OPERATIONAL + +For each TCM[TCMCI\_Level] overhead instance #i: + +aBEI[i]      ←        nBIPV[i] and TCMCI\_Mode ≠ TRANSPARENT + +NOTE 5 – Equipment prior to Edition 4.2 of this Recommendation will not execute aAIS consequent action in the case of dLTC. + +NOTE 6 – The default value for MI\_LTCAct\_Enable is to be set to "false" to ensure that an upgrade in the network does not cause unexpected traffic affecting consequent action execution in existing network implementations. + +### Defect correlations + +The function shall perform the following defect correlations to determine the most probable fault cause (see clause 6.4 of [ITU-T G.806]). This fault cause shall be reported to the EMF. + +cSSF        ←        CI\_SSF or dAIS + +cLTC        ←        dLTC and (not CI\_SSF) + +cOCI        ←        dOCI and (not CI\_SSF) + +cLCK        ←        dLCK and (not CI\_SSF) + +cTIM        ←        dTIM and (not CI\_SSF) and (not dAIS) and (not dLTC) and (not dOCI) and +                          (not dLCK) + +cDEG        ←        dDEG and (not CI\_SSF) and (not dAIS) and (not dLTC) and (not dOCI) and +                          (not dLCK) and (not (dTIM and (not TIMActDis)))) + +cBDI        ←        dBIDI and (not CI\_SSF) and (not dAIS) and (not dLTC) and (not dOCI) and +                          (not dLCK) and (not (dTIM and (not TIMActDis)))) + +### Performance monitoring + +If the TCMCI\_Mode has the value OPERATIONAL or MONITOR, the function shall perform the following performance monitoring primitives processing (see clause 6.5 of [ITU-T G.806]). The performance monitoring primitives shall be reported to the EMF. + +$pN\_DS \leftarrow$ CI\_SSF or dAIS or dLTC or dOCI or dLCK or dTIM + +$pF\_DS \leftarrow$ dBDI + +$pN\_EBC \leftarrow \sum nN\_B$ + +NOTE 7 – During CI\_SSF, dAIS, dLTC, dLCK and dOCI, no errored blocks shall be counted. + +$pF\_EBC \leftarrow \sum nF\_B$ + +NOTE 8 – During CI\_SSF, dAIS, dLTC, dLCK and dOCI, no errored blocks shall be counted. + +$pBIAE \leftarrow$ dBIAE + +NOTE 9 – pBIAE is activated at the end of a second if dBIAE was active once during the second. + +$pIAE \leftarrow$ dIAE + +NOTE 10 – pIAE is activated at the end of a second if dIAE was active once during the second. + +NOTE 11 – pIAE and pBIAE are used for the suppression of the PM data in the equipment management functions (see [ITU-T G.874]). If pBIAE is active, the F\_DS and F\_EBC values of the previous and current second have to be discarded (EBC = 0 and DS = false). If pIAE is active, the N/F\_DS and N/F\_EBC values of the previous and current second have to be discarded (EBC = 0 and DS = false). The previous second has to be included due to the delay of the IAE information coming from the remote source. + +$pN\_delay \leftarrow nN\_delay$ + +NOTE 12 – This count is triggered by the ODUT\_TT\_Sk\_MI\_DMValue toggle event, which is equal to the ODUT\_TT\_So\_MI\_DMValue toggle event. + +NOTE 13 – This value is a snapshot value. + +NOTE 14 – This value is invalid if a STAT field indicating AIS, OCI, LCK, LTC, or BDI is received during the measurement. + +#### 14.5.1.1.3 ODUT non-intrusive monitoring function (ODUTm\_TT\_Sk) + +The ODUTm\_TT\_Sk function reports the state of the ODU monitored tandem connection. It computes the BIP-8[1..n], extracts tandem connection monitoring overhead (TCMOH) – including the TTI, BIP-8[1..n], BDI and BEI[1..n] signals – in a selected TCMOH field from the ODU signal at its ODU\_TCP, detects for AIS, OCI, LCK, TIM, DEG and BDI defects, counts during one-second periods errors (detected via the BIP-8) and defects to feed performance monitoring. The ODUCn signal has n TCM overhead fields per TCM level; the ODUK signal has one ( $n = 1$ ) TCM overhead field per TCM level. + +For ODUT non-intrusive monitoring, the ODUTm\_TT\_Sk function can be connected to the ODU\_CPs as shown in Figure 14-119. The ODUTm\_TT\_Sk function can be connected to any ODU\_CP in this manner, either directly or via a connection function. + +The TSF and TSD outputs of an ODUKT non-intrusive monitor can be connected to an ODU\_C connection function and used as protection switching trigger criteria for SNC/N protection; for an ODUCnP non-intrusive monitor the TSF and TSD output are left open. + +![Figure 14-119: Connection of ODUTm_TT_Sk function (non-intrusive monitor).](40b685b3ae31d84f5f9edf37cbb945bb_img.jpg) + +This diagram illustrates the non-intrusive monitoring architecture for OTN. It features two parallel processing paths. The left path is for ODUk, and the right path is for ODUCn. In the ODUk path, data flows from an ODUkT/ODUk client through an ODUkT section, then through an ODUkT/ODUk section, and finally into a central ODUk multiplexing node. Monitoring points (ODUk\_TT\_Sk\_MP) are located at the input and output of the ODUkT/ODUk sections. The ODUkT section also receives a reference point (ODUkT\_RP) from the ODUkT section. The ODUk multiplexing node is connected to four ODUkTm monitoring blocks, which are further connected to TSF TSD blocks. The ODUCn path follows a similar structure but uses ODUCnT and ODUCnT/ODUCn components. The diagram is labeled G.798(17)\_F14-119. + +Figure 14-119: Connection of ODUTm\_TT\_Sk function (non-intrusive monitor). + +**Figure 14-119 – Connection of ODUTm\_TT\_Sk function (non-intrusive monitor)** + +The information flow and processing of the ODUTm\_TT\_Sk function is defined with reference to Figures 14-120 and 14-121. + +**Symbol** + +![Figure 14-120: ODUTm_TT_Sk function symbol.](2ffdb0621c4918479cd1ac7a531b1b92_img.jpg) + +This diagram shows the functional symbol for the ODUTm\_TT\_Sk function. It consists of two mirrored symbols. The left symbol is for ODUk, with an input labeled ODUk\_TCP at the bottom, a central triangle labeled ODUkTm, an output labeled ODUk\_AP at the top, and a monitoring point labeled ODUk\_TT\_Sk\_MP on the left. Below the triangle, it specifies 'k = 0, 1, 2, 2e, 3, 4, flex'. The right symbol is for ODUCn, with an input labeled ODUCn\_TCP at the bottom, a central triangle labeled ODUCnTm, an output labeled ODUCn\_AP at the top, and a monitoring point labeled ODUCnT\_TT\_Sk\_MP on the left. The diagram is labeled G.798(17)\_F14-120. + +Figure 14-120: ODUTm\_TT\_Sk function symbol. + +**Figure 14-120 – ODUTm\_TT\_Sk function** + +## Interfaces + +**Table 14-55 – ODUTm\_TT\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODU_CP:
ODU_CI_CK
ODU_CI_D
ODU_CI_FS
ODU_CI_MFS
ODU_CI_SSF
ODUTm_TT_Sk_MP:
ODUTm_TT_Sk_MI_Level
ODUTm_TT_Sk_MI_ExSAPI
ODUTm_TT_Sk_MI_ExDAPI
ODUTm_TT_Sk_MI_GetAcTI
ODUTm_TT_Sk_MI_TIMDetMo
ODUTm_TT_Sk_MI_TIMActDis
ODUTm_TT_Sk_MI_DEGThr
ODUTm_TT_Sk_MI_DEGM
ODUTm_TT_Sk_MI_1second | ODUT_AP:
ODUT_AI_TSF
ODUT_AI_TSD
ODUTm_TT_Sk_MP:
ODUTm_TT_Sk_MI_AcTI
ODUTm_TT_Sk_MI_cOCI (Note)
ODUTm_TT_Sk_MI_cLCK
ODUTm_TT_Sk_MI_cLTC
ODUTm_TT_Sk_MI_cTIM
ODUTm_TT_Sk_MI_cDEG
ODUTm_TT_Sk_MI_cBDI
ODUTm_TT_Sk_MI_cSSF
ODUTm_TT_Sk_MI_pN_EBC
ODUTm_TT_Sk_MI_pN_DS
ODUTm_TT_Sk_MI_pF_EBC
ODUTm_TT_Sk_MI_pF_DS
ODUTm_TT_Sk_MI_pBIAE
ODUTm_TT_Sk_MI_pIAE | +| NOTE – For ODUkTm_TT_Sk only. | | + +## Processes + +The processes associated with the ODUTm\_TT\_Sk function are as depicted in Figure 14-121. + +**TCMOH-BIP-8:** The BIP-8[1..n] shall be processed as defined in clause 8.3.4. The BIP-8[1..n] is extracted from the BIP-8 byte of the TCM[MI\_Level] fields in the n TCM overhead instances of the ODU signal at the ODU\_TCP. + +**TCMOH-TTI:** The trail trace identifier shall be recovered from the TTI byte position of the TCM[MI\_Level] field in the first ODU overhead instance of the ODU signal at the ODU\_TCP as specified in clause 8.6. The accepted value of the TTI is available at the MP (MI\_AcTI). + +**TCMOH-BDI:** The backward defect indication shall be recovered from the BDI bit position of the TCM[MI\_Level] field in the first ODU overhead instance of the ODU signal at the ODU\_TCP. It shall be used for BDI defect detection. + +**TCMOH-BEI/BIAE:** The BEI[1..n] shall be recovered from the BEI/BIAE bits in the TCM[MI\_Level] field of the n TCM overhead instances in the ODU signal at the ODU\_TCP. It shall be used to determine if a far-end errored block (nF\_B) has occurred. One nF\_B has occurred per BEI/BIAE[i] value is between 1 [0001] and 8 [1000]; otherwise, no nF\_B has occurred. The BEI/BIAE information is also used for BIAE defect detection. + +**TCMOH-STAT:** The status information shall be recovered from the STAT bits in the TCM[MI\_Level] field in the first ODU overhead instance of the ODU signal at the ODU\_TCP as defined in clause 8.8 (→ AcSTAT). It shall be used for AIS, OCI, LCK, LTC and IAE defect detection. + +![Block diagram of ODUTm_TT_Sk_MP processes showing internal components and their interactions with ODUT_AP and ODU_CP.](ea6b9ace0ed0694c2ce8dcdb8b5ea52b_img.jpg) + +The diagram illustrates the internal architecture of the ODUTm\_TT\_Sk\_MP process. It is divided into several functional blocks: + +- Process TTI:** Receives inputs MI\_TIMActDis, MI\_ExSAPI, MI\_ExDAPI, MI\_TIMDetMo, MI\_GetAcTI, and MI\_AcTI. It outputs dTIM and RxTI. RxTI is sent to 'Extract TTI' and also to 'Defect correlations'. +- Defect correlations:** Receives dTIM, RxTI, and various defect signals (dDEG, dLCK, dOCI, dAIS, dLTC, CI\_SSF). It outputs a set of defect signals (dTIM, dDEG, dBDI, dLTC, dLCK, dOCI, dAIS, CI\_SSF) to 'Process STAT'. +- Process STAT:** Receives defect signals from 'Defect correlations' and outputs dIAE, dLTC, dLCK, dOCI, and dAIS to 'Extract STAT'. +- Extract STAT:** Receives signals from 'Process STAT' and interacts with 'TCM[MI\_level] OH access'. +- Performance monitoring:** Receives MI\_Level, MI\_1second, MI\_pF\_DS, MI\_pBIAE, MI\_pF\_EBC, MI\_pN\_DS, MI\_pIAE, and MI\_pN\_EBC. It outputs dBDI, dBIAE, nF\_B, aTSF, dIAE, nN\_B, and nBIPV[1..n]. +- Extract BDI:** Receives dBDI from 'Performance monitoring' and interacts with 'TCM[MI\_level] OH access'. +- Extract BEI/BIAE:** Receives dBIAE and nF\_B from 'Performance monitoring' and interacts with 'TCM[MI\_level] OH access'. +- Extract BIP-8:** Receives nN\_B from 'Performance monitoring' and interacts with 'TCM[MI\_level] OH access'. +- Compute BIP-8:** Receives nBIPV[1..n] from 'Performance monitoring' and interacts with 'TCM[MI\_level] OH access'. +- Compare:** Receives nBIPV[1..n] from 'Performance monitoring' and nN\_B from 'Extract BIP-8'. It outputs dDEG to 'Process errors'. +- Process errors:** Receives MI\_DEGThr, MI\_DEGM, and dDEG from 'Compare'. It outputs aTSD and aTSF to 'Consequent actions'. +- Consequent actions:** Receives aTSD and aTSF from 'Process errors' and outputs AI\_TSD and AI\_TSF to the top. +- TCM[MI\_level] OH access:** A central vertical block that interacts with 'Extract TTI', 'Extract STAT', 'Extract BDI', 'Extract BEI/BIAE', 'Extract BIP-8', and 'Compute BIP-8'. + +External interfaces include ODUT\_AP (AI\_TSD, AI\_TSF) at the top and ODU\_CP (CI\_SSF, CI\_MFS, CI\_FS, CI\_CK, CI\_D) at the bottom. + +Block diagram of ODUTm\_TT\_Sk\_MP processes showing internal components and their interactions with ODUT\_AP and ODU\_CP. + +G.798(17)\_F14-121 + +Figure 14-121 – ODUTm\_TT\_Sk processes + +### Defects + +The function shall detect dLTC, dAIS, dOCI, dLCK, dTIM, dDEG, dIAE, dBIAE and dBDI defects. + +**dLTC:** See clause 6.2.1.5.1; dLTC shall be set to false during CI\_SSF. + +**dAIS:** See clause 6.2.6.3.2. + +**dOCI:** For ODUk, see clause 6.2.6.8.2; dOCI shall be set to false during CI\_SSF. For ODUCn dOCI shall be assumed false. + +**dLCK:** See clause 6.2.6.9.1; dLCK shall be set to false during CI\_SSF. + +**dTIM:** See clause 6.2.2.1; dTIM shall be set to false during CI\_SSF and dAIS. + +**dDEG:** See clause 6.2.3.4. + +NOTE 1 – IAE suppresses the one-second near-end errored block count, which is the input for the dDEG detection. This avoids wrong dDEG declaration due to alignment errors already incoming in an OTUk trail. + +**dBDI:** See clause 6.2.6.6.1; dBDI shall be set to false during CI\_SSF and dAIS. + +**dIAE:** See clause 6.2.6.10.2; dIAE shall be set to false during CI\_SSF, dAIS and dTIM. + +**dBIAE:** See clause 6.2.6.11.1; dBIAE shall be set to false during CI\_SSF, dAIS and dTIM. + +### Consequent actions + +The function shall perform the following consequent actions (see clause 6.3 of [ITU-T G.806]): + +aTSF $\leftarrow$ CI\_SSF or (dAIS or dLTC or dOCI or dLCK or (dTIM and (not TIMActDis)))) + +aTSD $\leftarrow$ dDEG + +### Defect correlations + +The function shall perform the following defect correlations to determine the most probable fault cause (see clause 6.4 of [ITU-T G.806]). This fault cause shall be reported to the EMF. + +cSSF $\leftarrow$ CI\_SSF or dAIS + +cLTC $\leftarrow$ dLTC and (not CI\_SSF) + +cOCI $\leftarrow$ dOCI and (not CI\_SSF) + +cLCK $\leftarrow$ dLCK and (not CI\_SSF) + +cTIM $\leftarrow$ dTIM and (not CI\_SSF) and (not dAIS) and (not dLTC) and (not dOCI) and (not dLCK) + +cDEG $\leftarrow$ dDEG and (not CI\_SSF) and (not dAIS) and (not dLTC) and (not dOCI) and (not dLCK) and (not (dTIM and (not TIMActDis)))) + +cBDI $\leftarrow$ dBDI and (not CI\_SSF) and (not dAIS) and (not dLTC) and (not dOCI) and (not dLCK) and (not (dTIM and (not TIMActDis)))) + +### Performance monitoring + +The function shall perform the following performance monitoring primitives processing (see clause 6.5 of [ITU-T G.806]). The performance monitoring primitives shall be reported to the EMF. + +pN\_DS $\leftarrow$ CI\_SSF or (dAIS or dLTC or dOCI or dLCK or dTIM) + +pF\_DS $\leftarrow$ dBDI + +pN\_EBC $\leftarrow \sum nN\_B$ + +NOTE 3 – During CI\_SSF, dAIS, dLTC, dLCK and dOCI, no errored blocks shall be counted. + +pF\_EBC $\leftarrow \sum nF\_B$ + +NOTE 4 – During CI\_SSF, dAIS, dLTC, dLCK and dOCI, no errored blocks shall be counted. + +pBIAE $\leftarrow$ dBIAE + +NOTE 5 – pBIAE is activated at the end of the second if dBIAE was active once during the second. + +pIAE $\leftarrow$ dIAE + +NOTE 6 – pIAE is activated at the end of the second if dIAE was active once during the second. + +NOTE 7 – pIAE and pBIAE are used for the suppression of the PM data in the equipment management functions (see [ITU-T G.874]). If pBIAE is active, the F\_DS and F\_EBC values of the previous and current second have to be discarded (EBC = 0 and DS = false). If pIAE is active, the N/F\_DS and N/F\_EBC values of the previous and current second have to be discarded (EBC = 0 and DS = false). The previous second has to be included due to the delay of the IAE information coming from the remote source. + +#### 14.5.1.2 ODUT to ODU adaptation function (ODUT/ODU\_A) + +The ODUT/ODU\_A function starts and ends a selected TCM level if it is OPERATIONAL. + +Furthermore, the ODUT/ODU\_A function provides access to the TCM status information in the ODU overhead over the TCM control point (TCMCP) for the tandem connection monitor control (TCMC) function that can be connected to an ODUT/ODU\_A. + +##### 14.5.1.2.1 ODUT to ODU adaptation source function (ODUT/ODU\_A\_So) + +The ODUT/ODU\_A\_So function starts a selected TCM level and can initiate maintenance signals (LCK) if it is OPERATIONAL. + +Furthermore, the ODUT/ODU\_A\_So function provides access to the TCM status information in the ODU overhead over the TCMCP for the TCMC function that can be connected to an ODUT/ODU\_A. Additionally, the ODUkT/ODUk\_A\_So provides access to the ODUk TCM APS overhead. + +The information flow and processing of the ODUT/ODU\_A\_So function is defined with reference to Figures 14-122 and 14-123. + +#### Symbol + +![Diagram of ODUT/ODU_A_So function symbols for ODUk and ODUCn levels.](6d7989325053731fda7ae4de0e946b24_img.jpg) + +The diagram illustrates two functional blocks for the ODUT/ODU\_A\_So function. The top block is for the ODUk level, represented by a trapezoidal symbol labeled 'ODUkT/ODUk'. It has four input/output points: 'ODUk\_CP' at the top, 'ODUkT/ODUk\_A\_So\_MP' on the left, 'ODUkT/ODUk\_A\_So\_TCMCP' on the right, and 'ODUkT\_AP' at the bottom. The bottom output is labeled with 'k = 0, 1, 2, 2e, 3, 4, flex'. The bottom block is for the ODUCn level, represented by a similar trapezoidal symbol labeled 'ODUCnT/ODUCn'. It has four input/output points: 'ODUCn\_CP' at the top, 'ODUCnT/ODUCn\_A\_So\_MP' on the left, 'ODUCnT/ODUCn\_A\_So\_TCMCP' on the right, and 'ODUCnT\_AP' at the bottom. + +Diagram of ODUT/ODU\_A\_So function symbols for ODUk and ODUCn levels. + +G.798(17)\_F14-122 + +Figure 14-122 – ODUT/ODU\_A\_So function + +## Interfaces + +**Table 14-56 – ODUT/ODU\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODU_CP:
ODU_CI_CK
ODU_CI_D
ODU_CI_FS
ODU_CI_MFS
ODU_CI_RP
ODU_CI_TSCC
ODUT_PP:
ODU_PI_APS (Note)
ODUT/ODU_A_So_MP:
ODUT/ODU_A_So_MI_AdminState
ODUT/ODU_A_So_TCMCP:
ODUT/ODU_A_So_TCMCI_Mode
ODUT/ODU_A_So_TCMCI_Level | ODUT_AP:
ODUT_AI_CK
ODUT_AI_D
ODUT_AI_FS
ODUT_AI_MFS
ODUT_AI_RP
ODUT_AI_TSCC
ODUT/ODU_A_So_TCMCP:
ODUT/ODU_A_So_TCMCI_AcSTAT[1..6] | +| NOTE – For ODUkT/ODUk_A_So only. | | + +## Processes + +The processes associated with the ODUT/ODU\_A\_So function are as depicted in Figure 14-123. + +**TCMOH-STAT Rx:** The status of all six TCM levels is recovered from the TCM OH [1..6] STAT field and provided to the TCM control function via TCMCI\_STAT[1..6]. For the STAT acceptance process, see clause 8.8. + +**ODU-LCK:** The function shall generate the ODU-LCK signal as defined in clause 16.5 of [ITU-T G.709]. The clock, frame start and multiframe start are defined by the incoming ODU signal. + +**Mode:** If the TCMCI\_Mode has the value OPERATIONAL, the following processes shall be performed. If the TCMCI\_Mode has the value TRANSPARENT, all information shall be passed through transparently and the following processes shall not be performed. + +**IAE:** If the incoming ODU frame start (CI\_FS) position is not at the expected frame start position, incoming alignment error (IAE) shall be activated. IAE shall be deactivated if the incoming ODU frame start (CI\_FS) position is at the expected frame start position. The expected frame start position is based on the previous incoming ODU frame start. + +**Selector:** If TCMCI\_Mode is OPERATIONAL, the normal signal may be replaced by the ODU-LCK signal. ODU-LCK signal is selected if the MI\_AdminState is LOCKED. + +**ODUk TCM APS:** If TCMCI\_Mode is OPERATIONAL, the ODUkT/ODUk\_S\_So function shall insert the PI\_APS value into the ODUk TCM APS/PCC[TCMCI\_Level] field, which is available once per eight ODUk frames as specified in Table 15-6 of [ITU-T G.709]. + +**TCMOH-STAT Tx:** If TCMCI\_Mode is OPERATIONAL, the TC status is inserted into the STAT bit positions of TCM OH[TCMCI\_Level] based on the incoming alignment error (IAE) information. Normally, the code "in use without IAE" (001) is inserted. Upon the declaration of IAE at this function, the function shall insert the code "in use with IAE" (010) in the STAT field for the next 16 multiframes. Each new declaration of aIAE restarts the 16-multiframe insertion time. + +**TCMOH-Others:** If TCMCI\_Mode is OPERATIONAL, all other TCM OH[TCMCI\_Level] bits are set to "0". + +![Figure 14-123 – ODUT/ODU_A_So processes. This block diagram illustrates the internal signal processing and control flow of the ODUT/ODU_A_So function. At the top, the ODU_CP (Control Plane) provides inputs: CI_D, CI_CK, CI_FS, CI_MFS, CI_RP, and CI_TSCC. CI_CK feeds into 'Generate ODU-LCK', which also receives FS and MFS. CI_RP and CI_TSCC feed into 'TCMOH[TCMCI_Level] access'. CI_D feeds into 'Normal' and 'LCK' blocks. 'Generate ODU-LCK' outputs D_LCK to 'LCK'. 'Normal' and 'LCK' feed into 'Select normal/LCK'. 'Select normal/LCK' outputs to 'TCM OH STAT Rx' and 'TCMOH[TCMCI_Level] access'. 'TCM OH STAT Rx' outputs TCMCI_AcSTAT[1..6]. 'TCMOH[TCMCI_Level] access' outputs to 'ODUk TCM APS' (labeled 'ODUkT/ODUk only') and 'STAT Tx'. 'ODUk TCM APS' outputs PI_APS. 'STAT Tx' outputs aIAE to 'IAE detection'. 'IAE detection' also receives CK, FS, MFS, RP, and TSCC. The bottom, ODUT_AP (Adaptation Plane), provides inputs: AI_D, AI_CK, AI_FS, AI_MFS, AI_RP, and AI_TSCC. AI_CK, AI_FS, AI_MFS, AI_RP, and AI_TSCC feed into 'IAE detection'. AI_D feeds into 'TCMOH[TCMCI_Level] access'. On the right, external interfaces are shown: MI_AdminState, TCMCI_AcSTAT[1..6], TCMCI_Mode, TCMCI_Level, and PI_APS. Brackets on the right label the top section as ODUT/ODU_A_So_MP and the bottom section as ODUT/ODU_A_So_TCMCP. The diagram is labeled G.798(17)_F14-123.](733da1815169d31c06238e8cd6ae23f2_img.jpg) + +Figure 14-123 – ODUT/ODU\_A\_So processes. This block diagram illustrates the internal signal processing and control flow of the ODUT/ODU\_A\_So function. At the top, the ODU\_CP (Control Plane) provides inputs: CI\_D, CI\_CK, CI\_FS, CI\_MFS, CI\_RP, and CI\_TSCC. CI\_CK feeds into 'Generate ODU-LCK', which also receives FS and MFS. CI\_RP and CI\_TSCC feed into 'TCMOH[TCMCI\_Level] access'. CI\_D feeds into 'Normal' and 'LCK' blocks. 'Generate ODU-LCK' outputs D\_LCK to 'LCK'. 'Normal' and 'LCK' feed into 'Select normal/LCK'. 'Select normal/LCK' outputs to 'TCM OH STAT Rx' and 'TCMOH[TCMCI\_Level] access'. 'TCM OH STAT Rx' outputs TCMCI\_AcSTAT[1..6]. 'TCMOH[TCMCI\_Level] access' outputs to 'ODUk TCM APS' (labeled 'ODUkT/ODUk only') and 'STAT Tx'. 'ODUk TCM APS' outputs PI\_APS. 'STAT Tx' outputs aIAE to 'IAE detection'. 'IAE detection' also receives CK, FS, MFS, RP, and TSCC. The bottom, ODUT\_AP (Adaptation Plane), provides inputs: AI\_D, AI\_CK, AI\_FS, AI\_MFS, AI\_RP, and AI\_TSCC. AI\_CK, AI\_FS, AI\_MFS, AI\_RP, and AI\_TSCC feed into 'IAE detection'. AI\_D feeds into 'TCMOH[TCMCI\_Level] access'. On the right, external interfaces are shown: MI\_AdminState, TCMCI\_AcSTAT[1..6], TCMCI\_Mode, TCMCI\_Level, and PI\_APS. Brackets on the right label the top section as ODUT/ODU\_A\_So\_MP and the bottom section as ODUT/ODU\_A\_So\_TCMCP. The diagram is labeled G.798(17)\_F14-123. + +Figure 14-123 – ODUT/ODU\_A\_So processes + +**Defects:** None. + +**Consequent actions** + +The function shall perform the following consequent actions: + +aIAE ← IAE + +**Defect correlations:** None. + +**Performance monitoring:** None. + +**14.5.1.2.2 ODUT to ODU adaptation sink function (ODUT/ODU\_A\_Sk)** + +The ODUT/ODU\_A\_Sk function ends a selected TCM level and can initiate maintenance signals (ODU-AIS, ODU-LCK) if it is OPERATIONAL. + +Furthermore, the ODUT/ODU\_A\_Sk function provides access to the TCM status information in the ODU overhead over the TCMCP for the TCMC function that can be connected to an ODUT/ODU\_A. Additionally, the ODUkT/ODUk\_A\_Sk provides access to ODUk TCM APS overhead. + +The information flow and processing of the ODUT/ODU\_A\_Sk function is defined with reference to Figures 14-124 and 14-125. + +## Symbol + +![Figure 14-124 – ODUT/ODU_A_Sk function symbol diagram. The diagram shows two identical functional blocks. The top block is labeled 'ODUKT/ODUK' and has four interfaces: 'ODUK_T_CP' (top), 'ODUKT/ODUk_A_Sk_MP' (left), 'ODUKT/ODUk_A_Sk_TCMCP' (right), and 'ODUKT_AP' (bottom). The bottom interface is labeled with 'k = 0, 1, 2, 2e, 3, 4, flex'. The bottom block is labeled 'ODUCnT/ODUCn' and has four interfaces: 'ODUCn_CP' (top), 'ODUCnT/ODUCn_A_Sk_MP' (left), 'ODUCnT/ODUCn_A_Sk_TCMCP' (right), and 'ODUCnT_AP' (bottom). Below the bottom block is the text 'G.798(17)_F14-124'.](87253027e8bb658bf7d211cb23248bcb_img.jpg) + +Figure 14-124 – ODUT/ODU\_A\_Sk function symbol diagram. The diagram shows two identical functional blocks. The top block is labeled 'ODUKT/ODUK' and has four interfaces: 'ODUK\_T\_CP' (top), 'ODUKT/ODUk\_A\_Sk\_MP' (left), 'ODUKT/ODUk\_A\_Sk\_TCMCP' (right), and 'ODUKT\_AP' (bottom). The bottom interface is labeled with 'k = 0, 1, 2, 2e, 3, 4, flex'. The bottom block is labeled 'ODUCnT/ODUCn' and has four interfaces: 'ODUCn\_CP' (top), 'ODUCnT/ODUCn\_A\_Sk\_MP' (left), 'ODUCnT/ODUCn\_A\_Sk\_TCMCP' (right), and 'ODUCnT\_AP' (bottom). Below the bottom block is the text 'G.798(17)\_F14-124'. + +Figure 14-124 – ODUT/ODU\_A\_Sk function + +## Interfaces + +Table 14-57 – ODUT/ODU\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUT_AP:
ODUT_AI_CK
ODUT_AI_D
ODUT_AI_FS
ODUT_AI_MFS
ODUT_AI_TSF
ODUT_AI_TSD
ODUT_AI_AIS
ODUT_AI_RP
ODUT_AI_TSCC
ODUT/ODU_A_Sk_MP:
ODUT/ODU_A_Sk_MI_AdminState
ODUT/ODU_A_Sk_TCMCP:
ODUT/ODU_A_Sk_TCMCI_Mode
ODUT/ODU_A_Sk_TCMCI_Level | ODU_CP:
ODU_CI_CK
ODU_CI_D
ODU_CI_FS
ODU_CI_MFS
ODU_CI_SSF
ODU_CI_SSD
ODU_CI_RP
ODU_CI_TSCC
ODUT_PP:
ODUT_PI_APS (Note)
ODUT_PI_TSF (Note)
ODUT_PI_TSD (Note)
ODUT/ODU_A_Sk_TCMCP:
ODUT/ODU_A_Sk_TCMCI_AcSTAT[1..6] | +| NOTE – For OTUk/ODUk_A_Sk only. | | + +## Processes + +The processes associated with the ODUT/ODU\_A\_Sk function are as depicted in Figure 14-125. + +**ODUk TCM APS:** If the TCMCI\_Mode has the value OPERATIONAL, the ODUkT/ODUk\_A\_Sk function shall extract the information from the ODUk TCM APS/PCC[TCMCI\_Level] field, which is available once per eight ODUk frames as specified in Table 15-6 of [ITU-T G.709] and apply this to the PI\_APS. + +**TCMOH-STAT Rx:** The status of all six TCM levels is recovered from the TCM OH [1..6] STAT field and provided to the control function via TCMCI\_AcSTAT[1..6]. For the STAT acceptance process, see clause 8.8. + +**ODU-LCK, ODU-AIS:** The function shall generate the ODU-LCK and ODU-AIS signals as defined in [ITU-T G.709]. The clock, frame start and multiframe start are defined by the incoming ODU signal. + +**Mode:** If the TCMCI\_Mode has the value OPERATIONAL, the following processes shall be performed. If the TCMCI\_Mode has the values MONITOR or TRANSPARENT, all information shall be passed through transparently and the following processes shall not be performed. + +**Selector:** If TCMCI\_Mode is OPERATIONAL, the normal signal may be replaced by either the ODU-AIS or the ODU-LCK signal. ODU-LCK signal is selected if the MI\_AdminState is LOCKED. ODU-AIS is selected if MI\_AdminState is not LOCKED and aAIS is true. If TCMCI\_Mode has the values MONITOR or TRANSPARENT, the normal signal is always selected. + +**Remove TCMOH:** If the TCMCI\_Mode has the value OPERATIONAL, an all-ZEROs pattern shall be inserted in the TCMOH and TCM APS/PCC at location TCMCI\_Level. If the TCMCI\_Mode has the values TRANSPARENT or MONITOR, the information shall be passed through transparently. + +![Figure 14-125 – ODUT/ODU_A_Sk processes. This block diagram illustrates the internal signal processing within an ODUT/ODU_A_Sk block. The block is divided into two main sections: ODUT/ODU_A_Sk_MP (top) and ODUT/ODU_A_Sk_TCMCP (bottom). Inputs on the left include MI_AdminState, TCMCI_Mode, TCMCI_Level, and TCMCI_AcSTAT[1..6]. The TCMCI_AcSTAT[1..6] input connects to a 'TCM OH STAT Rx' block. The 'ODUT/ODU_A_Sk_MP' section contains a 'Consequent actions' block that receives AI_TSD, AI_TSF, and AI_AIS signals and outputs aTSD, aTSF, and aAIS signals. The aAIS signal connects to a 'Select normal/AIS/LCK' block, which also receives D_AIS, D_LCK, and D_normal signals. The 'Select normal/AIS/LCK' block outputs RP, TSCC, MFS, FS, CK, and D signals. The 'ODUT/ODU_A_Sk_TCMCP' section contains a 'Generate ODU-AIS' block and a 'Generate ODU-LCK' block, both receiving MFS, FS, and CK signals. These blocks output D_AIS and D_LCK signals respectively. A 'Remove TCMOH[TCMCI_Level]' block receives TCMCI_Mode and TCMCI_Level signals and outputs a signal to the 'ODUk TCM APS' block. The 'ODUk TCM APS' block outputs PI_APS, PI_TSF, and PI_TSD signals. The bottom section of the diagram shows the ODUT_AP section, which receives AI_TSD, AI_TSF, AI_AIS, AI_RP, AI_TSCC, AI_MFS, AI_FS, AI_CK, and AI_D signals and outputs RP, TSCC, MFS, FS, and CK signals. The diagram is labeled G.798(17)_F14-125.](8453d7dc9225bb210abd09f5d0af3c9b_img.jpg) + +Figure 14-125 – ODUT/ODU\_A\_Sk processes. This block diagram illustrates the internal signal processing within an ODUT/ODU\_A\_Sk block. The block is divided into two main sections: ODUT/ODU\_A\_Sk\_MP (top) and ODUT/ODU\_A\_Sk\_TCMCP (bottom). Inputs on the left include MI\_AdminState, TCMCI\_Mode, TCMCI\_Level, and TCMCI\_AcSTAT[1..6]. The TCMCI\_AcSTAT[1..6] input connects to a 'TCM OH STAT Rx' block. The 'ODUT/ODU\_A\_Sk\_MP' section contains a 'Consequent actions' block that receives AI\_TSD, AI\_TSF, and AI\_AIS signals and outputs aTSD, aTSF, and aAIS signals. The aAIS signal connects to a 'Select normal/AIS/LCK' block, which also receives D\_AIS, D\_LCK, and D\_normal signals. The 'Select normal/AIS/LCK' block outputs RP, TSCC, MFS, FS, CK, and D signals. The 'ODUT/ODU\_A\_Sk\_TCMCP' section contains a 'Generate ODU-AIS' block and a 'Generate ODU-LCK' block, both receiving MFS, FS, and CK signals. These blocks output D\_AIS and D\_LCK signals respectively. A 'Remove TCMOH[TCMCI\_Level]' block receives TCMCI\_Mode and TCMCI\_Level signals and outputs a signal to the 'ODUk TCM APS' block. The 'ODUk TCM APS' block outputs PI\_APS, PI\_TSF, and PI\_TSD signals. The bottom section of the diagram shows the ODUT\_AP section, which receives AI\_TSD, AI\_TSF, AI\_AIS, AI\_RP, AI\_TSCC, AI\_MFS, AI\_FS, AI\_CK, and AI\_D signals and outputs RP, TSCC, MFS, FS, and CK signals. The diagram is labeled G.798(17)\_F14-125. + +**Figure 14-125 – ODUT/ODU\_A\_Sk processes** + +**Defects:** None. + +**Consequent actions** + +aAIS $\leftarrow$ AI\_AIS and (TCMCI\_Mode = OPERATIONAL) and +(not MI\_AdminState = LOCKED) + +aSSF $\leftarrow$ AI\_TSF and (not MI\_AdminState = LOCKED) + +aSSD $\leftarrow$ AI\_TSD and (not MI\_AdminState = LOCKED) + +On declaration of aAIS, the function shall output an ODU-AIS signal within two frames. On clearing aAIS, the ODU-AIS signal shall be removed within two frames with normal data being output. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +**14.5.1.3 ODUT TCM control functions (ODUT\_TCMC)** + +The ODUT\_TCMC functions are responsible for the activation/deactivation of a TCM trail. An ODUT\_TCMC function is connected to the ODUT\_TT and ODUT/ODU\_A functions at the TCM control points (TCMCP) as shown in Figure 14-126. + +Currently only an ODUT\_TCMC function for manual activation/deactivation via the management interface is defined. ODUT\_TCMC functions for automatic activation are for further study. + +![Diagram showing ODUT_TCMC connections for two levels: ODUT/ODUk and ODUCnT/ODUCn. Each level shows a central TCMC block connected to source (So) and sink (Sk) functions via TCMCP signals, and a management point (MP) at the bottom. The diagram is labeled G.798(17)_F14-126.](088fd744940924d37de4d237e53bb684_img.jpg) + +The diagram illustrates the connections for ODUT\_TCMC functions at two levels. The top level shows the ODUT/ODUk functions, and the bottom level shows the ODUCnT/ODUCn functions. Each level consists of a central ODUT\_TCMC (or ODUCnT\_TCMC) block connected to source (So) and sink (Sk) functions via TCM control points (TCMCP). The source functions are connected to the TCMC block via ODUT/ODUk\_A\_So\_TCMCP (or ODUCnT/ODUCn\_A\_So\_TCMCP) and ODUT\_TT\_So\_TCMCP (or ODUCnT\_TT\_So\_TCMCP) signals. The sink functions are connected via ODUT/ODUk\_A\_Sk\_TCMCP (or ODUCnT/ODUCn\_A\_Sk\_TCMCP) and ODUT\_TT\_Sk\_TCMCP (or ODUCnT\_TT\_Sk\_TCMCP) signals. A management point (MP) is also connected to each TCMC block via ODUCnT\_TCMC\_MP signals. The diagram is labeled G.798(17)\_F14-126. + +Diagram showing ODUT\_TCMC connections for two levels: ODUT/ODUk and ODUCnT/ODUCn. Each level shows a central TCMC block connected to source (So) and sink (Sk) functions via TCMCP signals, and a management point (MP) at the bottom. The diagram is labeled G.798(17)\_F14-126. + +**Figure 14-126 – ODUT\_TCMC connections** + +**14.5.1.3.1 ODUT control function for manual activation (ODUT\_TCMCm)** + +The ODUT\_TCMCm function performs manual activation/deactivation of a TCM trail via the management interface. + +The TCM status of the sink and source is provided to the management interface. The TCM level and the mode of the sink and source functions is selected by the management interface. + +The information flow and processing of the ODUT\_TCMCm function is defined with reference to Figures 14-127 and 14-128. + +## Symbol + +![Diagram showing the symbol for ODUT_TCMCm function. It consists of two rectangular blocks. The top block is labeled ODUT_TCMCm and has four external connections: ODUKT/ODUk_A_So_TCMCP (input), ODUKT_TT_So_TCMCP (input), ODUKT/ODUk_A_Sk_TCMCP (output), and ODUKT_TT_Sk_TCMCP (output). A vertical double-headed arrow labeled 'k = 0, 1, 2, 2e, 3, 4, flex' connects the top block to a bottom block labeled ODUCnT_TCMCm. The bottom block has four external connections: ODUCnT/ODUCn_A_So_TCMCP (input), ODUCnT_TT_So_TCMCP (input), ODUCnT/ODUCn_A_Sk_TCMCP (output), and ODUCnT_TT_Sk_TCMCP (output). A vertical double-headed arrow labeled 'k = 0, 1, 2, 2e, 3, 4, flex' connects the bottom block to ODUCnT_TCMCm_MP. The text G.798(17)_F14-127 is in the bottom right corner.](74c3f93d2f82f78de6a3925bb8e15977_img.jpg) + +Diagram showing the symbol for ODUT\_TCMCm function. It consists of two rectangular blocks. The top block is labeled ODUT\_TCMCm and has four external connections: ODUKT/ODUk\_A\_So\_TCMCP (input), ODUKT\_TT\_So\_TCMCP (input), ODUKT/ODUk\_A\_Sk\_TCMCP (output), and ODUKT\_TT\_Sk\_TCMCP (output). A vertical double-headed arrow labeled 'k = 0, 1, 2, 2e, 3, 4, flex' connects the top block to a bottom block labeled ODUCnT\_TCMCm. The bottom block has four external connections: ODUCnT/ODUCn\_A\_So\_TCMCP (input), ODUCnT\_TT\_So\_TCMCP (input), ODUCnT/ODUCn\_A\_Sk\_TCMCP (output), and ODUCnT\_TT\_Sk\_TCMCP (output). A vertical double-headed arrow labeled 'k = 0, 1, 2, 2e, 3, 4, flex' connects the bottom block to ODUCnT\_TCMCm\_MP. The text G.798(17)\_F14-127 is in the bottom right corner. + +Figure 14-127 – ODUT\_TCMCm function + +## Interfaces + +Table 14-58 – ODUT\_TCMCm inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUT_TCMCm_MP:
ODUT_TCMCm_MI_Level
ODUT_TCMCm_MI_ModeSo
ODUT_TCMCm_MI_ModeSk
ODUT_TCMCm_MI_TCM_Extension
ODUT/ODU_A_So_TCMCP:
ODUT/ODU_A_So_TCMCI_AcSTAT[1..6]
ODUT/ODU_A_Sk_TCMCP:
ODUT/ODU_A_Sk_TCMCI_AcSTAT[1..6] | ODUT_TCMCm_MP:
ODUT_TCMCm_MI_AcSTATSo[1..6]
ODUT_TCMCm_MI_AcSTATSk[1..6]
ODUT/ODU_A_So_TCMCP:
ODUT/ODU_A_So_TCMCI_Mode
ODUT/ODU_A_So_TCMCI_Level
ODUT/ODU_A_Sk_TCMCP:
ODUT/ODU_A_Sk_TCMCI_Mode
ODUT/ODU_A_Sk_TCMCI_Level
ODUT_TT_So_TCMCP:
ODUT_TT_So_TCMCI_Mode
ODUT_TT_So_TCMCI_Level
ODUT_TT_Sk_TCMCP:
ODUT_TT_Sk_TCMCI_Mode
ODUT_TT_Sk_TCMCI_Level | + +## Processes + +The processes associated with the ODUT\_TCMCm function are as depicted in Figure 14-128. + +The TCM level is provided by the management via MI\_Level and distributed to sink and source termination and adaptation functions. + +The mode is provided independently for sink and source by the management (MI\_ModeSo and MI\_ModeSk). + +The sink and source TCM status of all six levels is provided to the management (MI\_AcSTATSo[1..6] and MI\_AcSTATSk[1..6]). + +TCM information forwarding and erasing: TCM information can be forwarded or erased for continuing TCM information into sections at the end of a TCM section and the related ODUT\_TT\_Sk function. With the MI\_TCM\_Extension control that can take three values: normal, pass through or erase, this function is controlled to either terminate TCM information or let it continue or erase. The default of the MI\_TCM\_Extension must be set to "Normal". + +NOTE – Equipment prior to Edition 4.4 of this Recommendation does not provide the MI\_TCM\_Extension and will always behave as configured "Normal". + +![Diagram of ODUT_TCMCm_MP processes showing signal flow and management information exchange between ODUT/ODU_A_So_TCMCP and ODUT/ODU_A_Sk_TCMCP interfaces.](34921caa1996eef32dd520e93a1e64b8_img.jpg) + +The diagram illustrates the ODUT\_TCMCm\_MP process. It shows the flow of TCM information and management signals between two interfaces: ODUT/ODU\_A\_So\_TCMCP on the left and ODUT/ODU\_A\_Sk\_TCMCP on the right. At the top, management signals MI\_AcSTATSo[1..6], MI\_ModeSo, MI\_Level, MI\_ModeSk, MI\_TCM\_Extension, and MI\_AcSTATSk[1..6] are shown. The TCM information flow is indicated by arrows: TCMCI\_AcSTAT[1..6] and TCMCI\_Level/Mode signals are passed from the source to the sink. The MI\_TCM\_Extension control is shown with three options: 'normal' (solid line), 'Transparent' (dashed line), 'pass-through' (dotted line), and 'Operational' (dash-dot line). The 'normal' option is the default. The diagram also shows the TCMCI\_Mode and TCMCI\_Level signals being passed from the sink back to the source. The reference G.798(17)\_F14-128 is noted at the bottom right. + +Diagram of ODUT\_TCMCm\_MP processes showing signal flow and management information exchange between ODUT/ODU\_A\_So\_TCMCP and ODUT/ODU\_A\_Sk\_TCMCP interfaces. + +Figure 14-128 – ODUT\_TCMCm processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +## 14.6 Blank clause + +NOTE – This clause is intentionally left blank. + +## 15 FlexO functions + +Figure 15-1 illustrates the FlexO layer and client layer adaptation functions. The information crossing the FlexO connection point (FlexO\_CP) is referred to as the FlexO characteristic information (FlexO\_CI). The information crossing the FlexO access point (FlexO\_AP) is referred to as the FlexO adapted information (FlexO\_AI). The information crossing the FlexO-x connection point (FlexO-x\_CP) is referred to as the FlexO-x characteristic information (FlexO-x\_CI). The information crossing the FlexO-x access point (FlexO-x\_AP) is referred to as the FlexO-x adapted information (FlexO-x\_AI). + +The FlexO-x to FCC adaptation function (FlexO-x/FCC\_A) is optional. + +The $m^{\text{th}}$ FlexO-x/FlexO\_A\_So function may have the last $x \times m - n$ FlexO\_CPs not connected. These input ports should assume the presence of an unequipped FlexO signal. + +![Figure 15-1: FlexO functions diagram showing the flow of data through various FlexO components like SD_CP, OTUCn_(T)CPs, FlexO/SD, FlexO-n/OTUCn, FlexO, FCC_CP, FlexO-x/FCC, FlexO-x/FlexO, and FlexO-x_(T)CP. It illustrates the mapping and adaptation of client signals into FlexO frames.](08246879b7e3340f5c7af67ca43e48ff_img.jpg) + +Figure 15-1: FlexO functions diagram showing the flow of data through various FlexO components like SD\_CP, OTUCn\_(T)CPs, FlexO/SD, FlexO-n/OTUCn, FlexO, FCC\_CP, FlexO-x/FCC, FlexO-x/FlexO, and FlexO-x\_(T)CP. It illustrates the mapping and adaptation of client signals into FlexO frames. + +G.798(17)-Amd.3(20)\_F15-1 + +Figure 15-1 – FlexO functions + +FlexO characteristic information + +The FlexO characteristic information (FlexO\_CI) is the FlexO frame as defined in [ITU-T G.709.1] with valid FlexO payload overhead (GID, IID, MAP, PT and client-mapping specific) as defined in [ITU-T G.709.1] and [ITU-T G.709.3], together with a frame and multi-frame start. The remaining overhead fields contain all-ZERO's. + +In case of a synchronous FlexO interface, the FlexO\_CI also includes the FlexO synchronization message channel overhead (OSMC) in FlexO instance #1. + +The FlexO overhead present at the FlexO\_CP is shown in Figure 15-1.1. + +![Figure 15-1.1: FlexO overhead at FlexO_CP and FlexO_AP. This figure includes a detailed byte map of a 128-bit block, a table for OSMC/RES fields, a table for client-mapping multiplexed OTUCn, and a detailed view of the overhead fields (GID, IID, PT, Client mapping specific) for a 128-bit block.](0c360dc1fae48be6b928e626f9e7569b_img.jpg) + +| 128-bit block # | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | Byte | +|-----------------|-----------|---|---|---|---|---|---|---|---|----|----|----|----|----|----|-----------|------| +| 1 | | | | | | | | | | | | | | | | | | +| 2 | | | | | | | | | | | | | | | | | | +| 3 | | | | | | | | | | | | | | | | | | +| 4 | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | | | | | | | +| 6 | | | | | | | | | | | | | | | | | | +| 7 | | | | | | | | | | | | | | | | | | +| 8 | | | | | | | | | | | | | | | | | | +| 9 | MAP (LSB) | | | | | | | | | | | | | | | MAP (MSB) | | +| 10 | OSMC/RES | | | | | | | | | | | | | | | | | + + + +| 128-bit block #9 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | Byte | +|------------------|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|----|------| +| Frame # | | | | | | | | | | | | | | | | | | +| 1 | | | | | | | | | | | | | | | | | | +| 2 | | | | | | | | | | | | | | | | | | +| 3 | | | | | | | | | | | | | | | | | | +| 4 | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | | | | | | | +| 6 | | | | | | | | | | | | | | | | | | +| 7 | | | | | | | | | | | | | | | | | | +| 8 | | | | | | | | | | | | | | | | | | + + + +| 128-bit block #8 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | Byte | +|------------------|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|----|------| +| Frame # | | | | | | | | | | | | | | | | | | +| 1 | | | | | | | | | | | | | | | | | | +| 2 | | | | | | | | | | | | | | | | | | +| 3 | | | | | | | | | | | | | | | | | | +| 4 | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | | | | | | | +| 6 | | | | | | | | | | | | | | | | | | +| 7 | | | | | | | | | | | | | | | | | | +| 8 | | | | | | | | | | | | | | | | | | + + + +| Frame # | OSMC | RES | FlexO instance #1 | FlexO instance #2..#n or #m × x | +|---------|------|-----|-------------------|---------------------------------| +| 1 | | | | | +| 2 | | | | | +| 3 | | | | | +| 4 | | | | | +| 5 | | | | | +| 6 | | | | | +| 7 | | | | | +| 8 | | | | | + + + +| Frame # | Client-mapping: Multiplexed OTUCn | | +|---------|-----------------------------------|-----| +| 2 | JC4 | JC1 | +| 3 | JC5 | JC2 | +| 4 | JC6 | JC3 | +| 5 | MSI | | +| 6 | JC4 | JC1 | +| 7 | JC5 | JC2 | +| 8 | JC6 | JC3 | + + + +| Frame # | GID | IID | PT | Client mapping specific | +|---------|-----|-----|----|-------------------------| +| 1 | | | | | +| 2 | | | | | +| 3 | | | | | +| 4 | | | | | +| 5 | | | | | +| 6 | | | | | +| 7 | | | | | +| 8 | | | | | + +Figure 15-1.1: FlexO overhead at FlexO\_CP and FlexO\_AP. This figure includes a detailed byte map of a 128-bit block, a table for OSMC/RES fields, a table for client-mapping multiplexed OTUCn, and a detailed view of the overhead fields (GID, IID, PT, Client mapping specific) for a 128-bit block. + +G.798(17)-Amd.3(21)\_F15-1.1 + +Figure 15-1.1 – FlexO overhead at FlexO\_CP and FlexO\_AP + +FlexO adapted information + +The FlexO adapted information (FlexO\_AI) consists of the client layer CI adapted to the FlexO frame as defined in [ITU-T G.709.1] and [ITU-T G.709.3], and valid FlexO payload overhead (GID, IID, MAP, PT and client-mapping specific) as shown in Figure 15-1.1, together with a frame and multi-frame start. The mapping-specific overhead depends on the client mapping scheme; e.g., for + +the multiplexed OTUCn client-mapping it consists of MSI and JC1 to JC6. For the case of a synchronous FlexO interface, the FlexO\_AI also includes the FlexO synchronization message channel overhead (OSMC) in FlexO instance #1. + +### Unequipped FlexO characteristic and adapted information + +An unequipped FlexO signal contains an all-ZEROs bit stream with FlexO clock, frame start and multi-frame start common with FlexO\_CI instance #1 of the last FlexO-x instance of the FlexO-x--m interface group and with SSF = false. + +NOTE – The FlexO\_AI and FlexO\_CI overhead (GID, IID and MAP) in an unequipped FlexO have the value all-ZEROs. + +### FlexO-x adapted information + +The FlexO-x adapted information (FlexO-x\_AI) consists of *x* instances of the FlexO\_CI and one instance of valid FlexO-x specific overhead (FCC plus FlexO\_CI overhead) as shown in Figure 15-1.2, together with a frame and multi-frame start. + +In case of COMMS access at the FlexO-x\_AP, it also includes the FlexO-x FCC overhead. + +![Figure 15-1.2 – FlexO overhead at FlexO-x_AP. The diagram shows the structure of FlexO overhead across 16 bytes (128 bits) for two blocks, block #9 and block #8. Block #9 contains MAP (LSB), FCC (LSB/RES), and OSMC/RES. Block #8 contains GID, IID, and Client mapping specific information. The Client mapping specific information includes a table for multiplexed OTUCn client mapping and a table for FlexO instance specific information. The diagram also shows the structure of the FlexO-x characteristic information (FlexO-x_CI) and the FlexO-x adapted information (FlexO-x_AI).](8c43614237e5bb57f1d5cf614291b32e_img.jpg) + +The diagram illustrates the FlexO overhead structure at the FlexO-x\_AP. It is divided into two 128-bit blocks, block #9 and block #8, each shown as a 16-byte grid. + +- Block #9:** + - Bytes 1-8: MAP (LSB) + - Bytes 9-12: FCC (LSB/RES) + - Bytes 13-16: OSMC/RES +- Block #8:** + - Bytes 1-8: GID + - Bytes 9-12: IID + - Bytes 13-16: Client mapping specific information + +The Client mapping specific information in Block #8 is further detailed with two tables: + +| Frame # | JC4 | JC1 | +|---------|-----|-----| +| 2 | JC5 | JC2 | +| 3 | JC6 | JC3 | +| 4 | MSI | | +| 5 | JC4 | JC1 | +| 6 | JC5 | JC2 | +| 7 | JC6 | JC3 | +| 8 | | | + + + +| Frame # | FlexO instance #1 in a FlexO-x | FlexO instance #2..n in a FlexO-x | +|---------|--------------------------------|-----------------------------------| +| 1 | FCC (MSB) | FCC (LSB) | +| 2 | RES | RES | + +Figure 15-1.2 – FlexO overhead at FlexO-x\_AP. The diagram shows the structure of FlexO overhead across 16 bytes (128 bits) for two blocks, block #9 and block #8. Block #9 contains MAP (LSB), FCC (LSB/RES), and OSMC/RES. Block #8 contains GID, IID, and Client mapping specific information. The Client mapping specific information includes a table for multiplexed OTUCn client mapping and a table for FlexO instance specific information. The diagram also shows the structure of the FlexO-x characteristic information (FlexO-x\_CI) and the FlexO-x adapted information (FlexO-x\_AI). + +Figure 15-1.2 – FlexO overhead at FlexO-x\_AP + +### FlexO-x characteristic information + +The FlexO-x characteristic information (FlexO-x\_CI) is the FlexO-x\_AI plus one instance of valid FlexO-x trail overhead (STAT(RPF), CRC16), together with a frame and multi-frame start. + +The FlexO-x overhead present at the FlexO-x\_CP is shown in Figure 15-1.3. + +![Figure 15-1.3: FlexO overhead at FlexO-x_CP. This diagram shows the structure of FlexO overhead across multiple 128-bit blocks. The top part shows a grid of 16 bytes per block, with rows 1-8 for data and rows 9-10 for overhead. Row 9 contains MAP (LSB), CRC16, and FCC (MSB)/RES. Row 10 contains FCC (LSB)/RES and OSMC/RES. Below this, two detailed overhead structures are shown. The left structure for '128-bit block #9' shows a frame number, OSMC, RES, and FlexO instance #1. The right structure for '128-bit block #8' shows a frame number, GID, IID, and a 'Client mapping specific' section containing PT. At the bottom, a table shows the mapping of FlexO instances to client mappings (JC1-JC6, MSI) across multiple frames.](d11039755489421fdcdad3ed6edd05d8_img.jpg) + +Figure 15-1.3: FlexO overhead at FlexO-x\_CP. This diagram shows the structure of FlexO overhead across multiple 128-bit blocks. The top part shows a grid of 16 bytes per block, with rows 1-8 for data and rows 9-10 for overhead. Row 9 contains MAP (LSB), CRC16, and FCC (MSB)/RES. Row 10 contains FCC (LSB)/RES and OSMC/RES. Below this, two detailed overhead structures are shown. The left structure for '128-bit block #9' shows a frame number, OSMC, RES, and FlexO instance #1. The right structure for '128-bit block #8' shows a frame number, GID, IID, and a 'Client mapping specific' section containing PT. At the bottom, a table shows the mapping of FlexO instances to client mappings (JC1-JC6, MSI) across multiple frames. + +Figure 15-1.3 – FlexO overhead at FlexO-x\_CP + +## 15.1 Connection functions + +Not applicable. + +## 15.2 Termination functions + +### 15.2.1 FlexO trail termination function (FlexO\_TT) + +The FlexO\_TT function terminates the section monitoring overhead of the FlexO overhead to determine the status of the FlexO trail. Figure 15-2 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Figure 15-2: FlexO_TT. This diagram shows two unidirectional FlexO_TT functions. The left side shows a sink function where a signal flows from FlexO_AP through a FlexO triangle to FlexO_TCP. The right side shows a source function where a signal flows from FlexO_TCP through a FlexO triangle to FlexO_AP. The text 'G.798(17)-Amd.3(21)_F15-2' is at the bottom.](53c60f255aa58c330efd23c77dfdc762_img.jpg) + +Figure 15-2: FlexO\_TT. This diagram shows two unidirectional FlexO\_TT functions. The left side shows a sink function where a signal flows from FlexO\_AP through a FlexO triangle to FlexO\_TCP. The right side shows a source function where a signal flows from FlexO\_TCP through a FlexO triangle to FlexO\_AP. The text 'G.798(17)-Amd.3(21)\_F15-2' is at the bottom. + +Figure 15-2 – FlexO\_TT + +#### 15.2.1.1 FlexO trail termination source function (FlexO\_TT\_So) + +The FlexO\_TT\_So function relays the FlexO signal at its FlexO\_AP input to its FlexO\_TCP. + +The information flow and processing of the FlexO\_TT\_So function is defined with reference to Figures 15-3 and 15-4. + +## Symbol + +![Symbol diagram for FlexO_TT_So function. It shows a downward arrow from FlexO_AP to a triangle labeled FlexO, which then points down to FlexO_TCP. Below the diagram is the text G.798(17)-Amd.3(21)_F15-3.](ce543c6123474723be64e31597330590_img.jpg) + +G.798(17)-Amd.3(21)\_F15-3 + +Symbol diagram for FlexO\_TT\_So function. It shows a downward arrow from FlexO\_AP to a triangle labeled FlexO, which then points down to FlexO\_TCP. Below the diagram is the text G.798(17)-Amd.3(21)\_F15-3. + +**Figure 15-3 – FlexO\_TT\_So function** + +## Interfaces + +**Table 15-1 – FlexO\_TT\_So inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| FlexO_AP:
FlexO_AI_CK
FlexO_AI_D
FlexO_AI_FS
FlexO_AI_MFS | FlexO_TCP:
FlexO_CI_CK
FlexO_CI_D
FlexO_CI_FS
FlexO_CI_MFS | + +## Processes + +The processes associated with the FlexO\_TT\_So function are as depicted in Figure 15-3. + +![Process diagram for FlexO_TT_So. It shows four vertical arrows representing data flows from FlexO_AP (labeled AI_D, AI_CK, AI_FS, AI_MFS) to FlexO_TCP (labeled CI_D, CI_CK, CI_FS, CI_MFS). Below the diagram is the text G.978(17)-Amd.3(21)_F15-4.](4a5c1280cac5c4924f49158846cde66c_img.jpg) + +G.978(17)-Amd.3(21)\_F15-4 + +Process diagram for FlexO\_TT\_So. It shows four vertical arrows representing data flows from FlexO\_AP (labeled AI\_D, AI\_CK, AI\_FS, AI\_MFS) to FlexO\_TCP (labeled CI\_D, CI\_CK, CI\_FS, CI\_MFS). Below the diagram is the text G.978(17)-Amd.3(21)\_F15-4. + +**Figure 15-4 – FlexO\_TT\_So processes** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 15.2.1.2 FlexO trail termination sink function (FlexO\_TT\_Sk) + +The FlexO\_TT\_Sk function reports the state of the FlexO trail. + +The information flow and processing of the FlexO\_TT\_Sk function is defined with reference to Figures 15-5 and 15-6. + +## Symbol + +![Symbol diagram for FlexO function. A triangle labeled 'FlexO' has an input arrow from 'FlexO_TCP' at the bottom vertex, an output arrow from the top vertex to 'FlexO_AP', and an output arrow from the left side to 'FlexO_TT_Sk_MP'. Below the diagram is the text 'G.798(17)-Amd.3(21)_F15-5'.](278814bf2c6d42b5817a334979f10bc0_img.jpg) + +Symbol diagram for FlexO function. A triangle labeled 'FlexO' has an input arrow from 'FlexO\_TCP' at the bottom vertex, an output arrow from the top vertex to 'FlexO\_AP', and an output arrow from the left side to 'FlexO\_TT\_Sk\_MP'. Below the diagram is the text 'G.798(17)-Amd.3(21)\_F15-5'. + +Figure 15-5 – FlexO\_TT\_Sk function + +## Interfaces + +Table 15-2 – FlexO\_TT\_Sk inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FlexO_TCP:
FlexO_CI_CK
FlexO_CI_D
FlexO_CI_FS
FlexO_CI_MFS
FlexO_CI_CRCerr
FlexO_CI_SSF | FlexO_AP:
FlexO_AI_CK
FlexO_AI_D
FlexO_AI_FS
FlexO_AI_MFS
FlexO_AI_CRCerr
FlexO_AI_TSF
FlexO_TT_Sk_MP:
FlexO_TT_Sk_MI_cSSF | + +## Processes + +The processes associated with the FlexO\_TT\_Sk function are as depicted in Figure 15-6. + +![Diagram of FlexO_TT_Sk processes showing internal components and interfaces.](14d497ab16a07c50b3215ffef2149ab9_img.jpg) + +The diagram illustrates the internal structure of the FlexO\_TT\_Sk\_MP process. It features a central grey rectangular block representing the process. Inside, there are two white boxes: 'Consequent actions' at the top and 'Defect correlations' on the left. Arrows indicate internal flow: from 'CI\_SSF' to 'Consequent actions', and from 'CI\_SSF' to 'Defect correlations'. From 'Defect correlations', an arrow points to 'MI\_cSSF', which then points out of the process boundary to the left. On the right side, several vertical arrows point upwards from the bottom (FlexO\_TCP) to the top (FlexO\_AP). These are labeled from left to right: 'CI\_SSF', 'CI\_FS', 'CI\_MFS', 'CI\_CK', 'CI\_CRCerr', and 'CI\_D'. Above the 'Consequent actions' box, an arrow labeled 'aTSF' points upwards to the top interface 'AI\_TSF'. Other top interfaces are labeled 'AI\_FS', 'AI\_MFS', 'AI\_CK', 'AI\_CRCerr', and 'AI\_D'. The bottom of the diagram is labeled 'FlexO\_TCP' and the top 'FlexO\_AP'. A small text 'G.798(17)-Amd.3(21)\_F15-6' is at the bottom right. + +Diagram of FlexO\_TT\_Sk processes showing internal components and interfaces. + +Figure 15-6 – FlexO\_TT\_Sk processes + +**Defects:** None. + +**Consequent actions** + +The function shall perform the following consequent action: + +aTSF ← CI\_SSF + +**Defect correlations** + +The function shall perform the following defect correlation to determine the most probable fault cause. This fault cause shall be reported to the EMF. + +cSSF ← CI\_SSF + +**Performance monitoring:** None. + +**15.2.2 FlexO-x trail termination function (FlexO-x\_TT)** + +The FlexO-x\_TT function terminates the section monitoring overhead of the FlexO-x overhead to determine the status of the FlexO-x trail. Figure 15-6.1 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Diagram of FlexO-x_TT showing bidirectional flow between FlexO-x_AP and FlexO-x_TCP via FlexO-x blocks.](af664ceebdaf69ac46f3af52f51df20e_img.jpg) + +The diagram shows two identical FlexO-x blocks, each represented by a downward-pointing triangle. The left block has an input arrow from 'FlexO-x\_AP' at the top and an output arrow to 'FlexO-x\_TCP' at the bottom. The right block has an input arrow from 'FlexO-x\_TCP' at the bottom and an output arrow to 'FlexO-x\_AP' at the top. A horizontal arrow labeled 'FlexO-x\_RP' points from the right block to the left block, indicating a bidirectional relationship between the two unidirectional functions. A small text 'G.798(17)-Amd.3(21)\_F15-6.1' is at the bottom right. + +Diagram of FlexO-x\_TT showing bidirectional flow between FlexO-x\_AP and FlexO-x\_TCP via FlexO-x blocks. + +Figure 15-6.1 – FlexO-x\_TT + +### 15.2.2.1 FlexO-x trail termination source function (FlexO-x\_TT\_So) + +The FlexO\_TT\_So function adds FlexO-x section monitoring overhead – including the RPF signal – in the STAT overhead field to the FlexO-x signal at its FlexO-x\_AP. + +The information flow and processing of the FlexO-x\_TT\_So function is defined with reference to Figures 15-6.2 and 15-6.3. + +#### Symbol + +![Symbol diagram for the FlexO-x_TT_So function. It shows an input FlexO-x_AP entering a triangle labeled 'FlexO-x' from the top. An input FlexO-x_RP enters the triangle from the right. The output is FlexO-x_TCP exiting from the bottom. Below the triangle is the text 'G.798(17)-Amd.3(21)_F15-6.2'.](95ca5789af2916f3ebaf64172683c29b_img.jpg) + +Symbol diagram for the FlexO-x\_TT\_So function. It shows an input FlexO-x\_AP entering a triangle labeled 'FlexO-x' from the top. An input FlexO-x\_RP enters the triangle from the right. The output is FlexO-x\_TCP exiting from the bottom. Below the triangle is the text 'G.798(17)-Amd.3(21)\_F15-6.2'. + +Figure 15-6.2 – FlexO-x\_TT\_So function + +#### Interfaces + +Table 15-2.1 – FlexO-x\_TT\_So inputs and outputs + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| FlexO-x_AP:
FlexO-x_AI_CK
FlexO-x_AI_D[1..x]
FlexO-x_AI_FS
FlexO-x_AI_MFS
FlexO-x_RP:
FlexO-x_RI_RPF | FlexO-x_TCP:
FlexO-x_CI_CK
FlexO-x_CI_D[1..x]
FlexO-x_CI_FS
FlexO-x_CI_MFS | + +#### Processes + +The processes associated with the FlexO-x\_TT\_So function are as depicted in Figure 15-12. + +**STAT-RPF:** The remote PHY fault indication is inserted in the RPF bit position of the STAT field of FlexO instance #1 of the FlexO-x as described in clause 9.2.5 of [ITU-T G.709.1]. Its value is derived from reference point FlexO-x\_RP. Upon the declaration/clearing of aRPF at the termination sink function, the trail termination source function shall have inserted/removed the RPF indication within 50 ms. + +**STAT-RES:** The RES field is reserved for future international standardization. The value shall be fixed to 00. + +**CRC-16:** The function shall compute the CRC-16 and insert the calculated CRC-16 value into the CRC-16 byte of the FlexO overhead field in every FlexO instance of the FlexO-x as described in clause 9.2.7 of [ITU-T G.709.1]. + +![Figure 15-6.3 – FlexO-x_TT_So processes. This diagram shows the internal processing of FlexO-x_TT_So. At the top, FlexO-x_AP inputs include AI_D[x], AI_D[2], AI_D[1], AI_CK, AI_FS, and AI_MFS. These pass through a series of 'OH insertion' and 'Compute and insert CRC-16' blocks. An 'Insert RPF' block receives RI_RPF and outputs to the third 'OH insertion' block. The bottom outputs are FlexO-x_TCP signals: CI_D[x], CI_D[2], CI_D[1], CI_CK, CI_FS, and CI_MFS. A label 'FlexO-x_RP' is on the right side. Reference G.798(17)-Amd.3(21)_F15-6.3 is at the bottom right.](04a21eb4cd167fac602b875e961ded35_img.jpg) + +Figure 15-6.3 – FlexO-x\_TT\_So processes. This diagram shows the internal processing of FlexO-x\_TT\_So. At the top, FlexO-x\_AP inputs include AI\_D[x], AI\_D[2], AI\_D[1], AI\_CK, AI\_FS, and AI\_MFS. These pass through a series of 'OH insertion' and 'Compute and insert CRC-16' blocks. An 'Insert RPF' block receives RI\_RPF and outputs to the third 'OH insertion' block. The bottom outputs are FlexO-x\_TCP signals: CI\_D[x], CI\_D[2], CI\_D[1], CI\_CK, CI\_FS, and CI\_MFS. A label 'FlexO-x\_RP' is on the right side. Reference G.798(17)-Amd.3(21)\_F15-6.3 is at the bottom right. + +Figure 15-6.3 – FlexO-x\_TT\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +**15.2.2.2 FlexO-x trail termination sink function (FlexO-x\_TT\_Sk)** + +The FlexO-x\_TT\_Sk function reports the state of the FlexO-x trail. It extracts FlexO-x monitoring overhead – including the RPF signal – in the STAT overhead field from the FlexO signal at its FlexO-x\_TCP, detects for the RPF defect, and forwards the error and defect information as backward indications to the companion FlexO-x\_TT\_So function. + +The information flow and processing of the FlexO-x\_TT\_Sk function is defined with reference to Figures 15-6.4 and 15-6.5. + +**Symbol** + +![Figure 15-6.4 – FlexO-x_TT_Sk function. This symbol diagram shows a central triangle labeled 'FlexO-x'. Inputs/Outputs are: FlexO-x_AP (top, pointing up), FlexO-x_TT_Sk_MP (left, pointing left), FlexO-x_RP (right, pointing right), and FlexO-x_TCP (bottom, pointing up). Reference G.798(17)-Amd.3(21)_F15-6.4 is at the bottom right.](f3d0615dd9e87088a29786cc6a1c8a35_img.jpg) + +Figure 15-6.4 – FlexO-x\_TT\_Sk function. This symbol diagram shows a central triangle labeled 'FlexO-x'. Inputs/Outputs are: FlexO-x\_AP (top, pointing up), FlexO-x\_TT\_Sk\_MP (left, pointing left), FlexO-x\_RP (right, pointing right), and FlexO-x\_TCP (bottom, pointing up). Reference G.798(17)-Amd.3(21)\_F15-6.4 is at the bottom right. + +Figure 15-6.4 – FlexO-x\_TT\_Sk function + +## Interfaces + +**Table 15-2.2 – FlexO-*x*\_TT\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FlexO-x_TCP:
FlexO- x _CI_CK
FlexO- x _CI_D[1.. x ]
FlexO- x _CI_FS
FlexO- x _CI_MFS
FlexO- x _CI_SSF | FlexO-x_AP:
FlexO- x _AI_CK
FlexO- x _AI_D[1.. x ]
FlexO- x _AI_FS
FlexO- x _AI_MFS
FlexO- x _AI_CRCerr[1.. x ]
FlexO- x _AI_TSF
FlexO-x_RP:
FlexO- x _RI_RPF
FlexO-x_TT_Sk_MP:
FlexO- x _TT_Sk_MI_cRDI
FlexO- x _TT_Sk_MI_cSSF | + +## Processes + +The processes associated with the FlexO-*x*\_TT\_Sk function are as depicted in Figure 15-14. + +**CRC-16:** See clause 9.2.7 of [ITU-T G.709.1]. The CRC-16 is extracted from the CRC-16 field in every FlexO instance of the FlexO-*x*. If the extracted CRC-16 value can be divided by the expected polynomial, CRCerr[*j*] (*j* = 1..*x*) is set to 0 (the default value); otherwise, CRCerr[*j*] is set to 1. + +**STAT-RPF:** The remote PHY fault indication shall be recovered from the RPF bit position of the accepted STAT value in FlexO instance #1 of the FlexO-*x* as described in clause 9.2.5 of [ITU-T G.709.1]. A new STAT value is accepted if a new value of the STAT field is received in a FlexO overhead frame with good CRC. The STAT-RPF shall be used for RPF defect detection. + +**STAT-RES:** RES in the STAT field in the FlexO signal at the FlexO\_TCP is reserved for future international standardization. For this version of this Recommendation, its value shall be ignored. + +![Figure 15-6.5 – FlexO-x_TT_Sk processes. This block diagram illustrates the internal processing flow of the FlexO-x_TT_Sk function. On the left, the FlexO-x_TT_Sk_MP interface provides inputs MI_cRDI and MI_cSSF. MI_cRDI enters an 'Extract RPF' block, which outputs aRPF to 'Consequent actions' and dRDI to 'Defect correlations'. MI_cSSF enters 'Defect correlations', which outputs RI_RPF. 'Consequent actions' outputs aTSF. The main processing path consists of multiple instances (1 to x) of 'Overhead access' blocks. Each instance receives CI_D[i] and produces CRCerr[i] and AI_D[i]. Between each 'Overhead access' block is an 'Extract, compute and compare CRC-16' block that receives CRCerr[i-1] and produces CRCerr[i]. The first instance also receives CI_SSF, CI_FS, CI_MFS, and CI_CK, and produces AI_TSF, AI_FS, AI_MFS, and AI_CK. The final instance produces AI_CRCerr[x] and AI_D[x]. The entire process is labeled FlexO-x_TT_Sk_MP on the left and FlexO-x_AP on the right. The bottom of the diagram is labeled FlexO-x_TCP.](98a6715208267336f8339163b005c28f_img.jpg) + +Figure 15-6.5 – FlexO-x\_TT\_Sk processes. This block diagram illustrates the internal processing flow of the FlexO-x\_TT\_Sk function. On the left, the FlexO-x\_TT\_Sk\_MP interface provides inputs MI\_cRDI and MI\_cSSF. MI\_cRDI enters an 'Extract RPF' block, which outputs aRPF to 'Consequent actions' and dRDI to 'Defect correlations'. MI\_cSSF enters 'Defect correlations', which outputs RI\_RPF. 'Consequent actions' outputs aTSF. The main processing path consists of multiple instances (1 to x) of 'Overhead access' blocks. Each instance receives CI\_D[i] and produces CRCerr[i] and AI\_D[i]. Between each 'Overhead access' block is an 'Extract, compute and compare CRC-16' block that receives CRCerr[i-1] and produces CRCerr[i]. The first instance also receives CI\_SSF, CI\_FS, CI\_MFS, and CI\_CK, and produces AI\_TSF, AI\_FS, AI\_MFS, and AI\_CK. The final instance produces AI\_CRCerr[x] and AI\_D[x]. The entire process is labeled FlexO-x\_TT\_Sk\_MP on the left and FlexO-x\_AP on the right. The bottom of the diagram is labeled FlexO-x\_TCP. + +G.798(17)-Amd.3(21)\_F15-6.5 + +**Figure 15-6.5 – FlexO-*x*\_TT\_Sk processes** + +**Defects** + +The function shall detect the dRDI defect. + +**dRDI:** If the extracted RPF is "1", dRDI shall be declared; Otherwise, dRDI shall be cleared; dRDI shall be set to false during CI\_SSF. + +**Consequent actions** + +The function shall perform the following consequent actions: + +aRPF $\leftarrow$ CI\_SSF + +aTSF $\leftarrow$ CI\_SSF + +**Defect correlations** + +The function shall perform the following defect correlations to determine the most probable fault cause. This fault cause shall be reported to the EMF. + +cRDI $\leftarrow$ dRDI + +cSSF $\leftarrow$ CI\_SSF + +**Performance monitoring:** None. + +**15.3 Adaptation functions****15.3.1 FlexO-n to OTUCn adaptation function (FlexO-n/OTUCn\_A)** + +The FlexO-n to OTUCn adaptation functions perform the adaptation between the FlexO-n layer adapted information and the characteristic information of the OTUCn layer signal. + +**15.3.1.1 FlexO-n to OTUCn adaptation source function (FlexO-n/OTUCn\_A\_So)** + +The FlexO-n to OTUCn adaptation source function is defined for OTUCn. + +The information flow and processing of the FlexO-n/OTUCn\_A\_So function is defined with reference to Figures 15-7 and 15-8. + +**Symbol**![Functional block diagram of FlexO-n/OTUCn_A_So. A trapezoidal block labeled 'FlexO-n/OTUCn' has a top input 'OTUCn_CP', a side input 'FlexO-n/OTUCn_A_So_MP', and multiple bottom outputs 'FlexO_AP[1]' through 'FlexO_AP[n]'.](eaaf53ac65d77e590778a391a25b92e4_img.jpg) + +``` + +graph TD + MP[FlexO-n/OTUCn_A_So_MP] --> Block + CP[OTUCn_CP] --> Block + subgraph Block [FlexO-n/OTUCn] + direction TB + L1[1] --- Ln[n] + end + Block --> AP1[FlexO_AP[1]] + Block --> APn[FlexO_AP[n]] + +``` + +G.798(17)\_F15-7 + +Functional block diagram of FlexO-n/OTUCn\_A\_So. A trapezoidal block labeled 'FlexO-n/OTUCn' has a top input 'OTUCn\_CP', a side input 'FlexO-n/OTUCn\_A\_So\_MP', and multiple bottom outputs 'FlexO\_AP[1]' through 'FlexO\_AP[n]'. + +**Figure 15-7 – FlexO-n/OTUCn\_A\_So function** + +## Interfaces + +**Table 15-3 – FlexO-n/OTUCn\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| OTUCn_CP:
OTUCn_CI_CK
OTUCn_CI_D
OTUCn_CI_FS
OTUCn_CI_MFS
FlexO-n/OTUCn_A_So_MP:
FlexO-n/OTUCn_A_So_MI_TxGID
FlexO-n/OTUCn_A_So_MI_TxIID[1..n]
FlexO-n/OTUCn_A_So_MI_TxFMAP | n × FlexO_AP:
FlexO_AI_D
FlexO_AI_CK
FlexO_AI_FS
FlexO_AI_MFS | + +## Processes + +The processes associated with the FlexO-n/OTUCn\_A\_So function are as depicted in Figure 15-8. + +**OTUCn FAS/MFAS insertion:** The function shall insert the FAS and MFAS into the OTUCn OH area as described in clause 11.3 of [ITU-T G.709]. + +**OTUCn distribution:** The function shall divide OTUCn into n OTUC instance signals as described in clause 10.1.1 of [ITU-T G.709.1]. + +**Clock generation:** The function shall generate the FlexO (AI\_CK) clock by multiplying the incoming OTUCn clock (CI\_CK) by a factor of $1/n \times 4112/4097$ . The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCb clock), apply. During failure conditions of the incoming OTUCn clock signal (CI\_CK), the FlexO clock shall stay within its limits as defined in [ITU-T G.8251] and no frame phase discontinuity shall be introduced. + +**FS and MFS generator:** The function shall generate FlexO frame and multi-frame starter identifier as described in clause 8.1 and 8.2 of [ITU-T G.709.1]. + +**Mapping:** The function shall map the OTUC instance signal into FlexO frame payload area as defined in clause 10.2.2 of [ITU-T G.709.1] and the fixed stuff bits in the 8-frame multi-frame payload area shall be set to all-ZEROs. + +NOTE – In order to minimize implementation complexity and avoid the skew introduction between n OTUC instance signals, n lanes of mapping may use one unified mapping control mechanism to complete all the mapping processes and keep actions consistent between them. + +**All-0's OH insertion:** The function shall insert all-ZEROs into all the FlexO AM, EOH and BOH bit locations. + +**FlexO OH Insertion:** The function shall insert the overhead information of FlexO group signal in the corresponding overhead area (GID, IID, MAP and RES) as defined in clause 9.2 of [ITU-T G.709.1]. + +**FlexO GID:** The FlexO group identifier is inserted in the GID field. Its value is derived from reference point FlexO\_TT\_So\_MP. The GID format is described in clause 9.2.2.1 of [ITU-T G.709.1]. + +**FlexO IID:** The FlexO Instance Identifier is inserted in the IID field. Its value is derived from reference point FlexO\_TT\_So\_MP. The IID format is described in clause 9.2.2.2 of [ITU-T G.709.1]. + +**FlexO MAP:** The FlexO instance map is inserted in the FlexO MAP field. Its value is derived from reference point FlexO\_TT\_So\_MP. The FlexO MAP format is described in clause 9.2.2.3 of [ITU-T G.709.1]. + +**RES:** The function shall insert all-ZEROs into the RES bytes. + +![Figure 15-8 – FlexO-n/OTUCn_A_So processes. This block diagram illustrates the transmission path for FlexO-n signals to OTUCn. At the top, OTUCn_CP inputs (CI_D, CI_CK, CI_FS, CI_MFS) enter an 'OTUCn FAS/MFAS insertion' block. This block outputs CI_CK to a 'Clock generator', which in turn provides AI_CK, AI_FS, and AI_MFS to an 'FS and MFS generator'. The 'OTUCn FAS/MFAS insertion' block also outputs D, CK, and FS signals to an 'OTUCn distribution' block. The 'OTUCn distribution' block outputs OTUC #1 and OTUC #n signals. Each OTUC signal (e.g., OTUC #1) enters an 'Elastic store' block with inputs D, CK, and FS, and outputs WR and RD. The 'Elastic store' block outputs AI_CK, AI_FS, and AI_MFS signals. Below the 'Elastic store' is a block 'Insert all-0's in all FlexO AM, EOH, BOH bits'. This is followed by a 'FlexO overhead insertion' block. The 'FlexO overhead insertion' block receives inputs from 'Insert IID' (MI_TxIID[1]), 'Insert GID' (MI_TxGID), 'Insert MAP' (MI_TxFMAP), and 'Insert RES'. The 'FlexO overhead insertion' block outputs AI_D, AI_CK, AI_FS, and AI_MFS signals, which are grouped as FlexO_AP[1]. The same process is shown for OTUC #n, with inputs MI_TxIID[n], MI_TxGID, MI_TxFMAP, and MI_TxRES, resulting in FlexO_AP[n] outputs. A vertical label on the right side reads 'FlexO-n/OTUCn_A_So_MP'. The diagram is labeled G.798(17)-Amd.4(22)_F15-8.](5d70cb9af3e025f57d437dc84524e9a4_img.jpg) + +Figure 15-8 – FlexO-n/OTUCn\_A\_So processes. This block diagram illustrates the transmission path for FlexO-n signals to OTUCn. At the top, OTUCn\_CP inputs (CI\_D, CI\_CK, CI\_FS, CI\_MFS) enter an 'OTUCn FAS/MFAS insertion' block. This block outputs CI\_CK to a 'Clock generator', which in turn provides AI\_CK, AI\_FS, and AI\_MFS to an 'FS and MFS generator'. The 'OTUCn FAS/MFAS insertion' block also outputs D, CK, and FS signals to an 'OTUCn distribution' block. The 'OTUCn distribution' block outputs OTUC #1 and OTUC #n signals. Each OTUC signal (e.g., OTUC #1) enters an 'Elastic store' block with inputs D, CK, and FS, and outputs WR and RD. The 'Elastic store' block outputs AI\_CK, AI\_FS, and AI\_MFS signals. Below the 'Elastic store' is a block 'Insert all-0's in all FlexO AM, EOH, BOH bits'. This is followed by a 'FlexO overhead insertion' block. The 'FlexO overhead insertion' block receives inputs from 'Insert IID' (MI\_TxIID[1]), 'Insert GID' (MI\_TxGID), 'Insert MAP' (MI\_TxFMAP), and 'Insert RES'. The 'FlexO overhead insertion' block outputs AI\_D, AI\_CK, AI\_FS, and AI\_MFS signals, which are grouped as FlexO\_AP[1]. The same process is shown for OTUC #n, with inputs MI\_TxIID[n], MI\_TxGID, MI\_TxFMAP, and MI\_TxRES, resulting in FlexO\_AP[n] outputs. A vertical label on the right side reads 'FlexO-n/OTUCn\_A\_So\_MP'. The diagram is labeled G.798(17)-Amd.4(22)\_F15-8. + +Figure 15-8 – FlexO-n/OTUCn\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 15.3.1.2 FlexO-n to OTUCn adaptation sink function (FlexO-n/OTUCn\_A\_Sk) + +The FlexO-n to OTUCn adaptation sink function is defined for OTUCn. + +The information flow and processing of the FlexO-n/OTUCn\_A\_Sk function is defined with reference to Figures 15-9 and 15-10. + +## Symbol + +![Diagram of the FlexO-n/OTUCn_A_Sk function symbol. It shows a trapezoidal block labeled 'FlexO-n/OTUCn'. Above the block, an arrow points up to 'OTUCn_CP'. Below the block, multiple arrows point up from 'FlexO_AP[1]' to 'FlexO_AP[n]', with a dashed line and ellipsis between them. To the left of the block, an arrow points left to 'FlexO-n/OTUCn_A_Sk_MP'. The reference 'G.798(17)_F15-9' is shown at the bottom right.](30b76717cca15621840d1c16fff50f89_img.jpg) + +Diagram of the FlexO-n/OTUCn\_A\_Sk function symbol. It shows a trapezoidal block labeled 'FlexO-n/OTUCn'. Above the block, an arrow points up to 'OTUCn\_CP'. Below the block, multiple arrows point up from 'FlexO\_AP[1]' to 'FlexO\_AP[n]', with a dashed line and ellipsis between them. To the left of the block, an arrow points left to 'FlexO-n/OTUCn\_A\_Sk\_MP'. The reference 'G.798(17)\_F15-9' is shown at the bottom right. + +Figure 15-9 – FlexO-n/OTUCn\_A\_Sk function + +## Interfaces + +Table 15-4 – FlexO-n/OTUCn\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n × FlexO_AP:
FlexO_AI_D
FlexO_AI_CK (Note)
FlexO_AI_FS
FlexO_AI_MFS
FlexO_AI_CRCerr
FlexO_AI_TSF
FlexO-n/OTUCn_A_Sk_MP:
FlexO-n/OTUCn_A_Sk_MI_ExGID
FlexO-n/OTUCn_A_Sk_MI_ExFMAP | OTUCn_CP:
OTUCn_CI_CK
OTUCn_CI_D
OTUCn_CI_FS
OTUCn_CI_MFS
OTUCn_CI_SSF
FlexO-n/OTUCn_A_Sk_MP:
FlexO-n/OTUCn_A_Sk_MI_AcGID[1..n]
FlexO-n/OTUCn_A_Sk_MI_AcFMAP[1..n]
FlexO-n/OTUCn_A_Sk_MI_AcIID[1..n]
FlexO-n/OTUCn_A_Sk_MI_cLOFLOM[1..n]
FlexO-n/OTUCn_A_Sk_MI_cGIDM
FlexO-n/OTUCn_A_Sk_MI_cFMM
FlexO-n/OTUCn_A_Sk_MI_cLOL | +| NOTE – The function only needs one FlexO_AI_CK, e.g., FlexO_AI_CK[1]. | | + +## Processes + +The processes associated with the FlexO-n/OTUCn\_A\_Sk function are as depicted in Figure 15-10. + +**FlexO OH Extraction:** The function shall extract the overhead of FlexO group interface (GID, IID and MAP) from each FlexO frame as defined in clause 9.2 of [ITU-T G.709.1]. + +**FlexO GID:** The GID fields shall be extracted from the FlexO overhead and processed as specified in clause B.2.2.1. The accepted GID values are available at the MP (MI\_AcGID[i]) and are used for dGIDM defect detection. + +NOTE – A GID field carrying an all-0's value indicates the presence of an unequipped FlexO instance. Such unequipped FlexO instance represents a FlexO-x configuration mistake. + +**FlexO IID:** The IID fields shall be extracted from the FlexO overhead and processed as specified in clause B.2.2.2.1. The accepted IID values are available at the MP (MI\_AcIID[i]) and are used for dFMM defect detection. + +**FlexO MAP:** The FlexO MAP fields shall be extracted from the FlexO overhead and processed as specified in clause B.2.2.3.1. The accepted MAP values are available at the MP (MI\_AcFMAP[i]) and are used for dFMM defect detection. + +**FlexO-n Reorder:** The function shall reorder n FlexO instances based on IID as described in clauses 9.2.3 and 10.3 of [ITU-T G.709.1]. + +**Demapping:** The function shall demap the OTUC instance signal from FlexO frame as described in clause 10.1.2 of [ITU-T G.709.1]. + +**OTUCn Frame and multi-frame alignment:** The function shall recover the OTUC instance frame start and multi-frame start as described in clause 8.2.3. + +**OTUCn Deskew:** The function shall compensate the skew between n OTUC instances based on OTUC instance frame start indication as described in clause 10.1.4 of [ITU-T G.709.1]. The alignment process shall establish the delay compensation, compensating the differential delay between the FlexO instance signals as given in clause 10.1.4 of [ITU-T G.709.1]. The compensation between the FlexO instances is achieved by an elastic store per OTUC instance. Each OTUC instance signal shall be written into an elastic store with the OTUC frame start indication. Each elastic store shall be capable of compensating at least 300 ns of absolute differential delay between the OTUC instances for FlexO-SR applications and at least 1 $\mu$ s of absolute differential delay between the OTUC instances for FlexO-LR applications. The process has two states, out-of-multilane-alignment (OLA) and in-multilane-alignment (ILA). The alignment start shall be maintained during the OLA state. In the OLA state, if the bytes of the OTUC instances signals can be written consistently into the elastic store in the presence of a differential delay in line without exceeding the buffering time, the ILA state shall be entered. In this case, the differential delay can be compensated. In the ILA state, if the differential delay between two OTUC instances exceeds the maximum delay that can be compensated, the OLA state shall be entered. + +**OTUCn Recover:** The function shall recombine n OTUC instances into an OTUCn as described in clause 10.1.1 of [ITU-T G.709.1]. + +![Figure 15-10 – FlexO-n/OTUCn_A_Sk processes. This block diagram illustrates the internal architecture of the FlexO-n/OTUCn_A_Sk processes. At the bottom, multiple FlexO_AP inputs (labeled FlexO_AP[1] to FlexO_AP[n]) are shown, each with signals AI_D, AI_CK, AI_FS, AI_MFS, AI_TSF, and AI_CRCerr. These inputs feed into 'Extract GID', 'Extract IID', and 'Extract MAP' blocks, which output AcGID, AcIID, and AcFMAP respectively, along with CRCerr. These signals then pass through a 'FlexO-n Reorder' block. Above this, 'Elastic store' blocks (WR and RD) are connected to 'Frame and multiframe alignment' blocks, which output dLOFLOM[1] to dLOFLOM[n]. A 'Clock generator' block receives CK[1] and provides WR and RD signals. The alignment blocks feed into 'OTUCn deskew' and 'OTUCn recover' blocks, which output CL_D, CL_CK, CL_FS, and CL_MFS. To the right, detection blocks for 'dGIDM detection', 'dFMM detection', and 'Defect correlations' receive various inputs (AI_TSF, AcGID, dLOFLOM, dLOL, dFMM, dGIDM) and output MI_ExGID, MI_ExFMAP, MI_cLOFLOM, MI_cLOL, MI_cFMM, MI_cGIDM, MI_AcGID, MI_AcIID, and MI_AcFMAP. A 'Consequent actions' block at the top right receives dGIDM, dFMM, dLOL, dLOFLOM, and AI_TSF, and outputs aSSF. The diagram is labeled G.798(17)-Amd.4(22)_F15-10 and has a vertical label FlexO-n/OTUCn_A_Sk_MP on the right.](7a24dd6d3d2059e1251e5cac12dabbd0_img.jpg) + +Figure 15-10 – FlexO-n/OTUCn\_A\_Sk processes. This block diagram illustrates the internal architecture of the FlexO-n/OTUCn\_A\_Sk processes. At the bottom, multiple FlexO\_AP inputs (labeled FlexO\_AP[1] to FlexO\_AP[n]) are shown, each with signals AI\_D, AI\_CK, AI\_FS, AI\_MFS, AI\_TSF, and AI\_CRCerr. These inputs feed into 'Extract GID', 'Extract IID', and 'Extract MAP' blocks, which output AcGID, AcIID, and AcFMAP respectively, along with CRCerr. These signals then pass through a 'FlexO-n Reorder' block. Above this, 'Elastic store' blocks (WR and RD) are connected to 'Frame and multiframe alignment' blocks, which output dLOFLOM[1] to dLOFLOM[n]. A 'Clock generator' block receives CK[1] and provides WR and RD signals. The alignment blocks feed into 'OTUCn deskew' and 'OTUCn recover' blocks, which output CL\_D, CL\_CK, CL\_FS, and CL\_MFS. To the right, detection blocks for 'dGIDM detection', 'dFMM detection', and 'Defect correlations' receive various inputs (AI\_TSF, AcGID, dLOFLOM, dLOL, dFMM, dGIDM) and output MI\_ExGID, MI\_ExFMAP, MI\_cLOFLOM, MI\_cLOL, MI\_cFMM, MI\_cGIDM, MI\_AcGID, MI\_AcIID, and MI\_AcFMAP. A 'Consequent actions' block at the top right receives dGIDM, dFMM, dLOL, dLOFLOM, and AI\_TSF, and outputs aSSF. The diagram is labeled G.798(17)-Amd.4(22)\_F15-10 and has a vertical label FlexO-n/OTUCn\_A\_Sk\_MP on the right. + +**Figure 15-10 – FlexO-n/OTUCn\_A\_Sk processes** + +### Defects + +The function shall detect dGIDM, dFMM, dLOL and dLOFLOM[i], where 'i' is 1..n. + +**dGIDM:** See clause B.1.1.2.1. dGIDM shall be set to false during $\sum AI\_TSF[i]$ . + +**dFMM:** See clause B.1.1.2.2. dFMM shall be set to false during $\sum AI\_TSF[i]$ . + +**dLOFLOM[i]:** See clause 6.2.5.3. + +**dLOL:** If the alignment process is in the OLA state, dLOL shall be set to true. dLOL shall be set to false when the alignment process is in the ILA state; dLOL shall be set to false during $\sum AI\_TSF[i]$ . + +**Consequent actions** + +aSSF $\leftarrow$ dGIDM or dFMM or dLOL or $\sum dLOFLOM[i]$ or $\sum AI\_TSF[i]$ + +**Defect correlations** + +cGIDM $\leftarrow$ dGIDM + +cFMM $\leftarrow$ dFMM and (not dGIDM) + +cLOFLOM $\leftarrow \sum (dLOFLOM[i] \text{ and (not } AI\_TSF[i])) \text{ and (not dGIDM) and (not dFMM)}$ + +cLOL $\leftarrow$ dLOL and (not dGIDM) and (not dFMM) and (not $\sum dLOFLOM[i]$ ) + +**Performance monitoring:** None. + +**15.3.2 FlexO-x to FCC adaptation functions** + +The FlexO-x to FCC adaptation functions provide access to the FCC overhead in the FlexO interface for interface management. + +**15.3.2.1 FlexO-x to FCC adaptation source function (FlexO-x/FCC\_A\_So)** + +The FlexO-x/FCC\_A\_So function maps the FlexO-x interface management FCC data into the FlexO FCC overhead. + +The information flow and processing of the FlexO-x/FCC\_A\_So functions is defined with reference to Figures 15-11 and 15-12. + +**Symbol** + +![Flowchart showing the FlexO-x/FCC_A_So function. It starts with FCC_CP at the top, pointing down to a trapezoidal block labeled 'FlexO-x/FCC', which then points down to FlexO-x_AP at the bottom. Below the diagram is the text G.798(17)-Amd.3(21)_F15-11.](beb1af5db94ec438ceeab4ef895ffb48_img.jpg) + +``` + +graph TD + FCC_CP --> FlexO_x_FCC{{FlexO-x/FCC}} + FlexO_x_FCC --> FlexO_x_AP + style FCC_CP fill:none,stroke:none + style FlexO_x_AP fill:none,stroke:none + +``` + +G.798(17)-Amd.3(21)\_F15-11 + +Flowchart showing the FlexO-x/FCC\_A\_So function. It starts with FCC\_CP at the top, pointing down to a trapezoidal block labeled 'FlexO-x/FCC', which then points down to FlexO-x\_AP at the bottom. Below the diagram is the text G.798(17)-Amd.3(21)\_F15-11. + +**Figure 15-11 – FlexO-x/FCC\_A\_So function** + +**Interfaces** + +**Table 15-5 – FlexO-x/FCC\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| FCC_CP:
FCC_CI_D
FlexO-x_AP:
FlexO-x
FlexO-x_AI_FS
FlexO-x_AI_MFS | FCC_CP:
FCC_CI_CK
FlexO-x_AP:
FlexO-x_AI_D | + +**Processes** + +The processes associated with the FlexO-x/FCC\_A\_So function are as depicted in Figure 15-12. + +**FCC clock generation:** The function shall generate the FCC clock (CI\_CK) by dividing the FlexO-x clock (AI\_CK) by a factor of 14/82240. + +**Mapping:** The function shall map the incoming FCC data (CI\_D) into the FCC overhead of the FlexO frame #1 of the FlexO-x (AI\_D) as described in clause 9.2.8 of [ITU-T G.709.1]. The bit rate of the FCC data is defined by the outgoing FCC clock (CI\_CK). + +The insertion of the FlexO-x interface management data follows the transmission order of the FCC overhead bits and bytes. + +![Figure 15-12: FlexO-x/FCC_A_So processes diagram. A grey box labeled 'FCC_CP' contains two white boxes: 'Mapping' and 'FCC clock generation'. Inputs from the bottom are AI_MFS, AI_FS, AI_D, and AI_CK. AI_D and AI_CK enter the 'Mapping' and 'FCC clock generation' boxes respectively. CI_D and CI_CK exit the 'Mapping' and 'FCC clock generation' boxes respectively. The label 'FlexO_AP' is positioned below the box.](1ba9045eb6dc22039a16b92b1427e696_img.jpg) + +Figure 15-12: FlexO-x/FCC\_A\_So processes diagram. A grey box labeled 'FCC\_CP' contains two white boxes: 'Mapping' and 'FCC clock generation'. Inputs from the bottom are AI\_MFS, AI\_FS, AI\_D, and AI\_CK. AI\_D and AI\_CK enter the 'Mapping' and 'FCC clock generation' boxes respectively. CI\_D and CI\_CK exit the 'Mapping' and 'FCC clock generation' boxes respectively. The label 'FlexO\_AP' is positioned below the box. + +G.798(17)\_F15-12 + +**Figure 15-12 – FlexO-x/FCC\_A\_So processes** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 15.3.2.2 FlexO-x to FCC adaptation sink function (FlexO-x/FCC\_A\_Sk) + +The FlexO-x/FCC\_A\_Sk extracts the FlexO-x interface management data from the FlexO FCC overhead. + +The information flow and processing of the FlexO-x/FCC\_A\_Sk functions is defined with reference to Figures 15-13 and 15-14. + +#### Symbol + +![Figure 15-13: FlexO-x/FCC_A_Sk function symbol diagram. A trapezoidal symbol labeled 'FlexO-x/FCC' has an input arrow from the bottom labeled 'FlexO-x_AP' and an output arrow pointing upwards labeled 'FCC_CP'.](e96884b4726abd1ef715e32b100b05e6_img.jpg) + +Figure 15-13: FlexO-x/FCC\_A\_Sk function symbol diagram. A trapezoidal symbol labeled 'FlexO-x/FCC' has an input arrow from the bottom labeled 'FlexO-x\_AP' and an output arrow pointing upwards labeled 'FCC\_CP'. + +G.798(17)-Amd.3(21)\_F15-13 + +**Figure 15-13 – FlexO-x/FCC\_A\_Sk function** + +## Interfaces + +**Table 15-6 – FlexO-x/FCC\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| FlexO-x_AP:
FlexO-x_AI_CK
FlexO-x_AI_D
FlexO-x_AI_FS
FlexO-x_AI_MFS
FlexO-x_AI_TSF | FCC_CP:
FCC_CI_CK
FCC_CI_D
FCC_CI_SSF | + +## Processes + +The processes associated with the FlexO-x/FCC\_A\_Sk function are as depicted in Figure 15-14. + +**FCC clock generation:** The function shall generate the FCC clock (CI\_CK) by dividing the FlexO-x clock (AI\_CK) by a factor of $x \times 14/82240$ . + +**Demapping:** The function shall extract the FCC data (CI\_D) from the FCC overhead of the FlexO frame #1 of the FlexO-x (AI\_D) as described in clause 9.2.8 of [ITU-T G.709.1]. The bit rate of the FCC data is defined by the outgoing FCC clock (CI\_CK). + +The extraction of the FlexO-x interface management data follows the transmission order of the FCC overhead bits and bytes. + +![Figure 15-14 – FlexO-x/FCC_A_Sk processes diagram. The diagram shows a grey box labeled 'FCC_CP' containing two sub-processes: 'Demapping' and 'FCC clock generation'. Inputs from 'FlexO-x_AP' (AI_MFS, AI_FS, AI_D, AI_CK, AI_TSF) enter from the bottom. AI_D and AI_FS enter the 'Demapping' block. AI_CK enters the 'FCC clock generation' block. AI_TSF enters a label 'aSSF'. Outputs CI_D, CI_CK, and CI_SSF exit from the top. CI_D is output from 'Demapping'. CI_CK is output from 'FCC clock generation'. CI_SSF is output from the 'aSSF' label. A small text 'G.798(17)-Amd.3(21)_F15-14' is in the bottom right.](3b1646c728aab109f7312ecb46537a4a_img.jpg) + +Figure 15-14 – FlexO-x/FCC\_A\_Sk processes diagram. The diagram shows a grey box labeled 'FCC\_CP' containing two sub-processes: 'Demapping' and 'FCC clock generation'. Inputs from 'FlexO-x\_AP' (AI\_MFS, AI\_FS, AI\_D, AI\_CK, AI\_TSF) enter from the bottom. AI\_D and AI\_FS enter the 'Demapping' block. AI\_CK enters the 'FCC clock generation' block. AI\_TSF enters a label 'aSSF'. Outputs CI\_D, CI\_CK, and CI\_SSF exit from the top. CI\_D is output from 'Demapping'. CI\_CK is output from 'FCC clock generation'. CI\_SSF is output from the 'aSSF' label. A small text 'G.798(17)-Amd.3(21)\_F15-14' is in the bottom right. + +**Figure 15-14 – FlexO-x/FCC\_A\_Sk processes** + +**Defects:** None. + +### Consequent actions + +The function shall perform the following consequent actions: + +$aSSF \leftarrow AI\_TSF$ + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 15.3.3 FlexO to synchronization distribution adaptation functions + +FlexO to synchronization distribution (SD) adaptation functions are given in clause 8.12 of [ITU-T G.781]. + +### 15.3.4 FlexO-*x* to FlexO adaptation function (FlexO-*x*/FlexO\_A) + +The FlexO-*x* to FlexO adaptation functions perform the adaptation between the FlexO-*x* layer adapted information and the characteristic information of the FlexO layer signals. + +#### 15.3.4.1 FlexO-*x* to FlexO adaptation source function (FlexO-*x*/FlexO\_A\_So) + +The FlexO-*x*/FlexO\_A\_So function interleaves *x* FlexO signals from the *x* × FlexO\_CPs into a FlexO-*x* signal. For the case that up to *x*-1 FlexO\_CPs are not connected and do not receive an input signal, the function replaces these FlexO\_CI by an all-0's unequipped FlexO signal. + +The information flow and processing of the FlexO-*x*/FlexO\_A\_So function is defined with reference to Figures 15-15 and 15-16. + +#### Symbol + +![Diagram of the FlexO-x/FlexO_A_So function symbol. It shows x FlexO_CP inputs (labeled 1, 2, ..., x) entering a trapezoidal block labeled 'FlexO-x/FlexO'. An arrow points from the block to an output labeled 'FlexO-x_AP'. Below the output is the text 'G.798(17)-Amd.3(21)_F15-15'.](60590b20ec9994e388840f5fc4572e39_img.jpg) + +Diagram of the FlexO-x/FlexO\_A\_So function symbol. It shows x FlexO\_CP inputs (labeled 1, 2, ..., x) entering a trapezoidal block labeled 'FlexO-x/FlexO'. An arrow points from the block to an output labeled 'FlexO-x\_AP'. Below the output is the text 'G.798(17)-Amd.3(21)\_F15-15'. + +Figure 15-15 – FlexO-*x*/FlexO\_A\_So function + +#### Interfaces + +Table 15-9 – FlexO-*x*/FlexO\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|-----------------------------|--------------------------------------| +| x × FlexO_CP: | FlexO-x_AP: | +| FlexO_CI_CK | FlexO- x _AI_CK | +| FlexO_CI_D | FlexO- x _AI_D[1.. x ] | +| FlexO_CI_FS | FlexO- x _AI_FS | +| FlexO_CI_MFS | FlexO- x _AI_MFS | + +#### Processes + +The processes associated with the FlexO-*x*/FlexO\_A\_So function are as depicted in Figure 15-16. + +The function shall forward the CI\_CK, CI\_FS, CI\_MFS from FlexO\_CP[1] and the CI\_D from FlexO\_CP[1] to FlexO\_CP[*x*] to the FlexO-*x*\_AP. For the case that one or more FlexO\_CPs are not connected, their FlexO\_CI\_D contains the all-0's pattern. Such all-0's pattern is referred to as unequipped FlexO pattern. + +NOTE – 10-bit frame and multi-frame synchronous interleaving of the *x* FlexO instances is performed in the OTSiG/FlexO-*x*\_A\_So function. + +![Figure 15-16: FlexO-x/FlexO_A_So processes diagram. It shows multiple FlexO_CP[j] blocks (1, 2, ..., x) at the top, each with four input signals: CI_MFS, CI_FS, CI_CK, and CI_D. Below these is a large grey box representing the FlexO-x_AP. Arrows point from the CI signals down into the FlexO-x_AP box. From the bottom of the box, arrows point up to output signals: AI_MFS, AI_FS, AI_CK, and AI_D[j] (for j=1, 2, ..., x). A note inside the box states: 'NOTE – CI_D[j] contains all-0s pattern if FlexO_CP[j] (j = 2..x) is not connected'. The diagram is labeled G.798(17)-Amd.3(21)_F15-16.](6347ebb7bc58aba4272fc340a410bd97_img.jpg) + +Figure 15-16: FlexO-x/FlexO\_A\_So processes diagram. It shows multiple FlexO\_CP[j] blocks (1, 2, ..., x) at the top, each with four input signals: CI\_MFS, CI\_FS, CI\_CK, and CI\_D. Below these is a large grey box representing the FlexO-x\_AP. Arrows point from the CI signals down into the FlexO-x\_AP box. From the bottom of the box, arrows point up to output signals: AI\_MFS, AI\_FS, AI\_CK, and AI\_D[j] (for j=1, 2, ..., x). A note inside the box states: 'NOTE – CI\_D[j] contains all-0s pattern if FlexO\_CP[j] (j = 2..x) is not connected'. The diagram is labeled G.798(17)-Amd.3(21)\_F15-16. + +Figure 15-16 – FlexO-x/FlexO\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +**15.3.4.2 FlexO-x to FlexO adaptation sink function (FlexO-x/FlexO\_A\_Sk)** + +The FlexO-x/FlexO\_A\_Sk function disinterleaves $x$ FlexO signals from the FlexO\_AP and present these at the $x$ FlexO\_CPs. + +The information flow and processing of the FlexO-x/FlexO\_A\_Sk function is defined with reference to Figures 15-17 and 15-18. + +**Symbol** + +![Figure 15-17: FlexO-x/FlexO_A_Sk function symbol diagram. A trapezoidal block labeled 'FlexO-x/FlexO' has an input arrow from the bottom labeled 'FlexO-x_AP'. It has an output arrow to the left labeled 'FlexO-x/FlexO_A_Sk_MP'. At the top, there are multiple output arrows labeled 'FlexO_CP' with subscripts 1, 2, ..., x.](1c453289f9bc736ca66bdaf7178601c3_img.jpg) + +Figure 15-17: FlexO-x/FlexO\_A\_Sk function symbol diagram. A trapezoidal block labeled 'FlexO-x/FlexO' has an input arrow from the bottom labeled 'FlexO-x\_AP'. It has an output arrow to the left labeled 'FlexO-x/FlexO\_A\_Sk\_MP'. At the top, there are multiple output arrows labeled 'FlexO\_CP' with subscripts 1, 2, ..., x. + +Figure 15-17 – FlexO-x/FlexO\_A\_Sk function + +**Interfaces** + +Table 15-10 – FlexO-x/FlexO\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-------------------------|----------------------------------------| +| FlexO-x_AP: | x \times FlexO_CP: | +| FlexO-x_AI_CK | FlexO_CI_CK | +| FlexO-x_AI_D[1..x] | FlexO_CI_D | +| FlexO-x_AI_FS | FlexO_CI_FS | +| FlexO-x_AI_MFS | FlexO_CI_MFS | +| FlexO-x_AI_CRCerr[1..x] | FlexO_CI_CRCerr | +| FlexO-x_AI_TSF | FlexO_CI_SSF | + +**Processes** + +The processes associated with the FlexO-x/FlexO\_A\_Sk function are as depicted in Figure 15-18. + +NOTE – 10-bit frame and multi-frame synchronous disinterleaving of the $x$ FlexO instances in the FlexO- $x$ is performed in the OTSiG/FlexO- $x$ A\_Sk function. + +![Diagram of FlexO-x/FlexO_A_Sk processes showing signal flow from AI_TSF and AI_D[x] inputs through a FlexO-x_AP block to multiple FlexO_CP[x] outputs. The diagram includes signal labels such as AI_MFS, AI_FS, AI_CK, AI_D[1], AI_D[2], AI_D[x], CI_D, CI_CK, CI_FS, CI_MFS, CI_CRCerr, and CI_SSF. A box labeled 'Consequent actions' is connected to the aSSF signal.](d23fe5b7e93dc24c2ffa70b743025c5b_img.jpg) + +The diagram illustrates the FlexO-x/FlexO\_A\_Sk processes. At the bottom, a large grey block labeled 'FlexO-x\_AP' receives several input signals: AI\_MFS, AI\_FS, AI\_CK, AI\_D[1], AI\_D[2], AI\_D[x], CI\_CRCerr[1], CI\_CRCerr[2], CI\_CRCerr[x], and AI\_TSF. Above this block, multiple output signal groups are shown, labeled FlexO\_CP[1], FlexO\_CP[2], ..., FlexO\_CP[x]. Each group contains the signals CI\_D, CI\_CK, CI\_FS, CI\_MFS, CI\_CRCerr, and CI\_SSF. Lines connect the inputs to the FlexO-x\_AP block and then to the corresponding outputs. A signal labeled 'aSSF' is shown on the right, entering a box labeled 'Consequent actions'. + +Diagram of FlexO-x/FlexO\_A\_Sk processes showing signal flow from AI\_TSF and AI\_D[x] inputs through a FlexO-x\_AP block to multiple FlexO\_CP[x] outputs. The diagram includes signal labels such as AI\_MFS, AI\_FS, AI\_CK, AI\_D[1], AI\_D[2], AI\_D[x], CI\_D, CI\_CK, CI\_FS, CI\_MFS, CI\_CRCerr, and CI\_SSF. A box labeled 'Consequent actions' is connected to the aSSF signal. + +G.798(17)-Amd.3(21)\_F15-18 + +Figure 15-18 – FlexO- $x$ /FlexO A\_Sk processes + +### Consequent actions + +The function shall perform the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 15.3.5 FlexO- $n$ to OTUC $n_i$ adaptation function (FlexO- $n$ /OTUC $n_i$ A) + +The FlexO- $n$ to OTUC $n_i$ multiplexing adaptation functions perform the adaptation between the FlexO layer adapted information and the characteristic information of the OTUC $n_i$ layer signals. + +The set of $n$ FlexO instances may carry multiple OTUC $n_i$ ( $i = 1..N$ ) signals via GMP. In the most general case, the $n = n_1 + n_2 + \dots + n_N$ OTUC instances of the OTUC $n_i$ ( $i = 1..N$ ) are mapped to a FlexO- $x$ -- $m$ group of $m$ FlexO- $x$ - interfaces, each with a FlexO- $x$ - interface bandwidth of $\lceil n/m \rceil \times 100G$ . + +Tributary ports are dynamically created and deleted under the control of management. Each tributary port is associated with one OTUC $n_i$ connection point on one hand, and $n_i$ FlexO instances on the other hand. The multiplex structure identifier (MSI) carries the configuration of tributary ports to FlexO instances. + +#### 15.3.5.1 FlexO- $n$ to OTUC $n_i$ adaptation source function (FlexO- $n$ /OTUC $n_i$ A\_So) + +The FlexO- $n$ /OTUC $n_i$ A\_So function creates the $n$ FlexO signals from a free-running clock or an external synchronization clock. It asynchronously maps the up to $n$ OTUC client signals from the $N \times$ OTUC $n_i$ CPs into $n$ FlexO instances including justification control (JC) information. It adds FlexO payload and group management overhead. + +The information flow and processing of the FlexO- $n$ /OTUC $n_i$ A\_So function is defined with reference to Figures 15-19 and 15-20. + +## Symbol + +![Figure 15-19 – FlexO-n/OTUCn_i_A_So function symbol. The diagram shows a trapezoidal block labeled 'FlexO-n/OTUCn_i'. Inputs from the top are 'OTUCn_i_CP's (labeled 1, 2, 3, ..., N). Inputs from the left are 'FlexO-n/OTUCn_i_A_So_MP'. Input from the right is 'FlexO_TP'. Outputs from the bottom are 'FlexO_AP[1]' and 'FlexO_AP[n]', with a dashed oval indicating multiple outputs. A small text 'G.798(17)-Amd.3(21)_F15-19' is at the bottom right.](ea72687397bac53eb690650f371bfd63_img.jpg) + +Figure 15-19 – FlexO-n/OTUCn\_i\_A\_So function symbol. The diagram shows a trapezoidal block labeled 'FlexO-n/OTUCn\_i'. Inputs from the top are 'OTUCn\_i\_CP's (labeled 1, 2, 3, ..., N). Inputs from the left are 'FlexO-n/OTUCn\_i\_A\_So\_MP'. Input from the right is 'FlexO\_TP'. Outputs from the bottom are 'FlexO\_AP[1]' and 'FlexO\_AP[n]', with a dashed oval indicating multiple outputs. A small text 'G.798(17)-Amd.3(21)\_F15-19' is at the bottom right. + +Figure 15-19 – FlexO-n/OTUCni\_A\_So function + +## Interfaces + +Table 15-11 – FlexO-n/OTUCni\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| N × OTUCn_CP:
OTUCn_CI_CK
OTUCn_CI_D
OTUCn_CI_FS
OTUCn_CI_MFS
FlexO_TP:
FlexO_TI_CK
FlexO-n/OTUCni_A_So_MP:
FlexO-n/OTUCn i _A_So_MI_TxMSI[1..n]
FlexO-n/OTUCn i _A_So_MI_TxGID
FlexO-n/OTUCn i _A_So_MI_TxIID[1..n]
FlexO-n/OTUCn i _A_So_MI_TxFMAP | n × FlexO_AP:
FlexO_AI_D
FlexO_AI_CK
FlexO_AI_FS
FlexO_AI_MFS | + +## Processes + +The processes associated with the FlexO-n/OTUCni\_A\_So function are specific processes for each OTUCni\_CP, common processes and specific processes for each OTUC instance of each OTUCni and each FlexO instance of the n FlexO as depicted in Figure 15-20. + +### OTUCni specific processes + +The specific processes are performed independently for each OTUCni client signal that is multiplexed into the FlexO group. The specific processes perform the mapping of the OTUCni into a group of ni FlexO instances. + +**OTUCni FAS/MFAS insertion:** The function shall insert the FAS and MFAS into the OTUCni OH area as described in clause 11.3 of [ITU-T G.709]. + +**OTUCni distribution:** The function shall divide OTUCni into ni OTUC instance signals as described in clause 10.1.1 of [ITU-T G.709.1]. + +### Common processes + +**Clock generation:** The function shall generate a local FlexO clock (FlexO\_AI\_CK) of $4112/4097 \times 239/226 \times 99\,532\,800$ kbit/s $\pm 20$ ppm from the synchronization timing information clock input (TI\_CK) or, if the TI\_CK is absent, a free-running oscillator. The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock), apply. + +**FS and MFS generator:** The function shall generate the (multi)frame start reference signals AI\_FS and AI\_MFS for the FlexO signal. The AI\_FS signal shall be active once per 657 920 clock cycles. AI\_MFS shall be active once every 8 frames. + +**OTUCn to FlexO distribution:** The function assigns each OTUCn to $n_i$ specific FlexO instances of the FlexO group as defined by the multiplex structure (see Annex F of [ITU-T G.709.3]) under control of TxMSI[1..n]. The $n_i$ OTUC instances of an OTUCn are allocated to the assigned $n_i$ FlexO instances in sequential order. + +#### **OTUC and FlexO specific processes** + +**Mapping, frequency justification and bit-rate adaptation:** The function shall provide an elastic store (buffer) process for the OTUC client signal. The data signal OTUC\_CI shall be written into the buffer under the control of the associated input clock. + +Justification method GMP, as described below, is provided. The OTUC rate determines the base value and ranges for the parameters $C_n$ and $C_m$ . + +*FlexO payload:* The OTUC data shall be read out of the buffer and written onto groups of 256 successive bits of the FlexO 4-frame multi-frame payload area under the control of the FlexO clock and the GMP data/stuff control mechanism as defined in clause F.4 of [ITU-T G.709.3]. The 256-bit word alignment of the OTUC is preserved through the mapping procedure; i.e., the position of the first 256-bits of the OTUC is always located after an integer number of 256-bit words from the start of the FlexO 4-frame multi-frame payload structure. + +NOTE – In order to minimize implementation complexity and avoid the skew introduction between $n$ OTUC instance signals, $n_i$ lanes of mapping may use one unified mapping control mechanism to complete all the mapping processes and keep actions consistent between them. + +*Buffer size:* In the presence of jitter as specified by [ITU-T G.8251] and a frequency within the range specified in Table 8-1 of [ITU-T G.709.1], this mapping process shall not introduce any errors. The maximum buffer hysteresis, and therefore the maximum phase error introduced, is for further study. + +**All-0's OH insertion:** The function shall insert all-ZEROs into all the FlexO AM, EOH and BOH bit locations. + +**FlexO OH Insertion:** The function shall insert the overhead information of FlexO group signal in the corresponding overhead area (GID, IID, MAP) as defined in clause 9.2 of [ITU-T G.709.1]. + +**FlexO JC1/JC2/JC3, JC4/JC5/JC6:** The function shall generate the GMP $C_m$ and GMP $\sum C_{nD}$ information and insert this into the JC1/JC2/JC3 and JC4/JC5/JC6 bytes, respectively, according to the specification in clause F. and Annex D of [ITU-T G.709]. + +**FlexO MSI:** The function shall insert the TxMSI[p] into the MSI overhead byte as defined in clause F.3.1 of [ITU-T G.709.3]. The TxMSI[p] value, and as such the multiplex structure, is configurable via MI\_TxMSI[1..n]. + +**FlexO PT:** The function shall insert code "0000 0010" (GMP based OTUC mapping for OTUCn multiplexing) into the PT overhead byte as defined in clause 9.2.6.2 of [ITU-T G.709.1]. + +**FlexO GID:** The FlexO group identifier is inserted in the GID field. Its value is derived from reference point FlexO\_TT\_So\_MP. The GID format is described in clause 9.2.2.1 of [ITU-T G.709.1]. + +**FlexO IID:** The function shall insert the TxIID[p] into the IID overhead byte as defined in clause 9.2.2.2 of [ITU-T G.709.1]. The TxIID[p] value is configurable via MI\_TxIID[1..n]. + +**FlexO MAP:** The FlexO instance map is inserted in the FlexO MAP field. Its value is derived from reference point FlexO\_TT\_So\_MP. The FlexO MAP format is described in clause 9.2.2.3 of [ITU-T G.709.1]. + +![Figure 15-20 – FlexO-n/OTUCn_i_A_So processes. This block diagram illustrates the transmission (So) process for FlexO-n signals. At the top, multiple OTUCn inputs (OTUCn_CP[1] to OTUCn_CP[N]) are processed through FAS/MFAS insertion, resulting in OTUCn #1 distribution and OTUCn #N distribution. These are then mapped to a common FlexO distribution bus. A free-running clock generator provides a base clock (TI_CK) which is divided by 657920 and then by 8 to generate the Master FlexO Clock (MFS). The FlexO distribution bus carries signals for OTUC #1.1 to OTUC #N.n_N. Each OTUC signal is processed through an Elastic store (with Write Read pointers) and a Justification control and JC generation block. This is followed by the insertion of overhead bits (all-0's in AM, EOH, BOH) and specific overhead fields: MSI, PT, IID, GIP, MAP, and RES. The final output for each OTUC signal is a FlexO_AP signal, which includes data (D), clock (CK), frame sync (FS), and master flexo clock (MFS) components. The diagram also shows various management interface signals (MI_TxMSI, MI_TxIID, MI_TxGID, MI_TxFMAP) and timing signals (AI_D, AI_CK, AI_FS, AI_MFS).](1b683c1801ad8e24cf113cede25b36f0_img.jpg) + +Figure 15-20 – FlexO-n/OTUCn\_i\_A\_So processes. This block diagram illustrates the transmission (So) process for FlexO-n signals. At the top, multiple OTUCn inputs (OTUCn\_CP[1] to OTUCn\_CP[N]) are processed through FAS/MFAS insertion, resulting in OTUCn #1 distribution and OTUCn #N distribution. These are then mapped to a common FlexO distribution bus. A free-running clock generator provides a base clock (TI\_CK) which is divided by 657920 and then by 8 to generate the Master FlexO Clock (MFS). The FlexO distribution bus carries signals for OTUC #1.1 to OTUC #N.n\_N. Each OTUC signal is processed through an Elastic store (with Write Read pointers) and a Justification control and JC generation block. This is followed by the insertion of overhead bits (all-0's in AM, EOH, BOH) and specific overhead fields: MSI, PT, IID, GIP, MAP, and RES. The final output for each OTUC signal is a FlexO\_AP signal, which includes data (D), clock (CK), frame sync (FS), and master flexo clock (MFS) components. The diagram also shows various management interface signals (MI\_TxMSI, MI\_TxIID, MI\_TxGID, MI\_TxFMAP) and timing signals (AI\_D, AI\_CK, AI\_FS, AI\_MFS). + +Figure 15-20 – FlexO-n/OTUCn\_i\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 15.3.5.2 FlexO-n to OTUCn\_i adaptation sink function (FlexO-n/OTUCn\_i\_A\_Sk) + +The FlexO-n/OTUCn\_i\_A\_Sk function extracts the FlexO group management and payload overhead and monitors the reception of the correct payload type. It recovers the up to $n \times$ OTUC signals from + +the N OTUCn using the justification control information (JC, JC1/2/3/4/5/6 overhead). It performs frame and multi-frame alignment of the OTUC. + +The information flow and processing of the FlexO-n/OTUCn\_A\_Sk function is defined with reference to Figures 15-21, 15-22 and 15-23. + +### Symbol + +![Figure 15-21 – FlexO-n/OTUCn_i_A_Sk function symbol diagram. The diagram shows a trapezoidal block labeled 'FlexO-n/OTUCn_i'. On the left, an arrow labeled 'FlexO-n/OTUCn_i_A_Sk_MP' points into the block. On the right, an arrow labeled 'OTUCn_i_CPs' points out of the block, with sub-indices 1, 2, 3, and N. Below the block, two dashed arrows represent input and output vectors: 'FlexO_AP[1]' pointing into the block and 'FlexO_AP[n]' pointing out of the block. A small note 'G.798(17)-Amd.3(21)_F15-21' is at the bottom right.](a70d42d1621bc4d20c0f9d2e396222c1_img.jpg) + +Figure 15-21 – FlexO-n/OTUCn\_i\_A\_Sk function symbol diagram. The diagram shows a trapezoidal block labeled 'FlexO-n/OTUCn\_i'. On the left, an arrow labeled 'FlexO-n/OTUCn\_i\_A\_Sk\_MP' points into the block. On the right, an arrow labeled 'OTUCn\_i\_CPs' points out of the block, with sub-indices 1, 2, 3, and N. Below the block, two dashed arrows represent input and output vectors: 'FlexO\_AP[1]' pointing into the block and 'FlexO\_AP[n]' pointing out of the block. A small note 'G.798(17)-Amd.3(21)\_F15-21' is at the bottom right. + +Figure 15-21 – FlexO-n/OTUCn\_A\_Sk function + +### Interfaces + +Table 15-12 – FlexO-n/OTUCn\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n × FlexO_AP:
FlexO_AI_D
FlexO_AI_CK (Note)
FlexO_AI_FS
FlexO_AI_MFS
FlexO_AI_CRCerr
FlexO_AI_TSF
FlexO-n/OTUCn_A_Sk_MP:
FlexO-n/OTUC n _A_Sk_MI_ExGID
FlexO-n/OTUC n _A_Sk_MI_ExFMAP
FlexO-n/OTUC n _A_Sk_MI_ExMSI[1..n] | N × OTUCn_CP:
OTUC n _CI_CK
OTUC n _CI_D
OTUC n _CI_FS
OTUC n _CI_MFS
OTUC n _CI_SSF
FlexO-n/OTUCn_A_Sk_MP:
FlexO-n/OTUC n _A_Sk_MI_AcGID[1..n]
FlexO-n/OTUC n _A_Sk_MI_AcFMAP[1..n]
FlexO-n/OTUC n _A_Sk_MI_AcIID[1..n]
FlexO-n/OTUC n _A_Sk_MI_AcPT[1..n]
FlexO-n/OTUC n _A_Sk_MI_AcMSI[1..n]
FlexO-n/OTUC n _A_Sk_MI_cGIDM
FlexO-n/OTUC n _A_Sk_MI_cFMM
FlexO-n/OTUC n _A_Sk_MI_cPLM
FlexO-n/OTUC n _A_Sk_MI_cMSIM[1..N]
FlexO-n/OTUC n _A_Sk_MI_cLOFLOM[1..N]
FlexO-n/OTUC n _A_Sk_MI_cLOL[1..N] | +| NOTE – The function only needs one FlexO_AI_CK, e.g., FlexO_AI_CK[1]. | | + +### Processes + +The processes associated with the FlexO-n/OTUCn\_A\_Sk function are specific processes for each FlexO instance of the n FlexO, common processes, specific processes for each OTUC instance of each OTUCn and specific processes for each OTUCn\_CP as depicted in Figures 15-22 and 15-23. + +### FlexO specific processes + +**FlexO OH Extraction:** The function shall extract the overhead of FlexO group interface (GID, IID and MAP) from each FlexO frame as defined in clause 9.2 of [ITU-T G.709.1]. + +**FlexO GID:** The GID fields shall be extracted from the FlexO overhead and processed as specified in clause B.2.2.1. The accepted GID values are available at the MP (MI\_AcGID[i]) and are used for dGIDM defect detection. + +NOTE – A GID field carrying an all-0's value indicates the presence of an unequipped FlexO instance. Such unequipped FlexO instance represents a FlexO-x configuration mistake. + +**FlexO IID:** The IID fields shall be extracted from the FlexO overhead and processed as specified in clause B.2.2.1. The accepted IID values are available at the MP (MI\_AcIID[i]) and are used for dFMM defect detection. + +**FlexO MAP:** The FlexO MAP fields shall be extracted from the FlexO overhead and processed as specified in clause B.2.2.3.1. The accepted MAP values are available at the MP (MI\_AcFMAP[i]) and are used for dFMM defect detection. + +**PT:** The function shall extract the PT byte from the PT overhead as defined in clause 8.7.1.2. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. The PLM detection shall be based on the comparison of the accepted PT with the value 0x02. + +**MSI:** The function shall extract the MSI byte from the MSI overhead as defined in clause 8.7.2.4. The accepted MSI (AcMSI[1..n]) is available at the MP (MI\_AcMSI[1..n]). The multiplex structure is defined by ExMSI[1..n], which is configurable via MI\_ExMSI[1..n]. + +#### **Common processes** + +**FlexO-n Reorder:** The function shall reorder n FlexO instances based on IID as described in clauses 9.2.3 and 10.3 of [ITU-T G.709.1]. + +**FlexO to OTUCn distribution:** The function assigns the individual FlexO instances to specific OTUCn instances as defined by the multiplex structure (see Annex F of [ITU-T G.709.3]) under control of MI\_ExMSI[1..n]. + +![Figure 15-22 – FlexO-n/OTUCn_i_A_Sk processes. This block diagram illustrates the internal architecture of FlexO-n/OTUCn_i_A_Sk processes. At the top, multiple OTUCn specific processes (labeled #1 to #N) are shown, each receiving inputs from FlexO-n to OTUCn distribution blocks and outputting to ODUCn_CP [1] and ODUCn_CP [N] via CI_D, CI_CK, CI_FS, CI_MFS, and CI_SSF signals. Each OTUCn process contains internal blocks for AI_TSF, dFMM, dGIDM, dPLM, dMSIM, MI_cMSIM, MI_cLOL, and MI_cLOFLOM. Below the OTUCn processes, FlexO-n Reorder blocks are shown, which receive inputs from FlexO_AP blocks (containing AI_D, AI_CK, AI_FS, AI_MFS, AI_TFS, and AI_CRCerr) and output to Extract MSI, Extract PT, Extract GID, Extract IID, and Extract MAP blocks. These extraction blocks output to AcMSI, AcPT, AcGID, AcIID, and AcFMAP signals, which are then processed by detection blocks (dMSIM, dPLM, dGIDM, dFMM) to produce MI_ExMSI, MI_ExGID, and MI_ExFMAP signals. A central 'Defect correlations' block receives inputs from AI_TSF, dFMM, dGIDM, dPLM, dMSIM, dLOL, and dLOFLOM across all OTUCn processes and outputs to MI_cFMM, MI_cGIDM, MI_cPLM, MI_cMSIM, MI_cLOL, and MI_cLOFLOM signals. A vertical label on the right side reads 'FlexO-n/OTUCn_A_Sk_MP'.](601a4295d83c115fcd66101f49de0c4e_img.jpg) + +Figure 15-22 – FlexO-n/OTUCn\_i\_A\_Sk processes. This block diagram illustrates the internal architecture of FlexO-n/OTUCn\_i\_A\_Sk processes. At the top, multiple OTUCn specific processes (labeled #1 to #N) are shown, each receiving inputs from FlexO-n to OTUCn distribution blocks and outputting to ODUCn\_CP [1] and ODUCn\_CP [N] via CI\_D, CI\_CK, CI\_FS, CI\_MFS, and CI\_SSF signals. Each OTUCn process contains internal blocks for AI\_TSF, dFMM, dGIDM, dPLM, dMSIM, MI\_cMSIM, MI\_cLOL, and MI\_cLOFLOM. Below the OTUCn processes, FlexO-n Reorder blocks are shown, which receive inputs from FlexO\_AP blocks (containing AI\_D, AI\_CK, AI\_FS, AI\_MFS, AI\_TFS, and AI\_CRCerr) and output to Extract MSI, Extract PT, Extract GID, Extract IID, and Extract MAP blocks. These extraction blocks output to AcMSI, AcPT, AcGID, AcIID, and AcFMAP signals, which are then processed by detection blocks (dMSIM, dPLM, dGIDM, dFMM) to produce MI\_ExMSI, MI\_ExGID, and MI\_ExFMAP signals. A central 'Defect correlations' block receives inputs from AI\_TSF, dFMM, dGIDM, dPLM, dMSIM, dLOL, and dLOFLOM across all OTUCn processes and outputs to MI\_cFMM, MI\_cGIDM, MI\_cPLM, MI\_cMSIM, MI\_cLOL, and MI\_cLOFLOM signals. A vertical label on the right side reads 'FlexO-n/OTUCn\_A\_Sk\_MP'. + +**Figure 15-22 – FlexO-n/OTUCni\_A\_Sk processes** + +### OTUC specific processes + +**Demapping:** The function shall demap the OTUC instance signal from FlexO frame as described in clause F of [ITU-T G.709.3]. + +Justification method GMP as described below is provided. The OTUC rate determines the base value and ranges for the parameters $C_{n}$ and $C_{m}$ . + +**FlexO JC1/2/3 and JC4/5/6:** The function shall interpret the GMP overhead information in the JC1/2/3 and JC4/5/6 bytes as defined in clause F of [ITU-T G.709.3] in order to determine the number of 256-bit OTUC entities in the next FlexO 4-frame multi-frame. + +**Demapping, CBR clock generation:** The function shall provide an elastic store (buffer) process. + +*FlexO:* The OTUC data shall be extracted from the groups of 256 successive bits of the FlexO payload area under the control of the GMP data/stuff control mechanism as defined in clause F.4 of [ITU-T G.709.3] and be written into the buffer. The $C_n$ information associated with the OTUC is computed from the GMP $C_m$ and $\sum C_{nD}$ parameters carried within the JC1/2/3 and JC 4/5/6 overhead of the FlexO 4-frame multi-frame as specified in clause F.3.2 of [ITU-T G.709.3]. For the GMP data/stuff control mechanism, refer to Annex D of [ITU-T G.709]. + +The OTUC data (CI\_D) shall be read out of the buffer under the control of the OTUC clock (CI\_CK). + +*Smoothing and jitter limiting process:* The function shall provide for a clock smoothing and elastic store (buffer) process. The OTUC data signal shall be written into the buffer under the control of the associated (gapped) FlexO payload input clock (with a frequency accuracy within $\pm 20$ ppm). The data signal shall be read out of the buffer under the control of a smoothed (equally spaced) OTUC clock (the rate is determined by the OTUC signal at the input of the remote FlexO-nP/OTUCni\_A\_So). + +The clock parameters, including jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCp clock), apply. + +*Buffer size:* In the presence of jitter as specified by [ITU-T G.8251] and a frequency within the tolerance range specified for the OTUC signal in Table 7-1 of [ITU-T G.709], this justification process shall not introduce any errors. + +Following a step in frequency of the OTUC signal transported (for example, due to reception of OTUCni\_CI from a new OTUCni\_TT\_So at the far end or removal of an OTUCni-AIS or ODUCni-AIS signal with a frequency offset), there will be a maximum recovery time of X seconds after which this process shall not generate any bit errors. The value of X is for further study; a value of one second has been proposed. + +#### **OTUCni specific processes** + +**OTUCni Frame and multi-frame alignment:** The function shall recover the OTUC instance frame start and multi-frame start as described in clause 8.2.3. + +**OTUCni Deskew:** The function shall compensate the skew between ni OTUC instances based on OTUC instance frame start indication (alignment markers) as described in clause 10.1.4 of [ITU-T G.709.1]. The alignment process shall establish the delay compensation, compensating the differential delay between the OTUC instance signals as given in clause 10.1.4 of [ITU-T G.709.1]. The compensation between the OTUC instances is achieved by an elastic store per OTUC instance. Each OTUC instance signal shall be written into an elastic store with the OTUC frame start indication. Each elastic store shall be capable of compensating at least 300 ns of absolute differential delay between the OTUC instances for FlexO short reach applications and at least 1 $\mu$ s of absolute differential delay between the OTUC instances for FlexO long reach applications. The process has two states, out-of-alignment (OOA) and in-alignment (IA). The alignment start shall be maintained during the OOA state. In the OOA state, if the bytes of the OTUC instances signals can be written consistently into the elastic store in the presence of a differential delay in line without exceeding the buffering time, the IA state shall be entered. In this case, the differential delay can be compensated. In the IA state, if the differential delay between two OTUC instances exceeds the maximum delay that can be compensated, the OOA state shall be entered. + +**OTUCni Recover:** The function shall recombine ni OTUC instances into an OTUCni as described in clause F.1 of [ITU-T G.709.3]. + +![Figure 15-23 – FlexO-n/OTUCn_i_A_Sk client specific processes. This block diagram illustrates the internal architecture of a FlexO-n/OTUCn_i_A_Sk client. At the bottom, multiple tributary ports (i=1..N) provide data (D[i, n_j]), clock (CK[i, n_j]), and frame synchronization (FS[i, n_j]) signals. Each port has an 'Extract JC' block feeding into a 'Justification control'. These controls manage 'Elastic store' units (WR/Read, RD/Write) which output data (D[i, n_j]), clock (CK[i, n_j]), and frame synchronization (FS[i, n_j]) signals. A 'Clock generator (ODCp)' receives clock signals (CK[i, 1]) and provides write (WR) and read (RD) signals to the elastic stores. Above the elastic stores, 'OTUC frame and multiframe alignment' blocks process the data to produce 'dLOFLOM[i, 1]' and 'dLOFLOM[i, n_j]' signals. These are followed by 'OTUCn_i deskew' and 'OTUCn_i recover' blocks, which output 'MFS', 'FS', 'CK', and 'D' signals. A 'Select normal/AIS' block contains 'Normal' and 'AIS' sub-blocks, receiving 'aAIS' and 'aSSF' signals from 'Consequent actions'. The 'Consequent actions' block also receives 'AI_TSF[i, 1..n_j]' and various defect signals: 'dFMM', 'dGIDM', 'dPLM', 'dMSIM[i]', 'dLOL[i]', and 'dLOFLOM[i, 1..n_j]'. The 'Select normal/AIS' block outputs 'CI_MFS', 'CI_FS', 'CI_CK', and 'CI_D' signals. Finally, an 'OTUCn_CP[i]' block at the top outputs 'CI_SSF'.](600c8f9d34f98c395e29c266aebfbd8e_img.jpg) + +Figure 15-23 – FlexO-n/OTUCn\_i\_A\_Sk client specific processes. This block diagram illustrates the internal architecture of a FlexO-n/OTUCn\_i\_A\_Sk client. At the bottom, multiple tributary ports (i=1..N) provide data (D[i, n\_j]), clock (CK[i, n\_j]), and frame synchronization (FS[i, n\_j]) signals. Each port has an 'Extract JC' block feeding into a 'Justification control'. These controls manage 'Elastic store' units (WR/Read, RD/Write) which output data (D[i, n\_j]), clock (CK[i, n\_j]), and frame synchronization (FS[i, n\_j]) signals. A 'Clock generator (ODCp)' receives clock signals (CK[i, 1]) and provides write (WR) and read (RD) signals to the elastic stores. Above the elastic stores, 'OTUC frame and multiframe alignment' blocks process the data to produce 'dLOFLOM[i, 1]' and 'dLOFLOM[i, n\_j]' signals. These are followed by 'OTUCn\_i deskew' and 'OTUCn\_i recover' blocks, which output 'MFS', 'FS', 'CK', and 'D' signals. A 'Select normal/AIS' block contains 'Normal' and 'AIS' sub-blocks, receiving 'aAIS' and 'aSSF' signals from 'Consequent actions'. The 'Consequent actions' block also receives 'AI\_TSF[i, 1..n\_j]' and various defect signals: 'dFMM', 'dGIDM', 'dPLM', 'dMSIM[i]', 'dLOL[i]', and 'dLOFLOM[i, 1..n\_j]'. The 'Select normal/AIS' block outputs 'CI\_MFS', 'CI\_FS', 'CI\_CK', and 'CI\_D' signals. Finally, an 'OTUCn\_CP[i]' block at the top outputs 'CI\_SSF'. + +G.798(17)-Amd.3(21)\_F15-23 + +**Figure 15-23 – FlexO-n/OTUCni\_A\_Sk client specific processes** + +## Defects + +The function shall detect dGIDM, dFMM, dPLM, dMSIM[i], dLOFLOM[i,j] and dLOL[i] where 'i' is 1..N, j = 1..ni, and ji = 1..ni. + +**dGIDM:** See clause B.1.1.2.1. dGIDM shall be set to false during $\sum AI\_TSF[j]$ . + +**dFMM:** See clause B.1.1.2.2. dFMM shall be set to false during $\sum AI\_TSF[j]$ . + +**dPLM:** See clause 6.2.4.2. The expected payload type is "0000 0010". dPLM shall be set to false during $\sum AI\_TSF[j]$ . + +Per OTUCni tributary port #i (i = 1..N): + +**dMSIM[i]:** See clause 6.2.9.2. dMSIM is detected per active OTUCni. + +**dLOL[i]**: If the alignment process is in the OLA state, dLOL[i] shall be set to true. dLOL[i] shall be set to false when the alignment process is in the ILA state; dLOL[i] shall be set to false during $\sum_{AI\_TSF}[i, 1..n_i]$ . + +Per OTUC instance #(i,ji) (i = 1 .. N, ji = 1..ni): + +**dLOFLOM[i,ji]**: See clause 6.2.5.3. + +### Consequent actions + +Per OTUCn tributary port #i (i = 1..N): + +$$aSSF[i] \leftarrow dGIDM \text{ or } dFMM \text{ or } dPLM \text{ or } dLOL[i] \text{ or } \sum_j dLOFLOM[i,j] \text{ or } dMSIM[i] \text{ or } \sum_{AI\_TSF}[j]$$ + +$$aAIS[i] \leftarrow dGIDM \text{ or } dFMM \text{ or } dPLM \text{ or } dLOL[i] \text{ or } \sum_j dLOFLOM[i,j] \text{ or } dMSIM[i] \text{ or } \sum_{AI\_TSF}[j]$$ + +On declaration of aAIS[i], the function shall output an all-ONES pattern/signal within two frames on the OTUCn\_CP[i]. On clearing aAIS[i], the all-ONES pattern/signal shall be removed within two frames, with normal data being output. The AIS clock, frame start and multi-frame start shall be independent from the incoming clock, frame start and multi-frame start. The clock has to be within the OTUCn frequency tolerance range as specified in Table 7-1 of [ITU-T G.709]. Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCa clock) apply. + +### Defect correlations + +$$cGIDM \leftarrow dGIDM$$ + +$$cFMM \leftarrow dFMM \text{ and (not } dGIDM)$$ + +$$cPLM \leftarrow dPLM \text{ and (not } dGIDM) \text{ and (not } dFMM)$$ + +Per OTUCn tributary port #i (i = 1..N, ji = 1..ni): + +$$cMSIM[i] \leftarrow dMSIM[i] \text{ and (not } dGIDM) \text{ and (not } dFMM) \text{ and (not } dPLM)$$ + +$$cLOFLOM[i] \leftarrow \sum_j (dLOFLOM[i,j] \text{ and (not } AI\_TSF[j])) \text{ and (not } dGIDM) \text{ and (not } dFMM)$$ + +$$cLOL[i] \leftarrow dLOL[i] \text{ and (not } dGIDM) \text{ and (not } dFMM) \text{ and (not } dPLM) \text{ and (not } \sum_j dLOFLOM[i,j])$$ + +**Performance monitoring:** None. + +## 15.4 Compound functions + +### 15.4.1 FlexO-x compound trail termination function (FlexO-x\_CTT) + +The FlexO-x compound trail termination function (FlexO-x\_CTT) contains one FlexO-x\_TT function, one FlexO-x/FlexO\_A function and 1 to x FlexO\_TT functions. + +NOTE – This FlexO-x\_CTT function is typically deployed on FlexO-x-RS interfaces. This FlexO-x\_CTT function may also be deployed on other FlexO-x- interfaces. + +Figure 15-24 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Figure 15-24: FlexO-x_CTT diagram showing two FlexO-x blocks. The left block has inputs FlexO-x_APs (1, 2, ..., x) and FlexO-x_TCP at the bottom. The right block has outputs FlexO-x_APs (1, 2, ..., x) and FlexO-x_TCP at the bottom. A horizontal arrow labeled FlexO-x_RP points from the right block to the left block. A small note G.798(17)-Amd.3(21)_F15-24 is at the bottom right.](29e446c8e2363d27e282737c3d7c3421_img.jpg) + +Figure 15-24: FlexO-x\_CTT diagram showing two FlexO-x blocks. The left block has inputs FlexO-x\_APs (1, 2, ..., x) and FlexO-x\_TCP at the bottom. The right block has outputs FlexO-x\_APs (1, 2, ..., x) and FlexO-x\_TCP at the bottom. A horizontal arrow labeled FlexO-x\_RP points from the right block to the left block. A small note G.798(17)-Amd.3(21)\_F15-24 is at the bottom right. + +Figure 15-24 – FlexO-*x* \_CTT + +**15.4.1.1 FlexO-*x* compound trail termination source function (FlexO-*x* \_CTT\_So)** + +The FlexO-*x* \_CTT\_So function interleaves *x* FlexO signals from the *x* × FlexO\_APs into a FlexO-*x* signal adding FlexO-*x* section monitoring overhead – including the RPF signal – in the STAT overhead field. For the case that up to *x*-1 FlexO\_APs are not connected and do not receive an input signal, the function replaces these FlexO\_AI by an all-0's unequipped FlexO signal. + +The information flow and processing of the FlexO-*x* \_CTT\_So function is defined with reference to Figures 15-25 and 15-26. + +**Symbol** + +![Figure 15-25: FlexO-x_TT_So function symbol. A FlexO-x block has inputs FlexO_APs (1, 2, ..., x) at the top and FlexO-x_RP from the right. It has an output FlexO-x_TCP at the bottom. A small note G.798(17)-Amd.3(21)_F15-25 is at the bottom right.](d7a98a717edbc26ca1508aaab7a566f4_img.jpg) + +Figure 15-25: FlexO-x\_TT\_So function symbol. A FlexO-x block has inputs FlexO\_APs (1, 2, ..., x) at the top and FlexO-x\_RP from the right. It has an output FlexO-x\_TCP at the bottom. A small note G.798(17)-Amd.3(21)\_F15-25 is at the bottom right. + +Figure 15-25 – FlexO-*x* \_TT\_So function + +**Interfaces** + +Table 15-13 – FlexO-*x* \_CTT\_So inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 to x × FlexO_AP:
FlexO- x _AI_CK
FlexO- x _AI_D[1.. x ]
FlexO- x _AI_FS
FlexO- x _AI_MFS
FlexO-x _RP:
FlexO- x _RI_RPF | FlexO-x _TCP:
FlexO- x _CI_CK
FlexO- x _CI_D[1.. x ]
FlexO- x _CI_FS
FlexO- x _CI_MFS | + +**Atomic functions** + +The atomic functions associated with the FlexO-*x* \_CTT\_So function and the inputs and outputs are as depicted in Figure 15-26. + +**FlexO\_TT\_So:** 1 to $x$ instances of this atomic function are present. Typically, the first $m-1$ FlexO- $x$ \_CTT\_So functions that support the FlexO- $x$ -- $m$ interface group contain $x$ instances of this atomic function and the last FlexO- $x$ \_CTT\_So function contains $n - x \times m$ instances, with $n$ determined by the FlexO- $n$ /\_A\_So function. + +**FlexO- $x$ /FlexO\_A\_So:** 1 instance of this atomic function is present. + +**FlexO- $x$ \_TT\_So:** 1 instance of this atomic function is present. + +**FlexO\_AP:** 1 to $x$ instances of this reference point are present. Typically, the first $m-1$ FlexO- $x$ \_CTT\_So functions that support the FlexO- $x$ -- $m$ interface group contain $x$ instances of this reference point and the last FlexO- $x$ \_CTT\_So function contains $n - x \times m$ instances, with $n$ determined by the FlexO- $n$ /\_A\_So function. + +**FlexO- $x$ \_TCP:** 1 instance of this reference point is present. + +**FlexO- $x$ \_RP:** 1 instance of this reference point is present. + +![Diagram of FlexO-x_CTT_So atomic functions showing signal flow from FlexO-APs through FlexO and FlexO-x blocks to FlexO-x_TCP.](000a505684f871e191bad335434f58a9_img.jpg) + +The diagram illustrates the signal flow within the FlexO- $x$ \_CTT\_So atomic functions. At the top, multiple input signals, labeled 1, 2, ..., $x$ , enter from the FlexO\_APs. Each input signal passes through a trapezoidal block labeled 'FlexO'. The outputs of these 'FlexO' blocks converge into a single horizontal bar labeled 'FlexO- $x$ /FlexO'. Below this bar, the signal passes through a trapezoidal block labeled 'FlexO- $x$ '. The final output of the system is labeled 'FlexO- $x$ \_TCP' at the bottom. A small text label 'G.798(17)-Amd.3(21)\_F15-26' is located at the bottom right of the diagram. + +Diagram of FlexO-x\_CTT\_So atomic functions showing signal flow from FlexO-APs through FlexO and FlexO-x blocks to FlexO-x\_TCP. + +**Figure 15-26 – FlexO- $x$ \_CTT\_So atomic functions** + +#### **15.4.1.2 FlexO- $x$ compound trail termination sink function (FlexO- $x$ \_CTT\_Sk)** + +The FlexO- $x$ \_CTT\_Sk function reports the state of the FlexO- $x$ trail. It extracts FlexO- $x$ monitoring overhead – including the RPF signal – in the STAT overhead field from the FlexO signal at its FlexO- $x$ \_TCP, detects for the RPF defect, and forwards the error and defect information as backward indications to the companion FlexO- $x$ \_CTT\_So function. The function disinterleaves $x$ FlexO signals from the FlexO- $x$ signal and present these at the $x$ FlexO\_APs. + +The information flow and processing of the FlexO- $x$ \_CTT\_Sk function is defined with reference to Figures 15-27 and 15-28. + +## Symbol + +![Symbol diagram for FlexO-x_CTT_Sk function. A central triangle labeled 'FlexO-x' has an input arrow from the bottom labeled 'FlexO-x_TCP'. It has an output arrow to the right labeled 'FlexO-x_RP' and an output arrow to the left labeled 'FlexO-x_CTT_Sk_MP'. Above the triangle, there are x output arrows labeled 'FlexO-x_AP' with subscripts 1, 2, and x.](2339cc41fe4145cad3d90c1cd295dfd3_img.jpg) + +G.798(17)-Amd.3(21)\_F15-27 + +Symbol diagram for FlexO-x\_CTT\_Sk function. A central triangle labeled 'FlexO-x' has an input arrow from the bottom labeled 'FlexO-x\_TCP'. It has an output arrow to the right labeled 'FlexO-x\_RP' and an output arrow to the left labeled 'FlexO-x\_CTT\_Sk\_MP'. Above the triangle, there are x output arrows labeled 'FlexO-x\_AP' with subscripts 1, 2, and x. + +Figure 15-27 – FlexO-*x*\_CTT\_Sk function + +## Interfaces + +Table 15-14 – FlexO-*x*\_CTT\_Sk inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FlexO-x_TCP:
FlexO- x _CI_CK
FlexO- x _CI_D[1.. x ]
FlexO- x _CI_FS
FlexO- x _CI_MFS
FlexO- x _CI_SSF | 1 to x × FlexO-x_AP:
FlexO_AI_CK
FlexO_AI_D[1.. x ]
FlexO_AI_FS
FlexO_AI_MFS
FlexO_AI_CRCerr[1.. x ]
FlexO_AI_TSF
FlexO-x_RP:
FlexO- x _RI_RPF
FlexO-x_CTT_Sk_MP:
FlexO- x _CTT_Sk_MI_cRDI
FlexO- x _CTT_Sk_MI_cSSF | + +## Atomic functions + +The atomic functions associated with the FlexO-*x*\_CTT\_Sk function and the inputs and outputs are as depicted in Figure 15-28. + +**FlexO\_TT\_Sk:** 1 to *x* instances of this atomic function are present. Typically, the first *m*-1 FlexO-*x*\_CTT\_Sk functions that support the FlexO-*x*--*m* interface group contain *x* instances of this atomic function and the last FlexO-*x*\_CTT\_Sk function contains *n* – *x* × *m* instances, with *n* determined by the FlexO-*n*/\_A\_Sk function. + +**FlexO-*x*/FlexO\_A\_Sk:** 1 instance of this atomic function is present. + +**FlexO-*x*\_TT\_Sk:** 1 instance of this atomic function is present. + +**FlexO\_AP:** 1 to *x* instances of this reference point are present. Typically, the first *m*-1 FlexO-*x*\_CTT\_Sk functions that support the FlexO-*x*--*m* interface group contain *x* instances of this reference point and the last FlexO-*x*\_CTT\_Sk function contains *n* – *x* × *m* instances, with *n* determined by the FlexO-*n*/\_A\_Sk function. + +**FlexO-*x*\_TCP:** 1 instance of this reference point is present. + +**FlexO-*x*\_RP:** 1 instance of this reference point is present. + +**FlexO-*x*\_CTT\_Sk\_MP:** 1 instance of this reference point is present and presents the information of the FlexO-*x*\_TT\_Sk\_MP. + +![Diagram of FlexO-x_CTT_Sk atomic functions showing multiple FlexO units (1, 2, ..., x) connected to a central FlexO-x block. The diagram shows data flow from FlexO-x_TCP through FlexO-x_CTT_Sk_MP, then through a central FlexO-x block to FlexO-x_RP. Above the central block, multiple FlexO units are shown, each with a FlexO-x_TT_Sk_MP input and a FlexO output. The FlexO outputs are connected to FlexO_APs. The diagram is labeled G.798(17)-Amd.3(21)_F15-28.](5083128e335a383c042e15d2d8795c95_img.jpg) + +Diagram of FlexO-x\_CTT\_Sk atomic functions showing multiple FlexO units (1, 2, ..., x) connected to a central FlexO-x block. The diagram shows data flow from FlexO-x\_TCP through FlexO-x\_CTT\_Sk\_MP, then through a central FlexO-x block to FlexO-x\_RP. Above the central block, multiple FlexO units are shown, each with a FlexO-x\_TT\_Sk\_MP input and a FlexO output. The FlexO outputs are connected to FlexO\_APs. The diagram is labeled G.798(17)-Amd.3(21)\_F15-28. + +**Figure 15-28 – FlexO-*x* CTT\_Sk atomic functions** + +## 16 OTSi adaptation functions + +### 16.1 OTSi to OTUk or OTUk-RS adaptation function (OTSi/OTUk\_A or OTSi/OTUk-RS\_A) + +The OTSi to OTUk (*k* = 0, 1, 2, 3, 4) or OTUk-RS (*k* = 25u, 25, 50u, 50) adaptation functions perform the adaptation between the OTSi layer adapted information and the characteristic information of the completely standardized OTUk or OTUk-RS layer signal. For OTUk with *k* = 0, 1, 2, 3, 4, three types of functions are defined: one that supports the standardized forward error correction (FEC), one that does not support FEC, and one that supports vendor-specific FEC. For OTUk-RS with *k* = 25u, 25, 50u, 50, the functions support the RS FEC schemes specified in [ITU-T G.709.4]. + +**Table 16-1 – OTSi to OTUk adaptation functions (*k* = 0, 1, 2, 3, 4)** + +| Function type | Function name | OTUk | +|---------------|-----------------------------------------------------------|---------------------| +| OTSi/OTUk-a_A | OTSi to OTUk adaptation function with FEC | k =0,1,2,3,4 | +| OTSi/OTUk-b_A | OTSi to OTUk adaptation function without FEC | k =0,1,2,3 | +| OTSi/OTUk-v_A | OTSi to OTUk adaptation function with vendor-specific FEC | k =0,1,2,3,4 | + +NOTE 1 – OTSi/OTUk\_A is used throughout this clause as shorthand for the specific function type for *k* = 0, 1, 2, 3, 4. + +NOTE 2 – The OTSi to OTU4-SC adaptation function with SC FEC (OTSi/OTU4-SC\_A) is specified in clause 16.3. + +#### 16.1.1 OTSi to OTUk adaptation source function (OTSi/OTUk\_A\_So; *k* = 0, 1, 2, 3, 4) + +The information flow and processing of the OTSi/OTUk\_A\_So function is defined with reference to Figures 16-1 and 16-2. + +## Symbol + +![Symbol diagram for OTSi/OTUk_A_So function. An input OTUk_CP enters a trapezoidal block labeled OTSi/OTUk from the top. An output OTSi_AP exits the block from the bottom. The reference G.798(17)_F16-1 is shown below the output.](09e709f61c6ce948e16ddcc0f7efebcb_img.jpg) + +Symbol diagram for OTSi/OTUk\_A\_So function. An input OTUk\_CP enters a trapezoidal block labeled OTSi/OTUk from the top. An output OTSi\_AP exits the block from the bottom. The reference G.798(17)\_F16-1 is shown below the output. + +Figure 16-1 – OTSi/OTUk\_A\_So function (k = 0, 1, 2, 3, 4) + +## Interfaces + +Table 16-2 – OTSi/OTUk\_A\_So inputs and outputs (k = 0, 1, 2, 3, 4) + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------|--------------------------------| +| OTUk_CP:
OTUk_CI_CK
OTUk_CI_D
OTUk_CI_FS
OTUk_CI_MFS | OTSi_AP:
OTSi_AI_PLD | + +## Processes + +The processes associated with the OTSi/OTUk\_A\_So function are as depicted in Figure 16-2. + +**FAS/MFAS insertion:** The function shall insert the FAS and MFAS into the OTU frame alignment area as described in [ITU-T G.709]. + +**FEC encoder:** See clause 8.5.2 for the OTSi/OTUk-a\_A\_So function, clause 8.5.1 for the OTSi/OTUk-b\_A\_So function and clause 8.5.3 for the OTSi/OTUk-v\_A\_So function. + +**Scrambler:** The function shall scramble the signal as defined in clause 11.2 of [ITU-T G.709]. + +![Process diagram for OTSi/OTUk_A_So. The input OTUk_CP is shown at the top with four vertical lines labeled CI_D, CI_CK, CI_FS, and CI_MFS entering a large grey box. Inside the box, the signals pass through three blocks: 'FAS/MFAS insertion', 'FEC encoder', and 'Scrambler'. Between each block, the signals are labeled D, CK, and FS. An output line labeled AI_PLD exits the bottom of the grey box, leading to the final output OTSi_AP. The reference G.798(17)_F16-2 is shown next to the exit point.](7e19e42b9cf476a0c228935fa4d635d5_img.jpg) + +Process diagram for OTSi/OTUk\_A\_So. The input OTUk\_CP is shown at the top with four vertical lines labeled CI\_D, CI\_CK, CI\_FS, and CI\_MFS entering a large grey box. Inside the box, the signals pass through three blocks: 'FAS/MFAS insertion', 'FEC encoder', and 'Scrambler'. Between each block, the signals are labeled D, CK, and FS. An output line labeled AI\_PLD exits the bottom of the grey box, leading to the final output OTSi\_AP. The reference G.798(17)\_F16-2 is shown next to the exit point. + +Figure 16-2 – OTSi/OTUk\_A\_So processes (k = 0, 1, 2, 3, 4) + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 16.1.2 OTSi to OTUk adaptation sink function (OTSi/OTUk\_A\_Sk; k = 0, 1, 2, 3, 4) + +The information flow and processing of the OTSi/OTUk\_A\_Sk function is defined with reference to Figures 16-3 and 16-4. + +#### Symbol + +![Diagram of the OTSi/OTUk_A_Sk function symbol. A central trapezoidal block labeled 'OTSi/OTUk' has two input arrows pointing to its bottom from 'OTSi_AP' and 'OTSiG-O_AP'. It has one output arrow pointing upwards to 'OTUk_CP'. A double-headed horizontal arrow on the left points to the block from 'OTSi/OTUk_A_Sk_MP'. Below the diagram is the text 'G.798(17)-Amd.4(22)_F16-3'.](4b4b9c9c016880edb872f25cefc85eb1_img.jpg) + +Diagram of the OTSi/OTUk\_A\_Sk function symbol. A central trapezoidal block labeled 'OTSi/OTUk' has two input arrows pointing to its bottom from 'OTSi\_AP' and 'OTSiG-O\_AP'. It has one output arrow pointing upwards to 'OTUk\_CP'. A double-headed horizontal arrow on the left points to the block from 'OTSi/OTUk\_A\_Sk\_MP'. Below the diagram is the text 'G.798(17)-Amd.4(22)\_F16-3'. + +**Figure 16-3 – OTSi/OTUk\_A\_Sk function (k = 0, 1, 2, 3, 4)** + +#### Interfaces + +**Table 16-3 – OTSi/OTUk\_A\_Sk inputs and outputs (k = 0, 1, 2, 3, 4)** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OTSi_AP:
OTSi_AI_PLD
OTSiG-O_AP:
OTSiG-O_AI_TSF-P
OTSiG-O_AI_TSF-O
OTSi/OTUk_A_Sk_MP:
OTSi/OTUk_A_Sk_MI_FECEn (Note)
OTSi/OTUk_A_Sk_MI_1second (Note) | OTUk_CP:
OTUk_CI_CK
OTUk_CI_D
OTUk_CI_FS
OTUk_CI_MFS
OTUk_CI_SSF
OTSi/OTUk_A_Sk_MP:
OTSi/OTUk_A_Sk_MI_cLOS-P
OTSi/OTUk_A_Sk_MI_cLOF
OTSi/OTUk_A_Sk_MI_cLOM
OTSi/OTUk_A_Sk_MI_pFECcorrErr (Note) | +| NOTE – For OTSi/OTUk-a_A_Sk and OTSi/OTUk-v_A_Sk only. | | + +#### Processes + +The processes associated with the OTSi/OTUk\_A\_Sk function are as depicted in Figure 16-4. + +**Clock recovery:** The function shall recover the OTUk clock signal from the incoming data. The function shall introduce no errors in case of jitter and wander as defined in clause 6 of [ITU-T G.8251]. + +**Frame alignment:** The function shall recover the OTUk frame start as described in clause 8.2.1. + +**Descrambler:** The function shall perform descrambling as defined in clause 11.2 of [ITU-T G.709]. + +**FEC decoder:** See clause 8.5.2 for the OTSi/OTUk-a\_A\_Sk function, clause 8.5.1 for the OTSi/OTUk-b\_A\_Sk function and clause 8.5.3 for the OTSi/OTUk-v\_A\_Sk function. + +**Multiframe alignment:** The function shall recover the OTUk multiframe start as described in clause 8.2.2. + +![Figure 16-4 – OTSi/OTUk_A_Sk processes (k = 0, 1, 2, 3, 4). This block diagram illustrates the signal processing flow for OTSi/OTUk_A_Sk processes. The diagram is divided into two main sections: OTUk_CP (top) and OTSi_AP (bottom). The signal flow starts from the bottom (OTSi_AP) with inputs AI_PLD, AI_TSF-O, and AI_TSF-P. AI_TSF-O and AI_TSF-P feed into a 'Clock recovery' block, which outputs D, CK, and FS. These signals feed into a 'Frame alignment' block, which outputs D, CK, and FS. The 'Frame alignment' block feeds into 'dLOF detection' (outputting dLOF), 'dAIS detection' (outputting dAIS), and 'LOS detection' (outputting dLOS-P). The 'dLOF detection', 'dAIS detection', and 'LOS detection' blocks feed into 'Defect correlations', which outputs MI_cLOM, MI_cLOF, and MI_cLOS. The 'Frame alignment' block also feeds into a 'Descrambler' block, which outputs D, CK, and FS. The 'Descrambler' block feeds into a 'FEC decoder' block, which outputs D, CK, and FS. The 'FEC decoder' block feeds into 'Multiframe alignment', which outputs CI_D, CI_CK, CI_FS, and CI_MFS. The 'Multiframe alignment' block feeds into 'dLOM detection' (outputting dLOM). The 'dLOM detection' block feeds into 'Consequent actions', which outputs aSSF. The 'Consequent actions' block also receives inputs dLOF, dAIS, dLOS-P, and AI_TSF-P. The 'Consequent actions' block feeds into CI_SSF. The 'Performance monitoring' block receives inputs nFECcorrErr, MI_FECEn, MI_1second, and MI_pFECcorrErr. The 'Performance monitoring' block feeds into 'Defect correlations'.](0b733c1407312c5b063e9bb458ef99db_img.jpg) + +Figure 16-4 – OTSi/OTUk\_A\_Sk processes (k = 0, 1, 2, 3, 4). This block diagram illustrates the signal processing flow for OTSi/OTUk\_A\_Sk processes. The diagram is divided into two main sections: OTUk\_CP (top) and OTSi\_AP (bottom). The signal flow starts from the bottom (OTSi\_AP) with inputs AI\_PLD, AI\_TSF-O, and AI\_TSF-P. AI\_TSF-O and AI\_TSF-P feed into a 'Clock recovery' block, which outputs D, CK, and FS. These signals feed into a 'Frame alignment' block, which outputs D, CK, and FS. The 'Frame alignment' block feeds into 'dLOF detection' (outputting dLOF), 'dAIS detection' (outputting dAIS), and 'LOS detection' (outputting dLOS-P). The 'dLOF detection', 'dAIS detection', and 'LOS detection' blocks feed into 'Defect correlations', which outputs MI\_cLOM, MI\_cLOF, and MI\_cLOS. The 'Frame alignment' block also feeds into a 'Descrambler' block, which outputs D, CK, and FS. The 'Descrambler' block feeds into a 'FEC decoder' block, which outputs D, CK, and FS. The 'FEC decoder' block feeds into 'Multiframe alignment', which outputs CI\_D, CI\_CK, CI\_FS, and CI\_MFS. The 'Multiframe alignment' block feeds into 'dLOM detection' (outputting dLOM). The 'dLOM detection' block feeds into 'Consequent actions', which outputs aSSF. The 'Consequent actions' block also receives inputs dLOF, dAIS, dLOS-P, and AI\_TSF-P. The 'Consequent actions' block feeds into CI\_SSF. The 'Performance monitoring' block receives inputs nFECcorrErr, MI\_FECEn, MI\_1second, and MI\_pFECcorrErr. The 'Performance monitoring' block feeds into 'Defect correlations'. + +**Figure 16-4 – OTSi/OTUk\_A\_Sk processes (k = 0, 1, 2, 3, 4)** + +## Defects + +The function shall detect dLOS-P, dAIS, dLOF and dLOM. + +**dLOS-P:** See clause 6.2.1.2. + +**dAIS:** See clause 6.2.6.3.1 for k = 1, 2, 3; otherwise dAIS shall be assumed false. + +**dLOF:** See clause 6.2.5.1. + +**dLOM:** See clause 6.2.5.2. + +## Consequent actions + +aSSF $\leftarrow$ dLOS-P or dAIS or dLOF or dLOM or AI\_TSF-P + +## Defect correlations + +cLOS-P $\leftarrow$ dLOS-P and (not AI\_TSF-P) + +cLOF $\leftarrow$ dLOF and (not dLOS-P) and (not dAIS) and (not AI\_TSF-P) + +cLOM $\leftarrow$ dLOM and (not dLOS-P) and (not dLOF) and (not dAIS) and (not AI\_TSF-P) + +NOTE 1 – dAIS is not reported as fault cause as it is a secondary alarm and will result in aSSF, which is reported as cSSF fault cause in the OTUk\_TT\_Sk that directly follows this function. + +## Performance monitoring + +The OTSi/OTUk-a\_A\_Sk and OTSi/OTUk-v\_A\_Sk functions shall perform the following performance monitoring primitives processing. The performance monitoring primitives shall be reported to the EMF. + +$$pFECcorrErr \leftarrow \sum nFECcorrErr$$ + +NOTE 2 – During AI\_TSF-P, dAIS, dLOF and dLOM, no corrected bits shall be counted. + +### 16.1.3 OTSi to OTUk-RS adaptation source function (OTSi/OTUk-RS\_A\_So; k = 25u, 25, 50u, 50) + +The information flow and processing of the OTSi/OTUk-RS\_A\_So function is defined with reference to Figures 16-4.1 and 16-4.2. + +#### Symbol + +![Diagram of the OTSi/OTUk-RS_A_So function symbol. It shows an input labeled OTUk_CP entering a trapezoidal block labeled OTSi/OTUk-Rs from the top. An output labeled OTSi_AP exits the block from the bottom. Below the output label is the reference G.798(23)_F16-4.1.](527fb299e6996504538a9cb5ef733d84_img.jpg) + +Diagram of the OTSi/OTUk-RS\_A\_So function symbol. It shows an input labeled OTUk\_CP entering a trapezoidal block labeled OTSi/OTUk-Rs from the top. An output labeled OTSi\_AP exits the block from the bottom. Below the output label is the reference G.798(23)\_F16-4.1. + +Figure 16-4.1 – OTSi/OTUk-RS\_A\_So function (k = 25u, 25, 50u, 50) + +#### Interfaces + +Table 16-3.1 – OTSi/OTUk-RS\_A\_So inputs and outputs (k = 25u, 25, 50u, 50) + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------|--------------------------------| +| OTUk_CP:
OTUk_CI_CK
OTUk_CI_D
OTUk_CI_FS
OTUk_CI_MFS | OTSi_AP:
OTSi_AI_PLD | + +#### Processes + +The processes associated with the OTSi/OTUk-RS\_A\_So function are as depicted in Figure 16-4.2. + +**FAS/MFAS insertion:** The function shall insert the FAS and MFAS into the OTU frame alignment area as described in [ITU-T G.709]. + +**Scrambler:** The function shall scramble the signal as defined in clause 8.4 of [ITU-T G.709.4] for k = 25, 25u and clause 9.4 of [ITU-T G.709.4] for k = 50, 50u. + +**Clock generation:** The function shall generate the OTUk-RS clock by multiplying the incoming OTUk clock (CI\_CK) by [21760/20559] for k = {25, 50u, 50} or by [640/623] for k = 25u to the frequencies as listed in [ITU-T G.709.4] Table B.1 (k = 25u, 50u), Table 8-1 (k = 25) or Table 9-1 (k = 50). + +**FS generator:** The function shall generate OTUk-RS frame starter identifier as described in clause 8.1 (k=25), clause 9.1 (k=50u,50) or clause B.1 (k=25u) of [ITU-T G.709.4]. + +**Mapping:** The function shall map (i.e., addition of alignment/codeword marker overhead area and FEC parity area) the incoming OTUk frame into the OTUk-RS frame payload area as defined in clause 10 of [ITU-T G.709.4]. + +**Alignment insertion:** The function shall insert the alignment/codeword marker into the OTUk-RS frame alignment area as described in clauses 8.3.1 and 9.3.1 of [ITU-T G.709.4]. + +**FEC encoder:** See clause 8.5.6 for k = 25, 50u, 50 and clause 8.5.7 for k = 25u. + +**Symbol Distribution:** For k = 50 the function shall divide the OTU50-RS frame signal into 2 OTL50.2-RS lanes based on 10-bit symbol granularity as described in clause 9.6 of [ITU-T G.709.4]. + +**2:1 bit interleaver:** For k = 50, the process bit multiplexes the two logical lanes of the OTU50-RS signal to a single physical optical OTSi signal according to clause 9.6 of [ITU-T G.709.4]. + +![Figure 16-4.2 – OTSi/OTUk-RS_A_So processes (k = 25u, 25, 50u, 50). The diagram shows two parallel processing paths. The left path is for OTU50_CP, starting with inputs CI_D, CI_CK, CI_FS, and CI_MFAS. It includes blocks for OTU50-RS clock generation (x21760/20559), FAS/MFAS insertion, Scrambler, Mapping, Alignment insertion, FEC encoder, Symbol distribution (outputting 1...2 lanes), and a 2:1 bit interleaver, resulting in OTL50.1-RS and OTSi_AP outputs. The right path is for OTU25_CP, starting with the same inputs. It includes blocks for OTU25-RS clock generation (x21760/20559 for k=25, x640/623 for k=25u), FAS/MFAS insertion, Scrambler, Mapping, Alignment insertion, and FEC encoder, resulting in OTSi_AP output. Both paths include an FS_RS generator block that provides clock and frame signal inputs to the Mapping and Alignment insertion blocks.](f6dcf82b673244b5b8c95616ca0d0556_img.jpg) + +Figure 16-4.2 – OTSi/OTUk-RS\_A\_So processes (k = 25u, 25, 50u, 50). The diagram shows two parallel processing paths. The left path is for OTU50\_CP, starting with inputs CI\_D, CI\_CK, CI\_FS, and CI\_MFAS. It includes blocks for OTU50-RS clock generation (x21760/20559), FAS/MFAS insertion, Scrambler, Mapping, Alignment insertion, FEC encoder, Symbol distribution (outputting 1...2 lanes), and a 2:1 bit interleaver, resulting in OTL50.1-RS and OTSi\_AP outputs. The right path is for OTU25\_CP, starting with the same inputs. It includes blocks for OTU25-RS clock generation (x21760/20559 for k=25, x640/623 for k=25u), FAS/MFAS insertion, Scrambler, Mapping, Alignment insertion, and FEC encoder, resulting in OTSi\_AP output. Both paths include an FS\_RS generator block that provides clock and frame signal inputs to the Mapping and Alignment insertion blocks. + +G.798(17)-Amd.4(22)\_F16-4.2 + +**Figure 16-4.2 – OTSi/OTUk-RS\_A\_So processes (k = 25u, 25, 50u, 50)** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 16.1.4 OTSi to OTUk-RS adaptation sink function (OTSi/OTUk-RS\_A\_Sk; k = 25u, 25, 50u, 50) + +The information flow and processing of the OTSi/OTUk-RS\_A\_Sk function is defined with reference to Figures 16-4.3 and 16-4.4. + +#### Symbol + +![Figure 16-4.3: Symbol diagram for the OTSi/OTUk-RS_A_Sk function. A central trapezoidal block labeled 'OTSi/OTUk-RS' has two input arrows from below labeled 'OTSi_AP' and 'OTSiG-O_AP'. It has one output arrow pointing upwards labeled 'OTUk_CP'. A double-headed horizontal arrow to the left of the block is labeled 'OTSi/OTUk-RS_A_Sk_MP'. Below the diagram is the text 'G.798(17)-Amd.4(22)_F16-4.3'.](45b71f54324c8fd8c2830610b367dced_img.jpg) + +Figure 16-4.3: Symbol diagram for the OTSi/OTUk-RS\_A\_Sk function. A central trapezoidal block labeled 'OTSi/OTUk-RS' has two input arrows from below labeled 'OTSi\_AP' and 'OTSiG-O\_AP'. It has one output arrow pointing upwards labeled 'OTUk\_CP'. A double-headed horizontal arrow to the left of the block is labeled 'OTSi/OTUk-RS\_A\_Sk\_MP'. Below the diagram is the text 'G.798(17)-Amd.4(22)\_F16-4.3'. + +Figure 16-4.3 – OTSi/OTUk-RS\_A\_Sk function (k = 25u, 25, 50u, 50) + +#### Interfaces + +Table 16-3.2 – OTSi/OTUk-RS\_A\_Sk inputs and outputs (k = 25u, 25, 50u, 50) + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OTSi_AP:
OTSi_AI_PLD
OTSiG-O_AP:
OTSiG-O_AI_TSF-P
OTSiG-O_AI_TSF-O
OTSi/OTUk-RS_A_Sk_MP:
OTSi/OTUk-RS_A_Sk_MI_FECEn
OTSi/OTUk-RS_A_Sk_MI_1second | OTUk_CP:
OTUk_CI_CK
OTUk_CI_D
OTUk_CI_FS
OTUk_CI_MFS
OTUk_CI_SSF
OTSi/OTUk-RS_A_Sk_MP:
OTSi/OTUk-RS_A_Sk_MI_cLOS-P
OTSi/OTUk-RS_A_Sk_MI_cLOL
OTSi/OTUk-RS_A_Sk_MI_cLOF
OTSi/OTUk-RS_A_Sk_MI_cLOM
OTSi/OTUk-RS_A_Sk_MI_pFECcorrErr | + +#### Processes + +The processes associated with the OTSi/OTUk-RS\_A\_Sk function are as depicted in Figure 16-4.4. + +**Clock recovery:** The function shall recover the OTUk clock signal from the incoming data. The function shall introduce no errors in case of jitter and wander as defined in clause 6 of [ITU-T G.8251]. + +**1:2 bit dis-interleaver:** For k=50 the process shall bit de-multiplex the bitstream of the OTL50.1-RS physical lane into two logical lanes as defined in clause 9.6 of [ITU-T G.709.4]. + +**Alignment lock:** The function shall recover the start of OTUk-RS frame through obtaining LOCK to the alignment/codeword markers as specified by the FEC synchronization state diagram in clause 108.5.3.1 of [IEEE 802.3] for k = 25u, 25, or clause 134.5.3.1 of [IEEE 802.3] for k = 50u, 50. Additionally, the synchronization process on all logical lanes shall be restarted (restart\_lock set to true) if five consecutive alignment markers fail to match on any of the logical lanes. + +**Deskew & Reorder:** For k = 50 the function shall include deskewing and reordering processes. The deskewing process shall remove the skew of the two OTL50.2-RS lanes as specified by the FEC alignment state diagram in clause 134.5.3.1 of [IEEE 802.3]. It shall support a maximum skew of 180 + +ns between FEC lanes and a maximum skew variation of 4 ns. The reordering process shall reorder these two OTL50.2-RS lanes according to its lane number (see clause 9.6 of [ITU-T G.709.4]). + +**FEC decoder:** See clause 8.5.6 for k = 25, 50u, 50 and clause 8.5.7 for k = 25u. + +**Demapping:** The function shall demap (i.e., removal of alignment/codeword marker overhead area and FEC parity area) the OTUk frame from the OTUk-RS frame payload area as defined in clause 10 of [ITU-T G.709.4]. + +**Frame alignment:** The function shall recover the OTUk frame start as described in clause 8.2.9. + +**Descrambler:** The function shall perform descrambling as defined in clause 8.4 of [ITU-T G.709.4] for k = 25, 25u and clause 9.4 of [ITU-T G.709.4] for k = 50, 50u. + +**Multiframe alignment:** The function shall recover the OTUk multi-frame start as described in clause 8.2.2. + +![Block diagram of OTSi/OTU25(u)-R_A_Sk processes showing signal flow from OTSi_AP to OTU25_CP through various processing stages including Clock recovery, Alignment lock, FEC decoder, Demapping, Frame alignment, Descrambler, and Multi-frame alignment. It also includes detection blocks for dLOM, dLOF, dLOS-P, and a Defect correlation block.](fffcd82cf1347760ecef4f2db3059360_img.jpg) + +The diagram illustrates the OTSi/OTU25(u)-R\_A\_Sk processing pipeline. The signal flow is as follows: + +- Inputs:** OTSi\_AP (AI\_PLD, AI\_TSF-O, AI\_TSF-P) enter the bottom of the diagram. +- Clock recovery:** Receives AI\_TSF-O and AI\_TSF-P. It outputs D, CK, and FS signals upwards. It also connects to a **LOS detection** block which outputs **dLOS-P**. +- Alignment lock:** Receives D, CK, and FS. It outputs **dLOL** to the right. +- FEC decoder:** Receives D, CK, and FS. It outputs **nFECcorrErr** to the **Performance monitoring** block. +- Demapping:** Receives D, CK, and FS. +- Frame alignment:** Receives D, CK, and FS. It connects to a **dLOF detection** block which outputs **dLOF**. +- Descrambler:** Receives D, CK, FS, and MFS (from frame alignment). It outputs D, CK, FS, and MFS upwards. +- Multi-frame alignment:** Receives D, CK, FS, and MFS. It connects to a **dLOM detection** block which outputs **dLOM**. +- Outputs:** The final output is **OTU25\_CP**, which includes signals **CI\_D, CI\_CK, CI\_FS, and CI\_MFS**. +- Monitoring and Defect Correlation:** + - Performance monitoring:** Receives **nFECcorrErr** from the FEC decoder. It outputs **MI\_1second** and **MI\_pFECcorrErr** to the right. + - Defect correlation:** Receives **dLOM, dLOF, dLOL, dLOS-P, and AI\_TSF-P**. It outputs **MI\_cLOM, MI\_cLOF, MI\_cLOL, and MI\_cLOS-P** to the right. + - Consequent actions:** Receives **dLOM, dLOF, dLOS-P, and AI\_TSF-P**. It outputs **aSSF** to the **CI\_SSF** output line. +- Vertical Label:** OTSi/OTU25-RS\_A\_Sk\_MP is located on the far right side of the diagram. +- Diagram Code:** G.798(23)\_F16-4.4 is located at the bottom right of the diagram area. + +Block diagram of OTSi/OTU25(u)-R\_A\_Sk processes showing signal flow from OTSi\_AP to OTU25\_CP through various processing stages including Clock recovery, Alignment lock, FEC decoder, Demapping, Frame alignment, Descrambler, and Multi-frame alignment. It also includes detection blocks for dLOM, dLOF, dLOS-P, and a Defect correlation block. + +Figure 16-4.4 – OTSi/OTU25(u)-R\_A\_Sk processes + +![Block diagram of OTSi/OTU50(u)-RS_A_Sk processes showing signal flow from OTU50_CP to OTSi_AP through various processing stages including clock recovery, alignment, deskew, and FEC decoding. It also shows defect detection and monitoring blocks.](f4b7c84516339d37b6c63b18287d1493_img.jpg) + +The diagram illustrates the OTSi/OTU50(u)-RS\_A\_Sk processes. The signal flow is as follows: + +- OTU50\_CP** (top) provides signals **CI\_D**, **CI\_CK**, **CI\_FS**, and **CI\_MFS** to a **Multi-frame alignment** block. +- The **Multi-frame alignment** block outputs **dLOM** to a **dLOM detection** block and **aSSF** to **CI\_SSF** (top right). +- The **dLOM detection** block outputs **dLOM** to **Consequent actions**. +- The **Multi-frame alignment** block also outputs **D**, **CK**, **FS**, and **MFS** to a **Descrambler** block. +- The **Descrambler** block outputs **D**, **CK**, **FS**, and **MFS** to a **Frame alignment** block. +- The **Frame alignment** block outputs **dLOF** to a **dLOF detection** block. +- The **dLOF detection** block outputs **dLOF** to **Consequent actions**. +- The **Frame alignment** block also outputs **D**, **CK**, and **FS** to a **Demapping** block. +- The **Demapping** block outputs **D**, **CK**, and **FS** to a **FEC decoder** block. +- The **FEC decoder** block outputs **nFECcorrErr** to **Performance monitoring**. +- Performance monitoring** outputs **MI\_1second** and **MI\_pFECcorrErr** to **OTSIG/OTU50-RS\_A\_Sk\_MP** (right). +- The **FEC decoder** block also outputs **D**, **CK**, and **FS** to a **Lane reorder** block. +- The **Lane reorder** block outputs **D**, **CK**, and **FS** to a **Deskew** block. +- The **Deskew** block outputs **dLOL** to **Defect correlation**. +- Defect correlation** outputs **MI\_cLOM**, **MI\_cLOF**, **MI\_cLOL**, and **MI\_cLOS-P** to **OTSIG/OTU50-RS\_A\_Sk\_MP**. +- The **Deskew** block also outputs **D**, **CK**, and **FS** to two **Alignment lock** blocks (Lane #1 and Lane #2). +- The **Alignment lock** blocks output **restart\_lock[1]** and **restart\_lock[2]** to a **Lane marker process** block. +- The **Lane marker process** block outputs **restart** to the **Alignment lock** blocks. +- The **Alignment lock** blocks output **D[1]**, **CK[1]**, and **FS[1]** to a **1:2 bit dis-interleaver** block (Lane #1). +- The **1:2 bit dis-interleaver** block outputs **D[2]**, **CK[2]**, and **FS[2]** to the **Alignment lock** block (Lane #2). +- The **1:2 bit dis-interleaver** block also outputs **D** and **CK** to a **Clock recovery** block. +- The **Clock recovery** block outputs **dLOS-P** to **LOS detection**. +- The **LOS detection** block outputs **dLOS-P** to **Consequent actions**. +- The **Physical lane** (bottom left) contains the **Clock recovery** and **LOS detection** blocks. +- The **Physical lane** outputs **OTL50.1-RS** to **OTSIG/OTU50-RS\_A\_Sk\_MP**. +- OTSIG/OTU50-RS\_A\_Sk\_MP** outputs **AI\_PLD**, **AI\_TSF-O**, and **AI\_TSF-P** to **OTSi\_AP** (bottom). + +Labels on the right side of the diagram include: **OTSIG/OTU50-RS\_A\_Sk\_MP**, **Consequent actions**, **Performance monitoring**, and **Defect correlation**. + +Labels on the left side of the diagram include: **OTU50\_CP**, **CI\_D**, **CI\_CK**, **CI\_FS**, **CI\_MFS**, **CI\_SSF**, **Multi-frame alignment**, **dLOM detection**, **dLOM**, **aSSF**, **Descrambler**, **Frame alignment**, **dLOF detection**, **dLOF**, **Demapping**, **FEC decoder**, **nFECcorrErr**, **MI\_1second**, **MI\_pFECcorrErr**, **Lane reorder**, **Deskew**, **dLOL**, **Defect correlation**, **MI\_cLOM**, **MI\_cLOF**, **MI\_cLOL**, **MI\_cLOS-P**, **Alignment lock**, **restart\_lock[1]**, **restart\_lock[2]**, **Lane #1**, **Lane #2**, **D[1]**, **CK[1]**, **FS[1]**, **D[2]**, **CK[2]**, **FS[2]**, **1:2 bit dis-interleaver**, **Clock recovery**, **LOS detection**, **dLOS-P**, **Physical lane**, **OTSIG/OTU50-RS\_A\_Sk\_MP**, **OTL50.1-RS**, **AI\_PLD**, **AI\_TSF-O**, **AI\_TSF-P**, **OTSi\_AP**, **Lane marker process**, and **restart**. + +Block diagram of OTSi/OTU50(u)-RS\_A\_Sk processes showing signal flow from OTU50\_CP to OTSi\_AP through various processing stages including clock recovery, alignment, deskew, and FEC decoding. It also shows defect detection and monitoring blocks. + +G.798(23)\_F16-4.5 + +Figure 16-4.5 – OTSi/OTU50(u)-RS\_A\_Sk processes + +**Defects** + +The function shall detect dLOS-P, dLOL, dLOF and dLOM. + +**dLOS-P:** See clause 6.2.1.2. + +**dLOL:** For $k = 50u$ , 50 dLOL is generated based on the multilane FEC alignment lock process specified in clause 134.5.3.1 of [IEEE 802.3]. For $k = 25u$ , 25 dLOL is generated based on the codeword marker alignment lock and monitor processes specified in clauses 108.5.3.1 and 108.5.3.3 of [IEEE 802.3]. dLOL shall be declared if *fec\_alignment\_valid* is false for 3 ms. To provide for the case of intermittent out-of-locks (*fec\_alignment\_valid* is false), the integrating timer shall not be reset to zero until an in-lock (*fec\_alignment\_valid* is true) condition persists continuously for 3 ms. dLOL shall be cleared if *fec\_alignment\_valid* is true for 3 ms. + +**dLOF:** See clause 6.2.5.1. + +**dLOM:** See clause 6.2.5.2. + +#### Consequent actions + +aSSF $\leftarrow$ dLOS-P or dLOL or dLOF or dLOM or AI\_TSF-P + +#### Defect correlations + +cLOS-P $\leftarrow$ dLOS-P and (not AI\_TSF-P) + +cLOL $\leftarrow$ dLOL and (not dLOS-P) and (not AI\_TSF-P) + +cLOF $\leftarrow$ dLOF and (not dLOL) and (not dLOS-P) and (not AI\_TSF-P) + +cLOM $\leftarrow$ dLOM and (not dLOF) and (not dLOL) and (not dLOS-P) and (not AI\_TSF-P) + +#### Performance monitoring + +The function shall perform the following performance monitoring primitives processing. The performance monitoring primitives shall be reported to the EMF. + +pFECcorrErr $\leftarrow \sum nFECcorrErr$ + +NOTE – During AI\_TSF-P, dLOL, no corrected bits shall be counted. + +### 16.2 OTSi to OTUkV adaptation function (OTSi/OTUkV\_A) + +The OTSi to OTUkV adaptation functions perform the adaptation between the OTSi layer adapted information and the characteristic information of functionally standardized OTUkV layer signal. + +#### 16.2.1 OTSi to OTUkV adaptation source function (OTSi/OTUkV\_A\_So) + +The information flow and processing of the OTSi/OTUkV\_A\_So function is defined with reference to Figure 16-5. + +#### Symbol + +![Diagram of the OTSi/OTUkV_A_So function symbol. It shows a vertical flow: OTUkV_CP at the top, an arrow pointing down to a trapezoidal symbol labeled OTSi/OTUkV, and an arrow pointing down from that symbol to OTSi_AP at the bottom. The text G.798(17)_F16-5 is located to the right of the bottom arrow.](2977acb9333aa9e25450fff36691806b_img.jpg) + +``` +graph TD; A[OTUkV_CP] --> B{{OTSi/OTUkV}}; B --> C[OTSi_AP]; +``` + +G.798(17)\_F16-5 + +Diagram of the OTSi/OTUkV\_A\_So function symbol. It shows a vertical flow: OTUkV\_CP at the top, an arrow pointing down to a trapezoidal symbol labeled OTSi/OTUkV, and an arrow pointing down from that symbol to OTSi\_AP at the bottom. The text G.798(17)\_F16-5 is located to the right of the bottom arrow. + +**Figure 16-5 – OTSi/OTUkV\_A\_So function** + +## Interfaces + +**Table 16-4 – OTSi/OTUkV\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------|--------------------------------| +| OTUkV_CP:
OTUkV_CI_CK
OTUkV_CI_D
OTUkV_CI_FS
OTUkV_VI_MFS (Note) | OTSi_AP:
OTSi_AI_PLD | +| NOTE – If OTUkV has a multiframe. | | + +## Processes + +The OTSi/OTUkV\_A\_So function provides all processes necessary for the adaptation to the OTSi layer, which includes processes that ensure clock and frame recovery at the adaptation sink and optional forward error correction coding. + +The specific processes are outside the scope of this Recommendation. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 16.2.2 OTSi to OTUkV adaptation sink function (OTSi/OTUkV\_A\_Sk) + +The information flow and processing of the OTSi/OTUkV\_A\_Sk function is defined with reference to Figure 16-6. + +#### Symbol + +![Diagram of the OTSi/OTUkV_A_Sk function symbol. A central trapezoidal block labeled 'OTSi/OTUkV' has three connections: a horizontal double-headed arrow on the left labeled 'OTSi/OTUkV_A_Sk_MP', an upward-pointing arrow on top labeled 'OTUkV_CP', and two downward-pointing arrows on the bottom labeled 'OTSi_AP' and 'OTSiG-O_AP'. Below the block is the reference text 'G.798(17)-Amd.4(22)_F16-6'.](ea3fc2de81f3b1ff5c2f12cdeadcf831_img.jpg) + +Diagram of the OTSi/OTUkV\_A\_Sk function symbol. A central trapezoidal block labeled 'OTSi/OTUkV' has three connections: a horizontal double-headed arrow on the left labeled 'OTSi/OTUkV\_A\_Sk\_MP', an upward-pointing arrow on top labeled 'OTUkV\_CP', and two downward-pointing arrows on the bottom labeled 'OTSi\_AP' and 'OTSiG-O\_AP'. Below the block is the reference text 'G.798(17)-Amd.4(22)\_F16-6'. + +**Figure 16-6 – OTSi/OTUkV\_A\_Sk function** + +## Interfaces + +**Table 16-5 – OTSi/OTUkV\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| For each OTSi_AP:
OTSi_AI_PLD
OTSiG-O_AP:
OTSiG-O_AI_TSF-P
OTSiG-O_AI_TSF-O
OTSi/OTUkV_A_Sk_MP:
OTSi/OTUkV_A_Sk_MI_1second (Note 2) | OTUkV_CP:
OTUkV_CI_CK
OTUkV_CI_D
OTUkV_CI_FS
OTUkV_CI_MFS (Note 1)
OTUkV_CI_SSF
OTSi/OTUkV_A_Sk_MP:
OTSi/OTUkV_A_Sk_MI_cLOS-P
OTSi/OTUkV_A_Sk_MI_cLOF
OTSi/OTUkV_A_Sk_MI_cLOM (Note 1)
OTSi/OTUkV_A_Sk_MI_pFECcorrErr (Note 2) | +| NOTE 1 – If OTUkV has a multiframe.
NOTE 2 – If the function performs FEC. | | + +## Processes + +The OTSi/OTUkV\_A\_Sk function provides all processes necessary for the adaptation from the OTSi layer, which includes processes for clock and frame start recovery and optional forward error correction decoding. + +The specific processes are outside the scope of this Recommendation. + +## Defects + +The function shall detect dAIS and dLOF. If the OTUkV includes a multiframe, it shall in addition detect dLOM. + +**dLOS-P:** See clause 6.2.1.2. + +**dAIS:** See clause 6.2.6.3.1. + +**dLOF:** The dLOF detection depends on the specific frame structure and is outside the scope of this Recommendation. + +**dLOM:** The dLOM detection is only required if the OTUkV has a multiframe, the detection depends on the specific multiframe structure and is outside the scope of this Recommendation. + +## Consequent actions: + +aSSF ← dLOS-P or dAIS or dLOF or AI\_TSF-P or dLOM + +NOTE 1 – dLOM is only included if the OTUkV has a multiframe. + +## Defect correlations + +cLOS-P ← dLOS-P and (not AI\_TSF-P) + +cLOF ← dLOF and (not dLOS-P) and (not dAIS) and (not AI\_TSF-P) + +cLOM ← dLOM and (not dLOS-P) and (not dLOF) and (not dAIS) and (not AI\_TSF-P) + +NOTE 2 – cLOM is only defined if the OTUkV has a multiframe. + +NOTE 3 – dAIS is not reported as fault cause as it is a secondary alarm and will result in aSSF, which is reported as cSSF fault cause in the ODU\_TT\_Sk that directly follows this function. + +## Performance monitoring + +The function shall perform the following performance monitoring primitives processing if it includes FEC processing. The performance monitoring primitives shall be reported to the EMF. + +$$pFECcorrErr \leftarrow \sum nFECcorrErr$$ + +NOTE 4 – During AI\_TSF-P, dAIS, dLOF and dLOM no corrected bits shall be counted. + +### 16.3 OTSiG to OTUk adaptation function (OTSiG/OTUk\_A) + +The OTSiG to OTUk adaptation functions perform the adaptation between the OTSiG layer adapted information and the characteristic information of the completely standardized OTUk layer signal. Three types of functions are defined: one that supports G.709 forward error correction (FEC), one that does not support FEC, and one that does support SC FEC. The functions without FEC are only defined for OTU3. + +**Table 16-6 – OTSiG to OTUk adaptation functions** + +| Function type | Function name | OTUk | +|----------------|--------------------------------------------------|----------| +| OTSiG/OTUk-a_A | OTSiG to OTUk adaptation function with G.709 FEC | k = 3, 4 | +| OTSiG/OTUk-b_A | OTSiG to OTUk adaptation function without FEC | k = 3 | +| OTSi/OTU4-SC_A | OTSi to OTU4 adaptation function with SC FEC | k = 4 | + +NOTE – OTSiG/OTUk\_A is used throughout this clause as shorthand for the specific function type. + +#### 16.3.1 OTSiG to OTUk adaptation source function (OTSiG/OTUk\_A\_So) + +The information flow and processing of the OTSiG/OTUk\_A\_So function is defined with reference to Figures 16-7 and 16-8. + +##### Symbol + +![Diagram of the OTSiG/OTUk_A_So function symbol. An input labeled OTUk_CP enters a trapezoidal block labeled OTSiG/OTUk from the top. From the bottom of the block, multiple output lines emerge, labeled 1, ..., m, leading to OTSi_AP[1] and OTSi_AP[m]. Below the diagram is the text G.798(17)-Amd.4(22)_F16-7.](96be3e8be94c247917bab0d91881b5dc_img.jpg) + +Diagram of the OTSiG/OTUk\_A\_So function symbol. An input labeled OTUk\_CP enters a trapezoidal block labeled OTSiG/OTUk from the top. From the bottom of the block, multiple output lines emerge, labeled 1, ..., m, leading to OTSi\_AP[1] and OTSi\_AP[m]. Below the diagram is the text G.798(17)-Amd.4(22)\_F16-7. + +**Figure 16-7 – OTSiG/OTUk\_A\_So function** + +##### Interfaces + +**Table 16-7 – OTSiG/OTUk\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------|------------------------------------| +| OTUk_CP:
OTUk_CI_CK
OTUk_CI_D
OTUk_CI_FS
OTUk_CI_MFS | per OTSi_AP:
OTSi_AI_PLD | + +## Processes + +The processes associated with the OTSiG/OTUk\_A\_So function are as depicted in Figure 16-8. + +The processes associated with the OTSiG/OTUk\_A\_So function are specific processes for each OTSi lane signal of the OTSiG, and common processes for the compound signal as depicted in Figure 16-8. + +### Common processes + +**FAS/MFAS insertion:** The function shall insert the FAS and MFAS into the OTUk OH area as described in [ITU-T G.709]. + +**FEC encoder:** See clause 8.5.2 for the OTSiG/OTUk-a\_A\_So function, clause 8.5.1 for the OTSiG/OTU3-b\_A\_So function and clause 8.5.4 for the OTSiG/OTU4-SC\_A\_So. + +**Scrambler:** The function shall scramble the signal as defined in clause 11.2 of [ITU-T G.709]. + +**LLM insertion:** The function shall insert the logical lane marker (LLM) as defined in Annex C of [ITU-T G.709] for OTU4. The LLM replaces the 3rd OA2 byte position of the OTU4 FAS signal. In the case that no OTU4 frame is present (no FS indication), no LLM shall be inserted. + +NOTE 2 – No LLM insertion for OTU3 is required as this function is performed by the MFAS LSB positions of the OTU3 frame. + +**16-byte block distributor and rotator:** The function shall distribute each 16-byte block of the OTU3/OTU4 signal in round-robin way to the related lane structure ( $y = 20$ logical lanes for OTU4 and $y = 4$ lanes for OTU3), as defined in Annex C of [ITU-T G.709]. The distribution is aligned to the OTUk frame and for OTU3 to the LSB positions of the multiframe. After every 16320th byte the mapping to the lanes shall be rotated forward by one lane, so that the OTUk FAS position will be located in the next lane as specified in Annex C of [ITU-T G.709] (see Figures C.2 and C.3 of [ITU-T G.709]). + +### Lane specific processes + +**5:1 bit interleaver:** The process bit multiplexes groups of five logical lanes of the 20 logical lanes of the OTU4 signal to four physical optical OTSi signals according to Annex C of [ITU-T G.709]. + +![Figure 16-8: OTSiG/OTUk_A_So processes. The diagram shows two flowcharts for k=3 (left) and k=4 (right). Both start with OTUk_CP inputs (CI_D, CI_CK, CI_FS, CI_MFS) entering a 'FAS/MFAS insertion' block. The output (D, CK, FS, MFS) goes to an 'FEC encoder', then a 'Scrambler', and finally a '16-byte block distributor and rotator'. The outputs (1 to 4) are labeled AI_PLD and OTSi_AP[1] to OTSi_AP[4]. The k=4 diagram adds an 'LLM insertion' block between the scrambler and the distributor, and splits the distributor outputs into two '5.1 bit interleaver' blocks before reaching the AI_PLD and OTSi_AP outputs. A reference code G.798(17)_F16-8 is present.](385c524299e3256900f891bc068d62b6_img.jpg) + +Figure 16-8: OTSiG/OTUk\_A\_So processes. The diagram shows two flowcharts for k=3 (left) and k=4 (right). Both start with OTUk\_CP inputs (CI\_D, CI\_CK, CI\_FS, CI\_MFS) entering a 'FAS/MFAS insertion' block. The output (D, CK, FS, MFS) goes to an 'FEC encoder', then a 'Scrambler', and finally a '16-byte block distributor and rotator'. The outputs (1 to 4) are labeled AI\_PLD and OTSi\_AP[1] to OTSi\_AP[4]. The k=4 diagram adds an 'LLM insertion' block between the scrambler and the distributor, and splits the distributor outputs into two '5.1 bit interleaver' blocks before reaching the AI\_PLD and OTSi\_AP outputs. A reference code G.798(17)\_F16-8 is present. + +Figure 16-8 – OTSiG/OTUk\_A\_So processes (left: k=3, right: k=4) + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 16.3.2 OTSiG to OTUk adaptation sink function (OTSiG/OTUk\_A\_Sk) + +The information flow and processing of the OTSiG/OTUk\_A\_Sk function is defined with reference to Figures 16-9 and 16-10. + +## Symbol + +![Diagram of the OTSiG/OTUk_A_Sk function symbol. A central trapezoidal block is labeled 'OTSiG/OTUk'. Above it, an arrow points up to 'OTUk_CP'. To the left, an arrow points left to 'OTSiG/OTUk_A_Sk_MP'. Below the block, three arrows point up from 'OTSi_AP[1]', 'OTSi_AP[m]', and 'OTSiG-O_AP'. A dashed oval with arrows labeled 'l' and 'm' is positioned between the input arrows and the block. A reference label 'G.798(17)-Amd.4(22)_F16-9' is at the bottom right.](189062b6daff39a4a33fb150b0aca878_img.jpg) + +Diagram of the OTSiG/OTUk\_A\_Sk function symbol. A central trapezoidal block is labeled 'OTSiG/OTUk'. Above it, an arrow points up to 'OTUk\_CP'. To the left, an arrow points left to 'OTSiG/OTUk\_A\_Sk\_MP'. Below the block, three arrows point up from 'OTSi\_AP[1]', 'OTSi\_AP[m]', and 'OTSiG-O\_AP'. A dashed oval with arrows labeled 'l' and 'm' is positioned between the input arrows and the block. A reference label 'G.798(17)-Amd.4(22)\_F16-9' is at the bottom right. + +Figure 16-9 – OTSiG/OTUk\_A\_Sk function + +## Interfaces + +Table 16-8 – OTSiG/OTUk\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| per OTSi_AP:
OTSi_AI_PLD
OTSiG-O_AP:
OTSiG-O_AI_TSF-P
OTSiG-O_AI_TSF-O
OTSiG/OTUk_A_Sk_MP:
OTSiG/OTUk_A_Sk_MI_FECEn (Note)
OTSiG/OTUk_A_Sk_MI_1second | OTUk_CP:
OTUk_CI_CK
OTUk_CI_D
OTUk_CI_FS
OTUk_CI_MFS
OTUk_CI_SSF
OTSiG/OTUk_A_Sk_MP:
OTSiG/OTUk_A_Sk_MI_cLOS-P
OTSiG/OTUk_A_Sk_MI_cLOL
OTSiG/OTUk_A_Sk_MI_cLOF
OTSiG/OTUk_A_Sk_MI_cLOM
OTSiG/OTUk_A_Sk_MI_pFECcorrErr | +| NOTE – This input does not exist for OTU4. | | + +## Processes + +The processes associated with the OTSiG/OTUk\_A\_Sk function are as depicted in Figures 16-10 and 16-11. + +### Frame alignment: + +- For OTSiG/OTUk-a\_A\_Sk and OTSiG/OTUk-b\_A\_Sk, this optional process shall recover the OTUk frame start as described in clause 8.2.1. +- For OTSiG/OTU4-SC\_A\_Sk, this optional process shall recover the OTU4 frame start. The detailed processing is for further study. + +### Pre-FEC Multiframe alignment: + +- For OTSiG/OTUk-a\_A\_Sk and OTSiG/OTUk-b\_A\_Sk, the process shall transparently pass the scrambled data at its input to the output. +- For OTSiG/OTU4-SC\_A\_Sk, the process shall recover the pre-FEC multiframe start. The detailed processing is for further study. + +**Descrambler:** The process shall perform descrambling as defined in clause 11.2 of [ITU-T G.709]. + +**FEC decoder:** See clause 8.5.2 for the OTSiG/OTUk-a\_A\_Sk function, clause 8.5.1 for the OTSiG/OTU3-b\_A\_Sk function and clause 8.5.4 for the OTSiG/OTU4-SC\_A\_Sk. + +**Multiframe alignment:** The function shall recover the OTUk multiframe start as described in clause 8.2.2. + +### Specific processes + +**Clock recovery:** The process shall recover the clock of the OTL physical lane signals from the incoming data. The function shall introduce no errors in case of jitter and wander, as defined in [ITU-T G.8251]. + +**1/5 Bit dis-interleaver (OTU4):** The process shall bit de-multiplex the bitstream of the OTL physical lane into five logical lanes as defined in Annex C of [ITU-T G.709]. + +#### Lane frame alignment: + +- For OTSiG/OTUk-a\_A\_Sk and OTSiG/OTUk-b\_A\_Sk, the process shall recover the logical lane frame start, as described in clause 8.2.5. +- For OTSiG/OTU4-SC\_A\_Sk, the process shall recover the logical lane frame start. The detailed processing is for further study. + +**Lane alignment recovery:** The process shall recover the lane alignment signal of the logical lane, as described in clause 8.2.6. + +**LLM removal (OTU4):** The process shall remove the LLM and re-establish the OTU4-FAS OA2 byte pattern in the 6th byte position of the individual logical lane stream. + +**Lane deskew:** The lane deskew consists of 4 or 20 elastic store processes, and the lane marker and delay process. The process shall establish the delay compensation, compensating the differential delay between the logical lane signals as given in Annex C of [ITU-T G.709] for OTU3 and OTU4. The compensation between the data lanes is achieved by an elastic store per lane, writing the lane data under the control of the marker processing at the correct time into the 16-byte data block multiplexer. Each elastic store shall be capable of compensating at least 180 ns of absolute differential delay between the lanes in line with [IEEE 802.3]. + +NOTE – [IEEE 802.3] considers the differential delay to be split into a static and variable part where the variable part of the differential delay may be up to 4 ns of variation. + +**OTU clock generator:** The process shall generate the OTUk clock from the incoming lane clock. + +**16-byte block mux:** The process shall interleave the 4 or 20 logical lane signals in 16-byte increments to restore the original OTUk, as given in Annex C of [ITU-T G.709], Figures C.2 and C.3. The OTUk frame start shall be recovered from the 4 or 20 lane frame start signals. + +![Block diagram of OTSiG/OTUk_A_Sk processes (k = 3). The diagram shows the signal flow from 4 physical lanes at the bottom to a single OTU3_CP output at the top. Each physical lane contains a Clock recovery and LOS detection block. These connect to 4 logical lanes, each containing a Lane frame alignment, Lane alignment recovery, and Elastic store (with RD and WR pointers). A central Lane marker and delay processing block connects the logical lanes and provides a dLOL signal. The signals then pass through a 16-byte block Mux (with Lane rotation and muxing control). Above the mux is an Optional section with Frame alignment and dLOF detection, followed by a Descrambler, FEC decoder, and Multiframe alignment block. This block outputs CI_D, CI_CK, CI_FS, and CI_MFS signals. Various detection signals (dLOM, dLOF, dLOL, dLOFLANE[1..4], dLOS-P[1..4]) are fed into Consequent actions (producing aSSF) and Defect correlation (producing MI_cLOM, MI_cLOF, MI_cLOL, MI_cLOS) blocks. Performance monitoring blocks receive nFECcorrErr and MI_FECEn signals and output MI_1second and MI_pFECcorrErr. The entire process is labeled OTSiG/OTU3_A_Sk_MP on the right. Inputs at the bottom are OTSi_AP[1] and OTSi_AP[4].](ffd430265e73d833a0aa30a5dd8261e3_img.jpg) + +The diagram illustrates the OTSiG/OTUk\_A\_Sk processes for k=3. It shows the aggregation of 4 physical lanes into a single OTU3\_CP output. + +- Physical Lanes (Bottom):** Four physical lanes (Lane #1 to Lane #4) are shown. Each lane contains a **Clock recovery** and **LOS detection** block. The inputs are OTSi\_AP[1] and OTSi\_AP[4]. The outputs are dLOS[1] and dLOS[4]. +- Logical Lanes:** Each physical lane connects to a logical lane. Each logical lane contains a **Lane frame alignment**, **Lane alignment recovery**, and an **Elastic store** (with RD and WR pointers). The outputs are dLOFLANE[1] and dLOFLANE[4]. +- Central Processing:** A **Lane marker and delay processing** block connects all logical lanes and provides a dLOL signal. A **16-byte block Mux** (with **Lane rotation and muxing control**) aggregates the signals from the logical lanes. +- Optional Section:** Above the mux is an **Optional** section containing **Frame alignment** and **dLOF detection**, which outputs a dLOF signal. +- Descrambler and FEC:** The signal then passes through a **Descrambler**, **FEC decoder**, and **Multiframe alignment** block. The **Multiframe alignment** block outputs CI\_D, CI\_CK, CI\_FS, and CI\_MFS signals. +- Defect Detection and Monitoring:** + - dLOM detection** receives signals from the **Multiframe alignment** block and outputs a dLOM signal. + - Consequent actions** block receives dLOM, dLOF, dLOL, dLOFLANE[1..4], and dLOS-P[1..4] signals and outputs aSSF. + - Defect correlation** block receives dLOM, dLOF, dLOL, dLOFLANE[1..4], and dLOS-P[1..4] signals and outputs MI\_cLOM, MI\_cLOF, MI\_cLOL, and MI\_cLOS signals. + - Performance monitoring** block receives nFECcorrErr and MI\_FECEn signals and outputs MI\_1second and MI\_pFECcorrErr signals. +- Labels:** The entire process is labeled **OTSiG/OTU3\_A\_Sk\_MP** on the right side. The top output is labeled **OTU3\_CP**. + +Block diagram of OTSiG/OTUk\_A\_Sk processes (k = 3). The diagram shows the signal flow from 4 physical lanes at the bottom to a single OTU3\_CP output at the top. Each physical lane contains a Clock recovery and LOS detection block. These connect to 4 logical lanes, each containing a Lane frame alignment, Lane alignment recovery, and Elastic store (with RD and WR pointers). A central Lane marker and delay processing block connects the logical lanes and provides a dLOL signal. The signals then pass through a 16-byte block Mux (with Lane rotation and muxing control). Above the mux is an Optional section with Frame alignment and dLOF detection, followed by a Descrambler, FEC decoder, and Multiframe alignment block. This block outputs CI\_D, CI\_CK, CI\_FS, and CI\_MFS signals. Various detection signals (dLOM, dLOF, dLOL, dLOFLANE[1..4], dLOS-P[1..4]) are fed into Consequent actions (producing aSSF) and Defect correlation (producing MI\_cLOM, MI\_cLOF, MI\_cLOL, MI\_cLOS) blocks. Performance monitoring blocks receive nFECcorrErr and MI\_FECEn signals and output MI\_1second and MI\_pFECcorrErr. The entire process is labeled OTSiG/OTU3\_A\_Sk\_MP on the right. Inputs at the bottom are OTSi\_AP[1] and OTSi\_AP[4]. + +G.798(17)-Cor.2(21)\_F16-10 + +Figure 16-10 – OTSiG/OTUk\_A\_Sk processes (k = 3) + +![Block diagram of OTSiG/OTU4_A_Sk_MP processes (k=4).](d081abfd06a4b868f797e5669c6dff78_img.jpg) + +The diagram illustrates the OTSiG/OTU4\_A\_Sk\_MP processes (k=4). The signal flow starts at the bottom with physical lanes and moves upwards to the OTU4\_CP interface. + +- Physical Layer:** At the bottom, there are 4 physical lanes (represented by OTSi\_AP[1] to OTSi\_AP[4]). Each physical lane contains a **Clock recovery** block and a **LOS detection** block (outputting dLOS-P[1..4]). These feed into **1:5 bit dis-interleaver** blocks, which expand the 4 physical lanes into 20 logical lanes. +- Logical Lanes:** There are 20 logical lanes (Lane #1 to Lane #20). Each logical lane consists of: + - Lane frame alignment** (outputting dLOFLANE[1..20]) + - Lane alignment recovery** + - LLM removal** + - Elastic store** (with RD and WR clock domains) + A central **Lane marker and delay processing** block coordinates across all 20 logical lanes and outputs a **dLOL** (Loss of Lane Alignment) signal. +- Multiplexing and Alignment:** The 20 logical lanes are combined by a **16-byte block Mux**. This is followed by an **Optional Frame alignment** block and **dLOF detection** (outputting dLOF). +- Processing Chain:** The signal then passes through: + - Descrambler** + - Pre-FEC Multiframe alignment** + - FEC decoder** (outputting nFECcorrErr) + - Multiframe alignment** (outputting dLOM detection and dLOM) +- Outputs and Monitoring:** The final data output is **OTU4\_CP** (with signals CI\_D, CI\_CK, CI\_FS, CI\_MFS). + - Performance monitoring** block outputs MI\_1second and MI\_pFECcorrErr. + - Defect correlation** block outputs MI\_cLOM, MI\_cLOF, MI\_cLOL, and MI\_cLOS. + - Consequent actions** block receives various defect signals (dLOM, dLOF, dLOL, dLOFLANE, dLOS-P) and outputs **aSSF** and **CI\_SSF**. +- Control:** A **Lane rotation and mixing control** block (labeled 'A') interfaces with the Mux and Lane marker processing. + +Block diagram of OTSiG/OTU4\_A\_Sk\_MP processes (k=4). + +G.798(17)-Cor.2(21)\_F16-11 + +OTSiG/OTU4-a\_A\_Sk\_MP + +Figure 16-11 – OTSiG/OTUk\_A\_Sk processes (k = 4) + +## Defects + +The function shall detect dLOS-P[1...4], dLOFLANE[1...y], dLOL, dLOF and dLOM. + +For OTU3, y = 4; for OTU4, y = 20. + +For each physical lane #i with i = 1..4: + +**dLOS-P[i]**: See clause 6.2.1.2. + +For each logical lane #i with i = 1..y: + +**dLOFLANE[i]**: See clause 6.2.5.6. + +**dLOL**: See clause 6.2.5.5. + +**dLOF**: If the optional frame alignment process is present, see clause 6.2.5.1, otherwise + +$$\text{dLOF} \leftarrow \sum \text{dLOFLANE}[i]$$ + +**dLOM**: See clause 6.2.5.2. + +## Consequent actions + +$$\text{aSSF} \leftarrow \text{dLOF or dLOM or } \sum \text{dLOS-P}[i] \text{ or dLOL or } \sum \text{dLOFLANE}[i]$$ + +## Defect correlations + +$$\text{cLOS} \leftarrow \sum \text{dLOS-P}[i]$$ +$$\text{cLOL} \leftarrow (\text{dLOL or } \sum \text{dLOFLANE}[i]) \text{ and (not } \sum \text{dLOS-P}[i])$$ +$$\text{cLOF} \leftarrow \text{dLOF and (not } \sum \text{dLOS-P}[i])$$ +$$\text{cLOM} \leftarrow \text{dLOM and (not dLOF) and (not } \sum \text{dLOS-P}[i])$$ + +## Performance monitoring + +The OTSiG/OTUk-a\_A\_Sk function shall perform the following performance monitoring primitives processing. The performance monitoring primitives shall be reported to the equipment management function (EMF). + +$$\text{pFECorrErr} \leftarrow \sum \text{nFECorrErr}$$ + +NOTE 2 – During AI\_TSF-P, dAIS, dLOF and dLOM, no corrected bits shall be counted. + +## 16.4 OTSiG to OTUkV adaptation function (OTSiG/OTUkV\_A) + +The OTSiG to OTUkV adaptation functions perform the adaptation between the OTSiG layer adapted information and the characteristic information of functionally standardized OTUkV layer signal. + +### 16.4.1 OTSiG to OTUkV adaptation source function (OTSiG/OTUkV\_A\_So) + +The information flow and processing of the OTSiG/OTUkV\_A\_So function is defined with reference to Figure 16-12. + +## Symbol + +![Diagram of the OTSiG/OTUkV_A_So function symbol. An input OTUkV_CP enters a trapezoidal block labeled OTSiG/OTUkV. Inside the block, a dashed oval with arrows at both ends is labeled '1' on the left and 'm' on the right. Below the block, two output arrows are shown, labeled OTSi_AP[1] and OTSi_AP[m]. Below the diagram is the text G.798(17)-Amd.4(22)_F16-12.](34f4f0a61ba9563367acac205416e28c_img.jpg) + +Diagram of the OTSiG/OTUkV\_A\_So function symbol. An input OTUkV\_CP enters a trapezoidal block labeled OTSiG/OTUkV. Inside the block, a dashed oval with arrows at both ends is labeled '1' on the left and 'm' on the right. Below the block, two output arrows are shown, labeled OTSi\_AP[1] and OTSi\_AP[m]. Below the diagram is the text G.798(17)-Amd.4(22)\_F16-12. + +Figure 16-12 – OTSiG/OTUkV\_A\_So function + +## Interfaces + +Table 16-9 – OTSiG/OTUkV\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------|-------------------------------------------| +| OTUkV_CP:
OTUkV_CI_CK
OTUkV_CI_D
OTUkV_CI_FS
OTUkV_VI_MFS (Note) | For each OTSiG_AP:
OTSiG_AI_PLD | +| NOTE – If OTUkV has a multiframe | | + +## Processes + +The OTSiG/OTUkV\_A\_So function provides all processes necessary for the adaptation to the OTSiG layer, which includes processes that ensure clock and frame recovery at the adaptation sink and optional forward error correction coding. + +The specific processes are outside the scope of this Recommendation. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 16.4.2 OTSiG to OTUkV adaptation sink function (OTSiG/OTUkV\_A\_Sk) + +The information flow and processing of the OTSiG/OTUkV\_A\_Sk function is defined with reference to Figure 16-13. + +## Symbol + +![Diagram of the OTSiG/OTUkV_A_Sk function symbol. The symbol is a trapezoid labeled 'OTSiG/OTUkV'. It has multiple input arrows from the bottom: 'OTSi_AP[1]', 'OTSi_AP[m]', and 'OTSiG-O_AP'. A dashed oval with arrows labeled '1' and 'm' is positioned between the bottom inputs and the trapezoid, with the label 'OTSiG' to its left. An output arrow points from the top of the trapezoid to 'OTUkV_CP'. Another output arrow points from the left side of the trapezoid to 'OTSiG/OTUkV_A_Sk_MP'. A small note 'G.798(17)-Amd.4(22)_F16-13' is at the bottom right.](eaa8ee2530516c47ef4dcc8a5db20fd0_img.jpg) + +Diagram of the OTSiG/OTUkV\_A\_Sk function symbol. The symbol is a trapezoid labeled 'OTSiG/OTUkV'. It has multiple input arrows from the bottom: 'OTSi\_AP[1]', 'OTSi\_AP[m]', and 'OTSiG-O\_AP'. A dashed oval with arrows labeled '1' and 'm' is positioned between the bottom inputs and the trapezoid, with the label 'OTSiG' to its left. An output arrow points from the top of the trapezoid to 'OTUkV\_CP'. Another output arrow points from the left side of the trapezoid to 'OTSiG/OTUkV\_A\_Sk\_MP'. A small note 'G.798(17)-Amd.4(22)\_F16-13' is at the bottom right. + +Figure 16-13 – OTSiG/OTUkV\_A\_Sk function + +## Interfaces + +Table 16-10 – OTSiG/OTUkV\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| For each OTSi_AP:
OTSi_AI_PLD
OTSiG-O_AP:
OTSiG-O_AI_TSF-P
OTSiG-O_AI_TSF-O
OTSiG/OTUkV_A_Sk_MP:
OTSiG/OTUkV_A_Sk_MI_1second (Note 2) | OTUkV_CP:
OTUkV_CI_CK
OTUkV_CI_D
OTUkV_CI_FS
OTUkV_CI_MFS (Note 1)
OTUkV_CI_SSF
OTSiG/OTUkV_A_Sk_MP:
OTSiG/OTUkV_A_Sk_MI_cLOS-P
OTSiG/OTUkV_A_Sk_MI_cLOF
OTSiG/OTUkV_A_Sk_MI_cLOM (Note 1)
OTSiG/OTUkV_A_Sk_MI_pFECcorrErr (Note 2) | +| NOTE 1 – If OTUkV has a multiframe. | | +| NOTE 2 – If the function performs FEC. | | + +## Processes + +The OTSiG/OTUkV\_A\_Sk function provides all processes necessary for the adaptation from the OTSiG layer, which includes processes for clock and frame start recovery and optional forward error correction decoding. + +The specific processes are outside the scope of this Recommendation. + +## Defects + +The function shall detect dAIS and dLOF. If the OTUkV includes a multiframe, it shall in addition detect dLOM. + +**dLOS-P:** See clause 6.2.1.2. + +**dAIS:** See clause 6.2.6.3.1. + +**dLOF:** The dLOF detection depends on the specific frame structure and is outside the scope of this Recommendation. + +**dLOM:** The dLOM detection is only required if the OTUkV has a multiframe, the detection depends on the specific multiframe structure and is outside the scope of this Recommendation. + +**Consequent actions:** + +aSSF $\leftarrow$ dLOS-P or dAIS or dLOF or AI\_TSF-P or dLOM + +NOTE 1 – dLOM is only included if the OTUkV has a multiframe. + +**Defect correlations** + +cLOS-P $\leftarrow$ dLOS-P and (not AI\_TSF-P) + +cLOF $\leftarrow$ dLOF and (not dLOS-P) and (not dAIS) and (not AI\_TSF-P) + +cLOM $\leftarrow$ dLOM and (not dLOS-P) and (not dLOF) and (not dAIS) and (not AI\_TSF-P) + +NOTE 2 – cLOM is only defined if the OTUkV has a multiframe. + +NOTE 3 – dAIS is not reported as fault cause as it is a secondary alarm and will result in aSSF, which is reported as cSSF fault cause in the ODU\_TT\_Sk that directly follows this function. + +**Performance monitoring** + +The function shall perform the following performance monitoring primitives processing if it includes FEC processing. The performance monitoring primitives shall be reported to the EMF. + +pFECcorrErr $\leftarrow \sum$ nFECcorrErr + +NOTE 4 – During AI\_TSF-P, dAIS, dLOF and dLOM no corrected bits shall be counted. + +**16.5 OTSi to OTUCn adaptation function (OTSi/OTUCn\_A)** + +The OTSi to OTUCn adaptation functions perform the adaptation between the OTSi layer adapted information and the characteristic information of the completely standardized OTUCn layer signal. + +**16.5.1 OTSi to OTUCn adaptation source function (OTSi/OTUCn\_A\_So)** + +The information flow and processing of the OTSi/OTUCn\_A\_So function is defined with reference to Figure 16-14. + +**Symbol** + +![Diagram of the OTSi/OTUCn_A_So function symbol. It shows an input OTUCn_CP entering a trapezoidal block labeled OTSi/OTUCn, with an output OTSi_AP exiting the block. Below the diagram is the text G.798(17)_F16-14.](e09924f32278bb6a47909ae24bbea647_img.jpg) + +G.798(17)\_F16-14 + +Diagram of the OTSi/OTUCn\_A\_So function symbol. It shows an input OTUCn\_CP entering a trapezoidal block labeled OTSi/OTUCn, with an output OTSi\_AP exiting the block. Below the diagram is the text G.798(17)\_F16-14. + +**Figure 16-14 – OTSi/OTUCn\_A\_So function** + +**Interfaces** + +**Table 16-11 – OTSi/OTUCn\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------|--------------------------------| +| OTUCn_CP:
OTUCn_CI_CK
OTUCn_CI_D
OTUCn_CI_FS
OTUCn_CI_MFS | OTSi_AP:
OTSi_AI_PLD | + +## Processes + +The OTSi/OTUCn\_A\_So function provides all processes necessary for the adaptation to the OTSi layer, which includes processes that ensure clock and frame recovery at the adaptation sink and optional forward error correction coding. + +The specific processes are outside the scope of this Recommendation. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 16.5.2 OTSi to OTUCn adaptation sink function (OTSi/OTUCn\_A\_Sk) + +The information flow and processing of the OTSi/OTUCn\_A\_Sk function is defined with reference to Figure 16-15. + +#### Symbol + +![Diagram of the OTSi/OTUCn_A_Sk function. A central trapezoidal block labeled 'OTSi/OTUCn' has two input arrows from below labeled 'OTSi_AP' and 'OTSiG-O_AP'. It has one output arrow pointing upwards labeled 'OTUCn_CP'. It also has a bidirectional horizontal arrow on the left labeled 'OTSiG/OTUCn_A_Sk_MP'. Below the diagram is the text 'G.798(17)-Amd.4(22)_F16-15'.](f01f6190861749ff3bb7749fd05d4a18_img.jpg) + +Diagram of the OTSi/OTUCn\_A\_Sk function. A central trapezoidal block labeled 'OTSi/OTUCn' has two input arrows from below labeled 'OTSi\_AP' and 'OTSiG-O\_AP'. It has one output arrow pointing upwards labeled 'OTUCn\_CP'. It also has a bidirectional horizontal arrow on the left labeled 'OTSiG/OTUCn\_A\_Sk\_MP'. Below the diagram is the text 'G.798(17)-Amd.4(22)\_F16-15'. + +**Figure 16-15 – OTSi/OTUCn\_A\_Sk function** + +#### Interfaces + +**Table 16-12 – OTSi/OTUCn\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OTSi_AP:
OTSi_AI_PLD
OTSiG-O_AP:
OTSiA_AI_TSF-O
OTSiA_AI_TSF-P
OTSi/OTUCn_A_Sk_MP:
OTSi/OTUCn_A_Sk_MI_1second | OTUCn_CP:
OTUCn_CI_CK
OTUCn_CI_D
OTUCn_CI_FS
OTUCn_CI_MFS
OTUCn_CI_SSF
OTSi/OTUCn_A_Sk_MP:
OTSi/OTUCn_A_Sk_MI_cLOS-P
OTSi/OTUCn_A_Sk_MI_cLOL
OTSi/OTUCn_A_Sk_MI_cLOF
OTSi/OTUCn_A_Sk_MI_cLOM
OTSi/OTUCn_A_Sk_MI_pFECcorrErr | + +## Processes + +The OTSi/OTUCn\_A\_Sk function provides all processes necessary for the adaptation from the OTSi layer, which includes processes for clock and frame start recovery and optional forward error correction decoding. + +The specific processes are outside the scope of this Recommendation. + +## Defects + +The function shall detect dLOS-P[1..m], dLOF and dLOM. + +**dLOS-P[i]:** See clause 6.2.1.2. + +**dLOF:** See clause 6.2.5.1. + +**dLOM:** See clause 6.2.5.2. + +## Consequent actions: + +$a\text{SSF} \leftarrow \sum d\text{LOS-P}[i] \text{ or } d\text{LOF} \text{ or } \text{AI\_TSF-P} \text{ or } d\text{LOM}$ + +## Defect correlations + +$c\text{LOS-P} \leftarrow \sum d\text{LOS-P}[i] \text{ and (not AI\_TSF-P)}$ + +$c\text{LOF} \leftarrow d\text{LOF} \text{ and (not } \sum d\text{LOS-P}[i] \text{) and (not AI\_TSF-P)}$ + +$c\text{LOM} \leftarrow d\text{LOM} \text{ and (not } \sum d\text{LOS-P}[i] \text{) and (not } d\text{LOF) and (not AI\_TSF-P)}$ + +## Performance monitoring + +The function shall perform the following performance monitoring primitives processing if it includes FEC processing. The performance monitoring primitives shall be reported to the EMF. + +$p\text{FECcorrErr} \leftarrow \sum n\text{FECcorrErr}$ + +NOTE – During AI\_TSF-P, dLOF and dLOM no corrected bits shall be counted. + +## 16.6 OTSiG to OTUCn adaptation function (OTSiG/OTUCn\_A) + +The OTSiG to OTUCn adaptation functions perform the adaptation between the OTSiG layer adapted information and the characteristic information of the completely standardized OTUCn layer signal. + +### 16.6.1 OTSiG to OTUCn adaptation source function (OTSiG/OTUCn\_A\_So) + +The information flow and processing of the OTSiG/OTUCn\_A\_So function is defined with reference to Figure 16-16. + +#### Symbol + +![Diagram of the OTSiG/OTUCn_A_So function symbol. An input labeled OTUCn_CP enters a trapezoidal block labeled OTSiG/OTUCn. Inside the block, a dashed oval contains two vertical arrows pointing downwards, labeled 1 and m respectively. The output consists of two parallel lines labeled OTSi_AP[1] and OTSi_AP[m]. Below the diagram is the text G.798(17)-Amd.4(22)_F16-16.](9a53cf0c36d7542a25d60835be986e5a_img.jpg) + +G.798(17)-Amd.4(22)\_F16-16 + +Diagram of the OTSiG/OTUCn\_A\_So function symbol. An input labeled OTUCn\_CP enters a trapezoidal block labeled OTSiG/OTUCn. Inside the block, a dashed oval contains two vertical arrows pointing downwards, labeled 1 and m respectively. The output consists of two parallel lines labeled OTSi\_AP[1] and OTSi\_AP[m]. Below the diagram is the text G.798(17)-Amd.4(22)\_F16-16. + +**Figure 16-16 – OTSiG/OTUCn\_A\_So function** + +## Interfaces + +**Table 16-13 – OTSiG/OTUCn\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------|-----------------------------------------| +| OTUCn_CP:
OTUCn_CI_CK
OTUCn_CI_D
OTUCn_CI_FS
OTUCn_CI_MFS | For each OTSi_AP:
OTSi_AI_PLD | + +## Processes + +The OTSiG/OTUCn\_A\_So function provides all processes necessary for the adaptation to the OTSiA layer, which includes processes that ensure clock and frame recovery at the adaptation sink and optional forward error correction coding. + +The specific processes are outside the scope of this Recommendation. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 16.6.2 OTSiG to OTUCn adaptation sink function (OTSiG/OTUCn\_A\_Sk) + +The information flow and processing of the OTSiG/OTUCn\_A\_Sk function is defined with reference to Figure 16-17. + +#### Symbol + +![Diagram of the OTSiG/OTUCn_A_Sk function. A central trapezoidal block is labeled 'OTSiG/OTUCn'. To its left, an arrow labeled 'OTSiG/OTUCn_A_Sk_MP' points into the block. Above the block, an arrow labeled 'OTUCn_CP' points out. Below the block, three arrows point into it: 'OTSi_AP[1]', 'OTSi_AP[m]', and 'OTSiG-O_AP'. A dashed oval labeled 'OTSiG' encloses the bottom input arrows, with '1' and 'm' indicating multiple inputs.](50d5b503f4b41d7a601c1340dfd6aa74_img.jpg) + +G.798(17)-Amd.4(22)\_F16-17 + +Diagram of the OTSiG/OTUCn\_A\_Sk function. A central trapezoidal block is labeled 'OTSiG/OTUCn'. To its left, an arrow labeled 'OTSiG/OTUCn\_A\_Sk\_MP' points into the block. Above the block, an arrow labeled 'OTUCn\_CP' points out. Below the block, three arrows point into it: 'OTSi\_AP[1]', 'OTSi\_AP[m]', and 'OTSiG-O\_AP'. A dashed oval labeled 'OTSiG' encloses the bottom input arrows, with '1' and 'm' indicating multiple inputs. + +**Figure 16-17 – OTSiG/OTUCn\_A\_Sk function** + +## Interfaces + +**Table 16-14 – OTSiG/OTUCn\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| For each OTSi_AP:
OTSi_AI_PLD
OTSiG-O_AP:
OTSiA_AI_TSF-O
OTSiA_AI_TSF-P
OTSiG/OTUCn_A_Sk_MP:
OTSiG/OTUCn_A_Sk_MI_1second | OTUCn_CP:
OTUCn_CI_CK
OTUCn_CI_D
OTUCn_CI_FS
OTUCn_CI_MFS
OTUCn_CI_SSF
OTSiG/OTUCn_A_Sk_MP:
OTSiG/OTUCn_A_Sk_MI_cLOS-P
OTSiG/OTUCn_A_Sk_MI_cLOL
OTSiG/OTUCn_A_Sk_MI_cLOF
OTSiG/OTUCn_A_Sk_MI_cLOM
OTSiG/OTUCn_A_Sk_MI_pFECcorrErr | + +## Processes + +The OTSiG/OTUCn\_A\_Sk function provides all processes necessary for the adaptation from the OTSiG layer, which includes processes for clock and frame start recovery and optional forward error correction decoding. + +The specific processes are outside the scope of this Recommendation. + +## Defects + +The function shall detect dLOS-P[1..m], dLOF and dLOM. + +**dLOS-P[i]:** See clause 6.2.1.2. + +**dLOF:** See clause 6.2.5.1. + +**dLOM:** See clause 6.2.5.2. + +## Consequent actions: + +aSSF $\leftarrow \sum$ dLOS-P[i] or dLOF or AI\_TSF-P or dLOM + +## Defect correlations + +cLOS-P $\leftarrow \sum$ dLOS-P[i] and (not AI\_TSF-P) + +cLOF $\leftarrow$ dLOF and (not $\sum$ dLOS-P[i]) and (not AI\_TSF-P) + +cLOM $\leftarrow$ dLOM and (not $\sum$ dLOS-P[i]) and (not dLOF) and (not AI\_TSF-P) + +## Performance monitoring + +The function shall perform the following performance monitoring primitives processing if it includes FEC processing. The performance monitoring primitives shall be reported to the EMF. + +pFECcorrErr $\leftarrow \sum$ nFECcorrErr + +NOTE – During AI\_TSF-P, dLOF and dLOM no corrected bits shall be counted. + +## 16.7 OTSi to FlexO-x adaptation function (OTSi/FlexO-x\_A) + +The OTSi to FlexO-x ( $x = 1, 2, 4$ ) adaptation functions perform the adaptation between the Modulator/Demodulator layer adapted information and the characteristic information of the FlexO-x + +layer signal for the flexible OTN long reach interfaces with different FEC schemes and targeting various modulation schemes. For each FEC scheme, two types of functions are defined: one that supports the standardized FlexOsec encryption and authentication functions (GCM-AES-256) and one that does not support FlexOsec encryption and authentication. + +**Table 16-14.1 – OTSi to FlexO-*x* adaptation functions (*x* = 1, 2, 4)** + +| Function type | Function name | FlexO- x | +|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| +| M-AI/FlexO-1-SC_A | OTSi to FlexO-1 adaptation function with Staircase FEC code (no DSP frame) with 4 lanes towards the M-AP and without FlexOsec encryption and authentication | x =1 | +| M-AI/FlexO-1-GCM-SC_A | OTSi to FlexO- x adaptation source function with Staircase FEC code (no DSP frame), with 4 lanes towards the M-AP and with GCM-AES-256 FlexOsec encryption and authentication | x =1 | +| M-AI/FlexO- x -DSH-Z_A | OTSi to FlexO- x adaptation function with Staircase plus Hamming concatenated FEC code using the DSH frame format, with Z lanes towards the M-AP and without FlexOsec encryption and authentication | { x , Z }= {1,4}, {2,4}, {2,8}, {4,8} | +| M-AI/FlexO- x -GCM-DSH-Z_A | OTSi to FlexO- x adaptation source function with Staircase plus Hamming concatenated FEC code using the DSH frame format, with Z lanes towards the M-AP and with GCM-AES-256 FlexOsec encryption and authentication | { x , Z }= {1,4}, {2,4}, {2,8}, {4,8} | +| M-AI/FlexO- x -DO-Z_A | OTSi to FlexO- x adaptation function with OFEC code using the DO frame format, with Z lanes towards the M-AP and without FlexOsec encryption and authentication | { x , Z }= {1,4}, {2,4}, {2,8}, {4,8} | +| M-AI/FlexO- x -GCM-DO-Z_A | OTSi to FlexO- x adaptation source function with OFEC code using the DO frame format, with Z lanes towards the M-AP and with GCM-AES-256 FlexOsec encryption and authentication | { x , Z }= {1,4}, {2,4}, {2,8}, {4,8} | + +### 16.7.1 OTSi to FlexO-1-SC adaptation source function (OTSi/FlexO-1-SC\_A\_So and OTSi/FlexO-1-GCM-SC\_A\_So) + +The information flow and processing of the OTSi/FlexO-1-SC\_A\_So and M-AI/FlexO-1-GCM-SC\_A\_So functions is defined with reference to Figures 16-17.1 and 16-17.2. The interfaces of these functions are defined in Table 16-14.1. + +## Symbol + +![Diagram showing two functional symbols. The left symbol is 'M-AI/FlexO-1-SC' with input 'FlexO-1_CP (x = 1, 2, 4)' and output 'OTSi_AP' via 'M-AP[1..4]'. The right symbol is 'M-AI/FlexO-1-GCM-SC' with inputs 'FlexO-1_CP (x = 1, 2, 4)' and 'SK_COMMS_CP', and output 'OTSi_AP' via 'M-AP[1..4]'. It also has an input 'M-AI/FlexO-1-GCM-SC_A_So_SKP'.](18d75b5fb1019ed4bc5384d14f8d1b7a_img.jpg) + +G.798(17)-Amd.4(22)\_F16-17.1 + +Diagram showing two functional symbols. The left symbol is 'M-AI/FlexO-1-SC' with input 'FlexO-1\_CP (x = 1, 2, 4)' and output 'OTSi\_AP' via 'M-AP[1..4]'. The right symbol is 'M-AI/FlexO-1-GCM-SC' with inputs 'FlexO-1\_CP (x = 1, 2, 4)' and 'SK\_COMMS\_CP', and output 'OTSi\_AP' via 'M-AP[1..4]'. It also has an input 'M-AI/FlexO-1-GCM-SC\_A\_So\_SKP'. + +**Figure 16-17.1 – OTSi/FlexO-1-SC\_A\_So and M-AI/FlexO-1-GCM-SC\_A\_So function** + +## Interfaces + +**Table 16-14.1 – OTSi/FlexO-1-SC\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------| +| FlexO_CP :
FlexO_CI_CK
FlexO_CI_D
FlexO_CI_FS
FlexO_CI_MFS
M-AI/FlexO-1-GCM-SC_A_So_SKP: (Note)
M-AI/FlexO-1-GCM-SC_A_So_SKI_Key[0,1,2,3]
M-AI/FlexO-1-GCM-SC_A_So_SKI_KI
M-AI/FlexO-1-GCM-SC_A_So_SKI_IV_Fixed_ID
SK_COMMS_CP: (Note)
SK_COMMS_CI_D | M-AP:
M-AI_D[1..4]
SK_COMMS_CP: (Note)
SK_COMMS_CI_CK | +| NOTE – For OTSiG/FlexO-1-GCM-SC_A_So only. | | + +## Processes + +The processes associated with the OTSi/FlexO-1-SC\_A\_So and M-AI/FlexO-1-GCM-SC\_A\_So function are as depicted in Figure 16-17.2. + +**MFAS insertion:** The function shall insert the MFAS into the FlexO overhead area as described in [ITU-T G.709.1]. + +### FlexOsec processes: + +- For M-AI/FlexO-1-GCM-SC\_A\_So function, see clause 8.14.1, and clause 8.14.3.1 for the specific FlexOsec GCM-AES-256 encryption and authentication processes with the cipher suite type (CST) code point value 000001, as defined in clause B.1 of [ITU-T G.709.1]. The secure key information (SKI) inputs from the key exchange and agreement functions provide a set of configurable keys and trigger the switch to a new key through SKI\_KI input. +- For M-AI/FlexO-1-SC\_A\_So function, this is a null process connecting its output signals to the corresponding input signals. + +**COMMS clock generation:** For M-AI/FlexO-1-GCM-SC\_A\_So function, the process shall generate SK\_COMMS clock (CK\_COM) by dividing the FlexO clock (CI\_CK) by a factor of 82240. + +**Insert KCC:** The in-band key exchange communication channel (KCC) is optional for M-AI/FlexO-1-GCM-SC\_A\_So function and unused for M-AI/FlexO-1-SC\_A\_So function. When used, the + +incoming SK\_COMMS\_CI\_D data is inserted after FlexOsec authentication and encryption into the KCC field of the FlexO-1 frame (CI\_D) as described in clause 9.3.2.5 of [ITU-T G.709.1]. When it is not used, the all-ZEROS reserved value is inserted into the KCC field. + +**Alignment insertion:** The function shall insert the alignment marker into the FlexO-1 frame AM area as described in clause 9 of [ITU-T G.709.3]. + +**Mapping:** The function shall map (i.e., addition of staircase FEC parity area) the incoming FlexO-1 frame into the FlexO-1-SC frame payload area as defined in clause 11.1 of [ITU-T G.709.3]. + +**Clock generation:** The function shall generate the FlexO-1-SC clock by multiplying the incoming FlexO clock (CI\_CK) by $[5485/5140]$ to the frequency as listed in Table 11-2 of [ITU-T G.709.3]. The FOIC1.4-SC lane clock is obtained by dividing the FlexO-1-SC clock by a factor 4. + +**FBS, FBGS and MBS generation:** The function shall generate the staircase (SC) FEC block start (BS) and group start (FBGS) using the incoming FlexO-1 frame start (FS) to align the Staircase FEC blocks structure with the FlexO-1-SC frame structure as described in clause 11.1 of [ITU-T G.709.3]. An SC FEC block group (FBG) consists of 238 consecutive FlexO-1-SC frame rows that is exactly $5140 \times 238$ bits; it contains five SC FEC blocks. In addition, the function shall generate the SC FEC multi-block sequence start (MBS) every 128 SC FEC blocks, to synchronize the state of the staircase (SC) FEC error decorrelator (ED) as described in clause 11.3.2 of [ITU-T G.709.3]. + +**Generate FBA:** The function shall generate the FEC block alignment (FBA) overhead as described in clause 11.3.1 of [ITU-T G.709.3]. + +**FEC OH insertion:** The function shall insert the FEC block alignment (FBA) overhead into the FEC overhead area within the extended overhead of the FlexO-1-SC frame as described in clause 11.3 of [ITU-T G.709.3]. + +**Generate MBAS:** The function shall generate the 6-bit SC FEC multi block alignment signal (MBAS) to be inserted into the FlexO-1-SC OH area as described in clause 11.3.2 and Annex C of [ITU-T G.709.3]. + +**FEC adapter and encoder:** See clause 8.5.4. + +**Scrambler:** The function shall scramble FlexO-1-SC frame payload, FEC parity, fixed stuffing, extended overhead and basic overhead area as defined in clause 11.5 of [ITU-T G.709.3]. + +**Symbol Distribution:** The function shall divide FlexO-1-SC frame signal into 4 FOIC1.4-SC lanes based on 10-bit symbol granularity as described in clause 11.6 of [ITU-T G.709.3]. + +Note that the 4 FOIC1.4-SC logical lanes carry a dual polarization symbol, so that 2 lanes are to be associated with polarization X, while the other 2 lanes are to be associated with the polarization Y. The mapping of the 4 lanes to the dual polarization symbol is specified in clause 11.6.1 of [ITU-T G.709.3]. + +**PMA process:** The process shall map the FOIC1.4-SC lanes onto the physical media adapted interface. The details are out of scope of this Recommendation. + +![Block diagram of OTSi/FlexO-1-SC_A_So and M-AI/FlexO-1-GCM-SC_A_So processes. The diagram shows the signal flow from FlexO-1_CP and SK_COMMS_CP inputs through various processing stages including MFAS insertion, FlexOsec processes, Alignment insertion, Mapping, FEC OH insertion, FEC adapter and encoder, Scrambler, Symbol distribution, and PMA to M-AP outputs. Control signals like CK_D, CK_CK, CK_FS, CK_MFS, CK_COM, D_COM, CK_SC, and various keys (SKI_Key, SKI_KI, SKI_IV_Fixed_ID) are also shown.](9ef8e686bf7d4fdc4504d136e1b350f0_img.jpg) + +The diagram illustrates the signal processing flow for OTSi/FlexO-1-SC\_A\_So and M-AI/FlexO-1-GCM-SC\_A\_So. At the top, FlexO-1\_CP inputs (CI\_D, CI\_CK, CI\_FS, CI\_MFS) enter the 'MFAS insertion' block. SK\_COMMS\_CP inputs (CI\_CK, CI\_D) enter the 'COMMS clock generation' block. The 'COMMS clock generation' block outputs CK\_COM and D\_COM signals. The 'FlexOsec processes' block receives D, CK, and FS signals from 'MFAS insertion' and control signals (SKI\_Key[0, 1, 2, 3], SKI\_KI, SKI\_IV\_Fixed\_ID) from the right. It also receives CK\_COM and D\_COM from 'COMMS clock generation' and D\_sec from 'Insert KCC'. The 'Insert KCC' block receives CK\_COM and D\_COM from 'COMMS clock generation'. The 'FlexOsec processes' block outputs D, CK, and FS signals to the 'Alignment insertion' block. The 'Alignment insertion' block outputs D, CK, and FS signals to the 'Mapping (to-SC frame)' block. The 'Mapping (to-SC frame)' block receives CK\_SC from 'FlexO-1 SC clock generation (×5485/5140)' and outputs D and FS signals. The 'FEC OH insertion' block receives D and FS signals from 'Mapping (to-SC frame)' and FBA from 'Generate FBA'. It outputs D and FS signals to the 'FEC adapter and encoder' block. The 'Generate FBA' block receives FBGS, MBS, and BS from the 'BS, MBS and FBGS generator' and outputs FBA. The 'FEC adapter and encoder' block receives D and FS signals from 'FEC OH insertion' and MBAS from 'Generate MBAS'. It outputs D and FS signals to the 'Scrambler' block. The 'Generate MBAS' block receives FBGS, MBS, and BS from the 'BS, MBS and FBGS generator' and outputs MBAS. The 'Scrambler' block receives D and FS signals from 'FEC adapter and encoder' and outputs D and FS signals to the 'Symbol distribution' block. The 'Symbol distribution' block outputs FOIC1.4-SC D[1..4] and CK\_SC signals to the 'PMA' block. The 'PMA' block outputs 1, ..., 4 signals to the 'M-AP' block. The 'M-AP' block outputs M-AI\_D[1] ... M-AI\_D[4] signals. The 'BS, MBS and FBGS generator' block receives CK\_SC from 'FlexO-1 SC clock generation (×5485/5140)' and outputs FBGS, MBS, and BS signals to 'Generate FBA' and 'Generate MBAS' blocks. The 'FlexO-1 SC clock generation (×5485/5140)' block receives CK\_COM from 'COMMS clock generation' and outputs CK\_SC signals to 'Mapping (to-SC frame)' and 'BS, MBS and FBGS generator' blocks. The diagram is labeled G.798(23)\_F16-17.2 and M-AI/FlexO-1-(GCM)-SC\_A\_So\_SKP. + +Block diagram of OTSi/FlexO-1-SC\_A\_So and M-AI/FlexO-1-GCM-SC\_A\_So processes. The diagram shows the signal flow from FlexO-1\_CP and SK\_COMMS\_CP inputs through various processing stages including MFAS insertion, FlexOsec processes, Alignment insertion, Mapping, FEC OH insertion, FEC adapter and encoder, Scrambler, Symbol distribution, and PMA to M-AP outputs. Control signals like CK\_D, CK\_CK, CK\_FS, CK\_MFS, CK\_COM, D\_COM, CK\_SC, and various keys (SKI\_Key, SKI\_KI, SKI\_IV\_Fixed\_ID) are also shown. + +Figure 16-17.2 – OTSi/FlexO-1-SC\_A\_So and M-AI/FlexO-1-GCM-SC\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +## 16.7.2 OTSi to FlexO-1-SC adaptation sink function (OTSi/FlexO-1-SC\_A\_Sk and M-AI/FlexO-1-GCM-SC\_A\_Sk) + +The information flow and processing of the OTSi/FlexO-1-SC\_A\_Sk and OTSi/FlexO-1-GCM-SC\_A\_Sk functions is defined with reference to Figures 16-17.3 and 16-17.4. The interfaces of these functions are defined in Table 16-14.2. + +### Symbol + +![Figure 16-17.3 shows two block diagrams. The left diagram represents the OTSi/FlexO-1-SC_A_Sk function, showing a block 'M-AI/FlexO-1-SC' with inputs 'M-AP[1..Z]' (from OTSi_AP) and 'M-AI/FlexO-1-SC_Sk_MP' (from M-AI/FlexO-1-SC_Sk_MP), and output 'FlexO-1_CP'. The right diagram represents the M-AI/FlexO-1-GCM-SC_A_Sk function, showing a block 'M-AI/FlexO-1-GCM-SC' with inputs 'M-AP[1..Z]' (from OTSi_AP), 'M-AI/FlexO-1-GCM-SC_Sk_MP' (from M-AI/FlexO-1-GCM-SC_Sk_MP), and 'M-AI/FlexO-1-GCM-SC_A_Sk_SKP' (from M-AI/FlexO-1-GCM-SC_A_Sk_SKP), and outputs 'FlexO-1_CP' and 'SK_COMMS_CP'. A note 'G.798(17)-Amd.4(22)_F16-17.3' is present below the right diagram.](c8262867e39639276066c34941705aed_img.jpg) + +Figure 16-17.3 shows two block diagrams. The left diagram represents the OTSi/FlexO-1-SC\_A\_Sk function, showing a block 'M-AI/FlexO-1-SC' with inputs 'M-AP[1..Z]' (from OTSi\_AP) and 'M-AI/FlexO-1-SC\_Sk\_MP' (from M-AI/FlexO-1-SC\_Sk\_MP), and output 'FlexO-1\_CP'. The right diagram represents the M-AI/FlexO-1-GCM-SC\_A\_Sk function, showing a block 'M-AI/FlexO-1-GCM-SC' with inputs 'M-AP[1..Z]' (from OTSi\_AP), 'M-AI/FlexO-1-GCM-SC\_Sk\_MP' (from M-AI/FlexO-1-GCM-SC\_Sk\_MP), and 'M-AI/FlexO-1-GCM-SC\_A\_Sk\_SKP' (from M-AI/FlexO-1-GCM-SC\_A\_Sk\_SKP), and outputs 'FlexO-1\_CP' and 'SK\_COMMS\_CP'. A note 'G.798(17)-Amd.4(22)\_F16-17.3' is present below the right diagram. + +Figure 16-17.3 – OTSi/FlexO-1-SC\_A\_Sk and M-AI/FlexO-1-GCM-SC\_A\_Sk functions + +### Interfaces + +Table 16-14.2 – OTSi/FlexO-1-SC\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| M_AP:
M-AI_D[1..4]
OTSiG-O_AP:
OTSiA_AI_TSF-O
OTSiA_AI_TSF-P
M-AI/FlexO-1-SC_A_Sk_MP:
M-AI/FlexO-1-SC_A_Sk_MI_1second
M-AI/FlexO-1-SC_A_Sk_MI_SquelchEn (Note)
M-AI/FlexO-1-GCM-SC_A_Sk_SKP: (Note)
M-AI/FlexO-1-GCM-SC_A_Sk_SKI_Key[0,1,2,3]
M-AI/FlexO-1-GCM-SC_A_Sk_SKI_IV_Fixed_ID | FlexO-1_CP:
FlexO-1_CI_CK
FlexO-1_CI_D
FlexO-1_CI_FS
FlexO-1_CI_MFS
FlexO-1_CI_SSF
M-AI/FlexO-1-SC_A_Sk_MP:
M-AI/FlexO-1-SC_A_Sk_MI_AcCST (Note)
M-AI/FlexO-1-SC_A_Sk_MI_cLOS-P
M-AI/FlexO-1-SC_A_Sk_MI_cLOL
M-AI/FlexO-1-SC_A_Sk_MI_cLOM
M-AI/FlexO-1-SC_A_Sk_MI_cCSTM (Note)
M-AI/FlexO-1-SC_A_Sk_MI_cUnlockSec (Note)
M-AI/FlexO-1-SC_A_Sk_MI_pFECcorrErr
M-AI/FlexO-1-SC_A_Sk_MI_pAuthCheckErr (Note)
M-AI/FlexO-1-GCM-SC_A_Sk_SKP: (Note)
M-AI/FlexO-1-GCM-SC_A_Sk_SKI_AcKI
SK_COMMS_CP: (Note)
SK_COMMS_CI_D
SK_COMMS_CI_CK | +| NOTE – For OTSiG/FlexO-1-GCM-SC_A_Sk only. | | + +### Processes + +The processes associated with the OTSi/FlexO-1-SC\_A\_Sk and M-AI/FlexO-1-GCM-SC\_A\_Sk function are as depicted in Figure 16-17.4. + +**PMA process:** The process shall recover the data and clock of the FOIC1.4-SC lanes from the physical media adapted interface. The details are out of scope of this Recommendation. + +**FOIC1.4 Frame alignment:** The function shall recover the start of ¼ FlexO-1-SC frame (FOIC1.4-SC) through obtaining LOCK to the alignment markers as specified by the FEC synchronization state diagram in clause 91.5.3.1 of [IEEE 802.3]. The specific alignment marker to be locked shall be CM0 to CM5 (48 bits) per frame as specified in clause 9.1 of [ITU-T G.709.1] while the distance between alignment markers (counted by amp\_counter) shall correspond to 128 rows as specified in clause 11.1 of [ITU-T G.709.3]. Additionally, the synchronization process on all logical lanes shall be restarted (restart\_lock set to true) if five consecutive alignment markers fail to match on any of the logical lanes. + +**Deskew:** The deskewing process shall remove the skew of all four FOIC1.4-SC lanes as specified by the FEC alignment state diagram in clause 91.5.3.1 of [IEEE 802.3]. It shall support a maximum skew of 180 ns between FEC lanes and a maximum skew variation of 4 ns. + +**Recombination:** The function shall multiplex the aligned and ordered four FOIC1.4-SC lanes into the original stream of FEC-1-SC and reconstruct the FlexO-1-SC frame as described in clause 11.6 of [ITU-T G.709.3]. + +**Descrambler:** The function shall perform descrambling for FlexO-1-SC frame payload, fixed stuffing and extended overhead and basic overhead area as described in clause 11.5 of [ITU-T G.709.3]. + +**FEC OH Extraction:** The function shall extract the FEC Block Alignment (FBA) overhead from the FEC overhead area within the extended overhead of the FlexO-1-SC frame as described in clause 11.3 of [ITU-T G.709.3]. + +**FEC Adapter and Decoder:** See clause 8.5.4. + +NOTE – In this process, the Multi Block Alignment Signal (MBAS) overhead is extracted from FlexO-1-SC overhead as described in clause B.2 of [ITU-T G.709.3] and MBAS sequence is aligned to synchronize SC FEC Error Decorrelator (ED). + +**Demapping:** The function shall demap (i.e., removal of staircase SC FEC parity area) the FlexO-1 frame from the incoming FlexO-1-SC frame as defined in clause 11.1 of [ITU-T G.709.3]. + +**Extract and replace KCC:** The in-band key exchange communication channel (KCC) is optional for M-AI/FlexO-1-GCM-SC\_A\_Sk and unused for M-AI/FlexO-1-SC\_A\_Sk. When used, the function shall extract the KCC data (SK\_COMMS\_CI\_D) from the FlexOsec KCC overhead field of the FlexO-1 as described in clause 9.2.8 of [ITU-T G.709.1]. The bit rate of the KCC data is defined by the outgoing KCC clock. The function shall generate the KCC clock (SK\_COMMS\_CI\_CK) by dividing the FlexO-*x* clock by a factor of 82240. After extraction, the KCC byte in the FlexOsec overhead is replaced with value 0x00 at the input of the FlexOsec sink processes. + +#### **FlexOsec processes:** + +- For M-AI/FlexO-1-GCM-SC\_A\_Sk function, see clause 8.14.2 and clause 8.14.3.1 for the specific GCM-AES-256 decryption and authentication processes with the cipher suite type (CST) code point value 000001, as defined in clause B.1 of [ITU-T G.709.1]. The Secure Key Information (SKI) inputs from the key exchange and agreement functions provide a set of configurable keys and trigger the switch to a new key through SKI\_KI input. +- For M-AI/FlexO-1-SC\_A\_Sk function, this is a null process connecting its output signals to the corresponding input signals. + +**Multiframe alignment:** The process shall recover the FlexO multi-frame start as described in clause 8.2.2. + +![Functional block diagram of OTSi/FlexO-1-SC_A_Sk and M-AI/FlexO-1-GCM-SC_A_Sk processes. The diagram shows a vertical flow of data from bottom to top through various processing stages including PMA, FOIC1.4-SC, Alignment lock, Recombination, Descrambler, FBA extract and alignment, FEC adapter and decoder, Demapping, FlexOsec processes, and Multiframe alignment. It also includes side blocks for Consequent actions, Performance monitoring, Defect correlation, and dCSTM detection. Numerous control and monitoring signals (MI, AI, CI, d-series defects) are shown entering and leaving the blocks.](0bce130a8686477232911728d05b4b13_img.jpg) + +The diagram illustrates the internal architecture of OTSi/FlexO-1-SC\_A\_Sk and M-AI/FlexO-1-GCM-SC\_A\_Sk processes. At the bottom, the **PMA** and **FOIC1.4-SC** blocks receive inputs from **AI\_CKLOC**, **AI\_D[1]..AI\_D[4]** (via **M-AP**), and **AI\_TSF-P** (via **OTSiG-O\_AP**). It outputs **dLOL** and **dLOS-P**. Above this is a lane-based **Alignment lock** stage (4 logical lanes) with **Lane marker process**, feeding into **Recombination**, **Descrambler**, **FBA extract and alignment**, **FEC adapter and decoder**, and **Demapping (from SC-Frame)**. Each block has **D** (data), **CK** (clock), and **FS** (frame sync) interfaces. The **Demapping** block feeds into **FlexOsec processes**, which in turn feed into **Multiframe alignment**. **Multiframe alignment** outputs **dLOM** and various control signals (**Dsec**, **CK**, **FS**) to the **FlexO\_CP** interface. **FlexOsec processes** also output **AuthCheckErr**, **dUnlockSec**, **dLOL**, **MI\_SquelchEn**, and **AcCST**. **AcCST** is processed by **dCSTM detection** to produce **dCSTM**. **dCSTM** and other signals (**dLOM**, **dUnlockSec**, **dLOL**, **dLOS-P**, **AI\_TSF-P**) are processed by **Consequent actions** to produce **aSSF**. **Performance monitoring** and **Defect correlation** blocks receive various error and status signals and output management information (MI) signals. A **Replace and extract KCC** block handles **SK\_COMM\_CP** signals. On the right, vertical text labels the processes as **M-AI/FlexO-1-GCM-SC\_A\_Sk\_SKP** and **M-AI/FlexO-1-GCM-SC\_A\_Sk\_MP**. The diagram is labeled **G.798(23)\_F16-17.4** at the bottom right. + +Functional block diagram of OTSi/FlexO-1-SC\_A\_Sk and M-AI/FlexO-1-GCM-SC\_A\_Sk processes. The diagram shows a vertical flow of data from bottom to top through various processing stages including PMA, FOIC1.4-SC, Alignment lock, Recombination, Descrambler, FBA extract and alignment, FEC adapter and decoder, Demapping, FlexOsec processes, and Multiframe alignment. It also includes side blocks for Consequent actions, Performance monitoring, Defect correlation, and dCSTM detection. Numerous control and monitoring signals (MI, AI, CI, d-series defects) are shown entering and leaving the blocks. + +Figure 16-17.4 – OTSi/FlexO-1-SC\_A\_Sk and M-AI/FlexO-1-GCM-SC\_A\_Sk processes + +## Defects + +The function shall detect dLOS-P, dCSTM, dUnlockSec, dLOL and dLOM. + +**dLOS-P:** See clause 6.2.1.2. + +**dLOL:** dLOL is generated for multilane interfaces based on the FEC alignment state diagram in clause 91.5.3.1 of [IEEE 802.3]. dLOL shall be declared if fec\_alignment\_valid is false for 3 ms. To provide for the case of intermittent out-of-locks (fec\_alignment\_valid is false), the integrating timer shall not be reset to zero until an in-lock (fec\_alignment\_valid is true) condition persists continuously for 3 ms. dLOL shall be cleared if fec\_alignment\_valid is true for 3 ms. + +**dCSTM:** See clause 6.2.11. The expected cipher suite type is "0000 0001". Set to false for M-AI/FlexO-1-SC\_Sk function without FlexOsec. + +**dUnlockSec:** See clause 6.2.7.2.1. Set to false for M-AI/FlexO-1-SC\_Sk function without FlexOsec. + +**dLOM:** See clause 6.2.5.2. + +## Consequent actions + +aSSF $\leftarrow$ dLOM or dLOS-P or dUnlockSec or dCSTM or dLOL or AI\_TSF-P + +## Defect correlations + +cLOS-P $\leftarrow$ dLOS-P and (not AI\_TSF-P) + +cLOL $\leftarrow$ dLOL and (not dLOS-P) and (not AI\_TSF-P) + +cCSTM $\leftarrow$ dCSTM and (not dLOL) and (not AI\_TSF-P) + +cUnlockSec $\leftarrow$ UnlockSec and (not dCSTM) and (not dLOL) and (not AI\_TSF-P) + +cLOM $\leftarrow$ dLOM and (not dCSTM) and (not dLOL) and (not AI\_TSF-P) + +## Performance monitoring + +The function shall perform the following performance monitoring primitives processing. The performance monitoring primitives shall be reported to the equipment management function (EMF). + +pFECcorrErr $\leftarrow \sum$ nFECcorrErr + +pAuthcheckErr $\leftarrow \sum$ AuthcheckErr + +NOTE – During AI\_TSF-P, dUnlockSec and dLOL no corrected bits or authentication failure shall be counted. + +### 16.7.3 OTSi to FlexO-x-DSH adaptation source functions (M-AI/FlexO-x-DSH-Z\_A\_So and M-AI/FlexO-x-GCM-DSH-Z\_A\_So) + +The information flow and processing of the M-AI/FlexO-x-DSH-Z\_A\_So and M-AI/FlexO-x-GCM-DSH-Z\_A\_So functions ( $\{x,Z\}=\{1,4\}, \{2,4\}, \{2,8\}, \{4,8\}$ ) is defined with reference to Figures 16-17.5 and 16-17.6. The interfaces of these functions are defined in Table 16-14.3. + +## Symbol + +![Figure 16-17.5: Symbol diagrams for M-AI/FlexO-x-DSH-Z_A_So and M-AI/FlexO-x-GCM-DSH-Z_A_So functions. The left diagram shows FlexO-x_CP (x = 1, 2, 4) as input to M-AI/FlexO-x-DSH-Z, which outputs M-AP[1..Z] and OTSi_AP. The right diagram shows FlexO-x_CP (x = 1, 2, 4) and SK_COMMS_CP as inputs to M-AI/FlexO-x-GCM-DSH-Z, which also outputs M-AP[1..Z] and OTSi_AP. A note G.798(17)-Amd.4(22)_F16-17.5 is present.](4e716e2091c1c947b7a687ed4e6dae2f_img.jpg) + +Figure 16-17.5: Symbol diagrams for M-AI/FlexO-x-DSH-Z\_A\_So and M-AI/FlexO-x-GCM-DSH-Z\_A\_So functions. The left diagram shows FlexO-x\_CP (x = 1, 2, 4) as input to M-AI/FlexO-x-DSH-Z, which outputs M-AP[1..Z] and OTSi\_AP. The right diagram shows FlexO-x\_CP (x = 1, 2, 4) and SK\_COMMS\_CP as inputs to M-AI/FlexO-x-GCM-DSH-Z, which also outputs M-AP[1..Z] and OTSi\_AP. A note G.798(17)-Amd.4(22)\_F16-17.5 is present. + +**Figure 16-17.5 – M-AI/FlexO-x-DSH-Z\_A\_So and M-AI/FlexO-x-GCM-DSH-Z\_A\_So functions ( $\{x,Z\}=\{1,4\}, \{2,4\}, \{2,8\}, \{4,8\}$ )** + +## Interfaces + +**Table 16-14.3 – M-AI/FlexO-x-DSH-Z\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| FlexO-x_CP :
FlexO-x_CI_CK
FlexO-x_CI_D[1..x]
FlexO-x_CI_FS
FlexO-x_CI_MFS

M-AI/FlexO-x-GCM-DSH-Z_A_So_SKP: (Note)
M-AI/FlexO-x-GCM-DSH-Z_A_So_SKI_Key[0,1,2,3]
M-AI/FlexO-x-GCM-DSH-Z_A_So_SKI_KI
M-AI/FlexO-x-GCM-DSH-Z_A_So_SKI_IV_Fixed_ID

SK_COMMS_CP: (Note)
SK_COMMS_CI_D | M_AP:
M-AI_D[1..Z]

SK_COMMS_CP: (Note)
SK_COMMS_CI_CK | +| NOTE – For OTSiG/FlexO-x-GCM-DSH-Z_A_So only. | | + +## Processes + +The processes associated with the M-AI/FlexO-x-GCM-DSH-Z\_A\_So function are as depicted in Figure 16-17.6. For the M-AI/FlexO-x-DSH-Z\_A\_So function, Figure 16-17.6 could also be used, except that the FlexOsec process is a null process connecting its output signals to the corresponding input signals. + +**MFAS insertion:** The function shall insert the MFAS into the FlexO basic overhead area in every FlexO instance of the FlexO-x as described in [ITU-T G.709.1]. + +### FlexOsec processes: + +- For M-AI/FlexO-x-GCM-DSH-Z\_A\_So function, see clause 8.14.1 and clause 8.14.3.1 for the specific GCM-AES-256 encryption and authentication processes with the cipher suite type (CST) code point value 000001, as defined in clause B.1 of [ITU-T G.709.1]. The FlexOsec encryption and authentication processes are performed for each individual FlexO instance frame signal in parallel, prior to interleaving into the FlexO-x. The same management information (MI) input from the EMF and Secure Key Information (SKI) input from the key exchange and agreement functions are shared by the $x$ sets of FlexOsec processes. The same key is used by the $x$ sets of FlexOsec source processes which are + +simultaneously triggered by the key exchange and agreement functions (through SKI\_KI input) to switch to a new key. + +- For M-AI/FlexO-*x*-DSH-Z\_A\_So function, this is a null process connecting its output signals to the corresponding input signals. + +**COMMS Clock generation:** For M-AI/FlexO-*x*-GCM-DSH-Z\_A\_So function, the process shall generate SK\_COMMS clock (CK\_COM) by dividing the FlexO clock (CI\_CK) by a factor of 82240. + +**Insert KCC:** The in-band key exchange communication channel (KCC) is optional for M-AI/FlexO-*x*-GCM-DSH-Z\_A\_So function and unused for M-AI/FlexO-*x*-DSH-Z\_A\_So function. When used, the incoming SK\_COMMS\_CI\_D data is inserted after FlexOsec authentication and encryption into the KCC field of the first FlexO instance frame (CI\_D[1]) of the FlexO-*x* as described in clause 9.3.2.5 of [ITU-T G.709.1]. When it is not used, the all-ZEROS reserved value is inserted into the KCC field. + +**Interleaving:** See clause 8.13.1 for the *x* FlexO instance signals interleaving to FlexO-*x*. + +**Alignment insertion:** The function shall insert the alignment marker into the FlexO-*x* frame AM area as described in clause 9.1.1, 9.1.3 or 9.1.5 of [ITU-T G.709.1] for 100G FlexO-1 (*x*=1), 200G FlexO-2 (*x*=2) or 400G FlexO-4 (*x*=4), respectively. + +**Clock generation:** The function shall generate the FlexO-*x*-DSH clock by multiplying the incoming FlexO clock (CI\_CK) by [*x* × 25984/21845] to the frequencies as listed in Table 15-2 of [ITU-T G.709.3] for 100G FlexO-1-DSH (*x*=1), 200G FlexO-2-DSH (*x*=2) or 400G FlexO-4-DSH (*x*=4). The FOIC*x*Z-DSH lane clock is obtained by dividing the FlexO-*x*-DSH clock by a factor *Z*. + +NOTE – The function also generates the intermediate FlexO-*x*-SC clock by multiplying the incoming FlexO clock (CI\_CK) by [*x* × 5485/5140] to the frequencies as listed in Table 11-2, 12-2 or 13-1 of [ITU-T G.709.3] for FlexO-1-SC (*x*=1), FlexO-2-SC (*x*=2) or FlexO-4-SC (*x*=4), respectively. + +**Mapping to -SC frame:** The function shall map (i.e., addition of staircase FEC parity area) the incoming FlexO-*x* frame into the FlexO-*x*-SC frame payload area as defined in clause 11.1, 12.1 or 13-1 of [ITU-T G.709.3] for 100G FlexO-1-SC (*x*=1), 200G FlexO-2-SC (*x*=2) or 400G FlexO-4-SC (*x*=4), respectively. + +**FBS, FBGS and MBS generation:** The function shall generate the staircase (SC) FEC block start (BS) and group start (FBGS) using the incoming FlexO-*x* frame start (FS) to align the Staircase FEC blocks structure with the FlexO-*x*-SC frame structure as described in clause 11.1, 12.1 and 13.1 of [ITU-T G.709.3] for FlexO-1-SC (*x*=1), FlexO-2-SC (*x*=2) or FlexO-4-SC (*x*=4), respectively. An SC FEC block group (FBG) consists of 238 (*x*=1) or 119 (*x*=2 or 4) consecutive FlexO-*x*-SC frame rows that is exactly 10970×119 bits; it contains five SC FEC blocks. In addition, the function shall generate the SC FEC multi-block sequence start every 128 SC FEC blocks, to synchronize the state of the Staircase (SC) FEC Error Decorrelator (ED) as described in clause 11.3.2 (*x*=1), 12.3 (*x*=2), or 13.2 (*x*=4) of [ITU-T G.709.3]. + +**Generate MBAS:** The function shall generate the 6-bit SC FEC multi block alignment signal (MBAS) to be inserted into the FlexO-*x*-SC OH area as described in clause 11.3.2 and Annex C of [ITU-T G.709.3]. + +**Staircase (SC) FEC adapter and encoder:** See clause 8.5.4. + +**Padding:** The function shall add six 119-bit padding blocks (i.e., 714-bit pad) at the end of every FlexO-*x*-SC FBG of 10970×119-bit block as described in clauses 15.4.2 and 15.4.1 of [ITU-T G.709.3]. The extended FBG is a structure consisting in 10976×119-bit blocks. + +**Scrambler:** The function shall scramble the extended FBG as defined in clause 15.4.1 of [ITU-T G.709.3], meaning that all data within the FlexO-*x*-SC frame are scrambled. + +**Convolution Interleaving:** The function shall interleave 119-bit blocks within the extended FBG as defined in clause 15.4.3 of [ITU-T G.709.3]. + +**Hamming FEC mapping and encoder:** See clause 8.5.8. After Hamming FEC mapping and encoding, the extended FBG structure consists of $10976 \times 128$ -bit blocks. + +**DFS, DMFS and DSFS generation:** The function shall generate the FlexO-*x*-DSH frame start (DFS), 49-frame multiframe start (DMFS) and 4-multiframe super-frame start (DSFS) using the incoming extended FEC block group start (FBGS) to synchronize the extended FBG structure after Hamming FEC encoding with the FlexO-*x*-DSH DSP frame structure as described in clause 15.1 of [ITU-T G.709.3]. The FlexO-*x*-DSH frame consists of $(3712 \times Z)$ bits as described in [ITU-T G.709.3] clause 14.1 ( $Z=4$ for $x=1$ or 2; $Z=8$ for $x=2$ or 4). For $Z=8$ a FlexO-*x*-DSH multiframe carries one FBG, while for $Z=4$ a FlexO-*x*-DSH super-frame carries two FBG. + +**Mapping to -DSH frame:** The function shall map the incoming extended FBG signal (carrying the FlexO-*x*-SC signal after padding, scrambling, convolution interleaving and Hamming FEC encoding) into the payload area of the FlexO-*x*-DSH DSP frame signal as defined in clauses 15.4.5.1 ( $Z=8$ for $x=2$ or 4) and 15.4.5.2 ( $Z=4$ for $x=1$ or 2) of [ITU-T G.709.3]. + +**Generate and insert training sequence:** The function shall generate and insert the training sequence into the TS overhead position (11 Z-bit) at the start of the FlexO-*x*-DSH frame as defined in clause 14.2.1 of [ITU-T G.709.3]. + +**Generate and insert pilot sequence:** The function shall generate and insert the pilot sequence into the PS overhead position (Z-bit) at the start of each FlexO-*x*-DSH frame row as defined in clause 14.2.2 of [ITU-T G.709.3]. + +**Generate and insert MFAS:** The function shall generate and insert the DSH 49-frame multiframe alignment signal into the MFAS overhead position (22 Z-bit) in the first FlexO-*x*-DSH frame of each multiframe as defined in clause 15.1.1 of [ITU-T G.709.3]. + +**Generate and insert FS:** The function shall generate and insert the 54 Z-bit fixed stuff into the FS overhead position in the first FlexO-*x*-DSH frame of each 49-frame multiframe as defined in clause 15.3.3 of [ITU-T G.709.3]. + +**Generate and insert SFAS:** The function shall generate and insert the DSH 4-multiframe super-frame alignment signal into the SFAS overhead position (22 Z-bit) in the first FlexO-*x*-DSH frame of each super-frame as defined in clause 15.1.2 of [ITU-T G.709.3]. + +**Lane Distribution:** The function shall divide FlexO-*x*-DSH frame signal into *Z* FOIC*x*-*Z*-DSH logical lanes based on a bit-by-bit distribution as described in clause 15.5.1, 15.5.2, 15.5.3 or 15.5.4 of [ITU-T G.709.3] for FOIC2.4-DSH ( $x=2$ , $Z=4$ ), FOIC2.8-DSH ( $x=2$ , $Z=8$ ), FOIC4.8-DSH ( $x=4$ , $Z=8$ ) or FOIC1.4-DSH ( $x=1$ , $Z=4$ ), respectively. + +Note that the *Z* FOIC*x*-*Z*-DSH logical lanes carry a dual polarization symbol, so that *Z*/2 lanes are to be associated with polarization X, while the other *Z*/2 lanes are to be associated with the polarization Y. The mapping of the *Z* lanes to the dual polarization symbol is specified in clause 15.4.5 of [ITU-T G.709.3]. + +**PMA process:** The process shall map the FOIC*x*-*z*-DSH lanes onto the physical media adapted interface. The details are out of scope of this Recommendation. + +![Block diagram of M-AI/FlexO-x-GCM-DSH-Z_A_So processes showing data flow from inputs through various processing stages to the PMA and OTSi_AP.](9fd6d80e1aab4be30024f5d67f3a4a53_img.jpg) + +The diagram illustrates the internal processing flow of the M-AI/FlexO-x-GCM-DSH-Z\_A\_So processes. At the top, multiple input streams labeled $CI\_D[1], CI\_D[2], \dots, CI\_D[x]$ enter the system. Each stream passes through an **MFAS insertion** block, which outputs $CK, D, FS, MFS$ . These are then processed by **FlexOsec processes**, which also receive $CK\_COM$ from a **COMMS clock generation** block and $D\_COM$ from an **Insert KCC** block. The FlexOsec processes output $D_{sec1}, D_{sec2}, \dots, D_{secx}$ to an **Interleaving** block. The Interleaving block also receives $CK$ from a **FlexO-x clock gen. ( $\times x$ )** block. The interleaved data $D, FS$ goes to an **Alignment insertion** block, which outputs $CK, D, FS$ . This is followed by **Mapping to-SC frame**, which receives $CK\_SC$ from a **FlexO-x-SC clock generation/ ( $\times 5485/5140$ )** block. The mapping block outputs $D, FS$ to an **SC FEC adapter and encoder (FlexO-x-SC)**. This block also receives **MBAS** from a **Generate MBAS** block and **FBGS** from a **BS, MBS and FBGS generator** block. The SC FEC adapter outputs $CK, D, FBGS$ to a **Padding** block, which outputs $D, FBGS$ to a **Scrambler** block, which outputs $D, FBGS$ to a **Convolutional interleaving** block, which outputs $D, FBGS$ to a **Hamming FEC map and encoder** block. This block also receives $CK_{DSH}$ from a **FlexO-x-DSH clock generation/ ( $\times 25984/21845$ )** block and outputs $CK, D, FBGS$ to a **Mapping to-DSH frame and multiframe** block. This mapping block also receives **DFS, DMFS** from a **DFS, DMFS and DSFS generator** block and outputs $D, CK_{DSH}, DFS, DMFS$ to a **Lane distribution (for symbol/Pol. distribution)** block. The lane distribution block also receives $CK_L$ from a **FlexO-x-Z-DSH clock generation/ ( $\times 1/Z$ )** block. The lane distribution block outputs $D[1..Z], CK_L, DFS, DMFS$ to a **PMA** block. The PMA block is connected to an **M-AP** block, which outputs $AI\_D[1], \dots, AI\_D[Z]$ to an **OTSi\_AP** block. Various other blocks generate specific sequences: **Generate and insert training sequence** (DFS), **Generate and insert pilot sequence** (DFS), **Generate and insert MFAS** (DMFS), **Generate and insert fixed Stuff** (DMFS), and **Generate and insert SFAS** (SMFS). These are also inputs to the lane distribution block. The diagram also includes labels for **SK\\_COMMS\\_CP**, **SKI\\_Key[0,1,2,3]**, **SKI\\_KI**, **SKI\\_IV\\_Fixed\\_ID**, and **FOIC1.4-DSH ( $x=1, Z=4$ )**, **FOIC2.4-DSH ( $x=2, Z=4$ )**, **FOIC2.8-DSH ( $x=2, Z=8$ )**, and **FOIC4.8-DSH ( $x=4, Z=8$ )**. A vertical label on the right side reads **M-AI/FlexO-1-GCM-DSH-Z\_A\_So\_SKP**. The bottom right corner contains the text **G.798(17)-Amd.4(22)\_F16-17.6**. + +Block diagram of M-AI/FlexO-x-GCM-DSH-Z\_A\_So processes showing data flow from inputs through various processing stages to the PMA and OTSi\_AP. + +Figure 16-17.6 – M-AI/FlexO-x-GCM-DSH-Z\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 16.7.4 OTSi to FlexO-x-DSH adaptation sink functions (M-AI/FlexO-x-DSH-Z\_A\_Sk and M-AI/FlexO-x-GCM-DSH-Z\_A\_Sk) + +The information flow and processing of the M-AI/FlexO-x-DSH-Z\_A\_Sk and M-AI/FlexO-x-GCM-DSH-Z\_A\_Sk functions ( $\{x,Z\}=\{1,4\}, \{2,4\}, \{2,8\}, \{4,8\}$ ) is defined with reference to Figures 16-17.7 and 16-17.8. The interfaces of these functions are defined in Table 16-14.4. + +##### Symbol + +![Diagram showing two adaptation sink function symbols. The left symbol is 'M-AI/FlexO-x-DSH-Z' with inputs 'OTSi_AP' and 'M-AP[1..Z]' (via a dashed oval) and output 'FlexO-x_CP'. It has a bidirectional interface 'M-AI/FlexO-x-DSH-Z_A_Sk_MP'. The right symbol is 'M-AI/FlexO-x-GCM-DSH-Z' with inputs 'OTSi_AP' and 'M-AP[1..Z]' (via a dashed oval) and outputs 'FlexO-x_CP' and 'SK_COMMS_CP'. It has bidirectional interfaces 'M-AI/FlexO-x-GCM-DSH-Z_A_Sk_MP' and 'M-AI/FlexO-x-GCM-DSH-Z_A_Sk_SKP'. A reference code 'G.798(17)-Amd.4(22)_F16-17.7' is at the bottom right.](82a7d47fd0aee910d598c30998c23e08_img.jpg) + +G.798(17)-Amd.4(22)\_F16-17.7 + +Diagram showing two adaptation sink function symbols. The left symbol is 'M-AI/FlexO-x-DSH-Z' with inputs 'OTSi\_AP' and 'M-AP[1..Z]' (via a dashed oval) and output 'FlexO-x\_CP'. It has a bidirectional interface 'M-AI/FlexO-x-DSH-Z\_A\_Sk\_MP'. The right symbol is 'M-AI/FlexO-x-GCM-DSH-Z' with inputs 'OTSi\_AP' and 'M-AP[1..Z]' (via a dashed oval) and outputs 'FlexO-x\_CP' and 'SK\_COMMS\_CP'. It has bidirectional interfaces 'M-AI/FlexO-x-GCM-DSH-Z\_A\_Sk\_MP' and 'M-AI/FlexO-x-GCM-DSH-Z\_A\_Sk\_SKP'. A reference code 'G.798(17)-Amd.4(22)\_F16-17.7' is at the bottom right. + +**Figure 16-17.7 – M-AI/FlexO-x-DSH-Z\_A\_Sk and M-AI/FlexO-x-GCM-DSH-Z\_A\_Sk functions ( $\{x,Z\}=\{1,4\}, \{2,4\}, \{2,8\}, \{4,8\}$ )** + +## Interfaces + +**Table 16-14.4 – M-AI/FlexO-*x*-DSH-Z\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| M_AP:
M-AI_D[1..Z]
OTSiG-O_AP:
OTSiA_AI_TSF-O
OTSiA_AI_TSF-P
M-AI/FlexO-x-DSH-Z_A_Sk_MP:
M-AI/FlexO- x -DSH-Z_A_Sk_MI_1second
M-AI/FlexO- x -DSH-Z_A_Sk_MI_SquelchEn (Note)
M-AI/FlexO-x-GCM-DSH_A_Sk_SKP: (Note)
M-AI/FlexO- x -GCM-DSH-Z_A_Sk_SKI_Key[0,1,2,3]
M-AI/FlexO- x -GCM-DSH-Z_A_Sk_SKI_IV_Fixed_ID | FlexO-x_CP:
FlexO- x _CI_CK
FlexO- x _CI_D[1.. x ]
FlexO- x _CI_FS
FlexO- x _CI_MFS
FlexO- x _CI_SSF
M-AI/FlexO-x-DSH-Z_A_Sk_MP:
M-AI/FlexO- x -DSH-Z_A_Sk_MI_AcCST[1.. x ] (Note)
M-AI/FlexO- x -DSH-Z_A_Sk_MI_cLOS-P
M-AI/FlexO- x -DSH-Z_A_Sk_MI_cLOL
M-AI/FlexO- x -DSH-Z_A_Sk_MI_cLOF
M-AI/FlexO- x -DSH-Z_A_Sk_MI_cLOM
M-AI/FlexO- x -DSH-Z_A_Sk_MI_cCSTM (Note)
M-AI/FlexO- x -DSH-Z_A_Sk_MI_cUnlockSec (Note)
M-AI/FlexO- x -DSH-Z_A_Sk_MI_pFECcorrErr
M-AI/FlexO- x -DSH-Z_A_Sk_MI_pAuthCheckErr (Note)
M-AI/FlexO-x-GCM-DSH_A_Sk_SKP: (Note)
M-AI/FlexO- x -GCM- DSH-Z_A_Sk_SKI_AcKI
SK_COMMS_CP: (Note)
SK_COMMS_CI_D
SK_COMMS_CI_CK | +| NOTE – For OTSiG/FlexO- x -GCM-DSH-Z_A_Sk only. | | + +## Processes + +The processes associated with the M-AI/FlexO-*x*-GCM-DSH-Z\_A\_Sk function are as depicted in Figure 6-17.8. For the M-AI/FlexO-*x*-DSH-Z\_A\_Sk function, Figure 16-17.8 could also be used, except that the FlexOsec process is a null process connecting its output signals to the corresponding input signals. + +**PMA process:** The process shall recover the data and clock of the FOIC $x$ .Z-DSH lanes from the physical media adapted interface. The details are out of scope of this Recommendation. + +**Recombination:** The function shall recombine the *Z* FOIC $x$ .Z-DSH logical lanes and reconstruct the FlexO-*x*-DSH frame and Hamming FEC codewords soft signal for FOIC2.4-DSH (*x*=2, *Z*=4), FOIC2.8-DSH (*x*=2, *Z*=8), FOIC4.8-DSH (*x*=4, *Z*=8) or FOIC1.4-DSH (*x*=1, *Z*=4), respectively. + +**Demapping from-DSH frame and multiframe:** The function shall demap the extended FBG signal structure (carrying the padded, scrambled, interleaved and Hamming FEC encoded FlexO-*x*-SC signal) from the payload area of the FlexO-*x*-DSH DSP frame signal as defined in clause 15.4.5.1 (*Z*=8 for *x*=2 or 4) and 15.4.5.2 (*Z*=4 for *x*=1 or 2) of [ITU-T G.709.3]. It shall generate the FBGS block start indication derived from the FlexO-*x*-DSH multiframe and superframe start indication. + +**Soft decision Hamming FEC decoder and demapping:** See clause 8.5.8 for the soft decision extended Hamming decoder. After Hamming FEC decoding and demapping, the extended FBG structure consists of 10976×119-bit blocks. + +**Convolution deinterleaving:** The function shall deinterleave the 119-bit blocks within the extended FBG as defined in clause 15.4.3 of [ITU-T G.709.3]. + +**Descrambler:** The function shall descramble the extended FBG as defined in clause 15.4.1 of [ITU-T G.709.3], resulting into the unscrambled FlexO-*x*-SC frame. + +**Unpadding:** The function shall remove the six 119-bit padding blocks (i.e., 714-bit pad) from the end of every extended FlexO-*x*-SC FBG structure of 10976×119-bit block as described in clauses 15.4.2 and 15.4.1 of [ITU-T G.709]. The resulting FBG structure consists in 10970×119-bit blocks. + +**Staircase (SC) FEC decoder and adapter:** See clause 8.5.4. + +NOTE – In this process, the Multi Block Alignment Signal (MBAS) overhead is extracted from FlexO-*x*-SC overhead as described in clause B.2 (*x*=1) or C.2 (*x*=2 or 4) of [ITU-T G.709.3] and MBAS sequence is aligned to synchronize SC FEC Error Decorrelator (ED). + +**SC-frame demapping:** The function shall demap (i.e., removal of staircase SC FEC parity area) the FlexO-*x* frame from the incoming FlexO-*x*-SC frame as defined in clause 11.1, 12.1 or 13-1 of [ITU-T G.709.3] for 100G FlexO-1-SC (*x*=1), 200G FlexO-2-SC (*x*=2) or 400G FlexO-4-SC (*x*=4), respectively. + +**FlexO-*x* frame alignment:** See clause 8.2.8. + +**De-interleaving:** See clause 8.13.2. + +**Extract and replace KCC:** The in-band key exchange communication channel (KCC) is optional in M-AI/FlexO-*x*-GCM-DSH-Z\_A\_Sk and unused in M-AI/FlexO-*x*-DSH-Z\_A\_Sk function. When used, the function shall extract the KCC data (SK\_COMMS\_CI\_D) from the FlexOsec KCC overhead field of the first FlexO instance frame of the FlexO-*x* as described in clause 9.2.8 of [ITU-T G.709.1]. The bit rate of the KCC data is defined by the outgoing KCC clock. The function shall generate the KCC clock (SK\_COMMS\_CI\_CK) by dividing the FlexO-*x* clock by a factor of 82240. After extraction, the KCC byte in the FlexOsec overhead is replaced with value 0x00 at the input of the FlexOsec sink processes. + +**FlexOsec processes:** + +- For M-AI/FlexO-*x*-GCM-DSH-Z\_A\_Sk function, see clause 8.14.2 and clause 8.14.3.1 for the specific GCM-AES-256 decryption and authentication processes with the cipher suite type (CST) code point value 000001, as defined in clause B.1 of [ITU-T G.709.1]. The FlexOsec decryption and authentication processes are performed for each individual FlexO instance frame signal in parallel, after to deinterleaving from FlexO-*x*. The same management information (MI) input from the EMF and Secure Key Information (SKI) input from the key exchange and agreement functions are shared by the *x* sets of FlexOsec processes. The same sets of keys are configured to be used by the *x* sets of FlexOsec sink processes. +- For M-AI/FlexO-*x*-DSH-Z\_A\_Sk function, this is a null process connecting its output signals to the corresponding input signals. + +**Multiframe alignment:** The process shall recover the FlexO multi-frame start as described in clause 8.2.2. + +![Figure 16-17.8 – M-AI/FlexO-x-GCM-DSH-Z_A_Sk processes. This is a complex block diagram showing the signal processing flow for FlexO-x interfaces. At the bottom, multiple FlexO-x interfaces (FOIC1.4-DSH, FOIC2.4-DSH, FOIC2.8-DSH, FOIC4.8-DSH) are shown with their respective Z values. These connect to a PMA block, which outputs dLOL and dLOS-P signals. Above the PMA is a 'Lane recombination (from Pol/symbol)' block. The signal then passes through a series of processing stages: 'Demapping from-DSH frame and multiframe', 'Soft decision hamming FEC decoder and demap', 'Convolutional deinterleaving', 'Descrambler', 'Unpadding', 'SC FEC adapter and decoder (FlexO-x-SC)', 'Demapping from-SC frame', and 'FlexO-x frame alignment'. This stage outputs dLOF. The signal then enters a 'De-interleaving' block. Above this, there are multiple 'FlexOsec processes' (labeled 1, 2, ..., x). Each process includes 'Multiframe alignment' (outputting dLOM[1], dLOM[2], ..., dLOM[x]) and 'FlexOsec processes' blocks. These blocks output various signals including AuthCheckErr[j], dUnlockSec[j], dLOL, MI_SquelchEn, AcCST[j], SKI_Key[0,1,2,3], SKI_IV_Fixed_ID, and SKI_AcKII[j]. A 'Replace and extract KCC' block is also shown. On the right side, there are 'Performance monitoring' and 'Defect correlation' blocks that receive inputs from the FlexOsec processes and output MI signals like MI_pAuthcheckErr, MI_lsecond, MI_pFECorrErr, MI_cCSTM, MI_cUnlockSec, MI_cLOM, MI_cLOF, MI_cLOL, and MI_cLOS-P. The top of the diagram shows the SK_COMM_CP and FlexO-x_CP (x = 1, 2 or 4) interfaces with signals like D_COM, CK_COM, CL_SK_D, CL_SK_CK, CL_D[1], CL_CK, CL_FS, CL_MFS, CL_D[2], ..., CL_D[x], and CL_SSF. Vertical labels on the far right identify the sections as 'M-AI/FlexO-x-GCM-DSH-Z_A_Sk_SKP' and 'M-AI/FlexO-x-GCM-DSH-Z_A_Sk_MP'. The diagram is labeled G.798(23)_F16-17.8 at the bottom right.](9f1b05b6b77146b0d62dbc084ebbe162_img.jpg) + +Figure 16-17.8 – M-AI/FlexO-x-GCM-DSH-Z\_A\_Sk processes. This is a complex block diagram showing the signal processing flow for FlexO-x interfaces. At the bottom, multiple FlexO-x interfaces (FOIC1.4-DSH, FOIC2.4-DSH, FOIC2.8-DSH, FOIC4.8-DSH) are shown with their respective Z values. These connect to a PMA block, which outputs dLOL and dLOS-P signals. Above the PMA is a 'Lane recombination (from Pol/symbol)' block. The signal then passes through a series of processing stages: 'Demapping from-DSH frame and multiframe', 'Soft decision hamming FEC decoder and demap', 'Convolutional deinterleaving', 'Descrambler', 'Unpadding', 'SC FEC adapter and decoder (FlexO-x-SC)', 'Demapping from-SC frame', and 'FlexO-x frame alignment'. This stage outputs dLOF. The signal then enters a 'De-interleaving' block. Above this, there are multiple 'FlexOsec processes' (labeled 1, 2, ..., x). Each process includes 'Multiframe alignment' (outputting dLOM[1], dLOM[2], ..., dLOM[x]) and 'FlexOsec processes' blocks. These blocks output various signals including AuthCheckErr[j], dUnlockSec[j], dLOL, MI\_SquelchEn, AcCST[j], SKI\_Key[0,1,2,3], SKI\_IV\_Fixed\_ID, and SKI\_AcKII[j]. A 'Replace and extract KCC' block is also shown. On the right side, there are 'Performance monitoring' and 'Defect correlation' blocks that receive inputs from the FlexOsec processes and output MI signals like MI\_pAuthcheckErr, MI\_lsecond, MI\_pFECorrErr, MI\_cCSTM, MI\_cUnlockSec, MI\_cLOM, MI\_cLOF, MI\_cLOL, and MI\_cLOS-P. The top of the diagram shows the SK\_COMM\_CP and FlexO-x\_CP (x = 1, 2 or 4) interfaces with signals like D\_COM, CK\_COM, CL\_SK\_D, CL\_SK\_CK, CL\_D[1], CL\_CK, CL\_FS, CL\_MFS, CL\_D[2], ..., CL\_D[x], and CL\_SSF. Vertical labels on the far right identify the sections as 'M-AI/FlexO-x-GCM-DSH-Z\_A\_Sk\_SKP' and 'M-AI/FlexO-x-GCM-DSH-Z\_A\_Sk\_MP'. The diagram is labeled G.798(23)\_F16-17.8 at the bottom right. + +**Figure 16-17.8 – M-AI/FlexO-x-GCM-DSH-Z\_A\_Sk processes** + +## Defects + +The function shall detect dLOS-P, dLOL, dLOF, dCSTM, dUnlockSec[j] and dLOM[j]. + +**dLOS-P:** See clause 6.2.1.2. + +**dLOL:** dLOL is generated for FlexO-x-DSH interfaces based on the pilot symbols, DSP frame and DSP multiframe alignment. dLOL shall be declared if alignment is false for 3 ms. To provide for the + +case of intermittent out-of-alignment, the integrating timer shall not be reset to zero until an alignment condition persists continuously for 3 ms. dLOL shall be cleared if alignment is true for 3 ms. + +**dLOF:** See clause 6.2.5.1. + +**dCSTM:** See clause 6.2.11. The expected cipher suite type is "0000 0001". Set to false for M-AI/FlexO-*x*-DSH-Z\_Sk function without FlexOsec. + +Per FlexO instance #*j* detection (*j* = 1..*x*): + +**dLOM[*j*]:** See clause 6.2.5.2. + +**dUnlockSec[*j*]:** See clause 6.2.7.2.1. Set to false for M-AI/FlexO-*x*-DSH-Z\_Sk function without FlexOsec. + +### Consequent actions + +aSSF $\leftarrow \sum dLOM[j] \text{ or } \sum dUnlockSec[j] \text{ or } dCSTM \text{ or } dLOF \text{ or } \sum dLOS-P[i] \text{ or } dLOL \text{ or } AI\_TSF-P$ + +### Defect correlations + +cLOS-P $\leftarrow dLOS-P \text{ and (not } AI\_TSF-P)$ + +cLOL $\leftarrow dLOL \text{ and (not } dLOS-P) \text{ and (not } AI\_TSF-P)$ + +cLOF $\leftarrow dLOF \text{ and (not } dLOL) \text{ and (not } AI\_TSF-P)$ + +cCSTM $\leftarrow dCSTM \text{ and (not } dLOF) \text{ and (not } dLOL) \text{ and (not } AI\_TSF-P)$ + +cUnlockSec $\leftarrow \sum dUnlockSec[j] \text{ and (not } dCSTM) \text{ and (not } dLOF) \text{ and (not } dLOL) \text{ and (not } AI\_TSF-P)$ + +cLOM $\leftarrow \sum dLOM[j] \text{ and (not } dCSTM) \text{ and (not } dLOF) \text{ and (not } dLOL) \text{ and (not } AI\_TSF-P)$ + +### Performance monitoring + +The function shall perform the following performance monitoring primitives processing. The performance monitoring primitives shall be reported to the equipment management function (EMF). + +pFECcorrErr $\leftarrow \sum nFECcorrErr$ + +pAuthcheckErr $\leftarrow \sum AuthcheckErr$ + +NOTE – During AI\_TSF-P, $\sum dUnlockSec[j]$ and dLOL, no corrected bits or authentication failure shall be counted. + +### 16.7.5 OTSi to FlexO-*x*-DO adaptation source functions (M-AI/FlexO-*x*-DO-Z\_A\_So and M-AI/FlexO-*x*-GCM-DO-Z\_A\_So) + +The information flow and processing of the M-AI/FlexO-*x*-DO-Z\_A\_So and M-AI/FlexO-*x*-GCM-DO-Z\_A\_So functions ( $\{x, Z\} = \{1, 4\}, \{2, 4\}, \{2, 8\}, \{4, 8\}$ ) is defined with reference to Figures 16-17.9 and 16-17.10. The interfaces of these functions are defined in Table 16-14.5. + +## Symbol + +![Diagram showing the symbols for M-AI/FlexO-x-DO-Z_A_So and M-AI/FlexO-x-GCM-DO-Z_A_So functions. The left symbol for M-AI/FlexO-x-DO-Z takes FlexO-x_CP (x = 1, 2, 4) as input and produces M-AP[1..Z] and OTSi_AP as outputs. The right symbol for M-AI/FlexO-x-GCM-DO-Z takes FlexO-x_CP (x = 1, 2, 4), SK_COMMS_CP, and M-AI/FlexO-x-GCM-DO-Z_A_So_SKP as inputs and produces M-AP[1..Z] and OTSi_AP as outputs. A note G.798(17)-Amd.4(22)_F16-17.9 is present.](c8b66b38ad7369d0771b91b51c155b32_img.jpg) + +Diagram showing the symbols for M-AI/FlexO-x-DO-Z\_A\_So and M-AI/FlexO-x-GCM-DO-Z\_A\_So functions. The left symbol for M-AI/FlexO-x-DO-Z takes FlexO-x\_CP (x = 1, 2, 4) as input and produces M-AP[1..Z] and OTSi\_AP as outputs. The right symbol for M-AI/FlexO-x-GCM-DO-Z takes FlexO-x\_CP (x = 1, 2, 4), SK\_COMMS\_CP, and M-AI/FlexO-x-GCM-DO-Z\_A\_So\_SKP as inputs and produces M-AP[1..Z] and OTSi\_AP as outputs. A note G.798(17)-Amd.4(22)\_F16-17.9 is present. + +**Figure 16-17.9 – M-AI/FlexO-x-DO-Z\_A\_So and M-AI/FlexO-x-GCM-DO-Z\_A\_So functions** + $(\{x,Z\}=\{1,4\}, \{2,4\}, \{2,8\}, \{4,8\})$ + +## Interfaces + +**Table 16-14.5 – M-AI/FlexO-x-DO-Z\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------| +| FlexO-x_CP :
FlexO-x_CI_CK
FlexO-x_CI_D[1..x]
FlexO-x_CI_FS
FlexO-x_CI_MFS
M-AI/FlexO-x-GCM-DO-Z_A_So_SKP: (Note)
M-AI/FlexO-x-GCM-DO-Z_A_So_SKI_Key[0,1,2,3]
M-AI/FlexO-x-GCM-DO-Z_A_So_SKI_KI
M-AI/FlexO-x-GCM-DO-Z_A_So_SKI_IV_Fixed_ID
SK_COMMS_CP: (Note)
SK_COMMS_CI_D | M_AP:
M-AI_D[1..Z]
SK_COMMS_CP: (Note)
SK_COMMS_CI_CK | +| NOTE – For OTSiG/FlexO-x-GCM-DO-Z_A_So only. | | + +## Processes + +The processes associated with the M-AI/FlexO-x-GCM-DO-Z\_A\_So function are as depicted in Figure 16-17.10. For the M-AI/FlexO-x-DO-Z\_A\_So function, Figure 16-17.10 could also be used, except that the FlexOsec process is a null process connecting its output signals to the corresponding input signals. + +**MFAS insertion:** The function shall insert the MFAS into the FlexO basic overhead area in every FlexO instance of the FlexO-x as described in [ITU-T G.709.1]. + +### FlexOsec processes: + +- For M-AI/FlexO-x-GCM-DO-Z\_A\_So function, see clause 8.14.1 and clause 8.14.3.1 for the specific GCM-AES-256 encryption and authentication processes with the cipher suite type (CST) code point value 000001, as defined in clause B.1 of [ITU-T G.709.1]. The FlexOsec encryption and authentication processes are performed for each individual FlexO instance frame signal in parallel, prior to interleaving into the FlexO-x. The same management information (MI) input from the EMF and Secure Key Information (SKI) input from the key exchange and agreement functions are shared by the $x$ sets of FlexOsec processes. The same key is used by the $x$ sets of FlexOsec source processes which are simultaneously triggered by the key exchange and agreement functions (through SKI\_KI input) to switch to a new key. + +– For M-AI/FlexO-*x*-DO-Z\_A\_So function, this is a null process connecting its output signals to the corresponding input signals. + +**COMMS Clock generation:** For M-AI/FlexO-*x*-GCM-DO-Z\_A\_So function, the process shall generate SK\_COMMS clock (CK\_COM) by dividing the FlexO clock (CI\_CK) by a factor of 82240. + +**Insert KCC:** The in-band key exchange communication channel (KCC) is optional for M-AI/FlexO-*x*-GCM-DO-Z\_A\_So function and unused for M-AI/FlexO-*x*-DO-Z\_A\_So function. When used, the incoming SK\_COMMS\_CI\_D data is inserted after FlexOsec authentication and encryption into the KCC field of the first FlexO instance frame (CI\_D[1]) of the FlexO-*x* as described in clause 9.3.2.5 of [ITU-T G.709.1]. When it is not used, the all-ZEROS reserved value is inserted into the KCC field + +**Interleaving:** See clause 8.13.1 for the *x* FlexO instance signals interleaving to FlexO-*x*. + +**Alignment insertion:** The function shall insert the alignment marker into the FlexO-*x* frame AM area as described in clause 9.1.1, 9.1.3 or 9.1.5 of [ITU-T G.709.1] for 100G FlexO-1 (*x*=1), 200G FlexO-2 (*x*=2) or 400G FlexO-4 (*x*=4), respectively. + +**Clock generation:** The function shall generate the FlexO-*x*-DO clock by multiplying the incoming FlexO clock (CI\_CK) by [*x*× 1536/1285] to the frequencies as listed in Table 16-2 of [ITU-T G.709.3] for 100G FlexO-1-DO (*x*=1), 200G FlexO-2-DO (*x*=2) or 400G FlexO-4-DO (*x*=4). The FOIC*x*-Z-DO lane clock is obtained by dividing the FlexO-*x*-DO clock by a factor *Z*. + +**OFBGS and OFCS generation:** The function shall generate the open FEC block group start of order *Z* (OFBG*Z*S, with *Z*=4 or 8) providing the OFEC coders alignment (OFCi) using the incoming FlexO-*x* frame start (FS) to align the OFBG*Z* structure with the FlexO-*x* frame structure as described in clause 16.4.1 of [ITU-T G.709.3]. An OFEC block group (OFBG*Z*) is aligned with 116 consecutive FlexO-*x* frame rows ( $\{x,Z\}=\{4,8\}$ , $\{2,8\}$ or $\{1,4\}$ ) or 58 consecutive FlexO-*x* frame rows ( $\{x,Z\}=\{2,4\}$ ). It contains exactly 149184×*Z* bits data. For $\{x,Z\}=\{4,8\}$ or $\{x,Z\}=\{2,8\}$ , it corresponds to 10280×116 bits of FlexO-*x* data plus 992-bit pad and contains 168 OFEC coder blocks (OFCs). For $\{x,Z\}=\{2,4\}$ or $\{x,Z\}=\{1,4\}$ , it corresponds to 10280×58 or 5140×116 bits of FlexO-*x* data plus 496-bit pad and contains 84 OFEC coder blocks (OFCs). + +**Padding:** For $\{x,Z\}=\{4,8\}$ or $\{x,Z\}=\{2,8\}$ , the function shall add 992-bit pad at the end of every set of 116 FlexO-*x* rows to create an OFBG8 of 149184× 8-bit data (*Z*= 8) as described in clause 16.4.1 of [ITU-T G.709.3]. For $\{x,Z\}=\{2,4\}$ or $\{x,Z\}=\{1,4\}$ , the function shall add 496-bit pad at the end of every set of 116 FlexO-1 rows or 58 FlexO-2 rows to create an OFBG4 of 149184× 4-bit data (*Z*=4) as described in clause 16.4.1 of [ITU-T G.709.3]. + +**Scrambler:** The function shall scramble the OFBG*Z* as defined in clause 16.4.2 of [ITU-T G.709.3], meaning that all data within the FlexO-*x* frame are scrambled. + +**FEC mapping and encoder:** See clause 8.5.9. After OFEC mapping and encoding, the OFBG*Z*P structure (OFBG*Z* plus OFEC parity bits) consists of 172032×*Z*-bit blocks. + +**Interleaving:** The function shall interleave the bits within the OFBG*Z*P as defined in clause 16.4.5 of [ITU-T G.709.3]. + +**DFS and DMFS generation:** The function shall generate the FlexO-*x*-DO frame start (DFS) and 48-frame multiframe start (DMFS) using the incoming OFEC block group start (OFBGS) to synchronize the OFBG*Z*P structure after OFEC encoding with the FlexO-*x*-DO DSP frame structure as described in clauses 16.1 of [ITU-T G.709.3]. The FlexO-*x*-DO frame consists of (3712×*Z*) bits as described in [ITU-T G.709.3] clause 14.1 (*Z*=4 for *x*=1 or 2; *Z*=8 for *x*=2 or 4). A FlexO-*x*-DO multiframe carries one OFBG*Z*P. + +**Mapping to -DO frame:** The function shall map the incoming OFBG*Z*P signal (carrying the FlexO-*x* signal after padding, scrambling, OFEC encoding and interleaving) into the payload area of the FlexO-*x*-DO DSP frame signal as defined in clause 16.4.6.1 (*Z*=8 for *x*=2 or 4) and 15.4.6.2 (*Z*=4 for *x*=1 or 2) of [ITU-T G.709.3]. + +**Generate and insert training sequence:** The function shall generate and insert the training sequence into the TS overhead position (11 Z-bit) at the start of the FlexO-*x*-DO frame as defined in clause 14.2.1 of [ITU-T G.709.3]. + +**Generate and insert pilot sequence:** The function shall generate and insert the pilot sequence into the PS overhead position (Z-bit) at the start of each FlexO-*x*-DO frame row as defined in clause 14.2.2 of [ITU-T G.709.3]. + +**Generate and insert MFAS:** The function shall generate and insert the DO 48-frame multiframe alignment signal into the MFAS overhead position (22 Z-bit) in the first FlexO-*x*-DO frame of each multiframe as defined in clauses 16.1.1 and 16.3.1 of [ITU-T G.709.3]. + +**Generate and insert FS:** The function shall generate and insert the 54 Z-bit fixed stuff into the FS overhead position in the first FlexO-*x*-DO frame of each 49-frame multiframe as defined in clause 16.3.2 of [ITU-T G.709.3]. + +**Lane Distribution:** The function shall divide FlexO-*x*-DO frame signal into Z FOIC*x*-Z-DO logical lanes based on a bit-by-bit distribution as described in clause 16.5.1, 16.5.2, 16.5.3 or 16.5.4 of [ITU-T G.709.3] for FOIC2.4-DO (*x*=2, Z=4), FOIC2.8-DO (*x*=2, Z=8), FOIC4.8-DO (*x*=4, Z=8) or FOIC1.4-DO (*x*=1, Z=4), respectively. + +Note that the Z FOIC*x*-Z-DO logical lanes carry a dual polarization symbol, so that Z/2 lanes are to be associated with polarization X, while the other Z/2 lanes are to be associated with the polarization Y. The mapping of the Z lanes to the dual polarization symbol is specified in clause 16.4.6 of [ITU-T G.709.3]. + +**PMA process:** The process shall map the FOIC*x*-Z-DO lanes onto the physical media adapted interface. The details are out of scope of this Recommendation. + +![Block diagram of M-AI/FlexO-x-GCM-DO-Z_A_So processes showing data flow from FlexO-x_CP inputs through various processing stages (MFAS insertion, FlexOsec Processes, Interleaving, Alignment Insertion, padding, Scrambler, FEC map and encoder, Interleaving, Mapping to -DO frame & multiframe) to a PMA and finally to OTSi_AP outputs. The diagram includes clock generation blocks, sequence insertion blocks, and configuration parameters like SKI_Key, FOICx.Z-DO clock generation, and lane distribution.](d3581354fc6f1b5e27d3c990e41cc805_img.jpg) + +The diagram illustrates the M-AI/FlexO-x-GCM-DO-Z\_A\_So processes. At the top, FlexO-x\_CP (x=1, 2 or 4) inputs (CI\_CK, CI\_D[1], CI\_FS, CI\_MFS, CI\_D[2], ..., CI\_D[x]) are processed through MFAS insertion and FlexOsec Processes. SK\_COMMS\_CP inputs (CI\_CK, CI\_D) are also processed. The data from FlexOsec Processes is interleaved and then processed through Alignment Insertion, padding, Scrambler, FEC map and encoder, and another Interleaving stage. The data is then mapped to -DO frame & multiframe. Various sequences are generated and inserted: Training Sequence (DFS), Pilot Sequence (DFS), MFAS (DMFS), and Fixed Stuff (DMFS). Clock signals (CK, CK\_com, CK\_o, CK\_DO, CK\_DSH) are generated and distributed throughout the process. The final data is sent to the PMA, which outputs to the OTSi\_AP (AI\_D[1], ..., AI\_D[Z]). + +Configuration parameters and labels include: + +- SKI\_Key[0,1,2,3] +- SKI\_KI +- SKI\_IV\_Fixed\_ID +- M-AI/FlexO-x-DO-Z\_A\_So\_SKP +- FOIC1.4-DO (x=1, Z=4) +- FOIC2.4-DO (x=2, Z=4) +- FOIC2.8-DO (x=2, Z=8) +- FOIC4.8-DO (x=4, Z=8) + +Block diagram of M-AI/FlexO-x-GCM-DO-Z\_A\_So processes showing data flow from FlexO-x\_CP inputs through various processing stages (MFAS insertion, FlexOsec Processes, Interleaving, Alignment Insertion, padding, Scrambler, FEC map and encoder, Interleaving, Mapping to -DO frame & multiframe) to a PMA and finally to OTSi\_AP outputs. The diagram includes clock generation blocks, sequence insertion blocks, and configuration parameters like SKI\_Key, FOICx.Z-DO clock generation, and lane distribution. + +Figure 16-17.10 – M-AI/FlexO-x-GCM-DO-Z\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 16.7.6 OTSi to FlexO-x-DO adaptation sink functions (M-AI/FlexO-x-DO-Z\_A\_Sk and M-AI/FlexO-x-GCM-DO-Z\_A\_Sk) + +The information flow and processing of the M-AI/FlexO-x-DO-Z\_A\_Sk and M-AI/FlexO-x-GCM-DO-Z\_A\_Sk functions ( $\{x,Z\}=\{1,4\}, \{2,4\}, \{2,8\}, \{4,8\}$ ) is defined with reference to Figures 16-17.11 and 16-17.12. The interfaces of these functions are defined in Table 16-14.6. + +#### Symbol + +![Diagram showing the symbols for M-AI/FlexO-x-DO-Z and M-AI/FlexO-x-GCM-DO-Z functions. The left symbol for M-AI/FlexO-x-DO-Z has an input OTSi_AP at the bottom, an output FlexO-x_CP at the top, and a bidirectional interface M-AI/FlexO-x-DO-Z_A_Sk_MP on the left. A dashed oval labeled M-AP[1..Z] is inside. The right symbol for M-AI/FlexO-x-GCM-DO-Z has an input OTSi_AP at the bottom, outputs FlexO-x_CP and SK_COMMS_CP at the top, a bidirectional interface M-AI/FlexO-x-GCM-DO-Z_A_Sk_MP on the left, and an output M-AI/FlexO-x-GCM-DO-Z_A_Sk_SKP on the right. It also has a dashed oval labeled M-AP[1..Z] inside. A small text 'G.798(17)-Amd.4(22)_F16-17.11' is at the bottom right.](a6a834290f84822c2d026a3da95617c5_img.jpg) + +G.798(17)-Amd.4(22)\_F16-17.11 + +Diagram showing the symbols for M-AI/FlexO-x-DO-Z and M-AI/FlexO-x-GCM-DO-Z functions. The left symbol for M-AI/FlexO-x-DO-Z has an input OTSi\_AP at the bottom, an output FlexO-x\_CP at the top, and a bidirectional interface M-AI/FlexO-x-DO-Z\_A\_Sk\_MP on the left. A dashed oval labeled M-AP[1..Z] is inside. The right symbol for M-AI/FlexO-x-GCM-DO-Z has an input OTSi\_AP at the bottom, outputs FlexO-x\_CP and SK\_COMMS\_CP at the top, a bidirectional interface M-AI/FlexO-x-GCM-DO-Z\_A\_Sk\_MP on the left, and an output M-AI/FlexO-x-GCM-DO-Z\_A\_Sk\_SKP on the right. It also has a dashed oval labeled M-AP[1..Z] inside. A small text 'G.798(17)-Amd.4(22)\_F16-17.11' is at the bottom right. + +**Figure 16-17.11 – M-AI/FlexO-x-DO-Z\_A\_Sk and M-AI/FlexO-x-GCM-DO-Z\_A\_Sk functions ( $\{x,Z\}=\{1,4\}, \{2,4\}, \{2,8\}, \{4,8\}$ )** + +## Interfaces + +**Table 16-14.6– M-AI/FlexO-*x*-DO-*Z* *A\_Sk* inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| M_AP:
M-AI_D[1.. Z ]
OTSiG-O_AP:
OTSiA_AI_TSF-O
OTSiA_AI_TSF-P
M-AI/FlexO-x-DO-Z A_Sk_MP:
M-AI/FlexO- x -DO- Z A_Sk _MI_1second
M-AI/FlexO- x -DO- Z A_Sk _MI_SquelchEn (Note)
M-AI/FlexO-x-GCM-DO A_Sk SKP: (Note)
M-AI/FlexO- x -GCM-DO- Z A_Sk _SKI_Key[0,1,2,3]
M-AI/FlexO- x -GCM-DO- Z A_Sk _SKI_IV_Fixed_ID | FlexO-x CP:
FlexO- x CI_CK
FlexO- x CI_D[1.. x ]
FlexO- x CI_FS
FlexO- x CI_MFS
FlexO- x CI_SSF
M-AI/FlexO-x-DO-Z A_Sk_MP:
M-AI/FlexO- x -DO- Z A_Sk _MI_AcCST[1.. x ] (Note)
M-AI/FlexO- x -DO- Z A_Sk _MI_cLOS-P
M-AI/FlexO- x -DO- Z A_Sk _MI_cLOL
M-AI/FlexO- x -DO- Z A_Sk _MI_cLOF
M-AI/FlexO- x -DO- Z A_Sk _MI_cLOM
M-AI/FlexO- x -DO- Z A_Sk _MI_cCSTM (Note)
M-AI/FlexO- x -DO- Z A_Sk _MI_cUnlockSec (Note)
M-AI/FlexO- x -DO- Z A_Sk _MI_pFECcorrErr
M-AI/FlexO- x -DO- Z A_Sk _MI_pAuthCheckErr (Note)
M-AI/FlexO-x-GCM-DO A_Sk SKP: (Note)
M-AI/FlexO- x -GCM- DO- Z A_Sk _SKI_AcKI
SK_COMMS_CP: (Note)
SK_COMMS_CI_D
SK_COMMS_CI_CK | +| NOTE – For OTSiG/FlexO- x -GCM-DO- Z A_Sk only. | | + +## Processes + +The processes associated with the M-AI/FlexO-*x*-GCM-DO-*Z* *A\_Sk* function are as depicted in Figure 16-17.12. For the M-AI/FlexO-*x*-DO-*Z* *A\_Sk* function, Figure 16-17.12 could also be used, except that the FlexOsec process is a null process connecting its output signals to the corresponding input signals. + +**PMA process:** The process shall recover the data and clock of the FOIC*x.Z*-DO lanes from the physical media adapted interface. The details are out of scope of this Recommendation. + +**Recombination:** The function shall recombine the *Z* FOIC*x.Z*-DO logical lanes and reconstruct the OFBGz soft signal and FlexO-*x*-DO frame for FOIC2.4-DO (*x*=2, *Z*=4), FOIC2.8-DO (*x*=2, *Z*=8), FOIC4.8-DO (*x*=4, *Z*=8) or FOIC1.4-DO (*x*=1, *Z*=4), respectively. + +**Demapping from -DO frame and multiframe:** The function shall demap the OFBGzP signal structure (carrying the padded, scrambled, OFEC encoded and interleaved FlexO-*x* signal data) from the payload area of the FlexO-*x*-DO DSP frame signal as defined in clause 16.4.6.1 (*Z*=8 for *x*=2 or 4) and 15.4.6.2 (*Z*=4 for *x*=1 or 2) of [ITU-T G.709.3]. It shall generate the OFBGzS block start indication derived from the FlexO-*x*-DO multiframe start indication + +**Deinterleaving:** The function shall deinterleave the bits within the OFBGzP as defined in clause 16.4.5 of [ITU-T G.709.3]. + +**Soft decision FEC decoder and demapping:** See clause 8.5.9 for the soft decision OFEC decoder. After OFEC decoding and demapping, the OFBGz structure consists of $149184 \times Z$ -bit blocks. + +**Descrambler:** The function shall descramble the OFBGz as defined in clause 16.4.2 of [ITU-T G.709.3], resulting into the unscrambled FlexO-*x* frame with pads. + +**Unpadding:** For $\{x, Z\} = \{4, 8\}$ or $\{x, Z\} = \{2, 8\}$ , the function shall remove the 992-bit pad at the end of every OFBG8 structure of $149184 \times 8$ -bit data ( $Z = 8$ ), resulting in of 116 FlexO-*x* frame rows of 10280-bit as described in clause 16.4.1 of [ITU-T G.709.3]. For $\{x, Z\} = \{2, 4\}$ or $\{x, Z\} = \{1, 4\}$ , the function shall remove the 496-bit pad at the end of every OFBG4 of $149184 \times 4$ -bit data ( $Z = 4$ ), resulting in 58 FlexO-2 frame rows of 10280-bit or 116 FlexO-1 frame rows of 5140-bit as described in clause 16.4.1 of [ITU-T G.709.3]. + +**FlexO-*x* frame alignment:** See clause 8.2.8. + +**De-interleaving:** See clause 8.13.2. + +**Extract and replace KCC:** The in-band key exchange communication channel (KCC) is optional in M-AI/FlexO-*x*-GCM-DO-Z\_A\_Sk and unused in M-AI/FlexO-*x*-DO-Z\_A\_Sk function. When used, the function shall extract the KCC data (SK\_COMMS\_CI\_D) from the FlexOsec KCC overhead field of the first FlexO instance frame of the FlexO-*x* as described in clause 9.2.8 of [ITU-T G.709.1]. The bit rate of the KCC data is defined by the outgoing KCC clock. The function shall generate the KCC clock (SK\_COMMS\_CI\_CK) by dividing the FlexO-*x* clock by a factor of 82240. After extraction, the KCC byte in the FlexOsec overhead is replaced with value 0x00 at the input of the FlexOsec sink processes. + +**FlexOsec processes:** + +- For M-AI/FlexO-*x*-GCM-DO-Z\_A\_Sk function See clause 8.14.2 and clause 8.14.3.1 for the specific GCM-AES-256 decryption and authentication processes with the cipher suite type (CST) code point value 000001, as defined in clause B.1 of [ITU-T G.709.1]. The FlexOsec decryption and authentication processes are performed for each individual FlexO instance frame signal in parallel, after to deinterleaving from FlexO-*x*. The same management information (MI) input from the EMF and Secure Key Information (SKI) input from the key exchange and agreement functions are shared by the *x* sets of FlexOsec processes. The same sets of keys are configured to be used by the *x* sets of FlexOsec sink processes. +- For M-AI/FlexO-*x*-DO-Z\_A\_Sk function, this is a null process connecting its output signals to the corresponding input signals. + +**Multiframe alignment:** The process shall recover the FlexO multi-frame start as described in clause 8.2.2. + +![Figure 16-17.12 – M-AI/FlexO-x-GCM-DO-Z_A_Sk processes](64b6966c073f3c3789a8070dbd6106c5_img.jpg) + +The diagram shows the functional architecture of the M-AI/FlexO-x-GCM-DO-Z\_A\_Sk sink function. At the bottom, it starts with the PMA and Lane recombination (from Pol./symbol/) for various FOIC interfaces (FOIC1.4-DO, FOIC2.4-DO, FOIC2.8-DO, FOIC4.8-DO). The signal flows upward through Demapping, Deinterleaving, Soft decision FEC decoder, Descrambler, Unpadding, and FlexO-x frame alignment. From there, it goes through De-interleaving to multiple parallel paths (x = 1, 2, or 4) each containing Multiframe alignment and FlexOsec processes. Management and monitoring signals (MI\_...) are extracted on the right side, including performance monitoring (nFECcorrErr) and defect correlation (dCSTM, dUnlockSec, dLOM, dLOF, dLOL, dLOS-P). Consequent actions (aSSF) are triggered based on these defects. Key management signals (SKI\_Key, SKI\_IV, SKI\_AckI) are also shown interacting with the FlexOsec processes. + +**Figure 16-17.12 – M-AI/FlexO-x-GCM-DO-Z\_A\_Sk processes** + +Figure 16-17.12 – M-AI/FlexO-x-GCM-DO-Z\_A\_Sk processes + +**Defects** + +The function shall detect dLOS-P, dLOL, dLOF, dCSTM, dUnlockSec[*j*] and dLOM[*j*]. + +**dLOS-P**: See clause 6.2.1.2. + +**dLOL**: dLOL is generated for FlexO-*x*-DO interfaces based on the pilot symbols, DSP frame and DSP multiframe alignment. dLOL shall be declared if alignment is false for 3 ms. To provide for the case of intermittent out-of-alignment, the integrating timer shall not be reset to zero until an alignment condition persists continuously for 3 ms. dLOL shall be cleared if alignment is true for 3 ms. + +**dLOF**: See clause 6.2.5.1. + +**dCSTM**: See clause 6.2.11. The expected cipher suite type is "0000 0001". Set to false for M-AI/FlexO-*x*-DO-Z\_Sk function without FlexOsec. + +**Rec. ITU-T G.798 (09/2023)**     403 + +Per FlexO instance #j detection (j = 1..x): + +**dLOM[j]**: See clause 6.2.5.2. + +**dUnlockSec[j]**: See clause 6.2.7.2.1. Set to false for M-AI/FlexO-x-DO-Z\_Sk function without FlexOsec. + +### Consequent actions + +aSSF $\leftarrow \sum dLOM[j]$ or $\sum dUnlockSec[j]$ or dCSTM or dLOF or or dLOS-P or dLOL or AI\_TSF-P + +### Defect correlations + +cLOS-P $\leftarrow$ dLOS-P and (not AI\_TSF-P) + +cLOL $\leftarrow$ dLOL and (not dLOS-P) and (not AI\_TSF-P) + +cLOF $\leftarrow$ dLOF and (not dLOL) and (not AI\_TSF-P) + +cCSTM $\leftarrow$ dCSTM and (not dLOF) and (not dLOL) and (not AI\_TSF-P) + +cUnlockSec $\leftarrow \sum dUnlockSec[j]$ and (not dCSTM) and (not dLOF) and (not dLOL) and (not AI\_TSF-P) + +cLOM $\leftarrow \sum dLOM[j]$ and (not dCSTM) and (not dLOF) and (not dLOL) and (not AI\_TSF-P) + +### Performance monitoring + +The function shall perform the following performance monitoring primitives processing. The performance monitoring primitives shall be reported to the equipment management function (EMF). + +pFECcorrErr $\leftarrow \sum nFECcorrErr$ + +pAuthcheckErr $\leftarrow \sum AuthcheckErr$ + +NOTE – During AI\_TSF-P, $\sum dUnlockSec[j]$ and dLOL, no corrected bits or authentication failure shall be counted. + +## 16.8 OTSiG to FlexO-x adaptation function (OTSiG/FlexO-x\_A) + +The OTSiG to FlexO-x (x = 1, 2, 4) adaptation functions perform the adaptation between the OTSiG layer adapted information and the characteristic information of the FlexO-x layer signal for the flexible OTN short reach interfaces with RS(544,514) FEC code. Two types of functions are defined: one that supports the standardized FlexOsec encryption and authentication functions (GCM-AES-256) and one that does not support FlexOsec encryption and authentication. + +**Table 16-14.7 – OTSi to FlexO-x adaptation functions (x=1,2,4)** + +| Function type | Function name | FlexO-x | +|------------------------|-----------------------------------------------------------------------------------------------------------------------|---------| +| OTSiG/FlexO-x-RS_A | OTSiG to FlexO-x adaptation function with RS(544,514) FEC code and without FlexOsec encryption and authentication | x=1,2,4 | +| OTSiG/FlexO-x-GCM-RS_A | OTSiG to FlexO-x adaptation function with RS(544,514) FEC code and GCM-AES-256 FlexOsec encryption and authentication | x=1,2,4 | + +NOTE – OTSiG/FlexO-x-RS\_A is used throughout this clause as shorthand for the specific function type. + +### 16.8.1 OTSiG to FlexO-*x*-RS adaptation source function (OTSiG/FlexO-*x*-RS\_A\_So) + +The information flow and processing of the OTSiG/FlexO-*x*-RS\_A\_So and OTSiG/FlexO-*x*-GCM-RS\_A\_So functions (*x* = 1, 2, 4) is defined with reference to Figures 16-18 and 16-19. + +#### Symbol + +![Diagram showing the symbols for OTSiG/FlexO-x-RS_A_So and OTSiG/FlexO-x-GCM-RS_A_So functions. The top part shows the OTSiG/FlexO-x-RS_A_So function with input FlexO-x_CP (x=1, 2, 4) entering a trapezoidal block. Inside the block, a dashed oval with arrows indicates a loop. The block has two outputs: OTSi_AP[1] and OTSi_AP[k]. The bottom part shows the OTSiG/FlexO-x-GCM-RS_A_So function with inputs FlexO-x_CP (x=1, 2, 4) and SK_COMMS_CP entering a trapezoidal block. Inside this block, a dashed oval with arrows indicates a loop. The block has two outputs: OTSi_AP[1] and OTSi_AP[k]. A label OTSiG/FlexO-x-GCM-RS_A_So_SKP points to the block. A reference G.798(17)-Amd.4(22)_F16-18 is shown below the bottom block.](7d2489babb3bf789de160fddd90c535b_img.jpg) + +Diagram showing the symbols for OTSiG/FlexO-x-RS\_A\_So and OTSiG/FlexO-x-GCM-RS\_A\_So functions. The top part shows the OTSiG/FlexO-x-RS\_A\_So function with input FlexO-x\_CP (x=1, 2, 4) entering a trapezoidal block. Inside the block, a dashed oval with arrows indicates a loop. The block has two outputs: OTSi\_AP[1] and OTSi\_AP[k]. The bottom part shows the OTSiG/FlexO-x-GCM-RS\_A\_So function with inputs FlexO-x\_CP (x=1, 2, 4) and SK\_COMMS\_CP entering a trapezoidal block. Inside this block, a dashed oval with arrows indicates a loop. The block has two outputs: OTSi\_AP[1] and OTSi\_AP[k]. A label OTSiG/FlexO-x-GCM-RS\_A\_So\_SKP points to the block. A reference G.798(17)-Amd.4(22)\_F16-18 is shown below the bottom block. + +Figure 16-18 – OTSiG/FlexO-*x*-RS\_A\_So and OTSiG/FlexO-*x*-GCM-RS\_A\_So functions + +#### Interfaces + +Table 16-15 – OTSiG/FlexO-*x*-RS\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| FlexO-x_CP :
FlexO- x _CI_CK
FlexO- x _CI_D
FlexO- x _CI_FS
FlexO- x _CI_MFS
OTSiG/FlexO-x-GCM-RS_A_So_SKP: (Note)
OTSiG/FlexO- x -GCM-RS_A_So_SKI_Key[0,1,2,3]
OTSiG/FlexO- x -GCM-RS_A_So_SKI_KI
OTSiG/FlexO- x -GCM-RS_A_So_SKI_IV_Fixed_ID
SK_COMMS_CP: (Note)
SK_COMMS_CI_D | per OTSi_AP:
OTSi_AI_PLD
SK_COMMS_CP: (Note)
SK_COMMS_CI_CK | +| NOTE – For OTSiG/FlexO- x -GCM-RS_A_So only. | | + +#### Processes + +The processes associated with the OTSiG/FlexO-*x*-RS\_A\_So function are as depicted in Figure 16-19. + +**MFAS insertion:** The function shall insert the MFAS into the FlexO basic overhead area in every FlexO instance of the FlexO-*x* as described in [ITU-T G.709.1]. + +**FlexOsec processes:** For OTSiG/FlexO-*x*-GCM-RS\_A\_So, see clause 8.14.1 and clause 8.14.3.1 for the specific GCM-AES-256 encryption and authentication processes with the cipher suite type (CST) + +code point value 000001, as defined in clause B.1 of [ITU-T G.709.1]. The FlexOsec encryption and authentication processes are performed for each individual FlexO instance frame signal in parallel, prior to interleaving into the FlexO-*x*. The same management information (MI) input from the EMF and Secure Key Information (SKI) input from the key exchange and agreement functions are shared by the *x* sets of FlexOsec processes. The same key is used by the *x* sets of FlexOsec source processes which are simultaneously triggered by the key exchange and agreement functions (through SKI\_KI input) to switch to a new key. + +For OTSiG/FlexO-*x*-RS\_A\_So the FlexOsec processes are not present. + +**Interleaving:** See clause 8.13.1. + +**COMMS Clock generation:** For OTSiG/FlexO-*x*-GCM-RS\_A\_So, the function shall generate the SK\_COMMS clock (CK\_COM) by dividing the FlexO clock (CI\_CK) by a factor of 82240. For OTSiG/FlexO-*x*-RS\_A\_So this process is not present. + +**Insert KCC:** For OTSiG/FlexO-*x*-GCM-RS\_A\_So, the in-band key exchange communication channel (KCC) is optional. When used, the incoming SK\_COMMS\_CI\_D data is inserted after FlexOsec authentication and encryption into the KCC field of the first FlexO instance frame (CI\_D[1]) of the FlexO-*x* as described in clause 9.3.2.5 of [ITU-T G.709.1]. When it is not used, the all-ZEROS reserved value is inserted into the KCC field. For OTSiG/FlexO-*x*-RS\_A\_So this process is not present. + +**Clock generation:** The function shall generate the FlexO-*x*-RS clock by multiplying the incoming FlexO clock (CI\_CK) by $[x \times 544/514]$ to the frequencies as listed in Table 11-2, 12-2 or 13-2 of [ITU-T G.709.1] for 100G FlexO-1-RS (*x*=1), 200G FlexO-2-RS (*x*=2) or 400G FlexO-4-RS (*x*=4), respectively. + +**Mapping:** The function shall map (i.e., addition of FEC parity area) the incoming FlexO-*x* frame into the FlexO-*x*-RS frame payload area as defined in clause 11.1, 12.1 or 13-1 of [ITU-T G.709.1] for 100G FlexO-1-RS (*x*=1), 200G FlexO-2-RS (*x*=2) or 400G FlexO-4-RS (*x*=4), respectively. + +**Scrambler:** The function shall scramble FlexO-*x*-RS frame payload, fixed stuffing, extended overhead and basic overhead area as defined in clause 11.4, 12.4 or 13.4 of [ITU-T G.709.1] for 100G FlexO-1-RS (*x*=1), 200G FlexO-2-RS (*x*=2) or 400G FlexO-4-RS (*x*=4) respectively. + +**Alignment insertion:** The function shall insert the alignment marker into the FlexO-*x* frame AM area as described in clause 9.1.1, 9.1.3 or 9.1.5 of [ITU-T G.709.1] for 100G FlexO-1-RS (*x*=1), 200G FlexO-2-RS (*x*=2) or 400G FlexO-4-RS (*x*=4) respectively. + +**FEC encoder:** See clause 8.5.5. + +**Symbol Distribution:** The function shall divide FlexO-*x*-RS frame signal into $(4 \times x)$ FOIC*x*.*k* logical lanes based on 10-bit symbol granularity as described in clause 11.6.1, 12.6.1 or 13.6.1 of [ITU-T G.709.1] for 100G FlexO-1-RS (*x*=1), 200G FlexO-2-RS (*x*=2) or 400G FlexO-4-RS (*x*=4) respectively. + +For *x*=1, the 4 logical lanes of the FlexO-1-RS signal correspond to four FOIC1.4-RS physical lanes and optical OTSi payload signals per clause 11.6.1 of [ITU-T G.709.1]. + +**Bit interleaver:** + +The bit interleaver process bit multiplexes $(4 \times x)/k$ specific logical lanes of the $(4 \times x)$ logical lanes of the FlexO-*x*-RS signal to *k* FOIC*x*.*k*-RS physical lanes and optical OTSi payload signals according to clauses 11.6.5 (*x*=1), 12.6.1 (*x*=2), 13.6.1 and 13.6.6 (*x*=4) of [ITU-T G.709.1]. + +In case $(4 \times x)$ equals *k* the process transparently connects its input to its output. + +![Block diagram of OTSiG/FlexO-x-GCM-RS_A_So processes showing data flow from FlexO-x_CP and SK_COMMS_CP through various processing stages including MFAS insertion, FlexOsec processes, interleaving, mapping, scrambling, alignment insertion, FEC encoding, and symbol distribution to physical lanes.](ca29ffd592187cc2b1719b98a5417521_img.jpg) + +The diagram illustrates the OTSiG/FlexO-x-GCM-RS\_A\_So processes. At the top, **FlexO-x\_CP** provides inputs $CI\_CK$ , $CI\_D[1]$ , $CI\_FS$ , and $CI\_MFS$ to multiple **MFAS insertion** blocks. These blocks output $CK$ , $D^1$ , $FS$ , and $MFS$ to **FlexOsec processes**. **SK\_COMMS\_CP** provides $CI\_CK$ and $CI\_D$ to a **COMMS clock generation** block, which outputs $CK_{COM}$ . A **FlexO-x clock gen. ( $\times x$ )** block also outputs $CK_{COM}$ and $D_{COM}$ to an **Insert KCC** block. The **FlexOsec processes** receive $SKI\_Key[0,1,2,3]$ , $SKI\_KI$ , and $SKI\_IV\_Fixed\_ID$ and output $D_{sec1}$ , $FS$ , and $D_{sec2}$ to an **Interleaving** block. The **Interleaving** block outputs $CK$ , $D$ , and $FS$ to a **Mapping** block. A **FlexO-x-RS clock generation ( $\times 544/514$ )** block outputs $CK_{RS}$ to the **Mapping**, **Scrambler**, **Alignment insertion**, and **FEC encoder** blocks. The **Mapping** block outputs $D$ and $FS$ to the **Scrambler**, which outputs $D$ and $FS$ to the **Alignment insertion**, which outputs $D$ and $FS$ to the **FEC encoder**, which outputs $D$ and $FS$ to a **Symbol distribution** block. The **Symbol distribution** block outputs $1$ , $(4x/k)$ , $4x(k-1)/k+1$ , and $(4x)$ to **(4x) logical lanes**. These lanes are distributed across **Physical lane** blocks, each containing a **(4x/k):1 bit interleaver**. The outputs of the interleavers are $1$ and $(4x/k)$ to **$k$ physical lanes**. The physical lanes are labeled **AI\_PLD** and **OTSi\_AP[1]** through **OTSi\_AP[k]**. A list of FOIC standards is provided at the bottom left: FOIC1.4-RS ( $x = 1, k = 4$ ), FOIC1.1-RS ( $x = 1, k = 1$ ), FOIC2.4-RS ( $x = 2, k = 4$ ), FOIC4.8-RS ( $x = 4, k = 8$ ), and FOIC4.4-RS ( $x = 4, k = 4$ ). The diagram is labeled G.798(23)\_F16-19. + +Block diagram of OTSiG/FlexO-x-GCM-RS\_A\_So processes showing data flow from FlexO-x\_CP and SK\_COMMS\_CP through various processing stages including MFAS insertion, FlexOsec processes, interleaving, mapping, scrambling, alignment insertion, FEC encoding, and symbol distribution to physical lanes. + +OTSiG/FlexO-x-GCM-RS\_A\_So\_SKP + +Figure 16-19 – OTSiG/FlexO-x-GCM-RS\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 16.8.2 OTSiG to FlexO-x-RS adaptation sink function (OTSiG/FlexO-x-RS\_A\_Sk) + +The information flow and processing of the OTSiG/FlexO-x-RS\_A\_Sk and OTSiG/FlexO-x-GCM-RS\_A\_Sk functions is defined with reference to Figures 16-20 and 16-21. + +#### Symbol + +![Diagram showing the symbols for OTSiG/FlexO-x-RS_A_Sk and OTSiG/FlexO-x-GCM-RS_A_Sk functions.](56a00f931e8602f822917af7fa379c0d_img.jpg) + +The diagram illustrates two functional blocks representing adaptation sink functions. + +**Top Block: OTSiG/FlexO-x-RS** + +- A central trapezoidal block labeled **OTSiG/FlexO-x-RS**. +- An input arrow labeled **OTSiG/FlexO-x-RS\_A\_Sk\_MP** enters from the left. +- An output arrow labeled **FlexO-x\_CP** exits from the top. +- Multiple input arrows labeled **OTSi\_AP[1]**, **OTSi\_AP[k]**, and **OTSiG-O\_AP** enter from the bottom. A dashed oval with arrows indicates a series of inputs from 1 to k. + +**Bottom Block: OTSiG/FlexO-x-GCM-RS** + +- A central trapezoidal block labeled **OTSiG/FlexO-x-GCM-RS**. +- An input arrow labeled **OTSiG/FlexO-x-GCM-RS\_A\_Sk\_MP** enters from the left. +- An output arrow labeled **FlexO-x\_CP** exits from the top. +- An output arrow labeled **SK\_COMMS\_CP** exits from the top right. +- An input arrow labeled **OTSiG/FlexO-x-GCM-RS\_A\_Sk\_SKP** enters from the right. +- Multiple input arrows labeled **OTSi\_AP[1]**, **OTSi\_AP[k]**, and **OTSiG-O\_AP** enter from the bottom. A dashed oval with arrows indicates a series of inputs from 1 to k. + +G.798(17)-Amd.4(22)\_F16-20 + +Diagram showing the symbols for OTSiG/FlexO-x-RS\_A\_Sk and OTSiG/FlexO-x-GCM-RS\_A\_Sk functions. + +**Figure 16-20 – OTSiG/FlexO-x-RS\_A\_Sk and OTSiG/FlexO-x-GCM-RS\_A\_Sk functions** + +## Interfaces + +**Table 16-16 – OTSiG/FlexO-*x*-RS\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| per OTSi_AP:
OTSi_AI_PLD
OTSiG-O_AP:
OTSiA_AI_TSF-O
OTSiA_AI_TSF-P
OTSiG/FlexO-x-RS_A_Sk_MP:
OTSiG/FlexO- x -RS_A_Sk_MI_1second
OTSiG/FlexO- x -RS_A_Sk_MI_SquelchEn (Note)
OTSiG/FlexO-x-GCM-RS_A_Sk_SKP: (Note)
OTSiG/FlexO- x -GCM-
RS_A_Sk_SKI_Key[0,1,2,3]
OTSiG/FlexO- x -GCM-
RS_A_Sk_SKI_IV_Fixed_ID | FlexO-x_CP:
FlexO- x _CI_CK
FlexO- x _CI_D[1.. x ]
FlexO- x _CI_FS
FlexO- x _CI_MFS
FlexO- x _CI_SSF
OTSiG/FlexO-x-RS_A_Sk_MP:
OTSiG/FlexO- x -RS_A_Sk_AcCST (Note)
OTSiG/FlexO- x -RS_A_Sk_MI_cLOS-P
OTSiG/FlexO- x -RS_A_Sk_MI_cLOL
OTSiG/FlexO- x -RS_A_Sk_MI_cLOF
OTSiG/FlexO- x -RS_A_Sk_MI_cLOM
OTSiG/FlexO- x -RS_A_Sk_MI_cCSTM (Note)
OTSiG/FlexO- x -RS_A_Sk_MI_cUnlockSec (Note)
OTSiG/FlexO- x -RS_A_Sk_MI_pFECcorrErr
OTSiG/FlexO- x -RS_A_Sk_MI_pAuthCheckErr (Note)
OTSiG/FlexO-x-GCM-RS_A_Sk_SKP: (Note)
OTSiG/FlexO- x -GCM-RS_A_Sk_SKI_AcKI
SK_COMMS_CP: (Note)
SK_COMMS_CI_D
SK_COMMS_CI_CK | +| NOTE – For OTSiG/FlexO- x -GCM-RS_A_Sk only. | | + +## Processes + +The processes associated with the OTSiG/FlexO-*x*-RS\_A\_Sk function are as depicted in Figure 16-21.1 (*x*=1) and Figure 16-21.2 (*x*=2,4). + +**Lane Clock Recovery:** The process shall recover the clock of the FOIC*x.k*-RS lane signal from the incoming data. The function shall introduce no errors in case of jitter and wander, as defined in [ITU-T G.8251]. + +### Bit de-interleaver: + +The bit de-interleaver process bit de-multiplexes each of the *k* FOIC*x.k*-RS physical lanes into (4×*x*)/*k* logical lanes of the (4×*x*) logical lanes of the FlexO-*x*-RS signal according to clauses 11.6.5 (*x*=1), 12.6.1 (*x*=2), 13.6.1 and 13.6.6 (*x*=4) of [ITU-T G.709.1]. + +In case (4×*x*) equals *k* the process transparently connects its inputs to its outputs. + +**Alignment lock:** The function shall recover the FOIC*x.k* logical lane frame start (1/(4×*x*) of FlexO-*x*-RS frame) through obtaining LOCK to the alignment markers as specified by the FEC synchronization state diagram in clause 91.5.3.1 of [IEEE 802.3] for FOIC1.4 or in clause 119.2.5.1 of [IEEE 802.3] for FOIC2.8 or FOIC4.16. The specific alignment marker to be locked shall be CM0 to CM5 (48 bits) per frame as specified in clause 9.1.1, 9.1.3 or 9.1.5 of [ITU-T G.709.1] while the distance between alignment markers (counted by amp\_counter) shall correspond to 128, 256 or 512 FEC codewords as specified in clause 11.1, 12.1 or 13.1 of [ITU-T G.709.1] for FlexO-1-RS, + +FlexO-2-RS or FlexO-4-RS respectively. Additionally, the synchronization process on all logical lanes shall be restarted (restart\_lock set to true) if five consecutive alignment markers fail to match on any of the logical lanes. + +**Deskew & Reorder:** The function shall include deskewing and reordering processes. The deskewing process shall remove the skew of all $(4 \times x)$ FOICx.k logical lanes as specified by the FEC alignment state diagram in clause 91.5.3.1 of [IEEE 802.3] for FOIC1.4 or in clause 119.2.5.1 of [IEEE 802.3] for FOIC2.8 or FOIC4.16. It shall support a maximum skew of 180 ns between logical lanes and a maximum skew variation of 4 ns. The reordering process shall reorder these $(4 \times x)$ FOICx.k logical lanes according to their lane number (see clause 9.1.1, 9.1.3 or 9.1.5 of [ITU-T G.709.1] for FOIC1.4, FOIC2.8 or FOIC4.16 respectively). The FOICx.k lane number is identified by six 8-bit unique markers from the UMx area. + +**Recombination:** The function shall multiplex the aligned and ordered $(4 \times x)$ FOICx.k logical lanes into the original stream of FEC codewords and reconstruct the FlexO-x-RS frame. + +**FEC Decoder:** See clause 8.5.5. + +**Descrambler:** The function shall perform descrambling for FlexO-x-RS frame payload, fixed stuffing, basic overhead and extended overhead area as described in clause 11.4, 12.4 or 13.4 of [ITU-T G.709.1] for 100G FlexO-1-RS ( $x=1$ ), 200G FlexO-2-RS ( $x=2$ ) or 400G FlexO-4-RS ( $x=4$ ) respectively. + +**Demapping:** The function shall demap (i.e., removal of FEC parity area) the FlexO-x frame from the incoming FlexO-x-RS frame as defined in clause 11.1, 12.1 or 13.1 of [ITU-T G.709.1] for 100G FlexO-1-RS ( $x=1$ ), 200G FlexO-2-RS ( $x=2$ ) or 400G FlexO-4-RS ( $x=4$ ), respectively. + +**Extract and replace KCC:** For OTSiG/FlexO-x-GCM-RS\_A\_Sk the in-band key exchange communication channel (KCC) is optional. When used, the function shall extract the KCC data (SK\_COMMS\_CI\_D) from the FlexOsec KCC overhead field of the first FlexO instance frame of the FlexO-x as described in clause 9.2.8 of [ITU-T G.709.1]. The bit rate of the KCC data is defined by the outgoing KCC clock. The function shall generate the KCC clock (SK\_COMMS\_CI\_CK) by dividing the FlexO-x clock by a factor of 82240. After extraction, the KCC byte in the FlexOsec overhead is replaced with value 0x00 at the input of the FlexOsec sink processes. + +For OTSiG/FlexO-x-RS\_A\_Sk this process is not present. + +**FlexOsec processes:** For OTSiG/FlexO-x-GCM-RS\_A\_Sk see clause 8.14.2 and clause 8.14.3.1 for the specific GCM-AES-256 decryption and authentication processes with the cipher suite type (CST) code point value 000001, as defined in clause B.1 of [ITU-T G.709.1]. The FlexOsec decryption and authentication processes are performed for each individual FlexO instance frame signal in parallel, after deinterleaving from FlexO-x. The same management information (MI) input from the EMF and Secure Key Information (SKI) input from the key exchange and agreement functions are shared by the $x$ sets of FlexOsec processes. The same sets of keys are configured to be used by the $x$ sets of FlexOsec sink processes. + +For OTSiG/FlexO-x-RS\_A\_Sk this process is not present. + +**De-interleaving:** See clause 8.13.2. + +**Multiframe alignment:** The process shall recover the FlexO multi-frame start as described in clause 8.2.2. + +![Figure 16-21 – OTSiG/FlexO-x-GCM-RS_A_Sk processes. This is a complex block diagram showing the signal processing flow for OTSiG/FlexO-x-GCM-RS_A_Sk. At the bottom, multiple physical lanes (k physical lanes) are shown. Each lane has a 'Clock recovery' block followed by a 'LOS detection' block, which outputs dLOS-P[i]. Above this, there are '(4x/k) bit deinterleaver' blocks. The next stage is 'Alignment lock' blocks, which take inputs from the deinterleavers and produce 'restart_lock[i]' and 'restart' signals. These are followed by 'Deskew' and 'Lane reorder and recombination' blocks. The signal then passes through a 'FEC decoder', 'Descrambler', and 'Demapping' blocks. Above these are 'De-interleaving' blocks. The next major stage consists of 'FlexOsec processes' (labeled 1, 2, ..., x). Each process takes inputs from the de-interleaving stage and produces 'AuthCheckErr[i]', 'dUnlockSec[i]', 'AcCST[i]', 'SKI_AcKI[i]', and 'dLOM[i]'. These are followed by 'Multiframe alignment' blocks, which produce 'dLOM[i]'. At the top, there are 'Consequent actions' blocks that take inputs from the multiframe alignment and produce 'dCSTM', 'dLOL', 'dUnlockSec[1..x]', and 'dLOM[1..x]'. Various other signals like 'CK', 'D', 'FS', 'MI_SquelchEn', 'MI_AcCST[1..x]', 'MI_pAuthcheckErr', 'MI_1second', 'MI_pFECorrErr', 'MI_cCSTM', 'MI_cUnlockSec', 'MI_cLOM', 'MI_cLOL', 'MI_cLOS-P', 'aSSF', and 'SKI_Key[0, 1, 2, 3]' are shown throughout the diagram. On the right side, there are labels for 'OTSiG/FlexO-x-GCM-RS_A_Sk_SKP' and 'OTSiG/FlexO-x-RS_A_Sk_MP'. At the bottom right, there is a list of FOIC configurations: FOIC1.4-RS (x = 1, k = 4), FOIC1.1-RS (x = 1, k = 1), FOIC2.4-RS (x = 2, k = 4), FOIC4.8-RS (x = 4, k = 8), and FOIC4.4-RS (x = 4, k = 4).](51b3f989269d40b52bbf69c7a448bf52_img.jpg) + +Figure 16-21 – OTSiG/FlexO-x-GCM-RS\_A\_Sk processes. This is a complex block diagram showing the signal processing flow for OTSiG/FlexO-x-GCM-RS\_A\_Sk. At the bottom, multiple physical lanes (k physical lanes) are shown. Each lane has a 'Clock recovery' block followed by a 'LOS detection' block, which outputs dLOS-P[i]. Above this, there are '(4x/k) bit deinterleaver' blocks. The next stage is 'Alignment lock' blocks, which take inputs from the deinterleavers and produce 'restart\_lock[i]' and 'restart' signals. These are followed by 'Deskew' and 'Lane reorder and recombination' blocks. The signal then passes through a 'FEC decoder', 'Descrambler', and 'Demapping' blocks. Above these are 'De-interleaving' blocks. The next major stage consists of 'FlexOsec processes' (labeled 1, 2, ..., x). Each process takes inputs from the de-interleaving stage and produces 'AuthCheckErr[i]', 'dUnlockSec[i]', 'AcCST[i]', 'SKI\_AcKI[i]', and 'dLOM[i]'. These are followed by 'Multiframe alignment' blocks, which produce 'dLOM[i]'. At the top, there are 'Consequent actions' blocks that take inputs from the multiframe alignment and produce 'dCSTM', 'dLOL', 'dUnlockSec[1..x]', and 'dLOM[1..x]'. Various other signals like 'CK', 'D', 'FS', 'MI\_SquelchEn', 'MI\_AcCST[1..x]', 'MI\_pAuthcheckErr', 'MI\_1second', 'MI\_pFECorrErr', 'MI\_cCSTM', 'MI\_cUnlockSec', 'MI\_cLOM', 'MI\_cLOL', 'MI\_cLOS-P', 'aSSF', and 'SKI\_Key[0, 1, 2, 3]' are shown throughout the diagram. On the right side, there are labels for 'OTSiG/FlexO-x-GCM-RS\_A\_Sk\_SKP' and 'OTSiG/FlexO-x-RS\_A\_Sk\_MP'. At the bottom right, there is a list of FOIC configurations: FOIC1.4-RS (x = 1, k = 4), FOIC1.1-RS (x = 1, k = 1), FOIC2.4-RS (x = 2, k = 4), FOIC4.8-RS (x = 4, k = 8), and FOIC4.4-RS (x = 4, k = 4). + +**Figure 16-21 – OTSiG/FlexO-x-GCM-RS\_A\_Sk processes** + +## Defects + +The function shall detect dLOS-P[1..k], dLOL, dCSTM, dUnlockSec[1..x] and dLOM[1..x]. + +**dLOS-P[i]:** See clause 6.2.1.2. + +**dLOL:** dLOL is generated for multilane interfaces based on the FEC alignment state diagram in clause 91.5.3.1 of [IEEE 802.3] for FOIC1.4 or on the PCS synchronization state diagram in clause 119.2.5.1 of [IEEE 802.3] for FOIC2.8 or FOIC4.16. dLOL shall be declared if fec\_alignment\_valid is false for 3 ms. To provide for the case of intermittent out-of-locks + +(fec\_alignment\_valid is false), the integrating timer shall not be reset to zero until an in-lock (fec\_alignment\_valid is true) condition persists continuously for 3 ms. dLOL shall be cleared if fec\_alignment\_valid is true for 3 ms. + +NOTE – The hi\_ser variable shall be assumed to be zero in the PCS synchronization state diagram of clause 119.2.5.1 of [IEEE 802.3] because the FEC\_bypass\_indication\_enable is always set to zero in the case of OTN. + +**dCSTM:** For OTSiG/FlexO-x-GCM-RS\_A\_Sk see clause 6.2.11. The expected cipher suite type is "0000 0001". For OTSiG/FlexO-x-RS\_A\_Sk dCSTM is assumed to be false. + +Per FlexO instance #j detection (j = 1..x): + +**dLOM[j]:** See clause 6.2.5.2. + +**dUnlockSec[j]:** For OTSiG/FlexO-x-GCM-RS\_A\_Sk see clause 6.2.7.2.1; for OTSiG/FlexO-x-RS\_A\_Sk dUnlockSec[j] is assumed to be false. + +#### Consequent actions + +aSSF $\leftarrow \sum dLOM[j]$ or $\sum dUnlockSec[j]$ or dCSTM or $\sum dLOS-P[i]$ or dLOL or AI\_TSF-P + +#### Defect correlations + +cLOS-P $\leftarrow \sum dLOS-P[i]$ and (not AI\_TSF-P) + +cLOL $\leftarrow dLOL$ and (not $\sum dLOS-P[i]$ ) and (not AI\_TSF-P) + +cCSTM $\leftarrow dCSTM$ and (not dLOL) and (not AI\_TSF-P) + +cUnlockSec $\leftarrow \sum dUnlockSec[j]$ and (not dCSTM) and (not dLOL) and (not AI\_TSF-P) + +cLOM $\leftarrow \sum dLOM[j]$ and (not dCSTM) and (not dLOL) and (not AI\_TSF-P) + +#### Performance monitoring + +The function shall perform the following performance monitoring primitives processing. The performance monitoring primitives shall be reported to the equipment management function (EMF). + +pFECcorrErr $\leftarrow \sum nFECcorrErr$ + +For OTSiG/FlexO-x-GCM-RS\_A\_Sk only: + +pAuthcheckErr $\leftarrow \sum AuthcheckErr$ + +NOTE – During AI\_TSF-P and dLOL, no corrected bits or authentication failure shall be counted. + +### 16.9 OTSi to OSC adaptation function (OTSi/OSC\_A) + +The OTSi to OSC adaptation functions perform the adaptation between the OTSi layer adapted information and the characteristic information of functionally standardized OSC layer signal. + +#### 16.9.1 OTSi to OSC adaptation source function (OTSi/OSC\_A\_So) + +The information flow and processing of the OTSi/OSC\_A\_So function is defined with reference to Figure 16-22. + +## Symbol + +![Symbol diagram for OTSi/OSC_A_So function. It shows a trapezoidal block labeled 'OTSi/OSC'. An arrow labeled 'OSC_CP' points into the top of the block, and an arrow labeled 'OTSi_AP' points out from the bottom. The diagram is labeled G.798(17)_F16-22.](5cb3b242ac7ea1fa7007ebd51b80e5b9_img.jpg) + +Symbol diagram for OTSi/OSC\_A\_So function. It shows a trapezoidal block labeled 'OTSi/OSC'. An arrow labeled 'OSC\_CP' points into the top of the block, and an arrow labeled 'OTSi\_AP' points out from the bottom. The diagram is labeled G.798(17)\_F16-22. + +Figure 16-22 – OTSi/OSC\_A\_So function + +## Interfaces + +Table 16-17 – OTSi/OSC\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------|--------------------------------| +| OSC_CP:
OSC_CI_OH
OSC_CI_CK | OTSi_AP:
OTSi_AI_PLD | + +## Processes + +The OTSi/OSC\_A\_So function provides all processes necessary for the adaptation to the OTSi layer, which includes processes that ensure clock and frame recovery at the adaptation sink and optional forward error correction coding. + +The specific processes are outside the scope of this Recommendation. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 16.9.2 OTSi to OSC adaptation sink function (OTSi/OSC\_A\_Sk) + +The OTSi/OSC\_A\_Sk detects the dLOS-O defectand counts during one-second periods defects to feed performance monitoring when connected. + +The information flow and processing of the OTSi/OSC\_A\_Sk function is defined with reference to Figure 16-23. + +## Symbol + +![Symbol diagram for OTSi/OSC_A_Sk function. It shows a trapezoidal block labeled 'OTSi/OSC'. An arrow labeled 'OTSi_AP' points into the bottom of the block, and an arrow labeled 'OSC_CP' points out from the top. A double-headed arrow labeled 'OTSi/OSC_A_Sk_MP' is connected to the left side of the block. The diagram is labeled G.798(17)_F16-23.](1ff7740e14c18789657d277030fb69ce_img.jpg) + +Symbol diagram for OTSi/OSC\_A\_Sk function. It shows a trapezoidal block labeled 'OTSi/OSC'. An arrow labeled 'OTSi\_AP' points into the bottom of the block, and an arrow labeled 'OSC\_CP' points out from the top. A double-headed arrow labeled 'OTSi/OSC\_A\_Sk\_MP' is connected to the left side of the block. The diagram is labeled G.798(17)\_F16-23. + +Figure 16-23 – OTSi/OSC\_A\_Sk function + +## Interfaces + +**Table 16-18 – OTSi/OSC\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| OTSi_AP:
OTSi_AI_PLD
OTSi/OSC_A_Sk_MP:
OTSi/OSC_A_Sk_MI_1second | OSC_CP:
OSC_CI_OH
OSC_CI_CK
OSC_CI_SSF
OTSi/OSC_A_Sk_MP:
OTSi/OSC_A_Sk_MI_cLOS-O
OTSi/OSC_A_Sk_MI_pN_DS-O | + +## Processes + +The OTSi/OSC\_A\_Sk function provides all processes necessary for the adaptation from the OTSi layer, which includes processes for clock recovery. + +The specific processes are outside the scope of this Recommendation. + +## Defects + +The OTSi/OSC\_A\_Sk function shall detect the dLOS-O defect. + +**dLOS-O:** See clause 6.2.1.3. + +## Consequent actions + +The OTSi/OSC\_A\_Sk function shall perform the following consequent action: + +aSSF $\leftarrow$ dLOS-O + +## Defect correlations + +The OTSi/OSC\_A\_Sk function shall perform the following defect correlation: + +cLOS-O $\leftarrow$ dLOS-O + +## Performance monitoring + +The OTSi/OSC\_A\_Sk function shall perform the following performance monitoring primitives. The performance monitoring primitives shall be reported to the EMF. + +pN\_DS-O $\leftarrow$ dLOS-O + +## 17 Media element + +The optical transmission layer is described by media elements. Non-associated overhead (see clauses 9, 10, 11, and 12) provides management structure for the optical media layer. + +A media element operates on the envelope of any optical signals that are present in a media channel (e.g., amplify the signal, constrain or direct the media channel etc.) and is not aware of the information being carried. Media elements do not demodulate the signal and therefore do not process the digital information that is carried by the signal. + +A media element has N ports. An optical signal that is present at a port may be transferred to 0 or more other ports on the media element. + +- Each pair of ports that allow signal transfer has one or more media channels with a frequency slot (defined by m and n; see [ITU-T G.694.1]) for each media channel. + +- Each media channel has zero or more transfer parameters. The transfer parameters (the optical characteristics of the media channel) are defined in other Recommendations including for example [ITU-T G.663] and [ITU-T G.680]. + +The media channel and signal transfer are modelled independently for each direction of signal propagation. The internal structure of a media element is not visible, only the media channels between the ports are defined. + +The media element has a management port to allow exchange of management information with the equipment management function. + +To facilitate management of the optical network, non-associated overhead can be used with a media element to provide maintenance entities that can assist with fault isolation, management communications, and other OAM functions. The media element has a defect port that is used to communicate loss of signal information to the atomic functions that provide this management structure. + +### Internal signal monitors + +A media element may include an optical parameter monitor (OPM) function that monitors the bulk properties (e.g., power) of any of the optical signals that are present in a media channel. Depending on the frequency slot of the media channel the OPM may operate on for example an aggregated set of OTSi (e.g., the input to an optical line amplifier) or a single OTSi. The output of the OPM is an electrical signal that is quantized and encoded to a binary value that is proportional to the observed optical power. The mapping between the optical power and the binary values is vendor specific and is not subject to standardization. + +The OPM may be associated via an internal media channel with any of the externally visible ports, or it may monitor an OMS\_ME end point or an OTS\_ME end point that are implemented within the media element. Note that the OPM functions may be integrated into an optical amplifier. The location of the OMS and OTS are defined in [ITU-T G.872]. Appendix VII provides some examples of the case where the OMS and OTS end points are encapsulated within a media element. + +### Attachment of external signal monitors + +The ability to attach an external signal monitor to the optical signal that is present on a port of a media element is provided by an additional media channel (within the media element) from the subject port to another external port. + +### Symbol + +![Diagram of MediaElement function showing various ports and signal flow.](f4bcd6496e0add3544afc0a70f7973ec_img.jpg) + +The diagram illustrates the MediaElement function as a central grey rounded rectangle. It features several external connections: at the top, multiple bidirectional arrows represent OTSi\_AP (Optical Transport Signal Interface - Administrative Point) connections, indicated by an ellipsis between two arrows; on the right side, two single-headed arrows point outwards to ME\_MP (Media Element Management Point) and ME\_DP (Media Element Defect Point); at the bottom, a single bidirectional arrow represents the Optical signal input/output. The text 'G.798(17)\_F17-1' is located in the bottom right corner of the diagram area. + +Diagram of MediaElement function showing various ports and signal flow. + +Figure 17-1 – MediaElement function + +## Interfaces + +**Table 17-1 – MediaElement inputs and outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MediaElement_MP:
ME_MI_configureMediaChannel(port j, port k, freqSlot, signalTransfer)
ME_MI_configureOPM(port j, freqSlot, threshold)

per OTSi_AP:
OTSi_AI_PLD | MediaElement_MP:
ME_MI_queryMediaChannel(port j, port k, freqSlot, signalTransfer)
ME_MI_OPM(port j, freqSlot, value)
ME_MI_dLOS-P[i]

per OTSi_AP:
OTSi_AI_PLD

MediaElement_DP:
ME_DI_dLOS-P[i] | + +## Processes + +The specific processes performed in a media element are outside the scope of this Recommendation. They are expressed in terms of the transfer function associated with each of the media channels within the media element. + +## Defects + +If the MediaElement function includes an OPM then each OPM *i* shall detect dLOS-P[*i*]. The presence of dLOS-P[*i*] is reported at either the Management Point (for communication with the equipment management function, in cases where there is no non-associated overhead) or the Defect Point (for communication with atomic functions related to non-associated overhead). + +**Consequent actions:** None. + +**Defect correlations:** None. + +## Performance monitoring + +The OPM may in addition to dLOS-P[*i*] may also provide an electrical signal that is quantized and encoded to a binary value that is proportional to the observed optical power. The mapping between the optical power and the binary values is vendor specific and is not subject to standardization. + +## Annex A + +### Optical section (OSx) and constant bit rate (CBRx) layer functions + +(This annex forms an integral part of this Recommendation.) + +#### Introduction + +The OSx and CBRx layer functions are not part of the OTN. They are defined in this Recommendation in order to provide transparent transport of constant bit rate (CBR) signals over the OTN. The CBR signal is mapped into the ODU (see clause 14.3). + +The parameter x defines the supported bit rate or bit-rate range. The values x = 2G5, 10G and 40G are defined for client signals that correspond to the SDH bit rates defined in Table A.1. The values x = FC-100, FC-200, FC-400, FC-800, FC-1200, FC-1600 and FC-3200 are defined for client signals that comply to the Fibre Channel bit rates as defined in Table A.1A. Support for other bit rates and bit-rate ranges are for further study. + +**Table A.1 – Defined values for x (SDH)** + +| OS type | x | Bit rate | Clock range | +|-------------------|-----|--------------------------------|-----------------------------| +| OS16 | 2G5 | 2 488 320 kbit/s $\pm$ 20 ppm | 2 488 320 kHz $\pm$ 20 ppm | +| OS64 | 10G | 9 953 280 kbit/s $\pm$ 20 ppm | 9 953 280 kHz $\pm$ 20 ppm | +| OS256 or OSM256.4 | 40G | 39 813 120 kbit/s $\pm$ 20 ppm | 39 813 120 kHz $\pm$ 20 ppm | + +**Table A.1A – Defined values for x (fibre channel)** + +| x | Bit rate | Clock range | Jitter standard | +|---------|---------------------------------|---------------------------------|---------------------| +| FC-100 | 1 062 500 kbit/s $\pm$ 100 ppm | 1 062 500 kbit/s $\pm$ 100 ppm | [b-ANSI INCITS 352] | +| FC-200 | 2 125 000 kbit/s $\pm$ 100 ppm | 2 125 000 kbit/s $\pm$ 100 ppm | [b-ANSI INCITS 352] | +| FC-400 | 4 250 000 kbit/s $\pm$ 100 ppm | 4 250 000 kbit/s $\pm$ 100 ppm | [b-ANSI INCITS 352] | +| FC-800 | 8 500 000 kbit/s $\pm$ 100 ppm | 8 500 000 kbit/s $\pm$ 100 ppm | [b-ANSI INCITS 352] | +| FC-1200 | 10 518 750 kbit/s $\pm$ 100 ppm | 10 518 750 kbit/s $\pm$ 100 ppm | [b-ANSI INCITS 364] | +| FC-1600 | 14 025 000 kbit/s $\pm$ 100 ppm | 14 025 000 kbit/s $\pm$ 100 ppm | [b-ANSI INCITS 352] | +| FC-3200 | 28 050 000 kbit/s $\pm$ 100 ppm | 28 050 000 kbit/s $\pm$ 100 ppm | [b-INCITS 512] | + +**Table A.1B – Jitter standard and replacement signals (fibre channel)** + +| x | Jitter standard | Replacement signal | FEC | +|---------|---------------------|---------------------------|------------------------------| +| FC-100 | [b-ANSI INCITS 352] | 17.7.1.2 of [ITU-T G.709] | None | +| FC-200 | [b-ANSI INCITS 352] | 17.7.2.1 of [ITU-T G.709] | None | +| FC-400 | [b-ANSI INCITS 352] | 17.9.1 of [ITU-T G.709] | None | +| FC-800 | [b-ANSI INCITS 352] | 17.9.1 of [ITU-T G.709] | None | +| FC-1200 | [b-ANSI INCITS 364] | 17.8.2 of [ITU-T G.709] | None | +| FC-1600 | [b-ANSI INCITS 352] | 17.9.2 of [ITU-T G.709] | Optional [b-ANSI INCITS 470] | +| FC-3200 | [b-INCITS 512] | 17.9.3 of [ITU-T G.709] | Mandatory [b-INCITS 488] | + +NOTE – FC-y is used throughout this clause as shorthand for the defined values for x for fibre channel type interfaces. + +Figure A.1 illustrates the OSx layer network and CBRx layer adaptation functions. The OSx layer network represents physical optical interface for constant bit-rate signals. The information crossing the OSx termination connection point (OSx\_TCP) is referred to as the OSx characteristic information (OSx\_CI). The information crossing the OSx access point (OSx\_AP) is referred to as the OSx adapted information (OSx\_AI). + +![Diagram of OSx layer network and client layer adaptation functions](5b9a924d48ea39458bd16a3c89a576d5_img.jpg) + +The diagram shows a vertical stack of components. At the top is 'CBRx\_CP'. Below it is a trapezoidal block labeled 'OSx/CBRx'. Below that is a double-headed vertical arrow labeled 'OSx\_AP'. Below that is a trapezoidal block labeled 'OSx'. Below that is another double-headed vertical arrow labeled 'OSx\_TCP'. At the bottom is the text 'G.798(12)\_FA.1'. + +Diagram of OSx layer network and client layer adaptation functions + +Figure A.1 – OSx layer network and client layer adaptation functions + +#### A.1 Connection functions + +Not applicable. + +#### A.2 Termination functions + +##### A.2.1 OSx trail termination function (OSx\_TT) (x = 2G5, 10G, 40G, FC-y) + +The OSx\_TT functions are responsible for the end-to-end supervision of the OSx trail. Figure A.2 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +NOTE – For the case where an STM-N signal is to be transported as a CBR signal, the OSx\_TT functions are equivalent to the OSn\_TT or OSMn.m\_TT functions specified in [ITU-T G.783]. + +![Diagram of OSx_TT functions](df1e7f3029a414245762364710a6a63e_img.jpg) + +The diagram shows two separate vertical paths. The left path starts with 'OSx\_AP' at the top, a downward arrow to a trapezoidal block labeled 'OSx', and a downward arrow to 'OSx\_TCP' at the bottom. The right path starts with 'OSx\_TCP' at the bottom, an upward arrow to a trapezoidal block labeled 'OSx', and an upward arrow to 'OSx\_AP' at the top. Below the right path is the text 'G.798(12)\_FA.2'. + +Diagram of OSx\_TT functions + +Figure A.2 – OSx\_TT + +##### A.2.1.1 OS trail termination source function (OSx\_TT\_So) (x = 2G5, 10G, 40G, FC-y) + +The information flow and processing of the OSx\_TT\_So function is defined with reference to Figures A.3 and A.4. The OSx\_TT\_So generates an optical signal. The physical parameters of the signal depend on the application. For SDH OSn type interfaces, the specifications in [ITU-T G.957] or [ITU-T G.691] apply. For SDH OSM256.4 type interfaces, [ITU-T G.783] clause 9.2.3 and the specifications in [ITU-T G.695] apply. + +## Symbol + +![Figure A.3: OSx_TT_So function symbol. A triangle labeled OSx has three input arrows from the top (OSx_AP), left (OSx_RP), and right (OSx_TT_So_MP). It has one output arrow pointing downwards (OSx_TCP). The diagram is labeled G.798(12)_FA.3.](5817c9e42aa8e99964a2845d4adee0d0_img.jpg) + +Figure A.3: OSx\_TT\_So function symbol. A triangle labeled OSx has three input arrows from the top (OSx\_AP), left (OSx\_RP), and right (OSx\_TT\_So\_MP). It has one output arrow pointing downwards (OSx\_TCP). The diagram is labeled G.798(12)\_FA.3. + +Figure A.3 – OSx\_TT\_So function + +## Interfaces + +Table A.2 – OSx\_TT\_So inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| OSx_AP:
OSx_AI_D
OSx_RP:
OSx_RI_APR (Note 1)
OSx_TT_So_MP:
OSx_TT_So_MI_APRCtrl (Notes 1 and 2) | OSx_TCP:
OSx_CI | +| NOTE 1 – If APR is required. | | +| NOTE 2 – The APRCtrl commands depend on the specific APR process. | | + +## Processes + +The processes associated with the OSx\_TT\_So function are depicted in Figure A.4. + +**Automatic power reduction (APR):** For eye safety considerations, according to [IEC 60825-1] and [IEC 60825-2], it may be necessary to provide for a capability for automatic (optical) power reduction (APR) in case of loss of the optical input signal at the sink function. The OSx\_TT\_So performs in this case the power reduction for the outgoing OSx signal based on the trigger criteria from the sink (RI\_APR) and control information (MI\_APRCtrl). The specific APR procedures and trigger criteria are outside the scope of this Recommendation. Clause 6.2 of [ITU-T G.664] provides basic requirements for APR. + +![Figure A.4: OSx_TT_So processes diagram. A large rectangle contains a dashed box labeled 'APR process'. Inputs include OSx_AP (with sub-input AI_D) from the top, MI_APRCtrl and RI_APR from the right, and OSx_RP from the bottom right. The output is OSx_TCP (with sub-output CI) at the bottom. The diagram is labeled G.798(12)_FA.4.](97f616c98c1526454f9a6c183492b2b5_img.jpg) + +Figure A.4: OSx\_TT\_So processes diagram. A large rectangle contains a dashed box labeled 'APR process'. Inputs include OSx\_AP (with sub-input AI\_D) from the top, MI\_APRCtrl and RI\_APR from the right, and OSx\_RP from the bottom right. The output is OSx\_TCP (with sub-output CI) at the bottom. The diagram is labeled G.798(12)\_FA.4. + +Figure A.4 – OSx\_TT\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### A.2.1.2 OSx trail termination sink function (OSx\_TT\_Sk) (x = 2G5, 10G, 40G, FC-y) + +The information flow and processing of the OSx\_TT\_Sk function is defined with reference to Figures A.5 and A.6. The OSx\_TT\_Sk reports the state of the OSx trail. The OSx\_TT\_Sk accepts an optical signal. The physical parameters of the signal depend on the application. For SDH OSn type interfaces, the specifications in [ITU-T G.957] or [ITU-T G.691] apply. For SDH OSM256.4 type interfaces, [ITU-T G.783] clause 9.2.3 and the specifications in [ITU-T G.695] apply. + +##### Symbol + +![Symbol diagram for OSx_TT_Sk function. A central triangle labeled 'OSx' has an input arrow from the bottom labeled 'OSx_TCP'. It has three output arrows: one pointing up labeled 'OSx_AP', one pointing left labeled 'OSx_TT_Sk_MP', and one pointing right (dashed) labeled 'OSx_RP'. The diagram is labeled 'G.798(12)_FA.5' at the bottom right.](13df7f8b1a0bebbe3b52a35d9af93631_img.jpg) + +Symbol diagram for OSx\_TT\_Sk function. A central triangle labeled 'OSx' has an input arrow from the bottom labeled 'OSx\_TCP'. It has three output arrows: one pointing up labeled 'OSx\_AP', one pointing left labeled 'OSx\_TT\_Sk\_MP', and one pointing right (dashed) labeled 'OSx\_RP'. The diagram is labeled 'G.798(12)\_FA.5' at the bottom right. + +**Figure A.5 – OSx\_TT\_Sk function** + +##### Interfaces + +**Table A.3 – OSx\_TT\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| OSx_TCP:
OSx_CI | OSx_AP:
OSx_AI_D
OSx_AI_TSF
OSx_RP:
OSx_RI_APR (Note)
OSx_TT_Sk_MP:
OSx_TT_Sk_MI_cLOS
OSx_TT_Sk_MI_pN_DS | +| NOTE – If APR is required. | | + +##### Processes + +The processes associated with the OSx\_TT\_Sk function are depicted in Figure A.6. + +**Automatic Power Reduction (APR):** For eye safety considerations, according to [IEC 60825-1] and [IEC 60825-2], it may be necessary to provide for a capability for automatic (optical) power reduction (APR) in case of loss of the optical input signal at the sink function. The OSx\_TT\_Sk generates in this case the APR trigger criteria based on the incoming OSx signal (OSx\_CI) and forwards it to the OSx\_TT\_So (RI\_APR). The specific APR procedures and trigger criteria are outside the scope of this Recommendation. Clause 6.2 of [ITU-T G.664] provides basic requirements for APR. + +![Diagram of OSx_TT_Sk processes showing internal components and their interactions with external interfaces.](fd6100880c96880a39d994338c9d5f36_img.jpg) + +The diagram illustrates the internal processes of the OSx\_TT\_Sk function. It is bounded by a grey rectangle labeled G.798(12)\_FA.6. Inside, there are several functional blocks: 'Defect correlations', 'Performance monitoring', 'Consequent actions', 'LOS supervision', and 'APR process' (dashed box). External interfaces and signals include OSx\_AP, AI\_TSF, AI\_D, OSx\_TT\_Sk\_MP, MI\_cLOS, MI\_pN\_DS, OSx\_RP, RI\_APR, and CI OSx\_TCP. Arrows indicate the flow of information: dLOS signals from 'Consequent actions', 'Defect correlations', and 'Performance monitoring' to 'aTSF' and 'LOS supervision'. 'aTSF' outputs to OSx\_AP and AI\_TSF. 'LOS supervision' outputs to dLOS and AI\_D. 'Performance monitoring' outputs to MI\_pN\_DS. 'Defect correlations' outputs to MI\_cLOS. 'APR process' outputs to RI\_APR. A dashed arrow points from 'Performance monitoring' to 'APR process'. + +Diagram of OSx\_TT\_Sk processes showing internal components and their interactions with external interfaces. + +**Figure A.6 – OSx\_TT\_Sk processes** + +### Defects + +The OSx\_TT\_Sk function shall detect the dLOS defect. + +**dLOS:** See clause 6.2.1.1 of [ITU-T G.783]. + +### Consequent actions + +The OSx\_TT\_Sk function shall perform the following consequent action: + +aTSF $\leftarrow$ dLOS + +### Defect correlations + +The OSx\_TT\_Sk function shall perform the following defect correlation: + +cLOS $\leftarrow$ dLOS + +### Performance monitoring + +The OSx\_TT\_Sk function shall perform the following performance monitoring primitive. The performance monitoring primitive shall be reported to the EMF. + +pN\_DS $\leftarrow$ dLOS + +## A.3 Adaptation functions + +### A.3.1 OSx to CBRx adaptation (OSx/CBRx\_A) (x = 2G5, 10G, 40G, FC-y) + +The OSx to CBRx adaptation functions perform the adaptation between the OSx layer adapted information and the characteristic information of a CBRx layer signal. + +#### A.3.1.1 OSx to CBRx adaptation source function without FEC (OSx/CBRx\_A\_So) (x = 2G5, 10G, 40G, FC-y) + +For SDH OSn type interfaces and fibre channel type interfaces, the information flow and processing of the OSx/CBRx\_A\_So function is defined with reference to Figures A.7 and A.8. + +NOTE – For SDH OSM256.4 type interfaces, please see A.3.1.3. + +## Symbol + +![Figure A.7: OSx/CBRx_A_So function symbol diagram. It shows a trapezoidal symbol labeled 'OSx/CBRx'. An arrow labeled 'CBRx_CP' points into the top of the symbol, and an arrow labeled 'OSx_AP' points out from the bottom. The text 'G.798(17)_FA.7' is located below the symbol.](04244205ef763574ac5ef2df0513c14d_img.jpg) + +Figure A.7: OSx/CBRx\_A\_So function symbol diagram. It shows a trapezoidal symbol labeled 'OSx/CBRx'. An arrow labeled 'CBRx\_CP' points into the top of the symbol, and an arrow labeled 'OSx\_AP' points out from the bottom. The text 'G.798(17)\_FA.7' is located below the symbol. + +Figure A.7 – OSx/CBRx\_A\_So function + +## Interfaces + +Table A.4 – OSx/CBRx\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|--------------------------------------------|----------------------------| +| CBRx_CP:
CBRx_CI_D
CBRx_CI_CK | OSx_AP:
OSx_AI_D | + +## Processes + +The processes associated with the OSx/CBRx\_A\_So function are depicted in Figure A.8. + +**Mod (optical carrier modulation):** See clause 8.11. For parameters of SDH type interfaces, [ITU-T G.957] and [ITU-T G.691] apply. + +**Optical signal pre-conditioning:** Pre-conditioning of the single wavelength optical signal might be required. The specific conditioning processes depend on the OSx interface type (see [ITU-T G.957] and [ITU-T G.691] for SDH type interfaces). + +For SDH type interfaces, the jitter and wander requirements, as defined in clause 9.3.1.1 of [ITU-T G.783] apply. For fibre channel type interfaces, the input clock ranges are defined in Table A.1A and the jitter and wander requirements, as defined in the specifications referenced in Table A.1B, apply. + +![Figure A.8: OSx/CBRx_A_So processes diagram. It shows a grey rectangular box containing two sub-processes: 'Mod' (top) and 'Optical signal pre-conditioning' (bottom, enclosed in a dashed box). Inputs 'CBRx_CP', 'CI_D', and 'CI_CK' point into the 'Mod' process. An arrow points from 'Mod' to 'Optical signal pre-conditioning'. An arrow labeled 'AI_D' and 'OSx_AP' points out from the bottom of the 'Optical signal pre-conditioning' process. The text 'G.798(17)_FA.8' is located to the right of the box.](b98b6c7cbdaae63ffe90f117e507e81a_img.jpg) + +Figure A.8: OSx/CBRx\_A\_So processes diagram. It shows a grey rectangular box containing two sub-processes: 'Mod' (top) and 'Optical signal pre-conditioning' (bottom, enclosed in a dashed box). Inputs 'CBRx\_CP', 'CI\_D', and 'CI\_CK' point into the 'Mod' process. An arrow points from 'Mod' to 'Optical signal pre-conditioning'. An arrow labeled 'AI\_D' and 'OSx\_AP' points out from the bottom of the 'Optical signal pre-conditioning' process. The text 'G.798(17)\_FA.8' is located to the right of the box. + +Figure A.8 – OSx/CBRx\_A\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### A.3.1.2 OSx to CBRx adaptation sink function without FEC (OSx/CBRx\_A\_Sk) (x = 2G5, 10G, 40G, FC-y) + +For SDH OSn type interfaces and fibre channel type interfaces, the information flow and processing of the OSx/CBRx\_A\_Sk function is defined with reference to Figures A.9 and A.10. + +NOTE – For SDH OSM256.4 type interfaces, please see clause A.3.1.4. + +#### Symbol + +![Diagram of the OSx/CBRx_A_Sk function symbol. It shows a trapezoidal block labeled 'OSx/CBRx'. An arrow labeled 'OSx_AP' points into the block from below. An arrow labeled 'CBRx_CP' points out of the block from the top. The diagram is labeled 'G.798(17)_FA.9' at the bottom right.](a815ab84d8edcfc7061d7e8456ac7013_img.jpg) + +Diagram of the OSx/CBRx\_A\_Sk function symbol. It shows a trapezoidal block labeled 'OSx/CBRx'. An arrow labeled 'OSx\_AP' points into the block from below. An arrow labeled 'CBRx\_CP' points out of the block from the top. The diagram is labeled 'G.798(17)\_FA.9' at the bottom right. + +Figure A.9 – OSx/CBRx\_A\_Sk function + +#### Interfaces + +Table A.5 – OSx/CBRx\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------|-----------------------------------------------------------| +| OSx_AP:
OSx_AI_D
OSx_AI_TSF | CBRx_CP:
CBRx_CI_D
CBRx_CI_CK
CBRx_CI_SSF | + +#### Processes + +The processes associated with the OSx/CBRx\_A\_Sk function are depicted in Figure A.10. + +**Optical signal post-conditioning:** Post-conditioning of the single wavelength signal might be required. The specific conditioning processes depend on the OSx interface type (see [ITU-T G.957] and [ITU-T G.691] for SDH type interfaces). + +**DMod (optical carrier demodulation):** See clause 8.11. For parameters of SDH type interfaces, [ITU-T G.957] and [ITU-T G.691] apply. + +**Clock recovery:** The function shall recover the clock signal from the incoming data. For SDH type interfaces, the input clock ranges are defined in Table A.1 and the jitter and wander requirements, as defined in clause 9.3.1.2 of [ITU-T G.783], apply. For fibre channel type interfaces, the input clock ranges are defined in Table A.1A and the jitter and wander requirements, as defined in the specifications referenced in Table A.1B, apply. + +To ensure adequate immunity against the presence of consecutive identical digits (CID) in the signal, the function shall comply with the specification in clause 15.1.4 of [ITU-T G.783] for SDH type interfaces. + +![Figure A.10: OSx/CBRx_A_Sk processes diagram. A grey box labeled 'OSx_AP' contains several components. At the bottom, 'AI_D' and 'AI_TSF' enter from below. 'AI_D' goes to 'Optical signal post-conditioning' (dashed box), which then connects to 'DMod', which connects to 'Clock recovery'. 'AI_TSF' enters from the right and connects to 'Clock recovery'. Above 'Clock recovery' is a 'Replacement signal generator' box. Three signals exit from the top of the box: 'CI_D', 'CI_CK', and 'CI_SSF'. The diagram is labeled 'G.798(17)_FA.10'.](228db097d546afebf934a1befb86a0a6_img.jpg) + +Figure A.10: OSx/CBRx\_A\_Sk processes diagram. A grey box labeled 'OSx\_AP' contains several components. At the bottom, 'AI\_D' and 'AI\_TSF' enter from below. 'AI\_D' goes to 'Optical signal post-conditioning' (dashed box), which then connects to 'DMod', which connects to 'Clock recovery'. 'AI\_TSF' enters from the right and connects to 'Clock recovery'. Above 'Clock recovery' is a 'Replacement signal generator' box. Three signals exit from the top of the box: 'CI\_D', 'CI\_CK', and 'CI\_SSF'. The diagram is labeled 'G.798(17)\_FA.10'. + +**Figure A.10 – OSx/CBRx\_A\_Sk processes** + +**Defects:** None. + +**Consequent actions** + +The OSx/CBRx\_A\_Sk function performs the following consequent actions. + +aSSF $\leftarrow$ AI\_TSF + +aAIS $\leftarrow$ AI\_TSF + +On declaration of aAIS, the function shall output a replacement signal as defined in clause 16.6 of [ITU-T G.709] for SDH type interfaces and in Table A.1B for fibre channel type interfaces within X ms. On clearing aAIS, the replacement signal shall be removed within Y ms, with normal data being output. The values for X and Y are for further study. + +The replacement signal clock start shall be independent from the incoming clock. For the defined values of x, the replacement signal clock has to be within the range defined in Table A.1 for SDH type interfaces and Table A.1A for fibre channel type interfaces. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +**A.3.1.3 OSM256.4 to CBRx adaptation source function** + +The information flow and processing of the OSM256.4/CBRx\_So function is defined with reference to Figures A.11 and A.12. This is a null function connecting the CBRx\_CP output signals to the corresponding OSM256.4\_AP input signals. + +**Symbol** + +![Figure A.11: OSM256.4/CBRx_So function diagram. A central trapezoidal block is labeled 'OSM256.4/CBRx'. An arrow labeled 'CBRx_CP' points into the top of the block. An arrow labeled 'OSM256.4_AP' points out from the bottom of the block. A horizontal arrow labeled 'OSM256.4/CBRx_A_So_MP' points out from the left side of the block. The diagram is labeled 'G.798(17)_FA.11'.](1cf7488717213a910c805cf83ee186ee_img.jpg) + +Figure A.11: OSM256.4/CBRx\_So function diagram. A central trapezoidal block is labeled 'OSM256.4/CBRx'. An arrow labeled 'CBRx\_CP' points into the top of the block. An arrow labeled 'OSM256.4\_AP' points out from the bottom of the block. A horizontal arrow labeled 'OSM256.4/CBRx\_A\_So\_MP' points out from the left side of the block. The diagram is labeled 'G.798(17)\_FA.11'. + +**Figure A.11 – OSM256.4/CBRx\_So function** + +## Interfaces + +**Table A.6 – OSM256.4/CBRx\_So inputs and outputs** + +| Input(s) | Output(s) | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| CBRx_CP:
CBRx_CI_D
CBRx_CI_CK | OSM256.4_AP:
OSM256.4_AI_D
OSM256.4_AI_CK
OSM256.4_AI_FS
OSM256.4/CBRx_A_So_MP:
OSM256.4/CBRx_A_So_MI_cLOF | + +## Processes + +The processes associated with the OSM256.4/CBRx\_So function are depicted in Figure A.12. + +![Figure A.12 – OSM256.4/CBRx_So processes. This block diagram shows the internal signal flow of the OSM256.4/CBRx_So function. Inputs CI_D and CI_CK enter the 'Frame alignment' block. The 'Frame alignment' block outputs dLOF and FS, and provides D and CK signals to the 'Replacement signal generator' and 'AIS insertion' blocks. The 'Replacement signal generator' outputs aAIS to the 'AIS insertion' block. The 'AIS insertion' block outputs AI_FS, AI_D, and AI_CK. The 'Defect correlations' block receives dLOF and outputs MI_cLOF. The 'Consequent actions' block receives dLOF and aAIS, and outputs AL_SSF. The entire process is labeled CBRx_CP at the top and OSM256.4_AP at the bottom. A vertical label on the right reads OSM256.4/CBRx_A_So_MP. A reference G.798(17)_FA.12 is noted at the bottom right.](2bb36c10542436112c2e54d97771bf32_img.jpg) + +Figure A.12 – OSM256.4/CBRx\_So processes. This block diagram shows the internal signal flow of the OSM256.4/CBRx\_So function. Inputs CI\_D and CI\_CK enter the 'Frame alignment' block. The 'Frame alignment' block outputs dLOF and FS, and provides D and CK signals to the 'Replacement signal generator' and 'AIS insertion' blocks. The 'Replacement signal generator' outputs aAIS to the 'AIS insertion' block. The 'AIS insertion' block outputs AI\_FS, AI\_D, and AI\_CK. The 'Defect correlations' block receives dLOF and outputs MI\_cLOF. The 'Consequent actions' block receives dLOF and aAIS, and outputs AL\_SSF. The entire process is labeled CBRx\_CP at the top and OSM256.4\_AP at the bottom. A vertical label on the right reads OSM256.4/CBRx\_A\_So\_MP. A reference G.798(17)\_FA.12 is noted at the bottom right. + +**Figure A.12 – OSM256.4/CBRx\_So processes** + +**Frame Alignment:** The function shall perform frame alignment on the STM-N frame as described in clause 8.2.1 of [ITU-T G.783]. The function is required before the signal can be output in a multi-lane, OSM256.4 format. + +### Defects + +The function shall detect dLOF. + +**dLOF:** See clause 6.2.5.1 of [ITU-T G.783]. + +### Consequent actions + +aAIS ← dLOF + +On declaration of aAIS, the function shall output a replacement signal as defined in clauses 17.2 and 17.9 of [ITU-T G.709] within two frames. On clearing of aAIS the replacement pattern/signal shall be removed within two frames and normal data being output. The replacement signal clock shall be independent from the incoming clock. The replacement signal clock has to be within the range specified by Table 14-9. Jitter and wander requirements, as defined in Annex A of [ITU-T G.8251] (ODCp clock), apply. + +### Defect correlations + +cLOF $\leftarrow$ dLOF + +Performance monitoring: None. + +### A.3.1.4 OSM256.4 to CBRx adaptation sink function + +The information flow and processing of the OSM256.4/CBRx\_A\_Sk function is defined with reference to Figures A.13 and A.14. + +### Symbol + +![Symbol diagram for OSM256.4/CBRx_A_Sk function. A trapezoidal block labeled 'OSM256.4/CBRx' has an input arrow from 'OSM256.4_AP' at the bottom and an output arrow pointing to 'CBRx_CP' at the top. Below the diagram is the text 'G.798(12)-Amd.1(14)_FA.13'.](0823130a6e07569e2fdb6bbdfc355d39_img.jpg) + +G.798(12)-Amd.1(14)\_FA.13 + +Symbol diagram for OSM256.4/CBRx\_A\_Sk function. A trapezoidal block labeled 'OSM256.4/CBRx' has an input arrow from 'OSM256.4\_AP' at the bottom and an output arrow pointing to 'CBRx\_CP' at the top. Below the diagram is the text 'G.798(12)-Amd.1(14)\_FA.13'. + +Figure A.13 – OSM256.4/CBRx\_A\_Sk function + +### Interfaces + +Table A.7 – OSM256.4/CBRx\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------|-----------------------------------------------------------| +| OSM256.4_AP:
OSM256.4_AI_D
OSM256.4_AI_CK
OSM256.4_AI_TSF | CBRx_CP:
CBRx_CI_D
CBRx_CI_CK
CBRx_CI_SSF | + +### Processes + +The processes associated with the OSM256.4/CBRx\_A\_Sk function are depicted in Figure A.14. + +![Process diagram for OSM256.4/CBRx_A_Sk. A large grey rectangle represents the function. At the bottom, three input labels 'AI_D', 'AI_CK', and 'AI_TSF' point to the rectangle. At the top, three output labels 'CI_D', 'CI_CK', and 'CI_SSF' point away from the rectangle. Above the top labels is 'CBRx_CP' and below the bottom labels is 'OSM256.4_AP'. To the right of the rectangle is the text 'G.798(12)-Amd.1(14)_FA.14'.](c40bbeb66e1572660694c68dcb5734e1_img.jpg) + +G.798(12)-Amd.1(14)\_FA.14 + +Process diagram for OSM256.4/CBRx\_A\_Sk. A large grey rectangle represents the function. At the bottom, three input labels 'AI\_D', 'AI\_CK', and 'AI\_TSF' point to the rectangle. At the top, three output labels 'CI\_D', 'CI\_CK', and 'CI\_SSF' point away from the rectangle. Above the top labels is 'CBRx\_CP' and below the bottom labels is 'OSM256.4\_AP'. To the right of the rectangle is the text 'G.798(12)-Amd.1(14)\_FA.14'. + +Figure A.14 – OSM256.4/CBRx\_A\_Sk processes + +Defects: None. + +Consequent actions: None. + +Defect correlations: None. + +**Performance monitoring:** None. + +#### A.3.1.5 OSx to CBRx adaptation source function for 64B/66B encoded clients with FEC (OSx/CBRx-b\_A\_So) (x = FC-y) + +The information flow and processing of the OSx/CBRx-b\_A\_So function is defined with reference to Figures A.15 and A.16. + +##### Symbol + +![Symbol diagram for the OSx/CBRx-b_A_So function. It shows a trapezoidal block labeled 'OSx/CBRx-b'. An arrow labeled 'CBRx_CP' points into the top of the block, and an arrow labeled 'OSx_AP' points out of the bottom. Below the block is the text 'G.798(17)_FA.15'.](9d81a26facbcf05a73cb7c027e66c1c8_img.jpg) + +``` +graph TD; CBRx_CP --> OSx_CBRx_b[OSx/CBRx-b]; OSx_CBRx_b --> OSx_AP; G.798(17)_FA.15 +``` + +Symbol diagram for the OSx/CBRx-b\_A\_So function. It shows a trapezoidal block labeled 'OSx/CBRx-b'. An arrow labeled 'CBRx\_CP' points into the top of the block, and an arrow labeled 'OSx\_AP' points out of the bottom. Below the block is the text 'G.798(17)\_FA.15'. + +**Figure A.15 – OSx/CBRx-b\_A\_So function** + +##### Interfaces + +**Table A.8 – OSx/CBRx-b\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------|----------------------------| +| CBRx_CP:
CBRx_CI_D
CBRx_CI_CK
CBRx_CI_SSF | OSx_AP:
OSx_AI_D | + +##### Processes + +The processes associated with the OSx/CBRx-b\_A\_So function are depicted in Figure A.16. + +**Block alignment:** Block alignment consists of the recovering 64B/66B block lock per the state diagram in Figure 49-14 of [IEEE 802.3]. + +**Transcoder:** Transcoding of the 64B/66B blocks might be required. The specific transcoding processes depend on the CBRx client type, as defined in the specifications referenced in Table A.1B. The transcoder shall convert invalid 66B blocks to an error control block before transcoding. An invalid 66B block is one which does not have a sync header of "01" or "10", or one which has a sync header of "10" and an invalid control block type field. + +**FEC encoder:** The function shall generate and insert the FEC code words. The specific processes and FEC coding scheme depend on the CBRx client type, as defined in the specifications referenced in Table A.1B. + +**Scrambler:** Scrambling of the FEC code words might be required. The specific scrambling process depends on the CBRx client type, as defined in the specifications referenced in Table A.1B. + +**Mod (optical carrier modulation):** See clause 8.11. + +**Optical signal pre-conditioning:** Pre-conditioning of the single wavelength optical signal might be required. The specific conditioning processes depend on the OSx interface type. + +For fibre channel type interfaces, the input clock ranges are defined in Table A.1A and the jitter and wander requirements, as defined in the specifications referenced in Table A.1B, apply. + +![Figure A.16 – OSx/CBRx-b_A_So processes. This block diagram illustrates the signal flow and control logic for the OSx/CBRx-b_A_So function. At the top, three input signals are shown: CI_SSF, CI_D, and CI_CK. CI_SSF and CI_D enter an 'Alignment' block, which outputs 'dLOCA' (defect loss of client alignment) to 'Consequent actions'. CI_CK enters the 'Alignment' block and outputs 'CK' (clock) to the 'Transcoder'. The 'Alignment' block also outputs 'BlockStart' to the 'Replacement signal generator'. The 'Replacement signal generator' outputs a signal to the 'Transcoder'. The 'Transcoder' receives 'BlockStart', 'D' (data), and 'CK' (clock) from the 'Alignment' block and outputs 'BlockStart', 'D', and 'CK' to the 'FEC encoder'. The 'FEC encoder' receives 'BlockStart', 'D', and 'CK' from the 'Transcoder' and outputs 'FECWordStart', 'D', and 'CK' to the 'Scrambler'. The 'Scrambler' receives 'FECWordStart', 'D', and 'CK' from the 'FEC encoder' and outputs 'D' and 'CK' to the 'Mod' block. The 'Mod' block receives 'D' and 'CK' from the 'Scrambler' and outputs a signal to the 'Optical signal pre-conditioning' block (represented by a dashed box). The 'Optical signal pre-conditioning' block outputs 'AI_D' and 'OSx_AP' signals. A dashed line labeled 'aAIS' connects the 'Consequent actions' block to the 'Transcoder'.](d186ab1411a29b6f0938ab43178e9f0d_img.jpg) + +Figure A.16 – OSx/CBRx-b\_A\_So processes. This block diagram illustrates the signal flow and control logic for the OSx/CBRx-b\_A\_So function. At the top, three input signals are shown: CI\_SSF, CI\_D, and CI\_CK. CI\_SSF and CI\_D enter an 'Alignment' block, which outputs 'dLOCA' (defect loss of client alignment) to 'Consequent actions'. CI\_CK enters the 'Alignment' block and outputs 'CK' (clock) to the 'Transcoder'. The 'Alignment' block also outputs 'BlockStart' to the 'Replacement signal generator'. The 'Replacement signal generator' outputs a signal to the 'Transcoder'. The 'Transcoder' receives 'BlockStart', 'D' (data), and 'CK' (clock) from the 'Alignment' block and outputs 'BlockStart', 'D', and 'CK' to the 'FEC encoder'. The 'FEC encoder' receives 'BlockStart', 'D', and 'CK' from the 'Transcoder' and outputs 'FECWordStart', 'D', and 'CK' to the 'Scrambler'. The 'Scrambler' receives 'FECWordStart', 'D', and 'CK' from the 'FEC encoder' and outputs 'D' and 'CK' to the 'Mod' block. The 'Mod' block receives 'D' and 'CK' from the 'Scrambler' and outputs a signal to the 'Optical signal pre-conditioning' block (represented by a dashed box). The 'Optical signal pre-conditioning' block outputs 'AI\_D' and 'OSx\_AP' signals. A dashed line labeled 'aAIS' connects the 'Consequent actions' block to the 'Transcoder'. + +**Figure A.16 – OSx/CBRx-b\_A\_So processes** + +## Defects + +The OSx/CBRx-b\_A\_So function shall detect the loss of client alignment defect (dLOCA). + +**dLOCA:** If 66B block alignment is persistently lost for 3 ms, dLOCA shall be declared. dLOCA shall be cleared immediately when 66B block alignment is recovered. + +## Consequent actions + +The OSx/CBRx-b\_A\_So function shall perform the following consequent action: + +aAIS ← dLOCA + +On declaration of aAIS, the function shall output a replacement signal as defined in Table A.1B for fibre channel type interfaces within X ms. On clearing of aAIS, the replacement signal shall be removed within Y ms, with normal data being output. The values for X and Y are for further study. + +The replacement signal clock start shall be independent from the incoming clock. 66B Block alignment shall be maintained. For the defined values of x, the replacement signal clock has to be within the range defined in Table A.1A for fibre channel type interfaces. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### A.3.1.6 OSx to CBRx adaptation sink function for 64B/66B encoded clients with optional FEC (OSx/CBRx-b\_A\_Sk) (x = FC-y) + +The information flow and processing of the OSx/CBRx-b\_A\_Sk function is defined with reference to Figures A.17 and A.18. + +## Symbol + +![Symbol diagram for OSx/CBRx-b_A_Sk function. A central trapezoidal block labeled 'OSx/CBRx-b' has three connections: an input arrow from the left labeled 'OSx/CBRx-b_A_Sk_MP', an output arrow pointing up labeled 'CBRx_CP', and an input arrow from below labeled 'OSx_AP'. A reference code 'G.798(12)-Amd.2(15)_FA.17' is shown to the right of the block.](3b330f29256259f2a9854f1c371ed269_img.jpg) + +Symbol diagram for OSx/CBRx-b\_A\_Sk function. A central trapezoidal block labeled 'OSx/CBRx-b' has three connections: an input arrow from the left labeled 'OSx/CBRx-b\_A\_Sk\_MP', an output arrow pointing up labeled 'CBRx\_CP', and an input arrow from below labeled 'OSx\_AP'. A reference code 'G.798(12)-Amd.2(15)\_FA.17' is shown to the right of the block. + +Figure A.17 – OSx/CBRx-b\_A\_Sk function + +## Interfaces + +Table A.9 – OSx/CBRx-b\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OSx_AP:
OSx_AI_D
OSx_AI_TSF
OSx/CBRx-b_A_Sk_MP:
OSx/CBRx-b_A_Sk_MI_FECEn
OSx/CBRx-b_A_Sk_MI_1second | CBRx_CP:
CBRx_CI_D
CBRx_CI_CK
CBRx_CI_SSF
OSx/CBRx-b_A_Sk_MP:
OSx/CBRx-b_A_Sk_MI_cLFA
OSx/CBRx-b_A_Sk_MI_pFECcorrErr
OSx/CBRx-b_A_Sk_MI_pFECuncorrErr | + +## Processes + +The processes associated with the OSx/CBRx-b\_A\_Sk function are depicted in Figure A.18. + +If FEC processing is enabled (MI\_FECEn is true), the function shall perform the FEC code word alignment, descrambler, FEC decoder and transcoder processes. Otherwise, the FEC data is ignored and no error correction is performed. + +**FEC code word alignment:** The function shall recover the FEC code word start (FCWS). This process is specific for the CBRx client type, as defined in the specifications referenced in Table A.1B. + +**Descrambler:** Descrambling of the FEC code words might be required. The specific descrambling process depends on the CBRx client type, as defined in the specifications referenced in Table A.1B. + +**FEC decoder:** The function shall extract the FEC data and perform error correction. The specific processes and FEC coding scheme depend on the CBRx client type, as defined in the specifications referenced in Table A.1B. Uncorrectable FEC words shall be replaced with the corresponding number of 66B error control blocks. The number of corrected and uncorrectable errors shall be reported (nFECcorrErr, nFECuncorrErr). + +**Transdecoder:** Transdecoding to 64B/66B blocks might be required. The specific transdecoding processes depend on the CBRx client type, as defined in the specifications referenced in Table A.1B. + +**Optical signal post-conditioning:** Post-conditioning of the single wavelength signal might be required. The specific conditioning processes depend on the OSx interface type. + +**DMod (optical carrier demodulation):** See clause 8.11. + +**Clock recovery:** The function shall recover the clock signal from the incoming data. For fibre channel type interfaces, the input clock ranges are defined in Table A.1A and the jitter and wander requirements, as defined in the specifications referenced in Table A.1B, apply. + +![Figure A.18 – OSx/CBRx-b_A_Sk processes. This block diagram illustrates the internal signal processing flow of the OSx/CBRx-b_A_Sk function. At the bottom, the 'Optical signal post-conditioning' block (dashed box) receives 'AI_D' and 'OSx_AP' inputs and sends data to the 'DMod' block. 'DMod' outputs to the 'Clock recovery' block, which provides 'CK' signals to the 'FEC code word alignment', 'Descrambler', and 'FEC decoder' blocks. The 'FEC code word alignment' block receives 'D' data and 'CK' clock, and outputs 'dLFA' to the 'Defect correlations' block. The 'Defect correlations' block outputs 'MI_cLFA' and 'MI_FECEn'. The 'FEC code word alignment' also outputs 'FCWS' to the 'Descrambler'. The 'Descrambler' outputs 'D' data and 'CK' clock to the 'FEC decoder'. The 'FEC decoder' outputs 'nFECcorrErr' and 'nFECuncorrErr' to the 'Performance monitoring' block. The 'Performance monitoring' block outputs 'MI_1second', 'MI_pFECcorrErr', and 'MI_pFECuncorrErr'. The 'FEC decoder' also outputs 'D' data and 'CK' clock to the 'Transdecoder'. The 'Transdecoder' outputs 'CI_D' and 'CI_CK' signals. A 'Replacement signal generator' block receives 'dLFA' and 'AI_TSF' inputs and outputs a signal to the 'Consequent actions' block. The 'Consequent actions' block also receives 'FECEn' and 'dLFA' inputs and outputs 'CI_SSF'. The entire process is labeled 'OSx/CBRx-b_A_Sk_MP' on the right side. Reference 'G.798(17)_FA.18' is noted at the bottom right of the diagram area.](43aeecf3cbc60c4418d560d8a4512ebb_img.jpg) + +Figure A.18 – OSx/CBRx-b\_A\_Sk processes. This block diagram illustrates the internal signal processing flow of the OSx/CBRx-b\_A\_Sk function. At the bottom, the 'Optical signal post-conditioning' block (dashed box) receives 'AI\_D' and 'OSx\_AP' inputs and sends data to the 'DMod' block. 'DMod' outputs to the 'Clock recovery' block, which provides 'CK' signals to the 'FEC code word alignment', 'Descrambler', and 'FEC decoder' blocks. The 'FEC code word alignment' block receives 'D' data and 'CK' clock, and outputs 'dLFA' to the 'Defect correlations' block. The 'Defect correlations' block outputs 'MI\_cLFA' and 'MI\_FECEn'. The 'FEC code word alignment' also outputs 'FCWS' to the 'Descrambler'. The 'Descrambler' outputs 'D' data and 'CK' clock to the 'FEC decoder'. The 'FEC decoder' outputs 'nFECcorrErr' and 'nFECuncorrErr' to the 'Performance monitoring' block. The 'Performance monitoring' block outputs 'MI\_1second', 'MI\_pFECcorrErr', and 'MI\_pFECuncorrErr'. The 'FEC decoder' also outputs 'D' data and 'CK' clock to the 'Transdecoder'. The 'Transdecoder' outputs 'CI\_D' and 'CI\_CK' signals. A 'Replacement signal generator' block receives 'dLFA' and 'AI\_TSF' inputs and outputs a signal to the 'Consequent actions' block. The 'Consequent actions' block also receives 'FECEn' and 'dLFA' inputs and outputs 'CI\_SSF'. The entire process is labeled 'OSx/CBRx-b\_A\_Sk\_MP' on the right side. Reference 'G.798(17)\_FA.18' is noted at the bottom right of the diagram area. + +**Figure A.18 – OSx/CBRx-b\_A\_Sk processes** + +## Defects + +The OSx/CBRx-b\_A\_Sk function shall detect the loss of FEC word alignment defect (dLFA). + +**dLFA:** The detection of dLFA depends on the CBRx client type, as defined in the specifications referenced in Table A.1B. + +## Consequent actions + +The OSx/CBRx\_A\_Sk function performs the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF or (dLFA and FECEn) + +aAIS $\leftarrow$ AI\_TSF or (dLFA and FECEn) + +On declaration of aAIS, the function shall output a replacement signal as defined in Table A.1B for fibre channel type interfaces within X ms. On clearing of aAIS, the replacement signal shall be removed within Y ms, with normal data being output. The values for X and Y are for further study. + +The replacement signal clock start shall be independent from the incoming clock. For the defined values of x, the replacement signal clock has to be within the range defined in Table A.1A for fibre channel type interfaces. + +### Defect correlations + +The OSx/CBRx-b\_A\_Sk function shall perform the following defect correlation: + +cLFA $\leftarrow$ dLFA and FECEn and (not AI\_TSF) + +**Performance monitoring:** The function shall perform the following performance monitoring primitives processing. The performance monitoring primitives shall be reported to the EMF. + +pFECcorrErr $\leftarrow \sum$ nFECcorrErr + +pFECuncorrErr $\leftarrow \sum$ nFECuncorrErr + +NOTE – During AI\_TSF no corrected or uncorrectable errors shall be counted. + +### A.3.1.7 OSx to CBRx adaptation sink function for 64B/66B encoded clients with mandatory FEC (OSx/CBRx-c\_A\_Sk) (x = FC-y) + +The information flow and processing of the OSx/CBRx\_A\_Sk function is defined with reference to Figures A.19 and A.20. + +### Symbol + +![Diagram of the OSx/CBRx-c_A_Sk function symbol. A central trapezoidal block is labeled 'OSx/CBRx-c'. An arrow labeled 'OSx_AP' points into the block from the bottom. An arrow labeled 'CBRx_CP' points out of the block from the top. A double-headed arrow labeled 'OSx/CBRx-c_A_Sk_MP' is connected to the left side of the block. Below the diagram is the text 'G.798(12)-Amd.2(15)_FA.19'.](5f1f8e1973a0dd08d313a5aab38502ad_img.jpg) + +Diagram of the OSx/CBRx-c\_A\_Sk function symbol. A central trapezoidal block is labeled 'OSx/CBRx-c'. An arrow labeled 'OSx\_AP' points into the block from the bottom. An arrow labeled 'CBRx\_CP' points out of the block from the top. A double-headed arrow labeled 'OSx/CBRx-c\_A\_Sk\_MP' is connected to the left side of the block. Below the diagram is the text 'G.798(12)-Amd.2(15)\_FA.19'. + +Figure A.19 – OSx/CBRx-c\_A\_Sk function + +### Interfaces + +Table A.10 – OSx/CBRx-c\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OSx_AP:
OSx_AI_D
OSx_AI_TSF
OSx/CBRx-c_A_Sk_MP:
OSx/CBRx-c_A_Sk_MI_1second | CBRx_CP:
CBRx_CI_D
CBRx_CI_CK
CBRx_CI_SSF
OSx/CBRx-c_A_Sk_MP:
OSx/CBRx-c_A_Sk_MI_cLFA
OSx/CBRx-c_A_Sk_MI_pFECcorrErr
OSx/CBRx-c_A_Sk_MI_pFECuncorrErr | + +### Processes + +The processes associated with the OSx/CBRx-c\_A\_Sk function are depicted in Figure A.20. + +**FEC code word alignment:** The function shall recover the FEC code word start (FCWS). This process is specific for the CBRx client type, as defined in the specifications referenced in Table A.1B. + +**Descrambler:** Descrambling of the FEC code words might be required. The specific descrambling process depends on the CBRx client type, as defined in the specifications referenced in Table A.1B. + +**FEC decoder:** The function shall extract the FEC data and perform error correction. The specific processes and FEC coding scheme depend on the CBRx client type, as defined in the specifications referenced in Table A.1B. Uncorrectable FEC words shall be replaced with the corresponding number of 66B error control blocks. The number of corrected and uncorrectable errors shall be reported (nFECcorrErr, nFECuncorrErr). + +**Transdecoder:** Transdecoding to 64B/66B blocks might be required. The specific transdecoding processes depend on the CBRx client type, as defined in the specifications referenced in Table A.1B. + +**Optical signal post-conditioning:** Post-conditioning of the single wavelength signal might be required. The specific conditioning processes depend on the OSx interface type. + +**DMod (optical carrier demodulation):** See clause 8.11. + +**Clock recovery:** The function shall recover the clock signal from the incoming data. For fibre channel type interfaces, the input clock ranges are defined in Table A.1A and the jitter and wander requirements, as defined in the specifications referenced in Table A.1B, apply. + +![Block diagram of OSx/CBRx-c_A_Sk processes showing signal flow from OSx_AP to CBRx_CP through various processing blocks including Optical signal post-conditioning, DMod, Clock recovery, FEC code word alignment, Descrambler, FEC decoder, and Transdecoder. It also includes monitoring blocks like Performance monitoring and Defect correlations, and a Replacement signal generator.](637fa2ec2e8639bc53dea306e19b7c05_img.jpg) + +The diagram illustrates the signal processing flow within the OSx/CBRx-c\_A\_Sk processes. The main components and their interactions are as follows: + +- Inputs:** AI\_D and AI\_TSF enter from the bottom (OSx\_AP side). A dashed box labeled "Optical signal post-conditioning" is at the bottom. +- Signal Path:** The signal flows upwards through a series of blocks: "DMod", "Clock recovery", "FEC code word alignment", "Descrambler", "FEC decoder", and "Transdecoder". +- Clock and Control Signals:** + - "Clock recovery" provides "D" and "CK" signals to "FEC code word alignment". + - "FEC code word alignment" provides "FCWS", "D", and "CK" signals to "Descrambler". + - "Descrambler" provides "FCWS", "D", and "CK" signals to "FEC decoder". + - "FEC decoder" provides "FCWS", "D", and "CK" signals to "Transdecoder". + - "Transdecoder" provides "D" and "CK" signals to a "Replacement signal generator". + - The "Replacement signal generator" provides "CI\_D", "CI\_CK", and "CI\_SSF" signals to the top (CBRx\_CP side). +- Monitoring and Correlation:** + - "FEC decoder" outputs "nFECcorrErr" and "nFECuncorrErr" to a "Performance monitoring" block. + - "Performance monitoring" outputs "MI\_1second", "MI\_pFECcorrErr", and "MI\_pFECuncorrErr" to the right (OSx/CBRx-c\_A\_Sk\_MP side). + - "FEC code word alignment" outputs "dLFA" to a "Defect correlations" block. + - "Defect correlations" outputs "MI\_cLFA" to the right. + - Both "Performance monitoring" and "Defect correlations" output "dLFA" and "AI\_TSF" signals to a "Consequent actions" block. + - "Consequent actions" outputs "CI\_SSF" to the top. +- Labels:** The diagram is labeled "CBRx\_CP" at the top and "OSx\_AP" at the bottom. A reference "G.798(17)\_FA.20" is in the bottom right corner. + +Block diagram of OSx/CBRx-c\_A\_Sk processes showing signal flow from OSx\_AP to CBRx\_CP through various processing blocks including Optical signal post-conditioning, DMod, Clock recovery, FEC code word alignment, Descrambler, FEC decoder, and Transdecoder. It also includes monitoring blocks like Performance monitoring and Defect correlations, and a Replacement signal generator. + +Figure A.20 – OSx/CBRx-c\_A\_Sk processes + +## Defects + +The OSx/CBRx-b\_A\_Sk function shall detect the loss of FEC word alignment defect (dLFA). + +**dLFA:** The detection of dLFA depends on the CBRx client type, as defined in the specifications referenced in Table A.1B. + +## Consequent actions + +The OSx/CBRx\_A\_Sk function performs the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF or dLFA + +aAIS $\leftarrow$ AI\_TSF or dLFA + +On declaration of aAIS, the function shall output a replacement signal as defined in Table A.1B for fibre channel type interfaces within X ms. On clearing of aAIS, the replacement signal shall be removed within Y ms, with normal data being output. The values for X and Y are for further study. + +The replacement signal clock start shall be independent from the incoming clock. For the defined values of x, the replacement signal clock has to be within the range defined in Table A.1A for fibre channel type interfaces. + +## Defect correlations + +The OSx/CBRx-c\_A\_Sk function shall perform the following defect correlation: + +cLFA $\leftarrow$ dLFA and (not AI\_TSF) + +**Performance monitoring:** The function shall perform the following performance monitoring primitives processing. The performance monitoring primitives shall be reported to the EMF. + +pFECcorrErr $\leftarrow \sum nFECcorrErr$ + +pFECuncorrErr $\leftarrow \sum nFECuncorrErr$ + +NOTE – During AI\_TSF no corrected or uncorrectable errors shall be counted. + +## Annex B + +### Generic FlexE and FlexO supervision and processes + +(This annex forms an integral part of this Recommendation.) + +#### B.1 Supervision + +##### B.1.1 Defects + +###### B.1.1.1 Alignment supervision + +###### B.1.1.1.1 FlexE overhead Loss of Frame (dLOF) + +FlexE overhead dLOF is generated based on the state of the frame alignment process defined in clause B.2.1.1. + +dLOF shall be declared if the FlexE overhead frame alignment process is in the out-of-frame (OOF) state for 3ms. To provide for the case of intermittent OOFs, the integrating timer shall not be reset to zero until an in-frame (IF) condition persists continuously for 3 ms. + +dLOF shall be cleared when the IF state persists continuously for 3 ms. + +###### B.1.1.1.2 FlexE overhead Loss of Multi-frame (dLOM) + +FlexE overhead dLOM is generated based on the state of the multi-frame alignment process defined in clause B.2.1.2. + +dLOM shall be declared if the multi-frame alignment process is persistently in the out-of-multiframe (OOM) state for 10 ms. + +dLOM shall be cleared immediately when the multi-frame alignment process is in the in-multiframe (IM) state. + +##### B.1.1.2 Group supervision + +###### B.1.1.2.1 Group ID Mismatch (dGIDM) + +dGIDM shall be declared if the accepted GID (AcGID) of any of the group member interfaces is not equal to the expected GID (ExGID). + +dGIDM shall be cleared if the accepted GID of all group member interfaces is equal to the expected GID. + +dGIDM shall be detected within 100 ms of changes to the AcGID. + +###### B.1.1.2.2 FlexO/FlexE Map Mismatch (dFMM) + +The FlexO/FlexE Map mismatch defect of a FlexO group or FlexE (sub)group of p members is based on the comparison of the p AcFMAP values, the p AcIID values and the expected FlexO/FlexE Map (ExFMAP). + +dFMM shall be cleared if + +- the AcFMAP value of each member matches the value of ExFMAP, +- each value of AcIID has the corresponding bit set in ExFMAP, +- every AcIID value is unique. + +Otherwise, dFMM shall be declared. + +dFMM shall be detected within 100 ms of changes to the AcFMAP[1..p] or AcIID[1..p] values. + +## **B.2 Generic processes** + +### **B.2.1 Alignment processes** + +#### **B.2.1.1 FlexE overhead frame alignment** + +The FlexE overhead frame alignment shall be found by searching for FlexE block 1 of the FlexE overhead frame every $(1023 \times 20 + 1) \times 8$ blocks as described in clause 7.3.1 of [OIF FlexE IA]. + +NOTE – The FlexE block 1 of the FlexE overhead frame is encoded as a special ordered set. The sync header is 10, the control block type is 0x4B (ordered set), and the "O" code is 0x5. + +The process has two states, out-of-frame (OOF) and in-frame (IF). The frame alignment start shall be maintained during the OOF state. + +In the OOF state, the frame alignment shall be assumed to be recovered and the IF state shall be entered, when a valid FlexE block 1 is found in two consecutive FlexE overhead frames. + +In the IF state, OOF shall be entered when the FlexE block 1 of the FlexE overhead frame has mismatches on the sync header, control block type or O code fields for 5 occurrences. + +#### **B.2.1.2 FlexE overhead multi-frame alignment** + +The FlexE overhead multi-frame is a sequence of 32 FlexE overhead frames. The Flex overhead multi-frame alignment shall be found based on the overhead multi-frame (OMF) bit in the FlexE overhead. The OMF bit has a value of "0" for the first sixteen overhead frames of the FlexE overhead multi-frame, and a value of "1" for the last sixteen overhead frames of the FlexE overhead multi-frame, as described in clause 7.3.1 of [OIF FlexE IA]. + +The process has two states, out-of-multi-frame (OOM) and in-multi-frame (IM). The multi-frame start shall be maintained during the OOM state. + +In the OOM state, the state will change from OOM to IM upon detecting a "0" to "1" or a "1" to "0" transition of the OMF bit in two consecutive FlexE overhead frames with good CRC. In the IM state, the state shall change from IM to OOM, when the two consecutive FlexE overhead frames where the "0" to "1" or "1" to "0" transition of the OMF bit is expected, have a good CRC, but do not have the expected transition. + +### **B.2.2 Overhead acceptance processes** + +#### **B.2.2.1 Group Identification (GID) acceptance process** + +A new GID value (AcGID) is accepted if a new value of the Group Identification field of the FlexO overhead or the Group Number field of the FlexE overhead is received in an overhead frame with good CRC. + +#### **B.2.2.2 FlexO/FlexE Instance Identification (IID) acceptance process** + +##### **B.2.2.2.1 FlexO IID acceptance process** + +A new IID value (AcIID) is accepted if a new value of the FlexO Instance Identification field of the FlexO overhead is received in an overhead frame with good CRC. + +##### **B.2.2.2.2 FlexE IID acceptance process** + +A new IID value (AcIID) is accepted when the same value of the FlexE Instance Number field of the FlexE overhead is received in two consecutive overhead frames with good CRC. + +### **B.2.2.3 PHY Map acceptance process** + +#### **B.2.2.3.1 FlexO Map acceptance process** + +The 256-bit Map[0:255] is recovered from the MAP field of the FlexO overhead. + +When FlexO overhead frame #i in the 8 frame multi-frame is received with good CRC, the bits AcFMAP[(i-1)×32:(i-1)×32+31] are accepted from the FlexO MAP field. + +#### **B.2.2.3.2 FlexE Map acceptance process** + +The 256-bit Map[0:255] is recovered from the Map field of the FlexE overhead. + +When FlexE overhead frame #i in the 32 frame multi-frame is received with good CRC, the bits AcFMAP[(i-1)×8:(i-1)×8+7] are accepted from the FlexE Map field. + +## Appendix I + +### Applications and functional diagrams + +(This appendix does not form an integral part of this Recommendation.) + +This appendix shows example functional diagrams for a number of OTN and non-OTN interface ports on OTN equipment and a number of OTN interface ports on non-OTN equipment. + +NOTE – The following functional diagrams are for illustrative purposes only. + +#### **I.1 Transparent CBRx tributary interface port with optional SDH RS non-intrusive monitor on OTN equipment** + +NOTE – A generic, bit rate non-specific model is presented. Actual interface ports will be bit rate specific; e.g., 10 Gbit/s (n = 64, x = 10G). + +Figure I.1 shows the equipment functions for this application. The processing down to the ODUsk layer, in the direction of the line interface, is shown. + +The following operations are performed: + +- termination of the ITU-T G.957/ITU-T G.691 or ITU-T G.695 optical signal; +- optional RSn non-intrusive monitoring in ingress and egress directions; +- mapping of CBR signal into the ODUsk; +- termination of ODUsk path overhead; +- termination of up to three levels of ODUsk TCM overhead in line port direction. + +![Figure I.1: Transparent CBRx tributary interface port with optional SDH RS non-intrusive monitor on OTN equipment. The diagram shows two main signal paths. The left path represents the ingress direction, starting from an optical signal (STLn.m or STM-n) through an OSn layer, then an OSn/RSn or OSn/CBRx layer, and finally an RSn layer. The right path represents the egress direction, starting from an OTN signal (ODUk) through an ODUk/ODUk layer, then an ODUk layer, and finally an ODUkP/CBRx or ODUkP/RSn layer. Both paths include non-intrusive monitoring points for the RSn layer. The diagram is labeled with various interfaces and layers, and includes a reference to G.798(17)_Fl.1.](ea4d1f05669860c1f910e6cb1e7a22b6_img.jpg) + +STLn.m (ITU-T G.695) +STM-n (ITU-T G.957/ITU-T G.691) + +G.798(17)\_Fl.1 + +Figure I.1: Transparent CBRx tributary interface port with optional SDH RS non-intrusive monitor on OTN equipment. The diagram shows two main signal paths. The left path represents the ingress direction, starting from an optical signal (STLn.m or STM-n) through an OSn layer, then an OSn/RSn or OSn/CBRx layer, and finally an RSn layer. The right path represents the egress direction, starting from an OTN signal (ODUk) through an ODUk/ODUk layer, then an ODUk layer, and finally an ODUkP/CBRx or ODUkP/RSn layer. Both paths include non-intrusive monitoring points for the RSn layer. The diagram is labeled with various interfaces and layers, and includes a reference to G.798(17)\_Fl.1. + +**Figure I.1 – Transparent CBRx tributary interface port with optional SDH RS non-intrusive monitor on OTN equipment** + +## I.2 OTU tributary interface port on OTN equipment + +NOTE – A generic, bit rate non-specific model is presented. Actual interface ports will be bit rate specific; e.g., 10 Gbit/s (m = 2). + +Figure I.2 shows the equipment functions for this application. The processing down to the ODUk layer, in the direction of the line interface, is shown. + +The following operations are performed: + +- termination of the ITU-T G.959.1 optical signal; +- termination of OTUk section overhead; +- termination of up to three levels of ODUk TCM overhead in tributary port direction; +- ODUkP non-intrusive monitoring in ingress and egress directions; + +- termination of up to three levels of ODUk TCM overhead in the line port direction. + +![Diagram of OTU tributary interface port on OTN equipment showing signal flow and monitoring points.](7aaba112378eb1ada76b4c7ae2f7ab83_img.jpg) + +The diagram illustrates the internal structure of an OTN equipment's OTU tributary interface port. It shows two parallel signal paths within a yellow-shaded area, representing the equipment's internal processing. Both paths start from the bottom with an **OTUk (ITU-T G.959.1)** signal entering the equipment. The signal then passes through an **OTSiG** interface (indicated by a dashed circle and the number 1), followed by an **OTSi** block, an **OTSi/OTUk** block, and an **OTUk** block. Above these are several layers of **ODUk** processing, each consisting of an **ODUk** block, an **ODUk/ODUk** block, and an **ODUk\_TCMC** block. The text **ODUk\_CI** is used to label the interfaces between these blocks. At the top of the internal processing, there are two **ODUkP** blocks, with the text **ODUkP non-intrusive monitoring** between them. A horizontal line connects these two blocks. The signal then exits the equipment through the top of the yellow area. A label **G.798(17)-Amd.3(21)\_FI.2** is present in the bottom right of the yellow area. A text label **To/from ODUk\_C or OTUk[V]/ODUk\_A** is located near the bottom right of the internal processing section. + +Diagram of OTU tributary interface port on OTN equipment showing signal flow and monitoring points. + +Figure I.2 – OTU tributary interface port on OTN equipment + +### **I.3 Selectable CBRx/OTUk tributary interface port on OTN equipment** + +NOTE – A generic, bit rate non-specific model is presented. Actual interface ports will be bit rate specific; e.g., 10 Gbit/s (n = 64, x = 10G). + +As the optical interfaces for CBRx (STM-n) and OTUk interfaces are similar, it is possible to build equipment that can switch the processing between the two signals at the same tributary port. This is a combination of the two applications defined above. Depending on the selected interface mode, one of two function sets is active. + +Figure I.3 shows the equipment functions for this application. The processing down to the ODuk layer, in the direction of the line interface, is shown. + +The following operations, independent of the interface mode, are performed: + +- termination of up to three levels of ODuk TCM overhead in the line port direction; +- termination of OTUk section overhead. + +The following operations, specific to the OTUk mode, are performed: + +- termination of up to three levels of ODuk TCM overhead in tributary port direction; +- ODukP non-intrusive monitoring in ingress and egress directions. + +The following operations, specific to the CBRx mode, are performed: + +- optional RSn non-intrusive monitoring in ingress and egress directions; +- mapping of CBR signal into the ODuk; +- termination of ODuk path overhead. + + + +#### I.4 OTU interface ports on non-OTN equipment + +OTN interfaces can be used in non-OTN equipment in the same way as SDH interfaces in non-SDH equipment (e.g., STM-n interfaces for IP routers and IP switches). Figure I.4 shows two examples, an OTU2 interface port on an IP/Ethernet network element and an OTU3 interface port on an SDH network element: + +The OTU2 interface port on Ethernet equipment supports: + +- mapping and multiplexing of Ethernet MAC frames into the ODU2 using GFP-F; +- termination of ODU2 path overhead; +- termination of OTU2 section overhead; +- termination of the ITU-T G.959.1 optical signal. + +The OTU3 interface port on SDH equipment supports: + +- mapping and multiplexing of the STM-256 signal (RS256 layer) into the ODU3; +- termination of ODU3 path overhead; +- termination of up to one level of ODU3 TCM overhead; +- termination of OTU3 section overhead; +- termination of the ITU-T G.959.1 optical signal. + +![Diagram showing the internal structure of OTU2 and OTU3 interface ports on non-OTN equipment.](d94747f06bbc2d98d92f9ca113ab737e_img.jpg) + +The diagram illustrates the internal signal processing paths for two types of OTN interfaces on non-OTN equipment, both shown within yellow rectangular boxes. + +**Left Box (OTU2 on Ethernet equipment):** Labeled "To/from ETH\_C" at the top. The signal flow from top to bottom is: ODU2P/ETH (trapezoid), ODU2P (triangle), ODU2\_CI (text), OTU2/ODU2 (trapezoid), OTU2 (triangle), OTU2\_CI (text), OTSi/OTU2 (trapezoid), OTSi (triangle), OTSIG (text with a dashed circle and "1"). The bottom label is "OTU2 (ITU-T G.959.1)". + +**Right Box (OTU3 on SDH equipment):** Labeled "To/from RS\_TT" at the top. The signal flow from top to bottom is: ODU3P/RS256 (trapezoid), ODU3P (triangle), ODU3\_CI (text), ODU3T/ODU3 (trapezoid), OTU3T (triangle), ODU3\_CI (text), OTU3/ODU3 (trapezoid), OTU3 (triangle), OTU3\_CI (text), OTSi/OTU3 (trapezoid), OTSi (triangle), OTSIG (text with a dashed circle and "1"). A vertical box labeled "ODUk\_TCMC" is connected to the ODU3T/ODU3 and OTU3T stages. The bottom label is "OTU3 (ITU-T G.959.1)". + +G.798(17)-Amd.3(21)\_FI.4 + +Diagram showing the internal structure of OTU2 and OTU3 interface ports on non-OTN equipment. + +Figure I.4 – OTU interface ports on non-OTN equipment + +For the above applications without ODUk TCM processing, the OTUk/ODUk overhead has the following fields in use as a minimum (see Figure I.5): + +- client-specific overhead if applicable; +- OPUk payload type in the payload structure identifier (PSI); +- ODUk path monitoring (PM) overhead; +- OTUk section monitoring (SM) overhead; +- frame alignment (FAS, MFAS). + +The other overhead fields are set to all-ZEROs. + +![Figure I.5: Minimum OTUk/ODUk overhead diagram. A table showing the structure of the overhead with 16 columns (1-16) and 4 rows (1-4). Row 1: FAS (columns 1-6), MFAS (column 7), SM (columns 8-10), columns 11-14 are All-ZEROs. Row 2: columns 1-2 are All-ZEROs, column 3 is All-ZEROs, columns 4-6 are All-ZEROs, columns 7-10 are All-ZEROs, column 11 is All-ZEROs, column 12 is All-ZEROs, column 13 is All-ZEROs, column 14 is All-ZEROs. Row 3: columns 1-2 are All-ZEROs, columns 3-6 are All-ZEROs, columns 7-10 are All-ZEROs, PM (columns 11-12), columns 13-14 are All-ZEROs. Row 4: columns 1-2 are All-ZEROs, columns 3-6 are All-ZEROs, columns 7-10 are All-ZEROs, columns 11-14 are All-ZEROs, PSI (column 15), column 16 is All-ZEROs. To the right of the table, 'Client specific' is labeled for rows 1-3, 'OPUk payload' for row 1, and 'OTUk FEC' for row 4. A legend indicates that grey cells represent the 'All-ZEROs pattern'. Source: G.798(12)_FI.5](b56ccd10a090e772debb888ae457727b_img.jpg) + +Figure I.5: Minimum OTUk/ODUk overhead diagram. A table showing the structure of the overhead with 16 columns (1-16) and 4 rows (1-4). Row 1: FAS (columns 1-6), MFAS (column 7), SM (columns 8-10), columns 11-14 are All-ZEROs. Row 2: columns 1-2 are All-ZEROs, column 3 is All-ZEROs, columns 4-6 are All-ZEROs, columns 7-10 are All-ZEROs, column 11 is All-ZEROs, column 12 is All-ZEROs, column 13 is All-ZEROs, column 14 is All-ZEROs. Row 3: columns 1-2 are All-ZEROs, columns 3-6 are All-ZEROs, columns 7-10 are All-ZEROs, PM (columns 11-12), columns 13-14 are All-ZEROs. Row 4: columns 1-2 are All-ZEROs, columns 3-6 are All-ZEROs, columns 7-10 are All-ZEROs, columns 11-14 are All-ZEROs, PSI (column 15), column 16 is All-ZEROs. To the right of the table, 'Client specific' is labeled for rows 1-3, 'OPUk payload' for row 1, and 'OTUk FEC' for row 4. A legend indicates that grey cells represent the 'All-ZEROs pattern'. Source: G.798(12)\_FI.5 + +Figure I.5 – Minimum OTUk/ODUk overhead + +### I.5 Multi-channel interface port with 3-R regeneration functionality for an ODUk connection function + +Figure I.6 shows the equipment functions for this application. The processing up to the ODUk layer is shown. A vendor-specific OTUkV signal is used in the example. + +The multi-channel interface port supports: + +- termination of the optical DWDM signal; +- termination of the OTS-O and OMS-O; +- wavelength multiplexing and demultiplexing; +- termination of the OTSiG-O; +- termination of OTUkV section overhead; +- termination of up to three levels of ODUk TCM overhead; +- ODUkP non-intrusive monitoring in ingress and egress directions; +- ODUk cross-connection. + +![Functional block diagram of a multi-channel interface port with 3-R regeneration functionality for an ODUk connection function. The diagram shows signal flow from external sources through various ODUk and OTUk processing stages, including TCMC and CI functions, down to an optical section with amplifiers and filters, ending at a media element.](4eda1b9e9c4f581b9747ffacabeae936_img.jpg) + +``` + + graph TD + Top[To/from ODUkP_TT, OTUk[V]/ODUk_A, ODUkT/ODUk_A, ODUkT_TT] --> ODUk_Oval((ODUk)) + ODUk_Oval --> ODUkT1[ODUkT] + ODUk_Oval --> ODUkT2[ODUkT] + ODUkT1 --> ODUk_CI1[ODUk_CI] + ODUk_CI1 --> ODUkT_ODUk1[ODUkT/ODUk] + ODUkT_ODUk1 --> ODUkT3[ODUkT] + ODUkT3 --> ODUk_CI2[ODUk_CI] + ODUkT_ODUk1 --- TCMC1[ODUk_TCMC] + ODUk_CI2 --> ODUkT_ODUk2[ODUkT/ODUk] + ODUkT_ODUk2 --- TCMC2[ODUk_TCMC] + ODUkT_ODUk2 --> ODUkT4[ODUkT] + ODUkT4 --> ODUk_CI3[ODUk_CI] + ODUk_CI3 --> ODUkT_ODUk3[ODUkT/ODUk] + ODUkT_ODUk3 --- TCMC3[ODUk_TCMC] + ODUkT_ODUk3 --> ODUkT5[ODUkT] + ODUkT5 --> ODUk_CI4[ODUk_CI] + ODUk_CI4 --> OTUkV_ODUk[OTUkV/ODUk] + OTUkV_ODUk --> OTUkV[OTUkV] + OTUkV --> OTUk_CI[OTUk_CI] + OTUk_CI --> OTSiA_OTUkV[OTSiA/OTUkV] + OTSiA_OTUkV --> AI_TSF[AI_TSF] + OTSiA_OTUkV --> OTSi[OTSi] + OTSiA_OTUkV --> OTSiG_O[OTSiG-O] + OTSi --> OTSiG[OTSiG] + OTSiG_O --> OTSiA[OTSiA] + OTSiA --> OTSiA_OCh_Oval((OTSiA | OCh)) + + subgraph Media_Element [Media element] + OTSiA_OCh_Oval --> OTSi_filter[OTSi filter] + OTSi_filter --> Optical_amp[Optical amplifier] + Optical_amp --> OSC_filter[OSC filter] + + OTSiA_OCh_Oval --> OMS_O_OTSiG[OMS-O/OTSiG | OCh-O] + OMS_O_OTSiG --> OMS_O[OMS-O] + OMS_O --> OMS_O_CI[OMS-O_CI] + OMS_O_CI --> OTS_O_OMS_O[OTS-O/OMS-O] + OTS_O_OMS_O --> OTS_O[OTS-O] + OTS_O --> OTS_O_CI[OTS-O_CI] + OTS_O_CI --> OSC_OTS_O[OSC/OTS-O] + OSC_OTS_O --> OSC[OSC] + OSC --> OTSi_OSC[OTSi/OSC] + OTSi_OSC --> OTSi_Bottom[OTSi] + + OMS_P_OPM[OMS-P OPM] -- OMS-P_LOS --> OMS_O + OTS_P_OPM[OTS-P OPM] -- OTS-P_LOS --> OTS_O + end + + Media_Element --- MC_Interface[Multi-channel interface] + +``` + +The diagram illustrates the functional architecture of a multi-channel interface port. At the top, multiple input paths are labeled "To/from ODUkP\_TT, OTUk[V]/ODUk\_A, ODUkT/ODUk\_A, ODUkT\_TT". These connect to a central "ODUk" processing block. Below this, the signal path descends through a series of stages: + - ODUkT / ODUkT blocks with associated "ODUk\_CI" labels. + - ODUkT/ODUk blocks, each followed by an "ODUk\_TCMC" (Tandem Connection Monitoring Control) block. + - ODUkT / ODUkT blocks with "ODUk\_CI" labels. + - ODUkT/ODUk blocks, each followed by an "ODUk\_TCMC" block. + - ODUkT / ODUkT blocks with "ODUk\_CI" labels. + - OTUkV/ODUk blocks, followed by "OTUkV" blocks and "OTUk\_CI" labels. + - OTSiA/OTUkV blocks, followed by "AI\_TSF" and "OTSiG" blocks. + The signals then enter a section labeled "OTSiA | OCh". This section includes: + - An "Optical amplifier" block connected to "OTSi filter" and "OSC filter" blocks. + - "OMS-P OPM" and "OTS-P OPM" (Optical Monitoring Point) blocks providing "OMS-P\_LOS" and "OTS-P\_LOS" (Loss of Signal) information. + - Downstream processing: "OMS-O/OTSiG | OCh-O" → "OMS-O" → "OMS-O\_CI" → "OTS-O/OMS-O" → "OTS-O" → "OTS-O\_CI" → "OSC/OTS-O" → "OSC" → "OTSi/OSC" → "OTSi". + The entire assembly is connected to a "Media element" at the bottom, and the interface is labeled "Multi-channel interface". The diagram is identified by the code "G.798(17)-Amd.3(21)\_Fl.6". + +Functional block diagram of a multi-channel interface port with 3-R regeneration functionality for an ODUk connection function. The diagram shows signal flow from external sources through various ODUk and OTUk processing stages, including TCMC and CI functions, down to an optical section with amplifiers and filters, ending at a media element. + +**Figure I.6 – Multi-channel interface port with 3-R regeneration functionality for an ODUk connection function** + +## **Appendix II** + +### **Blank appendix** + +(This appendix does not form an integral part of this Recommendation.) + +This appendix is intentionally left blank. + +## Appendix III + +### Performance of processes + +(This appendix does not form an integral part of this Recommendation.) + +#### III.1 Introduction + +This appendix provides information on the performance of some processes such as defect detection and frame alignment. + +#### III.2 OTuk frame alignment process + +##### III.2.1 False out-of-frame events + +False out-of-frame events will occur whenever the in-frame state is lost due to the line bit error rate. This event is related to the probability $P_{wFAS}$ of receiving a corrupted FAS, which is equal to: + +$$P_{wFAS} = 1 - (1 - \varepsilon)^{FASL} \cong \varepsilon \times FASL$$ + +Where $\varepsilon$ is the line bit error rate, with Poisson distribution, and FASL is the number of bits of the FAS to be checked. The probability $P_{fOOF}$ that the system will detect an OOF state coincides with the probability that $\alpha$ consecutive FAS are received. It means that: + +$$P_{fOOF} = P_{wFAS}^{\alpha} \cong (\varepsilon \times FASL)^{\alpha}$$ + +It shall be noted that such a probability of occurrence is directly proportional to the FAS length and inversely proportional to the number of pre-alarm states (i.e., $\alpha - 1$ ) defined in the alignment process. + +The average time between two false out-of-frame events is defined as follows: + +$$T_{fOOF} = \frac{T_{frame}}{P_{fOOF}}$$ + +##### III.2.2 Minimum average time between false out-of-frame events + +It is not possible to give the exact expression for the minimum average time between two out-of-frame events, due to it being a stochastic process. It is instead possible to give an approximate value for it. Given that the distribution of the OOF events is Poisson-like, it is possible to evaluate the minimum interval between two events with a given probability of occurrence. In other words, assuming that the probability of occurrence of an out-of-frame event in an interval shorter than $T_{min}$ is $P[t \leq T_{min}] = p$ , it can be demonstrated that: + +$$T_{min} = -T_{OOF} \times \ln(1 - p)$$ + +With $p = 10^{-3}$ the minimum average time between false OOF events results: $T_{min} \cong T_{OOF} \times 10^{-3}$ . + +Figure III.1 shows the numerical results. + +![Figure III.1: Minimum average time between false out-of-frame events. The graph plots 'Minimum average time between two OOF events (minutes)' on the y-axis (0 to 30) against 'Line BER (10^-3)' on the x-axis (3 to 3.8). Three curves are shown: OTU1 (orange dashed), OTU2 (blue dash-dot), and OTU3 (green solid). A horizontal purple line at 6 minutes is labeled '6 min'. The curves show that as BER increases, the minimum average time between OOF events decreases. OTU1 reaches 6 minutes at approximately BER 3.35, OTU2 at approximately 3.55, and OTU3 at approximately 3.7. A small label 'G.798(12)_FIII.1' is in the bottom right corner.](e7b45a567404ef205acf9b0ae262216f_img.jpg) + +Figure III.1: Minimum average time between false out-of-frame events. The graph plots 'Minimum average time between two OOF events (minutes)' on the y-axis (0 to 30) against 'Line BER (10^-3)' on the x-axis (3 to 3.8). Three curves are shown: OTU1 (orange dashed), OTU2 (blue dash-dot), and OTU3 (green solid). A horizontal purple line at 6 minutes is labeled '6 min'. The curves show that as BER increases, the minimum average time between OOF events decreases. OTU1 reaches 6 minutes at approximately BER 3.35, OTU2 at approximately 3.55, and OTU3 at approximately 3.7. A small label 'G.798(12)\_FIII.1' is in the bottom right corner. + +**Figure III.1 – Minimum average time between false out-of-frame events** + +### III.2.3 False in-frame events + +The probability for false in-frame alignment can be obtained noting that the FAS is searched for up to one frame (FL bit long) with FL-1 possibilities for a false (simulated) FAS and confirmed the following $\delta$ frames. Given the equi-probability of receiving the symbol '0' or symbol '1', it is clear that the simulation of FAS only depends on FAS length. In fact, it results: + +$$P_{fFAS} = \left(\frac{1}{2}\right)^{FASL}$$ + +False frame recovery probability can be defined as: + +$$P_{ff} = 1 - (1 - P_{fFAS})^{FL-1}$$ + +The resulting probability for the false in-frame event thus results: + +$$P_{fIF} = P_{ff} \times P_{fFAS}^{\delta}$$ + +The resulting rate of false frame recovery occurrence depends on frame length and is equal to: + +$$T_{fIF} = \frac{T_{frame}}{P_{fIF}}$$ + +### III.2.4 Frame alignment time + +The frame alignment time is the time needed to reach the in-frame state starting from out-of-frame state. + +In case of no FAS simulation, it is clear that this time is $T_{frame} \times (1 + \delta)$ . Otherwise, the detection of a false FAS will start an alignment process that will lead inevitably to OOF state. This time is taken into account in the above defined relation with an aleatory variable, $H$ , depending on false frame alignment probability; that means: + +$$T_{IF} = T_{frame} \times (1 + \delta + H)$$ + +The value of the variable $H$ is approximated by: + +$$H = P_{fFAS} \times FASL$$ + +It shall be noted that in practice the frame alignment time is not affected by the false alignment occurrence. It means that, in any case, the in-frame state will be reached in two periods of the OTUk frame. + +### III.3 STAT acceptance process and related defect detection + +#### III.3.1 Average acceptance, raising and clearing time + +The average acceptance time for the STAT field can be calculated using Equation 33 of [b-Choi] as the STAT acceptance procedure is analogous to the misframe declaration procedure in Figure 7 of [b-Choi] by reading $p_d$ as probability for a disturbed STAT value. + +**Table III.1 – Average STAT acceptance time** + +| BER | ODU frames | | Time ( $\mu\text{s}$ ) | | | | | | | +|---------|------------|--------|------------------------|-------|------|-------|------|------|-------| +| | X = 3 | X = 15 | ODU0 | ODU1 | ODU2 | ODU2e | ODU3 | ODU4 | ODUCn | +| 1.0E-03 | 3.02 | 15.37 | 296.8 | 147.8 | 36.8 | 35.5 | 9.2 | 3.5 | 17.9 | +| 1.0E-04 | 3.00 | 15.04 | 295.2 | 147.0 | 36.6 | 35.3 | 9.1 | 3.5 | 17.5 | +| 1.0E-05 | 3.00 | 15.00 | 295.1 | 146.9 | 36.6 | 35.3 | 9.1 | 3.5 | 17.4 | +| 1.0E-06 | 3.00 | 15.00 | 295.1 | 146.9 | 36.6 | 35.3 | 9.1 | 3.5 | 17.4 | + +The average dAIS, dOCI, dLTC, dLCK and dIAE raising/clearing time is equal to the average acceptance time. + +#### III.3.2 Mean time between false OTUCn dAIS, ODUP/T dAIS and ODU T dIAE defects due to bit errors assuming a transmitted STAT value of "001" (normal path signal) + +$$p_d(\text{false dAIS}) = (\text{BER}^2 \cdot (1 - \text{BER}))^X$$ + +where X is the number of consecutive STAT fields for acceptance (X = 3 for ODUk, X = 15 for ODUCn). + +The mean number of frames between false defects is approximately the reciprocal of $p_d$ : $t_{dm} = 1/p_d$ . + +**Table III.2 – Mean time between false ODUCn dAIS, ODUP/T dAIS and ODUT dIAE defects** + +| BER | ODU frames | | Time (year) | | | | | | | +|---------|------------|----------|-------------|---------|---------|---------|---------|---------|----------| +| | X=3 | X=15 | ODU0 | ODU1 | ODU2 | ODU2e | ODU3 | ODU4 | ODUCn | +| 1.0E-03 | 1.0E+18 | 1.0E+90 | 3.1E+06 | 1.6E+06 | 3.9E+05 | 3.7E+05 | 9.7E+04 | 3.7E+04 | 3.7E+76 | +| 1.0E-04 | 1.0E+24 | 1.0E+120 | 3.1E+12 | 1.6E+12 | 3.9E+11 | 3.7E+11 | 9.6E+10 | 3.7E+10 | 3.7E+106 | +| 1.0E-05 | 1.0E+30 | 1.0E+150 | 3.1E+18 | 1.6E+18 | 3.9E+17 | 3.7E+17 | 9.6E+16 | 3.7E+16 | 3.7E+136 | +| 1.0E-06 | 1.0E+36 | 1.0E+180 | 3.1E+24 | 1.6E+24 | 3.9E+23 | 3.7E+23 | 9.6E+22 | 3.7E+22 | 3.7E+166 | + +#### III.3.3 Mean time between false ODU dOCI defects due to bit errors assuming a transmitted STAT value of "001" (normal path signal) + +$$p_d(\text{false dOCI}) = (\text{BER}^3)^X$$ + +where X is the number of consecutive STAT fields for acceptance (X = 3 for ODUk, X = 15 for ODUCn). + +The mean number of frames between false defects is approximately the reciprocal of $p_d$ : $t_{dm} = 1/p_d$ . + +**Table III.3 – Mean time between false ODU dOCI defects** + +| BER | ODU frames | | Time (year) | | | | | | | +|---------|------------|----------|-------------|---------|---------|---------|---------|---------|----------| +| | X=3 | X=15 | ODU0 | ODU1 | ODU2 | ODU2e | ODU3 | ODU4 | ODUCn | +| 1.0E-03 | 1.0E+27 | 1.0E+135 | 3.1E+15 | 1.6E+15 | 3.9E+14 | 3.7E+14 | 9.6E+13 | 3.7E+13 | 3.7E+121 | +| 1.0E-04 | 1.0E+36 | 1.0E+180 | 3.1E+24 | 1.6E+24 | 3.9E+23 | 3.7E+23 | 9.6E+22 | 3.7E+22 | 3.7E+166 | +| 1.0E-05 | 1.0E+45 | 1.0E+225 | 3.1E+33 | 1.6E+33 | 3.9E+32 | 3.7E+32 | 9.6E+31 | 3.7E+31 | 3.7E+211 | +| 1.0E-06 | 1.0E+54 | 1.0E+270 | 3.1E+42 | 1.6E+42 | 3.9E+41 | 3.7E+41 | 9.6E+40 | 3.7E+40 | 3.7E+256 | + +### III.3.4 Mean time between false ODUT dLTC and ODUP/T dLCK defects due to bit errors assuming a transmitted STAT value of "001" (normal path signal) + +$$p_d(\text{false dLTC, dLCK}) = (\text{BER} \cdot (1 - \text{BER})^2)^X$$ + +where X is the number of consecutive STAT fields for acceptance (X = 3 for ODUk, X = 15 for ODUCn). + +The mean number of frames between false defects is approximately the reciprocal of $p_d$ : $t_{dm} = 1/p_d$ . + +**Table III.4 – Mean time between false ODUkTdLTC and ODUP/TdLCK defects** + +| BER | | 1.0E-03 | 1.0E-04 | 1.0E-05 | 1.0E-06 | +|------------|------|---------------|---------------|---------------|---------------| +| ODU frames | X=3 | 1.01E+09 | 1.00E+12 | 1.00E+15 | 1.00E+18 | +| ODU0 | | 27.5 h | 3,1 years | 3.1E+03 years | 3.1E+06 years | +| ODU1 | | 13.7 h | 1.6 years | 1.6E+03 years | 1.6E+06 years | +| ODU2 | | 3.4 h | 3.9E-01 years | 3.9E+02 years | 3.9E+05 years | +| ODU2e | | 3.3 h | 3.7E-01 years | 3.7E+02 years | 3.7E+05 years | +| ODU3 | | 0.8 h | 843.6 h | 9.6E+01 years | 9.6E+04 years | +| ODU4 | | 0.3 h | 324.6 h | 3.7E+01 years | 3.7E+04 years | +| ODU frames | X=15 | 1.03E+45 | 1.00E+60 | 1.00E+75 | 1.00E+90 | +| ODUCn | | 3.8E+31 years | 3.7E+46 years | 3.7E+61 years | 3.7E+76 years | + +## III.4 OTU dIAE, OTU dBDI, ODU dBDI detection + +### III.4.1 Average raising and clearing time + +The average raising/clearing delay can be calculated using Equation 33 of [b-Choi] as the detection procedure is analogous to the misframe declaration procedure in Figure 7 of [b-Choi] by reading $p_d$ as probability for a disturbed value. + +**Table III.5 – Average OTU dIAE, ODU dBDI, ODU dBDI raising/clearing time** + +| BER | OTU/ODU frames | Time (μs) | | | | | | | +|---------|----------------|-----------|-------|------|-------|------|------|-------| +| | | ODU0 | ODU1 | ODU2 | ODU2e | ODU3 | ODU4 | ODUCn | +| 1.0E-03 | 5.02 | 493.2 | 245.6 | 61.1 | 59.0 | 15.2 | 5.9 | 5.8 | +| 1.0E-04 | 5.00 | 491.9 | 244.9 | 61.0 | 58.9 | 15.2 | 5.8 | 5.8 | +| 1.0E-05 | 5.00 | 491.8 | 244.9 | 61.0 | 58.8 | 15.2 | 5.8 | 5.8 | +| 1.0E-06 | 5.00 | 491.8 | 244.9 | 61.0 | 58.8 | 15.2 | 5.8 | 5.8 | + +### III.4.2 Mean time between false defects due to bit errors + +$$p_d(\text{false dBDI}) = \text{BER}^X$$ + +where X is the number of consecutive fields for acceptance ( $X = 5$ ). + +The mean number of frames between false defects is approximately the reciprocal of $p_d$ : $t_{dm} = 1/p_d$ . + +**Table III.6 – Mean time between false OTU dIAE, OTUk dBDI, ODU dBDI defects** + +| BER | OTU/ODU frames | Time (year) | | | | | | | +|---------|----------------|-------------|---------|---------|---------|---------|---------|---------| +| | | ODU0 | ODU1 | ODU2 | ODU2e | ODU3 | ODU4 | ODUCn | +| 1.0E-03 | 1.00E+15 | 3.1E+03 | 1.6E+03 | 3.9E+02 | 3.7E+02 | 9.6E+01 | 3.7E+01 | 3.7E+01 | +| 1.0E-04 | 1.00E+20 | 3.1E+08 | 1.6E+08 | 3.9E+07 | 3.7E+07 | 9.6E+06 | 3.7E+06 | 3.7E+06 | +| 1.0E-05 | 1.00E+25 | 3.1E+13 | 1.6E+13 | 3.9E+12 | 3.7E+12 | 9.6E+11 | 3.7E+11 | 3.7E+11 | +| 1.0E-06 | 1.00E+30 | 3.1E+18 | 1.6E+18 | 3.9E+17 | 3.7E+17 | 9.6E+16 | 3.7E+16 | 3.7E+16 | + +## III.5 PT acceptance process and ODUPdPLM detection + +### III.5.1 Average acceptance, raising and clearing time + +The average acceptance time for the PT field can be calculated using Equation 33 of [b-Choi] as the PT acceptance procedure is analogous to the misframe declaration procedure in Figure 7 of [b-Choi] by reading $p_d$ as probability for a disturbed PT value. + +**Table III.7 – Average PT acceptance time** + +| BER | ODU multiframes | Time (ms) | | | | | | | +|---------|-----------------|-----------|------|------|-------|------|------|-------| +| | | ODU0 | ODU1 | ODU2 | ODU2e | ODU3 | ODU4 | ODUCn | +| 1.0E-03 | 3.05 | 76.8 | 38.2 | 9.5 | 9.2 | 2.4 | 0.9 | 0.9 | +| 1.0E-04 | 3.00 | 75.7 | 37.7 | 9.4 | 9.1 | 2.3 | 0.9 | 0.9 | +| 1.0E-05 | 3.00 | 75.5 | 37.6 | 9.4 | 9.0 | 2.3 | 0.9 | 0.9 | +| 1.0E-06 | 3.00 | 75.5 | 37.6 | 9.4 | 9.0 | 2.3 | 0.9 | 0.9 | + +The average dPLM raising/clearing time is equal to the average acceptance time. + +### III.5.2 Mean time between false PLM defects due to bit errors + +A false PLM defect is declared if the same i bits (out of $n = 8$ ) are disturbed in $X = 3$ consecutive multiframes. According to Equation 33 of [b-Choi], the mean number of multiframes between the acceptance of a false PT byte with i certain false bits is: + +$$t_{mf, i} = \frac{1}{p_i^X} \frac{1 - p_i^X}{1 - p_i}$$ + +with the probability $p_i$ of i certain bits being disturbed within one multiframe. + +$$p_i = \text{BER}^i \cdot (1 - \text{BER})^{n-i}$$ + +The mean number of multiframes between any false acceptance resulting in a false dPLM is: + +$$t_{mf} = \frac{1}{\sum_i \binom{n}{i} \cdot \frac{1}{t_{mf,i}}}$$ + +**Table III.8 – Mean time between false ODUPL defects** + +| BER | | 1.0E-03 | 1.0E-04 | 1.0E-05 | 1.0E-06 | +|-------------------|-----|----------|-------------|----------------|----------------| +| ODU frames | X=3 | 1.25E+08 | 1.25E+11 | 1.25E+14 | 1.25E+17 | +| ODU0 | | 893.7 h | 100.0 years | 9.98E+04 years | 9.98E+04 years | +| ODU1 | | 445.0 h | 49.6 years | 4.97E+04 years | 4.97E+07 years | +| ODU2 | | 110.8 h | 12.4 years | 1.24E+04 years | 1.24E+07 years | +| ODU2e | | 106.9 h | 12.0 years | 1.19E+04 years | 1.19E+07 years | +| ODU3 | | 27.6 h | 3.1 years | 3.08E+03 years | 3.08E+06 years | +| ODU4 | | 10.6 h | 1.2 years | 1.19E+03 years | 1.18E+06 years | +| ODUCn | | 10.6 h | 1.2 years | 1.18E+03 years | 1.18E+06 years | + +### III.6 Generic AIS and OTUk-AIS (k = 1, 2, 3) detection + +#### III.6.1 Average dAIS detection time + +The probability of detecting the generic AIS pattern within one counting interval is: + +$$p_d = \sum_{k=0}^{255} \binom{Nb}{k} \cdot (3 \cdot BER)^k \cdot (1 - 3 \cdot BER)^{(Nb-k)}$$ + +with Nb = 8192 being the number of bits per counting interval. Inserting $p_d$ and the number of counting intervals in which the generic AIS signal must be detected before raising the defect, $c = 3$ , into Equation 33 of [b-Choi] leads to the average dAIS detection time. The factors of three found in the above equation are due to the error multiplication that occurs within the generic AIS detection circuit (see clause 6.2.6.3.3). + +**Table III.9 – Average dAIS detection time** + +| BER | | 2.0E-02 | 1.0E-02 | 1.0E-03 | 1.0E-04 | 1.0E-05 | 1.0E-06 | +|--------------|-------------|---------|---------|---------|---------|---------|---------| +| intervals | (8192 bits) | 5.0E+98 | 5.68 | 3 | 3 | 3 | 3 | +| | | (years) | (μs) | | | | | +| ODU0 | | 1.0E+86 | 37.40 | 19.75 | 19.75 | 19.75 | 19.75 | +| ODU1 | | 5.2E+85 | 18.62 | 9.84 | 9.84 | 9.84 | 9.84 | +| ODU2 | | 1.3E+85 | 4.64 | 2.45 | 2.45 | 2.45 | 2.45 | +| ODU2e | | 1.2E+85 | 4.47 | 2.36 | 2.36 | 2.36 | 2.36 | +| ODU3 | | 3.2E+84 | 1.15 | 0.61 | 0.61 | 0.61 | 0.61 | +| ODU4 | | 1.2E+84 | 0.44 | 0.23 | 0.23 | 0.23 | 0.23 | +| ODUCn | | 1.2E+84 | 0.44 | 0.23 | 0.23 | 0.23 | 0.23 | + +**III.7 OTU and ODUT dBIAE detection process** + +**III.7.1 Average dBIAE detection time** + +The average dBIAE detection/clearing time can be calculated using Equation 33 of [b-Choi], as the procedure is analogous to the misframe declaration procedure in Figure 7 of [b-Choi] by reading $q_d$ as probability for an undisturbed BIAE value. + +$$q_d = (1 - BER)^n$$ + +$$t_d = \frac{1}{q_d^X} \frac{1 - q_d^X}{1 - q_d}$$ + +n: number of BEI/BIAE bits (n = 4) + +X: number of consecutive BIAE values for dBIAE (X = 3). + +**Table III.10 – Average dBIAE detection/clearing time** + +| BER | OTU/ODU frames | | Time (μs) | | | | | | | +|---------|----------------|-------|-----------|-------|------|-------|------|------|-------| +| | X=3 | X=15 | ODU0 | ODU1 | ODU2 | ODU2e | ODU3 | ODU4 | ODUCn | +| 1.0E-03 | 3.02 | 15.49 | 297.4 | 148.1 | 36.9 | 35.6 | 9.2 | 3.5 | 18.0 | +| 1.0E-04 | 3.00 | 15.05 | 295.3 | 147.0 | 36.6 | 35.3 | 9.1 | 3.5 | 17.5 | +| 1.0E-05 | 3.00 | 15.00 | 295.1 | 146.9 | 36.6 | 35.3 | 9.1 | 3.5 | 17.4 | +| 1.0E-06 | 3.00 | 15.00 | 295.1 | 146.9 | 36.6 | 35.3 | 9.1 | 3.5 | 17.4 | + +**III.7.2 Mean time between false BIAE defects due to bit errors** + +A false BIAE defect is declared if the received BEI value is disturbed in such a way that the BIAE value (i.e., '1011') is falsely detected in X = 3 consecutive frames. Since the BEI value changes each frame due to received far-end bit errors, the probability of a false BIAE value occurring depends on the specific value of BEI generated each frame. Therefore, the probability of detecting a false BIAE value is the product of the conditional probability of a false BIAE value occurring given a particular BEI value and the probability of the occurrence of the particular BEI value. Summing over all possible BEI values gives the total probability of a false BIAE being detected in any single frame: + +$$p = \sum_{k=0}^8 p_{BEI,k} \cdot p_{BIAE|BEI,k}$$ + +where: + +$$p_{BEI, k} = \binom{8}{k} (p_{BIP1})^k \cdot (1 - p_{BIP1})^{8-k}, \quad 0 \leq k \leq 8$$ + +and: + +$$p_{BIAE|BEI, k} = (BER)^n \cdot (1 - BER)^{4-n}, \quad 0 \leq k \leq 8$$ + +where $n$ represents the number of BEI bit errors required to convert the BEI value to a false BIAE value ( $n = 3, 2, 2, 1, 4, 3, 3, 2, 2$ , for $k = 0, 1, 2, 3, 4, 5, 6, 7$ and $8$ , respectively). Additionally, Equation C.3 of [b-ATIS 0300231.01] provides a closed form expression for the probability of an error in a single BIP thread as follows: + +$$p_{BIP1} = \frac{1 - (1 - 2 \cdot BER)^m}{2}, \quad m = 15240$$ + +The value 15240 represents the number of bits per thread of the BIP-8 of the ODU tandem connection and path monitors. + +According to Equation 33 of [b-Choi], the mean number of frames between false BIAE defects because of bit errors within the BEI/BIAE field is: + +$$t_{mf} = \frac{1}{p^X} \frac{1 - p^X}{1 - p}$$ + +with the probability $p$ of a false BIAE. + +In Table III.11, the same BER for both directions of a bidirectional connection is assumed. + +**Table III.11 – Mean time between false BIAE defects** + +| BER | | 1.0E-03 | 1.0E-04 | 1.0E-05 | 1.0E-06 | +|-------------------|-----|---------|---------|---------|---------| +| ODU frames | X=3 | 9.6E+10 | 7.4E+13 | 4.0E+18 | 1.8E+29 | +| | | (h) | (years) | | | +| ODU0 | | 2628 | 230 | 1.3E+07 | 5.7E+17 | +| ODU1 | | 1308 | 115 | 6.3E+06 | 2.9E+17 | +| ODU2 | | 326 | 28.6 | 1.6E+06 | 7.2E+16 | +| ODU2e | | 314 | 27.6 | 1.5E+05 | 6.9E+16 | +| ODU3 | | 81.1 | 7.1 | 3.9E+05 | 1.8E+16 | +| ODU4 | | 31.2 | 2.74 | 1.5E+05 | 6.8E+15 | +| ODUCn | | 31.1 | 2.72 | 1.5E+05 | 6.8E+15 | + +## Appendix IV + +### TTI processing examples + +(This appendix does not form an integral part of this Recommendation.) + +This appendix gives implementation examples for TTI processing that fulfil the definitions given in the main body of this Recommendation. Other implementations that fulfil the definitions are possible. + +#### IV.1 Example 1 + +##### IV.1.1 Trail trace identifier (TTI) acceptance and reporting process + +A new TTI is accepted if a new consistent value is received in the 64 TTI bytes in X consecutive multiframes. X shall be 3. + +The accepted TTI shall be reported to the management system (MI\_AcTI) if requested (MI\_GetAcTI). The SAPI and DAPI part of the accepted TTI shall be compared with the expected SAPI and DAPI for TTI mismatch detection (see clause IV.I.2). + +##### IV.1.2 SAPI/DAPI compare process + +The SAPI/DAPI compare process compares the SAPI/DAPI part of the accepted TTI (AcTI, see clause IV.1.1) with the equivalent expected SAPI/DAPI values set via the MP (MI\_ExSAPI/DAPI). The comparison result is "match" if all 16 bytes were equal, and "mismatch" if one or more bytes were unequal. + +For the dTIM generation based on the results of the SAPI/DAPI compare process, see clause 6.2.2.1. + +#### IV.1.3 Performance of example 1 + +##### IV.1.3.1 Average TTI acceptance time + +The average TTI acceptance time can be calculated using Equation 33 of [b-Choi], as the procedure is analogous to the misframe declaration procedure in Figure 7 of [b-Choi] by reading $q_d$ as probability for the received TTI value being equal to the last one. + +$$q_d = (1 - BER)^n$$ + +$$t_d = \frac{1}{q_d^X} \frac{1 - q_d^X}{1 - q_d}$$ + +n: number of TTI bits (n = 512) + +X: number of consecutive equal comparison results for TTI acceptance (X = 3). + +Table IV.1 – Average TTI acceptance time + +| BER | TTI periods | Time (ms) | | | | | | | +|---------|-------------|-----------|------|------|-------|------|------|-------| +| | | ODU0 | ODU1 | ODU2 | ODU2e | ODU3 | ODU4 | ODUCn | +| 1.0E-03 | 9.10 | 57.3 | 28.5 | 7.1 | 6.9 | 1.8 | 0.7 | 0.7 | +| 1.0E-04 | 3.33 | 20.9 | 10.4 | 2.6 | 2.5 | 0.6 | 0.2 | 0.2 | +| 1.0E-05 | 3.03 | 19.1 | 9.5 | 2.4 | 2.3 | 0.6 | 0.2 | 0.2 | +| 1.0E-06 | 3.00 | 18.9 | 9.4 | 2.3 | 2.3 | 0.6 | 0.2 | 0.2 | + +#### IV.1.3.2 Average dTIM detection and clearing time + +The average dTIM detection and clearing times are equal to the TTI acceptance time. + +#### IV.1.3.3 Mean time between false TIM defects due to bit errors + +A false TTI defect is declared if a TTI with bit errors is accepted and an errored bit is within the compared SAPI, respectively DAPI, field of the TTI. The same $i$ bits (out of $n = 512$ ) have to be disturbed in $X = 3$ consecutive TTIs. According to Equation 33 of [b-Choi], the mean number of TTIs between the acceptance of a false TTI with $i$ certain false bits is: + +$$t_{mf,i} = \frac{1}{p_i^X} \cdot \frac{1-p_i^X}{1-p_i}$$ + +with the probability $p_i$ of $i$ certain bits being disturbed within one TTI: + +$$p_i = BER^i \cdot (1-BER)^{n-i}$$ + +The mean number of TTIs between any false dTIM is: + +$$t_{mf} = \frac{1}{\sum_i \frac{p_{API,i}}{t_{mf,i}}}$$ + +with the probability $p_{API,i}$ that the API field contains an errored bit of the false accepted TTI with $i$ bit errors. + +$n$ : number of TTI bits + +$X$ : number of consecutive equal comparison results for TTI acceptance ( $X = 3$ ) + +**Table IV.2 – Mean time between false TIM defects** + +| BER | | 1.0E-03 | 1.0E-04 | 1.0E-05 | 1.0E-06 | +|------------|-------|----------|----------|----------|-----------| +| ODU frames | $X=3$ | 3.62E+07 | 9.11E+09 | 7.93E+12 | 7.82E+15 | +| | | (h) | (years) | | | +| ODU0 | | 63.4 | 1.8 | 1583 | 1 561 785 | +| ODU1 | | 31.5 | 0.9 | 788 | 777 625 | +| ODU2 | | 7.9 | 0.23 | 196 | 193 589 | +| ODU2e | | 7.6 | 0.22 | 189 | 186 846 | +| ODU3 | | 2.0 | 0.06 | 49 | 48 193 | +| ODU4 | | 0.8 | 0.02 | 19 | 18 542 | +| ODUCn | | 0.7 | 0.02 | 19 | 18 460 | + +## IV.2 Example 2 + +### IV.2.1 TTI reporting + +TTI reporting consists of control, compare and store, and persistency processes as shown in Figure IV.1. When a request for TTI reporting is received via MI\_GetAcTI by the control process, it starts the compare and store, and persistency processes. + +The compare and store process contains a 64-byte store, holding the latest stored TTI. Once started, this process compares the received TTI byte with the equivalent byte in the store. After the comparison the byte is copied into the store. After all 64 bytes have been compared and stored, the + + + +$$t_d = \frac{1}{q_d^X} \frac{1 - q_d^X}{1 - q_d}$$ + +n: number of TTI bits (n = 512) + +X: number of consecutive equal comparison results for a stable TTI (X = 3) + +**Table IV.3 – Average TTI acceptance time** + +| BER | TTI periods | Time (ms) | | | | | | | +|---------|-------------|-----------|------|------|-------|------|------|-------| +| | | ODU0 | ODU1 | ODU2 | ODU2e | ODU3 | ODU4 | ODUCn | +| 1.0E-03 | 9.10 | 57.3 | 28.5 | 7.1 | 6.9 | 1.8 | 0.7 | 0.7 | +| 1.0E-04 | 3.33 | 20.9 | 10.4 | 2.6 | 2.5 | 0.6 | 0.2 | 0.2 | +| 1.0E-05 | 3.03 | 19.1 | 9.5 | 2.4 | 2.3 | 0.6 | 0.2 | 0.2 | +| 1.0E-06 | 3.00 | 18.9 | 9.4 | 2.3 | 2.3 | 0.6 | 0.2 | 0.2 | + +#### IV.2.3.2 Average dTIM detection time + +The average dTIM detection time can be calculated using Equation 33 of [b-Choi], as the procedure is analogous to the misframe declaration procedure in Figure 7 of [b-Choi] by reading $q_d$ as probability for an unequal SAPI, respectively DAPI, value. Here the worst case is calculated where ExSAPI and RxSAPI, respectively ExDAPI and RxDAPI, differ in only one bit. + +$$q_d = 1 - BER$$ + +$$t_d = \frac{1}{q_d^X} \frac{1 - q_d^X}{1 - q_d}$$ + +X: number of consecutive unequal comparison results for dTIM (X = 7) + +**Table IV.4 – Average dTIM detection time** + +| BER | TTI periods | Time (ms) | | | | | | | +|---------|-------------|-----------|------|------|-------|------|------|-------| +| | | ODU0 | ODU1 | ODU2 | ODU2e | ODU3 | ODU4 | ODUCn | +| 1.0E-03 | 7.03 | 44.2 | 22.0 | 5.5 | 5.3 | 1.4 | 0.5 | 0.5 | +| 1.0E-04 | 7.00 | 44.1 | 21.9 | 5.5 | 5.3 | 1.4 | 0.5 | 0.5 | +| 1.0E-05 | 7.00 | 44.1 | 21.9 | 5.5 | 5.3 | 1.4 | 0.5 | 0.5 | +| 1.0E-06 | 7.00 | 44.1 | 21.9 | 5.5 | 5.3 | 1.4 | 0.5 | 0.5 | + +#### IV.2.3.3 Average dTIM clearing time + +The average dTIM clearing time can be calculated using Equation 33 of [b-Choi], as the procedure is analogous to the misframe declaration procedure in Figure 7 of [b-Choi] by reading $q_d$ as probability for an equal SAPI, respectively DAPI, value. + +$$q_d = (1 - BER)^n$$ + +$$t_d = \frac{1}{q_d^X} \frac{1 - q_d^X}{1 - q_d}$$ + +n: number of SAPI, respectively DAPI, bits (n = 128) + +X: number of consecutive equal comparison results for dTIM clearance (X = 3) + +**Table IV.5 – Average dTIM clearance time for point-to-multipoint and multipoint-to-point configurations** + +| BER | TTI periods | Time (ms) | | | | | | | +|---------|-------------|-----------|------|------|-------|------|------|-------| +| | | ODU0 | ODU1 | ODU2 | ODU2e | ODU3 | ODU4 | ODUCn | +| 1.0E-03 | 3.90 | 24.5 | 12.2 | 3.0 | 2.9 | 0.8 | 0.3 | 0.3 | +| 1.0E-04 | 3.08 | 19.4 | 9.6 | 2.4 | 2.3 | 0.6 | 0.2 | 0.2 | +| 1.0E-05 | 3.01 | 18.9 | 9.4 | 2.3 | 2.3 | 0.6 | 0.2 | 0.2 | +| 1.0E-06 | 3.00 | 18.9 | 9.4 | 2.3 | 2.3 | 0.6 | 0.2 | 0.2 | + +**IV.2.3.4 Mean time between false TIM defects due to bit errors** + +The mean time between false TIM defects can be calculated using Equation 33 of [b-Choi], as the procedure is analogous to the misframe declaration procedure in Figure 7 of [b-Choi] by reading $q_d$ as probability for an unequal SAPI, respectively DAPI, value due to bit errors. + +$$q_d = 1 - (1 - BER)^n$$ + +$$t_d = \frac{1}{q_d^X} \frac{1 - q_d^X}{1 - q_d}$$ + +n: number of SAPI, respectively DAPI, bits (n = 128) + +X: number of consecutive unequal comparison results for dTIM (X = 7) + +**Table IV.6 – Mean time between false TIM defects for point-to-multipoint and multipoint-to-point configurations** + +| BER | | 1.0E-03 | 1.0E-04 | 1.0E-05 | 1.0E-06 | +|--------------|-----|----------|----------|----------|----------| +| ODU frames | X=7 | 3.13E+06 | 1.88E+13 | 1.79E+20 | 1.78E+27 | +| | | (h) | (years) | | | +| ODU0 | | 5.5 | 3754 | 3.6E+10 | 3.5E+17 | +| ODU1 | | 2.7 | 1869 | 1.8E+10 | 1.8E+17 | +| ODU2 | | 0.7 | 465 | 4.4E+09 | 4.4E+16 | +| ODU2e | | 0.7 | 449 | 4.3E+09 | 4.2E+16 | +| ODU3 | | 0.2 | 116 | 1.1E+09 | 1.1E+16 | +| ODU4 | | 0.1 | 45 | 4.2E+08 | 4.2E+15 | +| ODUCn | | 0.1 | 44 | 4.2E+08 | 4.2E+15 | + +## **Appendix V** + +### **Blank appendix** + +(This appendix does not form an integral part of this Recommendation.) + +This appendix is intentionally left blank. + +## **Appendix VI** + +### **Blank appendix** + +(This appendix does not form an integral part of this Recommendation.) + +This appendix is intentionally left blank. + +**Appendix VII** + +**Examples of media elements** + +(This appendix does not form an integral part of this Recommendation.) + +This appendix provides examples where a media element encapsulates the OMS or OTS end points. + +![Figure VII.1 – Example of an OTN terminal implemented with a single media element](782eaa616e0b199419dde477a878be7d_img.jpg) + +The diagram illustrates the functional model of an OTN terminal. At the top, an OTUk\_CI signal enters an OTSi/OTUKV adaptation function. Below this, an OTSi signal is formed, which then enters an OTSiG group. A dashed line indicates coordination (AI\_TSF) with an OTSiG-O function. The signals pass through an OTSiA|OCh layer. A large grey box labeled 'Media element' contains several components: an OTSi filter, an optical amplifier, and an OSC filter. Monitoring points (OMS-P OPM and OTS-P OPM) provide defect indications (DI\_dLOS-P[OMS] and DI\_dLOS-P[OTS]) to the overhead processing chain on the right. This chain includes functions for OMS-O/OTSiG|OCh-O, OMS-O, OTS-O/OMS-O, OTS-O, OSC/OTS-O, OSC, and OTSi/OSC, ending in an OTSi termination. The bottom of the media element connects to a Multi-channel interface. + +Figure VII.1 – Example of an OTN terminal implemented with a single media element + +G.798(23)\_FVII.1 + +Multi-channel interface + +**Figure VII.1 – Example of an OTN terminal implemented +with a single media element** + +Rec. ITU-T G.798 (09/2023)    461 + +![Diagram of a single vendor OTN line system with three media elements connected by fibre. Each element contains an OSC filter, OTSi, OTS-P OPM, Optical amplifier, OMS-P OPM, and OTSi filter connected to a Media subnetwork. OSC network connections are shown between the elements.](4e09aad97504825adf16d63ace42b461_img.jpg) + +The diagram illustrates a single vendor OTN line system implemented with a single media element in each location. It consists of three main components connected by fibre: + +- Left Media Element:** Contains an OSC filter, OTSi, OTS-P OPM, Optical amplifier, OMS-P OPM, and OTSi filter. The OTSi filter is connected to a Media subnetwork, which in turn connects to two OTSi units. The OSC filter is connected to a fibre line and an OSC network connection (via an OSC unit and OTSi unit). +- Central Media Element:** Contains an OSC filter, OTS-P OPM, Optical amplifier, and OTS-P OPM. The OSC filter is connected to a fibre line and an OSC network connection (via an OSC unit and OTSi unit). The OTS-P OPM units are connected to the Optical amplifier. +- Right Media Element:** Similar to the left element, it contains an OSC filter, OTSi, OTS-P OPM, Optical amplifier, OMS-P OPM, and OTSi filter. The OTSi filter is connected to a Media subnetwork, which connects to two OTSi units. The OSC filter is connected to a fibre line and an OSC network connection (via an OSC unit and OTSi unit). + +The fibre lines connect the OSC filters of adjacent media elements. Dashed lines represent various OSME (Optical Subnetwork Management Entity) boundaries: OTSi OSME, OMS OSME, and OTS OSME. The OSC network connections are shown between the OSC units and OTSi units of adjacent media elements. + +G.798(17)-Amd.4(22)\_FVII.2 + +Diagram of a single vendor OTN line system with three media elements connected by fibre. Each element contains an OSC filter, OTSi, OTS-P OPM, Optical amplifier, OMS-P OPM, and OTSi filter connected to a Media subnetwork. OSC network connections are shown between the elements. + +**Figure VII.2 – Example of a single vendor OTN line system implemented with a single media element in each location** + +## Appendix VIII + +### Trail protection of OTS-O/OMS-O layers in support of media layer protection + +(This appendix does not form an integral part of this Recommendation.) + +Appendix III of [ITU-T G.873.1] describes media layer protection schemes for OTS and OMS maintenance entities. These schemes use an optical switch within the media element to protect the optical signal, and an associated trail protection scheme for the OTS-O or OMS-O layer. Trail protection is modelled as an expansion of the access point for a trail to include a protection sublayer. The expansion is identical for both of the layers, so it is described here with 'OxS-O' nomenclature. + +#### VIII.1 OxS-O trail protection sub-layer functions + +The OxS-O trail protection sub-layer (OxS-OP) is generated by expanding the OxS access point, as shown in Figure VIII.1. OxS-O trail protection provides 1+1 unidirectional protection. + +![Figure VIII.1 – OxS-O trail protection sub-layer functions. The diagram illustrates the functional architecture of the OxS-O trail protection sub-layer. On the left, a 'Media element' box contains 'Other media functions', an 'Optical switch/splitter', and two more 'Other media functions' blocks. The optical switch/splitter is connected to an 'OxS-OP/Client' block at the top and to an 'OxS-OP 1+1u' block via a 'Switch coordination' line. The 'OxS-OP 1+1u' block has three ports: 'n' (top), 'w' (left), and 'p' (right). Port 'n' is connected to an 'OxS-OP' block, which is further connected to an 'OxS-O/OxS-OP' block. Port 'w' is connected to an 'OxS-O' block labeled 'Working trail'. Port 'p' is connected to an 'OxS-O' block labeled 'Protection trail'. Both 'OxS-O' blocks are connected to an 'OxS-O' layer at the bottom. Dashed lines labeled 'DI_dLOS-P[OxS]' connect the 'Other media functions' in the media element to the 'OxS-O' blocks. Vertical labels on the right identify the 'OxS-O trail protection sublayer' and the 'OxS-O layer'. The diagram is labeled 'G.798(23)_FVIII.1' at the bottom right.](7a4168ad9aed51fc9c5f121a863b8dbb_img.jpg) + +Figure VIII.1 – OxS-O trail protection sub-layer functions. The diagram illustrates the functional architecture of the OxS-O trail protection sub-layer. On the left, a 'Media element' box contains 'Other media functions', an 'Optical switch/splitter', and two more 'Other media functions' blocks. The optical switch/splitter is connected to an 'OxS-OP/Client' block at the top and to an 'OxS-OP 1+1u' block via a 'Switch coordination' line. The 'OxS-OP 1+1u' block has three ports: 'n' (top), 'w' (left), and 'p' (right). Port 'n' is connected to an 'OxS-OP' block, which is further connected to an 'OxS-O/OxS-OP' block. Port 'w' is connected to an 'OxS-O' block labeled 'Working trail'. Port 'p' is connected to an 'OxS-O' block labeled 'Protection trail'. Both 'OxS-O' blocks are connected to an 'OxS-O' layer at the bottom. Dashed lines labeled 'DI\_dLOS-P[OxS]' connect the 'Other media functions' in the media element to the 'OxS-O' blocks. Vertical labels on the right identify the 'OxS-O trail protection sublayer' and the 'OxS-O layer'. The diagram is labeled 'G.798(23)\_FVIII.1' at the bottom right. + +Figure VIII.1 – OxS-O trail protection sub-layer functions + +##### VIII.1.1 OxS-OP 1+1 unidirectional trail protection connection function (OxS-OP1+1u\_C) + +The OxS-OP1+1u\_C provide 1+1 unidirectional trail protection at the OxS-O layer. + +###### VIII.1.1.1 OxS-OP 1+1 unidirectional trail protection connection source function (OxS-OP1+1u\_C\_So) + +The information flow and processing of the OxS-OP1+1u\_C\_So function is defined with reference to Figure VIII.2. + +## Symbol + +![Diagram of the OxS-OP1+1u_C_So function symbol. An oval labeled 'OxS-OP 1+1u' has an input 'n' from 'OxS-OP_CPn' entering from the top. It has two outputs: 'w' leading to 'OxS-OP_CPw' and 'p' leading to 'OxS-OP_CPp'. A small note 'G.798(17)-Amd.1(18)_FVIII.2' is at the bottom right.](f863cb8837fe502a913bc2be8d1afd8a_img.jpg) + +G.798(17)-Amd.1(18)\_FVIII.2 + +Diagram of the OxS-OP1+1u\_C\_So function symbol. An oval labeled 'OxS-OP 1+1u' has an input 'n' from 'OxS-OP\_CPn' entering from the top. It has two outputs: 'w' leading to 'OxS-OP\_CPw' and 'p' leading to 'OxS-OP\_CPp'. A small note 'G.798(17)-Amd.1(18)\_FVIII.2' is at the bottom right. + +**Figure VIII.2 – OxS-OP1+1u\_C\_So function** + +## Interfaces + +**Table VIII.1 – OxS-OP1+1u\_C\_So inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------|---------------------------------------------------| +| OxS-OP_CPn:
OxS-OP_CI_OH | OxS-OP_CPw and OxS-OP_CPp:
OxS-OP_CI_OH | + +## Processes + +The function performs the bridge for the 1+1 unidirectional trail protection. + +For 1+1 architecture, the CI coming from the normal (protected) OxS-OP\_CP is bridged permanently to both the working and protection OxS-OP\_CP. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### **VIII.1.1.2 OxS-OP 1+1 unidirectional trail protection connection sink function (OxS-OP1+1u\_C\_Sk)** + +The information flow and processing of the OxS-OP1+1u\_C\_Sk function is defined with reference to Figure VIII.3. + +## Symbol + +![Symbol diagram for the OxS-OP1+1u_C_Sk function. It shows an oval labeled 'OxS-OP 1+1u'. At the top, an arrow labeled 'n' points to an output 'OxS-OP_CPn'. At the bottom left, an arrow labeled 'w' points from input 'OxS-OP_CPw'. At the bottom right, an arrow labeled 'p' points from input 'OxS-OP_CPp'. On the right side, a double-headed arrow connects to 'OxS-OP1+1u_C_Sk_MP'. Below the diagram is the text 'G.798(17)-Amd.1(18)_FVIII.3'.](806faec01366b8a02de54ed0de2b6a83_img.jpg) + +Symbol diagram for the OxS-OP1+1u\_C\_Sk function. It shows an oval labeled 'OxS-OP 1+1u'. At the top, an arrow labeled 'n' points to an output 'OxS-OP\_CPn'. At the bottom left, an arrow labeled 'w' points from input 'OxS-OP\_CPw'. At the bottom right, an arrow labeled 'p' points from input 'OxS-OP\_CPp'. On the right side, a double-headed arrow connects to 'OxS-OP1+1u\_C\_Sk\_MP'. Below the diagram is the text 'G.798(17)-Amd.1(18)\_FVIII.3'. + +Figure VIII.3 – OxS-OP1+1u\_C\_Sk function + +## Interfaces + +Table VIII.2 – OxS-OP1+1u\_C\_Sk inputs and outputs + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| OxS-OP_CPw and OxS-OP_CPp:
OxS-OP_CI_OH
OxS-OP_CI_SSF-P
OxS-OP_CI_SSF-O
OxS-OP1+1u_C_Sk_MP:
OxS-OP_C_MI_OperType
OxS-OP_C_MI_WTR
OxS-OP_C_MI_HoTime
OxS-OP_C_MI_ExtCMD | OxS-OP_CPn:
OxS-OP_CI_OH
OxS-OP_CI_SSF-P
OxS-OP_CI_SSF-O
OxS-OP1+1u_C_Sk_MP:
For further study | + +## Processes + +For a 1+1 architecture, the CI from either the working or protection OxS-OP\_CP is switched to the normal (protected) OxS-OP\_CP. A switch-over from working to protection OxS-OP\_CP or vice versa is initiated by the switch initiation criteria defined below. + +### *Switch initiation criteria:* + +Automatic protection switching is based on the defect conditions of the working and protection trail. These condition(s) are server signal fail payload (SSF-P), and server signal fail overhead (SSF-O). Note that defects detected by the media element will be reported to the OxS-O\_TT\_Sk via the defect port and cause TSF-P to be asserted, which will cause SSF-P to be seen by the OxS-OP1+1u\_C\_Sk. + +In order to allow interworking between nested protection schemes, a hold-off timer is provided. The hold-off timer delays switch initiation in case of signal fail in order to allow a nested protection to react and clear the fault condition. The hold-off timer is started by the activation of signal fail and runs for the hold-off time. Protection switching is only initiated if signal fail is still present at the end of the hold-off time. The hold-off time shall be provisionable between 0 and 10 s in steps of 100 ms. + +Protection switching can also be initiated by external switch commands received via the MP. + +Depending on the mode of operation, internal states (e.g., wait to restore) may also initiate a switch-over. + +*Switch restoration:* + +In the revertive mode of operation, the protected signal shall be switched back from the protection trail to the working trail when the working trail has recovered from the fault. + +To prevent frequent operation of the protection switch due to an intermittent fault, a failed working trail must become fault-free for a certain period of time before it is used again. This period, called the wait to restore (WTR) period should be on the order of 5-12 minutes and should be capable of being set. + +In the non-revertive mode of operation, no switchback to the working trail is performed when it has recovered from the fault. + +Protection switching notifications to the MP are for further study. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +**VIII.1.2 OxS-OP trail termination function (OxS-OP\_TT)** + +**VIII.1.2.1 OxS-OP trail termination source function (OxS-OP\_TT\_So)** + +The information flow and processing of the OxS-OP\_TT\_So function is defined with reference to Figure VIII.4. + +**Symbol** + +![Symbol diagram for OxS-OP_TT_So function. It shows an input labeled OxS-OP_AP entering a triangle labeled OxS-OP from the top. An output labeled OxS-OP_TCP exits the triangle from the bottom. Below the output label is the text 'G.798(17)-Amd.1(18)_FVIII.4'.](07b57db1227a83b659cd2def7b8ba5ea_img.jpg) + +OxS-OP\_AP +↓ +OxS-OP +↓ +OxS-OP\_TCP +G.798(17)-Amd.1(18)\_FVIII.4 + +Symbol diagram for OxS-OP\_TT\_So function. It shows an input labeled OxS-OP\_AP entering a triangle labeled OxS-OP from the top. An output labeled OxS-OP\_TCP exits the triangle from the bottom. Below the output label is the text 'G.798(17)-Amd.1(18)\_FVIII.4'. + +**Figure VIII.4 – OxS-OP\_TT\_So function** + +**Interfaces** + +**Table VIII.3 – OxS-OP\_TT\_So inputs and outputs** + +| Input(s) | Output(s) | +|--------------------------|-----------------------------| +| OxS-O_AP:
OxS-O_AI_OH | OxS-OP_TCP:
OxS-OP_CI_OH | + +**Processes** + +No information processing is required in the OxS-OP\_TT\_So, the OxS-OP\_CI at its output being identical to the OxS-O\_AI at its input. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### VIII.1.2.2 OxS-OP trail termination sink function (OxS-OP\_TT\_Sk) + +The information flow and processing of the OxS-OP\_TT\_Sk function is defined with reference to Figure VIII.5. + +#### Symbol + +![Diagram of the OxS-OP_TT_Sk function symbol. It is a triangle pointing downwards with 'OxS-OP' written inside. An arrow points from 'OxS-OP_TCP' at the bottom vertex into the triangle. An arrow points from the top vertex to 'OxS-OP_AP'. An arrow points from the left side of the triangle to 'OxS-OP_TT_Sk_MP'. Below the diagram is the text 'G.798(17)-Amd.1(18)_FVIII.5'.](7450203d6606590615fbbeaf2f663b36_img.jpg) + +Diagram of the OxS-OP\_TT\_Sk function symbol. It is a triangle pointing downwards with 'OxS-OP' written inside. An arrow points from 'OxS-OP\_TCP' at the bottom vertex into the triangle. An arrow points from the top vertex to 'OxS-OP\_AP'. An arrow points from the left side of the triangle to 'OxS-OP\_TT\_Sk\_MP'. Below the diagram is the text 'G.798(17)-Amd.1(18)\_FVIII.5'. + +**Figure VIII.5 – OxS-OP\_TT\_Sk function** + +#### Interfaces + +**Table VIII.4 – OxS-OP\_TT\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OxS-OP_TCP:
OxS-OP_CI_OH
OxS-OP_CI_SSF-P
OxS-OP_CI_SSF-O | OxS-O_AP:
OxS-O_AI_OH
OxS-O_AI_TSF-P
OxS-O_AI_TSF-O
OxS-OP_TT_Sk_MP:
OxS-OP_TT_Sk_MI_cSSF-P
OxS-OP_TT_Sk_MI_cSSF-O
OxS-OP_TT_Sk_MI_cSSF | + +#### Processes + +The OxS-OP\_TT\_Sk function reports the state of the protected OxS-O trail. + +No additional information processing is required in the OxS-OP\_TT\_Sk, the OxS-O\_AI at its output being identical to the OxS-OP\_CI at its input. + +**Defects:** None. + +#### Consequent actions + +The OxS-OP\_TT\_Sk function performs the following consequent actions. + +$a\text{TSF-P} \leftarrow \text{CI\_SSF-P}$ + +$a\text{TSF-O} \leftarrow \text{CI\_SSF-O}$ + +#### Defect correlations + +The OxS-OP\_TT\_Sk function shall perform the following defect correlations. + +$\text{cSSF} \leftarrow \text{CI\_SSF-P and CI\_SSF-O}$ + +cSSF-P $\leftarrow$ CI\_SSF-P and (not CI\_SSF-O) + +cSSF-O $\leftarrow$ CI\_SSF-O and (not CI\_SSF\_P) + +**Performance monitoring:** None. + +### VIII.1.3 OxS-O to OxS-OP adaptation function (OxS-O/OxS-OP\_A) + +#### VIII.1.3.1 OxS-O to OxS-OP adaptation source function (OxS-O/OxS-OP\_A\_So) + +The information flow and processing of the OxS-O/OxS-OP\_A\_So functions is defined with reference to Figure VIII.6. + +##### Symbol + +![Diagram of the OxS-O/OxS-OP_A_So function symbol. It shows an input 'OxS-OP_CP' entering a trapezoidal block labeled 'OxS-O/OxS-OP', which then outputs 'OxS-OP_AP'. Below the diagram is the text 'G.798(17)-Amd.1(18)_FVIII.6'.](43100f35a10f651fb3685f9eb7abdf9d_img.jpg) + +G.798(17)-Amd.1(18)\_FVIII.6 + +Diagram of the OxS-O/OxS-OP\_A\_So function symbol. It shows an input 'OxS-OP\_CP' entering a trapezoidal block labeled 'OxS-O/OxS-OP', which then outputs 'OxS-OP\_AP'. Below the diagram is the text 'G.798(17)-Amd.1(18)\_FVIII.6'. + +**Figure VIII.6 – OxS-O/OxS-OP\_A\_So function** + +##### Interfaces + +**Table VIII.5 – OxS-O/OxS-OP\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------|--------------------------| +| OxS-OP_CP:
OxS-OP_CI_OH | OxS-O_AP:
OxS-O_AI_OH | + +##### Processes + +No information processing is required in the OxS-O/OxS-OP\_A\_So, the OxS-O\_AI at its output being identical to the OxS-OP\_CI at its input. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### VIII.1.3.2 OxS-O to OxS-OP adaptation sink function (OxS-O/OxS-OP\_A\_Sk) + +The information flow and processing of the OxS-O/OxS-OP\_A\_Sk function is defined with reference to Figure VIII.7. + +## Symbol + +![Symbol diagram for the OxS-O/OxS-OP_A_Sk function. It shows a trapezoidal block labeled 'OxS-O/OxS-OP'. An arrow labeled 'OxS-OP_AP' points into the bottom of the block, and an arrow labeled 'OxS-OP_CP' points out of the top of the block. Below the diagram is the text 'G.798(17)-Amd.1(18)_FVIII.7'.](9947dd291b40f299948b56f3190ec7b0_img.jpg) + +Symbol diagram for the OxS-O/OxS-OP\_A\_Sk function. It shows a trapezoidal block labeled 'OxS-O/OxS-OP'. An arrow labeled 'OxS-OP\_AP' points into the bottom of the block, and an arrow labeled 'OxS-OP\_CP' points out of the top of the block. Below the diagram is the text 'G.798(17)-Amd.1(18)\_FVIII.7'. + +Figure VIII.7 – OxS-O/OxS-OP\_A\_Sk function + +## Interfaces + +Table VIII.8 – OxS-O/OxS-OP\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|------------------|-------------------| +| OxS-O_AP: | OxS-OP_CP: | +| OxS-O_AI_OH | OxS-OP_CI_OH | +| OxS-O_AI_TSF-P | OxS-OP_CI_SSF-P | +| OxS-O_AI_TSF-O | OxS-OP_CI_SSF-O | + +## Processes + +No information processing is required in the OxS-O/OxS-OP\_A\_Sk, the OxS-OP\_CI at its output being identical to the OxS-O\_AI at its input. + +**Defects:** None. + +## Consequent actions + +aSSF-P $\leftarrow$ AI\_TSF-P + +aSSF-O $\leftarrow$ AI\_TSF-O + +**Defect correlations:** None. + +**Performance monitoring:** None. + +## Appendix IX + +### Examples of compound adaptation functions without SM monitoring + +(This appendix does not form an integral part of this Recommendation.) + +For a point-to-point, single optical span application, one client per wavelength, the ODUP PM overhead and the OTU SM overhead monitor the same entity. Figures IX.1 and IX.2 show examples of compound adaptation functions without SM monitoring. + +![Figure IX.1: OTSi(G) to ODU adaptation compound function. The diagram shows three examples of adaptation functions. The top-left diagram shows a single OTSi/ODU adaptation unit. The top-right diagram shows a compound adaptation function for a single OTSi/ODU unit, enclosed in a dashed box, with an OTU/ODU, OTU, and OTSi/OTU block, and a 'MI_Mode = transparent' label. The bottom-left diagram shows a compound adaptation function for multiple OTSi(AP) units (1 to m) adapted to a single OTSiG/ODU unit. The bottom-right diagram shows a compound adaptation function for multiple OTSi(AP) units (1 to m) adapted to a single OTSiG/OTU unit, enclosed in a dashed box, with an OTU/ODU, OTU, and OTSiG/OTU block, and a 'MI_Mode = transparent' label. All diagrams show interfaces for ODU_CP, OTSiA, OTSiG, OTSi_AP, and OTSiG-O_AP.](7c414f2c4afc45fae028f3d82cc6dbdf_img.jpg) + +The diagram illustrates three examples of compound adaptation functions without SM monitoring: + +- Top-left:** A single adaptation unit consisting of an **ODU\_CP** interface connected to an **OTSi/ODU** block. The **OTSi/ODU** block is connected to two interfaces: **OTSi\_AP** and **OTSiG-O\_AP**, with an **OTSiA** interface in between. +- Top-right:** A compound adaptation function for a single **OTSi/ODU** unit, enclosed in a dashed box. It consists of an **ODU\_CP** interface connected to an **OTU/ODU** block, which is connected to an **OTU** block (labeled **MI\_Mode = transparent**), which is connected to an **OTSi/OTU** block. The **OTSi/OTU** block is connected to two interfaces: **OTSi\_AP** and **OTSiG-O\_AP**, with an **OTSiA** interface in between. +- Bottom-left:** A compound adaptation function for multiple **OTSi(AP)** units (labeled 1 to m) adapted to a single **OTSiG/ODU** block. The **OTSiG/ODU** block is connected to an **ODU\_CP** interface at the top and three interfaces at the bottom: **OTSi\_AP[1]**, **OTSi\_AP[m]**, and **OTSiG-O\_AP**. The **OTSiG** and **OTSiA** interfaces are shown between the **OTSiG/ODU** block and the bottom interfaces. +- Bottom-right:** A compound adaptation function for multiple **OTSi(AP)** units (labeled 1 to m) adapted to a single **OTSiG/OTU** block, enclosed in a dashed box. It consists of an **ODU\_CP** interface connected to an **OTU/ODU** block, which is connected to an **OTU** block (labeled **MI\_Mode = transparent**), which is connected to an **OTSiG/OTU** block. The **OTSiG/OTU** block is connected to three interfaces: **OTSi\_AP[1]**, **OTSi\_AP[m]**, and **OTSiG-O\_AP**, with **OTSiG** and **OTSiA** interfaces in between. + +G.798(17)-Amd.1(18)\_FIX.1 + +Figure IX.1: OTSi(G) to ODU adaptation compound function. The diagram shows three examples of adaptation functions. The top-left diagram shows a single OTSi/ODU adaptation unit. The top-right diagram shows a compound adaptation function for a single OTSi/ODU unit, enclosed in a dashed box, with an OTU/ODU, OTU, and OTSi/OTU block, and a 'MI\_Mode = transparent' label. The bottom-left diagram shows a compound adaptation function for multiple OTSi(AP) units (1 to m) adapted to a single OTSiG/ODU unit. The bottom-right diagram shows a compound adaptation function for multiple OTSi(AP) units (1 to m) adapted to a single OTSiG/OTU unit, enclosed in a dashed box, with an OTU/ODU, OTU, and OTSiG/OTU block, and a 'MI\_Mode = transparent' label. All diagrams show interfaces for ODU\_CP, OTSiA, OTSiG, OTSi\_AP, and OTSiG-O\_AP. + +Figure IX.1 – OTSi(G) to ODU adaptation compound function + +![Diagram illustrating FlexO-n to ODU adaptation compound function. The left side shows a high-level view with FlexO-n/ODUCn block, ODUCn_CP, and multiple FlexO_AP interfaces. The right side shows a detailed internal structure with OTUCn/ODUCn and OTUCn blocks, including a transparent mode loop, all within a dashed boundary.](4834b6d862f59622ea6314c723c7572f_img.jpg) + +The diagram illustrates the FlexO-n to ODU adaptation compound function. On the left, a high-level view shows a **FlexO-n/ODUCn** block connected to **ODUCn\_CP** at the top and multiple **FlexO\_AP** interfaces (labeled **FlexO\_AP[1]** and **FlexO\_AP[n]**) at the bottom. The connections are labeled **1** and **n**. On the right, a detailed view shows the internal structure: **ODUCn\_CP** connects to an **OTUCn/ODUCn** block, which connects to an **OTUCn** block. The **OTUCn** block has a feedback loop labeled **MI\_Mode = transparent** and connects to another **FlexO-n/ODUCn** block. This block then connects to the **FlexO\_AP** interfaces. The internal components are enclosed in a dashed boundary. + +G.798(17)-Amd.1(18)\_FIX.2 + +Diagram illustrating FlexO-n to ODU adaptation compound function. The left side shows a high-level view with FlexO-n/ODUCn block, ODUCn\_CP, and multiple FlexO\_AP interfaces. The right side shows a detailed internal structure with OTUCn/ODUCn and OTUCn blocks, including a transparent mode loop, all within a dashed boundary. + +**Figure IX.2 – FlexO-n to ODU adaptation compound function** + +## Bibliography + +- [b-ANSI INCITS 296] ANSI INCITS 296-1997, *Single-Byte Command Code Sets CONnection (SBCON) Architecture (formerly ANSI X3.296-1997)*. +- [b-ANSI INCITS 352] ANSI INCITS 352-2002, *Information Technology – Fibre Channel – Physical Interfaces (FC-PI)*. +- [b-ANSI INCITS 364] ANSI INCITS 364-2003, *Information Technology – Fibre Channel 10 Gigabit (10GFC)*. +- [b-ATIS 0300231.01] ATIS 0300231.01-1997, *In-service Digital Transmission Performance Monitoring*. +- [b-Choi] Choi, D. (1990), *Frame alignment in digital carrier system – a tutorial*, IEEE Communications Magazine. +- [b-INCITS 470] INCITS 470:2011, *Information Technology – Fibre Channel – Framing and Signaling – 3 (FC-FS-3)*. +- [b-INCITS 488] INCITS 488:2016, *Information Technology – Fibre Channel – Framing and Signaling – 4 (FC-FS-4)*. +- [b-INCITS 512] INCITS 512:2015, *Information Technology – Fibre Channel – Physical Interfaces – 6 (FC-PI-6)*. + + + +## 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.8021-202204-I_PDF-E/raw.md b/marked/G/T-REC-G.8021-202204-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0eaac89fc1d1de8e717d3d35a1d30a853de5ccb7 --- /dev/null +++ b/marked/G/T-REC-G.8021-202204-I_PDF-E/raw.md @@ -0,0 +1,8334 @@ + + +**ITU-T** + +**G.8021/Y.1341** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(04/2022) + +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 + +# --- **Characteristics of Ethernet transport network equipment functional blocks** + +Recommendation ITU-T G.8021/Y.1341 + +# 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.8021/Y.1341 + +# Characteristics of Ethernet transport network equipment functional blocks + +## Summary + +Recommendation ITU-T G.8021/Y.1341 specifies both the functional components and the methodology that should be used in order to specify the Ethernet transport network functionality of network elements; it does not specify individual Ethernet transport network equipment. + +This Recommendation, together with Recommendation ITU-T G.8012/Y.1308, supersedes Recommendation ITU-T G.8021.1/Y.1341.1 (10/2012). + +This Recommendation also removes items formerly considered for further study and incorporates terms formerly defined in Recommendation ITU-T G.8001/Y.1354 (04/2016). + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|-----------------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.8021/Y.1341 | 2004-08-22 | 15 | 11.1002/1000/7364 | +| 1.1 | ITU-T G.8021/Y.1341 (2004) Amd. 1 | 2006-06-06 | 15 | 11.1002/1000/8776 | +| 2.0 | ITU-T G.8021/Y.1341 | 2007-12-22 | 15 | 11.1002/1000/9173 | +| 2.1 | ITU-T G.8021/Y.1341 (2007) Amd. 1 | 2009-01-13 | 15 | 11.1002/1000/9661 | +| 2.2 | ITU-T G.8021/Y.1341 (2007) Amd. 2 | 2010-02-22 | 15 | 11.1002/1000/10428 | +| 3.0 | ITU-T G.8021/Y.1341 | 2010-10-22 | 15 | 11.1002/1000/10900 | +| 3.1 | ITU-T G.8021/Y.1341 (2010) Amd. 1 | 2011-07-22 | 15 | 11.1002/1000/11137 | +| 4.0 | ITU-T G.8021/Y.1341 | 2012-05-07 | 15 | 11.1002/1000/11512 | +| 4.1 | ITU-T G.8021/Y.1341 (2012) Amd. 1 | 2012-10-29 | 15 | 11.1002/1000/11777 | +| 4.2 | ITU-T G.8021/Y.1341 (2012) Amd. 2 | 2013-08-29 | 15 | 11.1002/1000/12030 | +| 5.0 | ITU-T G.8021/Y.1341 | 2015-04-06 | 15 | 11.1002/1000/12382 | +| 5.1 | ITU-T G.8021/Y.1341 (2015) Cor. 1 | 2015-08-13 | 15 | 11.1002/1000/12551 | +| 6.0 | ITU-T G.8021/Y.1341 | 2016-11-13 | 15 | 11.1002/1000/13095 | +| 7.0 | ITU-T G.8021/Y.1341 | 2018-06-06 | 15 | 11.1002/1000/13543 | +| 7.1 | ITU-T G.8021/Y.1341 (2018) Cor. 1 | 2019-08-29 | 15 | 11.1002/1000/14008 | +| 8.0 | ITU-T G.8021/Y.1341 | 2022-04-22 | 15 | 11.1002/1000/14932 | + +## Keywords + +Atomic functions, equipment functional blocks, Ethernet transport network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2022 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 3 | +| 3 Definitions ..... | 4 | +| 3.1 Terms defined elsewhere ..... | 4 | +| 3.2 Terms defined in this Recommendation..... | 5 | +| 4 Abbreviations and acronyms ..... | 6 | +| 5 Methodology and conventions..... | 10 | +| 6 Supervision ..... | 10 | +| 6.1 Defects..... | 10 | +| 6.2 Consequent actions ..... | 18 | +| 6.3 Defect correlations..... | 18 | +| 7 Information flow across reference points ..... | 18 | +| 8 Generic processes for Ethernet equipment ..... | 18 | +| 8.1 OAM related processes..... | 18 | +| 8.2 Queueing process..... | 108 | +| 8.3 Filter process ..... | 108 | +| 8.4 Replicate process ..... | 109 | +| 8.5 MAC length check process..... | 110 | +| 8.6 Server-specific processes..... | 110 | +| 9 Ethernet MAC layer (ETH) functions ..... | 112 | +| 9.1 ETH connection (ETH_C) function ..... | 116 | +| 9.2 ETH termination functions ..... | 123 | +| 9.3 ETH adaptation functions..... | 147 | +| 9.4 ETH diagnostic functions ..... | 174 | +| 9.5 Server to ETH adaptation functions (/ETH_A)..... | 192 | +| 9.6 ETH traffic conditioning and shaping functions (ETH_TCS) ..... | 194 | +| 9.7 ETH link aggregation functions ..... | 195 | +| 9.8 ETH MEP and MIP functions ..... | 205 | +| 10 Ethernet server to ETH adaptation functions ..... | 207 | +| 11 Non-Ethernet server to ETH adaptation functions ..... | 207 | +| 11.1 OTN to ETH adaptation functions ..... | 208 | +| Appendix I – Applications and functional diagrams ..... | 209 | +| Appendix II – AIS/RDI mechanism for an Ethernet private line over a single OTN server layer ..... | 210 | +| Appendix III – Compound functions ..... | 214 | +| Appendix IV – Start-up conditions ..... | 215 | +| Appendix V – SDL descriptions ..... | 216 | + +| | Page | +|----------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Appendix VI – Calculation methods for frame loss measurement ..... | 217 | +| VI.1    Dual-ended loss measurement ..... | 217 | +| VI.2    Single-ended loss measurement ..... | 217 | +| Appendix VII – Considerations of the support of a rooted multipoint EVC service..... | 219 | +| Appendix VIII – Configurations for ingress VID filtering..... | 220 | +| Appendix IX – Handling of Expected Defects ..... | 221 | +| IX.1    Interruption events..... | 221 | +| IX.2    Service activation ..... | 222 | +| IX.3    Additional considerations ..... | 223 | +| Appendix X – Mapping guidelines between the atomic functions defined in b-ITU-T
G.8021-2016 and those defined in ITU-T G.8023 ..... | 224 | +| Appendix XI – Basic Ethernet MAC layer network (ETH) equipment types ..... | 226 | +| XI.1    Provider edge bridge (PEB)..... | 228 | +| XI.2    Provider bridge (PB)..... | 230 | +| Bibliography..... | 232 | + +# Introduction + +This Recommendation forms part of a suite of ITU-T Recommendations covering the full functionality of Ethernet transport network architecture and equipment (e.g., Recommendations ITU-T G.8010/Y.1306 and ITU-T G.8012/Y.1308) and follows the principles defined in Recommendation ITU-T G.805. + +This Recommendation specifies a library of basic building blocks and a set of rules by which they may be combined in order to describe equipment used in an Ethernet transport network. The building blocks are based on atomic modelling functions defined in Recommendations ITU-T G.806 and ITU-T G.809. The library comprises the functional building blocks needed to wholly specify the generic functional structure of the Ethernet transport network. In order to be compliant with this Recommendation, the Ethernet functionality of any equipment which processes at least one of the Ethernet transport layers needs to be describable as an interconnection of a subset of these functional blocks contained within this Recommendation. The interconnections of these blocks should obey the combination rules given. + +The specification method is based on functional decomposition of the equipment into atomic and compound functions. The equipment is then described by its equipment functional specification which lists the constituent atomic and compound functions and their interconnection. + + + +# Characteristics of Ethernet transport network equipment functional blocks + +# 1 Scope + +This Recommendation covers the functional requirements of Ethernet functionality within Ethernet transport equipment. + +This Recommendation uses the specification methodology defined in [ITU-T G.806] in general for transport network equipment and is based on the architecture of Ethernet layer networks defined in [ITU-T G.8010], the interfaces for Ethernet transport networks defined in [ITU-T G.8012], and in support of services defined in [ITU-T G.8011]. It also provides processes for Ethernet OAM based on [ITU-T G.8013]. The description is generic and no particular physical partitioning of functions is implied. The input/output information flows associated with the functional blocks serve for defining the functions of the blocks and are considered to be conceptual, not physical. + +The functionality defined in this Recommendation can be applied at user-to-network interfaces (UNIs) and network-to-network interfaces (NNIs) of the Ethernet transport network. + +Not every functional block defined in this Recommendation is required for every application. Different subsets of functional blocks from this Recommendation and others (e.g., [ITU-T G.798] and [ITU-T G.806]) may be assembled in different ways according to the combination rules given in these Recommendations (e.g., [ITU-T G.806]) to provide a variety of different capabilities. Network operators and equipment suppliers may choose which functions to implement for each application. + +The internal structure of the implementation of this functionality (equipment design) need not be identical to the structure of the functional model, as long as all the details of the externally observable behaviour comply with the equipment functional specification. + +Equipment developed prior to the production of this Recommendation may not comply with all the details in this Recommendation. + +The equipment requirements described in this Recommendation are generic and no particular physical partitioning of functions is implied. The input/output information flows associated with the functional blocks define the functions of the blocks and are considered to be conceptual, not physical. + +Figure 1-1 presents a summary illustration of the set of atomic functions associated with the Ethernet signal transport. These atomic functions may be combined in various ways to support a variety of Ethernet services, some of which are illustrated in Appendix I. In order to reduce the complexity of the figures, the functions for the processing of management communication channels (e.g., OTN COMMS) are not shown. For COMMS functions, refer to the specific layer network descriptions. + +![Overview of ITU-T G.802/Y.1341 atomic model functions diagram showing various network interfaces and their connections to a central ETH bus.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +The diagram illustrates the atomic model functions for ITU-T G.802/Y.1341, centered around a horizontal oval labeled 'ETH'. + +- Top Left:** A stack of interfaces including 'ETHx/ETH', 'ETHx', 'ETH\_TFP', 'ETHD/ETH', 'ETHDe', and 'ETH\_TFP'. Above 'ETHx/ETH' is a '(Note) n' label. +- Top Middle-Left:** A stack of interfaces including 'ETHx/ETH-m', 'ETHx', 'ETH\_TFP', 'ETHD/ETH', 'ETHDe', and 'ETH\_TFP'. Above 'ETHx/ETH-m' is a '(Note) n' label. +- Top Middle:** A stack of interfaces including 'ETHG/ETH', 'ETHG', 'ETHG\_TFP', 'ETHD/ETH', 'ETHDe', and 'ETH\_TFP'. Above 'ETHG/ETH' is a '(Note) n' label. +- Top Middle-Right:** A stack of interfaces including 'ETHx/ETHG', 'ETHx', 'ETH\_TFP', 'ETHD/ETH', 'ETHDe', and 'ETH\_TFP'. Above 'ETHx/ETHG' is a '(Note) n' label. +- Top Right:** Two separate stacks. The first includes 'ETHx/BP', 'ETHx', 'ETH\_TFP', and 'ETHD/ETH'. The second includes 'ETHx/MCC', 'ETHx', 'ETH\_TFP', and 'ETHD/ETH'. +- Far Right:** A diamond-shaped 'ETH' interface with 'ETH\_FP' and 'ETH\_TFP' labels on both sides. +- Bottom Left:** A stack of interfaces including 'ETH-LAG/ETH', 'ETH-LAG', 'ETH-LAG\_TFP', 'ETH-Np/ETH-LAG-Na', 'Np', and 'ETHnull'. Above 'ETH-LAG/ETH' is a '(Note) n' label. +- Bottom Right:** A stack of interfaces including '/ETH' and '\_AP'. Above '/ETH' is a '(Note) n' label. + +Labels like 'ETH\_AP', 'ETHG\_APP', 'ETHG\_TFP', 'ETH\_TFP', 'ETHD/ETH', 'ETHDe', 'ETH\_TFP', 'ETH\_FP', and 'ETH\_TFP' are repeated throughout the diagram to indicate interface types. + +Overview of ITU-T G.802/Y.1341 atomic model functions diagram showing various network interfaces and their connections to a central ETH bus. + +NOTE – ETH\_TFP interface of adaptation functions towards the ETH\_FT functions connects to logical link control. See [ITU-T G.8010] and function definition for details. + +G.8021-Y.1341(22)\_F1-1 + +**Figure 1-1 – Overview of ITU-T G.8021/Y.1341 atomic model functions** + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.709] Recommendation ITU-T G.709/Y.1331 (2020), *Interfaces for the optical transport network (OTN)*. +- [ITU-T G.798] Recommendation ITU-T G.798 (2017), *Characteristics of optical transport network hierarchy equipment functional blocks*. +- [ITU-T G.805] Recommendation ITU-T G.805 (2000), *Generic functional architecture of transport networks*. +- [ITU-T G.806] Recommendation ITU-T G.806 (2012), *Characteristics of transport equipment Description methodology and generic functionality*. +- [ITU-T G.809] Recommendation ITU-T G.809 (2003), *Functional architecture of connectionless layer networks*. +- [ITU-T G.7041] Recommendation ITU-T G.7041/Y.1303 (2016), *Generic framing procedure*. +- [ITU-T G.7710] Recommendation ITU-T G.7710/Y.1701 (2020), *Common equipment management function requirements*. +- [ITU-T G.8010] Recommendation ITU-T G.8010/Y.1306 (2004), *Architecture of Ethernet layer networks*. +- [ITU-T G.8011] Recommendation ITU-T G.8011/Y.1307 (2020), *Ethernet service characteristics*. +- [ITU-T G.8012] Recommendation ITU-T G.8012/Y.1308 (2021), *Ethernet UNI and Ethernet NNI*. +- [ITU-T G.8013] Recommendation ITU-T G.8013/Y.1731 (2015), *OAM functions and mechanisms for Ethernet based networks*. +- [ITU-T G.8023] Recommendation ITU-T G.8023 (2018), *Characteristics of equipment functional blocks supporting Ethernet physical layer and Flex Ethernet interfaces*. +- [ITU-T G.8031] Recommendation ITU-T G.8031/Y.1342 (2015), *Ethernet linear protection switching*. +- [ITU-T G.8032] Recommendation ITU-T G.8032/Y.1344 (2020), *Ethernet ring protection switching*. +- [ITU-T Z.101] Recommendation ITU-T Z.101 (2021), *Specification and Description Language (SDL) – Basic SDL-2010*. +- [IEEE 802.1AX] IEEE 802.1AX (2020), *IEEE Standard for Local and Metropolitan Area Networks: Link Aggregation*. +- [IEEE 802.1Q] IEEE 802.1Q (2018), *IEEE Standard for Local and metropolitan area networks – Bridges and Bridged Networks*. +- [IEEE 802.3] IEEE 802.3 (2018), *IEEE Standard for Ethernet*. + +[MEF 45.1] MEF 45.1 (2018), *Layer 2 Control Protocols in Ethernet Services*. + +[OIF FLEXE IA] OIF IA OIF-FLEXE-02.1 (2019), *Flex Ethernet Implementation Agreement 2.1*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **access point**: [ITU-T G.805], [ITU-T G.809] +- 3.1.2 **adaptation**: [ITU-T G.809] +- 3.1.3 **adapted information**: [ITU-T G.809] +- 3.1.4 **characteristic information**: [ITU-T G.809] +- 3.1.5 **client/server relationship**: [ITU-T G.809] +- 3.1.6 **connection point**: [ITU-T G.805] +- 3.1.7 **connectionless trail**: [ITU-T G.809] +- 3.1.8 **consequent actions**: [ITU-T G.806] +- 3.1.9 **defect correlations**: [ITU-T G.806] +- 3.1.10 **defects**: [ITU-T G.806] +- 3.1.11 **dual-ended**: [ITU-T G.8013] +- 3.1.12 **flow**: [ITU-T G.809] +- 3.1.13 **flow domain**: [ITU-T G.809] +- 3.1.14 **flow domain flow**: [ITU-T G.809] +- 3.1.15 **flow point**: [ITU-T G.809] +- 3.1.16 **flow point pool**: [ITU-T G.809] +- 3.1.17 **flow termination**: [ITU-T G.809] +- 3.1.18 **flow termination sink**: [ITU-T G.809] +- 3.1.19 **flow termination source**: [ITU-T G.809] +- 3.1.20 **generic framing procedure (GFP)**: [ITU-T G.7041] +- 3.1.21 **jabber**: [IEEE 802.3] +- 3.1.22 **layer network**: [ITU-T G.809] +- 3.1.23 **link**: [ITU-T G.805] +- 3.1.24 **link connection**: [ITU-T G.805] +- 3.1.25 **link flow**: [ITU-T G.809] +- 3.1.26 **MAC frame**: [IEEE 802.3] +- 3.1.27 **media access control (MAC)**: [IEEE 802.3] +- 3.1.28 **network**: [ITU-T G.809] +- 3.1.29 **network connection**: [ITU-T G.805] +- 3.1.30 **network flow**: [ITU-T G.809] + +- 3.1.31 **network operator:** [b-ITU-T M.3208.1] +- 3.1.32 **network-to-network interface (NNI):** [ITU-T G.8012] +- 3.1.33 **one-way:** [ITU-T G.8013] +- 3.1.34 **ordered set:** [IEEE 802.3] +- 3.1.35 **performance filters:** [ITU-T G.806] +- 3.1.36 **physical layer entity (PHY):** [IEEE 802.3] +- 3.1.37 **port:** [ITU-T G.809] +- 3.1.38 **reference point:** [ITU-T G.805] [ITU-T G.809] +- 3.1.39 **reference points:** [ITU-T G.806] +- 3.1.40 **service provider:** [b-ITU-T M.3208.1] +- 3.1.41 **single-ended:** [ITU-T G.8013] +- 3.1.42 **termination connection point:** [ITU-T G.805] +- 3.1.43 **termination flow point:** [ITU-T G.809] +- 3.1.44 **termination flow point pool:** Refer to clause 6.3.5.5 of [ITU-T G.8010] +- 3.1.45 **timing point:** [ITU-T G.806] +- 3.1.46 **traffic conditioning function:** [ITU-T G.8010] +- 3.1.47 **traffic unit:** [ITU-T G.809] +- 3.1.48 **trail:** [ITU-T G.805] +- 3.1.49 **trail termination:** [ITU-T G.805] +- 3.1.50 **transport:** [ITU-T G.809] +- 3.1.51 **transport entity:** [ITU-T G.809] +- 3.1.52 **transport processing function:** [ITU-T G.809] +- 3.1.53 **two-way:** [ITU-T G.8013] +- 3.1.54 **user-to-network interface (UNI):** [ITU-T G.8012] + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +- 3.2.1 **Ethernet flow replication point (ETHF\_PP):** Connection point between /ETH adaptation source and sink. ETH\_CI from source Ethernet flow point (ETH\_FP) is replicated and delivered across ETHF\_PP to sink Ethernet termination flow point (ETH\_TFP). +- 3.2.2 **Ethernet replicated information (ETH\_PI):** Replicated ETH\_CI delivered across ETHTF\_PP or ETHF\_PP. +- 3.2.3 **Ethernet termination flow replication point (ETHTF\_PP):** Connection point between /ETH adaptation source and sink. ETH\_CI from source Ethernet termination flow point (ETH\_TFP) is replicated and delivered across ETHTF\_PP to sink filter process. +- 3.2.4 **traffic shaping function:** A transport processing function that accepts the characteristic information of the layer network at its input, classifies the traffic units according to configured rules, meters each traffic unit within its class to determine its eligibility, controls non-conformant traffic units by buffering and scheduling them alternately with conformant traffic units for presentation at its output as characteristic information of the layer network. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|--------------------------------| +| IDM | 1-way Delay Measurement | +| A | Adaptation function | +| AI | Adapted Information | +| AIS | Alarm Indication Signal | +| AP | Access Point | +| APP | Access Point Pool | +| APS | Automatic Protection Switching | +| BER | Bit Error Ratio | +| BN | Bandwidth Notification | +| BNM | Bandwidth Notification Message | +| BS | Bad Second | +| C | Connection Function | +| CC | Continuity Check | +| CCM | Continuity Check Message | +| C-EC | Customer Ethernet Connection | +| CI | Characteristic Information | +| CK | Clock | +| COMMS | Communications channel | +| CoS | Class of Service | +| CP | Connection Point | +| CRC | Cyclic Redundancy Check | +| CSF | Client Signal Fail | +| D | Data | +| DA | Destination Address | +| DCI | Defect Clear Indication | +| DCN | Data Communication Network | +| DE | Drop Eligibility | +| DEI | Drop Eligible Identifier | +| DEG | Degraded | +| DEGM | Degraded M | +| DEGTHR | Degraded Threshold | +| DM | Delay Measurement | +| DMM | Delay Measurement Message | +| DMR | Delay Measurement Reply | +| EC | Ethernet Connection | + +| | | +|--------|-----------------------------------------------------------------------------------| +| ED | Expected Defect | +| EDM | Expected Defect Message | +| EMF | Equipment Management Function | +| EPL | Ethernet Private Line | +| ETH | Ethernet Media Access Control layer network | +| ETH_CI | Ethernet Media Access Control Characteristic Information | +| ETHD | Ethernet MAC layer network Diagnostic function | +| ETHDe | Ethernet MAC layer network Diagnostic function within MEP | +| ETHDi | Ethernet MAC layer network Diagnostic function within MIP | +| ETHG | Ethernet MAC layer network Group | +| ETH-m | Ethernet MAC layer network – multiplexing | +| ETHx | Ethernet MAC layer network at level $x$ ( $x$ = path, tandem connection, section) | +| ETY | Ethernet physical layer network | +| EVC | Ethernet Virtual Connection | +| EXM | Extension Header Mismatch | +| FCS | Frame Check Sequence | +| FD | Flow Domain | +| FD | Frame Delay | +| FDI | Forward Defect Indication | +| FDV | Frame Delay Variation | +| FF | Flow Forwarding | +| FOP | Failure Of Protocol | +| FP | Flow Point | +| FS | Frame Start | +| FT | Flow Termination | +| GFP | Generic Framing Procedure | +| GFP-F | Generic Framing Procedure – Frame mapped | +| GNM | Generic Notification Message | +| GS | Good Second | +| LAG | Link Aggregation | +| LAN | Local Area Network | +| LB | LoopBack | +| LBM | LoopBack Message | +| LBR | LoopBack Reply | +| LCAS | Link Capacity Adjustment Scheme | +| LCK | Lock | +| L-EC | Link Ethernet Connection | + +| | | +|------|---------------------------------------------| +| LF | Lost Frames | +| LFD | Loss of Frame Delineation | +| LM | Loss Measurement | +| LMM | Loss Measurement Message | +| LMR | Loss Measurement Reply | +| LOC | Loss Of Continuity | +| LOS | Loss Of Signal | +| LT | Link Trace | +| LTM | Link Trace Message | +| LTR | Link Trace Reply | +| M-AI | Media layer Adapted Information | +| MAC | Media Access Control | +| MCC | Maintenance Communication Channel | +| ME | Maintenance Entity | +| MEG | Maintenance Entity Group | +| MEL | Maintenance Entity group Level | +| MEP | Maintenance entity group End Point | +| MI | Management Information | +| MIP | Maintenance entity group Intermediate Point | +| MMG | Mismerge | +| MP | Management Point | +| MSDU | Media access control Service Data Unit | +| NCM | Network Connection Monitoring | +| NNI | Network-to-Network Interface | +| OAM | Operations, Administration and Maintenance | +| ODU | Optical channel Data Unit | +| ODUk | Optical channel Data Unit – order k | +| OO | Out of Order | +| OPC | OpCode | +| OPU | Optical channel Payload Unit | +| OTN | Optical Transport Network | +| OUI | Organizational Unique Identifier | +| P | Priority | +| PCP | Priority Code Point | +| PCS | Physical Convergence Sublayer | +| PDU | Protocol Data Unit | +| PEB | Provider Edge Bridge | + +| | | +|-------|------------------------------------------------| +| PEP | Provider Edge Port | +| PHY | Physical layer entity | +| PI | replication Information | +| PLM | Payload Mismatch | +| PNP | Provider Network Port | +| PP | replication Point | +| PP-OS | Preamble, Payload, and Ordered Set information | +| PRBS | Pseudo-Random Bit Sequence | +| QoS | Quality of Service | +| R-APS | Ring-Automatic Protection Switching | +| REC | Received | +| RES | Reserved | +| RDI | Remote Defect Indication | +| RI | Remote Information | +| RP | Remote Point | +| RxFCf | Received Frame Count far end | +| RxFCI | Received Frame Count local | +| SA | Source Address | +| SDU | Service Data Unit | +| S-EC | Service Ethernet Connection | +| SL | Synthetic Loss | +| SLM | Synthetic Loss Message | +| SLR | Synthetic Loss Reply | +| SNC | Sub-Network Connection | +| SSD | Server Signal Degrade | +| SSF | Server Signal Fail | +| svd | saved | +| TA | Target MAC Address | +| TCI | Tag Control Information | +| TCM | Tandem Connection Monitoring | +| TCP | Trail Connection Point | +| TCS | Traffic Conditioning and Shaping | +| TF | Transmitted Frames | +| TFP | Termination Flow Point | +| TI | Timing Information | +| TID | Transaction Identifier | +| TLV | Type, Length, Value | + +| | | +|-------|-----------------------------------------------------| +| TP | Timing Point | +| TSD | Trail Signal Degrade | +| TSF | Trail Signal Fail | +| TST | Test | +| TT | Trail Termination | +| TTL | Time To Live | +| TxFCf | Transmitted Frame Count far end | +| TxFCI | Transmitted Frame Count local | +| UNI | User-to-Network Interface | +| UNL | Unexpected maintenance entity group Level | +| UNM | Unexpected Maintenance entity group end point | +| UNP | Unexpected Period | +| UNPr | Unexpected Priority | +| UPI | (Generic Framing Procedure) User Payload Identifier | +| UPM | User Payload Mismatch | +| VID | Virtual local area network Identifier | +| VCAT | Virtual Concatenation | +| VLAN | Virtual Local Area Network | + +# 5 Methodology and conventions + +For the basic methodology to describe transport network functionality of network elements, refer to clause 5 of [ITU-T G.806]. For Ethernet-specific extensions to the methodology, see clause 5 of [ITU-T G.8010]. + +All process descriptions in clauses 6, 8 and 9 use the SDL methodology defined in [ITU-T Z.101]. Pseudocode in this recommendation uses "switch" statements where each "case" statement is exclusive (i.e., "case" statements do not fall through to each other). + +The conventions `_[IEEE 802.1AX oAggregator mandatory objects]`, `_[IEEE 802.1AX oAggregationPort mandatory objects]`, `_[IEEE 802.1Q]`, and `_[IEEE 802.3]` are used to indicate the MI\_ input/output signals required to map the management attributes, defined in [IEEE 802.1AX], [IEEE 802.1Q], and [IEEE 802.3], to the [IEEE 802.1AX], [IEEE 802.1Q], and [IEEE 802.3] processes supported by a given function or process. Their detailed definition is intentionally left outside the scope of this Recommendation. + +# 6 Supervision + +The generic supervision functions are defined in clause 6 of [ITU-T G.806]. Specific supervision functions for the Ethernet transport network are defined in this clause. + +## 6.1 Defects + +### 6.1.1 Summary of detection and clearance conditions for defects + +The defect detection and clearance conditions are based on events. Occurrence or absence of specific events may detect or clear specific defects. + +In the following: + +Valid means a received value is equal to the value configured via the MI input interface(s). + +Invalid means a received value is not equal to the value configured via the MI input interface(s). + +The events defined for this Recommendation are summarized in Table 6-1. Events, other than automatic protection switching (APS) or ring-automatic protection switching (R-APS) events are generated by processes in the ETHx\_FT\_Sk function as defined in clause 9.2.1.2. APS events are generated by the subnetwork connection protection process as defined in clause 9.1.2. R-APS events are generated by the ring protection control process as defined in clause 9.1.3. These processes define the exact conditions for these events, Table 6-1 only provides a quick overview. + +**Table 6-1 – Overview of events** + +| Event | Meaning | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| unexpMEL | Reception of a continuity check message (CCM) frame with an invalid MEL value | +| unexpMEG | Reception of a CCM frame with an invalid MEG value, but with a valid MEL value | +| unexpMEP | Reception of a CCM frame with an invalid MEP value, but with valid MEL and MEG values | +| unexpPeriod | Reception of a CCM frame with an invalid periodicity value, but with valid MEL, MEG and MEP values | +| unexpPriority | Reception of a CCM frame with an invalid priority value, but with valid MEL, MEG, MEP and periodicity values | +| expCCM[i] | Reception of a CCM frame with valid MEL, MEG, MEP and periodicity values, where an MEP is indexed by "i" | +| RDI[i]=x | Reception by an MEP indexed by "i" of a CCM frame with valid MEL, MEG, MEP and periodicity values and the RDI flag set to x; where x=0 (remote defect clear) and x=1 (remote defect set) | +| LCK | Reception of a LCK frame | +| AIS | Reception of an adapted information signal (AIS) frame | +| CSF-LOS | Reception of a CSF frame that indicates a client loss of signal | +| CSF-FDI | Reception of a CSF frame that indicates a client forward defect indication | +| CSF-RDI | Reception of a CSF frame that indicates a client reverse defect indication | +| BS | Bad second, a second in which the lost frame ratio exceeds the degraded threshold (MI_LM_DEGTHR) | +| expAPS | Reception of a valid APS frame | +| expRAPS | Reception of a valid R-APS frame | +| APSw | Reception of an APS frame from the working transport entity | +| APSb | Reception of an APS frame with incompatible "B" bit value | +| APSr | Reception of an APS frame with incompatible "Requested Signal" value (Note) | +| RAPSpm | Reception by the RPL owner of an R-APS(NR, RB) frame with a node ID that differs from its own | +| NOTE – One way to detect this event is to detect that the transmitted "Requested Signal" and the received "Requested Signal" values differ, for example in case traffic switching occurs due to a local request. | | + +The occurrence or absence of these events may detect or clear a defect. An overview of the conditions is given in Table 6-2. The notation "#event=x (K\*period)" is used to indicate the occurrence of x events within the period as specified between the brackets; $3.25 \leq K \leq 3.5$ . + +Table 6-2 gives a quick overview of the detection and clearance conditions for the various defects. In the following clauses 6.1.2, 6.1.3, 6.1.4 and 6.1.5 the precise conditions are specified using SDL diagrams. + +**Table 6-2 – Overview of defect detection and clearance** + +| Defect | Defect detection | Defect clearance | +|----------|--------------------------------------------------------------------------------------|---------------------------------------------------------| +| dLOC[] | #expCCM[] == 0 (K*MI_CC_Period) | expCCM[] | +| dUNL | unexpMEL | #unexpMEL == 0 (K*CCM_Period) | +| dUNPr | unexpPriority | #unexpPriority == 0 (K*CCM_Period) | +| dMMG | unexpMEG | #unexpMEG == 0 (K*CCM_Period) | +| dUNM | unexpMEP | #unexpMEP == 0 (K*CCM_Period) | +| dUNP | unexpPeriod | #unexpPeriod == 0 (K*CCM_Period) | +| dRDI[] | RDI[] == 1 | RDI[] == 0 | +| dAIS | AIS | #AIS == 0 (K*AIS_Period) | +| dLCK | LCK | #LCK == 0 (K*LCK_Period) | +| dCSF-LOS | CSF-LOS | #CSF-LOS == 0
(K*CSF_Period or CSF-DCI) | +| dCSF-FDI | CSF-FDI | #CSF-FDI == 0
(K*CSF_Period or CSF-DCI) | +| dCSF-RDI | CSF-RDI | #CSF-RDI == 0
(K*CSF_Period or CSF-DCI) | +| dDEG | #BadSecond == 1
(MI_LM_DEGM*1second) | #BadSecond == 0
(MI_LM_M*1second) | +| dFOP-CM | APSw | #APSw == 0 (K*normal APS Period) | +| dFOP-PM | APSb or RAPSPm | expAPS or #RAPSPm == 0
(K*long R-APS frame interval) | +| dFOP-NR | APSr continues more than 50 ms | expAPS | +| dFOP-TO | #expAPS==0 (K * long APS interval) or
#expRAPS==0 (K * long R-APS frame interval) | expAPS or expRAPS | + +Note that for the case of CCM\_Period, AIS\_Period, LCK\_Period, and CSF\_Period the values for the CCM, AIS, LCK, and CSF periods are based on the periodicity as indicated in the CCM, AIS, LCK, or CSF frame that triggered the timer to be started. + +For dUNL, dMMG, dUNM, dUNP, dUNPr there may be multiple frames received detecting the same defect but carrying a different periodicity. In that case the longest received period will be used. See the detailed descriptions below. + +### 6.1.2 Continuity supervision + +![Flowchart of the dLOC[] detection and clearance process.](812e188283162af0b54fb3e30ffee51b_img.jpg) + +``` +graph TD; + Start([dLOC detection and clearance]) --> Set1[Set(K*MI_CC_Period, Timer)]; + Set1 --> Cleared([dLOC[i] Cleared]); + Cleared --> expCCM1[/expCCM[i]/]; + Cleared --> Timer[/Timer/]; + expCCM1 --> Reset[Reset(Timer) +Set(K*MI_CC_Period, Timer)]; + Timer --> dLOCi[/dLOC[i]/]; + Reset --> Detected([dLOC[i] detected]); + dLOCi --> Detected; + Detected --> expCCM2[/expCCM[i]/]; + expCCM2 --> Set2[Set(K*MI_CC_Period, Timer)]; + Set2 --> NotdLOC[/!dLOC[i]/]; + NotdLOC --> Set1; +``` + +The flowchart illustrates the dLOC[] detection and clearance process. It begins with a rounded rectangle labeled 'dLOC detection and clearance', which points down to a rectangle 'Set(K\*MI\_CC\_Period, Timer)'. This rectangle points down to a rounded rectangle 'dLOC[i] Cleared'. From 'dLOC[i] Cleared', the flow splits into two parallel paths: one through a parallelogram 'expCCM[i]' to a rectangle 'Reset(Timer)' followed by 'Set(K\*MI\_CC\_Period, Timer)', and another through a parallelogram 'Timer' to a parallelogram 'dLOC[i]'. Both paths converge at a rounded rectangle 'dLOC[i] detected'. From 'dLOC[i] detected', the flow proceeds through a parallelogram 'expCCM[i]' to a rectangle 'Set(K\*MI\_CC\_Period, Timer)', which then leads to a parallelogram '!dLOC[i]'. Finally, an arrow loops back from '!dLOC[i]' to the 'Set(K\*MI\_CC\_Period, Timer)' rectangle at the top of the loop. + +G.8021-Y.1341(16)\_F6-1 + +Flowchart of the dLOC[] detection and clearance process. + +**Figure 6-1 – dLOC[] detection and clearance process** + +#### 6.1.2.1 Loss of continuity defect (dLOC[]) + +The loss of continuity defect is calculated at the ETH layer. It monitors the presence of continuity in ETH trails. + +Its detection and clearance are defined in Figure 6-1. The timer in Figure 6-1 is set to $K * MI\_CC\_Period$ , where $MI\_CC\_Period$ corresponds to the configured CCM period and $K$ is such that $3.25 \leq K \leq 3.5$ . + +NOTE – The dLOC entry/exit criteria defined in this version of the Recommendation are different to those defined in previous versions of this Recommendation (i.e., the 2007 and 2010 versions), because they have been aligned with those defined in clause 21 of [IEEE 802.1Q]. This change impacts only the conditions for defect detection and therefore does not affect interoperability between equipment compliant with this version of the Recommendation (and/or with clause 21 of [IEEE 802.1Q]) and those compliant with older versions of this Recommendation. + +### 6.1.3 Connectivity supervision + +![Flowchart showing the defect detection and clearance process. It starts with 'Defect detection and clearance' and proceeds through various states including ' Cleared', '(Period)', '', and 'Set(K*Period, Timer)'. It then enters a loop for ' Detected' with three branches: one for handling new events with period checks, one for clear events, and one for timer expiration. All branches eventually loop back to the start or the detection state.](08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg) + +``` + +graph TD + Start([Defect detection and clearance]) --> Cleared( Cleared) + Cleared --> Event1[/(Period)/] + Event1 --> Defect1[//] + Defect1 --> Set1[Set(K*Period, Timer) +Old_Period=Period] + Set1 --> Detected( Detected) + + Detected --> Event2[/(Period)/] + Detected --> ClearEvent[//] + Detected --> Timer[/Timer/] + + Event2 --> Reset1[Reset(Timer)] + ClearEvent --> Reset2[Reset(Timer)] + Timer --> NotDefect1[/!/] + + Reset1 --> PeriodCheck{Period NotDefect2[/!/] + + PeriodCheck -- Y --> SetOld[Set(K*Old_Period, Timer)] + PeriodCheck -- N --> SetNew[Set(K*Period, Timer)] + + SetNew --> OldPeriod[Old_Period=Period] + + SetOld --> Detected + OldPeriod --> Detected + + NotDefect1 --> Cleared + NotDefect2 --> Cleared + + subgraph Footer + direction LR + Label[G.8021-Y.1341(16)_F6-2] + end + style Label fill:none,stroke:none + +``` + +Flowchart showing the defect detection and clearance process. It starts with 'Defect detection and clearance' and proceeds through various states including ' Cleared', '(Period)', '', and 'Set(K\*Period, Timer)'. It then enters a loop for ' Detected' with three branches: one for handling new events with period checks, one for clear events, and one for timer expiration. All branches eventually loop back to the start or the detection state. + +**Figure 6-2 – Defect detection and clearance process for dUNL, dMMG, dUNM, dUNP, dUNPr, dAIS, dLCK, and dCSF** + +Figure 6-2 shows a generic state diagram that is used to detect and clear the dUNL, dMMG, dUNM, dUNP, dUNPr, dAIS, dLCK and dCSF defects. In this diagram needs to be replaced with the specific defect and with the specific event related to this defect. Furthermore, in Figure 6-2, $3.25 \leq K \leq 3.5$ . + +Figure 6-2 shows that the timer is set based on the last received period value, unless an earlier OAM frame triggering (and therefore the detection of ) carried a longer period. As a consequence, clearing certain defects may take more time than necessary. + +#### 6.1.3.1 Unexpected MEL defect (dUNL) + +The unexpected MEL defect is calculated at the ETH layer. It monitors the connectivity in a maintenance entity group. + +Its detection and clearance are defined in Figure 6-2. The in Figure 6-2 is dUNL. The in Figure 6-2 is the unexpMEL event (generated by the CCM reception process in clause 8.1.7.3) and the period is the period carried in the CCM frame that triggered this event, unless an earlier CCM frame triggering an unexpMEL event carried a greater period. + +#### 6.1.3.2 Mismatch defect (dMMG) + +The mismatch defect is calculated at the ETH layer. It monitors the connectivity in a maintenance entity group. + +Its detection and clearance are defined in Figure 6-2. The in Figure 6-2 is dMMG. The in Figure 6-2 is the unexpMEG event (as generated by the CCM reception process in clause 8.1.7.3) and the period is the period carried in the CCM frame that triggered the event, unless an earlier CCM frame triggering an unexpMEG event carried a greater period. + +#### 6.1.3.3 Unexpected MEP defect (dUNM) + +The unexpected MEP defect is calculated at the ETH layer. It monitors the connectivity in a maintenance entity group. + +Its detection and clearance are defined in Figure 6-2. The in Figure 6-2 is dUNM. The in Figure 6-2 is the unexpMEP event (as generated by the CCM reception process in clause 8.1.7.3) and the period is the period carried in the CCM frame that triggered the event, unless an earlier CCM frame triggering an unexpMEP event carried a greater period. + +#### 6.1.3.4 Degraded signal defect (dDEG) + +This defect is only defined for point-to-point ETH connections. + +![Flowchart of the dDEG detection and clearance process. The process starts with 'dDEC detection and clearance', followed by 'BS=GS=0' and 'BadSecond=0'. It then branches into two main paths: 'dDEG Cleared' and 'dDEG detected'. The 'dDEG Cleared' path involves 'nN_TF(N_TF)' and 'nN_LF(N_LF)', 'Update BS and GS', and a decision 'BS==MI_LM_DEGM'. The 'dDEG detected' path involves 'nN_TF(N_TF)' and 'nN_LF(N_LF)', 'Update BS and GS', and a decision 'GS==MI_LM_M'. Both paths lead to 'dDEG' or '!dDEG'. A separate path on the right starts with 'Update BS and GS', followed by a decision 'If ((N_TF>MI_LM_TFMIN) && (N_LF>=0))'. If 'Yes', it goes to 'If ((N_LF/N_TF)>MI_LM_DEGTHR)'. If 'Yes', 'BadSecond=1'. If 'No', 'BadSecond=0'. Both lead to 'If BadSecond'. If 'Yes', 'GS=0' and 'BS++'. If 'No', 'GS++' and 'BS=0'. All final states lead to a circle with an 'X'.](19a59d6b53059ebd27b13c98793f88e0_img.jpg) + +``` + +graph TD + Start([dDEC detection and clearance]) --> Init[BS=GS=0 +BadSecond=0] + Init --> Cleared([dDEG Cleared]) + Init --> Detected([dDEG detected]) + Cleared --> nNTF1[nN_TF(N_TF) +nN_LF(N_LF)] + nNTF1 --> UpdateBS1[Update BS and GS] + UpdateBS1 --> BS_EQ{BS==MI_LM_DEGM} + BS_EQ -- No --> Cleared + BS_EQ -- Yes --> dDEG1[dDEG] + Detected --> nNTF2[nN_TF(N_TF) +nN_LF(N_LF)] + nNTF2 --> UpdateBS2[Update BS and GS] + UpdateBS2 --> GS_EQ{GS==MI_LM_M} + GS_EQ -- No --> Detected + GS_EQ -- Yes --> NotdDEG1[!dDEG] + dDEG1 --> Join((X)) + NotdDEG1 --> Join + UpdateBS3([Update BS and GS]) --> If1{If ((N_TF>MI_LM_TFMIN) +&& (N_LF>=0))} + If1 -- No --> BadSecond0_1[BadSecond=0] + If1 -- Yes --> If2{If ((N_LF/N_TF)> +MI_LM_DEGTHR)} + If2 -- No --> BadSecond0_2[BadSecond=0] + If2 -- Yes --> BadSecond1[BadSecond=1] + BadSecond1 --> IfBadSecond{If BadSecond} + BadSecond0_1 --> IfBadSecond + BadSecond0_2 --> IfBadSecond + IfBadSecond -- Yes --> GS0[GS=0 +BS++] + IfBadSecond -- No --> GSInc[GS++ +BS=0] + GS0 --> Join + GSInc --> Join + style Start fill:none,stroke:none + style Init fill:none,stroke:none + style UpdateBS1 fill:none,stroke:none + style UpdateBS2 fill:none,stroke:none + style UpdateBS3 fill:none,stroke:none + style dDEG1 fill:none,stroke:none + style NotdDEG1 fill:none,stroke:none + style BadSecond1 fill:none,stroke:none + style BadSecond0_1 fill:none,stroke:none + style BadSecond0_2 fill:none,stroke:none + style GS0 fill:none,stroke:none + style GSInc fill:none,stroke:none + style Join fill:none,stroke:none + style BS_EQ fill:none,stroke:none + style GS_EQ fill:none,stroke:none + style If1 fill:none,stroke:none + style If2 fill:none,stroke:none + style IfBadSecond fill:none,stroke:none + style nNTF1 fill:none,stroke:none + style nNTF2 fill:none,stroke:none + +``` + +Flowchart of the dDEG detection and clearance process. The process starts with 'dDEC detection and clearance', followed by 'BS=GS=0' and 'BadSecond=0'. It then branches into two main paths: 'dDEG Cleared' and 'dDEG detected'. The 'dDEG Cleared' path involves 'nN\_TF(N\_TF)' and 'nN\_LF(N\_LF)', 'Update BS and GS', and a decision 'BS==MI\_LM\_DEGM'. The 'dDEG detected' path involves 'nN\_TF(N\_TF)' and 'nN\_LF(N\_LF)', 'Update BS and GS', and a decision 'GS==MI\_LM\_M'. Both paths lead to 'dDEG' or '!dDEG'. A separate path on the right starts with 'Update BS and GS', followed by a decision 'If ((N\_TF>MI\_LM\_TFMIN) && (N\_LF>=0))'. If 'Yes', it goes to 'If ((N\_LF/N\_TF)>MI\_LM\_DEGTHR)'. If 'Yes', 'BadSecond=1'. If 'No', 'BadSecond=0'. Both lead to 'If BadSecond'. If 'Yes', 'GS=0' and 'BS++'. If 'No', 'GS++' and 'BS=0'. All final states lead to a circle with an 'X'. + +G.8021-Y.1341(16)\_F6-3 + +Figure 6-3 – dDEG detection and clearance process + +The degraded signal defect is calculated at the ETH layer. It monitors the connectivity of an ETH trail. + +Its detection and clearance are defined in Figure 6-3. + +Every second the state machine receives the one-second counters for near end received and transmitted frames and determines whether the second was a bad second. The defect is detected if there are MI\_LM\_DEGM consecutive bad seconds and cleared if there are MI\_LM\_M consecutive good seconds. + +In order to declare a bad second, the number of transmitted frames must exceed a threshold (MI\_LM\_TFMIN). Furthermore, if the frame loss ratio (lost frames/transmitted frames) is greater than MI\_LM\_DEGTHR, a bad second is declared. + +### 6.1.4 Protocol supervision + +#### 6.1.4.1 Unexpected periodicity defect (dUNP) + +The unexpected periodicity defect is calculated at the ETH layer. It detects the configuration of different periodicities at different MEPs belonging to the same MEG. + +Its detection and clearance are defined in Figure 6-2. The in Figure 6-2 is dUNP. The in Figure 6-2 is the unexpPeriod event (as generated by the CCM reception process in clause 8.1.7.3) and the period is the period carried in the CCM frame that triggered the event, unless an earlier CCM frame triggering an unexpPeriod event carried a greater period. + +#### 6.1.4.2 Unexpected priority defect (dUNPr) + +The unexpected priority defect is calculated at the ETH layer. It detects the configuration of different priorities for CCM at different MEPs belonging to the same MEG. + +Its detection and clearance are defined in Figure 6-2. The in Figure 6-2 is dUNPr. The in Figure 6-2 is the unexpPriority event (as generated by the CCM reception process in clause 8.1.7.3) and the period is the period carried in the CCM frame that triggered the event, unless an earlier CCM frame triggering an unexpPriority event carried a greater period. + +#### 6.1.4.3 Protection protocol supervision + +##### 6.1.4.3.1 Linear or ring protection failure of protocol provisioning mismatch (dFOP-PM) + +The failure of protocol provisioning mismatch defect is calculated at the ETH layer. It monitors the provisioning mismatch of: + +- linear protection by comparing B bits of the transmitted and the received APS protocol, or +- ring protection by comparing the node ID of the RPL owner and the node ID in a received R-APS(NR, RB) frame. + +Its detection and clearance are defined in Table 6-2. dFOP-PM is detected: + +- in the case of linear protection, on receipt of an APSb event and cleared on receipt of an expAPS event. These events are generated by the subnetwork connection protection process (clause 9.1.2), or +- in the case of ring protection, on receipt of an RAPSPm event and cleared on receipt of no RAPSPm event during K times the long R-APS frame intervals defined in [ITU-T G.8032], where $3.25 \leq K \leq 3.5$ . These events are generated by the ring protection control process (clause 9.1.3). + +##### 6.1.4.3.2 Linear protection failure of protocol no response (dFOP-NR) + +The failure of protocol no response defect is calculated at the ETH layer. It monitors incompletion of protection switching by comparing the transmitted "Requested Signal" values and the received "Requested Signal" in the APS protocol. + +Its detection and clearance are defined in Table 6-2. dFOP-NR is detected when an APSr event continues for more than 50 ms and it is cleared on receipt of the expAPS event. These events are generated by the subnetwork connection protection process (clause 9.1.2). This defect is not applied in the case of a unidirectional protection switching operation. + +##### 6.1.4.3.3 Linear protection failure of protocol configuration mismatch (dFOP-CM) + +The failure of protocol configuration mismatch defect is calculated at the ETH layer. It monitors working and protection configuration mismatch by detecting the receipt of the APS protocol from the working transport entity. + +Its detection and clearance are defined in Table 6-2. dFOP-CM is detected on receipt of an APSw event and cleared on receipt of no APSw event during K times the normal APS transmission period defined in [ITU-T G.8031], where $3.25 \leq K \leq 3.5$ . These events are generated by the subnetwork connection protection process (clause 9.1.2). + +##### 6.1.4.3.4 Linear or ring protection failure of protocol time out (dFOP-TO) + +The failure of protocol time out defect is calculated at the ETH layer. It monitors the time out defect of: + +- linear protection by detecting the prolonged absence of expected APS frames, or +- ring protection by detecting the prolonged absence of expected R-APS frames. + +Its detection and clearance are defined in Table 6-2. + +In the case of linear protection, dFOP-TO is detected on receipt of no expAPS event during K times the long APS interval defined in [ITU-T G.8031] (where $K \geq 3.5$ ). dFOP-TO is cleared on receipt of an expAPS event. These events are generated by the subnetwork connection protection process (clause 9.1.2). + +In the case of ring protection, dFOP-TO is detected on receipt of no expRAPS event during K times the long R-APS frame intervals defined in [ITU-T G.8032] (where $K \geq 3.5$ ). dFOP-TO is cleared on receipt of an expRAPS event. These events are generated by the ring protection control process (clause 9.1.3). + +### 6.1.5 Maintenance signal supervision + +#### 6.1.5.1 Remote defect indicator defect (dRDI[]) + +The remote defect indicator defect is calculated at the ETH layer. It monitors the presence of an RDI maintenance signal. + +dRDI is detected on receipt of the $RDI[]=1$ event and cleared on receipt of the $RDI[]=0$ event. These events are generated by the CCM reception process. + +#### 6.1.5.2 Alarm indication signal defect (dAIS) + +The alarm indication signal defect is calculated at the ETH layer. It monitors the presence of an AIS maintenance signal. + +Its detection and clearance conditions are defined in Figure 6-2. The in Figure 6-2 is dAIS. The in Figure 6-2 is the AIS event (as generated by the AIS reception process in clause 9.2.1.2) and the period is the period carried in the AIS frame that triggered the event, unless an earlier AIS frame carried a greater period. + +#### 6.1.5.3 Locked defect (dLCK) + +The locked defect is calculated at the ETH layer. It monitors the presence of a locked maintenance signal. + +Its detection and clearance conditions are defined in Figure 6-2. The in Figure 6-2 is dLCK. The in Figure 6-2 is the LCK event (as generated by the LCK reception process in clause 9.2.1.2) and the period is the period carried in the LCK frame that triggered the event, unless an earlier LCK frame carried a greater period. + +#### 6.1.5.4 Client signal fail defect (dCSF) + +The CSF (CSF-LOS, CSF-FDI, and CSF-RDI) defect is calculated at the ETH layer. It monitors the presence of a CSF maintenance signal. + +Its detection and clearance conditions are defined in Figure 6-2. The in Figure 6-2 is dCSF-LOS, dCSF-FDI, or dCSF-RDI. The in Figure 6-2 is the CSF event (as generated by the CSF extract process in clause 8.1.17) and the period is the period carried in the CSF frame that triggered the event, unless an earlier CSF frame carried a greater period. + +The in Figure 6-2 is the CSF event which indicates defect clear indication (DCI). + +## 6.2 Consequent actions + +For consequent actions see [ITU-T G.806] and the specific atomic functions. + +## 6.3 Defect correlations + +For defect correlations see the specific atomic functions. + +# 7 Information flow across reference points + +See clause 7 of [ITU-T G.806] for the generic description of information flow. For Ethernet-specific information flow, see the description of the functions in clause 9. + +# 8 Generic processes for Ethernet equipment + +This clause defines processes specific to equipment supporting the Ethernet transport network. + +## 8.1 OAM related processes + +### 8.1.1 OAM MEL filter + +![Diagram of the OAM MEL filter process. A central purple box labeled 'OAM MEL Filter' has three input ports on the left labeled 'Port 1', '2', and 'N'. Each input port has three incoming arrows labeled 'P', 'DE', and 'D'. Each output port has three outgoing arrows labeled 'P', 'DE', and 'D'. A signal labeled 'MI_MEL' enters the filter from the right. The diagram is labeled 'G.8021-Y.1341(12)_F8-1' at the bottom right.](298e7e2164a95d0d5bb8e5d1f7155094_img.jpg) + +The diagram illustrates the OAM MEL filter process. A central purple rectangular block is labeled "OAM MEL Filter". On the left side, there are three input ports labeled "Port 1", "2", and "N". Each input port has three incoming arrows labeled "P", "DE", and "D". On the right side, there are three corresponding output ports, each with three outgoing arrows labeled "P", "DE", and "D". A signal labeled "MI\_MEL" enters the filter from the right. The diagram is labeled "G.8021-Y.1341(12)\_F8-1" at the bottom right. + +Diagram of the OAM MEL filter process. A central purple box labeled 'OAM MEL Filter' has three input ports on the left labeled 'Port 1', '2', and 'N'. Each input port has three incoming arrows labeled 'P', 'DE', and 'D'. Each output port has three outgoing arrows labeled 'P', 'DE', and 'D'. A signal labeled 'MI\_MEL' enters the filter from the right. The diagram is labeled 'G.8021-Y.1341(12)\_F8-1' at the bottom right. + +Figure 8-1 – OAM MEL filter process + +The OAM MEL filter process filters incoming ETH OAM traffic units based on the MEL they carry. All traffic units with an MEL equal to or lower than the MEL provided by the MI\_MEL signal are discarded. + +The criteria for filtering depends on the values of the fields in the MSDU field of the ETH\_CI\_D signal. + +The ETH OAM traffic unit and complementing P and DE signals will be filtered, if + +- length/type field = OAM EtherType (89-02 as defined in clause 10 of [ITU-T G.8013]), and +- MEL field $\leq$ MI\_MEL + +Figure 8-1 shows the OAM MEL filter process for multiple ports. Figure 8-2 shows the filtering process that is running per port. + +![Flowchart of OAM MEL filter behaviour](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` +graph TD; + Start([OAM MEL filter]) --> Running([Running]); + Running --> Input[/D(D),P(P),DE(DE)/]; + Input --> Decision{Etype(D)=89-02 & +MEL(D)≤MI_MEL}; + Decision -- Y --> LoopBack(( )); + Decision -- N --> Output[/D(D),P(P),DE(DE)/]; + Output --> LoopBack; + LoopBack --> Running; + style LoopBack width:0px,height:0px; +``` + +The flowchart illustrates the OAM MEL filter process. It begins with an oval labeled 'OAM MEL filter', which points down to another oval labeled 'Running'. This in turn points down to a parallelogram labeled 'D(D),P(P),DE(DE)'. Below this is a decision diamond labeled 'Etype(D)=89-02 & MEL(D)≤MI\_MEL'. If the condition is 'Y' (Yes), the flow loops back to the 'Running' oval via a junction point. If the condition is 'N' (No), the flow proceeds to another parallelogram labeled 'D(D),P(P),DE(DE)' before looping back to the 'Running' oval. A small label 'G.8021-Y.1341(16)\_F8-2' is located at the bottom right of the diagram. + +Flowchart of OAM MEL filter behaviour + +**Figure 8-2 – OAM MEL filter behaviour** + +### 8.1.2 LCK generation process + +![Diagram of LCK generation process](088921fa3f5a44c8551815122517eefd_img.jpg) + +``` +graph LR; + subgraph LCK_Block [ ] + direction TB + LCK[LCK +Generate] + end + + LCK --> P[P] + LCK --> DE[DE] + LCK --> D[D] + + MI1[MI_MEP_MAC] --> LCK + MI2[MI_Client_MEL] --> LCK + MI3[MI_LCK_Period] --> LCK + MI4[MI_LCK_Pri] --> LCK +``` + +The diagram shows a central block labeled 'LCK Generate'. From the top of the block, three arrows labeled 'P', 'DE', and 'D' point upwards. On the right side, four arrows point into the block from the right, labeled 'MI\_MEP\_MAC', 'MI\_Client\_MEL', 'MI\_LCK\_Period', and 'MI\_LCK\_Pri'. A small label 'G.8021-Y.1341(12)\_F8-3' is located at the bottom of the diagram. + +Diagram of LCK generation process + +**Figure 8-3 – LCK generation process** + +The LCK generation process (see Figure 8-3) generates ETH\_CI traffic units where the ETH\_CI\_D signal contains the LCK signal. Figure 8-4 defines the behaviour of the LCK generation process. + +![Flowchart of LCK generation behaviour. The process starts with 'LCK generation' (oval), followed by 'Set(0, Timer)' (rectangle). A loop begins with 'LCK Generate' (oval), 'Timer' (parallelogram), 'OAM=LCK( MI_MEP_MAC, MI_Client_MEL, MI_LCK_Period )' (rectangle), 'D(OAM, P(MI_LCK_Pri), DE(0))' (parallelogram), and 'Set(MI_LCK_Period, Timer)' (rectangle). A feedback arrow loops from the final step back to the entry point of the 'LCK Generate' step. The diagram is labeled G.8021-Y.1341(16)_F8-4 at the bottom.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +``` + +graph TD + A([LCK generation]) --> B[Set(0, Timer)] + B --> C([LCK Generate]) + C --> D[/Timer/] + D --> E[OAM=LCK( +MI_MEP_MAC, +MI_Client_MEL, +MI_LCK_Period +) ] + E --> F[/D(OAM, +P(MI_LCK_Pri), +DE(0)) /] + F --> G[Set(MI_LCK_Period, Timer)] + G --> C + +``` + +G.8021-Y.1341(16)\_F8-4 + +Flowchart of LCK generation behaviour. The process starts with 'LCK generation' (oval), followed by 'Set(0, Timer)' (rectangle). A loop begins with 'LCK Generate' (oval), 'Timer' (parallelogram), 'OAM=LCK( MI\_MEP\_MAC, MI\_Client\_MEL, MI\_LCK\_Period )' (rectangle), 'D(OAM, P(MI\_LCK\_Pri), DE(0))' (parallelogram), and 'Set(MI\_LCK\_Period, Timer)' (rectangle). A feedback arrow loops from the final step back to the entry point of the 'LCK Generate' step. The diagram is labeled G.8021-Y.1341(16)\_F8-4 at the bottom. + +**Figure 8-4 – LCK generation behaviour** + +The LCK generation process continuously generates LCK traffic units; every time the timer expires an LCK traffic unit will be generated. The period between two consecutive traffic units is determined by the MI\_LCK\_Period input signal. Allowed values are defined in Table 8-1. + +**Table 8-1 – LCK period values** + +| 3-bits | Period value | Comments | +|---------|---------------|----------------------------| +| 000-011 | Invalid value | Invalid value for LCK PDUs | +| 100 | 1 s | 1 frame per second | +| 101 | Invalid value | Invalid value for LCK PDUs | +| 110 | 1 min | 1 frame per minute | +| 111 | Invalid value | Invalid value for LCK PDUs | + +The ETH\_CI\_D signal contains a source and destination address field and an MSDU field. The format of the MSDU field for LCK traffic units is defined in clauses 9.1 and 9.8 of [ITU-T G.8013]. The MEL in the MSDU field is determined by the MI\_Client\_MEL input parameter. + +The values of the source and destination address fields in the ETH\_CI\_D signal are determined by the local MAC address (SA) and the multicast class 1 DA as described in [ITU-T G.8013] (DA). The value of the multicast class 1 DA is 01-80-C2-00-00-3x, where x is equal to MI\_Client\_MEL as defined in clause 10.1 of [ITU-T G.8013]. The value of MI\_MEP\_MAC should be a valid unicast MAC address. + +The periodicity (as defined by MI\_LCK\_Period) is encoded in the three least significant bits of the flags field in the LCK PDU using the values from Table 8-1. + +The LCK (SA, Client\_MEL, Period) function generates an LCK traffic unit with the SA, MEL and period fields defined by the values of the parameters. Figure 8-5 below shows the ETH\_CI\_D signal format resulting from the function call from Figure 8-4: + +OAM=LCK( +MI\_MEP\_MAC, +MI\_Client\_MEL, +MI\_LCK\_Period +) + +![](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +| 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +|-------------------------------------------------|---|---|---|---|------------------------|---|---|----------------|---|---|---|---|---|---|---|---------------------|---|---|---|-------------|---|---|---|-------------------|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| DA = 01-80-C2-00-00-3x, where x = MI_Client_MEL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | SA = MI_MEP_MAC | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EtherType = 89-02 | | | | | | | | | | | | | | | | MEL = MI_Client_MEL | | | | Version = 0 | | | | OpCode = 35 (LCK) | | | | | | | | +| 0 | 0 | 0 | 0 | 0 | Period = MI_LCK_Period | | | TLV Offset = 0 | | | | | | | | End TLV = 0 | | | | | | | | | | | | | | | | + +G.8021-Y.1341(16)\_F8-5 + +**Figure 8-5 – LCK traffic unit** + +The value of the ETH\_CI\_P signal associated with the generated LCK traffic units is defined by the MI\_LCK\_Pri input parameter; valid values are in the range 0-7. + +The value of the ETH\_CI\_DE signal associated with the generated LCK traffic units is always set to drop ineligible. + +### 8.1.3 Selector process + +![Diagram of the Selector process. A 'Selector' block contains two sub-blocks: 'Normal' and 'LCK'. The 'Normal' block has inputs P, DE, and D. The 'LCK' block also has inputs P, DE, and D. An external input 'MI_Admin_State' points to the 'Selector' block. The output of the 'Selector' block is labeled P, DE, and D. A reference label 'G.8021-Y.1341(12)_F8-6' is at the bottom.](f2ea0f64a770b22b902820457d262265_img.jpg) + +``` + +graph LR + subgraph Selector + direction LR + Normal[Normal] + LCK[LCK] + end + InNormalP[P] --> Normal + InNormalDE[DE] --> Normal + InNormalD[D] --> Normal + InLCKP[P] --> LCK + InLCKDE[DE] --> LCK + InLCKD[D] --> LCK + MI_Admin_State --> Selector + Selector --> OutP[P] + Selector --> OutDE[DE] + Selector --> OutD[D] + +``` + +G.8021-Y.1341(12)\_F8-6 + +Diagram of the Selector process. A 'Selector' block contains two sub-blocks: 'Normal' and 'LCK'. The 'Normal' block has inputs P, DE, and D. The 'LCK' block also has inputs P, DE, and D. An external input 'MI\_Admin\_State' points to the 'Selector' block. The output of the 'Selector' block is labeled P, DE, and D. A reference label 'G.8021-Y.1341(12)\_F8-6' is at the bottom. + +**Figure 8-6 – Selector process** + +The selector process (see Figure 8-6) selects the valid signal from the input of the normal ETH\_CI signal or the ETH\_CI LCK signal (as generated by the LCK generation process). The normal signal is blocked if MI\_Admin\_State is LOCKED. The behaviour is defined in Figure 8-7. + +![Figure 8-7: Selector behaviour flowchart. The process starts with a 'Selector' block leading to a 'Normal' state. In the 'Normal' state, three paths are shown: 1) 'Normal.D(D), Normal.P(P), Normal.DE(DE)' leading to 'D(D),P(P),DE(DE)'; 2) 'LCK.D(D), LCK.P(P), LCK.DE(DE)'; 3) 'MI_Admin_State(State)' leading to a decision 'State=Locked?'. If 'State=Locked?' is 'Y', it leads to the 'Locked' state. If 'State=Locked?' is 'N', it loops back to the 'Normal' state. In the 'Locked' state, three paths are shown: 1) 'Normal.D(D), Normal.P(P), Normal.DE(DE)'; 2) 'LCK.D(D), LCK.P(P), LCK.DE(DE)' leading to 'D(D),P(P),DE(DE)'; 3) 'MI_Admin_State(State)' leading to a decision 'State=Normal?'. If 'State=Normal?' is 'Y', it loops back to the 'Normal' state. If 'State=Normal?' is 'N', it loops back to the 'Locked' state. The diagram is labeled G.8021-Y.1341(16)_F8-7.](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +Figure 8-7: Selector behaviour flowchart. The process starts with a 'Selector' block leading to a 'Normal' state. In the 'Normal' state, three paths are shown: 1) 'Normal.D(D), Normal.P(P), Normal.DE(DE)' leading to 'D(D),P(P),DE(DE)'; 2) 'LCK.D(D), LCK.P(P), LCK.DE(DE)'; 3) 'MI\_Admin\_State(State)' leading to a decision 'State=Locked?'. If 'State=Locked?' is 'Y', it leads to the 'Locked' state. If 'State=Locked?' is 'N', it loops back to the 'Normal' state. In the 'Locked' state, three paths are shown: 1) 'Normal.D(D), Normal.P(P), Normal.DE(DE)'; 2) 'LCK.D(D), LCK.P(P), LCK.DE(DE)' leading to 'D(D),P(P),DE(DE)'; 3) 'MI\_Admin\_State(State)' leading to a decision 'State=Normal?'. If 'State=Normal?' is 'Y', it loops back to the 'Normal' state. If 'State=Normal?' is 'N', it loops back to the 'Locked' state. The diagram is labeled G.8021-Y.1341(16)\_F8-7. + +Figure 8-7 – Selector behaviour + +### 8.1.4 AIS insert process + +![Figure 8-8: AIS insert process symbol. The symbol is a rectangular block labeled 'AIS Insert'. It has three input signals on the left: 'aAIS' (top), 'P' (middle), and 'DE' (bottom). It has three output signals on the right: 'P' (top), 'DE' (middle), and 'D' (bottom). It also has four management interface inputs on the right: 'MI_MEP_MAC', 'MI_Client_MEL', 'MI_AIS_Period', and 'MI_AIS_Pri'. The diagram is labeled G.8021-Y.1341(12)_F8-8.](dd5771673aececa53d42ece89218299d_img.jpg) + +Figure 8-8: AIS insert process symbol. The symbol is a rectangular block labeled 'AIS Insert'. It has three input signals on the left: 'aAIS' (top), 'P' (middle), and 'DE' (bottom). It has three output signals on the right: 'P' (top), 'DE' (middle), and 'D' (bottom). It also has four management interface inputs on the right: 'MI\_MEP\_MAC', 'MI\_Client\_MEL', 'MI\_AIS\_Period', and 'MI\_AIS\_Pri'. The diagram is labeled G.8021-Y.1341(12)\_F8-8. + +Figure 8-8 – AIS insert process + +Figure 8-8 shows the AIS insert process symbol, and Figure 8-9 defines the behaviour. If the aAIS signal is true, the AIS insert process continuously generates ETH\_CI traffic units where the ETH\_CI\_D signal contains the AIS signal until the aAIS signal is false. The generated AIS traffic units are inserted in the incoming stream, i.e., the output stream contains the incoming traffic units and the generated AIS traffic units. + +![Flowchart of AIS insert behaviour. The process starts with 'AIS insert' leading to 'AIS Disabled'. From 'AIS Disabled', it branches to 'aAIS(1)' and 'D(D),P(P),DE(DE)'. 'aAIS(1)' leads to 'Set (0, Timer)', which then leads to 'AIS Enabled'. 'D(D),P(P),DE(DE)' also leads to 'AIS Enabled'. From 'AIS Enabled', it branches to 'aAIS(0)', 'Timer', and 'D(D),P(P),DE(DE)'. 'aAIS(0)' loops back to 'AIS Disabled'. 'Timer' leads to 'OAM=AIS( MI_MEP_MAC, MI_Client_MEL, MI_AIS_Period )', which leads to 'D(OAM), P(MI_AIS_Pri), DE(0)', which leads to 'Set(MI_AIS_Period, Timer)'. 'D(D),P(P),DE(DE)' loops back to 'AIS Disabled'. A small text 'G.8021-Y.1341(16)_F8-9' is at the bottom right.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +``` + +graph TD + AIS_insert([AIS insert]) --> AIS_Disabled([AIS Disabled]) + AIS_Disabled --> aAIS1[/aAIS(1)/] + AIS_Disabled --> DDPDE1[/D(D),P(P),DE(DE)/] + aAIS1 --> Set0Timer[Set (0, Timer)] + DDPDE1 --> DDPDE2[/D(D),P(P),DE(DE)/] + Set0Timer --> AIS_Enabled([AIS Enabled]) + DDPDE2 --> AIS_Enabled + AIS_Enabled --> aAIS0[/aAIS(0)/] + AIS_Enabled --> Timer[/Timer/] + AIS_Enabled --> DDPDE3[/D(D),P(P),DE(DE)/] + aAIS0 --> AIS_Disabled + Timer --> OAM_AIS["OAM=AIS( MI_MEP_MAC, MI_Client_MEL, MI_AIS_Period )"] + OAM_AIS --> D_OAM["D(OAM), P(MI_AIS_Pri), DE(0)"] + D_OAM --> SetMI_AIS_Period["Set(MI_AIS_Period, Timer)"] + DDPDE3 --> DDPDE4[/D(D),P(P),DE(DE)/] + DDPDE4 --> AIS_Enabled + SetMI_AIS_Period --> AIS_Enabled + +``` + +G.8021-Y.1341(16)\_F8-9 + +Flowchart of AIS insert behaviour. The process starts with 'AIS insert' leading to 'AIS Disabled'. From 'AIS Disabled', it branches to 'aAIS(1)' and 'D(D),P(P),DE(DE)'. 'aAIS(1)' leads to 'Set (0, Timer)', which then leads to 'AIS Enabled'. 'D(D),P(P),DE(DE)' also leads to 'AIS Enabled'. From 'AIS Enabled', it branches to 'aAIS(0)', 'Timer', and 'D(D),P(P),DE(DE)'. 'aAIS(0)' loops back to 'AIS Disabled'. 'Timer' leads to 'OAM=AIS( MI\_MEP\_MAC, MI\_Client\_MEL, MI\_AIS\_Period )', which leads to 'D(OAM), P(MI\_AIS\_Pri), DE(0)', which leads to 'Set(MI\_AIS\_Period, Timer)'. 'D(D),P(P),DE(DE)' loops back to 'AIS Disabled'. A small text 'G.8021-Y.1341(16)\_F8-9' is at the bottom right. + +**Figure 8-9 – AIS insert behaviour** + +The period between consecutive AIS traffic units is determined by the MI\_AIS\_Period parameter. Allowed values are once per second and once per minute; the encoding of these values is defined in Table 8-2. Note that this encoding is the same as for the LCK generation process. + +**Table 8-2 – AIS period values** + +| 3-bits | Period Value | Comments | +|---------|---------------|----------------------------| +| 000-011 | Invalid Value | Invalid value for AIS PDUs | +| 100 | 1 s | 1 frame per second | +| 101 | Invalid Value | Invalid value for AIS PDUs | +| 110 | 1 min | 1 frame per minute | +| 111 | Invalid Value | Invalid value for AIS PDUs | + +The ETH\_CI\_D signal contains a source and destination address field and an MSDU field. The format of the MSDU field for AIS traffic units is defined in clauses 9.1 and 9.7 of [ITU-T G.8013]. The MEL in the MSDU field is determined by the MI\_Client\_MEL input parameter. + +The values of the source and destination address fields in the ETH\_CI\_D signal are determined by the local MAC address (SA) and the multicast class 1 DA as described in [ITU-T G.8013] (DA). The value of the multicast class 1 DA is 01-80-C2-00-00-3x, where x is equal to MI\_Client\_MEL as defined in clause 10.1 of [ITU-T G.8013]. The value of MI\_MEP\_MAC should be a valid unicast MAC address. + +The periodicity (as defined by MI\_AIS\_Period) is encoded in the three least significant bits of the flags field in the AIS PDU using the values from Table 8-2. + +The AIS (SA, Client\_MEL, Period) function generates an AIS traffic unit with the SA, MEL and period fields defined by the values of the parameters. Figure 8-10 below shows the ETH\_CI\_D signal format resulting from the function call from Figure 8-9: + +``` +OAM=AIS( +MI_MEP_MAC, +MI_Client_MEL, +MI_AIS_Period +) +``` + +![](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +| | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +|----|-------------------------------------------------|---|---|---|---|------------------------|----------------|---|---|---|---|---|---|---|-------------|---|---------------------|---|---|---|-------------|---|---|---|-------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | DA = 01-80-C2-00-00-3x, where x = MI_Client_MEL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | | | | | | SA = MI_MEP_MAC | | | | | | | | | | | | | | | | +| 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 13 | EtherType = 89-02 | | | | | | | | | | | | | | | | MEL = MI_Client_MEL | | | | Version = 0 | | | | OpCode = 33 (AIS) | | | | | | | | +| 17 | 0 | 0 | 0 | 0 | 0 | Period = MI_AIS_Period | TLV Offset = 0 | | | | | | | | End TLV = 0 | | | | | | | | | | | | | | | | | | + +G.8021-Y.1341(16)\_F8-10 + +Figure 8-10 – AIS traffic unit + +The value of the ETH\_CI\_P signal associated with the generated AIS traffic units is defined by the MI\_AIS\_Pri input parameter; valid values are in the range 0-7. + +The value of the ETH\_CI\_DE signal associated with the generated AIS traffic units is always set to drop ineligible. + +### 8.1.5 APS insert process + +![Diagram of the APS insert process. A central block labeled 'APS Insert' has three input arrows from the top labeled APS, P, and DE. It has three output arrows to the bottom labeled P, DE, and D. It also has three input arrows from the right labeled MI_MEP_MAC, MI_MEL, and MI_APS_Pri. A small text label G.8021-Y.1341(12)_F8-11 is at the bottom left of the diagram.](80ec3bf791fd8eb41f73a420c2122529_img.jpg) + +Diagram of the APS insert process. A central block labeled 'APS Insert' has three input arrows from the top labeled APS, P, and DE. It has three output arrows to the bottom labeled P, DE, and D. It also has three input arrows from the right labeled MI\_MEP\_MAC, MI\_MEL, and MI\_APS\_Pri. A small text label G.8021-Y.1341(12)\_F8-11 is at the bottom left of the diagram. + +Figure 8-11 – APS insert process + +The APS insert process encodes the ETH\_CI\_APS (APS input signal in Figure 8-11) signal into the ETH\_CI\_D signal of an ETH\_CI traffic unit; the resulting APS traffic unit is inserted into the stream of incoming traffic units, i.e., the outgoing stream consists of the incoming traffic units and the inserted APS traffic units. The ETH\_CI\_APS signal contains the APS specific information as defined in clause 11.1 of [ITU-T G.8031] (APS format). The behaviour is defined in Figure 8-12. + +![Flowchart of APS insert behaviour. The process starts with 'APS insert', leading to 'Waiting'. From 'Waiting', it branches into two paths. The left path shows a traffic unit 'D(D),P(P),DE(DE)' being processed. The right path shows 'APS(APS)' being processed by 'OAM=APS( MI_MEP_MAC, MI_MEL, APS )', resulting in a traffic unit 'D(OAM),P(MI_APS_Pri), DE(0)'. Both paths then merge back into the 'Waiting' state. A reference code 'G.8021-Y.1341(16)_F8-12' is at the bottom right.](c76da2d73c064464051d1583fd80bb6b_img.jpg) + +``` + +graph TD + APS_insert([APS insert]) --> Waiting([Waiting]) + Waiting --> LeftPath[/D(D),P(P),DE(DE)/] + Waiting --> RightPath[/APS(APS)/] + LeftPath --> LeftOut[/D(D),P(P),DE(DE)/] + RightPath --> OAM[OAM=APS( +MI_MEP_MAC, +MI_MEL, +APS +) ] + OAM --> RightOut[/D(OAM),P(MI_APS_Pri), +DE(0)/] + LeftOut --> Waiting + RightOut --> Waiting + +``` + +G.8021-Y.1341(16)\_F8-12 + +Flowchart of APS insert behaviour. The process starts with 'APS insert', leading to 'Waiting'. From 'Waiting', it branches into two paths. The left path shows a traffic unit 'D(D),P(P),DE(DE)' being processed. The right path shows 'APS(APS)' being processed by 'OAM=APS( MI\_MEP\_MAC, MI\_MEL, APS )', resulting in a traffic unit 'D(OAM),P(MI\_APS\_Pri), DE(0)'. Both paths then merge back into the 'Waiting' state. A reference code 'G.8021-Y.1341(16)\_F8-12' is at the bottom right. + +**Figure 8-12 – APS insert behaviour** + +The ETH\_CI\_D signal contains a source and destination address field and an MSDU field. The format of the MSDU field for APS traffic units is defined in clauses 9.1 and 9.10 of [ITU-T G.8013]. The MEL in the MSDU field is determined by the MI\_MEL input parameter. + +The values of the source and destination address fields in the ETH\_CI\_D signal are determined by the local MAC address (SA) and the multicast class 1 DA as described in [ITU-T G.8013] (DA). The value of the multicast class 1 DA is 01-80-C2-00-00-3x, where x is equal to MI\_MEL as defined in clause 10.1 of [ITU-T G.8013]. The value of MI\_MEP\_MAC should be a valid unicast MAC address. The APS(SA, MEL, APS) function generates an APS traffic unit with the SA, MEL and APS fields defined by the values of the parameters. Figure 8-13 below shows the ETH\_CI\_D signal format resulting from the function call from Figure 8-12: + +``` + +OAM=APS( +MI_MEP_MAC, +MI_MEL, +APS +) + +``` + +![](7ae836e598020d937ed1478c2ef13025_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----|------------------------------------------|---|---|---|---|---|---|---|----------------|---|---|---|---|---|---|---|--------------------------------|-------------|-------------------|---|---|---|---|---|---|---|---|---|---|---|---|---| +| | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | DA = 01-80-C2-00-00-3x, where x = MI_MEL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | | | | | | SA = MI_MEP_MAC | | | | | | | | | | | | | | | | +| 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 13 | EtherType = 89-02 | | | | | | | | | | | | | | | | MEL = MI_MEL | Version = 0 | OpCode = 39 (APS) | | | | | | | | | | | | | | +| 17 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | TLV Offset = 4 | | | | | | | | APS_Specific_Information = APS | | | | | | | | | | | | | | | | +| 21 | APS_Specific_Information continued | | | | | | | | | | | | | | | | End TLV = 0 | | | | | | | | | | | | | | | | + +G.8021-Y.1341(16)\_F8-13 + +**Figure 8-13 – APS traffic unit** + +The value of the ETH\_CI\_P signal associated with the generated APS traffic units is determined by the MI\_APS\_Pri input parameter; valid values are in the range 0-7. + +The value of the ETH\_CI\_DE signal associated with the generated APS traffic units is always set to drop ineligible. + +### **8.1.6 APS extract process** + +![Diagram of the APS extract process. A central block labeled 'APS Extract' has an input 'MI_MEL' from the left. It has four output arrows pointing up labeled 'APS', 'P', 'DE', and 'D'. It also has four input arrows pointing up from below labeled 'P', 'DE', and 'D' (the last one is unlabeled).](a4b963a07cc368283154762c4b156fe7_img.jpg) + +G.8021-Y.1341(12)\_F8-14 + +Diagram of the APS extract process. A central block labeled 'APS Extract' has an input 'MI\_MEL' from the left. It has four output arrows pointing up labeled 'APS', 'P', 'DE', and 'D'. It also has four input arrows pointing up from below labeled 'P', 'DE', and 'D' (the last one is unlabeled). + +**Figure 8-14 – APS extract process** + +The APS extract process (see Figure 8-14) extracts ETH\_CI\_APS signals from the incoming stream of ETH\_CI traffic units. ETH\_CI\_APS signals are only extracted if they belong to the MEL as defined by the MI\_MEL input parameter. + +If an incoming traffic unit is an APS traffic unit belonging to the MEL defined by MI\_MEL, the ETH\_CI\_APS signal will be extracted from this traffic unit and the traffic unit will be filtered. The ETH\_CI\_APS is the APS specific information contained in the received traffic unit. All other traffic units will be transparently forwarded. The encoding of the ETH\_CI\_D signal for APS frames is defined in clause 9.10 of [ITU-T G.8013]. + +The criteria for filtering are based on the values of the fields within the MSDU field of the ETH\_CI\_D signal: + +- length/type field equals the OAM EtherType (89-02) +- MEL field equals MI\_MEL +- OAM type equals APS (39), as defined in clause 9.1 of [ITU-T G.8013]. + +This is defined in Figure 8-15. The function APS(D) extracts the APS specific information from the received traffic unit. + +![Flowchart of APS extract behaviour. The process starts with 'APS extract', followed by 'Waiting', then 'D(D,P(P),DE(DE))'. A decision diamond asks 'Etype(D)=89-02 & MEL(D)<=MI_MEL & OPC(D)=39?'. If 'N' (No), it goes to 'D(D,P(P),DE(DE))'. If 'Y' (Yes), it goes to 'APS(APS(D))'. Both paths lead to a common exit point labeled 'G.8021-Y.1341(16)_F8-15'.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +``` + +graph TD + APS_extract([APS extract]) --> Waiting[/Waiting/] + Waiting --> D_DP_DE[/D(D,P(P),DE(DE))/] + D_DP_DE --> Decision{Etype(D)=89-02 & MEL(D)<=MI_MEL & OPC(D)=39?} + Decision -- N --> D_DP_DE_out[/D(D,P(P),DE(DE))/] + Decision -- Y --> APS_APD[/APS(APS(D))/] + D_DP_DE_out --> Exit(( )) + APS_APD --> Exit + Exit -.-> G8021Y134116_F815[G.8021-Y.1341(16)_F8-15] + +``` + +Flowchart of APS extract behaviour. The process starts with 'APS extract', followed by 'Waiting', then 'D(D,P(P),DE(DE))'. A decision diamond asks 'Etype(D)=89-02 & MEL(D)<=MI\_MEL & OPC(D)=39?'. If 'N' (No), it goes to 'D(D,P(P),DE(DE))'. If 'Y' (Yes), it goes to 'APS(APS(D))'. Both paths lead to a common exit point labeled 'G.8021-Y.1341(16)\_F8-15'. + +Figure 8-15 – APS extract behaviour + +### 8.1.7 Continuity check (CC) processes + +#### 8.1.7.1 Overview + +![Diagram showing the overview of processes involved with continuity check across three entities: MEP, MIP, and MEP. It details the flow of CCM frames, OAM data, and control signals between these entities. The left MEP includes blocks for Counter, Proactive OAM Insertion, CCM Generation, CCM Reception, and Proactive OAM Extraction. The MIP includes On-demand OAM Extraction and On-demand OAM Insertion. The right MEP includes Proactive OAM Extraction, Counter, CCM Reception, CCM Generation, and Proactive OAM Insertion. Various interfaces like ETH_CI, RI_CC_RxFCI, RI_CC_TxFCI, and MI_..._Enable are shown.](9870bf462aa0d916a16d14b5a100c60a_img.jpg) + +The diagram illustrates the continuity check (CC) process across three entities: MEP, MIP, and MEP. The flow of data and control signals is as follows: + +- Left MEP:** + - CCM Generation:** Receives inputs from MI\_CC\_Pri, MI\_CC\_Enable, MI\_LMC\_Enable, MI\_MEG\_ID, MI\_MEP\_ID, MI\_CC\_Period, MI\_CC\_Pri, and RI\_CC\_RDI. It generates CCM frames and sends them to the Counter and Proactive OAM Insertion blocks. + - Proactive OAM Insertion:** Receives CCM frames from the Counter and inserts them into the ETH\_CI stream. + - CCM Reception:** Receives CCM frames from the Proactive OAM Extraction block and processes them. It outputs RDI[i] and Events. + - Proactive OAM Extraction:** Receives CCM frames from the ETH\_CI stream and extracts them for the CCM Reception block. + - Counter:** Counts CCM frames and provides data to the CCM Generation and Proactive OAM Insertion/Extraction blocks. + - LMp:** Receives RI\_CC\_RxFCI and RI\_CC\_TxFCI signals and provides MI\_LMC\_Enable to the CCM Generation and CCM Reception blocks. +- MIP:** + - On-demand OAM Extraction:** Receives CCM frames from the ETH\_CI stream and extracts them for the CCM Reception block in the right MEP. + - On-demand OAM Insertion:** Receives CCM frames from the CCM Generation block in the right MEP and inserts them into the ETH\_CI stream. +- Right MEP:** + - CCM Reception:** Receives CCM frames from the On-demand OAM Extraction block and processes them. It outputs RDI[i] and Events. + - CCM Generation:** Receives inputs from MI\_CC\_Pri, MI\_CC\_Enable, MI\_LMC\_Enable, MI\_MEG\_ID, MI\_MEP\_ID, MI\_CC\_Period, MI\_CC\_Pri, and RI\_CC\_RDI. It generates CCM frames and sends them to the Counter and Proactive OAM Insertion blocks. + - Proactive OAM Insertion:** Receives CCM frames from the Counter and inserts them into the ETH\_CI stream. + - Proactive OAM Extraction:** Receives CCM frames from the ETH\_CI stream and extracts them for the CCM Reception block. + - Counter:** Counts CCM frames and provides data to the CCM Generation and Proactive OAM Insertion/Extraction blocks. + - LMp:** Receives RI\_CC\_RxFCI and RI\_CC\_TxFCI signals and provides MI\_LMC\_Enable to the CCM Generation and CCM Reception blocks. + +Common interfaces and signals include: + +- ETH\_CI:** Ethernet Client Interface, used for sending and receiving CCM frames. +- RI\_CC\_RxFCI / RI\_CC\_TxFCI:** Remote Fault Control Information, used for fault detection. +- MI\_...\_Enable:** Management Interface enable signals for various CC functions. +- MI\_MEG\_ID / MI\_MEP\_ID:** Management Interface MEG and MEP IDs, used for identification. +- MI\_CC\_Pri / MI\_CC\_Period:** Management Interface CC priority and period settings. +- RI\_CC\_RDI:** Remote Defect Indication, used for defect detection. +- CCM Reception / CCM Generation:** Blocks responsible for processing and generating CCM frames. +- Proactive OAM Insertion / Proactive OAM Extraction:** Blocks responsible for inserting and extracting OAM data into/from the data stream. +- Counter:** Blocks responsible for counting CCM frames. +- LMp:** Link Management Protocol block, used for fault detection and management. +- Events / RDI[i]:** Output signals from the CCM Reception blocks indicating detected events or defects. +- Counters:** Output signals from the Counter blocks indicating the number of CCM frames received or transmitted. + +Diagram showing the overview of processes involved with continuity check across three entities: MEP, MIP, and MEP. It details the flow of CCM frames, OAM data, and control signals between these entities. The left MEP includes blocks for Counter, Proactive OAM Insertion, CCM Generation, CCM Reception, and Proactive OAM Extraction. The MIP includes On-demand OAM Extraction and On-demand OAM Insertion. The right MEP includes Proactive OAM Extraction, Counter, CCM Reception, CCM Generation, and Proactive OAM Insertion. Various interfaces like ETH\_CI, RI\_CC\_RxFCI, RI\_CC\_TxFCI, and MI\_...\_Enable are shown. + +G.8021-Y.1341(12)\_F8-16 + +Figure 8-16 – Overview of processes involved with continuity check + +Figure 8-16 gives an overview of the processes involved in the CC. The CCM generation process generates the CCM frames if MI\_CC\_Enable is true. The MI\_MEG\_ID and MI\_MEP\_ID are the MEG and MEP IDs of the MEP itself and these IDs are carried in the CCM frame. The CCM frames + +are generated with a periodicity determined by MI\_CC\_Period and with a priority determined by MI\_CC\_Pri. If MI\_LMC\_Enable is set the CCM frames will also carry loss measurement information. The generated CCM traffic units are inserted in the flow of ETH\_CI by the OAM MEP source insertion process. + +The CCM frames pass transparently through MIPs. + +The OAM MEP sink extraction process extracts the CCM unit from the flow of ETH\_CI and the CCM reception process processes the received CCM traffic unit. It compares the received MEG ID with the provisioned MI\_MEG\_ID, and the received MEP\_ID with the provisioned MI\_PeerMEP\_ID[], that contains the list of all expected peer MEPs in the MEG. Based on the processing of this frame one or more events may be generated that serve as input for the defect detection process (not shown in Figure 8-16). + +RDI information is carried in the CCM frame based upon the RI\_CC\_RDI input. It is extracted in the CCM reception process. + +#### 8.1.7.2 CCM generation process + +![Flowchart of the CCM generation process. It starts with 'CCM generation' leading to 'Disabled'. From 'Disabled', it goes to 'MI_CC_Enable'. If 'MI_CC_Enable' is true, it goes to 'Set(MI_CC_Period, Timer)' and then to 'Enabled'. From 'Enabled', it branches to 'Timer' and '!'MI_CC_Enable'. 'Timer' leads to a decision 'MI_LM_Enable?'. If 'N' (No), it generates an OAM=CCM frame with specific fields. If 'Y' (Yes), it generates a similar frame but includes TxFCf, RI_CC_RxFCf, and RI_CC_TxFcf. Both frame generation paths lead to 'D(OAM), P(MI_CC_Pri), DE(0)' and then to 'Set(MI_CC_Period, Timer)'. The '!'MI_CC_Enable' path leads to 'Stop(Timer)' and loops back to the entry point before 'Disabled'.](fcbc3c31776721edc98ceb1944ec438f_img.jpg) + +``` + +graph TD + Start([CCM generation]) --> Disabled([Disabled]) + Disabled --> MI_CC_Enable{{MI_CC_Enable}} + MI_CC_Enable -- True --> Set1[Set(MI_CC_Period, Timer)] + Set1 --> Enabled([Enabled]) + Enabled --> Timer{{Timer}} + Enabled --> NotMI_CCEnable{{!MI_CC_Enable}} + NotMI_CCEnable --> StopTimer[Stop(Timer)] + StopTimer --> Disabled + Timer --> MI_LM_Enable{MI_LM_Enable?} + MI_LM_Enable -- N --> OAM_N[OAM=CCM( +MI_CC_MEG, +MI_CC_MEP, +MI_CC_Period, +RI_CC_RDI, +0, +0, +) ] + MI_LM_Enable -- Y --> OAM_Y[OAM=CCM( +MI_CC_MEG, +MI_CC_MEP, +MI_CC_Period, +RI_CC_RDI, +TxFCf, +RI_CC_RxFCf, +RI_CC_TxFcf, +) ] + OAM_N --> D_OAM[D(OAM), P(MI_CC_Pri), DE(0)] + OAM_Y --> D_OAM + D_OAM --> Set2[Set(MI_CC_Period, Timer)] + Set2 --> Enabled + +``` + +Flowchart of the CCM generation process. It starts with 'CCM generation' leading to 'Disabled'. From 'Disabled', it goes to 'MI\_CC\_Enable'. If 'MI\_CC\_Enable' is true, it goes to 'Set(MI\_CC\_Period, Timer)' and then to 'Enabled'. From 'Enabled', it branches to 'Timer' and '!'MI\_CC\_Enable'. 'Timer' leads to a decision 'MI\_LM\_Enable?'. If 'N' (No), it generates an OAM=CCM frame with specific fields. If 'Y' (Yes), it generates a similar frame but includes TxFCf, RI\_CC\_RxFCf, and RI\_CC\_TxFcf. Both frame generation paths lead to 'D(OAM), P(MI\_CC\_Pri), DE(0)' and then to 'Set(MI\_CC\_Period, Timer)'. The '!'MI\_CC\_Enable' path leads to 'Stop(Timer)' and loops back to the entry point before 'Disabled'. + +G.8021-Y.1341(16)\_F8-17 + +Figure 8-17 – CCM generation behaviour + +Figure 8-17 shows the state diagram for the CCM generation process. The CCM generation process can be enabled and disabled using the MI\_CC\_Enable signal, where the default value is FALSE. + +The CCM generation process generates and transmits an OAM frame every MI\_CC\_Period. The allowed values for MI\_CC\_Period are defined in Table 8-3. + +**Table 8-3 – CCM period values** + +| 3-bits | Period value | Comments | +|--------|---------------|----------------------------| +| 000 | Invalid value | Invalid value for CCM PDUs | +| 001 | 3.33 ms | 300 frames per second | +| 010 | 10 ms | 100 frames per second | +| 011 | 100 ms | 10 frames per second | +| 100 | 1 s | 1 frame per second | +| 101 | 10 s | 6 frames per minute | +| 110 | 1 min | 1 frame per minute | +| 111 | 10 min | 6 frame per hour | + +The ETH\_CI\_D signal contains a source and destination address field and an MSDU field. The format of the MSDU field is defined in clauses 9.1 and 9.2 of [ITU-T G.8013]. + +The value of the destination address field (DA) is the multicast class 1 DA as described in [ITU-T G.8013]. The value of the multicast class 1 DA is 01-80-C2-00-00-3x, where x is equal to MI\_MEL as defined in clause 10.1 of [ITU-T G.8013]. This x will be filled in later by the OAM MEP insertion process and will be undefined in this process. The value of the source address will be filled in later by the OAM MEP insertion process and will be undefined in this process. + +The MSDU field contains a CCM PDU. Figure 8-18 below shows the MSDU field where the CCM specific values are shown. It shows the traffic unit resulting from the function call in Figure 8-17: + +``` +OAM=CCM( + MI_CC_MEG, + MI_CC_MEP, + MI_CC_Period, + RI_CC_RDI, + TxFCI, + RI_CC_RxFCI, + RI_CC_TxFCF +) + +, or if !MI_LMC_Enable: + +OAM=CCM( + MI_CC_MEG, + MI_CC_MEP, + MI_CC_Period, + RI_CC_RDI, + 0, + 0, + 0 +) +``` + +The value of the ETH\_CI\_P signal associated with the generated CCM traffic unit is defined by the MI\_CC\_Pri input parameter; valid values are in the range 0-7. + +The value of the ETH\_CI\_DE signal associated with the generated CCM traffic units is always set to drop ineligible (0). + +![](7f5df81190b8dc50dad2604562ae0715_img.jpg) + +| 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +|---------------------------------------------------------------------------------------|---|---|---|---|---|---|---|---|---|---|---|------------------|---|-----------------|---|-------------|---|---------------------|---|-------------------|---|---|---|---|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| DA = 01-80-C2-00-00-3x, where x is changed to MI_MEL by the OAM MEP insertion process | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ----- | | | | | | | | | | | | SA = Undefined | | | | | | | | | | | | | | | | | | | | +| EtherType = 89-02 | | | | | | | | | | | | MEL = UnDef | | | | Version = 0 | | | | OpCode = 01 (CCM) | | | | | | | | | | | | +| R
D
I | | | | | | 0 | | 0 | | 0 | | MI_CC
_Period | | TLV Offset = 70 | | | | Sequence Number = 0 | | | | | | | | | | | | | | +| Sequence Number continued | | | | | | | | | | | | 0 | | 0 | | 0 | | MEP ID = MI_MEP_ID | | | | | | | | | | | | | | +| MEG ID = MI_MEG_ID | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TxFcf=TxFCl, if MI_LMC_Enable else 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RxFcb=RI_CC_RxFCl, if MI_LMC_Enable else 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TxFcb=RI_CC_TxFcf, if MI_LMC_Enable else 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Reserved (0) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| End TLV (0) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +G.8021-Y.1341(16)\_F8-18 + +Figure 8-18 – CCM traffic unit + +#### 8.1.7.3 CCM reception process + +The CCM reception process processes CCM OAM frames. It checks the various fields of the frames and generates the corresponding events (as defined in clause 6). If the version, MEL, MEG, MEP and period are valid, the values of the frame counters are sent to the performance counter process. The CCM reception behaviour is outlined in Figure 8-19. + +Note that unexpPriority event does not prevent the CCM from being processed, since the MEL, MEG, MEP and period are as expected. + +![Flowchart of CCM reception behaviour. The process starts with 'CCM reception' leading to 'Waiting'. From 'Waiting', it branches into two paths: one for 'D(OAM), P(P), DE(DE)' and another for 'MI_Get_SvdCCm' leading to 'MI_SvdCCM(SvdCCM)'. Both paths lead to a decision 'Period(OAM)=000'. If 'Y' (Yes), it goes to 'SvdCCM:=(D,P,DE)'. If 'N' (No), it enters a series of decision diamonds: 'MEL(OAM)==MI_MEL', 'MEG(OAM)==MI_MEG_ID', 'MEP(OAM) in MI_PeerMEP_ID[]', 'Period(OAM)==MI_CC_Period', and 'P==MI_CC_Pri'. Each 'N' branch from these decisions leads to an 'unexp' function (unexpMEL, unexpMEG, unexpMEP, unexpPeriod) which then leads to 'SvdCCM:=(D,P,DE)'. The final 'Y' branch from 'P==MI_CC_Pri' leads to a series of processing blocks: 'expCCM[Index(OAM.MEP)]', 'TxFCf(TxFCf(OAM)) RxFCb(RxFCb(OAM)) TxFCb(TxFCb(OAM)) RxFCf(RxFCf)', 'RI_CC_RxFCf(RxFCf) RI_CC_TxFCf(TxFCf(OAM))', and 'RDI[Index(MEP(OAM))]=RDI(OAM)'. All these blocks lead to 'SvdCCM:=(D,P,DE)'.](77959075c823bb5169480d7b8ff82a63_img.jpg) + +``` + +graph TD + Start([CCM reception]) --> Waiting([Waiting]) + Waiting --> D_OAM_P_DE[D(OAM), P(P), DE(DE)] + Waiting --> MI_Get_SvdCCm[MI_Get_SvdCCm] + MI_Get_SvdCCm --> MI_SvdCCM[MI_SvdCCM(SvdCCM)] + D_OAM_P_DE --> Period_000{Period(OAM)=000} + MI_SvdCCM --> Period_000 + Period_000 -- Y --> SvdCCM_1[SvdCCM:=(D,P,DE)] + Period_000 -- N --> MEL_OAM{MEL(OAM)==MI_MEL} + MEL_OAM -- N --> unexpMEL[unexpMEL(Period(OAM))] + MEL_OAM -- Y --> MEG_OAM{MEG(OAM)==MI_MEG_ID} + MEG_OAM -- N --> unexpMEG[unexpMEG(Period(OAM))] + MEG_OAM -- Y --> MEP_OAM{MEP(OAM) in MI_PeerMEP_ID[]} + MEP_OAM -- N --> unexpMEP[unexpMEP(Period(OAM))] + MEP_OAM -- Y --> Period_OAM{Period(OAM)==MI_CC_Period} + Period_OAM -- N --> unexpPeriod[unexpPeriod(Period(OAM))] + Period_OAM -- Y --> P_OAM{P==MI_CC_Pri} + P_OAM -- N --> unexpPriority[unexpPriority(Period(OAM))] + P_OAM -- Y --> expCCM[expCCM[Index(OAM.MEP)]] + unexpMEL --> SvdCCM_1 + unexpMEG --> SvdCCM_1 + unexpMEP --> SvdCCM_1 + unexpPeriod --> SvdCCM_1 + unexpPriority --> SvdCCM_1 + expCCM --> TxFCf_RxFCb[TxFCf(TxFCf(OAM)) +RxFCb(RxFCb(OAM)) +TxFCb(TxFCb(OAM)) +RxFCf(RxFCf)] + TxFCf_RxFCb --> RI_CC[RI_CC_RxFCf(RxFCf) +RI_CC_TxFCf(TxFCf(OAM))] + RI_CC --> RDI[RDI[Index(MEP(OAM))]=RDI(OAM)] + RDI --> SvdCCM_1 + +``` + +Flowchart of CCM reception behaviour. The process starts with 'CCM reception' leading to 'Waiting'. From 'Waiting', it branches into two paths: one for 'D(OAM), P(P), DE(DE)' and another for 'MI\_Get\_SvdCCm' leading to 'MI\_SvdCCM(SvdCCM)'. Both paths lead to a decision 'Period(OAM)=000'. If 'Y' (Yes), it goes to 'SvdCCM:=(D,P,DE)'. If 'N' (No), it enters a series of decision diamonds: 'MEL(OAM)==MI\_MEL', 'MEG(OAM)==MI\_MEG\_ID', 'MEP(OAM) in MI\_PeerMEP\_ID[]', 'Period(OAM)==MI\_CC\_Period', and 'P==MI\_CC\_Pri'. Each 'N' branch from these decisions leads to an 'unexp' function (unexpMEL, unexpMEG, unexpMEP, unexpPeriod) which then leads to 'SvdCCM:=(D,P,DE)'. The final 'Y' branch from 'P==MI\_CC\_Pri' leads to a series of processing blocks: 'expCCM[Index(OAM.MEP)]', 'TxFCf(TxFCf(OAM)) RxFCb(RxFCb(OAM)) TxFCb(TxFCb(OAM)) RxFCf(RxFCf)', 'RI\_CC\_RxFCf(RxFCf) RI\_CC\_TxFCf(TxFCf(OAM))', and 'RDI[Index(MEP(OAM))]=RDI(OAM)'. All these blocks lead to 'SvdCCM:=(D,P,DE)'. + +G.8021-Y.1341(16)\_F8-19 + +Figure 8-19 – CCM reception behaviour + +#### 8.1.7.4 Counter process + +This process counts the number of transmitted and received frames. + +The counter process for CCM generation forwards data frames and counts all transmitted ETH\_AI frames with priority (P) (i.e., ETH\_AI\_P) equal to MI\_CC\_Pri and Drop Eligibility (DE) (i.e., ETH\_AI\_DE) equal to . The D, P and DE signals are forwarded unchanged as indicated by the dotted lines in Figure 8-16. + +![Flowchart of Counter behaviour for CCM generation](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` +graph TD; Start([Counter for CCM generation]) --> Waiting([Waiting]); Waiting --> D1[/D(D),P(P),DE(DE)/]; D1 --> D2[/D(D),P(P),DE(DE)/]; D2 --> Decision{P==MI_CC_Pri & DE==}; Decision -- Y --> TxFCH[TxFCH++]; TxFCH --> Waiting; Decision -- N --> Waiting; +``` + +The flowchart illustrates the counter behaviour for CCM generation. It begins with a rounded rectangle labeled "Counter for CCM generation". An arrow points down to a rounded rectangle labeled "Waiting". From "Waiting", an arrow points down to a parallelogram labeled "D(D),P(P),DE(DE)". Another arrow points down to a second parallelogram labeled "D(D),P(P),DE(DE)". From the second parallelogram, an arrow points down to a decision diamond labeled "P==MI\_CC\_Pri & DE==". If the condition is true (Y), the flow goes down to a rectangle labeled "TxFCH++". If the condition is false (N), the flow goes to the right and then down to the "Waiting" rectangle. A dotted line on the left side of the "Waiting" rectangle indicates that the D, P, and DE signals are forwarded unchanged. + +G.8021-Y.1341(16)\_F8-20 + +Flowchart of Counter behaviour for CCM generation + +Figure 8-20 – Counter behaviour for CCM generation + +The counter process for CCM reception receives ETH\_CI and forwards them as ETH\_AI traffic units. It counts this number of received ETH\_AI traffic units that have priority (P) (i.e., ETH\_AI\_P) equal to MI\_CC\_Pri and drop eligibility (DE) (i.e., ETH\_AI\_DE) equal to . See Figure 8-20 for the counter behaviour for CCM generation, and Figure 8-21 for the counter behaviour for CCM reception. + +![Flowchart of Counter behaviour for CCM reception](107da2e3495b2f24352c9e3b26ec4841_img.jpg) + +``` +graph TD; Start([Counter for CCM reception]) --> Waiting([Waiting]); Waiting --> D1[/D(D),P(P),DE(DE)/]; D1 --> D2[/D(D),P(P),DE(DE)/]; D2 --> Decision{P==MI_CC_Pri & DE==}; Decision -- Y --> RxFCH[RxFCH++]; RxFCH --> Waiting; Decision -- N --> Waiting; +``` + +The flowchart illustrates the counter behaviour for CCM reception. It begins with a rounded rectangle labeled "Counter for CCM reception". An arrow points down to a rounded rectangle labeled "Waiting". From "Waiting", an arrow points down to a parallelogram labeled "D(D),P(P),DE(DE)". Another arrow points down to a second parallelogram labeled "D(D),P(P),DE(DE)". From the second parallelogram, an arrow points down to a decision diamond labeled "P==MI\_CC\_Pri & DE==". If the condition is true (Y), the flow goes down to a rectangle labeled "RxFCH++". If the condition is false (N), the flow goes to the right and then down to the "Waiting" rectangle. A dotted line on the left side of the "Waiting" rectangle indicates that the D, P, and DE signals are forwarded unchanged. + +G.8021-Y.1341(16)\_F8-21 + +Flowchart of Counter behaviour for CCM reception + +Figure 8-21 – Counter behaviour for CCM reception + +#### 8.1.7.5 Proactive loss measurement (LMp) process + +This process calculates the number of transmitted and lost frames per second. Figure 8-22 shows the LM process behaviour. + +![Flowchart of the LM process behaviour. The process starts with 'LM', goes to 'Disabled', then 'MI_LMC_Enabled'. It initializes variables: N_TF=N_LF=0, F_TF=F_LF=0, TxFCf_svd=TxFCb_svd=0, RxFCb_svd=RxRCI_svd=0, saved=false. It sets a 1s timer and enters 'Enabled' state. In 'Enabled', it receives frame counts (TxFCf, RxFCb, TxFCb, RxFCI), checks 'saved'. If 'saved' is false (N), it calculates transmitted and lost frames (N_TF+=|TxFCf-TxFCf_svd|, N_LF+=|TxFCf-TxFCf_svd| - |RxFCI-RxFCI_svd|, F_TF+=|TxFCb-TxFCb_svd|, F_LF+=|TxFCb-TxFCb_svd| - |RxFCb-RxFCb_svd|), updates saved values, sets saved=true, and restarts the timer. If 'saved' is true (Y), it updates saved values and restarts the timer. A 'Timer' block outputs nN_TF, nN_LF, nF_TF, nF_LF and restarts the timer. A '!MI_LMC_Enable' condition loops back to 'Disabled'.](95e259e8cb3519025066052af263f8c0_img.jpg) + +``` + +graph TD + LM([LM]) --> Disabled([Disabled]) + Disabled --> MI_LMC_Enabled[/MI_LMC_Enabled/] + MI_LMC_Enabled --> Init["N_TF=N_LF=0 +F_TF=F_LF=0 +TxFCf_svd=TxFCb_svd=0 +RxFCb_svd=RxRCI_svd=0 +saved=false"] + Init --> SetTimer1[Set(1s, Timer)] + SetTimer1 --> Enabled([Enabled]) + Enabled --> Input[/TxFCf(TxFCf) +RxFCb(RxFCb) +TxFCb(TxFCb) +RxFCI(RxFCI)/] + Input --> saved{saved} + saved -- N --> Calc["N_TF+=|TxFCf-TxFCf_svd| +N_LF+=|TxFCf-TxFCf_svd| - |RxFCI-RxFCI_svd| +F_TF+=|TxFCb-TxFCb_svd| +F_LF+=|TxFCb-TxFCb_svd| - |RxFCb-RxFCb_svd|"] + saved -- Y --> Calc + Calc --> Update["TxFCf_svd=TxFCf +RxFCb_svd=RxFCb +TxFCb_svd=TxFCb +RxFCI_svd=RxFCI +saved=true"] + Update --> SetTimer2[Set(1s, Timer)] + SetTimer2 --> Enabled + Enabled --> Timer[/Timer/] + Timer --> Output[/nN_TF(N_TF) +nN_LF(N_LF) +nF_TF(F_TF) +nF_LF(F_LF)/] + Output --> Reset["N_TF=0 +N_LF=0 +F_TF=0 +F_LF=0"] + Reset --> SetTimer3[Set(1s, Timer)] + SetTimer3 --> Enabled + Enabled --> NotEnabled[/!MI_LMC_Enable/] + NotEnabled --> Disabled + +``` + +Flowchart of the LM process behaviour. The process starts with 'LM', goes to 'Disabled', then 'MI\_LMC\_Enabled'. It initializes variables: N\_TF=N\_LF=0, F\_TF=F\_LF=0, TxFCf\_svd=TxFCb\_svd=0, RxFCb\_svd=RxRCI\_svd=0, saved=false. It sets a 1s timer and enters 'Enabled' state. In 'Enabled', it receives frame counts (TxFCf, RxFCb, TxFCb, RxFCI), checks 'saved'. If 'saved' is false (N), it calculates transmitted and lost frames (N\_TF+=|TxFCf-TxFCf\_svd|, N\_LF+=|TxFCf-TxFCf\_svd| - |RxFCI-RxFCI\_svd|, F\_TF+=|TxFCb-TxFCb\_svd|, F\_LF+=|TxFCb-TxFCb\_svd| - |RxFCb-RxFCb\_svd|), updates saved values, sets saved=true, and restarts the timer. If 'saved' is true (Y), it updates saved values and restarts the timer. A 'Timer' block outputs nN\_TF, nN\_LF, nF\_TF, nF\_LF and restarts the timer. A '!MI\_LMC\_Enable' condition loops back to 'Disabled'. + +G.8021-Y.1341(16)\_F8-22 + +Figure 8-22 – LM process behaviour + +It processes the TxFCf, RxFCb, TxFCb, RxFCI values and determines the number of transmitted frames and the number of lost frames. Every second, the number of transmitted and lost frames in that second are sent to the performance monitoring and defect generation processes. + +### 8.1.8 Loopback (LB) processes + +#### 8.1.8.1 Overview + +Figure 8-23 shows the different processes inside MEPs and MIPs that are involved in the loopback 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 sink extraction process in clause 9.4.2.2, and the MIP on-demand OAM source insertion process in clause 9.4.2.1. In summary, they insert and extract ETH\_CI OAM signals into and from the stream of ETH\_CI\_D traffic units and the complementing P and D signals going through an MEP and MIP; the extraction is based on MEL and OpCode. Furthermore, the insertion process inserts the correct MEL and SA values in the OAM traffic units. The other processes are defined in this clause. + +![Figure 8-23 – Overview of processes involved with loopback](8d5d12ba8fe7313bc891241275c64d20_img.jpg) + +The diagram shows three main vertical blocks: a MEP (left), a MIP (middle), and another MEP (right). + - The left MEP contains 'On-demand OAM Insertion', 'LBM Generation', 'LB Control', 'LBR Reception', and 'On-demand OAM Extraction'. It receives MI\_LB signals and outputs ETH\_CI. + - The middle MIP contains 'On-demand OAM Extraction', 'LBM MIP Reception', 'LBR Generation', and 'On-demand OAM Insertion'. It acts as a pass-through or a loopback point. + - The right MEP contains 'On-demand OAM Extraction', 'LBM MEP Reception', 'LBR Generation', and 'On-demand OAM Insertion'. + Signals like LBM(DA, P, DE, TLV, TID) and RI\_LBM(D, P, DE) flow between these blocks. Management interfaces (MI\_MIP\_MAC, MI\_MEP\_MAC) are also shown. + +Figure 8-23 – Overview of processes involved with loopback + +**Figure 8-23 – Overview of processes involved with loopback** + +The LBM protocol is controlled by the LB control process. There are three possible MI signals that can trigger the LB protocol: + +- **MI\_LB\_Discover( P)**: To discover the MAC addresses of the other MEPs in the same MEG. +- **MI\_LB\_Series(DA, DE, P, N, Length, Period)**: to send a series of N LB messages to a particular MEP/MIP; these LB messages are generated every "Period". +- **MI\_LB\_Test(DA, DE, P, Pattern, Length, Period)**: to send a series of LB messages carrying a test pattern to a particular MEP; these LB messages are generated every "Period" until the MI\_LB\_Test\_Terminate signal is received. + +The details are described later in this clause. + +The LBM control protocol triggers the LBM generation process to generate an LBM traffic unit that is received and forwarded by MIPs and received by MEPs in the same MEG. The LBM control process controls the number of LBM generated and the period between consecutive LBM traffic units. + +The LBM MIP/MEP reception processes process the received LBM traffic units and as a result the LBR generation process may generate an LBR traffic unit in response. The LBR reception process receives and processes the LBR traffic units. The source address (SA), transaction ID (TID) and type, length, value (TLV) values are given to the LBM control process. + +34 Rec. ITU-T G.8021/Y.1341 (04/2022) + +The LBM control process processes these received values to determine the result of the requested LB operation. The result is communicated back using the following MI signals: + +- MI\_LB\_Discover\_Result(MACs): reports back the MACs that have responded with a valid LBR. +- MI\_LB\_Series\_Result(REC,OO): reports back the total number of received LBR frames (REC), as well as counts of specific errors: + - OO: number of LBR traffic units that were received out of order (OO). +- MI\_LB\_Test\_Result(Sent, REC, CRC, BER, OO): reports back the total number of LBM frames sent (Sent) as well as the total number of LBR frames received (REC); for the latter counts of specific errors are reported: + - CRC: number of LBR frames where the cyclic redundancy check (CRC) in the pattern failed. + - BER: number of LBR frames where there was a bit error in the pattern. + - OO: number of LBR frames that were received out of order. + +The detailed functionality of the various processes is defined below. + +#### 8.1.8.2 LB control process + +The LB control process can receive several MI signals to trigger the LB protocol; this is shown in Figure 8-24. + +![Flowchart of LB control process behavior](9a14684f8ae1345c6efea6f5994c730c_img.jpg) + +``` +graph TD; A([LB control]) --> B([Init]); B --> C1{{MI_LB_Discover(P)}}; B --> C2{{MI_LB_Series(DA,DE,P,N,Length,Period)}}; B --> C3{{MI_LB_Test(DA,DE,P,Pattern,Length,Period)}}; C1 --> D1((Discover)); C2 --> D2((Series)); C3 --> D3((Test)); +``` + +The diagram illustrates the flow of the LB control process. It begins with a rounded rectangle labeled 'LB control', which points down to another rounded rectangle labeled 'Init'. From 'Init', three arrows branch out to three separate chevron-shaped boxes representing different MI signals: 'MI\_LB\_Discover(P)', 'MI\_LB\_Series(DA,DE,P,N,Length,Period)', and 'MI\_LB\_Test(DA,DE,P,Pattern,Length,Period)'. Each chevron box points down to a circle representing an action: 'Discover', 'Series', and 'Test' respectively. A small text label 'G.8021-Y.1341(16)\_F8-24' is located at the bottom right of the diagram. + +Flowchart of LB control process behavior + +**Figure 8-24 –LB control behaviour** + +Figure 8-25 shows the behaviour if the MI\_LB\_Discover signal is received. + +Figure 8-26 shows the behaviour if the MI\_LB\_Series signal is received. + +Figure 8-27 shows the behaviour if the MI\_LB\_Test signal is received. + +NOTE – The state machine (Figure 8-24 combined with Figures 8-25, 8-26 and 8-27) shows that the LB\_Discover, LB\_Series and LB\_Test actions are mutually exclusive. Furthermore, a new instantiation of any of these actions cannot be initiated until the current action is finished. + +##### MI\_LB\_Discover behaviour + +![Flowchart of LB control discover behaviour](b05bae46f7079e5c9b1da38adb2319e8_img.jpg) + +``` +graph TD; Discover((Discover)) --> LBM["LBM(01-80-C2-00-00-3x, P, 0, Null, TID)"]; LBM --> SetTimer["set Timer 5
TID++
MACs={}"]; SetTimer --> WaitingDiscover([Waiting Discover]); WaitingDiscover --> RI_LBR["RI_LBR(SA,rTLV,TID)"]; WaitingDiscover --> Timer[Timer]; RI_LBR --> MACsUpdate["MACs=MACs+SA"]; MACsUpdate --> WaitingDiscover; Timer --> MI_LB_Discover_Result["MI_LB_Discover_Result
(MACs)"]; MI_LB_Discover_Result --> Init((Init)); +``` + +The flowchart illustrates the LB control discover behaviour. It begins with a 'Discover' state, leading to the generation of an LBM frame with parameters (01-80-C2-00-00-3x, P, 0, Null, TID). This is followed by setting Timer 5, incrementing TID, and initializing the MACs set. The process then enters a 'Waiting Discover' state. During this time, it processes received RI\_LBR(SA,rTLV,TID) signals by adding the SA to the MACs set and continues to wait. After the timer expires, it sends the MI\_LB\_Discover\_Result(MACs) signal and returns to the 'Init' state. + +G.8021-Y.1341(16)\_F8-25 + +Flowchart of LB control discover behaviour + +**Figure 8-25 – LB control discover behaviour** + +Figure 8-25 shows the behaviour when an MI\_LB\_Discover(DE,P) signal is received. + +First the LBM generation process is requested to generate an LBM frame by sending the LBM(01-80-c2-00-00-3x, P, 0, Null, TID) signal to the LBM generation process. The DA is set to the class 1 multicast address as defined in [ITU-T G.8013], where the last part (x) will be overwritten with MEL by the OAM MEP insertion process. There are no TLVs included, hence the TLV parameter is set to Null. + +After triggering the transmission of the LBM frame, received RI\_LBR is processed for 5 seconds (as governed by the timer). Every time the RI\_LBR(SA,rTLV,TID) is received the SA is stored in the set of received MACs. + +After 5 seconds all the received SAs are reported back using the MI\_LB\_Discover\_Result(MACs) signal and the LBM control process returns to the Init state. + +##### MI\_LB\_Series behaviour + +![Flowchart of LB control series behaviour. The process starts with 'Series' (circle), followed by initialization: set(0, TxTimer), OLD_TID=Undef, REC=0, OO=0. It then enters 'Waiting Series' (oval). Three parallel paths emerge: 1) TxTimer (parallelogram) leads to TLV=Generate(Length), LBM(DA,P,DE,TLV,TID), TID++, then a decision N>1. If N>1 (Y), it sets Period and decrements N, then loops back to Waiting Series. If N>1 (N), it sets 5s for TxTimer and loops back. 2) RI_LBR(SA,rTLV,TID) (parallelogram) leads to REC++, then a decision OLD_TID!=Undef. If Y, it checks TID!=OLD_TID+1. If Y, it increments OO. Both paths lead to OLD_TID=TID. 3) Timer (parallelogram) leads to MI_LB_Series_Result(REC,OO) (parallelogram), which ends at Init (circle).](878d9539700bd792e7d12ad6f1203c5d_img.jpg) + +``` + +graph TD + Series((Series)) --> Init1["set(0, TxTimer) +OLD_TID=Undef +REC=0 +OO=0"] + Init1 --> WaitingSeries([Waiting Series]) + WaitingSeries --> TxTimer[/TxTimer/] + WaitingSeries --> RI_LBR[/RI_LBR(SA,rTLV,TID)/] + WaitingSeries --> Timer[/Timer/] + TxTimer --> TLV["TLV=Generate(Length)"] + TLV --> LBM[/LBM(DA,P,DE,TLV,TID)/] + LBM --> TID["TID++"] + TID --> Ngt1{"N>1"} + Ngt1 -- Y --> setPeriod["set(Period, TxTimer) +N--"] + Ngt1 -- N --> set5s["set(5s, TxTimer)"] + setPeriod --> WaitingSeries + set5s --> WaitingSeries + RI_LBR --> REC["REC++"] + REC --> OLD_TID_Undef{"OLD_TID!=Undef"} + OLD_TID_Undef -- Y --> TID_diff{"TID!=OLD_TID+1"} + OLD_TID_Undef -- N --> OLD_TID_TID["OLD_TID=TID"] + TID_diff -- Y --> OO["OO++"] + TID_diff -- N --> OLD_TID_TID + OO --> OLD_TID_TID + OLD_TID_TID --> WaitingSeries + Timer --> MI_LB_Series_Result[/MI_LB_Series_Result(REC,OO)/] + MI_LB_Series_Result --> Init((Init)) + +``` + +Flowchart of LB control series behaviour. The process starts with 'Series' (circle), followed by initialization: set(0, TxTimer), OLD\_TID=Undef, REC=0, OO=0. It then enters 'Waiting Series' (oval). Three parallel paths emerge: 1) TxTimer (parallelogram) leads to TLV=Generate(Length), LBM(DA,P,DE,TLV,TID), TID++, then a decision N>1. If N>1 (Y), it sets Period and decrements N, then loops back to Waiting Series. If N>1 (N), it sets 5s for TxTimer and loops back. 2) RI\_LBR(SA,rTLV,TID) (parallelogram) leads to REC++, then a decision OLD\_TID!=Undef. If Y, it checks TID!=OLD\_TID+1. If Y, it increments OO. Both paths lead to OLD\_TID=TID. 3) Timer (parallelogram) leads to MI\_LB\_Series\_Result(REC,OO) (parallelogram), which ends at Init (circle). + +G.8021-Y.1341(16)\_F8-26 + +**Figure 8-26 – LB control series behaviour** + +Figure 8-26 defines the behaviour of the LB control process after the reception of the $MI\_LB\_Series(DA,DE,P,N,Length,Period)$ signal. + +The TLV field of the LBM frames is determined by the $Generate(Length)$ function. $Generate(Length)$ generates a Data TLV with length "Length" of an arbitrary bit pattern to be included in the LBM frame. + +After the receipt of the $MI\_LB\_Series$ signal, the LBM generation process is requested N times to generate an LBM frame (where "Period" determines the interval between two LBM frames); this is done by issuing the $LBM(DA,P,DE,TLV,TID)$ signal. + +Whenever an $RI\_LBR(SA, rTLV, TID)$ signal is received, the number of received LBR frames is increased ( $REC++$ ). If the TID value from the $RI\_LBR$ signal does not consecutively follow the last received TID value, the counter for out of order frames is incremented by one ( $OO++$ ). + +Five seconds after sending the last LBM frame (i.e., after sending the Nth LBM frame) the received (REC) and OO counters are reported back in the $MI\_LB\_Series\_Result$ signal. + +##### MI\_LB\_Test Behaviour + +![Flowchart of MI_LB_Test Behaviour. It starts with 'Test', followed by initialization of variables (set(0, TxTimer), OLD_TID=Undef, Sent=0, REC=0, CRC=0, BER=0, OO=0). It then enters a 'Waiting Test' state. From there, it branches into four paths: 1) TxTimer path: TLV=Generate(Pattern,Length) -> LBM(DA,P,DE,TLV,TID) -> Sent++, TID++, Set(Period,TxTimer). 2) RI_LBR(SA,r,TLV,TID) path: REC++ -> Decision: (Pattern==1 or Pattern==3)&&(CheckCRC(TLV)==Fail). If Y: CRC++ -> Decision: Check(Pattern, TLV)==Fail. If Y: BER++ -> Decision: OLD_TID!=Undef. If Y: Decision: TID!=OLD_TID+1. If Y: OO++ -> OLD_TID=TID. 3) MI_LB_TEST_Terminate path: set(5s, Timer). 4) Timer path: MI_LB_Test_Result(Sent,REC,CRC,BER,OO) -> Init. All paths eventually lead back to the 'Waiting Test' state.](6cc85a2b62fd8a2a3faab29730f20e81_img.jpg) + +``` + +graph TD + Test((Test)) --> InitVars["set(0, TxTimer) +OLD_TID=Undef +Sent=0 +REC=0 +CRC=0 +BER=0 +OO=0"] + InitVars --> WaitingTest([Waiting Test]) + WaitingTest --> TxTimer[/TxTimer/] + WaitingTest --> RI_LBR[/RI_LBR(SA,r,TLV,TID)/] + WaitingTest --> MI_LB_TEST_Terminate[/MI_LB_TEST_Terminate/] + WaitingTest --> Timer[/Timer/] + + TxTimer --> TLV_Gen["TLV=Generate(Pattern,Length)"] + TLV_Gen --> LBM["LBM(DA,P,DE,TLV,TID)"] + LBM --> SentInc["Sent++ +TID++ +Set(Period,TxTimer)"] + + RI_LBR --> RECInc["REC++"] + RECInc --> Dec1{"(Pattern==1 or Pattern==3)&&(CheckCRC(TLV)==Fail)"} + Dec1 -- Y --> CRCInc["CRC++"] + Dec1 -- N --> Dec2{"Check(Pattern, TLV)==Fail"} + CRCInc --> Dec2 + Dec2 -- Y --> BERInc["BER++"] + Dec2 -- N --> Dec3{"OLD_TID!=Undef"} + BERInc --> Dec3 + Dec3 -- Y --> Dec4{"TID!=OLD_TID+1"} + Dec3 -- N --> OLD_TID_TID["OLD_TID=TID"] + Dec4 -- Y --> OOInc["OO++"] + Dec4 -- N --> OLD_TID_TID + OOInc --> OLD_TID_TID + OLD_TID_TID --> WaitingTest + + MI_LB_TEST_Terminate --> SetTimer["set(5s, Timer)"] + SetTimer --> WaitingTest + + Timer --> MI_LB_Test_Result["MI_LB_Test_Result(Sent,REC,CRC,BER,OO)"] + MI_LB_Test_Result --> Init((Init)) + Init --> WaitingTest + +``` + +Flowchart of MI\_LB\_Test Behaviour. It starts with 'Test', followed by initialization of variables (set(0, TxTimer), OLD\_TID=Undef, Sent=0, REC=0, CRC=0, BER=0, OO=0). It then enters a 'Waiting Test' state. From there, it branches into four paths: 1) TxTimer path: TLV=Generate(Pattern,Length) -> LBM(DA,P,DE,TLV,TID) -> Sent++, TID++, Set(Period,TxTimer). 2) RI\_LBR(SA,r,TLV,TID) path: REC++ -> Decision: (Pattern==1 or Pattern==3)&&(CheckCRC(TLV)==Fail). If Y: CRC++ -> Decision: Check(Pattern, TLV)==Fail. If Y: BER++ -> Decision: OLD\_TID!=Undef. If Y: Decision: TID!=OLD\_TID+1. If Y: OO++ -> OLD\_TID=TID. 3) MI\_LB\_TEST\_Terminate path: set(5s, Timer). 4) Timer path: MI\_LB\_Test\_Result(Sent,REC,CRC,BER,OO) -> Init. All paths eventually lead back to the 'Waiting Test' state. + +G.8021-Y.1341(16)\_F8-27 + +Figure 8-27 – LB control test behaviour + +Figure 8-27 defines the behaviour of the LB control process after the reception of the MI\_LB\_Test(DA,DE,P,Pattern,Length,Period) signal. + +Every period an LBM frame is generated until the MI\_LB\_Test\_Terminate signal is received. Five seconds after receiving this MI\_LB\_Test\_Terminate signal the "Sent", REC, CRC, BER and OO counters are reported back using the MI\_LB\_Test\_Result signal. + +The TLV field of the LBM frames 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 2^31-1 without CRC-32" +- 3: "PRBS 2^31-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 LBM frame. Therefore, this TLV is passed using the LBM(DA,P,DE,TLV,TID) signal to the LBM generation process. + +Upon receipt of the RI\_LBR(SA,rTLV,TID) remote information, the received LBR counter is incremented by one (REC++). If the TLV contains a CRC (Pattern 1 or 3) the CRC counter is incremented by one 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 BER counter is increased. If the TID value from the RI\_LBR signal does not follow the last received TID value, the counter for out of order frames is incremented by one (OO++). + +#### 8.1.8.3 LBM generation process + +The LBM generation process generates a single LBM OAM traffic unit (ETH\_CI\_D) complemented with ETH\_CI\_P and ETH\_CI\_DE signals on receipt of the LBM(DA,P,DE,TLV,TID) signal. The process is defined in Figure 8-28. + +![Flowchart of the LBM generation process. The steps are: LBM generation (oval), Waiting (oval), LBM(DA,P,DE,TLV,TID) (parallelogram), OAM=LBM(DA,TLV,TID) (rectangle), and D(OAM, P(P), DE(DE)) (parallelogram). A feedback loop connects the final step back to the Waiting step.](18291be12b470a557e8c9f3a74e021be_img.jpg) + +``` +graph TD; A([LBM generation]) --> B([Waiting]); B --> C[/LBM(DA,P,DE,TLV,TID)/]; C --> D[OAM=LBM(DA,TLV,TID)]; D --> E[/D(OAM, P(P), DE(DE))/]; E --> B; +``` + +G.8021-Y.1341(16)\_F8-28 + +Flowchart of the LBM generation process. The steps are: LBM generation (oval), Waiting (oval), LBM(DA,P,DE,TLV,TID) (parallelogram), OAM=LBM(DA,TLV,TID) (rectangle), and D(OAM, P(P), DE(DE)) (parallelogram). A feedback loop connects the final step back to the Waiting step. + +Figure 8-28 – LBM generation behaviour + +From the LBM(DA,P,DE,TLV,TID) signal the P field determines the value of the ETH\_CI\_P signal, the DE field determines the value of the ETH\_CI\_DE signal. The DA, TLV and TID fields are used in the construction of the ETH\_CI\_D signal that carries the LBM traffic unit. + +The format of the LBM traffic unit and the values are shown in Figure 8-29. + +The values of the SA and MEL fields will be determined by the OAM MEP insertion process, as well as the last part (x) of the DA if the DA is set to 01-80-c2-00-00-3x. + +![](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +| 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +|-----------------------------|---|---|---|---|---|---|---|----------------|---|---|---|---------------------------|---|---|---|-------------|---|---|---|-------------------|---|---|---|---|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| DA = LBM(DA) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SA = Undefined | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EtherType = 89-02 | | | | | | | | | | | | MEL = Unedef | | | | Version = 0 | | | | OpCode = 03 (LBM) | | | | | | | | | | | | +| Flags = 0 | | | | | | | | TLV Offset = 4 | | | | Transaction ID = LBM(TID) | | | | | | | | | | | | | | | | | | | | +| Transaction ID continued | | | | | | | | | | | | TLV = LBM(TLV) | | | | | | | | | | | | | | | | | | | | +| 25
29
33
:
last | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | End TLV (0) | | | | | | | | | | | | | | | | + +G.8021-Y.1341(16)\_F8-29 + +Figure 8-29 – LBM traffic unit + +#### 8.1.8.4 MIP LBM reception process + +The MIP LBM reception process receives ETH\_CI traffic units containing LBM PDUs complemented by the P and D signals. + +The behaviour is defined in Figure 8-30. If the DA field in the traffic unit (D signal) equals the local MAC address (MI\_MIP\_MAC), the loopback is intended for this MIP and the information is forwarded to the loopback reply generation process using the RI\_LBM(D,P,DE) signal; otherwise the information is ignored and no action is taken. + +Note that an MIP therefore does not reply to LBM traffic units that have a class 1 multicast address. + +![Flowchart of MIP LBM reception behaviour. The process starts with 'MIP LBM reception', followed by 'Waiting', then 'D(D),P(P),DE(DE)'. A decision diamond asks 'DA(D)=MI_MIP_MAC'. If 'Y' (Yes), it proceeds to 'RI_LBM(D,P,DE)'. If 'N' (No), it loops back to the entry point. A small text 'G.8021-Y.1341(16)_F8-30' is at the bottom right.](12c19090355e19922e23044633b9d1ea_img.jpg) + +``` + +graph TD + Start([MIP LBM reception]) --> Waiting([Waiting]) + Waiting --> DDPDE[D(D),P(P),DE(DE)] + DDPDE --> DA{DA(D)=MI_MIP_MAC} + DA -- Y --> RILBM[RI_LBM(D,P,DE)] + DA -- N --> Start + RILBM --> Start + +``` + +G.8021-Y.1341(16)\_F8-30 + +Flowchart of MIP LBM reception behaviour. The process starts with 'MIP LBM reception', followed by 'Waiting', then 'D(D),P(P),DE(DE)'. A decision diamond asks 'DA(D)=MI\_MIP\_MAC'. If 'Y' (Yes), it proceeds to 'RI\_LBM(D,P,DE)'. If 'N' (No), it loops back to the entry point. A small text 'G.8021-Y.1341(16)\_F8-30' is at the bottom right. + +**Figure 8-30 – MIP LBM reception behaviour** + +#### **8.1.8.5 MEP LBM reception process** + +The MEP LBM reception process receives ETH\_CI traffic units containing LBM PDUs complemented by the P and D signals. + +The behaviour is defined in Figure 8-31. + +![Flowchart of MEP LBM reception behaviour. The process starts with 'MEP LBM reception', followed by 'Waiting', then 'D(D),P(P),DE(DE)'. A decision diamond asks 'DA(D)=MI_MEP_MAC'. If 'Yes', it proceeds to 'RI_LBM(D,P,DE)'. If 'No', it goes to another decision 'DA(D)=Multicast Address?'. If 'Yes' to the second decision, it proceeds to 'Wait_Time=Random(0..1s) Set(Wait_Time,Timer)', then 'Waiting Timer', then 'Timer', then 'RI_LBM(D,P,DE)'. If 'No' to the second decision, it loops back to the entry point. A small text 'G.8021-Y.1341(16)_F8-31' is at the bottom right.](1ce027dfd26183da52137cf990213724_img.jpg) + +``` + +graph TD + Start([MEP LBM reception]) --> Waiting([Waiting]) + Waiting --> DDPDE[D(D),P(P),DE(DE)] + DDPDE --> DA1{DA(D)=MI_MEP_MAC} + DA1 -- Yes --> RILBM1[RI_LBM(D,P,DE)] + DA1 -- No --> DA2{DA(D)=Multicast Address?} + DA2 -- Yes --> WaitTime[Wait_Time=Random(0..1s) +Set(Wait_Time,Timer)] + WaitTime --> WaitingTimer([Waiting Timer]) + WaitingTimer --> Timer[Timer] + Timer --> RILBM2[RI_LBM(D,P,DE)] + DA2 -- No --> Start + RILBM1 --> Start + RILBM2 --> Start + +``` + +G.8021-Y.1341(16)\_F8-31 + +Flowchart of MEP LBM reception behaviour. The process starts with 'MEP LBM reception', followed by 'Waiting', then 'D(D),P(P),DE(DE)'. A decision diamond asks 'DA(D)=MI\_MEP\_MAC'. If 'Yes', it proceeds to 'RI\_LBM(D,P,DE)'. If 'No', it goes to another decision 'DA(D)=Multicast Address?'. If 'Yes' to the second decision, it proceeds to 'Wait\_Time=Random(0..1s) Set(Wait\_Time,Timer)', then 'Waiting Timer', then 'Timer', then 'RI\_LBM(D,P,DE)'. If 'No' to the second decision, it loops back to the entry point. A small text 'G.8021-Y.1341(16)\_F8-31' is at the bottom right. + +**Figure 8-31 – MEP LBM reception behaviour** + +If the DA field in the LBM traffic unit (D signal) equals the local MAC address (MI\_MEP\_MAC), the loopback is intended for this MEP, and the information is forwarded to the loopback reply generation process (RI\_LBM(D,P,DE)). + +If the DA field in the LBM traffic unit (D signal) is a multicast address, an LBR traffic unit must be generated after a random delay between 0 and 1 second. This is specified by instantiating a separate process, the Send\_MC\_LBR process. This process chooses a random waiting time between 0 and 1 second and, after waiting for the chosen period of time, the D, P and DE information is forwarded to the loopback reply generation process (RI\_LBM(D,P,DE)). Finally, this process instance is terminated. + +Since the 0 to 1 second waiting time is performed in a separate process, it does not block the reception and processing of other LBM frames within that waiting period. + +#### 8.1.8.6 LBR generation process + +Note that the LBR generation process is the same for MEPs and MIPs. + +Upon receipt of the LBM traffic unit and accompanying signals (RI\_LBM(D,P,DE)) from the LBM reception process the LBR generation process generates an LBR traffic unit together with the complementing P and DE signals. + +The behaviour is specified in Figure 8-32. The generated traffic unit is the same as the received RI\_LBM(D) traffic unit except: + +- the DA of the generated LBR traffic unit is the SA of the received LBM traffic unit, and +- the OpCode is set to LBR OpCode. + +NOTE – In the generated LBR, in the OAM (MEP) insertion process, the SA will be overwritten with the local MAC address, and the MEL will be overwritten with MI\_MEL. + +![Flowchart of LBR generation behaviour](9ed248b025d766251d58be10b01a1cc0_img.jpg) + +``` +graph TD; A([LBR generation]) --> B([Waiting]); B --> C[/RI_LBM(D,P,DE)/]; C --> D["DA(D)=SA(D) +OPC(D)=02"]; D --> E[/RI_LBM(D,P,DE)/]; E --> A; +``` + +The flowchart illustrates the LBR generation process. It begins with a rounded rectangle labeled 'LBR generation', which points down to another rounded rectangle labeled 'Waiting'. From 'Waiting', the flow proceeds down to a parallelogram labeled 'RI\_LBM(D,P,DE)'. This is followed by a rectangular process block containing 'DA(D)=SA(D)' and 'OPC(D)=02'. Below this block is another parallelogram labeled 'RI\_LBM(D,P,DE)'. A feedback line originates from the bottom of the final parallelogram, loops back up to the left side of the 'Waiting' block. At the bottom of the diagram, the text 'G.8021-Y.1341(16)\_F8-32' is present. + +Flowchart of LBR generation behaviour + +**Figure 8-32 – LBR generation behaviour** + +The resulting LBR traffic unit format is shown in Figure 8-33. + +![](dbd074feb5cce1300f42f91da8f673d1_img.jpg) + +| 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +|------|-----------------------------|---|---|---|---|---|---------------------------------------|---|---|---|---|-----------------------------------------------|---|---|----------------------------------|---|---|---|-------------------|---------------------------------|---|---|---|---|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | DA = SA(RI_LBM(D)) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | SA = Undefined | | | | | | | | | | | | | | | | | | | | +| 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 13 | EtherType = 89-02 | | | | | | | | | | | MEL =
Undef | | | Version = Version
(RI_LBM(D)) | | | | OpCode = 02 (LBR) | | | | | | | | | | | | | +| 17 | Flags =
Flags(RI_LBM(D)) | | | | | | TLV Offset =
TLV Offset(RI_LBM(D)) | | | | | Transaction ID =
Transaction ID(RI_LBM(D)) | | | | | | | | | | | | | | | | | | | | +| 21 | Transaction ID continued | | | | | | | | | | | TLV = TLV(RI_LBM(D)) | | | | | | | | | | | | | | | | | | | | +| 25 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 29 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 33 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| : | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| last | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | End TLV = End
TLV(RI_LBM(D)) | | | | | | | | | | | | + +G.8021-Y.1341(16)\_F8-33 + +Figure 8-33 – LBR traffic unit + +#### 8.1.8.7 LBR reception process + +The LBR reception process receives LBR traffic units (D signal) together with the complementing P and DE signals. The LBR reception process will inspect the DA field in the received traffic unit; if the DA equals the local MAC address (MI\_MEP\_MAC) the SA, TID and TLV values will be extracted from the LBR PDU and signalled to the LB control process using the RI\_LBR(SA,TID,TLV) signal. The behaviour is defined in Figure 8-34. + +![Flowchart of the LBR reception process. It starts with 'LBR reception', followed by 'Waiting', then 'D(D),P(P),DE(DE)'. A decision diamond asks 'DA(D)=MI_MEP_MAC'. If 'No', it loops back to 'Waiting'. If 'Yes', it proceeds to 'SA=SA(D), TID=TID(D), TLV=TLV(D)', then to 'RI_LBR(SA,TID,TLV)', and finally loops back to 'Waiting'.](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +``` + +graph TD + A([LBR reception]) --> B([Waiting]) + B --> C[/D(D),P(P),DE(DE)/] + C --> D{DA(D)=MI_MEP_MAC} + D -- No --> B + D -- Yes --> E[SA=SA(D) +TID=TID(D) +TLV=TLV(D)] + E --> F[/RI_LBR(SA,TID,TLV)/] + F --> B + +``` + +Flowchart of the LBR reception process. It starts with 'LBR reception', followed by 'Waiting', then 'D(D),P(P),DE(DE)'. A decision diamond asks 'DA(D)=MI\_MEP\_MAC'. If 'No', it loops back to 'Waiting'. If 'Yes', it proceeds to 'SA=SA(D), TID=TID(D), TLV=TLV(D)', then to 'RI\_LBR(SA,TID,TLV)', and finally loops back to 'Waiting'. + +G.8021-Y.1341(16)\_F8-34 + +Figure 8-34 – LBR reception behaviour + +### 8.1.9 Loss measurement (LM) processes + +#### 8.1.9.1 Overview + +Figure 8-35 shows the different processes inside MEPs and MIPs that are involved in the on-demand loss 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 sink extraction process in clause 9.4.2.2, and the MIP on-demand OAM source insertion process in clause 9.4.2.1. In summary, they insert and extract ETH\_CI OAM signals into and from the stream of ETH\_CI\_D traffic units together with the complementing P and D signals going through an MEP and MIP; the extraction is based on MEL and OpCode. Furthermore, the insertion process inserts the correct MEL and SA values into the OAM traffic units. + +![Figure 8-35: Overview of processes involved with on-demand loss measurement. The diagram shows three main components: a transmitting MEP, a middle MIP, and a receiving MEP. The transmitting MEP (left) includes a Counter, On-demand OAM Insertion, LMM Generation, On-demand LM Control, LMR Reception, and On-demand OAM Extraction. The MIP (middle) includes On-demand OAM Extraction and On-demand OAM Insertion. The receiving MEP (right) includes On-demand OAM Extraction, Counter, LMM Reception, LMR Generation, and On-demand OAM Insertion. Data flows are shown as ETH_CI, TxFCI[], RxFCI[], D,P,DE, and LMM/LMR signals. External signals include MI_LM_Start, MI_LM_Intermediate_Request, MI_LM_Terminate, MI_LM_Result, and MI_MEP_MAC.](fb4274c4b7882a4059103f1dbca9b111_img.jpg) + +The diagram illustrates the flow of data and control signals for on-demand loss measurement across three network elements: a transmitting MEP, a middle MIP, and a receiving MEP. + +- Transmitting MEP (Left):** + - ETH\_CI data enters a Counter. + - The Counter outputs Data and TxFCI[] signals. + - TxFCI[] is sent to the LMM Generation block. + - LMM Generation outputs LMM(D,A,P,0) to the On-demand LM Control block. + - On-demand LM Control receives MI\_LM\_Start(D,A,P,Period), MI\_LM\_Intermediate\_Request, MI\_LM\_Terminate, and MI\_LM\_Result(N\_TF, N\_LF, F\_TF, F\_LF) signals. + - On-demand LM Control outputs RI\_LMR(rSA,TxFcf,RxFcf, TxFcb,RxFcb) to the LMR Reception block. + - LMR Reception receives MI\_MEP\_MAC and D,P,DE signals. + - LMR Reception outputs RxFCI[] to the On-demand OAM Extraction block. + - On-demand OAM Extraction outputs ETH\_CI data. +- MIP (Middle):** + - ETH\_CI data from the transmitting MEP enters the On-demand OAM Extraction block. + - On-demand OAM Extraction outputs ETH\_CI data to the On-demand OAM Insertion block. + - On-demand OAM Insertion outputs ETH\_CI data to the receiving MEP. +- Receiving MEP (Right):** + - ETH\_CI data from the MIP enters the On-demand OAM Extraction block. + - On-demand OAM Extraction outputs Data and D,P,DE signals. + - Data enters a Counter. + - Counter outputs ETH\_CI data. + - D,P,DE is sent to the LMR Generation block. + - LMR Generation outputs TxFCI[] to the On-demand OAM Insertion block. + - On-demand OAM Insertion outputs ETH\_CI data. + - On-demand OAM Extraction also outputs RI\_LMM(D,P,DE) to the LMM Reception block. + - LMM Reception receives MI\_MEP\_MAC and RI\_LMM(D,P,DE) signals. + +Reference: G.8021-Y.1341(16)\_F8-35 + +Figure 8-35: Overview of processes involved with on-demand loss measurement. The diagram shows three main components: a transmitting MEP, a middle MIP, and a receiving MEP. The transmitting MEP (left) includes a Counter, On-demand OAM Insertion, LMM Generation, On-demand LM Control, LMR Reception, and On-demand OAM Extraction. The MIP (middle) includes On-demand OAM Extraction and On-demand OAM Insertion. The receiving MEP (right) includes On-demand OAM Extraction, Counter, LMM Reception, LMR Generation, and On-demand OAM Insertion. Data flows are shown as ETH\_CI, TxFCI[], RxFCI[], D,P,DE, and LMM/LMR signals. External signals include MI\_LM\_Start, MI\_LM\_Intermediate\_Request, MI\_LM\_Terminate, MI\_LM\_Result, and MI\_MEP\_MAC. + +Figure 8-35 – Overview of processes involved with on-demand loss measurement + +The on-demand LM control process controls the on-demand LM protocol. The protocol is activated upon receipt of the MI\_LM\_Start(D,A,P,Period) signal and remains activated until the MI\_LM\_Terminate signal is received. + +The result is communicated via the MI\_LM\_Result(N\_TF, N\_LF, F\_TF, F\_LF) signal when the process is terminated by the MI\_LM\_Terminate signal or when an intermediate result is requested via the MI\_LM\_Intermediate\_Request signal. If the on-demand LM control process activates the multiple monitoring on different class of service (CoS) levels simultaneously, each result is independently managed per CoS level. + +The LMM generation process generates an LMM traffic unit that passes transparently through MIPs, but that will be processed by the LMM reception process in MEPs. The LMR generation process generates an LMR traffic unit in response to the receipt of an LMM traffic unit. The LMR reception process receives and processes the LMR traffic units. + +Figure 8-36 shows the different processes inside MEPs and MIPs that are involved in the proactive loss 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, the MIP OAM extraction process in clause 9.4.2.1, and the MIP OAM insertion process in clause 9.4.2.2. In summary, they insert and extract ETH\_CI OAM signals into and from the stream of ETH\_CI\_D traffic units and the complementing P and D signals going through an MEP and MIP; the extraction is based on MEL and OpCode. Furthermore, the insertion process inserts the correct MEL and SA values into the OAM traffic units. + +![Figure 8-36: Overview of processes involved with proactive loss measurement. The diagram shows three main components: a transmitting MEP, a middle MIP, and a receiving MEP. The transmitting MEP contains a Proactive LM Control process that receives inputs (MI_LM_Enable, MI_LM_MAC_DA, MI_LM_Period, MI_LM_Pri) and generates LMM (DA, P, 1) frames. These frames are processed by an LMM Generation block, then a Counter, and finally a Proactive OAM Insertion block which adds them to the ETH_CI stream. The MIP contains an On-demand OAM Extraction block. The receiving MEP contains a Proactive OAM Extraction block that receives the stream, followed by a Counter, an LMM Reception block (which receives RI_LMM(D,P,DE) and MI_MEP_MAC), an LMR Generation block, another Counter, and a Proactive OAM Insertion block. The receiving MEP also includes an LMR Reception block that receives RI_LMR (rSA, TxFCf, RxFCf, TxFCb, RxFC) and generates an LM_Result. Various internal signals like D,P,DE, TxFCf, RxFCf, and ETH_CI are shown throughout the process flow.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +Figure 8-36: Overview of processes involved with proactive loss measurement. The diagram shows three main components: a transmitting MEP, a middle MIP, and a receiving MEP. The transmitting MEP contains a Proactive LM Control process that receives inputs (MI\_LM\_Enable, MI\_LM\_MAC\_DA, MI\_LM\_Period, MI\_LM\_Pri) and generates LMM (DA, P, 1) frames. These frames are processed by an LMM Generation block, then a Counter, and finally a Proactive OAM Insertion block which adds them to the ETH\_CI stream. The MIP contains an On-demand OAM Extraction block. The receiving MEP contains a Proactive OAM Extraction block that receives the stream, followed by a Counter, an LMM Reception block (which receives RI\_LMM(D,P,DE) and MI\_MEP\_MAC), an LMR Generation block, another Counter, and a Proactive OAM Insertion block. The receiving MEP also includes an LMR Reception block that receives RI\_LMR (rSA, TxFCf, RxFCf, TxFCb, RxFC) and generates an LM\_Result. Various internal signals like D,P,DE, TxFCf, RxFCf, and ETH\_CI are shown throughout the process flow. + +**Figure 8-36 – Overview of processes involved with proactive loss measurement** + +The proactive LM control process controls the proactive LM protocol. If MI\_LM\_Enable is set the LMM frames are sent periodically. The LMM frames are generated with a periodicity determined by MI\_LM\_Period and with a priority determined by MI\_LM\_Pri. The result (N\_TF, N\_LF, F\_TF, F\_LF) is reported via an LMR reception. If the proactive LM control process activates the multiple monitoring on different CoS levels simultaneously, each result is independently managed per CoS level. + +The behaviour of the processes is defined below. + +#### 8.1.9.2 LM control process + +The behaviour of the on-demand LM control process is defined in Figure 8-37. + +![Flowchart of the on-demand LM control process. The process starts with 'On-demand LM control' leading to 'Init', then 'MI_LM_Start(DA,P,Period)', 'Set(0,Timer)', and an initialization block for counters. It then enters a 'Running' state. From 'Running', it branches to 'Timer' (leading to 'LMM(DA,P,0)' and 'Set(Period,Timer)'), 'RI_LMR(rSA, TxFCf, RxFCf, TxFCb, RxFCI)' (leading to a 'saved' decision), 'MI_LM_Intermediate_Request' (leading to 'MI_LM_Result(N_TF,N_LF,F_TF,F_LF)'), and 'MI_LM_Terminate' (leading to 'MI_LM_Result(N_TF,N_LF,F_TF,F_LF)'). The 'saved' decision leads to an update block for counters if 'Y' (Yes), which then leads to a reset block for saved counters and 'saved=true', returning to the 'Running' state. All 'MI_LM_Result' blocks also return to the 'Running' state. A loop back from 'Init' to 'On-demand LM control' is also shown.](640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg) + +``` + +graph TD + Start([On-demand LM control]) --> Init([Init]) + Init --> MI_LM_Start[/MI_LM_Start(DA,P,Period)/] + MI_LM_Start --> Set_0_Timer[Set(0,Timer)] + Set_0_Timer --> Init_Counters["N_TF=N_LF=0 +F_TF=F_LF=0 +TxFCf_svd=TxFCb_svd=0 +RxFCf_svd=RxFCI_svd=0 +saved=false"] + Init_Counters --> Running([Running]) + Running --> Timer[/Timer/] + Running --> RI_LMR[/RI_LMR(rSA, TxFCf, RxFCf, TxFCb, RxFCI)/] + Running --> MI_LM_Intermediate_Request[/MI_LM_Intermediate_Request/] + Running --> MI_LM_Terminate[/MI_LM_Terminate/] + Timer --> LMM[/LMM(DA,P,0)/] + LMM --> Set_Period_Timer[Set(Period,Timer)] + Set_Period_Timer --> Running + RI_LMR --> saved{saved} + saved -- Y --> Update_Counters["N_TF+=|TxFCb-TxFCb_svd| +N_LF+=|TxFCb-TxFCb_svd| - |RxFCI-RxFCI_svd| +F_TF+=|TxFCf-TxFCf_svd| +F_LF+=|TxFCf-TxFCf_svd| - |RxFCf-RxFCf_svd|"] + Update_Counters --> Reset_Saved["TxFCf_svd=TxFCf +RxFCf_svd=RxFCf +TxFCb_svd=TxFCb +RxFCI_svd=RxFCI +saved=true"] + Reset_Saved --> Running + saved -- N --> Running + MI_LM_Intermediate_Request --> MI_LM_Result_I[/MI_LM_Result(N_TF,N_LF,F_TF,F_LF)/] + MI_LM_Terminate --> MI_LM_Result_T[/MI_LM_Result(N_TF,N_LF,F_TF,F_LF)/] + MI_LM_Result_I --> Running + MI_LM_Result_T --> Running + Init --> Start + +``` + +Flowchart of the on-demand LM control process. The process starts with 'On-demand LM control' leading to 'Init', then 'MI\_LM\_Start(DA,P,Period)', 'Set(0,Timer)', and an initialization block for counters. It then enters a 'Running' state. From 'Running', it branches to 'Timer' (leading to 'LMM(DA,P,0)' and 'Set(Period,Timer)'), 'RI\_LMR(rSA, TxFCf, RxFCf, TxFCb, RxFCI)' (leading to a 'saved' decision), 'MI\_LM\_Intermediate\_Request' (leading to 'MI\_LM\_Result(N\_TF,N\_LF,F\_TF,F\_LF)'), and 'MI\_LM\_Terminate' (leading to 'MI\_LM\_Result(N\_TF,N\_LF,F\_TF,F\_LF)'). The 'saved' decision leads to an update block for counters if 'Y' (Yes), which then leads to a reset block for saved counters and 'saved=true', returning to the 'Running' state. All 'MI\_LM\_Result' blocks also return to the 'Running' state. A loop back from 'Init' to 'On-demand LM control' is also shown. + +G.8021-Y.1341(16)\_F8-37 + +**Figure 8-37 – On-demand LM control behaviour** + +Upon receipt of the MI\_LM\_Start(DA,P,Period), the LM protocol is started. Every period the generation of an LMM frame is triggered (using the LMM(DA,P,0) signal) until the MI\_LM\_Terminate signal is received. + +The received counters are used to count the near-end and far-end transmitted and lost frames. This result is reported using the MI\_LM\_Result(N\_TF, N\_LF, F\_TF, F\_LF) signal after the receipt of the MI\_LM\_Terminate signal or of the MI\_LM\_Intermediate\_Request signal. + +![Flowchart of Proactive LM control behaviour. The process starts with 'Proactive LM control' leading to 'Disabled'. From 'Disabled', it goes to 'MI_LML_Enable'. If 'MI_LML_Enable' is false, it loops back to 'Disabled'. If true, it goes to 'Set(0, Timer)', then initializes variables (N_TF=N_LF=0, F_TF=F_LF=0, TxFCf_svd=TxFCb_svd=0, RxFCf_svd=RxRCI_svd=0, saved=false). It then enters 'Enabled' state. In 'Enabled', it branches to 'Timer', 'RI_LMR(rSA, TxFCf, RxFCf, TxFCb, RxFCI)', and '!MI_LML_Enable'. 'Timer' leads to 'LMM(MI_LM_MAC_DA, MI_LM_Pri, 1)' then 'Set(MI_LM_Period, Timer)'. 'RI_LMR' leads to a 'saved' decision diamond. If 'N' (No), it loops back to 'Enabled'. If 'Y' (Yes), it calculates N_TF, N_LF, F_TF, F_LF, then 'RI_LM_Result(N_TF, N_LF, F_TF, F_LF)', then updates variables (TxFCf_svd=TxFCf, RxFCf_svd=RxFCf, TxFCb_svd=TxFCb, RxFCI_svd=RxFCI, saved=true) and loops back to 'Enabled'.](89f8aefc01866631793087542316cef2_img.jpg) + +``` + +graph TD + Start([Proactive LM control]) --> Disabled([Disabled]) + Disabled --> MI_LML_Enable{MI_LML_Enable} + MI_LML_Enable -- false --> Disabled + MI_LML_Enable -- true --> Set0Timer[Set(0, Timer)] + Set0Timer --> Init["N_TF=N_LF=0 +F_TF=F_LF=0 +TxFCf_svd=TxFCb_svd=0 +RxFCf_svd=RxRCI_svd=0 +saved=false"] + Init --> Enabled([Enabled]) + Enabled --> Timer{Timer} + Enabled --> RI_LMR["RI_LMR(rSA, TxFCf, +RxFCf, TxFCb, RxFCI)"] + Enabled --> NotMI_LML_Enable{"!MI_LML_Enable"} + Timer --> LMM["LMM(MI_LM_MAC_DA, +MI_LM_Pri, 1)"] + LMM --> SetMILMPeriod["Set(MI_LM_Period, Timer)"] + SetMILMPeriod --> Enabled + RI_LMR --> saved{saved} + saved -- N --> Enabled + saved -- Y --> Calc["N_TF=|TxFCb-TxFCb_svd| +N_LF=|TxFCb-TxFCb_svd| - |RxFCI-RxFCI_svd| +F_TF=|TxFCf-TxFCf_svd| +F_LF=|TxFCf-TxFCf_svd| - |RxFCf-RxFCf_svd|"] + Calc --> RI_LM_Result["RI_LM_Result( +N_TF, N_LF, F_TF, F_LF)"] + RI_LM_Result --> Update["TxFCf_svd=TxFCf +RxFCf_svd=RxFCf +TxFCb_svd=TxFCb +RxFCI_svd=RxFCI +saved=true"] + Update --> Enabled + +``` + +Flowchart of Proactive LM control behaviour. The process starts with 'Proactive LM control' leading to 'Disabled'. From 'Disabled', it goes to 'MI\_LML\_Enable'. If 'MI\_LML\_Enable' is false, it loops back to 'Disabled'. If true, it goes to 'Set(0, Timer)', then initializes variables (N\_TF=N\_LF=0, F\_TF=F\_LF=0, TxFCf\_svd=TxFCb\_svd=0, RxFCf\_svd=RxRCI\_svd=0, saved=false). It then enters 'Enabled' state. In 'Enabled', it branches to 'Timer', 'RI\_LMR(rSA, TxFCf, RxFCf, TxFCb, RxFCI)', and '!MI\_LML\_Enable'. 'Timer' leads to 'LMM(MI\_LM\_MAC\_DA, MI\_LM\_Pri, 1)' then 'Set(MI\_LM\_Period, Timer)'. 'RI\_LMR' leads to a 'saved' decision diamond. If 'N' (No), it loops back to 'Enabled'. If 'Y' (Yes), it calculates N\_TF, N\_LF, F\_TF, F\_LF, then 'RI\_LM\_Result(N\_TF, N\_LF, F\_TF, F\_LF)', then updates variables (TxFCf\_svd=TxFCf, RxFCf\_svd=RxFCf, TxFCb\_svd=TxFCb, RxFCI\_svd=RxFCI, saved=true) and loops back to 'Enabled'. + +G.8021-Y.1341(16)\_F8-38 + +**Figure 8-38 – Proactive LM control behaviour** + +The behaviour of the proactive LM control process is defined in Figure 8-38. If the MI\_LML\_Enable is asserted, the process starts to generate LMM frames (using the LMM(MI\_LM\_MAC\_DA, MI\_LM\_Pri, 1) signal). The result (N\_TF, N\_LF, F\_TF, F\_LF) is reported via an LMR reception. + +#### 8.1.9.3 LMM generation process + +This process generates an LMM traffic unit on receipt of the LMM(DA,P,Type) signal. + +![Flowchart of the LMM generation process. The steps are: LMM generation (oval) -> Waiting (oval) -> LMM(DA,P,Type) (parallelogram) -> OAM=LMM(DA, Type, TxFC[P]) (rectangle) -> LMM.D(OAM), LMM.P(P), LMM.DE(0) (parallelogram). A feedback loop connects the final output back to the Waiting state. The diagram is labeled G.8021-Y.1341(16)_F8-39.](675af5bb2357ce5b510e613d04f66bdc_img.jpg) + +Flowchart of the LMM generation process. The steps are: LMM generation (oval) -> Waiting (oval) -> LMM(DA,P,Type) (parallelogram) -> OAM=LMM(DA, Type, TxFC[P]) (rectangle) -> LMM.D(OAM), LMM.P(P), LMM.DE(0) (parallelogram). A feedback loop connects the final output back to the Waiting state. The diagram is labeled G.8021-Y.1341(16)\_F8-39. + +Figure 8-39 – LMM generation behaviour + +The LMM traffic unit contains a source and destination address field and an MSDU field. The format of the MSDU field for LMM traffic units is defined in clauses 9.1 and 9.12 of [ITU-T G.8013]. + +The LMM traffic unit is generated by the LMM generate function in Figure 8-39. Figure 8-40 shows the resultant LMM traffic unit. The type signal is set to 1 if it is the proactive OAM, or set to 0 if it is the on-demand OAM operation. + +| | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----|--------------------|---|---|---|---|---|---|------------------|----------------|---|---|---|---|---|---|---|--------------|-----------|---|---|---|-----------------|---|---|---|---|---|---|---|---|---|---|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | DA=LMM(DA) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | | | | | | SA=Undefined | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 13 | EtherType=89-02 | | | | | | | | | | | | | | | | MEL=Undef | Version=1 | | | | OpCode=43 (LMM) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 17 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | T
y
p
e | TLV Offset =12 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 21 | TxFCf Continued | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 25 | Reserved Continued | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 29 | Reserved Continued | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +Figure 8-40 – LMM traffic unit + +#### 8.1.9.4 LMM reception process + +This process processes received LMM traffic units. It checks the destination address, the DA must be either the local MAC address or it should be a multicast class 1 destination address. If this is the case the LMM reception process writes the Rx Counter value to the received traffic unit in the RxFCf field, and forwards the received traffic unit and complementing P and DE signals as remote information to the LMR generation process. Figure 8-41 shows the LMM reception behaviour. + +![Flowchart of LMM reception behaviour. The process starts with 'LMM reception', followed by 'Waiting'. It then enters a loop: 'LMM_D(OAM), LMM_P(P), LMM_DE(DE)' -> decision 'DA(OAM)=MI_MEP_MAC or DA(OAM)=MC Class 1'. If 'Y' (Yes), it proceeds to 'RxFCf(OAM)=RxFC[P]' -> 'RI_LMM(OAM,P,DE)'. If 'N' (No), it loops back to the entry point of the loop. The diagram is labeled G.8021-Y.1341(16)_F8-41.](cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg) + +``` + +graph TD + Start([LMM reception]) --> Waiting([Waiting]) + Waiting --> Process1[LMM_D(OAM), LMM_P(P), LMM_DE(DE)] + Process1 --> Decision{DA(OAM)=MI_MEP_MAC or DA(OAM)=MC Class 1} + Decision -- N --> Process1 + Decision -- Y --> Process2[RxFCf(OAM)=RxFC[P]] + Process2 --> Process3[RI_LMM(OAM,P,DE)] + Process3 --> Process1 + +``` + +G.8021-Y.1341(16)\_F8-41 + +Flowchart of LMM reception behaviour. The process starts with 'LMM reception', followed by 'Waiting'. It then enters a loop: 'LMM\_D(OAM), LMM\_P(P), LMM\_DE(DE)' -> decision 'DA(OAM)=MI\_MEP\_MAC or DA(OAM)=MC Class 1'. If 'Y' (Yes), it proceeds to 'RxFCf(OAM)=RxFC[P]' -> 'RI\_LMM(OAM,P,DE)'. If 'N' (No), it loops back to the entry point of the loop. The diagram is labeled G.8021-Y.1341(16)\_F8-41. + +**Figure 8-41 – LMM reception behaviour** + +#### 8.1.9.5 LMR generation process + +The LMR generation process generates an LMR traffic unit on receipt of RI\_LMM signals. The LMR traffic unit is based on the received LMM traffic unit (as conveyed in the RI\_LMM\_D signal), however: + +- the SA of the LMM traffic unit becomes the DA of the LMR traffic unit +- the OpCode is set to LMR +- the TxFCb field is assigned the value of the Tx counter. + +Figure 8-42 shows the LMR generation behaviour. + +NOTE – In the generated LMR, in the OAM (MEP) insertion process, the SA will be overwritten with the local MAC address, and the MEL will be overwritten with MI\_MEL. + +Note that the RxFCf field is already assigned a value by the LMM reception process. + +![Flowchart of LMR generation behaviour. The process starts with 'LMR generation', followed by 'Waiting', then 'RI_LMM(OAM,P,DE)'. Next is a block with 'DA(OAM)=SA(OAM)', 'SA(OAM)=Undefined', 'OPC(OAM)=LMR', and 'TxFCb=TxFC[P]'. The final block contains 'LMR.D(OAM), LMR.P(P), LMR.DE(DE)'. A feedback loop connects the final block back to the 'Waiting' block. The diagram is labeled G.8021-Y.1341(16)_F8-42.](c0b9e5fc63e19306394e0d4249da62cd_img.jpg) + +``` + +graph TD + Start([LMR generation]) --> Wait([Waiting]) + Wait --> Input[/RI_LMM(OAM,P,DE)/] + Input --> Process[DA(OAM)=SA(OAM) +SA(OAM)=Undefined +OPC(OAM)=LMR +TxFCb=TxFC[P]] + Process --> Output[/LMR.D(OAM), +LMR.P(P), +LMR.DE(DE)/] + Output --> Wait + +``` + +Flowchart of LMR generation behaviour. The process starts with 'LMR generation', followed by 'Waiting', then 'RI\_LMM(OAM,P,DE)'. Next is a block with 'DA(OAM)=SA(OAM)', 'SA(OAM)=Undefined', 'OPC(OAM)=LMR', and 'TxFCb=TxFC[P]'. The final block contains 'LMR.D(OAM), LMR.P(P), LMR.DE(DE)'. A feedback loop connects the final block back to the 'Waiting' block. The diagram is labeled G.8021-Y.1341(16)\_F8-42. + +Figure 8-42 – LMR generation behaviour + +Figure 8-43 shows the resultant LMR traffic unit. + +| | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +|----|--------------------------|---|---|---|---|---|---|---|------------------------------------|---|---|---|---|---|---|---|------------------------------|---|---|---|-------------------------------|---|---|---|-------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | DA = SA(RI_LMM(D)) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | | | | | | SA = Undefined | | | | | | | | | | | | | | | | +| 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 13 | EtherType = 89-02 | | | | | | | | | | | | | | | | MEL = Undef | | | | Version = version (RI_LMM(D)) | | | | OpCode = 42 (LMR) | | | | | | | | +| 17 | Flags = Flags(RI_LMM(D)) | | | | | | | | TLV Offset = TLV Offset(RI_LMM(D)) | | | | | | | | TxFCf = TxFCf(RI_LMM(D)) | | | | | | | | | | | | | | | | +| 21 | TxFCf continued | | | | | | | | | | | | | | | | RxFCf = RxFCf(RI_LMM(D)) | | | | | | | | | | | | | | | | +| 25 | RxFCf continued | | | | | | | | | | | | | | | | TxFCb = Tx counter | | | | | | | | | | | | | | | | +| 29 | TxFCb continued | | | | | | | | | | | | | | | | End TLV = End TLV(RI_LMM(D)) | | | | | | | | | | | | | | | | + +G.8021-Y.1341(16)\_F8-43 + +Figure 8-43 – LMR traffic unit + +#### 8.1.9.6 LMR reception process + +This process processes received LMR traffic units. If the DA equals the local MAC address, it extracts the counter values TxFCf, RxFCf, TxFCb from the received traffic unit as well as the SA field. These values together with the value of the Rx counter(RxFCI) are forwarded as RI signals. Figure 8-44 shows the LMR reception behaviour. + +![Flowchart of LMR reception behaviour. The process starts with 'LMR reception', followed by 'Waiting'. It then enters a loop: 'LMR_D(OAM), LMR_P(P), LMR_DE(DE)' -> decision 'DA(OAM)=MI_MEP_MAC'. If 'Y' (Yes), it proceeds to 'RI_LMR(rSA(OAM), TxFCf(OAM), RxFCf(OAM), TxFCb(OAM), RxFC[P])'. If 'N' (No), it loops back to the entry point of the loop. The diagram is labeled G.8021-Y.1341(16)_F8-44.](51d4540605fdfa2c090638305022143b_img.jpg) + +``` + +graph TD + Start([LMR reception]) --> Join(( )) + Join --> Waiting([Waiting]) + Waiting --> Process1[/LMR_D(OAM), +LMR_P(P), +LMR_DE(DE)/] + Process1 --> Decision{DA(OAM)=MI_MEP_MAC} + Decision -- N --> Join + Decision -- Y --> Process2[/RI_LMR( +rSA(OAM), +TxFCf(OAM), +RxFCf(OAM), +TxFCb(OAM), +RxFC[P])/] + Process2 --> Join + +``` + +Flowchart of LMR reception behaviour. The process starts with 'LMR reception', followed by 'Waiting'. It then enters a loop: 'LMR\_D(OAM), LMR\_P(P), LMR\_DE(DE)' -> decision 'DA(OAM)=MI\_MEP\_MAC'. If 'Y' (Yes), it proceeds to 'RI\_LMR(rSA(OAM), TxFCf(OAM), RxFCf(OAM), TxFCb(OAM), RxFC[P])'. If 'N' (No), it loops back to the entry point of the loop. The diagram is labeled G.8021-Y.1341(16)\_F8-44. + +G.8021-Y.1341(16)\_F8-44 + +**Figure 8-44 – LMR reception behaviour** + +#### 8.1.9.7 Counter process + +This process counts the number of transmitted and received frames. + +The counter process for LMM/LMR generation receives ETH\_AI and forwards it. It counts the number of ETH\_AI traffic units received with ETH\_AI\_DE to . Figure 8-45 shows the counter behaviour for LMM/LMR generation. + +![Flowchart showing the counter behaviour for LMM/LMR generation. The process starts with 'Counter for LMM/LMR generation', followed by 'Waiting', then two steps of 'Data.D(D), Data.P(P), Data.DE(DE)'. A decision diamond 'DE==' follows. If 'N' (No), it loops back to the start. If 'Y' (Yes), it enters another decision diamond with the condition: 'Etype(D)==89-02 & MEL(D)==MI_MEL & (OPC(D)==LMM || OPC(D)==LMR || OPC(D)==DMM || OPC(D)==DMR || OPC(D)==1DM || OPC(D)==SLM || OPC(D)==SLR || OPC(D)==ISL)'. If 'Y' (Yes), it loops back to the start. If 'N' (No), it performs 'TxFCI[P]++' and then loops back to the start.](c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg) + +``` + +graph TD + Start([Counter for LMM/LMR generation]) --> Waiting([Waiting]) + Waiting --> Data1[/Data.D(D), Data.P(P), Data.DE(DE)/] + Data1 --> Data2[/Data.D(D), Data.P(P), Data.DE(DE)/] + Data2 --> DE{DE==} + DE -- N --> Start + DE -- Y --> Etype{Etype(D)==89-02 & MEL(D)==MI_MEL & (OPC(D)==LMM || OPC(D)==LMR || OPC(D)==DMM || OPC(D)==DMR || OPC(D)==1DM || OPC(D)==SLM || OPC(D)==SLR || OPC(D)==ISL)} + Etype -- Y --> Start + Etype -- N --> TxFCI[TxFCI[P]++] + TxFCI --> Start + +``` + +G.8021-Y.1341(16)\_F8-45 + +Flowchart showing the counter behaviour for LMM/LMR generation. The process starts with 'Counter for LMM/LMR generation', followed by 'Waiting', then two steps of 'Data.D(D), Data.P(P), Data.DE(DE)'. A decision diamond 'DE==' follows. If 'N' (No), it loops back to the start. If 'Y' (Yes), it enters another decision diamond with the condition: 'Etype(D)==89-02 & MEL(D)==MI\_MEL & (OPC(D)==LMM || OPC(D)==LMR || OPC(D)==DMM || OPC(D)==DMR || OPC(D)==1DM || OPC(D)==SLM || OPC(D)==SLR || OPC(D)==ISL)'. If 'Y' (Yes), it loops back to the start. If 'N' (No), it performs 'TxFCI[P]++' and then loops back to the start. + +**Figure 8-45 – Counter behaviour for LMM/LMR generation** + +The counter process for LMM/LMR reception receives ETH\_CI and forwards them as ETH\_AI traffic units. It counts this number of ETH\_AI instances with ETH\_AI\_DE equal to . Figure 8-46 shows the counter behaviour for LMM/LMR reception. + +![Flowchart illustrating the counter behaviour for LMM/LMR reception. The process starts with 'Counter for LMM/LMR reception', followed by 'Waiting', then two steps for 'Data.D(D), Data.P(P), Data.DE(DE)'. A decision diamond 'DE==' follows. If 'N' (No), it loops back to the start. If 'Y' (Yes), it enters another decision diamond with a complex condition: 'Etype(D)==89-02 & MEL(D)==MI_MEL & (OPC(D)==LMM || OPC(D)==LMR || OPC(D)==DMM || OPC(D)==DMR || OPC(D)==IDM || OPC(D)==SLM || OPC(D)==SLR || OPC(D)==ISL)'. If 'Y' (Yes), it loops back to the start. If 'N' (No), it proceeds to 'RxFCI[P]++' and then loops back to the start.](6f11044c88ea04e43de06c3491defeee_img.jpg) + +``` + +graph TD + A([Counter for LMM/LMR reception]) --> B([Waiting]) + B --> C[/Data.D(D), Data.P(P), Data.DE(DE)/] + C --> D[/Data.D(D), Data.P(P), Data.DE(DE)/] + D --> E{DE==} + E -- N --> A + E -- Y --> F{Etype(D)==89-02 & MEL(D)==MI_MEL & (OPC(D)==LMM || OPC(D)==LMR || OPC(D)==DMM || OPC(D)==DMR || OPC(D)==IDM || OPC(D)==SLM || OPC(D)==SLR || OPC(D)==ISL)} + F -- Y --> A + F -- N --> G[RxFCI[P]++] + G --> A + +``` + +G.8021-Y.1341(16)\_F8-46 + +Flowchart illustrating the counter behaviour for LMM/LMR reception. The process starts with 'Counter for LMM/LMR reception', followed by 'Waiting', then two steps for 'Data.D(D), Data.P(P), Data.DE(DE)'. A decision diamond 'DE==' follows. If 'N' (No), it loops back to the start. If 'Y' (Yes), it enters another decision diamond with a complex condition: 'Etype(D)==89-02 & MEL(D)==MI\_MEL & (OPC(D)==LMM || OPC(D)==LMR || OPC(D)==DMM || OPC(D)==DMR || OPC(D)==IDM || OPC(D)==SLM || OPC(D)==SLR || OPC(D)==ISL)'. If 'Y' (Yes), it loops back to the start. If 'N' (No), it proceeds to 'RxFCI[P]++' and then loops back to the start. + +**Figure 8-46 – Counter behaviour for LMM/LMR reception** + +NOTE 1 – To maintain the same behaviour with the earlier versions of this Recommendation, the counter process for LMM/LMR generation and reception excludes the counting of OAM frames which are applicable to both proactive and on-demand performance monitoring (i.e., LMM, LMR, DMM, DMR, IDM, SLM, SLR and ISL). + +NOTE 2 – The current version of this Recommendation assumes that this process activates the needed TxFCI and RxFCI frame counters before any ETH-LM measurement is initiated. The mechanisms for activating these counters as well as the behaviour when an ETH-LM measurement is initiated before these counters are activated are outside the scope of this version of the Recommendation. + +### 8.1.10 Single-ended delay measurement (DM) processes + +#### 8.1.10.1 Overview + +Figure 8-47 shows the different processes inside MEPs and MIPs that are involved in the on-demand single-ended delay measurement protocol. + +NOTE – In previous versions of this Recommendation, single-ended delay measurement was known as delay measurement. With regard to those definitions, refer to [ITU-T G.8013]. + +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 sink extraction process in clause 9.4.2.2, and the MIP on-demand OAM source insertion process in clause 9.4.2.1. In summary, they insert and extract ETH\_CI OAM signals into and from the stream of ETH\_CI\_D traffic units and the complementing P and D signals going through an MEP and MIP; the extraction is based on MEL and OpCode. Furthermore, the insertion process inserts the correct MEL and SA values into the OAM traffic units. + +![Figure 8-47: Overview of processes involved with on-demand single-ended delay measurement. The diagram shows three nodes: MEP (source), MIP (intermediate), and MEP (sink). The source MEP contains an On-demand OAM Insertion block, a DMM Generation block, an On-demand DM Control block, and a DMR Reception block. The MIP contains On-demand OAM Extraction and Insertion blocks. The sink MEP contains an On-demand OAM Extraction block, a DMM Reception block, a DMR Generation block, and an On-demand OAM Insertion block. Data flows include ETH_CI, D,P,DE, MI_DM_Start(DA,P, Test ID,Length,Period), MI_DM_Intermediate_Request, MI_DM_Terminate, MI_DM_Result(count, B_FD[],F_FD[],N_FD[]), DMM(DA,P,0 Test ID TLV,TLV), RI_DMR(rSA, TxTimeStampf, RxTimeStampf, TxStampb, rTestID), MI_MEP_MAC, RI_DMM(D,P,DE), and G.8021-Y.1341(16)_F8-47.](7e14467740b2570a44379b347a697921_img.jpg) + +Figure 8-47: Overview of processes involved with on-demand single-ended delay measurement. The diagram shows three nodes: MEP (source), MIP (intermediate), and MEP (sink). The source MEP contains an On-demand OAM Insertion block, a DMM Generation block, an On-demand DM Control block, and a DMR Reception block. The MIP contains On-demand OAM Extraction and Insertion blocks. The sink MEP contains an On-demand OAM Extraction block, a DMM Reception block, a DMR Generation block, and an On-demand OAM Insertion block. Data flows include ETH\_CI, D,P,DE, MI\_DM\_Start(DA,P, Test ID,Length,Period), MI\_DM\_Intermediate\_Request, MI\_DM\_Terminate, MI\_DM\_Result(count, B\_FD[],F\_FD[],N\_FD[]), DMM(DA,P,0 Test ID TLV,TLV), RI\_DMR(rSA, TxTimeStampf, RxTimeStampf, TxStampb, rTestID), MI\_MEP\_MAC, RI\_DMM(D,P,DE), and G.8021-Y.1341(16)\_F8-47. + +**Figure 8-47 – Overview of processes involved with on-demand single-ended delay measurement** + +The on-demand DM control process controls the on-demand DM protocol. The protocol is activated upon receipt of the MI\_DM\_Start(DA,P,Test ID,Length,Period) signal and remains activated until the MI\_DM\_Terminate signal is received. The result is communicated via the MI\_DM\_Result(count, B\_FD[], F\_FD[], N\_FD[]) signal when the process is terminated by the MI\_DM\_Terminate signal or when an intermediate result is requested via the MI\_DM\_Intermediate\_Request signal. If the on-demand DM control process activates the 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. If the protocol is used in multipoint-to-multipoint environments, the multicast class 1 address can be used for a DA and the test result is independently managed per peer node. + +The DMM generation process generates DMM traffic units that pass through MIPs transparently, but are received and processed by DMM reception processes in MEPs. The DMR generation process may generate a DMR traffic unit in response. This DMR traffic unit also passes transparently through MIPs, but is received and processed by DMR reception processes in MEPs. + +At the source MEP side, the DMM generation process stamps the value of the local time to the TxTimeStampf field in the DMM message when the first bit of the frame is transmitted. Note well that at the sink MEP side, the DMM reception process stamps the value of the local time to the RxTimeStampf field in the DMM message when the last bit of the frame is received. + +The DMR generation and reception process stamps with the same way as the DMM generation and reception process. + +Figure 8-48 shows the different processes inside MEPs and MIPs that are involved in the proactive 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, the MIP OAM extraction process in clause 9.4.2.1, and the MIP OAM insertion process in clause 9.4.2.2. In summary, they insert and extract ETH\_CI OAM signals into and from the stream of ETH\_CI\_D traffic units and the complementing P and D signals going through an MEP and MIP; the extraction is based on MEL and OpCode. Furthermore, the insertion process inserts the correct MEL and SA values into the OAM traffic units. + +![Figure 8-48 – Overview of processes involved with proactive single-ended delay measurement](55086c71bc8ee4c0abc7160d26a8092c_img.jpg) + +The diagram illustrates the flow of Delay Measurement Message (DMM) and Delay Measurement Reply (DMR) between two MEPs (Maintenance association End Points) via a MIP (Maintenance association Intermediate Point). + - \*\*Left MEP\*\*: Receives control signals (MI\_DM\_Enable, MI\_DM\_MAC\_DA, etc.) into a 'Proactive DM Control' block. This triggers 'DMM Generation', which sends a DMM frame through 'Proactive OAM Insertion' onto the ETH\_CI path. It also includes a 'DMR Reception' block that receives replies from the 'Proactive OAM Extraction' block and outputs 'DM\_Result'. + - \*\*Middle MIP\*\*: Contains 'On-demand OAM Extraction' and 'On-demand OAM Insertion' blocks on the ETH\_CI path, which pass the signals through. + - \*\*Right MEP\*\*: Receives the DMM via 'Proactive OAM Extraction' into a 'DMM Reception' block. This triggers 'DMR Generation', which sends a DMR frame back through 'Proactive OAM Insertion' onto the return ETH\_CI path. It receives MI\_MEP\_MAC as an input. + +Figure 8-48 – Overview of processes involved with proactive single-ended delay measurement + +**Figure 8-48 – Overview of processes involved with proactive single-ended delay measurement** + +The proactive DM control process controls the proactive DM protocol. If *MI\_DM\_Enable* is set the DMM frames are sent periodically. The DMM frames are generated with a periodicity determined by *MI\_DM\_Period* and with a priority determined by *MI\_DM\_Pri*. The result (B\_FD, F\_FD, N\_FD) is reported via a DMR reception. If the proactive DM control process activates the 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. If the protocol is used in multipoint-to-multipoint environments, the multicast class 1 address can be used for a DA and the test result is independently managed per peer node. + +**Rec. ITU-T G.8021/Y.1341 (04/2022)**      55 + +#### 8.1.10.2 DM control process + +The behaviour of the on-demand DM control process is defined in Figure 8-49. + +![Flowchart of the on-demand DM control process. The process starts with 'On-demand DM control' leading to 'Init', then 'MI_DM_Start(DA,P,Test ID,Length,Period)', and 'Set(0,Timer) count=0'. It enters a 'Running' state where it branches into 'Timer', 'RI_DMR(rSA, TxTimeStampf, RxTimeStampf, TxTimeStampb, RxTimeb, rTestID)', 'MI_DM_Intermediate_Request', and 'MI_DM_Terminate'. The 'Timer' path generates 'Test ID TLV=GenID(Test ID)', 'TLV=Generate(Length)', 'DMM(DA,P,0, Test ID TLV,TLV)', and 'Set(Period,Timer)'. The 'RI_DMR' path checks 'rSA=DA?' and 'TestID!=NULL and rTestID!=TestID'. If 'N' for 'rSA=DA?', it goes to 'B_FD[count] = (RxTimeb - TxTimeStampf) - (TxTimeStampb - RxTimeStampf)'. If 'Y' for 'rSA=DA?' and 'N' for 'TestID!=NULL and rTestID!=TestID', it also goes to 'B_FD[count]'. From 'B_FD[count]', it checks 'TxTimeStampb = RxTimeStampf = 0?'. If 'N', it sets 'F_FD[count] = Invalid' and 'N_FD[count] = Invalid'. If 'Y', it sets 'F_FD[count] = RxTimeStampf - TxTimeStampf' and 'N_FD[count] = RxTimeb - TxTimeStampb'. All paths lead to 'count++', which loops back to the start of the 'Running' state.](52c40e2f443985dc63f45dec57d90c8c_img.jpg) + +``` + +graph TD + Start([On-demand DM control]) --> Init([Init]) + Init --> MI_DM_Start[MI_DM_Start
DA,P,Test ID,Length,Period] + MI_DM_Start --> Set_0_Timer[Set(0,Timer)
count=0] + Set_0_Timer --> Running([Running]) + Running --> Timer[Timer] + Running --> RI_DMR[RI_DMR
rSA,
TxTimeStampf,
RxTimeStampf,
TxTimeStampb,
RxTimeb,
rTestID] + Running --> MI_DM_Intermediate_Request[MI_DM_Intermediate_Request] + Running --> MI_DM_Terminate[MI_DM_Terminate] + MI_DM_Intermediate_Request --> MI_DM_Result1[MI_DM_Result
count,B_FD[], F_FD[], N_FD[]] + MI_DM_Terminate --> MI_DM_Result2[MI_DM_Result
count,B_FD[], F_FD[], N_FD[]] + Timer --> Test_ID_TLV[Test ID TLV=GenID(Test ID)] + Test_ID_TLV --> TLV[TLV=Generate(Length)] + TLV --> DMM[DMM(DA,P,0,
Test ID TLV,TLV)] + DMM --> Set_Period_Timer[Set(Period,Timer)] + Set_Period_Timer --> Running + RI_DMR --> rSA_DA{rSA=DA?} + rSA_DA -- N --> B_FD_calc[B_FD[count] = (RxTimeb - TxTimeStampf)
- (TxTimeStampb - RxTimeStampf)] + rSA_DA -- Y --> TestID_NULL{TestID!=NULL and
rTestID!=TestID} + TestID_NULL -- Y --> B_FD_calc + TestID_NULL -- N --> B_FD_calc + B_FD_calc --> Tx_Rx_0{TxTimeStampb =
RxTimeStampf = 0?} + Tx_Rx_0 -- N --> Invalid[ F_FD[count] = Invalid
N_FD[count] = Invalid] + Tx_Rx_0 -- Y --> F_FD_calc[ F_FD[count] = RxTimeStampf - TxTimeStampf
N_FD[count] = RxTimeb - TxTimeStampb] + Invalid --> count_inc[count++] + F_FD_calc --> count_inc + count_inc --> Running + +``` + +Flowchart of the on-demand DM control process. The process starts with 'On-demand DM control' leading to 'Init', then 'MI\_DM\_Start(DA,P,Test ID,Length,Period)', and 'Set(0,Timer) count=0'. It enters a 'Running' state where it branches into 'Timer', 'RI\_DMR(rSA, TxTimeStampf, RxTimeStampf, TxTimeStampb, RxTimeb, rTestID)', 'MI\_DM\_Intermediate\_Request', and 'MI\_DM\_Terminate'. The 'Timer' path generates 'Test ID TLV=GenID(Test ID)', 'TLV=Generate(Length)', 'DMM(DA,P,0, Test ID TLV,TLV)', and 'Set(Period,Timer)'. The 'RI\_DMR' path checks 'rSA=DA?' and 'TestID!=NULL and rTestID!=TestID'. If 'N' for 'rSA=DA?', it goes to 'B\_FD[count] = (RxTimeb - TxTimeStampf) - (TxTimeStampb - RxTimeStampf)'. If 'Y' for 'rSA=DA?' and 'N' for 'TestID!=NULL and rTestID!=TestID', it also goes to 'B\_FD[count]'. From 'B\_FD[count]', it checks 'TxTimeStampb = RxTimeStampf = 0?'. If 'N', it sets 'F\_FD[count] = Invalid' and 'N\_FD[count] = Invalid'. If 'Y', it sets 'F\_FD[count] = RxTimeStampf - TxTimeStampf' and 'N\_FD[count] = RxTimeb - TxTimeStampb'. All paths lead to 'count++', which loops back to the start of the 'Running' state. + +G.8021-Y.1341(16)\_F8-49 + +**Figure 8-49 – On-demand DM control behaviour** + +Upon receipt of the MI\_DM\_Start(DA,P,Test ID,Length,Period), the DM protocol is started. Every period the generation of a DMM frame is triggered (using the DMM(DA,P,0,Test ID TLV,TLV) signal) until the MI\_DM\_Terminate signal is received. The TLV field of the DMM frames can have two types of TLVs. The first one is the test ID TLV, which is optionally used for a discriminator of each test and the value Test ID is included in the TLV. The second one is the data TLV, which is determined by the Generate(Length) function. Generate(Length) generates a data TLV with length "Length" of an arbitrary bit pattern to be included in the DMM frame. + +Upon receipt of a DMR traffic unit the delay value recorded by this particular DMR traffic unit is calculated. This result is reported using the MI\_DM\_Result(count, B\_FD[], F\_FD[], N\_FD[]) signal after the receipt of the MI\_DM\_Terminate signal or of the MI\_DM\_Intermediate\_Request signal. Note that the measurements of F\_FD and N\_FD are not supported by peer MEP if both TxTimeStampb and TxTimeStampf are zero. + +![Flowchart of Proactive DM control behaviour. The process starts with 'Proactive DM control' leading to 'Disabled'. From 'Disabled', it goes to 'MI_DM_Enable'. From 'MI_DM_Enable', it goes to 'Set(0,Timer)'. From 'Set(0,Timer)', it goes to 'Enabled'. From 'Enabled', it branches into three paths: 'Timer', 'RI_DMR(rSA, TxTimeStampf, RxTimeStampf, TxTimeStampb, RxTimeb, rTestID)', and '!MI_DM_Enable'. The 'Timer' path leads to 'Test ID TLV=GenID(MI_DM_Test ID)', then 'TLV=Generate(MI_DM_Length)', then 'DMM(MI_DM_MAC_DA, MI_DM_Pri, 1, Test ID TLV, TLV)', then 'Set(MI_DM_Period,Timer)'. The 'RI_DMR' path leads to a decision 'rSA=DA?'. If 'N' (No), it leads to 'F_FD = Invalid' and 'N_FD = Invalid'. If 'Y' (Yes), it leads to a decision 'MI_DM_TestID!=NULL and rTestID!=MI_DM_TestID'. If 'Y' (Yes), it leads to 'F_FD = Invalid' and 'N_FD = Invalid'. If 'N' (No), it leads to 'B_FD = (RxTimeb - TxTimeStampf) - (TxTimeStampb - RxTimeStampf)'. From 'B_FD', it leads to a decision 'TxTimeStampb=RxTimeStampf=0?'. If 'N' (No), it leads to 'F_FD = Invalid' and 'N_FD = Invalid'. If 'Y' (Yes), it leads to 'F_FD = RxTimeStampf - TxTimeStampf' and 'N_FD = RxTimeb - TxTimeStampb'. Both 'F_FD' and 'N_FD' paths lead to 'DM_Result(B_FD, F_FD, N_FD)'. The 'DM_Result' path loops back to the 'Enabled' state.](2cc973099f02f2cc67558feea3b18cde_img.jpg) + +``` + +graph TD + Start([Proactive DM control]) --> Disabled([Disabled]) + Disabled --> MI_DM_Enable[/MI_DM_Enable/] + MI_DM_Enable --> Set0Timer[Set(0,Timer)] + Set0Timer --> Enabled([Enabled]) + Enabled --> Timer[/Timer/] + Enabled --> RI_DMR[/RI_DMR(rSA, TxTimeStampf, RxTimeStampf, TxTimeStampb, RxTimeb, rTestID)/] + Enabled --> NotMI_DM_Enable[/!MI_DM_Enable/] + NotMI_DM_Enable --> Disabled + Timer --> TestIDTLV[Test ID TLV=GenID(MI_DM_Test ID)] + TestIDTLV --> TLVGenerate[TLV=Generate(MI_DM_Length)] + TLVGenerate --> DMM[/DMM(MI_DM_MAC_DA, MI_DM_Pri, 1, Test ID TLV, TLV)/] + DMM --> SetMI_DM_Period[Set(MI_DM_Period,Timer)] + SetMI_DM_Period --> Enabled + RI_DMR --> rSA_DA{rSA=DA?} + rSA_DA -- N --> F_FD_Invalid[F_FD = Invalid +N_FD = Invalid] + rSA_DA -- Y --> MI_DM_TestID{MI_DM_TestID!=NULL and +rTestID!=MI_DM_TestID} + MI_DM_TestID -- Y --> F_FD_Invalid + MI_DM_TestID -- N --> B_FD[B_FD = (RxTimeb - TxTimeStampf) +- (TxTimeStampb - RxTimeStampf)] + B_FD --> TxTimeStampb_RxTimeStampf{TxTimeStampb= +RxTimeStampf=0?} + TxTimeStampb_RxTimeStampf -- N --> F_FD_Invalid + TxTimeStampb_RxTimeStampf -- Y --> F_FD_N_FD[F_FD = RxTimeStampf - TxTimeStampf +N_FD = RxTimeb - TxTimeStampb] + F_FD_Invalid --> DM_Result[/DM_Result(B_FD, F_FD, N_FD)/] + F_FD_N_FD --> DM_Result + DM_Result --> Enabled + +``` + +Flowchart of Proactive DM control behaviour. The process starts with 'Proactive DM control' leading to 'Disabled'. From 'Disabled', it goes to 'MI\_DM\_Enable'. From 'MI\_DM\_Enable', it goes to 'Set(0,Timer)'. From 'Set(0,Timer)', it goes to 'Enabled'. From 'Enabled', it branches into three paths: 'Timer', 'RI\_DMR(rSA, TxTimeStampf, RxTimeStampf, TxTimeStampb, RxTimeb, rTestID)', and '!MI\_DM\_Enable'. The 'Timer' path leads to 'Test ID TLV=GenID(MI\_DM\_Test ID)', then 'TLV=Generate(MI\_DM\_Length)', then 'DMM(MI\_DM\_MAC\_DA, MI\_DM\_Pri, 1, Test ID TLV, TLV)', then 'Set(MI\_DM\_Period,Timer)'. The 'RI\_DMR' path leads to a decision 'rSA=DA?'. If 'N' (No), it leads to 'F\_FD = Invalid' and 'N\_FD = Invalid'. If 'Y' (Yes), it leads to a decision 'MI\_DM\_TestID!=NULL and rTestID!=MI\_DM\_TestID'. If 'Y' (Yes), it leads to 'F\_FD = Invalid' and 'N\_FD = Invalid'. If 'N' (No), it leads to 'B\_FD = (RxTimeb - TxTimeStampf) - (TxTimeStampb - RxTimeStampf)'. From 'B\_FD', it leads to a decision 'TxTimeStampb=RxTimeStampf=0?'. If 'N' (No), it leads to 'F\_FD = Invalid' and 'N\_FD = Invalid'. If 'Y' (Yes), it leads to 'F\_FD = RxTimeStampf - TxTimeStampf' and 'N\_FD = RxTimeb - TxTimeStampb'. Both 'F\_FD' and 'N\_FD' paths lead to 'DM\_Result(B\_FD, F\_FD, N\_FD)'. The 'DM\_Result' path loops back to the 'Enabled' state. + +G.8021-Y.1341(16)\_F8-50 + +**Figure 8-50 – Proactive DM control behaviour** + +The behaviour of the proactive DM control process is defined in Figure 8-50. If the MI\_DM\_Enable is asserted, the process starts to generate DMM frames (using the DMM(MI\_DM\_MAC\_DA, MI\_DM\_Pri, 1, Test ID TLV, TLV) signal). The result (B\_FD, F\_FD, N\_FD) is reported via a DMR reception. + +#### 8.1.10.3 DMM generation process + +The behaviour of the DMM generation process is defined in Figure 8-51. + +![Flowchart of the DMM generation process. The steps are: DMM generation (oval), Waiting (oval), DMM(DA,P, Type,Test ID TLV,TLV) (parallelogram), OAM=DMM(DA,P, Type,Test ID TLV,TLV) (rectangle), TxTimeStampf(OAM)= Local Time (rectangle), and D(OAM,P(P), DE(0)) (parallelogram). A feedback loop connects the final step back to the Waiting step. The diagram is labeled G.8021-Y.1341(16)_F8-51 at the bottom.](fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg) + +``` +graph TD; A([DMM generation]) --> B([Waiting]); B --> C[/DMM(DA,P, Type,Test ID TLV,TLV)/]; C --> D[OAM=DMM(DA,P, Type,Test ID TLV,TLV)]; D --> E[TxTimeStampf(OAM)= Local Time]; E --> F[/D(OAM,P(P), DE(0))/]; F --> B; +``` + +G.8021-Y.1341(16)\_F8-51 + +Flowchart of the DMM generation process. The steps are: DMM generation (oval), Waiting (oval), DMM(DA,P, Type,Test ID TLV,TLV) (parallelogram), OAM=DMM(DA,P, Type,Test ID TLV,TLV) (rectangle), TxTimeStampf(OAM)= Local Time (rectangle), and D(OAM,P(P), DE(0)) (parallelogram). A feedback loop connects the final step back to the Waiting step. The diagram is labeled G.8021-Y.1341(16)\_F8-51 at the bottom. + +**Figure 8-51 – DMM generation behaviour** + +Upon receiving the DMM(DA,P,Type,Test ID TLV,TLV), a single DMM traffic unit (see Figure 8-52) is generated together with the complementing P and DE 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 P signal value is defined by DMM(P). The DE signal is set to 0. The type signal is set to 1 if it is the proactive OAM, or set to 0 if it is the on-demand OAM operation. The test ID signal is determined by the DMM(Test ID TLV) signal. The TLV signal is determined by the DMM(TLV) signal. If both the test ID TLV and data TLV are included in the DMM PDU, it is recommended that the test ID TLV be located at the beginning of the optional TLV field. It makes for easier classification of the test ID in the received PDUs. + +![](7e5f8a1e5575ef87a54c9c091eaaa66d_img.jpg) + +| 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +|-----------------------|---|---|---|---|---|------|---|-----------------|---|---|---|---|---|---|---|------------------------------------------|---|---|---|-------------|---|---|---|-------------------|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| DA = DMM(DA) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | SA = Undefined | | | | | | | | | | | | | | | | +| EtherType = 89-02 | | | | | | | | | | | | | | | | MEL = Undef | | | | Version = 1 | | | | OpCode = 47 (DMM) | | | | | | | | +| 0 | 0 | 0 | 0 | 0 | 0 | TYPE | 0 | TLV Offset = 32 | | | | | | | | TxTimeStampf = Local time | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | 0 (Reserved for DMM receiving equipment) | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | 0 (Reserved for DMR) | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | 0 (Reserved for DMR receiving equipment) | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | Test ID TLV=DMM(Test ID TLV) if exists | | | | | | | | | | | | | | | | +| Test ID TLV Continued | | | | | | | | | | | | | | | | Data TLV = DMM (TLV) if exists | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | End TLV = 0 | | | | | | | | + +G.8021-Y.1341(16)\_F8-52 + +**Figure 8-52 – DMM traffic unit** + +### 8.1.10.4 DMM reception process + +The DMM reception process processes the received DMM traffic units and the complementing P and DE signals. The behaviour is defined in Figure 8-53. + +**Rec. ITU-T G.8021/Y.1341 (04/2022)**      59 + +![Flowchart of DMM reception behaviour. The process starts with 'DMM reception' (oval), followed by 'Waiting' (oval). It then enters a loop: 'D(OAM), P(P), DE(DE)' (parallelogram) -> decision 'DA(OAM)=MI_MEP_MAC or DA(OAM)=MC Class1' (diamond). If 'Y' (Yes), it proceeds to 'TxTimeStampf(OAM)=Local_Time' (rectangle) -> 'RI_DMM(OAM,P,DE)' (parallelogram). If 'N' (No), it loops back to the entry point of 'Waiting'. A small text 'G.8021-Y.1341(16)_F8-53' is at the bottom right.](15de63f0b5df62e6ab9164f2a72e2e33_img.jpg) + +``` + +graph TD + A([DMM reception]) --> B([Waiting]) + B --> C[/D(OAM), P(P), DE(DE)/] + C --> D{DA(OAM)=MI_MEP_MAC or DA(OAM)=MC Class1} + D -- Y --> E[TxTimeStampf(OAM)=Local_Time] + E --> F[/RI_DMM(OAM,P,DE)/] + F --> B + D -- N --> B + +``` + +Flowchart of DMM reception behaviour. The process starts with 'DMM reception' (oval), followed by 'Waiting' (oval). It then enters a loop: 'D(OAM), P(P), DE(DE)' (parallelogram) -> decision 'DA(OAM)=MI\_MEP\_MAC or DA(OAM)=MC Class1' (diamond). If 'Y' (Yes), it proceeds to 'TxTimeStampf(OAM)=Local\_Time' (rectangle) -> 'RI\_DMM(OAM,P,DE)' (parallelogram). If 'N' (No), it loops back to the entry point of 'Waiting'. A small text 'G.8021-Y.1341(16)\_F8-53' is at the bottom right. + +**Figure 8-53 – DMM reception behaviour** + +First the DA is checked, it should be the local MAC address or a multicast class 1 address, otherwise the frame is ignored. + +If the DA is the local MAC or a multicast class 1 address the RxTimeStampf field is assigned the value of the local time and traffic unit and the complementing P and DE signals are forwarded as remote information to the DMR generation process. + +#### 8.1.10.5 DMR generation process + +The DMR generation process generates a DMR traffic unit and its complementing P and DE signals. The behaviour is defined in Figure 8-54. + +![Flowchart of DMR generation behaviour. The process starts with 'DMR generation' (oval), followed by 'Waiting' (oval). It then enters a loop: 'RI_DMM(OAM, P, DE)' (parallelogram) -> 'DA(OAM)=SA(OAM), SA(OAM)=Undefined, OPC(OAM)=DMR, TxTimeStampb(OAM)=Local Time' (rectangle) -> 'D(OAM), D.P(P), D.DE(DE)' (parallelogram). A feedback loop returns from the final parallelogram to the entry point of 'Waiting'. A small text 'G.8021-Y.1341(16)_F8-54' is at the bottom right.](6031b46d356ee24f96bfe37ee2cb7616_img.jpg) + +``` + +graph TD + A([DMR generation]) --> B([Waiting]) + B --> C[/RI_DMM(OAM, P, DE)/] + C --> D["DA(OAM)=SA(OAM) +SA(OAM)=Undefined +OPC(OAM)=DMR +TxTimeStampb(OAM)=Local Time"] + D --> E[/D(OAM), D.P(P), D.DE(DE)/] + E --> B + +``` + +Flowchart of DMR generation behaviour. The process starts with 'DMR generation' (oval), followed by 'Waiting' (oval). It then enters a loop: 'RI\_DMM(OAM, P, DE)' (parallelogram) -> 'DA(OAM)=SA(OAM), SA(OAM)=Undefined, OPC(OAM)=DMR, TxTimeStampb(OAM)=Local Time' (rectangle) -> 'D(OAM), D.P(P), D.DE(DE)' (parallelogram). A feedback loop returns from the final parallelogram to the entry point of 'Waiting'. A small text 'G.8021-Y.1341(16)\_F8-54' is at the bottom right. + +**Figure 8-54 – DMR generation behaviour** + +Upon receipt of the remote information containing a DMM 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: + +- DA of the DMR traffic unit is the SA of the original DMM traffic unit. +- The OpCode is changed into DMR 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 remote information containing the original DMM traffic unit. + +The resulting DMR traffic unit is shown in Figure 8-55. + +NOTE – In the generated DMR, in the OAM (MEP) insertion process, the SA will be overwritten with the local MAC address, and the MEL will be overwritten with MI\_MEL. + +The TLVs are copied from the remote information containing the original DMM traffic unit. If multiple TLVs exist, the order of the TLVs is unchanged. + +![](4260aa4a7ece77c411597094c9d197bd_img.jpg) + +| | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | | +|------|------------------------|---|---|---|---|---|---|---|-----------------------------------|---|---|---|---|---|---|---|------------------------------------------|------------------------------|-----------------|---|---|---|---|---|----------------------------|---|---|---|---|---|---|---|--| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 1 | DA=SA(RI_DMM(D)) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | | | | | | SA=Undefined | | | | | | | | | | | | | | | | | +| 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 13 | EtherType=89-02 | | | | | | | | | | | | | | | | MEL=Undef | Version= Version (RI_DMM(D)) | OpCode=46 (DMR) | | | | | | | | | | | | | | | +| 17 | Flags=Flags(RI_DMM(D)) | | | | | | | | TLV Offset= TLV Offset(RI_DMM(D)) | | | | | | | | TxTimeStampf=TxTimeStampf(RI_DMM(D)) | | | | | | | | | | | | | | | | | +| 21 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 25 | | | | | | | | | | | | | | | | | RxTimeStampf=RxTimeStampf(RI_DMM(D)) | | | | | | | | | | | | | | | | | +| 29 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 33 | | | | | | | | | | | | | | | | | TxTimeStampb=Local Time | | | | | | | | | | | | | | | | | +| 37 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 41 | | | | | | | | | | | | | | | | | 0 (Reserved for DMR reception process) | | | | | | | | | | | | | | | | | +| 45 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 49 | | | | | | | | | | | | | | | | | Test ID TLV=Test ID(RI_DMM(D)) if exists | | | | | | | | | | | | | | | | | +| 53 | Test ID TLV Continued | | | | | | | | | | | | | | | | Data TLV= TLV (RI_DMM(D)) if exists | | | | | | | | | | | | | | | | | +| 57 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 61 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| : | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| last | | | | | | | | | | | | | | | | | | | | | | | | | End TLV=End TLV(RI_DMM(D)) | | | | | | | | | + +Figure 8-55 – DMR traffic unit + +#### 8.1.10.6 DMR reception process + +The DMR reception process processes the received DMR traffic units and the complementing P and DE signals. The behaviour is defined in Figure 8-56. + +![Flowchart of the DMR reception process. The process starts with 'DMR reception', followed by 'Waiting', then a block for 'D(OAM), P(P), DE(DE)'. A decision diamond asks 'DA(OAM)=MI_MEP_MAC'. If 'N' (No), it loops back to the start. If 'Y' (Yes), it proceeds to a block for 'RI_DMR(' followed by a list of parameters: 'SA(OAM), TxTimeStampf(OAM), RxTimeStampf(OAM), TxTimeStampb(OAM), Local Time, Test ID(OAM))'. The diagram is labeled 'G.8021-Y.1341(16)_F8-56'.](b35ea3e304aad7d350a9902270413930_img.jpg) + +``` +graph TD; A([DMR reception]) --> B([Waiting]); B --> C[/D(OAM), P(P), DE(DE)/]; C --> D{DA(OAM)=MI_MEP_MAC}; D -- N --> A; D -- Y --> E[/RI_DMR( +SA(OAM), +TxTimeStampf(OAM), +RxTimeStampf(OAM), +TxTimeStampb(OAM), +Local Time, +Test ID(OAM))/]; E --> A; +``` + +G.8021-Y.1341(16)\_F8-56 + +Flowchart of the DMR reception process. The process starts with 'DMR reception', followed by 'Waiting', then a block for 'D(OAM), P(P), DE(DE)'. A decision diamond asks 'DA(OAM)=MI\_MEP\_MAC'. If 'N' (No), it loops back to the start. If 'Y' (Yes), it proceeds to a block for 'RI\_DMR(' followed by a list of parameters: 'SA(OAM), TxTimeStampf(OAM), RxTimeStampf(OAM), TxTimeStampb(OAM), Local Time, Test ID(OAM))'. The diagram is labeled 'G.8021-Y.1341(16)\_F8-56'. + +Figure 8-56 – DMR reception behaviour + +Upon receipt of a DMR traffic unit the DA field of the traffic unit is checked. If the DA field equals the local MAC address, the DMR traffic unit is processed further, otherwise it is ignored. + +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.1.11 Dual-ended delay measurement (IDM) processes + +#### 8.1.11.1 Overview + +Figure 8-57 shows the different processes inside MEPs and MIPs that are involved in the on-demand dual-ended delay measurement protocol. + +NOTE – In previous versions of this Recommendation, dual-ended delay measurement was known as one-way delay measurement. With regard to those definitions, refer to [ITU-T G.8013]. + +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, and the MIP on-demand OAM sink extraction process in clause 9.4.2.2. In summary, they insert and extract ETH\_CI OAM signals into and from the stream of ETH\_CI\_D traffic units and the complementing P and DE signals going through an MEP and MIP; the extraction is based on MEL and OpCode. Furthermore, the insertion process inserts the correct MEL and SA values into the OAM traffic units. + +![Figure 8-57: Overview of processes involved with on-demand dual-ended delay measurement. The diagram shows three network elements: a source MEP, a MIP, and a sink MEP. The source MEP contains an 'On-demand OAM Insertion' block, an 'IDM Generation' block, and an 'On-demand IDM Control_So' block. It receives 'MI_IDM_Start(DA,P,Test ID,Length,Period)' and 'MI_IDM_Terminate' signals. The 'On-demand IDM Control_So' block sends 'IDM(DA,P,Test ID TLV,TLV)' to the 'IDM Generation' block, which in turn sends 'D,P,DE' to the 'On-demand OAM Insertion' block. The 'On-demand OAM Insertion' block is connected to an 'ETH_CI' interface and passes data to the MIP. The MIP contains an 'On-demand OAM Extraction' block that passes data to the sink MEP. The sink MEP contains an 'On-demand OAM Extraction' block, an 'IDM Reception' block, and an 'On-demand IDM Control_Sk' block. The 'On-demand OAM Extraction' block sends 'D,P,DE' to the 'IDM Reception' block, which receives 'MI_MEP_MAC' and sends 'IDM(rSA,P,TxTimeStampf,RxTimef,rTestID)' to the 'On-demand IDM Control_Sk' block. The 'On-demand IDM Control_Sk' block receives 'MI_IDM_Start (SA,P,Test ID)', 'MI_IDM_Intermediate_Request', 'MI_IDM_Terminate', and 'MI_IDM_Result (count, N_FD[])' signals, and sends 'MI_IDM_Result (count, N_FD[])' back to the 'On-demand OAM Extraction' block, which then outputs to an 'ETH_CI' interface. The diagram is labeled G.8021-Y.1341(16)_F8-57.](99698c448635861b7dc8d352f87a1b2b_img.jpg) + +Figure 8-57: Overview of processes involved with on-demand dual-ended delay measurement. The diagram shows three network elements: a source MEP, a MIP, and a sink MEP. The source MEP contains an 'On-demand OAM Insertion' block, an 'IDM Generation' block, and an 'On-demand IDM Control\_So' block. It receives 'MI\_IDM\_Start(DA,P,Test ID,Length,Period)' and 'MI\_IDM\_Terminate' signals. The 'On-demand IDM Control\_So' block sends 'IDM(DA,P,Test ID TLV,TLV)' to the 'IDM Generation' block, which in turn sends 'D,P,DE' to the 'On-demand OAM Insertion' block. The 'On-demand OAM Insertion' block is connected to an 'ETH\_CI' interface and passes data to the MIP. The MIP contains an 'On-demand OAM Extraction' block that passes data to the sink MEP. The sink MEP contains an 'On-demand OAM Extraction' block, an 'IDM Reception' block, and an 'On-demand IDM Control\_Sk' block. The 'On-demand OAM Extraction' block sends 'D,P,DE' to the 'IDM Reception' block, which receives 'MI\_MEP\_MAC' and sends 'IDM(rSA,P,TxTimeStampf,RxTimef,rTestID)' to the 'On-demand IDM Control\_Sk' block. The 'On-demand IDM Control\_Sk' block receives 'MI\_IDM\_Start (SA,P,Test ID)', 'MI\_IDM\_Intermediate\_Request', 'MI\_IDM\_Terminate', and 'MI\_IDM\_Result (count, N\_FD[])' signals, and sends 'MI\_IDM\_Result (count, N\_FD[])' back to the 'On-demand OAM Extraction' block, which then outputs to an 'ETH\_CI' interface. The diagram is labeled G.8021-Y.1341(16)\_F8-57. + +**Figure 8-57 – Overview of processes involved with on-demand dual-ended delay measurement** + +The on-demand 1DM protocol is controlled by the on-demand 1DM Control\_So and 1DM Control\_Sk processes. The on-demand 1DM Control\_So process triggers the generation of 1DM traffic units upon receipt of an MI\_IDM\_Start(DA,P,Test ID,Length,Period) signal. The on-demand 1DM Control\_Sk process processes the information from received 1DM traffic units after receiving the MI\_IDM\_Start(SA,P,Test ID) signal. The result is communicated by the sink MEP when the on-demand 1DM Control\_Sk process is terminated by the MI\_IDM\_Terminate signal or when an intermediate result is requested via the MI\_IDM\_Intermediate\_Request signal. + +The 1DM generation process generates 1DM messages that pass transparently through MIPs and are received and processed by the 1DM reception process in MEPs. + +At the source MEP side, the 1DM generation process stamps the value of the local time to the TxTimeStampf field in the 1DM message when the first bit of the frame is transmitted. Note well that at the sink MEP side, the 1DM reception process records the value of the local time when the last bit of the frame is received. + +Figure 8-58 shows the different processes inside MEPs and MIPs that are involved in the proactive dual-ended delay measurement protocol. + +![Figure 8-58: Overview of processes involved with proactive dual-ended delay measurement. The diagram shows three network elements: a source MEP, a MIP, and a sink MEP. The source MEP contains a 'Proactive OAM Insertion' block, an 'IDM Generation' block, and a 'Proactive IDM Control_So' block. It receives 'MI_IDM_Enable', 'MI_IDM_MAC_DA', 'MI_IDM_Test_ID', 'MI_IDM_length', 'MI_IDM_Period', and 'MI_IDM_Pri' signals. The 'Proactive IDM Control_So' block sends 'IDM(DA,P,Test ID TLV,TLV)' to the 'IDM Generation' block, which in turn sends 'D,P,DE' to the 'Proactive OAM Insertion' block. The 'Proactive OAM Insertion' block is connected to an 'ETH_CI' interface and passes data to the MIP. The MIP contains an 'On-demand OAM Extraction' block that passes data to the sink MEP. The sink MEP contains a 'Proactive OAM Extraction' block, an 'IDM Reception' block, and a 'Proactive IDM Control_Sk' block. The 'Proactive OAM Extraction' block sends 'D,P,DE' to the 'IDM Reception' block, which receives 'MI_MEP_MAC' and sends 'IDM(rSA,P,TxTimeStampf,RxTimef,rTestID)' to the 'Proactive IDM Control_Sk' block. The 'Proactive IDM Control_Sk' block receives 'MI_IDM_Enable', 'MI_IDM_MAC_DA', 'MI_IDM_Test_ID', and 'MI_IDM_Pri' signals, and sends 'IDM_Result' back to the 'Proactive OAM Extraction' block, which then outputs to an 'ETH_CI' interface. The diagram is labeled G.8021-Y.1341(16)_F8-58.](d6c377ae3e619ff992bd3647dbf43593_img.jpg) + +Figure 8-58: Overview of processes involved with proactive dual-ended delay measurement. The diagram shows three network elements: a source MEP, a MIP, and a sink MEP. The source MEP contains a 'Proactive OAM Insertion' block, an 'IDM Generation' block, and a 'Proactive IDM Control\_So' block. It receives 'MI\_IDM\_Enable', 'MI\_IDM\_MAC\_DA', 'MI\_IDM\_Test\_ID', 'MI\_IDM\_length', 'MI\_IDM\_Period', and 'MI\_IDM\_Pri' signals. The 'Proactive IDM Control\_So' block sends 'IDM(DA,P,Test ID TLV,TLV)' to the 'IDM Generation' block, which in turn sends 'D,P,DE' to the 'Proactive OAM Insertion' block. The 'Proactive OAM Insertion' block is connected to an 'ETH\_CI' interface and passes data to the MIP. The MIP contains an 'On-demand OAM Extraction' block that passes data to the sink MEP. The sink MEP contains a 'Proactive OAM Extraction' block, an 'IDM Reception' block, and a 'Proactive IDM Control\_Sk' block. The 'Proactive OAM Extraction' block sends 'D,P,DE' to the 'IDM Reception' block, which receives 'MI\_MEP\_MAC' and sends 'IDM(rSA,P,TxTimeStampf,RxTimef,rTestID)' to the 'Proactive IDM Control\_Sk' block. The 'Proactive IDM Control\_Sk' block receives 'MI\_IDM\_Enable', 'MI\_IDM\_MAC\_DA', 'MI\_IDM\_Test\_ID', and 'MI\_IDM\_Pri' signals, and sends 'IDM\_Result' back to the 'Proactive OAM Extraction' block, which then outputs to an 'ETH\_CI' interface. The diagram is labeled G.8021-Y.1341(16)\_F8-58. + +**Figure 8-58 – 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 proactive 1DM Control\_So process triggers the generation of 1DM traffic units if MI\_1DM\_Enable signal is set. The 1DM frames are generated with a periodicity determined by MI\_1DM\_Period and with a priority determined by MI\_1DM\_Pri. The result (N\_FD) is reported via a 1DM reception by the 1DM Control\_Sk process. + +#### 8.1.11.2 1DM Control\_So Process + +Figure 8-59 shows the behaviour of the on-demand 1DM Control\_So Process. Upon receipt of the MI\_1DM\_Start(DA,P,Test ID,Length,Period) signal the 1DM protocol is started. The protocol will run until the receipt of the MI\_1DM\_Terminate signal. + +If the DM protocol is running every period (as specified in the MI\_1DM\_Start signal) the generation of a 1DM message is triggered by generating the 1DM(DA,P,0,Test ID TLV,TLV) signal towards the 1DM generation process. The TLV field of the 1DM frames can have two types of TLVs. The first one is the test ID TLV, which is optionally used for a discriminator of each test and the value Test ID is included in the TLV. The second one is the data TLV, which is determined by the Generate(Length) function. Generate(Length) generates a data TLV with length "Length" of an arbitrary bit pattern to be included in the 1DM frame. + +![Flowchart of On-demand 1DM Control_So behaviour](38a51baf4d5b8857d162e5d9a0645269_img.jpg) + +``` +graph TD; A([On-demand 1DM Control_So]) --> B([Init]); B --> C[/MI_1DM_Start(DA,P,Test ID,Length,Period)/]; C --> D[Set(0,Timer)]; D --> E([Running]); E --> F[/Timer/]; E --> G[/MI_1DM_Terminate/]; F --> H[Test ID TLV=GenID(Test ID)]; H --> I[TLV=Generate(Length)]; I --> J[/1DM(DA,P,0, Test ID TLV,TLV)/]; J --> K[Set(Period,Timer)]; K --> E; G --> E; +``` + +The flowchart illustrates the on-demand 1DM Control\_So process. It begins with an oval labeled "On-demand 1DM Control\_So", which points to an oval labeled "Init". From "Init", the flow proceeds to a parallelogram labeled "MI\_1DM\_Start(DA,P,Test ID,Length,Period)". This is followed by a rectangle labeled "Set(0,Timer)". The flow then enters a loop through an oval labeled "Running". From "Running", the flow splits into two paths: one through a parallelogram labeled "Timer" and another through a parallelogram labeled "MI\_1DM\_Terminate". The "Timer" path leads to a sequence of rectangles: "Test ID TLV=GenID(Test ID)", "TLV=Generate(Length)", and "1DM(DA,P,0, Test ID TLV,TLV)" (the latter in a parallelogram), followed by a rectangle "Set(Period,Timer)". The "Set(Period,Timer)" rectangle loops back to the "Running" oval. The "MI\_1DM\_Terminate" parallelogram also loops back to the "Running" oval. + +Flowchart of On-demand 1DM Control\_So behaviour + +G.8021-Y.1341(16)\_F8-59 + +Figure 8-59 – On-demand 1DM Control\_So behaviour + +![Flowchart of Proactive 1DM Control_So behaviour. The process starts at 'Proactive 1DM Control_So', goes to 'Disabled', then 'MI_1DM_Enable', then 'Set(0,Timer)'. It then enters a loop: 'Enabled' -> 'Timer' -> 'Test ID TLV=GenID(MI_1DM_Test ID)' -> 'TLV=Generate(MI_1DM_Length)' -> 'IDM(MI_1DM_MAC_DA, MI_1DM_Pri, 1, Test ID TLV, TLV)' -> 'Set(MI_1DM_Period,Timer)'. From 'Set(MI_1DM_Period,Timer)', it loops back to 'Enabled'. There is also a branch from 'Enabled' to 'MI_1DM_Enable' and a loop back from 'MI_1DM_Enable' to 'Disabled'.](b20942bb14022381a243971ab9790dd9_img.jpg) + +``` + +graph TD + Start([Proactive 1DM Control_So]) --> Disabled([Disabled]) + Disabled --> MI_1DM_Enable{{MI_1DM_Enable}} + MI_1DM_Enable --> Set0Timer[Set(0,Timer)] + Set0Timer --> Enabled([Enabled]) + Enabled --> Timer{{Timer}} + Timer --> TestIDTLV[Test ID TLV=GenID(MI_1DM_Test ID)] + TestIDTLV --> TLVGenerate[TLV=Generate(MI_1DM_Length)] + TLVGenerate --> IDMSignal{{IDM(MI_1DM_MAC_DA, MI_1DM_Pri, 1, Test ID TLV, TLV)}} + IDMSignal --> SetMI_1DM_Period[Set(MI_1DM_Period,Timer)] + SetMI_1DM_Period --> Enabled + Enabled --> MI_1DM_Enable + MI_1DM_Enable --> Disabled + +``` + +Flowchart of Proactive 1DM Control\_So behaviour. The process starts at 'Proactive 1DM Control\_So', goes to 'Disabled', then 'MI\_1DM\_Enable', then 'Set(0,Timer)'. It then enters a loop: 'Enabled' -> 'Timer' -> 'Test ID TLV=GenID(MI\_1DM\_Test ID)' -> 'TLV=Generate(MI\_1DM\_Length)' -> 'IDM(MI\_1DM\_MAC\_DA, MI\_1DM\_Pri, 1, Test ID TLV, TLV)' -> 'Set(MI\_1DM\_Period,Timer)'. From 'Set(MI\_1DM\_Period,Timer)', it loops back to 'Enabled'. There is also a branch from 'Enabled' to 'MI\_1DM\_Enable' and a loop back from 'MI\_1DM\_Enable' to 'Disabled'. + +G.8021-Y.1341(16)\_F8-60 + +**Figure 8-60 – Proactive 1DM Control\_So behaviour** + +The behaviour of the proactive 1DM control process is defined in Figure 8-60. + +If the MI\_1DM\_Enable is asserted, the process starts to generate IDM frames (using the IDM(MI\_1DM\_MAC\_DA,MI\_1DM\_Pri,1, Test ID TLV,TLV) signal). + +#### 8.1.11.3 1DM generation process + +![Flowchart of the 1DM generation process. The steps are: 1DM generation (oval), Waiting (oval), 1DM(DA,P, Type,Test ID TLV,TLV) (parallelogram), OAM=1DM(DA, P, Type, Local Time, Test ID TLV, TLV) (rectangle), and D(OAM),P(P),DE(0) (parallelogram). A feedback loop connects the final step back to the Waiting step. The diagram is labeled G.8021-Y.1341(16)_F8-61 at the bottom.](4801e73fa692059f2ca78196e6e907be_img.jpg) + +``` +graph TD; A([1DM generation]) --> B([Waiting]); B --> C[/1DM(DA,P, Type,Test ID TLV,TLV)/]; C --> D[OAM=1DM(DA, P, Type, Local Time, Test ID TLV, TLV)]; D --> E[/D(OAM),P(P),DE(0)/]; E --> B; +``` + +G.8021-Y.1341(16)\_F8-61 + +Flowchart of the 1DM generation process. The steps are: 1DM generation (oval), Waiting (oval), 1DM(DA,P, Type,Test ID TLV,TLV) (parallelogram), OAM=1DM(DA, P, Type, Local Time, Test ID TLV, TLV) (rectangle), and D(OAM),P(P),DE(0) (parallelogram). A feedback loop connects the final step back to the Waiting step. The diagram is labeled G.8021-Y.1341(16)\_F8-61 at the bottom. + +**Figure 8-61 – 1DM generation behaviour** + +Figure 8-61 shows the 1DM generation process. Upon receiving the 1DM(DA,P,Type,Test ID TLV,TLV) signal a single 1DM traffic unit is generated by the OAM=1DM (DA,P,Type, LocalTime, Test ID TLV, TLV) call. + +Together with this 1DM traffic unit the complementing P and DE signals are generated. The DA of the generated 1DM traffic unit is determined by the 1DM(DA) signal. The TxTimeStampf field is assigned the value of the local time. The value of the P signal is determined by the 1DM(P) signal. The DE signal is set to 0. The type signal is set to 1 if it is the proactive OAM, or set to 0 if it is the on-demand OAM operation. The test ID signal is determined by the 1DM(Test ID TLV) signal. The TLV signal is determined by the 1DM(TLV) signal. + +The resulting traffic unit is shown in Figure 8-62. + +NOTE – In the generated 1DM traffic unit, in the OAM (MEP) insertion process, the SA will be assigned the local MAC address, and the MEL will be assigned by MI\_MEL. + +If both the test ID TLV and data TLV are included in the 1DM PDU, it is recommended that the test ID TLV be located at the beginning of the optional TLV field. It makes for easier classification of the test ID in the received PDUs. + +![](8c3eb53c927f55acd19723cfcd0c43b6_img.jpg) + +| | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +|------|-----------------------|---|---|---|---|---|---|---|----------------|---|---|---|---|---|---|---|------------------------------------------|---|---|---|-----------|---|---|---|-----------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | DA=IDM(DA) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | | | | | | SA=Undefined | | | | | | | | | | | | | | | | +| 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 13 | EtherType=89-02 | | | | | | | | | | | | | | | | MEL=Undef | | | | Version=1 | | | | OpCode=45 (IDM) | | | | | | | | +| 17 | 0 | 0 | 0 | 0 | 0 | 0 | T | y | TLV Offset =16 | | | | | | | | TxTimeStampf=Local Time | | | | | | | | | | | | | | | | +| 21 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 25 | | | | | | | | | | | | | | | | | 0 (Reserved for IDM receiving equipment) | | | | | | | | | | | | | | | | +| 29 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 33 | | | | | | | | | | | | | | | | | Test ID TLV=IDM(Test ID TLV) if exists | | | | | | | | | | | | | | | | +| 37 | Test ID TLV Continued | | | | | | | | | | | | | | | | Data TLV=IDM(TLV) if exists | | | | | | | | | | | | | | | | +| 41 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 45 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| : | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| last | | | | | | | | | | | | | | | | | | | | | | | | | End TLV (0) | | | | | | | | + +Figure 8-62 – 1DM traffic unit + +#### 8.1.11.4 1DM reception process + +The 1DM reception process processes the received 1DM traffic units and the complementing P and DE signals. The behaviour is defined in Figure 8-63. + +![Flowchart of 1DM reception behaviour. It starts with 'IDM reception', followed by 'Waiting', then a block for 'D(OAM), P(P), DE(DE)'. A decision diamond asks 'DA(OAM)=MI_MEP_MAC or DA(OAM)=MC Class1'. If 'N' (No), it loops back to 'Waiting'. If 'Y' (Yes), it proceeds to a block for 'IDM(SA(OAM), P(P), TxTimeStampf(OAM), Local Time, Test ID(OAM))', which then loops back to 'Waiting'.](9f50279046b74a4e66a1a0144c3b1d11_img.jpg) + +``` + +graph TD + A([IDM reception]) --> B([Waiting]) + B --> C[/D(OAM), P(P), DE(DE)/] + C --> D{DA(OAM)=MI_MEP_MAC or DA(OAM)=MC Class1} + D -- N --> B + D -- Y --> E[/IDM(SA(OAM), P(P), TxTimeStampf(OAM), Local Time, Test ID(OAM))/] + E --> B + +``` + +G.8021-Y.1341(16)\_F8-63 + +Flowchart of 1DM reception behaviour. It starts with 'IDM reception', followed by 'Waiting', then a block for 'D(OAM), P(P), DE(DE)'. A decision diamond asks 'DA(OAM)=MI\_MEP\_MAC or DA(OAM)=MC Class1'. If 'N' (No), it loops back to 'Waiting'. If 'Y' (Yes), it proceeds to a block for 'IDM(SA(OAM), P(P), TxTimeStampf(OAM), Local Time, Test ID(OAM))', which then loops back to 'Waiting'. + +Figure 8-63 – 1DM reception behaviour + +Upon receipt of a 1DM traffic unit the DA field is checked. The 1DM traffic unit is processed if the DA is equal to the local MAC address or multicast class 1 MAC address. Otherwise, the traffic unit is ignored. + +If the 1DM traffic unit is processed the SA and TxTimeStampf fields are extracted and forwarded to the 1DM Control\_Sk process together with the local time using the IDM(rSA,rP,TxTimeStampf,RxTimef,rTestID) signal. + +#### 8.1.11.5 1DM Control\_Sk Process + +Figure 8-64 shows the behaviour of the on-demand 1DM Control\_Sk process. The MI\_1DM\_Start(SA,P,TestID) signal starts the processing of 1DM messages coming from an MEP with SA as the MAC address. The protocol runs until the receipt of the MI\_1DM\_Terminate signal. + +While running the process processes the received 1DM(rSA,rP,TxTimeStampf,RxTimef,rTestID) information. First the rSA is compared with the SA from the MI\_1DM\_Start (SA) signal. If the rSA is not equal to this SA, the information is ignored. Next the rP is compared with the priority from the MI\_1DM\_Start (P) signal. If the rP is not equal to this P, the information is ignored. Finally, the rTestID is compared with the TestID from the MI\_1DM\_Start (Test ID) signal. If the MI\_1DM\_Start (Test ID) signal is configured and rTestID is available but both values are different, the information is ignored. Otherwise, the delay from the single received 1DM traffic unit is calculated. This result is reported using the MI\_1DM\_Result(count, N\_FD[]) signal after the receipt of the MI\_1DM\_Terminate signal or of the MI\_1DM\_Intermediate\_Request signal. + +![Flowchart of the On-demand 1DM Control_Sk process. The process starts with 'On-demand 1DM Control_Sk' leading to 'Init', then 'Count=0', and 'MI_1DM_Start(SA,P,Test ID)'. It then enters a 'Running' loop. Inside the loop, it receives '1DM(rSA,rP,TxTimeStampf,RxTimef,rTestID)'. It checks if rSA==SA. If No (N), it loops back to the start of the loop. If Yes (Y), it checks if rP==P. If No (N), it loops back. If Yes (Y), it checks if TestID!=NULL and rTestID!=TestID. If Yes (Y), it loops back. If No (N), it calculates N_FD[count] = RxTimef - TxTimeStampf and increments count. It then checks for 'MI_1DM_Intermediate_Request' or 'MI_1DM_Terminate'. Both lead to 'MI_1DM_Result(count,N_FD[])'. The 'MI_1DM_Terminate' path also loops back to the start of the loop.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` +graph TD; A([On-demand 1DM Control_Sk]) --> B([Init]); B --> C[Count=0]; C --> D[/MI_1DM_Start(SA,P,Test ID)/]; D --> E([Running]); E --> F[/1DM(rSA,rP,TxTimeStampf,RxTimef,rTestID)/]; F --> G{rSA==SA?}; G -- N --> E; G -- Y --> H{rP==P?}; H -- N --> E; H -- Y --> I{TestID!=NULL and rTestID!=TestID}; I -- Y --> E; I -- N --> J[N_FD[count] = RxTimef - TxTimeStampf
count++]; J --> E; E --> K[/MI_1DM_Intermediate_Request/]; K --> L[/MI_1DM_Result(count,N_FD[])/]; E --> M[/MI_1DM_Terminate/]; M --> NFD[/MI_1DM_Result(count,N_FD[])/]; NFD --> E; +``` + +Flowchart of the On-demand 1DM Control\_Sk process. The process starts with 'On-demand 1DM Control\_Sk' leading to 'Init', then 'Count=0', and 'MI\_1DM\_Start(SA,P,Test ID)'. It then enters a 'Running' loop. Inside the loop, it receives '1DM(rSA,rP,TxTimeStampf,RxTimef,rTestID)'. It checks if rSA==SA. If No (N), it loops back to the start of the loop. If Yes (Y), it checks if rP==P. If No (N), it loops back. If Yes (Y), it checks if TestID!=NULL and rTestID!=TestID. If Yes (Y), it loops back. If No (N), it calculates N\_FD[count] = RxTimef - TxTimeStampf and increments count. It then checks for 'MI\_1DM\_Intermediate\_Request' or 'MI\_1DM\_Terminate'. Both lead to 'MI\_1DM\_Result(count,N\_FD[])'. The 'MI\_1DM\_Terminate' path also loops back to the start of the loop. + +G.8021-Y.1341(16)\_F8-64 + +Figure 8-64 – On-demand 1DM Control\_Sk process + +![Flowchart of the Proactive 1DM Control_Sk process. The process starts with 'Proactive 1DM Control_Sk' (oval), leading to 'Disabled' (oval), then 'MI_1DM_Enable' (parallelogram). It then enters an 'Enabled' (oval) state. From 'Enabled', it branches to 'IDM(rSA,rP,TxTimeStampf, RxTimef,rTestID)' (parallelogram) and '!MI_1DM_Enable' (parallelogram). The 'IDM' parallelogram leads to a decision diamond 'rSA= MI_1DM_MAC_SA?'. If 'N' (No), it loops back to the entry point before 'Enabled'. If 'Y' (Yes), it leads to another decision diamond 'rP= MI_1DM_Pri?'. If 'N', it loops back. If 'Y', it leads to a third decision diamond 'MI_1DM_TestID!=NULL and rTestID!=MI_1DM_TestID'. If 'Y', it loops back. If 'N', it leads to a process block 'N_FD = RxTimef - TxTimeStampf', which then leads to 'IDM_Result(N_FD)' (parallelogram). Finally, it loops back to the entry point before 'Enabled'.](3bf1696c3034743b5ab07a0b5e398347_img.jpg) + +``` + +graph TD + Start([Proactive 1DM Control_Sk]) --> Disabled([Disabled]) + Disabled --> MI_1DM_Enable[/MI_1DM_Enable/] + MI_1DM_Enable --> Enabled([Enabled]) + Enabled --> IDM[/IDM(rSA,rP,TxTimeStampf, RxTimef,rTestID)/] + Enabled --> NotMI_1DM_Enable[/!MI_1DM_Enable/] + IDM --> rSA{rSA= MI_1DM_MAC_SA?} + rSA -- N --> Entry + rSA -- Y --> rP{rP= MI_1DM_Pri?} + rP -- N --> Entry + rP -- Y --> TestID{MI_1DM_TestID!=NULL and rTestID!=MI_1DM_TestID} + TestID -- Y --> Entry + TestID -- N --> N_FD[N_FD = RxTimef - TxTimeStampf] + N_FD --> IDM_Result[/IDM_Result(N_FD)/] + IDM_Result --> Entry + Entry --> Enabled + style Entry fill:none,stroke:none + +``` + +Flowchart of the Proactive 1DM Control\_Sk process. The process starts with 'Proactive 1DM Control\_Sk' (oval), leading to 'Disabled' (oval), then 'MI\_1DM\_Enable' (parallelogram). It then enters an 'Enabled' (oval) state. From 'Enabled', it branches to 'IDM(rSA,rP,TxTimeStampf, RxTimef,rTestID)' (parallelogram) and '!MI\_1DM\_Enable' (parallelogram). The 'IDM' parallelogram leads to a decision diamond 'rSA= MI\_1DM\_MAC\_SA?'. If 'N' (No), it loops back to the entry point before 'Enabled'. If 'Y' (Yes), it leads to another decision diamond 'rP= MI\_1DM\_Pri?'. If 'N', it loops back. If 'Y', it leads to a third decision diamond 'MI\_1DM\_TestID!=NULL and rTestID!=MI\_1DM\_TestID'. If 'Y', it loops back. If 'N', it leads to a process block 'N\_FD = RxTimef - TxTimeStampf', which then leads to 'IDM\_Result(N\_FD)' (parallelogram). Finally, it loops back to the entry point before 'Enabled'. + +G.8021-Y.1341(16)\_F8-65 + +**Figure 8-65 – Proactive 1DM Control\_Sk process** + +The behaviour of the proactive 1DM Control\_Sk Process is defined in Figure 8-65. If the MI\_1DM\_Enable is asserted, the result (N\_FD) is reported via a 1DM reception. + +### 8.1.12 Test (TST) processes + +#### 8.1.12.1 Overview + +Figure 8-66 shows the different processes inside MEPs and MIPs that are involved in the test 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 sink extraction process in clause 9.4.2.2. In summary, they insert and extract ETH\_CI OAM signals into and from the stream of ETH\_CI\_D traffic units together with the complementing P and DE signals going through an MEP and MIP; the extraction is based on MEL and OpCode. Furthermore, the insertion process inserts the correct MEL and SA values into the OAM traffic units. + +![Figure 8-66: Overview of processes involved with the test protocol. The diagram shows three network elements: a transmitting MEP, a MIP, and a receiving MEP. The transmitting MEP contains a 'TST Control_So' process that receives 'MI_TST(DA,DE,P,Pattern,Length,Period)', 'MI_TST_Terminate', and 'MI_TST_Result(Sent)' signals. It sends 'TST(DA,P,DE,TLV,TID)' to a 'TST Generation' block, which then connects to an 'On-demand OAM Insertion' block. This block interfaces with 'ETH_CI' and sends data to the MIP. The MIP contains an 'On-demand OAM Extraction' block that interfaces with 'ETH_CI' and sends data to the receiving MEP. The receiving MEP contains an 'On-demand OAM Extraction' block that interfaces with 'ETH_CI' and sends data to a 'TST Reception' block. This block sends 'TST(SA,TID,TLV)' to a 'TST Control_Sk' process. The 'TST Control_Sk' process receives 'MI_TST_Start(SA,Pattern)', 'MI_TST_Terminate', and 'MI_TST_Result(Rec,CRC,BER,OO)' signals. A reference 'G.8021-Y.1341(16)_F8-66' is shown at the bottom right.](32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg) + +Figure 8-66: Overview of processes involved with the test protocol. The diagram shows three network elements: a transmitting MEP, a MIP, and a receiving MEP. The transmitting MEP contains a 'TST Control\_So' process that receives 'MI\_TST(DA,DE,P,Pattern,Length,Period)', 'MI\_TST\_Terminate', and 'MI\_TST\_Result(Sent)' signals. It sends 'TST(DA,P,DE,TLV,TID)' to a 'TST Generation' block, which then connects to an 'On-demand OAM Insertion' block. This block interfaces with 'ETH\_CI' and sends data to the MIP. The MIP contains an 'On-demand OAM Extraction' block that interfaces with 'ETH\_CI' and sends data to the receiving MEP. The receiving MEP contains an 'On-demand OAM Extraction' block that interfaces with 'ETH\_CI' and sends data to a 'TST Reception' block. This block sends 'TST(SA,TID,TLV)' to a 'TST Control\_Sk' process. The 'TST Control\_Sk' process receives 'MI\_TST\_Start(SA,Pattern)', 'MI\_TST\_Terminate', and 'MI\_TST\_Result(Rec,CRC,BER,OO)' signals. A reference 'G.8021-Y.1341(16)\_F8-66' is shown at the bottom right. + +**Figure 8-66 – Overview of processes involved with the test protocol** + +The TST protocol is controlled by the TST Control\_So and TST Control\_Sk processes. The TST Control\_So process triggers the generation of TST traffic units after the receipt of an MI\_TST\_Start(DA,DE,P,Pattern,Length,Period) signal. The TST Control\_Sk process processes the information from received TST traffic units after receiving the MI\_TST\_Start(SA,Pattern) signal. + +The TST generation process generates TST messages that pass transparently through MIPs and are received and processed by the TST reception process in MEPs. + +The processes are defined below. + +#### 8.1.12.2 TST Control\_So process + +Figure 8-67 defines the behaviour of the TST Control\_So process. This process starts the transmission of TST traffic units after receiving the MI\_Test(DA,DE,P,Pattern,Length,Period) signal. Each transmission of TST traffic units is triggered by the generation of the TST(DA,P,DE,TLV,TID) signal. This is continued until the receipt of the MI\_Test\_Terminate signal. After receiving this signal the number of triggered TST traffic units is reported back using the MI\_Test\_Result(Sent) signal. + +The TLV field of the TST frames 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 2^31-1 without CRC-32" +- 3: "PRBS 2^31-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 TST frame. Therefore, this TLV is passed using the TST(DA,P,DE,TLV,TID) signal to the TST generation process. + +![Flowchart of TST Control_So behaviour. The process starts with 'TST Control_So' (oval), followed by 'Init' (oval), then 'MI_Test(DA,DE,P,Pattern,Length,Period)' (parallelogram). It then enters a loop: 'Set(0,TxTimer)' and 'Sent=0' (rectangle), 'Waiting Test' (oval), 'TxTimer' (parallelogram), 'TLV=Generate(Pattern,Length)' (rectangle), 'TST(DA,P,DE,TLV,TID)' (parallelogram), 'Sent++, TID++, set(Period,TxTimer)' (rectangle). From 'Waiting Test', it also branches to 'MI_TST_Terminate' (parallelogram) and 'MI_TST_Result(Sent)' (parallelogram). Arrows indicate the flow and loops.](c6212a3b14736d6a8c81ace75ae94ccf_img.jpg) + +``` + +graph TD + A([TST Control_So]) --> B([Init]) + B --> C[/MI_Test(DA,DE,P,Pattern,Length,Period)/] + C --> D["Set(0,TxTimer) +Sent=0"] + D --> E([Waiting Test]) + E --> F[/TxTimer/] + E --> G[/MI_TST_Terminate/] + F --> H["TLV=Generate(Pattern,Length)"] + H --> I[/TST(DA,P,DE,TLV,TID)/] + I --> J["Sent++ +TID++ +set(Period,TxTimer)"] + J --> E + G --> K[/MI_TST_Result(Sent)/] + K --> B + +``` + +G.8021-Y.1341(16)\_F8-67 + +Flowchart of TST Control\_So behaviour. The process starts with 'TST Control\_So' (oval), followed by 'Init' (oval), then 'MI\_Test(DA,DE,P,Pattern,Length,Period)' (parallelogram). It then enters a loop: 'Set(0,TxTimer)' and 'Sent=0' (rectangle), 'Waiting Test' (oval), 'TxTimer' (parallelogram), 'TLV=Generate(Pattern,Length)' (rectangle), 'TST(DA,P,DE,TLV,TID)' (parallelogram), 'Sent++, TID++, set(Period,TxTimer)' (rectangle). From 'Waiting Test', it also branches to 'MI\_TST\_Terminate' (parallelogram) and 'MI\_TST\_Result(Sent)' (parallelogram). Arrows indicate the flow and loops. + +**Figure 8-67 – TST Control\_So behaviour** + +#### **8.1.12.3 TST generation process** + +Figure 8-68 defines the behaviour of the TST generation process. + +![Flowchart of TST generation behaviour. The process starts with 'TST generation' (oval), followed by 'Waiting' (oval), then 'TST(DA,P,DE,TLV,TID)' (parallelogram). It then enters a loop: 'OAM=TST(DA, TLV, TID)' (rectangle), 'D(OAM,P(P),DE(DE))' (parallelogram), which loops back to 'Waiting'.](04f7b8f64493f6d83188232f10f86fe2_img.jpg) + +``` + +graph TD + A([TST generation]) --> B([Waiting]) + B --> C[/TST(DA,P,DE,TLV,TID)/] + C --> D["OAM=TST( +DA, +TLV, +TID +)"] + D --> E[/D(OAM),P(P),DE(DE)/] + E --> B + +``` + +G.8021-Y.1341(16)\_F8-68 + +Flowchart of TST generation behaviour. The process starts with 'TST generation' (oval), followed by 'Waiting' (oval), then 'TST(DA,P,DE,TLV,TID)' (parallelogram). It then enters a loop: 'OAM=TST(DA, TLV, TID)' (rectangle), 'D(OAM,P(P),DE(DE))' (parallelogram), which loops back to 'Waiting'. + +**Figure 8-68 – TST generation behaviour** + +Upon receiving the TST(DA,P,DE,TLV,TID), a single TST traffic unit is generated together with the complementing P and DE signals. The TST traffic unit is generated by: + +$$\text{OAM} = \text{TST}(\text{DA}, \text{TLV}, \text{TID}).$$ + +The DA of the generated TST traffic unit is determined by the TST(DA) signal. The transaction identifier field gets the value of TST(TID); the TLV field is populated with TST(TLV). The resulting TST traffic unit is shown in Figure 8-69. + +NOTE – In the generated TST traffic unit, in the OAM (MEP) insertion process, the SA will be assigned the local MAC address, and the MEL will be assigned by MI\_MEL. + +The P signal is determined by the TST(P) signal. + +The DE signal is determined by the TST(DE) signal. + +![](efb282bed9f06eef1987a14fb27bc599_img.jpg) + +| | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +|---|----------------------------------|---|---|---|---|---|---|---|---------------|---|---|---|---|---|---|---|---------------------------------|---|---|---|-----------|---|---|---|----------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | DA=TST(DA) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2 | | | | | | | | | | | | | | | | | SA=Undefined | | | | | | | | | | | | | | | | +| 3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4 | EtherType=89-02 | | | | | | | | | | | | | | | | MEL=Undef | | | | Version=0 | | | | OpCode=37(TST) | | | | | | | | +| 5 | Flags=0 | | | | | | | | TLV Offset =4 | | | | | | | | Transaction Identifier=TST(TID) | | | | | | | | | | | | | | | | +| 6 | Transaction Identifier Continued | | | | | | | | | | | | | | | | TST(TLV) | | | | | | | | | | | | | | | | +| 7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 9 | | | | | | | | | | | | | | | | | End TLV=0 | | | | | | | | | | | | | | | | + +Figure 8-69 – TST traffic unit + +#### 8.1.12.4 TST reception process + +Figure 8-70 defines the behaviour of the TST reception process. + +![Flowchart of the TST reception process. It starts with 'TST reception', followed by 'Waiting', then a process block 'D(OAM, P(P), DE(DE))'. A decision diamond asks 'DA(OAM)=MI_MEP_MAC or DA(OAM)=MC Class 1'. If 'Y' (Yes), it goes to a process block 'TST(SA(OAM), TID(OAM), TLV(OAM))'. If 'N' (No), it loops back to the 'Waiting' state. The diagram is labeled G.8021-Y.1341(16)_F8-70.](ec31af936fa94a6917bf19f154df8ac3_img.jpg) + +``` + +graph TD + A([TST reception]) --> B([Waiting]) + B --> C[/D(OAM, P(P), DE(DE))/] + C --> D{DA(OAM)=MI_MEP_MAC or DA(OAM)=MC Class 1} + D -- Y --> E[/TST(SA(OAM), TID(OAM), TLV(OAM))/] + D -- N --> B + E --> F[G.8021-Y.1341(16)_F8-70] + +``` + +Flowchart of the TST reception process. It starts with 'TST reception', followed by 'Waiting', then a process block 'D(OAM, P(P), DE(DE))'. A decision diamond asks 'DA(OAM)=MI\_MEP\_MAC or DA(OAM)=MC Class 1'. If 'Y' (Yes), it goes to a process block 'TST(SA(OAM), TID(OAM), TLV(OAM))'. If 'N' (No), it loops back to the 'Waiting' state. The diagram is labeled G.8021-Y.1341(16)\_F8-70. + +Figure 8-70 – TST reception behaviour + +First the DA is checked, it should be the local MAC address (as configured via MI\_MEP\_MAC) or a multicast class 1 address, otherwise the frame is ignored. + +If the DA is the local MAC or a multicast class 1 address the SA, TID and TLV fields from the TST traffic unit are forwarded using the TST signal. + +#### **8.1.12.5 TST Control\_Sk process** + +Figure 8-71 shows the behaviour of the TST Control\_Sk process. The MI\_TST\_Start (SA) signal starts the processing of TST messages coming from an MEP with SA as the MAC address. The protocol is running until the receipt of the MI\_TST\_Terminate signal. + +While running, the process processes the received TST(rSA,rTLV,TID) information. First the rSA is compared with the SA from the MI\_TST\_Start (SA) signal. If the rSA is not equal to this SA, the information is ignored. Otherwise, the received information is processed. + +First, the received TST 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 frames is incremented by one (OO++). + +![Flowchart of TST Control_Sk behaviour. The process starts with 'TST Control_Sk' (oval) leading to 'Init' (oval), then 'MI_TST_Start(SA,Pattern)' (parallelogram). It initializes variables: OLD_TID=Undef, REC=0, CRC=0, BER=0, OO=0. It then enters a 'Waiting Test' (oval) state. From here, it can receive 'TST(rSA,rTLV,TID)' (parallelogram), 'MI_TST_Terminate' (parallelogram), or a 'Timer' (parallelogram). The 'TST' path checks if rSA==SA? If No (N), it loops back to 'Waiting Test'. If Yes (Y), it increments REC++, then checks if (Pattern==1 or Pattern==3)&& (CheckCRC(TLV)==Fail). If Yes (Y), it increments CRC++. Then it checks if Check(Pattern, TLV)==Fail. If Yes (Y), it increments BER++. Then it checks if (OLD_TID=Undef)&& (TID!=OLD_TID+1). If Yes (Y), it increments OO++. Finally, it updates OLD_TID=TID and loops back to 'Waiting Test'. The 'MI_TST_Terminate' path leads to 'Set(5s,Timer)' (rectangle). The 'Timer' path leads to 'MI_TST_Result( REC,CRC,BER,OO )' (parallelogram), which then loops back to 'Init'.](24ba47df8be44ae91945d88ce2232df5_img.jpg) + +``` + +graph TD + TST_Control_Sk([TST Control_Sk]) --> Init([Init]) + Init --> MI_TST_Start[/MI_TST_Start(SA,Pattern)/] + MI_TST_Start --> InitVars["OLD_TID=Undef +REC=0 +CRC=0 +BER=0 +OO=0"] + InitVars --> WaitingTest([Waiting Test]) + WaitingTest --> TST[/TST(rSA,rTLV,TID)/] + WaitingTest --> MI_TST_Terminate[/MI_TST_Terminate/] + WaitingTest --> Timer[/Timer/] + TST --> rSA_SA{rSA==SA?} + rSA_SA -- N --> WaitingTest + rSA_SA -- Y --> REC_inc[REC++] + REC_inc --> Pattern_CRC{Pattern==1 or Pattern==3 && CheckCRC(TLV)==Fail} + Pattern_CRC -- Y --> CRC_inc[CRC++] + CRC_inc --> Check_Pattern_TLV{Check(Pattern, TLV)==Fail} + Check_Pattern_TLV -- Y --> BER_inc[BER++] + BER_inc --> OLD_TID_TID{OLD_TID=Undef && TID!=OLD_TID+1} + OLD_TID_TID -- Y --> OO_inc[OO++] + OO_inc --> OLD_TID_TID_update[OLD_TID=TID] + OLD_TID_TID_update --> WaitingTest + MI_TST_Terminate --> Set_Timer[Set(5s,Timer)] + Timer --> MI_TST_Result[/MI_TST_Result( REC,CRC,BER,OO )/] + MI_TST_Result --> Init + +``` + +Flowchart of TST Control\_Sk behaviour. The process starts with 'TST Control\_Sk' (oval) leading to 'Init' (oval), then 'MI\_TST\_Start(SA,Pattern)' (parallelogram). It initializes variables: OLD\_TID=Undef, REC=0, CRC=0, BER=0, OO=0. It then enters a 'Waiting Test' (oval) state. From here, it can receive 'TST(rSA,rTLV,TID)' (parallelogram), 'MI\_TST\_Terminate' (parallelogram), or a 'Timer' (parallelogram). The 'TST' path checks if rSA==SA? If No (N), it loops back to 'Waiting Test'. If Yes (Y), it increments REC++, then checks if (Pattern==1 or Pattern==3)&& (CheckCRC(TLV)==Fail). If Yes (Y), it increments CRC++. Then it checks if Check(Pattern, TLV)==Fail. If Yes (Y), it increments BER++. Then it checks if (OLD\_TID=Undef)&& (TID!=OLD\_TID+1). If Yes (Y), it increments OO++. Finally, it updates OLD\_TID=TID and loops back to 'Waiting Test'. The 'MI\_TST\_Terminate' path leads to 'Set(5s,Timer)' (rectangle). The 'Timer' path leads to 'MI\_TST\_Result( REC,CRC,BER,OO )' (parallelogram), which then loops back to 'Init'. + +G.8021-Y.1341(16)\_F8-71 + +Figure 8-71 – TST Control\_Sk behaviour + +### 8.1.13 Link trace (LT) processes + +#### 8.1.13.1 Overview + +Figure 8-72 shows the different processes involved in the link trace protocol. + +![Figure 8-72 – LT protocol overview diagram showing the flow of Link Trace (LT) messages between three network elements: MEP, MIP, and MEP.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +The diagram illustrates the flow of Link Trace (LT) messages between three network elements: MEP (Message End Point), MIP (Message Intermediate Point), and MEP. The flow is as follows: + +- Left MEP:** An external signal **MI\_LT(TA,TTL, P)** is received by the **LM Control** block. The **LM Control** block sends a signal **LTM(TA,TTL, TID, P)** to the **LTM Generation** block. The **LTM Generation** block sends a signal **D,P,DE** to the **On-demand OAM Insertion** block. The **On-demand OAM Insertion** block sends a signal **ETH\_CI** to the **MIP**. The **On-demand OAM Insertion** block also receives a signal **ETH\_CI** from the **MIP**. The **On-demand OAM Insertion** block sends a signal **D,P,DE** to the **LTM Reception** block. The **LTM Reception** block sends a signal **RI\_LTR(SA, TTL,TID,TLV)** to the **LM Control** block. The **LM Control** block sends a signal **MI\_LT\_Result(Results)** to the external environment. The **LM Control** block also receives a signal **MI\_MEP\_MAC** from the external environment. +- MIP:** The **On-demand OAM Extraction** block receives a signal **ETH\_CI** from the **Left MEP**. The **On-demand OAM Extraction** block sends a signal **D,P,DE** to the **MIP LTM Reception** block. The **MIP LTM Reception** block receives a signal **MI\_MIP\_MAC** from the external environment. The **MIP LTM Reception** block sends a signal **RI\_LTM(D,P,DE)** to the **LTM Generation** block. The **LTM Generation** block sends a signal **D,P,DE** to the **On-demand OAM Insertion** block. The **On-demand OAM Insertion** block sends a signal **ETH\_CI** to the **Right MEP**. The **On-demand OAM Insertion** block also receives a signal **ETH\_CI** from the **Right MEP**. +- Right MEP:** The **On-demand OAM Insertion** block receives a signal **ETH\_CI** from the **MIP**. The **On-demand OAM Insertion** block sends a signal **D,P,DE** to the **LTM Generation** block. The **LTM Generation** block sends a signal **D,P,DE** to the **MEP LTM Reception** block. The **MEP LTM Reception** block receives a signal **MI\_MEP\_MAC** from the external environment. The **MEP LTM Reception** block sends a signal **RI\_LTM(D,P,DE)** to the **LTM Generation** block. The **LTM Generation** block sends a signal **D,P,DE** to the **On-demand OAM Extraction** block. The **On-demand OAM Extraction** block sends a signal **ETH\_CI** to the external environment. + +Figure 8-72 – LT protocol overview diagram showing the flow of Link Trace (LT) messages between three network elements: MEP, MIP, and MEP. + +G.8021-Y.1341(12)\_F8-72 + +Figure 8-72 – LT protocol overview + +The link trace protocol is started upon receipt of an **MI\_LT(TA, TTL, P)** signal. The result of the process will be communicated back via the **MI\_LT\_Result(Results)** signal. + +The LM control will trigger the transmission of an LTM traffic unit and then wait for the LTR traffic units that are sent in reply to this LTM traffic unit. + +The LTM traffic unit is processed by MIP LTM reception processes and by MEP LTM reception processes. Depending on the DA given in the **MI\_LT(TA, TTL, P)** signal these processes may decide to trigger the transmission of an LTR traffic unit back to the source of the LTM traffic unit. + +NOTE – In the 2008 version of Recommendation ITU-T G.8013/Y.1731 the LTM traffic unit is received by an ETH-LT responder process which solely resides in a network element and acts as an alternative process for LTM MIP reception. Similarly, the trigger of sending an LTR traffic unit is decided by the ETH-LT responder. + +#### 8.1.13.2 LT control process + +Figure 8-73 shows the behaviour of the LT control process. + +![Flowchart of the LT control process. It starts with 'LT control' leading to 'Init'. 'Init' leads to 'MI_LT(TA,TTL,P)', which leads to 'LTM(TA,TTL,TID,P)', which leads to 'Set(5s,Timer)' and 'Results={}'. A loop from 'Set(5s,Timer)' leads to 'Waiting for LTR'. 'Waiting for LTR' branches to 'Timer' and 'LTR(SA,TTL,rTID,TLV)'. 'Timer' leads to 'MI_LT_Result(Results)', which leads to 'TID++'. 'LTR(SA,TTL,rTID,TLV)' leads to a decision 'rTID==TID?'. If 'No', it loops back to 'Waiting for LTR'. If 'Yes', it leads to 'Results=Results+{(SA,TTL,TLV)}', which then loops back to 'Waiting for LTR'. A small text 'G.8021-Y.1341(16)_F8-73' is at the bottom right.](d510bddda14c44163bbeee33b491a105_img.jpg) + +``` +graph TD + LT_control([LT control]) --> Init([Init]) + Init --> MI_LT["MI_LT(TA,TTL,P)"] + MI_LT --> LTM["LTM(TA,TTL,TID,P)"] + LTM --> Set["Set(5s,Timer) +Results={}"] + Set --> Waiting["Waiting for LTR"] + Waiting --> Timer["Timer"] + Waiting --> LTR["LTR(SA,TTL,rTID,TLV)"] + Timer --> MI_LT_Result["MI_LT_Result(Results)"] + MI_LT_Result --> TID_plus["TID++"] + TID_plus --> Waiting + LTR --> rTID_eq_TID{"rTID==TID?"} + rTID_eq_TID -- No --> Waiting + rTID_eq_TID -- Yes --> Results_update["Results=Results+{(SA,TTL,TLV)}"] + Results_update --> Waiting +``` + +Flowchart of the LT control process. It starts with 'LT control' leading to 'Init'. 'Init' leads to 'MI\_LT(TA,TTL,P)', which leads to 'LTM(TA,TTL,TID,P)', which leads to 'Set(5s,Timer)' and 'Results={}'. A loop from 'Set(5s,Timer)' leads to 'Waiting for LTR'. 'Waiting for LTR' branches to 'Timer' and 'LTR(SA,TTL,rTID,TLV)'. 'Timer' leads to 'MI\_LT\_Result(Results)', which leads to 'TID++'. 'LTR(SA,TTL,rTID,TLV)' leads to a decision 'rTID==TID?'. If 'No', it loops back to 'Waiting for LTR'. If 'Yes', it leads to 'Results=Results+{(SA,TTL,TLV)}', which then loops back to 'Waiting for LTR'. A small text 'G.8021-Y.1341(16)\_F8-73' is at the bottom right. + +Figure 8-73 – LT control behaviour + +After receiving the $MI\_LT(TA, TTL, P)$ input signal, the transmission of an LTM traffic unit is triggered. In the "Waiting for LTR" state, the LTM control process waits for the LTR traffic units that will be sent in response. The waiting period is five seconds. For each received LTR traffic unit the TID value in the received LTM traffic unit is compared with the one that was sent in the LTM traffic unit. If they are equal, the SA, TTL and TLV values are stored in the results. These results are communicated back using the $MI\_LT\_Results$ signal after the five second waiting period is over. + +#### 8.1.13.3 LTM generation process + +Figure 8-74 shows the behaviour of the LTM generation process. + +![Flowchart of the LTM generation process. It starts with 'LTM generation' leading to 'Waiting'. 'Waiting' leads to 'LTM(TA,TTL,TID,P)', which leads to 'OAM=LTM(TA,TTL,TID)', which leads to 'D(OAM,P(P),DE(0))'. A loop from 'D(OAM,P(P),DE(0))' leads back to 'Waiting'. A small text 'G.8021-Y.1341(16)_F8-74' is at the bottom right.](afd9ce64c136f2090b978ea5f3ef9d8d_img.jpg) + +``` +graph TD + LTM_generation([LTM generation]) --> Waiting["Waiting"] + Waiting --> LTM["LTM(TA,TTL,TID,P)"] + LTM --> OAM["OAM=LTM(TA,TTL,TID)"] + OAM --> D["D(OAM,P(P),DE(0))"] + D --> Waiting +``` + +Flowchart of the LTM generation process. It starts with 'LTM generation' leading to 'Waiting'. 'Waiting' leads to 'LTM(TA,TTL,TID,P)', which leads to 'OAM=LTM(TA,TTL,TID)', which leads to 'D(OAM,P(P),DE(0))'. A loop from 'D(OAM,P(P),DE(0))' leads back to 'Waiting'. A small text 'G.8021-Y.1341(16)\_F8-74' is at the bottom right. + +Figure 8-74 – LTM generation behaviour + +The LTM generation process generates an LTM traffic unit with the function: + +OAM=LTM(TA, TTL, TID) and the result is shown in Figure 8-75. + +NOTE – In the generated LTM traffic unit, in the OAM (MEP) insertion process, the SA will be assigned the local MAC address, and the MEL will be assigned by MI\_MEL. The value of the multicast class 2 DA is 01-80-C2-00-00-3y, where y is equal to {MI\_MEL + 8} as defined in clause 10.1 of [ITU-T G.8013]. The usage of flags is specified in clause 9.5.2 of [ITU-T G.8013]. + +| 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------|---|---|---|---|---|---|---|----------------------|---|---|---|---|---|---|---|---------------------------|-------------|---|---|---|-------------------|---|---|-------------------|---|---|---|---|---|---|---|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DA = 01-80-C2-00-00-3y where y is changed to MI_MEL by the OAM insertion process. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SA = Undefined | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EtherType = 89-02 | | | | | | | | | | | | | | | | MEL = Unedef | Version = 0 | | | | OpCode = 05 (LTM) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Flags | | | | | | | | TLV Offset = 17 | | | | | | | | Transaction ID = LTM(TID) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Transaction ID continued | | | | | | | | | | | | | | | | TTL = LTM(TTL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Originating MAC = MI_MEP_MAC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | Target MAC = LTM(TA) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | [TLV starts here] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | End TLV = 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +G.8021-Y.1341(16)\_F8-75 + +Figure 8-75 – LTM traffic unit + +#### 8.1.13.4 MIP LTM reception process + +Figure 8-76 shows the behaviour of the MIP LTM reception process. + +![Flowchart of the MIP LTM reception process. It starts with 'MIP LTM reception' leading to 'Init', then 'D(D),P(P),DE(DE)'. A decision 'TTL(D)>0' follows. If 'No', it loops back to 'Init'. If 'Yes', it checks 'TMAC(D)=MI_MIP_MAC || Forward(TMAG(D))'. If 'No', it loops back to 'Init'. If 'Yes', it proceeds to 'TTL(D)--', then 'RI_LTM(D,P,DE)'. Another decision 'TMAC(D)!=MI_MIP_MAC && TTL>0' follows. If 'No', it loops back to 'Init'. If 'Yes', it proceeds to 'D(D),P(P),DE(DE)' and then loops back to 'Init'.](4224f170b677d60f6f86ce95d8dc725a_img.jpg) + +``` + +graph TD + Start([MIP LTM reception]) --> Init([Init]) + Init --> D1[/D(D),P(P),DE(DE)/] + D1 --> TTLgt0{TTL(D)>0} + TTLgt0 -- No --> Init + TTLgt0 -- Yes --> TMACeq{TMAC(D)=MI_MIP_MAC +|| Forward(TMAG(D))} + TMACeq -- No --> Init + TMACeq -- Yes --> TTLdec[TTL(D)--] + TTLdec --> RI_LTM[/RI_LTM(D,P,DE)/] + RI_LTM --> TMACneq{TMAC(D)!=MI_MIP_MAC +&& TTL>0} + TMACneq -- No --> Init + TMACneq -- Yes --> D2[/D(D),P(P),DE(DE)/] + D2 --> Init + +``` + +Flowchart of the MIP LTM reception process. It starts with 'MIP LTM reception' leading to 'Init', then 'D(D),P(P),DE(DE)'. A decision 'TTL(D)>0' follows. If 'No', it loops back to 'Init'. If 'Yes', it checks 'TMAC(D)=MI\_MIP\_MAC || Forward(TMAG(D))'. If 'No', it loops back to 'Init'. If 'Yes', it proceeds to 'TTL(D)--', then 'RI\_LTM(D,P,DE)'. Another decision 'TMAC(D)!=MI\_MIP\_MAC && TTL>0' follows. If 'No', it loops back to 'Init'. If 'Yes', it proceeds to 'D(D),P(P),DE(DE)' and then loops back to 'Init'. + +G.8021-Y.1341(16)\_F8-76 + +Figure 8-76 – MIP LTM reception behaviour + +Upon receipt of an LTM traffic unit, first the TTL is checked, only LTM traffic units with a TTL>0 are processed. Thereafter, the target MAC (TMAC) of the LTM traffic unit is checked. + +There are two reasons to send back an LTR traffic unit. The first is if the TMAC in the LTM traffic unit is the MAC address of the MIP itself. + +The second reason is summarized in Figure 8-65 as Forward(TM MAC(D)). This function returns true if: + +- the network element that the MIP LTM reception process resides in would forward a normal data traffic unit with its DA equal to the TMAC to a single port (forwarding port), and +- the MIP LTM reception process resides in the egress port which equals to the "forwarding port" (LTM in egress port), or the MIP LTM reception process resides in the ingress port which does not equal to the "forwarding port" (LTM in ingress port). + +Furthermore, after triggering the transmission of an LTR traffic unit, the LTM traffic unit is forwarded if the TMAC was not the MAC of the MIP and if the TTL>0. + +#### 8.1.13.5 MEP LTM reception process + +Figure 8-77 shows the behaviour of the MEP LTM reception process. + +![Flowchart of MEP LTM reception behaviour](beefc2239bc009e7b97963ac4f166db1_img.jpg) + +``` +graph TD; Start([MEP LTM reception]) --> Init([Init]); Init --> D["D(D),P(P),DE(DE)"]; D --> TTL{ "TTL(D)>0" }; TTL -- No --> Init; TTL -- Yes --> TMAC{ "TMAC(D)=MI_MEP_MAC || Forward(TM MAC(D))" }; TMAC -- No --> Init; TMAC -- Yes --> TTLDec["TTL(D)--"]; TTLDec --> RI["RI_LTM(D,P,DE)"]; RI --> Init; +``` + +The flowchart illustrates the MEP LTM reception process. It begins with 'MEP LTM reception', followed by 'Init', and then a process block 'D(D),P(P),DE(DE)'. A decision diamond 'TTL(D)>0' follows. If 'No', it loops back to 'Init'. If 'Yes', it proceeds to another decision diamond 'TMAC(D)=MI\_MEP\_MAC || Forward(TM MAC(D))'. If 'No', it loops back to 'Init'. If 'Yes', it proceeds to 'TTL(D)--', then 'RI\_LTM(D,P,DE)', and finally loops back to 'Init'. + +G.8021-Y.1341(16)\_F8-77 + +Flowchart of MEP LTM reception behaviour + +**Figure 8-77 – MEP LTM reception behaviour** + +Upon receipt of an LTM traffic unit first the TTL is checked, only LTM traffic units with a TTL>0 are processed. Thereafter the Target MAC (TMAC) of the LTM traffic unit is checked. Conditions to send back an LTR traffic unit are similar with ones for MIP LTM reception process. The first is if the TMAC in the LTM traffic unit is the MAC address of the MEP itself. The second is summarized in Figure 8-77 as Forward(TM MAC(D)). This function returns true if: + +- the network element the MEP LTM reception process resides in would forward a normal data traffic unit with its DA equal to the TMAC to a single port (forwarding port), and +- the MEP LTM reception process resides in the egress port which equals to the "forwarding port" (LTM in egress port), or the MEP LTM reception process resides in the ingress port which does not equal to the "forwarding port" (LTM in ingress port). + +Note that the LTM traffic unit is not forwarded anymore regardless of the value of TMAC. + +#### 8.1.13.6 LTR generation process + +Figure 8-78 shows the behaviour of the LTR generation process. + +![Flowchart of the LTR generation process. The steps are: LTR generation (oval), Waiting (oval), RI_LTM(D,P,DE) (parallelogram), DA(D)=Orig MAC(D) and OPC(D)=04 (rectangle), Wait_Time=Random(0..1s) and Set(Wait_Time,Timer) (rectangle), Waiting Timer (oval), Timer (parallelogram), and D(D),P(P),DE(DE) (parallelogram). A feedback loop connects the final output back to the start of the Waiting step.](4a2b39fa33747a6553031cfe1e0947fa_img.jpg) + +``` +graph TD; A([LTR generation]) --> B([Waiting]); B --> C[/RI_LTM(D,P,DE)/]; C --> D["DA(D)=Orig MAC(D) +OPC(D)=04"]; D --> E["Wait_Time=Random(0..1s) +Set(Wait_Time,Timer)"]; E --> F([Waiting Timer]); F --> G[/Timer/]; G --> H[/D(D),P(P),DE(DE)/]; H --> B; +``` + +G.8021-Y.1341(16)\_F8-78 + +Flowchart of the LTR generation process. The steps are: LTR generation (oval), Waiting (oval), RI\_LTM(D,P,DE) (parallelogram), DA(D)=Orig MAC(D) and OPC(D)=04 (rectangle), Wait\_Time=Random(0..1s) and Set(Wait\_Time,Timer) (rectangle), Waiting Timer (oval), Timer (parallelogram), and D(D),P(P),DE(DE) (parallelogram). A feedback loop connects the final output back to the start of the Waiting step. + +**Figure 8-78 – LTR generation behaviour** + +The LTR generation process generates the LTR traffic unit to be sent back, based on the LTM traffic unit. The DA of the LTR traffic unit is the originating MAC (Orig MAC) as contained in the LTM traffic unit. The OpCode is the LTR OpCode. The resulting LTR traffic unit is shown in Figure 8-79. The SA and MEL will be overwritten by the OAM insertion process. The LTR traffic unit is sent back after a random delay between 0 and 1 second. The usage of flags is specified in clause 9.6.2 of [ITU-T G.8013]. + +The resulting frame is shown in Figure 8-79. + +NOTE – In the generated LTR, in the OAM (MEP) insertion process, the SA will be overwritten with the local MAC address, and the MEL will be overwritten with MI\_MEL. + +![](e8f5117fb031f413a836525061addd61_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------|--------------------------|---|---|---|----------------|---|---|---|--------------------------------------------|---|---|---|-------------|---|---|---|----------------------------------|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | DA = orig MAC(RI_LTM(D)) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 | SA = undefined | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 13 | EtherType = 89-02 | | | | | | | | MEL = undef | | | | Version = 0 | | | | OpCode = 04 (LTR) | | | | | | | | | | | | | | | | +| 17 | Flags | | | | TLV Offset = 6 | | | | Transaction ID = transaction ID(RI_LTM(D)) | | | | | | | | | | | | | | | | | | | | | | | | +| 21 | Transaction ID continued | | | | | | | | TTL = TTL(RI_LTM(D)) | | | | | | | | Relay action (reserved for IEEE) | | | | | | | | | | | | | | | | +| : | [TLV starts here] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| last | End TLV = 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +G.8021-Y.1341(12)\_F8-79 + +**Figure 8-79 – LTR traffic unit** + +#### **8.1.13.7 LTR reception process** + +Figure 8-80 shows the behaviour of the LTR reception process. + +![Flowchart of the LTR reception process. It starts with 'LTR reception', followed by 'Waiting', then 'D(D),P(P),DE(DE)'. A decision diamond asks 'DA(D)=MI_MEP_MAC'. If 'No', it loops back to 'Waiting'. If 'Yes', it proceeds to a box with 'SA=SA(D)', 'TTL=TTL(D)', 'TID=TID(D)', 'TLV=TLV(D)', then to 'LTR(SA,TTL,TID, TLV)', and finally loops back to 'Waiting'.](8f8caebe58364416a2eda21039d8c7bf_img.jpg) + +``` + +graph TD + A([LTR reception]) --> B([Waiting]) + B --> C[/D(D),P(P),DE(DE)/] + C --> D{DA(D)=MI_MEP_MAC} + D -- No --> B + D -- Yes --> E["SA=SA(D) +TTL=TTL(D) +TID=TID(D) +TLV=TLV(D)"] + E --> F[/LTR(SA,TTL,TID, TLV)/] + F --> B + +``` + +G.8021-Y.1341(16)\_F8-80 + +Flowchart of the LTR reception process. It starts with 'LTR reception', followed by 'Waiting', then 'D(D),P(P),DE(DE)'. A decision diamond asks 'DA(D)=MI\_MEP\_MAC'. If 'No', it loops back to 'Waiting'. If 'Yes', it proceeds to a box with 'SA=SA(D)', 'TTL=TTL(D)', 'TID=TID(D)', 'TLV=TLV(D)', then to 'LTR(SA,TTL,TID, TLV)', and finally loops back to 'Waiting'. + +**Figure 8-80 – LTR reception behaviour** + +The LTR reception process checks the DA of the received LTR traffic unit and passes the SA, TTL, TID and TLV fields from the LTR traffic unit to the LT control process. + +### **8.1.14 Single-ended synthetic loss measurement (SL) processes** + +#### **8.1.14.1 Overview** + +Figure 8-81 shows the different processes inside MEPs and MIPs that are involved in the on-demand single-ended synthetic loss measurement protocol. + +NOTE – In previous versions of this Recommendation, single-ended synthetic loss measurement was known as synthetic loss measurement. With regard to those definitions, refer to [ITU-T G.8013]. + +The MEP on-demand OAM insertion process is defined in clause 9.4.1.1, the MEP OAM on-demand extraction process in clause 9.4.1.2, the MIP OAM extraction process in clause 9.4.2.1, and the MIP OAM insertion process in clause 9.4.2.2. In summary, they insert and extract ETH\_CI OAM signals into and from the stream of ETH\_CI\_D traffic units and the complementing P and D signals going through an MEP and MIP; the extraction is based on MEL and OpCode. Furthermore, the insertion process inserts the correct MEL and SA values into the OAM traffic units. + +![Figure 8-81: Overview of processes involved with an on-demand single-ended synthetic loss measurement protocol. The diagram shows three main components: a transmitting MEP, a middle MIP, and a receiving MEP. The transmitting MEP contains an 'On-demand OAM Insertion' block, an 'SLM Generation' block, an 'On-demand SL Control' block, and an 'SLR Reception' block. The 'On-demand SL Control' block receives inputs like MI_SL_Start, MI_SL_Intermediate_Request, MI_SL_Terminate, MI_MEP_ID, and MI_SL_Result, and sends control signals to the 'On-demand OAM Insertion' and 'SLM Generation' blocks. The 'SLM Generation' block sends SLM traffic units (containing DA, P, MEP_ID, Test_ID, TxFCI, TLV) to the 'On-demand OAM Insertion' block. The 'On-demand OAM Insertion' block inserts OAM signals into the ETH_CI stream. The MIP contains 'On-demand OAM Extraction' and 'On-demand OAM Insertion' blocks that pass through the ETH_CI stream. The receiving MEP contains an 'On-demand OAM Extraction' block, an 'SLM Reception' block, an 'SLR Generation' block, and an 'On-demand OAM Insertion' block. The 'On-demand OAM Extraction' block receives OAM signals from the MIP and sends them to the 'SLM Reception' block. The 'SLM Reception' block sends RI_SLM signals (containing OAM, P, DE, TxFCb) to the 'SLR Generation' block. The 'SLR Generation' block sends SLR traffic units (containing D, P, DE) to the 'On-demand OAM Insertion' block. The 'On-demand OAM Insertion' block inserts OAM signals into the ETH_CI stream. External inputs include MI_MEP_MAC and MI_MEP_ID. The diagram is labeled G.8021-Y.1341(16)_F8-81.](778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg) + +Figure 8-81: Overview of processes involved with an on-demand single-ended synthetic loss measurement protocol. The diagram shows three main components: a transmitting MEP, a middle MIP, and a receiving MEP. The transmitting MEP contains an 'On-demand OAM Insertion' block, an 'SLM Generation' block, an 'On-demand SL Control' block, and an 'SLR Reception' block. The 'On-demand SL Control' block receives inputs like MI\_SL\_Start, MI\_SL\_Intermediate\_Request, MI\_SL\_Terminate, MI\_MEP\_ID, and MI\_SL\_Result, and sends control signals to the 'On-demand OAM Insertion' and 'SLM Generation' blocks. The 'SLM Generation' block sends SLM traffic units (containing DA, P, MEP\_ID, Test\_ID, TxFCI, TLV) to the 'On-demand OAM Insertion' block. The 'On-demand OAM Insertion' block inserts OAM signals into the ETH\_CI stream. The MIP contains 'On-demand OAM Extraction' and 'On-demand OAM Insertion' blocks that pass through the ETH\_CI stream. The receiving MEP contains an 'On-demand OAM Extraction' block, an 'SLM Reception' block, an 'SLR Generation' block, and an 'On-demand OAM Insertion' block. The 'On-demand OAM Extraction' block receives OAM signals from the MIP and sends them to the 'SLM Reception' block. The 'SLM Reception' block sends RI\_SLM signals (containing OAM, P, DE, TxFCb) to the 'SLR Generation' block. The 'SLR Generation' block sends SLR traffic units (containing D, P, DE) to the 'On-demand OAM Insertion' block. The 'On-demand OAM Insertion' block inserts OAM signals into the ETH\_CI stream. External inputs include MI\_MEP\_MAC and MI\_MEP\_ID. The diagram is labeled G.8021-Y.1341(16)\_F8-81. + +**Figure 8-81 – Overview of processes involved with an on-demand single-ended synthetic loss measurement protocol** + +The SL protocol is controlled by the on-demand SL control process. + +The on-demand SL control process is activated upon receipt of the MI\_SL\_Start(DA,P,Test\_ID,Length,Period) signal and remains activated until the MI\_SL\_Terminate signal is received. The measured synthetic loss values are output via the MI\_SL\_Result(N\_TF,N\_LF,F\_TF,F\_LF) signal when the process is terminated by the MI\_SL\_Terminate signal or when an intermediate result is requested via the MI\_SL\_Intermediate\_Request signal. + +The SLM generation process generates SLM traffic units that pass through MIPs transparently, but are received and processed by SLM reception processes in MEPs. The SLR generation process may generate an SLR traffic unit in response. This SLR traffic unit also passes transparently through MIPs, but is received and processed by SLR reception processes in MEPs. + +Figure 8-82 shows the different processes inside MEPs and MIPs that are involved in the proactive single-ended synthetic loss 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, the MIP OAM extraction process in clause 9.4.2.1, and the MIP OAM insertion process in clause 9.4.2.2. In summary, they insert and extract ETH\_CI OAM signals into and from the stream of ETH\_CI\_D traffic units and the complementing P and D signals going through an MEP and MIP; the extraction is based on MEL and OpCode. Furthermore, the insertion process inserts the correct MEL and SA values into the OAM traffic units. + +![Figure 8-82: Overview of processes involved with a proactive single-ended synthetic loss measurement protocol. The diagram shows three main components: a transmitting MEP, a MIP, and a receiving MEP. The transmitting MEP includes a 'Proactive OAM Insertion' block, an 'SLM Generation' block, a 'Proactive SL Control' block, and an 'SLR Reception' block. The 'Proactive SL Control' block receives inputs like MI_SL_Enable, MI_SL_MAC_DA, MI_SL_Test_ID, MI_SL_Length, MI_SL_Period, MI_SL_Pri, MI_MEP_ID, and RI_SL_Result(N_TF, N_LF, F_TF, F_LF). It outputs SLM (DA, P, MEP_ID, Test_ID, TxFCI, TLV) to the 'SLM Generation' block, which then feeds into the 'Proactive OAM Insertion' block. The 'Proactive OAM Insertion' block outputs ETH_CI, D, P, DE signals. The MIP includes an 'On-demand OAM Extraction' block that receives ETH_CI, D, P, DE signals and outputs ETH_CI. The receiving MEP includes a 'Proactive OAM Extraction' block, an 'SLM Reception' block, an 'SLR Generation' block, and a 'Proactive OAM Insertion' block. The 'Proactive OAM Extraction' block receives ETH_CI, D, P, DE signals and outputs ETH_CI. The 'SLM Reception' block receives MI_MEP_MAC and RI_SLM(OAM, P, DE, TxFCb) signals. The 'SLR Generation' block receives MI_MEP_ID and D, P, DE signals and outputs ETH_CI, D, P, DE signals. The 'Proactive OAM Insertion' block receives ETH_CI, D, P, DE signals and outputs ETH_CI.](f4fdce3ce1c0fd291f31813f83d0d0d3_img.jpg) + +G.8021-Y.1341(16)\_F8-82 + +Figure 8-82: Overview of processes involved with a proactive single-ended synthetic loss measurement protocol. The diagram shows three main components: a transmitting MEP, a MIP, and a receiving MEP. The transmitting MEP includes a 'Proactive OAM Insertion' block, an 'SLM Generation' block, a 'Proactive SL Control' block, and an 'SLR Reception' block. The 'Proactive SL Control' block receives inputs like MI\_SL\_Enable, MI\_SL\_MAC\_DA, MI\_SL\_Test\_ID, MI\_SL\_Length, MI\_SL\_Period, MI\_SL\_Pri, MI\_MEP\_ID, and RI\_SL\_Result(N\_TF, N\_LF, F\_TF, F\_LF). It outputs SLM (DA, P, MEP\_ID, Test\_ID, TxFCI, TLV) to the 'SLM Generation' block, which then feeds into the 'Proactive OAM Insertion' block. The 'Proactive OAM Insertion' block outputs ETH\_CI, D, P, DE signals. The MIP includes an 'On-demand OAM Extraction' block that receives ETH\_CI, D, P, DE signals and outputs ETH\_CI. The receiving MEP includes a 'Proactive OAM Extraction' block, an 'SLM Reception' block, an 'SLR Generation' block, and a 'Proactive OAM Insertion' block. The 'Proactive OAM Extraction' block receives ETH\_CI, D, P, DE signals and outputs ETH\_CI. The 'SLM Reception' block receives MI\_MEP\_MAC and RI\_SLM(OAM, P, DE, TxFCb) signals. The 'SLR Generation' block receives MI\_MEP\_ID and D, P, DE signals and outputs ETH\_CI, D, P, DE signals. The 'Proactive OAM Insertion' block receives ETH\_CI, D, P, DE signals and outputs ETH\_CI. + +**Figure 8-82 – Overview of processes involved with a proactive single-ended synthetic loss measurement protocol** + +The SL protocol is controlled by the proactive SL control processes. + +The proactive SL control process is activated upon receipt of the MI\_SL\_Enable signal and remains activated until the signal is deactivated. The measured results are output every 1 s using the RI\_SL\_Result (N\_TF, N\_LF, F\_TF, F\_LF) signal. + +#### 8.1.14.2 SL control process + +The behaviour of the on-demand SL control process is defined in Figure 8-83. There are multiple instances of the on-demand SL control process, each handling an independent stream of SLM frames. + +![Flowchart of the on-demand SL control process. The process starts with 'On-demand SL control' leading to 'Init'. 'Init' leads to 'MI_SL_Start(DA, P, Test ID, Length, Period)'. This leads to a block setting 'Set (0, TxTimer)' and initializing counters 'N_TF = N_LF = F_TF = F_LF = 0' and 'saved = false'. The process then enters the 'Running' state. From 'Running', five parallel paths emerge: 1) 'TxTimer' leads to 'TLV = Generate(Length)' and 'TxFCf++', then 'SLM(DA,P,MEP_ID,Test_ID,TxFCf,TLV)', then 'Set(Period, TxTimer)'. 2) 'RI_SLR(rMEP_ID, rTest_ID, TxFcf, TxFCb)' leads to a 'saved' decision diamond. If 'N' (No), it loops back to 'Running'. If 'Y' (Yes), it updates counters: 'N_TF += |TxFcb-TxFcb_svd|', 'N_LF += |TxFcb-TxFcb_svd| - |RxFcf-RxFcf_svd|', 'F_TF += |TxFcf-TxFcf_svd|', 'F_LF += |TxFcf-TxFcf_svd| - |TxFcb-TxFcb_svd|', then updates saved values: 'TxFcf_svd = TxFcf', 'TxFcb_svd = TxFcb', 'RxFcf_svd = RxFcf', 'RxFcb_svd = RxFcb', 'RxFcf++', and 'saved = true', before looping back to 'Running'. 3) 'MI_SL_Intermediate_Request' leads to 'MI_SL_Result(N_TF, N_LF, F_TF, F_LF)'. 4) 'MI_SL_Terminate' leads to 'Set (5s, TimeoutTimer)' and 'Reset (TxTimer)'. 5) 'TimeoutTimer' leads to 'MI_SL_Result(N_TF, N_LF, F_TF, F_LF)'. All five paths eventually loop back to the 'Running' state. A label 'G.8021-Y.1341(16)_F8-83' is in the bottom right.](90183a52275501da5a0fd5c63d837009_img.jpg) + +Flowchart of the on-demand SL control process. The process starts with 'On-demand SL control' leading to 'Init'. 'Init' leads to 'MI\_SL\_Start(DA, P, Test ID, Length, Period)'. This leads to a block setting 'Set (0, TxTimer)' and initializing counters 'N\_TF = N\_LF = F\_TF = F\_LF = 0' and 'saved = false'. The process then enters the 'Running' state. From 'Running', five parallel paths emerge: 1) 'TxTimer' leads to 'TLV = Generate(Length)' and 'TxFCf++', then 'SLM(DA,P,MEP\_ID,Test\_ID,TxFCf,TLV)', then 'Set(Period, TxTimer)'. 2) 'RI\_SLR(rMEP\_ID, rTest\_ID, TxFcf, TxFCb)' leads to a 'saved' decision diamond. If 'N' (No), it loops back to 'Running'. If 'Y' (Yes), it updates counters: 'N\_TF += |TxFcb-TxFcb\_svd|', 'N\_LF += |TxFcb-TxFcb\_svd| - |RxFcf-RxFcf\_svd|', 'F\_TF += |TxFcf-TxFcf\_svd|', 'F\_LF += |TxFcf-TxFcf\_svd| - |TxFcb-TxFcb\_svd|', then updates saved values: 'TxFcf\_svd = TxFcf', 'TxFcb\_svd = TxFcb', 'RxFcf\_svd = RxFcf', 'RxFcb\_svd = RxFcb', 'RxFcf++', and 'saved = true', before looping back to 'Running'. 3) 'MI\_SL\_Intermediate\_Request' leads to 'MI\_SL\_Result(N\_TF, N\_LF, F\_TF, F\_LF)'. 4) 'MI\_SL\_Terminate' leads to 'Set (5s, TimeoutTimer)' and 'Reset (TxTimer)'. 5) 'TimeoutTimer' leads to 'MI\_SL\_Result(N\_TF, N\_LF, F\_TF, F\_LF)'. All five paths eventually loop back to the 'Running' state. A label 'G.8021-Y.1341(16)\_F8-83' is in the bottom right. + +G.8021-Y.1341(16)\_F8-83 + +Figure 8-83 – On-demand SL control behaviour + +Upon receipt of the $MI\_SL\_Start(DA,P,Test\_ID,Length,Period)$ , the SL protocol is started. Every designated period the generation of an SLM frame is triggered (using the $SLM(DA,P,MEP\_ID,Test\_ID,TxFCf,TLV)$ signal), until the $MI\_SL\_Terminate$ signal is received. The $MEP\_ID$ is the $MI\_MEP\_ID$ of the MEP itself. The TLV field of the SLM frames is determined by the $Generate(Length)$ function. $Generate(Length)$ generates a data TLV with length "Length" of an arbitrary bit pattern, as described in clause 8.1.8.2. If the length is 0, the TLV is set to NULL. + +Upon receipt of an SLR traffic unit, the received counter values are used to count the near-end and far-end transmitted and lost synthetic frames. This result is reported using the $MI\_SL\_Result(N\_TF,N\_LF,F\_TF,F\_LF)$ signal after the receipt of the $MI\_SL\_Terminate$ signal or of the $MI\_SL\_Intermediate\_Request$ signal. + +The behaviour of the proactive SL Control process is defined in Figure 8-84. There are multiple instances of the proactive SL Control process, each handling an independent stream of SLM frames. + +![Flowchart of Proactive SL control behaviour. The process starts with 'Proactive SL control' leading to 'Init', then 'MI_SL_Enable'. It then sets initial values for TxTimer, N_TF, N_LF, F_TF, F_LF, and saved. It sets ReportTimer to 1s and enters 'Running' state. From 'Running', it branches into four paths: 'TxTimer' (generating SLM frames), 'RI_SLR' (processing received frames), 'ReportTimer' (generating RI_SL_Result), and '!MI_SL_Enable' (stopping the process). All paths converge to a common loop back to the 'Running' state.](401f020d9ab5904f584424eabb596d2c_img.jpg) + +``` + +graph TD + Start([Proactive SL control]) --> Init([Init]) + Init --> MI_SL_Enable[/MI_SL_Enable/] + MI_SL_Enable --> InitValues["Set (0, TxTimer) +N_TF = N_LF = F_TF = F_LF = 0 +saved = false"] + InitValues --> SetReportTimer1["Set (1s, ReportTimer)"] + SetReportTimer1 --> Running([Running]) + Running --> TxTimer[/TxTimer/] + Running --> RI_SLR[/RI_SLR (rMEP_ID, rTest_ID, TxFCf, TxFCb)/] + Running --> ReportTimer[/ReportTimer/] + Running --> MI_SL_Enable_Off[/!MI_SL_Enable/] + + TxTimer --> GenerateTLV["TLV = Generate (MI_SL_Length) +TxFCI++"] + GenerateTLV --> SLM["SLM (MI_SL_MAC_DA, MI_SL_Pri, MI_SL_MEP_ID, MI_SL_Test_ID, TxFCI, TLV)"] + SLM --> SetTxPeriod["Set (MI_SL_Period, TxTimer)"] + + RI_SLR --> savedDecision{saved} + savedDecision -- N --> CalcLoss["N_TF += |TxFCb - TxFCb_svd| +N_LF += |TxFCb - TxFCb_svd| - |RxFCI - RxFCI_svd| +F_TF += |TxFCf - TxFCf_svd| +F_LF += |TxFCf - TxFCf_svd| - |TxFCb - TxFCb_svd|"] + savedDecision -- Y --> UpdateSvd["TxFCf_svd = TxFCf +TxFCb_svd = TxFCb +RxFCI_svd = RxFCI +RxFCI++ +saved = true"] + + ReportTimer --> RI_SL_Result[/RI_SL_Result (N_TF, N_LF, F_TF, F_LF)/] + RI_SL_Result --> ResetCounters["N_TF = 0 +N_LF = 0 +F_TF = 0 +F_LF = 0"] + ResetCounters --> SetReportTimer2["Set (1s, ReportTimer)"] + + MI_SL_Enable_Off --> Running + + CalcLoss --> UpdateSvd + UpdateSvd --> Running + SetTxPeriod --> Running + SetReportTimer2 --> Running + +``` + +Flowchart of Proactive SL control behaviour. The process starts with 'Proactive SL control' leading to 'Init', then 'MI\_SL\_Enable'. It then sets initial values for TxTimer, N\_TF, N\_LF, F\_TF, F\_LF, and saved. It sets ReportTimer to 1s and enters 'Running' state. From 'Running', it branches into four paths: 'TxTimer' (generating SLM frames), 'RI\_SLR' (processing received frames), 'ReportTimer' (generating RI\_SL\_Result), and '!MI\_SL\_Enable' (stopping the process). All paths converge to a common loop back to the 'Running' state. + +G.8021-Y.1341(16)\_F8-84 + +**Figure 8-84 – Proactive SL control behaviour** + +Upon receipt of the MI\_SL\_Enable, the SL protocol is started. Every designated MI\_SL\_Period the generation of an SLM frame is triggered (using the SLM(MI\_SL\_MAC\_DA, MI\_SL\_Pri, MI\_MEP\_ID, MI\_SL\_Test\_ID, TxFCI, TLV) signal). The TLV field of the SLM frames is determined by the Generate(MI\_SL\_Length) function. Generate(MI\_SL\_Length) generates a data TLV with MI\_SL\_Length of an arbitrary bit pattern, as described in clause 8.1.8.2. If the MI\_SL\_Length is 0, the TLV is set to NULL. + +Upon receipt of an SLR traffic unit, the received counter values are used to count the near-end and far-end transmitted and lost synthetic frames. The calculation is performed every 1 s and the RI\_SL\_Result(N\_TF, N\_LF, F\_TF, N\_LF) signal is generated. + +#### 8.1.14.3 SLM generation process + +The behaviour of the SLM generation process is defined in Figure 8-85. + +![Flowchart of SLM generation process. The steps are: SLM generation -> Waiting -> SLM(DA,P,MEP_ID, Test_ID,TxFCl,TLV) -> OAM = SLM(DA,P,MEP_ID, Test_ID,TxFCl,TLV) -> D(OAM,P(P), DE(0)). A feedback loop connects the final step back to the Waiting step.](8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg) + +``` + +graph TD + A([SLM generation]) --> B([Waiting]) + B --> C[/SLM(DA,P,MEP_ID, Test_ID,TxFCl,TLV)/] + C --> D[OAM = SLM(DA,P,MEP_ID, Test_ID,TxFCl,TLV)] + D --> E[/D(OAM,P(P), DE(0))/] + E --> B + +``` + +G.8021-Y.1341(16)\_F8-85 + +Flowchart of SLM generation process. The steps are: SLM generation -> Waiting -> SLM(DA,P,MEP\_ID, Test\_ID,TxFCl,TLV) -> OAM = SLM(DA,P,MEP\_ID, Test\_ID,TxFCl,TLV) -> D(OAM,P(P), DE(0)). A feedback loop connects the final step back to the Waiting step. + +Figure 8-85 – SLM generation behaviour + +Upon receiving the SLM(DA,P,MEP\_ID,Test\_ID,TxFCl,TLV), a single SLM traffic unit is generated together with the complementing P and DE signals. The DA, Source\_MEP\_ID, Test\_ID and TxFCf of the generated traffic unit are determined by the DA, MEP\_ID, Test\_ID and TxFCf respectively in the SLM(DA,P,MEP\_ID,Test\_ID,TxFCl,TLV) signal. If not NULL, the specified TLV is appended to the traffic unit as shown in Figure 8-86. + +The P signal value is defined by SLM(P). The DE signal is set to 0. + +| | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------|-----------------------------------|---|---|---|---|---|---|---|-----------------|---|---|---|---|---|---|---|--------------------------------|-----------|---|---|---|-----------------|---|---|---|---|---|---|---|---|-------------|---|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | DA=SLM(DA) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | | | | | | SA=Undefined | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 13 | EtherType=89-02 | | | | | | | | | | | | | | | | MEL=Undef | Version=0 | | | | OpCode=55 (SLM) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 17 | Flags=0 | | | | | | | | TLV Offset = 16 | | | | | | | | Source_MEP_ID = SLM(MI_MEP_ID) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 21 | 0 (Reserved for Responder_MEP_ID) | | | | | | | | | | | | | | | | Test_ID = SLM(Test_ID) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 25 | Test_ID Continued | | | | | | | | | | | | | | | | TxFCf = SLM(TxFCl) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 29 | TxFCf Continued | | | | | | | | | | | | | | | | Reserved for TxFCb | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 33 | Reserved Continued | | | | | | | | | | | | | | | | TLV = SLM(TLV) if exists | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 37 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 41 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 45 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| : | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| last | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | End TLV (0) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +Figure 8-86 – SLM traffic unit + +#### 8.1.14.4 SLM reception process + +The SLM reception process processes the received SLM traffic units and the complementing P and DE signals. The behaviour is defined in Figure 8-87. + +![Flowchart of the SLM reception process. The process starts with 'SLM reception', followed by 'Waiting', then a parallelogram for input 'D(OAM), P(P), DE(DE)'. A decision diamond checks if 'DA(OAM)=MI_MEP_MAC or DA(OAM)=MC Class 1'. If 'Y' (Yes), it proceeds to a rectangle with 'RxFCI(MEP_ID(OAM), Test_ID(OAM))++' and 'TxFCb=RxFCI(MEP_ID(OAM), Test_ID(OAM))'. If 'N' (No), it loops back to the 'Waiting' state. The final step is a chevron for output 'RI_SLM(OAM,P,DE, TxFCb)'. A small label 'G.8021-Y.1341(16)_F8-87' is at the bottom right.](abeba89144744fac6a1571aa9f94889e_img.jpg) + +``` +graph TD; A([SLM reception]) --> B([Waiting]); B --> C[/D(OAM), P(P), DE(DE)/]; C --> D{DA(OAM)=MI_MEP_MAC or DA(OAM)=MC Class 1}; D -- N --> B; D -- Y --> E["RxFCI(MEP_ID(OAM), Test_ID(OAM))++ +TxFCb=RxFCI(MEP_ID(OAM), Test_ID(OAM))"]; E --> F[/RI_SLM(OAM,P,DE, TxFCb)/]; F --> B; +``` + +G.8021-Y.1341(16)\_F8-87 + +Flowchart of the SLM reception process. The process starts with 'SLM reception', followed by 'Waiting', then a parallelogram for input 'D(OAM), P(P), DE(DE)'. A decision diamond checks if 'DA(OAM)=MI\_MEP\_MAC or DA(OAM)=MC Class 1'. If 'Y' (Yes), it proceeds to a rectangle with 'RxFCI(MEP\_ID(OAM), Test\_ID(OAM))++' and 'TxFCb=RxFCI(MEP\_ID(OAM), Test\_ID(OAM))'. If 'N' (No), it loops back to the 'Waiting' state. The final step is a chevron for output 'RI\_SLM(OAM,P,DE, TxFCb)'. A small label 'G.8021-Y.1341(16)\_F8-87' is at the bottom right. + +**Figure 8-87 – SLM reception behaviour** + +First the DA is checked, it should be the local MAC address or a multicast class 1 address, otherwise the frame is ignored. + +If the DA is the local MAC or a multicast class 1 address, the MEP\_ID and the Test\_ID fields are extracted from the traffic unit. The local received counter RxFCI maintained per MEP\_ID and Test\_ID values, is incremented. The received OAM information, P and DE signals, as well as the local TxFCb value are forwarded as remote information to the SLR generation process using the RI\_SLM(OAM,P,DE, TxFCb) signal. + +NOTE – The SLM reception process allocates and maintains local resources for the counter RxFCI per MEP\_ID and Test\_ID. To facilitate the automatic release of local resources, a timer for monitoring no receipt of SLM can be utilized. The SLM reception process must ensure that there is no discontinuity in RxFCI for a given MEP ID and Test ID for a given interval (e.g., 5 minutes) after the last received SLM for that MEP ID and Test ID. A detailed mechanism for the release is out of the scope of this Recommendation. + +#### 8.1.14.5 SLR generation process + +The SLR generation process generates an SLR traffic unit and its complementing P and DE signals. The behaviour is defined in Figure 8-88. + +![Flowchart of SLR generation behaviour](b3d488012fdceacab867cf24c5efef05_img.jpg) + +``` +graph TD; A([SLR generation]) --> B([Waiting]); B --> C[/RI_SLM (OAM,P,DE TxFCb)/]; C --> D["DA(OAM) = SA(OAM) +SA(OAM) = Undefined +OPC(OAM) = SLR +Responder_MEP_ID(OAM) = MI_MEP_ID +TxFCb(OAM) = TxFCb"]; D --> E[/D(OAM), D.P(P), D.DE(DE)/]; E --> F[G.8021-Y.1341(16)_F8-88]; F --> A; +``` + +The flowchart illustrates the SLR generation process. It begins with 'SLR generation' (oval), leading to 'Waiting' (oval). From 'Waiting', the process moves to 'RI\_SLM (OAM,P,DE TxFCb)' (parallelogram). This is followed by a block of assignments: 'DA(OAM) = SA(OAM)', 'SA(OAM) = Undefined', 'OPC(OAM) = SLR', 'Responder\_MEP\_ID(OAM) = MI\_MEP\_ID', and 'TxFCb(OAM) = TxFCb'. The next step is 'D(OAM), D.P(P), D.DE(DE)' (parallelogram). A feedback loop from the bottom of this block, labeled 'G.8021-Y.1341(16)\_F8-88', returns to the 'SLR generation' block. + +Flowchart of SLR generation behaviour + +**Figure 8-88 – SLR generation behaviour** + +Upon receipt of the RI\_SLM (OAM,P,DE,TxFCb) signal containing an SLM traffic unit, the SLR generation process generates an SLR traffic unit and forwards it to the MEP OAM insertion process. As part of the SLR generation: + +- the DA of the SLR traffic unit is the SA of the original SLM traffic unit +- the OpCode is changed into SLR OpCode +- the responder MEP\_ID is set to MI\_MEP\_ID +- TxFcb field is assigned the TxFcb value passed in the SLR(TxFcb) +- the other fields and optional TLVs are copied from the SLM. + +The resulting SLR traffic unit is shown in Figure 8-89. + +NOTE – In the generated SLR, in the OAM (MEP) insertion process, the SA will be overwritten with the local MAC address, and the MEL will be overwritten with MI\_MEL. + +![](ca86f53f9735fe98b6c6003d1b759f64_img.jpg) + +| | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +|------|------------------------------|---|---|---|---|---|---|---|----------------------------------------|---|---|---|---|---|---|---|----------------------------------------------|---|---|---|-----------|---|---|---|--------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | DA=SA(RI_SLM(OAM)) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | | | | | | SA=Undefined | | | | | | | | | | | | | | | | +| 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 13 | EtherType=89-02 | | | | | | | | | | | | | | | | MEL=Undef | | | | Version=0 | | | | OpCode=54(SLR) | | | | | | | | +| 17 | Flags=Flags(RI_SLM(OAM)) | | | | | | | | TLV Offset = TLV Offset((RI_SLM(OAM))) | | | | | | | | Source_MEP_ID = Source_MEP_ID((RI_SLM(OAM))) | | | | | | | | | | | | | | | | +| 21 | Responder_MEP_ID = MI_MEP_ID | | | | | | | | | | | | | | | | Test_ID = Test_ID((RI_SLM(OAM))) | | | | | | | | | | | | | | | | +| 25 | Test_ID Continued | | | | | | | | | | | | | | | | TxFCf = TxFCf((RI_SLM(OAM))) | | | | | | | | | | | | | | | | +| 29 | TxFCf Continued | | | | | | | | | | | | | | | | TxFCb = (RI_SLM(TxFCb)) | | | | | | | | | | | | | | | | +| 33 | TxFCb Continued | | | | | | | | | | | | | | | | TLV = TLV((RI_SLM(OAM))) if exists | | | | | | | | | | | | | | | | +| 37 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 41 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 45 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| : | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| last | | | | | | | | | | | | | | | | | | | | | | | | | End TLV = End TLV(RI_SLM(OAM)) | | | | | | | | + +Figure 8-89 – SLR traffic unit + +#### 8.1.14.6 SLR reception process + +The SLR reception process processes the received SLR traffic units and the complementing P and DE signals. The behaviour is defined in Figure 8-90. + +![Flowchart of SLR reception behaviour. The process starts with 'SLR reception', followed by 'Waiting', then 'D(OAM), P(P), DE(DE)'. A decision diamond asks 'DA(OAM) = MI_MEP_MAC'. If 'N' (No), it loops back to the entry point. If 'Y' (Yes), it proceeds to 'RI_SLR(MEP_ID(OAM), Test_ID(OAM), TxFCf(OAM), TxFCb(OAM))'.](61d000f6a2a1ff2f0da0b51fb732fafb_img.jpg) + +``` + +graph TD + A([SLR reception]) --> B([Waiting]) + B --> C[/D(OAM), P(P), DE(DE)/] + C --> D{DA(OAM) = MI_MEP_MAC} + D -- N --> A + D -- Y --> E[/RI_SLR(MEP_ID(OAM), Test_ID(OAM), TxFCf(OAM), TxFCb(OAM))/] + E --> A + +``` + +Flowchart of SLR reception behaviour. The process starts with 'SLR reception', followed by 'Waiting', then 'D(OAM), P(P), DE(DE)'. A decision diamond asks 'DA(OAM) = MI\_MEP\_MAC'. If 'N' (No), it loops back to the entry point. If 'Y' (Yes), it proceeds to 'RI\_SLR(MEP\_ID(OAM), Test\_ID(OAM), TxFCf(OAM), TxFCb(OAM))'. + +G.8021-Y.1341(16)\_F8-90 + +Figure 8-90 – SLR reception behaviour + +Upon receipt of an SLR traffic unit, the DA field of the traffic unit is checked. If the DA field equals the local MAC address, the SLR traffic unit is processed further, otherwise it is ignored. + +If the SLR traffic unit is processed, Test\_ID, TxFCf, TxFCb, responder MEP\_ID, are extracted from the traffic unit and signalled, using the RI\_SLR(MEP\_ID, Test\_ID, TxFCf, TxFCb) signal. + +### 8.1.15 Dual-ended synthetic loss measurement (ISL) processes + +#### 8.1.15.1 Overview + +Figure 8-91 shows the different processes inside MEPs and MIPs that are involved in the on-demand dual-ended synthetic loss measurement protocol. + +NOTE – In previous versions of this Recommendation, dual-ended synthetic loss measurement was known as one-way synthetic loss measurement. With regard to those definitions, refer to [ITU-T G.8013]. + +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 sink extraction process in clause 9.4.2.2. In summary, they insert and extract ETH\_CI\_OAM signals into and from the stream of ETH\_CI\_D traffic units and the complementing P and DE signals going through an MEP and MIP; the extraction is based on MEL and OpCode. Furthermore, the insertion process inserts the correct MEL and SA values into the OAM traffic units. + +![Figure 8-91: Overview of processes involved with on-demand dual-ended synthetic loss measurement. The diagram shows three main components: a source MEP, a middle MIP, and a sink MEP. The source MEP contains an 'On-demand OAM Insertion' block that receives 'ETH_CI' and 'D, P, DE' signals and outputs 'ETH_CI'. Below it, an 'ISL Generation' block receives 'ISL(DA, P, MEP_ID, Test_ID, TxFCI, TLV)' from an 'On-demand ISL Control_So' block. The 'On-demand ISL Control_So' block receives 'MI_1SL_Start(DA, P, Test_ID, Length, Period)', 'MI_1SL_Terminate', and 'MI_MEP_ID' signals. The MIP contains an 'On-demand OAM Extraction' block that receives 'ETH_CI' and outputs 'ETH_CI'. The sink MEP contains an 'On-demand OAM Extraction' block that receives 'ETH_CI' and outputs 'ETH_CI'. Below it, an 'ISL Reception' block receives 'D, P, DE' and 'MI_MEP_MAC' signals and outputs 'ISL(rSA, rMEPID, rTestID, TxFCf, RxFCf)' to an 'On-demand ISL Control_Sk' block. The 'On-demand ISL Control_Sk' block receives 'MI_1SL_Start(SA, Test_ID)', 'MI_1SL_Intermediate_Request', 'MI_1SL_Terminate', and outputs 'MI_1SL_Result(N_TF, N_LF)'.](796d2e601722450d6456085e0a801e1e_img.jpg) + +G.8021-Y.1341(16)\_F8-91 + +Figure 8-91: Overview of processes involved with on-demand dual-ended synthetic loss measurement. The diagram shows three main components: a source MEP, a middle MIP, and a sink MEP. The source MEP contains an 'On-demand OAM Insertion' block that receives 'ETH\_CI' and 'D, P, DE' signals and outputs 'ETH\_CI'. Below it, an 'ISL Generation' block receives 'ISL(DA, P, MEP\_ID, Test\_ID, TxFCI, TLV)' from an 'On-demand ISL Control\_So' block. The 'On-demand ISL Control\_So' block receives 'MI\_1SL\_Start(DA, P, Test\_ID, Length, Period)', 'MI\_1SL\_Terminate', and 'MI\_MEP\_ID' signals. The MIP contains an 'On-demand OAM Extraction' block that receives 'ETH\_CI' and outputs 'ETH\_CI'. The sink MEP contains an 'On-demand OAM Extraction' block that receives 'ETH\_CI' and outputs 'ETH\_CI'. Below it, an 'ISL Reception' block receives 'D, P, DE' and 'MI\_MEP\_MAC' signals and outputs 'ISL(rSA, rMEPID, rTestID, TxFCf, RxFCf)' to an 'On-demand ISL Control\_Sk' block. The 'On-demand ISL Control\_Sk' block receives 'MI\_1SL\_Start(SA, Test\_ID)', 'MI\_1SL\_Intermediate\_Request', 'MI\_1SL\_Terminate', and outputs 'MI\_1SL\_Result(N\_TF, N\_LF)'. + +**Figure 8-91 – Overview of processes involved with on-demand dual-ended synthetic loss measurement** + +The on-demand 1SL protocol is controlled by the on-demand 1SL Control\_So and 1SL Control\_Sk processes. The on-demand 1SL Control\_So process triggers the generation of 1SL traffic units upon receipt of an MI\_1SL\_Start(DA,P, Test\_ID,Length,Period) signal. The on-demand 1SL Control\_Sk process processes the information from received 1SL traffic units after receiving the MI\_1SL\_Start(SA,Test\_ID) signal. The result is communicated by the sink MEP when the process is terminated by the MI\_1SL\_Terminate signal or when an intermediate result is requested via the MI\_1SL\_Intermediate\_Request signal. + +The 1SL generation process generates 1SL messages that pass transparently through MIPs and are received and processed by the 1SL reception process in MEPs. + +Figure 8-92 shows the different processes inside MEPs and MIPs that are involved in the proactive dual-ended synthetic loss measurement protocol. + +![Figure 8-92: Overview of processes involved with proactive dual-ended synthetic loss measurement. The diagram shows three main components: a source MEP, a MIP, and a sink MEP. The source MEP contains 'Proactive OAM Insertion', '1SL Generation', and 'Proactive 1SL Control_So'. The MIP contains 'On-demand OAM Extraction'. The sink MEP contains 'Proactive OAM Extraction', '1SL Reception', and 'Proactive 1SL Control_Sk'. Data flows include ETH_CI, D, P, DE, 1SL (DA, P, MEP_ID, Test_ID, TxFCI, TLV), MI_1SL_Enable, MI_1SL_MAC_DA, MI_1SL_Test_ID, MI_1SL_Length, MI_1SL_Period, MI_1SL_Pri, MI_MEP_ID, MI_MEP_MAC, MI_1SL_Enable, MI_1SL_Mac_SA, MI_1SL_Test_ID, 1SL (rSA, rMEP_ID, rTest_ID, TxFCf, RxFCI), and 1SL_Result.](b3335932702b8668e62791e9fd12c9ff_img.jpg) + +The diagram illustrates the flow of OAM and 1SL traffic in a dual-ended synthetic loss measurement scenario. It consists of three main entities: a source MEP, a MIP, and a sink MEP. + +- Source MEP:** + - Proactive OAM Insertion:** Receives **ETH\_CI** and sends **ETH\_CI** to the MIP. It also receives **D, P, DE** from the 1SL Generation process. + - 1SL Generation:** Receives **1SL (DA, P, MEP\_ID, Test\_ID, TxFCI, TLV)** from the Proactive 1SL Control\_So process and sends **D, P, DE** to the Proactive OAM Insertion process. + - Proactive 1SL Control\_So:** Receives inputs: **MI\_1SL\_Enable**, **MI\_1SL\_MAC\_DA**, **MI\_1SL\_Test\_ID**, **MI\_1SL\_Length**, **MI\_1SL\_Period**, **MI\_1SL\_Pri**, and **MI\_MEP\_ID**. It sends **1SL (DA, P, MEP\_ID, Test\_ID, TxFCI, TLV)** to the 1SL Generation process. +- MIP:** + - On-demand OAM Extraction:** Receives **ETH\_CI** from the source MEP and sends **ETH\_CI** to the sink MEP. +- Sink MEP:** + - Proactive OAM Extraction:** Receives **ETH\_CI** from the MIP and sends **ETH\_CI** out. It also receives **D, P, DE** from the 1SL Reception process. + - 1SL Reception:** Receives **MI\_MEP\_MAC** and sends **D, P, DE** to the Proactive OAM Extraction process. It also sends **1SL (rSA, rMEP\_ID, rTest\_ID, TxFCf, RxFCI)** to the Proactive 1SL Control\_Sk process. + - Proactive 1SL Control\_Sk:** Receives **1SL (rSA, rMEP\_ID, rTest\_ID, TxFCf, RxFCI)** from the 1SL Reception process and inputs: **MI\_1SL\_Enable**, **MI\_1SL\_Mac\_SA**, and **MI\_1SL\_Test\_ID**. It sends **1SL\_Result** out. + +G.8021-Y.1341(16)\_F8-92 + +Figure 8-92: Overview of processes involved with proactive dual-ended synthetic loss measurement. The diagram shows three main components: a source MEP, a MIP, and a sink MEP. The source MEP contains 'Proactive OAM Insertion', '1SL Generation', and 'Proactive 1SL Control\_So'. The MIP contains 'On-demand OAM Extraction'. The sink MEP contains 'Proactive OAM Extraction', '1SL Reception', and 'Proactive 1SL Control\_Sk'. Data flows include ETH\_CI, D, P, DE, 1SL (DA, P, MEP\_ID, Test\_ID, TxFCI, TLV), MI\_1SL\_Enable, MI\_1SL\_MAC\_DA, MI\_1SL\_Test\_ID, MI\_1SL\_Length, MI\_1SL\_Period, MI\_1SL\_Pri, MI\_MEP\_ID, MI\_MEP\_MAC, MI\_1SL\_Enable, MI\_1SL\_Mac\_SA, MI\_1SL\_Test\_ID, 1SL (rSA, rMEP\_ID, rTest\_ID, TxFCf, RxFCI), and 1SL\_Result. + +**Figure 8-92 – Overview of processes involved with proactive dual-ended synthetic loss 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.2.2.2. + +The proactive 1SL protocol is controlled by the proactive 1SL Control\_So and 1SL Control\_Sk processes. The proactive 1SL Control\_So process triggers the generation of 1SL traffic units if MI\_1SL\_Enable signal is set. The 1SL frames are generated with a periodicity determined by MI\_1SL\_Period and with a priority determined by MI\_1SL\_Pri. The result is reported every one second by the 1SL Control\_Sk process. + +#### 8.1.15.2 1SL Control\_So process + +Figure 8-93 shows the behaviour of the on-demand 1SL Control\_So process. Upon receipt of the MI\_1SL\_Start(DA,P,Test\_ID, Length, Period) signal the 1SL protocol is started. The protocol will run until the receipt of the MI\_1SL\_Terminate signal. + +If the 1SL protocol is running, every period (as specified in the MI\_1SL\_Start signal) the generation of a 1SL message is triggered by generating the 1SL(DA,P,MEP\_ID,Test\_ID,TxFCI,TLV) signal towards the 1SL generation process. The MEP\_ID is the MI\_MEP\_ID of the MEP itself. The TLV is determined by the Generate(Length) function. Generate(Length) generates a data TLV with length "Length" of an arbitrary bit pattern, as described in clause 8.1.8.2. If the length is 0, the TLV is set to NULL. + +![Flowchart of On-demand 1SL Control_So behaviour. The process starts with 'On-demand 1SL Control_So' (oval), leading to 'Init' (oval), then 'MI_1SL_Start(DA,P,Test_ID,Length,Period)' (parallelogram), and 'Set(0,Timer)' (rectangle). It then enters a 'Running' (oval) state. From 'Running', it branches to 'Timer' (parallelogram) and 'MI_1SL_Terminate' (parallelogram). The 'Timer' path leads to 'TLV = Generate(Length)' (rectangle), 'TxFCI++' (rectangle), 'ISL(DA,P,MEP_ID, Test_ID,TxFCI,TLV)' (parallelogram), and 'Set(Period,Timer)' (rectangle). A feedback loop from 'Set(Period,Timer)' returns to the 'Running' state. Another feedback loop from 'MI_1SL_Terminate' returns to the 'Init' state.](a37adbbe12ec735a20ead2466363d07a_img.jpg) + +``` + +graph TD + Start([On-demand 1SL Control_So]) --> Init([Init]) + Init --> MI_1SL_Start[/MI_1SL_Start(DA,P,Test_ID,Length,Period)/] + MI_1SL_Start --> Set0Timer[Set(0,Timer)] + Set0Timer --> Running([Running]) + Running --> Timer[/Timer/] + Running --> MI_1SL_Terminate[/MI_1SL_Terminate/] + Timer --> TLV[TLV = Generate(Length)] + TLV --> TxFCI[TxFCI++] + TxFCI --> ISL[/ISL(DA,P,MEP_ID, Test_ID,TxFCI,TLV)/] + ISL --> SetPeriodTimer[Set(Period,Timer)] + SetPeriodTimer --> Running + MI_1SL_Terminate --> Init + +``` + +G.8021-Y.1341(16)\_F8-93 + +Flowchart of On-demand 1SL Control\_So behaviour. The process starts with 'On-demand 1SL Control\_So' (oval), leading to 'Init' (oval), then 'MI\_1SL\_Start(DA,P,Test\_ID,Length,Period)' (parallelogram), and 'Set(0,Timer)' (rectangle). It then enters a 'Running' (oval) state. From 'Running', it branches to 'Timer' (parallelogram) and 'MI\_1SL\_Terminate' (parallelogram). The 'Timer' path leads to 'TLV = Generate(Length)' (rectangle), 'TxFCI++' (rectangle), 'ISL(DA,P,MEP\_ID, Test\_ID,TxFCI,TLV)' (parallelogram), and 'Set(Period,Timer)' (rectangle). A feedback loop from 'Set(Period,Timer)' returns to the 'Running' state. Another feedback loop from 'MI\_1SL\_Terminate' returns to the 'Init' state. + +**Figure 8-93 – On-demand 1SL Control\_So behaviour** + +The behaviour of the proactive 1SL control process is defined in Figure 8-94. + +If the MI\_1SL\_Enable is asserted, the process starts to generate 1SL frames (using the 1SL (MI\_1SL\_MAC\_DA, MI\_1SL\_Pri, MI\_MEP\_ID, MI\_1SL\_Test\_ID, TxFCI, TLV) signal). + +![Flowchart of Proactive 1SL Control_So behaviour. The process starts with 'Proactive 1SL Control_So' (oval), leading to 'Disabled' (oval), then 'MI_1SL_Enable' (input/output shape), and 'Set(0,Timer)' (rectangle). It then enters an 'Enabled' (oval) state. From 'Enabled', it branches into 'Timer' (input/output shape) and '!MI_1SL_Enable' (input/output shape). The 'Timer' path leads to 'TLV = Generate(MI_1SL_Length)' (rectangle), 'TxFCI++' (rectangle), '1SL(MI_1SL_MAC_DA, MI_1SL_Pri, MI_MEP_ID, MI_1SL_Test_ID, TxFCI, TLV)' (input/output shape), and 'Set(MI_1SL_Period,Timer)' (rectangle). A feedback loop from 'Set(MI_1SL_Period,Timer)' returns to the entry point of the 'Enabled' state. Another feedback loop from '!MI_1SL_Enable' returns to the entry point of the 'Disabled' state.](3481cde1adf61b0452dd6489dada6d6a_img.jpg) + +``` + +graph TD + Start([Proactive 1SL Control_So]) --> Disabled([Disabled]) + Disabled --> MI_1SL_Enable[/MI_1SL_Enable/] + MI_1SL_Enable --> Set0Timer[Set(0,Timer)] + Set0Timer --> Enabled([Enabled]) + Enabled --> Timer[/Timer/] + Enabled --> NotMI_1SL_Enable[/!MI_1SL_Enable/] + Timer --> TLV[TLV = Generate(MI_1SL_Length)] + TLV --> TxFCI[TxFCI++] + TxFCI --> ISL[/1SL(MI_1SL_MAC_DA, +MI_1SL_Pri, +MI_MEP_ID, +MI_1SL_Test_ID, +TxFCI, +TLV)/] + ISL --> SetPeriod[Set(MI_1SL_Period,Timer)] + SetPeriod --> Enabled + NotMI_1SL_Enable --> Disabled + +``` + +Flowchart of Proactive 1SL Control\_So behaviour. The process starts with 'Proactive 1SL Control\_So' (oval), leading to 'Disabled' (oval), then 'MI\_1SL\_Enable' (input/output shape), and 'Set(0,Timer)' (rectangle). It then enters an 'Enabled' (oval) state. From 'Enabled', it branches into 'Timer' (input/output shape) and '!MI\_1SL\_Enable' (input/output shape). The 'Timer' path leads to 'TLV = Generate(MI\_1SL\_Length)' (rectangle), 'TxFCI++' (rectangle), '1SL(MI\_1SL\_MAC\_DA, MI\_1SL\_Pri, MI\_MEP\_ID, MI\_1SL\_Test\_ID, TxFCI, TLV)' (input/output shape), and 'Set(MI\_1SL\_Period,Timer)' (rectangle). A feedback loop from 'Set(MI\_1SL\_Period,Timer)' returns to the entry point of the 'Enabled' state. Another feedback loop from '!MI\_1SL\_Enable' returns to the entry point of the 'Disabled' state. + +G.8021-Y.1341(16)\_F8-94 + +**Figure 8-94 – Proactive 1SL Control\_So behaviour** + +#### 8.1.15.3 1SL generation process + +![Flowchart of the 1SL generation process. The steps are: 1SL generation -> Waiting -> 1SL(DA,P,MEP_ID, Test_ID,TxFCl,TLV) -> OAM=1SL(DA, P, MEP_ID, Test_ID, TxFCl, TLV) -> D(OAM,P(P),DE(0)). A feedback loop connects the final step back to the Waiting step. The diagram is labeled G.8021-Y.1341(16)_F8-95.](48adb97a6a4a14b039450192f25cc1e0_img.jpg) + +``` + +graph TD + A([1SL generation]) --> B([Waiting]) + B --> C[/1SL(DA,P,MEP_ID, Test_ID,TxFCl,TLV)/] + C --> D[OAM=1SL(DA, P, MEP_ID, Test_ID, TxFCl, TLV)] + D --> E[/D(OAM,P(P),DE(0))/] + 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.8021-Y.1341(16)\_F8-95 + +Flowchart of the 1SL generation process. The steps are: 1SL generation -> Waiting -> 1SL(DA,P,MEP\_ID, Test\_ID,TxFCl,TLV) -> OAM=1SL(DA, P, MEP\_ID, Test\_ID, TxFCl, TLV) -> D(OAM,P(P),DE(0)). A feedback loop connects the final step back to the Waiting step. The diagram is labeled G.8021-Y.1341(16)\_F8-95. + +**Figure 8-95 – 1SL generation behaviour** + +Figure 8-95 shows the 1SL generation process. Upon receiving the 1SL(DA, P, MEP\_ID, Test\_ID, TxFCl, TLV) signal, a single 1SL traffic unit is generated, along with the complementing P and DE signals. + +The DA, source\_MEP\_ID, Test\_ID and TxFCl of the generated traffic unit are determined by the DA, MEP\_ID, Test\_ID and TxFCl respectively in the 1SL(DA,P,MEP\_ID,Test\_ID,TxFCl,TLV) signal. If not NULL, the specified TLV is appended to the traffic unit as shown. + +The value of the P signal is determined by the 1SL(P) signal. The DE signal is set to 0. + +The resulting traffic unit is shown in Figure 8-96. + +NOTE – In the generated 1SL traffic unit, in the OAM (MEP) insertion process, the SA will be assigned the local MAC address, and the MEL will be assigned by MI\_MEL. + +| | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------|-------------------|---|---|---|-----------------|---|---|---|--------------------------------|---|---|---|---|---|---|---|-----------|---|---|---|---|---|---|---|-----------------|---|---|---|---|---|---|---|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | DA=1SL(DA) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 | SA=Undefined | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 13 | EtherType=89-02 | | | | | | | | MEL=Undef | | | | | | | | Version=0 | | | | | | | | OpCode=53 (1SL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 17 | Flags=0 | | | | TLV Offset = 16 | | | | Source_MEP_ID = 1SL(MI_MEP_ID) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 21 | 0 (not used) | | | | | | | | Test_ID = 1SL(Test_ID) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 25 | Test_ID Continued | | | | | | | | TxFCl = 1SL(TxFCl) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 29 | TxFCl Continued | | | | | | | | 0 (Reserved) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 33 | 0 (Reserved) | | | | | | | | TLV = 1SL(TLV) if exists | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 37 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 41 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 45 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| : | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| last | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | End TLV (0) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Figure 8-96 – 1SL traffic unit** + +#### 8.1.15.4 1SL reception process + +The 1SL reception process processes the received 1SL traffic units and the complementing P and DE signals. The behaviour is defined in Figure 8-97. + +![Flowchart of the 1SL Reception behaviour. The process starts with '1SL reception', followed by 'Waiting', then a block for 'D(OAM), P(P), DE(DE)'. A decision diamond checks if 'DA(OAM) = MI_MEP_MAC or DA(OAM) = MC Class1'. If 'N' (No), it loops back to the start. If 'Y' (Yes), it proceeds to 'RxFCI(MEP_ID(OAM), Test_ID(OAM))++', then to a block with '1SL(SA(OAM), MEP_ID(OAM), Test_ID(OAM), TxFCf(OAM), RxFCI)'. A small note 'G.8021-Y.1341(16)_F8-97' is at the bottom right.](56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg) + +``` +graph TD; A([1SL reception]) --> B([Waiting]); B --> C[/D(OAM), P(P), DE(DE)/]; C --> D{DA(OAM) = MI_MEP_MAC or DA(OAM) = MC Class1}; D -- N --> A; D -- Y --> E[RxFCI(MEP_ID(OAM), Test_ID(OAM))++]; E --> F[/1SL(SA(OAM), MEP_ID(OAM), Test_ID(OAM), TxFCf(OAM), RxFCI)/]; F --> A; G[G.8021-Y.1341(16)_F8-97]; +``` + +Flowchart of the 1SL Reception behaviour. The process starts with '1SL reception', followed by 'Waiting', then a block for 'D(OAM), P(P), DE(DE)'. A decision diamond checks if 'DA(OAM) = MI\_MEP\_MAC or DA(OAM) = MC Class1'. If 'N' (No), it loops back to the start. If 'Y' (Yes), it proceeds to 'RxFCI(MEP\_ID(OAM), Test\_ID(OAM))++', then to a block with '1SL(SA(OAM), MEP\_ID(OAM), Test\_ID(OAM), TxFCf(OAM), RxFCI)'. A small note 'G.8021-Y.1341(16)\_F8-97' is at the bottom right. + +Figure 8-97 – 1SL Reception behaviour + +Upon receipt of a 1SL traffic unit, the DA field is checked. The 1SL traffic unit is processed if the DA is equal to the local MAC address or a multicast class 1 address and ignored otherwise. + +If the 1SL traffic unit is processed, the SA, source\_MEP\_ID, Test\_ID and TxFCf fields are extracted and the appropriate RxFCI counter is incremented. The values are forwarded to the 1SL Control\_Sk Process using the 1SL(rSA, rMEP\_ID, rTest\_ID, TxFCf, RxFCI) signal. + +#### 8.1.15.5 1SL Control\_Sk process + +Figure 8-98 shows the behaviour of the on-demand 1SL Control\_Sk process. The MI\_1SL\_Start(SA, Test\_ID) signal starts the processing of 1SL messages coming from an MEP with SA as the MAC address. The protocol runs until the receipt of the MI\_1SL\_Terminate signal. + +While running, the process processes the received 1SL(rSA, rMEP\_ID, rTest\_ID, TxFCf, RxFCI) information. First the rSA is compared with the SA from the MI\_1SL\_Start (SA, Test\_ID) signal. If the rSA is not equal to this SA, the information is ignored. Next the rTest\_ID is compared with the Test\_ID from the MI\_1SL\_Start (SA, Test\_ID) signal. If the Test\_ID signal is configured and rTest\_ID is available but both values are different, the information is ignored. Otherwise, the loss from the single received 1SL traffic unit is calculated. This result is reported using the MI\_1SL\_Result(N\_TF, N\_LF) signal after receiving the MI\_1SL\_Terminate signal or of the MI\_1SL\_Intermediate\_Request signal. + +![Flowchart of the On-demand 1SL Control_Sk process. The process starts with 'On-demand 1SL Control_Sk' leading to 'Init', then 'MI_1SL_Start(SA, Test ID)', and 'N_TF = 0, N_LF = 0, saved = false'. It enters a 'Running' state where it handles '1SL(rSA, rMEP_ID, rTest_ID, TxFCf, RxFCf)', 'MI_1SL_Intermediate_Request', and 'MI_1SL_Terminate' messages. Decision diamonds check 'rSA=SA?', 'TestID!=NULL and rTestID!=TestID', and 'saved'. If 'rSA=SA?' is N, it loops back to 'Running'. If Y, it checks 'TestID!=NULL and rTestID!=TestID'. If Y, it loops back to 'Running'. If N, it checks 'saved'. If N, it loops back to 'Running'. If Y, it calculates 'N_TF+ = |TxFCf - TxFCf_svd|' and 'N_LF+ = |TxFCf - TxFCf_svd| - |RxFCf - RxFCf_svd|', then updates 'TxFCf_svd = TxFCf', 'RxFCf_svd = RxFCf', and 'saved = true', before looping back to 'Running'. 'MI_1SL_Intermediate_Request' and 'MI_1SL_Terminate' both lead to 'MI_1SL_Result(N_TF, N_LF)', which then loops back to 'Running'.](21ea5add6a61cc951b5c43ddffefb3ff_img.jpg) + +``` + +graph TD + Start([On-demand 1SL Control_Sk]) --> Init([Init]) + Init --> MI_1SL_Start[/MI_1SL_Start(SA, Test ID)/] + MI_1SL_Start --> InitVars[N_TF = 0, N_LF = 0 +saved = false] + InitVars --> Running([Running]) + Running --> Input[/1SL(rSA, rMEP_ID, rTest_ID, TxFCf, RxFCf)/] + Input --> rSA_SA{rSA=SA?} + rSA_SA -- N --> Running + rSA_SA -- Y --> TestID_Null{TestID!=NULL and rTestID!=TestID} + TestID_Null -- Y --> Running + TestID_Null -- N --> saved{saved} + saved -- N --> Running + saved -- Y --> CalcVars[N_TF+ = |TxFCf - TxFCf_svd| +N_LF+ = |TxFCf - TxFCf_svd| - |RxFCf - RxFCf_svd|] + CalcVars --> UpdateVars[TxFCf_svd = TxFCf +RxFCf_svd = RxFCf +saved = true] + UpdateVars --> Running + Running --> MI_1SL_Intermediate_Request[/MI_1SL_Intermediate_Request/] + MI_1SL_Intermediate_Request --> MI_1SL_Result1[/MI_1SL_Result(N_TF, N_LF)/] + MI_1SL_Result1 --> Running + Running --> MI_1SL_Terminate[/MI_1SL_Terminate/] + MI_1SL_Terminate --> MI_1SL_Result2[/MI_1SL_Result(N_TF, N_LF)/] + MI_1SL_Result2 --> Running + +``` + +Flowchart of the On-demand 1SL Control\_Sk process. The process starts with 'On-demand 1SL Control\_Sk' leading to 'Init', then 'MI\_1SL\_Start(SA, Test ID)', and 'N\_TF = 0, N\_LF = 0, saved = false'. It enters a 'Running' state where it handles '1SL(rSA, rMEP\_ID, rTest\_ID, TxFCf, RxFCf)', 'MI\_1SL\_Intermediate\_Request', and 'MI\_1SL\_Terminate' messages. Decision diamonds check 'rSA=SA?', 'TestID!=NULL and rTestID!=TestID', and 'saved'. If 'rSA=SA?' is N, it loops back to 'Running'. If Y, it checks 'TestID!=NULL and rTestID!=TestID'. If Y, it loops back to 'Running'. If N, it checks 'saved'. If N, it loops back to 'Running'. If Y, it calculates 'N\_TF+ = |TxFCf - TxFCf\_svd|' and 'N\_LF+ = |TxFCf - TxFCf\_svd| - |RxFCf - RxFCf\_svd|', then updates 'TxFCf\_svd = TxFCf', 'RxFCf\_svd = RxFCf', and 'saved = true', before looping back to 'Running'. 'MI\_1SL\_Intermediate\_Request' and 'MI\_1SL\_Terminate' both lead to 'MI\_1SL\_Result(N\_TF, N\_LF)', which then loops back to 'Running'. + +G.8021-Y.1341(16)\_F8-98 + +**Figure 8-98 – On-demand 1SL Control\_Sk process** + +The behaviour of the proactive 1SL Control\_Sk process is defined in Figure 8-99. If the MI\_1SL\_Enable is asserted, the result (N\_TF, N\_LF) is reported every one second. + +![Flowchart of the Proactive 1SL Control_Sk process. The process starts with 'Proactive 1SL Control_Sk' (oval), leading to 'Disabled' (oval), then 'MI_1SL_Enable' (parallelogram), 'N_TF = 0, N_LF = 0, saved = false' (rectangle), and 'Set(Is, ReportTimer)' (rectangle). It then enters an 'Enabled' (oval) loop. From 'Enabled', it branches to 'ISL(rSA,rMEP_ID,rTest_ID, TxFCf,RxFCl)' (parallelogram), 'ReportTimer' (parallelogram), and '!MI_1SL_Enable' (parallelogram). The 'ISL' path leads to a decision 'rSA = MI_IDM_MAC_SA?' (diamond). If 'N', it loops back to the entry point before 'Enabled'. If 'Y', it leads to 'MI_1SL_Test_ID! = NULL and rTest_ID! = MI_1SL_Test_ID' (diamond). If 'Y', it loops back. If 'N', it leads to 'saved' (diamond). If 'N', it loops back. If 'Y', it leads to 'N_TF+ = |TxFCf - TxFCf_svd|, N_LF+ = |TxFCf - TxFCf_svd| - |RxFCl - RxFCl_svd|' (rectangle), then 'TxFCf_svd = TxFCf, RxFCl_svd = RxFCl, saved = true' (rectangle), then loops back. The 'ReportTimer' path leads to 'ISL_Result(N_TF,N_LF)' (parallelogram), 'N_TF = 0, N_LF = 0' (rectangle), and 'Set(Is, ReportTimer)' (rectangle), then loops back. The '!MI_1SL_Enable' path loops back to the entry point before 'Disabled'.](df803281854ce2cbde7019b5aeefd8cd_img.jpg) + +``` + +graph TD + Start([Proactive 1SL Control_Sk]) --> Disabled([Disabled]) + Disabled --> MI_1SL_Enable[/MI_1SL_Enable/] + MI_1SL_Enable --> Init1[N_TF = 0, N_LF = 0 +saved = false] + Init1 --> Set1[Set(Is, ReportTimer)] + Set1 --> Enabled([Enabled]) + Enabled --> ISL[/ISL(rSA,rMEP_ID,rTest_ID, +TxFCf,RxFCl)/] + Enabled --> ReportTimer[/ReportTimer/] + Enabled --> NotMI_1SL_Enable[/!MI_1SL_Enable/] + NotMI_1SL_Enable --> Start + ISL --> rSA_Dec{rSA = +MI_IDM_MAC_SA?} + rSA_Dec -- N --> Enabled + rSA_Dec -- Y --> TestID_Dec{MI_1SL_Test_ID! = NULL and +rTest_ID! = MI_1SL_Test_ID} + TestID_Dec -- Y --> Enabled + TestID_Dec -- N --> saved_Dec{saved} + saved_Dec -- N --> Enabled + saved_Dec -- Y --> UpdateN[ +N_TF+ = |TxFCf - TxFCf_svd| +N_LF+ = |TxFCf - TxFCf_svd| - |RxFCl - RxFCl_svd| +] + UpdateN --> UpdateSvd[ +TxFCf_svd = TxFCf +RxFCl_svd = RxFCl +saved = true +] + UpdateSvd --> Enabled + ReportTimer --> ISL_Result[/ISL_Result(N_TF,N_LF)/] + ISL_Result --> Init2[N_TF = 0, +N_LF = 0] + Init2 --> Set2[Set(Is, ReportTimer)] + Set2 --> Enabled + +``` + +Flowchart of the Proactive 1SL Control\_Sk process. The process starts with 'Proactive 1SL Control\_Sk' (oval), leading to 'Disabled' (oval), then 'MI\_1SL\_Enable' (parallelogram), 'N\_TF = 0, N\_LF = 0, saved = false' (rectangle), and 'Set(Is, ReportTimer)' (rectangle). It then enters an 'Enabled' (oval) loop. From 'Enabled', it branches to 'ISL(rSA,rMEP\_ID,rTest\_ID, TxFCf,RxFCl)' (parallelogram), 'ReportTimer' (parallelogram), and '!MI\_1SL\_Enable' (parallelogram). The 'ISL' path leads to a decision 'rSA = MI\_IDM\_MAC\_SA?' (diamond). If 'N', it loops back to the entry point before 'Enabled'. If 'Y', it leads to 'MI\_1SL\_Test\_ID! = NULL and rTest\_ID! = MI\_1SL\_Test\_ID' (diamond). If 'Y', it loops back. If 'N', it leads to 'saved' (diamond). If 'N', it loops back. If 'Y', it leads to 'N\_TF+ = |TxFCf - TxFCf\_svd|, N\_LF+ = |TxFCf - TxFCf\_svd| - |RxFCl - RxFCl\_svd|' (rectangle), then 'TxFCf\_svd = TxFCf, RxFCl\_svd = RxFCl, saved = true' (rectangle), then loops back. The 'ReportTimer' path leads to 'ISL\_Result(N\_TF,N\_LF)' (parallelogram), 'N\_TF = 0, N\_LF = 0' (rectangle), and 'Set(Is, ReportTimer)' (rectangle), then loops back. The '!MI\_1SL\_Enable' path loops back to the entry point before 'Disabled'. + +G.8021-Y.1341(16)\_F8-99 + +**Figure 8-99 – Proactive 1SL Control\_Sk process** + +### 8.1.16 CSF insert process + +![Figure 8-100: CSF insert process symbol. A central box labeled 'CSF Insert' has three input arrows on the left labeled 'aCSF-RDI', 'aCSF-FDI', and 'aCSF-LOS'. It has five input arrows on the right labeled 'MI_MEP_MAC', 'MI_MEL', 'MI_CSF_Period', 'MI_CSF_Pri', and 'MI_CSFdciEnable'. It has three output arrows at the top labeled 'D', 'DE', and 'P', and three output arrows at the bottom labeled 'D', 'DE', and 'P'. Below the box is the text 'G.8021-Y.1341(16)_F8-100'.](bbf92fa724597efff9a7b4625ec54041_img.jpg) + +Figure 8-100: CSF insert process symbol. A central box labeled 'CSF Insert' has three input arrows on the left labeled 'aCSF-RDI', 'aCSF-FDI', and 'aCSF-LOS'. It has five input arrows on the right labeled 'MI\_MEP\_MAC', 'MI\_MEL', 'MI\_CSF\_Period', 'MI\_CSF\_Pri', and 'MI\_CSFdciEnable'. It has three output arrows at the top labeled 'D', 'DE', and 'P', and three output arrows at the bottom labeled 'D', 'DE', and 'P'. Below the box is the text 'G.8021-Y.1341(16)\_F8-100'. + +Figure 8-100 – CSF insert process + +Figure 8-100 shows the CSF insert process symbol, and Figure 8-101 defines the behaviour. If any of the aCSF-RDI, aCSF-FDI or aCSF-LOS signals are true, the CSF insert process continuously generates ETH\_CI traffic units where the ETH\_CI\_D signal contains the CSF traffic unit until the condition no longer holds, ie all of aCSF-RDI, aCSF-FDI and aCSF-LOS are false. At this point, CSF traffic unit(s) with DCI (Defect Clear Information) are generated indicating that the defect has been cleared, if MI\_CSFdciEnable = True. + +NOTE 1 – Figure 8-101 shows a case where a single CSF traffic unit with DCI is generated. However, the detail transmission condition (e.g., transmission period, the number of traffic unit) is out of scope of this Recommendation. + +The generated CSF traffic units are inserted in the incoming stream, i.e., the output stream contains the incoming traffic units and the generated CSF traffic units. + +![Figure 8-101: CSF insert behaviour flowchart. The flowchart starts with 'CSF insert' leading to 'CSF Disabled' and 'CSF Enable'. 'CSF Disabled' leads to 'D(D),P(P),DE(DE)' and 'aCSF-RDI || CSF-FDI || aCSF-LOS'. 'aCSF-RDI || CSF-FDI || aCSF-LOS' leads to 'Set(0, Timer)'. 'CSF Enable' leads to 'Timer', 'D(D),P(P),DE(DE)', and '(!aCSF-RDI && !aCSF-FDI && !aCSF-LOS)'. '(!aCSF-RDI && !aCSF-FDI && !aCSF-LOS)' leads to 'MI_CSFdciEnable'. 'MI_CSFdciEnable' leads to 'OAM=CSF(...)' and 'D(D),P(P),DE(DE)'. 'OAM=CSF(...)' leads to 'D(OAM), P(MI_CSF_Pri), DE(0)'. 'D(OAM), P(MI_CSF_Pri), DE(0)' leads to 'Set(MI_CSF_Period, Timer)'. 'Set(MI_CSF_Period, Timer)' leads back to 'CSF Enable'.](e20792fef9de6560b2d6c5441da7614a_img.jpg) + +``` + +graph TD + Start([CSF insert]) --> Disabled([CSF Disabled]) + Start --> Enable([CSF Enable]) + Disabled --> D1[D(D),P(P),DE(DE)] + Disabled --> Cond1[aCSF-RDI || CSF-FDI || aCSF-LOS] + Cond1 --> Set1[Set(0, Timer)] + Set1 --> D1 + Enable --> Timer[Timer] + Enable --> D2[D(D),P(P),DE(DE)] + Enable --> Cond2[!aCSF-RDI && !aCSF-FDI && !aCSF-LOS] + Cond2 --> MI_CSFdciEnable{MI_CSFdciEnable} + MI_CSFdciEnable -- N --> D2 + MI_CSFdciEnable -- Y --> OAM1[OAM=CSF(MI_MEP_MAC, MI_MEL, DCI, MI_CSF_Period)] + OAM1 --> D3[D(OAM), P(MI_CSF_Pri), DE(0)] + D3 --> Set2[Set(MI_CSF_Period, Timer)] + Set2 --> Enable + MI_CSFdciEnable -- Y --> OAM2[OAM=CSF(MI_MEP_MAC, MI_MEL, CSF_Type, MI_CSF_Period)] + OAM2 --> D4[D(OAM), P(MI_CSF_Pri), DE(0)] + D4 --> Set2 + Timer --> CSF_Type[CSF_Type=getCSFType(aCSF-RDI, aCSF-FDI, aCSF-LOS)] + CSF_Type --> OAM2 + +``` + +Figure 8-101: CSF insert behaviour flowchart. The flowchart starts with 'CSF insert' leading to 'CSF Disabled' and 'CSF Enable'. 'CSF Disabled' leads to 'D(D),P(P),DE(DE)' and 'aCSF-RDI || CSF-FDI || aCSF-LOS'. 'aCSF-RDI || CSF-FDI || aCSF-LOS' leads to 'Set(0, Timer)'. 'CSF Enable' leads to 'Timer', 'D(D),P(P),DE(DE)', and '(!aCSF-RDI && !aCSF-FDI && !aCSF-LOS)'. '(!aCSF-RDI && !aCSF-FDI && !aCSF-LOS)' leads to 'MI\_CSFdciEnable'. 'MI\_CSFdciEnable' leads to 'OAM=CSF(...)' and 'D(D),P(P),DE(DE)'. 'OAM=CSF(...)' leads to 'D(OAM), P(MI\_CSF\_Pri), DE(0)'. 'D(OAM), P(MI\_CSF\_Pri), DE(0)' leads to 'Set(MI\_CSF\_Period, Timer)'. 'Set(MI\_CSF\_Period, Timer)' leads back to 'CSF Enable'. + +Figure 8-101 – CSF insert behaviour + +If exactly one of aCSF-RDI, aCSF-FDI and aCSF-LOS is set, the getCSFType() function returns RDI, FDI or LOS as appropriate. + +NOTE 2 – As described in [ITU-T Y.1731], triggering CSF is client and application specific. Ideally all clients and applications should ensure that at most one of the conditions is set at any given time. + +The period between consecutive CSF traffic units is determined by the MI\_CSF\_Period parameter. Allowed values are once per second and once per minute; the encoding of these values is defined in Table 8-4. Note that these encoding are the same as for the LCK/AIS generation process. + +**Table 8-4 – CSF period values** + +| 3-bits | Period value | Comments | +|--------|---------------|----------------------------------------------| +| 000 | Invalid value | Invalid value for CSF PDUs | +| 001 | Reserved | Reserved for future standardization by ITU-T | +| 010 | Reserved | Reserved for future standardization by ITU-T | +| 011 | Reserved | Reserved for future standardization by ITU-T | +| 100 | 1 s | 1 frame per second | +| 101 | Reserved | Reserved for future standardization by ITU-T | +| 110 | 1 min | 1 frame per minute | +| 111 | Reserved | Reserved for future standardization by ITU-T | + +The ETH\_CI\_D signal contains a source and destination address field and an MSDU field. The format of the MSDU field for CSF traffic units is defined in clauses 9.1 and 9.21 of [ITU-T G.8013]. The MEL in the MSDU field is determined by the MI\_MEL input parameter. + +The values of the source and destination address fields in the ETH\_CI\_D signal are determined by the local MAC address (SA) and the multicast class 1 DA as described in [ITU-T G.8013] (DA). The value of the multicast class 1 DA is 01-80-C2-00-00-3x, where x is equal to MI\_MEL as defined in clause 10.1 of [ITU-T G.8013]. The value of MI\_MEP\_MAC should be a valid unicast MAC address. + +The CSF\_Type is encoded in the three bits of the flags field in the CSF PDU using the values from Table 8-5. + +**Table 8-5 – CSF type values** + +| Value | Type | Comments | +|-------|---------|----------------------------------| +| 000 | LOS | Client loss of signal | +| 001 | FDI/AIS | Client forward defect indication | +| 010 | RDI | Client reverse defect indication | +| 011 | DCI | Client defect clear indication | + +The periodicity (as defined by MI\_CSF\_Period) is encoded in the three least significant bits of the flags field in the CSF PDU using the values from Table 8-4. + +The CSF (SA, MEL, type, period) function generates a CSF traffic unit with the SA, MEL, type and period fields defined by the values of the parameters. Figure 8-102 below shows the ETH\_CI\_D signal format resulting from the function call from Figure 8-101: + +``` + +OAM=CSF( + MI_MEP_MAC, + MI_MEL, + CSF_Type, + MI_CSF_Period +) + +``` + +![](48b17e34bf39cb8a801a634c791250c0_img.jpg) + +| 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +|--------------------------------------|---|----------|--------------------------|----------------|---|---|---|---|---|---|---|----------------|---|---|---|-----------|---|---|---|-----------------|---|---|---|---|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| DA=01-80-C2-00-00-3x, where x=MI_MEL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SA=MI_MEP_MAC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EtherType=89-02 | | | | | | | | | | | | MEL=
MI_MEL | | | | Version=0 | | | | OpCode=52 (CSF) | | | | | | | | | | | | +| 0 | 0 | CSF Type | Period=
MI_CSF_Period | TLV Offset = 0 | | | | | | | | End TLV=0 | | | | | | | | | | | | | | | | | | | | + +**Figure 8-102 – CSF traffic unit** + +### **8.1.17 CSF extract process** + +The CSF extract process extracts ETH\_CI\_CSF signals from the incoming stream of ETH\_CI traffic units. ETH\_CI\_CSF signals are only extracted if they belong to the MEL as defined by the MI\_MEL input parameter. + +If an incoming traffic unit is a CSF traffic unit belonging to the MEL defined by MI\_MEL, the ETH\_CI\_CSF signal will be extracted from this traffic unit and the traffic unit will be filtered. The ETH\_CI\_CSF is the CSF specific information contained in the received traffic unit. All other traffic units will be transparently forwarded. The encoding of the ETH\_CI\_D signal for CSF frames is defined in clause 9.12 of [ITU-T G.8013]. + +The criteria for filtering are based on the values of the fields within the MSDU field of the ETH\_CI\_D signal: + +- length/type field equals the OAM EtherType (89-02) +- MEL field equals MI\_MEL +- OAM type equals CSF (52), as defined in clause 9.12 of [ITU-T G.8013]. + +This is defined in Figure 8-103. The function CSF(D) extracts the CSF specific information from the received traffic unit. + +Figure 8-104 shows the CSF extract behaviour. + +![Block diagram of the CSF Extract process. A central box labeled 'CSF Extract' has four input arrows at the bottom labeled P, DE, and D. It has four output arrows at the top labeled CSF, P, DE, and D. A separate input arrow labeled MI_MEL points to the right side of the box.](b33756b534bb4d9e9ceb8d0af4617768_img.jpg) + +Block diagram of the CSF Extract process. A central box labeled 'CSF Extract' has four input arrows at the bottom labeled P, DE, and D. It has four output arrows at the top labeled CSF, P, DE, and D. A separate input arrow labeled MI\_MEL points to the right side of the box. + +G.8021-Y.1341(12)\_F8.103 + +**Figure 8-103 – CSF extract process** + +![Flowchart of CSF extract behaviour. The process starts with 'CSF extract', followed by 'Waiting', then 'D(D),P(P),DE(DE)'. A decision diamond asks 'Etype(D)=89-02 & MEL(D)==MI_MEL & OPC(D)=52?'. If 'N' (No), it goes to 'D(D),P(P),DE(DE)'. If 'Y' (Yes), it goes to 'CSF(CSF(D))'. Both paths lead back to the 'Waiting' state. The diagram is labeled G.8021-Y.1341(16)_F8-104.](b8d855a06aad434aeafa2739bf62e7de_img.jpg) + +``` + +graph TD + A([CSF extract]) --> B([Waiting]) + B --> C[/D(D),P(P),DE(DE)/] + C --> D{Etype(D)=89-02 & MEL(D)==MI_MEL & OPC(D)=52?} + D -- N --> E[/D(D),P(P),DE(DE)/] + D -- Y --> F[/CSF(CSF(D))/] + E --> B + F --> B + +``` + +G.8021-Y.1341(16)\_F8-104 + +Flowchart of CSF extract behaviour. The process starts with 'CSF extract', followed by 'Waiting', then 'D(D),P(P),DE(DE)'. A decision diamond asks 'Etype(D)=89-02 & MEL(D)==MI\_MEL & OPC(D)=52?'. If 'N' (No), it goes to 'D(D),P(P),DE(DE)'. If 'Y' (Yes), it goes to 'CSF(CSF(D))'. Both paths lead back to the 'Waiting' state. The diagram is labeled G.8021-Y.1341(16)\_F8-104. + +**Figure 8-104 – CSF extract behaviour** + +### 8.1.18 BNM insert process + +![Diagram of the BNM insert process. A central block labeled 'BNM Insert' has multiple input signals on the left: MI_BNM_Enable, MI_BNM_Enable_Always, MI_BNM_Enable_SF, MI_MEP_MAC, MI_Client_MEL, MI_BNM_Hold_Time, MI_BNM_Period, MI_BNM_Pri, and MI_BNM_PortID. It also has two input signals on the right: NominalBW and CurrentBW. Output signals D, P, and DE are shown at the top and bottom of the block. The diagram is labeled G.8021-Y.1341(16)_F8-105.](69467ece0a576b4c2ec3e0c89ba61527_img.jpg) + +G.8021-Y.1341(16)\_F8-105 + +Diagram of the BNM insert process. A central block labeled 'BNM Insert' has multiple input signals on the left: MI\_BNM\_Enable, MI\_BNM\_Enable\_Always, MI\_BNM\_Enable\_SF, MI\_MEP\_MAC, MI\_Client\_MEL, MI\_BNM\_Hold\_Time, MI\_BNM\_Period, MI\_BNM\_Pri, and MI\_BNM\_PortID. It also has two input signals on the right: NominalBW and CurrentBW. Output signals D, P, and DE are shown at the top and bottom of the block. The diagram is labeled G.8021-Y.1341(16)\_F8-105. + +**Figure 8-105 – BNM insert process** + +Figure 8-105 shows the bandwidth notification message (BNM) symbol, and Figure 8-106 defines the behaviour. The NominalBW and CurrentBW are continuously signalled from the server layer, and contain respectively the nominal full transmission bandwidth of the link at the server layer, and the current available transmission bandwidth. + +NOTE 1 – The NominalBW and CurrentBW are generated by adaptation functions of some specific server layer technology such as microwave links. + +When MI\_BNM\_Enable is set, the BNM insert process monitors the current and nominal transmission bandwidths, and when the current transmission bandwidth falls below the nominal bandwidth for a given hold time, it generates ETH\_CI traffic units where the ETH\_CI\_D signal contains a BNM traffic unit. If MI\_BNM\_Enable\_Always is set, ETH\_CI traffic units where the ETH\_CI\_D signal contains a BNM traffic unit are also transmitted periodically when there is no degradation. If MI\_BNM\_Enable\_SF is set, ETH\_CI traffic units where the ETH\_CI\_D signal contains a BNM traffic unit are also transmitted periodically when the link fails in the transmit direction (i.e., when the current transmission bandwidth is 0). + +When the current transmission bandwidth changes, MI\_BNM\_Hold\_Time specifies the hold time before the first notification is sent. Allowed values are between 0 and 10 s (in increments of 10 ms). At the end of the hold time, a number of BNM notifications containing the new value are sent quickly (the exact number and period is implementation-specific) in order to increase the reliability of the notification. + +NOTE 2 – BNM notifications are expected to be used where the server layer is a microwave link that uses adaptive bandwidth modulation. A hold time is used to prevent notifications if the degradation is very short, such as might be caused by an object passing through the line of sight of the microwave link. + +The traffic units are generated with the Source MAC specified by MI\_MEP\_MAC, the MEG level specified by MI\_Client\_MEL, and the priority specified by MI\_BNM\_Pri. During degradation or link failure, they are generated periodically at the period specified by MI\_BNM\_Period; allowed values are 1 s, 10 s and 1 min. BNM\_Fast\_Period and BNM\_Fast\_Count in the Figure 8-106 are implementation specific parameters that allow sending a number of the first BNM frames more quickly. The value of BNM\_Fast\_Period must be less than or equal to MI\_BNM\_Period. If MI\_BNM\_PortID is set, the Port ID field is set to the value specified in MI\_BNM\_PortID. Otherwise, the Port ID field is set to 0 to indicate that no Port ID was configured. + +The generated BNM traffic units are inserted in the incoming stream, i.e., the output stream contains the incoming traffic units and the generated BNM traffic units. + +The BNM insert process continues generating BNM traffic units until the current bandwidth is restored to the nominal bandwidth. At that point a number of the final BNM traffic units are generated with the current bandwidth set equal to the nominal bandwidth. If MI\_BNM\_Enabled\_Always is not set, generation of BNM traffic units then ceases. Otherwise, BNM traffic units continue to be generated periodically at the period specified by MI\_BNM\_Period. + +![Flowchart of BNM insert behaviour. The process starts with 'BNM insert' leading to 'Disabled'. From 'Disabled', it branches into 'D(D), P(P), DE(DE)' and 'MI_BNM_Enable'. 'MI_BNM_Enable' leads to initialization: 'ReportedBW = CurrentBW', 'nCount = BNM_Fast_Count', 'Holding = False', 'set (0, TxTimer)'. Both branches lead to 'Enabled'. From 'Enabled', it branches into five parallel paths: '!MI_BNM_Enable' (resets timers), 'CurrentBW' (checks if equal to ReportedBW), 'TxTimer' (checks if PortID is set), 'HoldTimer' (resets variables), and 'D(D), P(P), DE(DE)'. The 'CurrentBW' path leads to a 'Holding?' decision. If 'Holding?' is 'Y', it sets 'Holding = True' and updates 'MI_BNM_Hold_Time' and 'HoldTimer'. If 'Holding?' is 'N', it checks if 'CurrentBW = ReportedBW?'. If 'Y', it sets 'Holding = False' and resets 'HoldTimer'. If 'N', it leads to 'OAM = BNM' initialization. The 'TxTimer' path leads to 'MI_BNM_PortID = set?' decision. If 'Y', it sets 'PortID = MI_BNM_PortID'. If 'N', it sets 'PortID = 0'. Both lead to 'OAM = BNM' initialization. 'OAM = BNM' leads to 'D(OAM), P(MI_BNM_Pri), DE(0)'. This leads to 'nCount > 0?' decision. If 'Y', it decrements 'nCount' and loops back. If 'N', it leads to 'nCount = 0?' decision. If 'Y', it leads to 'ReportedBW > 0 or MI_BNM_Enable_SF' decision. If 'Y', it leads to 'ReportedBW != NominalBW or MI_BNM_Enable_Always' decision. If 'Y', it sets 'MI_BNM_Period' and 'TxTimer'. If 'N', it loops back to 'Enabled'. If 'ReportedBW != NominalBW or MI_BNM_Enable_Always' is 'Y', it sets 'BNM_Period' and 'TxTimer'. Both 'Set' blocks lead to a common exit point. The 'ReportedBW > 0 or MI_BNM_Enable_SF' decision is 'N', it loops back to 'Enabled'. The 'ReportedBW != NominalBW or MI_BNM_Enable_Always' decision is 'N', it loops back to 'Enabled'.](c7111699f84f3e2bc4016b7876f10de6_img.jpg) + +``` + +graph TD + Start([BNM insert]) --> Disabled([Disabled]) + Disabled --> D1[/D(D), P(P), DE(DE)/] + Disabled --> MI_Enable[/MI_BNM_Enable/] + D1 --> D2[/D(D), P(P), DE(DE)/] + MI_Enable --> Init1["ReportedBW = CurrentBW +nCount = BNM_Fast_Count +Holding = False +set (0, TxTimer)"] + Init1 --> Enabled([Enabled]) + D2 --> Enabled + Enabled --> NotMI_Enable[/!MI_BNM_Enable/] + Enabled --> CurrentBW[/CurrentBW/] + Enabled --> TxTimer[/TxTimer/] + Enabled --> HoldTimer[/HoldTimer/] + Enabled --> D3[/D(D), P(P), DE(DE)/] + NotMI_Enable --> ResetTimers["Reset (TxTimer) +Reset (HoldTimer)"] + ResetTimers --> Enabled + CurrentBW --> CBW_Equal{CurrentBW = ReportedBW?} + CBW_Equal -- Y --> HoldingFalse["Holding = False +Reset (HoldTimer)"] + HoldingFalse --> Enabled + CBW_Equal -- N --> Holding{Holding?} + Holding -- Y --> HoldingTrue["Holding = True +Set (MI_BNM_Hold_Time, +HoldTimer)"] + HoldingTrue --> CBW_Equal + Holding -- N --> OAMInit["OAM = BNM (MI_MEP_MAC, +MI_Client_MEL, +MI_BNM_Period, +NominalBW, +ReportedBW, +PortID)"] + OAMInit --> D4[/D(OAM), P(MI_BNM_Pri), DE(0)/] + D4 --> nCountGT0{nCount > 0?} + nCountGT0 -- Y --> nCountDec[nCount --] + nCountDec --> nCountGT0 + nCountGT0 -- N --> nCountZero{nCount = 0?} + nCountZero -- Y --> ReportedBWGT0{ReportedBW > 0 or +MI_BNM_Enable_SF} + nCountZero -- N --> SetBNM["Set (BNM_Period, TxTimer)"] + SetBNM --> Exit(( )) + ReportedBWGT0 -- Y --> ReportedBWNotNominal{ReportedBW != NominalBW or +MI_BNM_Enable_Always} + ReportedBWNotNominal -- Y --> SetMI["Set (MI_BNM_Period, TxTimer)"] + SetMI --> Exit + ReportedBWNotNominal -- N --> Enabled + ReportedBWGT0 -- N --> Enabled + TxTimer --> PortIDSet{MI_BNM_PortID = set?} + PortIDSet -- Y --> PortIDMI["PortID = MI_BNM_PortID"] + PortIDSet -- N --> PortID0["PortID = 0"] + PortIDMI --> OAMInit + PortID0 --> OAMInit + HoldTimer --> HoldingFalse2["Holding = False +ReportedBW = CurrentBW +nCount = BNM_Fast_Count +Set (0, TxTimer)"] + HoldingFalse2 --> D3 + D3 --> D5[/D(D), P(P), DE(DE)/] + D5 --> Enabled + +``` + +Flowchart of BNM insert behaviour. The process starts with 'BNM insert' leading to 'Disabled'. From 'Disabled', it branches into 'D(D), P(P), DE(DE)' and 'MI\_BNM\_Enable'. 'MI\_BNM\_Enable' leads to initialization: 'ReportedBW = CurrentBW', 'nCount = BNM\_Fast\_Count', 'Holding = False', 'set (0, TxTimer)'. Both branches lead to 'Enabled'. From 'Enabled', it branches into five parallel paths: '!MI\_BNM\_Enable' (resets timers), 'CurrentBW' (checks if equal to ReportedBW), 'TxTimer' (checks if PortID is set), 'HoldTimer' (resets variables), and 'D(D), P(P), DE(DE)'. The 'CurrentBW' path leads to a 'Holding?' decision. If 'Holding?' is 'Y', it sets 'Holding = True' and updates 'MI\_BNM\_Hold\_Time' and 'HoldTimer'. If 'Holding?' is 'N', it checks if 'CurrentBW = ReportedBW?'. If 'Y', it sets 'Holding = False' and resets 'HoldTimer'. If 'N', it leads to 'OAM = BNM' initialization. The 'TxTimer' path leads to 'MI\_BNM\_PortID = set?' decision. If 'Y', it sets 'PortID = MI\_BNM\_PortID'. If 'N', it sets 'PortID = 0'. Both lead to 'OAM = BNM' initialization. 'OAM = BNM' leads to 'D(OAM), P(MI\_BNM\_Pri), DE(0)'. This leads to 'nCount > 0?' decision. If 'Y', it decrements 'nCount' and loops back. If 'N', it leads to 'nCount = 0?' decision. If 'Y', it leads to 'ReportedBW > 0 or MI\_BNM\_Enable\_SF' decision. If 'Y', it leads to 'ReportedBW != NominalBW or MI\_BNM\_Enable\_Always' decision. If 'Y', it sets 'MI\_BNM\_Period' and 'TxTimer'. If 'N', it loops back to 'Enabled'. If 'ReportedBW != NominalBW or MI\_BNM\_Enable\_Always' is 'Y', it sets 'BNM\_Period' and 'TxTimer'. Both 'Set' blocks lead to a common exit point. The 'ReportedBW > 0 or MI\_BNM\_Enable\_SF' decision is 'N', it loops back to 'Enabled'. The 'ReportedBW != NominalBW or MI\_BNM\_Enable\_Always' decision is 'N', it loops back to 'Enabled'. + +Figure 8-106 – BNM insert behaviour + +To prevent very frequent changes in the notified bandwidth, server layer should avoid reporting consecutive changes of the CurrentBW within an implementation specific time: the filtering mechanism is implementation and server layer specific. + +The BNM(SA, MEL, Period, NominalBW, CurrentBW, PortID) function generates an ETH\_CI traffic unit containing a source and destination address field and an MSDU field. The source address is set to the given SA, and the destination address is set to the multicast class 1 DA as described in [ITU-T G.8013]. The format of the MSDU field for BNM traffic units is defined in [ITU-T G.8013]. The MEL, Period, Current Bandwidth, Nominal Bandwidth and Port ID fields are set to the given values. Figure 8-107 below shows the ETH\_CI\_D signal format resulting from the function call from Figure 8-106: + +``` +OAM=BNM( +MI_MEP_MAC, +MI_Client_MEL, +MI_BNM_Period, +NominalBW +ReportedBW, +PortID +) +``` + +![](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +| | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | +|----|--------------------------------------|---|---|---|---|------------------------------|-----------------|---|---|---|---|---|---|---|-------------------|---|--------------------|---|---|---|-----------|---|-------------------|---|-----------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | DA=01-80-C2-00-00-3x, where x=MI_MEL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | | | | | | SA=MI_MEP_MAC | | | | | | | | | | | | | | | | +| 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 13 | EtherType=89-02 | | | | | | | | | | | | | | | | MEL=
MI_
MEL | | | | Version=0 | | | | OpCode=32 (GNM) | | | | | | | | +| 17 | 0 | 0 | 0 | 0 | 0 | Period=
MI_BNM
_Period | TLV Offset = 13 | | | | | | | | SubOpCode=1 (BNM) | | | | | | | | Nominal Bandwidth | | | | | | | | | | +| 21 | Nominal Bandwidth Continued | | | | | | | | | | | | | | | | Current Bandwidth | | | | | | | | | | | | | | | | +| 25 | Current Bandwidth Continued | | | | | | | | | | | | | | | | Port ID | | | | | | | | | | | | | | | | +| 29 | Port ID Continued | | | | | | | | | | | | | | | | End TLV (0) | | | | | | | | | | | | | | | | + +Figure 8-107 – BNM traffic unit + +NOTE 3 – The Period field in the generated BNM Traffic Unit is always set to MI\_BNM\_Period, even for the initial traffic units generated after the expiry of the hold time, which are transmitted at an implementation-specific faster period. This ensures the correct operation of the BNM extract process in the receiving MEP. + +### 8.1.19 BNM extract process + +The BNM extract process processes the received BNM traffic units and the complementing P and DE signals. + +![Diagram of the BNM extract process. A central block labeled 'BNM extract' receives three inputs from the right: 'D', 'P', and 'DE'. It outputs two signals to the left: 'MI_MEP_MAC' and 'MI_BW_Report (SA, PortID, NominalBW, CurrentBW)'. Below the diagram is the text 'G.8021-Y.1341(16)_F8-108'.](6322885569221ec51d70560d7dba1339_img.jpg) + +Diagram of the BNM extract process. A central block labeled 'BNM extract' receives three inputs from the right: 'D', 'P', and 'DE'. It outputs two signals to the left: 'MI\_MEP\_MAC' and 'MI\_BW\_Report (SA, PortID, NominalBW, CurrentBW)'. Below the diagram is the text 'G.8021-Y.1341(16)\_F8-108'. + +Figure 8-108 – BNM extract process + +Figure 8-108 shows the BNM extract process symbol, and Figure 8-109 defines the behaviour. When BNM traffic units are received, if the DA is equal to the MEP's MAC, or it is a multicast class 1 address, then the SA, Port ID, Current Bandwidth and Nominal Bandwidth are extracted from the traffic unit and, if different to the previous values, are passed to the Management System via the MI\_BW\_Report(SA, PortID, NominalBW, CurrentBW) signal. + +![Flowchart of BNM extract behaviour. The process starts with 'BNM extract', followed by an initialization block for all SA and PortID: n_bw(SA, PortID) = 0, c_bw(SA, PortID) = 0. It then enters a 'Waiting' state. From 'Waiting', two paths emerge: one for receiving D(OAM,P(P),DE(DE)) and another for 'Timer(SA,PortID)'. The timer path leads to 'MI_BW_Report(SA,PortID, 0, 0)' and then resets n_bw and c_bw to 0. The D(OAM) path leads to a decision 'DA(OAM) = MI_MEP_MAC or DA(OAM) = MC Class 1?'. If 'N' (No), it loops back to 'Waiting'. If 'Y' (Yes), it leads to another decision 'n_bw(SA(OAM), PortID(OAM)) != NominalBW(OAM) or c_bw(SA(OAM), PortID(OAM)) != CurrentBW(OAM)?'. If 'Y' (Yes), it leads to 'MI_BW_Report(SA(OAM),PortID(OAM), NominalBW(OAM), CurrentBW(OAM))', then updates n_bw and c_bw, then 'Set(K*Period(OAM), Timer(SA(OAM), PortID(OAM)))', and loops back to 'Waiting'. If 'N' (No), it goes directly to 'Set(K*Period(OAM), Timer(SA(OAM), PortID(OAM)))' and loops back to 'Waiting'.](06b83e9b87612260a1221a69827ba169_img.jpg) + +``` + +graph TD + Start([BNM extract]) --> Init["For all SA, for all PortID: +n_bw(SA, PortID) = 0 +c_bw(SA, PortID) = 0"] + Init --> Waiting([Waiting]) + Waiting --> D["D(OAM,P(P),DE(DE))"] + Waiting --> Timer["Timer(SA,PortID)"] + Timer --> MI_BW_Report_T["MI_BW_Report(SA,PortID, 0, 0)"] + MI_BW_Report_T --> Reset_T["n_bw(SA,PortID)=0 +c_bw(SA,PortID)=0"] + Reset_T --> Waiting + D --> DA_Q{"DA(OAM) = MI_MEP_MAC or +DA(OAM) = MC Class 1?"} + DA_Q -- N --> Waiting + DA_Q -- Y --> BW_Q{"n_bw(SA(OAM), PortID(OAM)) != NominalBW(OAM) or +c_bw(SA(OAM), PortID(OAM)) != CurrentBW(OAM)?"} + BW_Q -- Y --> MI_BW_Report_B["MI_BW_Report( +SA(OAM),PortID(OAM) +NominalBW(OAM), +CurrentBW(OAM))"] + MI_BW_Report_B --> Update_B["n_bw(SA(OAM), PortID(OAM)) = NominalBW(OAM) +c_bw(SA(OAM), PortID(OAM)) = CurrentBW(OAM)"] + Update_B --> Set_T["Set(K*Period(OAM), +Timer(SA(OAM), PortID(OAM)))"] + Set_T --> Waiting + BW_Q -- N --> Set_T + +``` + +Flowchart of BNM extract behaviour. The process starts with 'BNM extract', followed by an initialization block for all SA and PortID: n\_bw(SA, PortID) = 0, c\_bw(SA, PortID) = 0. It then enters a 'Waiting' state. From 'Waiting', two paths emerge: one for receiving D(OAM,P(P),DE(DE)) and another for 'Timer(SA,PortID)'. The timer path leads to 'MI\_BW\_Report(SA,PortID, 0, 0)' and then resets n\_bw and c\_bw to 0. The D(OAM) path leads to a decision 'DA(OAM) = MI\_MEP\_MAC or DA(OAM) = MC Class 1?'. If 'N' (No), it loops back to 'Waiting'. If 'Y' (Yes), it leads to another decision 'n\_bw(SA(OAM), PortID(OAM)) != NominalBW(OAM) or c\_bw(SA(OAM), PortID(OAM)) != CurrentBW(OAM)?'. If 'Y' (Yes), it leads to 'MI\_BW\_Report(SA(OAM),PortID(OAM), NominalBW(OAM), CurrentBW(OAM))', then updates n\_bw and c\_bw, then 'Set(K\*Period(OAM), Timer(SA(OAM), PortID(OAM)))', and loops back to 'Waiting'. If 'N' (No), it goes directly to 'Set(K\*Period(OAM), Timer(SA(OAM), PortID(OAM)))' and loops back to 'Waiting'. + +G.8021-Y.1341(16)\_F8-109 + +**Figure 8-109 – BNM extract behaviour** + +Based on the received BNM frames and/or timer expiration the MEP is able to report the following information: + +- Full bandwidth conditions when $c\_bw = n\_bw \neq 0$ +- Degraded conditions when $c\_bw < n\_bw$ and $c\_bw \neq 0$ +- Link faults conditions when $c\_bw = 0$ and $n\_bw \neq 0$ +- Unknown link conditions when $c\_bw = n\_bw = 0$ + +NOTE 2 – The $c\_bw/n\_bw$ is the value in MI\_BW\_Report, not the value in the BNM. + +When the MEP reports unknown link conditions, the management system, if needed, can correlate this information with other network information (e.g., the network topology, the alarms, and SF status of this or other links) to determine which is the actual condition of the link. + +A timer is used in the BNM Extract process to detect when BNM traffic units are no longer being received. This is set to K times the period extracted from the Period field in the last received traffic unit. The BNM Extract process therefore does not require any local Management Information (MI) to set the period. + +### 8.1.20 Expected Defect (ED) processes + +#### 8.1.20.1 Overview + +Figure 8-110 shows the different processes inside MEPs that are involved in Expected Defect Message signals carried in MCC protocol data units. + +In the source side of ETHx to MCC adaptation function, expected defect message (EDM) signals are generated in EDM generation process when MI\_EDM\_Enable is set. MCC generation process encapsulates the signals into MCC PDUs and generates ETH\_AI\_D traffic units together with the complementing P and DE signals. In the sink side, the MCC reception process receives ETH\_AI traffic units and extracts EDM signals from MCC PDUs. Finally, EDM reception process terminates the signals and generates MI\_EDM\_Received (MEP\_ID, Duration) signals to equipment management function (EMF). + +![Figure 8-110: Overview of Expected Defect processes. This block diagram shows the flow of Expected Defect (ED) signals between two Management End Points (MEPs) through a Maintenance Intermediate Point (MIP). On the left (source side), an 'ETH_CI' input enters a block labeled 'MEP'. Inside, 'Other adaptation' and 'ETHx' blocks are shown. Below them, 'MCC Generation' and 'EDM Generation' blocks are present. Inputs to 'EDM Generation' include 'MI_EDM_Enable', 'MI_EDM_Period', 'MI_EDM_Duration', and 'MI_MEP_ID'. Its output 'D' goes to 'MCC Generation'. 'MCC Generation' also takes 'MCC_CI_D', 'MI_MEL', 'MI_MEP_MAC', and 'MI_MCC_Pri' as inputs and outputs 'ETH_AI'. This 'ETH_AI' signal passes through an 'ETHx' block, then through the 'MIP' block, and then through another 'ETHx' block on the right. On the right (sink side), the signal enters another 'MEP' block. It passes through 'ETHx' and 'Other adaptation' to become 'ETH_CI'. Below, 'MCC Reception' takes 'ETH_AI' as input and outputs 'MCC_CI_D', 'MI_MEL', and 'MI_MEP_MAC'. Its output 'D' goes to 'EDM Reception', which outputs 'MI_EDM_Received (MEP_ID,Duration)'. Both MEP blocks are part of an 'ETHx/MCC_A_so' (source) and 'ETHx/MCC_A_sk' (sink) adaptation function. The diagram is labeled G.8021-Y.1341(16)_F8-110.](8edfc370769207831f060f44d2281084_img.jpg) + +Figure 8-110: Overview of Expected Defect processes. This block diagram shows the flow of Expected Defect (ED) signals between two Management End Points (MEPs) through a Maintenance Intermediate Point (MIP). On the left (source side), an 'ETH\_CI' input enters a block labeled 'MEP'. Inside, 'Other adaptation' and 'ETHx' blocks are shown. Below them, 'MCC Generation' and 'EDM Generation' blocks are present. Inputs to 'EDM Generation' include 'MI\_EDM\_Enable', 'MI\_EDM\_Period', 'MI\_EDM\_Duration', and 'MI\_MEP\_ID'. Its output 'D' goes to 'MCC Generation'. 'MCC Generation' also takes 'MCC\_CI\_D', 'MI\_MEL', 'MI\_MEP\_MAC', and 'MI\_MCC\_Pri' as inputs and outputs 'ETH\_AI'. This 'ETH\_AI' signal passes through an 'ETHx' block, then through the 'MIP' block, and then through another 'ETHx' block on the right. On the right (sink side), the signal enters another 'MEP' block. It passes through 'ETHx' and 'Other adaptation' to become 'ETH\_CI'. Below, 'MCC Reception' takes 'ETH\_AI' as input and outputs 'MCC\_CI\_D', 'MI\_MEL', and 'MI\_MEP\_MAC'. Its output 'D' goes to 'EDM Reception', which outputs 'MI\_EDM\_Received (MEP\_ID,Duration)'. Both MEP blocks are part of an 'ETHx/MCC\_A\_so' (source) and 'ETHx/MCC\_A\_sk' (sink) adaptation function. The diagram is labeled G.8021-Y.1341(16)\_F8-110. + +Figure 8-110 – Overview of Expected Defect processes + +#### 8.1.20.2 EDM Generation process + +![Figure 8-111: EDM Generation process. This block diagram shows the 'EDM generation' block. It has four inputs on the left: 'MI_EDM_Enable', 'MI_EDM_Period', 'MI_EDM_Duration', and 'MI_MEP_ID'. It has one output on the right labeled 'D'. The diagram is labeled G.8021-Y.1341(16)_F8-111.](878e3f080378afb04bb23d5863edc6a5_img.jpg) + +Figure 8-111: EDM Generation process. This block diagram shows the 'EDM generation' block. It has four inputs on the left: 'MI\_EDM\_Enable', 'MI\_EDM\_Period', 'MI\_EDM\_Duration', and 'MI\_MEP\_ID'. It has one output on the right labeled 'D'. The diagram is labeled G.8021-Y.1341(16)\_F8-111. + +Figure 8-111 – EDM Generation process + +Figure 8-111 shows the EDM Generation process symbol, and Figure 8-112 defines the behaviour. When MI\_EDM\_Enable is set, the process generates EDM signal. Based on the EDM signals, MCC PDUs are generated at the MCC Generation process. As a result, MCC PDUs are signalled to peer MEPs that CCM transmission will be interrupted or has not yet commenced, and hence that Loss of Continuity defects and consequent actions should be suppressed. + +EDM signals are generated periodically at the specified period and containing the specified Duration until MI\_EDM\_Enable is unset. + +![Flowchart of EDM Generation behaviour. The process starts with 'EDM generation' leading to 'Idle'. From 'Idle', it proceeds to 'MI_EDM_Enable'. If 'MI_EDM_Enable' is set, it goes to 'Set (0, Timer)' and then to 'Defect'. From 'Defect', it branches into two paths: one for '!MI_EDM_Enable' leading to 'Reset (Timer)' and back to 'Idle', and another for 'Timer' leading to 'D = EDM (MI_MEP_ID, MI_EDM_Duration)', then 'D(D)', then 'Set (MI_EDM_Period, Timer)', and finally back to 'Idle'.](7e12e1e0d03a03790d2e9d74c3454bff_img.jpg) + +``` + +graph TD + Start([EDM generation]) --> Idle([Idle]) + Idle --> MI_EDM_Enable{MI_EDM_Enable} + MI_EDM_Enable --> Set0[Set (0, Timer)] + Set0 --> Defect([Defect]) + Defect --> NotMI_EDM_Enable{!MI_EDM_Enable} + Defect --> Timer{Timer} + NotMI_EDM_Enable --> Reset[Reset (Timer)] + Reset --> Idle + Timer --> D["D = EDM (MI_MEP_ID, MI_EDM_Duration)"] + D --> D_D[D(D)] + D_D --> SetMI["Set (MI_EDM_Period, Timer)"] + SetMI --> Idle + +``` + +Flowchart of EDM Generation behaviour. The process starts with 'EDM generation' leading to 'Idle'. From 'Idle', it proceeds to 'MI\_EDM\_Enable'. If 'MI\_EDM\_Enable' is set, it goes to 'Set (0, Timer)' and then to 'Defect'. From 'Defect', it branches into two paths: one for '!MI\_EDM\_Enable' leading to 'Reset (Timer)' and back to 'Idle', and another for 'Timer' leading to 'D = EDM (MI\_MEP\_ID, MI\_EDM\_Duration)', then 'D(D)', then 'Set (MI\_EDM\_Period, Timer)', and finally back to 'Idle'. + +G.8021-Y.1341(16)\_F8-112 + +**Figure 8-112 – EDM Generation behaviour** + +In the MCC Generation process, ETH\_AI traffic units containing a source and destination address field and an MSDU field are generated. The format of the MSDU field for MCC and EDM information is defined in [ITU-T G.8013]. The EDM signal contains the MEP ID set to MI\_MEP\_ID and the Expected Defect Duration set to MI\_EDM\_Duration. In addition, MCC PDUs are generated with the priority set to MI\_MCC\_Pri, the SA set to the local MAC address by MI\_MEP\_MAC and the MEL set to MI\_MEL. The value of the multicast class 1 DA is 01-80-C2-00-00-3x, where x is equal to MI\_MEL, as defined in clause 10.1 of [ITU-T G.8013]. Figure 8-113 shows the ETH\_CI\_D signal format resulting from the EDM Generation process and MCC Generation process. + +| 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | 4 | | | | | | | | | | | | | | | | | | | | +|--------------------------------------|---|---|---|---|---|---|---|-------------------|---|---|---|---|---|---|---|------------------|---|---|---|-----------|---|---|---|-----------------|---|---|---|---|---|---|---|--|--|--|--|--|--|--|--|--|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | +| DA=01-80-C2-00-00-3x, where x=MI_MEL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SA=MI_MEP_MAC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EtherType=89-02 | | | | | | | | | | | | | | | | MEL=
MI_MEL | | | | Version=0 | | | | OpCode=41 (MCC) | | | | | | | | | | | | | | | | | | | | +| Flags=0 | | | | | | | | TLV Offset = 10 | | | | | | | | OUI=00-19-A7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| OUI Continued | | | | | | | | SubOpCode=1 (EDM) | | | | | | | | MEP ID=MI_MEP_ID | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Expected Duration=MI_EDM_Duration | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| End TLV (0) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +Figure 8-113 – EDM traffic unit + +#### 8.1.20.3 EDM Reception process + +![EDM Reception process symbol diagram showing an input D entering a block labeled 'EDM Reception' which outputs MI_EDM_Received (MEP_ID, Duration).](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +``` + +graph LR + D((D)) --> ER[EDM Reception] + ER --> MER[MI_EDM_Received (MEP_ID, Duration)] + +``` + +G.8021-Y.1341(16)\_F8-114 + +EDM Reception process symbol diagram showing an input D entering a block labeled 'EDM Reception' which outputs MI\_EDM\_Received (MEP\_ID, Duration). + +Figure 8-114 – EDM Reception process + +Figure 8-114 shows the EDM Reception process symbol, and Figure 8-115 defines the behaviour. When EDM signals are received, then the MEP ID and Expected Defect Duration are extracted from the EDM signals and passed to the EMF via the MI\_EDM\_Received (MEP\_ID, Duration) signal. + +![EDM Reception behaviour flowchart showing the sequence: EDM reception -> Waiting -> D(D) -> MI_EDM_Received (MEP_ID(D), Duration(D)) -> loop back to Waiting.](467f1f3beb4da9f74ecac4c30e70c30c_img.jpg) + +``` + +graph TD + ER([EDM reception]) --> W([Waiting]) + W --> DD[/D(D)/] + DD --> MER{{MI_EDM_Received (MEP_ID(D), Duration(D))}} + MER --> W + +``` + +G.8021-Y.1341(16)\_F8-115 + +EDM Reception behaviour flowchart showing the sequence: EDM reception -> Waiting -> D(D) -> MI\_EDM\_Received (MEP\_ID(D), Duration(D)) -> loop back to Waiting. + +Figure 8-115 – EDM Reception behaviour + +NOTE – It is expected that the EMF handles the MI\_EDM\_Received (MEP\_ID, Duration) signal by unsetting MI\_CC\_Enable in the corresponding ETHx\_FT\_Sk or ETHG\_FT\_Sk function as appropriate, for the specified duration, if it has been configured to enable this functionality by the user. Further examples can be found in Appendix IX. + +## 8.2 Queueing process + +The queueing process buffers the received ETH\_CI traffic units for output (see Figure 8-116). The queueing process is also responsible for discarding the ETH\_CI traffic units if their rate at the ETH\_FP is higher than the rate that the \_AP can accommodate, as well as for maintaining PM counters for discarded frames. The queueing process is specified by reference to the queueing entities of clauses 8.6.6, 8.6.7 and 8.6.8 of [IEEE 802.1Q]. + +![Diagram of the Queueing process. A box labeled 'Queueing' has an input arrow labeled 'ETH_CI' from above and an output arrow labeled 'ETH_CI' from below. A horizontal double-headed arrow labeled 'MI_[IEEE802.1Q]' is connected to the right side of the 'Queueing' box. Below the diagram is the text 'G.8021-Y.1341(22)_F8-116'.](88fa0e6558e55b5d54f4d3029b21aabb_img.jpg) + +``` +graph TD; ETH_CI_in[ETH_CI] --> Queueing[Queueing]; Queueing --> ETH_CI_out[ETH_CI]; Queueing <--> MI_[IEEE802.1Q]; +``` + +Diagram of the Queueing process. A box labeled 'Queueing' has an input arrow labeled 'ETH\_CI' from above and an output arrow labeled 'ETH\_CI' from below. A horizontal double-headed arrow labeled 'MI\_[IEEE802.1Q]' is connected to the right side of the 'Queueing' box. Below the diagram is the text 'G.8021-Y.1341(22)\_F8-116'. + +**Figure 8-116 – Queueing process** + +NOTE – This Recommendation specifies this process by reference to [IEEE 802.1Q], and intentionally does not provide details as this functionality is well understood from the IEEE work. + +When the queueing process is not located at an [IEEE 802.1Q] bridge port and the rate at the ETH\_FP is the same as the rate at the \_AP, it can operate as a null function, i.e., present ingress ETH\_CI traffic units at egress unchanged, disregarding MI\_[IEEE 802.1Q]. + +## 8.3 Filter process + +The processing of incoming ETH\_CI traffic units corresponding to incoming Layer 2 Control Protocol (L2CP) frames is specified by reference to: + +- The [MEF 45.1] "L2CP Decision Point" when this process is located at a [MEF 45.1] "External Interface"; or +- Clause 8.6.3 of [IEEE 802.1Q] when this process is located at an [IEEE 802.1Q] bridge port. + +NOTE 1 – This Recommendation specifies this processing by reference to [IEEE 802.1Q] and [MEF 45.1], and intentionally does not provide details as this functionality is well understood from the IEEE and MEF work. + +The [ITU-T G.7710] EMF controls the processing of L2CP frames by configuring the management information to and from: + +- The filter process, i.e., MI\_FilterConfig in Figure 8-117; and +- Other processes that handle L2CP frames (e.g., the "[IEEE 802.3] processes" and "ITU-T slow protocols" processes specified in [ITU-T G.8023] that handle [IEEE 802.3]-specified "MAC Control frames" and ITU-T slow protocols, respectively). + +![Diagram of the Filter process. A box labeled 'Filter' has an input arrow labeled 'ETH_CI' from below and an output arrow labeled 'ETH_CI' from above. A horizontal double-headed arrow labeled 'MI_FilterConfig' is connected to the left side of the 'Filter' box. Below the diagram is the text 'G.8021-Y.1341(22)_F8-117'.](4c4dbc375c43addf79c26df84a24b082_img.jpg) + +``` +graph TD; ETH_CI_in[ETH_CI] --> Filter[Filter]; Filter --> ETH_CI_out[ETH_CI]; Filter <--> MI_FilterConfig; +``` + +Diagram of the Filter process. A box labeled 'Filter' has an input arrow labeled 'ETH\_CI' from below and an output arrow labeled 'ETH\_CI' from above. A horizontal double-headed arrow labeled 'MI\_FilterConfig' is connected to the left side of the 'Filter' box. Below the diagram is the text 'G.8021-Y.1341(22)\_F8-117'. + +**Figure 8-117 – Filter process** + +The filter process supports two filter actions and applies them, as configured by MI\_FilterConfig, to ETH\_CI traffic units corresponding to incoming L2CP frames that are presented to it. These two filter actions are either: + +- Discard: the ETH\_CI traffic unit is discarded by the filter process. +- Pass: the ETH\_CI traffic unit is passed unchanged through the filter process. + +The filter process passes other ETH\_CI traffic units. + +NOTE 2 – MI\_FilterConfig is configured by the EMF to trigger filtering of L2CP frames based on applicable [IEEE 802.1Q] specification or [MEF 45.1] "L2CP Service Attributes" configuration, and is not exposed to the operator as a configuration parameter of the equipment management interface. + +When the filter process is not located as described in items a) or b), it operates as a null function, i.e., it presents ingress ETH\_CI traffic units at egress unchanged, disregarding MI\_FilterConfig. + +## 8.4 Replicate process + +The replicate process is specified by reference to clause 8.5.1 of [IEEE 802.1Q] and is equivalently decomposed in sink and source processes in Figure 8-118 to fit the description methodology of clause 5. + +![Diagram of Replicate processes showing Sink Replicate and Source Replicate blocks with their respective inputs and outputs.](235f4d3bfb16ff9c2ab5776a240248a8_img.jpg) + +The diagram illustrates the flow of ETH\_CI traffic units through Sink and Source Replicate processes. On the left, the Sink Replicate block receives an input ETH\_CI traffic unit from below. It has three outputs: one pointing up to (To ETH\_TFP) ETH\_CI, one pointing up to (To filter) ETH\_CI, and one pointing right to the Source Replicate block. The output to the Source Replicate block is labeled (ETH\_TF\_PP), (ETH\_PI), and (ETHF\_PP). The Source Replicate block on the right has two inputs from above: (From ETH\_TFP) ETH\_CI and (From queueing) ETH\_CI. It has three outputs: one pointing down to ETH\_CI, one pointing left to the Sink Replicate block (also labeled (ETH\_TF\_PP), (ETH\_PI), and (ETHF\_PP)), and one pointing up to (To filter) ETH\_CI. A small label G.8021-Y.1341(18)\_F8-118 is at the bottom right. + +Diagram of Replicate processes showing Sink Replicate and Source Replicate blocks with their respective inputs and outputs. + +**Figure 8-118 – Replicate processes** + +NOTE – This Recommendation specifies this process by reference to [IEEE 802.1Q], and intentionally does not provide details as this functionality is well understood from the IEEE work. + +The /ETH\_A\_So replicate process replicates ETH\_CI traffic units received on the input from: + +- The queueing process and delivers them: + - To the server-specific processes; and + - As ETH\_PI, to the ETHF\_PP interface; and +- The ETH\_TFP and delivers them: + - To the server-specific processes; and + - As ETH\_PI, to the ETHTF\_PP interface. + +The /ETH\_A\_Sk replicate process: + +- Replicates ETH\_CI traffic units received on the input from the server-specific processes and delivers them to: + - The ETH\_TFP; and + - The filter process; and +- Delivers ETH\_PI traffic units received on the input from the ETHF\_PP interface to the ETH\_TFP as ETH\_CI traffic units; and +- Delivers ETH\_PI traffic units received on the input from the ETHTF\_PP to the filter process as ETH\_CI traffic units. + +When either the ETH\_TFP or the ETH\_FP are unconnected, the replicate process operates as a null function, i.e. it presents ingress ETH\_CI traffic units at egress unchanged, bypassing ETHF\_PP and ETHTF\_PP interfaces therefore performing only items a) i, b) i, and c). + +## 8.5 MAC length check process + +The MAC length check process is specified by reference to [IEEE 802.3] content related to checking MAC frame length. + +NOTE – This Recommendation specifies this process by reference to [IEEE 802.3], and intentionally does not provide details as this functionality is well understood from the IEEE work. + +## 8.6 Server-specific processes + +### 8.6.1 802.3 MAC FCS generation process + +![Flowchart of the 802.3 MAC FCS generation process. An arrow labeled 'ETH_CI' points down to a box labeled 'MAC FCS generation'. An arrow points down from this box to the text 'MAC frame'. Below the text is the identifier 'G.8021-Y.1341(22)_F8-119'.](ff06304def736f4144f7bdd2957b9e22_img.jpg) + +``` +graph TD; A[ETH_CI] --> B[MAC FCS generation]; B --> C[MAC frame]; +``` + +Flowchart of the 802.3 MAC FCS generation process. An arrow labeled 'ETH\_CI' points down to a box labeled 'MAC FCS generation'. An arrow points down from this box to the text 'MAC frame'. Below the text is the identifier 'G.8021-Y.1341(22)\_F8-119'. + +Figure 8-119 – 802.3 MAC FCS generation process + +The MAC FCS is calculated over the received ETH\_CI traffic units and is inserted into the MAC FCS fields of the transmitted MAC frames as defined in clause 4.2.3 of [IEEE 802.3]. Figure 8-119 shows the MAC FCS generation process. + +NOTE – This Recommendation specifies this process by reference to [IEEE 802.3] and intentionally does not provide details, as this functionality is well understood from the IEEE work. + +### 8.6.2 802.3 MAC FCS check process + +![Flowchart of the 802.3 MAC FCS check process. An arrow labeled 'MAC frame' points up to a box labeled 'MAC FCS supervision'. An arrow points up from this box to the text 'ETH_CI'. An arrow points right from the 'MAC FCS supervision' box to a box labeled 'Performance monitoring', with the label 'FrameCheckSequenceErrors' above it. An arrow points right from the 'Performance monitoring' box to the text 'pFCSErrors'. Below the 'Performance monitoring' box is the identifier 'G.8021-Y.1341(22)_F8-120'.](db6adf216c948c2b545e513aba13a16a_img.jpg) + +``` +graph TD; A[MAC frame] --> B[MAC FCS supervision]; B --> C[ETH_CI]; B --> D[Performance monitoring]; D --> E[pFCSErrors]; +``` + +Flowchart of the 802.3 MAC FCS check process. An arrow labeled 'MAC frame' points up to a box labeled 'MAC FCS supervision'. An arrow points up from this box to the text 'ETH\_CI'. An arrow points right from the 'MAC FCS supervision' box to a box labeled 'Performance monitoring', with the label 'FrameCheckSequenceErrors' above it. An arrow points right from the 'Performance monitoring' box to the text 'pFCSErrors'. Below the 'Performance monitoring' box is the identifier 'G.8021-Y.1341(22)\_F8-120'. + +Figure 8-120 – 802.3 MAC FCS check process + +The MAC FCS is calculated over the received MAC frames and checked as specified in clause 4.2.4.1.2 of [IEEE 802.3]. If errors are detected, errored frames are indicated by FrameCheckSequenceErrors. Figure 8-120 shows the MAC FCS check process. + +NOTE – This Recommendation specifies this process by reference to [IEEE 802.3], and intentionally does not provide details as this functionality is well understood from the IEEE work. + +### 8.6.3 Link quality supervision + +Counts of transmitted and received octets and frames are maintained in /ETH\_A functions per the requirements of clause 30 of [IEEE 802.3]. Discarded jabber frames are counted in the M-AI/ETH\_A\_So function defined in [ITU-T G.8023]. + +NOTE – This Recommendation specifies this process by reference to [IEEE 802.3] and intentionally does not provide details, as this functionality is well understood from the IEEE work. + +### 8.6.4 ETH-specific GFP-F process + +#### 8.6.4.1 ETH-specific GFP-F source process + +See clause 8.5.4.1.1 of [ITU-T G.806]. GFP pFCS generation is disabled (FCSenable=false). The user payload identifier (UPI) value for frame-mapped Ethernet shall be inserted (as defined in Table 6-3 of [ITU-T G.7041]). The Ethernet frames are inserted into the client payload information field of the GFP-F frames according to clause 7.1 of [ITU-T G.7041]. Client management frame insertion is governed by the consequent actions. + +##### Consequent actions + +aCSF-RDI $\leftarrow$ CI\_SSFrdi and CSFrdifdiEnable and CSFEnable + +aCSF-FDI $\leftarrow$ CI\_SSFfdi and CSFrdifdiEnable and CSFEnable + +aCSF-LOS $\leftarrow$ CI\_SSF and CSFEnable + +#### 8.6.4.2 ETH-specific GFP-F sink process + +See clause 8.5.4.1.2 of [ITU-T G.806]. GFP pFCS checking, GFP p\_FCSerror, p\_FDis are not supported (FCSdiscard=false). The UPI value for frame-mapped Ethernet shall be expected (as defined in Table 6-3 of [ITU-T G.7041]). The Ethernet frames are extracted from the client payload information field of the GFP-F frames according to clause 7.1 of [ITU-T G.7041]. The generic defects and consequent actions are extended as follows. + +##### Defects + +dCSF-RDI: GFP client signal fail-remote defect indication (dCSF-RDI) is raised when a GFP client management frame with the RDI UPI (as defined in Table 6-4 of [ITU-T G.7041]) is received. dCSF-RDI is cleared when no such GFP client management frame is received in $N \times 1000$ ms (a value of 3 is suggested for N), a valid GFP client data frame is received, or a GFP client management frame with the DCI UPI is received. + +dCSF-FDI: GFP client signal fail-forward defect indication (dCSF-FDI) is raised when a GFP client management frame with the FDI UPI (as defined in Table 6-4 of [ITU-T G.7041]) is received. dCSF-FDI is cleared when no such GFP client management frame is received in $N \times 1000$ ms (a value of 3 is suggested for N), a valid GFP client data frame is received, or a GFP client management frame with the DCI UPI is received. + +dCSF-LOS: GFP client signal fail-loss of signal (dCSF-LOS) is raised when a GFP client management frame with the LOS UPI (as defined in Table 6-4 of [ITU-T G.7041]) is received. dCSF-LOS is cleared when no such GFP client management frame is received in $N \times 1000$ ms (a value of 3 is suggested for N), a valid GFP client data frame is received, or a GFP client management frame with the DCI UPI is received. + +##### Consequent actions + +aSSFrdi $\leftarrow$ dCSF-RDI and CSFrdifdiEnable + +aSSFfdi $\leftarrow$ dCSF-FDI and CSFrdifdiEnable + +aSSF $\leftarrow$ GFP\_SF or dUPM or dCSF-LOS + +##### Defect correlations + +cCSF $\leftarrow$ (dCSF-RDI or dCSF-FDI or dCSF-LOS) and (not dUPM) and (not GFP\_SF) and CSF\_Reported. + +The GFP\_SF term refers collectively to the set of defects detected in the Common GFP-F sink process (see clause 8.5.3.2 of [ITU-T G.806]), the server-specific GFP-F sink process (see clause 8.5.2.2 of [ITU-T G.806]), or the server-specific process (see clause 11) with the consequent action of aGFP\_SF. This includes dEXM, dLFD, any server-specific defects related to the GFP-F mapping, and server layer trail signal fail (TSF). + +# 9 Ethernet MAC layer (ETH) functions + +Figure 1-1 illustrates all the ETH layer network, server and client adaptation functions. The information crossing the ETH flow point (ETH\_FP) is referred to as the ETH characteristic information (ETH\_CI). The information crossing the ETH access point (ETH\_AP) is referred to as ETH adapted information (ETH\_AI). + +Figure 9-1 provides a view of the functions used to support ETH OAM from the perspective of the hierarchy of MEGs that can be created by expanding an ETH\_FP. The 'ETHx Sublayer' notation used top to bottom of Figure 9-1 corresponds to ETH2 (S-VLAN tagged frames), ETH1 (C-VLAN-tagged frames), and ETH0 (untagged frames), respectively, in clause 7.2.6 of [ITU-T G.8010] and does not represent an actual sublayer in the [ITU-T G.806] sense of the term. Each ETHx Sublayer can support an NCM (network connection monitoring) MEP and up to 7 TCM (tandem connection monitoring) MEPs. + +![Figure 9-1 – ETH sublayering diagram showing the flow of data through various sublayers and functions.](ea40403ee09ad7bcb209382495f36547_img.jpg) + +The diagram illustrates the ETH sublayering process across four layers, showing the flow of data from a client layer to a server layer through various sublayers and functions. + +- Client layer CTP:** The process starts with an **ETH TTP** (Client layer CTP) containing the following stack: + - ETH/ + - ETH + - NCM MEP + - ETHD/ ETH + - ETHDe +- ETHx Sublayer:** The data flows into the first **ETHx Sublayer**. This sublayer contains four parallel paths: + - TCM MEP:** ETH/ ETH → ETH → ETHD/ ETH → ETHDe + - ETHG/ ETH:** ETHG/ ETH → ETH → ETHD/ ETH → ETHDe + - Group MIP:** ETHD/ ETH → ETHD/ ETH → ETHD/ ETH → ETHD/ ETH + - MIP:** ETHD/ ETH → ETHD/ ETH → ETHD/ ETH → ETHD/ ETH + All four paths converge into a **CTP pool**. A **TCS** (Traffic Control System) is connected to the CTP pool. The label **6x** is present above the first path. +- Sublayer boundary:** A dashed line separates the first sublayer from the second. +- ETH CTP:** The data flows into an **ETH CTP** containing the stack: + - ETH/ ETH-m + - ETH + - NCM MEP + - ETHD/ ETH + - ETHDe +- ETHx Sublayer:** The data flows into the second **ETHx Sublayer**, which is identical in structure to the first, with four parallel paths (TCM MEP, ETHG/ ETH, Group MIP, MIP) converging into a **CTP pool** and connected to a **TCS**. The label **6x** is present above the first path. +- Sublayer boundary:** A dashed line separates the second sublayer from the third. +- ETH CTP:** The data flows into another **ETH CTP** containing the stack: + - ETH/ ETH-m + - ETH + - NCM MEP + - ETHD/ ETH + - ETHDe +- ETHx Sublayer:** The data flows into the third **ETHx Sublayer**. This sublayer contains two parallel paths: + - TCM MEP:** ETH/ ETH → ETH → ETHD/ ETH → ETHDe + - MIP:** ETHD/ ETH → ETHD/ ETH → ETHD/ ETH → ETHD/ ETH + These paths converge into a **CTP pool** connected to a **TCS**. The label **6x** is present above the first path. +- Server layer TTP:** The data flows into the **Server layer TTP** containing the stack: + - ETH CTP + - / ETH + - + +Vertical arrows on the left indicate the flow direction between layers. Horizontal arrows indicate flow between sublayers and CTPs. Dashed lines represent **Layer boundary** or **Sublayer boundary**. + +Figure 9-1 – ETH sublayering diagram showing the flow of data through various sublayers and functions. + +G.8021-Y.1341(16)\_F9-1 + +**Figure 9-1 – ETH sublayering** + +Figure 9-1 also illustrates the basic flow termination and adaptation functions involved and the possible ordering of these functions. The ETHx/ETH-m functions multiplex ETH\_CI streams. The ETHx and ETHG flow termination functions insert and extract the proactive [ITU-T G.803/Y.1731] OAM information (e.g., CCM). The ETHDy flow termination functions insert and extract the on-demand [ITU-T G.803/Y.1731] OAM information (e.g., LBM, LTM). The ETHx/ETH and ETHG/ETH adaptation functions insert and extract the administrative and control [ITU-T G.803/Y.1731] OAM information (e.g., LCK, APS). + +Any combination that can be constructed by following the directions in the figure is allowed. Some recursion is allowed as indicated by the arrows upwards; the number next to the arrow defines the number of recursions allowed. + +## ETH characteristic information + +The ETH\_CI is a stream of ETH\_CI traffic units complemented with ETH\_CI\_P, ETH\_CI\_DE, ETH\_CI\_SSF and ETH\_CI\_SSD signals. The ETH\_CI traffic units define the ETH\_CI\_D signal. The ETH\_CI traffic units are illustrated in Figure 9-2. The ETH\_CI traffic unit is defined in clause 6.2.1 of [ITU-T G.8012]. + +![Diagram of ETH characteristic information showing the structure of ETH_CI traffic units. At the top, a sequence of four boxes labeled 'ETH_CI traffic unit' is shown, with a dashed line labeled 'ETH_CI_D' pointing to the first. Below this, a dashed arrow points to a detailed view of the traffic unit structure. The structure consists of three stacked rectangular boxes. The top box is labeled 'MSDU' and has two small boxes on the left labeled 'DA' and 'SA'. The middle box is labeled 'Length/Type', 'Payload', and 'PAD'. The bottom box is labeled 'OAM EtherType', 'Payload', and 'PAD'. To the left of the middle and bottom boxes, labels 'ETH_CI Data traffic unit' and 'ETH_CI OAM traffic unit' are present, with dashed lines pointing to their respective boxes. A small text 'G.8021-Y.1341(22)_F9-2' is at the bottom right.](c21bad844b5cb6026c067a1f43ce67c3_img.jpg) + +Diagram of ETH characteristic information showing the structure of ETH\_CI traffic units. At the top, a sequence of four boxes labeled 'ETH\_CI traffic unit' is shown, with a dashed line labeled 'ETH\_CI\_D' pointing to the first. Below this, a dashed arrow points to a detailed view of the traffic unit structure. The structure consists of three stacked rectangular boxes. The top box is labeled 'MSDU' and has two small boxes on the left labeled 'DA' and 'SA'. The middle box is labeled 'Length/Type', 'Payload', and 'PAD'. The bottom box is labeled 'OAM EtherType', 'Payload', and 'PAD'. To the left of the middle and bottom boxes, labels 'ETH\_CI Data traffic unit' and 'ETH\_CI OAM traffic unit' are present, with dashed lines pointing to their respective boxes. A small text 'G.8021-Y.1341(22)\_F9-2' is at the bottom right. + +**Figure 9-2 – ETH characteristic information** + +There are two types of ETH\_CI traffic units: data traffic units and OAM traffic units. If the Length/Type field equals the OAM EtherType value (0x8902 as defined in clause 10 of [ITU-T G.8013]) the ETH\_CI traffic unit is an ETH\_CI OAM traffic unit, otherwise it is an ETH\_CI data traffic unit. + +The payload field of an ETH\_CI OAM traffic unit is defined in clause 9 of [ITU-T G.8013]. + +## Functions for traffic units + +The following functions are used in this Recommendation to indicate the various fields of a traffic unit: + +- SA(Traffic\_Unit): returns the value of the SA field in the traffic unit. +- DA(Traffic\_Unit): returns the value of the DA field in the traffic unit. +- Etype(Traffic\_Unit): returns the value of the EtherType field in the traffic unit. +- OPC(OAM Traffic\_Unit): returns the value of the OpCode field in the OAM traffic unit; returns an undefined value if the traffic unit is not an OAM traffic unit. +- MEL(OAM Traffic\_Unit): returns the value of the maintenance entity group level field in the OAM traffic unit; returns an undefined value if the traffic unit is not an OAM traffic unit. + +Flags(OAM Traffic\_Unit): returns the value of the flags field in the OAM traffic unit; returns an undefined value if the traffic unit is not an OAM traffic unit. + +NOTE – The ETH\_CI contains no VID field as the ETH\_CI is defined per virtual local area network (VLAN). + +## ETH adapted information + +The ETH\_AI is a stream of ETH\_AI traffic units complemented with the following signals: ETH\_AI\_P, ETH\_AI\_DE, ETH\_AI\_TSF and ETH\_AI\_TSD. The ETH\_AI traffic units define the ETH\_AI\_D signal as illustrated in Figure 9-3. + +![Diagram showing the structure of ETH_AI traffic units. At the top, a sequence of four 'ETH_AI traffic unit' boxes is shown, with a dashed line labeled 'ETH_AI_D' pointing to the first. Below this, four detailed traffic unit structures are shown, each with a dashed line connecting it to one of the boxes above. 1. 'Untagged ETH_AI Data traffic unit': consists of DA, SA, and MSDU. 2. 'Tagged ETH_AI Data traffic unit': consists of Tag, Length/Type, Payload, and PAD. 3. 'Untagged ETH_AI OAM traffic unit': consists of OAM EtherType, Payload, and PAD. 4. 'Tagged ETH_AI OAM traffic unit': consists of Tag, OAM EtherType, Payload, and PAD. The diagram uses dashed lines to show the mapping from the high-level traffic units to their internal structures.](b0b9bc3067d012eb2fa3539217b9c34d_img.jpg) + +Diagram showing the structure of ETH\_AI traffic units. At the top, a sequence of four 'ETH\_AI traffic unit' boxes is shown, with a dashed line labeled 'ETH\_AI\_D' pointing to the first. Below this, four detailed traffic unit structures are shown, each with a dashed line connecting it to one of the boxes above. 1. 'Untagged ETH\_AI Data traffic unit': consists of DA, SA, and MSDU. 2. 'Tagged ETH\_AI Data traffic unit': consists of Tag, Length/Type, Payload, and PAD. 3. 'Untagged ETH\_AI OAM traffic unit': consists of OAM EtherType, Payload, and PAD. 4. 'Tagged ETH\_AI OAM traffic unit': consists of Tag, OAM EtherType, Payload, and PAD. The diagram uses dashed lines to show the mapping from the high-level traffic units to their internal structures. + +G.8021-Y.1341(22)\_F9-3 + +**Figure 9-3 – ETH adapted information** + +Untagged ETH\_AI traffic units are the same as ETH\_CI traffic units. + +Tagged ETH\_AI traffic units are the same as ETH\_CI traffic units except that a tag (formatted as defined in clause 9.3 of [IEEE 802.1Q]) is inserted between SA and MSDU. + +In this Recommendation, "tagged" means that the Length/Type field equals either the customer VLAN tag value (0x81-00) or the service VLAN tag value (0x88-a8), both defined in clause 9.5 of [IEEE 802.1Q]. + +The ETH\_CI\_P and ETH\_CI\_DE signals respectively correspond to the priority and drop\_eligible parameters of [IEEE 802.1Q]. These parameters are encoded, as specified in clause 6.9.3 of [IEEE 802.1Q], in the priority code point field and potentially in the drop eligible indicator field of a VLAN tag, as specified in clause 9.6 of [IEEE 802.1Q]. + +All ETH\_AI traffic units may come from one ETH\_FP or different ETH\_FPs (in the case of multiplexing in ETHx/ETH-m\_A function). In the latter case the VID field value specified in clause 9.6 of [IEEE 802.1Q] is used to identify the ETH\_FP where the traffic unit is associated. + +Because of the stacking of ETH sublayers, ETH\_CI of a client ETH sublayer is encapsulated in ETH\_AI to be transferred via a server ETH sublayer. Figure 9-4 shows an ETH\_CI OAM traffic unit encapsulated in an ETH\_AI data traffic unit. The grey fields constitute the original ETH\_CI OAM traffic unit. The encapsulating traffic unit is no longer an OAM traffic unit, but a tagged traffic unit. Adding a VLAN tag hides the OAM information, and transforms an ETH\_CI OAM traffic unit into a tagged ETH\_AI data traffic unit. + +![](fda85db2e355bb8e3edcd5a74bf3d673_img.jpg) + +| | | | | | | +|----|----|-----|------------------|---------|-----| +| DA | SA | Tag | OAM
EtherType | Payload | PAD | +|----|----|-----|------------------|---------|-----| + +G.8021-Y.1341(22)\_F9-4 + +**Figure 9-4 – Tagged ETH\_AI carrying ETH\_CI OAM** + +This ETH\_AI tagged traffic unit will be transformed into an ETH\_CI data traffic unit by the ETHx\_FT source function, resulting in an ETH\_CI data traffic unit carrying a client layer ETH\_CI OAM traffic unit. + +## 9.1 ETH connection (ETH\_C) function + +The information flow and processing of the ETH\_C function is defined with reference to Figures 9-5 and 9-6. The ETH\_C function connects ETH characteristic information from its input ports to its output ports. As the process does not affect the nature of characteristic information, the reference points on either side of the ETH\_C function are the same as illustrated in Figure 9-5. + +The connection process is unidirectional and as such no differentiation in sink and source is required. + +In addition, the ETH\_C function supports the following protection schemes: + +- 1+1 unidirectional SNC/S protection without APS protocol. +- 1+1 unidirectional SNC/S protection with an APS protocol. +- 1+1 bidirectional SNC/S protection with an APS protocol. +- 1:1 bidirectional SNC/S protection with an APS protocol. +- Ring protection with an APS protocol. + +The protection functionality is described in clauses 9.1.2 and 9.1.3. + +NOTE 1 – The SNC/S protection processes have a dedicated sink and source behaviour. + +#### Symbol + +The ETH connection function, as shown in Figure 9-5, forwards ETH\_CI signals at its input ports to its output ports. + +![Diagram of the ETH_C symbol. It shows a central oval labeled 'ETH'. On the left, there are two pairs of vertical arrows pointing up and down, each labeled 'ETH_FP'. On the right, there is one pair of vertical arrows pointing up and down, labeled 'ETH_FP'. Below the right pair, there is a horizontal arrow pointing left towards the oval, labeled 'ETH_C_MP'. Dashed lines connect the top and bottom ETH_FP pairs on the left, and the top and bottom ETH_FP pair on the right. A small text 'G.8021-Y.1341(12)_F9-5' is at the bottom right.](450946c7ffef8b7fce38c312987a46e4_img.jpg) + +Diagram of the ETH\_C symbol. It shows a central oval labeled 'ETH'. On the left, there are two pairs of vertical arrows pointing up and down, each labeled 'ETH\_FP'. On the right, there is one pair of vertical arrows pointing up and down, labeled 'ETH\_FP'. Below the right pair, there is a horizontal arrow pointing left towards the oval, labeled 'ETH\_C\_MP'. Dashed lines connect the top and bottom ETH\_FP pairs on the left, and the top and bottom ETH\_FP pair on the right. A small text 'G.8021-Y.1341(12)\_F9-5' is at the bottom right. + +**Figure 9-5 – ETH\_C symbol** + +The actual forwarding is performed using flow forwarding processes ETH\_FF interconnecting the input and output ports. + +#### Interfaces + +Table 9-1 – ETH\_C interfaces + +| Inputs | Outputs | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Per ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_APS
ETH_CI_SSF
ETH_CI_SSD

ETH_C_MP per flow forwarding process:
ETH_C_MI_FF_[IEEE 802.1Q]

ETH_C_MP per SNC/S protection process:
ETH_C_MI_PS_WorkingPortId
ETH_C_MI_PS_ProtectionPortId
ETH_C_MI_PS_ProfType
ETH_C_MI_PS_OperType
ETH_C_MI_PS_HoTime
ETH_C_MI_PS_WTR
ETH_C_MI_PS_ExtCMD
ETH_C_MI_PS_BridgeType
ETH_C_MI_PS_SD_Protection

ETH_C_MP per Ring protection process:
ETH_C_MI_RAPS_PortIds[0..1]
ETH_C_MI_RAPS_RPL_Owner_Node
ETH_C_MI_RAPS_RPL_Neighbour_Node
ETH_C_MI_RAPS_Propagate_TC[1..M]
ETH_C_MI_RAPS_Compatible_Version
ETH_C_MI_RAPS_Revertive
ETH_C_MI_RAPS_Sub_Ring_Without_
Virtual_Channel
ETH_C_MI_RAPS_HoTime
ETH_C_MI_RAPS_WTR
ETH_C_MI_RAPS_GuardTime
ETH_C_MI_RAPS_ExtCMD
ETH_C_MI_RAPS_RingID | Per ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_APS

ETH_C_MP per SNC/S protection process:
ETH_C_MI_cFOP-PM
ETH_C_MI_cFOP-CM
ETH_C_MI_cFOP-NR
ETH_C_MI_cFOP-TO
ETH_C_MI_PS_RequestState
ETH_C_MI_PS_RequestedSignal
ETH_C_MI_PS_BridgedSignal
ETH_C_MP per Ring protection process:
ETH_C_MI_cFOP-PM
ETH_C_MI_cFOP-TO[0..1]
ETH_C_MI_RAPS_NodeState
ETH_C_MI_RAPS_PortState[0..1] | + +### Processes + +The processes associated with the ETH\_C function are depicted in Figure 9-6. + +ETH\_CI traffic units are forwarded between input and output ETH flow points by means of an ETH flow forwarding process. ETH flow points may be allocated within a protection group. + +NOTE 2 – Neither the number of input/output signals to the connection function, nor the connectivity, is specified in this Recommendation. That is a property of individual network elements. + +![Diagram of an ETH connection function with multiple ETH_FF processes. A central box labeled 'ETH connection' contains two 'ETH_FF' boxes. On the left, an 'ETH_C_MI' interface is shown. Multiple 'ETH_CI' signals, each with 'D', 'DE', and 'P' components, enter from the top and exit through the bottom via the 'ETH_FF' processes. The diagram is labeled G.8021-Y.1341(22)_F9-6.](92e26d86c5a582766cb9afdbd2c1aee7_img.jpg) + +Diagram of an ETH connection function with multiple ETH\_FF processes. A central box labeled 'ETH connection' contains two 'ETH\_FF' boxes. On the left, an 'ETH\_C\_MI' interface is shown. Multiple 'ETH\_CI' signals, each with 'D', 'DE', and 'P' components, enter from the top and exit through the bottom via the 'ETH\_FF' processes. The diagram is labeled G.8021-Y.1341(22)\_F9-6. + +**Figure 9-6 – ETH connection function with ETH\_FF processes** + +The flow forwarding process ETH\_FF is described in clause 9.1.1. + +**Defects** None. + +**Consequent actions** None. + +**Defect correlations** None. + +**Performance monitoring** None. + +### 9.1.1 ETH flow forwarding (ETH\_FF) process + +The ETH flow forwarding process in Figure 9-7 forwards ETH\_CI signals at its input ports to its output ports. This process applies to the flow of ETH\_CI signals that belong to one VLAN and is specified by reference to clauses 8.6, 8.7, 8.8 of [IEEE 802.1Q]. + +NOTE 1 – Since the functionality defined in clauses 8.6, 8.7, 8.8 of [IEEE 802.1Q] applies to all VLANs and also includes queueing and filtering, it maps to the functionality of the set of ETH\_FF processes within the ETH\_C and the queueing and filtering processes defined in clauses 8.2 and 8.3, respectively. + +In addition, transport equipment may rely on other active topology enforcement mechanisms than those mentioned in clause 8.6.1 of [IEEE 802.1Q]. This Recommendation specifies in clauses 9.1.2 and 9.1.3 the processes supporting two such mechanisms: Ethernet linear protection switching as specified in [ITU-T G.8031] and Ethernet ring protection switching as specified in [ITU-T G.8032]. + +![Diagram of the ETH flow forwarding process. An 'ETH_CI' signal enters a box labeled 'ETH_FF' from the top. A 'MI_FF_[IEEE802.1Q]' interface is connected to the left side of the box. An 'ETH_CI' signal exits from the bottom of the box. The diagram is labeled G.8021-Y.1341(22)_F9-7.](40ab4bd21d0b63caa80d90a50f44485e_img.jpg) + +Diagram of the ETH flow forwarding process. An 'ETH\_CI' signal enters a box labeled 'ETH\_FF' from the top. A 'MI\_FF\_[IEEE802.1Q]' interface is connected to the left side of the box. An 'ETH\_CI' signal exits from the bottom of the box. The diagram is labeled G.8021-Y.1341(22)\_F9-7. + +**Figure 9-7 – ETH flow forwarding process** + +NOTE 2 – This Recommendation specifies this process by reference to [IEEE 802.1Q], and intentionally does not provide details as this functionality is well understood from the IEEE work. + +### 9.1.2 Subnetwork connection protection process + +SNC protection with sublayer monitoring based on TCM is supported. + +Figure 9-8 shows the involved atomic functions in SNC/S. The ETHx\_FT\_Sk provides the TSF/TSD protection switching criterion via the ETHx/ETH\_A\_Sk function (SSF/SSD) to the ETH\_C function. + +![Figure 9-8: SNC/S atomic functions diagram. At the top, an oval labeled 'ETH' contains 'Normal', 'Working', and 'Protection' sections. Above the 'Normal' section is 'ETH_CI_D/P/DE'. Below the 'Working' section, a trapezoid labeled 'ETHx/ETH' is connected to 'ETHx' via 'ETH_AI_TSF/TSD' and 'ETH_AI_D/P/DE'. Above this 'ETHx/ETH' are 'ETH_CI_SSF/SSD' and 'ETH_CI_D/P/DE'. Below the 'Protection' section, another 'ETHx/ETH' trapezoid is connected to 'ETHx' via 'ETH_AI_D/P/DE'. Above this 'ETHx/ETH' are 'ETH_CI_APS' and 'ETH_CI_D/P/DE'. To the right of the 'Protection' section, a third 'ETHx/ETH' trapezoid is connected to 'ETHx' via 'ETH_AI_TSF/TSD' and 'ETH_AI_D/P/DE'. Above this 'ETHx/ETH' are 'ETH_CI_SSF/SSD/APS' and 'ETH_CI_D/P/DE'. Arrows indicate signal flow between these components and the 'ETH' oval. A label 'G.8021-Y.1341(22)_F9-8' is at the bottom right.](6ca842602b0473809416a9cf0d4106a4_img.jpg) + +Figure 9-8: SNC/S atomic functions diagram. At the top, an oval labeled 'ETH' contains 'Normal', 'Working', and 'Protection' sections. Above the 'Normal' section is 'ETH\_CI\_D/P/DE'. Below the 'Working' section, a trapezoid labeled 'ETHx/ETH' is connected to 'ETHx' via 'ETH\_AI\_TSF/TSD' and 'ETH\_AI\_D/P/DE'. Above this 'ETHx/ETH' are 'ETH\_CI\_SSF/SSD' and 'ETH\_CI\_D/P/DE'. Below the 'Protection' section, another 'ETHx/ETH' trapezoid is connected to 'ETHx' via 'ETH\_AI\_D/P/DE'. Above this 'ETHx/ETH' are 'ETH\_CI\_APS' and 'ETH\_CI\_D/P/DE'. To the right of the 'Protection' section, a third 'ETHx/ETH' trapezoid is connected to 'ETHx' via 'ETH\_AI\_TSF/TSD' and 'ETH\_AI\_D/P/DE'. Above this 'ETHx/ETH' are 'ETH\_CI\_SSF/SSD/APS' and 'ETH\_CI\_D/P/DE'. Arrows indicate signal flow between these components and the 'ETH' oval. A label 'G.8021-Y.1341(22)\_F9-8' is at the bottom right. + +**Figure 9-8 – SNC/S atomic functions** + +NOTE 1 – Since SNC/S is ETH subnetwork protection with sublayer monitoring, ETHx flow termination and ETHx/ETH adaptation functions in Figure 9-8 correspond to ETHT (tandem connection) sublayer where this abbreviation is described in Amendment 1 to [ITU-T G.8010]. + +The protection functions at both ends operate the same way, by monitoring the working and protection subnetwork connections for defects, evaluating the system status taking into consideration the priorities of defect conditions and of external switch requests, and switching the appropriate subnetwork flow point (i.e., working or protection) to the protected (sub)network flow point. + +The signal flows associated with the ETH\_C SNC protection process are described with reference to Figure 9-9. The protection process receives control parameters and external switch requests at the MP reference point. + +![Figure 9-9: SNC/S protection process diagram. A large rectangle contains the 'SNC protection process'. Inside, there are two boxes: 'Selector' and 'Bridge', each with 'W' (Working) and 'P' (Protection) sub-sections. Above the 'Normal' section is 'ETH_CI_D/P/DE'. To the left, 'ETH_CI_MI_PS' points to the 'Selector'. Below the 'Selector' are 'ETH_CI_D/P/DE' and 'ETH_CI_SSF/SSD'. Below the 'Bridge' are 'ETH_CI_D/P/DE/APS' and 'ETH_CI_SSF/SSD'. Arrows indicate signal flow between these components and the 'SNC protection process' box. A label 'G.8021-Y.1341(22)_F9-9' is at the bottom right.](dd8c4eb490876d1c18169c84d877ef32_img.jpg) + +Figure 9-9: SNC/S protection process diagram. A large rectangle contains the 'SNC protection process'. Inside, there are two boxes: 'Selector' and 'Bridge', each with 'W' (Working) and 'P' (Protection) sub-sections. Above the 'Normal' section is 'ETH\_CI\_D/P/DE'. To the left, 'ETH\_CI\_MI\_PS' points to the 'Selector'. Below the 'Selector' are 'ETH\_CI\_D/P/DE' and 'ETH\_CI\_SSF/SSD'. Below the 'Bridge' are 'ETH\_CI\_D/P/DE/APS' and 'ETH\_CI\_SSF/SSD'. Arrows indicate signal flow between these components and the 'SNC protection process' box. A label 'G.8021-Y.1341(22)\_F9-9' is at the bottom right. + +**Figure 9-9 – SNC/S protection process** + +#### *Source direction* + +For a 1+1 architecture, the CI coming from the normal (protected) ETH\_FP is bridged permanently to both the working and protection ETH\_FP. + +For a 1:1 architecture, the CI coming from the normal (protected) ETH\_FP is switched to either the working or the protection ETH\_FP. A switch-over from working to protection ETH\_FP or vice versa is initiated by the switch initiation criteria defined below. + +#### *Sink direction* + +For a 1+1 or 1:1 architecture, the CI coming from either the working or protection ETH\_FP is switched to the normal (protected) ETH\_FP. A switch-over from working to protection ETH\_FP or vice versa is initiated by the switch initiation criteria defined below. + +#### *Switch initiation criteria* + +Automatic protection switching is based on the defect conditions of the working and protection (sub)network connections, for SNC/S protection server signal fail (SSF) and server signal degrade (SSD). + +In order to allow interworking between nested protection schemes, a hold-off timer is provided. The hold-off timer delays switch initiation, in case of signal fail, in order to allow a nested protection to react and clear the fault condition. The hold-off timer is started by the activation of signal fail and runs for the hold-off time. Protection switching is only initiated if signal fail is still present at the end of the hold-off time. The hold-off time shall be provisionable between 0 and 10 s in steps of 100 ms; this is defined in clause 11.12 of [ITU-T G.8031]. + +Protection switching can also be initiated by external switch commands received via the MP or a request from the far end via the received ETH\_CI\_APS. Depending on the mode of operation, internal states (e.g., wait-to-restore) may also affect a switch-over. + +See the switching algorithm described in [ITU-T G.8031]. + +#### *Switching time* + +Refer to [ITU-T G.8031]. + +#### *Switch restoration* + +In the revertive mode of operation, the protected signal shall be switched back from the protection (sub)network connection to the working (sub)network connection when the working (sub)network connection has recovered from the fault. + +To prevent frequent operation of the protection switch due to an intermittent fault, a failed working (sub)network connection must become fault-free for a certain period of time before it is used again. This period, called the wait-to-restore (WTR) period, should be of the order of 5-12 minutes and should be capable of being set. The WTR is defined in clause 11.13 of [ITU-T G.8031]. + +In the non-revertive mode of operation no switch back to the working (sub)network connection is performed when it has recovered from the fault. + +#### *Configuration* + +The following configuration parameters are defined in [ITU-T G.8031]: + +- ETH\_C\_MI\_PS\_WorkingPortId associates the working port to a set of ETH flow points, one ETH flow point for each ETH\_FF process controlled by the SNC/S control process. +- ETH\_C\_MI\_PS\_ProtectionPortId associates the protection port to a set of ETH flow points, one ETH flow point for each ETH\_FF process controlled by the SNC/S control process. +- ETH\_C\_MI\_PS\_ProtType configures the protection type. +- ETH\_C\_MI\_PS\_OperType configures to be in revertive mode. +- ETH\_C\_MI\_PS\_HoTime configures the hold-off timer. +- ETH\_C\_MI\_PS\_WTR configures the wait-to-restore timer. + +- ETH\_C\_MI\_PS\_ExtCMD configures the protection group command. +- ETH\_C\_MI\_PS\_BridgeType configures the type of bridge used for 1:1 SNC protection switching. +- ETH\_C\_MI\_PS\_SD\_Protection configures the ability of an SNC protection switching process to trigger protection switching upon SD. + +NOTE 2 – ETH\_C\_MI\_PS\_WorkingPortId and ETH\_C\_MI\_PS\_ProtectionPortId are set by the EMF based on ETH SNC/S protection configuration and are not exposed to the operator as configuration parameters of the equipment management interface. + +#### *Reporting* + +The following reporting parameters are defined in [ITU-T G.8031]: + +ETH\_C\_MI\_PS\_RequestState + ETH\_C\_MI\_PS\_RequestedSignal + ETH\_C\_MI\_PS\_BridgedSignal + +#### *Defects* + +The function detects dFOP-PM, dFOP-CM, dFOP-NR and dFOP-TO defects in case the APS protocol is used. + +#### *Consequent actions* + +None. + +#### *Defect correlations* + +cFOP-PM $\leftarrow$ dFOP-PM and (not CI\_SSF) + cFOP-CM $\leftarrow$ dFOP-CM + cFOP-NR $\leftarrow$ dFOP-NR and (not CI\_SSF) + cFOP-TO $\leftarrow$ dFOP-TO and (not dFOP-CM) and (not CI\_SSF) + +NOTE 3 – In case of cFOP-PM/NR/TO, CI\_SSF of the protection transport entity is used. + +### **9.1.3 Ring protection control process** + +Ring protection with inherent, sub-layer, or test trail monitoring is supported. + +Figure 9-10 shows a subset of the atomic functions involved, and the signal flows associated with the ring protection control process. This is only an overview of the Ethernet ring protection control process as specified in [ITU-T G.8032]. The ETH\_FT\_Sk provides the TSF protection switching criterion via the ETHDi/ETH\_A\_Sk function (SSF). [ITU-T G.8032] specifies the requirements, options and the ring protection protocol supported by the ring protection control process. + +![Diagram of Ring protection atomic functions and control process. At the top, a 'Topology_Change' signal points to a 'Ring protection control process' block. This block is connected to 'ETH_C_MI_RAPS' on the left and has a 'Control' output to an 'ETH' oval. Below the control process, 'ETH_CI_RAPS', 'ETH_CI_SSF', and 'Topology_Change' signals are shown. Further down, a stack of protocol layers is depicted: 'ETHDi/ETH' (containing 'ETHDi'), 'ETHx/ETH-m' (receiving 'ETH_CI_SSF'), 'ETHx' (receiving 'ETH_AI_TSF'), 'ETHD/ETH', and 'ETHDe' at the bottom. Arrows indicate data flow and control signals between these layers and the control process.](26d6d8d333f84acff82b7a9f9b303da6_img.jpg) + +G.8021-Y.1341(22)\_F9-10 + +Diagram of Ring protection atomic functions and control process. At the top, a 'Topology\_Change' signal points to a 'Ring protection control process' block. This block is connected to 'ETH\_C\_MI\_RAPS' on the left and has a 'Control' output to an 'ETH' oval. Below the control process, 'ETH\_CI\_RAPS', 'ETH\_CI\_SSF', and 'Topology\_Change' signals are shown. Further down, a stack of protocol layers is depicted: 'ETHDi/ETH' (containing 'ETHDi'), 'ETHx/ETH-m' (receiving 'ETH\_CI\_SSF'), 'ETHx' (receiving 'ETH\_AI\_TSF'), 'ETHD/ETH', and 'ETHDe' at the bottom. Arrows indicate data flow and control signals between these layers and the control process. + +**Figure 9-10 – Ring protection atomic functions and control process** + +#### *Configuration* + +The following configuration parameters are defined in [ITU-T G.8032]: + +- `ETH_C_MI_RAPS_PortIds[0..1]` associates the given ring port (0 / 1) to a set of ETH flow points, one ETH flow point for each ETH\_FF process controlled by the ERP control process. +NOTE 1 – `ETH_C_MI_RAPS_PortIds` is set by the EMF based on ERP configuration and is not exposed to the operator as a configuration parameter of the equipment management interface. +- `ETH_C_MI_RAPS_RPL_Owner_Node` configures the node type. +- `ETH_C_MI_RAPS_RPL_Neighbour_Node` configures the adjacency of a node to the RPL owner. +- `ETH_C_MI_RAPS_Propagate_TC[1...M]` configures the flush logic of an interconnection node. +- `ETH_C_MI_RAPS_Compatible_Version` configures the backward compatibility logic. +- `ETH_C_MI_RAPS_Revertive` configures the revertive mode. +- `ETH_C_MI_RAPS_Sub_Ring_Without_Virtual_Channel` configures the sub-ring type. +- `ETH_C_MI_RAPS_HoTime` configures the hold-off timer. +- `ETH_C_MI_RAPS_WTR` configures the wait-to-restore timer. +- `ETH_C_MI_RAPS_GuardTime` configures the guard timer. + +- ETH\_C\_MI\_RAPS\_ExtCMD configures the protection command. +- ETH\_C\_MI\_RAPS\_RingID configures the Ring ID. + +#### *Reporting* + +The following reporting parameters are defined in [ITU-T G.8032]: + +- ETH\_C\_MI\_RAPS\_NodeState reports the current ring node state. +- ETH\_C\_MI\_RAPS\_PortState[0..1] reports the given ring port's forwarding state. + +#### *Defects* + +The function detects dFOP-PM and dFOP-TO[0..1] in case the R-APS protocol is used. + +#### *Consequent actions* + +None. + +#### *Defect correlations* + +$$\text{cFOP-PM} \leftarrow \text{dFOP-PM}$$ + +$$\text{cFOP-TO}[i] \leftarrow \text{dFOP-TO}[i] \text{ and (not CI\_SSF) and (not RAPS\_Block)}$$ + +NOTE 2 – As indicated in [ITU-T G.8032], cFOP-TO is not reported if a ring port has a link level failure (operationally disabled), or is administratively locked or blocked from R-APS message reception. The ETHDi/ETH\_A signals the CI\_SSF, when a ring port has a link level failure (operationally disabled), or it is administratively locked. The Ring Protection Control Process signals the RAPS\_Block, when a ring port is blocked from R-APS message reception. Clause 10.4 of [ITU-T G.8032] describes examples of the RAPS\_Block condition. + +## **9.2 ETH termination functions** + +### **9.2.1 ETHx flow termination functions (ETHx\_FT)** + +The bidirectional ETH flow termination (ETHx\_FT) function is performed by a co-located pair of ETH flow termination source (ETHx\_FT\_So) and sink (ETHx\_FT\_Sk) functions. + +#### **9.2.1.1 ETHx flow termination source function (ETHx\_FT\_So)** + +The ETHx\_FT\_So function symbol is shown in Figure 9-11, the interfaces in Table 9-2 and the process diagram in Figure 9-13. + +##### **Symbol** + +![Symbol diagram for ETHx_FT_So. It shows a central triangle labeled 'ETHx'. Above it, an arrow labeled 'ETH_AP' points down into the triangle. To the left, two arrows labeled 'ETHx_FT_So_MP' and 'ETH_TP' point into the triangle. To the right, an arrow labeled 'ETH_RP' points out of the triangle. Below the triangle, an arrow labeled 'ETH_TFP' points down away from it. At the bottom right, there is a small text label: G.8021-Y.1341(22)_F9-11.](d8efc806802d4f3fc14f4011667fa920_img.jpg) + +Symbol diagram for ETHx\_FT\_So. It shows a central triangle labeled 'ETHx'. Above it, an arrow labeled 'ETH\_AP' points down into the triangle. To the left, two arrows labeled 'ETHx\_FT\_So\_MP' and 'ETH\_TP' point into the triangle. To the right, an arrow labeled 'ETH\_RP' points out of the triangle. Below the triangle, an arrow labeled 'ETH\_TFP' points down away from it. At the bottom right, there is a small text label: G.8021-Y.1341(22)\_F9-11. + +**Figure 9-11 – ETHx\_FT\_So symbol** + +##### Interfaces + +Table 9-2 – ETHx\_FT\_So interfaces + +| Inputs | Outputs | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE

ETH_RP:
ETH_RI_CC_RxFCI
ETH_RI_CC_TxFCf
ETH_RI_CC_RDI
ETH_RI_CC_Blk
ETH_RI_LMM(OAM,P,DE)
ETH_RI_LMR(rSA,TxFCf,RxFCf,TxFCb,RxFCI)
[1...M LM ]
ETH_RI_DMM(OAM,P,DE)
ETH_RI_DMR(rSA,TxTimeStampf,
RxTimeStampf,TxTimeStampb,RxTimeb,
rTestID)[1...M DM ]
ETH_RI_SLM(OAM,P,DE,TxFCb)
ETH_RI_SLR(rMEP_ID,rTest_ID,
TxFCf, TxFCb) [1...M SL ]

ETH_TP:
ETHx_FT_So_TI_TimeStamp1

ETHx_FT_So_MP:
ETHx_FT_So_MI_MEL
ETHx_FT_So_MI_MEP_MAC
ETHx_FT_So_MI_CC_Enable
ETHx_FT_So_MI_LMC_Enable
ETHx_FT_So_MI_MEG_ID
ETHx_FT_So_MI_MEP_ID
ETHx_FT_So_MI_CC_Period
ETHx_FT_So_MI_CC_Pri
ETHx_FT_So_MI_LML_Enable[1...M LM ]
ETHx_FT_So_MI_LM_MAC_DA[1...M LM ]
ETHx_FT_So_MI_LM_Period[1...M LM ]
ETHx_FT_So_MI_LM_Pri[1...M LM ]
ETHx_FT_So_MI_DM_Enable[1...M DM ]
ETHx_FT_So_MI_DM_MAC_DA[1...M DM ]
ETHx_FT_So_MI_DM_Test_ID[1...M DM ]
ETHx_FT_So_MI_DM_Length[1...M DM ]
ETHx_FT_So_MI_DM_Period[1...M DM ]
ETHx_FT_So_MI_DM_Pri[1...M DM ]
ETHx_FT_So_MI_1DM_Enable[1...M 1DM ]
ETHx_FT_So_MI_1DM_MAC_DA[1...M 1DM ]
ETHx_FT_So_MI_1DM_Test_ID[1...M 1DM ]
ETHx_FT_So_MI_1DM_Length[1...M 1DM ]
ETHx_FT_So_MI_1DM_Period[1...M 1DM ]
ETHx_FT_So_MI_1DM_Pri[1...M 1DM ] | ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE

ETH_RP:
ETH_RI_LM_Result(N_TF,N_LF,F_TF,F_LF)
[1...M LM ]
ETH_RI_DM_Result(B_FD,F_FD,N_FD)
[1...M DM ]
ETH_RI_SL_Result(N_TF,N_LF,F_TF,F_LF)
[1...M SL ] | + +**Table 9-2 – ETHx\_FT\_So interfaces** + +| Inputs | Outputs | +|--------------------------------------------------|----------------| +| ETHx_FT_So_MI_SL_Enable[1...M SL ] | | +| ETHx_FT_So_MI_SL_MAC_DA[1...M SL ] | | +| ETHx_FT_So_MI_SL_Test_ID[1...M SL ] | | +| ETHx_FT_So_MI_SL_Length[1...M SL ] | | +| ETHx_FT_So_MI_SL_Period[1...M SL ] | | +| ETHx_FT_So_MI_SL_Pri[1...M SL ] | | +| ETHx_FT_So_MI_1SL_Enable[1...M 1SL ] | | +| ETHx_FT_So_MI_1SL_MAC_DA[1...M 1SL ] | | +| ETHx_FT_So_MI_1SL_Test_ID[1...M 1SL ] | | +| ETHx_FT_So_MI_1SL_Length[1...M 1SL ] | | +| ETHx_FT_So_MI_1SL_Period[1...M 1SL ] | | +| ETHx_FT_So_MI_1SL_Pri[1...M 1SL ] | | + +##### Processes + +![Block diagram of the ETHx_FT_So process showing various control signals, generation blocks, and multiplexers.](67cbb5a621a69ab58534bb3376bbb724_img.jpg) + +The diagram illustrates the internal structure of the ETHx\_FT\_So process. It features several control signal inputs on the left, including RI\_CC\_Blk, RI\_CC\_RxFCl, RI\_CC\_TxFCl, RI\_CC\_RDI, MI\_CC\_Enable, MI\_LMC\_Enable, MI\_MEG\_ID, MI\_MEP\_ID, MI\_CC\_Period, MI\_CC\_Pri, MI\_LML\_Enable, MI\_LM\_MAC\_DA, MI\_LM\_Period, MI\_LM\_Pri, RI\_LMR(rSA,TxFCl,RxFCl, TxFClb,RxFCl), RI\_LM\_Result(N\_TF,N\_LF, F\_TF,F\_LF), RI\_LMM(OAM,P,DE), MI\_DM\_Enable, MI\_DM\_MAC\_DA, MI\_DM\_Test\_ID, MI\_DM\_Length, MI\_DM\_Period, MI\_DM\_Pri, RI\_DMR(rSA, TxTimeStampf, RxTimeStampf,TxTimeStampb, RxTimeb,rTestID), RI\_DM\_Result(B\_FD,F\_FD,N\_FD), RI\_DMM(OAM,P,DE), MI\_IDM\_Enable, MI\_IDM\_MAC\_DA, MI\_IDM\_Test\_ID, MI\_IDM\_Length, MI\_IDM\_Period, MI\_IDM\_Pri, TI\_TimeStamp1, MI\_SL\_Enable, MI\_SL\_MAC\_DA, MI\_SL\_Test\_ID, MI\_SL\_Length, MI\_SL\_Period, MI\_SL\_Pri, RI\_SLR(rMEP\_ID,rTest\_ID,TxFCl, TxFClb), RI\_SL\_Result(N\_TF,N\_LF, F\_TF,F\_LF), RI\_SLM(OAM,P,DE,TxFClb), MI\_ISL\_Enable, MI\_ISL\_MAC\_DA, MI\_ISL\_Test\_ID, MI\_ISL\_Length, MI\_ISL\_Period, MI\_ISL\_Pri, MI\_MEL, and MI\_MEP\_MAC. These signals feed into various processing blocks: CCM Generation, Proactive LM Control, Proactive DM Control, Proactive IDM Control\_So, Proactive SL Control, and Proactive ISL Control\_So. Each control block connects to a corresponding Mux (LMM Mux, DMM Mux, IDM Mux, SLM Mux, ISL Mux) which outputs X, Y, and Z signals. These are then processed by Generation blocks (LMM Generation, LMR Generation, DMM Generation, DMR Generation, IDM Generation, SLM Generation, SLR Generation, ISL Generation). The diagram also shows data paths for ETH\_AI\_D/P/DE, Block, Data, Counter, and ETH\_CI\_D/P/DE. A vertical label on the right indicates 'MEP Proactive-OAM insertion'. + +Block diagram of the ETHx\_FT\_So process showing various control signals, generation blocks, and multiplexers. + +Figure 9-12 – ETHx\_FT\_So process + +###### *MEP proactive OAM insertion process* + +This process inserts the OAM traffic units in the stream of ETH\_CI, sets the MEL field to MI\_MEL and sets the SA field to MI\_MEP\_MAC (see Figure 9-13). + +If the DA of the OAM traffic unit is a class 1 multicast DA, the OAM insertion process updates the DA to reflect the correct MEL. + +![Flowchart of OAM MEP insertion behaviour](9958beca8f65818eb0ff893647af94de_img.jpg) + +``` +graph TD; Start([OAM MEP insertion]) --> Waiting([Waiting]); Waiting --> DataFields1[Data.D(D), Data.P(P), Data.DE(DE)]; DataFields1 --> DataFields2[D(D), P(P), DE(DE)]; DataFields2 --> Waiting; Waiting --> OAMFields1[OAM.D(D), OAM.P(P), OAM.DE(DE)]; OAMFields1 --> MELSet[MEL(D)=MI_MEL]; MELSet --> DACheck{DA(D)==01-80-C2-00-00-3*}; DACheck -- Y --> DAUpdate["x=MI_MEL
DA(D)=01-80-C2-00-00-3x"]; DACheck -- N --> SASet[SA(D)=MI_MEP_MAC]; DAUpdate --> SASet; SASet --> DataFields3[D(D), P(P), DE(DE)]; DataFields3 --> Waiting +``` + +The flowchart illustrates the OAM MEP insertion process. It begins with 'OAM MEP insertion', leading to a 'Waiting' state. From 'Waiting', the process branches into two parallel paths. The left path handles 'Data.D(D), Data.P(P), Data.DE(DE)', which are then processed into 'D(D), P(P), DE(DE)' before returning to 'Waiting'. The right path handles 'OAM.D(D), OAM.P(P), OAM.DE(DE)', followed by 'MEL(D)=MI\_MEL'. A decision diamond checks if 'DA(D)==01-80-C2-00-00-3\*'. If 'Y' (Yes), it calculates 'x=MI\_MEL' and updates 'DA(D)=01-80-C2-00-00-3x'. If 'N' (No), it proceeds to 'SA(D)=MI\_MEP\_MAC'. Both paths converge to 'SA(D)=MI\_MEP\_MAC', which then leads to 'D(D), P(P), DE(DE)' before returning to 'Waiting'. A small note at the bottom right reads 'G.8021-Y.1341(22)\_F9-13'. + +Flowchart of OAM MEP insertion behaviour + +**Figure 9-13 – OAM MEP insertion behaviour** + +###### *CCM generation process* + +This process is defined in clause 8.1.7 where the CC protocol is defined. Clause 8.1.7.2 defines the CCM generation process. + +###### *Block process* + +When RI\_CC\_Blk is raised, the block process will discard all ETH\_CI information it receives. If RI\_CC\_Blk is cleared, the received ETH\_CI information will be passed to the output port. + +###### *Counter process* + +This process is defined in clauses 8.1.7.4 and 8.1.9.7. It is used to count frames for proactive loss measurements with CCM and proactive LM protocols, respectively. + +###### *Proactive LM control* + +This process is defined in clause 8.1.9 where the LM protocol is defined. Clause 8.1.9.2 defines the proactive LM control process. + +###### *LMM generation* + +This process is defined in clause 8.1.9 where the LM protocol is defined. Clause 8.1.9.3 defines the LMM generation process. + +###### *LMR generation* + +This process is defined in clause 8.1.9 where the LM protocol is defined. Clause 8.1.9.5 defines the LMR generation process. + +###### *LMM Mux* + +The LMM Mux process interleaves the signal sets LMM(DA,P,1) from the input ports (X, Y, Z). + +##### *Proactive DM control* + +This process is defined in clause 8.1.10 where the DM protocol is defined. Clause 8.1.10.2 defines the DM control process. + +###### *DMM generation* + +This process is defined in clause 8.1.10 where the DM protocol is defined. Clause 8.1.10.3 defines the DMM generation process. + +###### *DMR generation* + +This process is defined in clause 8.1.10 where the DM protocol is defined. Clause 8.1.10.5 defines the DMR generation process. + +###### *DMM Mux* + +The DMM Mux process interleaves the signal sets DMM(DA,P,1,Test ID TLV, TLV) from the input ports (X, Y, Z). + +##### *Proactive IDM Control\_So* + +This process is defined in clause 8.1.11 where the IDM protocol is defined. Clause 8.1.11.2 defines the IDM Control\_So process. + +###### *IDM generation* + +This process is defined in clause 8.1.11 where the IDM protocol is defined. Clause 8.1.11.3 defines the IDM generation process. + +###### *IDM Mux* + +The IDM Mux process interleaves the signal sets IDM(DA,P,1,Test ID TLV, TLV) from the input ports (X, Y, Z). + +###### *Proactive SL control* + +This process is defined in clause 8.1.14 where the SL protocol is defined. Clause 8.1.14.2 defines the SL control process. + +###### *SLM generation* + +This process is defined in clause 8.1.14 where the SL protocol is defined. Clause 8.1.14.3 defines the SLM generation process. + +###### *SLR Generation* + +This process is defined in clause 8.1.14 where the SL protocol is defined. Clause 8.1.14.5 defines the SLR generation process. + +###### SLM Mux + +The SLM Mux process interleaves the signal sets SLM(DA,P,MEP\_ID,Test\_ID,TxFCl,TLV) from the input ports (X, Y, Z). + +##### Proactive ISL Control\_So + +This process is defined in clause 8.1.15 where the 1SL protocol is defined. Clause 8.1.15.2 defines the 1SL Control\_So process. + +###### 1SL generation + +This process is defined in clause 8.1.15 where the 1SL protocol is defined. Clause 8.1.15.3 defines the 1SL generation process. + +###### 1SL Mux + +The 1SL Mux process interleaves the signal sets 1SL(DA,P, MEP\_ID,Test\_ID, TxFCl, TLV) from the input ports (X, Y, Z). + +**Defects** None. + +**Consequent actions** None. + +**Defect correlations** None. + +**Performance monitoring** None. + +#### 9.2.1.2 ETHx flow termination sink function (ETHx\_FT\_Sk) + +The ETHx\_FT\_Sk function symbol is shown in Figure 9-14, the interfaces in Table 9-3 and the process diagram in Figure 9-15. + +##### Symbol + +![Symbol diagram for ETHx_FT_Sk function. It is a triangle pointing downwards with 'ETHx' inside. An arrow points up from the top vertex to 'ETH_AP'. An arrow points down to the bottom vertex from 'ETH_TFP'. On the left, two arrows point right into the triangle: the top one is labeled 'ETHx_FT_Sk_MP' and the bottom one is labeled 'ETH_TP'. On the right, an arrow points left from 'ETH_RP' into the triangle. Below the diagram is the text 'G.8021-Y.1341(22)_F9-14'.](0ca95580c45391f07eb17e83a3724caf_img.jpg) + +Symbol diagram for ETHx\_FT\_Sk function. It is a triangle pointing downwards with 'ETHx' inside. An arrow points up from the top vertex to 'ETH\_AP'. An arrow points down to the bottom vertex from 'ETH\_TFP'. On the left, two arrows point right into the triangle: the top one is labeled 'ETHx\_FT\_Sk\_MP' and the bottom one is labeled 'ETH\_TP'. On the right, an arrow points left from 'ETH\_RP' into the triangle. Below the diagram is the text 'G.8021-Y.1341(22)\_F9-14'. + +Figure 9-14 – ETHx\_FT\_Sk symbol + +##### Interfaces + +Table 9-3 – ETHx\_FT\_Sk interfaces + +| Inputs | Outputs | +|--------------------------------------------------------------------|-------------------------------------------------------------------| +| ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF | ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE
ETH_AI_TSF | + +**Table 9-3 – ETHx\_FT\_Sk interfaces** + +| Inputs | Outputs | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_RP:
ETH_RI_LM_Result(
N_TF,N_LF,F_TF,F_LF) [1...M LM ]
ETH_RI_DM_Result(B_FD,F_FD,N_FD)
[1...M DM ]
ETH_RI_SL_Result(N_TF,N_LF,F_TF,F_LF)
[1...M SL ]

ETH_TP:
ETHx_FT_Sk_TT_TimeStamp1

ETHx_FT_Sk_MP:
ETHx_FT_Sk_MI_CC_Enable
ETHx_FT_Sk_MI_LMC_Enable
ETHx_FT_Sk_MI_1Second
ETHx_FT_Sk_MI_LM_DEGM
ETHx_FT_Sk_MI_LM_M
ETHx_FT_Sk_MI_LM_DEGTHR
ETHx_FT_Sk_MI_LM_TFMIN
ETHx_FT_Sk_MI_MEL
ETHx_FT_Sk_MI_MEG_ID
ETHx_FT_Sk_MI_PeerMEP_ID[i]
ETHx_FT_Sk_MI_CC_Period
ETHx_FT_Sk_MI_CC_Pri
ETHx_FT_Sk_MI_GetSvdCCM
ETHx_FT_Sk_MI_1DM_Enable[1...M 1DM ]
ETHx_FT_Sk_MI_1DM_MAC_SA[1...M 1DM ]
ETHx_FT_Sk_MI_1DM_Pri[1...M 1DM ]
ETHx_FT_Sk_MI_1DM_Test_ID[1...M 1DM ]
ETHx_FT_Sk_MI_1SL_Enable[1...M 1SL ]
ETHx_FT_Sk_MI_1SL_MAC_SA[1...M 1SL ]
ETHx_FT_Sk_MI_1SL_Test_ID[1...M 1SL ]
ETHx_FT_Sk_MI_MEP_MAC | ETH_AI_TSD
ETH_AI_AIS

ETH_RP:
ETH_RI_CC_RxFCI
ETH_RI_CC_TxFCf
ETH_RI_CC_RDI
ETH_RI_CC_Blk
ETH_RI_LMM(OAM,P,DE)
ETH_RI_LMR(rSA,TxFCf,RxFCf,TxFCb,RxFCI)
[1...M LM ]
ETH_RI_DMM(OAM,P,DE)
ETH_RI_DMR(rSA,TxTimeStampf,
RxTimeStampf,TxTimeStampb,RxTimeb,
rTestID) [1...M DM ]
ETH_RI_SLM(OAM,P,DE,TxFCb)
ETH_RI_SLR(rMEP_ID,rTest_ID,TxFCf,TxFCb)
[1...M SL ]

ETHx_FT_Sk_MP:
ETHx_FT_Sk_MI_cLOC[i]
ETHx_FT_Sk_MI_cUNL
ETHx_FT_Sk_MI_cMMG
ETHx_FT_Sk_MI_cUNM
ETHx_FT_Sk_MI_cDEG
ETHx_FT_Sk_MI_cUNP
ETHx_FT_Sk_MI_cUNPr
ETHx_FT_Sk_MI_cRDI
ETHx_FT_Sk_MI_cSSF
ETHx_FT_Sk_MI_cLCK
ETHx_FT_Sk_MI_pN_TF
ETHx_FT_Sk_MI_pN_LF
ETHx_FT_Sk_MI_pF_TF
ETHx_FT_Sk_MI_pF_LF
ETHx_FT_Sk_MI_pF_DS
ETHx_FT_Sk_MI_pN_DS
ETHx_FT_Sk_MI_pB_FD
ETHx_FT_Sk_MI_pB_FDV
ETHx_FT_Sk_MI_pF_FD
ETHx_FT_Sk_MI_pF_FDV
ETHx_FT_Sk_MI_pN_FD
ETHx_FT_Sk_MI_pN_FDV
ETHx_FT_Sk_MI_SvdCCM
ETHx_FT_Sk_MI_BW_Report(SA, PortID,
NominalBW, CurrentBW) | + +NOTE 1 – If the delay measurement message rate is smaller than one second, there will be more than one set of primitive values (i.e., pB\_FD, pB\_FDV, pF\_FD, pF\_FDV, pN\_FD, pN\_FDV) for some 1-second period. If the delay measurement message rate is larger than one second, there will be no set of primitive values for some 1-second period. + +##### Processes + +![Figure 9-15 – ETHx_FT_Sk process block diagram showing internal components and interfaces for an Ethernet FT_Sk process.](56587d8256f60b3022273b5d8a90dfa8_img.jpg) + +The diagram illustrates the internal architecture of the ETHx\_FT\_Sk process. It features several key functional blocks and their interconnections: + +- Consequent action:** Receives inputs from RI\_CC\_RDI, RI\_CC\_Blk, and MI\_CC\_Enable. It outputs aRDI, aTSF, aTSD, aAIS, and aBLK. aBLK connects to a **Block** which also receives D, P, and DE inputs and outputs ETH\_AI\_D/P/DE. +- Defect Generation:** Receives inputs from MI\_LM\_DEGM, MI\_LM\_M, MI\_LM\_DEGTHR, and MI\_LM\_TFMIN. It outputs CI\_SSF, dLCK, dAIS, dRDI[i], dUNPr, dUNP, dDEG[i], dUNM, dMMG, dUNL, and dLOC[i]. +- Performance monitoring:** Receives inputs from TI\_TimeStamp1, MI\_1Second, MI\_pN\_TF, MI\_pN\_LF, MI\_pF\_TF, MI\_pF\_LF, MI\_pN\_DS, MI\_pF\_DS, MI\_pB\_FD, MI\_pB\_FDV, MI\_pF\_FD, MI\_pF\_FDV, MI\_pN\_FD, and MI\_pN\_FDV. It outputs nN\_LF, nN\_TF, nF\_LF, nF\_TF, aTSF, aRDI[1], RI\_DM\_Result, IDM\_Result, RI\_SL\_Result, and I\_SL\_Result. +- CCM reception:** Receives inputs from RI\_CC\_RxFCI, RI\_CC\_TxFCf, RI\_LM\_Result, and MI\_LMC\_Enable. It outputs RxFcb, TxFcb, RxFCI, TxFcf, MI\_CC\_Pri, and RxFC. It connects to **Data**, **Counter**, and **Data** blocks which output D, P, and DE. +- Defect correlation:** Receives inputs from MI\_cLOC[i], MI\_cUNL, MI\_cMMG, MI\_cUNM, MI\_cDEG, MI\_cUNP, MI\_cUNPr, MI\_cRDI, MI\_cSSF, MI\_cLCK, and MI\_CC\_Enable. It outputs dLOC[i], dUNL, dMMG, dUNM, dDEG[i], dUNP, dUNPr, dRDI[i], dAIS, dLCK, CI\_SSF, and MI\_CC\_Enable. +- MEP Proactive-OAM extraction:** A vertical column of reception blocks including LMM reception, LMR reception, LCK reception, AIS reception, DMM reception, DMR reception, IDM reception, SLM reception, SLR reception, ISL reception, and BNM extract. These receive inputs from RI\_LMM, RI\_LMR, LCK, AIS, RI\_DMM, RI\_DMR, RI\_SLM, RI\_SLR, RI\_ISL, and MI\_MEL. They output D, P, and DE signals. +- Proactive 1DM Control\_Sk:** Receives inputs from MI\_1DM\_Enable, MI\_1DM\_MAC\_SA, MI\_1DM\_Pri, and MI\_1DM\_Test\_ID. It outputs 1DM\_Result, RI\_DMR, and RI\_SLM. RI\_DMR connects to a **DMR Dmux** which outputs X, Y, and Z. +- Proactive 1SL Control\_Sk:** Receives inputs from MI\_1SL\_Enable, MI\_1SL\_MAC\_SA, and MI\_1SL\_Test\_ID. It outputs 1SL\_Result, RI\_SLR, and RI\_ISL. RI\_SLR connects to a **SLR Dmux** which outputs X, Y, and Z. +- Bottom Interface:** Includes ETH\_CI\_SSF, ETH\_CI\_D/P/DE, and a series of **Data**, **Counter**, and **Data** blocks with D, P, and DE outputs. + +G.8021-Y.1341(22)\_F9-15 + +Figure 9-15 – ETHx\_FT\_Sk process block diagram showing internal components and interfaces for an Ethernet FT\_Sk process. + +**Figure 9-15 – ETHx\_FT\_Sk process** + +###### *MEP proactive OAM extraction process* + +The MEP proactive OAM extraction process extracts OAM traffic units that are processed in the ETHx\_FT\_Sk process from the stream of traffic units according to the following pseudo code: + +``` +if (TYPE=) and (MEL=MI_MEL) then + switch(OPC) { + case : extract ETH-CCM OAM traffic unit and forward to CCM Port + case : extract ETH-AIS OAM traffic unit and forward to AIS Port + case : extract ETH-LCK OAM traffic unit and forward to LCK Port + case : extract ETH-LMM OAM traffic unit and forward to LMM Port + case : extract ETH-LMR OAM traffic unit and forward to LMR Port + case : extract ETH-DMM OAM traffic unit and forward to DMM Port + case : extract ETH-DMR OAM traffic unit and forward to DMR Port + case <1DM>: extract ETH-1DM OAM traffic unit and forward to 1DM Port + case : extract ETH-SLM OAM traffic unit and forward to SLM port + case : extract ETH-SLR OAM traffic unit and forward to SLR port + case <1SL>: extract ETH-1SL OAM traffic unit and forward to 1SL Port + case : switch(SubOPC) { + case : extract ETH-BN OAM traffic unit and forward to BNM Port + default: forward ETH_CI traffic unit to Data port + } + default: forward ETH_CI traffic unit to Data port + } +elseif (TYPE=) and (MELETH_AP:
ETH_AI_D[1...M]
ETH_AI_P[1...M]
ETH_AI_DE[1...M] | ETH_TFP:
ETH_CI_D[1...M]
ETH_CI_P[1...M]
ETH_CI_DE[1...M] | + +**Table 9-4 – ETHG\_FT\_So interfaces** + +| Inputs | Outputs | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

ETH_RP:

ETH_RI_CC_RxFCl
ETH_RI_CC_TxFCl
ETH_RI_CC_RDI
ETH_RI_CC_Blk
ETH_RI_LMM(OAM,P,DE)
ETH_RI_LMR(rSA,TxFCl,RxFCl,TxFClb,RxFCl)
[1...MLM]
ETH_RI_DMM(OAM,P,DE)
ETH_RI_DMR(rSA,TxTimeStampf,
RxTimeStampf,TxTimeStampb,RxTimeb,
rTestID) [1...MDM]
ETH_RI_SLM(OAM,P,DE,TxFClb)
ETH_RI_SLR(rMEP_ID,rTest_ID,
TxFCl, TxFClb) [1...MSL]

ETH_TP:

ETHG_FT_So_TI_TimeStampI

ETHG_FT_So_MP:

ETHG_FT_So_MI_MEL
ETHG_FT_So_MI_MEP_MAC
ETHG_FT_So_MI_CC_Enable
ETHG_FT_So_MI_LMC_Enable
ETHG_FT_So_MI_MEG_ID
ETHG_FT_So_MI_MEP_ID
ETHG_FT_So_MI_CC_Period
ETHG_FT_So_MI_CC_Pri
ETHG_FT_So_MI_LML_Enable[1...MLM]
ETHG_FT_So_MI_LM_MAC_DA[1...MLM]
ETHG_FT_So_MI_LM_Period[1...MLM]
ETHG_FT_So_MI_LM_Pri [1...MLM]
ETHG_FT_So_MI_DM_Enable [1...MDM]
ETHG_FT_So_MI_DM_MAC_DA [1...MDM]
ETHG_FT_So_MI_DM_Test_ID [1...MDM]
ETHG_FT_So_MI_DM_Length [1...MDM]
ETHG_FT_So_MI_DM_Period [1...MDM]
ETHG_FT_So_MI_DM_Pri [1...MDM]
ETHG_FT_So_MI_1DM_Enable [1...M1DM]
ETHG_FT_So_MI_1DM_MAC_DA [1...M1DM]
ETHG_FT_So_MI_1DM_Test_ID [1...M1DM]
ETHG_FT_So_MI_1DM_Length [1...M1DM]
ETHG_FT_So_MI_1DM_Period [1...M1DM]
ETHG_FT_So_MI_1DM_Pri [1...M1DM]
ETHG_FT_So_MI_SL_Enable [1...MSL]
ETHG_FT_So_MI_SL_MAC_DA [1...MSL]
ETHG_FT_So_MI_SL_Test_ID [1...MSL]
ETHG_FT_So_MI_SL_Length [1...MSL]

|

ETH_RP:

ETH_RI_LM_Result(N_TF,N_LF,F_TF,F_LF)
[1...MLM]
ETH_RI_DM_Result(B_FD,F_FD,N_FD)
[1...MDM]
ETH_RI_SL_Result(N_TF,N_LF,F_TF,F_LF)
[1...MSL]

| + +**Table 9-4 – ETHG\_FT\_So interfaces** + +| Inputs | Outputs | +|---------------------------------------------------|----------------| +| ETHG_FT_So_MI_SL_Period [1...M SL ] | | +| ETHG_FT_So_MI_SL_Pri [1...M SL ] | | +| ETHG_FT_So_MI_1SL_Enable [1...M 1SL ] | | +| ETHG_FT_So_MI_1SL_MAC_DA [1...M 1SL ] | | +| ETHG_FT_So_MI_1SL_Test_ID [1...M 1SL ] | | +| ETHG_FT_So_MI_1SL_Length [1...M 1SL ] | | +| ETHG_FT_So_MI_1SL_Period [1...M 1SL ] | | +| ETHG_FT_So_MI_1SL_Pri [1...M 1SL ] | | + +##### Processes + +![Block diagram of the ETHG_FT_So process showing various control and generation blocks connected to a central data path with counters and blocks.](0e9d4d612c4da4801262d0bf2f169713_img.jpg) + +The diagram illustrates the ETHG\_FT\_So process, showing the flow of data and control signals through various functional blocks. + +**Inputs:** + +- RI\_CC\_Blk** connects to the **Block**. +- RI\_CC\_RxFCl**, **RI\_CC\_TxFCl**, **RI\_CC\_RDI**, **MI\_CC\_Enable**, **MI\_LMC\_Enable**, **MI\_MEG\_ID**, **MI\_MEP\_ID**, **MI\_CC\_Period**, and **MI\_CC\_Pri** connect to the **CCM Generation** block. +- MI\_LML\_Enable**, **MI\_LM\_MAC\_DA**, **MI\_LM\_Period**, **MI\_LM\_Pri**, **RI\_LMR(rSA,TxFCl,RxFCl, TxFClb,RxFClb)**, and **RI\_LM\_Result(N\_TF,N\_LF, F\_TF, \_LF)** connect to the **Proactive LM Control** block. +- RI\_LMM(OAM,P,DE)** connects to the **LMR Generation** block. +- MI\_DM\_Enable**, **MI\_DM\_MAC\_DA**, **MI\_DM\_Test\_ID**, **MI\_DM\_Length**, **MI\_DM\_Period**, **MI\_DM\_Pri**, **RI\_DMR(rSA,TxTimeStampf, RxTimeStampf,TxTimeStampb, RxTimeb,rTestID)**, **RI\_DM\_Result(B\_FD,F\_FD,N\_FD)**, and **RI\_DMM(OAM,P,DE)** connect to the **Proactive DM Control** block. +- MI\_IDM\_Enable**, **MI\_IDM\_MAC\_DA**, **MI\_IDM\_Test\_ID**, **MI\_IDM\_Length**, **MI\_IDM\_Period**, **MI\_IDM\_Pri**, **TI\_TimeStamp1**, and **RI\_IDM(OAM,P,DE)** connect to the **Proactive IDM Control\_So** block. +- MI\_SL\_Enable**, **MI\_SL\_MAC\_DA**, **MI\_SL\_Test\_ID**, **MI\_SL\_Length**, **MI\_SL\_Period**, **MI\_SL\_Pri**, **RI\_SLR(rMEP\_ID, rTest\_ID,TxFCl,TxFClb)**, **RI\_SL\_Result(N\_TF,N\_LF, F\_TF,F\_LF)**, and **RI\_SLM(OAM,P,DE,TxFClb)** connect to the **Proactive SL Control** block. +- MI\_ISL\_Enable**, **MI\_ISL\_MAC\_DA**, **MI\_ISL\_Test\_ID**, **MI\_ISL\_Length**, **MI\_ISL\_Period**, **MI\_ISL\_Pri**, and **RI\_ISL(OAM,P,DE)** connect to the **Proactive ISL Control\_So** block. +- MI\_MEL** and **MI\_MEP\_MAC** connect to the bottom **Block**. + +**Internal Components:** + +- CCM Generation** block outputs **MI\_CC\_Pri** and **TxFCl**. +- Proactive LM Control** block outputs **LMM(DA,P,1)** to an **LMM Mux** (inputs X, Y, Z), which then connects to **LMM Generation**. +- Proactive DM Control** block outputs **DMM(DA,P,1, Test\_ID TLV, TLV)** to a **DMM Mux** (inputs X, Y, Z), which connects to **DMM Generation**. +- Proactive IDM Control\_So** block outputs **IDM(DA,P,1, Test\_ID TLV, TLV)** to an **IDM Mux** (inputs X, Y, Z), which connects to **IDM Generation**. +- Proactive SL Control** block outputs **SLM(DA,P,MEP\_ID, Test\_ID,TxFCl, TLV)** to an **SLM Mux** (inputs X, Y, Z), which connects to **SLM Generation**. +- Proactive ISL Control\_So** block outputs **ISL(DA,P,MEP\_ID, Test\_ID,TxFCl, TLV)** to an **ISL Mux** (inputs X, Y, Z), which connects to **ISL Generation**. +- Vertical labels **CCM**, **LMM**, **LMR**, **DMM**, **DMR**, **IDM**, **SLM**, **SLR**, and **ISL** are positioned next to their respective generation blocks. +- A vertical label **MEP Proactive-OAM insertion** is located to the right of the generation blocks. +- Top and bottom **Block** units each contain three **Data** blocks and a **Counter**. The top **Block** also has **ETH\_AI\_D/P/DE** inputs and outputs. The bottom **Block** has **ETH\_CI\_D/P/DE** inputs and outputs. + +**Outputs:** + +- ETH\_AI\_D/P/DE** (top right) and **ETH\_CI\_D/P/DE** (bottom right) are the final data outputs. + +**Reference:** G.8021-Y.1341(22)\_F9-17 + +Block diagram of the ETHG\_FT\_So process showing various control and generation blocks connected to a central data path with counters and blocks. + +Figure 9-17 – ETHG\_FT\_So process + +###### *MEP proActive OAM insertion process* + +This process inserts the OAM traffic units in the stream of ETH\_CI, sets the MEL field to MI\_MEL and sets the SA field to MI\_MEP\_MAC. This process resides only in the lowest number in the contiguous range of ETH\_FPs or a selected ETH\_FP within the group of arbitrary ETH\_FPs. The detail of the OAM insertion behaviour is described in clause 9.2.1.1. + +###### *CCM generation process* + +This process is defined in clause 8.1.7 where the CC protocol is defined. Clause 8.1.7.2 defines the CCM generation process. + +###### *Block process* + +When RI\_CC\_Blk is raised, the block process will discard all ETH\_CI information within the group of co-located flow points. If RI\_CC\_Blk is cleared, the received ETH\_CI information will be passed to the output port. + +###### *Counter process* + +This process is defined in clauses 8.1.7.4 and 8.1.9.7. It is used to count frames for proactive loss measurements with CCM and proactive LM protocols, respectively. + +###### *Proactive LM control* + +This process is defined in clause 8.1.9 where the LM protocol is defined. Clause 8.1.9.2 defines the proactive LM control process. + +###### *LMM generation* + +This process is defined in clause 8.1.9 where the LM protocol is defined. Clause 8.1.9.3 defines the LMM generation process. + +###### *LMR generation* + +This process is defined in clause 8.1.9 where the LM protocol is defined. Clause 8.1.9.5 defines the LMR generation process. + +###### *LMM Mux* + +The LMM Mux process interleaves the signal sets LMM(DA,P,1) from the input ports (X, Y, Z). + +###### *Proactive DM control* + +This process is defined in clause 8.1.10 where the DM protocol is defined. Clause 8.1.10.2 defines the DM control process. + +###### *DMM generation* + +This process is defined in clause 8.1.10 where the DM protocol is defined. Clause 8.1.10.3 defines the DMM generation process. + +###### *DMR generation* + +This process is defined in clause 8.1.10 where the DM protocol is defined. Clause 8.1.10.5 defines the DMR generation process. + +###### *DMM Mux* + +The DMM Mux process interleaves the signal sets DMM(DA,P,1,Test ID TLV, TLV) from the input ports (X, Y, Z). + +###### *Proactive IDM Control\_So* + +This process is defined in clause 8.1.11 where the IDM protocol is defined. Clause 8.1.11.2 defines the IDM Control\_So process. + +###### *IDM generation* + +This process is defined in clause 8.1.11 where the IDM protocol is defined. Clause 8.1.11.3 defines the IDM generation process. + +###### *IDM Mux* + +The IDM Mux process interleaves the signal sets IDM(DA,P,1,Test ID TLV, TLV) from the input ports (X, Y, Z). + +###### *Proactive SL control* + +This process is defined in clause 8.1.14 where the SL protocol is defined. Clause 8.1.14.2 defines the SL control process. + +###### *SLM generation* + +This process is defined in clause 8.1.14 where the SL protocol is defined. Clause 8.1.14.3 defines the SLM generation process. + +###### *SLR generation* + +This process is defined in clause 8.1.14 where the SL protocol is defined. Clause 8.1.14.5 defines the SLR generation process. + +###### *SLM Mux* + +The SLM Mux process interleaves the signal sets SLM(DA,P,MEP\_ID,Test\_ID,TxFCl,TLV) from the input ports (X, Y, Z). + +###### *Proactive 1SL Control\_So* + +This process is defined in clause 8.1.15 where the 1SL protocol is defined. Clause 8.1.15.2 defines the 1SL Control\_So process. + +###### *1SL generation* + +This process is defined in clause 8.1.15 where the 1SL protocol is defined. Clause 8.1.15.3 defines the 1SL generation process. + +###### *1SL Mux* + +The 1SL Mux process interleaves the signal sets 1SL(DA,P,Test\_ID,MEP\_ID,TxFCl, TLV) from the input ports (X, Y, Z). + +**Defects** None. + +**Consequent actions** None. + +**Defect correlations** None. + +**Performance monitoring** None. + +#### 9.2.2.2 ETH group flow termination sink function (ETHG\_FT\_Sk) + +The ETHG\_FT\_Sk function symbol is shown in Figure 9-18, the interfaces in Table 9-5 and the process diagram in Figure 9-19. + +##### Symbol + +![Figure 9-18 – ETHG_FT_Sk symbol. The diagram shows a central triangle labeled 'ETHG'. Above the triangle, three arrows point upwards labeled 'ETH_AP', 'ETH_AP', and 'ETH_AP' (with a vertical ellipsis between the second and third). To the left of the triangle, two arrows point rightwards labeled 'ETH_RP' and 'ETH_TP'. To the right of the triangle, one arrow points leftwards labeled 'ETHG_FT_Sk_MP'. Below the triangle, three arrows point upwards labeled 'ETH_TFP', 'ETH_TFP', and 'ETH_TFP' (with a vertical ellipsis between the second and third).](223792b3652794024244c277cc46394b_img.jpg) + +Figure 9-18 – ETHG\_FT\_Sk symbol. The diagram shows a central triangle labeled 'ETHG'. Above the triangle, three arrows point upwards labeled 'ETH\_AP', 'ETH\_AP', and 'ETH\_AP' (with a vertical ellipsis between the second and third). To the left of the triangle, two arrows point rightwards labeled 'ETH\_RP' and 'ETH\_TP'. To the right of the triangle, one arrow points leftwards labeled 'ETHG\_FT\_Sk\_MP'. Below the triangle, three arrows point upwards labeled 'ETH\_TFP', 'ETH\_TFP', and 'ETH\_TFP' (with a vertical ellipsis between the second and third). + +G.8021-Y.1341(22)\_F9-18 + +Figure 9-18 – ETHG\_FT\_Sk symbol + +##### Interfaces + +Table 9-5 – ETHG\_FT\_Sk interfaces + +| Inputs | Outputs | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_TFP:
ETH_CI_D[1...M]
ETH_CI_P[1...M]
ETH_CI_DE[1...M]
ETH_CI_SSF

ETH_RP:
ETH_RI_LM_Result(
N_TF,N_LF,F_TF,F_LF) [1...M LM ]
ETH_RI_DM_Result(
B_FD,F_FD,N_FD) [1...M DM ]
ETH_RI_SL_Result(
N_TF,N_LF,F_TF,F_LF) [1...M SL ]

ETH_TP:
ETHG_FT_Sk_TI_TimeStampl

ETHG_FT_Sk_MP:
ETHG_FT_Sk_MI_CC_Enable
ETHG_FT_Sk_MI_LMC_Enable
ETHG_FT_Sk_MI_1Second
ETHG_FT_Sk_MI_LM_DEGM
ETHG_FT_Sk_MI_LM_M
ETHG_FT_Sk_MI_LM_DEGTHR
ETHG_FT_Sk_MI_LM_TFMIN
ETHG_FT_Sk_MI_MEL
ETHG_FT_Sk_MI_MEG_ID
ETHG_FT_Sk_MI_PeerMEP_ID[i]
ETHG_FT_Sk_MI_CC_Period | ETH_AP:
ETH_AI_D[1...M]
ETH_AI_P[1...M]
ETH_AI_DE[1...M]
ETH_AI_TSF
ETH_AI_TSD
ETH_AI_AIS

ETH_RP:
ETH_RI_CC_RxFCI
ETH_RI_CC_TxFCf
ETH_RI_CC_RDI
ETH_RI_CC_Blk
ETH_RI_LMM(OAM,P,DE)
ETH_RI_LMR(rSA,TxFCf,RxFCf,TxFCb,RxFCI)
[1...M LM ]
ETH_RI_DMM(OAM,P,DE)
ETH_RI_DMR(rSA,TxTimeStampf,
RxTimeStampf,TxTimeStampb,RxTimeb,
rTestID) [1...M DM ]
ETH_RI_SLM(OAM,P,DE,TxFCb)
ETH_RI_SLR(rMEP_ID,rTest_ID,TxFCf, TxFCb)
[1...M SL ]

ETHG_FT_Sk_MP:
ETHG_FT_Sk_MI_cLOC[i]
ETHG_FT_Sk_MI_cUNL
ETHG_FT_Sk_MI_cMMG
ETHG_FT_Sk_MI_cUNM
ETHG_FT_Sk_MI_cDEG | + +**Table 9-5 – ETHG\_FT\_Sk interfaces** + +| Inputs | Outputs | +|---------------------------------------------------|-----------------------------------------------------------| +| ETHG_FT_Sk_MI_CC_Pri | ETHG_FT_Sk_MI_cUNP | +| ETHG_FT_Sk_MI_GetSvdCCM | ETHG_FT_Sk_MI_cUNPr | +| ETHG_FT_Sk_MI_1DM_Enable [1...M 1DM ] | ETHG_FT_Sk_MI_cRDI | +| ETHG_FT_Sk_MI_1DM_MAC_SA [1...M 1DM ] | ETHG_FT_Sk_MI_cSSF | +| ETHG_FT_Sk_MI_1DM_Pri [1...M 1DM ] | ETHG_FT_Sk_MI_cLCK | +| ETHG_FT_Sk_MI_1DM_Test_ID [1...M 1DM ] | ETHG_FT_Sk_MI_pN_TF | +| ETHG_FT_Sk_MI_1SL_Enable [1...M 1SL ] | ETHG_FT_Sk_MI_pN_LF | +| ETHG_FT_Sk_MI_1SL_MAC_SA [1...M 1SL ] | ETHG_FT_Sk_MI_pF_TF | +| ETHG_FT_Sk_MI_1SL_Test_ID [1...M 1SL ] | ETHG_FT_Sk_MI_pF_LF | +| ETHG_FT_Sk_MI_MEP_MAC | ETHG_FT_Sk_MI_pF_DS | +| | ETHG_FT_Sk_MI_pN_DS | +| | ETHG_FT_Sk_MI_pB_FD | +| | ETHG_FT_Sk_MI_pB_FDV | +| | ETHG_FT_Sk_MI_pF_FD | +| | ETHG_FT_Sk_MI_pF_FDV | +| | ETHG_FT_Sk_MI_pN_FD | +| | ETHG_FT_Sk_MI_pN_FDV | +| | ETHG_FT_Sk_MI_SvdCCM | +| | ETHG_FT_Sk_MI_BW_Report(SA, PortID, NominalBW, CurrentBW) | + +NOTE – If the delay measurement message rate is smaller than one second, there will be more than one set of primitive values (i.e., pB\_FD, pB\_FDV, pF\_FD, pF\_FDV, pN\_FD, pN\_FDV) for some 1-second period. If the delay measurement message rate is larger than one second, there will be no set of primitive values for some 1-second period. + +##### Processes + +![Figure 9-19 – ETHG_FT_Sk process diagram. This is a complex functional block diagram showing the internal architecture of an Ethernet G.802.1Y (ETHG) FT_Sk process. The diagram is organized into several functional blocks: + - Top: 'Consequent action' block receiving inputs like RI_CC_RDI, RI_CC_Blk, MI_CC_Enable, and various alarm signals (aTSF, aTSD, aAIS). It outputs aBLK to a 'Block' and control signals to 'Defect Generation'. + - 'Defect Generation' block: Receives MI_LM_DEGM, MI_LM_M, MI_LM_DEGTHR, MI_LM_TFMIN. It outputs alarm signals (aTSF, aRDI[1], nN_LF, nN_TF, nF_LF, nF_TF) to 'Performance monitoring' and 'Defect correlation'. + - 'Performance monitoring' block: Receives MI_TimeStamp1, MI_ISecond, MI_pN_TF, MI_pN_LF, MI_pF_TF, MI_pF_LF, MI_pN_DS, MI_pF_DS, MI_pB_FD, MI_pB_FDV, MI_pF_FD, MI_pF_FDV, MI_pN_FD, MI_pN_FDV. It outputs RI_DM_Result, 1DM_Result, RI_SL_Result to 'Defect correlation' and RI_LMR to 'LMR reception'. + - 'Defect correlation' block: Receives various defect signals and outputs dLOC[i], cUNL, cMMG, cUNM, dDEG[1], dUNP, dUNPr, dRDI[i], dAIS, dLCK, CI_SSF to 'Consequent action'. + - 'CCM reception' block: Receives RI_LMC_Enable, RI_LM_Result, RI_CC_RxFC1, RI_CC_TxFCf. It outputs RI_CC_Pri, RI_CC_Period, RI_PeerMEP_ID[i], RI_MEG_ID, RI_SvdCCM, RI_LMM to 'MEP ProActive-OAM extraction'. + - 'MEP ProActive-OAM extraction' block: A vertical stack of sub-blocks for LMM, LMR, LCK, AIS, DMM, DMR, 1DM, SLM, SLR, ISL, and BNM reception/extraction. It also includes 'Proactive 1DM Control_Sk' and 'Proactive ISL Control_Sk' blocks with Dmux units. + - Bottom: Data paths and counters. Includes 'Data' blocks, 'Counter' blocks, and output signals like ETH_AI_TSF/TSD/AIS, ETH_AI_D/P/DE, ETH_CI_SSF, and ETH_CI_D/P/DE. + - Various other signals and interfaces are shown, such as RI_CC_RDI, RI_CC_Blk, MI_CC_Enable, RI_LM_Result, RI_CC_RxFC1, RI_CC_TxFCf, MI_MEG_ID, MI_PeerMEP_ID[i], MI_CC_Period, MI_CC_Pri, MI_Get_SvdCCM, MI_SvdCCM, MI_cLOC[i], MI_cUNL, MI_cMMG, MI_cUNM, MI_cDEG, MI_cUNP, MI_cUNPr, MI_cRDI, MI_cSSF, MI_cLCK, MI_1DM_Enable, MI_1DM_MAC_SA, MI_1DM_Pri, MI_1DM_Test_ID, MI_1SL_Enable, MI_1SL_MAC_SA, MI_1SL_Test_ID, MI_MEP_MAC, MI_BW_Report, MI_MEL.](0757c1ca2d4a19ca824d92246e610fc7_img.jpg) + +Figure 9-19 – ETHG\_FT\_Sk process diagram. This is a complex functional block diagram showing the internal architecture of an Ethernet G.802.1Y (ETHG) FT\_Sk process. The diagram is organized into several functional blocks: + - Top: 'Consequent action' block receiving inputs like RI\_CC\_RDI, RI\_CC\_Blk, MI\_CC\_Enable, and various alarm signals (aTSF, aTSD, aAIS). It outputs aBLK to a 'Block' and control signals to 'Defect Generation'. + - 'Defect Generation' block: Receives MI\_LM\_DEGM, MI\_LM\_M, MI\_LM\_DEGTHR, MI\_LM\_TFMIN. It outputs alarm signals (aTSF, aRDI[1], nN\_LF, nN\_TF, nF\_LF, nF\_TF) to 'Performance monitoring' and 'Defect correlation'. + - 'Performance monitoring' block: Receives MI\_TimeStamp1, MI\_ISecond, MI\_pN\_TF, MI\_pN\_LF, MI\_pF\_TF, MI\_pF\_LF, MI\_pN\_DS, MI\_pF\_DS, MI\_pB\_FD, MI\_pB\_FDV, MI\_pF\_FD, MI\_pF\_FDV, MI\_pN\_FD, MI\_pN\_FDV. It outputs RI\_DM\_Result, 1DM\_Result, RI\_SL\_Result to 'Defect correlation' and RI\_LMR to 'LMR reception'. + - 'Defect correlation' block: Receives various defect signals and outputs dLOC[i], cUNL, cMMG, cUNM, dDEG[1], dUNP, dUNPr, dRDI[i], dAIS, dLCK, CI\_SSF to 'Consequent action'. + - 'CCM reception' block: Receives RI\_LMC\_Enable, RI\_LM\_Result, RI\_CC\_RxFC1, RI\_CC\_TxFCf. It outputs RI\_CC\_Pri, RI\_CC\_Period, RI\_PeerMEP\_ID[i], RI\_MEG\_ID, RI\_SvdCCM, RI\_LMM to 'MEP ProActive-OAM extraction'. + - 'MEP ProActive-OAM extraction' block: A vertical stack of sub-blocks for LMM, LMR, LCK, AIS, DMM, DMR, 1DM, SLM, SLR, ISL, and BNM reception/extraction. It also includes 'Proactive 1DM Control\_Sk' and 'Proactive ISL Control\_Sk' blocks with Dmux units. + - Bottom: Data paths and counters. Includes 'Data' blocks, 'Counter' blocks, and output signals like ETH\_AI\_TSF/TSD/AIS, ETH\_AI\_D/P/DE, ETH\_CI\_SSF, and ETH\_CI\_D/P/DE. + - Various other signals and interfaces are shown, such as RI\_CC\_RDI, RI\_CC\_Blk, MI\_CC\_Enable, RI\_LM\_Result, RI\_CC\_RxFC1, RI\_CC\_TxFCf, MI\_MEG\_ID, MI\_PeerMEP\_ID[i], MI\_CC\_Period, MI\_CC\_Pri, MI\_Get\_SvdCCM, MI\_SvdCCM, MI\_cLOC[i], MI\_cUNL, MI\_cMMG, MI\_cUNM, MI\_cDEG, MI\_cUNP, MI\_cUNPr, MI\_cRDI, MI\_cSSF, MI\_cLCK, MI\_1DM\_Enable, MI\_1DM\_MAC\_SA, MI\_1DM\_Pri, MI\_1DM\_Test\_ID, MI\_1SL\_Enable, MI\_1SL\_MAC\_SA, MI\_1SL\_Test\_ID, MI\_MEP\_MAC, MI\_BW\_Report, MI\_MEL. + +**Figure 9-19 – ETHG\_FT\_Sk process** + +###### *MEP proactive OAM extraction process* + +The MEP proactive OAM extraction process extracts OAM traffic units that are processed in the ETHx\_FT\_Sk process from the stream of traffic units. This process resides only in the lowest number in the contiguous range of ETH\_FPs or a selected ETH\_FP within the group of arbitrary ETH\_FPs (AIS reception, LCK reception, LMp, and defect generation processes as well). The details of this process are described in clause 9.2.1.2. + +###### *AIS reception process* + +This process generates the AIS event upon receipt of the AIS traffic unit from the OAM MEP extraction process. + +###### *LCK reception process* + +This process generates the LCK event upon receipt of the LCK traffic unit from the OAM MEP extraction process. + +###### *LMM reception* + +This process is defined in clause 8.1.9 where the LM protocol is defined. Clause 8.1.9.4 defines the LMM reception process. + +###### *LMR reception* + +This process is defined in clause 8.1.9 where the LM protocol is defined. Clause 8.1.9.6 defines the LMR reception process. + +###### *LMR Demux* + +The LMR Demux process de-interleaves the incoming signal set (D,P,DE) to the different output ports (X, Y, Z). P signal can be used for the selection of the port. + +###### *DMM reception* + +This process is defined in clause 8.1.10 where the DM protocol is defined. Clause 8.1.10.4 defines the DMM reception process. + +###### *DMR reception* + +This process is defined in clause 8.1.10 where the DM protocol is defined. Clause 8.1.10.6 defines the DMR reception process. + +###### *DMR Demux* + +The DMR Demux process de-interleaves the incoming signal set (D,P,DE) to the different output ports (X, Y, Z). P and/or Test\_ID signal can be used for the selection of the port. + +###### *IDM reception* + +This process is defined in clause 8.1.11 where the IDM protocol is defined. Clause 8.1.11.4 defines the IDM reception process. + +###### *IDM Demux* + +The IDM Demux process de-interleaves the incoming signal set (D,P,DE) to the different output ports (X, Y, Z). P and/or Test\_ID signal can be used for the selection of the port. + +###### *Proactive IDM Control\_Sk* + +This process is defined in clause 8.1.11 where the IDM protocol is defined. Clause 8.1.11.5 defines the IDM Control\_Sk process. + +###### *SLM reception* + +This process is defined in clause 8.1.14 where the SL protocol is defined. Clause 8.1.14.4 defines the SLM reception process. + +###### *SLR reception* + +This process is defined in clause 8.1.14 where the SL protocol is defined. Clause 8.1.14.6 defines the SLR reception process. + +###### *SLR Demux* + +The SLR Demux process de-interleaves the incoming signal set (D,P,DE) to the different output ports (X, Y, Z). P and/or Test\_ID signal can be used for the selection of the port. + +###### *1SL reception* + +This process is defined in clause 8.1.15 where the 1SL protocol is defined. Clause 8.1.15.4 defines the 1SL reception process. + +###### *1SL Demux* + +The 1SL Demux process de-interleaves the incoming signal set (D,P,DE) to the different output ports (X, Y, Z). P and/or Test\_ID signal can be used for the selection of the port. + +###### *Proactive 1SL Control\_Sk* + +This process is defined in clause 8.1.15 where the 1SL protocol is defined. Clause 8.1.15.5 defines the 1SL Control\_Sk process. + +##### *Block process* + +When aBlk is raised, the block process will discard all ETH\_CI information within the group of co-located flow points. If aBLK is cleared, the received ETH\_CI information will be passed to the output port. + +##### *LMp process* + +This process is defined in clause 8.1.7.4. + +##### *Defect generation process* + +This process detects and clears the defects (dLOC[i], dUNL, dMMG, dUNM, dDEG, dUNP, dUNPr, dRDI[i], dAIS, dLCK) as defined in clause 6, where [i] = maintenance entity. + +##### *CCM reception process* + +This process is defined in clause 8.1.7.3. + +##### *Counter process* + +This process is defined in clauses 8.1.7.4 and 8.1.9.7. It is used to count frames for proactive loss measurements with CCM and proactive LM protocols, respectively. + +##### *BNM Extract process* + +This process is defined in clause 8.1.19. + +**Defects** See clause 9.2.1.2. + +**Consequent actions** See clause 9.2.1.2. + +**Defect correlations** See clause 9.2.1.2. + +**Performance monitoring** See clause 9.2.1.2. + +### 9.2.3 ETHnull flow termination functions (ETHnull\_FT) + +The bidirectional ETHnull flow termination (ETHnull\_FT) function is performed by a co-located pair of ETHnull flow termination source (ETHnull\_FT\_So) and sink (ETHnull\_FT\_Sk) functions. These functions exist for the purpose of satisfying the ITU-T G.806 binding rules when terminating ETH sublayers that do not perform OAM. + +#### 9.2.3.1 ETHnull flow termination source function (ETHnull\_FT\_So) + +The ETHnull\_FT\_So function symbol is shown in Figure 9-20 and the interfaces in Table 9-6. + +##### Symbol + +![Symbol for ETHnull_FT_So function. It shows a downward arrow labeled ETH_AP entering a shaded inverted triangle labeled ETHnull, with a downward arrow labeled ETH_TFP exiting from the bottom vertex.](de18140c2e0030a43004b58338467655_img.jpg) + +G.8021-Y.1341(22)\_F9-20 + +Symbol for ETHnull\_FT\_So function. It shows a downward arrow labeled ETH\_AP entering a shaded inverted triangle labeled ETHnull, with a downward arrow labeled ETH\_TFP exiting from the bottom vertex. + +Figure 9-20 – ETHnull\_FT\_So symbol + +##### Interfaces + +Table 9-6 – ETHnull\_FT\_So interfaces + +| Inputs | Outputs | +|-----------------------------------------------------|------------------------------------------------------| +| ETH_AP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE | ETH_TFP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE | + +**Processes** None. + +**Defects** None. + +**Consequent actions** None. + +**Defect correlations** None. + +**Performance monitoring** None. + +#### 9.2.3.2 ETHnull flow termination sink function (ETHnull\_FT\_Sk) + +The ETHnull\_FT\_Sk function symbol is shown in Figure 9-21 and the interfaces in Table 9-7. + +##### **Symbol** + +![Symbol diagram for ETHx_FT_Sk. It shows a downward-pointing triangle labeled 'ETHnull'. An arrow labeled 'ETH_TFP' points into the bottom vertex of the triangle, and an arrow labeled 'ETH_AP' points out of the top vertex. Below the diagram is the text 'G.8021-Y.1341(22)_F9-21'.](61474739fd197587cfea52af9b6a3885_img.jpg) + +Symbol diagram for ETHx\_FT\_Sk. It shows a downward-pointing triangle labeled 'ETHnull'. An arrow labeled 'ETH\_TFP' points into the bottom vertex of the triangle, and an arrow labeled 'ETH\_AP' points out of the top vertex. Below the diagram is the text 'G.8021-Y.1341(22)\_F9-21'. + +**Figure 9-21 – ETHx\_FT\_Sk symbol** + +##### **Interfaces** + +**Table 9-7 – ETHnull\_FT\_So interfaces** + +| Inputs | Outputs | +|--------------------------------------------------------------------|-------------------------------------------------------------------| +| ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF | ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE
ETH_AI_TSF | + +**Processes** None. + +**Defects** None. + +**Consequent actions** aTSF ← CI\_SSF + +**Defect correlations** None. + +**Performance monitoring** None. + +## **9.3 ETH adaptation functions** + +### **9.3.1 ETH to ETH adaptation functions (ETHx/ETH\_A)** + +#### **9.3.1.1 ETH to ETH adaptation source function (ETHx/ETH\_A\_So)** + +This function maps client ETH\_CI traffic units into server ETH\_AI traffic units. The ETHx/ETH\_A\_So function symbol is shown in Figure 9-22, the interfaces in Table 9-8 and the process diagram in Figure 9-23. + +##### **Symbol** + +![Symbol diagram for ETHx/ETH_A_So. It shows a trapezoidal block labeled 'ETHx/ETH'. An arrow labeled 'ETH_FP' points into the top of the block, an arrow labeled 'ETHx/ETH_A_So_MP' points into the left side, and an arrow labeled 'ETH_AP' points out of the bottom. Below the diagram is the text 'G.8021-Y.1341(22)_F9-22'.](5a642532ddbbc4c36cb6de49a4bbeafc_img.jpg) + +Symbol diagram for ETHx/ETH\_A\_So. It shows a trapezoidal block labeled 'ETHx/ETH'. An arrow labeled 'ETH\_FP' points into the top of the block, an arrow labeled 'ETHx/ETH\_A\_So\_MP' points into the left side, and an arrow labeled 'ETH\_AP' points out of the bottom. Below the diagram is the text 'G.8021-Y.1341(22)\_F9-22'. + +**Figure 9-22 – ETHx/ETH\_A\_So symbol** + +##### Interfaces + +**Table 9-8 – ETHx/ETH\_A\_So interfaces** + +| Inputs | Outputs | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| +| ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_APS
ETH_CI_SSF
ETH_CI_SSFrdi
ETH_CI_SSFfdi

ETHx/ETH_A_So_MP:
ETHx/ETH_A_So_MI_MEP_MAC
ETHx/ETH_A_So_MI_Client_MEL
ETHx/ETH_A_So_MI_LCK_Period
ETHx/ETH_A_So_MI_LCK_Pri
ETHx/ETH_A_So_MI_Admin_State
ETHx/ETH_A_So_MI_MEL
ETHx/ETH_A_So_MI_APS_Pri
ETHx/ETH_A_So_MI_CSF_Period
ETHx/ETH_A_So_MI_CSF_Pri
ETHx/ETH_A_So_MI_CSF_Enable
ETHx/ETH_A_So_MI_CSFrdifdiEnable
ETHx/ETH_A_So_MI_CSFdciEnable | ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE | + +##### Processes + +![Figure 9-23 – ETHx/ETH_A_So process block diagram. The diagram shows a vertical flow of data and control signals. At the top, ETH_CI_SSF and ETH_CI_P/DE/D inputs enter a large light blue box. Inside, the flow is: LCK generation block (receiving MI_MEP_MAC, MI_Client_MEL, MI_LCK_Period, MI_LCK_Pri) -> Selector block (Normal/Lock) (receiving MI_Admin_State) -> OAM MEL filter (receiving MI_MEL) -> CSF insert (receiving aCSF-RDI, aCSF-FDI, aCSF-LOS from Consequent actions block, and MI_CSF_Period, MI_CSF_Pri, MI_CSFdciEnable) -> APS insert (receiving ETH_CI_APS and MI_APS_Pri). The output of the APS insert is ETH_AI_P/DE/D. A small label G.8021-Y.1341(22)_F9-23 is at the bottom right of the box.](659defdb54c35d60d4bb11a37b583228_img.jpg) + +Figure 9-23 – ETHx/ETH\_A\_So process block diagram. The diagram shows a vertical flow of data and control signals. At the top, ETH\_CI\_SSF and ETH\_CI\_P/DE/D inputs enter a large light blue box. Inside, the flow is: LCK generation block (receiving MI\_MEP\_MAC, MI\_Client\_MEL, MI\_LCK\_Period, MI\_LCK\_Pri) -> Selector block (Normal/Lock) (receiving MI\_Admin\_State) -> OAM MEL filter (receiving MI\_MEL) -> CSF insert (receiving aCSF-RDI, aCSF-FDI, aCSF-LOS from Consequent actions block, and MI\_CSF\_Period, MI\_CSF\_Pri, MI\_CSFdciEnable) -> APS insert (receiving ETH\_CI\_APS and MI\_APS\_Pri). The output of the APS insert is ETH\_AI\_P/DE/D. A small label G.8021-Y.1341(22)\_F9-23 is at the bottom right of the box. + +Figure 9-23 – ETHx/ETH\_A\_So process + +###### *LCK generation process* + +As defined in clause 8.1.2. + +###### *Selector process* + +As defined in clause 8.1.3. + +###### *OAM MEL filter process* + +As defined in clause 8.1.1. + +##### *CSF insert process* + +As defined in clause 8.1.16. + +##### *APS insert process* + +As defined in clause 8.1.5. + +When this process is activated, LCK admin state shall be unlocked. See clause 7.5.2.2 of [ITU-T G.8010]. + +##### Defects + +None. + +##### Consequent actions + +aCSF-LOS $\leftarrow$ CI\_SSF and MI\_CSFEnable + +aCSF-RDI $\leftarrow$ CI\_SSFrdi and MI\_CSFrdifdiEnable and MI\_CSFEnable + +aCSF-FDI $\leftarrow$ CI\_SSFfdi and MI\_CSFrdifdiEnable and MI\_CSFEnable + +**Defect correlations** None. + +**Performance monitoring** None. + +#### 9.3.1.2 ETH to ETH adaptation sink function (ETHx/ETH\_A\_Sk) + +This function retrieves client ETH\_CI traffic units from server ETH\_AI traffic units. The ETHx/ETH\_A\_Sk function symbol is shown in Figure 9-24, the interfaces in Table 9-9 and the process diagram in Figure 9-25. + +##### Symbol + +![Figure 9-24 – ETHx/ETH_A_Sk symbol. The diagram shows a trapezoidal symbol labeled 'ETHx/ETH'. An arrow labeled 'ETH_AP' points into the bottom of the symbol. An arrow labeled 'ETH_FP' points out of the top of the symbol. A label 'ETHx/ETH_A_Sk_MP' with an arrow points to the right side of the symbol. A small text 'G.8021-Y.1341(22)_F9-24' is located to the right of the symbol.](d74d2943c702ef88a5f9dec974fc92a5_img.jpg) + +Figure 9-24 – ETHx/ETH\_A\_Sk symbol. The diagram shows a trapezoidal symbol labeled 'ETHx/ETH'. An arrow labeled 'ETH\_AP' points into the bottom of the symbol. An arrow labeled 'ETH\_FP' points out of the top of the symbol. A label 'ETHx/ETH\_A\_Sk\_MP' with an arrow points to the right side of the symbol. A small text 'G.8021-Y.1341(22)\_F9-24' is located to the right of the symbol. + +Figure 9-24 – ETHx/ETH\_A\_Sk symbol + +##### Interfaces + +Table 9-9 – ETHx/ETH\_A\_Sk interfaces + +| Inputs | Outputs | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE
ETH_AI_TSF
ETH_AI_TSD
ETH_AI_AIS

ETHx/ETH_A_Sk_MP:
ETHx/ETH_A_Sk_MI_MEP_MAC
ETHx/ETH_A_Sk_MI_Client_MEL
ETHx/ETH_A_Sk_MI_LCK_Period
ETHx/ETH_A_Sk_MI_LCK_Pri
ETHx/ETH_A_Sk_MI_Admin_State
ETHx/ETH_A_Sk_MI_AIS_Period
ETHx/ETH_A_Sk_MI_AIS_Pri
ETHx/ETH_A_Sk_MI_MEL
ETHx/ETH_A_Sk_MI_CSF_Reported
ETHx/ETH_A_Sk_MI_CSFrdifdiEnable | ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_APS
ETH_CI_SSF
ETH_CI_SSFrdi
ETH_CI_SSFfdi
ETH_CI_SSD

ETHx/ETH_A_Sk_MP:
ETHx/ETH_A_Sk_MI_cCSF | + +##### Processes + +![Figure 9-25 – ETHx/ETH_A_Sk process block diagram. The diagram shows a vertical stack of process blocks: APS extract, CSF extract, OAM MEL filter, AIS insert, and Selector (with Normal and Lock sub-blocks). Data flows are indicated by arrows with labels like P, DE, D, aSSF, aAIS, and dCSF. Management Information (MI) inputs and outputs are shown on the left and right sides, including MI_Admin_State, MI_CSFrdifdiEnable, MI_cCSF, MI_CSF_Reported, MI_MEL, MI_AIS_Period, MI_AIS_Pri, MI_LCK_Period, MI_LCK_Pri, MI_Client_MEL, and MI_MEP_MAC. External interface labels include ETH_CI_SSF, ETH_CI_SSD, ETH_CI_APS, ETH_CI_P/DE/D, ETH_AI_TSF/AIS/TSD, and ETH_AI_P/DE/D. A reference code G.8021-Y.1341(22)_F9-25 is at the bottom right.](dc075f714892571abc5f74f1a76b80dc_img.jpg) + +Figure 9-25 – ETHx/ETH\_A\_Sk process block diagram. The diagram shows a vertical stack of process blocks: APS extract, CSF extract, OAM MEL filter, AIS insert, and Selector (with Normal and Lock sub-blocks). Data flows are indicated by arrows with labels like P, DE, D, aSSF, aAIS, and dCSF. Management Information (MI) inputs and outputs are shown on the left and right sides, including MI\_Admin\_State, MI\_CSFrdifdiEnable, MI\_cCSF, MI\_CSF\_Reported, MI\_MEL, MI\_AIS\_Period, MI\_AIS\_Pri, MI\_LCK\_Period, MI\_LCK\_Pri, MI\_Client\_MEL, and MI\_MEP\_MAC. External interface labels include ETH\_CI\_SSF, ETH\_CI\_SSD, ETH\_CI\_APS, ETH\_CI\_P/DE/D, ETH\_AI\_TSF/AIS/TSD, and ETH\_AI\_P/DE/D. A reference code G.8021-Y.1341(22)\_F9-25 is at the bottom right. + +Figure 9-25 – ETHx/ETH\_A\_Sk process + +##### *APS extract process* + +As defined in clause 8.1.6. + +##### *CSF extract process* + +As defined in clause 8.1.17. + +##### *OAM MEL filter process* + +As defined in clause 8.1.1. + +##### *AIS insert process* + +As defined in clause 8.1.4. + +##### *LCK generation process* + +As defined in clause 8.1.2. + +##### *Selector process* + +As defined in clause 8.1.3. + +##### Defects + +dCSF-LOS – See clause 6.1.5.4. + +dCSF-RDI – See clause 6.1.5.4. + +dCSF-FDI – See clause 6.1.5.4. + +##### Consequent actions + +aSSF $\leftarrow$ (AI\_TSF or dCSF-LOS) and (not MI\_Admin\_State == Locked) + +aSSFrdi $\leftarrow$ dCSF-RDI and MI\_CSFrdifdiEnable + +aSSSfdi $\leftarrow$ dCSF-FDI and MI\_CSFrdifdiEnable + +aAIS $\leftarrow$ AI\_AIS + +##### Defect correlations + +cCSF $\leftarrow$ (dCSF-LOS or dCSF-RDI or dCSF-FDI) and (not AI\_TSF) and MI\_CSF\_Reported + +##### Performance monitoring + +None. + +### 9.3.2 ETH to ETH multiplexing adaptation functions (ETHx/ETH-m\_A) + +This adaptation function multiplexes different ETH\_CI streams into a single ETH\_AI stream in the source direction and demultiplexes the ETH\_AI stream into individual ETH\_CI streams. The ETHx/ETH-m\_A function symbol is shown in Figure 9-26. + +###### Symbol + +![Figure 9-26: ETHx/ETH-m_A symbol diagram](b891f5bfe75fc06bab1fea98d7947c04_img.jpg) + +The diagram shows a trapezoidal symbol labeled 'ETHx/ETH-m'. On the left, a horizontal line labeled 'ETHx/ETH-m\_A\_MP' enters the symbol. On the top, two vertical lines labeled 'ETH\_TFP' and 'ETH\_FP' enter the symbol. On the bottom, a vertical line labeled 'ETH\_AP' exits the symbol. Below the symbol, the text 'G.8021-Y.1341(22)\_F9-26' is present. + +Figure 9-26: ETHx/ETH-m\_A symbol diagram + +Figure 9-26 – ETHx/ETH-m\_A symbol + +The ETHx/ETH-m\_A function is further decomposed into separate source and sink adaptation functions that are interconnected as shown in Figure 9-27. + +![Figure 9-27: ETHx/ETH-m_A source and sink symbols diagram](31de31bf5e79a328e5ea7f985add6e3d_img.jpg) + +The diagram shows two trapezoidal symbols, both labeled 'ETHx/ETH-m'. The left symbol (source) has a horizontal line labeled 'ETHx/ETH-m\_A\_So\_MP' entering from the left, vertical lines labeled 'ETH\_TFP' and 'ETH\_FP' entering from the top, and a vertical line labeled 'ETH\_AP' exiting from the bottom. The right symbol (sink) has a vertical line labeled 'ETH\_AP' entering from the bottom, vertical lines labeled 'ETH\_TFP' and 'ETH\_FP' exiting to the top, and a horizontal line labeled 'ETHx/ETH-m\_A\_Sk\_MP' exiting to the right. Between the two symbols, two horizontal lines labeled 'ETHTF\_PP' and 'ETHF\_PP' connect them. Below the right symbol, the text 'G.8021-Y.1341(22)\_F9-27' is present. + +Figure 9-27: ETHx/ETH-m\_A source and sink symbols diagram + +Figure 9-27 – ETHx/ETH-m\_A source and sink symbols + +#### 9.3.2.1 ETH to ETH multiplexing adaptation source function (ETHx/ETH-m\_A\_So) + +This function multiplexes individual ETH\_CI streams into a single ETH\_AI stream. The ETHx/ETH-m\_A\_So function symbol is shown in Figure 9-28, the interfaces in Table 9-10 and the process diagram in Figure 9-29. + +##### Symbol + +![Figure 9-28 – ETHx/ETH-m_A_So symbol. The diagram shows a trapezoidal block labeled 'ETHx/ETH-m'. Inputs include ETH_TFP and multiple ETH_FP streams entering from the top, and ETHx/ETH-m_A_So_MP entering from the left. Outputs include ETH_TF_PP and ETHF_PP exiting to the right, and ETH_AP exiting from the bottom. A reference code G.8021-Y.1341(22)_F9-28 is shown in the bottom right.](0073ee258067e591778333101c5d2edb_img.jpg) + +Figure 9-28 – ETHx/ETH-m\_A\_So symbol. The diagram shows a trapezoidal block labeled 'ETHx/ETH-m'. Inputs include ETH\_TFP and multiple ETH\_FP streams entering from the top, and ETHx/ETH-m\_A\_So\_MP entering from the left. Outputs include ETH\_TF\_PP and ETHF\_PP exiting to the right, and ETH\_AP exiting from the bottom. A reference code G.8021-Y.1341(22)\_F9-28 is shown in the bottom right. + +Figure 9-28 – ETHx/ETH-m\_A\_So symbol + +##### Interfaces + +Table 9-10 – ETHx/ETH-m\_A\_So interfaces + +| Inputs | Outputs | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_FP:
ETH_CI_D[1...M]
ETH_CI_P[1...M]
ETH_CI_DE[1...M]
ETH_CI_SSF[1]
ETH_CI_SSFrdi[1]
ETH_CI_SSFfdi[1]

ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE

ETHx/ETH-m_A_So_MP:
ETHx/ETH-m_A_So_MI_MEP_MAC
ETHx/ETH-m_A_So_MI_Client_MEL[1...M]
ETHx/ETH-m_A_So_MI_LCK_Period[1...M]
ETHx/ETH-m_A_So_MI_LCK_Pri[1...M]
ETHx/ETH-m_A_So_MI_Admin_State
ETHx/ETH-m_A_So_MI_VLAN_Config[1...M]
ETHx/ETH-m_A_So_MI_Etype
ETHx/ETH-m_A_So_MI_PCP_Config
ETHx/ETH-m_A_So_MI_MEL
ETHx/ETH-m_A_So_MI_CSF_Period
ETHx/ETH-m_A_So_MI_CSF_Pri
ETHx/ETH-m_A_So_MI_CSF_Enable
ETHx/ETH-m_A_So_MI_CSFrdifdiEnable
ETHx/ETH-m_A_So_MI_CSFdciEnable | ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE

ETHF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ETHTF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE | + +##### Processes + +![Figure 9-29 – ETHx/ETH-m_A_So process block diagram. The diagram shows the flow of Ethernet signals (P, D, DE) through various processing blocks. Inputs include ETH_CI_SSF, ETH_CI_P/DE/D, and ETH_TFP. The signal passes through LCK generation blocks (with Normal/Lock Selectors), VID MUX (ports X, Y, Z), P replicate, VLAN TAG, DE generation, Replicate, OAM MEL filter, and CSF insert. Outputs include ETH_TFP, ETH_PI_P, ETH_PI_DE, ETH_PI_D, and ETH_AI_P/DE/D. Management Interface (MI) parameters like MI_MEP_MAC, MI_VLAN_Config, and MI_CSF_Period are shown as inputs to the blocks.](42d1ffab6bbf720e8421aeace0808924_img.jpg) + +The diagram illustrates the ETHx/ETH-m\_A\_So process. At the top, three input signal sets (P, D, DE) from ETH\_CI\_P/DE/D and ETH\_CI\_SSF enter three parallel LCK generation blocks. Each block contains a 'Normal' and 'Lock' Selector. These are followed by a VID MUX with three input ports (X, Y, Z). The VID MUX outputs are processed by a 'P replicate' block and a 'VLAN TAG' block. The 'VLAN TAG' block also receives inputs from 'MI\_Etype' and 'MI\_PCP\_Config'. Below the VLAN TAG is a 'DE generation' block. The signal then enters a 'Replicate' block, which outputs to 'ETH\_PI\_P', 'ETH\_PI\_DE', and 'ETH\_PI\_D'. Next is an 'OAM MEL filter' block, followed by a 'CSF insert' block. The 'CSF insert' block receives inputs from 'MI\_CSF\_Period', 'MI\_CSF\_Pri', and 'MI\_CSF\_dciEnable'. The final output is 'ETH\_AI\_P/DE/D'. A 'Consequent actions' block on the left receives 'MI\_CSF\_Enable' and 'MI\_CSFrdifdiEnable' and sends 'aCSF\_RDI', 'aCSF\_FDI', and 'aCSF\_LOS' to the CSF insert block. Various other MI parameters like 'MI\_MEP\_MAC', 'MI\_Client\_MEL[1..M]', 'MI\_LCK\_Period[1..M]', 'MI\_LCK\_Pri[1..M]', 'MI\_Admin\_State', 'MI\_VLAN\_Config[1..M]', and 'MI\_MEL' are shown as inputs to the respective blocks. + +Figure 9-29 – ETHx/ETH-m\_A\_So process block diagram. The diagram shows the flow of Ethernet signals (P, D, DE) through various processing blocks. Inputs include ETH\_CI\_SSF, ETH\_CI\_P/DE/D, and ETH\_TFP. The signal passes through LCK generation blocks (with Normal/Lock Selectors), VID MUX (ports X, Y, Z), P replicate, VLAN TAG, DE generation, Replicate, OAM MEL filter, and CSF insert. Outputs include ETH\_TFP, ETH\_PI\_P, ETH\_PI\_DE, ETH\_PI\_D, and ETH\_AI\_P/DE/D. Management Interface (MI) parameters like MI\_MEP\_MAC, MI\_VLAN\_Config, and MI\_CSF\_Period are shown as inputs to the blocks. + +G.8021-Y.1341(22)\_F9-29 + +Figure 9-29 – ETHx/ETH-m\_A\_So process + +###### LCK generation process + +As defined in clause 8.1.2. Each FP has its LCK generation process. + +###### Selector process + +As defined in clause 8.1.3. The normal CI is blocked if Admin\_State = LOCKED. + +###### VID Mux process + +The VID MUX process interleaves the signal sets (P, D, DE) from the input ports (X, Y, Z). For each incoming signal set on forwarding the signal set, a VID signal is generated. The value of the VID signal is based on the port on which the signal set is received and the configuration from the MI\_VLAN\_Config input parameter. + +The MI\_VLAN\_Config input parameter determines for every input port the associated VID value. The allowed values for the VID signal are untagged, priority tagged and 1-4094. The following restriction applies to the allowed MI\_VLAN\_Config values: + +- every VID value is only used once. + +Note that IEEE 802.1 standards do not allow IEEE bridges to generate priority tagged frames. Priority tagged frames are only generated by end stations. However, a C-VLAN bridge may create S-VLAN priority tagged frames. + +###### *VLAN tag process* + +This process inserts a VLAN tag into the MSDU field of the incoming D signal. The EtherType used is determined by the value of the MI\_Etype input parameter. The MI\_PCP\_Config signal determines the encoding of the P and DE signals in the VLAN tag. This parameter defines a mapping from P value to PCP value in the case of C-VLAN tags, and from P value to PCP and drop eligible identifier (DEI) value in the case of S-VLAN tags. + +The VID signal determines the VID value in the VLAN tag. If the VID signal equals priority tagged, the VID value used is 0. If the VID signal equals untagged, no VLAN tag is inserted in the MSDU field. + +###### *P replicate process* + +The P replicate process replicates the incoming P signal to both output ports without changing the value of the signal. + +##### *DE generation process* + +The DE generation process generates a DE signal with the value drop ineligible. + +###### *Replicate process* + +As defined in clause 8.4. + +##### *OAM MEL filter process* + +As defined in clause 8.1.1. + +##### *CSF insert process* + +As defined in clause 8.1.16. The ETHx/ETH-m adaptation function generates a single OAM flow while it can accommodate multiple ETH APs. In the case of using multiple APs, the CSF signal is supported at only a representative OAM flow. + +**Defects** None. + +##### **Consequent actions** + +aCSF-LOS $\leftarrow$ CI\_SSF and MI\_CSFEnable + +aCSF-RDI $\leftarrow$ CI\_SSFrdi and MI\_CSFrdifdiEnable and MI\_CSFEnable + +aCSF-FDI $\leftarrow$ CI\_SSFfdi and MI\_CSFrdifdiEnable and MI\_CSFEnable + +**Defect correlations** None. + +**Performance monitoring** None. + +#### **9.3.2.2 ETH to ETH multiplexing adaptation sink function (ETHx/ETH-m\_A\_Sk)** + +The ETHx/ETH-m\_A\_Sk function symbol is shown in Figure 9-30, the interfaces in Table 9-11 and the process diagram in Figure 9-31. + +##### Symbol + +![Symbol diagram for ETHx/ETH-m_A_Sk. The symbol is a trapezoid labeled 'ETHx/ETH-m'. Inputs from the left are ETH_TFP, ETH_PP, and ETHF_PP. Inputs from the bottom are ETH_AP. Output to the right is ETHx/ETH-m_A_Sk_MP. Output to the top is ETH_FP, with a dashed line indicating multiple outputs.](f54b2e4444e410765295be668123f27a_img.jpg) + +G.8021-Y.1341(22)\_F9-30 + +Symbol diagram for ETHx/ETH-m\_A\_Sk. The symbol is a trapezoid labeled 'ETHx/ETH-m'. Inputs from the left are ETH\_TFP, ETH\_PP, and ETHF\_PP. Inputs from the bottom are ETH\_AP. Output to the right is ETHx/ETH-m\_A\_Sk\_MP. Output to the top is ETH\_FP, with a dashed line indicating multiple outputs. + +Figure 9-30 – ETHx/ETH-m\_A\_Sk symbol + +##### Interfaces + +Table 9-11 – ETHx/ETH-m\_A\_Sk interfaces + +| Inputs | Outputs | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE
ETH_AI_TSF
ETH_AI_AIS

ETHF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ETHF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ETHx/ETH-m_A_Sk_MP:
ETHx/ETH-m_A_Sk_MI_MEP_MAC
ETHx/ETH-m_A_Sk_MI_Client_MEL[1...M]
ETHx/ETH-m_A_Sk_MI_LCK_Period[1...M]
ETHx/ETH-m_A_Sk_MI_LCK_Pri[1...M]
ETHx/ETH-m_A_Sk_MI_Admin_State
ETHx/ETH-m_A_Sk_MI_AIS_Period[1...M]
ETHx/ETH-m_A_Sk_MI_AIS_Pri[1...M]
ETHx/ETH-m_A_Sk_MI_VLAN_Config[1...M]
ETHx/ETH-m_A_Sk_MI_P_Regenerate
ETHx/ETH-m_A_Sk_MI_PVID
ETHx/ETH-m_A_Sk_MI_PCP_Config
ETHx/ETH-m_A_Sk_MI_Etype
ETHx/ETH-m_A_Sk_MI_MEL
ETHx/ETH-m_A_Sk_MI_CSF_Reported
ETHx/ETH-m_A_Sk_MI_CSFdifdiEnable
ETHx/ETH-m_A_Sk_MI_Frametype_Config
ETHx/ETH-m_A_Sk_MI_FilterConfig | ETH_FP:
ETH_CI_D[1...M]
ETH_CI_P[1...M]
ETH_CI_DE[1...M]
ETH_CI_SSF[1...M]
ETH_CI_SSFrdi[1]
ETH_CI_SSFfdi[1]

ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE

ETHx/ETH-m_A_Sk_MP:
ETHx/ETH-m_A_Sk_MI_cCSF | + +##### Processes + +![Figure 9-31 – ETHx/ETH-m_A_Sk process block diagram. The diagram shows a complex signal processing flow for Ethernet frames. At the bottom, an 'ETH AI P/DE/D' input enters a 'Replicate' block. The output of 'Replicate' goes through a 'Filter' block, then a 'Frame type filter' block, then a 'CSF extract' block. The 'CSF extract' block connects to 'Defect generation' and 'Defect correlations' blocks. 'Defect correlations' connects to 'Consequent actions' block. 'Consequent actions' block connects to 'MI_CSFrdifdEnable' and 'MI_CSF_ Reported' inputs. The 'CSF extract' block also connects to an 'OAM MEL filter' block. The 'OAM MEL filter' block connects to 'P selector', 'DE selector', and 'VLAN TAG' blocks. 'P selector' connects to 'P regeneration' block. 'DE selector' connects to 'VLAN TAG' block. 'VLAN TAG' block connects to 'VID DEMUX' block. 'VID DEMUX' block has three outputs labeled X, Y, and Z. Output X connects to an 'AIS insert' block. Output Y connects to an 'AIS insert' block. Output Z connects to an 'AIS insert' block. Each 'AIS insert' block connects to a 'LCK generation' block. Each 'LCK generation' block connects to a 'Selector' block. Each 'Selector' block has 'Normal' and 'Lock' outputs. The 'Normal' output of each 'Selector' block connects to an 'ETH CI_P/DE/D' output. The 'Lock' output of each 'Selector' block connects to an 'ETH CI_SSF' output. The 'ETH CI_SSF' output connects to an 'ETH_TFP' output. The 'ETH_TFP' output connects to 'ETH CI_P/DE/D' and 'ETH CI_SSF' inputs. The 'MI_Admin_State' input connects to 'Consequent actions' block. The 'MI_P_ Regenerate' input connects to 'P regeneration' block. The 'MI_PVID', 'MI_PCP_Config', and 'MI_Etype' inputs connect to 'VLAN TAG' block. The 'MI_MEL' input connects to 'OAM MEL filter' block. The 'MI_Frametype_Config' input connects to 'Frame type filter' block. The 'MI_FilterConfig' input connects to 'Filter' block. The 'MI_VLAN_Config[1...M]' input connects to 'VID DEMUX' block. The 'MI_AIS_Period[1...M]' and 'MI_AIS_Pri[1...M]' inputs connect to 'AIS insert' blocks. The 'MI_LCK_Period[1...M]' and 'MI_LCK_Pri[1...M]' inputs connect to 'LCK generation' blocks. The 'MI_MEP_MAC' and 'MI_Client_MEL[1...M]' inputs connect to 'LCK generation' blocks. The 'MI_Admin_State' input also connects to 'LCK generation' blocks. The 'G.8021-Y.1341(18)_F9-31' label is at the bottom right.](cccf3125a7354e1865653731de1ca03d_img.jpg) + +Figure 9-31 – ETHx/ETH-m\_A\_Sk process block diagram. The diagram shows a complex signal processing flow for Ethernet frames. At the bottom, an 'ETH AI P/DE/D' input enters a 'Replicate' block. The output of 'Replicate' goes through a 'Filter' block, then a 'Frame type filter' block, then a 'CSF extract' block. The 'CSF extract' block connects to 'Defect generation' and 'Defect correlations' blocks. 'Defect correlations' connects to 'Consequent actions' block. 'Consequent actions' block connects to 'MI\_CSFrdifdEnable' and 'MI\_CSF\_ Reported' inputs. The 'CSF extract' block also connects to an 'OAM MEL filter' block. The 'OAM MEL filter' block connects to 'P selector', 'DE selector', and 'VLAN TAG' blocks. 'P selector' connects to 'P regeneration' block. 'DE selector' connects to 'VLAN TAG' block. 'VLAN TAG' block connects to 'VID DEMUX' block. 'VID DEMUX' block has three outputs labeled X, Y, and Z. Output X connects to an 'AIS insert' block. Output Y connects to an 'AIS insert' block. Output Z connects to an 'AIS insert' block. Each 'AIS insert' block connects to a 'LCK generation' block. Each 'LCK generation' block connects to a 'Selector' block. Each 'Selector' block has 'Normal' and 'Lock' outputs. The 'Normal' output of each 'Selector' block connects to an 'ETH CI\_P/DE/D' output. The 'Lock' output of each 'Selector' block connects to an 'ETH CI\_SSF' output. The 'ETH CI\_SSF' output connects to an 'ETH\_TFP' output. The 'ETH\_TFP' output connects to 'ETH CI\_P/DE/D' and 'ETH CI\_SSF' inputs. The 'MI\_Admin\_State' input connects to 'Consequent actions' block. The 'MI\_P\_ Regenerate' input connects to 'P regeneration' block. The 'MI\_PVID', 'MI\_PCP\_Config', and 'MI\_Etype' inputs connect to 'VLAN TAG' block. The 'MI\_MEL' input connects to 'OAM MEL filter' block. The 'MI\_Frametype\_Config' input connects to 'Frame type filter' block. The 'MI\_FilterConfig' input connects to 'Filter' block. The 'MI\_VLAN\_Config[1...M]' input connects to 'VID DEMUX' block. The 'MI\_AIS\_Period[1...M]' and 'MI\_AIS\_Pri[1...M]' inputs connect to 'AIS insert' blocks. The 'MI\_LCK\_Period[1...M]' and 'MI\_LCK\_Pri[1...M]' inputs connect to 'LCK generation' blocks. The 'MI\_MEP\_MAC' and 'MI\_Client\_MEL[1...M]' inputs connect to 'LCK generation' blocks. The 'MI\_Admin\_State' input also connects to 'LCK generation' blocks. The 'G.8021-Y.1341(18)\_F9-31' label is at the bottom right. + +Figure 9-31 – ETHx/ETH-m\_A\_Sk process + +###### Replicate process + +As defined in clause 8.4. + +###### Filter process + +As defined in clause 8.3. + +###### *Frame type filter process* + +The frame type filter process filters the ETH\_CI depending on the value of the MI\_frametype\_Config input parameter. There are three possible values for this parameter: + +- All Frames +- Only VLAN Tagged +- Only Untagged and Priority Tagged. + +If the value of MI\_frametype\_Config equals "All Frames", all ETH\_CI is passed through. For the other two values, the process inspects the MSDU field of the ETH\_CI\_D signal. It inspects the length/type field and, if applicable, the VID field. + +If MI\_frametype\_Config is set to "Only Untagged and Priority Tagged", all frames with L/T equals MI\_Etype and VID in the range 1...4094 are filtered. + +If MI\_frametype\_Config is set to "Only VLAN Tagged", all frames with L/T not equal to MI\_Etype and all frames with L/T equal to MI\_Etype and VID equal to zero are filtered. + +###### *CSF extract process* + +As defined in clause 8.1.17. The ETHx/ETH-m adaptation function generates a single OAM flow while it can accommodate multiple ETH APs. In the case of using multiple APs, the CSF signal is supported at only a representative OAM flow. + +##### *OAM MEL filter process* + +As defined in clause 8.1.1. + +##### *VLAN tag process* + +The VLAN tag process inspects the incoming D signal; if the value in the L/T field is equal to the value provisioned by the MI\_Etype input parameter a VLAN tag is present in the D signal. + +If there is no VLAN tag present the VID signal gets the value presented by the MI\_PVID input parameter. + +If there is a VLAN tag present the VLAN tag process extracts the P, DE and VID information from this VLAN tag. The VID value is taken from the VID field in the VLAN tag. The P and DE values are decoded from the PCP field of the VLAN tag (C-VLAN) or from the PCP and DEI fields of the VLAN tag (S-VLAN), using the decoding information presented via the MI\_PCP\_Config input parameter. The P value is presented to the P selector process and the DE value is presented to the DE selector process. + +##### *DE selector process* + +This process forwards the incoming DE signal. If there is no incoming DE signal present, it generates a DE signal with the value drop ineligible. + +##### *P selector process* + +This process forwards the P signal coming from the VLAN tag process. If this signal is not present, the P signal coming from the OAM MEL process is forwarded. + +##### *P regeneration process* + +This process regenerates the incoming P signal, based on the MI\_P\_Regenerate input signal. The MI\_P\_Regenerate signal specifies a mapping table from P value to P value. + +##### *VID Demux process* + +The VID Demux process de-interleaves the incoming signal set (DE, P, D) to the different ports (X, Y, Z in Figure 9-31). The VID signal determines the port to be selected, based on the MI\_Vlan\_Config input parameter. + +The MI\_Vlan\_Config parameter specifies the possible VID values for the ports to be used. If there is no port assigned to a specific VID value and this VID value is used, the VID Demux process will filter the incoming signal set. + +Disabling the ingress VID filtering is modelled by setting MI\_Vlan\_Config [1...4094]. Refer to Appendix VIII. + +##### *AIS insert process* + +As defined in clause 8.1.4. + +###### *LCK generation process* + +As defined in clause 8.1.2. Each FP has its own LCK generation process. + +###### *Selector process* + +As defined in clause 8.1.3. The normal CI is blocked if Admin\_State = LOCKED. + +##### **Defects** + +dCSF-LOS – See clause 6.1.5.4. + +dCSF-RDI – See clause 6.1.5.4. + +dCSF-FDI – See clause 6.1.5.4. + +##### **Consequent actions** + +aSSF[1] $\leftarrow$ (AI\_TSF or dCSF\_LOS) and (not MI\_Admin\_State == Locked) + +aSSFrdfi[1] $\leftarrow$ dCSF-RDI and MI\_CSFrdifdiEnable + +aSSFfdi[1] $\leftarrow$ dCSF-FDI and MI\_CSFrdifdiEnable + +aSSF[2...M] $\leftarrow$ AI\_TSF and (not MI\_Admin\_State == Locked) + +aAIS $\leftarrow$ AI\_AIS + +##### **Defect correlations** + +cCSF $\leftarrow$ (dCSF-LOS or dCSF-RDI or dCSF-FDI) and (not AI\_TSF) and MI\_CSF\_Reported + +**Performance monitoring** None. + +### **9.3.3 ETH group to ETH adaptation functions (ETHG/ETH\_A)** + +#### **9.3.3.1 ETH group to ETH adaptation source function (ETHG/ETH\_A\_So)** + +The ETHG/ETH\_A\_So function symbol is shown in Figure 9-32, the interfaces in Table 9-12 and the process diagram in Figure 9-33. + +##### Symbol + +![Symbol diagram for ETHG/ETH_A_So. It shows a trapezoidal block labeled 'ETHG/ETH'. A single input arrow labeled 'ETHG/ETH_A_So_MP' enters from the left. Multiple output arrows labeled 'ETH_FP' exit from the top. Multiple output arrows labeled 'ETH_AP' exit from the bottom. A small text 'G.8021-Y.1341(22)_F9-32' is located to the right of the block.](826bf067afc22bf94cdd2faf3e595893_img.jpg) + +Symbol diagram for ETHG/ETH\_A\_So. It shows a trapezoidal block labeled 'ETHG/ETH'. A single input arrow labeled 'ETHG/ETH\_A\_So\_MP' enters from the left. Multiple output arrows labeled 'ETH\_FP' exit from the top. Multiple output arrows labeled 'ETH\_AP' exit from the bottom. A small text 'G.8021-Y.1341(22)\_F9-32' is located to the right of the block. + +Figure 9-32 – ETHG/ETH\_A\_So symbol + +##### Interfaces + +Table 9-12 – ETHG/ETH\_A\_So interfaces + +| Inputs | Outputs | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------| +| ETH_FP:
ETH_CI_D[1..M]
ETH_CI_P[1..M]
ETH_CI_DE[1..M]
ETH_CI_APS
ETH_CI_SSF[1]
ETH_CI_SSFrdi[1]
ETH_CI_SSFfdi[1]

ETHG/ETH_A_So_MP:
ETHG/ETH_A_So_MI_MEP_MAC
ETHG/ETH_A_So_MI_Client_MEL[1..M]
ETHG/ETH_A_So_MI_LCK_Period[1..M]
ETHG/ETH_A_So_MI_LCK_Pri[1..M]
ETHG/ETH_A_So_MI_Admin_State
ETHG/ETH_A_So_MI_MEL
ETHG/ETH_A_So_MI_APS_Pri
ETHG/ETH_A_So_MI_CSF_Period
ETHG/ETH_A_So_MI_CSF_Pri
ETHG/ETH_A_So_MI_CSF_Enable
ETHG/ETH_A_So_MI_CSFrdifdiEnable
ETHG/ETH_A_So_MI_CSFdciEnable | ETH_AP:
ETH_AI_D[1..M]
ETH_AI_P[1..M]
ETH_AI_DE[1..M] | + +##### Processes + +![Figure 9-33 – ETHG/ETH_A_So process diagram. The diagram shows three parallel processing paths for Ethernet interfaces. Each path consists of an 'LCK generation' block, a 'Selector' block (with 'Normal' and 'Lock' inputs), and an 'OAM MEL filter' block. The 'LCK generation' blocks receive inputs from 'ETH_CI_SSF' and 'ETH_CI_P/DE/D'. The 'Selector' blocks receive inputs from 'LCK generation' and 'MI_Admin_State'. The 'OAM MEL filter' block receives inputs from the 'Selector' blocks and 'MI_MEL'. Below the 'OAM MEL filter', there are 'Consequent actions', 'CSF insert', and 'APS insert' blocks. The 'Consequent actions' block receives inputs from 'MI_CSF_Enable', 'MI_CSFrdifdiEnable', 'MI_CSF_Period', 'MI_CSF_Pri', and 'MI_CSFdicEnable', and outputs 'aCSF_RDI', 'aCSF_FDI', and 'aCSF_LOS'. The 'CSF insert' block receives inputs from 'Consequent actions', 'MI_MEP_MAC', and 'MI_MEL', and outputs 'ETH_AI_P/DE/D'. The 'APS insert' block receives inputs from 'ETH_CI_APS', 'MI_APS_Pri', 'MI_MEP_MAC', and 'MI_MEL', and outputs 'ETH_AI_P/DE/D'. The diagram is labeled G.8021-Y.1341(22)_F9-33.](6225dab0a1f85409f526e7b5c4b4f393_img.jpg) + +Figure 9-33 – ETHG/ETH\_A\_So process diagram. The diagram shows three parallel processing paths for Ethernet interfaces. Each path consists of an 'LCK generation' block, a 'Selector' block (with 'Normal' and 'Lock' inputs), and an 'OAM MEL filter' block. The 'LCK generation' blocks receive inputs from 'ETH\_CI\_SSF' and 'ETH\_CI\_P/DE/D'. The 'Selector' blocks receive inputs from 'LCK generation' and 'MI\_Admin\_State'. The 'OAM MEL filter' block receives inputs from the 'Selector' blocks and 'MI\_MEL'. Below the 'OAM MEL filter', there are 'Consequent actions', 'CSF insert', and 'APS insert' blocks. The 'Consequent actions' block receives inputs from 'MI\_CSF\_Enable', 'MI\_CSFrdifdiEnable', 'MI\_CSF\_Period', 'MI\_CSF\_Pri', and 'MI\_CSFdicEnable', and outputs 'aCSF\_RDI', 'aCSF\_FDI', and 'aCSF\_LOS'. The 'CSF insert' block receives inputs from 'Consequent actions', 'MI\_MEP\_MAC', and 'MI\_MEL', and outputs 'ETH\_AI\_P/DE/D'. The 'APS insert' block receives inputs from 'ETH\_CI\_APS', 'MI\_APS\_Pri', 'MI\_MEP\_MAC', and 'MI\_MEL', and outputs 'ETH\_AI\_P/DE/D'. The diagram is labeled G.8021-Y.1341(22)\_F9-33. + +Figure 9-33 – ETHG/ETH\_A\_So process + +###### *LCK generation process* + +As defined in clause 8.1.2. There is a single LCK generation process for each ETH. + +###### *Selector process* + +As defined in clause 8.1.3. The normal CI of each input is blocked if Admin\_State = LOCKED. + +###### *OAM MEL filter process* + +As defined in clause 8.1.1. + +###### *APS insert process* + +As defined in clause 8.1.5. + +##### *CSF insert process* + +As defined in clause 8.1.16. + +**Defects** None. + +##### **Consequent actions** + +$aCSF-LOS \leftarrow CI\_SSF \text{ and } MI\_CSFEnable$ + +$aCSF-RDI \leftarrow CI\_SSFrdi \text{ and } MI\_CSFrdifdiEnable \text{ and } MI\_CSFEnable$ + +$aCSF-FDI \leftarrow CI\_SSFfdi \text{ and } MI\_CSFrdifdiEnable \text{ and } MI\_CSFEnable$ + +**Defect correlations** None. + +**Performance Monitoring** None. + +#### **9.3.3.2 ETH group to ETH adaptation sink function (ETHG/ETH\_A\_Sk)** + +The ETHG/ETH\_A\_Sk function symbol is shown in Figure 9-34, the interfaces in Table 9-13 and the process diagram in Figure 9-35. + +##### **Symbol** + +![Symbol diagram for ETHG/ETH_A_Sk function. It shows a trapezoidal block labeled 'ETHG/ETH'. Above the block, three arrows point upwards labeled 'ETH_FP', with a dashed line between the middle and right arrows. Below the block, three arrows point upwards labeled 'ETH_AP', also with a dashed line between the middle and right arrows. To the right of the block, a double-headed arrow points to the block labeled 'ETHG/ETH_A_Sk_MP'. A small text 'G.8021-Y.1341(22)_F9-34' is at the bottom right.](b18f943d96bfcb2b1360a27b9e45e11e_img.jpg) + +Symbol diagram for ETHG/ETH\_A\_Sk function. It shows a trapezoidal block labeled 'ETHG/ETH'. Above the block, three arrows point upwards labeled 'ETH\_FP', with a dashed line between the middle and right arrows. Below the block, three arrows point upwards labeled 'ETH\_AP', also with a dashed line between the middle and right arrows. To the right of the block, a double-headed arrow points to the block labeled 'ETHG/ETH\_A\_Sk\_MP'. A small text 'G.8021-Y.1341(22)\_F9-34' is at the bottom right. + +**Figure 9-34 – ETHG/ETH\_A\_Sk symbol** + +##### **Interfaces** + +**Table 9-13 – ETHG/ETH\_A\_Sk interfaces** + +| Inputs | Outputs | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_AP:
ETH_AI_D[1...M]
ETH_AI_P[1...M]
ETH_AI_DE[1...M]
ETH_AI_TSF
ETH_AI_TSD
ETH_AI_AIS

ETHG/ETH_A_Sk_MP:
ETHG/ETH_A_Sk_MI_MEP_MAC
ETHG/ETH_A_Sk_MI_Client_MEL[1...M]
ETHG/ETH_A_Sk_MI_LCK_Period[1...M]
ETHG/ETH_A_Sk_MI_LCK_Pri[1...M]
ETHG/ETH_A_Sk_MI_Admin_State
ETHG/ETH_A_Sk_MI_AIS_Period[1...M]
ETHG/ETH_A_Sk_MI_AIS_Pri[1...M]
ETHG/ETH_A_Sk_MI_MEL
ETHG/ETH_A_Sk_MI_CSF_Reported
ETHG/ETH_A_Sk_MI_CSFrdifdiEnable | ETH_FP:
ETH_CI_D[1...M]
ETH_CI_P[1...M]
ETH_CI_DE[1...M]
ETH_CI_APS
ETH_CI_SSF[1...M]
ETH_CI_SSD
ETH_CI_SSFrdi[1]
ETH_CI_SSFfdi[1]

ETHG/ETH_A_Sk_MP:
ETHG/ETH_A_Sk_MI_cCSF | + +##### Processes + +![Figure 9-35 – ETHG/ETH_A_Sk process diagram. This block diagram illustrates the internal architecture of the ETHG/ETH_A_Sk process. At the top, three identical processing branches are shown, each containing a 'Selector' (with 'Normal' and 'Lock' inputs), an 'LCK generation' block, and an 'AIS insert' block. These branches receive inputs from 'ETH_CI_SSF/SSD', 'ETH_CI_P/DE/D', and 'ETH_CI_SSF'. They output to 'ETH_CI_P/DE/D' and 'ETH_CI_SSF'. Below these branches is a large 'OAM MEL filter' block. To the left of the filter are 'Consequent actions', 'Defect correlations', and 'Defect generation' blocks, which interact with 'MI_Admin_State', 'MI_CSFrdifdEnable', 'MI_CSF_ Reported', and 'dCSF'. Below the filter are 'CSF extract' and 'APS extract' blocks, which receive 'MI_MEL' and output to 'ETH_AI_P/DE/D'. The entire diagram is labeled with 'G.8021-Y.1341(22)_F9-35' in the bottom right corner.](7f160d34246308c7a49fa34793b776da_img.jpg) + +Figure 9-35 – ETHG/ETH\_A\_Sk process diagram. This block diagram illustrates the internal architecture of the ETHG/ETH\_A\_Sk process. At the top, three identical processing branches are shown, each containing a 'Selector' (with 'Normal' and 'Lock' inputs), an 'LCK generation' block, and an 'AIS insert' block. These branches receive inputs from 'ETH\_CI\_SSF/SSD', 'ETH\_CI\_P/DE/D', and 'ETH\_CI\_SSF'. They output to 'ETH\_CI\_P/DE/D' and 'ETH\_CI\_SSF'. Below these branches is a large 'OAM MEL filter' block. To the left of the filter are 'Consequent actions', 'Defect correlations', and 'Defect generation' blocks, which interact with 'MI\_Admin\_State', 'MI\_CSFrdifdEnable', 'MI\_CSF\_ Reported', and 'dCSF'. Below the filter are 'CSF extract' and 'APS extract' blocks, which receive 'MI\_MEL' and output to 'ETH\_AI\_P/DE/D'. The entire diagram is labeled with 'G.8021-Y.1341(22)\_F9-35' in the bottom right corner. + +Figure 9-35 – ETHG/ETH\_A\_Sk process + +###### *APS extract process* + +As defined in clause 8.1.6. + +###### *CSF extract process* + +As defined in clause 8.1.17. + +##### *OAM MEL filter process* + +As defined in clause 8.1.1. + +##### *AIS insert process* + +As defined in clause 8.1.4. There is a single AIS insert process for each ETH. + +##### *LCK generation process* + +As defined in clause 8.1.2. There is a single LCK generation process for each ETH. + +##### *Selector process* + +As defined in clause 8.1.3. The normal CI of each input is blocked if Admin\_State = LOCKED. + +##### Defects + +dCSF-LOS – See clause 6.1.5.4. + +dCSF-RDI – See clause 6.1.5.4. + +dCSF-FDI – See clause 6.1.5.4. + +##### Consequent actions + +aSSF[1] $\leftarrow$ (AI\_TSF or dCSF\_LOS) and (not MI\_Admin\_State == Locked) + +aSSFrdi[1] $\leftarrow$ dCSF-RDI and MI\_CSFrdifdiEnable + +aSSFfdi[1] $\leftarrow$ dCSF-FDI and MI\_CSFrdifdiEnable + +aSSF[2...M] $\leftarrow$ AI\_TSF and (not MI\_Admin\_State == Locked) + +aAIS $\leftarrow$ AI\_AIS + +##### Defect correlations + +cCSF $\leftarrow$ (dCSF-LOS or dCSF-RDI or dCSF-FDI) and (not AI\_TSF) and MI\_CSF\_Reported + +Performance monitoring None. + +### 9.3.4 ETHx to ETH group adaptation functions (ETHx/ETHG\_A) + +This adaptation function multiplexes different ETH\_CI streams in the ETH group into a single ETH\_AI stream and demultiplexes the ETH\_AI stream into individual ETH\_CI streams. The ETHx/ETHG\_A function symbol is shown in Figure 9-36. + +##### Symbol + +![Figure 9-36: ETHx/ETHG_A symbol diagram](3642ba0abb9db40eb14c771f02f9f44e_img.jpg) + +The diagram shows a trapezoidal block labeled 'ETHx/ETHG'. On the top, there are two input ports labeled 'ETH\_TFP' and 'ETH\_FP'. On the left side, a management point input is labeled 'ETHx/ETHG\_A\_MP'. On the bottom, there is an access point labeled 'ETH\_AP'. Below the diagram is the reference 'G.8021-Y.1341(22)\_F9-36'. + +Figure 9-36: ETHx/ETHG\_A symbol diagram + +**Figure 9-36 – ETHx/ETHG\_A symbol** + +The ETHx/ETHG\_A function is further decomposed into separate source and sink adaptation functions that are interconnected as shown in Figure 9-37. + +![Figure 9-37: ETHx/ETHG_A source and sink symbols diagram](cae2e86614cca6567f79cd6c89bea090_img.jpg) + +The diagram shows two trapezoidal blocks side-by-side. The left block is the source (So) and the right block is the sink (Sk). The source block has inputs 'ETH\_TFP' and 'ETH\_FP' on top, 'ETHx/ETHG\_A\_So\_MP' on the left, and an output 'ETH\_AP' on the bottom. The sink block has an input 'ETH\_AP' on the bottom, 'ETHx/ETHG\_A\_Sk\_MP' on the right, and outputs 'ETH\_TFP' and 'ETH\_FP' on top. Two internal paths connect the blocks: 'ETHTF\_PP' and 'ETHF\_PP'. Below the right block is the reference 'G.8021-Y.1341(22)\_F9-37'. + +Figure 9-37: ETHx/ETHG\_A source and sink symbols diagram + +**Figure 9-37 – ETHx/ETHG\_A source and sink symbols** + +#### 9.3.4.1 ETHx to ETH group adaptation source function (ETHx/ETHG\_A\_So) + +This function multiplexes individuals ETH\_CI streams in the ETH group into a single ETH\_AI stream. The ETHx/ETHG\_A\_So function symbol is shown in Figure 9-38, the interfaces in Table 9-14 and the process diagram in Figure 9-39. + +##### Symbol + +![Diagram of the ETHx/ETHG_A_So symbol. The symbol is a trapezoidal block labeled 'ETHx/ETHG'. It has three input interfaces on the top: 'ETH_TFP', 'ETH_FP', and 'ETHx/ETHG_A_So_MP' (entering from the left). It has three output interfaces: 'ETHF_PP' and 'ETHTF_PP' on the right, and 'ETH_AP' at the bottom. A reference label 'G.8021-Y.1341(22)_F9-38' is located to the right of the symbol.](061f273b184fe5ef7286f149580f3587_img.jpg) + +Diagram of the ETHx/ETHG\_A\_So symbol. The symbol is a trapezoidal block labeled 'ETHx/ETHG'. It has three input interfaces on the top: 'ETH\_TFP', 'ETH\_FP', and 'ETHx/ETHG\_A\_So\_MP' (entering from the left). It has three output interfaces: 'ETHF\_PP' and 'ETHTF\_PP' on the right, and 'ETH\_AP' at the bottom. A reference label 'G.8021-Y.1341(22)\_F9-38' is located to the right of the symbol. + +Figure 9-38 – ETHx/ETHG\_A\_So symbol + +##### Interfaces + +Table 9-14 – ETHx/ETHG\_A\_So interfaces + +| Inputs | Outputs | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_FP:
ETH_CI_D[1...M]
ETH_CI_P[1...M]
ETH_CI_DE[1...M]

ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE

ETHx/ETHG_A_So_MP:
ETHx/ETHG_A_So_MI_MEP_MAC
ETHx/ETHG_A_So_MI_Client_MEL[1...M]
ETHx/ETHG_A_So_MI_LCK_Period[1...M]
ETHx/ETHG_A_So_MI_LCK_Pri[1...M]
ETHx/ETHG_A_So_MI_Admin_State
ETHx/ETHG_A_So_MI_VLAN_Config[1...M]
ETHx/ETHG_A_So_MI_Etype
ETHx/ETHG_A_So_MI_PCP_Config
ETHx/ETHG_A_So_MI_MEL | ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE

ETHF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ETHTF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE | + +##### Processes + +![Figure 9-39 – ETHx/ETHG_A_So process block diagram. The diagram shows the flow of data through various processing stages: LCK generation, Selector, VID MUX, VLAN TAG, Replicate, and OAM MEL filter. Inputs include ETH_CI_P/DE/D signals and management information (MI) such as MI_MEP_MAC, MI_Client_MEL, MI_LCK_Period, MI_LCK_Pri, MI_Admin_State, MI_VLAN_Config, MI_Etype, MI_PCP_Config, and MI_MEL. Outputs include ETH_PI_P, ETH_PI_DE, ETH_PI_D, and ETH_AI_P/DE/D signals.](ec2cc2c65213e7cac311b3d28d1c428e_img.jpg) + +The diagram illustrates the **ETHx/ETHG\_A\_So process**. At the top, four input signal sets (P, DE, D) labeled **ETH\_CI\_P/DE/D** enter the system. Each input passes through an **LCK generation** block, which also receives inputs from **MI\_MEP\_MAC**, **MI\_Client\_MEL[1...M]**, **MI\_LCK\_Period[1...M]**, and **MI\_LCK\_Pri[1...M]**. The outputs of these blocks go to a **Selector** block containing **Normal** and **Lock** sub-blocks, which also receives **MI\_Admin\_State**. The Selector outputs (P, DE, D) then pass through a **VID MUX** block with sub-blocks **X**, **Y**, and **Z**, which also receives **MI\_VLAN\_Config[1...M]**. The VID MUX outputs (P, DE, D) go to a **VLAN TAG** block, which also receives **VID**, **MI\_Etype**, and **MI\_PCP\_Config**. A **P replicate** block takes the P signal and sends it to the VLAN TAG. The VLAN TAG outputs (P, DE, D) go to a **Replicate** block, which also receives a **DE** signal from a **DE generate** block. The Replicate block outputs (P, DE, D) go to an **OAM MEL filter** block, which also receives **MI\_MEL**. The final output is **ETH\_AI\_P/DE/D**. A dashed line separates the top three input signal sets from the fourth. + +Figure 9-39 – ETHx/ETHG\_A\_So process block diagram. The diagram shows the flow of data through various processing stages: LCK generation, Selector, VID MUX, VLAN TAG, Replicate, and OAM MEL filter. Inputs include ETH\_CI\_P/DE/D signals and management information (MI) such as MI\_MEP\_MAC, MI\_Client\_MEL, MI\_LCK\_Period, MI\_LCK\_Pri, MI\_Admin\_State, MI\_VLAN\_Config, MI\_Etype, MI\_PCP\_Config, and MI\_MEL. Outputs include ETH\_PI\_P, ETH\_PI\_DE, ETH\_PI\_D, and ETH\_AI\_P/DE/D signals. + +G.8021-Y.1341(22)\_F9-39 + +**Figure 9-39 – ETHx/ETHG\_A\_So process** + +###### *LCK generation process* + +As defined in clause 8.1.2. Each FP has its LCK generation process. + +###### *Selector process* + +As defined in clause 8.1.3. The normal CI is blocked if Admin\_State = LOCKED. + +###### *VID Mux process* + +The VID MUX process interleaves the signal sets (P, D, DE) from the input ports (X, Y, Z). The detail of this process is described in clause 9.3.2.1. + +##### *VLAN tag process* + +This process inserts a VLAN tag into the MSDU field of the incoming D signal. The detail of this process is described in clause 9.3.2.1. + +##### *P replicate process* + +The P replicate process replicates the incoming P signal to both output ports without changing the value of the signal. + +##### *DE generation process* + +The DE generation process generates a DE signal with the value drop ineligible. + +##### *Replicate process* + +As defined in clause 8.4. + +##### *OAM MEL filter process* + +As defined in clause 8.1.1. + +- Defects** None. +- Consequent actions** None. +- Defect correlations** None. +- Performance monitoring** None. + +#### **9.3.4.2 ETHx to ETH group adaptation sink function (ETHx/ETHG\_A\_Sk)** + +The ETHx/ETHG\_A\_Sk function symbol is shown in Figure 9-40, the interfaces in Table 9-15 and the process diagram in Figure 9-41. + +##### **Symbol** + +![Symbol diagram for ETHx/ETHG_A_Sk function. The symbol is a trapezoid labeled 'ETHx/ETHG'. It has two input arrows on the left labeled 'ETHTF_PP' and 'ETHF_PP'. It has one input arrow from the bottom labeled 'ETH_AP'. It has one input arrow from the right labeled 'ETHx/ETHG_A_Sk_MP'. It has two output arrows on the top labeled 'ETH_TFP' and 'ETH_FP'. A dashed line is shown between the two output arrows. A small text 'G.8021-Y.1341(22)_F9-40' is located to the right of the symbol.](ebe81c17cdf5809972e5a05e7b8c3ff8_img.jpg) + +G.8021-Y.1341(22)\_F9-40 + +Symbol diagram for ETHx/ETHG\_A\_Sk function. The symbol is a trapezoid labeled 'ETHx/ETHG'. It has two input arrows on the left labeled 'ETHTF\_PP' and 'ETHF\_PP'. It has one input arrow from the bottom labeled 'ETH\_AP'. It has one input arrow from the right labeled 'ETHx/ETHG\_A\_Sk\_MP'. It has two output arrows on the top labeled 'ETH\_TFP' and 'ETH\_FP'. A dashed line is shown between the two output arrows. A small text 'G.8021-Y.1341(22)\_F9-40' is located to the right of the symbol. + +**Figure 9-40 – ETHx/ETHG\_A\_Sk symbol** + +##### Interfaces + +Table 9-15 – ETHx/ETHG\_A\_Sk interfaces + +| Inputs | Outputs | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE
ETH_AI_TSF
ETH_AI_AIS

ETHF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ETHTF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ETHx/ETHG_A_Sk_MP:
ETHx/ETHG_A_Sk_MI_MEP_MAC
ETHx/ETHG_A_Sk_MI_Client_MEL[1...M]
ETHx/ETHG_A_Sk_MI_LCK_Period[1...M]
ETHx/ETHG_A_Sk_MI_LCK_Pri[1...M]
ETHx/ETHG_A_Sk_MI_Admin_State
ETHx/ETHG_A_Sk_MI_AIS_Period[1...M]
ETHx/ETHG_A_Sk_MI_AIS_Pri[1...M]
ETHx/ETHG_A_Sk_MI_VLAN_Config[1...M]
ETHx/ETHG_A_Sk_MI_P_Regenerate
ETHx/ETHG_A_Sk_MI_PVID
ETHx/ETHG_A_Sk_MI_PCP_Config
ETHx/ETHG_A_Sk_MI_Etype
ETHx/ETHG_A_Sk_MI_MEL
ETHx/ETHG_A_Sk_MI_Frametype_Config
ETHx/ETHG_A_Sk_MI_FilterConfig | ETH_FP:
ETH_CI_D[1...M]
ETH_CI_P[1...M]
ETH_CI_DE[1...M]
ETH_CI_SSF[1...M]

ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE | + +##### Processes + +![Figure 9-41 – ETHx/ETHG_A_Sk process block diagram showing internal components and interfaces.](46b6ae100e671c34c024598495e56c99_img.jpg) + +The diagram illustrates the internal architecture of the ETHx/ETHG\_A\_Sk process. It shows the flow of data from input interfaces through various processing blocks to output interfaces. + +**Input Interfaces:** + +- ETH\_AI\_P/DE/D +- ETH\_AI\_TSF +- ETH\_AI\_AIS + +**Internal Processing Flow:** + +- The input data enters the **Replicate** block. +- It then passes through a **Filter** block, which receives configuration from **MI\_Filter\_Config**. +- Next is the **FRAME TYPE FILTER** block, configured by **MI\_Frametype\_Config**. +- This is followed by the **OAM MEL filter** block, configured by **MI\_MEL**. +- The data then enters the **DE selector** block. +- From the DE selector, the path splits: one path goes to the **P selector** block, and another goes to the **VLAN TAG process** block. +- The **P selector** block feeds into the **P regenerate** block. +- The **VLAN TAG process** block receives configuration from **MI\_PVID**, **MI\_PCP\_Config**, and **MI\_Etype**, and it feeds into the **Consequent actions** block. +- The **Consequent actions** block also receives inputs **aSSF** and **aAIS**, and is configured by **MI\_P\_Regenerate**. +- The data from the **P regenerate** block and the **Consequent actions** block enters the **VID DEMUX** block, which is configured by **MI\_VLAN\_Config[1..M]**. +- The VID DEMUX has three output paths labeled **X**, **Y**, and **Z**. +- Each path (X, Y, Z) leads to an **AIS insert** block. +- Each AIS insert block is followed by an **LCK generation** block. +- Each LCK generation block is followed by a **Selector** block (with **Normal** and **Lock** options). +- Each Selector block receives configuration from **MI\_Admin\_State**, **MI\_MEP\_MAC**, **MI\_Client\_MEL[1..M]**, **MI\_LCK\_Period[1..M]**, and **MI\_LCK\_Pri[1..M]**. +- The output of each Selector block goes to the **ETH\_CI\_P/DE/D** interface. +- There are also **ETH\_CI\_SSF** interfaces at the top of the diagram. + +**Output Interfaces:** + +- ETH\_CI\_SSF +- ETH\_CI\_P/DE/D + +**Other Labels and Details:** + +- Internal labels include **P**, **DE**, and **D** indicating different data paths. +- External configuration interfaces include **ETH\_PI\_D**, **ETH\_PI\_P**, and **ETH\_PI\_DE** connected to the Replicate block. +- The diagram is identified by the code **G.8021-Y.1341(22)\_F9-41** in the bottom left corner. + +Figure 9-41 – ETHx/ETHG\_A\_Sk process block diagram showing internal components and interfaces. + +Figure 9-41 – ETHx/ETHG\_A\_Sk process + +###### *Replicate process* + +As defined in clause 8.4. + +###### *Filter Process* + +As defined in clause 8.3. + +###### *Frame type filter process* + +The frame type filter process filters the ETH\_CI depending on the value of the MI\_frametype\_Config input parameter. The details of this process is described in clause 9.3.2.2. + +##### *OAM MEL filter process* + +As defined in clause 8.1.1. + +##### *VLAN tag process* + +The VLAN tag process inspects the incoming D signal. The detail of this process is described in clause 9.3.2.1. + +##### *DE selector process* + +This process forwards the incoming DE signal. If there is no incoming DE signal present, it generates a DE signal with the value drop ineligible. + +##### *P selector process* + +This process forwards the P signal coming from the VLAN tag process. If this signal is not present, the P signal coming from the OAM MEL process is forwarded. + +##### *P regeneration process* + +This process regenerates the incoming P signal, based on the MI\_P\_Regenerate input signal. The MI\_P\_Regenerate signal specifies a mapping table from P value to P value. + +##### *VID Demux process* + +The VID Demux process de-interleaves the incoming signal set (DE, P, D) to the different ports (X, Y, Z in Figure 9-39). The detail of this process is described in clause 9.3.2.1. + +##### *AIS insert process* + +As defined in clause 8.1.4. + +##### *LCK generation process* + +As defined in clause 8.1.2. Each FP has its own LCK generation process. + +##### *Selector process* + +As defined in clause 8.1.3. The normal CI is blocked if Admin\_State = LOCKED. + +| | | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------------| +| Defects | None. | +| Consequent actions | $\text{aSSF} \leftarrow \text{AI\_TSF and (not MI\_Admin\_State == Locked)}$
$\text{aAIS} \leftarrow \text{AI\_AIS}$ | +| Defect correlations | None. | +| Performance monitoring | None. | + +### 9.3.5 ETH to MCC adaptation functions (ETHx/MCC\_A) + +#### 9.3.5.1 ETH to MCC adaptation source function (ETHx/MCC\_A\_So) + +This function maps MCC traffic units into server ETH\_AI traffic units. It also provides a maintenance communication channel for EMF via a management reference point. The ETHx/MCC\_A\_So function symbol is shown in Figure 9-42, the interfaces in Table 9-16 and the process diagram in Figure 9-43. + +##### Symbol + +![Figure 9-42: Symbol for ETHx/MCC_A_So function. It shows a trapezoidal block labeled 'ETHx/MCC'. An input 'MCC_CP' enters from the top. An input 'ETHx/MCC_A_So_MP' enters from the left. An output 'ETH_AP' exits from the bottom. A reference label 'G.8021-Y.1341(22)_F9-42' is at the bottom.](6ba19a99fb96f0139505f0992544a2cf_img.jpg) + +Figure 9-42: Symbol for ETHx/MCC\_A\_So function. It shows a trapezoidal block labeled 'ETHx/MCC'. An input 'MCC\_CP' enters from the top. An input 'ETHx/MCC\_A\_So\_MP' enters from the left. An output 'ETH\_AP' exits from the bottom. A reference label 'G.8021-Y.1341(22)\_F9-42' is at the bottom. + +Figure 9-42 – ETHx/MCC\_A\_So symbol + +##### Interfaces + +Table 9-16 – ETHx/MCC\_A\_So interfaces + +| Inputs | Outputs | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| +| MCC_CP:
MCC_CI_D

ETHx/MCC_A_So_MP:
ETHx/MCC_A_So_MI_MEL
ETHx/MCC_A_So_MI_MEP_MAC
ETHx/MCC_A_So_MI_MCC_Pri
ETHx/MCC_A_So_MI_MEP_ID
ETHx/MCC_A_So_MI_EDM_Enable
ETHx/MCC_A_So_MI_EDM_Period
ETHx/MCC_A_So_MI_EDM_Duration | ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE | + +##### Processes + +![Figure 9-43: Process diagram for ETHx/MCC_A_So. It shows a large light blue box containing two main blocks: 'EDM Generation' and 'MCC Generation'. 'EDM Generation' receives inputs MI_EDM_Enable, MI_EDM_Period, MI_EDM_Duration, and MI_MEP_ID, and outputs a signal 'D' to 'MCC Generation'. 'MCC Generation' receives 'MCC_CI_D' from the top, 'D' from 'EDM Generation', and inputs MI_MEL, MI_MEP_MAC, and MI_MCC_Pri from the right. It contains sub-blocks 'DCN' and 'EDM'. It outputs 'ETH_AI_D/P/DE' at the bottom. A reference label 'G.8021-Y.1341(22)_F9-43' is at the bottom right.](5880b089cf271989116a1bff7f3321e9_img.jpg) + +Figure 9-43: Process diagram for ETHx/MCC\_A\_So. It shows a large light blue box containing two main blocks: 'EDM Generation' and 'MCC Generation'. 'EDM Generation' receives inputs MI\_EDM\_Enable, MI\_EDM\_Period, MI\_EDM\_Duration, and MI\_MEP\_ID, and outputs a signal 'D' to 'MCC Generation'. 'MCC Generation' receives 'MCC\_CI\_D' from the top, 'D' from 'EDM Generation', and inputs MI\_MEL, MI\_MEP\_MAC, and MI\_MCC\_Pri from the right. It contains sub-blocks 'DCN' and 'EDM'. It outputs 'ETH\_AI\_D/P/DE' at the bottom. A reference label 'G.8021-Y.1341(22)\_F9-43' is at the bottom right. + +Figure 9-43 – ETHx/MCC\_A\_So process + +##### *MCC generation process* + +MCC generation process generates MCC traffic units based on the data signals from MCC\_connection point or EDM generation process. The data signals from MCC connection point are received at data communication network (DCN) port, and the signals from EDM generation are received at EDM port. + +This process builds an MCC traffic unit from the received data signals, MI\_MEL for MAC DA and MEG level, MI\_MEP\_MAC for MAC SA and MI\_MCC\_Pri signals. Figure 9-44 describes the behaviour of MCC traffic unit generation. + +![Flowchart of MCC generation behaviour](313826501fcb4294a5d337702ea35f2d_img.jpg) + +``` +graph TD; A([MCC generation]) --> B([Waiting]); B --> C[/DCN(D)/]; B --> D[/EDM(D)/]; C --> E["SubOPC = Undefined +MCCdata(D) = DCN(D)"]; D --> F["SubOPC = 01(EDM) +MCCdata(D) = EDM(D)"]; E --> G["X = MI_MEL +DA(D) = 01-80-C2-00-00-3x +SA(D) = MI_MEP_MAC +MEL(D) = MI_MEL +OPC(D) = 41(MCC) +OUI(D) = 00-19-A7(ITU)"]; F --> G; G --> H[/D(D) +P(MI_MCC_Pri) +DE(0)/]; H --> B; +``` + +The flowchart illustrates the MCC generation process. It begins with 'MCC generation' leading to 'Waiting'. From 'Waiting', the process branches into two parallel paths: 'DCN(D)' and 'EDM(D)'. The 'DCN(D)' path leads to a block where 'SubOPC = Undefined' and 'MCCdata(D) = DCN(D)'. The 'EDM(D)' path leads to a block where 'SubOPC = 01(EDM)' and 'MCCdata(D) = EDM(D)'. Both paths converge to a common block where various parameters are set: 'X = MI\_MEL', 'DA(D) = 01-80-C2-00-00-3x', 'SA(D) = MI\_MEP\_MAC', 'MEL(D) = MI\_MEL', 'OPC(D) = 41(MCC)', and 'OUI(D) = 00-19-A7(ITU)'. This is followed by a block with 'D(D)', 'P(MI\_MCC\_Pri)', and 'DE(0)'. Finally, the process loops back to the 'Waiting' state. A small note at the bottom right of the diagram reads 'G.8021-Y.1341(22)\_F9-44'. + +Flowchart of MCC generation behaviour + +**Figure 9-44 – MCC generation behaviour** + +NOTE – The SubOPC value for DCN is not assigned in the current version of [ITU-T G.8013]. + +###### *EDM generation process* + +As defined in clause 8.1.20.1. + +**Defects** None. + +**Consequent actions** None. + +**Defect correlations** None. + +**Performance monitoring** None. + +#### **9.3.5.2 ETH to MCC adaptation sink function (ETHx/MCC\_A\_Sk)** + +This function retrieves MCC\_CI traffic units from server ETH\_AI traffic units. It also provides a maintenance communication channel for EMF via a management reference point. The ETHx/MCC\_A\_Sk function symbol is shown in Figure 9-45, the interfaces in Table 9-17 and the process diagram in Figure 9-46. + +##### Symbol + +![Figure 9-45 – ETHx/MCC_A_Sk symbol diagram. A central trapezoidal block labeled 'ETHx/MCC' has three interfaces: 'MCC_CP' pointing upwards, 'ETHx/MCC_A_Sk_MP' pointing to the right, and 'ETH_AP' pointing upwards from below. The reference 'G.8021-Y.1341(22)_F9-45' is shown at the bottom right.](c8363610940980ea7cd1611443c94ef5_img.jpg) + +Figure 9-45 – ETHx/MCC\_A\_Sk symbol diagram. A central trapezoidal block labeled 'ETHx/MCC' has three interfaces: 'MCC\_CP' pointing upwards, 'ETHx/MCC\_A\_Sk\_MP' pointing to the right, and 'ETH\_AP' pointing upwards from below. The reference 'G.8021-Y.1341(22)\_F9-45' is shown at the bottom right. + +**Figure 9-45 – ETHx/MCC\_A\_Sk symbol** + +##### Interfaces + +**Table 9-17 – ETHx/MCC\_A\_Sk interfaces** + +| Inputs | Outputs | +|-----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------| +| ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE

ETHx/MCC_A_Sk_MP:
ETHx/MCC_A_Sk_MI_MEP_MAC
ETHx/MCC_A_Sk_MI_MEL | MCC_CP:
MCC_CI_D

ETHx/MCC_A_Sk_MP:
ETHx/MCC_A_Sk_MI_EDM_Received
(MEP_ID, Duration) | + +##### Processes + +![Figure 9-46 – ETHx/MCC_A_Sk process diagram. A large light blue rectangle contains two main blocks: 'EDM Reception' and 'MCC Reception'. 'EDM Reception' receives a 'D' signal from 'MCC Reception' and outputs 'MI_EDM_Received(MEP_ID,Duration)'. 'MCC Reception' receives 'ETH_AI_D/P/DE' from the bottom, 'MI_MEL' and 'MI_MEP_MAC' from the right, and outputs 'MCC_CI_D' from the top. Inside 'MCC Reception', there are sub-blocks 'EDM', 'DCN', and 'MCC Reception'. The reference 'G.8021-Y.1341(22)_F9-46' is shown at the bottom right.](da308c919c2b05d507cd6eb4dc7c00f9_img.jpg) + +Figure 9-46 – ETHx/MCC\_A\_Sk process diagram. A large light blue rectangle contains two main blocks: 'EDM Reception' and 'MCC Reception'. 'EDM Reception' receives a 'D' signal from 'MCC Reception' and outputs 'MI\_EDM\_Received(MEP\_ID,Duration)'. 'MCC Reception' receives 'ETH\_AI\_D/P/DE' from the bottom, 'MI\_MEL' and 'MI\_MEP\_MAC' from the right, and outputs 'MCC\_CI\_D' from the top. Inside 'MCC Reception', there are sub-blocks 'EDM', 'DCN', and 'MCC Reception'. The reference 'G.8021-Y.1341(22)\_F9-46' is shown at the bottom right. + +**Figure 9-46 – ETHx/MCC\_A\_Sk process** + +##### *MCC reception process* + +This process extracts MCC traffic units that are processed in the ETHx/MCC\_A\_Sk process according to the following pseudo code: + +``` + +if (TYPE=) and (MEL=MI_MEL) and ((DA=Class 1) or (DA=MI_MEP_MAC)) +and (OPC=MCC) then + switch(OUI) { + case : { + switch(SubOPC) { + case : extract ETH-MCC OAM traffic unit and forward to DCN Port + case : extract ETH-MCC OAM traffic unit and forward to EDM Port + default : discard the traffic unit + } + } + } + +``` + +``` + + } + default: outside the scope of this Recommendation + } +else + discard the traffic unit +endif + +``` + +NOTE – The SubOPC value for DCN is not assigned in the current version of [ITU-T G.8013]. + +##### *EDM reception process* + +As defined in clause 8.1.20.2. + +**Defects**                            None. +**Consequent actions**            None. +**Defect correlations**            None. +**Performance monitoring**    None. + +## **9.4    ETH diagnostic functions** + +### **9.4.1    ETH diagnostic flow termination functions for MEPs (ETHDe\_FT)** + +The bidirectional ETHDe flow termination (ETHDe\_FT) function is performed by a co-located pair of ETHDe flow termination source (ETHDe\_FT\_So) and sink (ETHDe\_FT\_Sk) functions. + +#### **9.4.1.1    ETH diagnostic flow termination source function for MEPs (ETHDe\_FT\_So)** + +The ETHDe\_FT\_So process function symbol is shown in Figure 9-47, the interfaces in Table 9-18 and the process diagram in Figure 9-48. + +##### **Symbol** + +![Diagram of the ETHDe_FT_So process function symbol. It shows a central triangle labeled 'ETHDe'. Above it, an arrow labeled 'ETH_AP' points down into the triangle. To the left, two arrows labeled 'ETHDe_FT_So_MP' and 'ETH_TP' point into the triangle. To the right, an arrow labeled 'ETH_RP' points into the triangle. Below the triangle, an arrow labeled 'ETH_TFP' points down away from it. At the bottom, the text 'G.8021-Y.1341(22)_F9-47' is present.](3494c4db3ab691da9a857f3d6293b54f_img.jpg) + +Diagram of the ETHDe\_FT\_So process function symbol. It shows a central triangle labeled 'ETHDe'. Above it, an arrow labeled 'ETH\_AP' points down into the triangle. To the left, two arrows labeled 'ETHDe\_FT\_So\_MP' and 'ETH\_TP' point into the triangle. To the right, an arrow labeled 'ETH\_RP' points into the triangle. Below the triangle, an arrow labeled 'ETH\_TFP' points down away from it. At the bottom, the text 'G.8021-Y.1341(22)\_F9-47' is present. + +**Figure 9-47 – ETHDe\_FT\_So symbol** + +##### Interfaces + +**Table 9-18 – ETHDe\_FT\_So interfaces** + +| Inputs | Outputs | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE

ETH_RP:
ETH_RI_LMM(D,P,DE)
ETH_RI_LMR(rSA,TxFCf,RxFCf,TxFCb,RxFCb)
ETH_RI_LBM(D,P,DE)
ETH_RI_LBR(SA,rTLV,TID)
ETH_RI_DMM(D,P,DE)
ETH_RI_DMR(rSA,TxTimeStampf,RxTimeStampf,
TxTimeStampb,RxTimeb,rTestID)
ETH_RI_LTM(D,P,DE)
ETH_RI_LTR(SA,TTL,TID,TLV)
ETH_RI_SLM(OAM,P,DE,TxFCb)
ETH_RI_SLR(rMEP_ID,rTest_ID,TxFCf,TxFCb)

ETH_TP:
ETHDe_FT_So_TI_TimeStampf
ETHDe_FT_So_MP:
ETHDe_FT_So_MI_LM_Start(DA,P,Period)
ETHDe_FT_So_MI_LM_Intermediate_Request
ETHDe_FT_So_MI_LM_Terminate
ETHDe_FT_So_MI_LB_Discover( P)
ETHDe_FT_So_MI_LB_Series(DA,DE,P,N, Length,
Period)
ETHDe_FT_So_MI_LB_Test
(DA,DE,P,Pattern, Length, Period)
ETHDe_FT_So_MI_LB_Test_Terminate
ETHDe_FT_So_MI_DM_Start(DA,P,Test
ID,Length,Period)
ETHDe_FT_So_MI_DM_Intermediate_Request
ETHDe_FT_So_MI_DM_Terminate
ETHDe_FT_So_MI_1DM_Start(DA,P,Test
ID,Length,Period)
ETHDe_FT_So_MI_1DM_Terminate
ETHDe_FT_So_MI_TST(DA,DE,P,Pattern, Length,
Period)
ETHDe_FT_So_MI_TST_Terminate
ETHDe_FT_So_MI_LT(TA,TTL,P)
ETHDe_FT_So_MI_MEP_MAC
ETHDe_FT_So_MI_MEL
ETHDe_FT_So_MI_MEP_ID
ETHDe_FT_So_MI_SL_Start(DA,P,Test_ID,Length,Period)
ETHDe_FT_So_MI_SL_Intermediate_Request
ETHDe_FT_So_MI_SL_Terminate
ETHDe_FT_So_MI_1SL_Start(
DA,P,Test_ID,Length,Period)
ETHDe_FT_So_MI_1SL_Terminate | ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE

ETHDe_FT_So_MP:
ETHDe_FT_So_MI_LM_Result( N_TF, N_LF, F_TF, F_LF)
ETHDe_FT_So_MI_LB_Discover_Result(MACs)
ETHDe_FT_So_MI_LB_Series_Result(REC,ERR,OO)
ETHDe_FT_So_MI_LB_Test_Result
(Sent, REC, CRC, BER, OO)
ETHDe_FT_So_MI_DM_Result(count,B_FD[],F_FD[],N_FD[])
ETHDe_FT_So_MI_TST_Result(Sent)
ETHDe_FT_So_MI_LT_Results(Results)
ETHDe_FT_So_MI_SL_Result(N_TF,N_LF,F_TF,F_LF) | + +##### Processes + +![Figure 9-48 – ETHDe_FT_So process diagram showing various network management processes and their interactions.](0e97550fb1a8a7e793a8325afac3700a_img.jpg) + +The diagram illustrates the ETHDe\_FT\_So process, showing various network management functions and their interactions. The processes are organized vertically within a large light-blue container, with data flows and control signals connecting them. + +- Top Interface:** ETH\_AI\_D/P/DE connects to a Data block, which is linked to a Counter and another Data block. These are connected to D, P, and DE lines. +- LM (Link Management) Process:** + - Inputs: RI\_LMR(rSA,TxFcF,RxFcF, TxFcB,RxFcB), MI\_LM\_Start(DA,P,Period), MI\_LM\_Intermediate\_Request, MI\_LM\_Terminate, MI\_LM\_Result(N\_TF,N\_LF,F\_TF,F\_LF), RI\_LMM(D,P,DE). + - Control: On-demand LM Control. + - Mux: LMM Mux (X, Y, Z) outputs LMM(DA,P,0). + - Generators: LMM Generation, LMR Generation. + - Output: LMM, LMR blocks on the right side. +- LB (Link Discovery) Process:** + - Inputs: RI\_LBR(SA,rTLV,TID), MI\_LB\_Discover(P), MI\_LB\_Discover\_Result(MACs), MI\_LB\_Series(DA,DE,P,N, Length,Period), MI\_LB\_Series\_Result(REC,ERR,OO), MI\_LB\_test(DA,DE,P,Pattern, Length,Period), MI\_LB\_Test\_Terminate, MI\_LB\_Test\_Result(Sent,REC, CRC,BER,OO), RI\_LBM(D,P,DE). + - Control: LB Control. + - Generators: LBM Generation, LBR Generation. + - Output: LBM, LBR blocks on the right side. +- DM (Delay Measurement) Process:** + - Inputs: RI\_DMR(rSA,TxTimeStampf, RxTimeStampf,TxTimeStampb, RxTimeb,rTest\_ID), MI\_DM\_Start(DA,P,Test\_ID, Length,Period), MI\_DM\_Intermediate\_Request, MI\_DM\_Terminate, MI\_DM\_Result(Count,B\_FD[], F\_FD[],N\_FD[]), RI\_DMM(D,P,DE). + - Control: On-demand DM Control. + - Mux: DMM Mux (X, Y, Z) outputs DMM(DA,P,0 Test ID TLV, TLV). + - Generators: DMM Generation, DMR Generation. + - Output: DMM, DMR blocks on the right side. +- IDM (Interval Delay Measurement) Process:** + - Inputs: MI\_IDM\_Start(DA,P,Test\_ID, Length,Period), MI\_IDM\_Terminate. + - Control: On-demand IDM Control\_So. + - Mux: IDM Mux (X, Y, Z) outputs IDM(DA,P,0 Test TD TLV, TLV). + - Generators: IDM Generation. + - Output: IDM block on the right side. +- TST (Test) Process:** + - Inputs: TI\_TimeStamp1, MI\_TST(DA,DE,P,Pattern, Length,Period), MI\_TST\_Terminate, MI\_TST\_Result(Sent). + - Control: TST Control\_So. + - Generator: TST Generation outputs TST(DA,P,DE, TLV,TLD). + - Output: TST block on the right side. +- LT (Link Trace) Process:** + - Inputs: RI\_LTR(SA,TTL,TID,TLV), MI\_LT(TA,TTL,P), MI\_LT\_Result(Results), RI\_LTM(D,P,DE). + - Control: LT Control. + - Generator: LTM Generation outputs LTM(TA,TTL, TID,P). + - Output: LTM, LTR blocks on the right side. +- SL (Segment Link) Process:** + - Inputs: RI\_SLR(rMEP\_ID,rTest\_ID, TxFcF,TxFcB), MI\_SL\_Start(DA,P,Test\_ID, Length,Period), MI\_SL\_Intermediate\_Request, MI\_SL\_Terminate, MI\_SL\_Result(N\_TF,N\_LF,F\_LF), RI\_SLM(OAM,P,DE,TxFcB). + - Control: On-demand SL Control. + - Mux: SLM Mux (X, Y, Z) outputs SLM(DA,P, MEP\_ID,Test\_ID TxFcF,TLV). + - Generators: SLM Generation, SLR Generation. + - Output: SLM, SLR blocks on the right side. +- ISL (Interval Segment Link) Process:** + - Inputs: MI\_ISL\_Start(DA,P,Test\_ID, Length,Period), MI\_ISL\_Terminate, MI\_MEP\_ID. + - Control: On-demand ISL Control\_So. + - Mux: ISL Mux (X, Y, Z) outputs ISL(DA,P, MEP\_ID,Test\_ID TxFcF,TLV). + - Generator: ISL Generation. + - Output: ISL block on the right side. +- Bottom Interface:** ETH\_CI\_D/P/DE connects to the bottom of the container. +- Side Labels:** + - MEP On Dem and-OAM insertion (vertical label on the right). + - MI\_MEL, MI\_MEP\_MAC (labels on the far right). + +Figure 9-48 – ETHDe\_FT\_So process diagram showing various network management processes and their interactions. + +Figure 9-48 – ETHDe\_FT\_So process + +###### *MEP on-demand OAM insertion process* + +The MEP on-demand OAM insertion process inserts OAM traffic units that are generated in the ETHDe\_FT\_So process into the stream of traffic units. + +For all ETH\_CI\_D received on any but the data input port, the SA field is overwritten with the MI\_MEP\_MAC value. In the MSDU field, the MEL field is overwritten with the MI\_MEL value. + +If the DA of the OAM traffic unit is a class 1 or class 2 multicast DA the OAM insertion process updates the DA to reflect the right MEL. + +This ensures that every generated OAM field has the correct SA, DA and MEL. + +###### *LB control* + +This process is defined in clause 8.1.8 where the LB protocol is defined. Clause 8.1.8.2 defines the LB control process. + +###### *LBM generation* + +This process is defined in clause 8.1.8 where the LB protocol is defined. Clause 8.1.8.3 defines the LBM generation process. + +###### *LBR generation* + +This process is defined in clause 8.1.8 where the LB protocol is defined. Clause 8.1.8.6 defines the LBR generation process. + +###### *On-demand LM control* + +This process is defined in clause 8.1.9 where the LM protocol is defined. Clause 8.1.9.2 defines the on-demand LM control process. + +###### *LMM generation* + +This process is defined in clause 8.1.9 where the LM protocol is defined. Clause 8.1.9.3 defines the LMM generation process. + +###### *LMR generation* + +This process is defined in clause 8.1.9 where the LM protocol is defined. Clause 8.1.9.5 defines the LMR generation process. + +###### *LMM Mux* + +The LMM Mux process interleaves the signal sets LMM(DA,P,0) from the input ports (X, Y, Z). + +###### *Counter process* + +This process is defined in clause 8.1.9.7 and used to count frames for on-demand loss measurements with the on-demand LM protocol. + +###### *On-demand DM control* + +This process is defined in clause 8.1.10 where the DM protocol is defined. Clause 8.1.10.2 defines the DM control process. + +###### *DMM generation* + +This process is defined in clause 8.1.10 where the DM protocol is defined. Clause 8.1.10.3 defines the DMM generation process. + +###### *DMR generation* + +This process is defined in clause 8.1.10 where the DM protocol is defined. Clause 8.1.10.5 defines the DMR generation process. + +###### *DMM Mux* + +The DMM Mux process interleaves the signal sets DMM(DA,P,0,Test ID TLV, TLV) from the input ports (X, Y, Z). + +###### *On-demand IDM Control\_So* + +This process is defined in clause 8.1.11 where the IDM protocol is defined. Clause 8.1.11.2 defines the IDM Control\_So process. + +###### *IDM generation* + +This process is defined in clause 8.1.11 where the IDM protocol is defined. Clause 8.1.11.3 defines the IDM generation process. + +###### *IDM Mux* + +The IDM Mux process interleaves the signal sets IDM(DA,P,0,Test ID TLV, TLV) from the input ports (X, Y, Z). + +###### *TST Control\_So* + +This process is defined in clause 8.1.12 where the TST protocol is defined. Clause 8.1.12.2 defines the TST control process. + +###### *TST generation* + +This process is defined in clause 8.1.12 where the TST protocol is defined. Clause 8.1.12.3 defines the TST generation process. + +###### *LT control* + +This process is defined in clause 8.1.13 where the LT protocol is defined. Clause 8.1.13.2 defines the LT control process. + +###### *LTM generation* + +This process is defined in clause 8.1.13 where the LT protocol is defined. Clause 8.1.13.3 defines the LTM generation process. + +###### *LTR generation* + +This process is defined in clause 8.1.13 where the LT protocol is defined. Clause 8.1.13.6 defines the LTR generation process. + +##### *On-demand SL control* + +This process is defined in clause 8.1.14 where the SL protocol is defined. Clause 8.1.14.2 defines the SL control process. + +###### *SLM generation* + +This process is defined in clause 8.1.14 where the SL protocol is defined. Clause 8.1.14.3 defines the SLM generation process. + +###### *SLR generation* + +This process is defined in clause 8.1.14 where the SL protocol is defined. Clause 8.1.14.5 defines the SLR generation process. + +###### *SLM Mux* + +The SLM Mux process interleaves the signal sets SLM(DA,P,MEP\_ID,Test\_ID,TxFCl,TLV) from the input ports (X, Y, Z). + +###### *On-demand 1SL Control\_So* + +This process is defined in clause 8.1.15 where the 1SL protocol is defined. Clause 8.1.15.2 defines the 1SL Control\_So process. + +###### *1SL generation* + +This process is defined in clause 8.1.15 where the 1SL protocol is defined. Clause 8.1.15.3 defines the 1SL generation process. + +###### *1SL Mux* + +The 1SL Mux process interleaves the signal sets 1SL(DA,P, MEP\_ID,Test\_ID, TxFCI, TLV) from the input ports (X, Y, Z). + +**Defects** None. + +**Consequent actions** None. + +**Defect correlations** None. + +**Performance monitoring** None. + +#### **9.4.1.2 ETH diagnostic flow termination sink function for MEPs (ETHDe\_FT\_Sk)** + +The ETHDe\_FT\_Sk function symbol is shown in Figure 9-49, the interfaces in Table 9-19 and the process diagram in Figure 9-50. + +##### **Symbol** + +![Symbol diagram for ETHDe_FT_Sk function. It is a triangle labeled 'ETHDe'. It has four interfaces: ETH_AP at the top (outgoing), ETH_RP and ETH_TP on the left (incoming), ETHDe_FT_Sk_MP on the right (incoming), and ETH_TFP at the bottom (incoming).](f7f230fff591a530410a07e745649926_img.jpg) + +G.8021-Y.1341(22)\_F9-49 + +Symbol diagram for ETHDe\_FT\_Sk function. It is a triangle labeled 'ETHDe'. It has four interfaces: ETH\_AP at the top (outgoing), ETH\_RP and ETH\_TP on the left (incoming), ETHDe\_FT\_Sk\_MP on the right (incoming), and ETH\_TFP at the bottom (incoming). + +**Figure 9-49 – ETHDe\_FT\_Sk symbol** + +##### Interfaces + +Table 9-19 – ETHDe\_FT\_Sk interfaces + +| Inputs | Outputs | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE

ETHDe_FT_Sk_MP:
ETHDe_FT_Sk_MI_MEL
ETHDe_FT_Sk_MI_MEP_MAC
ETHDe_FT_Sk_MI_IDM_Start(SA,P,Test ID)
ETHDe_FT_Sk_MI_IDM_Intermediate_Request
ETHDe_FT_Sk_MI_IDM_Terminate
ETHDe_FT_Sk_MI_TST_Start(SA,Pattern)
ETHDe_FT_Sk_MI_1SL_Intermediate_Request
ETHDe_FT_Sk_MI_TST_Terminate
ETHDe_FT_Sk_MI_1SL_Start(
SA,MEP_ID, Test_ID)
ETHDe_FT_Sk_MI_1SL_Terminate

ETH_TP:
ETHDe_FT_Sk_TI_TimeStamp1 | ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE

ETH_RP:
ETH_RI_LMM(D,P,DE)
ETH_RI_LMR(TxFCf,RxFCb,TxFCb,RxFCI)
ETH_RI_LMR(rSA,TxFCf,RxFCf,TxFCb,RxFCI)
ETH_RI_LBM(D,P,DE)
ETH_RI_LBR(SA,rTLV,TID)
ETH_RI_DMM(D,P,DE)
ETH_RI_DMR(
rSA,TxTimestampf,RxTimestampf,
TxTimestampb,RxTimeb,rTest ID)
ETH_RI_LTM(D,P,DE)
ETH_RI_LTR(SA,TTL,TID,TLV)
ETH_RI_SLM(OAM,P,DE,TxFCb)
ETH_RI_SLR(
rMEP_ID,rTest_ID,TxFCf,TxFCb)

ETHDe_FT_Sk_MP:
ETHDe_FT_Sk_MI_IDM_Result(
count,N_FD[])
ETHDe_FT_Sk_MI_TST_Result(
REC,CRC,BER,OO)
ETHDe_FT_Sk_MI_1SL_Result(N_TF,N_LF) | + +##### Processes + +![Block diagram of ETHDe_FT_Sk processes showing various reception and control blocks connected to external interfaces.](ee9591f2ed4d59907d52978bb341a903_img.jpg) + +The diagram illustrates the internal processes of the ETHDe\_FT\_Sk system, organized vertically within a large light-blue container. The components and their connections are as follows: + +- External Interfaces:** + - Top:** ETH\_AI\_D/P/DE (Data, Counter, Data blocks with P, D, DE inputs/outputs). + - Left (RI - Request/Indication):** + - RI\_LMM(D, P, DE) + - RI\_LMR(rSA, TxFCf, RxFCb, TxFCb, RxFCI) (connected to LMR DMux) + - RI\_LBM(D, P, DE) + - RI\_LBR(SA, rTVL, TID) + - RI\_DMM(D, P, DE) + - RI\_DMR(rSA, TxTimeStampf, RxTimeStampf, TxTimeStampb, RxTimeb, rTest\_ID) (connected to DMR DMux) + - RI\_LTM(D, P, DE) + - RI\_LTR(SA, TTL, TID, TLV) + - RI\_SLM(OAM, P, DE, TxFCb) + - RI\_SLR(rMEP\_ID, rTest\_ID, TxFCf, TxFCb) (connected to SLR DMux) + - Left (MI - Management Information):** + - MI\_IDM\_Start(SA, P, Test\_ID), MI\_IDM\_Intermediate\_Request, MI\_IDM\_Terminate, MI\_IDM\_Result(count, N\_FD[]) (connected to 1DM Control\_Sk and 1DM DMux) + - TI\_TimeStamp1 + - MI\_TST\_Start(SA, pattern), MI\_TST\_Terminate, MI\_TST\_Result(REC, CRC, BER, OO) (connected to TST Control\_Sk) + - MI\_ISL\_Start(SA, Test\_ID), MI\_ISL\_Intermediate\_Request, MI\_ISL\_Terminate, MI\_ISL\_Result(N\_TF, N\_LF) (connected to 1SL Control\_Sk and 1SL DMux) + - MI\_MEP\_MAC + - Bottom:** ETH\_CI\_D/P/DE (Data, Counter, Data blocks with P, D, DE inputs/outputs). +- Internal Processes (Reception Blocks):** + - LMM Reception + - LMR Reception (connected to LMR DMux) + - MEP LBM Reception + - LBR Reception + - DMM Reception + - DMR Reception (connected to DMR DMux) + - 1DM Reception (connected to 1DM DMux) + - TST Reception (connected to TST Control\_Sk) + - MEP LTM Reception + - LTR Reception + - SLM Reception + - SLR Reception (connected to SLR DMux) + - 1SL Reception (connected to 1SL DMux) +- Control and Multiplexing Blocks:** + - 1DM Control\_Sk (stack of blocks) + - TST Control\_Sk + - 1SL Control\_Sk (stack of blocks) + - DMux blocks: LMR DMux, DMR DMux, 1DM DMux, SLR DMux, 1SL DMux (each with X, Y, Z inputs/outputs). +- Vertical Labels:** + - MEP On Demand-OAM extraction:** Vertical label on the right side. + - MI\_MEL:** Horizontal label pointing to the right side of the container. + +Block diagram of ETHDe\_FT\_Sk processes showing various reception and control blocks connected to external interfaces. + +G.8021-Y.1341(22)\_F9-50 + +Figure 9-50 – ETHDe\_FT\_Sk processes + +###### *MEP on-demand OAM extraction process* + +The MEP on-demand OAM extraction process extracts OAM traffic units that are processed in the ETHDe\_FT\_Sk process from the stream of traffic units as defined in the following pseudo code: + +``` +if (TYPE=) and (MEL=MI_MEL) then + switch(OPC) { + case : if (Flag.Type=0) then + extract ETH-LMM OAM traffic unit and forward to LMM Port + endif + case : if (Flag.Type=0) then + extract ETH-LMR OAM traffic unit and forward to LMR Port + endif + case : if (Flag.Type=0) then + extract ETH-DMM OAM traffic unit and forward to DMM Port + endif + case : if (Flag.Type=0) then + extract ETH-DMR OAM traffic unit and forward to DMR Port + endif + case <1DM>: extract ETH-1DM OAM traffic unit and forward to 1DM Port + case : extract ETH-LTM OAM traffic unit and forward to LTM Port + case : extract ETH-LTR OAM traffic unit and forward to LTR Port + case : extract ETH-LBM OAM traffic unit and forward to LBM Port + case : extract ETH-LBR OAM traffic unit and forward to LBR Port + case : extract ETH-TST OAM traffic unit and forward to TST Port + case : extract ETH-SLM OAM traffic unit and forward to SLM port + case : extract ETH-SLR OAM traffic unit and forward to SLR port + case <1SL>: extract ETH-1SL OAM traffic unit and forward to 1SL Port + default: forward ETH_CI traffic unit to Data port + } +else + forward ETH_CI_traffic unit to Data Port +endif +``` + +NOTE 1 – Further filtering of OAM traffic units is performed by the OAM MEL filter process which forms part of the ETH adaptation functions specified in clause 9.3. + +NOTE 2 – If both ETHDe\_FT and ETHx\_FT are involved in synthetic loss measurements, the MEP on-demand OAM extraction process needs to determine which flow termination the received ETH-SLM PDU belongs to. + +###### *MEP LBM reception* + +This process is defined in clause 8.1.8 where the LB protocol is defined. Clause 8.1.8.5 defines the LBM MEP reception process. + +###### *LBR reception* + +This process is defined in clause 8.1.8 where the LB protocol is defined. Clause 8.1.8.7 defines the LBR reception process. + +###### *LMM reception* + +This process is defined in clause 8.1.9 where the LM protocol is defined. Clause 8.1.9.4 defines the LMM reception process. + +###### *LMR reception* + +This process is defined in clause 8.1.9 where the LM protocol is defined. Clause 8.1.9.6 defines the LMR reception process. + +###### *LMR Demux* + +The LMR Demux process de-interleaves the incoming signal set (D,P,DE) to the different output ports (X, Y, Z). P signal can be used for the selection of the port. + +###### *Counter process* + +This process is defined in clause 8.1.9.7 and used to count frames for on-demand loss measurements with on-demand LM protocol. + +###### *DMM reception* + +This process is defined in clause 8.1.10 where the DM protocol is defined. Clause 8.1.10.4 defines the DMM reception process. + +###### *DMR reception* + +This process is defined in clause 8.1.10 where the DM protocol is defined. Clause 8.1.10.6 defines the DMR reception process. + +###### *DMR Demux* + +The DMR Demux process de-interleaves the incoming signal set (D,P,DE) to the different output ports (X, Y, Z). P and/or Test\_ID signal can be used for the selection of the port. + +###### *IDM reception* + +This process is defined in clause 8.1.11 where the 1DM protocol is defined. Clause 8.1.11.4 defines the 1DM reception process. + +###### *IDM Demux* + +The 1DM Demux process de-interleaves the incoming signal set (D,P,DE) to the different output ports (X, Y, Z). P and/or Test\_ID signal can be used for the selection of the port. + +###### *IDM Control\_Sk* + +This process is defined in clause 8.1.11 where the 1DM protocol is defined. Clause 8.1.11.5 defines the 1DM Control\_Sk process. + +###### *TST reception* + +This process is defined in clause 8.1.12 where the TST protocol is defined. Clause 8.1.12.4 defines the TST reception process. + +###### *TST Control\_Sk* + +This process is defined in clause 8.1.12 where the TST protocol is defined. Clause 8.1.12.5 defines the TST Control\_Sk process. + +###### *MEP LTM reception* + +This process is defined in clause 8.1.13 where the LT protocol is defined. Clause 8.1.13.5 defines the MEP LTM reception process. + +###### *LTR reception* + +This process is defined in clause 8.1.13 where the LT protocol is defined. Clause 8.1.13.7 defines the LTR reception process. + +###### *SLM reception* + +This process is defined in clause 8.1.14 where the SL protocol is defined. Clause 8.1.14.4 defines the SLM reception process. + +###### *SLR reception* + +This process is defined in clause 8.1.14 where the SL protocol is defined. Clause 8.1.14.6 defines the SLR reception process. + +###### *SLR Demux* + +The SLR Demux process de-interleaves the incoming signal set (D,P,DE) to the different output ports (X, Y, Z). P and/or Test\_ID signal can be used for the selection of the port. + +###### *1SL reception* + +This process is defined in clause 8.1.15 where the 1SL protocol is defined. Clause 8.1.15.4 defines the 1SL reception process. + +###### *1SL Demux* + +The 1DM Demux process de-interleaves the incoming signal set (D,P,DE) to the different output ports (X, Y, Z). P and/or Test\_ID signal can be used for the selection of the port. + +###### *1SL Control\_Sk* + +This process is defined in clause 8.1.15 where the 1SL protocol is defined. Clause 8.1.15.5 defines the 1SL control\_Sk process. + +| | | +|-------------------------------|-------| +| Defects | None. | +| Consequent actions | None. | +| Defect correlations | None. | +| Performance monitoring | None. | + +### **9.4.2 ETH diagnostic flow termination functions for MIPs (ETHDi\_FT)** + +#### **9.4.2.1 ETH diagnostic flow termination source function for MIPs (ETHDi\_FT\_So)** + +The ETHDi\_FT\_So function symbol is shown in Figure 9-51, the interfaces in Table 9-20 and the process diagram in Figure 9-52. + +##### **Symbol** + +![Figure 9-51 – ETHDi_FT_So symbol. The diagram shows a process symbol represented by an inverted triangle labeled 'ETHDi'. It has four interfaces: 'ETH_AP' entering from the top, 'ETHDi_FT_So_MP' entering from the left, 'ETH_RP' entering from the right, and 'ETH_TFP' exiting from the bottom. Below the symbol is the text 'G.8021-Y.1341(22)_F9-51'.](db07d724465f878d65ab139b4b39fc65_img.jpg) + +G.8021-Y.1341(22)\_F9-51 + +Figure 9-51 – ETHDi\_FT\_So symbol. The diagram shows a process symbol represented by an inverted triangle labeled 'ETHDi'. It has four interfaces: 'ETH\_AP' entering from the top, 'ETHDi\_FT\_So\_MP' entering from the left, 'ETH\_RP' entering from the right, and 'ETH\_TFP' exiting from the bottom. Below the symbol is the text 'G.8021-Y.1341(22)\_F9-51'. + +**Figure 9-51 – ETHDi\_FT\_So symbol** + +##### Interfaces + +Table 9-20 – ETHDi\_FT\_So interfaces + +| Inputs | Outputs | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------| +| ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE

ETH_RP:
ETH_RI_LBM(D,P,DE)
ETH_RI_LTM(D,P,DE)

ETHDi_FT_So_MP:
ETHDi_FT_So_MI_MEL
ETHDi_FT_So_MI_MIP_MAC | ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE | + +##### Processes + +![Diagram of the ETHDi_FT_So process. A central 'MIP OAM insertion' block receives 'Data' from the top (ETH_AI_D/P/DE) and OAM traffic units from 'LBR generation' and 'LTR generation' blocks. The 'LBR generation' block receives RI_LBM(D,P,DE) and outputs D, P, and DE signals to the 'LBR' block. The 'LTR generation' block receives RI_LTM(D,P,DE) and outputs D, P, and DE signals to the 'LTR' block. The 'MIP OAM insertion' block also receives MI_MEL and MI_MIP_MAC inputs from the right. The output of the 'MIP OAM insertion' block is ETH_CI_D/P/DE at the bottom. The diagram is labeled G.8021-Y.1341(22)_F9-52.](b8711ada890f740e219352d774acd75d_img.jpg) + +Diagram of the ETHDi\_FT\_So process. A central 'MIP OAM insertion' block receives 'Data' from the top (ETH\_AI\_D/P/DE) and OAM traffic units from 'LBR generation' and 'LTR generation' blocks. The 'LBR generation' block receives RI\_LBM(D,P,DE) and outputs D, P, and DE signals to the 'LBR' block. The 'LTR generation' block receives RI\_LTM(D,P,DE) and outputs D, P, and DE signals to the 'LTR' block. The 'MIP OAM insertion' block also receives MI\_MEL and MI\_MIP\_MAC inputs from the right. The output of the 'MIP OAM insertion' block is ETH\_CI\_D/P/DE at the bottom. The diagram is labeled G.8021-Y.1341(22)\_F9-52. + +Figure 9-52 – ETHDi\_FT\_So process + +###### *MIP OAM insertion* + +The MIP OAM insertion process inserts OAM traffic units that are generated in the ETHDi\_FT\_So process into the stream of traffic units. + +For all ETH\_CI\_D received on any but the data input port, the SA field is overwritten with the MI\_MIP\_MAC value. In the MSDU field the EtherType value is overwritten with the OAM EtherType value (89-02) and the MEL field is overwritten with the MI\_MEL value. + +This ensures that every generated OAM field has the correct SA, EtherType and MEL. + +###### *LBR generation* + +This process is defined in clause 8.1.8 where the LB protocol is defined. Clause 8.1.8.6 defines the LBR generation process. + +###### *LTR generation* + +This process is defined in clause 8.1.13 where the LT protocol is defined. Clause 8.1.13.6 defines the LTR generation process. This process may be regarded as the LT responder which is located outside of this MIP independently, however, the process itself is the same. + +- Defects**                      None. +- Consequent actions**      None. +- Defect correlations**      None. +- Performance monitoring**      None. + +#### **9.4.2.2    ETH diagnostic flow termination sink function for MIPs (ETHDi\_FT\_Sk)** + +The ETHDi\_FT\_Sk function symbol is shown in Figure 9-53, the interfaces in Table 9-21 and the process diagram in Figure 9-54. + +##### **Symbol** + +![Symbol diagram for ETHDi_FT_Sk. It is an inverted triangle labeled 'ETHDi'. It has three input arrows pointing to its vertices: 'ETH_TFP' from the bottom vertex, 'ETHDi_FT_Sk_MP' from the right vertex, and 'ETH_RP' from the left vertex. It has one output arrow pointing from the top vertex labeled 'ETH_AP'. A small text 'G.8021-Y.1341(22)_F9-53' is located below the diagram.](8650b869a9e7291ac2caad3d008e1770_img.jpg) + +Symbol diagram for ETHDi\_FT\_Sk. It is an inverted triangle labeled 'ETHDi'. It has three input arrows pointing to its vertices: 'ETH\_TFP' from the bottom vertex, 'ETHDi\_FT\_Sk\_MP' from the right vertex, and 'ETH\_RP' from the left vertex. It has one output arrow pointing from the top vertex labeled 'ETH\_AP'. A small text 'G.8021-Y.1341(22)\_F9-53' is located below the diagram. + +**Figure 9-53 – ETHDi\_FT\_Sk symbol** + +##### **Interfaces** + +**Table 9-21 – ETHDi\_FT\_Sk interfaces** + +| Inputs | Outputs | +|------------------------------------------------------------------------|------------------------------------------------------------| +| ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE | ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE | +| ETHDi_FT_Sk_MP:
ETHDi_FT_Sk_MI_MEL
ETHDi_FT_Sk_MI_MIP_MAC | ETH_RP:
ETH_RI_LBM(D,P,DE)
ETH_RI_LTM(D,P,DE) | + +##### Processes + +![Diagram of the ETHDi_FT_Sk process showing data flow and control signals. The process is represented by a large blue rectangle. At the top, 'ETH_AI_D/P/DE' has three arrows pointing out. At the bottom, 'ETH_CI_D/P/DE' has three arrows pointing in. On the left, 'MI_MIP_MAC' points to a 'Data' block. 'RI_LTM(D,P,DE)' points to a 'MIP LTM reception' block, which in turn points to an 'LTM' block. 'RI_LBM(D,P,DE)' points to a 'MIP LBM reception' block, which points to an 'LBM' block. Both 'LTM' and 'LBM' blocks point to a 'MIP OAM extraction' block. This block has an output 'MI_MEL' on the right and points to a 'Data' block. Above the 'MIP OAM extraction' block is a 'MIP OAM insertion' block, which points to another 'Data' block. This 'Data' block points to the 'ETH_AI_D/P/DE' output. Various 'D', 'P', and 'DE' labels are associated with the internal blocks and their connections.](6fd13a25b57a43ec4327cca60c294973_img.jpg) + +Diagram of the ETHDi\_FT\_Sk process showing data flow and control signals. The process is represented by a large blue rectangle. At the top, 'ETH\_AI\_D/P/DE' has three arrows pointing out. At the bottom, 'ETH\_CI\_D/P/DE' has three arrows pointing in. On the left, 'MI\_MIP\_MAC' points to a 'Data' block. 'RI\_LTM(D,P,DE)' points to a 'MIP LTM reception' block, which in turn points to an 'LTM' block. 'RI\_LBM(D,P,DE)' points to a 'MIP LBM reception' block, which points to an 'LBM' block. Both 'LTM' and 'LBM' blocks point to a 'MIP OAM extraction' block. This block has an output 'MI\_MEL' on the right and points to a 'Data' block. Above the 'MIP OAM extraction' block is a 'MIP OAM insertion' block, which points to another 'Data' block. This 'Data' block points to the 'ETH\_AI\_D/P/DE' output. Various 'D', 'P', and 'DE' labels are associated with the internal blocks and their connections. + +Figure 9-54 – ETHDi\_FT\_Sk process + +###### *MIP OAM extraction process* + +The MIP OAM extraction process extracts OAM traffic units that are processed in the ETHDi\_FT\_Sk process from the stream of traffic units as defined in the following pseudo code: + +``` + +if (TYPE=) and (MEL=MI_MEL) then + switch(OPC) { + case : extract ETH-LBM OAM traffic unit + forward one copy of ETH-LBM OAM traffic unit to LBM Port + forward one copy of ETH-LBM OAM traffic unit to Data Port + case : extract ETH-LTM OAM traffic unit and forward to LTM Port + default: forward ETH_CI traffic unit to Data port + } +else + forward ETH CI traffic unit to Data Port +endif + +``` + +NOTE – Further filtering of OAM traffic units is performed by the OAM MEL filter process which forms part of the ETH adaptation functions specified in clause 9.3. + +###### *MIP OAM insertion process* + +The MIP OAM insertion process inserts OAM traffic units that are generated in the ETHDi\_FT\_Sk process into the stream of traffic units. + +For all ETH\_CI\_D received on any but the data input port, the SA field is overwritten with the MI\_MIP\_MAC value. In the MSDU field the EtherType value is overwritten with the OAM EtherType value (89-02) and the MEL field is overwritten with the MI\_MEL value. + +This ensures that every generated OAM field has the correct SA, EtherType and MEL. + +###### *MIP LBM reception process* + +This process is defined in clause 8.1.8 where the LB protocol is defined. Clause 8.1.8.4 defines the LBM MIP reception process. + +###### *MIP LTM reception process* + +This process is defined in clause 8.1.13 where the LT protocol is defined. Clause 8.1.13.4 defines the MIP LTM reception process. This process may be regarded as the LT responder which is located outside of this MIP independently, however, the process itself is the same. + +**Defects** None. + +**Consequent actions** None. + +**Defect correlations** None. + +**Performance monitoring** None. + +### **9.4.3 ETHD to ETH adaptation functions (ETHD/ETH\_A)** + +The ETHD/ETH adaptation function is an empty function; it is included to satisfy the modelling rules. + +The bidirectional ETHD/ETH adaptation function is performed by a co-located pair of ETHD/ETH adaptation source (ETHD/ETH\_A\_So) and sink (ETHD/ETH\_A\_Sk) functions. + +#### **9.4.3.1 ETHD to ETH adaptation source function (ETHD/ETH\_A\_So)** + +The ETHD/ETH\_A\_So function symbol is shown in Figure 9-55, the interfaces in Table 9-22 and a process diagram in Figure 9-56. + +![Symbol diagram for ETHD/ETH_A_So showing input ETH_FP entering a trapezoidal block labeled ETHD/ETH, with output ETH_AP exiting from the bottom.](509779aa1af96e7cd70c7f336dae46d7_img.jpg) + +Symbol diagram for ETHD/ETH\_A\_So showing input ETH\_FP entering a trapezoidal block labeled ETHD/ETH, with output ETH\_AP exiting from the bottom. + +G.8021-Y.1341(22)\_F9-55 + +**Figure 9-55 – ETHD/ETH\_A\_So symbol** + +##### **Interfaces** + +**Table 9-22 – ETHD/ETH\_A\_So interfaces** + +| Inputs | Outputs | +|------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE

See specific OAM process for additional inputs | ETH_AP:
ETHD_AI_D
ETHD_AI_P
ETHD_AI_DE

See specific OAM process for additional inputs | + +##### Processes + +![Figure 9-56 – ETHD/ETH_A_So process diagram. A rectangular box represents the process. Above the box are three labels: CI_D, CI_P, and CI_DE. Below the box are three labels: AI_D, AI_P, and AI_DE. Three downward-pointing arrows connect each label above the box to its corresponding label below the box. Below the diagram is the text G.8021-Y.1341(22)_F9-56.](f449330259f8d44842bfe0829754c00f_img.jpg) + +Figure 9-56 – ETHD/ETH\_A\_So process diagram. A rectangular box represents the process. Above the box are three labels: CI\_D, CI\_P, and CI\_DE. Below the box are three labels: AI\_D, AI\_P, and AI\_DE. Three downward-pointing arrows connect each label above the box to its corresponding label below the box. Below the diagram is the text G.8021-Y.1341(22)\_F9-56. + +**Figure 9-56 – ETHD/ETH\_A\_So process** + +| | | +|-------------------------------|-------| +| Defects | None. | +| Consequent actions | None. | +| Defect correlations | None. | +| Performance monitoring | None. | + +#### 9.4.3.2 ETHD to ETH adaptation sink function (ETHD/ETH\_A\_Sk) + +The ETHD/ETH\_A\_Sk function symbol is shown in Figure 9-57, the interfaces in Table 9-23 and the process diagram in Figure 9-58. + +##### Symbol + +![Figure 9-57 – ETHD/ETH_A_Sk symbol diagram. A trapezoidal symbol labeled 'ETHD/ETH' is shown. An upward-pointing arrow labeled 'ETH_FP' is above the symbol. A downward-pointing arrow labeled 'ETH_AP' is below the symbol. Below the diagram is the text G.8021-Y.1341(22)_F9-57.](b3ad5fc9a1d8a79bb5ed74ae00d9d9de_img.jpg) + +Figure 9-57 – ETHD/ETH\_A\_Sk symbol diagram. A trapezoidal symbol labeled 'ETHD/ETH' is shown. An upward-pointing arrow labeled 'ETH\_FP' is above the symbol. A downward-pointing arrow labeled 'ETH\_AP' is below the symbol. Below the diagram is the text G.8021-Y.1341(22)\_F9-57. + +**Figure 9-57 – ETHD/ETH\_A\_Sk symbol** + +##### Interfaces + +**Table 9-23 – ETHD/ETH\_A\_Sk interfaces** + +| Inputs | Outputs | +|--------------------------------------------------------|-----------------------------------------------------| +| ETH_AP:
ETHD_AI_D
ETHD_AI_P
ETHD_AI_DE | ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE | + +##### Processes + +![Figure 9-58 – ETHD/ETH_A_Sk process diagram. A rectangular box represents the process. Above the box are three labels: CI_D, CI_P, and CI_DE. Below the box are three labels: AI_D, AI_P, and AI_DE. Three upward-pointing arrows connect each label below the box to its corresponding label above the box. Below the diagram is the text G.8021-Y.1341(22)_F9-58.](e1b78b9e9c5f905794c8929f71c72894_img.jpg) + +Figure 9-58 – ETHD/ETH\_A\_Sk process diagram. A rectangular box represents the process. Above the box are three labels: CI\_D, CI\_P, and CI\_DE. Below the box are three labels: AI\_D, AI\_P, and AI\_DE. Three upward-pointing arrows connect each label below the box to its corresponding label above the box. Below the diagram is the text G.8021-Y.1341(22)\_F9-58. + +**Figure 9-58 – ETHD/ETH\_A\_Sk process** + +### 9.4.4 ETHDi to ETH adaptation functions (ETHDi/ETH\_A) + +The ETHDi/ETH inserts and extracts the R-APS information into or from the stream of ETH\_CI. + +#### 9.4.4.1 ETHDi to ETH adaptation source function (ETHDi/ETH\_A\_So) + +This function allows the insertion of R-APS information into a stream of ETH\_CI. The ETHDi/ETH\_A\_So function symbol is shown in Figure 9-59, the interfaces in Table 9-24 and the process diagram in Figure 9-60. + +##### Symbol + +![Figure 9-59: ETHDi/ETH_A_So symbol. A trapezoidal block labeled 'ETHDi/ETH'. An input arrow labeled 'ETH_FP' points from the top into the block. An output arrow labeled 'ETH_AP' points from the bottom of the block. A control input arrow labeled 'ETHDi/ETH_A_So_MP' points from the left into the block. Below the block is the text 'G.8021-Y.1341(22)_F9-59'.](c15a562ebfee037f0507073e0dfebda7_img.jpg) + +Figure 9-59: ETHDi/ETH\_A\_So symbol. A trapezoidal block labeled 'ETHDi/ETH'. An input arrow labeled 'ETH\_FP' points from the top into the block. An output arrow labeled 'ETH\_AP' points from the bottom of the block. A control input arrow labeled 'ETHDi/ETH\_A\_So\_MP' points from the left into the block. Below the block is the text 'G.8021-Y.1341(22)\_F9-59'. + +Figure 9-59 – ETHDi/ETH\_A\_So symbol + +##### Interfaces + +Table 9-24 – ETHDi/ETH\_A\_So interfaces + +| Inputs | Outputs | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| +| ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_RAPS

ETHDi/ETH_A_So_MP:
ETHDi/ETH_A_So_MI_MEL
ETHDi/ETH_A_So_MI_RAPS_Pri
ETHDi/ETH_A_So_MI_MIP_MAC | ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE | + +##### Processes + +![Figure 9-60: ETHDi/ETH_A_So process. A diagram showing a 'RAPS insert' block inside a larger grey box. Inputs from the top enter the 'RAPS insert' block: 'ETH_CI_RAPS' (direct), 'ETH_CI_P' (labeled 'P'), 'ETH_CI_DE' (labeled 'DE'), and 'ETH_CI_D' (labeled 'D'). Control inputs from the right enter the 'RAPS insert' block: 'MI_MEL', 'MI_RAPS_Pri', and 'MI_MIP_MAC'. Outputs from the bottom of the 'RAPS insert' block exit the grey box: 'ETH_AI_P' (labeled 'P'), 'ETH_AI_DE' (labeled 'DE'), and 'ETH_AI_D' (labeled 'D'). Below the grey box is the text 'G.8021-Y.1341(22)_F9-60'.](1d44bdd1863e06a905f90ab64d0daaa7_img.jpg) + +Figure 9-60: ETHDi/ETH\_A\_So process. A diagram showing a 'RAPS insert' block inside a larger grey box. Inputs from the top enter the 'RAPS insert' block: 'ETH\_CI\_RAPS' (direct), 'ETH\_CI\_P' (labeled 'P'), 'ETH\_CI\_DE' (labeled 'DE'), and 'ETH\_CI\_D' (labeled 'D'). Control inputs from the right enter the 'RAPS insert' block: 'MI\_MEL', 'MI\_RAPS\_Pri', and 'MI\_MIP\_MAC'. Outputs from the bottom of the 'RAPS insert' block exit the grey box: 'ETH\_AI\_P' (labeled 'P'), 'ETH\_AI\_DE' (labeled 'DE'), and 'ETH\_AI\_D' (labeled 'D'). Below the grey box is the text 'G.8021-Y.1341(22)\_F9-60'. + +Figure 9-60 – ETHDi/ETH\_A\_So process + +##### *RAPS insert* + +The RAPS insert process encodes the ETH\_CI\_RAPS signal into the ETH\_CI\_D signal of an ETH\_CI traffic unit; the resulting RAPS traffic unit is inserted into the stream of incoming traffic units, i.e., the outgoing stream consist of the incoming traffic units and the inserted RAPS traffic units. The ETH\_CI\_RAPS signal contains the RAPS specific information as defined in [ITU-T G.8032]. + +The ETH\_CI\_D signal contains a source and destination address field and an MSDU field. The format of the MSDU field for RAPS traffic units is determined by the ETH\_CI\_RAPS signal. The MEL in the MSDU field is determined by the MI\_MEL input parameter. + +The values of the source and destination address fields in the ETH\_CI\_D signal are determined by the local MAC address of the maintenance entity group intermediate point (MIP) (MI\_MIP\_MAC) and the ring multicast address as described in [ITU-T G.8032]. The value of the ring multicast MAC address is 01-19-A7-00-00-01. The value of MI\_MIP\_MAC should be a valid unicast MAC address. The value of the ETH\_CI\_P signal associated with the generated RAPS traffic units is determined by the MI\_RAPS\_Pri input parameter. + +The value of the ETH\_CI\_DE signal associated with the generated RAPS traffic units is set to drop ineligible. + +#### 9.4.4.2 ETHDi to ETH adaptation sink function (ETHDi/ETH\_A\_Sk) + +This function extracts the RAPS information from the RAPS traffic units without filtering the traffic unit. The ETHDi/ETH\_A\_Sk function symbol is shown in Figure 9-61, the interfaces in Table 9-25 and the process diagram in Figure 9-62. + +##### Symbol + +![Symbol diagram for ETHDi/ETH_A_Sk function. It shows a trapezoidal block labeled 'ETHDi/ETH'. An arrow labeled 'ETH_AP' points into the bottom of the block. An arrow labeled 'ETH_FP' points out of the top of the block. An arrow labeled 'ETHDi/ETH_A_Sk_MP' points into the right side of the block. Below the block is the text 'G.8021-Y.1341(22)_F9-61'.](e579f4085bfb7766ce76d03036f97e36_img.jpg) + +G.8021-Y.1341(22)\_F9-61 + +Symbol diagram for ETHDi/ETH\_A\_Sk function. It shows a trapezoidal block labeled 'ETHDi/ETH'. An arrow labeled 'ETH\_AP' points into the bottom of the block. An arrow labeled 'ETH\_FP' points out of the top of the block. An arrow labeled 'ETHDi/ETH\_A\_Sk\_MP' points into the right side of the block. Below the block is the text 'G.8021-Y.1341(22)\_F9-61'. + +Figure 9-61 – ETHDi/ETH\_A\_Sk symbol + +##### Interfaces + +Table 9-25 – ETHDi/ETH\_A\_Sk interfaces + +| Inputs | Outputs | +|-----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| ETH_AP:
ETH_AI_D
ETH_AI_P
ETH_AI_DE
ETH_AI_TSF

ETHDi/ETH_A_Sk_MP:
ETHDi/ETH_A_Sk_MI_MEL | ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_RAPS
ETH_CI_SSF | + +NOTE – Currently in this Recommendation, for the ETHDi\_FT\_Sk, no consequent action for the ETH\_CI\_SSF input has been defined. However, the consequent action should be ETH\_AI\_TSF output to propagate the failure information. + +##### Processes + +![Diagram of the ETHDi/ETH_A_Sk process. A large grey box represents the process boundary. Inside, on the left, a box labeled 'Consequent actions' receives an input from 'ETH_AI_TSF' (bottom) and sends an output to 'ETH_CI_SSF' (top). In the center, a box labeled 'RAPS extract' receives inputs 'P', 'DE', and 'D' from 'ETH_AI_P/DE/D' (bottom) and an external input 'MI_RAPS_MEL' (right). It sends an output to 'ETH_CI_RAPS' (top) and also outputs 'P', 'DE', and 'D' to 'ETH_CI_P/DE/D' (top). The diagram is labeled 'G.8021-Y.1341(22)_F9-62' at the bottom right.](07c0c40e07af066b06f77e9d74b193fc_img.jpg) + +Diagram of the ETHDi/ETH\_A\_Sk process. A large grey box represents the process boundary. Inside, on the left, a box labeled 'Consequent actions' receives an input from 'ETH\_AI\_TSF' (bottom) and sends an output to 'ETH\_CI\_SSF' (top). In the center, a box labeled 'RAPS extract' receives inputs 'P', 'DE', and 'D' from 'ETH\_AI\_P/DE/D' (bottom) and an external input 'MI\_RAPS\_MEL' (right). It sends an output to 'ETH\_CI\_RAPS' (top) and also outputs 'P', 'DE', and 'D' to 'ETH\_CI\_P/DE/D' (top). The diagram is labeled 'G.8021-Y.1341(22)\_F9-62' at the bottom right. + +Figure 9-62 – ETHDi/ETH\_A\_Sk process + +##### RAPS extract + +The RAPS extract process extracts ETH\_CI\_RAPS signals from the incoming stream of ETH\_CI traffic units without filtering the RAPS traffic unit. ETH\_CI\_RAPS signals are only extracted if they belong to the MEL as defined by the MI\_MEL input parameter. + +If an incoming traffic unit is an RAPS traffic unit belonging to the MEL defined by MI\_MEL, the traffic unit will be duplicated. The original RAPS traffic unit will be transparently forwarded and the ETH\_CI\_RAPS signal will be extracted from the duplicate. The ETH\_CI\_RAPS is the RAPS specific information contained in the received traffic unit. All other traffic units will be transparently forwarded without being duplicated. The encoding of the ETH\_CI\_D signal for RAPS frames is defined in clause 9.10 of [ITU-T G.8013]. + +The criteria for filtering are based on the values of the fields within the MSDU field of the ETH\_CI\_D signal: + +- length/type field equals the OAM EtherType (89-02) +- MEL field equals MI\_MEL +- OAM type equals RAPS (40), as defined in clause 9.1 of [ITU-T G.8013]. + +**Defects** None. + +**Consequent actions** aSSF ← AI\_TSF + +**Defect correlations** None. + +**Performance monitoring** None. + +## 9.5 Server to ETH adaptation functions (/ETH\_A) + +There are two basic types of Server to ETH adaptation functions defined in [ITU-T G.8010]: single ETH flow point (/ETH\_A) and multiple ETH flow points (/ETH-m\_A). + +Figure 9-63 presents a high-level view of the processes that are present in a generic server to ETH adaptation function (/ETH). The information crossing the /ETH termination flow point (ETH\_TFP) is referred to as the ETH characteristic information (ETH\_CI). The information crossing the server layer access point (\_AP) is referred to as the server-specific adapted information (\_AI). + +![Diagram of Server to ETH adaptation functions showing two side-by-side processing blocks. The left block (source direction) shows inputs ETH_TFP and ETH_FP entering a 'Queueing' block, which then feeds into a 'Replicate' block. The 'Replicate' block outputs to a 'Server specific' block and also has an output labeled ETH_PP. The 'Server specific' block outputs to /ETH_A_So. The right block (sink direction) shows the 'Server specific' block receiving input from /ETH_A_Sk and sending it to a 'Replicate' block. The 'Replicate' block feeds into a 'Filter' block, which then outputs to ETH_TFP and ETH_FP. A dashed line labeled '(Note)' separates the 'Replicate' and 'Server specific' blocks in both diagrams. The text G.8021-Y.1341(22)_F9-63 is at the bottom right.](d5de4c1d2f0b71aa339b6b2118268fbb_img.jpg) + +Diagram of Server to ETH adaptation functions showing two side-by-side processing blocks. The left block (source direction) shows inputs ETH\_TFP and ETH\_FP entering a 'Queueing' block, which then feeds into a 'Replicate' block. The 'Replicate' block outputs to a 'Server specific' block and also has an output labeled ETH\_PP. The 'Server specific' block outputs to /ETH\_A\_So. The right block (sink direction) shows the 'Server specific' block receiving input from /ETH\_A\_Sk and sending it to a 'Replicate' block. The 'Replicate' block feeds into a 'Filter' block, which then outputs to ETH\_TFP and ETH\_FP. A dashed line labeled '(Note)' separates the 'Replicate' and 'Server specific' blocks in both diagrams. The text G.8021-Y.1341(22)\_F9-63 is at the bottom right. + +NOTE – This dashed line is shown for reference only. It corresponds to the ISS interface in the [IEEE 802.1Q] model. + +**Figure 9-63 – Server to ETH adaptation functions** + +The "Filter", "Queueing", and "Replicate" processes are defined in clauses 8.3, 8.2, and 8.4, respectively. The adaptation functions for adapting the ETH layer to a particular server layer are defined in the ITU-T Recommendation that specifies the /ETH\_A function for that server layer. The processes above the annotated dashed line of Figure 9-63 are collectively called "client-specific processes" in ITU-T Recommendations specifying such /ETH\_A functions. Processes that apply to multiple (but not all) server layers are specified in clause 8.6 of this Recommendation to provide a common definition. + +The /ETH-m\_A is defined as a compound function of the /ETH\_A atomic function, an optional NCP MEP compound function (see clause 9.8.1) and the ETHx/ETH-m\_A atomic function (see clause 9.3.2). + +NOTE 1 – Filtering in the /ETH\_A sink adaptation function is not applied to frames forwarded to the ETH\_TFP. The processes connected to this ETH\_TFP should filter ETH\_CI or process it. + +NOTE 2 – Queueing of frames in the source direction is also not applied for frames from the ETH\_TFP. If queueing of frames in the sink direction is required when traffic conditioning is applied, this will be included in the traffic conditioning function. + +NOTE 3 – For the Ethernet private line (EPL) service defined in [ITU-T G.8011] ETH\_TFP is unconnected. For services supporting ETH\_TFP in the source direction, prioritization of frames received across the ETH\_FP and ETH\_TFP interfaces will be required. + +NOTE 4 – Server to ETH adaptation functions may have the processes of AIS insert (see clause 8.1.4) and LCK generation (see clause 8.1.2), and BNM insert (see clause 8.1.18). Note that Figure 9-63 and related figures in clauses 9.7, 10 and 11 do not explicitly depict those features to avoid introducing the description complexity. + +NOTE 5 – The queueing, filter, and replicate processes operate as null functions, as specified in clauses 8.2, 8.3 and 8.4, respectively, when the is MPLS-TP. + +## 9.6 ETH traffic conditioning and shaping functions (ETH\_TCS) + +### 9.6.1 ETH traffic shaping function (ETH\_TCS\_So) + +The ETH\_TCS\_So function symbol is shown in Figure 9-64 (where one or more ETH\_FPs may be present at both input and output) and the interfaces in Table 9-26. + +##### Symbol + +![Figure 9-64 – ETH_TCS_So symbol. The diagram shows a diamond-shaped function symbol. On the left, an arrow labeled 'ETH_TCS_So_MP' points into the diamond. Above the diamond, two arrows labeled 'ETH_FP' point down into it, with a vertical ellipsis between them. Below the diamond, two arrows labeled 'ETH_FP' point down from it, also with a vertical ellipsis between them. The text 'G.8021-Y.1341(22)_F9-64' is located to the right of the diamond.](7d31539efb05e7116d0c7b279767ae8f_img.jpg) + +Figure 9-64 – ETH\_TCS\_So symbol. The diagram shows a diamond-shaped function symbol. On the left, an arrow labeled 'ETH\_TCS\_So\_MP' points into the diamond. Above the diamond, two arrows labeled 'ETH\_FP' point down into it, with a vertical ellipsis between them. Below the diamond, two arrows labeled 'ETH\_FP' point down from it, also with a vertical ellipsis between them. The text 'G.8021-Y.1341(22)\_F9-64' is located to the right of the diamond. + +Figure 9-64 – ETH\_TCS\_So symbol + +#### Interfaces + +Table 9-26 – ETH\_TCS\_So interfaces + +| Inputs | Outputs | +|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| +| ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE

ETH_TCS_So_MP:
ETH_TCS_So_MI_[IEEE 802.1Q] | ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE | + +#### Processes + +The ETH traffic shaping process is specified by reference to general flow classification and metering in clause 8.6.5 of [IEEE 802.1Q]. + +NOTE – This Recommendation specifies this process by reference to [IEEE 802.1Q], and intentionally does not provide details as this functionality is well understood from the IEEE work. + +**Defects** None. + +**Consequent actions** None. + +**Defect correlations** None. + +**Performance monitoring** None. + +### 9.6.2 ETH traffic conditioning function (ETH\_TCS\_Sk) + +The ETH\_TCS\_Sk function symbol is shown in Figure 9-65 and the interfaces in Table 9-27. + +##### Symbol + +![Figure 9-65 – ETH_TCS_Sk symbol. The diagram shows a diamond-shaped function symbol. An arrow labeled 'ETH_TCS_Sk_MP' points into the diamond from the left. An arrow labeled 'ETH_FP' points out of the top vertex of the diamond. Another arrow labeled 'ETH_FP' points into the bottom vertex of the diamond. Below the diamond, the text 'G.8021-Y.1341(22)_F9-65' is present.](e27f0c293be4088211306b9fc673178b_img.jpg) + +Figure 9-65 – ETH\_TCS\_Sk symbol. The diagram shows a diamond-shaped function symbol. An arrow labeled 'ETH\_TCS\_Sk\_MP' points into the diamond from the left. An arrow labeled 'ETH\_FP' points out of the top vertex of the diamond. Another arrow labeled 'ETH\_FP' points into the bottom vertex of the diamond. Below the diamond, the text 'G.8021-Y.1341(22)\_F9-65' is present. + +Figure 9-65 – ETH\_TCS\_Sk symbol + +##### Interfaces + +Table 9-27 – ETH\_TCS\_Sk interfaces + +| Inputs | Outputs | +|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| +| ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE

ETH_TCS_Sk_MP:
ETH_TCS_Sk_MI_[IEEE 802.1Q] | ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE | + +#### Processes + +The ETH traffic conditioning process is specified on a per ETH\_FP basis by reference to the bandwidth profile parameters, algorithm and associated parameters in clause 8.6.5.1.3 of [IEEE 802.1Q]. + +NOTE – This Recommendation specifies this process by reference to [IEEE 802.1Q], and intentionally does not provide details as this functionality is well understood from the IEEE work. + +**Defects** None. + +**Consequent actions** None. + +**Defect correlations** None. + +**Performance monitoring** None. + +## 9.7 ETH link aggregation functions + +The ETH link aggregation functions model the link aggregation functionality as described in [IEEE 802.1AX]. + +The generic model used is shown in Figures 9-66 and 9-67. Figure 9-66 shows the simplified model for the case of one single aggregator, while Figure 9-67 shows the generic model for the case of several aggregators. Np denotes the number of members in the LAG, while Na is the number of aggregators. + +NOTE – Figures 9-66 and 9-67 decompose the internal processes of ETH-LAG-Np-Na\_FT function from a modelling standpoint. It is possible to instantiate MEPs on each of the members of a LAG. + +![Figure 9-66: Simplified model of Ethernet link aggregation with decomposition of ETH-LAG-Np-Na_FT function for Na=1. The diagram shows a transformation from a simplified model on the left to a detailed decomposition on the right. On the left, ETH_TFP and ETH_FP connect to an ETH-LAG/ETH block, which connects via ETH-LAG_AP to an ETH-LAG-Np-1 block. This block then connects to two ETH_TFP outputs, with a dashed line indicating multiple paths. On the right, the decomposition shows ETH_TFP and ETH_FP connecting to an ETH-LAG/ETH block, which connects via ETH-LAG_AP to an ETH-LAG block. This block connects via ETH-LAG_FP to an ETH-Np/ETH-LAG-1 block. This block then connects to two ETHnull blocks via ETH_AP[1...Np]. The ETHnull blocks connect to two ETH_TFP outputs, with a dashed line between them. A large green arrow points from the simplified model to the decomposition. The text G.8021-Y.1341(22)_F9-66 is at the bottom right.](130b3107ad97fbf300d3562dab05285b_img.jpg) + +Figure 9-66: Simplified model of Ethernet link aggregation with decomposition of ETH-LAG-Np-Na\_FT function for Na=1. The diagram shows a transformation from a simplified model on the left to a detailed decomposition on the right. On the left, ETH\_TFP and ETH\_FP connect to an ETH-LAG/ETH block, which connects via ETH-LAG\_AP to an ETH-LAG-Np-1 block. This block then connects to two ETH\_TFP outputs, with a dashed line indicating multiple paths. On the right, the decomposition shows ETH\_TFP and ETH\_FP connecting to an ETH-LAG/ETH block, which connects via ETH-LAG\_AP to an ETH-LAG block. This block connects via ETH-LAG\_FP to an ETH-Np/ETH-LAG-1 block. This block then connects to two ETHnull blocks via ETH\_AP[1...Np]. The ETHnull blocks connect to two ETH\_TFP outputs, with a dashed line between them. A large green arrow points from the simplified model to the decomposition. The text G.8021-Y.1341(22)\_F9-66 is at the bottom right. + +**Figure 9-66 – Simplified model of Ethernet link aggregation with decomposition of ETH-LAG-Np-Na\_FT function for Na=1** + +![Figure 9-67: Generic model of Ethernet link aggregation with decomposition of ETH-LAG-Np-Na_FT function. The diagram shows a transformation from a simplified model on the left to a detailed decomposition on the right. On the left, two ETH-LAG/ETH blocks (each connected to ETH_TFP and ETH_FP) connect via ETH-LAG_AP to an ETH-LAG-Np-Na block. This block then connects to two ETH_TFP outputs, with a dashed line indicating multiple paths. On the right, the decomposition shows two parallel paths. Each path starts with an ETH-LAG/ETH block (connected to ETH_TFP and ETH_FP) connecting via ETH-LAG_AP to an ETH-LAG block. These ETH-LAG blocks connect via ETH-LAG_FP[1...Na] to a common ETH-Np/ETH-LAG-Na block. This block then connects to two ETHnull blocks via ETH_AP[1...Np]. The ETHnull blocks connect to two ETH_TFP outputs, with a dashed line between them. A large green arrow points from the simplified model to the decomposition. The text G.8021-Y.1341(22)_F9-67 is at the bottom right.](351243fd59cdae993f191da9ebb48016_img.jpg) + +Figure 9-67: Generic model of Ethernet link aggregation with decomposition of ETH-LAG-Np-Na\_FT function. The diagram shows a transformation from a simplified model on the left to a detailed decomposition on the right. On the left, two ETH-LAG/ETH blocks (each connected to ETH\_TFP and ETH\_FP) connect via ETH-LAG\_AP to an ETH-LAG-Np-Na block. This block then connects to two ETH\_TFP outputs, with a dashed line indicating multiple paths. On the right, the decomposition shows two parallel paths. Each path starts with an ETH-LAG/ETH block (connected to ETH\_TFP and ETH\_FP) connecting via ETH-LAG\_AP to an ETH-LAG block. These ETH-LAG blocks connect via ETH-LAG\_FP[1...Na] to a common ETH-Np/ETH-LAG-Na block. This block then connects to two ETHnull blocks via ETH\_AP[1...Np]. The ETHnull blocks connect to two ETH\_TFP outputs, with a dashed line between them. A large green arrow points from the simplified model to the decomposition. The text G.8021-Y.1341(22)\_F9-67 is at the bottom right. + +**Figure 9-67 – Generic model of Ethernet link aggregation with decomposition of ETH-LAG-Np-Na\_FT function** + +### 9.7.1 ETH link aggregation layer flow termination function (ETH-LAG-Np-Na\_FT) + +The ETH-LAG-Np-Na\_FT function is decomposed as shown in Figures 9-66 and 9-67. The ETHx\_FT function is described in clause 9.2.1. + +NOTE 1 – ETH-LAG-Np-Na\_FT functions always consist of a pair of identically-sized source and sink functions (i.e., a source function with certain values of Na/Np and a sink function with the same Na/Np values), as per [IEEE 802.3]. + +NOTE 2 – In principle, the ETH\_TFP can be connected to any adaptation function that supports an ETH\_TFP. In practice, this will normally be an M-AI/ETH\_A function (see clause 6.1 of [ITU-T G.8023]), representing an [IEEE 802.3] PHY, but this is not strictly required. + +#### 9.7.1.1 ETH link aggregation adaptation source function (ETHx-Np/ETH-LAG-Na\_A\_So) + +The ETHx-Np/ETH-LAG-Na\_A\_So function symbol is shown in Figure 9-68 and the interfaces in Table 9-27. + +##### Symbol + +![Figure 9-68: Symbol for the ETHx-Np/ETH-LAG-Na_A_So function. The symbol is a trapezoid labeled 'ETHx-Np/ETH-LAG-Na'. Above the trapezoid, two arrows labeled 'ETH-LAG_FP' point into it. Below the trapezoid, two arrows labeled 'ETH_AP' point out of it. To the left of the trapezoid, a double-headed arrow labeled 'ETHx-Np/ETH-LAG-Na_A_So_MP' points to it. Below the diagram, the text 'G.8021-Y.1341(22)_F9-68' is present.](5f526e309fba0ac154ebdf14ea1953ab_img.jpg) + +Figure 9-68: Symbol for the ETHx-Np/ETH-LAG-Na\_A\_So function. The symbol is a trapezoid labeled 'ETHx-Np/ETH-LAG-Na'. Above the trapezoid, two arrows labeled 'ETH-LAG\_FP' point into it. Below the trapezoid, two arrows labeled 'ETH\_AP' point out of it. To the left of the trapezoid, a double-headed arrow labeled 'ETHx-Np/ETH-LAG-Na\_A\_So\_MP' points to it. Below the diagram, the text 'G.8021-Y.1341(22)\_F9-68' is present. + +Figure 9-68 – ETHx-Np/ETH-LAG-Na\_A\_So symbol + +##### Interfaces + +Table 9-27 – ETHx-Np/ETH-LAG-Na\_A\_So interfaces + +| Inputs | Outputs | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH-LAG_FP:
ETH-LAG-Na_CI_D =
ETH-LAG_CI[1..Na]_D
ETH-LAG-Na_CI_P =
ETH-LAG_CI[1..Na]_P
ETH-LAG-Na_CI_DE =
ETH-LAG_CI[1..Na]_DE

ETHx-Np/ETH-LAG-Na_A_So_MP:
ETHx-Np/ETH-LAG-Na_A_So_
MI_Agg[1..Na]_AP_List
ETHx-Np/ETH-LAG-Na_A_So_
MI_AggPort[1..Np]_
ActorAdmin_State | ETH_AP:
ETH-Np_AI_D = ETH_AI[1..Np]_D
ETH-Np_AI_P = ETH_AI[1..Np]_P
ETH-Np_AI_DE = ETH_AI[1..Np]_DE

ETHx-Np/ETH-LAG-Na_A_So_MP:
ETHx-Np/ETH-LAG-Na_A_So_
MI_Agg[1..Na]_
[IEEE 802.1AX oAggregator mandatory objects]
ETHx-Np/ETH-LAG-Na_A_So_
MI_AggPort[1..Np]_
[IEEE 802.1AX oAggregationPort mandatory objects]
ETHx-Np/ETH-LAG-Na_A_So_
MI_pAggOctetsTxOK[1..Na]
ETHx-Np/ETH-LAG-Na_A_So_
MI_pAggFramesTxOK[1..Na] | + +NOTE 1 – The signals ETHx-Np/ETH-LAG-Na\_A\_So\_MI\_Agg[1..Na] [IEEE 802.1AX oAggregator mandatory objects] and ETHx-Np/ETH-LAG-Na\_A\_So\_MI\_AggPort[1..Np] [IEEE 802.1AX oAggregationPort mandatory objects] represent the mandatory objects of the "oAggregator" and "oAggregationPort" managed object classes in Table 7-1 of [IEEE 802.1AX]. + +##### Processes + +A process diagram of this function is shown in Figure 9-69. + +![Figure 9-69: ETHx-Np/ETH-LAG-Na_A_So processes diagram. The diagram shows a system with multiple aggregators and access points. At the top, inputs ETH-LAG_CI[1], ETH-LAG_CI[2], ..., ETH-LAG_CI[Na] enter a box containing Aggregator #1, Aggregator #2, ..., Aggregator #Na. On the left, MI_Agg[1...Na]_..., MI_pAggOctetsTxOK[1...Na], and MI_pAggFramesTxOK[1...Na] are shown. Below the aggregators is an Aggregation control box. At the bottom, a box contains Access point #1, Access point #2, ..., Access point #Np. MI_AggPort[1...Np]_... is shown on the left. Below the access points are outputs ETH_AI[1], ETH_AI[2], ..., ETH_AI[Np]. Dashed lines connect the Aggregation control to the access points. Solid lines connect the aggregators to the access points. A reference G.8021-Y.1341(22)_F9-69 is at the bottom right.](f4aaee6522d9ab40472939a4a178e5a3_img.jpg) + +The diagram illustrates the internal structure of the ETHx-Np/ETH-LAG-Na\_A\_So processes. It features a top row of *Na* aggregators (Aggregator #1 to Aggregator #Na) and a bottom row of *Np* access points (Access point #1 to Access point #Np). Inputs *ETH-LAG\_CI[1]* through *ETH-LAG\_CI[Na]* enter the aggregators from above. On the left, management interfaces *MI\_Agg[1...Na]\_...*, *MI\_pAggOctetsTxOK[1...Na]*, and *MI\_pAggFramesTxOK[1...Na]* are associated with the aggregators. An *Aggregation control* block is positioned to the left of the aggregators. Below the aggregators, a row of access points is shown. Management interface *MI\_AggPort[1...Np]\_...* is associated with these access points. Outputs *ETH\_AI[1]*, *ETH\_AI[2]*, and *ETH\_AI[Np]* exit the access points from below. Dashed lines indicate control signals from the *Aggregation control* to each access point. Solid lines represent data paths from each aggregator to each access point. A reference label *G.8021-Y.1341(22)\_F9-69* is located in the bottom right corner. + +Figure 9-69: ETHx-Np/ETH-LAG-Na\_A\_So processes diagram. The diagram shows a system with multiple aggregators and access points. At the top, inputs ETH-LAG\_CI[1], ETH-LAG\_CI[2], ..., ETH-LAG\_CI[Na] enter a box containing Aggregator #1, Aggregator #2, ..., Aggregator #Na. On the left, MI\_Agg[1...Na]\_..., MI\_pAggOctetsTxOK[1...Na], and MI\_pAggFramesTxOK[1...Na] are shown. Below the aggregators is an Aggregation control box. At the bottom, a box contains Access point #1, Access point #2, ..., Access point #Np. MI\_AggPort[1...Np]\_... is shown on the left. Below the access points are outputs ETH\_AI[1], ETH\_AI[2], ..., ETH\_AI[Np]. Dashed lines connect the Aggregation control to the access points. Solid lines connect the aggregators to the access points. A reference G.8021-Y.1341(22)\_F9-69 is at the bottom right. + +Figure 9-69 – ETHx-Np/ETH-LAG-Na\_A\_So processes + +The input *MI\_Agg[1..Na]\_AP\_List* defines for each aggregator, which ports (access points) are provisioned to be assigned to it. The *AP\_List* attributes for all aggregators are disjunct lists. + +The system shall assign a unique value for the parameter *aAggActorAdminKey* for each aggregator in the system. The system shall also assign the value used for each aggregator to the parameter *aAggPortActorAdminKey* of all ports in its assigned port list (*AP\_List*). + +NOTE 2 – This automated *AdminKey* assignment is a simplification of the IEEE provisioning model where the keys are provisioned explicitly for each port and aggregator. + +##### Access point + +This represents the individual LAG member within the process diagram, including the source part of the control parser/multiplexer process as specified in [IEEE 802.1AX]. The MAC layer processes that are specific to a member are performed by the function that is attached to the *ETH\_AP* for that member. + +NOTE 3 – The control parser/multiplexer process is a single process shared between the source and the sink of a pair of source/sink adaptation functions. + +##### Aggregation control + +This process is the source part of the process of the same name in [IEEE 802.1AX]. + +NOTE 4 – The aggregation control process is a single process shared between the source and the sink of a pair of source/sink adaptation functions. + +NOTE 5 – As per the IEEE model and given the automated key assignment, only ports from each aggregator's *AP\_List* will be eligible to be selected by that aggregator. + +##### Aggregator + +This process is the source part of the process of the same name in [IEEE 802.1AX]. A coupled mux state machine model is used. + +NOTE 6 – Each "Aggregator #k" process is a single process shared between the source and the sink of a pair of source/sink adaptation functions. + +**Defects** None. + +**Consequent actions** None. + +**Defect correlations** None. + +##### Performance monitoring + +For each aggregator: + +MI\_pAggOctetsTxOK[1..Na] as per clause 7 of [IEEE 802.1AX]. + +MI\_pAggFramesTxOK[1..Na] as per clause 7 of [IEEE 802.1AX]. + +#### 9.7.1.2 ETH link aggregation adaptation sink function (ETHx-Np/ETH-LAG-Na\_A\_Sk) + +The ETHx-Np/ETH-LAG-Na\_A\_Sk function symbol is shown in Figure 9-70, the interfaces in Table 9-28 and the process diagram in Figure 9-71. + +##### Symbol + +![Figure 9-70 – ETHx-Np/ETH-LAG-Na_A_Sk symbol. The diagram shows a trapezoidal function symbol labeled 'ETHx-Np/ETH-LAG-Na'. It has two input interfaces on the left labeled 'ETH_AP' and one output interface on the right labeled 'ETHx-Np/ETH-LAG-Na_A_Sk_MP'. Above the symbol, there are two output interfaces labeled 'ETH-LAG_FP'.](a698d00b1c1bfed70ad423236a2a7d9f_img.jpg) + +G.8021-Y.1341(22)\_F9-70 + +Figure 9-70 – ETHx-Np/ETH-LAG-Na\_A\_Sk symbol. The diagram shows a trapezoidal function symbol labeled 'ETHx-Np/ETH-LAG-Na'. It has two input interfaces on the left labeled 'ETH\_AP' and one output interface on the right labeled 'ETHx-Np/ETH-LAG-Na\_A\_Sk\_MP'. Above the symbol, there are two output interfaces labeled 'ETH-LAG\_FP'. + +Figure 9-70 – ETHx-Np/ETH-LAG-Na\_A\_Sk symbol + +##### Interfaces + +Table 9-28 – ETHx-Np/ETH-LAG-Na\_A\_Sk interfaces + +| Inputs | Outputs | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_AP:
ETH-Np_AI_D=
ETH_AI[1..Np]_D
ETH-Np_AI_P=
ETH_AI[1..Np]_P
ETH-Np_AI_DE=
ETH_AI[1..Np]_DE

ETHx-Np/ETH-LAG-Na_A_Sk_MP:
ETHx-Np/ETH-LAG-Na_A_Sk_
MI_PLLThr[1..Na] | ETH-LAG_FP:
ETH-LAG-Na_CI_D=
ETH-LAG_CI[1..Na]_D
ETH-LAG-Na_CI_P=
ETH-LAG_CI[1..Na]_P
ETH-LAG-Na_CI_DE=
ETH-LAG_CI[1..Na]_DE
ETH-LAG-Na_CI_aSSF=
ETH-LAG_CI[1..Na]_aSSF

ETHx-Np/ETH-LAG-Na_A_Sk_MP:
ETHx-Np/ETH-LAG-Na_A_Sk_
MI_cPLL[1..Na]
ETHx-Np/ETH-LAG-Na_A_Sk_
MI_cTLL[1..Na]
ETHx-Np/ETH-LAG-Na_A_Sk_
MI_pAggOctetsRxOK[1..Na]
ETHx-Np/ETH-LAG-Na_A_Sk_
MI_pAggFramesRxOK[1..Na] | + +##### Processes + +![Figure 9-71 – ETHx-Np/ETH-LAG-Na_A_Sk process diagram. The diagram shows a hierarchical process structure. At the top, external interfaces ETH-LAG_CI[1], ETH-LAG_CI[2], ..., ETH-LAG_CI[Na] point to a row of 'Aggregator' blocks (Aggregator #1, Aggregator #2, ..., Aggregator #Na). On the left, a list of parameters (MI_cPLL[1..Na], MI_cTLL[1..Na], MI_PLLThr[1..Na], MI_pAggOctetsRxOK[1..Na], MI_pAggFramesRxOK[1..Na]) points to an 'Aggregation control' block. The 'Aggregation control' block has bidirectional connections to each 'Aggregator' block. Below the aggregators is a row of 'Access point' blocks (Access point #1, Access point #2, ..., Access point #Np). Each 'Access point' block has a bidirectional connection to its corresponding 'Aggregator' block and an external interface ETH_AI[i] (ETH_AI[1], ETH_AI[2], ..., ETH_AI[Np]). Dashed lines connect the 'Aggregation control' block to each 'Access point' block. A reference code G.8021-Y.1341(22)_F9-71 is in the bottom right corner.](021490adcafe4e26498ead48f8eb09fe_img.jpg) + +Figure 9-71 – ETHx-Np/ETH-LAG-Na\_A\_Sk process diagram. The diagram shows a hierarchical process structure. At the top, external interfaces ETH-LAG\_CI[1], ETH-LAG\_CI[2], ..., ETH-LAG\_CI[Na] point to a row of 'Aggregator' blocks (Aggregator #1, Aggregator #2, ..., Aggregator #Na). On the left, a list of parameters (MI\_cPLL[1..Na], MI\_cTLL[1..Na], MI\_PLLThr[1..Na], MI\_pAggOctetsRxOK[1..Na], MI\_pAggFramesRxOK[1..Na]) points to an 'Aggregation control' block. The 'Aggregation control' block has bidirectional connections to each 'Aggregator' block. Below the aggregators is a row of 'Access point' blocks (Access point #1, Access point #2, ..., Access point #Np). Each 'Access point' block has a bidirectional connection to its corresponding 'Aggregator' block and an external interface ETH\_AI[i] (ETH\_AI[1], ETH\_AI[2], ..., ETH\_AI[Np]). Dashed lines connect the 'Aggregation control' block to each 'Access point' block. A reference code G.8021-Y.1341(22)\_F9-71 is in the bottom right corner. + +**Figure 9-71 – ETHx-Np/ETH-LAG-Na\_A\_Sk process** + +##### Access point + +This represents the individual LAG member within the process diagram, including the sink part of the control parser/multiplexer process as specified in [IEEE 802.1AX]. The MAC layer processes that are specific to a member are performed by the function that is attached to the ETH\_AP for that member. + +NOTE 1 – The control parser/multiplexer process is a single process shared between the source and the sink of a pair of source/sink adaptation functions. + +##### Aggregation control + +This process is the sink part of the process of the same name in [IEEE 802.1AX]. + +NOTE 2 – The aggregation control process is a single process shared between the source and the sink of a pair of source/sink adaptation functions. The parameters used by this bidirectional process are defined in the interface section of the source adaptation function. + +###### Aggregator + +This process is the sink part of the process of the same name in [IEEE 802.1AX]. A coupled mux state machine model is used. + +NOTE 3 – Each "Aggregator #k" process is a single process shared between the source and the sink of a pair of source/sink adaptation functions. The parameters used by this bidirectional process are defined in the interface section of the source adaptation function. + +##### Defects + +dMNCD[j] (Member j not Collecting/Distributing): The defect shall be raised if an access point (port) in an aggregator's AP\_List stays outside of the COLLECTING\_DISTRIBUTING state for longer than $X_{\text{raise}}$ seconds. The defect shall be cleared if the port enters the COLLECTING\_DISTRIBUTING state and stays there for $X_{\text{clear}}$ seconds. + +$$X_{\text{raise}} = X_{\text{clear}} = 1 \text{ second.}$$ + +##### Consequent actions + +$$\text{ETH - LAG\_CI}[k]\_\text{aSSF} \leftarrow \prod_{j \in \text{MI\_AP\_List}[k]} \text{dMNCD}[j]$$ + +NOTE 4 – In other words, aSSF will be raised at the output ETH-LAG\_CI[k] of an aggregator if all ports in its assigned port list (AP\_List[k]) have the dMNCD defect active. + +##### Defect correlations + +Defining + +$$\text{mAP\_Active}[k] = \sum_{j \in \text{MI\_AP\_List}[k]} (\text{not dMNCD}[j])$$ + +i.e., the number of active (no-defect) ports among those in an aggregator's AP\_List, then: + +$$\text{ETH - LAG\_cTLL}[k] \leftarrow \text{mAP\_Active}[k] = 0$$ + +$$\text{ETH - LAG\_cPLL}[k] \leftarrow (0 < \text{mAP\_Active}[k]) \text{ and } (\text{mAP\_Active}[k] < \text{MI\_PLLThr}[k])$$ + +NOTE 5 – In other words, a cTLL (total link loss) fault cause will be raised if no ports are active for an aggregator. A cPLL (partial link loss) fault cause shall be raised if the number of active ports is less than the provisioned threshold. + +##### Performance monitoring + +For each aggregator: + +MI\_pAggOctetsRxOK[1..Na] as per clause 7 of [IEEE 802.1AX]. + +MI\_pAggFramesRxOK[1..Na] as per clause 7 of [IEEE 802.1AX]. + +#### 9.7.1.3 ETH link aggregation flow termination source function (ETH-LAG\_FT\_So) + +The ETH-LAG\_FT\_So function symbol is shown in Figure 9-72 and the interfaces in Table 9-29. + +##### Symbol + +![Figure 9-72 – ETH-LAG_FT_So symbol. The diagram shows a function symbol represented by an inverted triangle. Above the triangle is the input interface 'ETH-LAG_AP' with a downward arrow pointing to the top of the triangle. Inside the triangle is the label 'ETH-LAG'. Below the triangle is the output interface 'ETH-LAG_TFP' with a downward arrow pointing from the bottom of the triangle. At the very bottom, below the output interface, is the text 'G.8021-Y.1341(22)_F9-72'.](247968526c133d4def1d715318b99af1_img.jpg) + +Figure 9-72 – ETH-LAG\_FT\_So symbol. The diagram shows a function symbol represented by an inverted triangle. Above the triangle is the input interface 'ETH-LAG\_AP' with a downward arrow pointing to the top of the triangle. Inside the triangle is the label 'ETH-LAG'. Below the triangle is the output interface 'ETH-LAG\_TFP' with a downward arrow pointing from the bottom of the triangle. At the very bottom, below the output interface, is the text 'G.8021-Y.1341(22)\_F9-72'. + +Figure 9-72 – ETH-LAG\_FT\_So symbol + +##### Interfaces + +Table 9-29 – ETH-LAG\_FT\_So interfaces + +| Inputs | Outputs | +|---------------------------------------------------------------------|----------------------------------------------------------------------| +| ETH-LAG_AP:
ETH-LAG_AI_D
ETH-LAG_AI_P
ETH-LAG_AI_DE | ETH-LAG_TFP:
ETH-LAG_CI_D
ETH-LAG_CI_P
ETH-LAG_CI_DE | + +##### Processes + +This function just forwards the ETH-LAG\_AP information onto the ETH-LAG\_FP without manipulation. + +**Defects** None. + +**Consequent actions** None. + +**Defect correlations** None. + +**Performance monitoring** None. + +#### 9.7.1.4 ETH link aggregation flow termination sink function (ETH-LAG\_FT\_Sk) + +The ETH-LAG\_FT\_Sk function symbol is shown in Figure 9-73 and the interfaces in Table 9-30. + +##### Symbol + +![Figure 9-73 – ETH-LAG_FT_Sk symbol. The diagram shows a function symbol represented by an inverted triangle labeled 'ETH-LAG'. Above the triangle, an arrow points up to the label 'ETH-LAG_AP'. Below the triangle, an arrow points up from the label 'ETH-LAG_TFP'. To the right of the triangle, an arrow points left to the label 'ETH-LAG_FT_Sk_MP'. A small text label 'G.8021-Y.1341(22)_F9-73' is located to the right of the bottom input label.](0b775e8787c8d1c5018bf5ce227b3f76_img.jpg) + +Figure 9-73 – ETH-LAG\_FT\_Sk symbol. The diagram shows a function symbol represented by an inverted triangle labeled 'ETH-LAG'. Above the triangle, an arrow points up to the label 'ETH-LAG\_AP'. Below the triangle, an arrow points up from the label 'ETH-LAG\_TFP'. To the right of the triangle, an arrow points left to the label 'ETH-LAG\_FT\_Sk\_MP'. A small text label 'G.8021-Y.1341(22)\_F9-73' is located to the right of the bottom input label. + +**Figure 9-73 – ETH-LAG\_FT\_Sk symbol** + +##### Interfaces + +**Table 9-30 – ETH-LAG\_FT\_Sk interfaces** + +| Inputs | Outputs | +|---------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH-LAG_TFP:
ETH-LAG_CI_D
ETH-LAG_CI_P
ETH-LAG_CI_DE
ETH-LAG_CI_SSF

ETH-LAG_FT_Sk_MP:
ETH-LAG_FT_Sk_MI_SSF_Reported | ETH-LAG_AP:
ETH-LAG_AI_D
ETH-LAG_AI_P
ETH-LAG_AI_DE
ETH-LAG_AI_TSF
ETH-LAG_AI_AIS

ETH-LAG_FT_Sk_MP:
ETH-LAG_FT_Sk_MI_cSSF | + +##### Processes + +This function forwards the ETH-LAG\_FP information onto the ETH-LAG\_AP without manipulation. + +**Defects:** None. + +**Consequent actions** aTSF ← CI\_SSF + +**Defect correlations** cSSF ← CI\_SSF and SSF\_Reported + +**Performance monitoring** None. + +### 9.7.2 ETH-LAG to ETH adaptation function (ETH-LAG/ETH\_A) + +#### 9.7.2.1 ETH-LAG to ETH adaptation source function (ETH-LAG/ETH\_A\_So) + +The ETH-LAG/ETH\_A\_So function symbol is shown in Figure 9-74, the interfaces in Table 9-31 and the process diagram in Figure 9-75. + +##### Symbol + +![Figure 9-74: Symbol for ETH-LAG/ETH_A_So. It shows a trapezoidal block labeled 'ETH-LAG/ETH'. Two input arrows, 'ETH_TFP' and 'ETH_FP', enter from the top. Three output arrows exit from the right and bottom: 'ETH_TF_PP' and 'ETHF_PP' exit from the right side, and 'ETH-LAG_AP' exits from the bottom. A small label 'G.8021-Y.1341(22)_F9-74' is at the bottom right.](c139aa372176ff96d02d462be232c810_img.jpg) + +Figure 9-74: Symbol for ETH-LAG/ETH\_A\_So. It shows a trapezoidal block labeled 'ETH-LAG/ETH'. Two input arrows, 'ETH\_TFP' and 'ETH\_FP', enter from the top. Three output arrows exit from the right and bottom: 'ETH\_TF\_PP' and 'ETHF\_PP' exit from the right side, and 'ETH-LAG\_AP' exits from the bottom. A small label 'G.8021-Y.1341(22)\_F9-74' is at the bottom right. + +Figure 9-74 – ETH-LAG/ETH\_A\_So symbol + +##### Interfaces + +Table 9-31 – ETH-LAG/ETH\_A\_So interfaces + +| Inputs | Outputs | +|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE

ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE | ETH-LAG_AP:
ETH-LAG_AI_D
ETH-LAG_AI_P
ETH-LAG_AI_DE

ETH_TF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ETHF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE | + +##### Processes + +![Figure 9-75: Process diagram for ETH-LAG/ETH_A_So. It shows a grey rectangular box containing two sub-processes: 'Queueing' and 'Replicate'. An input 'ETH_CI (ETH_FP)' enters the 'Queueing' block. An input 'ETH_CI (ETH_TFP)' enters the 'Replicate' block. The 'Queueing' block has an output arrow pointing to the 'Replicate' block. The 'Replicate' block has two output arrows pointing to 'ETH_PI (ETH_TF_PP)' and 'ETH_PI (ETHF_PP)'. A single output arrow labeled 'ETH-LAG_AI' exits from the bottom of the grey box. A small label 'G.8021-Y.1341(22)_F9-75' is at the bottom right.](3baef64ba57070d61b536cf90c6fcda5_img.jpg) + +Figure 9-75: Process diagram for ETH-LAG/ETH\_A\_So. It shows a grey rectangular box containing two sub-processes: 'Queueing' and 'Replicate'. An input 'ETH\_CI (ETH\_FP)' enters the 'Queueing' block. An input 'ETH\_CI (ETH\_TFP)' enters the 'Replicate' block. The 'Queueing' block has an output arrow pointing to the 'Replicate' block. The 'Replicate' block has two output arrows pointing to 'ETH\_PI (ETH\_TF\_PP)' and 'ETH\_PI (ETHF\_PP)'. A single output arrow labeled 'ETH-LAG\_AI' exits from the bottom of the grey box. A small label 'G.8021-Y.1341(22)\_F9-75' is at the bottom right. + +Figure 9-75 – ETH-LAG/ETH\_A\_So process + +See "Queueing" in clause 8.2 and "Replicate" in clause 8.4. + +**Defects** None. + +**Consequent actions** None. + +**Defect correlations** None. + +**Performance monitoring** None. + +#### **9.7.2.2 ETH-LAG to ETH adaptation sink function (ETH-LAG/ETH\_A\_Sk)** + +The ETH-LAG/ETH\_A\_Sk function symbol is shown in Figure 9-76, the interfaces in Table 9-32 and a process in Figure 9-77. + +##### **Symbol** + +![Diagram of the ETH-LAG/ETH_A_Sk function symbol. It is a trapezoidal block labeled 'ETH-LAG/ETH'. Inputs include ETH_TFP and ETH_FP pointing out from the top, ETH_LAG_AP pointing in from the bottom, ETH_LAG/ETH_A_Sk_MP pointing in from the right, and ETHF_PP and ETHTF_PP pointing in from the left. A small note G.8021-Y.1341(22)_F9-76 is present at the bottom right.](f86fbc9826e1910a39e36f7e62b568c2_img.jpg) + +Diagram of the ETH-LAG/ETH\_A\_Sk function symbol. It is a trapezoidal block labeled 'ETH-LAG/ETH'. Inputs include ETH\_TFP and ETH\_FP pointing out from the top, ETH\_LAG\_AP pointing in from the bottom, ETH\_LAG/ETH\_A\_Sk\_MP pointing in from the right, and ETHF\_PP and ETHTF\_PP pointing in from the left. A small note G.8021-Y.1341(22)\_F9-76 is present at the bottom right. + +**Figure 9-76 – ETH-LAG/ETH\_A\_Sk symbol** + +##### **Interfaces** + +**Table 9-32 – ETH-LAG/ETH\_A\_Sk interfaces** + +| Inputs | Outputs | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| ETH-LAG_AP:
ETH-LAG_AI_D
ETH-LAG_AI_P
ETH-LAG_AI_DE
ETH-LAG-AI_TSF
ETH-LAG-AI_AIS

ETHTF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ETHF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ETH-LAG/ETH_A_Sk_MP:
ETH-LAG/ETH_A_Sk_MI_FilterConfig | ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF

ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF | + +##### Processes + +![Diagram of the ETH-LAG/ETH_A_Sk process. A central 'Replicate' block receives two inputs from the left: 'ETH_PI (ETH_TF_PP)' and 'ETH_PI (ETHF_PP)'. It also receives an input from the bottom: 'ETH-LAG_AI'. The 'Replicate' block has two outputs: one pointing to a 'Filter' block and another pointing to an output labeled 'ETH_CI (ETH_TFP)'. The 'Filter' block receives a configuration input 'MI_FilterConfig' from the right and produces an output labeled 'ETH_CI (ETH_FP)'.](4a70ffcf0c8f841b46b9bb6997a248fe_img.jpg) + +Diagram of the ETH-LAG/ETH\_A\_Sk process. A central 'Replicate' block receives two inputs from the left: 'ETH\_PI (ETH\_TF\_PP)' and 'ETH\_PI (ETHF\_PP)'. It also receives an input from the bottom: 'ETH-LAG\_AI'. The 'Replicate' block has two outputs: one pointing to a 'Filter' block and another pointing to an output labeled 'ETH\_CI (ETH\_TFP)'. The 'Filter' block receives a configuration input 'MI\_FilterConfig' from the right and produces an output labeled 'ETH\_CI (ETH\_FP)'. + +Figure 9-77 – ETH-LAG/ETH\_A\_Sk process + +See "Filter" in clause 8.3 and "Replicate" in clause 8.4. + +**Defects** None. + +**Consequent actions** None. + +**Defect correlations** None. + +**Performance monitoring** None. + +## 9.8 ETH MEP and MIP functions + +MEP and MIP compound functions are defined in [ITU-T G.806]. This clause specifies the composition of those functions with ETH flow termination, adaptation and diagnostic atomic functions described in clauses 9.2, 9.3 and 9.4, respectively. + +### 9.8.1 ETH NCM MEP function + +An ETH NCM (network connection monitoring) MEP function is capable of originating, filtering and terminating proactive ETH OAM signals and originating, responding to and terminating diagnostic ETH OAM signals at one of the NCM MEG levels. An NCM MEP is composed of ETHx\_FT, ETHD/ETH\_A and ETHDe\_FT atomic functions. This MEP is located at the ETH (sub)layer boundary and connected with ETHx/client\_A or ETHx/ETH-m\_A. Figure 9-78 shows the ETH NCM MEP compound functions. + +![Diagram illustrating the composition of ETH NCM MEP compound functions. On the left, a simple triangle symbol represents the overall function. An arrow points to the right, where a larger triangle is shown, subdivided into three horizontal layers. The top layer is labeled 'ETHx', the middle layer is 'ETHD/ETH', and the bottom layer is 'ETHDe'. Each layer has a small circle at its top and bottom boundary.](324758ffe8893d5c551bf7eb1c0e9ca9_img.jpg) + +Diagram illustrating the composition of ETH NCM MEP compound functions. On the left, a simple triangle symbol represents the overall function. An arrow points to the right, where a larger triangle is shown, subdivided into three horizontal layers. The top layer is labeled 'ETHx', the middle layer is 'ETHD/ETH', and the bottom layer is 'ETHDe'. Each layer has a small circle at its top and bottom boundary. + +Figure 9-78 – ETH NCM MEP compound functions + +### 9.8.2 ETH TCM MEP function + +An ETH TCM (tandem connection monitoring) MEP function is capable of originating, filtering and terminating proactive ETH OAM signals and originating, responding to and terminating diagnostic ETH OAM signals at one of the TCM MEG levels. A TCM MEP is composed of ETHx/ETH\_A, ETHx\_FT, ETHD/ETH\_A and ETHDe\_FT atomic functions. In addition, it can be composed of ETHG/ETH\_A, ETHG\_FT, ETHD/ETH\_A and ETDe\_FT if ETH group MEG is configured and multiple access point pools (APP) are accommodated. This MEP is located within an ETH (sub)layer. Figure 9-79 shows the ETH TCM MEP compound functions. + +![Diagram illustrating the ETH TCM MEP compound functions. The top part shows a single input (one circle) entering a trapezoidal block, which is then shown as a nested structure of four layers: ETHx/ETH, ETHx, ETHD/ETH, and ETHDe. The bottom part shows three inputs (three circles) entering a trapezoidal block, which is then shown as a nested structure of four layers: ETHG/ETH, ETHG, ETHD/ETH, and ETDe. The diagram is labeled G.8021-Y.1341(22)_F9-79.](35d5c5a5774a7997f06756915721031b_img.jpg) + +The diagram illustrates two configurations of the ETH TCM MEP compound functions. The top configuration shows a single input (represented by a circle) entering a trapezoidal block. This block is expanded into a nested structure of four layers: ETHx/ETH (top), ETHx, ETHD/ETH, and ETHDe (bottom). The bottom configuration shows three inputs (represented by three circles) entering a trapezoidal block. This block is expanded into a nested structure of four layers: ETHG/ETH (top), ETHG, ETHD/ETH, and ETDe (bottom). The diagram is labeled G.8021-Y.1341(22)\_F9-79. + +Diagram illustrating the ETH TCM MEP compound functions. The top part shows a single input (one circle) entering a trapezoidal block, which is then shown as a nested structure of four layers: ETHx/ETH, ETHx, ETHD/ETH, and ETHDe. The bottom part shows three inputs (three circles) entering a trapezoidal block, which is then shown as a nested structure of four layers: ETHG/ETH, ETHG, ETHD/ETH, and ETDe. The diagram is labeled G.8021-Y.1341(22)\_F9-79. + +Figure 9-79 – ETH TCM MEP compound functions + +### 9.8.3 ETH MIP function + +An ETH MIP function is capable of responding to on-demand ETH OAM signals at one of the MEG levels in both directions. The MIP combines two back-to-back half-MIP functions. It consists of two pairs of ETHD/ETH\_A and ETHDi\_FT atomic functions, each facing opposite directions. Figure 9-80 shows the ETH MIP compound functions. + +![Diagram of Figure 9-80: ETH MIP compound functions. On the left, a diamond-shaped symbol with four small circles at its vertices represents a full MIP function. An arrow points to the right, where a detailed view shows the internal structure: a large triangle containing four stacked rectangular blocks. From top to bottom, they are labeled 'ETHDi', 'ETHD/ETH', 'ETHD/ETH', and 'ETHDi'. Below the diagram is the text 'G.8021-Y.1341(22)_F9-80'.](a279b24bee8e82a60177168f08cce415_img.jpg) + +Diagram of Figure 9-80: ETH MIP compound functions. On the left, a diamond-shaped symbol with four small circles at its vertices represents a full MIP function. An arrow points to the right, where a detailed view shows the internal structure: a large triangle containing four stacked rectangular blocks. From top to bottom, they are labeled 'ETHDi', 'ETHD/ETH', 'ETHD/ETH', and 'ETHDi'. Below the diagram is the text 'G.8021-Y.1341(22)\_F9-80'. + +**Figure 9-80 – ETH MIP compound functions** + +### 9.8.4 ETH half MIP function + +An ETH half MIP function is capable of responding to on-demand ETH OAM signals at one of the MEG levels in a single direction. The half MIP is composed of a pair of ETHD/ETH\_A and ETHDi\_FT atomic functions. Figure 9-81 shows the ETH MIP compound functions. + +![Diagram of Figure 9-81: ETH MIP compound functions. On the left, a triangle-shaped symbol with two small circles at its top vertices represents a half MIP function. An arrow points to the right, where a detailed view shows the internal structure: a large triangle containing two stacked rectangular blocks. The top block is labeled 'ETHD/ETH' and the bottom block is labeled 'ETHDi'. Below the diagram is the text 'G.8021-Y.1341(22)_F9-81'.](24fb4322a331cba19f7f0b0084bc264c_img.jpg) + +Diagram of Figure 9-81: ETH MIP compound functions. On the left, a triangle-shaped symbol with two small circles at its top vertices represents a half MIP function. An arrow points to the right, where a detailed view shows the internal structure: a large triangle containing two stacked rectangular blocks. The top block is labeled 'ETHD/ETH' and the bottom block is labeled 'ETHDi'. Below the diagram is the text 'G.8021-Y.1341(22)\_F9-81'. + +**Figure 9-81 – ETH MIP compound functions** + +# 10 Ethernet server to ETH adaptation functions + +[ITU-T G.8023] defines the atomic functions for the Ethernet physical layer, as defined in [IEEE 802.3], and for the Flex Ethernet interfaces, as defined in [OIF FLEXE IA]. + +NOTE – The atomic functions defined in clause 10 of [b-ITU-T G.8021-2016] and older versions of this Recommendation have been superseded by the atomic functions defined in [ITU-T G.8023]. See Appendix X for some mapping guidelines between the atomic functions defined in clause 10 of [b-ITU-T G.8021-2016] and the new atomic functions defined in [ITU-T G.8023]. + +The M-AI/ETH\_A functions, defined in clause 6.1 of [ITU-T G.8023], provide the adaptation between the ETH layer network and the Ethernet physical layer defined in [IEEE 802.3]. + +The FlexEC/ETH\_A functions, defined in clause 8.2 of [ITU-T G.8023], provide the adaptation between the ETH layer network and the FlexE client interfaces defined in [OIF FLEXE IA]. + +# 11 Non-Ethernet server to ETH adaptation functions + +NOTE – Earlier editions of this Recommendation included adaptation functions related to synchronous digital hierarchy (SDH) and plesiochronous digital hierarchy (PDH) server layers. Equipment designed to those editions may still be used in some networks. + +## **11.1 OTN to ETH adaptation functions** + +### **11.1.1 ODUk to ETH adaptation functions (ODUkP/ETH\_A)** + +The ODUkP to Ethernet adaptation function supporting GFP-F mapping of Ethernet over ODUk is given in clause 14.3.11 of [ITU-T G.798]. + +### **11.1.2 ODU2P to Ethernet Reconciliation sublayer adaptation functions** + +The ODU2P to Ethernet Reconciliation sublayer adaptation function for supporting the transport of the preamble and ordered set information of the 10GBASE-R signals over extended OPU2 payload area is given in clause 14.3.3 of [ITU-T G.798]. + +### **11.1.3 ODU0P to 1 GbE client adaptation functions (ODU0P/CBRx\_A)** + +The adaptation function that supports the transport of 1GbE signals in the OTN is the ODU0P to the client adaptation function (ODU0P/CBRx\_A) ( $0 \leq x \leq 1.25G$ ) described in [ITU-T G.798]. When the client is 1 GbE, the CBRx and ETC1000X signals are equivalent. + +# Appendix I + +## Applications and functional diagrams + +(This appendix does not form an integral part of this Recommendation.) + +Figure I.1 presents the set of atomic functions associated with the Ethernet signal transport, shown in several example applications. + +- Ethernet UNI/NNI interface port on Ethernet over Transport equipment. +- Ethernet UNI interface port supporting multiplexed access on Ethernet over Transport equipment. + +![Functional diagram of Ethernet atomic functions in several possible applications.](66ba5db5f1629ba9048f8e850b576654_img.jpg) + +The diagram illustrates the functional layers for Ethernet transport across four different application scenarios. At the top, client data flows are shown entering the system. The first scenario shows a single client flow passing through an **ETH/** function, then an **ETH\_FT** function, and finally an **ETH\_TFP** function into the **Ethernet flow domain (ETH\_FD)**. The second and third scenarios show multiple client flows being multiplexed into a single **ETH\_FT** function before entering the **ETH\_FD**. The fourth scenario shows a client flow entering the **ETH\_FD** directly. Below the **ETH\_FD**, the data flows are processed by **/ETH\_A** functions, which are part of **Ethernet servers OTN servers**. These are followed by **\_TT** functions and then **ETH\_FFP Link** functions. The diagram uses various labels to identify the data flows, such as **\_CI** (client PDUs), **ETH\_AI** (MAC SDU flow), **ETH\_FT\_MI**, **ETH\_CI** (DA/SA/MSDU flow), and **ETH\_TFP**. A legend on the right identifies the clients as using Bridge protocol and Internet protocol. The reference G.8021-Y1341(18) Fl.1 is noted at the bottom right. + +Functional diagram of Ethernet atomic functions in several possible applications. + +G.8021-Y1341(18) Fl.1 + +Figure I.1 – Ethernet atomic functions in several possible applications + +# Appendix II + +## AIS/RDI mechanism for an Ethernet private line over a single OTN server layer + +(This appendix does not form an integral part of this Recommendation.) + +In order to address fault notification for failures in either the access links or within the OTN server layer when GFP-F mapping is used to provide a private line service, the following functionality is required: + +- a) Convey fault notification for an access link failure from one side of the network to the other. +- b) Convey fault notification for an OTN server layer failure to the access links. + +[ITU-T G.704] defines client management frames (CMFs) for conveying information about the client signal from an ingress edge NE to the egress edge NE. Defined CMF signals are client signal fail (CSF), client forward defect indication (FDI) and client reverse defect indication (RDI) implementing the remote fail indication mechanism. + +[ITU-T G.806] defines the equipment functional details of the CSF and RFI mechanisms. + +This Recommendation defines the Ethernet specific equipment functional details for the CSF and RFI mechanisms. + +The combination of the above three Recommendations provides the functionality required by (a) and (b). + +In addition, this basic functionality can be further enhanced to support fault notification for the Ethernet client by using Ethernet physical layer defect signals shown in Appendix VI of [ITU-T G.704] by means of Ethernet OAM. For example, use of the link fault flag defined in clause 57 of [IEEE 802.3] (EFM OAM), in conjunction with the GFP-F CMF CSF and RFI indications. This is illustrated below. + +A simplifying assumption can be made regarding the conditioning of the Ethernet access links on either side of the OTN transport network. For an EPL application, the access link is specific to a single service and since an Ethernet service is bidirectional, a fault in either direction should result in the access link being conditioned as "failed". + +The following fault scenarios and accompanying figures illustrate this example of interworking of the EFM OAM link fault flag with the GFP-F CMF CSF and RFI indications to appropriately condition the Ethernet access links. Only unidirectional faults are considered, the scenarios can be combined as per the superposition principle to describe bidirectional faults. Furthermore, only an OTN server layer is shown in the examples. CE = Customer edge. PE = Provider edge. + +### Scenario 1 + +In Figure II.1, a unidirectional fault occurs on the east access link on ingress to the carrier network. + +![Diagram of a network architecture showing a fault on the ingress link. The diagram illustrates three layers: MAC layer (ETH layer), PHY layer, and the Ethernet transport network. A fault occurs on the ingress link between the east PE and the east CE. The east PE detects the loss of signal and sends 'Link fault' upstream. The east CE detects the 'Link fault' and sends Idles towards the network. The west PE detects the GFP-F CMF CSF indication and shuts down the laser. The west CE detects the loss of signal and sends 'Link fault' upstream. The diagram also shows the EPL service, MAC frame visibility, CMF_CSF, GFP-F connection, 802.3 PHY, and OTN path.](f803be090d37a5189dbc87c1c87b6c63_img.jpg) + +The diagram illustrates a network architecture with the following components and layers: + +- EPL service:** Represented by a double-headed arrow at the top. +- Ethernet transport network:** A central cloud representing the network. +- CE (Customer Edge):** Two CE units, one on the left (west) and one on the right (east). +- PE (Provider Edge):** Two PE units, one on the left (west) and one on the right (east), connected to the network cloud. +- MAC layer (ETH layer):** Shows 'Link fault' signals (red arrows) and 'MAC frame visibility' (purple triangles) at the east PE and east CE. +- PHY layer:** Shows '802.3 PHY' connections, a 'Laser shutdown' (indicated by a crossed-out laser symbol at the west PE), 'CMF\_CSF' (blue arrow), 'GFP-F connection' (green arrow), and 'OTN path' (black arrow). +- Fault Location:** A fault is indicated by a red starburst on the ingress link between the east PE and the east CE. +- Reference:** G.8021-Y.1341(12)\_FII-1 + +Diagram of a network architecture showing a fault on the ingress link. The diagram illustrates three layers: MAC layer (ETH layer), PHY layer, and the Ethernet transport network. A fault occurs on the ingress link between the east PE and the east CE. The east PE detects the loss of signal and sends 'Link fault' upstream. The east CE detects the 'Link fault' and sends Idles towards the network. The west PE detects the GFP-F CMF CSF indication and shuts down the laser. The west CE detects the loss of signal and sends 'Link fault' upstream. The diagram also shows the EPL service, MAC frame visibility, CMF\_CSF, GFP-F connection, 802.3 PHY, and OTN path. + +**Figure II.1 – Fault on ingress** + +- The east PE detects a loss of signal on the ingress access link: + - 802.3 EFM OAM sends "Link fault" upstream, interspersed with Idles; + - GFP-F CMF CSF indication is sent into the network. +- The east CE detects "Link fault": + - Idles are sent towards the network and towards the enterprise. +- The west PE detects the GFP-F CMF CSF indication: + - If there is no network\_ETH\_AIS indication available, the laser (or electrical driver) is shut down. +- The west CE detects a loss of signal: + - 802.3 EFM OAM sends "Link fault" upstream, interspersed with Idles; + - Idles are sent towards the enterprise. + +### Scenario 2 + +In Figure II.2, a unidirectional fault occurs westbound on the server layer within the carrier network. + +![Diagram illustrating a fault within a carrier network across three layers: MAC (ETH), PHY, and EPL service. The diagram shows the flow of signals and fault indicators between Customer Equipment (CE), Packet Equipment (PE), and the Ethernet transport network. A fault occurs in the transport network, triggering various alarms and shutdowns.](fd4b2ee19b709bcb11190893e23f8453_img.jpg) + +The diagram illustrates the impact of a fault in an Ethernet transport network across different layers: + +- EPL service:** The top layer shows the end-to-end service between two CE units, which is interrupted by the fault in the transport network. +- MAC layer (ETH layer):** + - The west CE sends a "Link fault" message to the west PE. + - The west PE detects "MAC frame visibility" loss. + - The east PE detects "MAC frame visibility" loss. + - The east CE receives a "Link fault" message from the east PE. +- PHY layer:** + - The west PE generates "Path AIS", "Path RDI", and "CMF\_RDI" signals back into the network. + - The west PE performs a "Laser shutdown". + - The east PE detects "GFP-F connection" loss and "CMF\_RDI". + - The east PE performs a "Laser shutdown". + - The fault is also shown on the "OTN path" between the PEs. + +Diagram illustrating a fault within a carrier network across three layers: MAC (ETH), PHY, and EPL service. The diagram shows the flow of signals and fault indicators between Customer Equipment (CE), Packet Equipment (PE), and the Ethernet transport network. A fault occurs in the transport network, triggering various alarms and shutdowns. + +G.8021-Y.1341(12)\_FI-2 + +**Figure II.2 – Fault within a carrier network** + +- An NE in the carrier network detects the failure of one of the member paths of a virtual concatenation (VCAT) group: + - ODU AIS is generated downstream on the affected path. +- The west PE detects ODU AIS: + - ODU RDI is generated back into the network on the associated path; + - GFP-F CMF RDI is generated back into the network; + - if there is no network\_ETH\_AIS indication available, the laser (or electrical driver) is shut down. +- The west CE detects a loss of signal: + - 802.3 EFM OAM sends "Link fault" upstream, interspersed with Idles; + - Idles are sent towards the enterprise. +- The east PE detects the GFP-F CMF RDI indication: + - If there is no network\_ETH\_RDI indication available, the laser (or electrical driver) is shut down. +- The east CE detects a loss of signal: + - 802.3 EFM OAM sends "Link fault" upstream, interspersed with Idles; + - Idles are sent towards the enterprise. + +### Scenario 3 + +In Figure II.3, a unidirectional fault occurs on the west access link towards the enterprise network. + +![Diagram illustrating a fault on egress in an Ethernet transport network. The diagram shows three layers: MAC layer (ETH layer), PHY layer, and EPL service. A fault occurs on the egress path from the west PE to the east PE. The west CE detects a loss of signal and sends 'Link fault' upstream. The west PE detects the link fault and sends 'MAC frame visibility' and 'CMF_RDI' into the network. The east PE detects the 'GFP-F connection' and 'OTN path' and performs a 'Laser shutdown'. The east CE detects a loss of signal and sends 'Link fault' upstream. The diagram is labeled G.8021-Y.1341(12)_FI-3.](687c1faf4209421db20c72c280b06a3d_img.jpg) + +The diagram illustrates a fault on egress in an Ethernet transport network. It shows three layers: MAC layer (ETH layer), PHY layer, and EPL service. A fault occurs on the egress path from the west PE to the east PE. The west CE detects a loss of signal and sends "Link fault" upstream. The west PE detects the link fault and sends "MAC frame visibility" and "CMF\_RDI" into the network. The east PE detects the "GFP-F connection" and "OTN path" and performs a "Laser shutdown". The east CE detects a loss of signal and sends "Link fault" upstream. The diagram is labeled G.8021-Y.1341(12)\_FI-3. + +Diagram illustrating a fault on egress in an Ethernet transport network. The diagram shows three layers: MAC layer (ETH layer), PHY layer, and EPL service. A fault occurs on the egress path from the west PE to the east PE. The west CE detects a loss of signal and sends 'Link fault' upstream. The west PE detects the link fault and sends 'MAC frame visibility' and 'CMF\_RDI' into the network. The east PE detects the 'GFP-F connection' and 'OTN path' and performs a 'Laser shutdown'. The east CE detects a loss of signal and sends 'Link fault' upstream. The diagram is labeled G.8021-Y.1341(12)\_FI-3. + +**Figure II.3 – Fault on egress** + +- The west CE detects a loss of signal: + - 802.3 EFM OAM sends "Link fault" upstream, interspersed with Idles; + - Idles are sent towards the enterprise. +- The west PE detects the link fault indication: + - GFP-F CMF RDI indication is sent into the network; + - Idles are sent towards the CE. +- The east PE detects the GFP-F CMF RDI indication: + - If there is no network\_ETH\_RDI indication available, the laser (or electrical driver) is shut down. +- The east CE detects a loss of signal: + - 802.3 EFM OAM sends "Link fault" upstream, interspersed with Idles; + - Idles are sent towards the enterprise. + +Note that a PE only reacts to the reception of a link fault indication when there are no other conditioning alarms (i.e., the PE takes no further conditioning action when it receives a link fault indication in response to having shut down its own egress laser). + +# **Appendix III** + +## **Compound functions** + +(This appendix does not form an integral part of this Recommendation.) + +ETH MEP and MIP compound functions are defined in clause 9.8. + +# **Appendix IV** + +## **Start-up conditions** + +(This appendix does not form an integral part of this Recommendation.) + +The set of interconnected ETH\_FF processes must be loop-free, otherwise the integrity of the network may be compromised. This requirement implies that one can only include ports of the ETH\_FF process in the ETH\_C function if it is known that this will not create a loop. + +In [IEEE 802.1Q] this is realized by starting in a state without connectivity, except for the exchange of PDUs. Consequently, the active topology enforcement mechanism extends the connectivity while making sure that this does not create any loops. + +This means that the ETH\_C function as defined in this Recommendation, on start-up of the equipment may not contain an ETH\_FF that includes more than one port of its enclosing ETH\_FF process. After start-up, ports may be added to the ETH\_FF process under the control of the active topology enforcement mechanism. Alternatively, this may be done under control of a management system, as long as the management system can guarantee that there are no loops created. + +# Appendix V + +## 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 [ITU-T Z.101]. The SDL diagrams use the conventions in Figure V.1. + +![Figure V.1 – SDL symbols. A grid of 10 symbols with their names: Procedure start (oval), Procedure stop (X), State (oval with vertical line), Input (parallelogram), Save (parallelogram), Label/connector (circle), Decision (diamond), Task (rectangle), Output (rectangle with vertical line), Procedure call (rectangle with double vertical lines), Procedure return (circle with X). Oval symbol Diamond symbol X symbol Rectangle symbol Oval with vertical line symbol Rectangle with vertical line symbol Parallelogram symbol Rectangle with double vertical lines symbol Parallelogram symbol Circle with X symbol Circle symbol](8dd5c733658cf8d82fe930745b58994c_img.jpg) + +| | | | | +|--|-----------------|--|------------------| +| | Procedure start | | Decision | +| | Procedure stop | | Task | +| | State | | Output | +| | Input | | Procedure call | +| | Save | | Procedure return | +| | Label/connector | | | + +Figure V.1 – SDL symbols. A grid of 10 symbols with their names: Procedure start (oval), Procedure stop (X), State (oval with vertical line), Input (parallelogram), Save (parallelogram), Label/connector (circle), Decision (diamond), Task (rectangle), Output (rectangle with vertical line), Procedure call (rectangle with double vertical lines), Procedure return (circle with X). Oval symbol Diamond symbol X symbol Rectangle symbol Oval with vertical line symbol Rectangle with vertical line symbol Parallelogram symbol Rectangle with double vertical lines symbol Parallelogram symbol Circle with X symbol Circle symbol + +G.8021-Y.1341(16)\_FV.1 + +**Figure V.1 – SDL symbols** + +## Appendix VI + +### Calculation methods for frame loss measurement + +(This appendix does not form an integral part of this Recommendation.) + +Frame loss measurement is performed by the collection of counter values for ingress and egress service frames and the exchange of OAM frames with the local counter value between a pair of MEPs. In this Recommendation two different mechanisms are defined for frame loss measurement and both mechanisms have different calculation methods. + +#### VI.1 Dual-ended loss measurement + +This is performed by proactive OAM and both MEPs send dual-ended CCM frames to its peer MEP periodically. The calculation method specified in the proactive loss measurement process is depicted as shown in Figure VI.1. + +![Figure VI.1 – Dual-ended ETH LM sequence diagram](9eee1c87837684d5b5bf058a649750f5_img.jpg) + +The diagram shows a sequence of ETH-CCM frames exchanged between a Local and a Remote MEP. + On the Local side, ingress counters TxFCl and egress counters RxFCb are tracked. + On the Remote side, ingress counters TxFCl and egress counters RxFCb are tracked. + At time tp, Local sends a CCM containing (TxFCf[tp], RxFCb[tp], TxFCb[tp]). + At time tc, Local sends a CCM containing (TxFCf[tc], RxFCb[tc], TxFCb[tc]). + The Remote side performs similar operations, sending its own counters back to the Local side. + The diagram illustrates how these values are captured and exchanged to calculate loss. + +Figure VI.1 – Dual-ended ETH LM sequence diagram + +$$\begin{aligned} F\_LF \text{ (Frame Loss}_{\text{far-end}}) &= |TxFCb[t_c] - TxFCb[t_p]| - |RxFCb[t_c] - RxFCb[t_p]| \\ &= |TxFCb - TxFCb\_svd| - |RxFCb - RxFCb\_svd| \\ N\_LF \text{ (Frame Loss}_{\text{near-end}}) &= |TxFCf[t_c] - TxFCf[t_p]| - |RxFCf[t_c] - RxFCf[t_p]| \\ &= |TxFCf - TxFCf\_svd| - |RxFCf - RxFCf\_svd| \end{aligned}$$ + +**Figure VI.1 – Dual-ended ETH LM** + +#### VI.2 Single-ended loss measurement + +This is performed by the on-demand OAM and an MEP which sends LMM frames to its peer MEP and receives LMR frames from its peer MEP. The calculation method specified in the LM control process is depicted as shown in Figure VI.2. + +Rec. ITU-T G.8021/Y.1341 (04/2022)     217 + +![Diagram of Single-ended ETH LM showing Local and Remote components. The Local side has TxFCf[t_p], RxFCI[t_p], TxFCf[t_c], and RxFCI[t_c] blocks. The Remote side has TxFCf[t_p], RxFCf[t_p], TxFCb[t_p], TxFCb[t_c], and RxFCf[t_c] blocks. Arrows show data flow between them via ETH-LMM and ETH-LMR protocols. G.8021-Y.1341(12)_FVI-2 is noted at the bottom right.](1b2e5b12ac4f5d7bb2fa18524982f2d8_img.jpg) + +G.8021-Y.1341(12)\_FVI-2 + +Diagram of Single-ended ETH LM showing Local and Remote components. The Local side has TxFCf[t\_p], RxFCI[t\_p], TxFCf[t\_c], and RxFCI[t\_c] blocks. The Remote side has TxFCf[t\_p], RxFCf[t\_p], TxFCb[t\_p], TxFCb[t\_c], and RxFCf[t\_c] blocks. Arrows show data flow between them via ETH-LMM and ETH-LMR protocols. G.8021-Y.1341(12)\_FVI-2 is noted at the bottom right. + +$$\begin{aligned} + F\_LF (\text{Frame Loss}_{\text{far-end}}) &= | \text{TxFCf}[t_c] - \text{TxFCf}[t_p] | - | \text{RxFCf}[t_c] - \text{RxFCf}[t_p] | \\ + &= | \text{TxFCf} - \text{TxFCf\_svd} | - | \text{RxFCf} - \text{RxFCf\_svd} | \\ + N\_LF (\text{Frame Loss}_{\text{near-end}}) &= | \text{TxFCb}[t_c] - \text{TxFCb}[t_p] | - | \text{RxFCI}[t_c] - \text{RxFCI}[t_p] | \\ + &= | \text{TxFCb} - \text{TxFCb\_svd} | - | \text{RxFCI} - \text{RxFCI\_svd} | + \end{aligned}$$ + +**Figure VI.2 – Single-ended ETH LM** + +# **Appendix VII** + +## **Considerations of the support of a rooted multipoint EVC service** + +(This appendix does not form an integral part of this Recommendation.) + +This appendix has been removed. For considerations on supporting a rooted multipoint Ethernet virtual connection (EVC) service (per [ITU-T G.8011]), refer to clause F.1.3.2 of [IEEE 802.1Q]. + +# Appendix VIII + +## Configurations for ingress VID filtering + +(This appendix does not form an integral part of this Recommendation.) + +This appendix describes an example of the configuration for ingress VID filtering described in [IEEE 802.1Q]. + +![Diagram illustrating the configuration for ingress VID filtering. At the top, a yellow oval labeled ETH_C contains FF10, FF20, FF30, FF40, and FFx. Below are four ports: Port A, Port B, Port C, and Port D. Each port has a Sk (Switch) and So (Selector) block. Port A and B have Sk blocks with 1...4094 range and So blocks with 20 and 30 respectively. Port C and D have Sk blocks with 10 20 30 40 range and So blocks with 10 20 30 40. Arrows show traffic flow from Sk to So and then to the port. Red arrows show VID filtering from FF processes to So blocks. Blue arrows show VID filtering from FF processes to Sk blocks. A label G.8021-Y.1341(12)_FVIII.1 is at the bottom right.](1a1f0ff74dee05dae773437f24c5a996_img.jpg) + +Diagram illustrating the configuration for ingress VID filtering. At the top, a yellow oval labeled ETH\_C contains FF10, FF20, FF30, FF40, and FFx. Below are four ports: Port A, Port B, Port C, and Port D. Each port has a Sk (Switch) and So (Selector) block. Port A and B have Sk blocks with 1...4094 range and So blocks with 20 and 30 respectively. Port C and D have Sk blocks with 10 20 30 40 range and So blocks with 10 20 30 40. Arrows show traffic flow from Sk to So and then to the port. Red arrows show VID filtering from FF processes to So blocks. Blue arrows show VID filtering from FF processes to Sk blocks. A label G.8021-Y.1341(12)\_FVIII.1 is at the bottom right. + +Figure VIII.1 – Example of configuration for ingress VID filtering + +Table VIII.1 – VID configuration + +| VID | Port A | | Port B | | Port C | | Port D | | +|--------|---------|--------|---------|--------|---------|--------|---------|--------| +| | Ingress | Egress | Ingress | Egress | Ingress | Egress | Ingress | Egress | +| 10 | ✓ | | ✓ | | ✓ | ✓ | ✓ | ✓ | +| 20 | ✓ | ✓ | ✓ | | ✓ | ✓ | ✓ | ✓ | +| 30 | ✓ | | ✓ | ✓ | ✓ | ✓ | | | +| 40 | ✓ | | ✓ | | ✓ | ✓ | ✓ | ✓ | +| Others | ✓ | | ✓ | | | | | | + +Figure VIII.1 and Table VIII.1 show an example of the configuration. For the ingress configuration, MI\_Vlan\_Config[] signal is set to ETHx/ETH-m\_A\_Sk function and ETH\_CI signals corresponding VIDs are connected to ETH\_FF processes in ETH\_C function. For the egress configuration, MI\_Vlan\_Config[] signal is set to ETHx/ETH-m\_A\_So function and ETH\_CI signals corresponding VIDs are connected to ETH\_FF processes in ETH\_C function. + +On ports A and B in this example, MI\_Vlan\_Config[1...4094] are set to ETHx/ETH-m\_A\_Sk in order to disable the ingress VID filtering. In this case, all incoming VID traffic is forwarded once to ETH\_C. Since ETH\_FF is connected to configured ingress and egress ports only, the traffic is forwarded to the appropriate ports. + +# Appendix IX + +## Handling of Expected Defects + +(This appendix does not form an integral part of this Recommendation.) + +This appendix describes how the Expected Defect messages (EDMs) can be used to avoid spurious Loss of Continuity defects, and provides some recommendations for how the Element Management function (EMF) should control the associated management information (in particular, ETHx\_FT\_Sk\_MI\_CC\_Enable). + +There are two primary use cases for handling of expected defects: + +- Interruption events, such as in-service software upgrade, where transmission of CCMs is interrupted but there is no impact on the flow of data frames. +- Service activation, in particular adding a new end-point to an existing multipoint service. + +These are discussed further below, followed by some additional considerations. + +## IX.1 Interruption events + +In implementations where the OAM Generation functions execute in different hardware to that used for traffic forwarding – typically either a dedicated hardware chip designed for OAM, or in software on a general-purpose CPU – it is possible that the OAM traffic may be interrupted without affecting the data traffic flow, as shown in Figure IX.1. The desirable behaviour in this case may be for any peer devices to ignore the loss-of-continuity of the OAM traffic (since there is no interruption in the data traffic). If the interruption is due to a failure and is hence unexpected, that may not be possible; however, if it is due to an administrative action, then there is the possibility of notifying the peer in advance of the event. Examples of such intentional events include software or firmware upgrades, or manual recovery from earlier failure conditions. + +![Figure IX.1: Example where OAM functions and data traffic forwarding are in different hardware. The diagram shows two states of a device. In the left state, both OAM traffic (blue line) and Data traffic (black line) are shown as continuous. In the right state, the OAM traffic is interrupted (dashed blue line), while the Data traffic continues to flow (solid black line). Labels indicate 'OAM and data handled in different hardware' and 'OAM interrupted but data continues to flow'. A reference code 'G.8021-Y.1341(18)_FIX.1' is present in the bottom right.](716969acd545b06c228fee3867e07e5b_img.jpg) + +The diagram illustrates two scenarios of a network device where OAM and data traffic are handled in separate hardware components. In the left scenario, both OAM traffic (represented by a blue line) and Data traffic (represented by a black line) are shown as continuous, passing through their respective hardware blocks (green rectangles). In the right scenario, the OAM traffic is interrupted, indicated by a dashed blue line and a red rectangle, while the Data traffic continues to flow uninterrupted through its green hardware block. Labels within the diagram include 'OAM traffic', 'Data traffic', 'OAM and data handled in different hardware', and 'OAM interrupted but data continues to flow'. A reference code 'G.8021-Y.1341(18)\_FIX.1' is present in the bottom right corner. + +Figure IX.1: Example where OAM functions and data traffic forwarding are in different hardware. The diagram shows two states of a device. In the left state, both OAM traffic (blue line) and Data traffic (black line) are shown as continuous. In the right state, the OAM traffic is interrupted (dashed blue line), while the Data traffic continues to flow (solid black line). Labels indicate 'OAM and data handled in different hardware' and 'OAM interrupted but data continues to flow'. A reference code 'G.8021-Y.1341(18)\_FIX.1' is present in the bottom right. + +**Figure IX.1 – Example where OAM functions and data traffic forwarding are in different hardware** + +A mechanism to notify the peer MEPs in advance is particularly useful when OAM is used across multiple administrative domains (e.g., across a UNI or ENNI), as in these cases it may not be possible to correlate the event with the loss of continuity at the management layer. The Expected Defect message provides such a mechanism, by indicating that a loss of continuity is expected for a specified duration. It is triggered by setting MI\_EDM\_Enable to true, and MI\_EDM\_Duration to the expected duration for which CCM transmission will be interrupted. + +On receiving an EDM, the peer MEP relays the information to the EMF. If configured to do so, the EMF can then unset MI\_CC\_Enable in the flow termination sink function of the MEP (ETHx\_FT\_Sk or ETHG\_FT\_Sk), to disable receipt of CCMs for the duration specified in the EDM. When receipt of CCMs is disabled, loss of continuity (dLOC) does not result in either alarms (cLOC) or consequent + +actions (aTSF). After the specified duration, the EMF re-enables MI\_CC\_Enable; if CCMs have resumed, then dLOC will no longer be detected. If CCMs are still not being received, then dLOC will still be detected and this will result in alarms (cLOC) and consequent actions (aTSF). + +An example showing the use of EDM in this case is shown in Figure IX.2. + +![Sequence diagram illustrating the use of Expected Defect (EDM) to handle an interruption event between a Local MEP and a Peer MEP.](94563c795d36d598e53b9e5b4c95934c_img.jpg) + +The diagram shows a sequence of messages between a Local MEP (left) and a Peer MEP (right), each with an associated EMF. The sequence is as follows: + +- The Local MEP EMF sends two CCM messages to the Peer MEP EMF. +- An interruption event occurs at the Local MEP EMF, triggering a "Prepare for interruption" action. +- The Local MEP EMF sends an "Exp defect PDU (duration = 5 min)" message to the Peer MEP EMF. +- Upon receiving the PDU, the Peer MEP EMF sets `ETHx_FT_Sk_MI_CC_Enable = FALSE`. +- The Local MEP EMF then sends two more CCM messages to the Peer MEP EMF. +- Upon receiving these CCMs, the Peer MEP EMF sets `ETHx_FT_Sk_MI_CC_Enable = TRUE`. + +A large blue rectangle on the Local MEP side represents the interruption event. The text "G.8021-Y.1341(16)\_FIX.2" is visible in the bottom right corner of the diagram area. + +Sequence diagram illustrating the use of Expected Defect (EDM) to handle an interruption event between a Local MEP and a Peer MEP. + +**Figure IX.2 – Example showing EDM used to handle an interruption event** + +## IX.2 Service activation + +To enable correct operation of Continuity Checks in G.8013-based Ethernet OAM, it is necessary to configure each MEP in a MEG with its own unique MEP ID (via MI\_MEP\_ID), and in addition with the MEP IDs of all of its peer MEPs (via MI\_PeerMEP\_ID[]). + +This can cause difficulties when adding a new end-point (and hence a new MEP) to an existing service: to avoid spurious defects and alarms, the configuration must be changed on all of the existing MEPs simultaneously with enabling CCMs on the new MEP. Again, this is particularly challenging when the MEPs are in different administrative domains. + +The spurious alarms can be avoided in this case using the Expected Defect message, as follows. When the new MEP is added, before enabling CCM transmission, Expected Defect messages are sent. As in the above case, on receiving these, the existing MEPs in the MEG relay the information to their corresponding EMFs, and if so configured, the EMFs disabled CCM reception. The EMFs at the existing MEPs can then add the MEP ID of the new MEP to the list of Peer MEP IDs (MI\_PeerMEP\_ID[]) without triggering any Loss of Continuity alarms or consequent actions for the new MEP, even though CCMs are not yet being received. Once this is done, CCM transmission can be enabled at the new MEP, and this will not trigger Unexpected MEP defects (dUNM) at the existing MEPs, as the new MEP ID has already been added to their lists of Peer MEPs. Finally, once the duration in the EDM has passed, the EMFs at the existing MEPs re-enable CCM reception. + +An example showing this sequence can be seen in Figure IX.3. + +![Sequence diagram showing the interaction between Existing MEP 1, New MEP 2, and Existing MEP 100. The diagram illustrates the handling of an Expected Defect (EDM) notification from New MEP 2 to Existing MEP 100. The sequence starts with Existing MEP 1 and New MEP 2 sending CCM (MEP 1) frames to Existing MEP 100. New MEP 2 then sends an 'Exp defect PDU (MEP 2) (duration = 5 min)'. Existing MEP 100 receives this and sets 'Sk_MI_EDM_Received (MEP 2, duration = 5 min)'. The diagram shows two scenarios: 1) If 'New MEP: So_MI_EDM_Enable = TRUE', the EDM is processed. 2) If 'So_MI_EDM_Enable = FALSE' and 'So_MI_CC_Enable = TRUE', the EDM is ignored, and the system continues to receive CCM (MEP 1) and CCM (MEP 2) frames, resulting in 'No defect since MEP 2 is now expected'.](444aae06b7856be544a8e1bbae1302c3_img.jpg) + +The diagram illustrates a sequence of messages between three entities: Existing MEP 1, New MEP 2, and Existing MEP 100. The interaction involves the handling of an Expected Defect (EDM) notification from New MEP 2 to Existing MEP 100. + +- Initial State:** Existing MEP 1 and New MEP 2 are sending CCM (MEP 1) frames to Existing MEP 100. +- EDM Notification:** New MEP 2 sends an "Exp defect PDU (MEP 2) (duration = 5 min)" to Existing MEP 100. +- Existing MEP 100 Response:** Existing MEP 100 receives the EDM and sets the signal "Sk\_MI\_EDM\_Received (MEP 2, duration = 5 min)". +- Scenario 1 (EDM Enabled):** If "New MEP: So\_MI\_EDM\_Enable = TRUE", the EDM is processed. Existing MEP 100 continues to receive CCM (MEP 1) frames and sets "Sk\_MI\_CC\_Enable = FALSE" and "Sk\_MI\_PeerMEP\_ID[1, 2]". +- Scenario 2 (EDM Disabled, CC Enabled):** If "So\_MI\_EDM\_Enable = FALSE" and "So\_MI\_CC\_Enable = TRUE", the EDM is ignored. Existing MEP 100 continues to receive CCM (MEP 1) and CCM (MEP 2) frames, resulting in "No defect since MEP 2 is now expected". +- Final State:** Existing MEP 100 sets "Sk\_MI\_CC\_Enable = TRUE". + +G.8021-Y.1341(16)\_FIX.3 + +Sequence diagram showing the interaction between Existing MEP 1, New MEP 2, and Existing MEP 100. The diagram illustrates the handling of an Expected Defect (EDM) notification from New MEP 2 to Existing MEP 100. The sequence starts with Existing MEP 1 and New MEP 2 sending CCM (MEP 1) frames to Existing MEP 100. New MEP 2 then sends an 'Exp defect PDU (MEP 2) (duration = 5 min)'. Existing MEP 100 receives this and sets 'Sk\_MI\_EDM\_Received (MEP 2, duration = 5 min)'. The diagram shows two scenarios: 1) If 'New MEP: So\_MI\_EDM\_Enable = TRUE', the EDM is processed. 2) If 'So\_MI\_EDM\_Enable = FALSE' and 'So\_MI\_CC\_Enable = TRUE', the EDM is ignored, and the system continues to receive CCM (MEP 1) and CCM (MEP 2) frames, resulting in 'No defect since MEP 2 is now expected'. + +**Figure IX.3 – Example showing EDM used to handle a new MEP** + +## IX.3 Additional considerations + +It should not be possible – maliciously or accidentally – to circumvent normal fault monitoring by continuously sending Expected Defect notifications for an extended period of time. This can be prevented in a number of ways: + +- Implementations should limit the maximum value of MI\_EDM \_Duration that the user can specify. In some cases, the EMF may be able to derive the value without input from the end user; for example, in the case of an in-service software upgrade, the EMF can determine how long this will take, and hence for how long normal CCM transmission will be interrupted. It can then set MI\_EDM\_Enable and MI\_EDM \_Duration accordingly. +- The Expected Defect signal (MI\_EDM\_Received) should be ignored by the EMF unless processing is explicitly enabled by the user. The EMF should allow the user control over when this is enabled; for example, the user may wish to only allow Expected Defect notifications to be processed during a maintenance window. Even when enabled by the user, the EMF should temporarily disable the handling in some cases as described below. +- The EMF should allow the user to specify the maximum duration of an Expected Defect notification that will be handled. If an EDM is received indicating a longer duration than this, the duration is truncated to this value. +- The EMF should limit the number of times an Expected Defect notification is processed in a given period of time, for example to 3 times in a month. Note that the limit applies to each series of consecutive EDMs (from the same peer MEP), not to the number of individual EDM frames received. +- To prevent multiple uses of the Expected Defect notification in quick succession, the EMF should disable processing for a short time after the end of each expected defect condition. +- Whenever an Expected Defect notification is received, this should be logged by the EMF, so that any long-term trends can be analysed, and misuse can be detected. + +# Appendix X + +## Mapping guidelines between the atomic functions defined in b-ITU-T G.8021-2016 and those defined in ITU-T G.8023 + +(This appendix does not form an integral part of this Recommendation.) + +Clause 10 of [b-ITU-T G.8021-2016] and older versions of this Recommendation defined the Ethernet physical layer network (ETY) to model the Ethernet physical layer as defined in [IEEE 802.3]. These ETY-related atomic functions have been superseded by the atomic functions defined in [ITU-T G.8023]. Clause 10 of this Recommendation has been aligned with [ITU-T G.8023]. This appendix provides some informative guidelines to map between the atomic functions defined in [b-ITU-T G.8021-2016] and those defined in [ITU-T G.8023]. See Figures X.1 to X.3. + +Ethernet interfaces providing the adaptation between the ETH layer network and the Ethernet physical layer defined in [IEEE 802.3] are modelled in [ITU-T G.8023] by the M-AI/ETH\_A atomic functions, defined in clause 6.1 of [ITU-T G.8023], that supersede both the ETYn\_TT and ETYn/ETH\_A atomic functions, defined in clauses 10.2 and 10.3 of [b-ITU-T G.8021-2016]. + +![Diagram showing the mapping between ETYn/ETH and M-AI/ETH adaptation functions. The left side shows the structure defined in [b-ITU-T G.8021-2016] (Clause 10.3 and Clause 10.2), and the right side shows the structure defined in [ITU-T G.8023] (Clause 6.1).](739d9761cdbb47394f979141864a8de6_img.jpg) + +The diagram illustrates two architectural models for Ethernet adaptation functions. On the left, representing [b-ITU-T G.8021-2016], the top section (Clause 10.3) consists of a trapezoidal block labeled 'ETYn/ETH' with two input lines above it labeled 'ETH\_TFP' and 'ETH\_FP'. Below this block is a smaller rectangular block labeled 'ETYn\_AP'. The bottom section (Clause 10.2) is a large inverted triangle labeled 'ETYn'. A vertical line connects the 'ETYn\_AP' block to the 'ETYn' triangle. At the bottom of the triangle is a single vertical line. Below this entire structure is the text 'Atomic functions defined in [b-ITU-T G.8021-2016]'. On the right, representing [ITU-T G.8023] (Clause 6.1), the top section consists of a trapezoidal block labeled 'M-AI/ETH' with two input lines above it labeled 'ETH\_TFP' and 'ETH\_FP'. Below this block is a rectangular block labeled 'M-AI\_AP'. Between these two blocks are two vertical lines with small pentagonal shapes at their base, and an ellipsis '...' between them. Below the 'M-AI\_AP' block is a rectangular block labeled 'Media element', connected by a vertical line. At the bottom of the 'Media element' block is a single vertical line. Below this entire structure is the text 'Atomic functions defined in [ITU-T G.8023]'. A small reference code 'G.8021-Y.1341(18)\_FX.1' is located at the bottom right. + +Diagram showing the mapping between ETYn/ETH and M-AI/ETH adaptation functions. The left side shows the structure defined in [b-ITU-T G.8021-2016] (Clause 10.3 and Clause 10.2), and the right side shows the structure defined in [ITU-T G.8023] (Clause 6.1). + +**Figure X.1 – Mapping between ETYn/ETH and M-AI/ETH adaptation functions** + +Ethernet interfaces providing the adaptations between the 8B/10B codewords of the 1000BASE-X PCS and the Ethernet physical layer defined in [IEEE 802.3] are modelled in [ITU-T G.8023] by the M-AI/ETC1000X\_A atomic functions, defined in clause 6.3 of [ITU-T G.8023], that supersede both the ETY3\_TT atomic functions, which were not defined in [b-ITU-T G.8021-2016] and the ETY3/ETC3\_A atomic functions, defined in clauses 10.4 of [b-ITU-T G.8021-2016]. + +![Diagram showing the mapping between ETY3/ETC3 and M-AI/ETC1000X adaptation functions. The left side shows ETC3_CP at Clause 10.4 connected to ETY3/ETC3, which is connected to ETY3_AP. Below ETY3_AP is a dashed triangle labeled ETY3, with 'Not defined' to its left. At the bottom, it says 'Atomic functions defined in [b-ITU-T G.8021-2016]'. The right side shows ETC1000X_CP at Clause 6.3 connected to M-AI/ETC1000X, which is connected to M-AI_AP. Below M-AI_AP is a rectangle labeled 'Media element'. At the bottom, it says 'Atomic functions defined in [ITU-T G.8023]'. A small label 'G.8021-Y.1341(18) FX.2' is at the bottom right.](1b54a9e1b22fff830f6767035580c39e_img.jpg) + +Diagram showing the mapping between ETY3/ETC3 and M-AI/ETC1000X adaptation functions. The left side shows ETC3\_CP at Clause 10.4 connected to ETY3/ETC3, which is connected to ETY3\_AP. Below ETY3\_AP is a dashed triangle labeled ETY3, with 'Not defined' to its left. At the bottom, it says 'Atomic functions defined in [b-ITU-T G.8021-2016]'. The right side shows ETC1000X\_CP at Clause 6.3 connected to M-AI/ETC1000X, which is connected to M-AI\_AP. Below M-AI\_AP is a rectangle labeled 'Media element'. At the bottom, it says 'Atomic functions defined in [ITU-T G.8023]'. A small label 'G.8021-Y.1341(18) FX.2' is at the bottom right. + +**Figure X.2 – Mapping between ETY3/ETC3 and M-AI/ETC1000X adaptation functions** + +NOTE 1 – The ETY3\_TT atomic functions in this diagram that would have been used as the server layer of the ETY3/ETC3\_A atomic functions should have been different from the ETYn\_TT (n=3) atomic functions, defined in clause 10.2 of [b-ITU-T G.8021-2016] because the ETY3/ETC3\_A function operates on 8B/10B codewords instead of MAC frames. This inconsistency has been resolved with the new model defined in [ITU-T G.8023]. + +Ethernet interfaces providing the adaptations between the preamble and ordered set information of the 10G Ethernet Reconciliation sub-layer and the Ethernet physical layer defined in [IEEE 802.3] are modelled in [ITU-T G.8023] by the M\_AI/ERS10G\_A atomic functions, defined in clause 6.2 of [ITU-T G.8023], that supersede both the ETY4\_TT atomic functions, which were not defined in [b-ITU-T G.8021-2016] and ETY4/ETHPP-OS\_A atomic functions, defined in clauses 10.7 of [b-ITU-T G.8021-2016]. + +![Diagram showing the mapping between ETY4/ETHPP-OS and M-AI/ERS10G adaptation functions. The left side shows ETHPP-OS_CP at Clause 10.7 connected to ETY4/ETHPP-OS, which is connected to ETY4_AP. Below ETY4_AP is a dashed triangle labeled ETY4, with 'Not defined' to its left. At the bottom, it says 'Atomic functions defined in [b-ITU-T G.8021-2016]'. The right side shows ERS10G_CP at Clause 6.2 connected to M-AI/ERS10G, which is connected to M-AI_AP. Below M-AI_AP is a rectangle labeled 'Media element'. At the bottom, it says 'Atomic functions defined in [ITU-T G.8023]'. A small label 'G.8021-Y.1341(18) FX.3' is at the bottom right.](0462d0f51917c1299c5e71db9bd9ef32_img.jpg) + +Diagram showing the mapping between ETY4/ETHPP-OS and M-AI/ERS10G adaptation functions. The left side shows ETHPP-OS\_CP at Clause 10.7 connected to ETY4/ETHPP-OS, which is connected to ETY4\_AP. Below ETY4\_AP is a dashed triangle labeled ETY4, with 'Not defined' to its left. At the bottom, it says 'Atomic functions defined in [b-ITU-T G.8021-2016]'. The right side shows ERS10G\_CP at Clause 6.2 connected to M-AI/ERS10G, which is connected to M-AI\_AP. Below M-AI\_AP is a rectangle labeled 'Media element'. At the bottom, it says 'Atomic functions defined in [ITU-T G.8023]'. A small label 'G.8021-Y.1341(18) FX.3' is at the bottom right. + +**Figure X.3 – Mapping between ETY4/ETHPP-OS and M-AI/ERS10G adaptation functions** + +NOTE 2 – The ETY4\_TT atomic functions in this diagram that would have been used as the server layer of the ETY4/ETHPP-OS\_A atomic functions should have been different from the ETYn\_TT (n=4) atomic functions, defined in clause 10.2 of [b-ITU-T G.8021-2016] because the ETY4/ETHPP-OS\_A function preserves preamble and ordered set information. This inconsistency has been resolved with the new model defined in [ITU-T G.8023]. + +# Appendix XI + +## Basic Ethernet MAC layer network (ETH) equipment types + +(This appendix does not form an integral part of this Recommendation.) + +Some examples of Ethernet MAC layer network (ETH) equipment are described in this appendix, illustrating different ways to combine the atomic functions defined in this Recommendation. These particular combinations are aligned with the set of IEEE 802.1Q bridge types. This set is defined in [IEEE 802.1Q] and IEEE 802.1Q bridge types applicable to this Recommendation are illustrated in Figure XI.1 and Figure XI.2. + +![Figure XI.1: Provider edge bridge (PEB) diagram](7d675e1c380dccba3f69e2de4e72562c_img.jpg) + +The diagram shows a large rectangle labeled **PEB** at the top, with the text "Provider edge bridge" inside. Inside this rectangle are two side-by-side boxes: "S-VLAN component" on the left and "C-VLAN component" on the right. The S-VLAN component contains two smaller boxes, "PNP" and "CNP", connected by a horizontal line. The C-VLAN component contains two smaller boxes, "PEP" and "CEP", also connected by a horizontal line. A horizontal line connects the CNP box in the S-VLAN component to the PEP box in the C-VLAN component. On the far left, outside the S-VLAN component but inside the PEB box, is a label "NNI" with a small vertical tick mark. On the far right, outside the C-VLAN component but inside the PEB box, is a label "UNI" with a small vertical tick mark. + +G.8021-Y.1341(22)\_FXI.1 + +Figure XI.1: Provider edge bridge (PEB) diagram + +**Figure XI.1 – Provider edge bridge (PEB)** + +![Figure XI.2: Provider bridge (PB) diagram](f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg) + +The diagram shows a large rectangle labeled **PB** at the top, with the text "Provider bridge" inside. Inside this rectangle is a single box labeled "S-VLAN component". This box contains two smaller boxes, "PNP" and "CNP", connected by a horizontal line. On the far left, outside the S-VLAN component but inside the PB box, is a label "NNI" with a small vertical tick mark. On the far right, outside the S-VLAN component but inside the PB box, is a label "UNI" with a small vertical tick mark. + +G.8021-Y.1341(22)\_FXI.2 + +Figure XI.2: Provider bridge (PB) diagram + +**Figure XI.2 – Provider bridge (PB)** + +The full set of basic ETH equipment types is presented in Figure XI.3 using layer processor functions, as specified in clause 6.5.3 of [b-ITU-T G.800]. + +![Figure XI.3 – Layer processor-based model for basic ETH equipment types. The diagram shows four vertical stacks of network layers. All stacks share a top yellow oval labeled 'ETH'. Stack 1 (leftmost) descends from 'ETH' through 'S-EC ETH_FP' to 'ETH_SV' to 'L-EC ETH_FP' to 'M-AI/ETH', labeled 'CNP on PB, port-based service interface'. Stack 2 descends from 'ETH' through 'S-EC ETH_FPs' to 'ETH_SV' to 'L-EC ETH_FP' to 'M-AI/ETH', labeled 'CNP on PB, S-Tagged service interface'. Stack 3 descends from 'ETH' through 'PEP + CNP on PEB' to 'S-EC ETH_FP' to 'ETH_CV' to 'C-EC ETH_FPs' to a pink oval labeled 'ETH' to 'C-EC ETH_FPs' to 'ETH_CV' to 'L-EC ETH_FP' to 'M-AI/ETH', labeled 'CEP on PEB, C-Tagged service interface'. Stack 4 (rightmost) descends from 'ETH' through 'S-EC ETH_FP' to 'ETH_SV' to 'L-EC ETH_FP' to 'M-AI/ETH', labeled 'PNP on PB, PEB and [b-MEF 26.2] ENNI'. A reference code 'G.8021-Y.1341(22)_FXI.3' is at the bottom right.](c79d10d97e1f525e9c85e96e91616923_img.jpg) + +Figure XI.3 – Layer processor-based model for basic ETH equipment types. The diagram shows four vertical stacks of network layers. All stacks share a top yellow oval labeled 'ETH'. Stack 1 (leftmost) descends from 'ETH' through 'S-EC ETH\_FP' to 'ETH\_SV' to 'L-EC ETH\_FP' to 'M-AI/ETH', labeled 'CNP on PB, port-based service interface'. Stack 2 descends from 'ETH' through 'S-EC ETH\_FPs' to 'ETH\_SV' to 'L-EC ETH\_FP' to 'M-AI/ETH', labeled 'CNP on PB, S-Tagged service interface'. Stack 3 descends from 'ETH' through 'PEP + CNP on PEB' to 'S-EC ETH\_FP' to 'ETH\_CV' to 'C-EC ETH\_FPs' to a pink oval labeled 'ETH' to 'C-EC ETH\_FPs' to 'ETH\_CV' to 'L-EC ETH\_FP' to 'M-AI/ETH', labeled 'CEP on PEB, C-Tagged service interface'. Stack 4 (rightmost) descends from 'ETH' through 'S-EC ETH\_FP' to 'ETH\_SV' to 'L-EC ETH\_FP' to 'M-AI/ETH', labeled 'PNP on PB, PEB and [b-MEF 26.2] ENNI'. A reference code 'G.8021-Y.1341(22)\_FXI.3' is at the bottom right. + +**Figure XI.3 – Layer processor-based model for basic ETH equipment types** + +Each equipment type is then shown individually in the remainder of this appendix, first comprised of layer processor functions, followed by an expansion into ITU-T G.8021 atomic functions as outlined in Figure XI.4. + +These layer protocol functions are not atomic: each contained function is available for use individually, should that be required, and contained functions which are light grey are optional and need not appear in all implementations. This allows for MIPs and MEPs to be instantiated as required while not requiring a separate drawing for each and every possible OAM configuration. + +The signal names C-EC, S-EC and L-EC are defined in [ITU-T G.8012]. These symbols contain functions that only provide tag stacking and do not create a new layer boundary. + +![Diagram illustrating the layer processor to ITU-T G.8021 atomic functions expansion. The diagram shows a stack of layers within a grey trapezoidal shape. At the top, two circles represent 'C-EC or S-EC ETH_FPs'. Below them, a series of 'ETH' labels are stacked vertically, with a vertical ellipsis between the second and third. To the right of this stack, the text 'ETH_xV, x = C, S' is written vertically. Below the 'ETH' stack is a box labeled 'ETH/ETH-m' with a 'VLAN Tag' label next to it. Below this box is another 'ETH' label. At the bottom of the stack is a single 'ETH' label. At the very bottom, outside the grey shape, is a circle labeled 'S-EC or L-EC ETH_FP'. Below this circle is the text 'G.8021-Y.1341(22)_FXI.4'.](3469b61857e9088867368249efc8763d_img.jpg) + +Diagram illustrating the layer processor to ITU-T G.8021 atomic functions expansion. The diagram shows a stack of layers within a grey trapezoidal shape. At the top, two circles represent 'C-EC or S-EC ETH\_FPs'. Below them, a series of 'ETH' labels are stacked vertically, with a vertical ellipsis between the second and third. To the right of this stack, the text 'ETH\_xV, x = C, S' is written vertically. Below the 'ETH' stack is a box labeled 'ETH/ETH-m' with a 'VLAN Tag' label next to it. Below this box is another 'ETH' label. At the bottom of the stack is a single 'ETH' label. At the very bottom, outside the grey shape, is a circle labeled 'S-EC or L-EC ETH\_FP'. Below this circle is the text 'G.8021-Y.1341(22)\_FXI.4'. + +**Figure XI.4 – Layer processor to ITU-T G.8021 atomic functions expansion** + +The ETH\_CV layer processor function provides C-VLAN tag stacking over an L-EC ETH\_FP or an S-EC ETH\_FP while the ETH\_SV layer processor function provides S-VLAN tag stacking over an L-EC ETH\_FP. + +## **XI.1 Provider edge bridge (PEB)** + +See Figures XI.5 and XI.6 + +![Diagram of PEB layer processor and edge processor functions showing two parallel processing paths. The top path consists of a yellow oval labeled 'ETH' connected to two 'S-EC ETH_FP' blocks, which are part of 'PEP + CNP on PEB'. These connect to two 'ETH_CV' blocks, which then connect to 'C-EC ETH_FPs' blocks. These 'C-EC ETH_FPs' blocks connect to a pink oval labeled 'ETH', which connects to another 'C-EC ETH_FPs' block. This block connects to an 'ETH_CV' block, which connects to an 'L-EC ETH_FP' block. This block connects to an 'M-AI/ETH' block, which is labeled 'CEP C-Tagged service interface'. The bottom path consists of the top 'ETH' oval connecting to an 'S-EC ETH_FPs' block, which connects to an 'ETH_SV' block, which connects to an 'L-EC ETH_FP' block. This block connects to an 'M-AI/ETH' block, which is labeled 'PNP G.8021-Y.1341(22)_FXI.5'.](9e290fa7e4578ba0a8b8c5008c99b564_img.jpg) + +Diagram of PEB layer processor and edge processor functions showing two parallel processing paths. The top path consists of a yellow oval labeled 'ETH' connected to two 'S-EC ETH\_FP' blocks, which are part of 'PEP + CNP on PEB'. These connect to two 'ETH\_CV' blocks, which then connect to 'C-EC ETH\_FPs' blocks. These 'C-EC ETH\_FPs' blocks connect to a pink oval labeled 'ETH', which connects to another 'C-EC ETH\_FPs' block. This block connects to an 'ETH\_CV' block, which connects to an 'L-EC ETH\_FP' block. This block connects to an 'M-AI/ETH' block, which is labeled 'CEP C-Tagged service interface'. The bottom path consists of the top 'ETH' oval connecting to an 'S-EC ETH\_FPs' block, which connects to an 'ETH\_SV' block, which connects to an 'L-EC ETH\_FP' block. This block connects to an 'M-AI/ETH' block, which is labeled 'PNP G.8021-Y.1341(22)\_FXI.5'. + +**Figure XI.5 – PEB – layer processor and edge processor functions** + +![Diagram of PEB – ITU-T G.8021 atomic functions showing three network paths. The top path (yellow oval) connects to S-EC ETH_FP, which leads to a grey hexagonal block labeled ETH_CV containing multiple ETH nodes and a C-VLAN Tag. This connects to a pink oval (ETH) via C-EC ETH_FPs. The second path (yellow oval) connects to S-EC ETH_FP, leading to a similar grey hexagonal block with ETH_CV and C-VLAN Tag, connecting to the pink oval via C-EC ETH_FPs. The third path (yellow oval) connects to S-EC ETH_FPs, leading to a grey hexagonal block labeled ETH_SV containing multiple ETH nodes and an S-VLAN Tag. This connects to an L-EC ETH_FP, which is connected to an M-AI/ETH PNP. The pink oval (ETH) connects to C-EC ETH_FPs, which lead to a grey hexagonal block labeled ETH_CV containing multiple ETH nodes and a C-VLAN Tag. This connects to an L-EC ETH_FP, which is connected to an M-AI/ETH CEP C-Tagged service interface. Reference G.8021-Y.1341(22)_FXI.6 is noted.](169044aee9e8adb39eed822364eed8aa_img.jpg) + +Diagram of PEB – ITU-T G.8021 atomic functions showing three network paths. The top path (yellow oval) connects to S-EC ETH\_FP, which leads to a grey hexagonal block labeled ETH\_CV containing multiple ETH nodes and a C-VLAN Tag. This connects to a pink oval (ETH) via C-EC ETH\_FPs. The second path (yellow oval) connects to S-EC ETH\_FP, leading to a similar grey hexagonal block with ETH\_CV and C-VLAN Tag, connecting to the pink oval via C-EC ETH\_FPs. The third path (yellow oval) connects to S-EC ETH\_FPs, leading to a grey hexagonal block labeled ETH\_SV containing multiple ETH nodes and an S-VLAN Tag. This connects to an L-EC ETH\_FP, which is connected to an M-AI/ETH PNP. The pink oval (ETH) connects to C-EC ETH\_FPs, which lead to a grey hexagonal block labeled ETH\_CV containing multiple ETH nodes and a C-VLAN Tag. This connects to an L-EC ETH\_FP, which is connected to an M-AI/ETH CEP C-Tagged service interface. Reference G.8021-Y.1341(22)\_FXI.6 is noted. + +**Figure XI.6 – PE B – ITU-T G.8021 atomic functions** + +## **XI.2 Provider bridge (PB)** + +See Figures XI.7 and XI.8. + +![Diagram of PB – layer processor and edge processor functions showing three service interfaces: CNP port-based, CNP S-Tagged, and PNP.](670a9057bbab8c7c0eb91db3a6de4d55_img.jpg) + +This diagram illustrates the layer processor and edge processor functions for three different service interfaces. At the top is a yellow oval labeled "ETH". Below it, three vertical paths represent different interfaces: + +- CNP port-based service interface:** The path consists of "S-EC ETH\_FP" (a line), "ETH\_SV" (a downward-pointing triangle), "L-EC ETH\_FP" (a line), and "M-AI/ETH" (a trapezoid). +- CNP S-Tagged service interface:** The path consists of "S-EC ETH\_FPs" (a line with a small square), "ETH\_SV" (a downward-pointing triangle), "L-EC ETH\_FP" (a line), and "M-AI/ETH" (a trapezoid). +- PNP:** The path consists of "S-EC ETH\_FPs" (a line with a small square), "ETH\_SV" (a downward-pointing triangle), "L-EC ETH\_FP" (a line), and "M-AI/ETH" (a trapezoid). + +The text "G.8021-Y.1341(22)\_FXI.7" is located at the bottom right of the diagram. + +Diagram of PB – layer processor and edge processor functions showing three service interfaces: CNP port-based, CNP S-Tagged, and PNP. + +**Figure XI.7 – PB – layer processor and edge processor functions** + +![Diagram of PB – ITU-T G.8021 atomic functions showing three service interfaces with detailed internal structures.](5a0ceec2951b5bf8ab095948d3bf88e8_img.jpg) + +This diagram shows the ITU-T G.8021 atomic functions for the same three service interfaces. At the top is a yellow oval labeled "ETH". Below it, three vertical paths represent different interfaces, each enclosed in a gray shaded area representing the atomic functions: + +- CNP port-based service interface:** The path starts with "S-EC ETH\_FP" (a line), followed by a gray area containing a vertical stack of "ETH" blocks (triangles pointing up and down) and "ETH\_SV" (a line). Below the gray area is "ETH/ETH-m" (a trapezoid), "S-VLAN Tag" (a line), "ETH" (a triangle pointing down), and "ETH" (a triangle pointing up). The path ends with "L-EC ETH\_FP" (a line) and "M-AI/ETH" (a trapezoid). +- CNP S-Tagged service interface:** The path starts with "S-EC ETH\_FPs" (a line with a small square), followed by a gray area containing a vertical stack of "ETH" blocks (triangles pointing up and down) and "ETH\_SV" (a line). Below the gray area is "ETH/ETH-m" (a trapezoid), "S-VLAN Tag" (a line), "ETH" (a triangle pointing down), and "ETH" (a triangle pointing up). The path ends with "L-EC ETH\_FP" (a line) and "M-AI/ETH" (a trapezoid). +- PNP:** The path starts with "S-EC ETH\_FPs" (a line with a small square), followed by a gray area containing a vertical stack of "ETH" blocks (triangles pointing up and down) and "ETH\_SV" (a line). Below the gray area is "ETH/ETH-m" (a trapezoid), "S-VLAN Tag" (a line), "ETH" (a triangle pointing down), and "ETH" (a triangle pointing up). The path ends with "L-EC ETH\_FP" (a line) and "M-AI/ETH" (a trapezoid). + +The text "G.8021-Y.1341(22)\_FXI.8" is located at the bottom right of the diagram. + +Diagram of PB – ITU-T G.8021 atomic functions showing three service interfaces with detailed internal structures. + +**Figure XI.8 – PB – ITU-T G.8021 atomic functions** + +# Bibliography + +- [b-ITU-T G.800] Recommendation ITU-T G.800 (2016), *Unified functional architecture of transport networks.* +- [b-ITU-T G.8021-2016] Recommendation ITU-T G.8021/Y.1341 (2016), *Characteristics of Ethernet transport network equipment functional blocks.* +- [b-ITU-T M.3208.1] Recommendation ITU-T M.3208.1 (1997), *TMN management services for dedicated and reconfigurable circuits network: Leased circuit services.* +- [b-MEF 26.2] MEF 26.2 (2016), *External Network Network Interfaces (ENNI) and Operator Service Attributes.* + +# 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 | +| Computing power networks | 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.8031-201501-I_PDF-E/raw.md b/marked/G/T-REC-G.8031-201501-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f1f9e4bed91a4e1fb18c0f9548761c05d8a9b70a --- /dev/null +++ b/marked/G/T-REC-G.8031-201501-I_PDF-E/raw.md @@ -0,0 +1,3148 @@ + + +**ITU-T** + +**G.8031/Y.1342** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(01/2015) + +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 +AND NEXT-GENERATION NETWORKS + +Internet protocol aspects – Transport + +# --- **Ethernet linear protection switching** + +Recommendation ITU-T G.8031/Y.1342 + +## 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.8031/Y.1342 + +# Ethernet linear protection switching + +# Summary + +Recommendation ITU-T G.8031/Y.1342 describes the specifics of linear protection switching for Ethernet VLAN signals. Included are details pertaining to ETH linear protection characteristics, architectures and the automatic protection switching (APS) protocol. The protection scheme considered in this Recommendation is: + +- VLAN-based Ethernet subnetwork connection linear protection with sublayer monitoring. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|-----------------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.8031/Y.1342 | 2006-06-06 | 15 | 11.1002/1000/8779 | +| 1.1 | ITU-T G.8031/Y.1342 (2006) Amd. 1 | 2007-10-07 | 15 | 11.1002/1000/9174 | +| 1.2 | ITU-T G.8031/Y.1342 (2006) Cor. 1 | 2008-06-06 | 15 | 11.1002/1000/9392 | +| 2.0 | ITU-T G.8031/Y.1342 | 2009-11-13 | 15 | 11.1002/1000/10429 | +| 2.1 | ITU-T G.8031/Y.1342 (2009) Cor. 1 | 2010-09-06 | 15 | 11.1002/1000/10901 | +| 3.0 | ITU-T G.8031/Y.1342 | 2011-06-22 | 15 | 11.1002/1000/11138 | +| 3.1 | ITU-T G.8031/Y.1342 (2011) Cor. 1 | 2012-02-13 | 15 | 11.1002/1000/11513 | +| 3.2 | ITU-T G.8031/Y.1342 (2011) Amd.1 | 2013-08-29 | 15 | 11.1002/1000/12031 | +| 4.0 | ITU-T G.8031/Y.1342 | 2015-01-13 | 15 | 11.1002/1000/12383 | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2015 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|-------|------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 4 | +| 4 | Abbreviations and acronyms ..... | 4 | +| 5 | Conventions ..... | 5 | +| 5.1 | Representation of octets ..... | 5 | +| 6 | Introduction..... | 5 | +| 7 | Network objectives ..... | 6 | +| 8 | Protection characteristics ..... | 7 | +| 8.1 | Monitoring methods and conditions ..... | 7 | +| 9 | Protection group commands ..... | 8 | +| 9.1 | End-to-end commands and states ..... | 8 | +| 9.2 | Local commands..... | 8 | +| 10 | Protection architectures ..... | 8 | +| 10.1 | Unidirectional and bidirectional switching ..... | 9 | +| 10.2 | Need for APS communication..... | 9 | +| 10.3 | Revertive and non-revertive switching..... | 9 | +| 10.4 | Provisioning mismatches..... | 10 | +| 10.5 | Protection switching trigger ..... | 10 | +| 10.6 | Protection switching models..... | 10 | +| 11 | APS Protocol ..... | 17 | +| 11.1 | APS format ..... | 17 | +| 11.2 | 1-phase APS protocol ..... | 19 | +| 11.3 | Request type ..... | 22 | +| 11.4 | Protection types and bridge type ..... | 22 | +| 11.5 | Requested signal ..... | 23 | +| 11.6 | Bridged signal..... | 23 | +| 11.7 | Control of bridge ..... | 23 | +| 11.8 | Control of selector ..... | 23 | +| 11.9 | Signal fail of the protection transport entity ..... | 24 | +| 11.10 | Equal priority requests..... | 24 | +| 11.11 | Command acceptance and retention ..... | 24 | +| 11.12 | Hold-off timer..... | 25 | +| 11.13 | Wait-to-restore timer ..... | 25 | +| 11.14 | Exercise operation ..... | 25 | + +| | Page | +|------------------------------------------------------------------------------------|------| +| 11.15 Failure of protocol defects..... | 26 | +| 11.16 Signal degrade of the protection transport entity ..... | 26 | +| Annex A – State transition tables of protection switching..... | 27 | +| A.1 State transition for 1:1 bidirectional switching with revertive mode ..... | 27 | +| A.2 State transition for 1:1 bidirectional switching with non-revertive mode ..... | 31 | +| A.3 State transition for 1+1 bidirectional switching with revertive mode ..... | 36 | +| A.4 State transition for 1+1 bidirectional switching with non-revertive mode..... | 40 | +| A.5 State transition for 1+1 unidirectional switching with revertive mode ..... | 45 | +| A.6 State transition for 1+1 unidirectional switching with non-revertive mode... | 47 | +| Appendix I – Operation example of 1-phase APS protocol..... | 50 | +| I.1 Introduction ..... | 50 | +| I.2 Example scenario..... | 50 | +| I.3 APS protocol examples ..... | 50 | +| Appendix II – Interaction between Ethernet protection switching and STP..... | 53 | +| Appendix III – MIPs for protection switching environment..... | 55 | +| III.1 Introduction ..... | 55 | +| III.2 Considerations ..... | 55 | +| III.3 Configuration examples..... | 56 | +| Appendix IV – State transition diagrams using SDL..... | 58 | +| IV.1 Introduction ..... | 58 | +| IV.2 SDL diagrams ..... | 58 | + +## Recommendation ITU-T G.8031/Y.1342 + +# Ethernet linear protection switching + +# 1 Scope + +This Recommendation defines the automatic protection switching (APS) protocol and linear protection switching mechanisms for point-to-point VLAN-based ETH subnetwork connection (SNC) in Ethernet transport networks. All other protection schemes including point-to-multipoint and multipoint-to-multipoint are for further study. + +Linear 1+1 and 1:1 protection switching architectures with unidirectional and bidirectional switching are defined in this version of the Recommendation. + +The APS protocol and protection switching operation for all other Ethernet network architectures (e.g., ring, mesh) are for further study. + +# 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.780] Recommendation ITU-T G.780/Y.1351 (2010), *Terms and definitions for synchronous digital hierarchy (SDH) networks*. +- [ITU-T G.805] Recommendation ITU-T G.805 (2000), *Generic functional architecture of transport networks*. +- [ITU-T G.806] Recommendation ITU-T G.806 (2012), *Characteristics of transport equipment – Description methodology and generic functionality, plus Corrigendum 1 (2012)*. +- [ITU-T G.808.1] Recommendation ITU-T G.808.1 (2014), *Generic protection switching – Linear trail and subnetwork protection*. +- [ITU-T G.870] Recommendation ITU-T G.870/Y.1352 (2012), *Terms and definitions for Optical Transport Networks, plus Corrigendum 1 (2013)*. +- [ITU-T G.8010] ITU-T Recommendation G.8010/Y.1306 (2004), *Architecture of Ethernet layer networks, plus Erratum 1 (2007), Erratum 2 (2007), Amendment 1 (2006), Amendment 2 (2010)*. +- [ITU-T G.8013] Recommendation ITU-T G.8013/Y.1731 (2013), *OAM functions and mechanisms for Ethernet based networks, plus Amendment 1 (2015)*. +- [ITU-T G.8021] Recommendation ITU-T G.8021/Y.1341 (2015), *Characteristics of Ethernet transport network equipment functional blocks*. +- [IEEE 802.1Q] IEEE Std 802.1Q™-2014, *IEEE Standard for Local and Metropolitan Area networks–Bridges and Bridged Networks*. + +# **3 Definitions** + +## **3.1 Terms defined elsewhere** + +This Recommendation uses the following terms defined elsewhere: + +- Terms defined in [ITU-T G.780]: + - 3.1.1 bidirectional protection switching** + - 3.1.2 unidirectional protection switching** +- Terms defined in [ITU-T G.805]: + - 3.1.3 adapted information** + - 3.1.4 characteristic information** + - 3.1.5 link** + - 3.1.6 link connection** + - 3.1.7 tandem connection** + - 3.1.8 trail** + - 3.1.9 trail termination** +- Terms defined in [ITU-T G.806]: + - 3.1.10 atomic function** + - 3.1.11 defect** + - 3.1.12 failure** + - 3.1.13 server signal degrade (SSD)** + - 3.1.14 server signal fail (SSF)** + - 3.1.15 signal degrade (SD)** + - 3.1.16 signal fail (SF)** + - 3.1.17 trail signal degrade (TSD)** + - 3.1.18 trail signal fail (TSF)** +- Terms defined in [ITU-T G.808.1]: + - 3.1.19 transfer time (Tt)** +- Terms defined in [ITU-T G.870]: + - 3.1.20 APS protocol** + - 3.1.20.1 1-phase** + - 3.1.21 protection class** + - 3.1.21.1 individual** + - 3.1.21.2 group** + - 3.1.21.3 network connection protection** + - 3.1.21.4 subnetwork connection protection** + - 3.1.21.4.1 sublayer monitored (/S)** + - 3.1.21.4.2 non-intrusive monitored** + - 3.1.21.4.3 inherent monitored** + +- 3.1.21.4.4 test monitored (/T)** +- 3.1.21.5 trail protection** +- 3.1.22 switch** +- 3.1.23 component** +- 3.1.23.1 protected domain** +- 3.1.23.2 bridge** +- 3.1.23.2.1 permanent bridge** +- 3.1.23.2.2 broadcast bridge** +- 3.1.23.2.3 selector bridge** +- 3.1.23.3 selector** +- 3.1.23.3.1 selective selector** +- 3.1.23.4 head end** +- 3.1.23.5 tail end** +- 3.1.23.6 sink node** +- 3.1.23.7 source node** +- 3.1.23.8 intermediate node** +- 3.1.24 architecture** +- 3.1.24.1 1+1 protection architecture** +- 3.1.24.2 1:n protection architecture** +- 3.1.24.3 (1:1)n protection architecture** +- 3.1.25 signal** +- 3.1.25.1 traffic signal** +- 3.1.25.2 normal traffic signal** +- 3.1.25.3 extra traffic signal** +- 3.1.25.4 null signal** +- 3.1.26 time** +- 3.1.26.1 detection time** +- 3.1.26.2 hold-off time** +- 3.1.26.3 wait-to-restore time** +- 3.1.26.4 switching time** +- 3.1.27 transport entity** +- 3.1.27.1 protection transport entity** +- 3.1.27.2 working transport entity** +- 3.1.27.3 active transport entity** +- 3.1.27.4 standby transport entity** +- 3.1.28 protection** +- 3.1.29 impairment** + +- 3.1.30 protection ratio** +- 3.1.31 revertive (protection) operation** +- 3.1.32 non-revertive (protection) operation** +- Terms defined in [ITU-T G.8010]: +- 3.1.33 Ethernet characteristic information (ETH\_CI)** +- 3.1.34 Ethernet flow point (ETH\_FP)** +- 3.1.35 maintenance entity** +- 3.1.36 maintenance entity group** +- 3.1.37 maintenance entity group end point (MEP)** +- 3.1.38 maintenance entity group level** +- Terms defined in [ITU-T G.8021]: +- 3.1.39 Ethernet flow forwarding function (ETH\_FF)** + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------|--------------------------------------------------| +| AI | Adapted Information | +| APS | Automatic Protection Switching | +| CCM | Continuity Check Message | +| CI | Characteristic Information | +| DNR | Do Not Revert | +| EC | Ethernet Connection | +| ETH | Ethernet layer network | +| ETH-AIS | Ethernet Alarm Indication Signal function | +| ETH-APS | Ethernet Automatic Protection Switching function | +| ETH-CC | Ethernet Continuity Check function | +| EXER | Exercise | +| FS | Forced Switch | +| FT | Flow Termination | +| LCK | Locked | +| LO | Lockout of protection | +| LOC | Loss of Continuity | +| LSB | Least Significant Bit | +| MEP | Maintenance Entity Group End Point | +| MI | Management Information | +| MIP | Maintenance Entity Group Intermediate Point | + +| | | +|-------|-----------------------------------------------------| +| MS | Manual Switch | +| MSB | Most Significant Bit | +| NR | No Request | +| OAM | Operation, Administration and Maintenance | +| PDU | Protocol Data Unit | +| PS | Protection Switching | +| RR | Reverse Request | +| RSTP | Rapid Spanning Tree Protocol | +| SD | Signal Degrade | +| SF | Signal Fail | +| SF-P | Signal Fail on Protection | +| SNC | Subnetwork Connection | +| SNC/I | Subnetwork Connection with Inherent monitoring | +| SNC/N | Subnetwork Connection with Non-intrusive monitoring | +| SNC/S | Subnetwork Connection with Sublayer monitoring | +| SNC/T | Subnetwork Connection with Test trail monitoring | +| STP | Spanning Tree Protocol | +| TCM | Tandem Connection Monitoring | +| TLV | Type Length Value | +| VID | VLAN Identifier | +| VLAN | Virtual Local Area Network | +| WTR | Wait-to-Restore | + +# 5 Conventions + +## 5.1 Representation of octets + +Octets are represented as defined in [IEEE 802.1Q]. + +When consecutive octets are used to represent a binary number, the lower octet number has the most significant value. + +The bits in an octet are numbered from 1 to 8, where 1 is the least significant bit (LSB) and 8 is the most significant bit (MSB). + +# 6 Introduction + +This Recommendation specifies linear protection switching mechanisms to be applied to virtual local area network (VLAN)-based Ethernet networks as described in [ITU-T G.8010]. Protection switching is a fully allocated survivability mechanism. It is fully allocated in the sense that the route and bandwidth of the protection entity is reserved for a selected working entity. It provides a fast and simple survivability mechanism. It is easier for the network operator to grasp the status of the network (e.g., active network topology) with a protection switching than with other survivability mechanisms such as rapid spanning tree protocol (RSTP). + +This Recommendation specifies linear 1+1 protection switching architecture and linear 1:1 protection switching architecture. The linear 1+1 protection switching architecture operates with either unidirectional or bidirectional switching. The linear 1:1 protection switching architecture operates with bidirectional switching. + +In the linear 1+1 protection switching architecture, a protection transport entity is dedicated to each working transport entity. The normal traffic signal is copied and fed to both working and protection transport entities with a permanent bridge at the source of the protected domain. The traffic on working and protection transport entities is transmitted simultaneously to the sink of the protected domain, where a selection between the working and protection transport entities is made based on some predetermined criteria, such as server defect indication. + +Although selection is made only at the sink of the protected domain in linear 1+1 protection switching architecture, bidirectional linear 1+1 protection switching needs APS coordination protocol so that selectors for both direction selects the same entity. On the other hand, unidirectional linear 1+1 protection switching does not need APS coordination protocol. + +In the linear 1:1 protection switching architecture, the protection transport entity is dedicated to the working transport entity. However, the normal traffic signal is transported either on the working transport entity or on the protection transport entity using a selector bridge at the source of the protected domain. Alternatively, when using a broadcast bridge at the source of the protected domain, the normal traffic signal is transported on the working transport entity in normal condition, and is copied and fed to both working and protection transport entities when protection switching is triggered by any valid request. In both cases, the selector at the sink of the protected domain selects the entity which carries the normal traffic signal as indicated via the requested signal (see clause 11.8). Since source and sink need to be coordinated to ensure that the bridge at the source (either selector or broadcast) and the selector at the sink select the same entity, APS coordination protocol is necessary. (Additional details about using a selector or broadcast bridge are provided in clause 10.6.3). + +# 7 Network objectives + +- 1) Ethernet linear protection switching should be applicable to point-to-point VLAN-based ETH SNCs, which provides connectivity between two ETH flow points in an ETH flow domain. VLAN identifiers (VIDs) can be used to identify point-to-point VLAN-based ETH SNC(s) within ETH links. Additional details on ETH and related atomic functions can be obtained from [ITU-T G.8021] and [ITU-T G.8010]. Other entities to be protected are for further study. +- 2) The protected domain should be configured such that 100 per cent of the impaired normal traffic signal should be protected for a failure on a single working entity. +- 3) Transfer time (Tt) should be less than 50 ms. +- 4) The ETH layer connectivity of working transport entity and protection transport entity should be periodically monitored. +- 5) Subsequent to a protection switching event, frames should be delivered in order. + +NOTE – Subsequent to a protection switching event, frames may temporarily be lost or duplicated due to differential path delay. + +- 6) Individual and group protection switching should be supported. +- 7) Revertive and non-revertive switching should be provided as network operator options. +- 8) A mismatch between the bridge/selector positions of the near end and the far end should be detected. + - The bridge/selector mismatch for the local network element should be detected and reported. + +- The bridge/selector mismatch should be cleared by a network operator. +- 9) Operator requests such as lockout of protection (LO), forced switch (FS) and manual switch (MS) commands should be supported. +- 10) Prioritized protection between signal fail (SF) and operator requests should be supported. +- 11) A provisionable "generic hold-off function" should be provided so as to delay the beginning of the protection switching action. + +# 8 Protection characteristics + +## 8.1 Monitoring methods and conditions + +Protection switching will occur based on the detection of certain defects on the transport entities (working and protection) within the protected domain. How these defects are detected is the subject of the equipment Recommendations (e.g., [ITU-T G.8021]). For the purpose of the protection switching process, a transport entity within the protected domain has a condition of OK, failed (signal fail = SF), or degraded (signal degrade = SD) if applicable. + +The customary monitoring methods are as follows: + +**Inherent** – Inherent monitoring is based on defects detected by a trail termination function or adaptation function at the tail end. Ethernet subnetwork connection with inherent monitoring (SNC/I) is based on inherent monitoring. + +**Non-intrusive** – Protection switching is triggered by a non-intrusive monitor at the tail end of the protection group. This allows protecting a segment of a trail that is not constrained by the beginning or end of the trail. Ethernet subnetwork connection with non-intrusive monitoring (SNC/N) is a linear protection based on non-intrusive monitoring. Non-intrusive monitoring may be based on monitoring of a layer or sublayer (e.g., tandem connection monitoring (TCM) non-intrusive monitoring). + +**Sublayer** – Ethernet subnetwork connection with sublayer monitoring (SNC/S) is a linear protection architecture based on sublayer monitoring. Each serial compound link connection is extended with TCM or segment termination/adaptation functions to derive the fault condition status independent of the traffic signal present. For network layers supporting TCM, it is attractive to instantiate a TCM-monitored segment of a trail precisely across a protected segment so that protection switching is based only on defects within the protected segment. This has a further advantage over SNC/N in that defects that occur upstream of the protected segment will not be visible for the purpose of protection switching. + +**Test trail** – Defects are detected using extra test trail. An extra test trail is set up between source and sink of the protected domain, which includes a protection group of subnetwork connections. Ethernet subnetwork connection with test trail monitoring (SNC/T) is based on test trail monitoring that is applicable for group protection only. + +The protection switching controller does not care which monitoring method is used, as long as it can be given (OK, SF, SD if applicable) information for the transport entities within the protected domain. Some monitors or network layers may not have an SD detection method. Where this is the case, there is no need to use a different APS protocol: it would simply happen that an SD would not be issued from equipment that cannot detect it. Where an APS protocol is used, the implementation should not preclude the far end from declaring an SD over the APS protocol, even if the monitor at the near end cannot detect SD. + +In this version of the Recommendation, SNC/S monitoring architecture is supported for point-to-point VLAN-based ETH SNC. Other monitoring methods such as SNC/I, SNC/N and SNC/T are for further study. + +# 9 Protection group commands + +## 9.1 End-to-end commands and states + +This clause describes commands that apply to the protection group as a whole. When an APS protocol is present, these commands are signalled to the far end of the connection. In bidirectional switching, these commands affect the bridge and selector at both ends. + +**Lockout of protection** – This command prevents a working signal from being selected from the protection transport entity. This effectively disables the protection group. + +**Force switch normal traffic signal-to-protection** – Forces normal traffic signal to be selected from the protection transport entity. + +**Manual switch normal traffic signal-to-protection** – In the absence of a failure of a working or protection transport entity, forces normal traffic signal to be selected from the protection transport entity. + +**Manual switch normal traffic signal-to-working** – In the absence of a failure of a working or protection transport entity in non-revertive operation, forces normal traffic signal to be selected from the working transport entity. + +**Wait-to-restore normal traffic signal** – In revertive operation, after the clearing of a SF (or SD if applicable) on the working transport entity, maintains normal traffic signal as selected from the protection transport entity until a wait-to-restore timer expires. The state will be changed to NR if the timer expires prior to any other event or command. This is used to prevent frequent operation of the selector in the case of intermittent failures. + +**Exercise signal** – Exercise of the APS protocol. The signal is chosen so as not to modify the selector. + +**Do-not-revert normal traffic signal** – In non-revertive operation, this is used to maintain a normal traffic signal selected from the protection transport entity. + +**No request** – No request (NR) is the state entered by the local priority under all conditions where no local protection switching requests (including wait-to-restore and do not revert) are active. Normal traffic signal is selected from the corresponding transport entity. + +**Clear** – Clears the active near-end LO, FS, MS, wait-to-restore (WTR) state, or Exercise command. + +## 9.2 Local commands + +These commands apply only to the near end of the protection group. Even when an APS protocol is supported, they are not signalled to the far end. + +**Freeze** – Freezes the state of the protection group. Until the freeze is cleared, additional near-end commands are rejected. Condition changes and received APS information are ignored. When the Freeze command is cleared, the state of the protection group is recomputed based on the condition and received APS information. + +**Clear freeze** – Clears the active near-end Freeze command. + +# 10 Protection architectures + +In the linear protection architecture defined in this version of the Recommendation, protection switching occurs at the two distinct endpoints of a point-to-point VLAN-based ETH SNC. Between these endpoints, there will be both "working" and "protection" transport entities. + +For a given direction of transmission, the "head end" of the protected entity is capable of performing a bridge function, which will place a copy of a normal traffic signal onto a protection transport entity when required. The "tail end" will perform a selector function, where it is capable of selecting a normal traffic signal either from its usual working transport entity, or from a protection transport + +entity. In the case of bidirectional transmission, where both directions of transmission are protected, both ends of the protected entity will normally provide both bridge and selector functions. + +The following architectures are possible: + +**1+1** – In 1+1 architectures, a protection transport entity is employed to protect the normal traffic signal. At the head end, the bridge is permanent. Switching occurs exclusively at the tail end. + +**1:1** – In 1:1 architectures, a protection transport entity is employed to protect the normal traffic signal. At the head end, the bridge is not established until a protection switch is required. + +The architecture at each end of the protected domain must match. + +## **10.1 Unidirectional and bidirectional switching** + +In the case of bidirectional transmission, it is possible to choose either unidirectional or bidirectional switching. With unidirectional switching, the selectors at each end are fully independent. With bidirectional switching, an attempt is made to coordinate the two ends so that both have the same bridge and selector settings, even for a unidirectional failure. Bidirectional switching always requires APS information to coordinate the two endpoints. Unidirectional switching can protect two unidirectional failures (or degradations, if applicable) in opposite directions on different entities. + +## **10.2 Need for APS communication** + +The only switching type that does NOT require APS communication is 1+1 unidirectional switching. With a permanent bridge at the head end and no need to coordinate selector positions at the two ends, the tail end selector can be operated entirely according to defects and commands received at the tail end. + +Bidirectional switching always requires APS communication. + +## **10.3 Revertive and non-revertive switching** + +In revertive operation, normal traffic signal is restored to the working transport entity after the condition(s) causing a switch has cleared. In the case of clearing a command (e.g., Forced switch), this happens immediately. In the case of clearing of a defect, this generally happens after the expiry of a WTR timer, which is used to avoid chattering of selectors in the case of intermittent defects. + +In non-revertive operation, normal traffic signal is allowed to remain on the protection transport entity even after a switch reason has cleared. This is generally accomplished by replacing the previous switch request with a do not revert (DNR) request, which is low priority. + +1+1 protection is often provisioned as non-revertive operation, as the protection is fully dedicated in any case, and this avoids a second "glitch" to the normal traffic signal. There may, however, be reasons to provision this to be revertive operation (e.g., so that the normal traffic signal uses the "short" path except during failure conditions. Certain operator policies also dictate revertive operation even for 1+1). + +1:1 protection is usually revertive operation. Although it is possible to define the protocol in a way that would permit non-revertive operation for 1:1 protection, however, since the working transport entity is typically more optimized (i.e., from a delay and resourcing perspective) than the protection transport entity, it is better to revert and glitch the normal traffic signal when the working transport entity is repaired. + +In general, the choice of revertive/non-revertive operation will be the same at both ends of the protection group. However, a mismatch of this parameter does not prevent interworking; it just would be peculiar for one side to go to WTR for clearing of switches initiated from that side, while the other goes to DNR for its switches. + +Revertive/non-revertive operation of an SNC/S protection switching process shall be configured via ETH\_C\_MI\_PS\_OperType. + +## **10.4 Provisioning mismatches** + +With all of the options for provisioning of protection groups, there are opportunities for mismatches between the provisioning at the two ends. These provisioning mismatches take one of the following forms: + +- a) Mismatches where proper operation is not possible; +- b) Mismatches where one or both sides can adapt their operation to provide a degree of interworking in spite of the mismatch; +- c) Mismatches that do not prevent interworking. An example is the revertive/non-revertive mismatch discussed in clauses 10.3 and 11.4. + +Not all provisioning mismatches can be conveyed and detected by information passed through the APS communication. There are simply too many combinations of valid entity numbers to easily provide full visibility of all of the configuration options. What is desirable, however, is to provide visibility for the middle category, where the sides can adapt their operation to interwork in spite of the mismatch. For example, an equipment provisioned for bidirectional switching could fall back to unidirectional switching to allow interworking. An equipment provisioned for 1+1 switching with an APS communication could fall back to operate in 1+1 unidirectional switching without an APS communication. The user could still be informed of the provisioning mismatch, but a level of protection could still be provided by the equipment. + +## **10.5 Protection switching trigger** + +For example, protection switching should be performed when: + +- a) Initiated by operator control (e.g., FS, MS) if it has a higher priority than any other local request or the far-end request; or +- b) SF is declared on the active transport entity and is not declared on the standby transport entity, and the detected SF condition has a higher priority than any other local request or the far-end request; or +- c) SD is declared on the active transport entity and is not declared on the standby transport entity, and the detected SD condition has a higher priority than any other local request or the far-end request; or +- d) In the bidirectional 1+1 and 1:1 architecture, the received APS protocol requests to switch and it has a higher priority than any other local request. + +Other cases are described as state transition in Annex A. + +### **10.5.1 Signal fail declaration conditions** + +SF is declared when ETH trail signal fail condition is detected. ETH trail signal fail is specified in [ITU-T G.8021]. + +### **10.5.2 Signal degrade declaration conditions** + +SD is declared when ETH trail signal degrade condition is detected. ETH trail signal degrade is specified in [ITU-T G.8021]. + +## **10.6 Protection switching models** + +Figure 10-1 depicts an example of the VLAN-based ETH SNC/S protection switching models defined in this Recommendation. Other network scenarios are permissible. + +Within the ETH connection function (ETH\_C) an ETH SNC protection switching process is instantiated to protect the ETH connection (EC). When protection switching is configured for an EC, i.e., the protected ETH SNC, it is defined between two ETH flow points (ETH\_FPs) as depicted in Figure 10-1. Each instantiated SNC protection switching process determines the specific output ETH\_FP over which the protected ETH\_CI is transferred. + +For example, in the case of 1:1 protection switching configuration, ETH\_CI for the protected ETH can be forwarded to either working or protection transport entities by the instantiated ETH SNC protection switching process within the ETH\_C. + +![Diagram of ETH SNC/S protection switching architecture showing two protected paths, ETH#A and ETH#B, between a WEST side and EAST#1/EAST#2 sides. Each path has a working transport entity (solid line) and a protection transport entity (dashed line). The diagram includes labels for ETH_C, ETH_FP, and SNC protection switching process.](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +The diagram illustrates the ETH SNC/S protection switching architecture. It shows two protected paths, ETH#A and ETH#B, between a WEST side and EAST#1/EAST#2 sides. Each path consists of a working transport entity (solid line) and a protection transport entity (dashed line). The WEST side features two ETH\_C blocks, each with an associated SNC protection switching process. The EAST#1 and EAST#2 sides also feature ETH\_C blocks with associated SNC protection switching processes. The diagram includes labels for ETH\_FP (Ethernet Flow Point), ETH\_C (Ethernet Connection), and the specific transport entities. A legend at the bottom left shows the ETH\_FP symbol. The diagram is labeled G.8031-Y.1342(15)\_F10-1. + +Diagram of ETH SNC/S protection switching architecture showing two protected paths, ETH#A and ETH#B, between a WEST side and EAST#1/EAST#2 sides. Each path has a working transport entity (solid line) and a protection transport entity (dashed line). The diagram includes labels for ETH\_C, ETH\_FP, and SNC protection switching process. + +**Figure 10-1 – ETH SNC/S protection switching architecture** + +Working and protection transport entities for an SNC protection switching process shall be configured via ETH\_C\_MI\_PS\_WorkingPortId and ETH\_C\_MI\_PS\_ProtectionPortId. + +Since the protection switching mechanism requires monitoring for both working and protection transport entities, it is required that maintenance entity group end points (MEPs) be activated for the purpose of monitoring the working and protection transport entities. Both transport entities are monitored by individually exchanging continuity check message (CCM) defined in [ITU-T G.8013] as shown in Figure 10-2. + +![Diagram of MEPs in ETH SNC/S protection switching architecture. The diagram shows a 'Protected ETH SNC' spanning 'WEST' and 'EAST' sides. On the WEST side, an 'SNC protection switching process' is connected to 'ETH_C', which is connected to 'ETH_FP'. The 'ETH_C' connects to a 'MEP' block. Inside the 'MEP' block, there are two transport entities: a 'Working transport entity' with 'CCM' and a 'Protection transport entity' with 'CCM, APS'. The 'MEP' block connects to the 'EAST' side. On the 'EAST' side, another 'MEP' block receives the transport entities and connects to 'ETH_C', which is connected to 'ETH_FP'. The 'ETH_C' connects to the 'SNC protection switching process'. The diagram is labeled 'G.8031-Y.1342(15)_F10-2'.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +Diagram of MEPs in ETH SNC/S protection switching architecture. The diagram shows a 'Protected ETH SNC' spanning 'WEST' and 'EAST' sides. On the WEST side, an 'SNC protection switching process' is connected to 'ETH\_C', which is connected to 'ETH\_FP'. The 'ETH\_C' connects to a 'MEP' block. Inside the 'MEP' block, there are two transport entities: a 'Working transport entity' with 'CCM' and a 'Protection transport entity' with 'CCM, APS'. The 'MEP' block connects to the 'EAST' side. On the 'EAST' side, another 'MEP' block receives the transport entities and connects to 'ETH\_C', which is connected to 'ETH\_FP'. The 'ETH\_C' connects to the 'SNC protection switching process'. The diagram is labeled 'G.8031-Y.1342(15)\_F10-2'. + +**Figure 10-2 – MEPs in ETH SNC/S protection switching architecture** + +The protection switching process also requires APS communication in order to coordinate its switching behaviour with the other end of the protected domain if the protection switching architecture is not 1+1 unidirectional protection switching. APS protocol data unit (PDU) is transmitted and received between the same MEP pair on the protection transport entity where CCM is transmitted for the monitoring. + +APS information and defect condition which are terminated/detected by MEP sink function can be input to the protection switching process as shown in Figure 10-3. + +If a MEP detects an anomaly, which contributes to a SF (or SD if applicable) defect condition, it will inform the protection switching process that a failure condition has been detected. Termination of the CCM and locked (LCK) (which are defined in [ITU-T G.8013]) is done by the ETH\_FT atomic function. If the ETH\_FT detects a failure condition, an ETH\_AI\_TSF (or ETH\_AI\_TSD if applicable) is signalled to the ETH(x) to ETH adaptation sink (ETH(x)/ETH\_A\_Sk) which subsequently generates an ETH\_CI\_SSF (or ETH\_CI\_SSD if applicable). The ETH(x)/ETH adaptation function employs this ETH\_CI\_SSF (or ETH\_CI\_SSD if applicable) to notify the ETH SNC protection switching process within ETH\_C of the failure condition. + +The APS PDU is terminated by the ETH(x)/ETH\_A\_Sk function within the MEP. The ETH(x)/ETH\_A\_Sk function then extracts the APS-specific information from the received APS PDU, and then transfers it to the ETH SNC protection switching process as the APS characteristic information (ETH\_CI\_APS). + +The protection switching process determines the new switching state after it receives ETH\_CI\_SSF (or ETH\_CI\_SSD if applicable) or ETH\_CI\_APS, and then it determines the specific output ETH\_FP over which the protected ETH\_CI is transferred as necessary. + +It is noted that the administrative state of the ETH(x)/ETH adaptation function for both working and protection transport entities shall not be locked. + +![Figure 10-3: Behaviours of both MEPs and SNC protection switching process in ETH SNC/S protection switching architecture. The diagram shows a detailed internal structure of an Ethernet node. On the left, an 'ETH_C' interface is connected to an 'SNC protection switching process' block. This block is also connected to 'ETH_MI_PS_*' and 'ETH_CI_APS' inputs. The 'SNC protection switching process' has two output paths: one labeled 'Working transport entity' and another labeled 'Protection transport entity'. Both paths pass through a series of processing blocks including 'ETH/ETH', 'LCK', 'CCM', 'AI_TSF', and 'AI_TSD'. The 'Working transport entity' path ends at an 'ETHD' block, while the 'Protection transport entity' path ends at an 'ETHD' block. The entire internal structure is enclosed in a box labeled 'MEP' at the top. A reference code 'G.8031-Y.1342(15)_F10-3' is visible in the bottom right corner of the diagram area.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +Figure 10-3: Behaviours of both MEPs and SNC protection switching process in ETH SNC/S protection switching architecture. The diagram shows a detailed internal structure of an Ethernet node. On the left, an 'ETH\_C' interface is connected to an 'SNC protection switching process' block. This block is also connected to 'ETH\_MI\_PS\_\*' and 'ETH\_CI\_APS' inputs. The 'SNC protection switching process' has two output paths: one labeled 'Working transport entity' and another labeled 'Protection transport entity'. Both paths pass through a series of processing blocks including 'ETH/ETH', 'LCK', 'CCM', 'AI\_TSF', and 'AI\_TSD'. The 'Working transport entity' path ends at an 'ETHD' block, while the 'Protection transport entity' path ends at an 'ETHD' block. The entire internal structure is enclosed in a box labeled 'MEP' at the top. A reference code 'G.8031-Y.1342(15)\_F10-3' is visible in the bottom right corner of the diagram area. + +**Figure 10-3 – Behaviours of both MEPs and SNC protection switching process in ETH SNC/S protection switching architecture** + +SNC/S protection is not only limited to subnetwork connections; it is also possible to extend this protection mechanism to support a single link connection as well as network connections. + +### 10.6.1 1+1 bidirectional protection switching + +Figure 10-4 illustrates the 1+1 bidirectional linear protection switching architecture. The protected ETH\_CI traffic is permanently bridged to both the working transport entity and the protection transport entity. In this figure, the traffic is shown as being received via the ETH\_C only from the working entity. Figure 10-5 illustrates a situation where a protection switching has occurred due to a signal fail (or signal degrade) condition on the working transport entity. It should be noted that both directions are switched even when a unidirectional defect occurs. For this purpose, APS coordination protocol is necessary. + +![Figure 10-4: 1+1 bidirectional protection switching architecture. The diagram shows a linear protection setup between two nodes, 'WEST' and 'EAST', under the heading 'Protected ETH#A SNC'. At the 'WEST' node, 'ETH_C' and 'ETH_FP' interfaces are shown. The 'ETH_C' is connected to an 'SNC protection switching process' block. This block is connected to two parallel transport entities: 'Working transport entity (for ETH#A)' and 'Protection transport entity (for ETH#A)'. Both entities carry 'ETH#A (Normal traffic)'. The traffic from the working entity is shown being received by the 'ETH_C' interface. At the 'EAST' node, the traffic from both transport entities is shown being received by the 'ETH_C' interface, which is connected to its own 'SNC protection switching process' block. A reference code 'G.8031-Y.1342(15)_F10-4' is visible in the bottom right corner of the diagram area.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +Figure 10-4: 1+1 bidirectional protection switching architecture. The diagram shows a linear protection setup between two nodes, 'WEST' and 'EAST', under the heading 'Protected ETH#A SNC'. At the 'WEST' node, 'ETH\_C' and 'ETH\_FP' interfaces are shown. The 'ETH\_C' is connected to an 'SNC protection switching process' block. This block is connected to two parallel transport entities: 'Working transport entity (for ETH#A)' and 'Protection transport entity (for ETH#A)'. Both entities carry 'ETH#A (Normal traffic)'. The traffic from the working entity is shown being received by the 'ETH\_C' interface. At the 'EAST' node, the traffic from both transport entities is shown being received by the 'ETH\_C' interface, which is connected to its own 'SNC protection switching process' block. A reference code 'G.8031-Y.1342(15)\_F10-4' is visible in the bottom right corner of the diagram area. + +**Figure 10-4 – 1+1 bidirectional protection switching architecture** + +![Diagram of 1+1 bidirectional protection switching architecture showing a signal fail condition on the working entity.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +The diagram illustrates a 1+1 bidirectional protection switching architecture for ETH#A SNC. It is divided into WEST and EAST domains by a central protected domain. In the WEST domain, traffic enters from the left, passes through an ETH\_FP (represented by two hexagons), then an ETH\_C (represented by a circle). The traffic is split into two transport entities: a 'Working transport entity (for ETH#A)' and a 'Protection transport entity (for ETH#A)'. The working entity is shown with a red 'X' over its path, indicating a signal fail or degrade condition. The protection entity is shown with a solid line. Both entities rejoin at the EAST domain, pass through another ETH\_C, and exit to the right through another ETH\_FP. Labels include 'Protected ETH#A SNC', 'WEST', 'EAST', 'ETH#A (Normal traffic)', 'Working transport entity (for ETH#A)', 'Protection transport entity (for ETH#A)', 'SNC protection switching process', 'ETH\_C', 'ETH\_FP', and a reference code 'G.8031-Y.1342(15)\_F10-5'. + +Diagram of 1+1 bidirectional protection switching architecture showing a signal fail condition on the working entity. + +**Figure 10-5 – 1+1 bidirectional protection switching architecture – +Signal fail (or signal degrade) condition for working entity** + +The ability of an SNC protection switching process to trigger protection switching upon SD shall be configured via ETH\_C\_MI\_PS\_SD\_Protection. ETH\_C\_MI\_PS\_SD\_Protection accepts the values enabled and disabled. The default value of ETH\_C\_MI\_PS\_SD\_Protection shall be disabled. + +NOTE – ETH\_C\_MI\_PS\_SD\_Protection is recommended to be set to enabled only when both ends can trigger protection switching upon SD. + +### 10.6.2 1+1 unidirectional protection switching + +Figure 10-6 illustrates the 1+1 unidirectional linear protection switching architecture. The protected ETH\_CI traffic is permanently bridged to both the working transport entity and the protection transport entity. In this figure, the traffic is shown as being received via the ETH\_C only from the working entity for both directions. Figure 10-7 illustrates a situation where a protection switching has occurred due to a signal fail (or signal degrade) condition on the working transport entity in the west-to-east direction. The normal traffic signal in the east-to-west direction continues to be received via the working transport entity. In unidirectional protection switching, each direction is switched independently. Selectors at the sink of the protected domain operate only based on the local information. For this purpose, APS coordination protocol is not necessary. + +Figure 10-8 illustrates a case where signal fail (or signal degrade) condition exists on the working transport entity in the west-to-east direction and on the protection transport entity in the east-to-west direction. Unidirectional protection switching can protect this type of double defect scenarios while bidirectional protection switching cannot. + +![Figure 10-6: 1+1 unidirectional protection switching architecture diagram. It shows a 'Protected ETH#A SNC' spanning 'WEST' and 'EAST' nodes. In the WEST node, traffic enters an 'ETH_C' component, which is controlled by an 'SNC protection switching process'. The traffic is split into two paths: a 'Working transport entity (for ETH#A)' and a 'Protection transport entity (for ETH#A)'. Both paths carry 'ETH#A (Normal traffic)' and are connected to 'ETH_FP' (represented by two hexagons). The paths rejoin at the EAST node's 'ETH_C' component, which is also controlled by an 'SNC protection switching process', and exit as 'ETH#A (Normal traffic)'. Reference G.8031-Y.1342(15)_F10-6 is shown.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Figure 10-6: 1+1 unidirectional protection switching architecture diagram. It shows a 'Protected ETH#A SNC' spanning 'WEST' and 'EAST' nodes. In the WEST node, traffic enters an 'ETH\_C' component, which is controlled by an 'SNC protection switching process'. The traffic is split into two paths: a 'Working transport entity (for ETH#A)' and a 'Protection transport entity (for ETH#A)'. Both paths carry 'ETH#A (Normal traffic)' and are connected to 'ETH\_FP' (represented by two hexagons). The paths rejoin at the EAST node's 'ETH\_C' component, which is also controlled by an 'SNC protection switching process', and exit as 'ETH#A (Normal traffic)'. Reference G.8031-Y.1342(15)\_F10-6 is shown. + +**Figure 10-6 – 1+1 unidirectional protection switching architecture** + +![Figure 10-7: 1+1 unidirectional protection switching architecture diagram showing a signal fail condition. This diagram is similar to Figure 10-6, but the 'Working transport entity (for ETH#A)' path in the WEST node has a red 'X' over it, indicating a signal fail or degrade condition for the west-to-east direction. The protection path remains active. Reference G.8031-Y.1342(15)_F10-7 is shown.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +Figure 10-7: 1+1 unidirectional protection switching architecture diagram showing a signal fail condition. This diagram is similar to Figure 10-6, but the 'Working transport entity (for ETH#A)' path in the WEST node has a red 'X' over it, indicating a signal fail or degrade condition for the west-to-east direction. The protection path remains active. Reference G.8031-Y.1342(15)\_F10-7 is shown. + +**Figure 10-7 – 1+1 unidirectional protection switching architecture – Signal fail (or signal degrade) condition for working transport entity in the west-to-east direction** + +![Figure 10-8: 1+1 unidirectional protection switching architecture diagram showing signal fail conditions in both directions. This diagram is similar to Figure 10-6, but both the 'Working transport entity (for ETH#A)' and the 'Protection transport entity (for ETH#A)' paths in the WEST node have red 'X' marks over them, indicating signal fail or degrade conditions in both directions. Reference G.8031-Y.1342(15)_F10-8 is shown.](a3472689858b068ef469213682965325_img.jpg) + +Figure 10-8: 1+1 unidirectional protection switching architecture diagram showing signal fail conditions in both directions. This diagram is similar to Figure 10-6, but both the 'Working transport entity (for ETH#A)' and the 'Protection transport entity (for ETH#A)' paths in the WEST node have red 'X' marks over them, indicating signal fail or degrade conditions in both directions. Reference G.8031-Y.1342(15)\_F10-8 is shown. + +**Figure 10-8 – 1+1 unidirectional protection switching architecture – Signal fail (or signal degrade) condition in both directions** + +### 10.6.3 1:1 bidirectional protection switching + +1:1 SNC protection switching can be supported either by a selector bridge or by a broadcast bridge. The type of bridge used for 1:1 SNC protection switching (selector or broadcast) shall be configured + +via ETH\_C\_MI\_PS\_BridgeType. ETH\_C\_MI\_PS\_BridgeType accepts the values 0 (selector bridge) and 1 (broadcast bridge). The default value of ETH\_C\_MI\_PS\_BridgeType shall be 0. In the current version of this Recommendation the selector bridge does not support protection against SD while the broadcast bridge does. + +NOTE – Broadcast bridge is recommended to be used in revertive mode only. + +Figure 10-9 illustrates the 1:1 linear protection switching architecture, with the normal traffic signal (ETH#A) being transmitted via the working transport entity. This Figure 10-9 is applicable to both types of bridges (selector or broadcast). + +Figure 10-10 illustrates a situation where a protection switch has occurred, due to a signal fail condition on the working transport entity. A selector bridge is used at the source node where the normal traffic signal (ETH#A) is forwarded to the protection transport entity. At the sink node, the normal traffic signal (ETH#A) is received from the protection transport entity. + +Figure 10-11 illustrates a situation where a protection switch has occurred, due to a signal degrade condition on the working transport entity declared as specified in clause 10.5.2. As the ETH trail signal degrade condition detection specified in clause 10.5.2 depends on the presence of normal traffic signal, such condition declared on the working transport entity would be cleared following protection switching to the protection transport entity if a selector bridge is used, possibly resulting in flapping. To avoid flapping, a broadcast bridge is used at the source node where the normal traffic signal (ETH#A) is forwarded to both the working transport entity and protection transport entity. At the sink node, the normal traffic signal (ETH#A) is received from the protection transport entity. + +During the protection switching operation, transient mismatch between bridge/selector positions at both ends of the protected domain is possible. However, misconnection between ETH\_CI for ETH#A and other ETH\_CI is not possible because traffic is always forwarded correctly through the ETH\_C, based on the VID. Note that in order to achieve this forwarding behaviour, different VID must be configured on the protection transport entity for the protected ETH#A and the non-protected ETH traffic. + +The forwarding of traffic according to the VID in the ETH\_C function means that for 1:1 architectures, traffic misconnections are never possible. This greatly simplifies the functionality of the protection switching protocol, enabling a 1-phase protocol to be used, with only a single information exchange being required between both ends to complete a bidirectional switching. + +![Diagram of 1:1 protection switching architecture showing WEST and EAST nodes connected by a Protected ETH#A SNC. The diagram illustrates the flow of normal traffic (ETH#A) through the working transport entity and the null signal through the protection transport entity. Labels include: WEST, EAST, Protected ETH#A SNC, ETH#A (Normal traffic), Working transport entity (for ETH#A), ETH#A (Null signal), Protection transport entity (for ETH#A), ETH_C, ETH_FP, and SNC protection switching process. A legend at the bottom left shows the ETH_FP symbol.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +The diagram illustrates the 1:1 protection switching architecture. It shows two nodes, WEST and EAST, connected by a Protected ETH#A SNC. At the WEST node, the normal traffic signal (ETH#A) is transmitted via the working transport entity, and a null signal is transmitted via the protection transport entity. At the EAST node, the normal traffic signal (ETH#A) is received from the working transport entity, and the null signal is received from the protection transport entity. The diagram also shows the ETH\_C and ETH\_FP components, and the SNC protection switching process. A legend at the bottom left shows the ETH\_FP symbol. + +Diagram of 1:1 protection switching architecture showing WEST and EAST nodes connected by a Protected ETH#A SNC. The diagram illustrates the flow of normal traffic (ETH#A) through the working transport entity and the null signal through the protection transport entity. Labels include: WEST, EAST, Protected ETH#A SNC, ETH#A (Normal traffic), Working transport entity (for ETH#A), ETH#A (Null signal), Protection transport entity (for ETH#A), ETH\_C, ETH\_FP, and SNC protection switching process. A legend at the bottom left shows the ETH\_FP symbol. + +Figure 10-9 – 1:1 protection switching architecture + +![Figure 10-10: 1:1 protection switching architecture (with selector bridge) – Signal fail condition for working transport entity. The diagram shows a 'Protected ETH#A SNC' spanning 'WEST' and 'EAST' nodes. In the WEST node, a dashed line labeled 'ETH#A (Null signal)' is shown with a large 'X' over it, indicating a signal failure. Below it, a solid line labeled 'Working transport entity (for ETH#A)' and 'ETH#A (Normal traffic)' is shown. A solid line labeled 'Protection transport entity (for ETH#A)' is also shown. The 'SNC protection switching process' is indicated in both nodes. The legend shows 'ETH_C' as a circle with a horizontal line and 'ETH_FP' as two hexagons. Reference G.8031-Y.1342(15)_F10-10 is at the bottom right.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +Figure 10-10: 1:1 protection switching architecture (with selector bridge) – Signal fail condition for working transport entity. The diagram shows a 'Protected ETH#A SNC' spanning 'WEST' and 'EAST' nodes. In the WEST node, a dashed line labeled 'ETH#A (Null signal)' is shown with a large 'X' over it, indicating a signal failure. Below it, a solid line labeled 'Working transport entity (for ETH#A)' and 'ETH#A (Normal traffic)' is shown. A solid line labeled 'Protection transport entity (for ETH#A)' is also shown. The 'SNC protection switching process' is indicated in both nodes. The legend shows 'ETH\_C' as a circle with a horizontal line and 'ETH\_FP' as two hexagons. Reference G.8031-Y.1342(15)\_F10-10 is at the bottom right. + +**Figure 10-10 – 1:1 protection switching architecture (with selector bridge) – Signal fail condition for working transport entity** + +![Figure 10-11: 1:1 protection switching architecture (with broadcast bridge) – Signal degrade condition for working transport entity. The diagram shows a 'Protected ETH#A SNC' spanning 'WEST' and 'EAST' nodes. In the WEST node, a dashed line labeled 'ETH#A (Normal traffic)' is shown with a small 'X' over it, indicating a signal degrade condition. Below it, a solid line labeled 'Working transport entity (for ETH#A)' and 'ETH#A (Normal traffic)' is shown. A solid line labeled 'Protection transport entity (for ETH#A)' is also shown. The 'SNC protection switching process' is indicated in both nodes. The legend shows 'ETH_C' as a circle with a horizontal line and 'ETH_FP' as two hexagons. Reference G.8031-Y.1342(15)_F10-11 is at the bottom right.](d734a6ea1b381280f043fcf70391b6db_img.jpg) + +Figure 10-11: 1:1 protection switching architecture (with broadcast bridge) – Signal degrade condition for working transport entity. The diagram shows a 'Protected ETH#A SNC' spanning 'WEST' and 'EAST' nodes. In the WEST node, a dashed line labeled 'ETH#A (Normal traffic)' is shown with a small 'X' over it, indicating a signal degrade condition. Below it, a solid line labeled 'Working transport entity (for ETH#A)' and 'ETH#A (Normal traffic)' is shown. A solid line labeled 'Protection transport entity (for ETH#A)' is also shown. The 'SNC protection switching process' is indicated in both nodes. The legend shows 'ETH\_C' as a circle with a horizontal line and 'ETH\_FP' as two hexagons. Reference G.8031-Y.1342(15)\_F10-11 is at the bottom right. + +**Figure 10-11 – 1:1 protection switching architecture (with broadcast bridge) – Signal degrade condition for working transport entity** + +# 11 APS Protocol + +## 11.1 APS format + +APS information is carried within the APS PDU which is one of a suite of Ethernet operation, administration and maintenance (OAM) messages. OAM PDU formats for each type of Ethernet OAM operation are defined in [ITU-T G.8013]. APS-specific information is transmitted by a MEP within specific fields in the APS PDU. + +The APS messages use the multicast class 1 DA. + +The APS PDU is identified by a specific Ethernet OAM OpCode. In this version of the Recommendation, four octets in the APS PDU are used to carry APS-specific information. This is illustrated in Figure 11-1. In addition, it should be noted that for the current version of this Recommendation, the type length value (TLV) Offset field is required to be set to 0x04. + +![Figure 11-1 – APS PDU format diagram showing fields: MEL, Version (0), OpCode (APS=39), Flags (0), TLV Offset (4), APS-Specific Information, and END TLV (0).](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +The diagram shows the structure of an APS PDU. It is divided into four main sections labeled 1, 2, 3, and 4, each containing 8 bits. Section 1 contains MEL (bits 8-5) and Version (0) (bits 4-1). Section 2 contains OpCode (APS=39) (bits 8-1). Section 3 contains Flags (0) (bits 8-1). Section 4 contains TLV Offset (4) (bits 8-5) and the start of APS-Specific Information (bits 4-1). Below these sections is a row for APS-Specific Information, and at the bottom is a row for END TLV (0). + +Figure 11-1 – APS PDU format diagram showing fields: MEL, Version (0), OpCode (APS=39), Flags (0), TLV Offset (4), APS-Specific Information, and END TLV (0). + +**Figure 11-1 – APS PDU format** + +The Version field shall be set to 0x00. + +For other fields such as OpCode, Flags and END TLV, the following values shall be used as defined in [ITU-T G.8013]: + +- a) **OpCode:** 0d39 (=0x27) +- b) **Flags:** 0x00 +- c) **END TLV:** 0x00 + +In the MEL field, the MEG level of the APS PDU is inserted. + +The format of the APS-specific information within each APS PDU is defined as per Figure 11-2: + +![Figure 11-2 – APS-specific information format diagram showing fields: Request/State, Prot. Type (A, B, D, R), Requested Signal, Bridged Signal, T, and Reserved (0).](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +The diagram shows the structure of APS-specific information, divided into four sections labeled 1, 2, 3, and 4, each containing 8 bits. Section 1 contains Request/State (bits 8-5) and Prot. Type (bits 4-1, subdivided into A, B, D, R). Section 2 contains Requested Signal (bits 8-1). Section 3 contains Bridged Signal (bits 8-1). Section 4 contains T (bit 8) and Reserved (0) (bits 7-1). + +Figure 11-2 – APS-specific information format diagram showing fields: Request/State, Prot. Type (A, B, D, R), Requested Signal, Bridged Signal, T, and Reserved (0). + +**Figure 11-2 – APS-specific information format** + +All bits defined as "Reserved" in this Recommendation shall be transmitted as 0 and ignored on reception. + +Table 11-1 describes code points and values for APS-specific information. + +**Table 11-1 – Code points and field values** + +| | | | | +|---------------|--------|---------------------------------------------------|----------| +| Request/State | 1111 | Lockout of protection (LO) | Priority | +| | 1110 | Signal fail on protection (SF-P) | highest | +| | 1101 | Forced switch (FS) | | +| | 1011 | Signal fail for working (SF) | | +| | 1001 | Signal degrade (SD) | | +| | 0111 | Manual switch (MS) | | +| | 0110 | Deprecated | | +| | 0101 | Wait-to-restore (WTR) | | +| | 0100 | Exercise (EXER) | | +| | 0010 | Reverse request (RR) | | +| | 0001 | Do not revert (DNR) | | +| | 0000 | No request (NR) | lowest | +| | Others | Reserved for future international standardization | | + +**Table 11-1 – Code points and field values** + +| | | | | +|--------------------------------------------|---|-------|---------------------------| +| Protection Type | A | 0 | No APS channel | +| | | 1 | APS channel | +| | B | 0 | 1+1 (permanent bridge) | +| | | 1 | 1:1 (no permanent bridge) | +| | D | 0 | Unidirectional switching | +| | | 1 | Bidirectional switching | +| | R | 0 | Non-revertive operation | +| | | 1 | Revertive operation | +| Requested Signal | | 0 | Null signal | +| | | 1 | Normal traffic signal | +| | | 2-255 | (Reserved for future use) | +| Bridged Signal | | 0 | Null signal | +| | | 1 | Normal traffic signal | +| | | 2-255 | (Reserved for future use) | +| Bridge Type (for 1:1 protection switching) | T | 0 | Selector bridge | +| | | 1 | Broadcast bridge | + +For the supported protection architectures described in clause 10, 1-Phase APS shall be used. + +## 11.2 1-phase APS protocol + +### 11.2.1 Principle of operation + +Figure 11-3 illustrates the principle of the 1+1/1:1 linear protection switching algorithm. This algorithm is performed in network elements at both ends of the protected domain (locations WEST and EAST). Bidirectional switching is achieved by transmitting local switching requests to the Far End via the "request/state" in the first octet of the APS-specific information (see Figure 11-2). The transmitted "requested signal" and "bridged signal" in the second and the third octets of the APS-specific information contain the local bridge/selector status information; a persistent mismatch between both ends may thus be detected and leads to an alarm. + +![Figure 11-3 – Principle of 1+1/1:1 linear protection switching algorithm. The diagram shows the logic flow for determining the top priority request and handling protection switching. Inputs include ETH_CI_SSF(W), ETH_CI_SSF(P), ETH_CI_SSD(W), ETH_CI_SSD(P), and other local requests. These pass through 'Hold-off timer logic' and then 'Local priority logic' to produce a 'Top priority local request'. Simultaneously, 'APS specific information received from far end' is processed by a 'Validity check' to produce a 'Request/State' byte (far end request). Both the top priority local request and the far end request are processed by 'Global priority logic' to determine the 'Top priority global request'. This global request is compared with the 'Requested signal' far-end status in a 'Mismatch detection' block. If a mismatch is detected, it results in 'Delect dFOP (protection switching incomplete)'. The 'Top priority global request' also informs the 'Set local bridge/selector' and is sent to the far end via 'Request/State' byte and 'Requested signal' and 'Bridged signal' information. A text box on the right explains that if the request is EXER, DNR or other from the far end, RR, DNR or NR are sent respectively. Also, local bridge/selector status is sent to the far end via 'Requested signal' and 'Bridged signal' information.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +Figure 11-3 – Principle of 1+1/1:1 linear protection switching algorithm. The diagram shows the logic flow for determining the top priority request and handling protection switching. Inputs include ETH\_CI\_SSF(W), ETH\_CI\_SSF(P), ETH\_CI\_SSD(W), ETH\_CI\_SSD(P), and other local requests. These pass through 'Hold-off timer logic' and then 'Local priority logic' to produce a 'Top priority local request'. Simultaneously, 'APS specific information received from far end' is processed by a 'Validity check' to produce a 'Request/State' byte (far end request). Both the top priority local request and the far end request are processed by 'Global priority logic' to determine the 'Top priority global request'. This global request is compared with the 'Requested signal' far-end status in a 'Mismatch detection' block. If a mismatch is detected, it results in 'Delect dFOP (protection switching incomplete)'. The 'Top priority global request' also informs the 'Set local bridge/selector' and is sent to the far end via 'Request/State' byte and 'Requested signal' and 'Bridged signal' information. A text box on the right explains that if the request is EXER, DNR or other from the far end, RR, DNR or NR are sent respectively. Also, local bridge/selector status is sent to the far end via 'Requested signal' and 'Bridged signal' information. + +G.8031-Y.1342(15)\_F11-3 + +**Figure 11-3 – Principle of 1+1/1:1 linear protection switching algorithm** + +In detail, the functionality is as follows (see Figure 11-3): + +At the local network element, one or more local protection switching requests (as listed in clauses 9.1 and 9.2) may be active. The "local priority logic" determines which of these requests is of top priority, using the order of priority given in Table 11-1. This top priority local request information is passed on to the "global priority logic". Note that CLEAR command if accepted, clearance of SF(-P) (or of SD if applicable) or expiration of WTR timer shall not be processed by the local priority logic but shall be submitted to the global priority logic for processing. + +If the provisioned hold-off timer value is non-zero, when the "hold-off timer logic" receives new ETH\_CI\_SSF (or ETH\_CI\_SSD if applicable) information, it does not report this information to the "local priority logic" immediately. Instead the hold-off timer will be started (see clause 11.12). + +The local network element receives information from the network element of the far-end via the APS-specific information. The received APS-specific information is subjected to a validity check (see clause 11.2.4). The state transitions and the top priority global request are calculated in the "global priority logic" based on the top priority local request, the request of the last received "request/state" information, and state transition tables defined in Annex A, as follows: + +- a) If the top priority local request is CLEAR, or clearance of SF(-P) (or of SD if applicable), or expiration of WTR, a state transition is calculated first based on the top priority local request and state machine table for local requests to obtain an intermediate state1. This intermediate state is the final state in case of clearance of SF-P otherwise, starting at this intermediate state, the last received far-end request and the state machine table for far-end requests are used to calculate the final state; +- b) If the top priority local request is neither CLEAR, nor clearance of SF(-P) (or of SD if applicable), nor expiration of WTR, then the "global priority logic" compares the top priority local request with the request of the last received "request/state" information based on Table 11-1; + +1 The intermediate state is an abstraction to determine the final state. The local network element only enters the final state, not the intermediate state. As a result, no switch and no APS exchange are performed because of the intermediate state being determined. + +- i) if the top priority local request has higher or equal priority, it is used with the state transition table for local requests defined in Annex A to determine the final state2; otherwise; +- ii) the request of the last received "request/state" information is used with the state transition table for far-end requests defined in Annex A to determine the final state. + +The final state corresponds to the "top priority global request". + +If the top priority global request is the local request, it will be indicated in "request/state" field. If the top priority global request is EXER, DNR or other request from the far end, RR, DNR or NR will be indicated respectively. The top priority global request will be exactly same with the top priority local request in the case of unidirectional protection switching because the received "request/state" information should not affect the operation of the unidirectional protection switching. This request then determines the bridge/selector position (or status) of the local network element as follows: + +- c) For 1+1 architectures, only the selector position is controlled. For 1:1 architectures, both the bridge and the selector positions are maintained to select the same position; +- d) If the top priority global request is a request for a working entity, the associated normal traffic signal is bridged/switched to/from the protection entity, i.e., the associated bridge/selector of the local network element selects the protection entity. A switching request for a working entity means a request to switch from a working entity to the protection entity. + +The bridge/selector status is transmitted to the far end via the "requested signal" and "bridged signal" (with coding as described in Table 11-1). It is also compared with the bridge/selector status of the far end as indicated by the received "requested signal" and "bridged signal". + +Note that the linear protection switching algorithm commences immediately every time one of the input signals (see Figure 11-3) changes, i.e., when the status of any local request changes, or when a different APS-specific information is received from the far end. The consequent actions of the algorithm are also initiated immediately, i.e., change the local bridge/selector position (if necessary), transmit a new APS-specific information (if necessary), or detect dFOP if the protection switching is not completed within a period specified in clause 11.15. + +### 11.2.2 Revertive mode + +In revertive mode of unidirectional protection switching operation, in conditions where normal traffic signal is being received via the protection entity, if local protection switching requests (see Figure 11-3) have been previously active and now become inactive, a local wait-to-restore state is entered. Since this state now represents the highest priority local request, it is indicated on the transmitted "request/state" information and maintains the switch. + +In the case of bidirectional protection switching, a local WTR state is entered only when there is no higher priority of request received from the far end than that of the WTR state. + +This state normally times out and becomes a NR state after the WTR timer has expired. The WTR timer is deactivated earlier if any local request of higher priority pre-empts this state. + +A switch to the protection entity may be maintained by a local wait-to-restore state or by a remote request (wait-to-restore or other) received via the "request/state" information. Therefore, in a case where a bidirectional failure for a working entity has occurred and subsequent repair has taken place, the bidirectional reversion back to the working entity does not take place until both wait-to-restore timers at both ends have expired. + +2 Note however that, as stated in clause 11.10, once a switch has been completed due to a request, it will not be overridden by another request of the same priority (first come, first served behaviour). + +### 11.2.3 Non-revertive mode + +In non-revertive mode of unidirectional protection switching operation, in conditions where normal traffic signal is being transmitted via the protection entity, if local protection switching requests (see Figure 11-3) have been previously active and now become inactive, a local "DNR state" is entered. Since this state now represents the highest priority local request, it is indicated on the transmitted "request/state" information and maintains the switch, thus preventing reversion back to the released bridge/selector position in non-revertive mode under NR conditions. + +In the case of bidirectional protection switching operation, a local DNR state is entered when there is no higher priority of request received from the far end than that of the DNR state, or when both the local state and far-end state are NR with the requested signal number 1. + +### 11.2.4 Transmission and acceptance of APS + +Traffic units which carry APS PDU are called APS frames. The APS frames are transported via the protection transport entity only, being inserted by the head end of the protected domain and extracted by the tail end of the protected domain. + +A new APS frame must be transmitted immediately when a change in the transmitted status (see Figure 11-3) occurs. + +The first three APS frames should be transmitted as fast as possible only if the APS information to be transmitted has been changed so that fast protection switching is possible even if one or two APS frames are lost or corrupted. For the fast protection switching in 50 ms, the interval of the first three APS frames should be 3.3 ms, which is the same interval as CCM frames for fast defect detection. APS frames after the first three frames should be transmitted with the interval of 5 seconds. + +If no valid APS-specific information is received, the last valid received information remains applicable except in case of SF condition on the protection transport entity. + +If a protection end point receives APS-specific information from the working entity, it should ignore this information, and should detect the Failure of Protocol defect for the local network element (see clause 11.15). + +## 11.3 Request type + +The request types reflect the highest priority condition, command, or state. In the case of unidirectional switching, this is the highest priority value determined from the near end only. In bidirectional switching, the local request will be indicated only in the case where it is as high as or higher than any request received from the far end over the APS communication, otherwise NR will be indicated. In 1-phase APS protocol, the near end will signal a RR only in response to an EXER command from the far end. + +## 11.4 Protection types and bridge type + +The valid configurations of the protection type and bridge type are as specified in Table 11-2: + +**Table 11-2 – Valid configurations for protection type and bridge type** + +| Protection Type | Bridge Type | Valid configuration | +|-----------------|-------------|----------------------------------------------------------------| +| 000x | N/A | 1+1 Unidirectional, no APS communication | +| 100x | N/A | 1+1 Unidirectional w/APS communication | +| 101x | N/A | 1+1 Bidirectional w/APS communication | +| 111x | 0 | 1:1 Bidirectional w/APS communication using a selector bridge | +| 111x | 1 | 1:1 Bidirectional w/APS communication using a broadcast bridge | + +The protection type values are chosen such that the default value (all zeros) matches the only type of protection that can operate without APS (1+1 Unidirectional). + +Note that protection type values 010x, 001x, and 011x are invalid since 1:1 and bidirectional require an APS communication. + +If the "B" bit mismatches, the selector is released since 1:1 and 1+1 are incompatible. This will result in a defect. + +Provided the "B" bit matches: + +- a) If the "A" bit mismatches, the side expecting APS will fall back to 1+1 unidirectional switching without APS communication; +- b) If the "D" bit mismatches, the bidirectional side will fall back to unidirectional switching; +- c) If the "R" bit mismatches, one side will clear switches to "WTR" and the other will clear to "DNR". The two sides will interwork and the traffic is protected; +- d) If the "T" bit mismatches, the side using a broadcast bridge will fall back to using a selector bridge. + +The protection type of an SNC protection switching process shall be configured via ETH\_C\_MI\_PS\_ProtType. + +NOTE – Equipment not supporting the broadcast bridge (e.g., equipment compliant with previous versions of this Recommendation) sets the bridge type (T) bit to 0 and ignores it in reception. + +## 11.5 Requested signal + +This indicates the signal that the near-end requests be carried over the protection path. For NR, this is the null signal when the far end is not bridging normal traffic signal to the protection entity. When the far end is bridging normal traffic signal to the protection entity, the requested signal is the normal traffic signal for NR; for LO, this can only be the null signal. For Exercise, this can be the null signal when Exercise replaces NR or the normal traffic signal in the case where Exercise replaces DNR. For SF (or SD if applicable), this will be the normal traffic signal, or the null signal to indicate that protection has failed or has been degraded. For all other requests, this will be the normal traffic signal requested to be carried over the protection transport entity. + +## 11.6 Bridged signal + +This indicates the signal that is bridged onto the protection path. For 1+1 protection, this should always indicate the normal traffic signal, accurately reflecting the permanent bridge. For 1:1 protection, this will indicate what is actually bridged to the protection entity (either the null signal, or normal traffic signal). This will generally be the bridge requested by the far end. + +## 11.7 Control of bridge + +In 1+1 architectures, the normal traffic signal is permanently bridged to protection. The normal traffic signal will always be indicated in the bridged signal field of the APS information. + +In 1:1 architectures, the bridge will be set to the one indicated by the "requested signal" field of the incoming APS information. Once the bridge has been established, this will be indicated in the "bridged signal" field of the outgoing APS information. + +## 11.8 Control of selector + +In 1+1 unidirectional architectures (with or without APS communication), the selector is set entirely according to the highest priority local request. This is a single phase switch. + +In 1+1 bidirectional architectures, the normal traffic signal will be selected from the protection entity when the outgoing "requested signal" indicates the normal traffic signal. + +In 1:1 bidirectional architectures, normal traffic signal will be selected from the protection entity when the number appears in the outgoing "requested signal". + +## **11.9 Signal fail of the protection transport entity** + +Signal fail on the protection transport entity is higher priority than any defect that would cause a normal traffic signal to be selected from protection. For the case an APS signal is in use, a SF-P on the protection transport entity (over which the APS signal is routed) has priority over the Forced switch. Lockout command has higher priority than SF-P: during failure conditions, lockout status shall be kept active. + +## **11.10 Equal priority requests** + +In general, once a switch has been completed due to a request, it will not be overridden by another request of the same priority (first come, first served behaviour). Equal priority requests from both sides of a bidirectional protection group are both considered valid as follows: + +- a) If the local state is NR with the requested signal number 1 and the far-end state is NR with the requested signal number 0, the local state transits to NR with the requested signal number 0. This applies to the case when the remote request for switching to the protection transport entity has been cleared; +- b) If both the local and far-end states are NR with the requested signal number 1, the local state transits to the appropriate new state (see clause 11.2.3 for non-revertive mode and clause 11.13 for revertive mode). This applies to the case when the old request has been cleared at both ends; +- c) If both the local and far-end states are RR with the same requested signal number, the both ends transit to the appropriate new state according to the requested signal number. This applies to the case of concurrent deactivation of EXER from both ends; +- d) In other cases, no state transition occurs even if equal priority requests are activated from both ends. Note, in case MS is issued simultaneously either as local or far-end requests to both working and protection transport entities, MS to the working transport entity is considered as having higher priority than MS to the protection transport entity. + +## **11.11 Command acceptance and retention** + +The commands CLEAR, LO, FS, MS, and EXER are accepted or rejected in the context of previous commands, the condition of the working and protection entities in the protection group, and (in bidirectional switching only) the received APS information. + +The CLEAR command is only valid if a near-end LO, FS, MS, or EXER command is in effect, or if a WTR state is present at the near end and rejected otherwise. This command will remove the near-end command or WTR state, allowing the next lower priority condition or (in bidirectional switching) APS request to be asserted. + +Other commands are rejected unless they are higher priority than the previously existing command, condition, or (in bidirectional switching) APS request. If a new command is accepted, any previous, lower priority command that is overridden is forgotten. If a higher priority command overrides a lower priority condition or (in bidirectional switching) APS request, that other request will be reasserted if it still exists at the time the command is cleared. + +If a command is overridden by a condition or (in bidirectional switching) APS request, that command is forgotten. + +Each external command shall be input to an SNC protection switching process via ETH\_C\_MI\_PS\_ExtCMD. + +## 11.12 Hold-off timer + +In order to coordinate timing of protection switches at multiple layers or across cascaded protected domains, a hold-off timer may be required. The purpose is to allow either a server layer protection switch to have a chance to fix the problem before switching at a client layer, or to allow an upstream protected domain to switch before a downstream domain (e.g., to allow an upstream ring to switch before the downstream ring in a dual node interconnect configuration so that the switch occurs in the same ring as the failure). + +Each protection group should have a provisionable hold-off timer. The suggested range of the hold-off timer is 0 to 10 seconds in steps of 100 ms (accuracy of $\pm 5$ ms). + +When a new defect or more severe defect occurs (new SF (or SD if applicable)), this event will not be reported immediately to protection switching if the provisioned hold-off timer value is non-zero. Instead, the hold-off timer will be started. When the hold-off timer expires, it will be checked whether a defect still exists on the trail that started the timer. If it does, that defect will be reported to protection switching. The defect need not be the same one that started the timer. + +This hold-off timer mechanism shall be applied for both working and protection transport entities. + +The hold-off timer of an SNC protection switching process shall be configured via ETH\_C\_MI\_PS\_HoTime. + +## 11.13 Wait-to-restore timer + +In revertive mode of operation, to prevent frequent operation of the protection switch due to an intermittent defect, a failed working transport entity must become fault free. After the failed working transport entity meets this criterion, a fixed period of time shall elapse before a normal traffic signal uses it again. This period, called wait-to-restore (WTR) period, may be configured by the operator in 1 minute steps between 5 and 12 minutes; the default value is 5 minutes. A SF (or SD (W) if applicable) condition will override the WTR. To activate WTR timer appropriately even when both ends concurrently detect clearance of SF (or SD (W) if applicable), when the local state transits from SF (or SD (W) if applicable) to NR with the requested signal number 1, the previous local state, SF (or SD (W) if applicable), should be memorized. If both the local state and far-end state are NR with the requested signal number 1, the local state transits to WTR only when the previous local state is SF (or SD (W) if applicable). Otherwise, the local state transits to NR with the requested signal number 0. + +In revertive mode of operation, when the protection is no longer requested, i.e., the failed working transport entity is no longer in SF (or SD (W) if applicable) condition (and assuming no other requesting transport entities), a local wait-to-restore state will be activated. Since this state becomes the highest in priority, it is indicated on the APS signal (if applicable), and maintains the normal traffic signal from the previously failed working transport entity on the protection transport entity. This state shall normally time out and become a NR state. The wait-to-restore timer deactivates earlier when any request of higher priority pre-empts this state. + +The WTR timer of an SNC protection switching process shall be configured via ETH\_C\_MI\_PS\_WTR. + +## 11.14 Exercise operation + +Exercise is a command to test if the APS communication is operating correctly. It is lower priority than any "real" switch request. It is only valid in bidirectional switching, since this is the only place where you can get a meaningful test by looking for a response. + +Exercise command shall issue the command with the same requested and bridged signal numbers of the NR, RR or DNR request that it replaces. In 1-phase APS protocol, the valid response will be an RR with the corresponding requested and bridged signal numbers. When Exercise commands are + +input at both ends, an EXER, instead of RR, is transmitted from both ends. The standard response to DNR should be DNR rather than NR. When the exercise command is cleared, it will be replaced with NR or RR if the requested signal number is 0, and DNR or RR if the requested signal number is 1. + +## 11.15 Failure of protocol defects + +"Failure of protocol" situations for protection types requiring APS are as follows: + +- a) Fully incompatible provisioning (the "B" bit mismatch, described in clause 11.4); +- b) Working/protection configuration mismatch (described in clause 11.2.4); +- c) Lack of response to a bridge request (i.e., no match in sent "requested signal" and received "requested signal") in case of bidirectional switching for > 50 ms. + +NOTE – If the lack of response results from issuance at the local end of a: + +- SD request that is unknown at the far end then it is expected that the operator would set the ETH\_C\_MI\_PS\_SD\_Protection to disabled at the local end to resolve the dFOP-NR and the misalignment between the protection switching states at the two ends. + - MS [r/b=null] request that is unknown at the far end then it is expected that the operator would clear the MS [r/b=null] command at the local end to resolve the dFOP-NR and the misalignment between the protection switching states at the two ends. +- d) No APS frame is received on the protection transport entity during at least 3.5 times the long APS interval (e.g., at least 17.5 seconds) and there is no defect on the protection transport entity. + +Fully incompatible provisioning and working/protection configuration mismatch are detected by receiving only one APS frame. Detection and clearance of "failure of protocol" defects are defined in [ITU-T G.8021]. + +If an unknown request or a request for an invalid signal number is received, it will be ignored. + +## 11.16 Signal degrade of the protection transport entity + +Signal degrade on the protection transport entity has the same priority as signal degrade on the working transport entity. As a result, in case a SD condition affects both transport entities, the first SD detected is not overridden by the second SD detected. In case SD is detected simultaneously either as local or far-end requests on both working and protection transport entities, SD on the standby transport entity is considered as having higher priority than SD on the active transport entity, and the normal traffic signal continues to be selected from the active transport entity (i.e., no unneeded protection switching is performed). + +NOTE – In the preceding sentence, "simultaneously" relates to the occurrence of SD on both the active and standby transport entities at input to the SNC protection switching process at the same time, or as long as a SD request has not been acknowledged by the remote end in bidirectional protection switching. + +# Annex A + +## State transition tables of protection switching + +(This annex forms an integral part of this Recommendation.) + +In this annex, state transition tables for the following protection switching configurations are described: + +- a) 1:1 bidirectional (revertive mode, non-revertive mode); +- b) 1+1 bidirectional (revertive mode, non-revertive mode); +- c) 1+1 unidirectional (revertive mode, non-revertive mode). + +Note that any other global or local request which is not described in state transition tables does not trigger any state transition. + +NOTE – Re-assertion cases in state transition tables for far-end requests are provided to facilitate understanding and are otherwise covered by clause 11.2.1:b):i). + +## A.1 State transition for 1:1 bidirectional switching with revertive mode + +### A.1.1 Local requests + +Table A.1 shows the state transition by a local request for the 1:1 protection switching in revertive mode. + +**Table A.1 – State transition by local requests (1:1, bidirectional, revertive mode)** + +| State | | Signalled APS | Local request | | | | | | | | | | | | | | | +|-------|-----------------------------------|---------------|---------------|---------------|-----------------------------|--------------------------------------------|--------------------------------|-------------------------------------------------------------------|-----------------------------|--------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|------------------------------------------------------------------------------------------|----------|-------------------| +| | | | a | b | c | d | e | f | g | h | i | j | k | l | m | n | o | +| | | | Lockout | Forced switch | SF on working a) | Working recovers from SF | SF on protection a) | Protection recovers from SF | SD on working a) | Working recovers from SD | SD on protection a) | Protection recovers from SD | Manual switch to protection | Manual switch to working | Clear | Exercise | WTR timer expires | +| A | No Request | NR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | →K | N/A | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | | +| B | No Request | NR | →C | →D | →E | O | →F | N/A | →P | O | →Q | N/A | →G | →H | N/A | O | N/A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | +| C | Lockout | LO | O | O | O | O | O | O | O | O | O | O | O | O | →A | O | N/A | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | or →E b)
or →F c)
or →P d)
or →Q e) | | | +| D | Forced Switch | FS | →C | O | O | O | →F | N/A | O | O | O | O | O | O | →A | O | N/A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | or →E b)
or →P d)
or →Q e) | | | +| E | Signal Fail (W) | SF | →C | →D | N/A | →I | →F | N/A | O | O | O | O | O | O | N/A | O | N/A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | or →P d)
or →Q e) | | | | | | | | | | | | +| F | Signal Fail (P) | SF-P | →C | O | O | O | N/A | →A | O | O | O | O | O | O | N/A | O | N/A | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | or →E b)
or →P d)
or →Q e) | | | | | | | | | | +| P | Signal Degrade (W) | SD | →C | →D | →E | N/A | →F | N/A | N/A | →I | O | O | O | O | N/A | O | N/A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | or →Q e) | | | | | | | | +| Q | Signal Degrade (P) | SD | →C | →D | →E | N/A | →F | N/A | O | O | N/A | →A | O | O | N/A | O | N/A | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | or →P d) | | | | | | +| G | Manual Switch | MS | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | O | O | →A | O | N/A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | + +**Table A.1 – State transition by local requests (1:1, bidirectional, revertive mode)** + +| State | | Signalled APS | Local request | | | | | | | | | | | | | | | +|-------|-----------------------------------|---------------|---------------|---------------|-----------------------------|--------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|-------|----------|-------------------| +| | | | a | b | c | d | e | f | g | h | i | j | k | l | m | n | o | +| | | | Lockout | Forced switch | SF on working a) | Working recovers from SF | SF on protection a) | Protection recovers from SF | SD on working a) | Working recovers from SD | SD on protection a) | Protection recovers from SD | Manual switch to protection | Manual switch to working | Clear | Exercise | WTR timer expires | +| H | Manual Switch | MS | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | O | O | →A | O | N/A | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | | +| I | Wait to Restore | WTR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | →A | O | →A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | +| K | Exercise | EXER | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | →A | O | N/A | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | | +| M | Reverse Request | RR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | →K | N/A | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | | + +NOTE 1 – "N/A" means that the event is not expected to happen for the State. However if it does happen, the event should be ignored. +NOTE 2 – "O" means that the request shall be overruled by the existing condition because it has an equal or a lower priority. +NOTE 3 – "(→X)" represents that the state is not changed and remains the same state. +a) Signal fail or signal degrade on working or protection is input to the local priority logic only if the signal fail or signal degrade still exists after hold-off timer expires. +b) If SF is reasserted. +c) If SF-P is reasserted. +d) If SD (W) is reasserted. +e) If SD (P) is reasserted. + +### A.1.2 Far-end requests + +Table A.2 shows the state transition by a far-end request received by APS for the 1:1 bidirectional protection switching in revertive mode. + +**Table A.2 – State transition by far-end requests (1:1, bidirectional, revertive mode)** + +| State | | Signalled APS | Received far-end request | | | | | | | | | | | | | | +|-------|-----------------------------------|---------------|--------------------------|-------------|---------------|---------------|---------------|-------------|---------------|---------------------|---------------|-------------|-------------|------------------------------------------------------------------------------------------|---------------------|---------------| +| | | | p | q | r | s | t | u | v | w | x | y | z | aa | ab | ac | +| | | | LO | SF-P | FS | SF | SD | SD | MS | MS | WTR | EXER | RR | NR | NR | DNR | +| | | | [r/b= null] | [r/b= null] | [r/b= normal] | [r/b= normal] | [r/b= normal] | [r/b= null] | [r/b= normal] | [r/b= null] | [r/b= normal] | [r/b= null] | [r/b= null] | [r/b= null] | [r/b= normal] | [r/b= normal] | +| A | No Request | NR | (→A) | (→A) | →B | →B | →B | (→A) | →B | (→A) | →B | →M | (→A) | (→A) | (→A) | →B | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | or →E a)
or →F b)
or →P d)
or →Q e) | | | +| B | No Request | NR | →A | →A | (→B) | (→B) | (→B) | →A | (→B) | →A | (→B) | N/A | N/A | →A | →A | (→B) | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | or →E a)
or →P d) | or →I c) | | +| C | Lockout | LO | (→C) | O | O | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | +| D | Forced Switch | FS | →A | →A | (→D) | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| E | Signal Fail (W) | SF | →A | →A | →B | (→E) | O | O | O | O | O | O | O | O | O | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| F | Signal Fail (P) | SF-P | →A | (→F) | O | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | +| P | Signal Degrade (W) | SD | →A | →A | →B | →B | (→P) | O | O | O | O | O | O | O | O | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| Q | Signal Degrade (P) | SD | →A | →A | →B | →B | O | (→Q) | O | O | O | O | O | O | O | O | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | +| G | Manual Switch | MS | →A | →A | →B | →B | →B | →A | (→G) | (→G) | O | O | O | O | O | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | or →A f) | | | | | | | + +**Table A.2 – State transition by far-end requests (1:1, bidirectional, revertive mode)** + +| State | | Signalled APS | Received far-end request | | | | | | | | | | | | | | +|-------|-----------------------------------|---------------|--------------------------|-------------|---------------|---------------|---------------|-------------|---------------|-------------|---------------|-------------|-------------|-------------|---------------|---------------| +| | | | p | q | r | s | t | u | v | w | x | y | z | aa | ab | ac | +| | | | LO | SF-P | FS | SF | SD | SD | MS | MS | WTR | EXER | RR | NR | NR | DNR | +| | | | [r/b= null] | [r/b= null] | [r/b= normal] | [r/b= normal] | [r/b= normal] | [r/b= null] | [r/b= normal] | [r/b= null] | [r/b= normal] | [r/b= null] | [r/b= null] | [r/b= null] | [r/b= normal] | [r/b= normal] | +| H | Manual Switch | MS | →A | →A | →B | →B | →B | →A | O | (→H) | O | O | O | O | O | O | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | +| I | Wait to Restore | WTR | →A | →A | →B | →B | →B | →A | →B | →A | (→I) | O | O | N/A | O | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| K | Exercise | EXER | →A | →A | →B | →B | →B | →A | →B | →A | N/A | (→K) | (→K) | O | N/A | O | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | +| M | Reverse Request | RR | →A | →A | →B | →B | →B | →A | →B | →A | N/A | (→M) | →A | →A | N/A | O | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | + +NOTE 1 – "N/A" means that the event is not expected to happen for the State. However if it does happen, the event should be ignored. +NOTE 2 – "O" means that the request shall be overruled by the existing condition because it has an equal or a lower priority. +NOTE 3 – "(□X)" represents that the state is not changed and remains the same state. +a) If SF is reasserted. +b) If SF-P is reasserted. +c) If the previous local state is SF (or SD (W) if applicable, see clause 11.13). +d) If SD (W) is reasserted. +e) If SD (P) is reasserted. +f) Only if the far-end request is due to the simultaneous application of a manual switch to working command at the far end (i.e., no NR request acknowledging the local MS state received previously from the far end) + +## A.2 State transition for 1:1 bidirectional switching with non-revertive mode + +### A.2.1 Local requests + +Table A.3 shows the state transition by a local request for the 1:1 bidirectional protection switching in non-revertive mode. + +**Table A.3 – State transition by local requests (1:1, bidirectional, non-revertive mode)** + +| State | | Signalled APS | Local request | | | | | | | | | | | | | | +|-------|-----------------------------------|---------------|---------------|---------------|------------------------------|--------------------------------------------|---------------------------------|-------------------------------------------------------------------|------------------------------|--------------------------|---------------------------------|-----------------------------|-----------------------------|--------------------------|------------------------------------------------------------------------------------------------------|----------| +| | | | a | b | c | d | e | f | g | h | i | j | k | l | m | n | +| | | | Lockout | Forced switch | SF on working a ) | Working recovers from SF | SF on protection a ) | Protection recovers from SF | SD on working a ) | Working recovers from SD | SD on protection a ) | Protection recovers from SD | Manual switch to protection | Manual switch to working | Clear | Exercise | +| A | No Request | NR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | →K | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | +| B | No Request | NR | →C | →D | →E | O | →F | N/A | →P | O | □Q | N/A | →G | →H | N/A | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| C | Lockout | LO | O | O | O | O | O | O | O | O | O | O | O | O | →A | O | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | or
→E b)
or
→F c)
or
→P d)
or
→Q e) | | +| D | Forced Switch | FS | →C | O | O | O | →F | N/A | O | O | O | O | O | O | →J | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | or
→E b)
or
→P d)
or
→Q e) | | +| E | Signal Fail (W) | SF | →C | →D | N/A | →J | →F | N/A | O | O | O | O | O | O | N/A | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | or →P d)
or →Q e) | | | | | | | | | | | +| F | Signal Fail (P) | SF-P | →C | O | O | O | N/A | →A | O | O | O | O | O | O | N/A | O | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | or →E b)
or →P d)
or →Q e) | | | | | | | | | +| P | Signal Degrade (W) | SD | →C | →D | →E | N/A | →F | N/A | N/A | →J | O | O | O | O | N/A | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | or →Q e) | | | | | | | + +**Table A.3 – State transition by local requests (1:1, bidirectional, non-revertive mode)** + +| State | | Signalled APS | Local request | | | | | | | | | | | | | | +|-------|-----------------------------------|---------------|---------------|---------------|------------------------------|--------------------------|---------------------------------|-----------------------------|------------------------------|--------------------------|---------------------------------|-----------------------------|-----------------------------|--------------------------|-------|----------| +| | | | a | b | c | d | e | f | g | h | i | j | k | l | m | n | +| | | | Lockout | Forced switch | SF on working a ) | Working recovers from SF | SF on protection a ) | Protection recovers from SF | SD on working a ) | Working recovers from SD | SD on protection a ) | Protection recovers from SD | Manual switch to protection | Manual switch to working | Clear | Exercise | +| Q | Signal Degrade (P) | SD | →C | →D | →E | N/A | →F | N/A | O | O | N/A | →A | O | O | N/A | O | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | or →P d ) | | | | | +| G | Manual Switch | MS | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | O | O | →J | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| H | Manual Switch | MS | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | O | O | →A | O | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | +| J | Do Not Revert | DNR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | □L | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| K | Exercise | EXER | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | →A | O | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | +| L | Exercise | EXER | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | →J | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| M | Reverse Request | RR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | →K | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | +| N | Reverse Request | RR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | →L | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | + +NOTE 1 – "N/A" means that the event is not expected to happen for the State. However if it does happen, the event should be ignored. + +NOTE 2 – "O" means that the request shall be overruled by the existing condition because it has an equal or a lower priority. + +NOTE 3 – "(□X)" represents that the state is not changed and remains the same state. + +a) Signal fail or signal degrade on working or protection is input to the local priority logic only if the signal fail or signal degrade still exists after hold-off timer expires. + +b) If SF is reasserted. + +c) If SF-P is reasserted. + +d) If SD (W) is reasserted. + +e) If SD (P) is reasserted. + +### A.2.2 Far-end requests + +Table A.4 shows the state transition by a far-end request received by APS for the 1:1 bidirectional protection switching in non-revertive mode. + +**Table A.4 – State transition by far-end requests (1:1, bidirectional, non-revertive mode)** + +| State | | Signalled APS | Received far-end request | | | | | | | | | | | | | | | | +|-------|--------------------------------------|---------------|--------------------------|----------------|------------------|------------------|------------------|----------------|------------------|----------------|------------------|----------------|------------------|----------------|------------------|------------------------------------------------------------------------------------------|------------------|------------------| +| | | | o | p | q | r | s | t | u | v | w | x | y | z | aa | ab | ac | ad | +| | | | LO | SF-P | FS | SF | SD | SD | MS | MS | WTR | EXER | EXER | RR | RR | NR | NR | DNR | +| | | | [r/b=
null] | [r/b=
null] | [r/b=
normal] | [r/b=
normal] | [r/b=
normal] | [r/b=
null] | [r/b=
normal] | [r/b=
null] | [r/b=
normal] | [r/b=
null] | [r/b=
normal] | [r/b=
null] | [r/b=
normal] | [r/b=
null] | [r/b=
normal] | [r/b=
normal] | +| A | No Request | NR | (→A) | (→A) | →B | →B | →B | (→A) | →B | (→A) | →B | →M | N/A | (→A) | N/A | (→A) | (→A) | →J | +| | Working/Active
Protection/Standby | [r/b=null] | | | | | | | | | | | | | | or →E a)
or →F b)
or →P c)
or →Q d) | | | +| B | No Request | NR | →A | →A | (→B) | (→B) | (→B) | →A | (→B) | →A | (→B) | N/A | N/A | N/A | N/A | →A | →J | →J | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | | | | | | | | | | | or →E a)
or →P c) | | | +| C | Lockout | LO | (→C) | O | O | O | O | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Active
Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | | | +| D | Forced Switch | FS | →A | →A | (→D) | O | O | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | | +| E | Signal Fail (W) | SF | →A | →A | →B | (→E) | O | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | | +| F | Signal Fail (P) | SF-P | →A | (→F) | O | O | O | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Active
Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | | | +| P | Signal Degrade (W) | SD | →A | →A | →B | →B | (→P) | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | | +| Q | Signal Degrade (P) | SD | →A | →A | →B | →B | O | (→Q) | O | O | O | O | O | O | O | O | O | O | +| | Working/Active
Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | | | + +**Table A.4 – State transition by far-end requests (1:1, bidirectional, non-revertive mode)** + +| State | | Signalled APS | Received far-end request | | | | | | | | | | | | | | | | +|-------|-----------------------------------|---------------|--------------------------|------------|--------------|--------------|--------------|------------|--------------|------------------------|--------------|------------|--------------|------------|--------------|------------|--------------|--------------| +| | | | o | p | q | r | s | t | u | v | w | x | y | z | aa | ab | ac | ad | +| | | | LO | SF-P | FS | SF | SD | SD | MS | MS | WTR | EXER | EXER | RR | RR | NR | NR | DNR | +| | | | [r/b=null] | [r/b=null] | [r/b=normal] | [r/b=normal] | [r/b=normal] | [r/b=null] | [r/b=normal] | [r/b=null] | [r/b=normal] | [r/b=null] | [r/b=normal] | [r/b=null] | [r/b=normal] | [r/b=null] | [r/b=normal] | [r/b=normal] | +| G | Manual Switch | MS | →A | →A | →B | →B | →B | →A | (→G) | (→G) | O | O | O | O | O | O | O | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | or
→A e) | | | | | | | | | +| H | Manual Switch | MS | →A | →A | →B | →B | →B | →A | O | (→H) | O | O | O | O | O | O | O | O | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | | | +| J | Do Not Revert | DNR | →A | →A | →B | →B | →B | →A | →B | →A | →B | N/A | →N | N/A | (→J) | O | O | (→J) | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | | +| K | Exercise | EXER | →A | →A | →B | →B | →B | →A | →B | →A | →B | (→K) | N/A | (→K) | N/A | O | N/A | N/A | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | | | +| L | Exercise | EXER | →A | →A | →B | →B | →B | →A | →B | →A | →B | N/A | (→L) | N/A | (→L) | N/A | O | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | | +| M | Reverse Request | RR | →A | →A | →B | →B | →B | →A | →B | →A | →B | (→M) | N/A | →A | N/A | →A | N/A | N/A | +| | Working/Active Protection/Standby | [r/b=null] | | | | | | | | | | | | | | | | | +| N | Reverse Request | RR | →A | →A | →B | →B | →B | →A | →B | →A | →B | N/A | (→N) | N/A | →J | N/A | N/A | →J | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | | + +NOTE 1 – "N/A" means that the event is not expected to happen for the State. However if it does happen, the event should be ignored. +NOTE 2 – "O" means that the request shall be overruled by the existing condition because it has an equal or a lower priority. +NOTE 3 – "(□X)" represents that the state is not changed and remains the same state. +a) If SF is reasserted. +b) If SF-P is reasserted. +c) If SD (W) is reasserted. +d) If SD (P) is reasserted. +e) Only if the far-end request is due to the simultaneous application of a manual switch to working command at the far end (i.e., no NR request acknowledging the local MS state received previously from the far end) + +## A.3 State transition for 1+1 bidirectional switching with revertive mode + +### A.3.1 Local requests + +Table A.5 shows the state transition by a local request for the 1+1 bidirectional protection switching in revertive mode. + +**Table A.5 – State transition by local requests (1+1, bidirectional, revertive mode)** + +| State | | Signalled APS | Local request | | | | | | | | | | | | | | | +|-------|-----------------------------------|--------------------|---------------|---------------|-----------------------------|--------------------------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|------------------------------------------------------------------------------------------------------|----------|-------------------| +| | | | a | b | c | d | e | f | g | h | i | j | k | l | m | n | o | +| | | | Lockout | Forced switch | SF on working g) | Working recovers from SF | SF on protection a) | Protection recovers from SF | SD on working a) | Working recovers from SD | SD on protection a) | Protection recovers from SD | Manual switch to protection | Manual switch to working | Clear | Exercise | WTR timer expires | +| A | No Request | NR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | →K | N/A | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | | +| B | No Request | NR | →C | →D | →E | O | →F | N/A | →P | O | →Q | N/A | →G | →H | N/A | O | N/A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | +| C | Lockout | LO | O | O | O | O | O | O | O | O | O | O | O | O | →A | O | N/A | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | or
→E b)
or
→F c)
or
→P d)
or
→Q e) | | | +| D | Forced Switch | FS | →C | O | O | O | →F | N/A | O | O | O | O | O | O | →A | O | N/A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | or
→E b)
or
→P d)
or
→Q e) | | | +| E | Signal Fail (W) | SF | →C | →D | N/A | →I | →F | N/A | O | O | O | O | O | O | N/A | O | N/A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | or →P d)
or →Q e) | | | | | | | | | | | | + +**Table A.5 – State transition by local requests (1+1, bidirectional, revertive mode)** + +| State | | Signalled APS | Local request | | | | | | | | | | | | | | | +|-------|--------------------------------------|---------------|-----------------------|---------------|-----------------------------|--------------------------|--------------------------------|-------------------------------------------------------------------|-----------------------------|--------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|-------|----------|-------------------| +| | | | a | b | c | d | e | f | g | h | i | j | k | l | m | n | o | +| | | | Lockout | Forced switch | SF on working a) | Working recovers from SF | SF on protection a) | Protection recovers from SF | SD on working a) | Working recovers from SD | SD on protection a) | Protection recovers from SD | Manual switch to protection | Manual switch to working | Clear | Exercise | WTR timer expires | +| F | Signal Fail (P) | SF-P | →C | O | O | O | N/A | →A | O | O | O | O | O | O | N/A | O | N/A | +| | Working/Active
Protection/Standby | | | | | | | or →E b)
or →P d)
or →Q e) | | | | | | | | | | +| P | Signal Degrade (W) | SD | →C | →D | →E | N/A | →F | N/A | N/A | →I | O | O | O | O | N/A | O | N/A | +| | Working/Standby
Protection/Active | | [r/b=normal] | | | | | | | | or →Q e) | | | | | | | +| Q | Signal Degrade (P) | SD | →C | →D | →E | N/A | →F | N/A | O | O | N/A | →A | O | O | N/A | O | N/A | +| | Working/Active
Protection/Standby | | [r=null,
b=normal] | | | | | | | | | | or →P d) | | | | | +| G | Manual Switch | MS | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | O | O | →A | O | N/A | +| | Working/Standby
Protection/Active | | [r/b=normal] | | | | | | | | | | | | | | | +| H | Manual Switch | MS | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | O | O | →A | O | N/A | +| | Working/Active
Protection/Standby | | [r=null,
b=normal] | | | | | | | | | | | | | | | +| I | Wait to Restore | WTR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | →A | O | →A | +| | Working/Standby
Protection/Active | | [r/b=normal] | | | | | | | | | | | | | | | +| K | Exercise | EXER | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | →A | O | N/A | +| | Working/Active
Protection/Standby | | [r=null,
b=normal] | | | | | | | | | | | | | | | +| M | Reverse Request | RR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | →K | N/A | +| | Working/Active
Protection/Standby | | [r=null,
b=normal] | | | | | | | | | | | | | | | + +**Table A.5 – State transition by local requests (1+1, bidirectional, revertive mode)** + +NOTE 1 – "N/A" means that the event is not expected to happen for the State. However if it does happen, the event should be ignored. +NOTE 2 – "O" means that the request shall be overruled by the existing condition because it has an equal or a lower priority. +NOTE 3 – "(☒X)" represents that the state is not changed and remains the same state. + +- a) Signal fail or signal degrade on working or protection is input to the local priority logic only if the signal fail or signal degrade still exists after hold-off timer expires. +- b) If SF is reasserted. +- c) If SF-P is reasserted. +- d) If SD (W) is reasserted. +- e) If SD (P) is reasserted. + +### A.3.2 Far-end requests + +Table A.6 shows the state transition by a far-end request received by APS for the 1+1 bidirectional protection switching in revertive mode. + +**Table A.6 – State transition by far-end requests (1+1, bidirectional, revertive mode)** + +| State | | Signalled APS | Received far-end request | | | | | | | | | | | | | | +|-------|--------------------------------------|-----------------------|--------------------------|-----------------------|------------------|------------------|------------------|-----------------------|------------------|-----------------------|------------------|-----------------------|-----------------------|------------------------------------------------------------------------------------------|---------------------|------------------| +| | | | p | q | r | s | t | u | v | w | x | y | z | aa | ab | ac | +| | | | LO | SF-P | FS | SF | SD | SD | MS | MS | WTR | EXER | RR | NR | NR | DNR | +| | | | [r=null,
b=normal] | [r=null,
b=normal] | [r/b=
normal] | [r/b=
normal] | [r/b=
normal] | [r=null,
b=normal] | [r/b=
normal] | [r=null,
b=normal] | [r/b=
normal] | [r=null,
b=normal] | [r=null,
b=normal] | [r=null,
b=normal] | [r/b=
normal] | [r/b=
normal] | +| A | No Request | NR | (→A) | (→A) | →B | →B | →B | (→A) | →B | (→A) | →B | →M | (→A) | (→A) | (→A) | →B | +| | Working/Active
Protection/Standby | [r=null,
b=normal] | | | | | | | | | | | | or →E a)
or →F b)
or →P d)
or →Q e) | | | +| B | No Request | NR | →A | →A | (→B) | (→B) | (→B) | →A | (→B) | →A | (→B) | N/A | N/A | →A | →A | (→B) | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | | | | | | | | | or →E a)
or →P d) | or →I c) | | +| C | Lockout | LO | (→C) | O | O | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Active
Protection/Standby | [r=null,
b=normal] | | | | | | | | | | | | | | | +| D | Forced Switch | FS | →A | →A | (→D) | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| E | Signal Fail (W) | SF | →A | →A | →B | (→E) | O | O | O | O | O | O | O | O | O | O | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | + +**Table A.6 – State transition by far-end requests (1+1, bidirectional, revertive mode)** + +| State | | Signalled APS | Received far-end request | | | | | | | | | | | | | | +|-------|--------------------------------------|-----------------------|--------------------------|-----------------------|------------------|------------------|------------------|-----------------------|------------------|-----------------------------|------------------|-----------------------|-----------------------|-----------------------|------------------|------------------| +| | | | p | q | r | s | t | u | v | w | x | y | z | aa | ab | ac | +| | | | LO | SF-P | FS | SF | SD | SD | MS | MS | WTR | EXER | RR | NR | NR | DNR | +| | | | [r=null,
b=normal] | [r=null,
b=normal] | [r/b=
normal] | [r/b=
normal] | [r/b=
normal] | [r=null,
b=normal] | [r/b=
normal] | [r=null,
b=normal] | [r/b=
normal] | [r=null,
b=normal] | [r=null,
b=normal] | [r=null,
b=normal] | [r/b=
normal] | [r/b=
normal] | +| F | Signal Fail (P) | SF-P | →A | (→F) | O | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Active
Protection/Standby | [r=null,
b=normal] | | | | | | | | | | | | | | | +| P | Signal Degrade (W) | SD | →A | →A | →B | →B | (→P) | O | O | O | O | O | O | O | O | O | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| Q | Signal Degrade (P) | SD | →A | →A | →B | →B | O | (→Q) | O | O | O | O | O | O | O | O | +| | Working/Active
Protection/Standby | [r=null,
b=normal] | | | | | | | | | | | | | | | +| G | Manual Switch | MS | →A | →A | →B | →B | →B | →A | (→G) | (→G)
or →A f) | O | O | O | O | O | O | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| H | Manual Switch | MS | →A | →A | →B | →B | →B | →A | O | (→H) | O | O | O | O | O | O | +| | Working/Active
Protection/Standby | [r=null,
b=normal] | | | | | | | | | | | | | | | +| I | Wait to Restore | WTR | →A | →A | →B | →B | →B | →A | →B | →A | (→I) | O | O | N/A | O | O | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| K | Exercise | EXER | →A | →A | →B | →B | →B | →A | →B | →A | N/A | (→K) | (→K) | O | N/A | O | +| | Working/Active
Protection/Standby | [r=null,
b=normal] | | | | | | | | | | | | | | | +| M | Reverse Request | RR | →A | →A | →B | →B | →B | →A | →B | →A | N/A | (→M) | →A | →A | N/A | O | +| | Working/Active
Protection/Standby | [r=null,
b=normal] | | | | | | | | | | | | | | | + +**Table A.6 – State transition by far-end requests (1+1, bidirectional, revertive mode)** + +NOTE 1 – "N/A" means that the event is not expected to happen for the State. However if it does happen, the event should be ignored. + +NOTE 2 – "O" means that the request shall be overruled by the existing condition because it has an equal or a lower priority. + +NOTE 3 – "(□X)" represents that the state is not changed and remains the same state. + +a) If SF is reasserted. + +b) If SF-P is reasserted. + +c) If the previous local state is SF (or SD (W) if applicable, see clause 11.13). + +d) If SD (W) is reasserted. + +e) If SD (P) is reasserted. + +f) Only if the far-end request is due to the simultaneous application of a manual switch to working command at the far end (i.e., no NR request acknowledging the local MS state received previously from the far end) + +## A.4 State transition for 1+1 bidirectional switching with non-revertive mode + +### A.4.1 Local requests + +Table A.7 shows the state transition by a local request for the 1+1 bidirectional protection switching in non-revertive mode. + +**Table A.7 – State transition by local requests (1+1, bidirectional, non-revertive mode)** + +| State | | Signalled APS | Local request | | | | | | | | | | | | | | +|-------|-----------------------------------|--------------------|---------------|---------------|-----------------------------|--------------------------|--------------------------------|-----------------------------|-----------------------------|-------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|------------------------------------------------------------------------------------------------------|----------| +| | | | a | b | c | d | e | f | g | h | i | j | k | l | m | n | +| | | | Lockout | Forced switch | SF on working a) | Working recovers from SF | SF on protection a) | Protection recovers from SF | SD on working a) | Working recover from SD | SD on protection a) | Protection recovers from SD | Manual switch to protection | Manual switch to working | Clear | Exercise | +| A | No Request | NR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | →K | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | +| B | No Request | NR | →C | →D | →E | O | →F | N/A | →P | O | →Q | N/A | →G | →H | N/A | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| C | Lockout | LO | O | O | O | O | O | O | O | O | O | O | O | O | →A | O | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | or
→E b)
or
→F c)
or
→P d)
or
→Q e) | | + +**Table A.7 – State transition by local requests (1+1, bidirectional, non-revertive mode)** + +| State | | Signalled APS | Local request | | | | | | | | | | | | | | +|-------|-----------------------------------|--------------------|---------------|---------------|-----------------------------|--------------------------------------------|--------------------------------|-------------------------------------------------------------------|-----------------------------|-------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|----------------------------------------------------------------------------|----------| +| | | | a | b | c | d | e | f | g | h | i | j | k | l | m | n | +| | | | Lockout | Forced switch | SF on working a) | Working recovers from SF | SF on protection a) | Protection recovers from SF | SD on working a) | Working recover from SD | SD on protection a) | Protection recovers from SD | Manual switch to protection | Manual switch to working | Clear | Exercise | +| D | Forced Switch | FS | →C | O | O | O | →F | N/A | O | O | O | O | O | O | →J | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | or
→E b)
or
→P d)
or
→Q e) | | +| E | Signal Fail (W) | SF | →C | →D | N/A | →J | →F | N/A | O | O | O | O | O | O | N/A | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | or →P d)
or →Q e) | | | | | | | | | | | +| F | Signal Fail (P) | SF-P | →C | O | O | O | N/A | →A | O | O | O | O | O | O | N/A | O | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | or →E b)
or →P d)
or →Q e) | | | | | | | | | +| P | Signal Degrade (W) | SD | →C | →D | →E | N/A | →F | N/A | N/A | →J | O | O | O | O | N/A | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | or →Q e) | | | | | | | +| Q | Signal Degrade (P) | SD | →C | →D | →E | N/A | →F | N/A | O | O | N/A | →A | O | O | N/A | O | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | or →P d) | | | | | +| G | Manual Switch | MS | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | O | O | →J | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| H | Manual Switch | MS | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | O | O | →A | O | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | +| J | Do Not Revert | DNR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | →L | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| K | Exercise | EXER | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | →A | O | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | + +**Table A.7 – State transition by local requests (1+1, bidirectional, non-revertive mode)** + +| State | | Signalled APS | Local request | | | | | | | | | | | | | | +|-------|-----------------------------------|--------------------|---------------|---------------|-----------------------------|--------------------------|--------------------------------|-----------------------------|-----------------------------|-------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|-------|----------| +| | | | a | b | c | d | e | f | g | h | i | j | k | l | m | n | +| | | | Lockout | Forced switch | SF on working a) | Working recovers from SF | SF on protection a) | Protection recovers from SF | SD on working a) | Working recover from SD | SD on protection a) | Protection recovers from SD | Manual switch to protection | Manual switch to working | Clear | Exercise | +| L | Exercise | EXER | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | →J | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| M | Reverse Request | RR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | →K | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | +| N | Reverse Request | RR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | →L | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | + +NOTE 1 – "N/A" means that the event is not expected to happen for the State. However if it does happen, the event should be ignored. +NOTE 2 – "O" means that the request shall be overruled by the existing condition because it has an equal or a lower priority. +NOTE 3 – "(□X)" represents that the state is not changed and remains the same state. +a) Signal fail or signal degrade on working or protection is input to the local priority logic only if the signal fail or signal degrade still exists after hold-off timer expires. +b) If SF is reasserted. +c) If SF-P is reasserted. +d) If SD (W) is reasserted. +e) If SD (P) is reasserted. + +### A.4.2 Far-end requests + +Table A.8 shows the state transition by a far-end request received by APS for the 1+1 bidirectional protection switching in non-revertive mode. + +**Table A.8 – State transition by far-end requests (1+1 bidirectional, non-revertive mode)** + +| State | | Signalled APS | Received far-end request | | | | | | | | | | | | | | | | +|-------|-----------------------------------|--------------------|--------------------------|--------------------|--------------|--------------|--------------|--------------------|--------------|--------------------|--------------|--------------------|--------------|--------------------|--------------|------------------------------------------------------------------------------------------|--------------|--------------| +| | | | o | p | q | r | s | t | u | v | w | x | y | z | aa | ab | ac | ad | +| | | | LO | SF-P | FS | SF | SD | SD | MS | MS | WTR | EXER | EXER | RR | RR | NR | NR | DNR | +| | | | [r=null, b=normal] | [r=null, b=normal] | [r/b=normal] | [r/b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r/b=normal] | +| A | No Request | NR | (→A) | (→A) | →B | →B | →B | (→A) | →B | (→A) | →B | →M | N/A | (→A) | N/A | (→A) | (→A) | →J | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | or →E a)
or →F b)
or →P c)
or →Q d) | | | +| B | No Request | NR | →A | →A | (→B) | (→B) | (→B) | →A | (→B) | →A | (→B) | N/A | N/A | N/A | N/A | →A | →J | →J | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | or →E a)
or →P c) | | | +| C | Lockout | LO | (→C) | O | O | O | O | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | | | +| D | Forced Switch | FS | →A | →A | (→D) | O | O | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | | +| E | Signal Fail (W) | SF | →A | →A | →B | (→E) | O | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | | +| F | Signal Fail (P) | SF-P | →A | (→F) | O | O | O | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | | | + +**Table A.8 – State transition by far-end requests (1+1 bidirectional, non-revertive mode)** + +| State | | Signalled APS | Received far-end request | | | | | | | | | | | | | | | | +|-------|-----------------------------------|--------------------|--------------------------|--------------------|--------------|--------------|--------------|--------------------|--------------|-----------------------------|--------------|--------------------|--------------|--------------------|--------------|--------------------|--------------|--------------| +| | | | o | p | q | r | s | t | u | v | w | x | y | z | aa | ab | ac | ad | +| | | | LO | SF-P | FS | SF | SD | SD | MS | MS | WTR | EXER | EXER | RR | RR | NR | NR | DNR | +| | | | [r=null, b=normal] | [r=null, b=normal] | [r/b=normal] | [r/b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r/b=normal] | +| P | Signal Degrade (W) | SD | →A | →A | →B | →B | (→P) | O | O | O | O | O | O | O | O | O | O | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | | +| Q | Signal Degrade (P) | SD | →A | →A | →B | →B | O | (→Q) | O | O | O | O | O | O | O | O | O | O | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | | | +| G | Manual Switch | MS | →A | →A | →B | →B | →B | →A | (→G) | (→G)
or →A e) | O | O | O | O | O | O | O | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | | +| H | Manual Switch | MS | →A | →A | →B | →B | →B | →A | O | (→H) | O | O | O | O | O | O | O | O | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | | | +| J | Do Not Revert | DNR | →A | →A | →B | →B | →B | →A | →B | →A | →B | N/A | →N | N/A | (→J) | O | O | (→J) | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | | +| K | Exercise | EXER | →A | →A | →B | →B | →B | →A | →B | →A | →B | (→K) | N/A | (→K) | N/A | O | N/A | N/A | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | | | + +**Table A.8 – State transition by far-end requests (1+1 bidirectional, non-revertive mode)** + +| State | | Signalled APS | Received far-end request | | | | | | | | | | | | | | | | +|-------|-----------------------------------|--------------------|--------------------------|--------------------|--------------|--------------|--------------|--------------------|--------------|--------------------|--------------|--------------------|--------------|--------------------|--------------|--------------------|--------------|--------------| +| | | | o | p | q | r | s | t | u | v | w | x | y | z | aa | ab | ac | ad | +| | | | LO | SF-P | FS | SF | SD | SD | MS | MS | WTR | EXER | EXER | RR | RR | NR | NR | DNR | +| | | | [r=null, b=normal] | [r=null, b=normal] | [r/b=normal] | [r/b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r=null, b=normal] | [r/b=normal] | [r/b=normal] | +| L | Exercise | EXER | →A | →A | →B | →B | →B | →A | →B | →A | →B | N/A | (→L) | N/A | (→L) | N/A | O | O | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | | +| M | Reverse Request | RR | →A | →A | →B | →B | →B | →A | →B | →A | →B | (→M) | N/A | →A | N/A | →A | N/A | N/A | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | | | +| N | Reverse Request | RR | →A | →A | →B | →B | →B | →A | →B | →A | →B | N/A | (→N) | N/A | →J | N/A | N/A | □J | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | | + +NOTE 1 – "N/A" means that the event is not expected to happen for the State. However if it does happen, the event should be ignored. + +NOTE 2 – "O" means that the request shall be overruled by the existing condition because it has an equal or a lower priority. + +NOTE 3 – "(□X)" represents that the state is not changed and remains the same state. + +a) If SF is reasserted. + +b) If SF-P is reasserted. + +c) If SD (W) is reasserted. + +d) If SD (P) is reasserted. + +e) Only if the far-end request is due to the simultaneous application of a manual switch to working command at the far end (i.e., no NR request acknowledging the local MS state received previously from the far end) + +## A.5 State transition for 1+1 unidirectional switching with revertive mode + +### A.5.1 Local requests + +Table A.9 shows the state transition by a local request for the 1+1 unidirectional protection switching in revertive mode. + +**Table A.9 – State transition by local requests (1+1, unidirectional, revertive mode)** + +| State | | Signalled
APS | Local request | | | | | | | | | | | | | | | +|-------|--------------------------------------|-----------------------|---------------|------------------|-----------------------------------|--------------------------------------------|----------------------------------------|-------------------------------------------------------------------|--------------------------------|--------------------------------|----------------------------------------|-----------------------------------|--------------------------------------|-----------------------------------|------------------------------------------------------------------------------------------|---------------|-------------------------| +| | | | a | b | c | d | e | f | g | h | i | j | k | l | m | n | o | +| | | | Lockout | Forced
switch | SF on
working
a) | Working
recovers
from SF | SF on
protec-
tion a) | Protection
recovers
from SF | SD on
working a) | Working
recovers
from SD | SD on
protec-
tion a) | Protection
recovers
from SD | Manual
switch
to
protection | Manual
switch
to
working | Clear | Exerci-
se | WTR
timer
expires | +| A | No Request | NR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | N/A | N/A | +| | Working/Active
Protection/Standby | [r=null,
b=normal] | | | | | | | | | | | | | | | | +| C | Lockout | LO | O | O | O | O | O | O | O | O | O | O | O | O | (→A) | N/A | N/A | +| | Working/Active
Protection/Standby | [r=null,
b=normal] | | | | | | | | | | | | | or →E b)
or →F c)
or →P d)
or →Q e) | | | +| D | Forced Switch | FS | →C | O | O | O | →F | N/A | O | O | O | O | O | O | (→A) | N/A | N/A | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | | | | | | | | | | or →E b)
or →P d)
or →Q e) | | | +| E | Signal Fail (W) | SF | →C | →D | N/A | →I | →F | N/A | O | O | O | O | O | O | N/A | N/A | N/A | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | or →P d)
or →Q e) | | | | | | | | | | | | +| F | Signal Fail (P) | SF-P | →C | O | O | O | N/A | →A | O | O | O | O | O | O | N/A | N/A | N/A | +| | Working/Active
Protection/Standby | [r=null,
b=normal] | | | | | | or →E b)
or →P d)
or →Q e) | | | | | | | | | | +| P | Signal Degrade (W) | SD | →C | →D | →E | N/A | →F | N/A | N/A | →I | O | O | O | O | N/A | N/A | N/A | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | | | | | or →Q e) | | | | | | | | +| Q | Signal Degrade (P) | SD | →C | →D | →E | N/A | →F | N/A | O | O | N/A | →A | O | O | N/A | N/A | N/A | +| | Working/Active
Protection/Standby | [r=null,
b=normal] | | | | | | | | | | or →P d) | | | | | | +| G | Manual Switch | MS | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | O | O | →A | N/A | N/A | +| | Working/Standby
Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | + +**Table A.9 – State transition by local requests (1+1, unidirectional, revertive mode)** + +| State | | Signalled APS | Local request | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|--------------------|---------------|---------------|-----------------------------|--------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|-------|----------|-------------------| +| | | | a | b | c | d | e | f | g | h | i | j | k | l | m | n | o | +| | | | Lockout | Forced switch | SF on working a) | Working recovers from SF | SF on protection a) | Protection recovers from SF | SD on working a) | Working recovers from SD | SD on protection a) | Protection recovers from SD | Manual switch to protection | Manual switch to working | Clear | Exercise | WTR timer expires | +| H | Manual Switch | MS | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | O | O | →A | N/A | N/A | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | | +| I | Wait to Restore | WTR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | →A | N/A | →A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | | +| NOTE 1 – Signalled APS is communicated in the case of 1+1 unidirectional protection switching with APS communication but does not trigger any state transition. | | | | | | | | | | | | | | | | | | +| NOTE 2 – "N/A" means that the event is not expected to happen for the State. However if it does happen, the event should be ignored. | | | | | | | | | | | | | | | | | | +| NOTE 3 – "O" means that the request shall be overruled by the existing condition because it has an equal or a lower priority. | | | | | | | | | | | | | | | | | | +| NOTE 4 – "(□X)" represents that the state is not changed and remains the same state. | | | | | | | | | | | | | | | | | | +| a) Signal fail or signal degrade on working or protection is input to the local priority logic only if the signal fail or signal degrade still exists after hold-off timer expires. | | | | | | | | | | | | | | | | | | +| b) If SF is reasserted. | | | | | | | | | | | | | | | | | | +| c) If SF-P is reasserted. | | | | | | | | | | | | | | | | | | +| d) If SD (W) is reasserted. | | | | | | | | | | | | | | | | | | +| e) If SD (P) is reasserted. | | | | | | | | | | | | | | | | | | + +## A.6 State transition for 1+1 unidirectional switching with non-revertive mode + +### A.6.1 Local requests + +Table A.10 shows the state transition by a local request for the 1+1 unidirectional protection switching in non-revertive mode. + +**Table A.10 – State transition by local requests (1+1, unidirectional, non-revertive mode)** + +| State | | Signalled APS | Local request | | | | | | | | | | | | | | +|-------|-----------------------------------|--------------------|---------------|---------------|-----------------------------|--------------------------------------------|--------------------------------|-------------------------------------------------------------------|-----------------------------|--------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|------------------------------------------------------------------------------------------|----------| +| | | | a | b | c | d | e | f | g | h | i | j | k | l | m | n | +| | | | Lockout | Forced switch | SF on working a) | Working recovers from SF | SF on protection a) | Protection recovers from SF | SD on working a) | Working recovers from SD | SD on protection a) | Protection recovers from SD | Manual switch to protection | Manual switch to working | Clear | Exercise | +| A | No Request | NR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | N/A | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | +| C | Lockout | LO | O | O | O | O | O | O | O | O | O | O | O | O | →A | N/A | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | or →E b)
or →F c)
or →P d)
or →Q e) | | +| D | Forced Switch | FS | →C | O | O | O | →F | N/A | O | O | O | O | O | O | →J | N/A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | or →E b)
or →P d)
or →Q e) | | +| E | Signal Fail (W) | SF | →C | →D | N/A | →J | →F | N/A | O | O | O | O | O | O | N/A | N/A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | or →P d)
or →Q e) | | | | | | | | | | | +| F | Signal Fail (P) | SF-P | →C | O | O | O | N/A | →A | O | O | O | O | O | O | N/A | N/A | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | or →E b)
or →P d)
or →Q e) | | | | | | | | | +| P | Signal Degrade (W) | SD | →C | →D | →E | N/A | →F | N/A | N/A | →J | O | O | O | O | N/A | N/A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | or →Q e) | | | | | | | +| Q | Signal Degrade (P) | SD | →C | →D | →E | N/A | →F | N/A | O | O | N/A | →A | O | O | N/A | N/A | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | or →P d) | | | | | + +**Table A.10 – State transition by local requests (1+1, unidirectional, non-revertive mode)** + +| State | | Signalled APS | Local request | | | | | | | | | | | | | | +|-------|-----------------------------------|--------------------|---------------|---------------|-----------------------------|--------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|--------------------------------|-----------------------------|-----------------------------|--------------------------|-------|----------| +| | | | a | b | c | d | e | f | g | h | i | j | k | l | m | n | +| | | | Lockout | Forced switch | SF on working a) | Working recovers from SF | SF on protection a) | Protection recovers from SF | SD on working a) | Working recovers from SD | SD on protection a) | Protection recovers from SD | Manual switch to protection | Manual switch to working | Clear | Exercise | +| G | Manual Switch | MS | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | O | O | →J | N/A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | +| H | Manual Switch | MS | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | O | O | →A | N/A | +| | Working/Active Protection/Standby | [r=null, b=normal] | | | | | | | | | | | | | | | +| J | Do Not Revert | DNR | →C | →D | →E | N/A | →F | N/A | →P | N/A | →Q | N/A | →G | →H | N/A | N/A | +| | Working/Standby Protection/Active | [r/b=normal] | | | | | | | | | | | | | | | + +NOTE 1 – Signalled APS is communicated in the case of 1+1 unidirectional protection switching with APS communication but does not trigger any state transition. +NOTE 2 – "N/A" means that the event is not expected to happen for the State. However if it does happen, the event should be ignored. +NOTE 3 – "O" means that the request shall be overruled by the existing condition because it has an equal or a lower priority. +a) Signal fail or signal degrade on working or protection is input to the local priority logic only if the signal fail or signal degrade still exists after hold-off timer expires. +b) If SF is reasserted. +c) If SF-P is reasserted. +d) If SD (W) is reasserted. +e) If SD (P) is reasserted. + +# Appendix I + +## Operation example of 1-phase APS protocol + +(This appendix does not form an integral part of this Recommendation.) + +## I.1 Introduction + +Operation examples of 1-phase APS protocol (1:1, revertive and non-revertive modes) are shown here. + +## I.2 Example scenario + +### I.2.1 Revertive mode + +This example assumes the scenario below: + +- 1) The protected domain is operating without any defect (working entity is selected); +- 2) Then, SF (signal fail) occurs in the west to east direction (switches to protection entity); +- 3) Then, this defect is repaired (enters WTR state, maintains to select protection entity); +- 4) Then, WTR timer expires (switches to working entity). + +### I.2.2 Non-revertive mode + +This example assumes the scenario below: + +- 1) The protected domain is operating without any defect (working entity is selected); +- 2) Then, SF (signal fail) occurs in the west to east direction (switches to protection entity); +- 3) Then, this defect is repaired (enters DNR state, maintains to select protection entity). + +### I.2.3 Signal fail and forced switch + +This example assumes the scenario below: + +- 1) SF occurs in the west to east direction (switches to protection entity); +- 2) Then, the FS command is accepted at east (enters FS state); +- 3) Then, FS is cleared at east and SF is reasserted at east. + +## I.3 APS protocol examples + +APS protocol examples are shown in Figure I.1 (revertive mode), Figure I.2 (non-revertive mode) and Figure I.3 (SF and FS). + +![Sequence diagram for Figure I.1 (revertive mode) showing the protocol interaction between West and East nodes. The sequence starts with 'No defects, selector and bridge select working entity' on both sides. A failure occurs on the working entity (W -> E). The West node sends an SF (r/b = normal traffic signal) to the East node. The East node declares SF and selects the protection entity. The West node detects the far end request and selects the protection entity. The East node confirms the far end is also selecting the protection entity. The working entity is repaired. The West node sends a WTR (r/b = normal traffic signal) to the East node. The East node enters the Wait-to-restore state. After the WTR time expires, the West node sends an NR (r/b = null) to the East node. The East node selects the working entity. The West node detects the far end request has been cleared and selects the working entity. The East node confirms the far end is also selecting the working entity.](cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg) + +West + +No defects, selector and bridge select working entity + +NR (r/b = null) + +Working entity (W → E) fails + +SF (r/b = normal traffic signal) + +Detect far end request, selector and bridge select protection entity + +NR (r/b = normal traffic signal) + +Working entity (W → E) repaired + +WTR (r/b = normal traffic signal) + +WTR time + +NR (r/b = null) + +Detect far end request has been cleared, selector and bridge select working entity + +East + +No defects, selector and bridge select working entity + +SF is declared, selector and bridge select protection entity + +It is confirmed that the far end is also selecting protection entity + +SF is cleared, Wait-to-restore state is entered + +WTR timer expires, selector and bridge select working entity + +It is confirmed that the far end is also selecting working entity + +Sequence diagram for Figure I.1 (revertive mode) showing the protocol interaction between West and East nodes. The sequence starts with 'No defects, selector and bridge select working entity' on both sides. A failure occurs on the working entity (W -> E). The West node sends an SF (r/b = normal traffic signal) to the East node. The East node declares SF and selects the protection entity. The West node detects the far end request and selects the protection entity. The East node confirms the far end is also selecting the protection entity. The working entity is repaired. The West node sends a WTR (r/b = normal traffic signal) to the East node. The East node enters the Wait-to-restore state. After the WTR time expires, the West node sends an NR (r/b = null) to the East node. The East node selects the working entity. The West node detects the far end request has been cleared and selects the working entity. The East node confirms the far end is also selecting the working entity. + +G.8031-Y1342(15)\_FI.1 + +| | | | | +|-----|---------------------------------|-------|------------------------| +| DNR | Do-Not-Revert | SF | Signal failure | +| NR | No request | WTR | Wait-To-Restore | +| r/b | Requested signal/bridged signal | W → E | West to east direction | + +**Figure I.1 – Protocol example (revertive mode)** + +![Sequence diagram for Figure I.2 (non-revertive mode) showing the protocol interaction between West and East nodes. The sequence starts with 'No defects, selector and bridge select working entity' on both sides. A failure occurs on the working entity (W -> E). The West node sends an SF (r/b = normal traffic signal) to the East node. The East node declares SF and selects the protection entity. The West node detects the far end request and selects the protection entity. The East node confirms the far end is also selecting the protection entity. The working entity is repaired. The West node sends a DNR (r/b = normal traffic signal) to the East node. The East node enters the Do-Not-Revert state. The West node sends another DNR (r/b = normal traffic signal) to the East node. The East node confirms the state with a 'no change' response.](0a06de972d61ab9bb901bd74dd4ff51f_img.jpg) + +West + +No defects, selector and bridge select working entity + +NR (r/b = null) + +Working entity (W → E) fails + +SF (r/b = normal traffic signal) + +Detect far end request, selector and bridge select protection entity + +NR (r/b = normal traffic signal) + +Working entity (W → E) repaired + +DNR (r/b = normal traffic signal) + +DNR (r/b = normal traffic signal) + +(no change) + +East + +No defects, selector and bridge select working entity + +SF is declared, selector and bridge select protection entity + +It is confirmed that the far end is also selecting protection entity + +SF is cleared, Do-Not-Revert state is entered + +Sequence diagram for Figure I.2 (non-revertive mode) showing the protocol interaction between West and East nodes. The sequence starts with 'No defects, selector and bridge select working entity' on both sides. A failure occurs on the working entity (W -> E). The West node sends an SF (r/b = normal traffic signal) to the East node. The East node declares SF and selects the protection entity. The West node detects the far end request and selects the protection entity. The East node confirms the far end is also selecting the protection entity. The working entity is repaired. The West node sends a DNR (r/b = normal traffic signal) to the East node. The East node enters the Do-Not-Revert state. The West node sends another DNR (r/b = normal traffic signal) to the East node. The East node confirms the state with a 'no change' response. + +G.8031-Y1342(15)\_FI.2 + +| | | | | +|-----|---------------------------------|-------|------------------------| +| NR | No request | WTR | Wait-To-Restore | +| r/b | Requested signal/bridged signal | DNR | Do-Not-Revert | +| SF | Signal failure | W → E | West to east direction | + +**Figure I.2 – Protocol example (non-revertive mode)** + +![Sequence diagram illustrating the protocol for Signal Failure (SF) and Forced Switch (FS) between West and East entities. The diagram shows the exchange of SF, NR, and FS signals and the resulting state changes.](c0b9e5fc63e19306394e0d4249da62cd_img.jpg) + +The diagram illustrates the protocol interaction between a West entity and an East entity for Signal Failure (SF) and Forced Switch (FS) management. The sequence of events is as follows: + +- Working transport entity (W → E) fails**: Indicated by a crossed-out arrow from West to East. +- SF (r/b = normal traffic signal)**: Sent from East to West. +- NR (r/b = normal traffic signal)**: Sent from West to East. +- FS (r/b = normal traffic signal)**: Sent from West to East. +- NR (r/b = normal traffic signal) (no change)**: Sent from East to West. +- SF (r/b = normal traffic signal)**: Sent from East to West. + +State changes and actions: + +- East side**: + - Upon receiving SF: **SF is declared, selector and bridge select protection entity**. + - Upon receiving FS: **Local request FS is declared, FS state is entered**. + - Upon receiving NR (no change): **Local request clear is declared, SF is reasserted**. +- West side**: + - Upon receiving SF: **Detect far end request, selector and bridge select protection entity**. + +G.8031-Y.1342(15)\_FI.3 + +| | | | | +|-----|---------------------------------|-------|------------------------| +| NR | No request | FS | Forced switch | +| r/b | Requested signal/bridged signal | W → E | West to east direction | +| SF | Signal failure | | | + +Sequence diagram illustrating the protocol for Signal Failure (SF) and Forced Switch (FS) between West and East entities. The diagram shows the exchange of SF, NR, and FS signals and the resulting state changes. + +**Figure I.3 – Protocol example (SF and FS)** + +# Appendix II + +## Interaction between Ethernet protection switching and STP + +(This appendix does not form an integral part of this Recommendation.) + +This appendix shows that a bridge port within the protected domain must not participate in a spanning tree protocol (STP) domain if it is to avoid undesirable interaction between STP and Ethernet protection switching. One way to ensure this is to disable STP in the protected domain. However, domains outside of the protected domain could have STP enabled. Another way to ensure this is if the working and protection transport entities belong to two different STP domains. These two scenarios are discussed in this clause. + +Figure II.1 shows the first way introduced above, the protected domain and STP domains (#1 and #2) are segmented vertically and do not overlap. Bridges #A and #B at the edge of the protected domain and STP domains interconnect the STP domains without any loop problem. + +The second case mentioned above is shown in Figure II.2. STP domains (#1 and #2) are segmented horizontally, and provide two transport entities for Ethernet protection switching. Figure II.3 shows that the working and protection transport entities for Ethernet protection switching are provisioned separately within different STP domains. In this example, each VLAN and network resource would be used effectively. + +![Diagram of Figure II.1: No overlapping between the protected domain and STP. It shows a central orange hexagon labeled 'Protected domain' connected to two external STP domains. On the left, 'Bridge #A' connects the protected domain to 'STP domain #1' (yellow cloud), which is part of 'STP section #1'. On the right, 'Bridge #B' connects the protected domain to 'STP domain #2' (purple cloud), which is part of 'STP section #2'. Dashed vertical lines separate the STP sections from the protected domain. A reference code 'G.8031-Y.1342(15)_FII.1' is at the bottom right.](4842f073775fb1e84d101c02fd74e59e_img.jpg) + +Diagram of Figure II.1: No overlapping between the protected domain and STP. It shows a central orange hexagon labeled 'Protected domain' connected to two external STP domains. On the left, 'Bridge #A' connects the protected domain to 'STP domain #1' (yellow cloud), which is part of 'STP section #1'. On the right, 'Bridge #B' connects the protected domain to 'STP domain #2' (purple cloud), which is part of 'STP section #2'. Dashed vertical lines separate the STP sections from the protected domain. A reference code 'G.8031-Y.1342(15)\_FII.1' is at the bottom right. + +Figure II.1 – No overlapping between the protected domain and STP + +![Diagram of Figure II.2: Overlapping between the protected domain and STP. It shows two STP domains, 'STP domain #1' (yellow cloud) and 'STP domain #2' (purple cloud), both within a larger 'Protected domain' (indicated by a long double-headed arrow at the bottom). 'Bridge #A' on the left has a 'Working' path to 'STP domain #1' and a 'Protection' path (dashed line) to 'STP domain #2'. 'Bridge #B' on the right has a 'Working' path to 'STP domain #1' and a 'Protection' path (dashed line) to 'STP domain #2'. A shorter double-headed arrow labeled 'STP section' is shown below 'STP domain #2'. A reference code 'G.8031-Y.1342(15)_FII.2' is at the bottom right.](91b12db3c85bbf466ad27eb3665a1b06_img.jpg) + +Diagram of Figure II.2: Overlapping between the protected domain and STP. It shows two STP domains, 'STP domain #1' (yellow cloud) and 'STP domain #2' (purple cloud), both within a larger 'Protected domain' (indicated by a long double-headed arrow at the bottom). 'Bridge #A' on the left has a 'Working' path to 'STP domain #1' and a 'Protection' path (dashed line) to 'STP domain #2'. 'Bridge #B' on the right has a 'Working' path to 'STP domain #1' and a 'Protection' path (dashed line) to 'STP domain #2'. A shorter double-headed arrow labeled 'STP section' is shown below 'STP domain #2'. A reference code 'G.8031-Y.1342(15)\_FII.2' is at the bottom right. + +Figure II.2 – Overlapping between the protected domain and STP + +![Diagram illustrating the overlapping between the protected domain and STP per VLAN. It shows two bridges, Bridge #A and Bridge #B, connected by two STP domains: STP domain #1 (yellow cloud) and STP domain #2 (purple cloud). Bridge #A is connected to VLAN #1 (red line) and VLAN #2 (blue line). Bridge #B is connected to a red line and a blue line. The diagram shows 'Working' paths (solid lines) and 'Protection' paths (dashed lines) for both domains. The 'STP section' is the segment between the two bridges, and the 'Protected domain' is the segment between Bridge #A and Bridge #B. The text 'G.8031-Y.1342(15)_FII.3' is at the bottom right.](c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg) + +The diagram illustrates a network configuration involving two bridges, Bridge #A and Bridge #B, and two STP domains: STP domain #1 (yellow cloud) and STP domain #2 (purple cloud). Bridge #A is connected to two VLANs: VLAN #1 (red line) and VLAN #2 (blue line). Bridge #B is connected to a red line and a blue line. The diagram shows 'Working' paths (solid lines) and 'Protection' paths (dashed lines) for both domains. For VLAN #1, the working path goes through STP domain #1 and the protection path through STP domain #2. For VLAN #2, the working path goes through STP domain #2 and the protection path through STP domain #1. The 'STP section' is the segment between the two bridges, and the 'Protected domain' is the segment between Bridge #A and Bridge #B. The text 'G.8031-Y.1342(15)\_FII.3' is at the bottom right. + +Diagram illustrating the overlapping between the protected domain and STP per VLAN. It shows two bridges, Bridge #A and Bridge #B, connected by two STP domains: STP domain #1 (yellow cloud) and STP domain #2 (purple cloud). Bridge #A is connected to VLAN #1 (red line) and VLAN #2 (blue line). Bridge #B is connected to a red line and a blue line. The diagram shows 'Working' paths (solid lines) and 'Protection' paths (dashed lines) for both domains. The 'STP section' is the segment between the two bridges, and the 'Protected domain' is the segment between Bridge #A and Bridge #B. The text 'G.8031-Y.1342(15)\_FII.3' is at the bottom right. + +**Figure II.3 – Overlapping between the protected domain and STP per VLAN** + +# Appendix III + +## MIPs for protection switching environment + +(This appendix does not form an integral part of this Recommendation.) + +## III.1 Introduction + +In this appendix, considerations and some configuration examples of maintenance entity group intermediate points (MIPs) for a protection switching environment are shown. + +## III.2 Considerations + +Figure III.1 shows an example of MEPs and MIPs configuration for protection switching. In Figure III.1, two pairs of MEPs are configured to monitor both the working and protection transport entities in MEG Level N. Also in MEG Level N+1, MEPs and MIPs are configured at each port as depicted in the figure. + +![Diagram of MEPs and MIPs for 1:1 bidirectional protection switching across three MEG levels.](ad555483986d7170a46ce72d164b5bc8_img.jpg) + +The diagram illustrates the configuration of Maintenance Entity Group (MEG) levels N, N+1, and N+2 for 1:1 bidirectional protection switching. The system is divided into WEST and EAST sections, connected by a 'Protected ETH SNC #1'. + +- WEST Section:** Contains an 'SNC protection switching process' block connected to 'ETH\_C' and 'ETH\_FP' ports. It houses two pairs of Maintenance End Points (MEPs) and Maintenance Intermediate Points (MIPs) for 'Working transport entity' and 'Protection transport entity'. +- EAST Section:** Similar to the WEST section, it contains an 'SNC protection switching process' block connected to 'ETH\_C' and 'ETH\_FP' ports, with corresponding MEPs and MIPs. +- MEG Level = N:** The lowest level, shown with dashed lines and symbols for active and standby transport entities. +- MEG Level = N+1:** The middle level, shown with solid lines. It features two MIPs (circled in red) on the standby transport entity. A red arrow points to them with the text: **These MIPs cannot be accessed**. Another red arrow points to the right MIP with the text: **Accessible MIP will be changed by PS**. +- MEG Level = N+2:** The highest level, shown with dashed lines and symbols for active and standby transport entities. + +**Legend:** + +- ETH\_FP: Two small circles. +- MEP: A triangle with a horizontal line. +- MIP: A double-headed arrow. +- MEP/MIP for active transport entity: A white triangle and a white double-headed arrow. +- MEP/MIP for standby transport entity: A grey triangle and a grey double-headed arrow. + +Diagram of MEPs and MIPs for 1:1 bidirectional protection switching across three MEG levels. + +G.8031-Y.1342(15)\_FIII.1 + +**Figure III.1 – MEPs and MIPs for 1:1 bidirectional protection switching** + +If 1:1 protection switching is configured, MIPs in MEG Level N+1 on the standby transport entity cannot be accessed by MEPs for the same MEG, and accessible MIPs will be changed by the protection switching. Therefore, MIPs in MEG Level N+1 shown in Figure III.1, appear to be unnecessary. + +Figure III.2 shows a configuration of MEPs and MIPs for a 1+1 unidirectional protection switching environment. In this case, a request/response communication between a MEP and a MIP cannot be made correctly. Therefore, MIPs in MEG Level N+1 shown in Figure III.2 also appear to be unnecessary. + +![Diagram of MEPs and MIPs for 1+1 unidirectional protection switching. The diagram is divided into WEST and EAST sections by a 'Protected ETH SNC #1' boundary. In the WEST section, an 'ETH_FP' (represented by two hexagons) is connected to an 'ETH_C' (represented by a circle). The 'ETH_C' is connected to an 'SNC protection switching process' (represented by a rectangle). This process is connected to a 'MEP' (represented by a triangle) and a 'MIP' (represented by a double-headed arrow). The 'MEP' is connected to a 'Working transport entity' (represented by a black line) and a 'Protection transport entity' (represented by a red line). The 'MIP' is also connected to both transport entities. The same configuration is shown in the EAST section. Below the main diagram, three horizontal layers are shown: 'MEG Level = N + 2', 'MEG Level = N + 1', and 'MEG Level = N'. In 'MEG Level = N + 2', there are dashed hexagons. In 'MEG Level = N + 1', there are triangles (MEPs) and double-headed arrows (MIPs) connected by red lines. In 'MEG Level = N', there are dashed triangles. A legend at the bottom left shows the symbols for 'ETH_FP', 'MEP', and 'MIP'. The text 'G.8031-Y.1342(15)_FIII.2' is in the bottom right corner.](fee87ee34f98efee162e918fbaeec613_img.jpg) + +Diagram of MEPs and MIPs for 1+1 unidirectional protection switching. The diagram is divided into WEST and EAST sections by a 'Protected ETH SNC #1' boundary. In the WEST section, an 'ETH\_FP' (represented by two hexagons) is connected to an 'ETH\_C' (represented by a circle). The 'ETH\_C' is connected to an 'SNC protection switching process' (represented by a rectangle). This process is connected to a 'MEP' (represented by a triangle) and a 'MIP' (represented by a double-headed arrow). The 'MEP' is connected to a 'Working transport entity' (represented by a black line) and a 'Protection transport entity' (represented by a red line). The 'MIP' is also connected to both transport entities. The same configuration is shown in the EAST section. Below the main diagram, three horizontal layers are shown: 'MEG Level = N + 2', 'MEG Level = N + 1', and 'MEG Level = N'. In 'MEG Level = N + 2', there are dashed hexagons. In 'MEG Level = N + 1', there are triangles (MEPs) and double-headed arrows (MIPs) connected by red lines. In 'MEG Level = N', there are dashed triangles. A legend at the bottom left shows the symbols for 'ETH\_FP', 'MEP', and 'MIP'. The text 'G.8031-Y.1342(15)\_FIII.2' is in the bottom right corner. + +**Figure III.2 – MEPs and MIPs for 1+1 unidirectional protection switching** + +As described above, configuring MIPs at anywhere inside the protected domain, for a higher MEG Level than that of MEPs which monitors both working and protection transport entities, appear to be unnecessary. + +## III.3 Configuration examples + +Figure III.3 shows two examples of possible MEPs and MIPs configuration. + +In the first example, shown in the middle of Figure III.3, no MIPs are configured in MEG Level N+1, but MEPs are configured instead. In this case, the MEG in MEG Level N+1 represents the protected domain. + +The second example is shown in the bottom of Figure III.3. In this configuration, MIPs are configured in MEG Level N+1 at the edge of the protected domain. + +MEPs and MIPs shown in both examples are fully accessible because they are not configured inside the protected domain. + +![Diagram illustrating configuration examples of MEPs and MIPs for protection switching environment. The diagram is divided into three horizontal sections representing different MEG levels. The top section shows a 'Protected ETH SNC' between 'WEST' and 'EAST' nodes, with 'Working transport entity' (solid line) and 'Protection transport entity' (dashed line). The middle section shows 'MEG Level = N + 2' and 'MEG Level = N + 1' with a note 'No MIP is needed here.' for the latter. The bottom section shows 'MEG Level = N + 1' with a note 'If no MEP is needed here, an MIP can be configured here.' and 'MEG Level = N'. A legend defines symbols for 'MEP/MIP for active transport entity' (white arrow) and 'MEP/MIP for standby transport entity' (grey arrow), with an 'OR' symbol between them. Other labels include 'SNC protection switching process', 'ETH_FF', and 'ETH_FP'.](5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg) + +Protected ETH SNC + +WEST EAST + +Working transport entity + +Protection transport entity + +SNC protection switching process + +ETH\_FF + +ETH\_FP + +MEG Level = N + 2 + +No MIP is needed here. + +MEG Level = N + 1 + +MEG Level = N + +MEP/MIP for active transport entity + +MEP/MIP for standby transport entity + +OR + +MEG Level = N + 1 + +If no MEP is needed here, an MIP can be configured here. + +MEG Level = N + +G.8031-Y.1342(15)\_FIII.3 + +Diagram illustrating configuration examples of MEPs and MIPs for protection switching environment. The diagram is divided into three horizontal sections representing different MEG levels. The top section shows a 'Protected ETH SNC' between 'WEST' and 'EAST' nodes, with 'Working transport entity' (solid line) and 'Protection transport entity' (dashed line). The middle section shows 'MEG Level = N + 2' and 'MEG Level = N + 1' with a note 'No MIP is needed here.' for the latter. The bottom section shows 'MEG Level = N + 1' with a note 'If no MEP is needed here, an MIP can be configured here.' and 'MEG Level = N'. A legend defines symbols for 'MEP/MIP for active transport entity' (white arrow) and 'MEP/MIP for standby transport entity' (grey arrow), with an 'OR' symbol between them. Other labels include 'SNC protection switching process', 'ETH\_FF', and 'ETH\_FP'. + +**Figure III.3 – Configuration examples of MEPs and MIPs for protection switching environment** + +# **Appendix IV** + +## **State transition diagrams using SDL** + +(This appendix does not form an integral part of this Recommendation.) + +## **IV.1 Introduction** + +In Appendix IV, diagrams using SDL for state transitions defined in Annex A are provided for information. + +## **IV.2 SDL diagrams** + +### **IV.2.1 1:1 bidirectional protection switching** + +The following diagrams define state transitions of 1:1 bidirectional protection switching both in revertive and non-revertive modes. + +![State transition diagram for NR(r/b=null) state in 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, DNR, RR, WTR) based on specific conditions like 'Switch to protection', 'Revertive Mode?', and 'Local SF/P?'. It includes a legend for revertive and non-revertive modes and terminal states labeled A through M.](352d21d1e740e4a58cb17ab8656cfad8_img.jpg) + +The diagram illustrates the state transitions for the NR(r/b=null) state in 1:1 bidirectional protection switching. It begins with an initial state 'NR' with 'No Request', 'W=act', and 'P=stb'. Transitions are triggered by various conditions such as 'SF' (Signal Fail), 'SF-P' (Signal Fail-Priority), 'LO' (Loss of Continuity), 'FS' (Failure State), 'SD' (Signal Degrade), 'SD-P' (Signal Degrade-Priority), 'MS' (Misconnection State), 'MS-W' (Misconnection State-Warning), and 'EXER' (Exercise). The diagram includes a legend for 'Only for revertive mode' (vertical stripes) and 'Only for Non-revertive mode' (cross-hatch). Terminal states are labeled A through M, with some states (B, J) marked with patterns indicating revertive or non-revertive modes. + +``` + +stateDiagram-v2 + [*] --> NR + state "NR" as NR { + No Request + W=act + P=stb + null | null + } + NR --> SF + NR --> SF-P + NR --> LO + NR --> FS + NR --> SD + NR --> SD-P + NR --> MS + NR --> MS-W + NR --> EXER + + SF --> SwitchToProtection1[Switch to protection] + SwitchToProtection1 --> SF + SF --> E + + SF-P --> SF-P + SF-P --> F + + LO --> LO + LO --> C + + FS --> SwitchToProtection2[Switch to protection] + SwitchToProtection2 --> FS + FS --> D + + SD --> SwitchToProtection3[Switch to protection] + SwitchToProtection3 --> SD + SD --> P + + SD-P --> SD_r_b_null[SD r/b=null] + SD_r_b_null --> Q + + MS --> SwitchToProtection4[Switch to protection] + SwitchToProtection4 --> MS + MS --> G + + MS-W --> MS_r_b_null[MS r/b=null] + MS_r_b_null --> H + + EXER --> EXER_r_b_null[EXER r/b=null] + EXER_r_b_null --> K + + LO --> LO + LO --> A + + SF-P --> SF-P + SF-P --> B + + FS --> FS + FS --> SwitchToProtection5[Switch to protection] + SwitchToProtection5 --> NR_r_b_normal[NR r/b=normal] + NR_r_b_normal --> B + + SF --> SF + SF --> A + + SD --> SD + SD --> A + + SD_r_b_null --> SD_r_b_null + SD_r_b_null --> B + + MS --> MS + MS --> SwitchToProtection6[Switch to protection] + SwitchToProtection6 --> NR_r_b_normal[NR r/b=normal] + NR_r_b_normal --> A + + MS_r_b_null --> MS_r_b_null + MS_r_b_null --> B + + WTR --> WTR + WTR --> SwitchToProtection7[Switch to protection] + SwitchToProtection7 --> NR_r_b_normal[NR r/b=normal] + NR_r_b_normal --> A + + DNR --> RevertiveMode{Revertive Mode?} + RevertiveMode -- Yes --> SwitchToProtection8[Switch to protection] + SwitchToProtection8 --> NR_r_b_normal[NR r/b=normal] + NR_r_b_normal --> B + + RevertiveMode -- No --> SwitchToProtection9[Switch to protection] + SwitchToProtection9 --> DNR_r_b_normal[DNR r/b=normal] + DNR_r_b_normal --> J + + EXER_r_b_null --> EXER_r_b_null + EXER_r_b_null --> RR_r_b_null[RR r/b=null] + RR_r_b_null --> M + + RR_r_b_null --> RR_r_b_null + RR_r_b_null --> A + + NR_r_b_normal --> NR_r_b_normal + NR_r_b_normal --> A + + NR_r_b_null --> LocalSF_P{Local SF/P?} + LocalSF_P -- No --> LocalSD_P{Local SD/P?} + LocalSD_P -- No --> A + LocalSD_P -- Yes --> SD-P + LocalSF_P -- Yes --> SF + LocalSF_P -- Yes --> SF-P + +``` + +State transition diagram for NR(r/b=null) state in 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, DNR, RR, WTR) based on specific conditions like 'Switch to protection', 'Revertive Mode?', and 'Local SF/P?'. It includes a legend for revertive and non-revertive modes and terminal states labeled A through M. + +Figure IV.1 – NR(r/b=null) state for 1:1 bidirectional protection switching + +![State transition diagram for NR(r/b=normal) state for 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, etc.) based on events like 'No Request', 'SF', 'SD', 'MS', etc., and conditions like 'Revertive Mode?' and 'Local SF?'. It includes a legend for revertive and non-revertive modes.](fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg) + +Only for revertive mode + +Only for Non-revertive mode + +The diagram illustrates the state transitions for the NR(r/b=normal) state in 1:1 bidirectional protection switching. It starts from a 'No Request' state (W=stb, P=act) and branches into various states based on events and conditions. + +**States and Transitions:** + +- NR (No Request):** Initial state with W=stb, P=act. Transitions to SF, Working recovers from SF, SF-P, LO, FS, SD, Working recovers from SD, SD-P, MS, MS-W, and EXER. +- SF (Signal Fail):** Leads to state SF, then exit E. +- Working recovers from SF:** Leads to exit B. +- SF-P (Signal Fail - Protection):** Leads to 'Switch to working', then state SF-P, then exit F. +- LO (Lockout of Protection):** Leads to 'Switch to working', then state LO, then exit C. +- FS (Forced Switch):** Leads to state FS, then exit D. +- SD (Signal Degrade):** Leads to state SD, then exit P. +- Working recovers from SD:** Leads to exit B. +- SD-P (Signal Degrade - Protection):** Leads to 'Switch to working', then state SD r/b=null, then exit Q. +- MS (Manual Switch):** Leads to state MS, then exit G. +- MS-W (Manual Switch to Working):** Leads to 'Switch to working', then state MS r/b=null, then exit H. +- EXER (Exercise):** Leads to exit B. + +**Lower Decision Logic:** + +- A secondary row of events (LO, SF-P, FS, SF, SD, SD r/b=null, MS, MS r/b=null, WTR) leads to various exits (B, A, B, A, B). +- NR r/b=normal** event leads to **Revertive Mode?** decision. + - If **Yes**: Checks **Previous local state?**. If 'SF (or SD (W) if applicable)', goes to **WTR** state (striped) then exit I. If 'Other', goes to 'Switch to working', then **NR r/b=null** state, then exit A. + - If **No**: Goes to **DNR** state (cross-hatched) then exit J. +- DNR** event leads to **Revertive Mode?** decision. If 'Yes', goes to exit B. If 'No', goes to exit J. +- NR r/b=null** event leads to **Local SF?** decision. If 'Yes', returns to top flow. If 'No', checks **Local SD?**. If 'Yes', returns to top flow. If 'No', goes to 'Switch to working', then **NR r/b=null** state, then exit A. + +State transition diagram for NR(r/b=normal) state for 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, etc.) based on events like 'No Request', 'SF', 'SD', 'MS', etc., and conditions like 'Revertive Mode?' and 'Local SF?'. It includes a legend for revertive and non-revertive modes. + +**Figure IV.2 – NR(r/b=normal) state for 1:1 bidirectional protection switching** + +![State transition diagram for LO(r/b=null) state for 1:1 bidirectional protection switching. The diagram shows a flow from input events to state transitions and terminal states.](1b23b78336d8bd286c653cbdb38428dd_img.jpg) + +``` + +graph TD + Start["C LO +Lockout +W=act P=stb +null null"] --> Inputs + subgraph Inputs + SF + WR_SF["Working recovers from SF"] + SF-P + PR_SF["Protection recovers from SF"] + LO + FS + end + Inputs --> Logic + subgraph Logic + SD + WR_SD["Working recovers from SD"] + SD-P + PR_SD["Protection recovers from SD"] + MS + MS-W + EXER + CLEAR + end + Logic --> Decisions + subgraph Decisions + SF_Local{Local SF-P?} + SD_Local{Local SD-P?} + end + Decisions --> Terminals + Terminals((C, E, P, A, Q, F)) + +``` + +The diagram illustrates the state transitions for the LO(r/b=null) state. It begins with a state box containing 'C', 'LO', 'Lockout', 'W=act P=stb', and 'null' values. Transitions lead to a sequence of states: SF, Working recovers from SF, SF-P, Protection recovers from SF, LO, and FS. A legend indicates 'Only for Non-revertive mode'. Further transitions include SD, Working recovers from SD, SD-P, Protection recovers from SD, MS, MS-W, EXER, and CLEAR. Decision diamonds for 'Local SF-P?' and 'Local SD-P?' lead to states like Switch to protection, SF, SD, NR r/b=null, SD r/b=null, and SF-P, which then lead to terminal states E, P, A, Q, and F. Other terminal states include C and D. + +State transition diagram for LO(r/b=null) state for 1:1 bidirectional protection switching. The diagram shows a flow from input events to state transitions and terminal states. + +Figure IV.3 – LO(r/b=null) state for 1:1 bidirectional protection switching + +![State transition diagram for FS(r/b=normal) state for 1:1 bidirectional protection switching. The diagram shows a flow from input events to state transitions and terminal states.](935075de5250cfe8aa0fb9d65d63dde5_img.jpg) + +``` + +graph TD + Start["D FS +Forced Switch +W=stb P=act +normal normal"] + subgraph Inputs_FS + SF_FS[SF] + WR_SF_FS["Working recovers from SF"] + SF-P_FS[SF-P] + LO_FS[LO] + FS_FS[FS] + SD_FS[SD] + WR_SD_FS["Working recovers from SD"] + SD-P_FS[SD-P] + PR_SD_FS["Protection recovers from SD"] + CLEAR_FS[CLEAR] + end + subgraph Logic_FS + MS_FS[MS] + MS-W_FS[MS-W] + EXER_FS[EXER] + end + subgraph Decisions_FS + Local_SF{Local SF?} + Local_SDP{Local SD-P?} + Revertive{Revertive Mode?} + end + +``` + +The diagram illustrates the state transitions for the FS(r/b=normal) state. It begins with a state box containing 'D', 'FS', 'Forced Switch', 'W=stb P=act', and 'normal' values. Transitions lead to a sequence of states: SF, Working recovers from SF, SF-P, LO, FS, SD, Working recovers from SD, SD-P, Protection recovers from SD, and CLEAR. Legends indicate 'Only for revertive mode' and 'Only for Non-revertive mode'. Further transitions include MS, MS-W, EXER, and CLEAR. Decision diamonds for 'Local SF?', 'Local SD-P?', and 'Revertive Mode?' lead to states like Switch to working, SF-P, LO, SD, NR r/b=null, DNR r/b=normal, SD r/b=null, and SF, which then lead to terminal states A, D, P, A, J, Q, and E. Other terminal states include F, C, and D. + +State transition diagram for FS(r/b=normal) state for 1:1 bidirectional protection switching. The diagram shows a flow from input events to state transitions and terminal states. + +Figure IV.4 – FS(r/b=normal) state for 1:1 bidirectional protection switching + +![State transition diagram for 1:1 bidirectional protection switching. The diagram shows transitions between various states (E, SF, LO, FS, SD, MS, etc.) based on Signal Fail (W) conditions and revertive/non-revertive modes. States are represented by ovals (initial/normal), rectangles (transitions), diamonds (decisions), and trapezoids (specific states). Arrows indicate the flow between these states, with some paths leading to numbered circles (A-J, P-J) and others to lettered circles (A, B, C, D, E, F, I, J).](15de63f0b5df62e6ab9164f2a72e2e33_img.jpg) + +Only for revertive mode + +Only for Non-revertive mode + +``` + +graph TD + Start[E SF Signal Fail W +W=stb P=act +normal normal] --> RecoverSF[Working recovers from SF] + Start --> SFP_T[SF-P] + Start --> LO_T[LO] + Start --> FS_T[FS] + Start --> SD_T[SD] + Start --> RecoverSD[Working recovers from SD] + Start --> SDP_T[SD-P] + Start --> RecoverSDProt[Protection recovers from SD] + + RecoverSF --> LocalSDP{Local SD/-P?} + LocalSDP -- Yes --> SD_State[SD] + LocalSDP -- No --> Revertive{Revertive Mode?} + Revertive -- Yes --> WTR_State[WTR] + Revertive -- No --> DNR_State[DNR] + + SD_State --> P((P)) + WTR_State --> I((I)) + DNR_State --> J((J)) + + SFP_T --> SwitchWorking1[Switch to working] + LO_T --> SwitchWorking2[Switch to working] + FS_T --> SwitchWorking3[Switch to working] + + SwitchWorking1 --> SFP_S[SF-P] --> F((F)) + SwitchWorking2 --> LO_S[LO] --> C((C)) + SwitchWorking3 --> FS_S[FS] --> D((D)) + + SD_T --> E_Circle((E)) + + RecoverSD --> MS_Group[MS / MS-W / EXER] + SDP_T --> MS_Group + RecoverSDProt --> MS_Group + + MS_Group --> LO_B[LO] + MS_Group --> SFP_B[SF-P] + MS_Group --> FS_B[FS] + MS_Group --> SF_B[SF] + MS_Group --> SD_B[SD] + MS_Group --> SD_null[SD r/b=null] + MS_Group --> MS_B[MS] + MS_Group --> MS_null[MS r/b=null] + MS_Group --> WTR_B[WTR] + + LO_B --> SwitchWorking4[Switch to working] --> NR_null[NR r/b=null] --> A((A)) + FS_B --> NR_normal[NR r/b=normal] --> B((B)) + SF_B --> EXER_null[EXER r/b=null] --> E_Circle2((E)) + SD_B --> EXER_normal[EXER r/b=normal] --> E_Circle2 + SD_null --> RR_null[RR r/b=null] --> E_Circle2 + MS_B --> RR_normal[RR r/b=normal] --> E_Circle2 + MS_null --> NR_null2[NR r/b=null] --> E_Circle2 + WTR_B --> NR_normal2[NR r/b=normal] --> E_Circle2 + WTR_B --> DNR_normal[DNR r/b=normal] --> E_Circle2 + +``` + +State transition diagram for 1:1 bidirectional protection switching. The diagram shows transitions between various states (E, SF, LO, FS, SD, MS, etc.) based on Signal Fail (W) conditions and revertive/non-revertive modes. States are represented by ovals (initial/normal), rectangles (transitions), diamonds (decisions), and trapezoids (specific states). Arrows indicate the flow between these states, with some paths leading to numbered circles (A-J, P-J) and others to lettered circles (A, B, C, D, E, F, I, J). + +**Figure IV.5 – SF(r/b=normal) state for 1:1 bidirectional protection switching** + +![State transition diagram for SF-P(r/b=null) state for 1:1 bidirectional protection switching. The diagram shows various states (SF, LO, FS, SD, MS, etc.) and transitions between them based on conditions like 'Signal Fail (P)', 'Local SF?', and 'Local SD-P?'. A note indicates it is 'Only for Non-revertive mode'.](af6c3f383ddc0c142cdd7e186cc78199_img.jpg) + +The diagram illustrates the state transitions for the SF-P(r/b=null) state in 1:1 bidirectional protection switching. It is specifically for non-revertive mode. + +**Initial State:** SF-P (Signal Fail (P), W=act P=stb). Transitions from this state lead to SF, Working recovers from SF, Protection recovers from SF, LO, FS, SD, Working recovers from SD, SD-P, and Protection recovers from SD. + +**Transitions from SF:** Leads to state F. + +**Transitions from Working recovers from SF:** Leads to state E. + +**Transitions from Protection recovers from SF:** Leads to a decision diamond 'Local SF?'. + + +- If 'Yes' (SF), leads to 'Switch to protection' (state P). +- If 'No', leads to another decision diamond 'Local SD-P?'. + - If 'Yes' (SD-P), leads to 'Switch to protection' (state P). + - If 'No', leads to state A (NR r/b=null). + +**Transitions from LO:** Leads to state C. + +**Transitions from FS:** Leads to state F. + +**Transitions from SD:** Leads to state Q (SD r/b=null). + +**Transitions from Working recovers from SD:** Leads to state MS. + +**Transitions from SD-P:** Leads to state MS-W. + +**Transitions from Protection recovers from SD:** Leads to state EXER. + +**Transitions from MS:** Leads to state MS (r/b=null). + +**Transitions from MS-W:** Leads to state MS (r/b=null). + +**Transitions from EXER:** Leads to state EXER (r/b=null). + +**Transitions from LO (second row):** Leads to state NR (r/b=null) (state A). + +**Transitions from SF-P (second row):** Leads to state F. + +**Transitions from FS (second row):** Leads to state EXER (r/b=null). + +**Transitions from SF (second row):** Leads to state EXER (r/b=null). + +**Transitions from SD (second row):** Leads to state RR (r/b=null). + +**Transitions from SD (r/b=null) (second row):** Leads to state RR (r/b=null). + +**Transitions from MS (second row):** Leads to state NR (r/b=null). + +**Transitions from MS (r/b=null) (second row):** Leads to state NR (r/b=null). + +**Transitions from WTR:** Leads to state DNR (r/b=null). + +State transition diagram for SF-P(r/b=null) state for 1:1 bidirectional protection switching. The diagram shows various states (SF, LO, FS, SD, MS, etc.) and transitions between them based on conditions like 'Signal Fail (P)', 'Local SF?', and 'Local SD-P?'. A note indicates it is 'Only for Non-revertive mode'. + +Figure IV.6 – SF-P(r/b=null) state for 1:1 bidirectional protection switching + +![State transition diagram for MS(r/b=normal) state for 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR) and sub-states (E, F, C, D, P, Q, G, A, J). It includes a legend for 'Only for revertive mode' and 'Only for Non-revertive mode'. The initial state is 'Manual Switch W=stb P=act' with 'normal' r/b values.](6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg) + +The diagram illustrates the state transitions for the MS(r/b=normal) state in 1:1 bidirectional protection switching. It starts with a 'Manual Switch' state where W=stb and P=act, with both r and b set to 'normal'. Transitions are triggered by events like SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, and CLEAR. The diagram includes a legend indicating that some transitions are 'Only for revertive mode' (shaded with vertical lines) and others are 'Only for Non-revertive mode' (shaded with cross-hatch). States are represented by rectangles, sub-states by parallelograms, and terminal states by circles. Transitions between states are labeled with the triggering event. Transitions to sub-states include 'Switch to working' or 'Switch to protection' actions. A decision diamond 'Local MS acked w/ NR?' determines the next state based on whether a local MS acknowledgment was received with a Null Response. + +State transition diagram for MS(r/b=normal) state for 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR) and sub-states (E, F, C, D, P, Q, G, A, J). It includes a legend for 'Only for revertive mode' and 'Only for Non-revertive mode'. The initial state is 'Manual Switch W=stb P=act' with 'normal' r/b values. + +Figure IV.7 – MS(r/b=normal) state for 1:1 bidirectional protection switching + +![State transition diagram for MS(r/b=null) state for 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR) and sub-states (E, F, C, D, P, Q, H, A, B). It includes a legend for 'Only for Non-revertive mode'. The initial state is 'Manual Switch W=act P=stb' with 'null' r/b values.](b35ea3e304aad7d350a9902270413930_img.jpg) + +The diagram illustrates the state transitions for the MS(r/b=null) state in 1:1 bidirectional protection switching. It starts with a 'Manual Switch' state where W=act and P=stb, with both r and b set to 'null'. Transitions are triggered by events like SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, and CLEAR. The diagram includes a legend indicating that some transitions are 'Only for Non-revertive mode' (shaded with cross-hatch). States are represented by rectangles, sub-states by parallelograms, and terminal states by circles. Transitions between states are labeled with the triggering event. Transitions to sub-states include 'Switch to protection' or 'Switch to working' actions. A decision diamond 'Local MS acked w/ NR?' determines the next state based on whether a local MS acknowledgment was received with a Null Response. + +State transition diagram for MS(r/b=null) state for 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR) and sub-states (E, F, C, D, P, Q, H, A, B). It includes a legend for 'Only for Non-revertive mode'. The initial state is 'Manual Switch W=act P=stb' with 'null' r/b values. + +Figure IV.8 – MS(r/b=null) state for 1:1 bidirectional protection switching + +![State transition diagram for WTR(r/b=normal) state for 1:1 bidirectional protection switching. The diagram shows transitions between various states based on events like SF, LO, FS, SD, MS, EXER, CLEAR, and WTR timer expires. It includes a 'Wait To Restore' state with W=stb and P=act. A box indicates this mode is 'Only for revertive mode'.](99698c448635861b7dc8d352f87a1b2b_img.jpg) + +The diagram illustrates the state transitions for the WTR(r/b=normal) state in 1:1 bidirectional protection switching. It starts with a 'Wait To Restore' (WTR) state where W=stb and P=act, with both normal and normal sub-states. Transitions are triggered by events such as SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR, and WTR timer expires. 'Switch to working' actions lead to intermediate states like SF, SF-P, LO, FS, SD, SD r/b=null, MS, MS r/b=null, EXER, and NR r/b=null. These lead to final states labeled A through Q, with some states like A, B, and I being revisited through other paths. A note indicates this mode is 'Only for revertive mode'. + +State transition diagram for WTR(r/b=normal) state for 1:1 bidirectional protection switching. The diagram shows transitions between various states based on events like SF, LO, FS, SD, MS, EXER, CLEAR, and WTR timer expires. It includes a 'Wait To Restore' state with W=stb and P=act. A box indicates this mode is 'Only for revertive mode'. + +Figure IV.9 – WTR(r/b=normal) state for 1:1 bidirectional protection switching + +![State transition diagram for DNR(r/b=normal) state for 1:1 bidirectional protection switching. The diagram shows transitions between various states based on events like SF, LO, FS, SD, MS, EXER, and DNR. It includes a 'Do Not Revert' state with W=stb and P=act. A box indicates this mode is 'Only for Non-revertive mode'.](c3254408eadbf152632a8faf16310722_img.jpg) + +The diagram illustrates the state transitions for the DNR(r/b=normal) state in 1:1 bidirectional protection switching. It starts with a 'Do Not Revert' (DNR) state where W=stb and P=act, with both normal and normal sub-states. Transitions are triggered by events such as SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, and DNR. 'Switch to working' actions lead to intermediate states like SF, SF-P, LO, FS, SD, SD r/b=null, MS, MS r/b=null, EXER r/b=normal, and NR r/b=null. These lead to final states labeled A through L, with some states like A, B, and J being revisited through other paths. A note indicates this mode is 'Only for Non-revertive mode'. + +State transition diagram for DNR(r/b=normal) state for 1:1 bidirectional protection switching. The diagram shows transitions between various states based on events like SF, LO, FS, SD, MS, EXER, and DNR. It includes a 'Do Not Revert' state with W=stb and P=act. A box indicates this mode is 'Only for Non-revertive mode'. + +Figure IV.10 – DNR(r/b=normal) state for 1:1 bidirectional protection switching + +![State transition diagram for EXER(r/b=null) state for 1:1 bidirectional protection switching. The diagram shows transitions from an initial EXER state (W=act, P=stb) based on various input signals. Inputs like SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, and CLEAR lead to specific actions (like 'Switch to protection') and final states labeled A through K. A second row of inputs including LO, SF-P, FS, SF, SD, SD r/b=null, MS, MS r/b=null, WTR, EXER r/b=null, RR r/b=null, NR r/b=null, and DNR r/b=normal also lead to states A, B, or K. Legend boxes indicate that vertical striped boxes are 'Only for revertive mode' and cross-hatched boxes are 'Only for Non-revertive mode'.](a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg) + +The diagram illustrates the state transitions for the EXER(r/b=null) state in 1:1 bidirectional protection switching. The initial state is EXER, characterized by W=act and P=stb. The diagram is divided into two main horizontal sections. The top section shows transitions from EXER to various states: SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, and CLEAR. SF, FS, SD, and MS lead to 'Switch to protection' states, which then lead to SF, FS, SD, and MS respectively. These lead to final states E, D, P, and G. LO leads to C, SF-P leads to F, SD-P leads to Q, MS-W leads to H, EXER leads to K, and CLEAR leads to NR r/b=null, which leads to A. The bottom section shows transitions from EXER to LO, SF-P, FS, SF, SD, SD r/b=null, MS, MS r/b=null, WTR, EXER r/b=null, RR r/b=null, NR r/b=null, and DNR r/b=normal. LO leads to NR r/b=null, which leads to A. SF-P, FS, and SF lead to 'Switch to protection' states, which then lead to NR r/b=normal, which leads to B. SD leads to NR r/b=null, which leads to A. SD r/b=null leads to 'Switch to protection' states, which then lead to NR r/b=null, which leads to A. MS leads to NR r/b=normal, which leads to B. MS r/b=null leads to NR r/b=null, which leads to A. WTR leads to NR r/b=normal, which leads to B (shaded). EXER r/b=null leads to K. RR r/b=null, NR r/b=null, and DNR r/b=normal lead back to the top section. A legend indicates that states with vertical stripes (SD-P, MS r/b=null, WTR, EXER r/b=null) are 'Only for revertive mode', and states with cross-hatching (MS, MS-W, NR r/b=null, DNR r/b=normal) are 'Only for Non-revertive mode'. + +State transition diagram for EXER(r/b=null) state for 1:1 bidirectional protection switching. The diagram shows transitions from an initial EXER state (W=act, P=stb) based on various input signals. Inputs like SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, and CLEAR lead to specific actions (like 'Switch to protection') and final states labeled A through K. A second row of inputs including LO, SF-P, FS, SF, SD, SD r/b=null, MS, MS r/b=null, WTR, EXER r/b=null, RR r/b=null, NR r/b=null, and DNR r/b=normal also lead to states A, B, or K. Legend boxes indicate that vertical striped boxes are 'Only for revertive mode' and cross-hatched boxes are 'Only for Non-revertive mode'. + +**Figure IV.11 – EXER(r/b=null) state for 1:1 bidirectional protection switching** + +![State transition diagram for EXER(r/b=normal) state for 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, CLEAR, DNR, NR, RR) and events (E, F, C, D, P, Q, G, H, L, J, A, B). A box indicates 'Only for Non-revertive mode'.](b20942bb14022381a243971ab9790dd9_img.jpg) + +The diagram illustrates the state transitions for the EXER(r/b=normal) state in 1:1 bidirectional protection switching. It starts with an initial state 'EXER' (Exercise, W=stb, P=act) which is 'normal' on both sides (L and R). A box indicates this is 'Only for Non-revertive mode'. + +Transitions from the initial state lead to various intermediate states and events: + +- SF → SF → E +- SF-P → Switch to working → SF-P → F +- LO → Switch to working → LO → C +- FS → FS → D +- SD → SD → P +- SD-P → Switch to working → SD (r/b=null) → Q +- MS → MS → G +- MS-W → Switch to working → MS (r/b=null) → H +- EXER → EXER → L +- CLEAR → DNR (r/b=normal) → J + +From these intermediate states, further transitions occur: + +- From SF, LO, FS, SD, MS, and EXER, transitions lead to a second row of states: LO, SF-P, FS, SF, SD, SD (r/b=null), MS, MS (r/b=null), WTR, EXER (r/b=normal), RR (r/b=normal), NR (r/b=normal), and DNR (r/b=normal). +- From LO, SF-P, and FS, a 'Switch to working' transition leads to NR (r/b=null) → A. +- From SD and MS, a 'Switch to working' transition leads to NR (r/b=null) → A. +- From SD (r/b=null) and MS (r/b=null), a 'Switch to working' transition leads to NR (r/b=normal) → B. +- From WTR, a transition leads to NR (r/b=normal) → B. +- From EXER (r/b=normal), a transition leads to L. +- From RR (r/b=normal), NR (r/b=normal), and DNR (r/b=normal), transitions lead to L. + +State transition diagram for EXER(r/b=normal) state for 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, CLEAR, DNR, NR, RR) and events (E, F, C, D, P, Q, G, H, L, J, A, B). A box indicates 'Only for Non-revertive mode'. + +Figure IV.12 – EXER(r/b=normal) state for 1:1 bidirectional protection switching + +![State transition diagram for RR(r/b=null) state in 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, NR, DNR) based on specific conditions, leading to end states A, B, C, D, E, F, G, H, K, M, and P. A legend indicates states and transitions specific to revertive and non-revertive modes.](29043c6ca27a7cfbc757a5d2eb029d33_img.jpg) + +The diagram illustrates the state transitions for the **RR(r/b=null)** state in 1:1 bidirectional protection switching. It starts from the **RR** state (Reverse Request, W=act, P=stb) and branches into various intermediate states based on specific conditions. + +**Legend:** + +- Only for revertive mode:** States and transitions with vertical stripes. +- Only for Non-revertive mode:** States and transitions with cross-hatching. + +**States and Transitions:** + +- RR (Reverse Request, W=act, P=stb)** (M=null, RR=null) leads to: + - SF** (Switch to protection) → **SF** → **E** + - SF-P** → **SF-P** → **F** + - LO** → **LO** → **C** + - FS** (Switch to protection) → **FS** → **D** + - SD** (Switch to protection) → **SD** → **P** + - SD-P** → **SD r/b=null** → **Q** + - MS** (Switch to protection) → **MS** → **G** + - MS-W** → **MS r/b=null** → **H** + - EXER** → **EXER r/b=null** → **K** +- Intermediate States:** + - LO** → **NR r/b=null** → **A** + - SF-P** → **NR r/b=normal** → **B** + - FS** → **NR r/b=null** → **A** + - SF** → **NR r/b=normal** → **B** + - SD** → **NR r/b=null** → **A** + - SD r/b=null** → **NR r/b=null** → **A** + - MS** → **NR r/b=normal** → **B** + - MS r/b=null** → **NR r/b=null** → **A** + - WTR** (Switch to protection) → **NR r/b=normal** → **B** + - EXER r/b=null** → **M** + - RR r/b=null** → **NR r/b=null** → **A** + - NR r/b=null** → **M** + - DNR r/b=normal** → **M** + +State transition diagram for RR(r/b=null) state in 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, NR, DNR) based on specific conditions, leading to end states A, B, C, D, E, F, G, H, K, M, and P. A legend indicates states and transitions specific to revertive and non-revertive modes. + +**Figure IV.13 – RR(r/b=null) state for 1:1 bidirectional protection switching** + +![State transition diagram for 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, NR, DNR) and events (E, F, C, D, P, Q, G, H, L, A, B, N, J). A 'Reverse Request' (RR) state is shown at the top with 'W=stb' and 'P=act' parameters. A note indicates this is 'Only for Non-revertive mode'. Transitions include 'Switch to working' and 'Switch to protecting' actions.](8c3eb53c927f55acd19723cfcd0c43b6_img.jpg) + +The diagram illustrates the state transitions for 1:1 bidirectional protection switching. At the top, a 'Reverse Request' (RR) state is shown with parameters 'W=stb' and 'P=act', and a note 'Only for Non-revertive mode'. The main part of the diagram shows transitions between various states and events. + +**States and Events:** + +- RR (Reverse Request):** Initial state with 'W=stb' and 'P=act' parameters. Transitions to SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, and EXER. +- SF (Signal Fail):** State reached from RR. Transitions to SF-P (Switch to working) and then to event E. +- SF-P (Signal Fail - Protect):** State reached from SF via 'Switch to working'. Transitions to event F. +- LO (Loss of Signal):** State reached from RR. Transitions to LO (Switch to working) and then to event C. +- FS (Frame Synchronization):** State reached from RR. Transitions to event D. +- SD (Signal Degrade):** State reached from RR. Transitions to event P. +- SD-P (Signal Degrade - Protect):** State reached from SD via 'Switch to working'. Transitions to event Q. +- MS (Multiplex Section):** State reached from RR. Transitions to event G. +- MS-W (Multiplex Section - Working):** State reached from MS via 'Switch to working'. Transitions to event H. +- EXER (Exercise):** State reached from RR. Transitions to event L. +- LO (Loss of Signal):** State reached from event L. Transitions to 'Switch to working' and then to NR (r/b=null) state, which leads to event A. +- SF-P (Signal Fail - Protect):** State reached from event L. Transitions to event B. +- FS (Frame Synchronization):** State reached from event L. Transitions to event B. +- SF (Signal Fail):** State reached from event L. Transitions to event B. +- SD (Signal Degrade):** State reached from event L. Transitions to event B. +- SD (Signal Degrade):** State reached from event L. Transitions to 'Switch to working' and then to NR (r/b=null) state, which leads to event A. +- MS (Multiplex Section):** State reached from event L. Transitions to event B. +- MS (Multiplex Section):** State reached from event L. Transitions to 'Switch to working' and then to NR (r/b=null) state, which leads to event A. +- WTR (Wait To Restore):** State reached from event L. Transitions to event N. +- EXER (Exercise):** State reached from event L. Transitions to event N. +- RR (Reverse Request):** State reached from event L. Transitions to event J. +- DNR (Data Not Received):** State reached from event L. Transitions to event J. + +State transition diagram for 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, NR, DNR) and events (E, F, C, D, P, Q, G, H, L, A, B, N, J). A 'Reverse Request' (RR) state is shown at the top with 'W=stb' and 'P=act' parameters. A note indicates this is 'Only for Non-revertive mode'. Transitions include 'Switch to working' and 'Switch to protecting' actions. + +Figure IV.14 – RR(r/b=normal) state for 1:1 bidirectional protection switching + +![State transition diagram for 1:1 bidirectional protection switching starting from Signal Degrade (SD) state.](e2dad48ec062e71202459a9ab82261e4_img.jpg) + +The diagram illustrates the state transitions for 1:1 bidirectional protection switching, starting from the **Signal Degrade (W)** state where $W=stb$ and $P=act$ . Both the **P** (Protection) and **SD** (Signal Degrade) components are in the **normal** state. + +**Legend:** + +- Only for revertive mode +- Only for Non-revertive mode + +**Transitions from SD (normal):** + +- SF** → **SF** → **E** +- SF-P** → **Switch to working** → **SF-P** → **F** +- LO** → **Switch to working** → **LO** → **C** +- FS** → **FS** → **D** +- Working recovers from SD** → **No Local SD-P?** + - If **No**: Proceed to **Revertive Mode?** + - If **Yes**: **SD r/b=null** → **Q** +- SD-P** → **SD-P** → **MS** → **P** +- Protection recovers from SD** → **MS** → **P** +- MS** → **P** +- MS-W** → **MS-W** → **EXER** → **SD-P** +- EXER** → **SD-P** + +**Transitions from Revertive Mode?** + +- If **Yes**: **WTR** → **I** +- If **No**: **DNR** → **J** + +**Transitions from I and J:** + +- I** → **LO** → **Switch to working** → **NR r/b=null** → **A** +- I** → **SF-P** → **NR r/b=normal** → **B** +- I** → **FS** → **FS** → **P** +- I** → **SF** → **SF** → **P** +- I** → **SD** → **SD** → **P** +- I** → **SD r/b=null** → **SD r/b=null** → **EXER r/b=null** → **SD** +- I** → **MS** → **MS** → **P** +- I** → **MS r/b=null** → **MS r/b=null** → **MS-W** → **EXER** → **SD-P** +- I** → **WTR** → **WTR** → **I** +- J** → **SD** → **SD** → **P** +- J** → **SD r/b=null** → **SD r/b=null** → **EXER r/b=null** → **SD** +- J** → **MS** → **MS** → **P** +- J** → **MS r/b=null** → **MS r/b=null** → **MS-W** → **EXER** → **SD-P** +- J** → **WTR** → **WTR** → **I** + +**Additional Transitions:** + +- EXER r/b=null** → **SD** +- EXER r/b=normal** → **SD** +- RR r/b=null** → **SD** +- RR r/b=normal** → **SD** +- NR r/b=null** → **SD** +- NR r/b=normal** → **SD** +- DNR r/b=normal** → **SD** + +State transition diagram for 1:1 bidirectional protection switching starting from Signal Degrade (SD) state. + +Figure IV.15 – SD(r/b=normal) state for 1:1 bidirectional protection switching + +![State transition diagram for 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, MS, MS-W, EXER) and events (Signal Degrade, Switch to protection, Switch to working). It includes a decision diamond 'Local SD?' and a note 'Only for Non-revertive mode'. States are represented by rectangles, events by parallelograms, and terminal states by circles. Some states are shaded to indicate they are only for non-revertive mode.](3bf1696c3034743b5ab07a0b5e398347_img.jpg) + +The diagram illustrates the state transitions for 1:1 bidirectional protection switching. It begins with an initial state 'Q' (Signal Degrade (P), W=act P=stb) leading to a row of states: SF, SF-P, LO, FS, SD, Working recovers from SD, Protection recovers from SD, MS, MS-W, and EXER. A decision diamond 'Local SD?' is positioned between Protection recovers from SD and MS. A note 'Only for Non-revertive mode' is placed above the Protection recovers from SD state. Transitions lead to various terminal states (E, F, C, D, Q, A, P, Q) and intermediate states (LO, SF-P, FS, SF, SD, SD r/b=null, MS, MS r/b=null, WTR). Further transitions lead to terminal states (A, B, Q) and a row of states: EXER r/b=null, EXER r/b=normal, RR r/b=null, RR r/b=normal, NR r/b=null, NR r/b=normal, and DNR r/b=normal. A 'Switch to protection' event is shown between SF and LO. A 'Switch to working' event is shown between LO and NR r/b=null. + +State transition diagram for 1:1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, MS, MS-W, EXER) and events (Signal Degrade, Switch to protection, Switch to working). It includes a decision diamond 'Local SD?' and a note 'Only for Non-revertive mode'. States are represented by rectangles, events by parallelograms, and terminal states by circles. Some states are shaded to indicate they are only for non-revertive mode. + +Figure IV.16 – SD(r/b=null) state for 1:1 bidirectional protection switching + +### IV.2.2 1+1 bidirectional protection switching + +The following diagrams define state transitions of 1+1 bidirectional protection switching both in revertive and non-revertive modes. + +![State transition diagram for NR(r=null, b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER) and actions (Switch to protection, DNR, RR). It includes a legend for revertive and non-revertive modes and a decision logic for Local SF-P? and Local SD-P?.](32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg) + +**Legend:** + +- Only for revertive mode +- Only for Non-revertive mode + +**NR State Definition:** + +| | | +|---------------------------|--------| +| A | NR | +| No Request
W=act P=stb | | +| null | normal | + +**State Transitions:** + +- SF** → **Switch to protection** → **SF** → **E** +- SF-P** → **SF-P** → **F** +- LO** → **LO** → **C** +- FS** → **Switch to protection** → **FS** → **D** +- SD** → **Switch to protection** → **SD** → **P** +- SD-P** → **SD (r=null, b=normal)** → **Q** +- MS** → **Switch to protection** → **MS** → **G** +- MS-W** → **MS (r=null, b=normal)** → **H** +- EXER** → **EXER (r=null, b=normal)** → **K** + +**Intermediate State Transitions:** + +- LO** → **LO** → **A** +- SF-P** → **SF-P** → **Switch to protection** → **NR (r/b=normal)** → **B** +- FS** → **FS** → **Switch to protection** → **NR (r/b=normal)** → **A** +- SD** → **SD** → **SD (r=null, b=normal)** → **A** +- MS** → **MS** → **Switch to protection** → **NR (r/b=normal)** → **B** +- MS (r=null, b=normal)** → **MS (r=null, b=normal)** → **A** +- WTR** → **Switch to protection** → **NR (r/b=normal)** → **B** + +**Final State Transitions:** + +- DNR** → **Revertive Mode?** + - Yes** → **Switch to protection** → **NR (r/b=normal)** → **B** + - No** → **Switch to protection** → **DNR (r/b=normal)** → **J** +- EXER (r=null, b=normal)** → **RR (r=null, b=normal)** → **M** +- RR (r=null, b=normal)** → **RR (r=null, b=normal)** → **A** +- NR (r/b=normal)** → **Local SF-P?** + - No** → **Local SD-P?** + - No** → **SD-P** → **A** + - Yes** → **SD** → **A** + - Yes** → **SF** → **SF** → **A** +- NR (r=null, b=normal)** → **Local SF-P?** + - No** → **Local SD-P?** + - No** → **SD-P** → **A** + - Yes** → **SD** → **A** + - Yes** → **SF-P** → **SF-P** → **A** + +State transition diagram for NR(r=null, b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER) and actions (Switch to protection, DNR, RR). It includes a legend for revertive and non-revertive modes and a decision logic for Local SF-P? and Local SD-P?. + +Figure IV.17 – NR(r=null, b=normal) state for 1+1 bidirectional protection switching + +![State transition diagram for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, etc.) based on specific conditions like 'Revertive Mode?' or 'Local SD?'. It includes a legend for revertive and non-revertive modes and a top box defining the initial 'NR' state.](c6212a3b14736d6a8c81ace75ae94ccf_img.jpg) + +The diagram illustrates the state transitions for 1+1 bidirectional protection switching. At the top, a box defines the initial state: **NR** (No Request, W=stb, P=act), with two 'normal' sub-states. A legend indicates that boxes with vertical stripes are 'Only for revertive mode' and boxes with cross-hatching are 'Only for Non-revertive mode'. + +The main flow starts from the 'NR' state and branches into various states based on input conditions: SF, Working recovers from SF, SF-P, LO, FS, SD, Working recovers from SD, SD-P, MS, MS-W, and EXER. Each of these states has a corresponding transition to a lower-level state (e.g., SF to SF, LO to LO) and a terminal state (e.g., E, B, F, C, D, P, B, Q, G, H, B). + +From the lower-level states, transitions lead to a central decision area. This area includes states like LO, SF-P, FS, SF, SD, SD (r=null, b=normal), MS, MS (r=null, b=normal), and WTR. These lead to decision diamonds: 'Revertive Mode?', 'Previous local state?', and 'Local SD?'. The 'Revertive Mode?' and 'Local SD?' decisions lead to 'Switch to working' or 'DNR' (Only for Non-revertive mode) states. The 'Previous local state?' decision leads to 'Switch to working' or 'SF (or SD) (W) if applicable' states. The final terminal states are A, I, J (Only for Non-revertive mode), B, and A. + +State transition diagram for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, etc.) based on specific conditions like 'Revertive Mode?' or 'Local SD?'. It includes a legend for revertive and non-revertive modes and a top box defining the initial 'NR' state. + +Figure IV.18 – NR(r/b=normal) state for 1+1 bidirectional protection switching + +![State transition diagram for LO(r=null, b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states including SF, SD, MS, and CLEAR, with decision points for local SF-P and SD-P. A legend indicates 'Only for Non-revertive mode'.](f78d2e126f00fcc5d8d9797ca410cc09_img.jpg) + +The diagram illustrates the state transitions for the LO(r=null, b=normal) state. It starts with a state 'C' containing 'Lockout W=act P=stb' with 'null' and 'normal' sub-states. A legend indicates 'Only for Non-revertive mode'. Transitions include: + +- Top row of input events: SF, Working recovers from SF, SF-P, Protection recovers from SF, LO, FS. +- Middle row of input events: SD, Working recovers from SD, SD-P, Protection recovers from SD, MS, MS-W, EXER, CLEAR. +- A central row of states: LO, SF-P, FS, SF, SD, SD (r=null, b=normal), MS, MS (r=null, b=normal), WTR. +- Decision logic on the right: 'Local SF-P?' (Yes/No) and 'Local SD-P?' (Yes/No). 'No' paths lead to 'NR r=null b=normal' (A), 'SD r=null b=normal' (Q), and 'SF-P' (F). 'Yes' paths lead to 'Switch to protection' states resulting in 'SF' (E) and 'SD' (P). +- Bottom row of states: EXER (r=null, b=normal), EXER (r/b=normal), RR (r=null, b=normal), RR (r/b=normal), NR (r=null, b=normal), NR (r/b=normal), DNR (r/b=normal). + +State transition diagram for LO(r=null, b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states including SF, SD, MS, and CLEAR, with decision points for local SF-P and SD-P. A legend indicates 'Only for Non-revertive mode'. + +Figure IV.19 – LO(r=null, b=normal) state for 1+1 bidirectional protection switching + +![State transition diagram for FS(r/b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states including SF, SD, MS, and CLEAR, with decision points for local SF, SD-P, and Revertive Mode. Legends indicate 'Only for revertive mode' and 'Only for Non-revertive mode'.](cd3e29b6d40dce0580fa43b721157489_img.jpg) + +The diagram illustrates the state transitions for the FS(r/b=normal) state. It starts with a state 'D' containing 'Forced Switch W=stb P=act' with 'normal' and 'normal' sub-states. Legends indicate 'Only for revertive mode' and 'Only for Non-revertive mode'. Transitions include: + +- Top row of input events: SF, Working recovers from SF, SF-P, LO, FS, SD, Working recovers from SD, SD-P, Protection recovers from SD, CLEAR. +- Intermediate logic: 'Switch to working' leading to SF-P (F) and LO (C). +- A central row of states: LO, SF-P, FS, SF, SD, SD (r=null, b=normal), MS, MS (r=null, b=normal), WTR. +- Decision logic on the right: 'Local SF?' (Yes/No), 'Local SD-P?' (Yes/No), and 'Revertive Mode?' (Yes/No). +- Terminal states from logic: SD (P), NR (r=null, b=normal) (A), DNR (r/b=normal) (J), SD (r=null, b=normal) (Q), SF (E). +- Bottom row of states: Switch to working (leading to NR r=null b=normal (A)), EXER (r=null, b=normal), EXER (r/b=normal), RR (r=null, b=normal), RR (r/b=normal), NR (r=null, b=normal), NR (r/b=normal), DNR (r/b=normal). + +State transition diagram for FS(r/b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states including SF, SD, MS, and CLEAR, with decision points for local SF, SD-P, and Revertive Mode. Legends indicate 'Only for revertive mode' and 'Only for Non-revertive mode'. + +Figure IV.20 – FS(r/b=normal) state for 1+1 bidirectional protection switching + +![State transition diagram for 1+1 bidirectional protection switching starting from Signal Fail (W) state. The diagram shows transitions between various states like SD, LO, FS, SF-P, MS, EXER, and NR based on revertive mode and signal conditions.](e404de9a69c05473fbd6af28ee32311b_img.jpg) + +The diagram illustrates the state transitions for 1+1 bidirectional protection switching, starting from the **Signal Fail (W)** state. + +**Initial State:** **Signal Fail (W)** (W=stb, P=act). Both the **E** and **SF** components are in the **normal** state. + +**Legend:** + +- Only for revertive mode:** Indicated by vertical stripes. +- Only for Non-revertive mode:** Indicated by cross-hatching. + +**Transitions from Signal Fail (W):** + +- Working recovers from SF:** Leads to a decision diamond **SD Local SD-P?**. + - If **Yes**: Leads to **Revertive Mode?**. + - If **Yes**: Leads to **SD** (state **P**) and **WTR** (state **I**). + - If **No**: Leads to **Switch to working**, then to **SD r=null b=normal** (state **Q**). + - If **No**: Leads to **DNR** (state **J**). +- SF-P:** Leads to **Switch to working**, then to **SF-P** (state **F**). +- LO:** Leads to **Switch to working**, then to **LO** (state **C**). +- FS:** Leads to **FS** (state **D**). +- SD:** Leads to **SD** (state **E**). +- Working recovers from SD:** Leads to **MS** (state **E**). +- SD-P:** Leads to **MS-W** (state **E**). +- Protection recovers from SD:** Leads to **EXER** (state **E**). + +**Transitions from the middle section (states P, I, J, Q, F, C, D, E):** + +- LO:** Leads to **Switch to working**, then to **NR r=null b=normal** (state **A**). +- SF-P:** Leads to **NR r=null b=normal** (state **B**). +- FS:** Leads to **SF** (state **E**). +- SF:** Leads to **SD** (state **E**). +- SD r=null b=normal:** Leads to **MS** (state **E**). +- MS r=null b=normal:** Leads to **WTR** (state **E**). +- WTR:** Leads to **EXER r=null b=normal** (state **E**). + +**Transitions from the bottom section (states A, B, E):** + +- EXER r=null b=normal:** Leads to **RR r=null b=normal** (state **E**). +- RR r=null b=normal:** Leads to **NR r=null b=normal** (state **E**). +- NR r=null b=normal:** Leads to **DNR r=null b=normal** (state **E**). + +State transition diagram for 1+1 bidirectional protection switching starting from Signal Fail (W) state. The diagram shows transitions between various states like SD, LO, FS, SF-P, MS, EXER, and NR based on revertive mode and signal conditions. + +Figure IV.21 – SF(r/b=normal) state for 1+1 bidirectional protection switching + +![State transition diagram for SF-P(r=null, b=normal) state for 1+1 bidirectional protection switching. The diagram shows various states (SF, LO, FS, SD, MS, EXER, etc.) and transitions between them based on signal fail (P), working (W=act), and protection (P=stb) conditions. A note indicates 'Only for Non-revertive mode'.](24ba47df8be44ae91945d88ce2232df5_img.jpg) + +The diagram illustrates the state transitions for the SF-P(r=null, b=normal) state in 1+1 bidirectional protection switching. It is divided into three horizontal layers of states and transitions. + +- Top Layer:** + - Starts with a state **SF-P** (Signal Fail (P), W=act, P=stb) with sub-states **null** and **normal**. + - Transitions from **SF-P** to **SF**, **Working recovers from SF**, **Protection recovers from SF**, **LO**, **FS**, **SD**, **Working recovers from SD**, **SD-P**, and **Protection recovers from SD**. + - A decision diamond **Local SF?** (SF) leads to **Switch to protection** (if Yes) or another decision diamond **Local SD-P?** (SD-P) (if No). + - Switch to protection** leads to **SF** and **SD**. + - Local SD-P?** leads to **NR** (r=null, b=normal) and **SD** (r=null, b=normal) (if Yes) or **SD-P** (if No). + - LO** leads to another **LO** state. + - FS** leads to **SD**. + - SD** leads to **MS**, **MS-W**, and **EXER**. + - Working recovers from SD** leads to **SD-P**. + - SD-P** leads to **Protection recovers from SD**. + - Protection recovers from SD** leads to **FS**. + - States **SF**, **Working recovers from SF**, **Protection recovers from SF**, **LO**, **FS**, **SD**, **Working recovers from SD**, **SD-P**, and **Protection recovers from SD** all lead to a common horizontal bus. +- Middle Layer:** + - A horizontal bus connects states **LO**, **SF-P**, **FS**, **SF**, **SD**, **SD** (r=null, b=normal), **MS**, **MS** (r=null, b=normal), and **WTR**. + - Transitions from this bus lead to **NR** (r=null, b=normal), **EXER** (r=null, b=normal), **EXER** (r/b=normal), **RR** (r=null, b=normal), **RR** (r/b=normal), **NR** (r=null, b=normal), **NR** (r/b=normal), and **DNR** (r/b=normal). +- Bottom Layer:** + - States **NR** (r=null, b=normal), **EXER** (r=null, b=normal), **EXER** (r/b=normal), **RR** (r=null, b=normal), **RR** (r/b=normal), **NR** (r=null, b=normal), **NR** (r/b=normal), and **DNR** (r/b=normal) all lead to a common horizontal bus. + - Transitions from this bus lead to states **A** and **F**. + +A note in the top right corner states: "Only for Non-revertive mode". + +State transition diagram for SF-P(r=null, b=normal) state for 1+1 bidirectional protection switching. The diagram shows various states (SF, LO, FS, SD, MS, EXER, etc.) and transitions between them based on signal fail (P), working (W=act), and protection (P=stb) conditions. A note indicates 'Only for Non-revertive mode'. + +Figure IV.22 – SF-P(r=null, b=normal) state for 1+1 bidirectional protection switching + +![State transition diagram for MS(r/b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR) based on Manual Switch (W=stb, P=act) and other conditions like 'Switch to working', 'Revertive Mode?', and 'Local MS acked w/ NR?'. It includes a legend for revertive and non-revertive modes.](0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg) + +The diagram illustrates the state transitions for the MS(r/b=normal) state in 1+1 bidirectional protection switching. At the top, a Manual Switch (W=stb, P=act) is shown with 'normal' states for both W and P. A legend indicates that boxes with a cross-hatch pattern are 'Only for revertive mode', while others are 'Only for Non-revertive mode'. The main flow starts from the Manual Switch, leading to a series of states: SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, and CLEAR. Transitions between these states are triggered by 'Switch to working' or 'Revertive Mode?' (Yes/No). The diagram also shows transitions to intermediate states like LO, SF-P, FS, SF, SD, SD (r=null, b=normal), MS, and WTR. A decision point 'Local MS acked w/ NR?' leads to either 'Switch to working' or a series of states: EXER (r=null, b=normal), EXER (r/b=normal), RR (r=null, b=normal), RR (r/b=normal), NR (r=null, b=normal), NR (r/b=normal), and DNR (r/b=normal). The diagram ends with various terminal states labeled A, B, C, D, E, F, G, H, I, and J. + +State transition diagram for MS(r/b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR) based on Manual Switch (W=stb, P=act) and other conditions like 'Switch to working', 'Revertive Mode?', and 'Local MS acked w/ NR?'. It includes a legend for revertive and non-revertive modes. + +Figure IV.23 – MS(r/b=normal) state for 1+1 bidirectional protection switching + +![State transition diagram for MS(r=null, b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR) based on Manual Switch (W=act, P=stb) and other conditions like 'Switch to protection', 'Switch to working', and 'Local MS acked w/ NR?'. It includes a legend for non-revertive mode.](b1784a5cbeeb3d9fb9e60b333019c721_img.jpg) + +The diagram illustrates the state transitions for the MS(r=null, b=normal) state in 1+1 bidirectional protection switching. At the top, a Manual Switch (W=act, P=stb) is shown with 'null' for W and 'normal' for P. A legend indicates that boxes with a cross-hatch pattern are 'Only for Non-revertive mode'. The main flow starts from the Manual Switch, leading to a series of states: SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, and CLEAR. Transitions between these states are triggered by 'Switch to protection' or 'Switch to working'. The diagram also shows transitions to intermediate states like LO, SF-P, FS, SF, SD, SD (r=null, b=normal), MS, MS (r=null, b=normal), and WTR. A decision point 'Local MS acked w/ NR?' leads to either 'Switch to protection' or a series of states: EXER (r=null, b=normal), EXER (r/b=normal), RR (r=null, b=normal), RR (r/b=normal), NR (r=null, b=normal), NR (r/b=normal), and DNR (r/b=normal). The diagram ends with various terminal states labeled A, B, C, D, E, F, G, H, I, and J. + +State transition diagram for MS(r=null, b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR) based on Manual Switch (W=act, P=stb) and other conditions like 'Switch to protection', 'Switch to working', and 'Local MS acked w/ NR?'. It includes a legend for non-revertive mode. + +Figure IV.24 – MS(r=null, b=normal) state for 1+1 bidirectional protection switching + +![State transition diagram for WTR(r/b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states based on events like SF, LO, FS, SD, MS, EXER, CLEAR, and WTR timer expires. It includes a 'Wait To Restore' (WTR) state with parameters W=stb and P=act. Transitions lead to working and protection paths, eventually reaching states labeled A through I.](5e05915b2a93a3b404422e0966a7c924_img.jpg) + +The diagram illustrates the state transitions for the WTR(r/b=normal) state in 1+1 bidirectional protection switching. It starts with a 'Wait To Restore' (WTR) state where W=stb and P=act. Transitions are triggered by events such as SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR, and WTR timer expires. The diagram is divided into two main paths: working and protection. Transitions between states are labeled with 'Switch to working' or 'Switch to protection'. The final states are labeled A through I, with some states having additional parameters like r=null and b=normal. + +State transition diagram for WTR(r/b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states based on events like SF, LO, FS, SD, MS, EXER, CLEAR, and WTR timer expires. It includes a 'Wait To Restore' (WTR) state with parameters W=stb and P=act. Transitions lead to working and protection paths, eventually reaching states labeled A through I. + +Figure IV.25 – WTR(r/b=normal) state for 1+1 bidirectional protection switching + +![State transition diagram for DNR(r/b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states based on events like SF, LO, FS, SD, MS, EXER, and DNR. It includes a 'Do Not Revert' (DNR) state with parameters W=stb and P=act. Transitions lead to working and protection paths, eventually reaching states labeled A through J.](d510bddda14c44163bbeee33b491a105_img.jpg) + +The diagram illustrates the state transitions for the DNR(r/b=normal) state in 1+1 bidirectional protection switching. It starts with a 'Do Not Revert' (DNR) state where W=stb and P=act. Transitions are triggered by events such as SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, and DNR. The diagram is divided into two main paths: working and protection. Transitions between states are labeled with 'Switch to working' or 'Switch to protection'. The final states are labeled A through J, with some states having additional parameters like r=null and b=normal. + +State transition diagram for DNR(r/b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states based on events like SF, LO, FS, SD, MS, EXER, and DNR. It includes a 'Do Not Revert' (DNR) state with parameters W=stb and P=act. Transitions lead to working and protection paths, eventually reaching states labeled A through J. + +Figure IV.26 – DNR(r/b=normal) state for 1+1 bidirectional protection switching + +![State transition diagram for EXER(r=null, b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR) and their corresponding protection states (Switch to protection, NR, SD, MS). It includes a legend for revertive and non-revertive modes and an initial state table for K and EXER.](caeb1637753f79f4cd005eda3768d1d5_img.jpg) + +The diagram illustrates the state transitions for the EXER(r=null, b=normal) state in 1+1 bidirectional protection switching. It starts with an initial state table for K and EXER: + +| | | +|-------------------------|--------| +| K | EXER | +| Exercise
W=act P=stb | | +| null | normal | + +Legend: + +- Only for revertive mode +- Only for Non-revertive mode + +States and Transitions: + +- EXER (normal)** leads to **SF**, **SF-P**, **LO**, **FS**, **SD**, **SD-P**, **MS**, **MS-W**, **EXER**, and **CLEAR**. +- SF**, **SF-P**, **LO**, **FS**, **SD**, **SD-P**, **MS**, **MS-W**, **EXER**, and **CLEAR** all lead to a "Switch to protection" state. +- From "Switch to protection", the states transition to: **SF**, **SF-P**, **LO**, **FS**, **SD**, **SD (r=null b=normal)**, **MS**, **MS (r=null b=normal)**, **EXER**, and **NR (r=null b=normal)**. +- These states lead to intermediate states: **E**, **F**, **C**, **D**, **P**, **Q**, **G**, **H**, **K**, and **A**. +- From these intermediate states, the diagram shows further transitions to: **LO**, **SF-P**, **FS**, **SF**, **SD**, **SD (r=null b=normal)**, **MS**, **MS (r=null b=normal)**, **WTR**, **EXER (r=null b=normal)**, **RR (r=null b=normal)**, **NR (r=null b=normal)**, and **DNR (r=null b=normal)**. +- From these intermediate states, the diagram shows further transitions to: **NR (r=null b=normal)**, **NR (r=null b=normal)**, **NR (r=null b=normal)**, **NR (r=null b=normal)**, **NR (r=null b=normal)**, **NR (r=null b=normal)**, **NR (r=null b=normal)**, **NR (r=null b=normal)**, **K**, and **A**. +- From these intermediate states, the diagram shows further transitions to: **A**, **B**, **A**, **B**, **A**, **B**, **A**, **B**, **K**, and **A**. + +State transition diagram for EXER(r=null, b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR) and their corresponding protection states (Switch to protection, NR, SD, MS). It includes a legend for revertive and non-revertive modes and an initial state table for K and EXER. + +Figure IV.27 – EXER(r=null, b=normal) state for 1+1 bidirectional protection switching + +![State transition diagram for EXER(r/b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR) and their corresponding protection states (Switch to working, NR, SD, MS). It includes a legend for non-revertive mode and an initial state table for L and EXER.](37806e0fc150d857046ebc7e47893d7a_img.jpg) + +The diagram illustrates the state transitions for the EXER(r/b=normal) state in 1+1 bidirectional protection switching. It starts with an initial state table for L and EXER: + +| | | +|-------------------------|--------| +| L | EXER | +| Exercise
W=stb P=act | | +| normal | normal | + +Legend: + +- Only for Non-revertive mode + +States and Transitions: + +- EXER (normal)** leads to **SF**, **SF-P**, **LO**, **FS**, **SD**, **SD-P**, **MS**, **MS-W**, **EXER**, and **CLEAR**. +- SF**, **SF-P**, **LO**, **FS**, **SD**, **SD-P**, **MS**, **MS-W**, **EXER**, and **CLEAR** all lead to a "Switch to working" state. +- From "Switch to working", the states transition to: **SF**, **SF-P**, **LO**, **FS**, **SD**, **SD (r=null b=normal)**, **MS**, **MS (r=null b=normal)**, **EXER**, and **DNR (r=null b=normal)**. +- These states lead to intermediate states: **E**, **F**, **C**, **D**, **P**, **Q**, **G**, **H**, **L**, and **J**. +- From these intermediate states, the diagram shows further transitions to: **LO**, **SF-P**, **FS**, **SF**, **SD**, **SD (r=null b=normal)**, **MS**, **MS (r=null b=normal)**, **WTR**, **EXER (r=null b=normal)**, **RR (r=null b=normal)**, **NR (r=null b=normal)**, and **DNR (r=null b=normal)**. +- From these intermediate states, the diagram shows further transitions to: **NR (r=null b=normal)**, **NR (r=null b=normal)**, **NR (r=null b=normal)**, **NR (r=null b=normal)**, **NR (r=null b=normal)**, **NR (r=null b=normal)**, **NR (r=null b=normal)**, **NR (r=null b=normal)**, **L**, and **J**. +- From these intermediate states, the diagram shows further transitions to: **A**, **B**, **A**, **B**, **A**, **B**, **A**, **B**, **L**, and **J**. + +State transition diagram for EXER(r/b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER, CLEAR) and their corresponding protection states (Switch to working, NR, SD, MS). It includes a legend for non-revertive mode and an initial state table for L and EXER. + +Figure IV.28 – EXER(r/b=normal) state for 1+1 bidirectional protection switching + +![State transition diagram for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, NR, DNR, WTR) based on specific conditions. It includes a 'Reverse Request' (RR) state with 'W=act' and 'P=stb' parameters. States are categorized into 'null' and 'normal' modes. Some states are marked as 'Only for Non-revertive mode'. Transitions lead to various end states labeled A, B, C, D, E, F, G, H, K, M, and P.](5cc4a2ef554f31ea0577731931007fff_img.jpg) + +The diagram illustrates the state transitions for 1+1 bidirectional protection switching. It begins with a 'Reverse Request' (RR) state, which is divided into 'null' and 'normal' modes. The 'null' mode leads to a 'Reverse Request' state with 'W=act' and 'P=stb' parameters. The 'normal' mode leads to a 'Reverse Request' state with 'r=null' and 'b=normal' parameters. The diagram shows transitions between various states based on specific conditions, leading to various end states labeled A, B, C, D, E, F, G, H, K, M, and P. Some states are marked as 'Only for Non-revertive mode'. + +**States and Transitions:** + +- RR (Reverse Request):** Initial state with 'W=act' and 'P=stb' parameters. Transitions to 'SF', 'SF-P', 'LO', 'FS', 'SD', 'SD-P', 'MS', 'MS-W', and 'EXER' states. +- SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER:** Intermediate states. Transitions from 'SF', 'SF-P', 'LO', 'FS', 'SD', 'SD-P', 'MS', 'MS-W', and 'EXER' lead to 'Switch to protection' or directly to end states (E, F, C, D, P, Q, G, H, K). +- Switch to protection:** State transition block. Transitions from 'SF', 'SF-P', 'LO', 'FS', 'SD', 'SD-P', 'MS', 'MS-W', and 'EXER' lead to 'Switch to protection' or directly to end states. +- LO, SF-P, FS, SF, SD, SD (r=null, b=normal), MS, MS (r=null, b=normal), WTR, EXER (r=null, b=normal), RR (r=null, b=normal), NR (r=null, b=normal), DNR (r=null, b=normal):** Intermediate states. Transitions from these states lead to 'Switch to protection' or directly to end states (A, B, C, D, E, F, G, H, K, M, P). +- NR (r=null, b=normal):** State transition block. Transitions from 'LO', 'SF-P', 'FS', 'SF', 'SD', 'SD (r=null, b=normal)', 'MS', 'MS (r=null, b=normal)', 'WTR', 'EXER (r=null, b=normal)', 'RR (r=null, b=normal)', 'NR (r=null, b=normal)', and 'DNR (r=null, b=normal)' lead to 'NR (r=null, b=normal)' or directly to end states. +- End States:** A, B, C, D, E, F, G, H, K, M, P. Some states (B, M) are marked as 'Only for Non-revertive mode'. + +State transition diagram for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, NR, DNR, WTR) based on specific conditions. It includes a 'Reverse Request' (RR) state with 'W=act' and 'P=stb' parameters. States are categorized into 'null' and 'normal' modes. Some states are marked as 'Only for Non-revertive mode'. Transitions lead to various end states labeled A, B, C, D, E, F, G, H, K, M, and P. + +Figure IV.29 – RR(r=null, b=normal) state for 1+1 bidirectional protection switching + +![State transition diagram for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, RR, DNR) based on specific conditions like 'Switch to working' or 'r=null b=normal'. It includes a 'Reverse Request' box at the top and a note 'Only for Non-revertive mode'.](d546a282ce562b4930a36fcf2ec3e7b3_img.jpg) + +The diagram illustrates the state transitions for 1+1 bidirectional protection switching. At the top, a 'Reverse Request' box contains 'W=stb P=act' and two 'normal' states. A note indicates this is 'Only for Non-revertive mode'. The main part of the diagram shows a series of states and transitions: + +- Top Row:** SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, EXER. +- Transitions from Top Row:** + - SF-P, LO, SD-P, and MS-W all lead to a 'Switch to working' state. + - SF, FS, SD, MS, and EXER lead directly to the next row of states. +- Second Row:** SF, SF-P, LO, FS, SD, SD (r=null b=normal), MS, MS (r=null b=normal), EXER (r/b=normal). +- Transitions from Second Row:** + - SD (r=null b=normal), MS (r=null b=normal), and EXER (r/b=normal) lead to the third row of states. + - SF, SF-P, LO, FS, SD, and MS lead to the next row of states. +- Third Row:** LO, SF-P, FS, SF, SD, SD (r=null b=normal), MS, MS (r=null b=normal), WTR, EXER (r/b=normal), RR (r/b=normal), DNR (r/b=normal). +- Transitions from Third Row:** + - SD (r=null b=normal), MS (r=null b=normal), and EXER (r/b=normal) lead to 'Switch to working' states. + - LO, SF-P, FS, SF, SD, MS, WTR, RR (r/b=normal), and DNR (r/b=normal) lead to the final row of states. +- Final Row:** NR (r=null b=normal), NR (r/b=normal), NR (r=null b=normal), NR (r/b=normal), NR (r=null b=normal), NR (r/b=normal), N, DNR (r/b=normal). + +Circles labeled A through L represent specific states or endpoints in the switching process. + +State transition diagram for 1+1 bidirectional protection switching. The diagram shows transitions between various states (SF, LO, FS, SD, MS, EXER, RR, DNR) based on specific conditions like 'Switch to working' or 'r=null b=normal'. It includes a 'Reverse Request' box at the top and a note 'Only for Non-revertive mode'. + +Figure IV.30 – RR(r/b=normal) state for 1+1 bidirectional protection switching + +![Flowchart for SD(r/b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states based on signal conditions and configuration modes (revertive vs non-revertive).](e8f5117fb031f413a836525061addd61_img.jpg) + +The diagram illustrates the state transitions for 1+1 bidirectional protection switching starting from a Signal Degrade (SD) state. At the top, a state box shows **P SD** with **Signal Degrade (W)**, **W=stb P=act**, and inputs **normal normal**. + +A legend defines specific box styles: +- Vertical stripes: **Only for revertive mode** +- Cross-hatching: **Only for Non-revertive mode** + +The main flow consists of several parallel paths leading to terminal states (circles): +- **SF** → **SF** → **E** +- **SF-P** → **Switch to working** → **SF-P** → **F** +- **LO** → **Switch to working** → **LO** → **C** +- **FS** → **FS** → **D** +- **Working recovers from SD** → Decision: **Local SD-P?** +  - If **Yes** → **SD r=null b=normal** → **Q** +  - If **No** → Decision: **Revertive Mode?** +    - If **Yes** → **WTR** (striped) → **I** +    - If **No** → **DNR** (hatched) → **J** +- **SD-P** → **P** +- **Protection recovers from SD** → **P** +- **MS** → **P** +- **MS-W** → **P** +- **EXER** → **P** + +A bottom section shows transitions from various states (LO, SF-P, FS, SF, SD, SD r=null b=normal, MS, MS r=null b=normal, WTR) leading to: +- **Switch to working** → **NR r=null b=normal** → **A** +- **NR r/b=normal** → **B** +- A series of states leading to **P**: **EXER r=null b=normal**, **EXER r/b=normal**, **RR r=null b=normal**, **RR r/b=normal**, **NR r=null b=normal**, **NR r/b=normal**, and **DNR r/b=normal**. + +Flowchart for SD(r/b=normal) state for 1+1 bidirectional protection switching. The diagram shows transitions between various states based on signal conditions and configuration modes (revertive vs non-revertive). + +**Figure IV.31 – SD(r/b=normal) state for 1+1 bidirectional protection switching** + +![State transition diagram for 1+1 bidirectional protection switching in the SD(r=null, b=normal) state.](ec96d99a16edb981eb7defe41a79b57f_img.jpg) + +This diagram illustrates the state transitions for the SD(r=null, b=normal) state in 1+1 bidirectional protection switching. The top state is defined as Q / SD: Signal Degrade (P), W=act P=stb, with sub-states null and normal. + +The diagram branches into several input event paths: + +- SF:** Leads to 'Switch to protection' then state **E**. +- SF-P:** Leads to state **F**. +- LO:** Leads to state **C**. +- FS:** Leads to state **D**. +- SD:** Leads to state **Q**. +- Working recovers from SD:** Leads to a decision 'Local SD?'. If No, state **A** (NR r=null b=normal). If Yes, state **P** (SD). +- Protection recovers from SD:** Leads to state **Q**. +- MS:** Leads to state **Q**. +- MS-W:** Leads to state **Q**. +- EXER:** Leads to state **Q**. + +A second tier of transitions (labeled 'Only for Non-revertive mode') includes inputs like LO, SF-P, FS, SF, SD, MS, WTR, leading to various NR (No Request), RR (Reverse Request), EXER (Exercise), and DNR (Do Not Revert) states with specific r and b values, eventually terminating in states **A**, **B**, or **Q**. + +State transition diagram for 1+1 bidirectional protection switching in the SD(r=null, b=normal) state. + +Figure IV.32 – SD(r=null, b=normal) state for 1+1 bidirectional protection switching + +### IV.2.3 1+1 unidirectional protection switching + +The following diagrams define state transitions of 1+1 unidirectional protection switching both in revertive and non-revertive modes. + +![State transition diagram for 1+1 unidirectional protection switching in the NR(W=act/P=stb) state.](28f2f470a7b2446ae5f525123534383c_img.jpg) + +This diagram illustrates the NR(W=act/P=stb) state for 1+1 unidirectional protection switching. The initial state is **A**: No Request, W=act P=stb. + +Transitions based on input events: + +- SF:** 'Switch to protection' → state **E**. +- SF-P:** → state **F**. +- LO:** → state **C**. +- FS:** 'Switch to protection' → state **D**. +- SD:** 'Switch to protection' → state **P**. +- SD-P:** → state **Q**. +- MS:** 'Switch to protection' → state **G**. +- MS-W:** → state **H**. + +State transition diagram for 1+1 unidirectional protection switching in the NR(W=act/P=stb) state. + +Figure IV.33 – NR(W=act/P=stb) state for 1+1 unidirectional protection switching + +![State transition diagram for LO(W=act/P=stb) state for 1+1 unidirectional protection switching. The diagram shows transitions between various states including SF, LO, FS, SD, MS, and CLEAR, leading to terminal states C, E, P, A, Q, and F.](d1ad05f1189b0d80188fee24ae33c112_img.jpg) + +The diagram illustrates the state transitions for the LO(W=act/P=stb) state. It begins with a 'Lockout' state (C) where W=act and P=stb. Transitions from this state lead to SF, Working recovers from SF, SF-P, Protection recovers from SF, LO, FS, SD, Working recovers from SD, SD-P, and Protection recovers from SD. These states then lead to MS, MS-W, and CLEAR. From CLEAR, the path leads to a decision diamond 'Local SF/P?'. If 'No', it leads to another decision diamond 'Local SD/P?'. If 'No' to the second diamond, it leads to 'Switch to protection' (E) or 'Switch to protection' (P). If 'Yes' to either diamond, it leads to terminal states A, Q, or F. A long vertical line on the left leads from the first row of states to terminal state C. + +State transition diagram for LO(W=act/P=stb) state for 1+1 unidirectional protection switching. The diagram shows transitions between various states including SF, LO, FS, SD, MS, and CLEAR, leading to terminal states C, E, P, A, Q, and F. + +Figure IV.34 – LO(W=act/P=stb) state for 1+1 unidirectional protection switching + +![State transition diagram for FS(W=stb/P=act) state for 1+1 unidirectional protection switching. The diagram includes a legend for 'Only for revertive mode' and 'Only for Non-revertive mode'. It shows transitions between states like SF, LO, FS, SD, MS, and CLEAR, leading to terminal states D, F, C, P, A, J, Q, and E.](bd0283b61b6a59829e9370b29076c79a_img.jpg) + +The diagram illustrates the state transitions for the FS(W=stb/P=act) state. It begins with a 'Forced Switch' state (D) where W=stb and P=act. A legend indicates that states with vertical stripes are 'Only for revertive mode' and states with cross-hatching are 'Only for Non-revertive mode'. Transitions from the initial state lead to SF, Working recovers from SF, SF-P, LO, FS, SD, Working recovers from SD, SD-P, and Protection recovers from SD. These lead to MS, MS-W, and CLEAR. From CLEAR, the path leads to a decision diamond 'Local SF?'. If 'Yes', it leads to terminal state D. If 'No', it leads to 'Local SD/P?'. If 'No', it leads to 'Revertive Mode?'. If 'Yes' to 'Revertive Mode?', it leads to 'Switch to working' (A, revertive mode). If 'No', it leads to 'Switch to working' (Q). If 'Yes' to 'Local SD/P?', it leads to 'Switch to working' (P). Terminal states include D, F, C, P, A (revertive), J (non-revertive), Q, and E. + +State transition diagram for FS(W=stb/P=act) state for 1+1 unidirectional protection switching. The diagram includes a legend for 'Only for revertive mode' and 'Only for Non-revertive mode'. It shows transitions between states like SF, LO, FS, SD, MS, and CLEAR, leading to terminal states D, F, C, P, A, J, Q, and E. + +Figure IV.35 – FS(W=stb/P=act) state for 1+1 unidirectional protection switching + +![State transition diagram for SF(W=stb/P=act) state for 1+1 unidirectional protection switching. The diagram shows transitions between states P, I, J, Q, F, C, D, and E based on various failure and recovery events. A legend indicates that states with vertical stripes are 'Only for revertive mode' and states with cross-hatching are 'Only for Non-revertive mode'.](811d62d08ce934a2a7e5bd877abff7ad_img.jpg) + +The diagram illustrates the state transitions for the SF(W=stb/P=act) state. It begins with an initial state 'E' (Signal Fail (W) W=stb P=act). Transitions are triggered by events such as 'Working recovers from SF', 'SF-P', 'LO', 'FS', 'SD', 'Working recovers from SD', 'SD-P', 'Protection recovers from SD', 'MS', and 'MS-W'. Decision diamonds include 'SD Local SD-P?' and 'Revertive Mode?'. States are categorized as follows: + +- Normal states:** P, Q, F, C, D, E. +- Only for revertive mode:** I (vertical stripes). +- Only for Non-revertive mode:** J (cross-hatching). + +State transition diagram for SF(W=stb/P=act) state for 1+1 unidirectional protection switching. The diagram shows transitions between states P, I, J, Q, F, C, D, and E based on various failure and recovery events. A legend indicates that states with vertical stripes are 'Only for revertive mode' and states with cross-hatching are 'Only for Non-revertive mode'. + +Figure IV.36 – SF(W=stb/P=act) state for 1+1 unidirectional protection switching + +![State transition diagram for SF-P(W=act/P=stb) state for 1+1 unidirectional protection switching. The diagram shows transitions between states F, E, P, A, Q, C, and F based on various failure and recovery events. A legend indicates that states with vertical stripes are 'Only for revertive mode' and states with cross-hatching are 'Only for Non-revertive mode'.](90183a52275501da5a0fd5c63d837009_img.jpg) + +The diagram illustrates the state transitions for the SF-P(W=act/P=stb) state. It begins with an initial state 'F' (Signal Fail (P) W=act P=stb). Transitions are triggered by events such as 'SF', 'Working recovers from SF', 'Protection recovers from SF', 'LO', 'FS', 'SD', 'Working recovers from SD', 'SD-P', 'Protection recovers from SD', 'MS', and 'MS-W'. Decision diamonds include 'Local SF?' and 'SD Local SD-P?'. States are categorized as follows: + +- Normal states:** F, E, P, A, Q, C. +- Only for revertive mode:** F (vertical stripes). + +State transition diagram for SF-P(W=act/P=stb) state for 1+1 unidirectional protection switching. The diagram shows transitions between states F, E, P, A, Q, C, and F based on various failure and recovery events. A legend indicates that states with vertical stripes are 'Only for revertive mode' and states with cross-hatching are 'Only for Non-revertive mode'. + +Figure IV.37 – SF-P(W=act/P=stb) state for 1+1 unidirectional protection switching + +![State transition diagram for MS(W=stb/P=act) state for 1+1 unidirectional protection switching. The diagram shows transitions between states E, F, C, D, P, Q, G, A, and J based on various failure and recovery events. A legend indicates that states with vertical stripes are 'Only for revertive mode' and states with cross-hatching are 'Only for Non-revertive mode'.](f7b2cf9e1b71dc4f900f3810646d3903_img.jpg) + +The diagram illustrates the state transitions for the MS(W=stb/P=act) state. It begins with an initial state 'G' (Manual Switch W=stb P=act). Transitions are triggered by events such as 'SF', 'SF-P', 'LO', 'FS', 'SD', 'SD-P', 'MS', 'MS-W', and 'CLEAR'. Decision diamonds include 'Revertive Mode?'. States are categorized as follows: + +- Normal states:** E, F, C, D, P, Q, G. +- Only for revertive mode:** A (vertical stripes). +- Only for Non-revertive mode:** J (cross-hatching). + +State transition diagram for MS(W=stb/P=act) state for 1+1 unidirectional protection switching. The diagram shows transitions between states E, F, C, D, P, Q, G, A, and J based on various failure and recovery events. A legend indicates that states with vertical stripes are 'Only for revertive mode' and states with cross-hatching are 'Only for Non-revertive mode'. + +Figure IV.38 – MS(W=stb/P=act) state for 1+1 unidirectional protection switching + +![State diagram for Manual Switch (W=act P=stb) mode. The initial state is 'Manual Switch W=act P=stb' (H). Transitions lead to SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, and CLEAR. SF, FS, and SD lead to 'Switch to protection' which leads to state E. SF-P leads to state F. LO leads to state C. SD-P leads to state Q. MS leads to state H. MS-W leads to state H. CLEAR leads to state A.](401f020d9ab5904f584424eabb596d2c_img.jpg) + +``` + +stateDiagram-v2 + [*] --> ManualSwitch: Manual Switch W=act P=stb + ManualSwitch --> SF + ManualSwitch --> SF-P + ManualSwitch --> LO + ManualSwitch --> FS + ManualSwitch --> SD + ManualSwitch --> SD-P + ManualSwitch --> MS + ManualSwitch --> MS-W + ManualSwitch --> CLEAR + SF --> SwitchToProtection1: Switch to protection + SwitchToProtection1 --> E + SF-P --> F + LO --> C + FS --> SwitchToProtection2: Switch to protection + SwitchToProtection2 --> D + SD --> SwitchToProtection3: Switch to protection + SwitchToProtection3 --> P + SD-P --> Q + MS --> H + MS-W --> H + CLEAR --> A + +``` + +State diagram for Manual Switch (W=act P=stb) mode. The initial state is 'Manual Switch W=act P=stb' (H). Transitions lead to SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, and CLEAR. SF, FS, and SD lead to 'Switch to protection' which leads to state E. SF-P leads to state F. LO leads to state C. SD-P leads to state Q. MS leads to state H. MS-W leads to state H. CLEAR leads to state A. + +Figure IV.39 – MS(W=act/P=stb) state for 1+1 unidirectional protection switching + +![State diagram for Wait To Restore (W=stb P=act) mode. The initial state is 'Wait To Restore W=stb P=act' (I). Transitions lead to SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, CLEAR, and WTR timer expires. SF, LO, and SD lead to 'Switch to working' which leads to state E. SF-P leads to state F. LO leads to state C. SD-P leads to state Q. MS leads to state G. MS-W leads to state H. CLEAR leads to state A. WTR timer expires leads to state A.](8a781a0a8c956859f63a1ca7f2bb1644_img.jpg) + +``` + +stateDiagram-v2 + [*] --> WaitToRestore: Wait To Restore W=stb P=act + WaitToRestore --> SF + WaitToRestore --> SF-P + WaitToRestore --> LO + WaitToRestore --> FS + WaitToRestore --> SD + WaitToRestore --> SD-P + WaitToRestore --> MS + WaitToRestore --> MS-W + WaitToRestore --> CLEAR + WaitToRestore --> WTR: WTR timer expires + SF --> SwitchToWorking1: Switch to working + SwitchToWorking1 --> E + SF-P --> F + LO --> SwitchToWorking2: Switch to working + SwitchToWorking2 --> C + FS --> D + SD --> SwitchToWorking3: Switch to working + SwitchToWorking3 --> P + SD-P --> Q + MS --> G + MS-W --> H + CLEAR --> SwitchToWorking4: Switch to working + SwitchToWorking4 --> A + WTR --> A + +``` + +State diagram for Wait To Restore (W=stb P=act) mode. The initial state is 'Wait To Restore W=stb P=act' (I). Transitions lead to SF, SF-P, LO, FS, SD, SD-P, MS, MS-W, CLEAR, and WTR timer expires. SF, LO, and SD lead to 'Switch to working' which leads to state E. SF-P leads to state F. LO leads to state C. SD-P leads to state Q. MS leads to state G. MS-W leads to state H. CLEAR leads to state A. WTR timer expires leads to state A. + +Figure IV.40 – WTR(W=stb/P=act) state for 1+1 unidirectional protection switching + +![State diagram for Do Not Revert (W=stb P=act) mode. The initial state is 'Do Not Revert W=stb P=act' (J). Transitions lead to SF, SF-P, LO, FS, SD, SD-P, MS, and MS-W. SF, LO, and SD lead to 'Switch to working' which leads to state E. SF-P leads to state F. LO leads to state C. SD-P leads to state Q. MS leads to state G. MS-W leads to state H.](f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg) + +``` + +stateDiagram-v2 + [*] --> DoNotRevert: Do Not Revert W=stb P=act + DoNotRevert --> SF + DoNotRevert --> SF-P + DoNotRevert --> LO + DoNotRevert --> FS + DoNotRevert --> SD + DoNotRevert --> SD-P + DoNotRevert --> MS + DoNotRevert --> MS-W + SF --> SwitchToWorking1: Switch to working + SwitchToWorking1 --> E + SF-P --> F + LO --> SwitchToWorking2: Switch to working + SwitchToWorking2 --> C + FS --> D + SD --> SwitchToWorking3: Switch to working + SwitchToWorking3 --> P + SD-P --> Q + MS --> G + MS-W --> H + +``` + +State diagram for Do Not Revert (W=stb P=act) mode. The initial state is 'Do Not Revert W=stb P=act' (J). Transitions lead to SF, SF-P, LO, FS, SD, SD-P, MS, and MS-W. SF, LO, and SD lead to 'Switch to working' which leads to state E. SF-P leads to state F. LO leads to state C. SD-P leads to state Q. MS leads to state G. MS-W leads to state H. + +Figure IV.41 – DNR(W=stb/P=act) state for 1+1 unidirectional protection switching + +![State transition diagram for SD(W=stb/P=act) state for 1+1 unidirectional protection switching (Figure IV.42).](9c80cf99954eb0142f694456d39fae4b_img.jpg) + +``` + +graph TD + Start((P)) --> SD_W[Signal Degrade W +W=stb P=act] + SD_W --> SF + SD_W --> SF-P + SD_W --> LO + SD_W --> FS + SD_W --> WRSD[Working recovers from SD] + SD_W --> SD-P + SD_W --> PRSD[Protection recovers from SD] + SD_W --> MS + SD_W --> MS-W + + SF --> E((E)) + SF-P --> SWW1[Switch to working] --> F((F)) + LO --> SWW2[Switch to working] --> C((C)) + FS --> D((D)) + + WRSD --> LSDP{Local SD-P?} + LSDP -- No --> RM{Revertive Mode?} + LSDP -- Yes --> Q((Q)) + + RM -- Yes --> I((I)) + RM -- No --> J((J)) + + SD-P --> P((P)) + PRSD --> P + MS --> P + MS-W --> P + + subgraph Legend + L1[Only for revertive mode] --- I + L2[Only for Non-revertive mode] --- J + end + +``` + +The diagram illustrates state transitions from state P (Signal Degrade (W), W=stb, P=act). Input events lead to various target states: SF to E; SF-P through 'Switch to working' to F; LO through 'Switch to working' to C; FS to D. 'Working recovers from SD' leads to a decision 'Local SD-P?'. If 'Yes', it goes to state Q. If 'No', it leads to 'Revertive Mode?'. If 'Yes', it goes to state I (revertive mode only); if 'No', it goes to state J (non-revertive mode only). Events SD-P, 'Protection recovers from SD', MS, and MS-W all lead to state P. + +State transition diagram for SD(W=stb/P=act) state for 1+1 unidirectional protection switching (Figure IV.42). + +**Figure IV.42 – SD(W=stb/P=act) state for 1+1 unidirectional protection switching** + +![State transition diagram for SD(W=stb/P=act) state for 1+1 unidirectional protection switching (Figure IV.43).](8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg) + +``` + +graph TD + Start((Q)) --> SD_P[Signal Degrade P +W=act P=stb] + SD_P --> SF + SD_P --> SF-P + SD_P --> LO + SD_P --> FS + SD_P --> SD + SD_P --> WRSD[Working recovers from SD] + SD_P --> PRSD[Protection recovers from SD] + SD_P --> MS + SD_P --> MS-W + + SF --> SWP1[Switch to protection] --> E((E)) + SF-P --> F((F)) + LO --> C((C)) + FS --> SWP2[Switch to protection] --> D((D)) + + SD --> Q((Q)) + WRSD --> LSD{Local SD?} + PRSD --> LSD + + LSD -- No --> A((A)) + LSD -- Yes --> P((P)) + + MS --> Q + MS-W --> Q + +``` + +The diagram illustrates state transitions from state Q (Signal Degrade (P), W=act, P=stb). Input events lead to target states: SF through 'Switch to protection' to E; SF-P to F; LO to C; FS through 'Switch to protection' to D; SD to Q. Both 'Working recovers from SD' and 'Protection recovers from SD' lead to a 'Local SD?' decision. If 'No', it goes to state A; if 'Yes', it goes to state P. Events MS and MS-W lead back to state Q. + +State transition diagram for SD(W=stb/P=act) state for 1+1 unidirectional protection switching (Figure IV.43). + +**Figure IV.43 – SD(W=stb/P=act) state for 1+1 unidirectional protection switching** + + + +## 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 | +| 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 | + +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 | 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.807-202410-I_PDF-E/04dc3838022e96d8d5548bb1b777b38c_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/04dc3838022e96d8d5548bb1b777b38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..179ff3116977e18bd15fb163738f0f7ffdd2535d --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/04dc3838022e96d8d5548bb1b777b38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7cbc90db5c8e28b254de890e4e92acdd6737c93986f558a8c64da3c37b261f22 +size 44890 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/0fc5900959ab10acc878f9ca1e00fe37_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/0fc5900959ab10acc878f9ca1e00fe37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19600bd569ae1f25ebe5c91543c31935abca6385 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/0fc5900959ab10acc878f9ca1e00fe37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f8cb852c54dccbc4a9a950a6b8313413f84c1f0c9f7b940acfe6051b82203e8 +size 1518 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96e0f06d4013830cd3be3b6553a0e7afb2db1953 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40c760542912ac7a6d1af055454041b76aac6c1b82c695b98390afc93373b352 +size 33431 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a415c4056fe143f27c26fcb09c1f4aed65a44b9 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e480c674b57e9f7d495c05147541fd0e0fb9f8ae4e0eb1911ae938affbd6312 +size 82839 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c827f374a3abfb5b4ce3d34e727c4ab4a27417dc --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cfda77e9c349f8347df3695ab930fd3061cb6b5446dbe5c55eef62f41536dfc +size 39941 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a390acdcdfa9ea516298b7a803e2d996854ee1b4 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c876949cac76dd93e8cff0e4d769ac222d379d7bd1cfa1a7be5ecf404aa96c1 +size 35215 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbeba0424c2571610a4063a97b214cb36f1ae455 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f3b6320c724804c51c9ba655a413878c548ee856fea28166b2b4333d6fcb94c +size 93981 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/1ec9c5991b6cfbe205eacf87caeef44f_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/1ec9c5991b6cfbe205eacf87caeef44f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5355837d274ccdca60433fd8bf4d37b2a45e9df3 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/1ec9c5991b6cfbe205eacf87caeef44f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c11cf94923917fea6133a079d5e33ba854d42c5295b7152a50ddc2840b99b16 +size 996 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea40d761aeb4ed84c6e8e8d67723a112e243ada4 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b391dff6da1a60de49c8ca350e3639cb390e20c4b974c5cb0cf18f20c8d22336 +size 89168 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/237b76118be454462fc9b4e96adaa6c7_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/237b76118be454462fc9b4e96adaa6c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3587acdf61855ed50aa34d4049a9ff8d8ae31f99 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/237b76118be454462fc9b4e96adaa6c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70f692805c2948aeca9d679c02fff9a3ca8745d8c6230605ebac551c565c8459 +size 65388 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e12a1e6513c7467244d8c3050c47a48beb1e7c7 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24869595ed49ba049ae47596ab06e17987f2a1fb7670b4833d34eb055080c104 +size 102755 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/29f586959675cafdf81cf934954908eb_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/29f586959675cafdf81cf934954908eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6898ea11e518eac2c4af0999f9b8d6e10d8528b9 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/29f586959675cafdf81cf934954908eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:227b7dafc9c9227b665e888775c5cc50249d72eef429b171a59b9babee24fdff +size 57043 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/2e39534fa484c54b999a1fc9c8a46d5a_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/2e39534fa484c54b999a1fc9c8a46d5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7d0fbc2034240c3139745753f10bc178196711c --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/2e39534fa484c54b999a1fc9c8a46d5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc9f0772db27278f770376f84c97313a0b5a8c4b49ca354111ac91a4b734ddaf +size 1049 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7283ad03cc32867e27d9ff62537e8c39981d7eb9 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c31e07dca6b18123c060a1bb382cf25dfee8b05a371edc3cdf2fd0aa222da53 +size 21904 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7adc3caa7544f03e6f44027b6620505a45594d2e --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2857a70ab21a771e54a8b46994c118e82881dbae28bab4cfca322b7ec181f696 +size 74633 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/3b6177b1edfdc8c7740f03f346d7838f_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/3b6177b1edfdc8c7740f03f346d7838f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55c9960789cbdbc52149e29a0763866a77c8747d --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/3b6177b1edfdc8c7740f03f346d7838f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8e4f7c8cb9c91f917d2e5f7af26634bbf0dcbb386e47e59ce619222efb99073 +size 79716 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6693612ab410f9119b75952e95cd14ef3e01a893 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c90427df666991d2443e81f29ffbcf889d8a503cbc8137680be682bbfa25d831 +size 82890 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f530a635276d8b4d2e4996204f2dee9bf9a846ef --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1e8eb05d8ac109312f771df15c961125baf9462cc25486ec8c64f34b5afe3e8 +size 48519 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/4d7832f32da92348575447a4aae88cd6_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/4d7832f32da92348575447a4aae88cd6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2547e65edc429cfd87fbdcc18df39c40c4552bb4 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/4d7832f32da92348575447a4aae88cd6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:183c7dfc3773b4b32f50109e6839dd25e390312efad6b002c49c6550a7b31df7 +size 891 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a632b7fa52288ed84e36fcf4a1bca28b1fb010b --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84d7566266c837955782e999f9d0e65e18c16ce1ce96649a3c5c2c50cf0a45a9 +size 42528 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/5478f70a6cef3e5672b2b22d28830cfb_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/5478f70a6cef3e5672b2b22d28830cfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cadc5a0ed518518310268683b93aa6e1d12813f1 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/5478f70a6cef3e5672b2b22d28830cfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:887bd19b821423731a55f6011da8bab169da40b720d4ac62324f2646e09b25b4 +size 35626 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41993047774bbacbe919296f4b20cf14ac914025 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6fa1cea877625d56c0072757b37238ca4c2625df96515a00cdb06f6caa1b68b +size 104661 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/638a308af25f1f56b4456a1fc503f161_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/638a308af25f1f56b4456a1fc503f161_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69d5c93b991d60b0a14ccf63e01170bc05ab896c --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/638a308af25f1f56b4456a1fc503f161_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27a6f86826803e5cd9dc19aeda3dcc24fef5944a4bef9bdafe4a26ee44f0f75d +size 35892 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/6707cae4df136f92a0c9f3a4676f91a6_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/6707cae4df136f92a0c9f3a4676f91a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21205bf3caca1a1d7fbc45053b86b5c87e30bbf0 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/6707cae4df136f92a0c9f3a4676f91a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91117bd1a246789b85340cb6c83a926d052ea3ab67d5ff4362d71890a69b5af7 +size 50072 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e196cd8f3b6be9015e4d0aaa126bd3e65e8efaf --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:608d20355cd6f0f04ff15f3611b56962e59a67e206923b3178738f560488bd6d +size 60639 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abda52cbb1047d6649f89e40c898a1c33bed7267 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f3b7e07231c0f3e116c99c493bdda98ecd52313b6735faa6cea23815cf3162b +size 7190 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8e5f2b7147e3741571c0f362545b553d1dc7ab3 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:031382f43546e4a84af67445d1bd1dc339748058dd4ccf4e3b78c3a67c8a9c42 +size 88498 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/742a5484e7dd016256ab99921bbd635d_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/742a5484e7dd016256ab99921bbd635d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7950f949f6f32dde1aa725929b14631d4593f936 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/742a5484e7dd016256ab99921bbd635d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df8ea415473b3986588098e9f1b63e490f247c7a41f710497392241d21af0c38 +size 58416 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2580215c1e62ea936871dfccc32dca788de2d474 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4919de9de270955594ff67c760d60e4b92d7c76e41281045867555e62e28d74c +size 108038 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64e171b66aba99461123b60a07ca40c666b17f27 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a2b1fdc9ca76946de7c167bda76bafe05a6c8cb72b4375bf266f7b5e2072906 +size 28064 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..683be947e72a2c5a42e769dc4f7265c619d33b86 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b52d84ce797518c94ba98a5698cceac5a7a336d9225349b1615d13f9b5ed8f0 +size 100505 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe77a792ec60470ddb1b128dcb7250897105e1ad --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06a593eace704d5f33ff0dc5d62421a02cb5be73d615b2437714e6475e67bd61 +size 82978 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/91134b9a38d7f73f03375473e7b706f9_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/91134b9a38d7f73f03375473e7b706f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37769c30bbff13ff2327cc8fb1670b4d0aa97ee5 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/91134b9a38d7f73f03375473e7b706f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4441e7211af5af0e3c2836b53c53cce8ea6c97b83bca594e18333791b1b4d3d6 +size 25340 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/95e259e8cb3519025066052af263f8c0_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/95e259e8cb3519025066052af263f8c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a702a527c53a48c4b11bdcda6d1164e66f7ce946 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/95e259e8cb3519025066052af263f8c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d99d20ad3f03b6a82799a9472a03669554662fbb0e0691dac2dacf28e73f58f5 +size 97573 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/9cb54072e43a6b6717eb16036a7640a2_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/9cb54072e43a6b6717eb16036a7640a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acd77653c2e56d604689b23e22deedb290002cc4 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/9cb54072e43a6b6717eb16036a7640a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a06771690daaa0e2bc9b41cc41aeb6db216c3a8e5109dc54a0d969ef1775db17 +size 49203 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fcc7301b2bb571da06cb6a51dbedeaf1a828616 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b773a885df79b15a686df9987a72918f8be90e6df878eed02473ceae346f7b6 +size 35884 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/9ed248b025d766251d58be10b01a1cc0_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/9ed248b025d766251d58be10b01a1cc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21cdb11e2ee3b822ba261afff8f08c217e74e5e3 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/9ed248b025d766251d58be10b01a1cc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3087957455492256e85edfa3ee76bb315c38febcb6a54f26f1a67a1cec4bad1 +size 16679 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a0a847f649445263f7c3fd1dea5ded728f30381 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efb7e65a2f8a693a70ad8537e236d316e6be58682c42a7704aa4451ced301243 +size 98525 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/ad6ab0b77b86612fcbfecc8e2418b31e_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/ad6ab0b77b86612fcbfecc8e2418b31e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fb644a702c71aea4b7858b7b5a37b066cf68246 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/ad6ab0b77b86612fcbfecc8e2418b31e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7827fef7af46268b949aac11201be398a53c0f4255c4662f715f842fb1f68a4 +size 977 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ba5bea05709f3d0750ddb5f1dc667c395250663 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:009ee5bdf3fb7228530b2390f59335c3c7469aaee6adf0fdebf79be90487c50a +size 73005 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00db7407dac0ff45ef167c4bbe5d58af030515a9 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d512231964e72be0d8eb9e684e8441b648d9f56245066671f91ed3597fb3925f +size 34765 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c15c9f548111e72350c3dbbb58a2a803ddd238e7 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31aa23cddabb35f8b1fcc224877684b26a6febe2eb56a5fae9bb5451107f2b26 +size 46282 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f48f78f253e7c8cee1b4316ecab5f3a036f7ebd0 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a311b5c7aab72a338b3d586f09afae386939dbfa5c47ae9c20d64a0f16dfd4a0 +size 94076 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/c3cffc168beb4396c1e1a5a6db5d66b0_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/c3cffc168beb4396c1e1a5a6db5d66b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0fa8419f5dfd275e7e1daf895ffafc0d5c28e19 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/c3cffc168beb4396c1e1a5a6db5d66b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1df47cba957cfaed1e6f37ed4017d585ead2c9b0e46b667edce0321e25401b26 +size 907 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/c419b566d720267c499087add1506018_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/c419b566d720267c499087add1506018_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2124dd3427a4e0ea26476fae0d01931e95deffe --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/c419b566d720267c499087add1506018_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d01dcbd24c8b181598dd444699956085cb994172b153e12ccb9791c26693280e +size 9173 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0819c4a37527f27481cd9d1cea08c4086d5133be --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9bb65bed141f602fd680b966e5717762eb2be23f8abd85224dca621eaefc32e +size 43172 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5d9268976ebe83a9ad0aa9441da766cb27c96a8 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:861ef7f58207d6440761871ce2083ab330edd2a783545abd5f739922df607371 +size 44013 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..feb11322d878023797ad21169cd27bdb95dbd6ac --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0ed1f1b5b0447bcf74d40b65f7c39c127e005680804ae5b0cd50a5879f83ea8 +size 9502 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc5bbba32fc22d97af3d424374120f3d43297be5 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bb20eb8c33580f459481f20a49a49a55b3e13258e4a177cdae2798233800098 +size 55208 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ddf43ffe10920883e53918f51b74cc201198c75 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1afa1fe772358b73525e7811e71445699182ea4ca670ba2592c9ba64943a9fc +size 46255 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/e05122559f56af5699789b7118d8fe87_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/e05122559f56af5699789b7118d8fe87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10d25b013cda6be386051fe5ee1c6ba5a64b1019 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/e05122559f56af5699789b7118d8fe87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a590290fdd7c9adb7d35430a1aa5e0ea177b0ff6fc884c7413ad0c0a2bf23fa8 +size 40546 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86226bd79fb3427b0a8998e9c34641156961823e --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6da82aa2bc8bc788c29461310bd4bde9d982bce3a6c583e27f111362d0bd18f3 +size 61303 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/efafcae43acae17c4bb9f41420411b00_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/efafcae43acae17c4bb9f41420411b00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9d67be8ed9f18892e4a2e1f59e96ada6606fe5e --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/efafcae43acae17c4bb9f41420411b00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0d5477848073435f90f70a5bad762e074ebc33e3d7ae388c83612c7e8ace72c +size 965 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..213198f7612123278d6047b5fd0e81c338bb81de --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee3d6c52177671a8c44be976fcef5ed484e164f1af92c5b891db8e4aa45e4294 +size 96176 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/f4f9ac412efd7fead6377a2b0ae12137_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/f4f9ac412efd7fead6377a2b0ae12137_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77228578f4d80c926b725443e04fa089bf1781e9 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/f4f9ac412efd7fead6377a2b0ae12137_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ba9215b6b83df2cd66e14ab6fcddb0748fca4b96da9699a49c0f2998ad84fc2 +size 954 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59b8ef120edf57cc35d005079cd44156344737f3 --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c99f7d2f6412c7a68834d2408c2a856484ca518bef252042e43a694970d7a60d +size 114173 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/G/T-REC-G.807-202410-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0ce5215f95450681b1c023b56b5d9d2a558a8df --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5008dbf8befd36305f8f59cdbcbcdc6c492ba1df141fcd91aeb9d32254969bc +size 46929 diff --git a/marked/G/T-REC-G.807-202410-I_PDF-E/raw.md b/marked/G/T-REC-G.807-202410-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..73006aa577a0ef17e895d8d0c0c711600f55a2cd --- /dev/null +++ b/marked/G/T-REC-G.807-202410-I_PDF-E/raw.md @@ -0,0 +1,1966 @@ + + +# Recommendation **ITU-T G.807 (10/2024)** + +SERIES G: Transmission systems and media, digital systems and networks + +Digital networks – General aspects + +--- + +# **Generic functional architecture of the optical media layer** + +![ITU logo](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a white grid pattern, overlaid by the letters 'ITU' in a bold, blue, sans-serif font. The globe is stylized with a white arrow pointing towards the upper 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 | +| General aspects | G.800-G.809 | +| Design objectives for digital networks | G.810-G.819 | +| Synchronization, quality and availability targets | G.820-G.829 | +| Network capabilities and functions | G.830-G.839 | +| SDH network characteristics | G.840-G.849 | +| Management of transport network | G.850-G.859 | +| SDH radio and satellite systems integration | G.860-G.869 | +| Optical transport networks | G.870-G.879 | +| 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.807 + +# Generic functional architecture of the optical media layer + +## Summary + +Recommendation ITU-T G.807 describes the generic functional architecture of the optical media layer, that supports the propagation of signals within a transport network. This description is independent of the client characteristic information (CI) carried by a signal in the media network. + +Revision 2 updates the terminology, changing the modulator/demodulator construct to transmitter/receiver. It also aligns (esp. network media channel (NMC)) with the updated terminology in ITU-T G.959.1 (2024) Amd. 1 to include subcarrier modulation and point-to-multipoint optical topology in media architecture. Additionally, clause 10 is reorganized and includes a description of optical tributary signal (OTSi), which carries multiple independent digital clients using synchronization message channel (SCM). + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|---------------------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.807 | 2020-02-07 | 15 | 11.1002/1000/13997 | +| 1.1 | ITU-T G.807 (2020) Amd. 1 | 2021-01-13 | 15 | 11.1002/1000/14521 | +| 2.0 | ITU-T G.807 | 2024-10-22 | 15 | 11.1002/1000/16062 | + +## Keywords + +Functional architecture, optical media. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|----------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 3 | +| 4 | Abbreviations and acronyms ..... | 4 | +| 5 | Conventions ..... | 5 | +| 5.1 | Notational conventions..... | 5 | +| 5.2 | Diagrammatic conventions..... | 6 | +| 5.3 | Terminological conventions ..... | 7 | +| 5.4 | Media layer and media network ..... | 7 | +| 6 | Overview of media and signal ..... | 7 | +| 6.1 | General introduction of media and signal ..... | 7 | +| 6.2 | Functional architecture of the optical media layer ..... | 8 | +| 7 | Media constructs and media elements ..... | 10 | +| 7.1 | Media constructs..... | 10 | +| 7.2 | Media element ..... | 15 | +| 7.3 | Media network topology..... | 16 | +| 7.4 | Management of media channels ..... | 18 | +| 8 | Information/signal boundary ..... | 19 | +| 9 | Monitoring media constructs ..... | 19 | +| 9.1 | Optical parameter monitor (OPM-x) ..... | 19 | +| 9.2 | Optical signal maintenance entities (OSME) ..... | 20 | +| 10 | Optical tributary signals and interfaces ..... | 22 | +| 10.1 | OTSi ..... | 22 | +| 10.2 | OTSiG..... | 26 | +| 10.3 | OTSiA..... | 28 | +| 11 | Monitoring of optical signals..... | 33 | +| 11.1 | Non-associated overhead..... | 33 | +| 11.2 | Media channels and OSMEs ..... | 33 | +| 12 | OSC ..... | 36 | +| 13 | Transmitter/Receiver and termination functions ..... | 36 | +| 13.1 | Transmitter/Receiver ..... | 36 | +| 13.2 | OTSiG-O trail termination function ..... | 37 | +| 13.3 | OMS-O trail termination function ..... | 37 | +| 13.4 | OTS-O trail termination function ..... | 38 | +| 14 | Client/server associations ..... | 38 | + +| | Page | | +|---------------|------------------------------------------------------------------------------------|----| +| 14.1 | M-AI/ client CI adaptation function ..... | 38 | +| 14.2 | OMS-O/OTSiG-O adaptation function ..... | 39 | +| 14.3 | OTS-O/OMS-O adaptation function ..... | 39 | +| 14.4 | M-AI/OTS-O adaptation ..... | 39 | +| 15 | Management capabilities ..... | 39 | +| 15.1 | Media entity relationships ..... | 39 | +| 15.2 | Fault management ..... | 40 | +| 15.3 | Configuration management ..... | 41 | +| 15.4 | Performance management ..... | 41 | +| 15.5 | Non-associated overhead..... | 41 | +| 16 | Media network survivability techniques..... | 41 | +| 17 | Black link approach ..... | 42 | +| Annex A | – Media change and physical domain change ..... | 44 | +| Annex B | – Concept of network media channel group (NMCG) ..... | 45 | +| Annex C | – Optical Parameter Monitor – power (OPM-pwr) ..... | 46 | +| Appendix I | – Examples of the configuration of media channels..... | 50 | +| I.1 | Construction of network media channels ..... | 50 | +| I.2 | Use of configurable filters to route media channels..... | 50 | +| Appendix II | – Example of media network using tuneable transmitter/receiver for routing .... | 52 | +| II.1 | Network using coupler-splitters ..... | 52 | +| II.2 | Network using wide-band filters and coupler-splitters ..... | 52 | +| Appendix III | – Examples for transferring digital data over different media ..... | 53 | +| III.1 | Specific kinds of modulation/demodulation..... | 53 | +| III.2 | Digitized IF-band case..... | 53 | +| III.3 | Digitized I/Q baseband case ..... | 54 | +| III.4 | Analogue RoF case..... | 54 | +| Appendix IV | – Example for describing media network topology ..... | 56 | +| Appendix V | – Assessing media architecture with PON use cases ..... | 57 | +| V.1 | PON signal in an ODN ..... | 57 | +| V.2 | NG-PON2 ..... | 58 | +| Appendix VI | – Assessing media architecture with the visible light communication use case ..... | 60 | +| Appendix VII | – OMS/OTS reference points and reference points in other Recommendations ..... | 62 | +| Appendix VIII | – Description of inverse multiplexed clients..... | 63 | +| Appendix IX | – Media channel configuration and spectrum optimization..... | 64 | +| Appendix X | – Examples of grid systems defined in other Recommendations..... | 67 | +| Bibliography | ..... | 69 | + +# Generic functional architecture of the optical media layer + +# 1 Scope + +This Recommendation describes the generic functional architecture of the optical media layer from the viewpoint of the propagation of optical signals and the non-associated digital overhead, in the context of a transport network, from a sender at one location to a receiver at another location. The generic functional architecture also includes the description of monitoring of signals propagating in the media network, the encoding of client digital information streams i.e., the client characteristic information (CI), and the modulation onto signals and demodulation of signals to extract the client CI. + +This Recommendation provides a set of constructs (definitions and diagrammatic symbols) and the semantics that can be used to describe such a viewpoint. The modelling methodology described in [ITU-T G.800] is used with the extensions necessary to describe the optical media layer. + +This Recommendation describes the generic functional architecture of the optical media layer in a way that is independent of both the client CI that is transferred and the optical technology (e.g., modulation technique) used to perform the transfer. + +# 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.663] Recommendation ITU-T G.663 (2011), *Application-related aspects of optical amplifier devices and subsystems*. +- [ITU-T G.665] Recommendation ITU-T G.665 (2005), *Generic characteristics of Raman amplifiers and Raman amplified subsystems*. +- [ITU-T G.671] Recommendation ITU-T G.671 (2019), *Transmission characteristics of optical components and subsystems*. +- [ITU-T G.680] Recommendation ITU-T G.680 (2007), *Physical transfer functions of optical network elements*. +- [ITU-T G.694.1] Recommendation ITU-T G.694.1 (2020), *Spectral grids for WDM applications: DWDM frequency grid*. +- [ITU-T G.694.2] Recommendation ITU-T G.694.2 (2003), *Spectral grids for WDM applications: CWDM wavelength grid*. +- [ITU-T G.697] Recommendation ITU-T G.697 (2016), *Optical monitoring for dense wavelength division multiplexing systems*. +- [ITU-T G.698.1] Recommendation ITU-T G.698.1 (2023), *Multichannel DWDM applications with single-channel optical interfaces*. + +- [ITU-T G.698.2] Recommendation ITU-T G.698.2 (2018), *Amplified multichannel dense wavelength division multiplexing applications with single channel optical interfaces.* +- [ITU-T G.698.4] Recommendation ITU-T G.698.4 (2023), *Multichannel bi-directional DWDM applications with port agnostic single-channel optical interfaces.* +- [ITU-T G.800] Recommendation ITU-T G.800 (2016), *Unified functional architecture of transport networks.* +- [ITU-T G.805] Recommendation ITU-T G.805 (2000), *Generic functional architecture of transport networks.* +- [ITU-T G.872] Recommendation ITU-T G.872 (2024), *Architecture of the optical transport networks.* +- [ITU-T G.873.1] Recommendation ITU-T G.873.1 (2017), *Optical transport network: Linear protection.* +- [ITU-T G.959.1] Recommendation ITU-T G.959.1 (2024), *Optical transport network physical layer interfaces.* +- [ITU-T G.7712] Recommendation ITU-T G.7712/Y.1703 (2019), *Architecture and specification of data communication network.* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **adaptation:** See [ITU-T G.805]. +- 3.1.2 **adapted information:** See [ITU-T G.805]. +- 3.1.3 **characteristic information:** See [ITU-T G.805]. +- 3.1.4 **connection:** See [ITU-T G.805]. +- 3.1.5 **connection supervision:** See [ITU-T G.805]. +- 3.1.6 **forwarding end point:** See [ITU-T G.800]. +- 3.1.7 **forwarding point:** See [ITU-T G.800]. +- 3.1.8 **frequency slot:** See [ITU-T G.694.1]. +- 3.1.9 **layer network:** See [ITU-T G.805]. +- 3.1.10 **network connection:** See [ITU-T G.805]. +- 3.1.11 **optical tributary signal (OTSi):** See [ITU-T G.959.1]. +- 3.1.12 **optical tributary sub carrier signal (OTScSi):** See [ITU-T G.959.1]. +- 3.1.13 **receiver optical tributary signal (R-OTSi):** See [ITU-T G.959.1]. +- 3.1.14 **slot width:** See [ITU-T G.694.1]. +- 3.1.15 **topological component:** See [ITU-T G.805]. +- 3.1.16 **trail:** See [ITU-T G.805]. + +- 3.1.17 **transitional link:** See [ITU-T G.800]. +- 3.1.18 **transmitter optical tributary signal (T-OTSi):** See [ITU-T G.959.1]. +- 3.1.19 **transport entity:** See [ITU-T G.800]. +- 3.1.20 **transport processing function:** See [ITU-T G.805]. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +- 3.2.1 **effective frequency slot:** The effective frequency slot of a media channel is the frequency range that is common to the frequency slots of the filter functions present in the media channel. It is described by its nominal central frequency and its slot width. +- 3.2.2 **media channel:** A media association that represents both the topology (i.e., the path through the media) and the resource (i.e., frequency slot or effective frequency slot) that it occupies. A media channel supports zero or more OTSi. +- 3.2.3 **media channel assembly (MCA):** A media channel group (MCG) and its non-associated overhead. +- 3.2.4 **media channel group (MCG):** A unidirectional point-to-point management/control abstraction that represents a set of one or more media channels that are co-routed. A media channel group (MCG) is bounded by a pair of media ports. +- 3.2.5 **media subnetwork:** A media subnetwork is a topological construct that allows flexible creation or deletion of the associations (media channels) between its ports. +- 3.2.6 **media layer access point (M-AP):** A "reference point" at the boundary of the media layer that represents the binding between the transmitter/receiver and adaptation functions. +- 3.2.7 **media layer adapted information (M-AI):** The digital information stream which is transferred across the media layer. +- 3.2.8 **network media channel (NMC):** A network media channel (NMC) is a type of media channel that results from the serial concatenation of all the media channels between the media port of a transmitter and the media ports on one or more receivers, or the media port on a receiver and the media ports on one or more transmitters. An NMC supports zero or one OTSi. + +NOTE – An NMC supports a single unidirectional OTSi and an OTSi is supported by a single NMC. + +- 3.2.9 **optical parameter monitor-x (OPM-x):** A function that monitors a specific optical parameter (e.g., optical power) of the signals present in a media channel. To identify a specific parameter "x" is replaced by a unique string. +- 3.2.10 **OSC:** The OSC supports the transfer of the non-associated overhead information for the OTSiA, OMS OSME and the OTS OSME. +- 3.2.11 **optical tributary signal assembly (OTSiA):** The optical tributary signal group (OTSiG) together with the non-associated optical tributary signal group overhead (OTSiG-O). +- 3.2.12 **optical tributary signal group (OTSiG):** The set of optical tributary signals (OTSi) that supports a single digital client. + +NOTE – As described in clause 10.1.1, an OTSi may also support a message channel as defined in [ITU-T G.698.4]. + +- 3.2.13 **optical tributary signal group overhead (OTSiG-O):** The non-associated overhead for an OTSiG. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------------------|----------------------------------------------------------------------| +| A/D | Analogue to Digital | +| AI | Adapted Information | +| ASON | Automatically Switched Optical Network | +| BIP | Bit Interleaved Parity | +| B-PON | Broadband Passive Optical Network | +| CI | Characteristic Information | +| CWDM | Coarse Wavelength Division Multiplexing | +| D/A | Digital to Analogue | +| DAC | D/A Converter | +| DCC | Data Communications Channel | +| DWDM | Dense Wavelength Division Multiplexing | +| EMP | External Monitoring Point | +| FEC | Forward Error Correction | +| FP | Forwarding Point | +| FwEP | Forwarding end point | +| G-PON | Gigabit-capable Passive Optical Network | +| I/Q | In-phase and Quadrature-phase | +| LOS | Loss of Signal | +| M-AI | Media layer Adapted Information | +| M-AP | Media layer Access Point | +| MCA | Media Channel Assembly | +| MCG | Media Channel Group | +| MI | Management Information | +| MPI-R M | Main Path Interface – Multichannel reference point at the ONE input | +| MPI-S M | Main Path Interface – Multichannel reference point at the ONE output | +| MSI | Multiplex Structure Identifier | +| NG-PON | Next Generation Passive Optical Network | +| NMC | Network Media Channel | +| NMCG | Network Media Channel Group | +| OAM | Operation, Administration and Maintenance | +| OCC | Overhead Communications Channel | +| OCN | Overhead Communications Network | +| ODN | Optical Distribution Network | +| OMS | Optical Multiplex Section | + +| | | +|---------|---------------------------------------------| +| OMS-O | OMS Overhead | +| OPM-pwr | Optical Parameter Monitor – power | +| OPM-x | Optical Parameter Monitor | +| OSME | Optical Signal Maintenance Entity | +| OSNR | Optical Signal-to-Noise Ratio | +| OTN | Optical Transport Network | +| OTS | Optical Transmission Section | +| OTScSi | Optical Tributary Sub Carrier Signal(s) | +| OTScSiG | Optical Tributary Sub Carrier Signal Group | +| OTSi | Optical Tributary Signal(s) | +| OTSiA | Optical Tributary Signal Assembly | +| OTSiG | Optical Tributary Signal Group | +| OTSiG-O | Optical Tributary Signal Group Overhead | +| OTS-O | OTS Overhead | +| RF | Radio Frequency | +| ROADM | Reconfigurable Optical Add/Drop Multiplexer | +| RoF | Radio-over-Fibre | +| R-OTSi | Receiver OTSi | +| SDN | Software Defined Network | +| SMC | Synchronization Message Channel | +| T-OTSi | Transmitter OTSi | +| TTI | Trail Trace Identifier | +| VLC | Visible Light Communication | + +# 5 Conventions + +This Recommendation uses the diagrammatic conventions defined in [ITU-T G.800] and [ITU-T G.805], supplemented by the additional conventions described in this clause, to encompass optical signal and media-related aspects. + +## 5.1 Notational conventions + +The suffix –O is used to identify the non-associated overhead that corresponds to a group of optical signals, for example optical tributary signal group overhead (OTSiG-O) or optical multiplex section overhead (OMS-O). + +The transmitter is a signal source (called a "sender" in clause 1) and the receiver is a sink (called a "receiver" in clause 1). The term transmitter/receiver is used to describe a bidirectional function that consists of a pair of collocated transmitter and receiver functions. The transmitter described in this Recommendation includes both a light source that provides an optical signal and the ability to modulate that optical signal. + +## 5.2 Diagrammatic conventions + +Since some media constructs are similar to the functions performed by the topological components and transport processing functions used to describe the digital layers, it is convenient to reuse some of the diagrammatic conventions from [ITU-T G.800] and [ITU-T G.805]. Shading is added to distinguish media constructs from the topological components and transport processing functions for digital layers. The location of the media layer access point (M-AP) and the media layer access group are shown in Figure 5-1. + +Additional diagrammatic conventions are introduced to show signals, media without signals, media with signals and to differentiate between guided and unguided media. + +![Diagram showing a vertical stack of media network components: ITU-T G.800 FP or FwEP (circle), M-AI/client CI application (trapezoid), M-AP (square), Transmitter/receiver (shaded pentagon, T/R), and Media port (shaded diamond). Below this, a horizontal line shows three Transmitter/receiver (T/R) units connected by guided media (double lines). The rightmost T/R unit is connected to a Media layer access group (shaded circle). The label G.807(24) is present.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +| Digital layer network | Media network | +|-------------------------------------------------|--------------------------------------------------------------| +| Subnetwork (white oval) | Media subnetwork (shaded oval) | +| Trail termination function (white triangle) | Optical signal transmitter/receiver (shaded pentagon, T/R) | +| Non intrusive monitor function (white triangle) | Optical parameter monitor (shaded pentagon, P) | +| Adaptation (white trapezoid) | Adaptation (to media layer) (white trapezoid) | +| Layer processor function (white pentagon) | Filter (shaded pentagon, F) | +| Traffic conditioning function (white diamond) | Coupler-splitter (shaded pentagon, C) | +| Information transfer (ITU-T G.800) (white line) | Signal monitor (shaded pentagon, m) | +| | Amplifier (shaded diamond) | +| | Analog signal function (shaded hexagon) | +| | Frequency mixer (shaded circle with X) | +| | Guided media (double line) | +| | Signal carried in guided media (double line with signal) | +| | Free space media (dashed line) | +| | Signal carried in free space media (dashed line with signal) | + + + +Diagram showing a vertical stack of media network components: ITU-T G.800 FP or FwEP (circle), M-AI/client CI application (trapezoid), M-AP (square), Transmitter/receiver (shaded pentagon, T/R), and Media port (shaded diamond). Below this, a horizontal line shows three Transmitter/receiver (T/R) units connected by guided media (double lines). The rightmost T/R unit is connected to a Media layer access group (shaded circle). The label G.807(24) is present. + +Figure 5-1 – Diagrammatic conventions + +The term "media port" and the + +Image: shaded diamond symbol + + symbol are used to describe both an unbound port and a pair of bound ports. The media port symbol + +Image: shaded diamond symbol + + is used: + +- To indicate a media port on a media construct that does not have media attached; +- When a media port is attached to a media construct and it serves as a media reference point; +- To indicate the media port on functions that provide the transition between the digital information domain and a signal domain. + +In all other cases, a media port exists, but the media port symbol is not used. + +The term "media access point" and the ■ symbol represent the binding between the transmitter/receiver and adaptation functions. + +A shaded symbol ![shaded pentagon symbol](f4f9ac412efd7fead6377a2b0ae12137_img.jpg) is used in this Recommendation to represent functions that provide the transition between the digital information domain (M-AP at the top of the symbol) and a signal domain (media port at the bottom of the symbol). The label identifies the type of function. + +The symbol ![hexagon symbol](c3cffc168beb4396c1e1a5a6db5d66b0_img.jpg) is used to represent a function that performs an analogue signal function, having only signal inputs and outputs. It is not used to represent amplifiers, coupler-splitters/filters, frequency mixers, or the combination of functions within a media subnetwork. + +The symbol ![crossed circle symbol](ad6ab0b77b86612fcbfecc8e2418b31e_img.jpg) is used to represent a frequency mixer and reuses the commonly used circuit symbol for that signal multiplication function. + +The common port of a filter, coupler-splitter or signal monitor is at the point of the pentagram. + +## 5.3 Terminological conventions + +The following terminological conventions are used to distinguish between connections in the digital layers and media associations. + +The term *Connection* is used in the context of a transport entity, as defined in [ITU-T G.800] and [ITU-T G.805]. + +The term *Association* is used to describe the following relationships: + +- Between the media ports on a media element; +- Between the media ports on a media construct; +- Between a media port on a network media channel (NMC) and one or more media ports on a transmitter; or +- Between a media port on an NMC and one or more media ports on a receiver. + +## 5.4 Media layer and media network + +Media layer adapted information (M-AI) is transferred by the media layer. The media layer consists of a set of media layer access groups and the media network that supports the propagation of optical signals. This is illustrated in Figure 6-1. + +# 6 Overview of media and signal + +## 6.1 General introduction of media and signal + +In [ITU-T G.800] and its predecessors, only the transfer of information is modelled. Neither the modulation of the information onto a signal for propagation over a media nor the demodulation of the signal to recover the information are modelled. It means that the nomenclature of information transfer does not depict the nature of the signal in which the information is carried, nor the media through which the signal propagates. Therefore, new nomenclature to depict the nature of signal and media is defined in clause 5. The use of the nomenclature is illustrated in Appendices I, II, III, V and VI. + +In this Recommendation, the term optical tributary signals (OTSi), as defined in [ITU-T G.959.1], is used to identify each of the optical signals carried in the media. + +Media that can support propagation of OTSi include glass and free space. The diagrammatic conventions for these, shown in Figure 5-1, are the symbols "guided media" and "free space". + +## 6.2 Functional architecture of the optical media layer + +The functionality of the optical media layer is described by a set of constructs that support and constrain the propagation of OTSi. This includes constructs that are wavelength selective (e.g., filter functions). The structure of an optical media layer is provided in Figure 6-1 and Figure 6-2. + +![Figure 6-1: Overview of optical media layer. The diagram shows three transceiver symbols (T/R) on the left, with the first two connected by a dashed line and the third connected to a circle labeled 'Media layer access group'. To the right, a large rectangle labeled 'Media layer bounded by media access groups' contains a central oval labeled 'Largest media subnetwork' connected to four corner circles. An arrow labeled 'Media network' points to the central oval. The text 'G.807(24)' is at the bottom right.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +Figure 6-1: Overview of optical media layer. The diagram shows three transceiver symbols (T/R) on the left, with the first two connected by a dashed line and the third connected to a circle labeled 'Media layer access group'. To the right, a large rectangle labeled 'Media layer bounded by media access groups' contains a central oval labeled 'Largest media subnetwork' connected to four corner circles. An arrow labeled 'Media network' points to the central oval. The text 'G.807(24)' is at the bottom right. + +Figure 6-1 – Overview of optical media layer + +![](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +| | | | +|---------------------------------------------------------------------------------------------------------|-----------------------|---------------------| +| Digital clients of the optical media layer
(with technology-specific formats) | | | +| OTSiA | Optical signals | Optical media layer | +| Media constructs,
OMS/OTS optical signal maintenance entities
non-associated overhead information | Optical media network | | + +Figure 6-2 – Structure of the optical media layer + +The information of digital clients is carried across the media layer by an optical tributary signal (OTSi), described in clause 10. The transmitting and receiving of an OTSi are performed by transmitters and receivers, respectively, and are depicted by the symbol shown in Figure 5-1. The media network is described using the media constructs, listed in clause 7-1. + +Each OTSi is guided between its source(s) (one or more transmitters) and its destination(s) (one or more receivers) by an independent NMC. An NMC is formed by a serial concatenation of one or more media channels. An NMC may not be capable of supporting a particular OTSi, see clause 6.2.3. + +In some cases, configuration of media channels, transmitters and receivers may not be supported. Examples of non-configurable applications include those specified in [ITU-T G.959.1], where frequency slots and transmitter central frequencies are fixed. + +Operation, administration and maintenance (OAM) for the media layer is provided by using the monitoring constructs described in clause 8 and the use of non-associated overhead described in clause 11.1. Management capabilities are described in clause 15. + +The following terms are used in the description of the media layer and the OTSi. + +### 6.2.1 Frequency slot + +A frequency slot is the contiguous frequency range, defined by a nominal central frequency and a slot width, allocated to a slot and unavailable to any other slot. The only media construct that enforces a frequency slot is the filter function (described in clause 7.1.6). The frequency slot is the frequency range within which a filter function is implemented. Therefore, the passband of a filter is narrower than its frequency slot. The relationship between the frequency slot and the passband of a filter function, that enforces the frequency slot, is outside the scope of this Recommendation. + +To provide a consistent description, within this Recommendation all filter functions are described in terms of the frequency slot. + +NOTE 1 – In some cases, it may be more convenient to describe a frequency slot by the upper frequency and lower frequency of the contiguous frequency range allocated to that frequency slot. The difference between the upper and lower frequencies is the slot width. + +NOTE 2 – In some cases, a frequency grid with fixed channel spacing is defined. In this case the slot width is equal to the grid spacing. + +NOTE 3 – In other cases (e.g., for coarse wavelength division multiplexing (CWDM) applications) the frequency grid may be defined in terms of wavelength. + +Wavelength can be converted to frequency using formula $f = c/\lambda$ : + +$c$ (speed of light in vacuum) = $2.99792458 \times 10^8$ m/s. + +$\lambda$ = wavelength in m, + +$f$ = frequency in Hz. + +Examples of the frequency grids defined for use in the transport network are provided in [ITU-T G.694.1] for dense wavelength division multiplexing (DWDM) applications and [ITU-T G.694.2] for coarse wavelength division multiplexing (CWDM) applications. + +Examples of other grid systems are provided in Appendix X. + +A media channel may be a serial concatenation of one or more media channels, each with its own frequency slot (see clause 7.1.2). The effective frequency slot of a media channel is the contiguous frequency range that is common in the frequency slots of the media channels that are serially concatenated to form the longer media channel. + +The relationship between the effective frequency slot and the passband of the serial concatenation of the filters that form a media channel is outside the scope of this Recommendation. + +### 6.2.2 Transfer parameters + +Each media channel has transfer parameters which may include, for example, optical noise, non-linear impairments, latency, and the passband of the serial concatenation of the filters that form the media channel. + +The definition of transfer parameters is outside the scope of this Recommendation. + +### 6.2.3 Application identifier + +An application identifier is used to confirm the compatibility between a nNMC and the OTSi that it is intended to carry. The application identifier provides parameters for the transmitter(s), NMC and receiver(s). If present, each OTScSi within an OTSi may have a distinct application identifier. An application identifier includes the application codes defined in the appropriate optical system Recommendations (e.g., [ITU-T G.698.2]), as well as the possibility of proprietary identifiers. + +The parameters included in the application identifier for an NMC take into account the concatenation of the passband of the filter function and the transfer parameters of each of the media channels that are serially concatenated to form the NMC. + +The parameters included in the application identifier for the transmitter and receiver define all relevant aspects of the signal, including, for example, the characteristics of the OTSi at the media port on the transmitter and receiver, forward error correction (FEC), baud rate, and modulation type. + +The following aspects are outside the scope of this Recommendation: + +- The passband of the serial concatenation of the filters that form an NMC; +- The concatenation of the transfer parameters of the media channels that are serially concatenated to form the NMC; +- The definition of the parameters for a transmitter and receiver. + +# 7 Media constructs and media elements + +The media network is described using media constructs (see clause 7.1) to represent the different functions present in the media network. Media constructs operate on the signal envelope (see [b-IEC 60050 envelope]) (e.g., amplify or attenuate the signal power, constrain or direct the signal propagating through media channel, etc.) and are not aware of the client digital information being carried. Media constructs do not demodulate the signal and, therefore, do not process the client digital information that is carried by the signal. This architectural description is not intended to imply any particular implementation. The functions present at the boundary of a layer network, as defined in [ITU-T G.800], and the media network are described in clause 9. + +For the purposes of management and control, the media network is represented by a set of media constructs or media elements (see clause 7.2). A media element encompasses the functionality of one or more of the media constructs. + +## 7.1 Media constructs + +The following architectural media constructs are used to describe the architecture of the media layer: + +- Media port; +- Media channel; +- Media channel group (MCG); +- media channel assembly (MCA); +- Media subnetwork; +- Filter; +- Coupler-splitter +- Signal monitor +- Frequency mixer; +- Analogue signal conversion function; +- Optical amplifier; +- Fibre; +- Optical parameter monitor (OPM-x) described in clause 9.1; +- Optical signal maintenance entity (OSME) described in clause 9.2. + +### 7.1.1 Media port + +A media port is an abstraction that represents the location where a signal can enter or leave: + +- Media channel; +- Media construct; +- Media boundary function; +- Media element. + +NOTE – the constructs listed above have one or more media ports. + +A media port on a media channel may be bound to a media port on; + +- Another media channel; +- A media construct; +- A media boundary function; +- A media element. + +No other bindings are supported. + +A media port that is on the boundary of a media construct, media boundary function, or media element may also represent the location of a signal reference point as defined in this Recommendation or other Recommendations, for example [ITU-T G.680] or [ITU-T G.698.1]. + +A media port on the boundary of a media construct or a media element may encompass the media port(s) on one end of zero or more (internal) atomic media channels. + +### 7.1.2 Media channel + +The media channel represents both the topology (i.e., the path through the media) and the resource (i.e., frequency slot or effective frequency slot) that it occupies. A media channel is bounded by its ports. A media channel guides zero or more OTSi between its ports. A media channel may be formed by a serial concatenation of multiple media channels, each with its own frequency slot. A media channel that cannot be decomposed into a concatenation of other media channels is known as an atomic media channel. The media channels that exist within other media constructs (e.g., a filter, coupler-splitter, optical amplifier, or fibre) are examples of atomic media channels. Figure 7-1 provides some examples of the serial concatenation of media channels to form a longer media channel. + +![Diagram illustrating the serial concatenation of media channels. It shows a network media channel formed by a serial concatenation of media channels (A, B, C, D, E, F, G, H, I, J, K). The diagram includes OTSi #1 and OTSi #2 at the ends, connected via media ports (T and R). The network media channel is shown as a dashed blue line, and the media channel formed by a serial concatenation of media channels is shown as a solid blue line. The media channels are labeled A, B, C, D, E, F, G, H, I, J, K. The diagram also includes the text 'G.807(24)'.](29f586959675cafdf81cf934954908eb_img.jpg) + +The diagram illustrates the serial concatenation of media channels. On the left, two transceivers labeled 'OTSi #1' and 'OTSi #2' are connected to 'Media port' units labeled 'T'. On the right, two receivers labeled 'OTSi #2' and 'OTSi #1' are connected to 'Media port' units labeled 'R'. A dashed blue line labeled 'Network media channel formed by a serial concatenation of media channels' spans from the left 'T' port to the right 'R' port. A solid blue line labeled 'Media channel formed by a serial concatenation of media channels' follows a similar path. The central part of the diagram shows a series of media elements: a stack of four channels (A, B, C, D) on the left, followed by element 'E', then element 'F', then element 'G', and finally a stack of three channels (H, I, J) on the right. Element 'K' is shown as a separate component below element 'F'. Red arrows point from the text 'Media channel' to elements 'D', 'E', 'F', 'G', and 'K'. The text 'G.807(24)' is located in the bottom right corner. + +Diagram illustrating the serial concatenation of media channels. It shows a network media channel formed by a serial concatenation of media channels (A, B, C, D, E, F, G, H, I, J, K). The diagram includes OTSi #1 and OTSi #2 at the ends, connected via media ports (T and R). The network media channel is shown as a dashed blue line, and the media channel formed by a serial concatenation of media channels is shown as a solid blue line. The media channels are labeled A, B, C, D, E, F, G, H, I, J, K. The diagram also includes the text 'G.807(24)'. + +**Figure 7-1 – Serial concatenation of media channels** + +For example, in Figure 7-1 a media channel is formed by the serial concatenation of media channels C+E+F+G+J or E+F+G. A media channel has no internal structure, i.e., the examples of "narrower" + +and "wider" media channels illustrated in Figure 7-1 simply reflect their respective "narrower" and "wider" frequency slots and should not be interpreted as illustrating a containment relationship of the media channels. No hierarchy is created in either the media channels or the signals carried. + +The size of a media channel is specified by its frequency slot described in clause 6.2.1. + +The relationship between OTSi, media channels and media ports on other media constructs is shown in Figure 7-2. + +![Figure 7-2: Relationship between signals and media channels. The diagram shows two transmitters (T) connected to a media port, which is connected to a media channel (F). The OTSi (in media channels) is shown as a signal spectrum with four peaks. The optical spectrum is shown as a horizontal line with four peaks. The media channels are described by frequency slots of 50 GHz, 100 GHz, and 75 GHz. The diagram is labeled G.807(24).](4356776ca004ecba5d599667a155d7d4_img.jpg) + +The diagram illustrates the relationship between signals and media channels. On the left, two transmitters (T) are connected to a media port, which is connected to a media channel (F). The OTSi (in media channels) is shown as a signal spectrum with four peaks. The optical spectrum is shown as a horizontal line with four peaks. The media channels are described by frequency slots of 50 GHz, 100 GHz, and 75 GHz. The diagram is labeled G.807(24). + +Figure 7-2: Relationship between signals and media channels. The diagram shows two transmitters (T) connected to a media port, which is connected to a media channel (F). The OTSi (in media channels) is shown as a signal spectrum with four peaks. The optical spectrum is shown as a horizontal line with four peaks. The media channels are described by frequency slots of 50 GHz, 100 GHz, and 75 GHz. The diagram is labeled G.807(24). + +**Figure 7-2 – Relationship between signals and media channels** + +A media channel may be dimensioned to carry more than one OTSi. It may be possible to configure a media channel before it has been decided which OTSi will be allocated to it. However, a media channel may not be capable of supporting the transfer of a particular OTSi. + +Transition between different types of media is described in Annex A. + +#### 7.1.2.1 Network media channel (NMC) + +An NMC is a type of media channel that is formed by the serial concatenation of all media channels between the media port of a transmitter and the media ports on one or more receivers, or between the media port on a receiver and the media ports on one or more transmitters. The NMC is the media equivalent of the G.800 network connection that supports a single instance of the layer CI. An NMC: + +- Supports zero or one unidirectional OTSi; +- Must be present to allow the OTSi to be propagated from the transmitter(s) to the receiver(s); +- Cannot be divided into smaller media channels (with a narrower slot width); +- Cannot be concatenated with another media channel. + +Zero OTSi on the NMC corresponds to the condition when transmitter(s) are not active. + +Figure 7-1 shows, as an example, the NMC for OTSi #2 which results from the serial concatenation of media channels A+E+F+G+H. + +Two (or more) NMCs can use the same (wider) media channel as a part of the serial concatenation that forms the NMC. For example, in Figure 7-1 the NMC for OTSi #1 (B+E+F+G+I) and the NMC for OTSi #2 (A+E+F+G+H) share the media channels E+F+G. + +### 7.1.3 Media channel group + +A media channel group (MCG) is a unidirectional point-to-point management/control abstraction that represents a set of one or more media channels that are co-routed. An MCG is bounded by a pair of media ports. The constituent media channels may be atomic media channels or the serial concatenation of multiple media channels. The constituent media channels are not necessarily in a single contiguous block of the optical spectrum. A bidirectional MCG is formed by a pair of (contra directional) MCGs. + +### 7.1.4 Media channel assembly + +A media channel assembly (MCA) is a management /control abstraction that represents an MCG and its non-associated overhead. Two MCAs are described in this Recommendation: Optical multiplex section (OMS) MCA and optical transmission section (OTS) MCA. + +### 7.1.5 Media subnetwork + +The media subnetwork is a topological construct that allows flexible creation or deletion of the associations (represented by media channels) between the media ports. The association between a pair of media ports is provided by a media channel. + +A media subnetwork may be decomposed into smaller media subnetworks interconnected by MCGs. This decomposition may also expose other media constructs such as filters (see clause 7.1.6) or amplifiers (see clause 7.1.11), which are also interconnected by MCGs. In addition, media subnetworks, filters, amplifiers and the MCGs that interconnect them can be aggregated into a larger (containing) media subnetwork. In this case, the details of the contained media subnetworks, filters, amplifiers and MCGs are not visible. This is illustrated in Figure 7-3. For the purposes of management and control a media subnetwork is encompassed by a media element (together with other media constructs see clause 7.2). This represents the limit of decomposition of a media subnetwork. + +![Diagram illustrating the partitioning of media subnetworks. The diagram shows a hierarchical decomposition of a media subnetwork into smaller components. At the top, a single 'Media subnetwork' is shown. Below it, a 'Partition' arrow points to a level labeled 'Media subnetworks + MCGs', which consists of two media subnetworks connected by a double line representing an MCG. Below this, another 'Partition' arrow points to a third level labeled 'Media subnetworks + MCGs', which shows two more media subnetworks connected by a double line. Dashed lines connect the top 'Media subnetwork' to the two subnetworks in the middle level, and the two subnetworks in the middle level to the two subnetworks in the bottom level, illustrating the recursive decomposition process.](12de9b926df0384ec07702671827c9cd_img.jpg) + +G.807(20)\_F7-3 + +Diagram illustrating the partitioning of media subnetworks. The diagram shows a hierarchical decomposition of a media subnetwork into smaller components. At the top, a single 'Media subnetwork' is shown. Below it, a 'Partition' arrow points to a level labeled 'Media subnetworks + MCGs', which consists of two media subnetworks connected by a double line representing an MCG. Below this, another 'Partition' arrow points to a third level labeled 'Media subnetworks + MCGs', which shows two more media subnetworks connected by a double line. Dashed lines connect the top 'Media subnetwork' to the two subnetworks in the middle level, and the two subnetworks in the middle level to the two subnetworks in the bottom level, illustrating the recursive decomposition process. + +Figure 7-3 – Partitioning of media subnetworks + +### 7.1.6 Filter function + +The filter function models the ability to allow only those signals that are in a defined portion of spectrum to be passed from one media port to another media port1. The association between the media ports on a filter function is described by a media channel, which is specified by the media ports that bound it and its frequency slot. A media port on a filter may be associated with zero or more atomic media channels (with non-overlapping frequency slots) within the same filter. The passband of a filter is narrower than its frequency slot. The relationship between the frequency slot and the passband of a filter is outside the scope of this Recommendation. + +It may be possible to configure the frequency slot(s) of a filter functions (via the management/control plane). Within this Recommendation, these are referred to as configurable filter functions. An example of a configurable filter is a device that supports the flexible dense wavelength division multiplexing grid defined in [ITU-T G.694.1]. + +A configurable filter function may be implemented as a part of a coherent receiver optical module, and the characteristics of this filter function must be included when determining the effective frequency slot and the transfer characteristics of the NMC. + +### 7.1.7 Coupler-splitter + +The coupler-splitter provides a set of atomic media channels between one (common) port and two or more other (branch) ports. All of these atomic media channels have the same frequency slot. In the splitting direction, signals present at the common media port are transferred to all of the branch media ports2. In the combining direction, signals present at any of the branch media ports are aggregated and appear at the common media port. The term coupler3-splitter is a synonym for an optical branching component (wavelength non-selective), as defined in [ITU-T G.671]. + +### 7.1.8 Signal monitor + +The signal monitor is a type of splitter, and the signal power division is asymmetric. The signal monitor pair "![signal monitor pair symbol](0fc5900959ab10acc878f9ca1e00fe37_img.jpg) symbol is used in bidirectional diagrams. + +### 7.1.9 Analogue signal functions + +An analogue signal function operates only on analogue signals and only has signal inputs and outputs. These are represented diagrammatically with the hexagon (![hexagon symbol](2e39534fa484c54b999a1fc9c8a46d5a_img.jpg)) symbol. An example of such a function is an analogue optical modulator described in Appendix III. + +### 7.1.10 Frequency Mixer + +The frequency mixer is a type of analogue signal function that multiplies the frequencies of two input signals. This generates two output signals at different frequencies, one at the sum of the input frequencies, and the other at the difference between the input frequencies. The symbol ![cross symbol](1ec9c5991b6cfbe205eacf87caeef44f_img.jpg) is used to show a frequency mixer. + +### 7.1.11 Optical amplifier + +The optical amplifier is a type of analogue signal function that acts on the envelope of the OTSi to increase the optical power level. It is unidirectional and has two media ports with one or more media + +--- + +1 This is often referred to as the passband of the filter. + +2 When a signal is transferred from the common port to the branch port, the signal power is divided across the branches. + +3 [b-ITU-T G.989] uses the term combiner instead of coupler. + +channels between the ports. The power level of any OTSi present at the input port is increased and it is transferred to the output port. The $\diamond$ symbol is used to show an amplifier. + +In a discrete optical amplifier, the amplification effect is contained inside the media construct. In a distributed amplifier, the amplification effect is achieved via a portion of the optical fibre used for transmission. Therefore, one of the media ports of the amplifier will be at some (unspecified) location in the transmission fibre. For the purposes of the architecture the location of a distributed optical amplifier is considered to be the location where the pump wavelength is inserted. Optical amplifiers are described in terms of optical components, devices and subsystems in [ITU-T G.663] and [ITU-T G.665]. + +### 7.1.12 Fibre + +A fibre provides the ability to interconnect other media components. It contains an atomic media channel or a media channel group. Each media channel may have transfer parameters as described in clause 6.2.2. + +## 7.2 Media element + +An instance of a media element encapsulates the functionality represented by one or more of the media constructs described in clauses 7.1 and 9.1 and zero or more OSME reference points described in clause 9.2. The internal structure of a media element is not visible. The capabilities of the media element are described by the media channels within the media element that provide the association between these media ports. A media element cannot encompass another media element. + +An OTSi that is present at a media port may be transferred to zero or more other media ports on that media element. The ability to transfer an OTSi between ports is modelled by one or more atomic media channels: + +- Each pair of media ports that allow signal transfer has one or more atomic media channels with a frequency slot for each atomic media channel. +- Each atomic media channel has zero or more transfer parameters. The transfer parameters may include, for example, the latency and the optical characteristics of the atomic media channel that are defined in other Recommendations, including for example [ITU-T G.663] and [ITU-T G.680]. + +The atomic media channel and signal transfer are modelled independently for each direction of signal propagation. An atomic media channel may not be capable of supporting a particular OTSi, see clause 6.2.3. The definition of the transfer parameters for an atomic media channel is outside the scope of this Recommendation. + +The media subnetwork is a topological construct that represents the associations between the media ports. The media element encompasses one or more media constructs and represents all of the functions of the media constructs that it contains. While a media subnetwork can only describe the ability to propagate the signal from the input media port to the output media port, the media element describes this and also the output of any OPM-x functions that are encompassed. + +For the purposes of management and control, the media network is represented by a set of one or more media constructs and zero or more media elements. + +The media element may be used to represent the optical network element (ONE) described in [ITU-T G.680]. An example of an ONE described in [ITU-T G.680], that may be represented by a media element, is a reconfigurable optical add/drop multiplexer (ROADM), that may be composed of a set of interconnected filters and a media subnetwork, without defining the internal structure or exposing any internal interconnection of the media constructs. + +## 7.3 Media network topology + +This clause describes the topology of optical media network. The media network may provide point-to-point media channels, point-to-multipoint media channels or both. In some cases, e.g., if the topology includes a media subnetwork, it may be possible to configure the topology via the management/control plane. A media channel may support the propagation of a signal in one direction or both directions. A bidirectional OTSi is supported by two NMCs (one for each direction of propagation). + +As described in clause 7.2, a media element contains one or more media constructs and has n ports. Each pair of ports that allows signal transfer has one or more atomic media channels, with a frequency slot. Each media channel has zero or more transfer parameters. + +As described in clause 6.2, the OTSi is characterized by its central frequency and an application identifier. If multiple optical tributary sub carrier signals (OTScSi) are present in the OTSi, each has its own application identifier. The OTSi is guided to its destination by an NMC. + +The topology of the media network is first expressed in a simple graph, where media subnetworks are represented by vertices and the MCGs that interconnect them are represented by edges. The parameters of the MCGs (frequency slot and any relevant transfer parameters) are attached to the graph as edge semantics and domains of the graph having identical edge semantics are formed. + +An example for describing topology is provided in Appendix IV. + +### 7.3.1 Point to point network media channels + +An OTSi is by definition unidirectional. Bidirectional communication between two points is accomplished via a pair of OTSi, with each OTSi occupying a separate NMC. The NMCs through which a pair of OTSi that support bidirectional communication travel may be within the same media constructs (in which case the two OTSi typically use different frequency slots) or may be within different media constructs (in which case the two OTSi may use the same frequency slots, although this is not required). + +### 7.3.2 Point-to-multipoint network media channel + +A point-to-multipoint network media channel is used to broadcast a transmitter OTSi (T-OTSi) from one transmitter to a number of receivers. This is illustrated in Figure 7-4 where a point-to-multipoint association is provided in the media by means of a splitter. This represents the root of a multipoint media channel. Another example is provided in Appendix II. + +![Diagram of a point-to-multipoint network media channel (NMC). A transmitter (T) connected to a media port sends a signal to a splitter (S). The splitter branches the signal into three parallel paths, each containing a media element (F). These paths then converge and lead to three separate receivers (R). A legend indicates that 'T' stands for Transmitter and 'R' stands for Receiver. The diagram is labeled G.807(24) in the bottom right corner.](04dc3838022e96d8d5548bb1b777b38c_img.jpg) + +The diagram illustrates a point-to-multipoint network media channel. On the left, a transmitter (T) is connected to a 'Media port'. A signal from the transmitter enters a splitter (S). The splitter divides the signal into three parallel horizontal paths. Each path contains a media element represented by a trapezoidal shape labeled 'F'. After passing through these elements, the three paths converge into a single horizontal line. This line then branches out to three separate receivers (R) on the right. Each receiver is connected to one of the three parallel paths via another trapezoidal media element labeled 'F'. A legend at the bottom left shows a 'T' in a pentagon labeled 'Transmitter' and an 'R' in a pentagon labeled 'Receiver'. The diagram is labeled 'G.807(24)' in the bottom right corner. + +Diagram of a point-to-multipoint network media channel (NMC). A transmitter (T) connected to a media port sends a signal to a splitter (S). The splitter branches the signal into three parallel paths, each containing a media element (F). These paths then converge and lead to three separate receivers (R). A legend indicates that 'T' stands for Transmitter and 'R' stands for Receiver. The diagram is labeled G.807(24) in the bottom right corner. + +Figure 7-4 – Point-to-multipoint NMC + +### 7.3.3 OTS and OMS MCGs + +The OTS MCG and OMS MCG are topological constructs that are used for management control purposes. + +The OTS MCG represents the topological relationship between: + +- The output media port of one amplifier and the input media port of the next amplifier. For distributed optical amplifiers, described in [ITU-T G.665], the input media port or output media port of the amplifier may not be accessible. In this case the OTS MCG is considered to start or terminate at the location where the pump wavelength is inserted. +- Non-associated overhead (OTS-O) may be provided for the OTS MCG, the combination of the OTS MCG and OTS-O are referred to as the OTS MCA. The OTS-O is described in clause 15. + +The OMS MCG represents: + +- The topological relationship between the media port on a filter or coupler where a set of media channels are aggregated and the media port on a filter or splitter where one or more media channel is added to or removed from that aggregate. All of the media channels that are represented by the OMS MCG must be carried over the same serial concatenation of OTS MCGs and amplifiers. +- Non-associated overhead (OMS-O) may be provided for the OMS MCG, the combination of the OMS MCG and OMS-O are referred to as the OMS MCA. The OMS-O is described in clause 15. + +The composition of the OTS and OMS MCGs when discrete remote optical amplifiers are deployed is shown in Figure 7-5. + +![Diagram illustrating OTS and OMS MCGs with discrete remote optical amplifiers. The diagram shows two horizontal paths. The top path consists of three diamond-shaped nodes connected by double lines. The first segment is labeled 'OTS MCG' and the second segment is also labeled 'OTS MCG'. The bottom path consists of two pentagonal nodes (representing amplifiers) connected by double lines, with a diamond-shaped node between them. This segment is labeled 'OMS MCG'. Vertical double lines connect the pentagonal nodes to the diamond-shaped nodes. A legend at the bottom left shows a diamond shape labeled 'Media port'. A label 'G.807(24)' is at the bottom right.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +Diagram illustrating OTS and OMS MCGs with discrete remote optical amplifiers. The diagram shows two horizontal paths. The top path consists of three diamond-shaped nodes connected by double lines. The first segment is labeled 'OTS MCG' and the second segment is also labeled 'OTS MCG'. The bottom path consists of two pentagonal nodes (representing amplifiers) connected by double lines, with a diamond-shaped node between them. This segment is labeled 'OMS MCG'. Vertical double lines connect the pentagonal nodes to the diamond-shaped nodes. A legend at the bottom left shows a diamond shape labeled 'Media port'. A label 'G.807(24)' is at the bottom right. + +**Figure 7-5 – OTS and OMS MCGs with discrete remote optical amplifiers** + +The case where remote amplifiers are not deployed is shown in Figure 7-6 with both discrete and distributed amplifiers deployed at the sites where the OMS MCG terminates. + +![Figure 7-6: OTS and OMS MCGs without a remote amplifier. The diagram shows two identical network configurations. Each configuration consists of two pentagonal nodes at the top connected by two horizontal lines labeled 'OMS MCG' and 'OTS MCG'. Below these nodes are two diamond-shaped nodes. A blue line connects the two diamond nodes. At the bottom, there are two rectangular 'Media element' boxes. Each pentagonal node is connected to a diamond node, which is in turn connected to a 'Media element' box. A blue line labeled 'Pump wavelength insertion' connects the two 'Media element' boxes. The text 'G.807(20)-Amd.1(21)_F7-6' is at the bottom right.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +Figure 7-6: OTS and OMS MCGs without a remote amplifier. The diagram shows two identical network configurations. Each configuration consists of two pentagonal nodes at the top connected by two horizontal lines labeled 'OMS MCG' and 'OTS MCG'. Below these nodes are two diamond-shaped nodes. A blue line connects the two diamond nodes. At the bottom, there are two rectangular 'Media element' boxes. Each pentagonal node is connected to a diamond node, which is in turn connected to a 'Media element' box. A blue line labeled 'Pump wavelength insertion' connects the two 'Media element' boxes. The text 'G.807(20)-Amd.1(21)\_F7-6' is at the bottom right. + +**Figure 7-6 – OTS and OMS MCGs without a remote amplifier** + +In the case that an amplifier is not deployed at one end of the OMS MCG, the OTS MCG represents the topological relationship between: + +- The media port at the start of an OMS MCG and the input media port of the first amplifier in the OMS MCG; + +or: + +- The output media port of the last amplifier in the OMS MCG and the media port at the end of that OMS MCG. + +In the case where no optical amplifiers are deployed, the OTS MCG and OMS MCG are coincident. + +## 7.4 Management of media channels + +Management of media channels is only described for point-to-point media channels. As described in clause 7.1.2, a media channel may be a serial concatenation of one or more media channels, each with its own frequency slot. Media subnetworks provide a point of flexibility where the route of a media channel across the media network may be created or modified. + +For some media channels the frequency slot is fixed. If the media channel includes a configurable filter function, the frequency slot can be configured via the management/control plane. The configuration of a frequency slot in a configurable filter may create or modify the media channel between media ports of the filter function. This configuration can modify the route of a media channel across the network (an example of this is provided in Appendix I). The route of a media channel may also be created, or modified, by configuring a media channel in a media element such as a ROADM (that encompasses a media subnetwork and filter functions as described in clause 7.2). + +A media channel that has a "wide"4 frequency slot may be concatenated with multiple media channels each with its own "narrower" frequency slot. The effective frequency slot of a media channel is the frequency range that is common in the frequency slots of the media channels that are serially + +4 A "wide" media channel may be used to provide what is commonly called an "express" channel in a ROADM. + +concatenated to form the longer media channel. Some examples of the construction of media channels are provided in Appendix I. + +### 7.4.1 Management of network media channels (NMCs) + +An NMC provides the association between a transmitter and a receiver. It is formed by a contiguous serial concatenation of media channels between a transmitter and a receiver. This serial concatenation may include a set of media channels that are dedicated to a single NMC. Alternatively, if a number of NMCs take a common path through all, or part, of the media network, it may be possible to optimize the spectral utilization by using wider media channels. Some examples of this are provided in Appendix IX. + +# 8 Information/signal boundary + +There are multiple media boundary functions that may occur at the information/signal boundary. All are represented diagrammatically with the symbol ![A small grey downward-pointing arrow icon.](efafcae43acae17c4bb9f41420411b00_img.jpg). The functions include the transmitter and receiver described in clause 10 and clause 13.1, and the optical parameter monitor (OPM-x) described in clause 9.1. Examples of other media boundary functions are provided in Appendix III. + +Examples of functions at the information/signal boundary are shown in Table 8-1. + +**Table 8-1 – Examples of functions at information/signal boundary** + +| Function | Input | Output | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| 1. Transmitter | Client characteristic information (CI) adapted into M-AI. The data rate, and modulation format employed are not restricted. The same modulation scheme must be employed at the transmitter and receiver for a particular information stream. | An OTSi with the client digital information modulated on it. | +| 2. Receiver | An OTSi with digital information modulated on it. | The original client M-AI. | +| 3. Optical Parameter Monitor | An optical signal (OTSi with or without digital information modulated on it and optical noise). | Digital information that represents the parameter(s) of the signal(s) monitored. | + +# 9 Monitoring media constructs + +The media network has no inherent monitoring capability. The integrity of a media channel can be inferred by monitoring the OTSi that are expected to be present in that media channel. Monitoring of OTSi is achieved by attaching an optical parameter monitor (OPM-x) to the media channel. The OPM-x function may not be supported in all types of media networks, e.g., applications described in [ITU-T G.959.1]. + +## 9.1 Optical parameter monitor (OPM-x) + +The OPM-x media boundary function monitors generic parameters. When describing specific parameters, their scope must be clearly defined. Also, the frequency slot of the media channel between the monitoring reference point and the OPM-x must be defined if it is less than the effective frequency slot associated with the monitoring reference point. The OPM-x may be embedded in a media element + +and the monitoring reference point being observed may not be at the boundary of the media element. Multiple OPM-x may be attached to a single monitoring reference point. + +NOTE – When an OPM-x is attached to a bidirectional signal monitor, there may be two instances of OPM-x. The figures only show a single instance. + +## 9.2 Optical signal maintenance entities (OSME) + +An optical signal maintenance entity (OSME) provides monitoring for the set of the OTSi that traverse an MCG (described in clause 7.1.3). + +When an OPM-x is attached at each end of an MCG the OSME and its reference points are created. For example, the OPM-pwr measures the power of the optical signal (OTSi and optical noise) that is present in the MCG at the OMS/OTS OSME reference points. + +The set of OTSi carried by the optical multiplex section (OMS) MCG or the optical transmission section (OTS) MCG are monitored by the OMS OSME and OTS OSME, respectively. The same set of signals is carried by both the OMS MCG and the OTS MCG. This monitoring results in management information (MI) that is passed to a management system, as well as to the far end of the maintenance entity. The OTS MCG and OMS MCG are described in clause 11. + +This is illustrated in Figure 9-1 for discrete amplifiers and Figure 9-2 for distributed amplifiers. The OSC is described in clause 12. The relationship between the OMS OSME and OTS OSME reference points and the reference points described in other ITU-T optical system Recommendations is provided in Appendix VII. + +![Diagram of optical signal maintenance entities with discrete amplifiers. The diagram shows a bidirectional optical path between two transceivers (T/R) at the top, connected via a series of optical components. The path includes a signal monitor (hexagon), a media port (diamond), an OSC (square), a power monitor (P), and a fibre (F). A central 'Amplifier site' is enclosed in a dashed box and contains two fibre (F) units, each with its own OSC and power monitor (P). The OMS OSME (Optical Multiplex Section Optical Signal Maintenance Entity) is indicated by arrows pointing to the power monitors (P) at the ends of the main path. The OTS OSME (Optical Transmission Section Optical Signal Maintenance Entity) is indicated by arrows pointing to the power monitors (P) within the amplifier site. The path is labeled 'Fibre' at the bottom. A legend at the bottom left shows a hexagon for 'Signal monitor that diverts part of the signal power to the OPM' and a diamond for 'Media port'. The diagram is labeled G.807(24) in the bottom right.](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +Diagram of optical signal maintenance entities with discrete amplifiers. The diagram shows a bidirectional optical path between two transceivers (T/R) at the top, connected via a series of optical components. The path includes a signal monitor (hexagon), a media port (diamond), an OSC (square), a power monitor (P), and a fibre (F). A central 'Amplifier site' is enclosed in a dashed box and contains two fibre (F) units, each with its own OSC and power monitor (P). The OMS OSME (Optical Multiplex Section Optical Signal Maintenance Entity) is indicated by arrows pointing to the power monitors (P) at the ends of the main path. The OTS OSME (Optical Transmission Section Optical Signal Maintenance Entity) is indicated by arrows pointing to the power monitors (P) within the amplifier site. The path is labeled 'Fibre' at the bottom. A legend at the bottom left shows a hexagon for 'Signal monitor that diverts part of the signal power to the OPM' and a diamond for 'Media port'. The diagram is labeled G.807(24) in the bottom right. + +Figure 9-1 – Optical signal maintenance entities with discrete amplifiers + +![Diagram of optical signal maintenance entities with distributed amplifiers. The diagram shows a network of optical components including Transceivers (T/R), Optical Signal Monitors (OSME), Optical Signal Controllers (OSC), Pumps (P), Fibers (F), and Media elements. A central 'Amplifier site' is enclosed in a dashed box, containing two Media elements, two Fibers, an OSC, a Pump, and an OSME. The diagram is labeled with 'OMS OSME', 'OTS OSME', 'Fibre', and 'Pump wavelength insertion'. A legend at the bottom defines the symbols for signal monitors and media ports. The diagram is identified by the code G.807(24).](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +The diagram illustrates the optical signal maintenance entities in a network with distributed amplifiers. At the top, two Transceivers (T/R) are connected to a central hub. Below this, the network consists of several nodes connected by Fibre. Each node contains a Media element, a Pump (P), an Optical Signal Controller (OSC), and an Optical Signal Monitor (OSME). A central 'Amplifier site' is highlighted with a dashed box, containing two Media elements, two Fibers, an OSC, a Pump, and an OSME. The diagram is labeled with 'OMS OSME', 'OTS OSME', 'Fibre', and 'Pump wavelength insertion'. A legend at the bottom defines the symbols: a blue circle with a diagonal line for a 'Signal monitor that diverts part of the signal power to the OPM' and a black diamond for a 'Media port'. The diagram is identified by the code G.807(24). + +Diagram of optical signal maintenance entities with distributed amplifiers. The diagram shows a network of optical components including Transceivers (T/R), Optical Signal Monitors (OSME), Optical Signal Controllers (OSC), Pumps (P), Fibers (F), and Media elements. A central 'Amplifier site' is enclosed in a dashed box, containing two Media elements, two Fibers, an OSC, a Pump, and an OSME. The diagram is labeled with 'OMS OSME', 'OTS OSME', 'Fibre', and 'Pump wavelength insertion'. A legend at the bottom defines the symbols for signal monitors and media ports. The diagram is identified by the code G.807(24). + +**Figure 9-2 – Optical signal maintenance entities with distributed amplifiers** + +When the OTS OSME and OMS OSME start or end at the same location, a single (common) OPM-x may be used. This occurs, for example, when a discrete amplifier is not deployed in a terminal site. + +An NMC (see clause 7.1.2.1) can exist in the absence of the OMS OSME and OTS OSME. However, some of the alarm management, fault detection and fault isolation capabilities described in clause 15 will not be supported. + +The implementation of the OTS OPM-x or OMS OPM-x may include the ability to detect which frequency slots have an active OTSi, or measure the performance of an active OTSi (e.g., optical signal-to-noise ratio (OSNR)) at the output of various stages of optical amplification. For example, use of OPM-pwr to monitor active OTSi is illustrated in Figure 9-3. + +![Diagram of OPM-pwr for an active OTSi. The diagram shows a network path with transmitters (T), receivers (R), amplifiers (F), and signal monitors (P). A central 'Amplifier site' is enclosed in a dashed box. The path includes 'Fibre' segments and 'OMS OSME' and 'OTS OSME' labels. A legend at the bottom defines the symbols for signal monitors and media ports. The diagram is labeled G.807(24).](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +The diagram illustrates the optical power monitoring (OPM) architecture for an active Optical Tributary Signal (OTSi). At the far left, two transmitters (T) are connected to a media port (black diamond), which feeds into a signal monitor (P). This monitor is labeled 'OMS down'. The signal then passes through a series of components: a media port, a signal monitor (white pentagon), a media port, and a forwarding point (F). The signal then enters a central 'Amplifier site' enclosed in a dashed box. Inside this site, the signal passes through a media port, a signal monitor (P) labeled 'OTS up', a media port, a signal monitor (white pentagon), a media port, a signal monitor (P) labeled 'OTS down', a media port, and a forwarding point (F). The signal exits the amplifier site through a media port, a signal monitor (P) labeled 'OTS up', a media port, a signal monitor (white pentagon), a media port, and a forwarding point (F). The signal then passes through a 'Fibre' segment to another media port, a signal monitor (P) labeled 'OMS up', a media port, a signal monitor (white pentagon), a media port, and finally two receivers (R). Labels 'OMS OSME' and 'OTS OSME' are placed between the OMS and OTS signal monitors. The diagram is labeled 'G.807(24)' in the bottom right corner. + +Legend: + +- Signal monitor that diverts part of the signal power to the OPM (white pentagon) +- Media port (black diamond) + +Diagram of OPM-pwr for an active OTSi. The diagram shows a network path with transmitters (T), receivers (R), amplifiers (F), and signal monitors (P). A central 'Amplifier site' is enclosed in a dashed box. The path includes 'Fibre' segments and 'OMS OSME' and 'OTS OSME' labels. A legend at the bottom defines the symbols for signal monitors and media ports. The diagram is labeled G.807(24). + +**Figure 9-3 – OPM-pwr for an active OTSi** + +# 10 Optical tributary signals and interfaces + +## 10.1 OTSi + +The optical tributary signal (OTSi) is characterized by its central frequency and an application identifier (or application identifiers) described in clause 6.2.3. Each unidirectional OTSi is carried in an independent NMC (the NMC is described in clause 7.1.2.1). The client CI present at a forwarding point (FP) or forwarding end point (FwEP) is mapped and encoded by an adaptation source function. For multiple OTScSi in an OTSi, each has its own CI. + +NOTE – The encoding process in the M-AI/client CI adaptation may include the computation and insertion of a forward error correction (FEC) code. + +The M-AI is used by a transmitter to create a T-OTSi. The OTSi is converted back to M-AI by a receiver according to a specific modulation/demodulation mechanism. The adaptation sink function processes the M-AI to recreate the client CI. As described in clause 10.2, the client CI may be carried by more than one OTSi. + +### 10.1.1 Assignment of signals to media channels + +A unidirectional OTSi is assigned to one NMC and an NMC supports one unidirectional OTSi. Some media networks have a fixed configuration (e.g., the applications described in [ITU-T G.959.1]). In such a media network, the assignment of an OTSi to an NMC and the media channel(s) that form the NMC cannot be configured via the management/control plane. In a media network that supports + +configuration via the management/control plane, a media channel may be configured before it has been decided which OTSi will be assigned to it. The OTSi must be compatible with the NMC to which it has been assigned. This compatibility is confirmed by using an application identifier as described in clause 6.2.3. + +An NMC with an effective frequency slot that supports a single OTSi may be constructed, as described in clause 7.4, between the media port on a transmitter and the media port on a receiver. Alternatively, the media network may be constructed using only coupler-splitters, without any discrete filters. This creates a point-to-multipoint media channel between a transmitter and all receivers and a multipoint-to-point media channel between all transmitters and one receiver. Examples of OTSi in point-to-multipoint and multipoint-to-point media channels are given in clauses 7.3.2, 10.1.2, and Appendix V. Point-to-point communications between a specific pair of transmitter and receiver can be achieved by various techniques including configuring the same frequency slot at the transmitter5 and receiver6. This creates a point-to-point NMC. An example of this type of network is provided in Appendix II. + +### **10.1.2 OTSi with multiple independent information streams** + +The OTSi supports the transfer of the client digital information. In some cases, the client digital information may consist of two or more independent information streams (which results in two or more instances of M-AI). In this case, the M-AI from each client information stream is independently modulated onto the same OTSi in a way that allows the M-AI from each client to be demodulated and extracted independently. + +#### **10.1.2.1 OTSi supporting one client with multiple independent information streams** + +In this case the transmitter function supports two (independent) M-APs. Typically, one of the information streams carries the client data, the second digital information stream carries a low bit rate message channel. A low modulation index amplitude modulation is normally used to deliver the low bit rate message channel. + +An example of this is the metro network application defined in [ITU-T G.698.4]. The [ITU-T G.698.4] message channel is distinct from an overhead channel that is a part of the digital client's CI. The CI of the [ITU-T G.698.4] message channel CI and the client data are both independently modulated onto the OTSi. In effect, two transmitters and receivers are used to support a [ITU-T G.698.4] OTSi between a head end and tail end: one for the message channel CI, and one for the client data CI. This case is depicted in Figure 10-1. + +--- + +5 This may be achieved by using a tunable transmitter with a configurable filter. + +6 This may be achieved by use of a coherent receiver or a configurable filter at the demodulator. + +![Diagram of mapping two independent information streams over one OTSi. On the left, a 'Message channel' and a 'Digital client' are connected to a 'Transmitter X and Y'. On the right, another 'Message channel' and 'Digital client' are connected to a 'Receiver X and Y'. The transmitter and receiver are connected by a 'Fibre' line. Labels on the right side point to various components: 'ITU-T G.800 FP or FwEP', 'Adaptation (to modulator)', 'M-AP', 'OTSi', and 'Media port'. The diagram is labeled G.807(24).](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +Diagram of mapping two independent information streams over one OTSi. On the left, a 'Message channel' and a 'Digital client' are connected to a 'Transmitter X and Y'. On the right, another 'Message channel' and 'Digital client' are connected to a 'Receiver X and Y'. The transmitter and receiver are connected by a 'Fibre' line. Labels on the right side point to various components: 'ITU-T G.800 FP or FwEP', 'Adaptation (to modulator)', 'M-AP', 'OTSi', and 'Media port'. The diagram is labeled G.807(24). + +**Figure 10-1 – Mapping two independent information streams over one OTSi** + +In the case where the OTSi supporting a message channel are members of an OTSiG with two or more members, each message channel can be used independently, or the message channels can be used to support a single (larger) message channel client, as shown in Figure 10-2 and Figure 10-3, respectively. + +![Diagram of independent message channels in an OTSiG. At the top, 'Message channel 1' and 'Message channel n' are connected to 'CI' blocks. These are connected to an 'M-AI/client CI' block. Above this block is a 'FP' (Forwarding Plane) connected to 'CI (Client digital layer network)'. Below the 'M-AI/client CI' block is a dashed oval containing 'Multiple instances of M-AI'. Below this is another dashed oval labeled 'OTSiG' containing two 'T' (Transceiver) blocks, numbered '1' and 'n'. Each 'T' block is connected to a 'Media port'. The 'Media port' for instance '1' is highlighted with a red dot and labeled 'OTSi'. Below the 'OTSiG' oval, two blue lines represent 'NMC' (Network Management Channel) and 'NMCG' (Network Management Channel Group). The diagram is labeled G.807(24).](dd5771673aececa53d42ece89218299d_img.jpg) + +Diagram of independent message channels in an OTSiG. At the top, 'Message channel 1' and 'Message channel n' are connected to 'CI' blocks. These are connected to an 'M-AI/client CI' block. Above this block is a 'FP' (Forwarding Plane) connected to 'CI (Client digital layer network)'. Below the 'M-AI/client CI' block is a dashed oval containing 'Multiple instances of M-AI'. Below this is another dashed oval labeled 'OTSiG' containing two 'T' (Transceiver) blocks, numbered '1' and 'n'. Each 'T' block is connected to a 'Media port'. The 'Media port' for instance '1' is highlighted with a red dot and labeled 'OTSi'. Below the 'OTSiG' oval, two blue lines represent 'NMC' (Network Management Channel) and 'NMCG' (Network Management Channel Group). The diagram is labeled G.807(24). + +**Figure 10-2 – Independent message channels in an OTSiG** + +![Figure 10-3: Single message channel in an OTSiG. The diagram shows a 'Message channel CI' connected to a 'M-AI/client CI' block. Above the 'M-AI/client CI' block is an 'FP' (Frame Point) and 'CI (Client digital layer network)'. Below the 'M-AI/client CI' block, there are 'Multiple instances of M-AI' (indicated by a dashed oval) and an 'M-AP' (Media Adaptation Point). These connect to two transceivers labeled 'T'. The left 'T' has a 'Media port' and is labeled 'OTSi' in red. The right 'T' is labeled 'OTSiG'. Below the transceivers, a blue line represents the optical path, labeled 'NMC' and 'NMCG'. The reference 'G.807(24)' is shown at the bottom right.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +Figure 10-3: Single message channel in an OTSiG. The diagram shows a 'Message channel CI' connected to a 'M-AI/client CI' block. Above the 'M-AI/client CI' block is an 'FP' (Frame Point) and 'CI (Client digital layer network)'. Below the 'M-AI/client CI' block, there are 'Multiple instances of M-AI' (indicated by a dashed oval) and an 'M-AP' (Media Adaptation Point). These connect to two transceivers labeled 'T'. The left 'T' has a 'Media port' and is labeled 'OTSi' in red. The right 'T' is labeled 'OTSiG'. Below the transceivers, a blue line represents the optical path, labeled 'NMC' and 'NMCG'. The reference 'G.807(24)' is shown at the bottom right. + +**Figure 10-3 – Single message channel in an OTSiG** + +#### 10.1.2.2 OTSi carrying multiple independent digital clients using SCM + +Another method of supporting multiple independent digital clients within one OTSi is to use subcarrier multiplexing. Each client can be modulated to a distinct subcarrier (OTScSi), and multiple OTScSi may be present within a single OTSi. Typically, all digital clients of a single OTSi will have bit rates with the same order of magnitude and use the same modulation scheme. + +In Figure 10-4, the digital clients on the left side are adapted into media layer adapted information (M-AI) which is then input to a transmitter. The transmitter modulates each subcarrier with information in one or more M-AI, and the resultant T-OTSi at the $S_s$ reference point is depicted in Figure 10-4. The $S_s$ and $R_s$ reference points are defined in [ITU-T G.698.1]. The T-OTSi is input to an optical splitter that is used to distribute the T-OTSi to each receiver. At each $R_s$ reference point, the OTSi is input to a receiver that recovers M-AI from the subcarrier(s). + +For Client Z traffic, its M-AI is supported over a dedicated subcarrier that is not used by other client instances. More than one subcarrier could be used for one client stream, as illustrated with Client B, which is supported by M-AI2 and M-AI3. + +Figure 10-4 also illustrates the sharing of subcarriers by multiple clients. In the media adaptation process at the transmitter, information from clients A and C is multiplexed into M-AI1 which is then modulated onto a subcarrier. The optical splitter distributes the signal to the (separate) receivers for Client A and Client C, each of which is tuned to the same subcarrier onto which the transmitter modulated M-AI1. The media adaptation function on the right side demultiplexes only the required client information (A or C) from M-AI1. + +![Figure 10-4: Model of SCM in PtMP. This diagram illustrates the Point-to-Multipoint (PtMP) configuration. On the left, multiple clients (Client A, Client B, Client C, Client Z) are shown sending data (M-AI1, M-AI2, M-AI3, M-AIn) into a single Transmitter. The Transmitter outputs a signal labeled Ss, which is an SCM optical signal in fibre. Below the signal, a frequency spectrum is shown with multiple subcarriers labeled 1, 2, 3, ..., n in THz. The signal then enters an Optical splitter. From the Optical splitter, multiple Receivers (Receiver1, Receiver2,3, Receiver1, Receivern) receive the signal. Each receiver is associated with a client (Client A, Client B, Client C, Client Z) and outputs the corresponding data (M-AI1, M-AI2, M-AI3, M-AIn). A note above the first receiver states 'Receiver recovers M-AI1 from its subcarrier'. The diagram is labeled G.807(24) at the bottom right.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +Figure 10-4: Model of SCM in PtMP. This diagram illustrates the Point-to-Multipoint (PtMP) configuration. On the left, multiple clients (Client A, Client B, Client C, Client Z) are shown sending data (M-AI1, M-AI2, M-AI3, M-AIn) into a single Transmitter. The Transmitter outputs a signal labeled Ss, which is an SCM optical signal in fibre. Below the signal, a frequency spectrum is shown with multiple subcarriers labeled 1, 2, 3, ..., n in THz. The signal then enters an Optical splitter. From the Optical splitter, multiple Receivers (Receiver1, Receiver2,3, Receiver1, Receivern) receive the signal. Each receiver is associated with a client (Client A, Client B, Client C, Client Z) and outputs the corresponding data (M-AI1, M-AI2, M-AI3, M-AIn). A note above the first receiver states 'Receiver recovers M-AI1 from its subcarrier'. The diagram is labeled G.807(24) at the bottom right. + +Figure 10-4 – Model of SCM in PtMP + +In the multipoint to point (MPtP) direction shown in Figure 10-5, the OTSi from each Ss are aggregated in the optical coupler. For the case where Client A and C share the same subcarrier, a mechanism to share the subcarrier is needed to prevent loss of information when the signals from Client A and C are merged in the coupler. The receiver processes a receiver OTSi (R-OTSi) containing one or more OTScSi. + +![Figure 10-5: Model of SCM in MPtP. This diagram illustrates the Multipoint-to-Point (MPtP) configuration. On the right, multiple clients (Client A, Client B, Client C, Client Z) are shown sending data (M-AI1, M-AI2, M-AI3, M-AIn) into individual Transmitters (Transmitter1, Transmitter2,3, Transmitter1, Transmittern). Each transmitter modulates the data into a subcarrier, labeled Ss. The signals from these transmitters are aggregated in an Optical coupler. Below the coupler, a frequency spectrum is shown with multiple subcarriers labeled 1, 2, 3, ..., n in THz. The aggregated signal, labeled R-OTSi, is then sent to a Receiver. The Receiver outputs the data to multiple clients (Client A, Client C, Client B, Client Z). A note above the first transmitter states 'Transmitter modulates M-AI1 into a subcarrier'. The diagram is labeled G.807(24) at the bottom right.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +Figure 10-5: Model of SCM in MPtP. This diagram illustrates the Multipoint-to-Point (MPtP) configuration. On the right, multiple clients (Client A, Client B, Client C, Client Z) are shown sending data (M-AI1, M-AI2, M-AI3, M-AIn) into individual Transmitters (Transmitter1, Transmitter2,3, Transmitter1, Transmittern). Each transmitter modulates the data into a subcarrier, labeled Ss. The signals from these transmitters are aggregated in an Optical coupler. Below the coupler, a frequency spectrum is shown with multiple subcarriers labeled 1, 2, 3, ..., n in THz. The aggregated signal, labeled R-OTSi, is then sent to a Receiver. The Receiver outputs the data to multiple clients (Client A, Client C, Client B, Client Z). A note above the first transmitter states 'Transmitter modulates M-AI1 into a subcarrier'. The diagram is labeled G.807(24) at the bottom right. + +Figure 10-5 – Model of SCM in MPtP + +## 10.2 OTSiG + +The optical tributary signal group (OTSiG) is a management/control abstraction that represents a group of one or more OTSi that carry the CI of one client (the OTSi may also support a message channel as described in clause 10.1.2.1). The OTSiG is not present in the media network. For the purposes of management and control, the set of NMCs that support the members of the OTSiG can be represented as an NMC group (NMCG) as described in Annex B. A generic adaptation function + +label "M-AI/client CI" is used in this Recommendation to describe the encoding and mapping from the client CI into one or more instances of M-AI. The input of the adaptation source function is the client CI; the output is one or more instances of M-AI. Each transmitter accepts one instance of M-AI and outputs an OTSi. Each transmitter outputs an OTSiG. + +The case where a client CI is carried by a single OTSi is shown in Figure 10-6. + +![Figure 10-6: Mapping a client digital stream to an OTSiG that contains one OTSi. The diagram shows a flow from FP to CI (Client digital layer network) through an M-AI/client CI block, resulting in M-AI. This M-AI is then processed by an M block to produce an OTSi. The OTSi is then mapped to an OTSiG via a Media port. The OTSiG is then processed by an NMC block to produce an NMCG. The NMCG is then output via a Media port. The diagram is labeled G.807(24).](318886a86a1dcc59e1fc83db6f157c60_img.jpg) + +Figure 10-6: Mapping a client digital stream to an OTSiG that contains one OTSi. The diagram shows a flow from FP to CI (Client digital layer network) through an M-AI/client CI block, resulting in M-AI. This M-AI is then processed by an M block to produce an OTSi. The OTSi is then mapped to an OTSiG via a Media port. The OTSiG is then processed by an NMC block to produce an NMCG. The NMCG is then output via a Media port. The diagram is labeled G.807(24). + +**Figure 10-6 – Mapping a client digital stream to an OTSiG that contains one OTSi** + +The case where a client CI is carried by more than one OTSi is illustrated in Figure 10-7. + +![Figure 10-7: An OTSiG consists of more than one OTSi. The diagram shows a flow from FP to CI (Client digital layer network) through an M-AI/client CI block, resulting in multiple instances of M-AI. These multiple instances are then processed by multiple T blocks (labeled 1 and n) to produce multiple OTSi. The OTSi are then mapped to an OTSiG via Media ports. The OTSiG is then processed by an NMC block to produce an NMCG. The NMCG is then output via a Media port. The diagram is labeled G.807(24).](5478f70a6cef3e5672b2b22d28830cfb_img.jpg) + +Figure 10-7: An OTSiG consists of more than one OTSi. The diagram shows a flow from FP to CI (Client digital layer network) through an M-AI/client CI block, resulting in multiple instances of M-AI. These multiple instances are then processed by multiple T blocks (labeled 1 and n) to produce multiple OTSi. The OTSi are then mapped to an OTSiG via Media ports. The OTSiG is then processed by an NMC block to produce an NMCG. The NMCG is then output via a Media port. The diagram is labeled G.807(24). + +**Figure 10-7 –An OTSiG consists of more than one OTSi** + +The differential delay between members of the OTSiG must be controlled. For example, by carrying all members of the OTSiG over the same fibre. + +NOTE – The mapping and encoding used in the M-AI/client CI adaptation may be dependent on the modulation scheme. The details of the M-AI/client CI adaptation and transmitter are outside the scope of this Recommendation. + +The cardinality between the client CI, OTSiG, NMCG, M-AI, OTSi and NMC are: + +- Client CI (1): OTSiG (1): NMCG (1); +- Client CI (1): M-AI (n) where $n \geq 1$ ; +- M-AI (1): OTSi (1): NMC (1). + +Examples of the use of these entities to describe inverse multiplexed clients are provided in Appendix VIII. + +### 10.2.1 OTScSiG + +The optical tributary signal group (OTScSiG) is a management/control abstraction that represents a group of two or more OTScSi that carry the CI of one client. The OTScSiG is not present in the media network. A generic adaptation function label "M-AI/client CI" is used in this Recommendation to describe the encoding and mapping from the client CI into one or more instances of M-AI. The input of the adaptation source function is the client CI; the output is two or more instances of M-AI. Each transmitter accepts two or more instances of M-AI and outputs an OTSi as described in clause 10.1.2.2. + +The cardinality between the client CI, OTScSiG, M-AI and OTSi are: + +- Client CI (1): OTScSiG (1): OTSi (1); +- OTScSiG (k): OTSi (1) where $k \geq 1$ ; +- Client CI (1): M-AI (n) where $n \geq 1$ ; +- M-AI (1): OTScSi (1); +- OTScSi (m): OTSi (1) where $m > 1$ . + +## 10.3 OTSiA + +The optical tributary signal assembly (OTSiA) is a management/control abstraction that represents the OTSiG together with any non-associated OTSiG overhead (OTSiG-O). It is described only for point-to-point media channels. This is illustrated in Figure 10-8. To provide the management capabilities described in clause 15, the OTSiG-O should be carried by one of the following: + +- The OSC (see clause 12), and the OSC and OTSiG should be carried over the same fibre; or +- A message channel (see clause 10.1.1) or; +- An overhead communications channel (OCC) described in [ITU-T G.7712]. + +The multiplexing of OTSiG-O onto the OSC via the OMS-O and OTS-O is shown in Figure 10-9. + +One OTSiA supports the CI of one client. The OTSiA, together with the associated media channels, may be managed as part of a media network. In some cases, e.g., where the OTSiG-O does not support all the monitoring functions, OTSiA connection monitoring relies on the client digital stream for certain monitoring functions (e.g., path trace) in order to support the full operation, administration, maintenance (OAM) and fault management capabilities described in clause 15. + +![Diagram of an OTSiA architecture showing the flow from a Client digital layer network (CI) through an M-AI/client CI, multiple instances of M-AI, OTSiG-O, OTSiG, and finally to the NMC and NMCG.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +The diagram illustrates the architecture of an OTSiA. At the top, a 'FP' (Framing Point) is connected to a 'CI (Client digital layer network)'. Below the CI is a block labeled 'M-AI/client CI'. This block connects to multiple instances of 'M-AI' (Media Access Interface), which are grouped by a dashed oval and labeled 'Multiple instances of M-AI'. Each 'M-AI' instance is connected to an 'M-AP' (Media Access Point) and a 'T' (Transceiver). The 'T' transceivers are connected to 'OTSiG' (Optical Transport Signal) and 'OTSiA' (Optical Transport Signal A) components. The 'OTSiG' components are connected to an 'OTSiG-O' (Optical Transport Signal O) component. The 'OTSiG-O' component is connected to a 'NMC' (Network Management Channel) and an 'NMCG' (Network Management Channel Group). The 'NMC' and 'NMCG' are shown as blue lines at the bottom. The diagram is labeled 'G.807(24)' in the bottom right corner. + +Diagram of an OTSiA architecture showing the flow from a Client digital layer network (CI) through an M-AI/client CI, multiple instances of M-AI, OTSiG-O, OTSiG, and finally to the NMC and NMCG. + +**Figure 10-8 – An OTSiA comprised of OTSiG and OTSiG-O** + +NOTE 1 – The generation and processing of OTSiG-O is outside the scope of this Recommendation. + +NOTE 2 – As described in clause 10.1.2.1, the OTSi may also support digital OTSiG-O information. + +### 10.3.1 Management of OTSiA connections + +From a management control perspective, a request to carry an OTSiA should be considered as a single action. This action involves the configuration of the transmitter(s) and receiver(s), the media channels and the OTSiG-O. Configuration of the NMCs7 in the MCG that supports the OTSiG includes the configuration of the media elements that encompass the media constructs (e.g., media subnetworks, configurable filters and possibly amplifiers) that are part of the serial concatenation of media channels that forms the NMC. + +Two simple cases for the configuration of a media element that includes a media subnetwork when an OTSiA connection request is received are described below: + +- 1) Pre-configured media elements: +In this case the media channels in the media subnetwork and the associated filters are configured before the OTSiA connection request is received: + - The OTSiG-O connection function and the OMS Multiplex Structure Identifier8 (MSI) (carried by the OMS-O) are configured. The media channel(s) in the media subnetwork must be checked to verify that the correct ports are connected so that all members of the OTSiG are directed to and or from the same OMS media port. The associated filters are checked to ensure that frequency slot of each filter is compatible with the frequency slot requested for each OTSi. + - In general, when the OTSiA is deleted, only the OTSiG-O connection and OMS MSI (for that OTSiG) should be removed, the configuration of the media elements should not be changed. + +7 As described above, the media channels that support the NMC may be fully or partially configured before the OTSiA connection request is received. + +8 The OMS MSI indicates the frequency slots that have been allocated to an OTSiG on the OMS MCG. + +or: + +- 2) The media elements are not configured: + - In this case, the media channels in the media subnetworks and filters are configured as a result of the OTSiA connection request. The media channels in the media subnetwork and the associated filters, the OTSiG-O connection and the OMS MSI are configured after the OTSiA connection request is received. The consistency checks described above should be performed. + - In general, deletion of the OTSiA should cause the deletion of the media channels in the media subnetwork and the removal of the filter configuration. Also, the OTSiG-O connection should be deleted, and the OMS MSI (for that OTSiG) should be removed. In the case where a media channel (in a media subnetwork or filter) is being used to support another NMC these media channels should not be deleted. + +### 10.3.2 OTSiA subnetwork + +The OTSiA subnetwork is a management abstraction that represents the flexible media associations9 and the corresponding OTSiG-O subnetwork. As described in clause 10.3.1, a request for an OTSiA subnetwork connection is mapped into the appropriate configuration commands for media channels in the media subnetwork and configurable filters, and the corresponding connection in the OTSiG-O subnetwork and configuration of the OMS MSI. + +A simple example of an OTSiA subnetwork in the context of an add/drop site is provided in Figure 10-9. The filters, optical amplifiers and media subnetwork are shown as independent media constructs and the OTSiA only has one OTSi. The OMS and OTS monitoring reference points described in clause 9.2 are not shown. The forwarding of the OTSiG-O is modelled by the OTSiG-O subnetwork. Connection points on the OTSiG-O subnetwork must correspond to those of the media channels in the filters and media subnetwork that carry the corresponding set of OTSi in the OTSiG, and the OAM information flow must follow that of the media channel configured in the media subnetwork. + +--- + +9 This flexibility may be implemented by a media subnetwork, a set of interconnected configurable filters or some combination of configurable filters and media subnetworks. + +![Diagram of OTSiA subnetwork and supporting media and OTSiG-O subnetworks. The diagram shows two parallel optical paths. The left path starts at Port D1 (T/R) with OTSiA and OTSiG inputs, passing through a Media subnetwork (part of the OTSiA subnetwork), two Optical amplifiers, and an OSC filter to Port L1. The right path starts at an OTSiG-O input, passing through an OTSiG-O subnetwork (part of the OTSiA subnetwork), then through a series of layers: OMS-O/OTSiG-O, OMS-O, OTS-O/OMS-O, OTS-O, M-AI/OTS-O, and OSC, finally reaching Port L2 via an OSC filter. A 'Coordination' block with dashed arrows connects the Media subnetwork and OTSiG-O subnetwork. A red oval encloses the Media subnetwork and OTSiG-O subnetwork, labeled 'OTSiA subnetwork'. The label 'G.807(24)' is in the bottom right corner.](f57c7b37d7a05a99618104f390089f03_img.jpg) + +Diagram of OTSiA subnetwork and supporting media and OTSiG-O subnetworks. The diagram shows two parallel optical paths. The left path starts at Port D1 (T/R) with OTSiA and OTSiG inputs, passing through a Media subnetwork (part of the OTSiA subnetwork), two Optical amplifiers, and an OSC filter to Port L1. The right path starts at an OTSiG-O input, passing through an OTSiG-O subnetwork (part of the OTSiA subnetwork), then through a series of layers: OMS-O/OTSiG-O, OMS-O, OTS-O/OMS-O, OTS-O, M-AI/OTS-O, and OSC, finally reaching Port L2 via an OSC filter. A 'Coordination' block with dashed arrows connects the Media subnetwork and OTSiG-O subnetwork. A red oval encloses the Media subnetwork and OTSiG-O subnetwork, labeled 'OTSiA subnetwork'. The label 'G.807(24)' is in the bottom right corner. + +**Figure 10-9 – OTSiA subnetwork and the supporting media and OTSiG-O subnetworks** + +In the case where the optical amplifier is not present (described in clause 7.3.3) the OTS OSME and OMS OSME reference points (described in clause 9.2) are coincident. The OTS-O and OMS-O (described in clause 11.1) are present. + +The granularity of the OTSiG-O subnetwork connection is always that of a single OTSiG-O. The granularity of the media channel associations in the media subnetwork is determined by the effective slot width of the filters that are attached to the ports of the media subnetwork. The slot width may be the same as an NMC (and hence support a single OTSi), or it may be larger so that the media channel may be a part of multiple NMCs (and thus supporting multiple OTSi). The request to configure an OTSiA connection is mapped into configuration requests for the OTSiG-O subnetwork, the OMS MSI, the media subnetwork, and any configurable filters. + +An example of a media element that encompasses all of the media constructs shown in Figure 10-9 is a ROADM, as described in [ITU-T G.680]. This is illustrated in Figure 10-10. Other encapsulations that use more than one media element are possible. + +![Diagram of a media element and OTSiG-O subnetwork architecture.](7f5df81190b8dc50dad2604562ae0715_img.jpg) + +The diagram illustrates a network architecture involving a **Media element** and an **OTSiG-O subnetwork**. + +- Media element:** A large dashed box containing two parallel optical paths. Each path includes an **OSC filter**, an **Optical amplifier**, and a **Media subnetwork**. The element has three ports: **Port D1** (top left), **Port L1** (bottom left), and **Port L2** (bottom right). +- External Connections:** + - A **T/R** (Transceiver) is connected to **Port D1**, with **OTSiA** and **OTSiG** signals indicated. + - An external **OTSiG-O** node is also connected to **Port D1**. +- OTSiG-O subnetwork:** Enclosed in a red oval, it contains an **OTSiG-O** node that coordinates with the **Media subnetwork** inside the media element. This subnetwork connects to two parallel processing paths: + - Each path starts with an **OMS-O/OTSiG-O** node, followed by an **OMS-O** node, an **OTS-O/OMS-O** node, an **OTS-O** node, an **M-AI/OTS-O** node, and an **OSC** node. + - The **OSC** nodes from both paths are connected to a common horizontal bus line. + - This bus line connects to the **OSC filter** nodes inside the **Media element**. +- Internal Media Constructs:** The **Media element** contains two **Optical amplifier** nodes and two **OSC filter** nodes, which are part of the internal media constructs. + +G.807(24) + +Diagram of a media element and OTSiG-O subnetwork architecture. + +**Figure 10-10 – Media element and OTSiG-O subnetwork** + +In this case, the request to configure an OTSiA connection is mapped into a request to configure the OTSiG-O subnetwork, the OMS MSI and the corresponding media channels between ports L1 and L2, or between ports L1 and D1 or between ports L2 and D1 of the media element. The media element translates the request for an atomic media channel between its ports into the required configuration of the internal media constructs (such as configurable filters and media subnetworks). + +# 11 Monitoring of optical signals + +The media network has no inherent monitoring capability. In networks that support the OPM-x the integrity of a media channel can be inferred by monitoring the OTSi that are expected to be present in that media channel. Different monitoring reference points may be chosen in order to facilitate the management of the media network. This clause describes the use of the OPM-x (described in clause 9.1), as well as the OTS OSME and OMS OSME (described in clause 9.2), and the non-associated overhead. + +## 11.1 Non-associated overhead + +Non-associated overhead is only described for point-to-point media channels. + +Three types of non-associated overhead are used: + +- OTSiG-O carries the following: Status of the OTSiG; information for OTSiA connectivity supervision: information that describes the relevant characteristics of the OTSi that are in the OTSiG; +- OMS-O carries: OTSiG-O for each OTSiG in the OMS MCG; the status of the OMS; the OMS multiplex structure identifier (MSI). The MSI indicates the frequency slots that are occupied by an OTSiG, as well as the media channels that have been configured to use the OMS (which are independent of the OTSi that are being carried) and the frequency slot that is occupied by each media channel; +- OTS-O carries: OMS-O; status of the OTS; information for OTS connectivity supervision. + +The non-associated overhead may be carried by the OSC (described in clause 12). The OSC may also carry a synchronization message channel (SMC) and a data communications channel (DCC) described in [ITU-T G.7712]. + +The OTSiG-O may be carried by an OCC (described in clause 17) or a subset of the OTSiG-O may be carried by a message channel (described in clause 10.1.1). + +The multiplexing hierarchy of the non-associated overhead is illustrated in Figure 11-1. + +## 11.2 Media channels and OSMEs + +The relationship between the media, OMS OSME, OTS OSME and the non-associated overhead in a terminal is illustrated in Figure 11-1 (other OTSiA at the same interface would share the media subnetwork and OTSiG-O subnetwork). + +![Figure 11-1: Example of a terminal implementation for a single interface. This is a complex optical network diagram showing signal flow and monitoring points. At the top, a 'CI (Client digital layer network)' connects to an 'FP' (Framing Point), which in turn connects to an 'M-AI/client CI' block. Below this, two 'T/R' (Transceiver) blocks are shown, with 'OTSiG' and 'OTSiA' labels pointing to them. These connect to a 'Media subnetwork' oval. Below the media subnetwork is a pentagonal media element. To the left, 'OMS MCG' and 'OMS MCA' labels point to monitoring points. Below the media element is an 'Optical amplifier' diamond. To its left, 'OTS MCG' and 'OTS MCA' labels point to monitoring points. Below the amplifier is another pentagonal media element. To the right of the main path, several monitoring and control components are shown: an 'OTSiG-O' oval at the top right; an 'OMS-O/OTSiG-O' block below it; an 'OMS-O' block further down with a 'P' (Power monitor) block and a red 'OMS OSME' label; an 'OTS-O/OMS-O' block; an 'OTS-O' block with another 'P' block and a red 'OTS OSME' label; an 'M-AI/OTS-O' block; and an 'OSC' (Optical Supervisory Channel) block. At the bottom left is an 'OSC filter' pentagon. Blue lines represent the optical signal path, with small pentagonal icons indicating signal monitors that divert power to the OPM. A legend at the bottom states: 'Signal monitor that diverts part of the signal power to the OPM'. The diagram is labeled 'G.807(24)' in the bottom right corner.](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg) + +Figure 11-1: Example of a terminal implementation for a single interface. This is a complex optical network diagram showing signal flow and monitoring points. At the top, a 'CI (Client digital layer network)' connects to an 'FP' (Framing Point), which in turn connects to an 'M-AI/client CI' block. Below this, two 'T/R' (Transceiver) blocks are shown, with 'OTSiG' and 'OTSiA' labels pointing to them. These connect to a 'Media subnetwork' oval. Below the media subnetwork is a pentagonal media element. To the left, 'OMS MCG' and 'OMS MCA' labels point to monitoring points. Below the media element is an 'Optical amplifier' diamond. To its left, 'OTS MCG' and 'OTS MCA' labels point to monitoring points. Below the amplifier is another pentagonal media element. To the right of the main path, several monitoring and control components are shown: an 'OTSiG-O' oval at the top right; an 'OMS-O/OTSiG-O' block below it; an 'OMS-O' block further down with a 'P' (Power monitor) block and a red 'OMS OSME' label; an 'OTS-O/OMS-O' block; an 'OTS-O' block with another 'P' block and a red 'OTS OSME' label; an 'M-AI/OTS-O' block; and an 'OSC' (Optical Supervisory Channel) block. At the bottom left is an 'OSC filter' pentagon. Blue lines represent the optical signal path, with small pentagonal icons indicating signal monitors that divert power to the OPM. A legend at the bottom states: 'Signal monitor that diverts part of the signal power to the OPM'. The diagram is labeled 'G.807(24)' in the bottom right corner. + +**Figure 11-1 – Example of a terminal implementation for a single interface** + +In the case where the optical amplifier is not present (described in clause 7.3.3), the OTS OSME and OMS OSME reference points are coincident. In this case, a single OPM-x may be used to monitor both the OMS OSME and the OTS OSME. + +The media subnetwork, filter, optical amplifier OSC filter and OPM-x are shown as discrete (independent) media constructs to allow the reference points associated with the OMS OSME and OTS OSME to be exposed. When optical power monitoring is used, the OMS OPM-pwr and OTS OPM-pwr observe the bulk aggregate power level of the signals transiting the media. Frequently, these OPM-pwr functions are integrated into the optical amplifier. The output of the OSC is an OTSi, but it is labelled as OSC (instead of OTSi) to improve the clarity of the description. As described in clause 7.2, for management/control purposes, the media network is represented by media elements (that encapsulate media constructs). An example of a media element that encompasses all of the media + +constructs, OTS OSME monitoring reference point and OMS OSME monitoring reference point is shown in Figure 11-2. Other encapsulations that use more than one media element are possible10. + +The internal structure of a media element is not visible externally. However, the OTS OSME and OMS OSME monitoring reference points must be (logically) located at the monitoring reference points defined in clause 9.2. + +![Figure 11-2: Example of a terminal implementation using a single media element. The diagram shows a signal path from a Client digital layer network (CI) through an M-AI/client CI, then through two T/R units into a Media subnetwork. Inside the Media subnetwork, the signal passes through an Optical amplifier and an OSC filter. Monitoring points are indicated: OTSiG and OTSiA at the T/R units, OMS MCG and OMS MCA at the Optical amplifier, and OTS MCG and OTS MCA at the OSC filter. External monitoring points include OTSiG-O, OMS-O/OTSiG-O, OMS-O, OTS-O/OMS-O, OTS-O, and M-AI/OTS-O. Red arrows indicate OMS OSME and OTS OSME monitoring reference points. A legend at the bottom shows a blue pentagon symbol for a signal monitor that diverts part of the signal power to the OPM.](95e259e8cb3519025066052af263f8c0_img.jpg) + +The diagram illustrates a terminal implementation using a single media element. At the top, a Client digital layer network (CI) is connected to an M-AI/client CI. This is followed by two T/R (Transceiver) units. The signal then enters a Media subnetwork, which contains an Optical amplifier and an OSC (Optical Signal Controller) filter. Monitoring points are indicated by blue pentagons (Signal monitor that diverts part of the signal power to the OPM). The OMS OSME (Optical Management Section Monitoring Element) and OTS OSME (Optical Transport Section Monitoring Element) monitoring reference points are shown. The signal path continues through various optical components including OTSiG-O, OMS-O/OTSiG-O, OMS-O, OTS-O/OMS-O, OTS-O, and M-AI/OTS-O, ending at an OSC (Optical Signal Controller). The legend indicates that a blue pentagon represents a signal monitor that diverts part of the signal power to the OPM. + +Figure 11-2: Example of a terminal implementation using a single media element. The diagram shows a signal path from a Client digital layer network (CI) through an M-AI/client CI, then through two T/R units into a Media subnetwork. Inside the Media subnetwork, the signal passes through an Optical amplifier and an OSC filter. Monitoring points are indicated: OTSiG and OTSiA at the T/R units, OMS MCG and OMS MCA at the Optical amplifier, and OTS MCG and OTS MCA at the OSC filter. External monitoring points include OTSiG-O, OMS-O/OTSiG-O, OMS-O, OTS-O/OMS-O, OTS-O, and M-AI/OTS-O. Red arrows indicate OMS OSME and OTS OSME monitoring reference points. A legend at the bottom shows a blue pentagon symbol for a signal monitor that diverts part of the signal power to the OPM. + +**Figure 11-2 – Example of a terminal implementation using a single media element** + +In this case, the media element provides media channels between the line side interface and each of the OTSi and OSC transmitter/receiver. It may also provide the OMS LOS and OTS LOS indications. + +10 Placing the media constructs in different media elements provides management/control with more visibility of the implementation. + +# 12 OSC + +The OSC is an OTSi that, if present, may be used to carry the OTSiG-O, OMS-O, OTS-O, synchronization message channel (SMC), and a data communications channel (DCC), as described in [ITU-T G.7712], between amplifier sites, between a terminal site and an amplifier site, or, in the case where remote amplifiers are not deployed, between terminal sites. OSC is only described for point-to-point media channels. Both the signal and transmitter/receiver are labelled as OSC (instead of OTSi or M/D) within this Recommendation to distinguish it from an OTSi that is used to carry client CI. It is carried in a media channel (labelled as an OSC media channel). The OSC media channel is aggregated with the OTS MCG by the OSC filter. This is illustrated in Figure 12-1. + +![Figure 12-1: Insertion and removal of an OSC with discrete amplifiers. The diagram shows a sequence of components connected by fibre. On the left, a terminal site (grey diamond) connects to an OSC filter (black diamond), which is connected to an OSC transmitter/receiver (grey box) and a discrete amplifier (F, grey pentagon). The OSC filter is connected to the OTS MCG (black line). The discrete amplifier is connected to the fibre. A dashed box contains two more discrete amplifiers (F) and their corresponding OSC filters and transceivers. The OSC transceivers are connected to the OSC filter, which is connected to the OTS MCG. The OTS MCG is connected to the fibre. The fibre continues to the right, where another discrete amplifier (F) and its corresponding OSC filter and transceiver are shown. The OSC transceiver is connected to the OSC filter, which is connected to the OTS MCG. The OTS MCG is connected to the fibre. The fibre ends at a terminal site (grey diamond). The diagram is labeled G.807(24).](1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg) + +Figure 12-1: Insertion and removal of an OSC with discrete amplifiers. The diagram shows a sequence of components connected by fibre. On the left, a terminal site (grey diamond) connects to an OSC filter (black diamond), which is connected to an OSC transmitter/receiver (grey box) and a discrete amplifier (F, grey pentagon). The OSC filter is connected to the OTS MCG (black line). The discrete amplifier is connected to the fibre. A dashed box contains two more discrete amplifiers (F) and their corresponding OSC filters and transceivers. The OSC transceivers are connected to the OSC filter, which is connected to the OTS MCG. The OTS MCG is connected to the fibre. The fibre continues to the right, where another discrete amplifier (F) and its corresponding OSC filter and transceiver are shown. The OSC transceiver is connected to the OSC filter, which is connected to the OTS MCG. The OTS MCG is connected to the fibre. The fibre ends at a terminal site (grey diamond). The diagram is labeled G.807(24). + +**Figure 12-1 – Insertion and removal of an OSC with discrete amplifiers** + +The case of a distributed amplifier is illustrated in Figure 12-2. + +![Figure 12-2: Insertion and removal of an OSC with a distributed amplifier. The diagram shows a sequence of components connected by fibre. On the left, a terminal site (grey diamond) connects to an OSC filter (black diamond), which is connected to an OSC transmitter/receiver (grey box) and a discrete amplifier (F, grey pentagon). The OSC filter is connected to the OTS MCG (black line). The discrete amplifier is connected to the fibre. A dashed box labeled 'Amplifier site' contains two distributed amplifiers (Media element, grey rectangle) and their corresponding OSC filters and transceivers. The OSC transceivers are connected to the OSC filter, which is connected to the OTS MCG. The OTS MCG is connected to the fibre. The fibre continues to the right, where another discrete amplifier (F) and its corresponding OSC filter and transceiver are shown. The OSC transceiver is connected to the OSC filter, which is connected to the OTS MCG. The OTS MCG is connected to the fibre. The fibre ends at a terminal site (grey diamond). A blue arrow labeled 'Pump wavelength insertion' points to the first Media element. The diagram is labeled G.807(24).](e05122559f56af5699789b7118d8fe87_img.jpg) + +Figure 12-2: Insertion and removal of an OSC with a distributed amplifier. The diagram shows a sequence of components connected by fibre. On the left, a terminal site (grey diamond) connects to an OSC filter (black diamond), which is connected to an OSC transmitter/receiver (grey box) and a discrete amplifier (F, grey pentagon). The OSC filter is connected to the OTS MCG (black line). The discrete amplifier is connected to the fibre. A dashed box labeled 'Amplifier site' contains two distributed amplifiers (Media element, grey rectangle) and their corresponding OSC filters and transceivers. The OSC transceivers are connected to the OSC filter, which is connected to the OTS MCG. The OTS MCG is connected to the fibre. The fibre continues to the right, where another discrete amplifier (F) and its corresponding OSC filter and transceiver are shown. The OSC transceiver is connected to the OSC filter, which is connected to the OTS MCG. The OTS MCG is connected to the fibre. The fibre ends at a terminal site (grey diamond). A blue arrow labeled 'Pump wavelength insertion' points to the first Media element. The diagram is labeled G.807(24). + +**Figure 12-2 – Insertion and removal of an OSC with a distributed amplifier** + +The OTS MCG, OMS MCG and the OSC media channel must be carried by the same fibre to provide the OAM functions described clause 15. + +# 13 Transmitter/Receiver and termination functions + +## 13.1 Transmitter/Receiver + +The following generic processes take place at the transmitter/receiver: + +- Transmission defect detection and indication. + +There are three types of functional arrangements that provide bidirectional, source, and sink functions: + +- Bidirectional: consists of a pair of collocated transmitter and receiver functions. +- Transmitter: accepts one or more instances of M-AI at its input (M-AP), modulates that digital information onto the optical signal. The output of the transmitter is a T-OTSi at its media port. The T-OTSi may consist of: + - A single carrier (that carries a single digital client); or + - One or more sub-carriers (each sub-carrier may carry an independent digital client and is an OTScSi). +- The OTSi must be compatible with the NMC to which the OTSi has been assigned and should not cause detrimental interference to OTSi in other frequency slots. The spectral characteristics of the OTSi may be constrained by an inherent property of the modulation scheme, or by a filter function. The specification of the characteristics of the OTSi is outside the scope of this Recommendation. +- If the M-AI is not present the OTSi (if present) will be one unmodulated optical carrier or one or more unmodulated OTScSi. A transmitter may support more than one M-AP as described in clauses 10.1.1 and 10.1.2. +- Receiver: accepts one R-OTSi at its input media port, demodulates the R-OTSi (that contains one carrier or one or more OTScSi) and presents one or more instances of M-AI at its output (M-AP). The R-OTSi may have suffered impairments and the integrity of the M-AI extracted by the receiver may be impaired (e.g., by bit errors). + +## 13.2 OTSiG-O trail termination function + +The following generic processes are assigned to the OTSiG-O trail termination function: + +- Assessment of transmission quality; +- Transmission defect detection and indication. + +There are three types of OTSiG-O trail termination function: + +- OTSiG-O bidirectional termination: consists of a pair of collocated OTSiG-O termination source and sink functions; +- OTSiG-O source: accepts the input from the OPM-x associated with the transmitter (if present) and generates the OTSiG-O; +- OTSiG-O sink: processes the OTSiG overhead and the input from the OPM-x associated with the receiver (if present) and generates any OTSiA management information. + +## 13.3 OMS-O trail termination function + +The following generic processes are assigned to the OMS-O trail termination function: + +- Assessment of transmission quality; +- Transmission defect detection and indication. + +There are three types of OMS-O trail termination function: + +- OMS-O bidirectional termination: consists of a pair of collocated optical multiplex section termination source and sink functions; +- OMS-O source: accepts the input from the OPM-x located at the start of the OMS MCG and generates the OMS overhead; +- OMS-O sink: processes the OMS overhead and the input from the OPM-x located at the end of the OMS MCG and generates any OMS management information. + +The bulk property monitoring of the OMS OSME takes place in the co-collocated OPM-x. + +## 13.4 OTS-O trail termination function + +The following generic processes may be assigned to the OTS overhead (OTS-O) trail termination function: + +- Validation of connectivity; note that the OTS-O must arrange for squelching11 all components of the OTS in the event of a validation mismatch; +- Assessment of transmission quality; +- Transmission defect detection and indication. + +There are three types of OTS-O trail termination function: + +- OTS-O bidirectional trail termination: consists of a pair of collocated OTS-O trail termination source and sink functions; +- OTS-O source: accept input from the OPM-x located at the start of the OTS MCG and generates the OTS trail overhead; +- OTS-O sink: accepts input from the OPM-x located at the end of the OTS MCG, processes the OTS overhead contained within the OSC and generates any OTS management information. + +The bulk property monitoring of the OTS OSME takes place in the co-collocated OPM-x. + +# 14 Client/server associations + +## 14.1 M-AI/ client CI adaptation function + +The bidirectional M-AI/ client CI adaptation function is performed by a collocated pair of source and sink M-AI/ client CI adaptation functions. + +The M-AI/client CI adaptation source performs the following processes between its input and its output: + +- Accepts the CI from a digital layer network and performs the processing required to generate one or more instances of M-AI. The actual processes required are dependent on the particular client and the transmitter. Forward error correction is an optional feature, which may be required in cases where impairments (e.g., bit errors) are expected to be present in the M-AI at the output of the receiver; +- Generate any OTSiG-O. + +The M-AI/client CI adaptation sink performs the following processes between its input and its output: + +- Accept the M-AI from one or more receivers (in the OTSiG) and recovers and reassembles the client CI. The actual processes are dependent on the particular client and the receiver. Forward error correction is an optional feature12; +- Accept and process any OTSi overhead from the OTSiG-O trail termination function. + +--- + +11 Note that this requirement can be met by a blocking switch at different locations. It is an equipment design matter to place the switch. + +12 Some of these FEC processes may rely on information extracted from the OTSi by the demodulator. + +## 14.2 OMS-O/OTSiG-O adaptation function + +The bidirectional OMS-O/OTSiG-O adaptation function is performed by a collocated pair of source and sink OMS-O/OTSiG-O adaptation functions. + +The OMS-O/OTSiG-O adaptation source performs the following processes between its input and its output: + +- Generation of management/maintenance digital information streams. + +The OMS-O/OTSiG-O adaptation sink performs the following processes between its input and its output: + +- Termination of management/maintenance digital information streams. + +## 14.3 OTS-O/OMS-O adaptation function + +The bidirectional OTS-O/OMS-O adaptation function is performed by a collocated pair of source and sink OTS-O/OMS-O adaptation functions. + +The OTS-O/OMS-O adaptation source performs the following process between its input and its output: + +- Generation of management/maintenance digital information streams. + +The OTS-O/OMS-O adaptation sink performs the following process between its input and its output: + +- Termination of management/maintenance digital information streams. + +## 14.4 M-AI/OTS-O adaptation + +The bidirectional M-AI/OTS-O adaptation function is performed by a pair of collocated source and sink M-AI/OTS-O adaptation functions. + +The M-AI/OTS-O adaptation source performs the following processes between its input and its output: + +- All the processing required to generate a continuous data stream that can be modulated onto an OTSi. The actual processes required are dependent upon the particular implementation of the client/server. + +The M-AI/OTS-O adaptation sink performs the following processes between its input and its output: + +- Recovery of the digital stream from OSC. The actual processes are dependent upon the particular implementation of the client/server relationship. + +# 15 Management capabilities + +This clause only applies to point-to-point topologies. + +This clause outlines the fault, performance and configuration management capabilities of the media network. At the time this Recommendation was approved, the only transport technology that fully supports the management capabilities described in this clause is the optical transport network (OTN), as described in [ITU-T G.872]. + +## 15.1 Media entity relationships + +The serial concatenation of media channels to form a longer media channel is described in clause 7.1.2. A failure of any media channel that is a part of a serial concatenation will result in the failure of the longer media channel (and hence the loss of any OTSi that are using the failed media channel). + +## 15.2 Fault management + +Fault management is a set of functions, which enables the detection, isolation and correction of abnormal operation of the telecommunication network and its environment. The media network should support the following management capabilities. + +- Continuity supervision; +- Connectivity supervision; +- Maintenance information report. + +### 15.2.1 Continuity supervision + +Continuity supervision refers to the set of processes that monitors the continuity of an MCG. An MCG has no inherent monitoring capability, as described in clause 9.2, an OSME is used to provide monitoring for an MCG. Connectivity supervision is only supported in media networks that support the OPM-pwr. + +A loss of continuity of an MCG may be caused, for example by any combination of, fibre disruptions, equipment failures, or configuration errors. Equipment failures should be detected and reported by the equipment monitoring capabilities. + +The continuity of an OSME is inferred from the presence (or absence) of the OTSi that are intended to be present in that OSME. The OPM-pwr attached to the OSME reference point is used to monitor the total optical power present on the media channel(s). If the optical power observed by the OPM-pwr is less than the minimum expected total power a loss of continuity can be declared. + +NOTE – The OPM-pwr cannot distinguish between the power from (sets of) OTSi and the power from optical noise. Therefore, depending on the network configuration, the location of the fault and the design of the amplifiers, amplified optical noise may prevent the OPM-pwr from detecting a reduction in optical power that is sufficient to declare media channel loss of continuity. + +As described in clause 15.1, the failure of any media channel that is a part of a serial concatenation that forms a longer (emergent) media channel, that is monitored by the OSME, will result in the failure of that longer media channel (and hence the loss of any OTSi that are using the failed media channel). + +### 15.2.2 Connectivity supervision + +Connectivity supervision refers to the set of processes that verify that an MCG has been configured correctly and to ensure that connectivity is properly maintained while the media channel is active. + +Because of the media entity relationships (see clause 15.1), a connectivity fault in an OTS MCG will result in a connectivity fault in the supported OMS MCG, which in turn will result in a connectivity fault for any NMCs which include that OMS MCG. + +Connectivity supervision should be supported on the OTS MCG. Connectivity supervision can only be provided by using the non-associated overhead carried by the OSC, which must be in the same fibre as the OTS MCG or OMS MCG, as described in clause 12. + +Connectivity supervision should also be supported for an NMCG. Connectivity supervision for the NMCG can be provided by using the non-associated overhead or may be inferred from the connectivity monitoring capabilities (e.g., trail trace identifier (TTI)) carried in the client digital payload. + +## 15.3 Configuration management + +As defined in [b-ITU-T G.7710], configuration management provides functions to exercise control over, identify, collect data from and provide data to media elements. Configuration management supports network planning and engineering, installation, service planning and negotiation, provisioning, and status and control. + +In some cases, configuration of media channels, transmitters and receivers may not be supported. Examples of non-configurable applications are those specified in [ITU-T G.959.1], where frequency slots and transmitter central frequencies are fixed. + +For the media network, configuration management includes the configuration of media channels between media ports, OTSiA connection management (see clause 10.3.1), and OPM-x functions. This includes the configuration of media constructs within media elements to provide these associations and monitoring functions. + +### 15.3.1 Unused media channels + +No mechanisms exist for monitoring an unused media channel. Information on the allocation of OTSi to a frequency slot is provided by an administrative process. + +## 15.4 Performance management + +As defined in [b-ITU-T G.7710], performance management provides functions to evaluate and report upon the behaviour of telecommunication equipment and the effectiveness of the network, or NE. Its role is to gather and analyse statistical data for the purpose of monitoring and correcting the behaviour and effectiveness of the network, NEs or other equipment, and to aid in planning, provisioning, maintenance and the measurement of quality. + +Media channels have no monitoring capabilities, the performance of a media channel may be inferred by either observation of the properties of a signal in that media channel (e.g., OSNR) or from the digital information being carried by an OTSi in that media channel (e.g., bit interleaved parity (BIP) or pre-FEC errors). The performance monitoring for single OTSi is shown in Figure 9-3. The definition of performance parameters is outside the scope of this Recommendation. + +## 15.5 Non-associated overhead + +The non-associated overhead in the media network and its relationship to the OTS OSME and OMS OSME is described in clause 11.2. The non-associated overhead may be carried by either the OSC or, an OCN (see [ITU-T G.7712]). The OMS-O includes information on the set of frequency slots that support an OTSiG. The OTSiG information in the OMS-O allows a ROADMs to check that the NMCG and OTSiG-O that support an OTSiA have been configured correctly. + +NOTE – The OTSiG-O digital information may also be supported by an OTSi (as a second client) as described in clause 10.1.1 + +# 16 Media network survivability techniques + +This clause only applies to point-to-point topologies. + +Loss of continuity of an OSME may be used to trigger switching from the failed OSME to a standby OSME. The elements of non-associated overhead that are protected determines which type of protection is provided by a particular implementation. + +Specific survivability techniques include media protection described in the Appendix III of [ITU-T G.873.1] and restoration controlled for example by automatically switched optical network (ASON) or software defined network (SDN), are outside the scope of this Recommendation. + +# 17 Black link approach + +This clause only applies to point-to-point topologies. + +The black link approach is described in [ITU-T G.698.1] and [ITU-T G.698.2]. The specification method used in these Recommendations uses a "black link" approach, which means that optical interface parameters for only (single-channel) optical tributary signals and the transfer function of the media path are specified by a set of application codes. Use of a common application code ensures the compatibility of the media path, transmitter and receiver. This approach enables transverse compatibility at the single-channel point using a direct wavelength multiplexing configuration. However, it does not enable transverse compatibility at the multichannel points. Only a single client CI interface is supported, and the client CI must be supported by a single OTSi. The non-associated overhead for the single client CI interface must be provided by an overhead communications channel (OCC), as defined in [ITU-T G.7712]. + +The black link approach may be used to provide an NMC between a transmitter/receiver pair, as shown in Figure 17-1. The NMC, transmitter and receiver may be provided by different vendors but must all be within the domain of a single network operator. + +The black link approach provides a media channel, which is pre-certified for a particular intra-domain OTSi; the characteristics of this OTSi at the Ss and Rs reference points are defined in [ITU-T G.698.1] and [ITU-T G.698.2]. The media channel has no internal structure visible from either the transmitter or receiver. + +To provide the full set of fault management functions described in clause 15.2, the OTSiG-O must also be supported. However, in this application, it cannot be carried across the complete media network by the OSC, as described in clause 12. To complete the OTSiG-O connection, it is carried across the interface between the OTSiA subnetwork and the transmitter/receiver by an OCC within the overhead communications network (OCN), as shown in Figure 17-1. Within the OTSiA subnetwork the connection of the OTSiG-O and the media channel associations must be coordinated as described in clause 10.3. + +If the OCC is not supported, then OTSiA connection monitoring relies on the client digital stream for certain monitoring functions (e.g., path trace). In this case, the OTSiG-O termination function is located at the edge of the OTSiA subnetwork (i.e., it is not collocated with the transmitter/receiver). Fault isolation and fault correlation must be performed by a management system that has visibility of the end terminals (that contain the transmitter/receiver) and the OTSiA subnetwork (the optical line system). + +NOTE – Ss and Rs in Figure 17-1 identify the reference points defined in [ITU-T G.698.1] and [ITU-T G.698.2]. + +![Diagram of an OTSi subnetwork using the black link approach. It shows two external nodes, OTSiG-O Src and OTSiG-O Sk, connected via MI lines to internal transceivers T and R. These are connected to a 'Network media channel' which leads into an 'OTSiA subnetwork'. The subnetwork contains three 'Media subnetwork' units, each with a 'Media channel'. Above these are OTSiG-O nodes, some 'carried by OSC'. Signal points Ss and Rs are marked at the transceivers. A dashed box labeled OCN and OCC is shown within the external nodes.](12c19090355e19922e23044633b9d1ea_img.jpg) + +The diagram illustrates an OTSi subnetwork architecture using the black link approach. At the top, two external nodes, OTSiG-O Src and OTSiG-O Sk, are shown. Each is connected to an internal transceiver (T on the left, R on the right) via a Management Interface (MI). The transceivers are connected to a 'Network media channel'. Below this channel, the signal enters an 'OTSiA subnetwork', represented by a large oval. Inside the subnetwork, there are three 'Media subnetwork' units, each containing a 'Media channel'. Above each media channel is an OTSiG-O node. The first and third OTSiG-O nodes are connected to the network media channel. The second OTSiG-O node is 'carried by OSC' (Optical Supervisory Channel) from the first node, and the third is 'carried by OSC' from the second. A dashed box labeled 'OCN' (Optical Channel Network) and 'OCC' (Optical Channel Connection) is shown within the external nodes. Signal points Ss and Rs are indicated at the transceivers T and R respectively. + +Diagram of an OTSi subnetwork using the black link approach. It shows two external nodes, OTSiG-O Src and OTSiG-O Sk, connected via MI lines to internal transceivers T and R. These are connected to a 'Network media channel' which leads into an 'OTSiA subnetwork'. The subnetwork contains three 'Media subnetwork' units, each with a 'Media channel'. Above these are OTSiG-O nodes, some 'carried by OSC'. Signal points Ss and Rs are marked at the transceivers. A dashed box labeled OCN and OCC is shown within the external nodes. + +G.807(24) + +**Figure 17-1 – Example OTSi subnetwork using the black link approach** + +# Annex A + +## Media change and physical domain change + +(This annex forms an integral part of this Recommendation.) + +Signals can be classified into different physical domains which have different wave properties, such as acoustical and electromagnetic physical domains. A signal propagating in one physical domain may continue into another physical domain when there is a function capable of performing the change. The media over which a signal propagates within a physical domain may also change. Both types of changes are independent of any information that may be present in the signal. Depicting these changes separately from information transfer is important as the information (if present) is not altered. + +An example of media and physical domain change is the electro/optical (E/O) change. In this case, an EM wave carried on, for example, a pair of copper wires is changed into an optical wave that is carried on an optical fibre. The information (if present) is modulated onto the wave in each physical domain, and those modulations are independent of each other. This is illustrated in Figure A.1: + +![Figure A.1: Media and physical domain change – E/O conversion example. The diagram shows four 'M-AI/client CI' blocks at the top. Below them are four adaptation blocks: 'Modulation X', 'Demodulation X', 'Modulation Y', and 'Demodulation Y'. Thin lines represent information transfer between the client CIs and the adaptation blocks. Thick lines represent media channels. The first two adaptation blocks are connected by an 'Electrical media' channel, with a 'Media port' indicated at the left connection point. The last two adaptation blocks are connected by an 'Optical media' channel. The label 'G.807(24)' is in the bottom right corner.](9cbc1ebd80813fc36e499f7d70ed6881_img.jpg) + +Figure A.1: Media and physical domain change – E/O conversion example. The diagram shows four 'M-AI/client CI' blocks at the top. Below them are four adaptation blocks: 'Modulation X', 'Demodulation X', 'Modulation Y', and 'Demodulation Y'. Thin lines represent information transfer between the client CIs and the adaptation blocks. Thick lines represent media channels. The first two adaptation blocks are connected by an 'Electrical media' channel, with a 'Media port' indicated at the left connection point. The last two adaptation blocks are connected by an 'Optical media' channel. The label 'G.807(24)' is in the bottom right corner. + +**Figure A.1 – Media and physical domain change – E/O conversion example** + +In Figure A.1, the thin lines represent [ITU-T G.800] information transfer. Media is represented by a thick line. The signal, carried by the media, is not represented. Between physical domains, a digital information stream is shown between the top of the adaptations. The electrical signal and OTSi are carried within the media channels of their respective media. + +A change of media may occur in a media element, for example, in a photonic cross connect. This is shown in Figure A.2, where an OTSi is carried, first in an optical fibre, then enters free space, and then continues in a second optical fibre. There is no change to the physical domain. The OTSi traverses a serial concatenation of three media channels, the middle of which is in a different media. + +![Figure A.2: Media change – OTSi example. The diagram shows two 'T/R' blocks at the top, connected by a media path. The path consists of three segments: 'Fibre', 'Free space', and 'Fibre'. The 'Free space' segment is represented by a dashed line and is labeled 'Media change' with a bracket underneath. The label 'G.807(24)' is in the bottom right corner.](9ed248b025d766251d58be10b01a1cc0_img.jpg) + +Figure A.2: Media change – OTSi example. The diagram shows two 'T/R' blocks at the top, connected by a media path. The path consists of three segments: 'Fibre', 'Free space', and 'Fibre'. The 'Free space' segment is represented by a dashed line and is labeled 'Media change' with a bracket underneath. The label 'G.807(24)' is in the bottom right corner. + +**Figure A.2 – Media change – OTSi example** + +# **Annex B** + +## **Concept of network media channel group (NMCG)** + +(This annex forms an integral part of this Recommendation.) + +The network media channel group (NMCG) is a type of MCG that represents the set of NMCs that support the transfer of a single OTSiG. This construct allows management of an NMCG as a single entity. To avoid excessive differential delay, all NMCs in an NMCG should take a common path through the media network. + +Management information associated with the NMCG should indicate the frequency slot reserved for each of the NMCs in the NMCG. The NMCG management information could also include transfer parameters (e.g., differential delay) among these signals carried by the NMCG to help design/manage the network. + +# Annex C + +## Optical Parameter Monitor – power (OPM-pwr) + +(This annex forms an integral part of this Recommendation.) + +The OPM-pwr measures the optical power in the media channel. This measurement includes both the power from any OTSi that are present and the power of the optical noise. The OPM-pwr cannot distinguish the power of OTSi from optical noise. The optical spectrum over which the measurement is made is determined by the frequency slot of the media channel. For example, the frequency slot of the OPM-pwr may encompass the frequency slots of an OMS MCG or OTS MCG and, therefore, will measure the total power of the OTSi present and optical noise on the OMS MCG or OTS MCG. If the frequency slot is set to that of an NMC, then the OPM-pwr will measure the power of the OTSi (if present) and optical noise in that NMC. + +The OPM-pwr observes the optical power present on a media channel and outputs digital information that represents the power of the signal(s) in the monitored media channel. The power level is information about the signal(s) and the optical power monitor function does not access the client CI carried by the signal(s). The signal(s) may not be carrying any client information, but the power level is still a relevant type of information about the signal(s). + +NOTE 1 – Based on the knowledge of the OTSi that are expected to be present, a threshold may be set, which would allow loss of signal (LOS) to be declared. + +When an OPM-pwr is used, the OMS OSME monitors the optical power of the set of OTSi carried by the OMS MCG. The reference points at the end of the OMS OSME are defined by the location of the OMS OPM-pwr. The OMS OPM-pwr are not required to be in the same location as the OMS MCG aggregation/disaggregation. + +The set of OTSi in the OMS MCG and OTS MCG are identical. + +NOTE 2 – The implementation of the OTS OPM-pwr or OMS OPM-pwr may include the ability to detect which frequency slots have an active OTSi. This capability is particularly useful when the frequency slot of the OPM-pwr matches the effective frequency slot of an NMC. The information from this capability may be used for fault isolation in the case where a fault occurs in a frequency selective component and not all of the OTSi being carried by the OTS MCG or OMS MCG are impacted. Further details of other optical monitoring capabilities are provided in [ITU-T G.697]. + +Monitor points are unidirectional. When required, the OMS OSME and OTS OSME can be labelled to indicate at which end of the OSME the signal is being monitored. "UP" will denote monitoring of an optical signal prior to being amplified or entering a filter, and "DOWN" will denote the point after it has traversed amplifier/filter functions. An example is shown in Figure C.1. + +For clarity the OSC is not shown and only a single direction of signal propagation is shown in Figure C.1 and Figure C.2. + +![Schematic diagram of OPM-pwr with discrete amplifiers. The diagram shows a bidirectional optical path between two transceivers (T) and two receivers (R). The path includes optical multiplexers (OMS), optical transport sections (OTS), and an amplifier site. Signal monitors (blue pentagons) divert part of the signal power to the OPM. Media ports (black diamonds) are located at the transceivers, receivers, and within the amplifier site. The amplifier site contains two optical transport sections (OTS) and two amplifiers (F). The diagram is labeled with 'Fibre', 'OMS down', 'OMS up', 'OTS down', 'OTS up', and 'G.807(24)'.](4162c218fc7881cd90fc9574e07d2327_img.jpg) + +The diagram illustrates an optical network configuration with discrete amplifiers. At the left end, two transceivers (T) are connected to an optical multiplexer (OMS). The OMS is connected to a media port (P) labeled 'OMS down'. This port is connected to a signal monitor (blue pentagon). The signal monitor is connected to a media port (P) labeled 'OTS down'. This port is connected to a fibre (F). The fibre is connected to a signal monitor (blue pentagon). The signal monitor is connected to a media port (P) labeled 'OTS up'. This port is connected to an amplifier site. The amplifier site is enclosed in a dashed box and contains two optical transport sections (OTS) and two amplifiers (F). The first OTS is connected to the media port (P) labeled 'OTS up'. The first OTS is connected to a signal monitor (blue pentagon). The signal monitor is connected to a media port (P) labeled 'OTS down'. This port is connected to a fibre (F). The fibre is connected to a signal monitor (blue pentagon). The signal monitor is connected to a media port (P) labeled 'OTS up'. This port is connected to the second OTS. The second OTS is connected to a signal monitor (blue pentagon). The signal monitor is connected to a media port (P) labeled 'OTS down'. This port is connected to a fibre (F). The fibre is connected to a signal monitor (blue pentagon). The signal monitor is connected to a media port (P) labeled 'OTS up'. This port is connected to an optical multiplexer (OMS). The OMS is connected to two receivers (R). The diagram is labeled with 'Fibre', 'OMS down', 'OMS up', 'OTS down', 'OTS up', and 'G.807(24)'. + +Legend: + +- Signal monitor that diverts part of the signal power to the OPM (blue pentagon) +- Media port (black diamond) + +Schematic diagram of OPM-pwr with discrete amplifiers. The diagram shows a bidirectional optical path between two transceivers (T) and two receivers (R). The path includes optical multiplexers (OMS), optical transport sections (OTS), and an amplifier site. Signal monitors (blue pentagons) divert part of the signal power to the OPM. Media ports (black diamonds) are located at the transceivers, receivers, and within the amplifier site. The amplifier site contains two optical transport sections (OTS) and two amplifiers (F). The diagram is labeled with 'Fibre', 'OMS down', 'OMS up', 'OTS down', 'OTS up', and 'G.807(24)'. + +**Figure C.1 – OPM-pwr with discrete amplifiers** + +The case where only distributed amplifiers are used is shown in Figure C.2 below. + +![Diagram of OPM-pwr with distributed amplifiers showing signal flow from transceivers (T) to receivers (R) through optical media elements and fibre, with an amplifier site in the middle.](701bc79e78b382bcfd3ba85597dbb9c3_img.jpg) + +The diagram illustrates an optical transmission system with distributed amplifiers. At the left terminal, two transceivers (T) are connected to a media element via a coupler. The signal path includes an optical media element (F), a pump wavelength insertion point, and a fibre. An amplifier site is shown in the center, enclosed in a dashed box. Inside this site, the signal passes through another optical media element (F), a pump (P) with OTS up and OTS down ports, and another optical media element (F). The signal then continues through a fibre to the right terminal. At the right terminal, the signal passes through an optical media element (F), a pump (P) with OMS up and OTS up ports, and a coupler to two receivers (R). Signal monitors (blue pentagons) are placed at various points to divert part of the signal power to the OPM. Media ports (black diamonds) are shown at the transceivers and pumps. Labels include 'OMS down OTS down', 'OTS OSME', 'OMS OSME', 'Amplifier site', 'Fibre', and 'Pump wavelength insertion'. A legend at the bottom left defines the symbols for signal monitors and media ports. The text 'G.807(24)' is in the bottom right corner. + +Diagram of OPM-pwr with distributed amplifiers showing signal flow from transceivers (T) to receivers (R) through optical media elements and fibre, with an amplifier site in the middle. + +**Figure C.2 – OPM-pwr with distributed amplifiers** + +In the case illustrated in Figure C.2, only distributed amplifiers are used. A single OPM-pwr at a terminal site may provide information on both the OMS OSME and OTS OSME. Also, at the amplifier a single OPM-pwr observes the power at the input to the site and the output from the site. The amplification of the signal takes place in the transmission fibre and one port of the amplifier as at some, indeterminate and inaccessible point, in the transmission fibre. Note that in most cases when distributed amplification is used discrete amplifiers are also used. + +Figure C.3 illustrates the black link approach described in [ITU-T G.698.2] and clause 17. + +![Diagram of OPM-pwr with the black link approach showing signal paths, media ports, and signal monitors across a 'Black link' and an 'Amplifier site'.](89f8aefc01866631793087542316cef2_img.jpg) + +The diagram illustrates the OPM-pwr architecture with a 'black link' approach. It shows two main signal paths, one for transmit (T) and one for receive (R), passing through a 'Black link' and an 'Amplifier site'. + +- Transmit Path (Left):** Starts with a transmit (T) media port. The signal passes through a series of signal monitors (P) and OTS OSME (Optical Transport Section Optical Monitoring Element) points. The path enters the 'Black link' (dashed box) and then the 'Amplifier site' (dashed box). Inside the amplifier site, the signal passes through an amplifier (F) and then exits. The signal then passes through another OTS OSME point and a signal monitor (P) before exiting the 'Black link'. +- Receive Path (Right):** Starts with a receive (R) media port. The signal passes through a series of signal monitors (P) and OTS OSME points. The path enters the 'Black link' and then the 'Amplifier site'. Inside the amplifier site, the signal passes through an amplifier (F) and then exits. The signal then passes through another OTS OSME point and a signal monitor (P) before exiting the 'Black link'. +- OMS OSME:** An OMS OSME (Optical Multiplex Section Optical Monitoring Element) is shown in the center, connected to the signal path between the 'Black link' and the 'Amplifier site'. +- Legend:** + - Signal monitor that diverts part of the signal power to the OPM (represented by a pentagon with a circle inside). + - Media port (represented by a diamond with a circle inside). +- Labels:** + - T: Transmit media port. + - R: Receive media port. + - P: Signal monitor. + - OTS down, OTS up: OTS OSME points. + - OTS OSME: Optical Transport Section Optical Monitoring Element. + - Ss, Rs: Reference points. + - "Black link": The main transmission path. + - OMS OSME: Optical Multiplex Section Optical Monitoring Element. + - OMS down, OMS up: OMS OSME points. + - Amplifier site: Contains amplifiers (F). + - Fibre: The optical fiber medium. + - G.807(24): Reference number. + +Diagram of OPM-pwr with the black link approach showing signal paths, media ports, and signal monitors across a 'Black link' and an 'Amplifier site'. + +**Figure C.3 – OPM-pwr with the black link approach** + +The OTS OSME (and the associated OPM-pwr) on the inputs and output of the "black link" only support a single OTSi. Figure C.3 illustrates one case where reference points are inside a media element, but the "logical" location of those reference points must be exposed, so that the architecture and the information model derived from it are consistent. + +# Appendix I + +## Examples of the configuration of media channels + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Construction of network media channels + +An example of construction of NMCs is provided in Figure I.1. + +![Diagram illustrating the construction of network media channels (NMCs) using filters (F1-F6) and transmitters/receivers (T/R). The diagram shows three media links (A, B, C) and the flow of NMCs through filters. A legend at the bottom identifies T as Transmitter, R as Receiver, and F as Filter. The diagram is labeled G.807(24).](cc6f9dbfc36aa5821d9749ca84861f93_img.jpg) + +The diagram illustrates the construction of network media channels (NMCs) using filters (F1-F6) and transmitters/receivers (T/R). The diagram shows three media links (A, B, C) and the flow of NMCs through filters. A legend at the bottom identifies T as Transmitter, R as Receiver, and F as Filter. The diagram is labeled G.807(24). + +Legend: + +- T Transmitter +- R Receiver +- F Filter + +Diagram illustrating the construction of network media channels (NMCs) using filters (F1-F6) and transmitters/receivers (T/R). The diagram shows three media links (A, B, C) and the flow of NMCs through filters. A legend at the bottom identifies T as Transmitter, R as Receiver, and F as Filter. The diagram is labeled G.807(24). + +**Figure I.1 – Network media channel construction** + +The OMS MCGs shown in blue provides connectivity between the different sites. The filters F1-F6 aggregate and disaggregate the media channels. + +F1 aggregates the red, blue and green NMCs into OMS MCG A. + +F2 disaggregates the green NMC and the yellow media channel (that aggregates the red and blue media channels) from OMS MCG A. + +F3 aggregates the orange and purple media channels into OMS MCG B. + +F4 disaggregates the red purple and blue NMCs from OMS MCG B. + +F5 aggregates the blue NMC into OMS MCG C. + +F6 disaggregates the blue NMC from OMS MCG C. + +### I.2 Use of configurable filters to route media channels + +The ability to configure atomic media channels within a configurable filter can be used to modify or create a route for a media channel across the network. + +The configuration of a media channel includes both the creation and deletion of a media channel and defining its frequency slot (by configuring the nominal central frequency and a slot width). + +Consider, for example, a filter with the initial configuration of the media channels in as illustrated in Figure I.2. + +![Diagram of initial filter configuration showing port 1 connected to ports 2, 3, and 4 via red, purple, and green channels respectively. The diagram is labeled G.807(24).](cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg) + +The diagram shows a filter represented by a gray trapezoidal shape. At the bottom vertex, there is a black diamond labeled '1'. At the top edge, there are three black diamonds labeled '2', '3', and '4'. A red line connects port 1 to port 2, a purple line connects port 1 to port 3, and a green line connects port 1 to port 4. The label 'G.807(24)' is located to the right of the filter. + +Diagram of initial filter configuration showing port 1 connected to ports 2, 3, and 4 via red, purple, and green channels respectively. The diagram is labeled G.807(24). + +**Figure I.2 – Initial filter configuration** + +The filter disaggregates the media channel at port 1 into: + +- A red media channel that is delivered to port 2; +- A purple media channel that is delivered to port 3; +- A green media channel that is delivered to port 4. + +The atomic media channels within the filter may be reconfigured as shown in Figure I.3: + +![Diagram of modified filter configuration showing port 1 connected to ports 2, 3, and 4 via blue, red, and green channels respectively. The diagram is labeled G.807(24).](c419b566d720267c499087add1506018_img.jpg) + +The diagram shows the same filter as in Figure I.2, but with different channel colors. A blue line connects port 1 to port 2, a red line connects port 1 to port 3, and a green line connects port 1 to port 4. The label 'G.807(24)' is located to the right of the filter. + +Diagram of modified filter configuration showing port 1 connected to ports 2, 3, and 4 via blue, red, and green channels respectively. The diagram is labeled G.807(24). + +**Figure I.3 – Modified filter configuration** + +The filter disaggregates the media channel at port 1 into: + +- A blue media channel that is delivered to port 2; +- A red media channel that is delivered to port 3; +- A green media channel that is delivered to port 4. + +It is also possible to reconfigure the slot width of an atomic media channel without changing the nominal central frequency. + +# Appendix II + +## Example of media network using tuneable transmitter/receiver for routing + +(This appendix does not form an integral part of this Recommendation.) + +### II.1 Network using coupler-splitters + +A media network may be constructed using tuneable sources, frequency selective receivers and coupler-splitters (with amplifiers to compensate for the loss of the coupler-splitters). This architecture has limitations, in that frequency slots cannot be reused across the network. However, in the case of a simple linear add/drop chain where the traffic demands are predominantly from a hub site to downstream remote sites, this approach can simplify network operations. + +A simple example of such a network is provided in Figure II.1. + +![Diagram of a simple network example using coupler-splitters.](237b76118be454462fc9b4e96adaa6c7_img.jpg) + +The diagram illustrates a linear network topology across four sites, each enclosed in a dashed box. Site 1 contains three transmitters (T) labeled Red, Brown, and Green, all connected to a coupler C1. Site 2 contains a receiver (R) labeled Red connected to a splitter S2. Site 3 contains a receiver (R) labeled Brown and a transmitter (T) labeled Purple connected to a splitter S3. Site 4 contains two receivers (R) labeled Green and Purple connected to a splitter S5. The main backbone consists of coupler C1, splitter S2, splitter S3, coupler C4, and splitter S5 connected in series. Blue lines represent the optical paths. A label 'G.807(24)' is present in the bottom right corner. + +Diagram of a simple network example using coupler-splitters. + +Figure II.1 – Simple network example + +In this simple example, each modulator source and configurable filter are able to provide an OTSi in any defined frequency slot and the coherent receivers are able to select an OTSi from a specific frequency slot. Couplers C1 and C4 aggregate media channels. Splitters S2, S3 and S5 duplicate the media channel to provide two or more copies. + +The coupler-splitters provide a point-to-multipoint media channel between site 1 and all downstream sites. Coupler C4 in site 3 allows any attached source to use the point-to-multipoint media channel between sites 3 and 4 (or any other downstream sites). When the (restricted spectrum) of the source and the effect of the filter in the coherent receiver are considered, a point-to-point NMC is established between a specific modulator and demodulator, which supports a point-to-point communication. + +### II.2 Network using wide-band filters and coupler-splitters + +Coupler-splitters provide complete flexibility, in that all frequency slots are delivered to all sites. They have the disadvantages of high loss and that frequency slots cannot be reused within the network. In the example of Figure II.1, if S3 were replaced by a filter that that split the available spectrum between its output ports, then it would result in lower loss to both output ports and would allow the frequency slots that are dropped at site 3 to be reused downstream. However, some flexibility would be lost (i.e., some frequency slots from sites 1 and 2 are always delivered to site 3, while the remaining frequency slots are not delivered to site 3). The connectivity of the network is now constrained by the (wideband) filter and controlled by the selection of the frequency slot used by the modulator and demodulator. + +# Appendix III + +## Examples for transferring digital data over different media + +(This appendix does not form an integral part of this Recommendation.) + +### III.1 Specific kinds of modulation/demodulation + +As described in clause 9, functions at information/signal boundary are represented diagrammatically with the symbol ![A small downward-pointing arrow symbol.](4d7832f32da92348575447a4aae88cd6_img.jpg). Table III.1 describes some functions that are used in examples later in this appendix. + +**Table III.1 – Examples of functions at information/signal boundary** + +| Function | Input | Output | +|-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Signal Quantization (analogue to digital (A/D)) | A signal (with or without digital information modulated on it). | A digital information stream containing a sampled and quantized representation of the input waveform. | +| Signal recreation (digital to analogue (D/A)) | A digital information stream containing a sampled and quantized representation of the waveform. | A signal. The degree of similarity to the original signal form is a function of sampling and quantization parameters (e.g., sampling rate). | +| In-phase and quadrature-phase (I/Q) sampling | A modulated signal. | Two digital information streams, one representing the in-phase (I) and the other the quadrature (Q) components of the signal. | +| Signal recreation (I/Q) | Two digital information streams, one representing the in-phase (I) and the other the quadrature (Q) components of the signal. | A modulated signal. | + +### III.2 Digitized IF-band case + +Figure 6-4b of [b-ITU-T G Suppl. 55] is examined in Figure III.1. The digital-to-digital converter function is intended to output the payload data as if modulated on an IF carrier but digitally represented. After the D/A converter, the IF to RF band conversion occurs using a frequency mixer followed by an anti-aliasing filter to produce the RF-band signal output. + +![Figure III.1 – Digital radio over fibre: digitized IF-band signal. This diagram shows two configurations. Part (b) is a full duplex system where downlink payload data (digital baseband) is modulated by a Digital IF-band modulator to create a downlink digitized IF-band subcarrier. This is sent via an Optical transceiver (E/O converter and MUX/DEMUX) over a Fibre-optic link. On the receive side, the signal is demodulated by another Optical transceiver (MUX/DEMUX and O/E converter) to produce an uplink digitized IF-band subcarrier, which is then demodulated by a Digital IF-band demodulator to yield uplink payload data (digital baseband). A reference frequency is used for up/down conversion. Part (a) shows a simplified downlink path: Data in digital baseband is converted by a Digital to digital converter to produce digitized I/Q samples, which are then transmitted via an Optical transmitter over a Fibre-optic link. The signal is received by an Optical receiver, converted by a D/A converter to produce analogue I&Q signals, which are then mixed with a Ref frequency in a Frequency mixer and filtered by an RF-band filter to produce the Downlink RF signal. A large orange arrow indicates the Direction of transmission from left to right. The label G.807(24) is present in the bottom right.](c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg) + +Figure III.1 – Digital radio over fibre: digitized IF-band signal. This diagram shows two configurations. Part (b) is a full duplex system where downlink payload data (digital baseband) is modulated by a Digital IF-band modulator to create a downlink digitized IF-band subcarrier. This is sent via an Optical transceiver (E/O converter and MUX/DEMUX) over a Fibre-optic link. On the receive side, the signal is demodulated by another Optical transceiver (MUX/DEMUX and O/E converter) to produce an uplink digitized IF-band subcarrier, which is then demodulated by a Digital IF-band demodulator to yield uplink payload data (digital baseband). A reference frequency is used for up/down conversion. Part (a) shows a simplified downlink path: Data in digital baseband is converted by a Digital to digital converter to produce digitized I/Q samples, which are then transmitted via an Optical transmitter over a Fibre-optic link. The signal is received by an Optical receiver, converted by a D/A converter to produce analogue I&Q signals, which are then mixed with a Ref frequency in a Frequency mixer and filtered by an RF-band filter to produce the Downlink RF signal. A large orange arrow indicates the Direction of transmission from left to right. The label G.807(24) is present in the bottom right. + +**Figure III.1 – Digital radio over fibre: digitized IF-band signal** + +### III.3 Digitized I/Q baseband case + +This is an example from Figure 6-4c of [b-ITU-T G Suppl. 55] which is examined in Figure III.2. Here, the payload data is input to a digital I/Q modulator that is a digital-to-digital function whose outputs are digitized I and Q streams that are input to an optical modulator. After the digital radio-over-fibre (RoF) is demodulated from the optical domain into the electrical domain, it is input to a D/A converter (DAC) to yield two analogue I&Q signals. These are then converted to a radio frequency (RF) signal. The symbol with the label "I/Q modulator" is a type of modulator with analogue, not digital, inputs. + +![Figure III.2 – Digital radio over fibre: digitized I/Q baseband signal. This diagram shows two configurations. Part (c) is a full duplex system where downlink payload data (digital baseband) is modulated by a Digital I/Q modulator to create downlink digitized I/Q baseband signals. These are sent via an Optical transceiver (E/O converter and MUX/DEMUX) over a Fibre-optic link. On the receive side, the signal is demodulated by another Optical transceiver (MUX/DEMUX and O/E converter) to produce uplink digitized I/Q baseband signals, which are then demodulated by a Digital I/Q demodulator to yield uplink payload data (digital baseband). A reference frequency is used for up/down conversion. Part (a) shows a simplified downlink path: Data in digital baseband is converted by a Digital to digital converter to produce digitized I/Q samples, which are then transmitted via an Optical transmitter over a Fibre-optic link. The signal is received by an Optical receiver, converted by a D/A converter to produce analogue I&Q signals (labeled 'Analogue signal (I&Q)' and 'Copper wire'), which are then modulated by an I/Q modulator with a Ref frequency to produce the Downlink RF signal. A large orange arrow indicates the Direction of transmission from left to right. The label G.807(24) is present in the bottom right.](efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg) + +Figure III.2 – Digital radio over fibre: digitized I/Q baseband signal. This diagram shows two configurations. Part (c) is a full duplex system where downlink payload data (digital baseband) is modulated by a Digital I/Q modulator to create downlink digitized I/Q baseband signals. These are sent via an Optical transceiver (E/O converter and MUX/DEMUX) over a Fibre-optic link. On the receive side, the signal is demodulated by another Optical transceiver (MUX/DEMUX and O/E converter) to produce uplink digitized I/Q baseband signals, which are then demodulated by a Digital I/Q demodulator to yield uplink payload data (digital baseband). A reference frequency is used for up/down conversion. Part (a) shows a simplified downlink path: Data in digital baseband is converted by a Digital to digital converter to produce digitized I/Q samples, which are then transmitted via an Optical transmitter over a Fibre-optic link. The signal is received by an Optical receiver, converted by a D/A converter to produce analogue I&Q signals (labeled 'Analogue signal (I&Q)' and 'Copper wire'), which are then modulated by an I/Q modulator with a Ref frequency to produce the Downlink RF signal. A large orange arrow indicates the Direction of transmission from left to right. The label G.807(24) is present in the bottom right. + +**Figure III.2 – Digital radio over fibre: digitized I/Q baseband signal** + +### III.4 Analogue RoF case + +The case is to consider analogue radio-over-fibre (RoF). Figure 6-1a of [b-ITU-T G Suppl. 55] is illustrated in Figure III.3. The input to the optical modulator is an analogue RF signal. This is outside + +the scope of [ITU-T G.800] architecture but should be considered in this Recommendation. The functions performed are taking radio baseband and converting it first to an RF-band signal, then modulating that to an optical signal. At the optical receiver, the demodulator recovers the RF-band signal. As with the in-phase and quadrature-phase (I/Q) to RF converter, this is a direct analogue signal to analogue signal conversion. + +![Figure III.3 – Analogue radio over fibre: RF-band. The diagram consists of two parts. Part (a) shows a bidirectional system: on the left, 'Downlink payload data (digital baseband)' goes through an 'RF-band modulator' to become a 'Downlink RF-band subcarrier', which enters an 'E/O converter'. Conversely, an 'Uplink RF-band subcarrier' comes from an 'O/E converter' to an 'RF-band demodulator' to become 'Uplink payload data (digital baseband)'. These converters are part of an 'Optical transceiver' and connect to a 'MUX/DEMUX' which interfaces with a 'Fibre-optic link' (Analogue RoF). The right side mirrors this with another 'Optical transceiver' containing a 'MUX/DEMUX', 'O/E converter', and 'E/O converter', leading to 'RF-band filters' for Downlink and Uplink RF signals. Part (b) shows a unidirectional flow from left to right: 'Data in digital baseband' -> 'electrical modulator' -> 'RF-band subcarrier' (over 'Copper wire') -> 'Optical transmitter' -> 'Analogue RoF' (over 'Fibre') -> 'Optical receiver' -> 'RF-band filter' -> 'Downlink RF signal'. A large orange arrow at the bottom indicates the 'Direction of transmission'.](3766b291e69420b0437ae278b057b5ee_img.jpg) + +``` + +graph LR + subgraph Part_B [Part b] + A[Data in digital baseband] --> B[electrical modulator] + B --> C{RF-band subcarrier +Copper wire} + C --> D[Optical transmitter] + D --> E{Analogue RoF +Fibre} + E --> F[Optical receiver] + F --> G[RF-band filter] + G --> H[Downlink RF signal] + end + +``` + +a) + +Direction of transmission + +G.807(24) + +Figure III.3 – Analogue radio over fibre: RF-band. The diagram consists of two parts. Part (a) shows a bidirectional system: on the left, 'Downlink payload data (digital baseband)' goes through an 'RF-band modulator' to become a 'Downlink RF-band subcarrier', which enters an 'E/O converter'. Conversely, an 'Uplink RF-band subcarrier' comes from an 'O/E converter' to an 'RF-band demodulator' to become 'Uplink payload data (digital baseband)'. These converters are part of an 'Optical transceiver' and connect to a 'MUX/DEMUX' which interfaces with a 'Fibre-optic link' (Analogue RoF). The right side mirrors this with another 'Optical transceiver' containing a 'MUX/DEMUX', 'O/E converter', and 'E/O converter', leading to 'RF-band filters' for Downlink and Uplink RF signals. Part (b) shows a unidirectional flow from left to right: 'Data in digital baseband' -> 'electrical modulator' -> 'RF-band subcarrier' (over 'Copper wire') -> 'Optical transmitter' -> 'Analogue RoF' (over 'Fibre') -> 'Optical receiver' -> 'RF-band filter' -> 'Downlink RF signal'. A large orange arrow at the bottom indicates the 'Direction of transmission'. + +**Figure III.3 – Analogue radio over fibre: RF-band** + +# Appendix IV + +## Example for describing media network topology + +(This appendix does not form an integral part of this Recommendation.) + +The initial network topology of the media network comprises all available resources (e.g., all frequency slots). A topology instance is derived from the initial network topology by selecting those topological components, modulators and demodulators that support a specific set of parameters (e.g., a frequency slot). Any media components that do not support the selected parameter values are removed from the initial topology graph. Similarly, any unreachable media subnetworks are removed. The resulting topology now shows available connectable resources. + +For example, selecting a particular frequency slot for an OTSi removes all resources operating at different frequencies from the initial topology graph. The resulting topology instance now shows available connectable media channels that support the selected frequency slot. Determining whether the NMC provided by this topology instance will actually support communication between a modulator and a demodulator is outside the scope of this Recommendation. + +The process of removing resources operating at different frequencies or that result in paths that are not viable (i.e., cannot support the intended OTSi) may result in a topology graph that has isolated domains. Electrical regeneration (3R) can be used to provide connectivity for the client digital stream that is modulated onto the OTSi between isolated instances of the media topology. Since the regenerator terminates the OTSi and generates a new OTSi it can provide functions such as, frequency slot translation, changes in the modulation and/or forward error correction. When required, electrical regeneration must be applied to all of the OTSi in an OTSiG. In the topology regeneration can be represented by a topological construct that represents the means of transforming between disjoint domains. This is similar to the transitional link described in [ITU-T G.800]. + +# Appendix V + +## Assessing media architecture with PON use cases + +(This appendix does not form an integral part of this Recommendation.) + +### V.1 PON signal in an ODN + +The broadband passive optical network (B-PON, in ITU-T G.983-series), gigabit-capable passive optical network (G-PON, in ITU-T G.984-series) and next generation passive optical network (NG-PON in ITU-T G.987-series and G.989-series) Recommendations in SG15 use the optical distribution network (ODN) as defined in [b-ITU-T G.989]. + +**Optical distribution network (ODN):** A point-to-multipoint optical fibre infrastructure. A simple ODN is entirely passive and is represented by a single-rooted point-to-multipoint tree of optical fibres with splitters, combiners, filters and possibly other passive optical components. A composite ODN consists of two or more passive segments interconnected by active devices, each of the segments being either an optical trunk line segment or an optical distribution segment. A passive optical distribution segment is a simple ODN itself. Two ODNs with distinct roots can share a common subtree. + +Splitters, combiners, and filters are some of the media constructs described in [b-ITU-T G.989], although the splitter and coupler are described more generally in the coupler-splitter construct described in this Recommendation. Figure V.1 shows a portion of the optical distribution network (ODN) from Figure 5-1 of [b-ITU-T G.989]. In B-PON and G-PON, a signal is sent from the OLT (optical line termination, a network element that is the root of at least one ODN) to multiple ONUs (optical network units, a network element that terminates a leaf in an ODN). Conventionally, this is the downstream direction. It propagates in a single fibre to a splitter where the entire signal is split with each output signal propagated on its own fibre to an ONU. An individual ONU extracts information from the signal (in a TDM payload) that is assigned to it. In the upstream direction, signals from each of the ONUs (at a different optical frequency from the downstream signal) are combined in the coupler. A ranging function is performed for each ONU to determine its distance (and hence propagation delay) from the OLT. This enables ONUs to send information upstream that arrives in a timeslot at the OLT which is allocated to be for traffic originating from that ONU. The effect is that ONU upstream traffic is time-division multiplexed at the OLT. The OLT is able to determine from the information stream, what data was sent from which ONU. + +Figure V.1 also depicts PON signals that would be representative of B-PON [b-ITU-T G.983.1] and G-PON [b-ITU-T G.984.1] systems. + +![Diagram of a PON system and signal flow in an ODN.](3b6177b1edfdc8c7740f03f346d7838f_img.jpg) + +The diagram illustrates a PON system architecture. At the top, a large box labeled 'PON system' contains an OLT (Optical Line Terminal) connected to an SNI (Service Node Interface). The OLT connects to a 'Composite ODN' (Optical Distribution Network). Inside the Composite ODN, there is an OTL (Optical Trunk Line) leading to an RE (Reach Extender) and then to a Splitter within an 'ODS (simple ODN)'. Another path goes through an RE to a second Splitter. These splitters connect to multiple ONUs (Optical Network Units), which in turn connect to UNIs (User Network Interfaces). A separate 'ODS (simple ODN)' is shown below the composite one, containing a single splitter connecting the OLT to more ONUs. The entire setup is labeled 'Access network (AN) [b-ITU-T G.902]'. + +Below the main architecture, two smaller diagrams show signal flow. The left one shows an OLT sending a signal through a 'Splitter' to three ONUs, labeled 'BPON, GPON'. The right one shows three ONUs sending signals through a 'Coupler' back to an OLT, also labeled 'BPON, GPON'. + +**Figure V.1 – PON signal in an ODN** + +Diagram of a PON system and signal flow in an ODN. + +**V.2 NG-PON2** + +NG-PON2 is defined in [*b-ITU-T G.989*] as: + +**NG-PON2:** A PON system with a nominal aggregate capacity of 40 Gbit/s in the downstream direction and 10 Gbit/s in the upstream direction, and implementing the suite of protocols specified in the ITU-T G.989-series of Recommendations. An NG-PON2 system is composed of a set of TWDM channels and/or a set of PtP WDM channels. + +Time and wavelength division multiplexing (TWDM) is an acronym used in [*b-ITU-T G.989*]. The point-to-point WDM PON capability with the wavelength-selection function in the ONU, is examined in Figure V.2 from the perspective of optical media architecture. The following are definitions from [*b-ITU-T G.989*]: + +**PtP WDM channel:** In an NG-PON2 system, PtP WDM channel refers to the pair of one downstream wavelength channel and one upstream wavelength channel providing point-to-point connectivity. + +**PtP WDM PON:** A multiple wavelength PON system that enables point-to-point connectivity using a dedicated wavelength channel per ONU for the downstream direction and a dedicated wavelength channel per ONU for the upstream direction. + +**Wavelength multiplexer (WM):** A bidirectional functional element used to multiplex/demultiplex between NG-PON2 wavelength channel pairs and channel groups. + +58 Rec. ITU-T G.807 (10/2024) + +Each ONU has a tuneable transmitter and tuneable receiver and is served by a pair of upstream and downstream wavelengths dedicated to that ONU. As shown in Figure A.1 of [b-ITU-T G.989.2], the "wavelength selector can be located physically either within the ONU (wavelength selected case) or at a BN (wavelength routed case)". In the wavelength selected case, the section function is in the ONU and is determined in an activation process that involves the OLT. "The upstream wavelength is typically established as a fixed function of the assigned downstream wavelength". This pair of wavelengths is known as a PtP WDM channel. + +As noted in the NG-PON2 definition above, TWDM channels are also supported: + +**TWDM channel:** In an NG-PON2 system, TWDM channel refers to the pair of one downstream wavelength channel and one upstream wavelength channel providing point-to-multipoint connectivity by using, respectively, time division multiplexing and multiple access mechanisms. + +**TWDM PON:** A multiple wavelength PON system in which each wavelength channel may be shared among multiple ONUs by employing time division multiplexing and multiple access mechanisms. + +In Figure V.2, wavelengths from OLTs are combined into a common fibre. The coupler-splitter represents this. The branching node is a power splitter which may also have a bandpass filter associated with it for instance to remove the TWDM-PON wavelengths. There is a filter for each ONU that is part of the wavelength selection function. + +![Diagram of PtP WDM PON downstream architecture showing multiple OLTs connected to a wavelength mux (WM), which is then connected to a branching node. The branching node is controlled by a lambda selection function and connects to multiple ONUs. A legend defines CG as channel group, CP as channel pair, and WM as wavelength mux.](742a5484e7dd016256ab99921bbd635d_img.jpg) + +The diagram illustrates the downstream path for PtP WDM PON. On the left, multiple PtP WDM OLTs are shown, each connected to a Wavelength Mux (WM) via a channel pair (S/R-CP1, S/R-CP2, S/R-CP3, ..., S/R-CPn). The WM combines these into a single output. This output enters a 'Branching node'. Above the branching node is an oval labeled 'λ selection function' with arrows pointing to the node. The branching node then splits the signal into four PtP WDM ONUs. Below the diagram, a legend defines: + + +- CG – channel group +- CP – channel pair +- WM – wavelength mux + + The reference G.989.2(14)\_FA.1 is noted in the bottom right of the diagram area. + +Diagram of PtP WDM PON downstream architecture showing multiple OLTs connected to a wavelength mux (WM), which is then connected to a branching node. The branching node is controlled by a lambda selection function and connects to multiple ONUs. A legend defines CG as channel group, CP as channel pair, and WM as wavelength mux. + +![Diagram of PtP WDM PON downstream architecture showing three OLTs connected to a Wavelength MUX, which is then connected to a Splitter. The Splitter output is connected to three Filters, which then connect to three ONUs.](91134b9a38d7f73f03375473e7b706f9_img.jpg) + +This diagram shows a simplified version of the downstream path. Three OLTs (represented by red, green, and purple arrows) enter a 'Wavelength MUX'. The output of the MUX enters a 'Splitter'. The output of the Splitter then passes through three individual 'Filters', each corresponding to one of the original wavelengths. The output of each filter is an ONU. The reference G.807(24) is noted in the bottom right of the diagram area. + +Diagram of PtP WDM PON downstream architecture showing three OLTs connected to a Wavelength MUX, which is then connected to a Splitter. The Splitter output is connected to three Filters, which then connect to three ONUs. + +Figure V.2 – PtP WDM PON downstream + +# Appendix VI + +## Assessing media architecture with the visible light communication use case + +(This appendix does not form an integral part of this Recommendation.) + +[b-ITU-T G.991] specifies the "system architecture and functionality for all components of the physical (PHY) layer and data link layer (DLL) of visible light communication (VLC) transceivers for in-premises applications designed for the high-speed optical wireless transmission of data using visible light." + +In [b-ITU-T G.991], the media is free space. Wavelength band is defined: + +**Wavelength band:** A specific range of the wavelength of light that is associated with a domain. Multiple wavelength bands may be used in the same domain. The wavelength band is defined by a lower wavelength and upper wavelength. + +The wavelength band represents the same concept as the frequency slot described in this Recommendation. As described in clause 6.2.1, a wavelength band could be converted to an equivalent frequency slot. Two wavelength bands are defined in [b-ITU-T G.991], which are visible light (380 nm-780 nm) and infrared (800 nm-1 675 nm). + +Sender to receiver topologies include point to point, point to multipoint, and multipoint to multipoint. The physical layer is modelled after [b-ITU-T G.9960], but the medium-dependent interface is to free space media and VLC signals. + +Two modulations are described in [b-ITU-T G.991]. Figure VI.1 shows the ACO-OFDM modulation from Figure 9-1 of [b-ITU-T G.991] with an [ITU-T G.807] representation shown in parallel. + +![Functional model of PHY and ITU-T G.807 media equivalent diagram. The diagram shows the flow of data from MPDU in through the Physical coding sublayer (PCS), Physical media attachment (PMA), and Physical medium dependent (PMD) to LEDs. It also shows the ITU-T G.807 media equivalent path from a MAC frame through an M-AI/MAC and a T (ACO-OFDM) block to an OTSi in free space. Control data from a central PHY management block is shown for each layer.](1b23b78336d8bd286c653cbdb38428dd_img.jpg) + +The diagram illustrates the functional model of the PHY and its ITU-T G.807 media equivalent. It is divided into two main vertical paths. + +**Left Path (Standard PHY Model):** + +- MPDU in** enters the **Physical coding sublayer (PCS)** (generation of PHY-frame, mapping MAC frames into the PHY-frame) from above. +- The PCS outputs a **TX PHY frame** downwards to the **Physical media attachment (PMA)** (scrambling, FEC, segmentation to OFDM symbols, padding). +- The PMA outputs **TX symbol frames** downwards to the **Physical medium dependent (PMD)** (subcarrier mapping, constellation encoding, ACO-OFDM modulation, preamble insertion). +- The PMD outputs data to **LEDs** at the **MDI** (Media Dependent Interface). +- Return paths are indicated by upward arrows: **RX PHY frame** from PMA to PCS, and **RX symbol frames** from PMD to PMA. +- The final output is **MPDU out** from the PCS. +- A vertical **PHY management** line on the right of this path provides control data to each layer: **PCS control data**, **PMA control data**, and **PMD control data**. +- Reference points are marked with dashed horizontal lines: **PMI** (above PCS), **α-reference point** (between PCS and PMA), **δ-reference point** (between PMA and PMD), and **MDI** (at the LED interface). + +**Right Path (ITU-T G.807 Media Equivalent):** + +- A **MAC frame** enters the **M-AI/MAC** block. +- The M-AI/MAC outputs **Tx symbols at the δ-reference point to the PMD** to a **T (ACO-OFDM)** block. +- The T (ACO-OFDM) block outputs to an **OTSi** (Optical Transport Service Interface), which is located in **Free space**. + +The diagram is labeled **G.807(24)** at the bottom right. + +Functional model of PHY and ITU-T G.807 media equivalent diagram. The diagram shows the flow of data from MPDU in through the Physical coding sublayer (PCS), Physical media attachment (PMA), and Physical medium dependent (PMD) to LEDs. It also shows the ITU-T G.807 media equivalent path from a MAC frame through an M-AI/MAC and a T (ACO-OFDM) block to an OTSi in free space. Control data from a central PHY management block is shown for each layer. + +**Figure VI.1 – [b-ITU-T G.9991] functional model of PHY and ITU-T G.807 media equivalent** + +# Appendix VII + +## OMS/OTS reference points and reference points in other Recommendations + +(This appendix does not form an integral part of this Recommendation.) + +OMS and OTS OSME reference points are defined in this Recommendation for monitoring optical signals, while other Recommendations also define reference points, for example to indicate the location where optical parameters are defined. This appendix describes the relationship by comparing the positions of reference points in different optical network scenarios. + +In clause 6 of [ITU-T G.680], main path interface – multichannel reference point at the one output (MPI-SM) and main path interface – multichannel reference point at the one input (MPI-RM) are described as two different multichannel reference points on the optical fibre. MPI-SM usually exists after the optical network element transport interface output optical connector, and MPI-RM exists before the interface input connector. + +One difference between the OMS/OTS OSME reference points and MPI-SM/MPI-RM is the former may exist as a built-in function in the media element, while the latter are external to the media element. Therefore, it could be concluded that there is no direct relationship between the monitoring reference point defined in this Recommendation and [ITU-T G.680]. This is also the same case to the reference point defined in [ITU-T G.698.2] for black link and [b-ITU-T G.661] for amplifier. + +[ITU-T G.697] defines several external monitoring points (EMPs) for maintenance purposes. An example of positioning these EMP can be found in clause IV.4 of [ITU-T G.697], which is copied as Figure VII.1. It can be derived from the figure that the EMPs can be placed after the OM, or before the OD, or before/after amplifiers within the media element. These EMPs can be selected as OSME reference points for different purpose, e.g., EMP 1 and 8 can be selected as OMS OSME, EMP 2 and 3 can be selected as OTS OSME. Specific monitor position for optical power or OSNR can be found in Table IV.1 of [ITU-T G.697]. + +![Diagram of a two-stage line amplifier showing external monitoring point (EMP) positions.](ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg) + +The diagram illustrates a two-stage line amplifier system. It consists of three main blocks: an input block, a central 'Two-stage line amplifier' block, and an output block. The input block contains two sets of 'Single channel interfaces' (Rx, Tx λ1 and Rx, Tx λN) connected to an Optical Multiplexer (OM). The output block contains two sets of 'Single channel interfaces' (Rx λ1, Tx and Rx λN, Tx) connected to an Optical Demultiplexer (OD). The central 'Two-stage line amplifier' block is divided into two parallel paths. The top path contains a Booster amplifier (B), a Dispersion Compensating Module (DCM), and a Preamplifier (P). The bottom path contains an Optical Demultiplexer (OD), a Preamplifier (P), a DCM, and a Booster amplifier (B). Red dots indicate possible EMP positions at various points: 1. After the OM in the input block. 2. Before the B in the top path. 3. After the B in the top path. 4. Before the DCM in the top path. 5. After the DCM in the top path. 6. Before the P in the top path. 7. After the P in the top path. 8. Before the OD in the output block. The legend defines: B = Booster amplifier, P = Preamplifier, ● = Possible EMP position, Tx = Transmitter, Rx = Receiver, DCM = Dispersion compensating module. The diagram is labeled G.807(20)\_FVII.1. + +Diagram of a two-stage line amplifier showing external monitoring point (EMP) positions. + +Figure VII.1 – Example of external monitoring point positioning + +# Appendix VIII + +## Description of inverse multiplexed clients + +(This appendix does not form an integral part of this Recommendation.) + +Table VIII.1 provides some examples of the application of the media architecture to the description of inverse multiplexed digital clients, that use a variety of physical implementations. + +**Table VIII.1 – Example of assignment of OTSiG to a media channel** + +| Digital client | Number of fibres/
wavelengths per fibre | Number of OTSiG in
the OTSiG | Number of NMC in
the NMCG | +|------------------------------------------|--------------------------------------------|---------------------------------|------------------------------| +| 100GBASE-SR10 or:
OTL4.10 | 10/
1 | 10
(Note 1) | 10
(Note 1) | +| 100GBASE-LR4 or:
OTL4.4 | 1/
4 (CWDM) | 4
(Note 1) | 4
(Note 1) | +| OTUC4 Carried by a
FlexO-1--4 | 1/
4 (DWDM) | 4
(Note 2) | 4
(Note 2) | +| OTUC3 carried by two
150G wavelengths | 1/
2 (DWDM) | 2
(Note 2) | 2
(Note 2) | + +NOTE 1 – Typically, it is not necessary to expose the details of the group members for management. +NOTE 2 – Typically, the details of the group members are exposed, since each modulator/demodulator and the media channels that will compose the NMC must be configured independently (in the context of the group). + +# Appendix IX + +## Media channel configuration and spectrum optimization + +(This appendix does not form an integral part of this Recommendation.) + +The frequency slot of a media channel is enforced by a filter function with a passband that is narrower than the frequency slot, the concatenation of filter functions further narrows the passband. The passband of the NMC must be sufficient to allow the OTSi to be carried without excessive degradation. This is typically achieved by selecting the appropriate slot width based on the maximum number of filters allowed to be present in the NMC. + +If each network NMC consists of a serial concatenation of media channels each with a frequency slot that is equal to the effective frequency slot of the NMC, up to 6 NMC wide filters could be present in the NMC. Then, for example, with 8 OTSi between common end points and a 50 GHz slot width assigned for each OTSi, 400 GHz of spectrum is required between the end points. + +This is illustrated in Figure IX.1. + +![Diagram of independent media channels for each NMC](6707cae4df136f92a0c9f3a4676f91a6_img.jpg) + +The diagram illustrates two network elements, a transmitter (T) on the left and a receiver (R) on the right, connected by a series of media channels. At the top of each element, a 'Media port' is shown with an arrow pointing to a circle labeled 'FP' (Forward Path) and 'CI' (Control Interface). Below the media port, the transmitter (T) or receiver (R) has two input/output points labeled '1' and 'n'. The 'OTSi' (Optical Transport Signal) is shown entering/leaving the element at point '1', and the 'OTSiG' (Optical Transport Signal Group) is shown entering/leaving at point 'n'. The signal path between the transmitter and receiver consists of multiple segments: 'NMC' (Network Media Channel), 'NMCG' (Network Media Channel Group), and 'Each NMC in an independent MC' (indicated by a dashed line and arrow). The signal flows from the transmitter through the NMC, NMCG, and then through another NMC to the receiver. The diagram is labeled 'G.807(24)' in the bottom right corner. + +Diagram of independent media channels for each NMC + +**Figure IX.1 – Independent media channels for each NMC** + +If contiguous spectrum is available between the end points a wider media channels could be created. This need for contiguous spectrum may be identified as a part of a network planning process and the appropriate wide media channels13 could be configured when the optical line system is installed. The availability of contiguous spectrum may allow the use of the spectrum to be optimized since the number of NMC wide filters present in each of the NMCs could be limited to two (or less). This may allow the slot width assigned to each NMC to be less than 50 GHz and consequently the slot width of the wider media channel will be less than 400 GHz. Examples of how this edge to edge could be used to support one or more OTSiG are shown in Table IX.1. + +13 A "wide" media channel may be used to provide what is commonly called an "express" channel in a ROADMs network. + +**Table IX.1 – Example of assignment of OTSiG to a media channel** + +| # OTSiG | OTSi per OTSiG | Clients | +|---------|----------------|---------| +| 1 | 8 | OTU8C | +| 3 | 4 | OTU4C | +| | 2 | OTU2C | +| | 2 | OTU2C | +| 4 | 4 | OTU4C | +| | 2 | OTU2C | +| | 1 | OTU4 | +| | 1 | OTU4 | +| 8 | 8 | 8*OTU4 | + +Other sizes and combinations of OTSiG could also be supported. + +The case where a single NMCG (that supports one OTSiG) is assigned to an edge-to-edge media channel is shown in Figure IX.2. + +![Diagram of an edge-to-edge media channel with a single NMCG. It shows two transceivers, T and R, connected by a media channel. Each transceiver has a Media port, OTSi, and OTSiG interfaces. The NMCG is shown as a dashed line within the media channel. Labels include FP, CI, OTSi, OTSiG, Media port, NMC, NMCG, and G.807(24).](9cb54072e43a6b6717eb16036a7640a2_img.jpg) + +The diagram illustrates an edge-to-edge media channel with a single NMCG. On the left, a transceiver (T) is connected to a Media port. It has two interfaces: OTSi (labeled 1) and OTSiG (labeled n). These interfaces are connected to a dashed line representing the NMCG. The NMCG is part of a larger media channel (NMC) that spans between two transceivers, T and R. The central part of the diagram shows the media channel with two pentagonal symbols representing optical amplifiers or repeaters. A label "NMCG in one 'edge to edge' MC" points to the dashed line. On the right, another transceiver (R) is connected to a Media port. It also has OTSi (labeled 1) and OTSiG (labeled n) interfaces connected to the NMCG. Above the transceivers, there are labels FP and CI with arrows indicating signal flow. The diagram is labeled G.807(24). + +Diagram of an edge-to-edge media channel with a single NMCG. It shows two transceivers, T and R, connected by a media channel. Each transceiver has a Media port, OTSi, and OTSiG interfaces. The NMCG is shown as a dashed line within the media channel. Labels include FP, CI, OTSi, OTSiG, Media port, NMC, NMCG, and G.807(24). + +**Figure IX.2 – Edge-to-edge media channel with a single NMCG** + +The case where two NMCGs (that each supports one OTSiG) are assigned to an edge-to-edge media channel is shown in Figure IX.3. + +![Diagram of an edge-to-edge media channel with two NMCGs. It shows two transceivers connected by a media channel. Each transceiver has a Media port, NMC, NMCG 1, and NMCG 2 interfaces. The NMCGs are shown as dashed lines within the media channel. Labels include NMC, NMCG 1, NMCG 2, Media port, and G.807(20)-Amd.1(21)_FIX.3.](b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg) + +The diagram illustrates an edge-to-edge media channel with two NMCGs. On the left, a transceiver is connected to a Media port. It has three interfaces: NMC (labeled 1), NMCG 1 (labeled n), and NMCG 2 (labeled n). These interfaces are connected to two dashed lines representing the NMCGs. The NMCGs are part of a larger media channel (NMC) that spans between two transceivers. The central part of the diagram shows the media channel with two pentagonal symbols representing optical amplifiers or repeaters. A label "'Edge to edge' MC with 2 NMCGs" points to the dashed lines. On the right, another transceiver is connected to a Media port. It also has NMC (labeled 1), NMCG 1 (labeled n), and NMCG 2 (labeled n) interfaces connected to the NMCGs. The diagram is labeled G.807(20)-Amd.1(21)\_FIX.3. + +Diagram of an edge-to-edge media channel with two NMCGs. It shows two transceivers connected by a media channel. Each transceiver has a Media port, NMC, NMCG 1, and NMCG 2 interfaces. The NMCGs are shown as dashed lines within the media channel. Labels include NMC, NMCG 1, NMCG 2, Media port, and G.807(20)-Amd.1(21)\_FIX.3. + +**Figure IX.3 – Edge-to-edge media channel with two NMCGs** + +The case where a common media channel is shared by two NMCGs across part of the media network is shown in Figure IX.4. + +![Diagram of a media network showing a common media channel shared by two NMCGs.](638a308af25f1f56b4456a1fc503f161_img.jpg) + +The diagram illustrates a media network configuration. At node A, two Network Management Control Groups (NMCG 1 and NMCG 2) are connected to a central 'Media port'. Each NMCG is associated with a Network Management Channel (NMC), represented by a pair of blue lines. These channels lead from node A to node B, which acts as a splitter. From node B, the media channels split to nodes C and D. At node C, NMCG 1 is connected to an NMC. At node D, NMCG 2 is connected to an NMC. The connections between nodes are shown as pairs of blue lines, with dashed ovals indicating the NMCG components at each node. A small label 'G.807(24)' is present in the bottom right corner of the diagram area. + +Diagram of a media network showing a common media channel shared by two NMCGs. + +**Figure IX.4 – Media channel shared by two NMCGs across a part of the media network** + +A point to multipoint media channel from A to C and D can be provided by using a splitter at B. This provides the opportunity for spectrum optimization and flexibility in the assignment of NMCs (as described in Appendix II). + +The use of a filter at B provides two point-to-point media channels, one A-C the other A-D. + +Other configurations of "wide" media channels may also be used to optimize spectral utilization. + +# Appendix X + +## Examples of grid systems defined in other Recommendations + +(This appendix does not form an integral part of this Recommendation.) + +Frequency slots as described in this Recommendation may be part of frequency ranges or grids. As described in clause 6.2.1, for dense wavelength division multiplexing (DWDM) applications, the grid defined in [ITU-T G.694.1] may be used. For coarse wavelength division multiplexing (CWDM) applications, the grid defined in [ITU-T G.694.2] may be used. Examples of other grids that may be used for optical signals are given in this appendix. + +For Ethernet optical interfaces, the wavelength ranges are provided in [b-IEEE 802.3] for example the wavelength ranges for a 100GBASE-LR4 interface are provided in Table 88-5. + +For passive optical networks (PONs), clause 8.2.5 of [b-ITU-T G.983.1] provides wavelength ranges for both downstream and upstream directions and notes that [b-ITU-T G.983.3] "describes a more comprehensive wavelength plan that narrows this downstream range for single-fibre systems". Clause 8.2 of [b-ITU-T G.983.1] defines wavelength allocations for the optical access network that accommodate ATM-PON. + +A later generation of PON is NG-PON2 whose main definitions are in [b-ITU-T G.989]. Several terms from [b-ITU-T G.989] that relate to grids are: + +**3.2.1.28 wavelength channel:** A unidirectional (downstream or upstream) optical communications channel characterized by a single unique central frequency or a set of unique central frequencies mapped to one WM tributary port. + +**3.2.2.2 channel spacing:** The absolute difference between the nominal central frequencies of two adjacent wavelength channels in a given reference grid. + +**3.2.2.14 nominal central frequency:** The specified frequency of a wavelength channel. + +Clause 5.12 of [b-ITU-T G.989] discusses the terms "band" and "range" as follows: + +When used in the context of optical spectrum, both terms "band" and "range" generally denote a spectral interval in terms of frequency ( $f_{\min}$ , $f_{\max}$ ) or wavelength ( $\lambda_{\min}$ , $\lambda_{\max}$ ). Within the NG-PON2 context, the term "band" applies specifically to a spectral interval which covers all wavelength channels of a specific application (e.g., TWDM PON upstream band, narrow band option, shared spectrum band, G-PON downstream band), whereas the term "range" usually applies to a spectral interval corresponding to a single wavelength channel. + +The wavelength plans of several generations of PON systems are summarized in Figure 8-2 of [b-ITU-T G.989.1]. A more detailed NG-PON2 Recommendation [b-ITU-T G.989.2] details wavelength bands in clause 9.2 and also indicates that "In the expanded spectrum case, DWDM grids as specified in [ITU-T G.694.1] or [b-ITU-T G.698.3] can be used. See Appendix VII for some example channel plans; however other plans are conceivable and permitted." + +[b-ITU-T G.698.3] describes a case where the tail-end to head-end direction uses the [ITU-T G.694.1] grid but the head-end to tail-end direction "do not lie on the frequency grid for the minimum channel spacing given in [ITU-T G.694.1]. Instead, they are determined by the free spectral range of the cyclic OD/OM device." Appendix I of [b-ITU-T G.698.3] provides some details of the free spectral range of an AWG that could be used for this head-end to tail-end direction. + +In [b-ITU-T G.9960] one of the media specified for wire-line based home networking is plastic optical fibre. Annex F provides wavelength specifications for this media. The following definition is given in [b-ITU-T G.9991]: + +**bandplan:** A specific range of the frequency spectrum that is associated with a domain. Multiple bandplans may be used in the same domain provided that each bandplan used is a subset of the largest bandplan specified for the domain and a superset of the smallest bandplan specified for the domain. The bandplan is defined by a lower frequency and upper frequency except for RF, which is defined by a bandwidth and centre frequency. + +An example of optical signals in free space is specified in [b-ITU-T G.9991]. Clause 6.1.2.2 specifies that "Two wavelength bands are defined in this Recommendation, which are visible light (380 nm-780 nm) and infrared (800 nm-1 675 nm)." + +# Bibliography + +- [b-ITU-T G.661] Recommendation ITU-T G.661 (2007), *Definitions and test methods for the relevant generic parameters of optical amplifier devices and subsystems.* +- [b-ITU-T G.698.3] Recommendation ITU-T G.698.3 (2012), *Multichannel seeded DWDM applications with single-channel optical interfaces.* +- [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.983.3] Recommendation ITU-T G.983.3 (2001), *A broadband optical access system with increased service capability by wavelength allocation.* +- [b-ITU-T G.984.1] Recommendation ITU-T G.984.1 (2008), *Gigabit-capable passive optical networks (GPON): General characteristics.* +- [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.989.1] Recommendation ITU-T G.989.1 (2013), *40-Gigabit-capable passive optical networks (NG-PON2): General requirements.* +- [b-ITU-T G.989.2] Recommendation ITU-T G.989.2 (2019), *40-Gigabit-capable passive optical networks 2 (NG-PON2): Physical media dependent (PMD) layer specification.* +- [b-ITU-T G.7710] Recommendation ITU-T G.7710/Y.1701 (2020), *Common equipment management function requirements.* +- [b-ITU-T G.9960] Recommendation ITU-T G.9960 (2023), *Unified high-speed wireline-based home networking transceivers – System architecture and physical layer specification.* +- [b-ITU-T G.9991] Recommendation ITU-T G.9991 (2019), *High speed indoor visible light communication transceiver – System architecture, physical layer and data link layer specification.* +- [b-ITU-T G Suppl.55] Recommendation ITU-T G Suppl. 55 (2023), *Radio-over-fibre (RoF) technologies and their applications.* +- [b-IEC 60050 envelope] IEC Electropedia, International Electrotechnical Vocabulary, 314-08-05, <> +- [b-IEEE 802.3] IEEE 802.3 (2022), IEEE Std 802.3TM-2022 IEEE Standard for Ethernet (Revision of IEEE Std 802.3-2022) +<> + + + + + +## 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.808.3-201210-I_PDF-E/raw.md b/marked/G/T-REC-G.808.3-201210-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..20a6aa57a807b38b79207406100bed6078821394 --- /dev/null +++ b/marked/G/T-REC-G.808.3-201210-I_PDF-E/raw.md @@ -0,0 +1,671 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.808.3** + +(10/2012) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital networks – General aspects + +# --- **Generic protection switching – Shared mesh protection** + +Recommendation ITU-T G.808.3 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it, symbolizing global connectivity and telecommunications. The letters 'ITU' are prominently displayed in blue. + +ITU logo + +## ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600–G.699 | +| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| General aspects | G.800–G.809 | +| Design objectives for digital networks | G.810–G.819 | +| Quality and availability targets | G.820–G.829 | +| Network capabilities and functions | G.830–G.839 | +| SDH network characteristics | G.840–G.849 | +| Management of transport network | G.850–G.859 | +| SDH radio and satellite systems integration | G.860–G.869 | +| Optical transport networks | G.870–G.879 | +| 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.808.3** + +# **Generic protection switching – Shared mesh protection** + +## **Summary** + +Recommendation ITU-T G.808.3 provides an overview of generic aspects of a shared mesh protection (SMP) mechanism for connection-oriented layer networks that does not depend upon the presence of a control plane. SMP provides a method for sharing resources in the mesh network for protection against one or more failures in the network. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T G.808.3 | 2012-10-29 | 15 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3.1 Terms defined elsewhere..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Overview ..... | 3 | +| 6.1 Mesh topologies..... | 3 | +| 6.2 Capacity efficiency considerations..... | 4 | +| 7 SMP architecture types..... | 4 | +| 7.1 SMP architecture overview ..... | 4 | +| 8 Switching types..... | 9 | +| 9 Operation types..... | 9 | +| 10 Non-pre-emptible unprotected traffic (NUT) and extra traffic..... | 9 | +| 11 Automatic switch..... | 9 | +| 12 Pre-emption principle ..... | 9 | +| 13 Path status monitoring ..... | 10 | +| 14 Automatic protection switching (APS) protocol ..... | 10 | +| Annex A – Objectives..... | 11 | +| Appendix I – SMP scenarios..... | 13 | +| I.1 A simple SMP scenario ..... | 13 | +| I.2 SMP in mesh network ..... | 13 | +| Appendix II – Overview of shared mesh restoration (SMR) and shared mesh protection (SMP) operation ..... | 18 | +| Bibliography..... | 19 | + + + +## Recommendation ITU-T G.808.3 + +# Generic protection switching – Shared mesh protection + +# 1 Scope + +This Recommendation provides an overview of generic aspects of a shared mesh protection (SMP) mechanism for connection-oriented layer networks that does not depend upon the presence of a control plane. This mechanism is targeted for mesh network architectures, which offer further efficiencies in protection resource utilization. The primary characteristics of this path-based protection approach involve usage of pre-computation and pre-allocation of resources to maximize speed of recovery. The technology-specific shared mesh protection mechanisms will be defined in technology-specific Recommendation(s). + +This version of the Recommendation provides an architecture framework for SMP. + +# 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.780] Recommendation ITU-T G.780/Y.1351 (2010), *Terms and definitions for synchronous digital hierarchy (SDH) networks*. +- [ITU-T G.805] Recommendation ITU-T G.805 (2000), *Generic functional architecture of transport networks*. +- [ITU-T G.806] Recommendation ITU-T G.806 (2006), *Characteristics of transport equipment – Description methodology and generic functionality*. +- [ITU-T G.808.1] Recommendation ITU-T G.808.1 (2010), *Generic protection switching – Linear trail and subnetwork protection*. +- [ITU-T G.870] Recommendation ITU-T G.870/Y.1352 (2010), *Terms and definitions for optical transport network*. + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +### 3.1.1 Terms related to actions + +#### 3.1.1.1 switch [ITU-T G.870] + +### 3.1.2 Terms related to components + +#### 3.1.2.1 bridge [ITU-T G.870] + +#### 3.1.2.2 selector [ITU-T G.870] + +#### 3.1.2.3 intermediate node [ITU-T G.870] + +### 3.1.3 Terms related to fault conditions + +#### 3.1.3.1 signal degrade (SD) [ITU-T G.805] + +**3.1.3.2 signal fail (SF) [ITU-T G.805]** + +**3.1.4 Terms related to architecture** + +**3.1.4.1 m:n (protection) architecture [ITU-T G.870]** + +**3.1.5 Terms related to operation** + +**3.1.5.1 revertive (protection) operation [ITU-T G.870]** + +**3.1.6 Terms related to signals** + +**3.1.6.1 traffic signal [ITU-T G.870]** + +**3.1.6.2 normal traffic signal [ITU-T G.870]** + +**3.1.6.3 extra traffic signal [ITU-T G.870]** + +**3.1.7 Terms related to switching** + +**3.1.7.1 bidirectional (protection) switching [ITU-T G.780]** + +**3.1.7.2 unidirectional (protection) switching [ITU-T G.780]** + +**3.1.8 Terms related to transport entities** + +**3.1.8.1 link [ITU-T G.805]** + +**3.1.8.2 transport entity [ITU-T G.870]** + +**3.1.8.3 protection transport entity [ITU-T G.870]** + +**3.1.8.4 working transport entity [ITU-T G.870]** + +**3.1.9 protection [ITU-T G.870]** + +**3.1.10 restoration [ITU-T G.870]** + +**3.1.11 switch event [ITU-T G.870]** + +**3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 protection segment:** A link between two SMP nodes on a protection transport entity. + +**3.2.2 shared mesh protection:** A shared mesh protection (SMP) architecture involves multiple normal traffic signals, where each signal has one corresponding working transport entity and one or more protection transport entities, in a meshed network. In an SMP, the protection resources are shared among two or more protection transport entities. Only one of these protection transport entities can use the shared protection resources at any point of time. + +**3.2.3 shared protection segment:** A link between two SMP nodes, where the bandwidth resource on the link is shared by multiple protection transport entities. + +**4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +APS Automatic Protection Switching + +NUT Non-pre-emptible Unprotected Traffic + +OTN Optical Transport Network + +P Protection + +| | | +|-----|-------------------------------| +| SD | Signal Degrade | +| SDH | Synchronous Digital Hierarchy | +| SF | Signal Fail | +| SMP | Shared Mesh Protection | +| W | Working | + +# 5 Conventions + +None. + +# 6 Overview + +## 6.1 Mesh topologies + +A meshed transport network is one in which each node in the network is interconnected by at least two links whose remote ends are on different nodes from each other (see example a) of Figure 1). It should be noted that while the overall transport network may contain nodes that do not satisfy the above criteria (see left two nodes in example b) of Figure 1), such nodes would not be considered part of the portion of the transport network defined as being a mesh. A fully meshed topology is one in which each node is directly connected to every other node in a network (see example c) of Figure 1). + +![Figure 1 shows three examples of mesh network topologies: a) A partially meshed network with 10 nodes where most are interconnected but some are on the periphery. b) A network with 7 nodes where only 5 form a mesh and two are connected to it. c) A fully meshed network with 6 nodes where every node is connected to every other node.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +Figure 1 shows three examples of mesh network topologies: a) A partially meshed network with 10 nodes where most are interconnected but some are on the periphery. b) A network with 7 nodes where only 5 form a mesh and two are connected to it. c) A fully meshed network with 6 nodes where every node is connected to every other node. + +1-a: Example of a mesh network + +1-b: Example of a network, only a portion of which is meshed + +1-c: Example of a fully meshed network + +**Figure 1 – Examples of mesh network** + +Most mesh transport networks are only partially meshed (as in example a) of Figure 1), with some nodes fully meshed and others connecting to one or more nodes, but not to all of them (i.e., their maximum number being less than the total number of nodes – 1). While fully meshed network topologies offer the highest degree of survivability in the event of failures, they have the highest degree of transport resource redundancy. Most mesh transport networks are only partially meshed and generally require traversing intermediate nodes to go from each node to every other node. + +## 6.2 Capacity efficiency considerations + +Increased sharing of protection resources in mesh network architectures inherently allows for reduction of network costs by eliminating dedicated protection resources. Such architectures may also be designed according to the level of "guaranteed protection" and capacity efficiency desired by the operator, according to the grades of services offered. Capacity efficiency in mesh network architectures can be measured in various ways, including [b-BLTJ.1999]: + +- i) The fraction of demands that can be protected given the network capacities, point-to-point demands, and working path for each demand; +- ii) The needed network capacities for providing 100% protection given point-to-point demands and working path for each demand; or +- iii) The total network capacities for working and protection paths given point-to-point demands and provided 100% protection. + +The first approach involves finding protection paths for as many demands as possible under link capacity constraints in an existing network. This is distinguished from the latter two approaches, which assume that capacity planning is underway to assure 100% protection for all demands. + +It should be noted that at some point the desired degree of network resource optimization (resulting in insufficient link capacity) becomes inversely proportional to the degree of "guaranteed protection" that can be offered. In real capacity-constrained situations, it is necessary to be capable of prioritizing the demands and ensuring that those demands with high availability requirements are always assigned protection paths. + +Within this Recommendation, the focus is upon achieving maximal possible protection considering a given network's capabilities, including mechanisms for prioritizing demands to enable those demands with high availability requirements to be assigned protection paths. + +# 7 SMP architecture types + +## 7.1 SMP architecture overview + +SMP may be employed in fully meshed and partially meshed transport networks, which include, but are not limited to, long-haul and metro networks. Depending on the degree of inter-connection between network nodes, SMP protection can significantly improve network resource utilization, as compared with alternative 1:1 protection mechanisms. + +An SMP architecture involves multiple normal traffic signals, where each signal is associated with a working transport entity and one or more protection transport entities. SMP architecture is based upon m:1 protection (where m may be greater than or equal to one). + +In the m:1 SMP architecture, each working transport entity is protected by m protection transport entities. In this architecture, the working transport entity can be protected when one of the m protection transport entities is available. + +Each protection transport entity is constructed of one or multiple protection segments. The bandwidth of each protection segment can be shared by multiple protection transport entities. To prevent a network failure from interrupting the protected normal traffic signal, it is recommended that all working transport entities that share protection resources should be disjoint. + +The shared bandwidth for the protection segment should be capable of supporting the largest of the corresponding protection transport entities. + +NOTE – The protection resources and the information of protection transport entities are pre-configured through a control or management plane, and the detailed description of the pre-configuration process is out of the scope of this Recommendation. The (shared) mesh restoration mechanism based on a control plane is also out of the scope of this Recommendation. + +Figure 2 shows an example of a simple m:1 SMP architecture. There are two working transport entities, which are W1 (A-B) and W2 (E-F). The protection transport entities in this example have been configured as follows: + +- For W1, there are two protection transport entities P1 (A-C-D-B) and P1' (A-G-H-B); +- For W2, there is a protection transport entity P2 (E-C-D-F). + +If a failure of W2 is detected, the corresponding protection transport entity P2 will be activated to transmit the traffic. As a result of the bandwidth for protection segment PS3 being fully occupied by P2, the protection transport entity P1 has no protection capability to provide protection for the working transport entity W1, but the other protection transport entity P1' can be used to protect the working transport entity W1. + +![Diagram of an m:1 SMP architecture showing nodes A, B, C, D, E, F, G, H and their connections. W1 (A-B) is a solid blue line. W2 (E-F) is a solid green line. P1 (A-C-D-B) is a dashed blue line. P1' (A-G-H-B) is a dashed red line. P2 (E-C-D-F) is a dashed green line. Segments PS1, PS2, PS3, PS4, PS5, PS6, PS7, PS8 are labeled on the respective links between nodes.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +The diagram illustrates an m:1 SMP architecture with nodes A, B, C, D, E, F, G, and H. Node A is connected to B (solid blue line W1), C (solid black line), and G (solid black line). Node B is connected to A, D (solid black line), and H (solid black line). Node C is connected to A, B, D (solid black line), and E (solid black line). Node D is connected to B, C, E (solid black line), and F (solid black line). Node E is connected to C, D, and F (solid green line W2). Node F is connected to D and E. Node G is connected to A and H (solid black line). Node H is connected to B and G. Protection paths are shown as dashed lines: P1 (blue) from A to C to D to B; P1' (red) from A to G to H to B; and P2 (green) from E to C to D to F. Segments are labeled: PS1 (A-C), PS2 (B-D), PS3 (C-D), PS4 (C-E), PS5 (D-F), PS6 (A-G), PS7 (B-H), and PS8 (G-H). + +Diagram of an m:1 SMP architecture showing nodes A, B, C, D, E, F, G, H and their connections. W1 (A-B) is a solid blue line. W2 (E-F) is a solid green line. P1 (A-C-D-B) is a dashed blue line. P1' (A-G-H-B) is a dashed red line. P2 (E-C-D-F) is a dashed green line. Segments PS1, PS2, PS3, PS4, PS5, PS6, PS7, PS8 are labeled on the respective links between nodes. + +Figure 2 – Example of an m:1 SMP architecture + +Figure 3 shows a simple m:1 SMP architecture example where m=1. + +![Diagram of a 1:1 SMP architecture showing nodes A, B, C, D, E, and F. Node A is connected to B via a solid blue line labeled W1. Node C is connected to D via a dashed blue line labeled P1 and a dashed red line labeled P2. Node E is connected to F via a solid red line labeled W2. Vertical connections are: A to C (dashed blue line PS1), B to D (dashed blue line PS2), C to E (dashed red line PS4), and D to F (dashed red line PS5). A horizontal dashed blue line labeled PS3 connects C and D.](d4af765160d04ecef538e5066006dc77_img.jpg) + +Diagram of a 1:1 SMP architecture showing nodes A, B, C, D, E, and F. Node A is connected to B via a solid blue line labeled W1. Node C is connected to D via a dashed blue line labeled P1 and a dashed red line labeled P2. Node E is connected to F via a solid red line labeled W2. Vertical connections are: A to C (dashed blue line PS1), B to D (dashed blue line PS2), C to E (dashed red line PS4), and D to F (dashed red line PS5). A horizontal dashed blue line labeled PS3 connects C and D. + +**Figure 3 – Example of a 1:1 SMP architecture** + +### 7.1.1 SMP for circuit networks + +In circuit switch networks (e.g., SDH/OTN, the cross-connects in the intermediate nodes of the protection transport entity cannot be pre-established when the protection segment is shared by multiple protection transport entities. In this case, the intermediate nodes need to establish the cross-connects for the protection transport entity when the protected working transport entity is detected in failure. + +The end points of each working transport entity should have the monitoring functions to monitor the status of the working transport entity. The detected signal fail/signal degrade (SF/SD) status will trigger the protection switch procedure. Meanwhile, the nodes along the protection transport entity should also have the monitoring functions to monitor the status of the resources of each protection segment. The worst status among the statuses of the protection segments along a protection transport entity will be notified to the end points. If the status of the protection transport entity is worse than the status of the working transport entity, the end points should prevent the normal traffic signal from being switched to the protection transport entity. + +![Diagram a) shows the SMP for a circuit network with pre-established cross-connections. It features six nodes (A, B, C, D, E, F) and two working paths (Working 1 and Working 2). Protection segments (PS1, PS2, PS3, PS4, PS5) are shown with solid lines indicating pre-established cross-connections at intermediate nodes C and D. A legend indicates orange boxes are Cross- connect controllers and yellow boxes are Protection segments.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +a) SMP for circuit network with pre-established cross-connections + +Diagram a) shows the SMP for a circuit network with pre-established cross-connections. It features six nodes (A, B, C, D, E, F) and two working paths (Working 1 and Working 2). Protection segments (PS1, PS2, PS3, PS4, PS5) are shown with solid lines indicating pre-established cross-connections at intermediate nodes C and D. A legend indicates orange boxes are Cross- connect controllers and yellow boxes are Protection segments. + +![Diagram b) shows the SMP for a circuit network without pre-established cross-connections. It features the same nodes and paths as diagram a). Protection segments (PS1, PS2, PS3, PS4, PS5) are shown with dashed lines indicating that cross-connections at intermediate nodes C and D are not pre-established. A legend indicates orange boxes are Cross- connect controllers and yellow boxes are Protection segments.](4e4be0bd8b235167902f2c03e41da651_img.jpg) + +b) SMP for circuit network without pre-established cross-connections + +Diagram b) shows the SMP for a circuit network without pre-established cross-connections. It features the same nodes and paths as diagram a). Protection segments (PS1, PS2, PS3, PS4, PS5) are shown with dashed lines indicating that cross-connections at intermediate nodes C and D are not pre-established. A legend indicates orange boxes are Cross- connect controllers and yellow boxes are Protection segments. + +**Figure 4 – Examples of SMP for a circuit network** + +Figure 4 shows the SMP for a circuit network. The cross-connections in the intermediate nodes of the protection transport entities are not pre-established. The link connections may not be allocated before failure is detected, as showed in diagram b) of Figure 4. + +The end points (e.g., Node A/B, Node E/F) will monitor the status of Working 1 (W1) and Working 2 (W2). The nodes along the two protection transport entities (i.e., P1 and P2) will monitor the status of each. + +When the working transport entity W1 is detected to be impaired or failed and if the status of the protection transport entity is available, upon receiving the APS signal, node C needs to establish the cross-connect between PS1 and PS3 and node D needs to establish the cross-connect between PS3 and PS2 to activate the protection transport entity P1. For the case showed in diagram b) of Figure 4, the link connections of PS1, PS3 and PS2 should be established. + +NOTE – Figure 4 illustrates, for simplicity, a 1:1 SMP architecture for circuit networks. This example can be extended to illustrate the m:1 SMP architecture, where there are multiple protection transport entities for one working transport entity. + +### 7.1.2 SMP for packet networks + +In packet switch networks, it is possible to pre-establish different protection transport entities sharing the same bandwidth of the shared protection segment. In normal conditions, in which normal traffic signals are transported via working transport entities, only APS and OAM packets are transported via protection transport entities. The bandwidth of a shared protection segment should be allocated in such a way that it may be possible to protect any of the working transport entities whose protection transport entities are sharing the protection segment. + +The end points of each working transport entity should have monitoring functions to monitor the status of the working transport entity. The detected SF/SD status will trigger the protection switch procedure. Because the protection transport entity is pre-established, the status of the protection transport entity can also be monitored at the end points. + +![Diagram of SMP for a packet network showing two working transport entities (Working 1 and Working 2) and their corresponding protection transport entities (Protection 1 and Protection 2) sharing a common protection segment (PS3).](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +The diagram illustrates a 1:1 SMP architecture for packet networks. It features two working transport entities, Working 1 and Working 2, and two protection transport entities, Protection 1 and Protection 2. The network consists of six nodes: Node A, Node B, Node C, Node D, Node E, and Node F. Nodes A and B are the end points for Working 1. Nodes E and F are the end points for Working 2. Nodes C and D are intermediate nodes. Protection segment PS3 is a shared segment between nodes C and D. Protection segment PS1 is between Node A and Node C. Protection segment PS2 is between Node B and Node D. Protection segment PS4 is between Node E and Node C. Protection segment PS5 is between Node F and Node D. Bridge and selector functions are shown at each node, represented by yellow boxes. Protection 1 is pre-established through the path A-C-D-B. Protection 2 is pre-established through the path E-C-D-F. The legend indicates that yellow boxes represent 'Bridge and selector functions' and yellow lines represent 'Protection segment'. + +Diagram of SMP for a packet network showing two working transport entities (Working 1 and Working 2) and their corresponding protection transport entities (Protection 1 and Protection 2) sharing a common protection segment (PS3). + +**Figure 5 – Example of SMP for a packet network** + +Figure 5 shows the 1:1 SMP architecture for packet networks. PS3 is shared by the two protection transport entities which are pre-established through A-C-D-B and E-C-D-F, respectively. The two pairs of end points, node A and B pair and node E and F pair will monitor the status of Working 1 and Protection 1, and Working 2 and Protection 2, respectively. When one of the working transport + +entities is detected to be impaired or failed and if its corresponding protection transport entity is determined to be available, its normal traffic signal must be switched from the working to the protection transport entity. In the intermediate nodes (C and D), there is no need to create cross-connects because they have been already created in advance. + +NOTE – Figure 5 illustrates, for simplicity, a 1:1 SMP architecture for packet networks. This example can be extended to illustrate the m:1 SMP architecture, where there are multiple protection transport entities for one working transport entity. + +# **8 Switching types** + +The SMP mechanism supports the bidirectional switching type, as defined in [ITU-T G.808.1]. + +For bidirectional SMP, the selectors and bridges at both ends of the protection transport entity are operated. In addition, the bidirectional cross-connects at the intermediate nodes (if they are not pre-established) are activated. + +# **9 Operation types** + +The SMP mechanism supports only revertive operation, as defined in [ITU-T G.808.1]. + +# **10 Non-pre-emptible unprotected traffic (NUT) and extra traffic** + +SMP scheme supports non-pre-emptible unprotected traffic (NUT). + +NUT here is generic, which means that this traffic class does not use any protection resources and is not protected in the event of a failure along its path, but cannot be dropped from the network to allow protection of other traffic. + +Extra traffic is for further study. + +# **11 Automatic switch** + +For further study. + +# **12 Pre-emption principle** + +For SMP, pre-emption principles are applied for the case when multiple protection transport entities are competing for the same shared resource. + +To resolve the competition, two types of information should be taken into account: + +- Pre-emption priority: Every protection transport entity is assigned a pre-emption priority that is configured in advance. +- Request type priority: The relative priority of events (fault conditions and external commands) that trigger the protection. The assignment of these priorities is for further study. + +Both priorities must be taken into consideration by all the nodes along the protection transport entity. + +- 1) When a resource competition occurs between multiple protection transport entities having different pre-emption priorities, the protection transport entity with the higher pre-emption priority occupies the resources. +- 2) When a resource competition occurs between multiple protection transport entities having the same pre-emption priority, the protection transport entity having the higher priority request type occupies the resources. + +- 3) In the case where the resource competition occurs between multiple protection transport entities having the same pre-emption and request-type priorities, their transport entity IDs can be used for resolving the contention. + +# **13 Path status monitoring** + +The status of the working transport entity can be monitored using similar methods as those defined for existing linear protection schemes in [ITU-T G.808.1]. Specific monitoring methods are technology dependent. + +Depending on the underlying network transport technology, the protection transport entity may not be established in advance. In this case, there is no direct monitoring of the end-to-end status of the protection transport entity at the protection end points. Therefore, each protection segment needs to notify the end points of the protection transport entity of its status. + +If it is possible to pre-establish the protection transport entity, then its status can be monitored using similar methods as those defined for existing linear protection schemes in [ITU-T G.808.1]. Specific monitoring methods are technology dependent. + +Each protection segment needs to notify the end points of the protection transport entity of its resource availability. This notification is intended to reduce the likelihood of unnecessary protection switching requests which will otherwise fail once the request reaches the unavailable protection resource. + +# **14 Automatic protection switching (APS) protocol** + +For further study. + +# Annex A + +## Objectives + +(This annex forms an integral part of this Recommendation.) + +- A.1 Shall allow backwards compatibility with core structures/formats of technology-specific Recommendations. +- A.2 Shall not impact usage of existing technology-specific linear and ring APS protection mechanisms and communications channels (i.e., co-existence with existing APS specifications). +- A.3 Shall allow for any intra-/inter-operator applications for cascaded or nested protection deployments. +- A.4 Shall allow for co-existence of ASON-based protection/restoration and SMP protection at inter-domain boundaries. +- A.5 Shall be capable of supporting protection of one or more point-to-point bidirectional normal traffic signals from the ingress to the egress of the SMP domain. +- A.6 Shall not require that multiple working transport entities sharing the same protection resource(s) have the same end points. +- A.7 Shall monitor the status of the working transport entities for SMP protection switching triggers (e.g., SF, SD). +- A.8 Shall monitor availability of the shared protection resources along the protection transport entities. +- A.9 Shall include support for communicating information on the availability of the shared protection resources along the protection transport entities to the end points of the working transport entities that utilize the resources. +- A.10 Shall include support for communicating information among network nodes to perform protection switching. The message encoding and communicating channel between the nodes depends on the specific technology. +- A.11 Shall be capable of recovering a normal traffic signal from network failure(s) in a deterministic manner. For example, the protection switching shall complete within a finite (bounded) time, as described within the technology-specific Recommendations. +- A.12 Shall include support for a mechanism to detect protocol failures. +- A.13 Shall include support for a mechanism to detect possible inconsistencies in configuration between the ingress and egress nodes of an SMP domain. +- A.14 Shall be capable of supporting nesting of multiple levels of protection (whether SMP or other schemes such as SNC protection). To achieve this, shall include support for mechanism(s) that allow for coordination of protection activities (e.g., hold-off timer). +- A.15 Shall provide a mechanism to avoid protection switching flapping (e.g., wait-to-restore timer). +- A.16 Shall include support for multiple links between nodes, allowing for link and node diversity, and should be scalable with respect to the number of links and nodes within the SMP protection domain. +- A.17 Shall provide a contention resolution mechanism for permitting only one working transport entity to occupy protection resources in the case that these protection resources are shared by more than one working transport entity having the same priority (due to network topology and resource limitations). + +- A.18 Shall be capable of supporting the ability to set an upper limit on the maximum number of working transport entities that can share protection resources (which is governed by the specific technology). +- A.19 Shall include support for the ability to set an upper bound on the fraction of link resources that can be allocated to protecting transport entities. +- A.20 Shall allow for configuration (which may be via the management or control plane) of the protection transport entity identifiers, required bandwidth, and additionally for circuit SMP, the assignment of TSs to ensure the proper operation of the protection switching process. +- A.21 Shall support assignment of priority to support the request of a higher-priority transport entity to pre-empt the shared protection resource taken by a lower-priority transport entity. +- A.22 Shall only support revertive operation type. +- A.23 Shall only support bidirectional switching type. +- A.24 Shall be capable of supporting external commands from network operators. +- A.25 Shall be capable of supporting protection for more than one failure, including failures that are concurrent and/or failures involving shared resources. +- A.26 Shall be capable of protection switching activation initiated by either end or both ends (which may be simultaneous) of the SMP domain. + +# Appendix I + +## SMP scenarios + +(This appendix does not form an integral part of this Recommendation.) + +This appendix provides some typical scenarios for SMP. + +Note that not all the scenarios will be illustrated in this appendix. + +## I.1 A simple SMP scenario + +A simple scenario is illustrated in Figure I.1. The working connection W1 along the path A-B is protected by the protection connection P1 along the path A-P-Q-B, and the other working connection W2 along the path C-D is protected by the other protection connection P2 along the path C-P-Q-D. The protection connection P1 and P2 can share some common resource (i.e., the protection link P-Q can be shared by P1 and P2), because W1 and W2 are disjointed from each other. + +![Figure I.1: Simple SMP scenario diagram](12de9b926df0384ec07702671827c9cd_img.jpg) + +The diagram shows a network with four nodes: A, B, C, and D. Node A is connected to B via a working connection W1 (solid blue line). Node C is connected to D via a working connection W2 (solid red line). A protection connection P1 (dashed blue line) follows the path A-P-Q-B, where P and Q are intermediate nodes. Another protection connection P2 (dashed red line) follows the path C-P-Q-D. The link between P and Q is shared by both P1 and P2. The background is split into a light blue top half and a light green bottom half. + +Figure I.1: Simple SMP scenario diagram + +G.808.3(12)\_F1.1 + +Figure I.1 – Simple SMP scenario + +### I.2 SMP in mesh network + +The more general mesh network in Figure I.2 is used to describe various SMP scenarios. + +![Figure I.2: Example of SMP in a mesh network diagram](f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg) + +The diagram shows a mesh network with eight nodes labeled A through H arranged in a circle. Nodes are interconnected by various links. Working connections are shown as solid lines: W1 (blue, A-C), W2 (red, D-G), W3 (orange, A-B), W4 (orange, C-D), W5 (pink, F-G), and W6 (purple, A-H). Protection connections are shown as dashed lines: P1 (blue, A-H), P2 (red, A-B), P3 (blue, E-F), P4 (orange, C-D), P5 (pink, F-G), and P6 (purple, D-E). The diagram illustrates how multiple working and protection paths can coexist and share resources in a mesh topology. + +Figure I.2: Example of SMP in a mesh network diagram + +G.808.3(12)\_F1.2 + +Figure I.2 – Example of SMP + +The mesh network in Figure I.2 shows six working paths (W1, W2, W3, W4, W5 and W6) and their protection paths (P1, P2, P3, P4, P5 and P6), as summarized in Table I.1. + +**Table I.1 – Summary** + +| Colour | Working path | Protection path | +|-----------------|---------------------|------------------------| +| Green (W1, P1) | C-H | H-A-B-C | +| Red (W2, P2) | D-G | G-H-A- B-C-D | +| Blue (W3, P3) | A-B | B-C-D-E-F-G-H-A | +| Orange (W4, P4) | B- A-D | B-C-D | +| Pink (W5, P5) | H-E | H-G-F-E | +| Purple (W6, P6) | B-G | B-C-D-E-F-G | + +W3, W4 and W6 have a same end node B. W2 and W4 have a same end node D. W2 and W6 have a same end node G. W1 and W5 have a same end node H. Node A is an intermediate node of W4, but also an end node of W3. + +NOTE – Each scenario is separated from each other. + +#### Scenario 1 + +A simple scenario of SMP is that two protection paths share common resources. + +| Colour | Working path | Protection path | +|----------------|---------------------|------------------------| +| Green (W1, P1) | C-H | H-A-B-C | +| Red (W2, P2) | D-G | G-H-A- B-C-D | + +In Figure I.2, the working path W1 along the link C-H is protected by the protection path P1 along the segment H-A-B-C, and the working path W2 along the link D-G is protected by the other protection path P2 along the segment G-H-A- B-C-D. P1 and P2 can share some common resource (i.e., the protection segment H-A-B-C). + +#### Scenario 2 + +A port or link can have some resources that are used for working paths and other resources that are used for protection paths. + +| Colour | Working path | Protection path | +|-----------------|---------------------|------------------------| +| Green (W1, P1) | C-H | H-A-B-C | +| Red (W2, P2) | D-G | G-H-A- B-C-D | +| Blue (W3, P3) | A-B | B-C-D-E-F-G-H-A | +| Orange (W4, P4) | B- A-D | B-C-D | + +As shown in Figure I.3, the link A-B contains both working traffic for W3/W4 and also a protection resource that is used by P1/P2. + +![Diagram of Link A-B showing multiple protection resources (blue and orange lines) entering a link cylinder labeled 'Link A-B'. The diagram is labeled G.808.3(12)_FI.3.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Diagram of Link A-B showing multiple protection resources (blue and orange lines) entering a link cylinder labeled 'Link A-B'. The diagram is labeled G.808.3(12)\_FI.3. + +**Figure I.3 – Detail of Link A-B** + +#### **Scenario 3** + +There are multiple protection resources on a link. In this case, the working paths that have links in common can still use the same protection link for protection purpose as long as different resource is assigned for their corresponding protection paths. + +| Colour | Working path | Protection path | +|-----------------|--------------|-----------------| +| Blue (W3, P3) | A-B | B-C-D-E-F-G-H-A | +| Orange (W4, P4) | B- A-D | B-C-D | + +For example, as shown in Figure I.4, the segment B-C-D supports two protection paths on a single link but with different resources. Therefore, although W3 and W4 both have link A-B, they are still allowed to use segment B-C-D as part of their protection paths (P3 and P4). + +![Diagram of Segment B-C-D showing multiple protection resources (blue and orange lines) entering a segment cylinder labeled 'Segment B-C-D'. The diagram is labeled G.808.3(12)_FI.4.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +Diagram of Segment B-C-D showing multiple protection resources (blue and orange lines) entering a segment cylinder labeled 'Segment B-C-D'. The diagram is labeled G.808.3(12)\_FI.4. + +**Figure I.4 – Detail of Segment B-C-D** + +#### **Scenario 4** + +A particular resource used for protection can be an end point for some protection paths and an intermediate point for other protection paths. + +| Colour | Working path | Protection path | +|-----------------|--------------|-----------------| +| Orange (W4, P4) | B- A-D | B-C-D | +| Pink (W5, P5) | H-E | H-G-F-E | +| Purple (W6, P6) | B-G | B-C-D-E-F-G | + +For example, in Figure I.2, Node G, and in particular the port associated with the link G-F, illustrates how the protection resource can be an intermediate point for a path (i.e., P5) and an end point for another path (i.e., P6). Similarly Node D, and in particular the port associated with the link D-C, is an intermediate point for P6 and an end point for P4. + +#### Scenario 5 + +A working path may be a member of multiple disjoint shared risk groups (SRGs). + +| Colour | Working path | Protection path | +|-----------------|--------------|-----------------| +| Blue (W3, P3) | A-B | B-C-D-E-F-G-H-A | +| Orange (W4, P4) | B- A-D | B-C-D | +| Pink (W5, P5) | H-E | H-G-F-E | +| Purple (W6, P6) | B-G | B-C-D-E-F-G | + +As shown in Figure I.5, W6 (in purple) is a member of three shared risk groups: W6 and W4 represent a SRG because of protection segment B-C-D; W6 and W3 represent the second SRG because of protection segment D-E-F-G; W6 and W5 represent the third SRG because of protection segment E-F-G. + +In this case, W3 and W5 also represent an SRG because of segments E-F-G, but W4 and W5 do not represent a SRG since they do not share protection resource (i.e., there are two protection resources available in segment B-C-D). Thus, W4 can share risk with both W3 and W5. + +![Diagram illustrating the detail of Segment B-C-D and Segment D-E-F-G. It shows three cylindrical segments: 'Segment B-C-D' at the top, 'Link D-E' at the bottom left, and 'Segment E-F-G' at the bottom right. Each segment has multiple colored lines (representing paths) entering or exiting it. The 'Segment B-C-D' has four lines entering from the left. The 'Link D-E' has four lines exiting to the left and four lines entering from the right. The 'Segment E-F-G' has four lines exiting to the right and four lines entering from the left. The lines are color-coded: blue, orange, pink, and purple. A small label 'G.808.3(12)_FI.5' is visible at the bottom right of the diagram.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +Diagram illustrating the detail of Segment B-C-D and Segment D-E-F-G. It shows three cylindrical segments: 'Segment B-C-D' at the top, 'Link D-E' at the bottom left, and 'Segment E-F-G' at the bottom right. Each segment has multiple colored lines (representing paths) entering or exiting it. The 'Segment B-C-D' has four lines entering from the left. The 'Link D-E' has four lines exiting to the left and four lines entering from the right. The 'Segment E-F-G' has four lines exiting to the right and four lines entering from the left. The lines are color-coded: blue, orange, pink, and purple. A small label 'G.808.3(12)\_FI.5' is visible at the bottom right of the diagram. + +Figure I.5 – Detail of the Segment B-C-D and Segment D-E-F-G + +#### Scenario 6 + +A protection resource associated with one node may support multiple protection paths. While each of the protection paths is a point-to-point connection, if the paths happen to share some resources, there are some elements of point-to-multipoint and multipoint-to-point circuits that must be taken into account when setting up monitoring of the protection path. + +| Colour | Working path | Protection path | +|-----------------|--------------|-----------------| +| Orange (W4, P4) | B- A-D | B-C-D | +| Purple (W6, P6) | B-G | B-C-D-E-F-G | + +As shown in Figure I.6, the port associated with Node B that terminates segment B-C-D illustrates a scenario where two protection paths (i.e., P4 and P6) share segment B-C-D, but P4 and P6 have different end nodes (i.e., P4 ends in Node D, P6 ends in Node G). At any point in time, at the port in Node B, there will either be no path, or P4, or P6. Because of this, care must be taken in the configuration of trail trace identifier (TTI) values and trace identifier mismatch defect (dTIM) detection criteria in the case where there is to be a tandem connection that monitors the entire protection path. + +![Diagram of Segment B-C-D showing five stacked cylinders with red lines on the left and the label 'Segment B-C-D' inside the top cylinder. The text 'G.808.3(12)_FI.6' is at the bottom right.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +A diagram showing a vertical stack of five white cylinders. To the left of the cylinders, there are three horizontal red lines. The top cylinder is filled with a light blue color and contains the text "Segment B-C-D". Below the cylinders, the text "G.808.3(12)\_FI.6" is written in a small font. + +Diagram of Segment B-C-D showing five stacked cylinders with red lines on the left and the label 'Segment B-C-D' inside the top cylinder. The text 'G.808.3(12)\_FI.6' is at the bottom right. + +**Figure I.6 – Detail of Segment B-C-D** + +These scenarios need to be taken into account when designing the APS protocol and monitoring architectures. + +# Appendix II + +## Overview of shared mesh restoration (SMR) and shared mesh protection (SMP) operation + +(This appendix does not form an integral part of this Recommendation.) + +[ITU-T G.805] describes transport network availability enhancement techniques, where "protection" denotes replacement of a failed resource with a pre-assigned standby and "restoration" denotes replacement of a failed resource by re-routing using spare capacity. + +[b-ITU-T G.8080] describes protection as a mechanism for enhancing availability of a connection through the use of additional, assigned capacity. Automatically switched optical network (ASON) restoration of a call (connection service) is described as the replacement of a failed connection by re-routing the call using spare capacity. + +Different mechanisms have been defined for restoration in ASON networks. Note that the restoration mechanism that has the greatest similarity to SMP is often called shared mesh restoration with pre-calculated and pre-signalled restoration paths. This means that upon the successful creation of a new connection along its nominal/active path, a backup path is calculated (which should be fully disjoint with respect to the nominal/active path). A signalling session is subsequently established along this backup path and the availability of free resources checked during the establishment of the signalling session. Once, this process is complete, the backup path is activated when the nominal/active path is affected by a failure. + +Figure II.1, illustrates the distinction between ASON shared mesh restoration and SMP. + +![Diagram illustrating the distinction between ASON shared mesh restoration (SMR) and shared mesh protection (SMP).](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +The diagram illustrates the network architecture and failure recovery processes for SMR and SMP. At the top, a 'Planning tool/PCE/NMS' block is connected to two configuration blocks: 'ASON auto-configuration' (for SMR) and '\*NMS or ASON auto-configuration' (for SMP). The planning tool outputs 'the working paths and the restoration paths' to both. The SMR path involves 'Configure the working connections \*' and leads to a network diagram where a 'Working connection fails', triggering 'ASON signalling to activate the restoration connection'. The SMP path involves 'Configure the working connections and protection paths' and leads to the same network diagram where a 'Working connection fails', triggering 'SMP signalling to activate the protection connection'. The network diagram shows two working connections (1 and 2) and three protection paths (1, 2, and 3, where 3 is shared). Nodes are labeled A, B, C, D, E, F, and PB1-PB5. A note at the bottom states '\* SMP is independent of control plane'. + +NOTE – ASON may either: + +- Activate a pre-planned restoration path +- Compute and activate a new restoration path + +\* SMP is independent of control plane + +G.808.3(12)\_FII.1 + +Diagram illustrating the distinction between ASON shared mesh restoration (SMR) and shared mesh protection (SMP). + +Figure II.1 – SMR and SMP + +# Bibliography + +- [b-ITU-T G.8080] Recommendation ITU-T G.8080/Y.1304 (2012), *Architecture for the automatically switched optical network*. +- [b-BLTJ.1999] Doshi, B. T. et al. (1999), *Optical network design and restoration*, Bell Labs. Technical Journal, pp. 58-84, Jan.-Mar. 1999. + + + + + +## 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.811.1-201708-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/G/T-REC-G.811.1-201708-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e833b57236e86b7d4a316962451f15c987da0559 --- /dev/null +++ b/marked/G/T-REC-G.811.1-201708-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:458648899db3b571932f7abfaebc00a85dcc4bf58d2b407601a08107f5f55fb0 +size 6997 diff --git a/marked/G/T-REC-G.811.1-201708-I_PDF-E/925f55ce69802b9d3b00546382663ee2_img.jpg b/marked/G/T-REC-G.811.1-201708-I_PDF-E/925f55ce69802b9d3b00546382663ee2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d65b544ba1aa488b627cb25bfb196e3a0279a4b --- /dev/null +++ b/marked/G/T-REC-G.811.1-201708-I_PDF-E/925f55ce69802b9d3b00546382663ee2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fde5fd107e5de07c6269387be27f538a3df44f1fb9ed343f11a954429f19cc8 +size 128824 diff --git a/marked/G/T-REC-G.811.1-201708-I_PDF-E/adb1f42239329fa8283d1a40005f989f_img.jpg b/marked/G/T-REC-G.811.1-201708-I_PDF-E/adb1f42239329fa8283d1a40005f989f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc56dac0863e41133a8fab9cf834afb62edb855e --- /dev/null +++ b/marked/G/T-REC-G.811.1-201708-I_PDF-E/adb1f42239329fa8283d1a40005f989f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6538f2e3da40f3ad50903f75f3d572ee6abd03071dde97a3fb99b398fcf4a639 +size 86339 diff --git a/marked/G/T-REC-G.811.1-201708-I_PDF-E/raw.md b/marked/G/T-REC-G.811.1-201708-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..64b6dc3bb15d435d633e41fa2472a0e906d79582 --- /dev/null +++ b/marked/G/T-REC-G.811.1-201708-I_PDF-E/raw.md @@ -0,0 +1,319 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.811.1** + +(08/2017) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital networks – Design objectives for digital networks + +# --- **Timing characteristics of enhanced primary reference clocks** + +Recommendation ITU-T G.811.1 + +**ITU-T** + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it, symbolizing global communication. + +International +Telecommunication +Union + +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 | +| General aspects | G.800–G.809 | +| Design objectives for digital networks | G.810–G.819 | +| Synchronization, quality and availability targets | G.820–G.829 | +| Network capabilities and functions | G.830–G.839 | +| SDH network characteristics | G.840–G.849 | +| Management of transport network | G.850–G.859 | +| SDH radio and satellite systems integration | G.860–G.869 | +| Optical transport networks | G.870–G.879 | +| 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.811.1 + +# Timing characteristics of enhanced primary reference clocks + +## Summary + +Recommendation ITU-T G.811.1 outlines the requirements for enhanced primary reference clocks (ePRCs) suitable for frequency synchronization. These requirements apply under normal environmental conditions specified for the equipment. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.811.1 | 2017-08-13 | 15 | 11.1002/1000/13301 | + +## Keywords + +ePRC, ePRTC, frequency synchronization. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|--------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Frequency accuracy ..... | 2 | +| 7 Noise generation ..... | 2 | +| 7.1 Wander ..... | 3 | +| 7.2 Jitter ..... | 4 | +| 8 Phase discontinuity ..... | 4 | +| 9 Degradation of the performance of an ePRC..... | 5 | +| 10 Interfaces..... | 5 | +| Bibliography..... | 6 | + + + +## Recommendation ITU-T G.811.1 + +## Timing characteristics of enhanced primary reference clocks + +## 1 Scope + +This Recommendation outlines the requirements for enhanced primary reference clocks (ePRCs) suitable for frequency synchronization. These requirements apply under normal environmental conditions specified for the equipment. + +The ePRC provides the reference signal for the timing or synchronization of other clocks within a network or section of a network. In particular, the ePRC in its autonomous form can provide a frequency input to an enhanced primary reference time clock (ePRTC). This Recommendation defines the ePRC output, but it does not apply to the output of a slave clock directly fed by an ePRC. The long-term accuracy of the ePRC should be maintained at 1 part in $10^{12}$ or better, with verification to coordinated universal time (UTC). An ePRC may be realized as an autonomous clock, operating independently of other sources. Alternatively, the ePRC may be realized as a non-autonomous clock which is disciplined by UTC-derived precision signals received from a radio or satellite system. In either case, the requirements for long-term accuracy and short-term stability, as specified in this Recommendation, apply. + +Several classes of ePRCs are being considered. This version specifies ePRC class A. Other classes are for further study. + +The long-term accuracy specified in this Recommendation is adequate when a single ePRC provides the reference synchronization signal to all other clocks within a network (synchronous mode of operation). In the pseudo-synchronous mode, i.e., not all clocks in the network have timing traceable to the same ePRC, the long-term accuracy is dependent on the number of ePRCs in that network. + +When more than one ePRC is used in a network, a statistical approach is needed to determine the long-term accuracy of each ePRC in that network. + +## 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.703] Recommendation ITU-T G.703 (2016), *Physical/electrical characteristics of hierarchical digital interfaces*. +- [ITU-T G.810] Recommendation ITU-T G.810 (1996), *Definitions and terminology for synchronization networks*. +- [ITU-T G.8260] Recommendation ITU-T G.8260 (2015), *Definitions and terminology for synchronization in packet networks*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +The terms and definitions used in this Recommendation are contained in [ITU-T G.810] and [ITU-T G.8260]. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|---------------------------------------| +| CMI | Coded Mark Inversion | +| ePRC | enhanced Primary Reference Clock | +| ePRTC | enhanced Primary Reference Time Clock | +| FPM | Flicker Phase Modulation | +| MTIE | Maximum Time Interval Error | +| NE | Network Element | +| OAM | Operations and Maintenance | +| PLL | Phase Locked Loop | +| PRC | Primary Reference Clock | +| PRTC | Primary Reference Time Clock | +| SDH | Synchronous Digital Hierarchy | +| SEC | SDH Equipment Clock | +| SSMB | Synchronization Status Message Byte | +| STM | Synchronous Transport Module | +| TDEV | Time Deviation | +| UI | Unit Interval | +| UTC | Coordinated Universal Time | +| WFM | White Frequency Modulation | + +## 5 Conventions + +None. + +## 6 Frequency accuracy + +The maximum allowable fractional frequency offset for observation times greater than one week is 1 part in $10^{12}$ , over all applicable operational conditions. + +## 7 Noise generation + +The noise generation of an ePRC represents the amount of phase noise produced at its output. A suitable reference, for practical testing purposes, implies a performance level that is more stable than the output requirements. The ability of the clock to limit this noise is described by its frequency stability. The measures, maximum time interval error (MTIE) and time deviation (TDEV) are useful for characterization of noise generation performance. + +Both MTIE and TDEV are measured through an equivalent 10 Hz, first-order, low-pass measurement filter, at a maximum sampling time, $\tau_0$ , of 1/30 seconds. The minimum measurement period, $T$ , for + +TDEV is twelve times the integration period, $\tau$ ( $T = 12\tau$ ). For measurements over longer observation periods, alternative filter bandwidth and sampling time may be required for practical considerations. + +### 7.1 Wander + +The wander, expressed in MTIE and measured using the independent clock configuration defined in Figure 2a of [ITU-T G.810], should have the limits as shown in Table 1 and Figure 1: + +**Table 1 – Wander generation (MTIE)** + +| MTIE limit [ $\mu\text{s}$ ] | Observation interval $\tau$ [s] | +|----------------------------------------|---------------------------------| +| .004 | $0.1 < \tau \leq 1$ | +| $0.11114 \times 10^{-3}\tau + 0.00389$ | $1 < \tau \leq 100$ | +| $0.0375 \times 10^{-6}\tau + 0.015$ | $100 < \tau \leq 1000$ | +| $10^{-6}\tau + 0.0140375$ | $\tau > 1000$ | + +![Figure 1: MTIE as a function of an observation (integration) period τ. The graph is a log-log plot with MTIE on the y-axis (1 ns to 1 ms) and τ on the x-axis (0.1 s to 100 M s). The curve shows a piecewise linear increase on the log-log scale, corresponding to the formulas in Table 1. The curve starts at approximately 5 ns for τ = 0.1 s, rises to about 15 ns at τ = 100 s, and then continues to rise more steeply to 100 μs at τ = 100 M s. A small label 'G.811.1(17)_F01' is present at the bottom right of the graph area.](925f55ce69802b9d3b00546382663ee2_img.jpg) + +Figure 1: MTIE as a function of an observation (integration) period τ. The graph is a log-log plot with MTIE on the y-axis (1 ns to 1 ms) and τ on the x-axis (0.1 s to 100 M s). The curve shows a piecewise linear increase on the log-log scale, corresponding to the formulas in Table 1. The curve starts at approximately 5 ns for τ = 0.1 s, rises to about 15 ns at τ = 100 s, and then continues to rise more steeply to 100 μs at τ = 100 M s. A small label 'G.811.1(17)\_F01' is present at the bottom right of the graph area. + +**Figure 1 – MTIE as a function of an observation (integration) period $\tau$** + +The wander, expressed in TDEV and measured using the independent clock configuration defined in Figure 2a of [ITU-T G.810], should have the limits as shown in Table 2 and shown in Figure 2: + +**Table 2 – Wander generation (TDEV)** + +| TDEV limit [ns] | Observation interval $\tau$ [s] | +|-----------------|---------------------------------| +| 1 | $0.1 < \tau \leq 10000$ | + +![Figure 2: A log-log plot showing TDEV (Time Deviation) as a function of an observation (integration) period τ. The y-axis (TDEV) ranges from 100 ps to 10 ns, with major ticks at 100 ps, 1 ns, and 10 ns. The x-axis (τ) ranges from 0.1 s to 10 k s, with major ticks at 0.1, 1, 10, 100, 1 k, and 10 k. A horizontal blue line is plotted at 1 ns across the entire x-axis range. The plot is labeled G.811.1(17)_F02.](adb1f42239329fa8283d1a40005f989f_img.jpg) + +Figure 2: A log-log plot showing TDEV (Time Deviation) as a function of an observation (integration) period τ. The y-axis (TDEV) ranges from 100 ps to 10 ns, with major ticks at 100 ps, 1 ns, and 10 ns. The x-axis (τ) ranges from 0.1 s to 10 k s, with major ticks at 0.1, 1, 10, 100, 1 k, and 10 k. A horizontal blue line is plotted at 1 ns across the entire x-axis range. The plot is labeled G.811.1(17)\_F02. + +**Figure 2 – TDEV as a function of an observation (integration) period $\tau$** + +NOTE – Longer observation time and corresponding TDEV mask is for further study. + +### 7.2 Jitter + +While most specifications in this Recommendation are independent of the output interface at which they are measured, this is not the case for jitter production; jitter generation specifications must utilize existing specifications that are currently specified differently for different interface rates. These requirements are stated separately for the interfaces identified in clause 8. To be consistent with other jitter requirements, the specifications are in UIpp, where the unit interval (UI) corresponds to the reciprocal of the bit rate of the interface. + +The intrinsic jitter at 2048 kHz and 2048 kbit/s output interfaces as measured over a 60-second interval shall not exceed 0.05 UIpp when measured through a single pole band-pass filter with corner frequencies at 20 Hz and 100 kHz. + +The intrinsic jitter at 1544 kbit/s output interfaces as measured over a 60-second interval shall not exceed 0.015 UIpp when measured through a single pole band-pass filter with corner frequencies at 10 Hz and 40 kHz. + +The intrinsic jitter at 10 MHz output interfaces as measured over a 60-second interval shall not exceed 0.01 UIpp when measured through a single pole band-pass filter with corner frequencies at 20 Hz and 100 kHz. + +## 8 Phase discontinuity + +Primary reference clocks need a very high level of reliability and are likely to include replication of the equipment to ensure the continuity of the output. However, any phase discontinuity, due to internal operations within the clock, should only result in a lengthening or shortening of the timing signal interval and must not, at the clock output, cause a phase discontinuity in excess of 1/8 UI over a period of time up to 60 seconds (this refers to output signals at 1544 kbit/s, 2048 kbit/s, 2048 kHz, or 10 MHz). + +## 9 Degradation of the performance of an ePRC + +If redundancy is applied and a clock frequency departs significantly from its nominal value, this should be detected and switching to an undegraded oscillator should then be effected. This switching should be accomplished before the MTIE or TDEV specification is exceeded. + +## 10 Interfaces + +The requirements in this Recommendation are related to reference points, which may be internal to the equipment or network element (NE) in which the ePRC is embedded and are, therefore, not necessarily available for measurement or analysis by the user. Consequently, the performance of the ePRC is not specified at these internal reference points, but rather at the external interfaces of the equipment. The output interfaces specified for the equipment in which the ePRC clock may be contained are: + +- 2048 kHz interfaces according to clause 15 of [ITU-T G.703] with additional jitter and wander requirements as specified herein; +- 1544 kbit/s interfaces according to clause 7 of [ITU-T G.703] with additional jitter and wander requirements as specified herein; +- 2048 kbit/s interfaces according to clause 11 of [ITU-T G.703] with additional jitter and wander requirements as specified herein; +- 10 MHz interfaces according to [ITU-T G.703]; + +NOTE – 10 MHz interfaces may be available on autonomous ePRCs. 10 MHz interfaces may be required in the future when evolving an existing autonomous ePRC into an ePRTC. Such interfaces may provide an improvement in phase noise performance. + +- other interfaces (such as sine wave 8 kHz to 5 MHz) are for further study. + +All of the above interfaces may be implemented on all equipment. + +## Bibliography + +- [b-ITU-T G.783] Recommendation ITU-T G.783 (1997), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks.* +- [b-ITU-T G.811] Recommendation ITU-T G.811 (1997), *Timing characteristics of primary reference clocks.* +- [b-ITU-T G.812] Recommendation ITU-T G.812 (1988), *Timing requirements at the outputs of slave clocks suitable for plesiochronous operation of international digital links.* +- [b-ITU-T G.822] Recommendation ITU-T G.822 (1988), *Controlled slip rate objectives on an international digital connection.* +- [b-ITU-T G.823] Recommendation ITU-T G.823 (1993), *The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy.* +- [b-ITU-T G.824] Recommendation ITU-T G.824 (1993), *The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy.* +- [b-ITU-T G.825] Recommendation ITU-T G.825 (1993), *The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH).* +- [b-ITU-T G.8272.1] Recommendation ITU-T G.8272.1/Y.1367.1 (2016), *Timing characteristics of enhanced primary reference time clocks.* + + + +## 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.820-200407-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.820-200407-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/G/T-REC-G.820-200407-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/G/T-REC-G.820-200407-I_PDF-E/raw.md b/marked/G/T-REC-G.820-200407-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b5840c2968de794392ca8afc90d92ed67ff154b6 --- /dev/null +++ b/marked/G/T-REC-G.820-200407-I_PDF-E/raw.md @@ -0,0 +1,1191 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +# ITU-T G.820/I.351/Y.1501 + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(07/2004) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital networks – Quality and availability targets + +SERIES I: INTEGRATED SERVICES DIGITAL +NETWORK + +Overall network aspects and functions – Performance +objectives + +SERIES Y: GLOBAL INFORMATION +INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS +AND NEXT GENERATION NETWORKS + +Internet protocol aspects – Quality of service and network +performance + +--- + +**Relationships among ISDN, IP-based network +and physical layer performance +Recommendations** + +ITU-T Recommendation G.820/I.351/Y.1501 + +--- + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TESTING EQUIPMENTS | G.500–G.599 | +| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 | +| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| General aspects | G.800–G.809 | +| Design objectives for digital networks | G.810–G.819 | +| Quality and availability targets | G.820–G.829 | +| Network capabilities and functions | G.830–G.839 | +| SDH network characteristics | G.840–G.849 | +| Management of transport network | G.850–G.859 | +| SDH radio and satellite systems integration | G.860–G.869 | +| Optical transport networks | G.870–G.879 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | +| QUALITY OF SERVICE AND PERFORMANCE - GENERIC AND USER-RELATED ASPECTS | G.1000–G.1999 | +| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 | +| DIGITAL TERMINAL EQUIPMENTS | G.7000–G.7999 | +| DIGITAL NETWORKS | G.8000–G.8999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **ITU-T Recommendation G.820/I.351/Y.1501** + +# **Relationships among ISDN, IP-based network and physical layer performance Recommendations** + +## **Summary** + +This Recommendation defines relationships among a set of existing ITU-T Recommendations that collectively provide the basis for the specification and apportionment of performance in narrow-band and broadband ISDNs, Internet Protocol (IP)-based networks, and digital layers of transport networks, as well as jitter, wander, and network synchronization and timing performance. These Recommendations are intended to be used in describing performance between the measurement points that delimit and apportion international ISDNs, IP-based networks, and digital layers of transport networks. + +## **Source** + +ITU-T Recommendation G.820/I.351/Y.1501 was approved on 29 July 2004 by ITU-T Study Group 13 (2001-2004) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2004 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +###### Page + +| | | | +|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|---| +| 1 | Scope ..... | 1 | +| 2 | Abbreviations..... | 3 | +| 3 | General scope and content of performance Recommendations..... | 4 | +| 3.1 | ITU-T Rec. G.781 – Synchronization layer functions (1999)..... | 4 | +| 3.2 | ITU-T Rec. G.783 – Characteristics of Synchronous Digital Hierarchy (SDH) equipment functional blocks (2004) ..... | 4 | +| 3.3 | ITU-T Rec. G.798 – Characteristics of optical transport network hierarchy equipment functional blocks (2004)..... | 4 | +| 3.4 | ITU-T Rec. G.803 – Architecture of transport networks based on the Synchronous Digital Hierarchy (SDH) (2000)..... | 5 | +| 3.5 | ITU-T Rec. G.810 – Definitions and terminology for synchronization networks (1996)..... | 5 | +| 3.6 | ITU-T Rec. G.811 – Timing characteristics of primary reference clocks (1997) ..... | 5 | +| 3.7 | ITU-T Rec. G.812 – Timing requirements of slave clocks suitable for use as node clocks in synchronization networks (2004)..... | 5 | +| 3.8 | ITU-T Rec. G.813 – Timing characteristics of SDH equipment slave clocks (SEC) (2003) ..... | 5 | +| 3.9 | ITU-T Rec. G.821 – Error performance of an international digital connection operating at a bit rate below the primary rate and forming part of an ISDN (2002)..... | 6 | +| 3.10 | ITU-T Rec. G.822 – Controlled slip rate objectives on an international digital connection (1988)..... | 6 | +| 3.11 | ITU-T Rec. G.823 – The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy (2000) ..... | 6 | +| 3.12 | ITU-T Rec. G.824 – The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy (2000) ..... | 6 | +| 3.13 | ITU-T Rec. G.825 – The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH) (2000) ..... | 6 | +| 3.14 | ITU-T Rec. G.826 – End-to-end error performance parameters and objectives for international, constant bit-rate digital paths and connections (2002) ..... | 7 | +| 3.15 | ITU-T Rec. G.827 – Availability performance parameters and objectives for end-to-end international constant bit-rate digital paths (2003)..... | 7 | +| 3.16 | ITU-T Rec. G.828 – Error performance parameters and objectives for international, constant bit-rate synchronous digital paths (2000) ..... | 7 | +| 3.17 | ITU-T Rec. G.829 – Error performance events for SDH multiplex and regenerator sections (2002) ..... | 8 | +| 3.18 | ITU-T Rec. G.921 – Digital sections based on the 2048 kbit/s hierarchy (1988) ..... | 8 | + +| | | | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 3.19 | ITU-T Rec. G.8201 – Error performance parameters and objectives for multi-operator international paths within the Optical Transport Network (OTN) (2003)..... | 8 | +| 3.20 | ITU-T Rec. G.8251 – The control of jitter and wander within the Optical Transport Network (OTN) (2001) ..... | 9 | +| 3.21 | ITU-T Rec. I.350 – General aspects of quality of service and network performance in digital networks, including ISDNs (1993) ..... | 9 | +| 3.22 | ITU-T Rec. I.352 – Network performance objectives for connection processing delays in an ISDN (1993)..... | 9 | +| 3.23 | ITU-T Rec. I.353 – Reference events for defining ISDN and B-ISDN performance parameters (1996)..... | 9 | +| 3.24 | ITU-T Rec. I.354 – Network performance objectives for packet-mode communication in an ISDN (1993) ..... | 9 | +| 3.25 | ITU-T Rec. I.355 – ISDN 64 kbit/s connection type availability performance (2000) ..... | 10 | +| 3.26 | ITU-T Rec. I.356 – B-ISDN ATM layer cell transfer performance (2000) ... | 10 | +| 3.27 | ITU-T Rec. I.357 – B-ISDN semi-permanent connection availability (2000) ..... | 10 | +| 3.28 | ITU-T Rec. I.358 – Call processing performance for switched Virtual Channel Connections (VCCs) in a B-ISDN (2003) ..... | 10 | +| 3.29 | ITU-T Rec. I.359 – Accuracy and dependability of ISDN 64 kbit/s circuit mode connection types (1999)..... | 11 | +| 3.30 | ITU-T Rec. I.381 – ATM Adaptation Layer (AAL) Performance (2001) ..... | 11 | +| 3.31 | ITU-T Rec. Y.1530 – Call processing performance for voice service in hybrid IP networks (2004)..... | 11 | +| 3.32 | ITU-T Rec. Y.1540 – Internet protocol data communication service – IP packet transfer and availability performance parameters (2002) ..... | 11 | +| 3.33 | ITU-T Rec. Y.1541 – Network performance objectives for IP-based services (2002)..... | 11 | +| 3.34 | ITU-T Rec. Y.1560 – Parameters for TCP connection performance in the presence of middleboxes (2003)..... | 12 | +| 3.35 | ITU-T Rec. Y.1561 – Performance and availability parameters for MPLS networks (2004)..... | 12 | +| Annex A | – History of the G-series error performance Recommendations..... | 12 | +| A.1 | Background on the content of Annex A ..... | 12 | +| A.2 | History of the G-series error performance Recommendations..... | 12 | +| INDEX | ..... | 15 | + +# **Relationships among ISDN, IP-based network and physical layer performance Recommendations** + +# **1 Scope** + +This Recommendation describes relationships among the following ITU-T Recommendations: G.781, G.783, G.798, G.803, G.810, G.811, G.812, G.813, G.821, G.822, G.823, G.824, G.825, G.826, G.827, G.828, G.829, G.921, G.8201, G.8251, I.350, I.352, I.353, I.354, I.355, I.356, I.357, I.358, I.359, I.381, Y.1530, Y.1540, Y.1541, Y.1560 and Y.1561. Collectively, these Recommendations provide the basis for the specification and apportionment of performance in narrow-band and broadband ISDNs, Internet Protocol (IP)-based networks, and digital layers of transport networks. They include jitter, wander, and network synchronization and timing performance. These Recommendations are intended to be used in describing performance between the measurement points that delimit and apportion international ISDNs, IP-based networks, and digital layers of transport networks. + +The relevant Recommendations and their relationships are illustrated in Figure 1. The $3 \times 3$ performance description framework defined in ITU-T Rec. I.350 is used to illustrate the relationships among particular Recommendations. Three protocol-independent telecommunication functions are identified in the matrix: access, user information transfer, and disengagement. These general functions correspond to specified aspects of ISDN, IP-based network, and transport network digital layer services conforming to ITU-T standardized protocols1. Each function is considered with respect to three general performance concerns (or "performance criteria"): speed, accuracy, and dependability. These express, respectively, the delay or rate, degree of correctness, and degree of certainty with which the function is performed. Recommendations shown within the matrix define sets of protocol-specific parameters ("primary parameters") that describe performance relative to each function and criterion. An associated model provides a basis for describing overall service availability. A specified availability function compares the values for a subset of the primary parameters with corresponding outage thresholds to classify the services as "available" (no service outage) or "unavailable" (service outage) during scheduled service time. Figure 1 presents the Recommendations that specify availability functions and define availability parameters associated with ISDN, IP-based network, and transport network digital layer services. Recommendations concerning jitter, wander, and timing and synchronization performance of digital networks are illustrated in Figure 1 by their relationships to the complementary aspects of network level jitter, wander, and synchronization performance and related timing equipment performance. + +This Recommendation is organized as follows. The scope of the Recommendation is provided in clause 1. A list of abbreviations is provided in clause 2. The general scope and content of each Recommendation illustrated in Figure 1 is described in clause 32. Annex A contains information on the history of the G-series physical layer error performance Recommendations. An index listing key concepts and associated Recommendations is also provided. + +--- + +1 For B-ISDN, these general functions include multiparty and multipoint connection types. + +2 The most recent editions of draft and approved Recommendations should be consulted. + +| General performance aspects of ISDNs, IP-based networks and digital layers of transport networks | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| +| I.350 (QoS/Network performance framework in digital networks, including ISDNs)
I.353 (Reference events for defining ISDN performance parameters) | | | | +| ↓ | | | | +| ISDN, IP-based network and transport network digital layer performance | | | | +| Criterion
Function | Speed | Accuracy | Dependability | +| Access | I.352 (N-ISDN – CBR)
I.354 (N-ISDN – PKT)
I.358 (B-ISDN)
Y.1530 (IP)
Y.1560 (TCP) | I.354 (N-ISDN – PKT)
I.358 (B-ISDN)
I.359 (N-ISDN – CBR)
Y.1530 (IP)
Y.1560 (TCP) | I.354 (N-ISDN – PKT)
I.358 (B-ISDN)
I.359 (N-ISDN – CBR)
Y.1530 (IP)
Y.1560 (TCP) | +| Information transfer | I.354 (N-ISDN – PKT)
I.356 (ATM)
I.381 (AAL)
Y.1540 (IP)
Y.1541 (IP)
Y.1561 (MPLS) | G.821 (CBR)
G.826 (CBR)
G.828 (CBR)
G.829 (CBR)
G.921 (CBR)
G.8201 (OTN)
I.354 (N-ISDN – PKT)
I.356 (ATM)
I.381 (AAL)
Y.1540 (IP)
Y.1541 (IP)
Y.1561 (MPLS) | I.354 (N-ISDN – PKT)
I.356 (ATM)
Y.1540 (IP)
I.381 (AAL)
Y.1541 (IP)
Y.1561 (MPLS) | +| Disengagement | I.352 (N-ISDN – CBR)
I.354 (N-ISDN – PKT)
I.358 (B-ISDN)
Y.1530 (IP)
Y.1560 (TCP) | I.354 (N-ISDN – PKT)
I.358 (B-ISDN)
I.359 (N-ISDN – CBR)
Y.1530 (IP)
Y.1560 (TCP) | I.354 (N-ISDN – PKT)
I.358 (B-ISDN)
I.359 (N-ISDN – CBR)
Y.1530 (IP)
Y.1560 (TCP) | +| ↓ | | | | +| Availability | | | | +| G.827 (B-ISDN – CBR)
I.355 (N-ISDN – CBR & PKT)
I.357 (ATM)
Y.1540 (IP)
Y.1541 (IP) | | | | +| ↓ | | | | +| Timing and synchronization performance | | | | +| Network level jitter, wander, and synchronization | | Equipment jitter, wander and timing | | +| G.803 (Network Synchronization Architecture)
G.810 (Terminology)
G.822 (Slips)
G.823 (Jitter/Wander – 2048 kbit/s Hierarchy)
G.824 (Jitter/Wander – 1544 kbit/s Hierarchy)
G.825 (Jitter/Wander – SDH)
G.8251 (Jitter/Wander – OTN) | | G.781 (Synchronization Distribution Layer and Network Synchronization Layer Atomic Functions)
G.783 (Jitter/Wander – SDH Equipment)
G.798 (OTN CBR Client Asynchronous Mapper Buffer Hysteresis)
G.810 (Terminology)
G.811 (Primary Reference Clock)
G.812 (Synchronization Supply Unit)
G.813 (SDH Equipment Clock)
G.921 (Jitter – 2048 kbit/s Hierarchy)
G.8251 (Jitter/Wander – OTN Equipment and ODUk Clock) | | + +Figure 1/G.820/I.351/Y.1501 – Relationships among ISDN, IP and transport network digital layer performance Recommendations + +# 2 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|--------|--------------------------------------| +| AAL | ATM Adaptation Layer | +| ATM | Asynchronous Transfer Mode | +| B-ISDN | Broadband ISDN | +| CBR | Constant Bit Rate | +| EDC | Error Detection Code | +| IETF | Internet Engineering Task Force | +| IP | Internet Protocol | +| ISDN | Integrated Services Digital Network | +| kbit/s | kilobit/second | +| LSP | Label Switched Path | +| MRTIE | Maximum Relative Time Interval Error | +| MTIE | Maximum Time Interval Error | +| MPLS | Multi-Protocol Label Switching | +| N-ISDN | Narrow-band ISDN | +| NP | Network Performance | +| ODUk | Optical Channel Data Unit k | +| ODC | ODUk Clock | +| OTN | Optical Transport Network | +| PDH | Plesiochronous Digital Hierarchy | +| PKT | Packet Mode | +| PRC | Primary Reference Clock | +| PVC | Permanent Virtual Connection | +| QoS | Quality of Service | +| SDH | Synchronous Digital Hierarchy | +| SEC | SDH Equipment Clock | +| SSM | Synchronization Status Message | +| SSU | Synchronization Supply Unit | +| STM | Synchronous Transport Module | +| TCP | Transmission Control Protocol | +| TDEV | Time Deviation | +| VC | Virtual Channel | +| VCC | Virtual Channel Connection | +| VPC | Virtual Path Connection | + +# **3 General scope and content of performance Recommendations** + +The general scope and content of each of the ISDN, IP, and transport network digital layer performance Recommendations identified in Figure 1 is summarized below. For ease of reference, the Recommendations are listed alphanumerically. + +## **3.1 ITU-T Rec. G.781 – Synchronization layer functions (1999)** + +This Recommendation specifies mainly the SSM selection algorithm which is applicable to clocks of SDH equipments (ITU-T Rec. G.813). It specifies the synchronization interfaces, the Quality Level of clock sources, the SSM (Synchronization Status Message), the SDH clock selection process, some rules to prevent timing loops in SDH networks and all synchronization distribution basic functions that are required to describe a digital transmission equipment's synchronization functionality. + +This Recommendation specifies 3 different options. "Option I" applies to SDH networks optimized for the 2048 kbit/s hierarchy. "Option II" applies to SDH networks optimized for the 1544 kbit/s hierarchy that includes the rates 1544 kbit/s, 6312 kbit/s, and 44 736 kbit/s. "Option III" applies to SDH networks optimized for the 1544 kbit/s hierarchy that includes the rates 1544 kbit/s, 6312 kbit/s, 33 064 kbit/s, 44 736 kbit/s, and 97 728 kbit/s. + +## **3.2 ITU-T Rec. G.783 – Characteristics of Synchronous Digital Hierarchy (SDH) equipment functional blocks (2004)** + +This Recommendation covers general equipment requirements for SDH equipment. It specifically contains jitter and wander requirements in clauses 9.3 and 15. This includes jitter transfer, jitter tolerance and jitter generation for SDH regenerators, mappers, and demappers, and also wander specifications for SDH mappers and demappers. The jitter requirements for SDH regenerators ensure that the SDH jitter network limits are met. The jitter and wander requirements for SDH mappers and demappers help ensure that the jitter and wander requirements for PDH clients are met. + +## **3.3 ITU-T Rec. G.798 – Characteristics of optical transport network hierarchy equipment functional blocks (2004)** + +This Recommendation covers the functional requirements of Optical Transport Network functionality within equipment. It uses the specification methodology defined in ITU-T Rec. G.806 for transport network equipment and is based on the architecture of optical transport networks defined in ITU-T Rec. G.872 and the interfaces defined in ITU-T Rec. G.709/Y.1331. The portion of ITU-T Rec. G.798 that is relevant to jitter and wander performance (i.e., relevant to the network performance specifications and objectives for which corresponding Recommendations are summarized in ITU-T Rec. G.820/I.351/Y.1501) is the specification of the maximum buffer hysteresis for the asynchronous mapper. + +The requirement on maximum buffer hysteresis for the asynchronous mapper or multiplexer applies to asynchronous mapping of CBRx clients into ODUk (via the ODUkP/CBRx-a\_A\_So atomic function) and asynchronous multiplexing of ODUj clients into ODUk ( $k > j$ , via the ODUkP/ODUi[j]\_A\_So atomic function). The main purpose of the requirement on maximum buffer hysteresis for the asynchronous mapper or multiplexer is to limit the long-term wander on CBRx clients. + +## **3.4 ITU-T Rec. G.803 – Architecture of transport networks based on the Synchronous Digital Hierarchy (SDH) (2000)** + +Clause 8 of this Recommendation gives the rules that must be applied to build a synchronization network so that the requirements of synchronization interfaces are met. It specifies the synchronization network architecture, the clock synchronization modes, the synchronization network reference chain that gives the maximum number of clocks a synchronization signal can pass through, the synchronization strategy, how to deal with network evolution, and network robustness. It provides methods to prevent timing loops between SSUs, and also between SECs by use of the SSM. ITU-T Rec. G.803 also provides information on payload jitter and wander, pointer simulations and jitter at SDH/PDH boundaries, and PDH/SDH interworking. + +## **3.5 ITU-T Rec. G.810 – Definitions and terminology for synchronization networks (1996)3** + +This Recommendation provides definitions and terms for describing network timing, jitter, and synchronization performance. These definitions and terms are used in ITU-T Recs G.781, G.783, G.798, G.803, G.811, G.812, G.813, G.822, G.823, G.824, G.825, G.8251 and G.921. + +## **3.6 ITU-T Rec. G.811 – Timing characteristics of primary reference clocks (1997)** + +This Recommendation defines specifications for the Primary Reference Clock (PRC). The specifications utilize G.810 parameters and terminology. Key parameters are frequency accuracy, MTIE, TDEV, phase discontinuity, and peak-to-peak jitter. + +The specifications apply to PRC jitter and wander performance. This Recommendation provides part of the basis for the slip performance objectives in ITU-T Rec. G.822 and the wander reference models in ITU-T Recs G.823 and G.824. + +## **3.7 ITU-T Rec. G.812 – Timing requirements of slave clocks suitable for use as node clocks in synchronization networks (2004)** + +This Recommendation defines specifications for slave clocks (i.e., timing equipment synchronization supply units). The specifications utilize G.810 parameters and terminology. Key parameters are frequency accuracy, pull-in, pull-out, and hold-in ranges, MTIE, TDEV, phase discontinuity, and peak-to-peak jitter. Six clock types are defined, designated Type I through VI, respectively. + +The specifications apply to slave clock jitter, wander, transient, and holdover performance. Clock types I, V and VI are intended for PDH networks of the 2048 kbit/s hierarchy and SDH networks optimized for this hierarchy. Clock types II, III and IV are intended for PDH networks of the 1544 kbit/s hierarchy and SDH networks optimized for this hierarchy. + +## **3.8 ITU-T Rec. G.813 – Timing characteristics of SDH equipment slave clocks (SEC) (2003)** + +This Recommendation defines specifications for SDH equipment clocks. The specifications utilize G.810 parameters and terminology. Key parameters are frequency accuracy, pull-in, pull-out, and hold-in ranges, MTIE, TDEV, and peak-to-peak jitter. Two Options for the SDH Equipment Clock are defined, designated Option 1 and Option 2, respectively. + +The specifications apply to SDH Equipment Clock jitter, wander, transient, and holdover performance. Option 1 applies to SDH networks optimized for the 2048 kbit/s hierarchy and Option 2 applies to SDH networks optimized for the particular 1544 kbit/s hierarchy that includes the rates 1544 kbit/s, 6312 kbit/s, and 44 736 kbit/s. + +--- + +3 See also Corrigendum 1, 10-2001. + +## **3.9 ITU-T Rec. G.821 – Error performance of an international digital connection operating at a bit rate below the primary rate and forming part of an ISDN (2002)** + +This Recommendation defines error performance parameters and objectives for international digital connections operating below the primary rate of the digital hierarchy, using equipment designed prior to the adoption of revised ITU-T Rec. G.826 on 14 December 2002. The objectives given are independent of the physical network supporting the connection. This Recommendation is based upon bit error and bit error ratio measurements. The events, parameters and objectives are defined accordingly. Annex A/G.821 deals with the definition of availability of the connection. + +## **3.10 ITU-T Rec. G.822 – Controlled slip rate objectives on an international digital connection (1988)** + +ITU-T Rec. G.822 defines parameters and objectives for describing network controlled slip performance. The parameter definitions utilize G.810 terminology. Key parameters are the mean slip rate and its associated proportion of time. + +The parameters and objectives apply to specified portions of an international digital connection. This Recommendation provides a basis for Option 1 and Option 2 network wander limits in ITU-T Rec. G.813. + +## **3.11 ITU-T Rec. G.823 – The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy (2000)** + +This Recommendation defines specifications for jitter and wander performance for networks based on the 2048 kbit/s hierarchy. The specifications utilize G.810 parameters and terminology. Key parameters are peak-to-peak jitter and associated measurement filter bandwidths, MTIE, MRTIE, TDEV, and sinusoidal tolerance. + +The specifications apply to jitter and wander tolerance and network limits for PDH traffic interfaces and synchronization interfaces, for networks based on the 2048 kbit/s hierarchy. + +## **3.12 ITU-T Rec. G.824 – The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy (2000)** + +This Recommendation defines specifications for jitter and wander performance for networks based on the 1544 kbit/s hierarchy. The specifications utilize G.810 parameters and terminology. Key parameters are peak-to-peak jitter and associated measurement filter bandwidths, MTIE, MRTIE, TDEV, and sinusoidal tolerance. + +The specifications apply to jitter and wander tolerance and network limits for PDH traffic interfaces and synchronization interfaces, for networks based on the 1544 kbit/s hierarchy. This Recommendation provides input to the Option 2 wander budget and network wander limits in ITU-T Rec. G.813. + +## **3.13 ITU-T Rec. G.825 – The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH) (2000)4** + +This Recommendation defines specifications for jitter and wander performance for SDH networks. The specifications utilize G.810 parameters and terminology. Key parameters are peak-to-peak jitter and associated measurement filter bandwidths, and sinusoidal tolerance (for wander limits, which utilize MTIE, MRTIE, and TDEV parameters). ITU-T Rec. G.825 references ITU-T Recs G.823 and G.824. + +--- + +4 See also Erratum 1, 08-2001. + +The specifications apply to jitter and wander tolerance and network limits for SDH interfaces. ITU-T Rec. G.825 references ITU-T Recs G.783, G.812 and G.813 for jitter and wander generation and transfer requirements. ITU-T Rec. G.825 provides part of the basis for the Option 1 SEC bandwidth specification in ITU-T Rec. G.813. + +## **3.14 ITU-T Rec. G.826 – End-to-end error performance parameters and objectives for international, constant bit-rate digital paths and connections (2002)** + +This Recommendation defines end-to-end error performance parameters and objectives for international digital paths which operate at or above the primary rate, and for international digital connections which operate below the primary rate, of the digital hierarchy. The objectives given are independent of the physical network supporting the path or connection. + +For digital paths which operate at or above the primary rate, this Recommendation is based upon a block-based measurement concept using error detection codes inherent to the path under test. This supports in-service measurements. + +For digital connections which operate below the primary rate of the digital hierarchy, this Recommendation is based upon bit error and bit error ratio measurements. This approach does not support in-service measurements. + +Annex A/G.826 deals with the definition of availability of the path or connection. Annexes B, C and D give specific information concerning PDH, SDH and cell-based transmission paths. + +The ITU-T Rec. G.826 requirements for digital connections apply to connections using equipment designed after the adoption of revised ITU-T Rec. G.826 on 14 December 2002. It is not required to apply this Recommendation to connections using equipment designed prior to that date. + +This Recommendation deals with the performance of PDH paths, and of those SDH paths using equipment designed prior to the adoption of ITU-T Rec. G.828 in March 2000. + +## **3.15 ITU-T Rec. G.827 – Availability performance parameters and objectives for end-to-end international constant bit-rate digital paths (2003)** + +This Recommendation defines network performance parameters and objectives for the path elements and end-to-end availability of international constant bit rate digital paths. These parameters are independent of the type of physical network supporting the end-to-end path, e.g., optical fibre, radio relay or satellite. Guidance is included on methods for improving availability and calculating the end-to-end availability of a combination of network elements. + +## **3.16 ITU-T Rec. G.828 – Error performance parameters and objectives for international, constant bit-rate synchronous digital paths (2000)5** + +This Recommendation defines error performance parameters and objectives for international synchronous digital paths. While this Recommendation specifically addresses objectives for international digital paths, the allocation principles can be applied to the design of error performance for national or private synchronous digital paths. The objectives given are independent of the physical network supporting the path. The Recommendation is based upon a block-based measurement concept using error detection codes inherent to the path under test. The block repetition rate is in accordance with SDH technology. The events, parameters and objectives are defined accordingly. In addition to path performance assessment, tandem connection monitoring is covered. + +ITU-T Rec. G.828 is the only Recommendation required for designing the error performance of synchronous digital paths using equipment installed after the adoption of ITU-T Rec. G.828 in + +--- + +5 See also Corrigendum 1, 07-2001. + +March 2000. In accordance with the definition of a digital path, path end points may be located at user's premises. + +Paths are used to support services such as circuit switched, packet switched and leased circuit services. ITU-T Rec. G.828-based paths can carry ATM traffic. Synchronous digital paths meeting the objectives of ITU-T Rec. G.828 will enable the ATM traffic to meet ITU-T Rec. I.356. + +## **3.17 ITU-T Rec. G.829 – Error performance events for SDH multiplex and regenerator sections (2002)** + +This Recommendation defines error performance events and block structures for SDH multiplex and regenerator sections (see ITU-T Recs G.707/Y.1322 and G.708 for reference). SDH equipment functional blocks and SDH management are defined in ITU-T Recs G.783 and G.784. Observing the definitions given in this Recommendation shall ensure that error performance assessment on SDH multiplex and regenerator sections yields compatible results. Definition of events in this Recommendation is based on the same basic concept as in ITU-T Rec. G.828. + +The events defined for regenerator sections apply to microwave radio and satellite systems only. + +Performance monitoring of SDH sections is not mandatory. If implemented, the specifications of this Recommendation apply. + +## **3.18 ITU-T Rec. G.921 – Digital sections based on the 2048 kbit/s hierarchy (1988)** + +This Recommendation specifies characteristics of digital sections based on the 2048 kbit/s hierarchy. The performance specifications in ITU-T Rec. G.921 (i.e., the portions of ITU-T Rec. G.921 that are relevant to ITU-T Rec. G.820/I.351/Y.1501) include requirements for jitter, error, and availability performance. The jitter specifications utilize G.810 parameters and terminology; key parameters are peak-to-peak jitter and associated measurement filter bandwidths. The error performance specifications refer to ITU-T Rec. G.821 for the performance objectives for the end-to-end connection of which the digital section in question is part. ITU-T Rec. G.921 specifies the allocation of the objective for the end-to-end connection given to the digital section. The error performance specifications utilize events and parameters defined in ITU-T Rec. G.821. The jitter specifications apply to a single regenerator section of the 2048 kbit/s hierarchy. They include output jitter in the absence of input jitter (i.e., jitter generation for a single regenerator), jitter tolerance (ITU-T Rec. G.823 is referenced for these requirements), and jitter transfer. The error performance specifications apply to digital sections of the 2048 kbit/s hierarchy. + +## **3.19 ITU-T Rec. G.8201 – Error performance parameters and objectives for multi-operator international paths within the Optical Transport Network (OTN) (2003)** + +This Recommendation defines error performance parameters and objectives for international ODUk paths transported by the Optical Transport Network (OTN) as described in ITU-T Rec. G.709/Y.1331. While this Recommendation specifically addresses objectives for international ODUk paths, the allocation principles can be applied to the design of error performance for national or private ODUk paths. This Recommendation is based upon a block-based measurement concept using error detection code (EDC) and EDC usage inherent to the path under test; the block repetition rate being in accordance with OTN technology in accordance with ITU-T Rec. G.709/Y.1331. This simplifies in-service measurements. The events, parameters and objectives are defined accordingly. In addition to path performance assessment, tandem connection monitoring is covered. + +## **3.20 ITU-T Rec. G.8251 – The control of jitter and wander within the Optical Transport Network (OTN) (2001)6** + +This Recommendation defines specifications for jitter and wander performance for the Optical Transport Network (OTN). The specifications cover network limits, jitter tolerance of network interfaces, jitter generation, and jitter transfer. The specifications utilize G.810 parameters and terminology. Key parameters are peak-to-peak jitter and associated measurement filter bandwidths, sinusoidal jitter tolerance, maximum bandwidth and gain peaking for jitter transfer, and frequency accuracy, pull-in range, and pull-out range for relevant ODUk clocks. Annex A/G.8251 defines four ODUk clocks: ODCa for the asynchronous mapper, ODCb for the bit-synchronous mapper, ODCr for the 3R regenerator, and ODCp for the demapper or demultiplexer. + +The specifications in the main body apply to jitter and wander tolerance for OTN and client interfaces, and OTN network limits. The specifications in Annex A apply to the ODCa, ODCb, ODCr, and ODCp clocks. The OTN timing and jitter specifications do not distinguish between Option 1 and Option 2 networks; the specifications apply without regard to whether an SDH client is Option 1 or Option 2. + +## **3.21 ITU-T Rec. I.350 – General aspects of quality of service and network performance in digital networks, including ISDNs (1993)** + +This Recommendation defines Quality of Service (QoS) and Network Performance (NP) principles; illustrates how the QoS and NP concepts are applied in digital networks including ISDNs (providing both narrow-band and broadband capabilities); describes the features of, and the relationships between, these concepts; indicates and classifies performance concerns for which parameters may be needed; and identifies generic performance parameters. + +## **3.22 ITU-T Rec. I.352 – Network performance objectives for connection processing delays in an ISDN (1993)** + +This Recommendation defines speed parameters and objectives for describing N-ISDN circuit mode access and disengagement performance. Key parameters are call set-up delay and call clearing delay. The parameters and objectives apply to specified portions of an international end-to-end circuit mode connection. This Recommendation provides a basis for N-ISDN circuit mode availability performance specified in ITU-T Rec. I.355. + +## **3.23 ITU-T Rec. I.353 – Reference events for defining ISDN and B-ISDN performance parameters (1996)** + +This Recommendation defines the measurement points and performance-significant reference events that are used in ITU-T Recs I.352, I.354, I.355, I.356, I.357, I.358 and I.359 to define performance parameters for international ISDN services. + +## **3.24 ITU-T Rec. I.354 – Network performance objectives for packet-mode communication in an ISDN (1993)** + +This Recommendation defines speed, accuracy, and dependability parameters and objectives for describing N-ISDN packet-mode access, information transfer, and disengagement performance. Key parameters are call set-up delay, call set-up denial probability, errored packet ratio, packet loss ratio, and call clearing delay. The parameters and objectives apply to specified portions of an international end-to-end packet mode connection. This Recommendation provides a basis for N-ISDN packet-mode availability performance specified in ITU-T Rec. I.355. + +--- + +6 See also Corrigendum 1, 06-2002 and Amendment 1, 06-2002. + +## **3.25 ITU-T Rec. I.355 – ISDN 64 kbit/s connection type availability performance (2000)** + +This Recommendation defines parameters and objectives for describing N-ISDN circuit mode and packet mode availability performance. The parameters are defined on the basis of G.821, I.352 and I.354 parameter thresholds. Key parameters are percent service availability and mean time between service outages. The parameters and objectives apply to specified portions of international end-to-end N-ISDN circuit mode and packet mode connections. + +## **3.26 ITU-T Rec. I.356 – B-ISDN ATM layer cell transfer performance (2000)7** + +This Recommendation defines speed, accuracy, and dependability parameters and objectives for describing B-ISDN ATM information transfer performance. The key parameters include cell transfer delay, cell delay variation, cell error ratio, cell loss ratio, severely errored cell block ratio, frame transmission delay, and corrupted frame ratio. It includes adjusted parameter definitions that can be used when cell flows do not conform with the negotiated traffic contract. The parameters and objectives apply to specified portions of an end-to-end international B-ISDN ATM connection. Parameter values are grouped into five distinct QoS classes that users may request on a connection-by-connection basis. This Recommendation provides a basis for B-ISDN ATM availability performance specification in ITU-T Rec. I.357. + +## **3.27 ITU-T Rec. I.357 – B-ISDN semi-permanent connection availability (2000)** + +This Recommendation defines network performance parameters, objectives and measurement methods for describing B-ISDN ATM semi-permanent connection availability. The specified parameters and objectives apply to international ATM semi-permanent connection8 portions delimited by measurement points: National Portions, International Transit Portions and International Interoperator Portions. The objectives, which are worst-case values, are intended to assist providers in network planning by limiting the aggregate effect of network impairments, including congestion, equipment failures and transmission errors. Guidance on determining expected end-to-end performance is provided in Annex C/I.357. + +A two-state availability model is defined along with criteria for entry into and exit from the unavailable state. An estimation procedure is also defined, providing a means of estimating availability performance using sampling techniques. + +## **3.28 ITU-T Rec. I.358 – Call processing performance for switched Virtual Channel Connections (VCCs) in a B-ISDN (2003)** + +This Recommendation defines performance parameters and objectives for call processing in B-ISDNs for switched Virtual Channel Connections (VCCs). The B-ISDN call processing parameters defined in this Recommendation are applicable to point-to-point (Type 1) and point-to-multipoint (Type 2) connection topologies. The QoS relevant network performance objectives provided in this Recommendation are based on the general principles and generic performance parameters of ITU-T Rec. I.350. New performance-related aspects, associated with B-ISDN call processing functions providing access or disengagement, include the addition or release of a party to an existing B-ISDN connection. In a B-ISDN, a virtual connection can generally be either a Virtual Channel Connection (VCC) or a Virtual Path Connection (VPC). Since call processing capabilities are currently defined only for VCCs, a virtual connection within the context of this Recommendation is a VCC. + +--- + +7 See also Amendment 1, 02-2004. + +8 Also known as permanent virtual connection or PVC. + +## **3.29 ITU-T Rec. I.359 – Accuracy and dependability of ISDN 64 kbit/s circuit mode connection types (1999)** + +This Recommendation defines accuracy and dependability parameters for describing N-ISDN circuit mode access and disengagement performance. Key parameters are connection denial probability, incorrect call set-up probability, and premature disconnect probability. The parameters apply to specified portions of an international end-to-end 64 kbit/s circuit mode connection. + +## **3.30 ITU-T Rec. I.381 – ATM Adaptation Layer (AAL) Performance (2001)** + +This Recommendation describes an approach for the performance description of AAL processes. It is motivated by the need, based on field experiences, to examine more carefully the performance aspects of some specific applications of ATM network technology. The approach presented here provides a unified framework for describing the performance of processes that depend upon AAL Type 1 (AAL-1), AAL Type 2 (AAL-2), AAL Type 3/4 (AAL-3/4), AAL Type 5 (AAL-5), or potentially other types of AAL, up to the point at which AAL layer actions have been completed. For each AAL, parameters that describe loss and delay performance are for further study. These parameters are related to relevant ATM cell transfer performance parameters from ITU-T Rec. I.356. + +## **3.31 ITU-T Rec. Y.1530 – Call processing performance for voice service in hybrid IP networks (2004)** + +This Recommendation defines performance parameters and objectives for point-to-point call processing in voice service provided by hybrid IP networks. The parameter definitions are based on the principles and generic performance parameters defined in ITU-T Rec. I.350, and make use of relevant definitions from ISDN call processing performance Recommendations where appropriate. + +## **3.32 ITU-T Rec. Y.1540 – Internet protocol data communication service – IP packet transfer and availability performance parameters (2002)9** + +This Recommendation defines parameters that may be used in specifying and assessing the speed, accuracy, dependability, and availability of Internet Protocol (IP) packet transfer of international IP data communication service. Connectionless transport is a distinguishing aspect of the IP service that is considered in ITU-T Rec. Y.1540. The defined parameters apply to end-to-end, point-to-point IP service and to the network portions that provide, or contribute to the provision of, such service. The key parameters include IP packet transfer delay, IP packet delay variation, IP packet error ratio, IP packet loss ratio, spurious IP packet rate, and per cent IP service availability. Performance objectives for the parameters defined in ITU-T Rec. Y.1540 are specified in ITU-T Rec. Y.1541. Access and disengagement performance associated with IP service is addressed in ITU-T Rec. Y.1530. + +## **3.33 ITU-T Rec. Y.1541 – Network performance objectives for IP-based services (2002)10** + +This Recommendation defines classes of network Quality of Service (QoS), and specifies provisional objectives for Internet Protocol network performance parameters. These classes are intended to be the basis for agreements among network providers, and between end users and their network providers. + +Appendix I/Y.1541 provides information about how ATM might support IP layer performance. Appendix II discusses alternatives for defining IP delay variation. Appendix III presents the Hypothetical Reference Paths against which the Y.1541 QoS objectives were tested for feasibility. + +--- + +9 See also Amendment 1, 08-2003. + +10 See also Amendment 1, 08-2003; Appendix X, 11-2002; and Amendment 2 (02/04) – Appendix XI. + +Appendix IV gives example computations of packet delay variation. Appendix V discusses issues that must be considered whenever IP measurements are made. Appendix VI addresses the applicability of the transfer capabilities defined in ITU-T Rec. Y.1221 in support of the Y.1541 IP QoS classes. It also specifies the relationship between Y.1221 transfer capabilities and IETF Differentiated Services Per Hop Behaviours consistent with what is specified in ITU-T Rec. Y.1221. Appendix VII discusses the packet transfer delay objective and how it relates to other Recommendations. Appendix VIII presents a Bibliography. Appendix IX discusses potential applications of IP Networks. Appendix X provides Speech Quality Calculations for Y.1541 Hypothetical Reference Paths. Appendix XI provides methods for estimating UNI-UNI performance from a set of QoS values contributed by Network Sections. + +## **3.34 ITU-T Rec. Y.1560 – Parameters for TCP connection performance in the presence of middleboxes (2003)** + +This Recommendation describes end-to-end Transmission Control Protocol (TCP) performance in terms of speed, accuracy, and dependability in an IP-based network with middleboxes, which are network nodes terminating TCP connections. + +## **3.35 ITU-T Rec. Y.1561 – Performance and availability parameters for MPLS networks (2004)** + +This Recommendation defines parameters that may be used in specifying and assessing the performance of speed, accuracy, dependability, and availability of packet transfer over a Label Switched Path on a Multi-Protocol Label Switching (MPLS) network. The defined parameters apply to end-to-end, point-to-point and multipoint-to-point LSP and to any MPLS domain that provides, or contributes to the provision of, packet transfer services. Two categories of MPLS networks are considered: + +- 1) TE-LSP: Traffic Engineering Label Switched Path, or configured LSP. These are point-point paths. +- 2) LDP-based LSP: This includes point-to-point and multipoint-to-point LSPs. + +# **Annex A** + +## **History of the G-series error performance Recommendations** + +## **A.1 Background on the content of Annex A** + +Because of the somewhat complex history of the G-series error performance Recommendations, clause A.2 and Table A.1 of this annex provide guidance to help users of these Recommendations to find the right standard for their application. + +## **A.2 History of the G-series error performance Recommendations** + +ITU-T Rec. G.821 was adopted in 1980 and defined error performance parameters and objectives for ISDN connections operating at a bit rate of 64 kbit/s. Because it was the first Recommendation giving error performance objectives, it found wide application – even in some areas for which it was not developed. One of these applications was error performance evaluation at bit rates higher than 64 kbit/s. + +In 1984, ITU-T Rec. G.921 was developed to define different section quality classes for digital sections based on the 2048 kbit/s hierarchy. The same targets were defined in ITU-T Rec. G.931 for digital sections on non-hierarchical 3152 kbit/s interface but no values for error and availability + +parameters were indicated. These objectives were kept under study until the deletion of the Recommendation in 2002. In 1988, Annex D was added to ITU-T Rec. G.821, which indicated how to derive error performance data of 64 kbit/s connections taking into account measurements performed at higher bit rates. Practical experience showed, however, that this annex led in many cases to doubtful results. + +Another problem discovered in practical use of ITU-T Rec. G.821 was the applicability of the Degraded Minute parameter (DM). In practice, this event was hardly detected and it was therefore deleted from the Recommendation. + +In addition, it was a disadvantage of ITU-T Rec. G.821 that no signal overhead was available at the bit rates covered by the Recommendation. Because of this, in-service performance measurements were not possible. + +With the beginning of the development of SDH and ATM transport networks, the inadequate performance requirements of ITU-T Rec. G.821 for higher bit rates came to light. Thus, it became obvious that a Recommendation was needed which dealt with error performance parameters and objectives for higher bit rates and which would allow in-service measurements. To fill this gap, ITU-T Rec. G.826 was developed and was adopted in 1993. It gives error performance parameters and objectives for constant bit rate digital paths operating at bit rates at and above the primary rate. + +In 1996, ITU-T Rec. G.821 was restricted to bit rates below the primary rate and Annex D was deleted. On the other hand, the bit rate range between 64 kbit/s and the primary rate was to be covered by ITU-T Rec. G.821. + +ITU-T Rec. G.826 makes use of different concepts to allow in-service measurements based on blocks of contiguous bits. To point to some inconsistency problems existing between ITU-T Recs G.821 and G.826, Appendix I to ITU-T Rec. G.821 was prepared. + +In 2000, the new ITU-T Rec. G.828 was approved to meet the tighter requirements of synchronous digital paths supported by optical transport systems and to make sure that ATM traffic supported by these paths would meet the objectives of ITU-T Rec. I.356. + +In 2002, ITU-T Rec. G.826 was extended to digital connections that operate below the primary rate. This extension made the allocation principles for digital connections consistent with those for digital paths, and improved the ESR objective for digital connections. At this point, ITU-T Rec. G.821 was restricted to digital connections using equipment designed prior to the adoption of revised ITU-T Rec. G.826 on 14 December 2002. + +Finally, new ITU-T Rec. G.8201 for error and availability performance objectives of the optical transmission network (OTN) was completed in 2003. + +Table A.1 gives an overview on the history of the Recommendations discussed here. + +**Table A.1/G.820/I.351/Y.1501 – History of the error performance Recommendations** + +| Application | Validity period | | | | | | | +|------------------------------------------------------------------------------------|-----------------|--------------------|-----------|------------|------------|------------|------------| +| | 1980-1988 | 1988-1993 | 1993-1996 | Since 1996 | Since 2000 | Since 2002 | Since 2004 | +| Digital connections
operating below the primary rate | G.821 | | | | | | G.826 | +| Digital paths
operating at and above the primary rate
(PDH) | G.821 | G.821 +
Annex D | | | | | | +| Digital paths
operating at and above the primary rate
(PDH, SDH, cell-based) | | | G.826 | | | | | +| Digital paths
operating at and above the primary rate
(PDH, cell-based) | | | | | G.826 | | | +| Digital paths
operating at and above the primary rate
(SDH) | | | | | G.828 | | | +| PDH digital sections | G.921 | | | | | | | +| | G.931 | | | | | | | +| SDH digital sections | | | | | G.829 | | | +| Error performance of the OTN | | | | | | | G.8201 | + +# INDEX + +### A + +### Allan Deviation + +| | | +|-------------------------------|-------| +| Definition ..... | G.810 | +| Estimator and Properties..... | G.810 | + +### ATM Adaptation Layer Performance ..... I.356, I.381 + +### ATM Performance + +| | | +|---------------------------------|-------| +| Availability ..... | I.357 | +| User Information Transfer ..... | I.356 | + +### ATM Performance Allocation + +| | | +|---------------------------------|-------| +| Availability ..... | I.357 | +| User Information Transfer ..... | I.356 | + +### ATM Performance Assessment + +| | | +|---------------------------------|-------| +| Availability ..... | I.357 | +| User Information Transfer ..... | I.356 | + +### ATM Performance Objectives + +| | | +|---------------------------------|-------| +| Availability ..... | I.357 | +| User Information Transfer ..... | I.356 | + +### Availability Performance + +| | | +|------------------------------------------------------------------------|----------------| +| B-ISDN ATM Semi-Permanent Connection ..... | I.357 | +| IP Service..... | Y.1540, Y.1541 | +| ISDN 64 kbit/s Connection Type..... | I.355 | +| MPLS Service ..... | Y.1561 | +| Elements of International CBR Paths at or above the Primary Rate ..... | G.827 | +| End-to-end CBR paths at or above the Primary Rate ..... | G.827 | + +#### Availability Ratio..... I.357, G.827 + +### Available Time + +| | | +|-----------------------------------------------------------------------------|----------------------| +| B-ISDN Semi-Permanent Connection ..... | I.357 | +| Digital Connections ..... | G.821 | +| Digital Paths..... | G.826, G.828, G.8201 | +| IP Service..... | Y.1540, Y.1541 | +| ISDN 64 kbit/s Connection Type..... | I.355 | +| Path Elements of International CBR Paths at or above the Primary Rate ..... | G.827 | +| SDH Multiplex and Regenerator Sections..... | G.829 | + +### B + +#### Background Block Error + +| | | +|------------------------------|--------------| +| Digital Paths..... | G.826, G.828 | +| SDH Multiplex Sections ..... | G.829 | + +#### Background Block Error Ratio (Digital Paths)..... G.826, G.828, G.8201 + +### B-ISDN Performance + +| | | +|--------------------------------------------|-----------------------------| +| Availability ..... | I.357 | +| Call Processing ..... | I.358 | +| User Information Transfer ..... | I.356 | +| Bi-Level QoS Class..... | I.356 | +| Bit Error Ratio (Digital Connections)..... | G.821 | +| Bit Errors..... | G.821 | +| Block Errors ..... | G.826, G.828, G.829, G.8201 | + +### C + +| | | +|----------------------------------------------------|----------------------| +| Call Clearing Failure Probability ..... | I.359 | +| Call Set-Up Error Probability ..... | I.355 | +| Call Set-Up Failure Probability..... | I.355 | +| Cell Block ..... | I.356 | +| Cell Delay Variation ..... | I.356 | +| Cell Error Ratio..... | I.356 | +| Cell Loss Ratio..... | I.356 | +| Cell Misinsertion Rate ..... | I.356 | +| Cell Transfer Delay..... | I.356 | +| Cell Transfer Outcome..... | I.356 | +| Clock..... | G.810 | +| Clock Requirements | | +| Primary Reference Clock..... | G.811 | +| SDH Equipment Clock ..... | G.813 | +| Slave Clock..... | G.812 | +| ODUk Clock ..... | G.8251 | +| Connection Clearing Delay..... | Y.1560 | +| Connection Clearing Failure Probability ..... | I.358, I.359, Y.1560 | +| Connection Establishment Delay ..... | Y.1560 | +| Connection Establishment Error Probability ..... | Y.1560 | +| Connection Establishment Failure Probability ..... | Y.1560 | +| Connection Portion Availability ..... | I.357, I.355 | +| Connection Post Selection Delay..... | I.358 | +| Connection Set-Up Error Probability..... | I.355, I.358, I.359 | +| Connection Set-Up Failure Probability..... | I.355, I.358, I.359 | +| Corrupted Frame Ratio..... | I.356 | + +### D + +#### Defects resulting in Severely Errored Seconds + +| | | +|---------------------------------------------|--------------| +| Digital Paths..... | G.828, G.826 | +| SDH Multiplex and Regenerator Sections..... | G.829 | + +| | | +|-------------------------------------|-------| +| Derived Performance Parameters..... | I.350 | +|-------------------------------------|-------| + +#### Disconnect Delay + +| | | +|------------------|-------| +| Connection ..... | I.358 | +| Party ..... | I.358 | + +### E + +### Error Performance + +| | | +|---------------------------|----------------------| +| Digital Connections ..... | G.821 | +| Digital Paths..... | G.826, G.828, G.8201 | + +#### Error Performance Allocation + +#### Digital Connections + +| | | +|--------------------|-------| +| High Grade..... | G.821 | +| Local Grade..... | G.821 | +| Medium Grade ..... | G.821 | + +#### Digital Paths + +| | | +|-----------------------------|--------------| +| International Portion ..... | G.826, G.828 | +| National Portion..... | G.826, G.828 | + +### Error Performance Assessment + +#### Based upon Bit Errors + +| | | +|---------------------------|-------| +| Digital Connections ..... | G.821 | +|---------------------------|-------| + +#### Based upon Errored Blocks + +| | | +|--------------------------------------------------------------|----------------------| +| Block Structure, Digital Paths ..... | G.826, G.828, G.8201 | +| Block Structure, SDH Multiplex and Regenerator Sections..... | G.829 | + +| | | +|------------------------------|-----------------------------| +| In-Service Measurement ..... | G.826, G.828, G.829, G.8201 | +|------------------------------|-----------------------------| + +#### Error Performance Events + +| | | +|---------------------------------------------|--------------| +| Digital Connections ..... | G.821 | +| Digital Paths..... | G.826, G.828 | +| SDH Multiplex and Regenerator Sections..... | G.829 | + +#### Error Performance Objectives + +| | | +|---------------------------|----------------------| +| Digital Connections ..... | G.821 | +| Digital Paths..... | G.826, G.828, G.8201 | + +| | | +|------------------|-------| +| Errored Bit..... | G.821 | +|------------------|-------| + +| | | +|--------------------|----------------------| +| Errored Block..... | G.826, G.828, G.8201 | +|--------------------|----------------------| + +| | | +|-------------------|-------| +| Errored Cell..... | I.356 | +|-------------------|-------| + +#### Errored Packet + +| | | +|------------------------|----------------| +| IP ..... | Y.1540, Y.1541 | +| ISDN Packet Mode ..... | I.354 | + +| | | +|------------------------------------------------------------|------------------------------------| +| Errored Second | | +| Digital Connections ..... | G.821 | +| Digital Paths..... | G.826, G.828 | +| SDH Multiplex and Regenerator Sections..... | G.829 | +| Errored Second Ratio | | +| Digital Connections ..... | G.821 | +| Digital Paths..... | G.826, G.828 | +| F | | +| Fractional Frequency Deviation..... | G.810 | +| Frame Transmission Delay ..... | I.356 | +| Frequency Accuracy | | +| Definition ..... | G.810 | +| Requirement for Primary Reference Clock ..... | G.811 | +| Requirement for SDH Equipment Clock..... | G.813 | +| Requirement for Slave Clock..... | G.812 | +| Requirement for ODUk Clock..... | G.8251 | +| Frequency Drift..... | G.810 | +| Frequency Stability ..... | G.810 | +| G | | +| Generic Performance Parameters..... | I.350 | +| H | | +| Hold-in Range | | +| Definition ..... | G.810 | +| Requirement for SDH Equipment Clock..... | G.813 | +| Requirement for Slave Clock..... | G.812 | +| Holdover | | +| Definition ..... | G.810 | +| Requirement for SDH Equipment Clock..... | G.813 | +| Requirement for Slave Clock..... | G.812 | +| Hypothetical Reference Connection | | +| ATM Connection ..... | I.356 | +| Digital Connection..... | G.821 | +| Hypothetical Reference Path..... | G.821, G.826, G.828, G.829, G.8201 | +| I | | +| Internet Protocol Network Performance | | +| Performance Allocation Model..... | Y.1540, Y.1541 | +| Performance-Significant Reference Events, Parameters ..... | Y.1540 | +| IP Packet Delay Variation..... | Y.1540, Y.1541 | +| IP Packet Error Ratio ..... | Y.1540, Y.1541 | +| IP Packet Loss Ratio ..... | Y.1540, Y.1541 | + +| | | +|------------------------------------------|----------------| +| IP Packet Transfer Reference Event ..... | Y.1540, Y.1541 | +| IP Packet Octet-Based Throughput..... | Y.1540, Y.1541 | +| IP Packet Throughput..... | Y.1540, Y.1541 | +| IP Packet Transfer Delay ..... | Y.1540, Y.1541 | +| IP/Voice Interworking Performance ..... | Y.1530 | + +## J + +### Jitter + +| | | +|------------------------|-------| +| (Timing) Jitter ..... | G.810 | +| Alignment Jitter ..... | G.810 | + +### Jitter Generation Requirements + +| | | +|--------------------------------------------------------|--------| +| Primary Reference Clock..... | G.811 | +| SDH Equipment (regenerator, PDH client demapper) ..... | G.783 | +| SDH Equipment Clock ..... | G.813 | +| Slave Clock ..... | G.812 | +| ODUk Clock ..... | G.8251 | + +| | | +|-------------------------------------------------|-------| +| Jitter Measurement, 2048 kbit/s Hierarchy ..... | G.823 | +|-------------------------------------------------|-------| + +### Jitter Network Limit + +| | | +|------------------------------------------------------------------------------|--------| +| Jitter Accumulation for SDH Network Synchronization..... | G.813 | +| Output Jitter for 1544 kbit/s Hierarchy, Specification and Measurement ..... | G.824 | +| Output Jitter for 2048 kbit/s Hierarchy, Specification and Measurement ..... | G.823 | +| Output Jitter for SDH, Specification and Measurement ..... | G.825 | +| Output Jitter for OTN, Specification and Measurement..... | G.8251 | + +### Jitter Tolerance Requirements + +| | | +|--------------------------------------------------------------------------|--------| +| Digital Input Ports for Signals based on the 1544 kbit/s Hierarchy ..... | G.824 | +| Digital Input Ports for Signals based on the 2048 kbit/s Hierarchy ..... | G.823 | +| Digital Input Ports for Signals based on the SDH ..... | G.825 | +| Digital Input Ports for Signals based on the OTN ..... | G.8251 | +| SDH Equipment Clock ..... | G.813 | +| Slave Clock ..... | G.812 | +| ODUk Clock ..... | G.8251 | + +### Jitter Transfer Requirements + +| | | +|--------------------------------------------------------|--------| +| PDH Equipment based on the 1544 kbit/s Hierarchy ..... | G.824 | +| PDH Equipment based on the 2048 kbit/s Hierarchy ..... | G.823 | +| SDH Equipment Clock ..... | G.813 | +| SDH Equipment (regenerator, PDH client demapper) ..... | G.783 | +| Slave Clock ..... | G.812 | +| ODUk Clock ..... | G.8251 | + +## L + +| | | +|----------------|-------| +| Lost Cell..... | I.356 | +|----------------|-------| + +### Lost Packet + +| | | +|------------------------|----------------| +| IP ..... | Y.1540, Y.1541 | +| ISDN Packet Mode ..... | I.354 | + +## M + +| | | +|-------------------------------------------------------------------------|--------| +| Master Clock ..... | G.810 | +| Maximum Time Interval Error – Definition, Estimator and Properties..... | G.810 | +| Mean Time Between Connection Portion Outages..... | I.355 | +| Mean Time Between Digital Path Outages..... | G.827 | +| Mean Time Between Outages ..... | I.357 | +| Minimal Test for Availability State Determination | | +| ISDN 64 kbit/s Connection Type..... | I.355 | +| Misinserted Cell ..... | I.356 | +| Modified Allan Deviation – Definition, Estimator and Properties ..... | G.810 | +| MPLS Network Performance..... | Y.1561 | +| Multiparty Call Set-Up Error Probability ..... | I.358 | + +## N + +| | | +|--------------------------------------------------------------------------|--------| +| Network Performance ..... | I.350 | +| Network Synchronization | | +| Architecture ..... | G.803 | +| Reference Chain..... | G.803 | +| Atomic functions..... | G.781 | +| Quality levels ..... | G.781 | +| Synchronization Status Messages..... | G.781 | +| Node Clock ..... | G.810 | +| Noise Generation | | +| Primary Reference Clock..... | G.811 | +| SDH Equipment Clock ..... | G.813 | +| Slave Clock ..... | G.812 | +| ODUk Clock ..... | G.8251 | +| Noise Tolerance | | +| Digital Input Ports for Signals based on the 1544 kbit/s Hierarchy ..... | G.824 | +| Digital Input Ports for Signals based on the 2048 kbit/s Hierarchy ..... | G.823 | +| Digital Input Ports for Signals based on the SDH ..... | G.825 | +| SDH Equipment Clock ..... | G.813 | +| Slave Clock ..... | G.812 | +| ODUk Clock ..... | G.8251 | +| Noise Transfer | | +| PDH Equipment based on the 1544 kbit/s Hierarchy ..... | G.824 | +| PDH Equipment based on the 2048 kbit/s Hierarchy ..... | G.823 | +| SDH Equipment..... | G.825 | +| SDH Equipment Clock ..... | G.813 | +| Slave Clock ..... | G.812 | +| ODUk Clock ..... | G.8251 | + +### Noise Types, Power Law + +| | | +|---------------------------------------|-------| +| Flicker Frequency Modulation..... | G.810 | +| Flicker Phase Modulation ..... | G.810 | +| Random Walk Frequency Modulation..... | G.810 | +| White Frequency Modulation ..... | G.810 | +| White Phase Modulation..... | G.810 | + +## O + +| | | +|------------------------|--------------| +| Outage Intensity ..... | I.357, G.827 | +|------------------------|--------------| + +## P + +| | | +|------------------------------------------------------|-----------------------------| +| Party Add/Drop ..... | I.358 | +| Party Answer Signal Delay ..... | I.358 | +| Party Clearing Failure Probability ..... | I.358 | +| Party Post Selection Delay ..... | I.358 | +| Party Set-Up Error Probability..... | I.358 | +| Party Set-Up Failure Probability..... | I.358 | +| Path Elements and Categories..... | G.827 | +| Percent Service Available | | +| IP ..... | Y.1540, Y.1541 | +| MPLS ..... | Y.1561 | +| Percent Service Unavailable | | +| IP ..... | Y.1540, Y.1541 | +| MPLS ..... | Y.1561 | +| Performance Framework | | +| Digital Networks Including ISDNs..... | I.350 | +| Phase Discontinuity | | +| Requirement for Primary Reference Clock ..... | G.811 | +| Requirement for SDH Equipment Clock..... | G.813 | +| Requirement for Slave Clock..... | G.812 | +| Phase Transient | | +| Definition ..... | G.810 | +| Short Term, Requirement for SDH Equipment Clock..... | G.813 | +| Short Term, Requirement for Slave Clock ..... | G.812 | +| Plesiochronous (Definition) ..... | G.810 | +| Premature Disconnect Probability ..... | I.355, I.358, I.359, Y.1560 | +| Premature Disconnect Stimulus ..... | I.359 | +| Premature Disconnect Stimulus Probability ..... | I.359 | +| Primary Performance Parameters..... | I.350 | +| Primary Reference Clock ..... | G.810 | + +### Pull-in Range + +| | | +|-------------------------------------------|--------| +| Definition ..... | G.810 | +| Requirement for SDH Equipment Clock ..... | G.813 | +| Requirement for Slave Clock..... | G.812 | +| Requirement for ODUk Clock..... | G.8251 | + +### Pull-out Range + +| | | +|-------------------------------------------|--------| +| Definition ..... | G.810 | +| Requirement for SDH Equipment Clock ..... | G.813 | +| Requirement for Slave Clock..... | G.812 | +| Requirement for ODUk Clock ..... | G.8251 | + +## Q + +| | | +|-------------------------------|---------------| +| Quality of Service ..... | I.350 | +| Quality of Service Class..... | I.356, Y.1541 | + +## R + +### Release Delay + +| | | +|------------------|-------| +| Connection ..... | I.358 | +| Party ..... | I.358 | + +| | | +|-------------------------|-------| +| Reset Probability ..... | I.355 | +|-------------------------|-------| + +| | | +|---------------------------------|-------| +| Reset Stimulus Probability..... | I.355 | +|---------------------------------|-------| + +| | | +|---------------------------|-------| +| Residual Error Ratio..... | I.355 | +|---------------------------|-------| + +| | | +|-----------------------------------------------------------------------------------|-------| +| Root Mean Square Time Interval Error – Definition, Estimator and Properties ..... | G.810 | +|-----------------------------------------------------------------------------------|-------| + +## S + +### Set-Up Delay + +| | | +|------------------|--------------| +| Connection ..... | I.352, I.358 | +| Party ..... | I.358 | + +### Set-Up Error Probability + +| | | +|------------------|-------| +| Connection ..... | I.358 | +| Party ..... | I.358 | + +### Set-Up Failure Probability + +| | | +|------------------|-------| +| Call..... | I.359 | +| Connection ..... | I.358 | +| Party ..... | I.358 | + +| | | +|-----------------------------------|-------| +| Severely Errored Cell Block ..... | I.356 | +|-----------------------------------|-------| + +| | | +|----------------------------------------|-------| +| Severely Errored Cell Block Ratio..... | I.356 | +|----------------------------------------|-------| + +### Severely Errored Second + +| | | +|---------------------------------------------|----------------------| +| ATM Layer Connections ..... | I.357 | +| Digital Connections ..... | G.821 | +| Digital Paths..... | G.826, G.828, G.8201 | +| SDH Multiplex and Regenerator Sections..... | G.829 | + +| | | +|-------------------------------------------------------------------------------------|----------------------| +| Severely Errored Second Ratio | | +| Digital Connections ..... | G.821 | +| Digital Paths ..... | G.826, G.828, G.8201 | +| Slave Clock ..... | G.810 | +| Slip | | +| Controlled Slip Rate Objectives ..... | G.822 | +| Controlled Slip, Definition ..... | G.810 | +| Successfully Transferred Cell ..... | I.356 | +| Stringent QoS Class ..... | I.356 | +| Synchronization Network – Definition, Measurement Configurations and Structure..... | G.810 | +| Synchronization Supply Unit..... | G.810 | +| T | | +| Tagged Cell..... | I.356 | +| Tandem Connection Monitoring..... | G.828 | +| Throughput Capacity | | +| Internet..... | Y.1540 | +| ISDN Packet Mode ..... | I.354, I.355 | +| Time ..... | G.810 | +| Time Deviation – Definition, Estimator and Properties ..... | G.810 | +| Time Error Function..... | G.810 | +| Time Function..... | G.810 | +| Time Interval Error Function ..... | G.810 | +| Time Scale..... | G.810 | +| Time Variance..... | G.810 | +| Timing Signal..... | G.810 | +| Tolerant QoS Class ..... | I.356 | +| Transient Response for ODUk Clock on Loss of or Restoration of CBR Client..... | G.8251 | +| U | | +| Unavailability Ratio ..... | I.357, G.827 | +| Unavailable Time | | +| B-ISDN Semi-Permanent Connection ..... | I.357 | +| Digital Connections ..... | G.821 | +| Digital Paths..... | G.826, G.828, G.8201 | +| ISDN 64 kbit/s Connection Type..... | I.355 | +| Path Elements of International CBR Paths at or above the Primary Rate ..... | G.827 | +| IP Service..... | Y.1540, Y.1541 | +| End-to-end CBR Paths at or above the Primary Rate..... | G.827 | +| SDH Multiplex Sections ..... | G.829 | +| Unbounded Performance..... | I.356 | + +| | | +|----------------------------------------------------------------------------|-------| +| Universal Coordinated Time ..... | G.810 | +| Unspecified QoS Class..... | I.356 | +| W | | +| Wander ..... | G.810 | +| Wander Generation Requirements | | +| Primary Reference Clock..... | G.811 | +| SDH Equipment Clock ..... | G.813 | +| Slave Clock ..... | G.812 | +| Wander Network Limit | | +| Output Wander for 1544 kbit/s Hierarchy ..... | G.824 | +| Wander Accumulation for SDH Network Synchronization ..... | G.813 | +| Wander Reference Model | | +| Networks Based on 2048 kbit/s Hierarchy ..... | G.823 | +| VC-11 Island Model, SDH Networks Optimized for 1544 kbit/s Hierarchy ..... | G.813 | +| Wander Tolerance Requirements | | +| Digital Input Ports for Signals based on the 1544 kbit/s Hierarchy ..... | G.824 | +| Digital Input Ports for Signals based on the 2048 kbit/s Hierarchy ..... | G.823 | +| Digital Input Ports for Signals based on the SDH ..... | G.825 | +| SDH Equipment Clock ..... | G.813 | +| Slave Clock ..... | G.812 | +| Wander Transfer Requirements | | +| PDH Equipment based on the 1544 kbit/s Hierarchy ..... | G.824 | +| PDH Equipment based on the 2048 kbit/s Hierarchy ..... | G.823 | +| SDH Equipment Clock ..... | G.813 | +| Slave Clock ..... | G.812 | + +ITU-T I-SERIES RECOMMENDATIONS +INTEGRATED SERVICES DIGITAL NETWORK + +| | | +|--------------------------------------------|--------------------| +| GENERAL STRUCTURE | I.100–I.199 | +| SERVICE CAPABILITIES | I.200–I.299 | +| OVERALL NETWORK ASPECTS AND FUNCTIONS | I.300–I.399 | +| Network functional principles | I.310–I.319 | +| Reference models | I.320–I.329 | +| Numbering, addressing and routing | I.330–I.339 | +| Connection types | I.340–I.349 | +| Performance objectives | I.350–I.359 | +| Protocol layer requirements | I.360–I.369 | +| General network requirements and functions | I.370–I.399 | +| ISDN USER-NETWORK INTERFACES | I.400–I.499 | +| INTERNETWORK INTERFACES | I.500–I.599 | +| MAINTENANCE PRINCIPLES | I.600–I.699 | +| B-ISDN EQUIPMENT ASPECTS | I.700–I.799 | + +ITU-T Y-SERIES RECOMMENDATIONS +GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT +GENERATION NETWORKS + +| | | +|--------------------------------------------------------------------|----------------------| +| GLOBAL INFORMATION INFRASTRUCTURE | Y.100–Y.999 | +| INTERNET PROTOCOL ASPECTS | Y.1000–Y.1999 | +| 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 | Y.2000–Y.2999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/G/T-REC-G.825-200003-I_PDF-E/177e8bc1c595b7fe3461d9919f87e044_img.jpg b/marked/G/T-REC-G.825-200003-I_PDF-E/177e8bc1c595b7fe3461d9919f87e044_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e519cddf3257e0bf70b4ad7931599b14a58b3a6 --- /dev/null +++ b/marked/G/T-REC-G.825-200003-I_PDF-E/177e8bc1c595b7fe3461d9919f87e044_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:774ff8ecb37dd857c65541ee620509aba13a5ade6872991e72c93418532c0728 +size 47448 diff --git a/marked/G/T-REC-G.825-200003-I_PDF-E/1c427123350e0e73e2a109b79069314b_img.jpg b/marked/G/T-REC-G.825-200003-I_PDF-E/1c427123350e0e73e2a109b79069314b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..215bb18483dbb80ce3fb553f220efe1e27b75087 --- /dev/null +++ b/marked/G/T-REC-G.825-200003-I_PDF-E/1c427123350e0e73e2a109b79069314b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:493583bac90d37d0b7f075614b624b780d3b7c771e45d328d0f6c2b8c5a9e9d9 +size 32993 diff --git a/marked/G/T-REC-G.825-200003-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.825-200003-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..548413745b4d98c653d31c63962591b02de03f92 --- /dev/null +++ b/marked/G/T-REC-G.825-200003-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17406d74d7ebb46734a24b04abc40f7b6896f5c51ae5b230a11d81d12377be37 +size 8372 diff --git a/marked/G/T-REC-G.825-200003-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/G/T-REC-G.825-200003-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..594deaa1baf0b15e116c2ae2c0b3a610cb11dffe --- /dev/null +++ b/marked/G/T-REC-G.825-200003-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df0820aab5c3e0d3af5362d05873e4c695c4d01bbca48f0446d1ccef17122475 +size 38456 diff --git a/marked/G/T-REC-G.825-200003-I_PDF-E/411fa16c3211377525ba37c57784fee0_img.jpg b/marked/G/T-REC-G.825-200003-I_PDF-E/411fa16c3211377525ba37c57784fee0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bc608e48af713470a89537fc0ff77d5d2c44828 --- /dev/null +++ b/marked/G/T-REC-G.825-200003-I_PDF-E/411fa16c3211377525ba37c57784fee0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f098ecdc08370f3e112af1ebe53f4c41c3de0d19baec0f4cde4bedd658a2f17 +size 41510 diff --git a/marked/G/T-REC-G.825-200003-I_PDF-E/8791f79b259a7463279c1aeb14c31580_img.jpg b/marked/G/T-REC-G.825-200003-I_PDF-E/8791f79b259a7463279c1aeb14c31580_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0060456c8e6b9a82a42bc6071c56440fc54893b --- /dev/null +++ b/marked/G/T-REC-G.825-200003-I_PDF-E/8791f79b259a7463279c1aeb14c31580_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b99ee89d6866b21cfc2d9186bcbb9d89e2fca5edfe2f9a6c5028b9411939d01 +size 34060 diff --git a/marked/G/T-REC-G.825-200003-I_PDF-E/b05a8a3551db31147979064952179990_img.jpg b/marked/G/T-REC-G.825-200003-I_PDF-E/b05a8a3551db31147979064952179990_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81d4569446f9ed042f9d183e9e88893620fb86b4 --- /dev/null +++ b/marked/G/T-REC-G.825-200003-I_PDF-E/b05a8a3551db31147979064952179990_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1e6a5e133278b0cf7b942bc82c72fc47498f601a4d8cc152802ce363e6c46e6 +size 35388 diff --git a/marked/G/T-REC-G.825-200003-I_PDF-E/b2d16e07bfa79d67a8adabf7e26c7764_img.jpg b/marked/G/T-REC-G.825-200003-I_PDF-E/b2d16e07bfa79d67a8adabf7e26c7764_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b50cff53a8c8eb887d53eeec1df5b77b5d99feb --- /dev/null +++ b/marked/G/T-REC-G.825-200003-I_PDF-E/b2d16e07bfa79d67a8adabf7e26c7764_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:227eb8e415d9533f05e9b2638109e3e2cfd0940b81357da904d3f9befd2bf2ff +size 23288 diff --git a/marked/G/T-REC-G.825-200003-I_PDF-E/b3df5964338063224492c01f09e4fed6_img.jpg b/marked/G/T-REC-G.825-200003-I_PDF-E/b3df5964338063224492c01f09e4fed6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..759116263ec170ab75b11f89788a1f494c37bcfa --- /dev/null +++ b/marked/G/T-REC-G.825-200003-I_PDF-E/b3df5964338063224492c01f09e4fed6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dac9c763996d27b630b4533ffc2e139c9eb7d07b5f5d709f076415c186871a8b +size 53757 diff --git a/marked/G/T-REC-G.825-200003-I_PDF-E/b6750d26d3dd287a4a4d49b3670a44bd_img.jpg b/marked/G/T-REC-G.825-200003-I_PDF-E/b6750d26d3dd287a4a4d49b3670a44bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cced18ded684694a3a439db7db3a5a79a13e9e54 --- /dev/null +++ b/marked/G/T-REC-G.825-200003-I_PDF-E/b6750d26d3dd287a4a4d49b3670a44bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f0a4df792e0d12d07b4c9a72cf1735767316bcb2f1e2160b58d63e1554857c5 +size 18041 diff --git a/marked/G/T-REC-G.825-200003-I_PDF-E/raw.md b/marked/G/T-REC-G.825-200003-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..52795db01a55418d9995ec22e0a64efaf3c79c04 --- /dev/null +++ b/marked/G/T-REC-G.825-200003-I_PDF-E/raw.md @@ -0,0 +1,572 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.825** + +(03/2000) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital networks – Quality and availability targets + +--- + +**The control of jitter and wander within digital +networks which are based on the synchronous +digital hierarchy (SDH)** + +ITU-T Recommendation G.825 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| INTERNATIONAL ANALOGUE CARRIER SYSTEM | | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| General aspects | G.800–G.809 | +| Design objectives for digital networks | G.810–G.819 | +| Quality and availability targets | G.820–G.829 | +| Network capabilities and functions | G.830–G.839 | +| SDH network characteristics | G.840–G.849 | +| Management of transport network | G.850–G.859 | +| SDH radio and satellite systems integration | G.860–G.869 | +| Optical transport networks | G.870–G.879 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH)** + +## **Summary** + +This ITU-T Recommendation specifies the maximum network limits of jitter and wander that shall not be exceeded and the minimum equipment tolerance to jitter and wander that shall be provided at any relevant transport or synchronization interfaces which are based on the Synchronous Digital Hierarchy (SDH). + +The requirements for the jitter and wander characteristics that are specified in this ITU-T Recommendation must be adhered to in order to ensure interoperability of equipment produced by different manufacturers and a satisfactory network performance. + +## **Source** + +ITU-T Recommendation G.825 was revised by ITU-T Study Group 13 (1997-2000) and approved under the WTSC Resolution 1 procedure on 10 March 2000. + +## **Keywords** + +Clocks, Input Jitter Tolerance, Input Wander Tolerance, Network Limits, Output Jitter, Output Wander, Synchronization, Timing. + +## 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 Conference (WTSC), 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 WTSC Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | Page | +|---------------------------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations..... | 2 | +| 5 Network limits for the maximum output jitter and wander at any hierarchical interface ..... | 3 | +| 5.1 Network limits for jitter ..... | 3 | +| 5.2 Network limits for wander ..... | 4 | +| 6 The specification of individual digital equipment ..... | 4 | +| 6.1 Jitter and wander tolerance for STM-N input ports..... | 4 | +| 6.1.1 STM-N input wander tolerance ..... | 6 | +| 6.1.2 STM-N input jitter tolerance ..... | 6 | +| 6.2 Jitter and wander generation..... | 10 | +| 6.3 Jitter and wander transfer..... | 10 | +| Appendix I – Relationship between network interface jitter requirements and input jitter tolerance..... | 11 | +| I.1 Network interface jitter requirements ..... | 11 | +| I.2 Input jitter tolerance of network equipment ..... | 12 | +| Appendix II – Measurement methodology for output wander of synchronous interfaces ..... | 14 | +| Appendix III – SDH Line systems and Interworking implications ..... | 14 | + +## **Introduction and background** + +In a digital network, jitter and wander accumulate on transmission paths according to the jitter and wander generation and transfer characteristics of each equipment interconnected. This equipment may be different types of multiplexers/demultiplexers, cross-connects, clocks and line systems, for example. + +An excessive amount of jitter and wander can adversely affect both digital (e.g. by generation of bit errors, slips and other abnormalities) and analogue signals (e.g. by unwanted phase modulation of the transmitted signal). The consequences of such impairment will, in general, depend on the particular service that is being carried and the terminating or adaptation equipment involved. + +It is therefore necessary to set limits on the maximum magnitude of jitter and wander, and the corresponding minimum jitter and wander tolerance at network interfaces, in order to guarantee a proper quality of the transmitted signals and a proper design of the equipment. + +These network limits are independent from the particular service that is being carried. + +# **The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH)** + +## **1 Scope** + +The scope of this ITU-T Recommendation is to define the parameters and the relevant values that are able to control satisfactorily the amount of jitter and wander present at the SDH network-network interfaces (NNI). + +SDH network interfaces, to which this ITU-T Recommendation is applicable, are defined in terms of bit rates and frame structures in ITU-T Recommendation G.707; their electrical characteristics are described in ITU-T Recommendation G.703 and the optical characteristics in ITU-T Recommendations G.957 and G.691. + +Additional information regarding the architecture of SDH networks is found in ITU-T Recommendation G.803. + +Jitter and wander requirements for PDH and synchronization networks are specified in ITU-T Recommendation G.823, for networks based on the first level bit rate of 2048 kbit/s, and in ITU-T Recommendation G.824 for networks based on the first-level bit rate of 1544 kbit/s. + +The jitter and wander control philosophy is based on the need: + +- to recommend a maximum network limit that should not be exceeded at any relevant interface; +- to recommend a consistent framework for the specification of individual digital equipment (i.e. jitter and wander transfer, tolerance and generation requirements); +- to provide sufficient information and guidelines for organizations to measure and study jitter and wander accumulation in any network configuration. + +## **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.691 (draft), *Optical interfaces for single-channel STM-64, STM-256 and other SDH systems with optical amplifiers*. +- ITU-T Recommendation G.703 (1998), *Physical/electrical characteristics of hierarchical digital interfaces*. +- ITU-T Recommendation G.707 (1996), *Network Node interface for the Synchronous Digital Hierarchy (SDH)*. +- ITU-T Recommendation G.783 (1997), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks*. +- ITU-T Recommendation G.803 (2000), *Architecture of transport networks based on the synchronous digital hierarchy (SDH)*. + +- ITU-T Recommendation G.810 (1996), *Definitions and terminology for synchronization networks*. +- ITU-T Recommendation G.811 (1997), *Timing characteristics of primary reference clocks*. +- ITU-T Recommendation G.812 (1998), *Timing requirements of slave clocks suitable for use as node clocks in synchronization networks*. +- ITU-T Recommendation G.813 (1996), *Timing characteristics of SDH equipment slave clocks (SEC)*. +- ITU-T Recommendation G.823 (2000), *The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy*. +- ITU-T Recommendation G.824 (2000), *The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy*. +- ITU-T Recommendation G.832 (1998), *Transport of SDH elements on PDH networks – Frame and multiplexing structures*. +- ITU-T Recommendation G.957 (1999), *Optical interfaces for equipments and systems relating to the synchronous digital hierarchy*. +- ITU-T Recommendation O.171 (1997), *Timing jitter and wander measuring equipment for digital systems which are based on the Plesiochronous Digital Hierarchy (PDH)*. +- ITU-T Recommendation O.172 (1999), *Jitter and wander measuring equipment for digital systems which are based on the Synchronous Digital Hierarchy (SDH)*. + +## 3 Definitions + +This ITU-T Recommendation defines the following terms. Additional definitions relating to synchronization networks are provided in ITU-T Recommendation G.810. + +**3.1 synchronous interface:** These interfaces provide an output signal with frequency that is normally traceable to a PRC. + +**3.2 asynchronous interface:** These interfaces provide an output signal with frequency that is not traceable to a PRC and that meets the frequency offset requirements given in ITU-T Recommendation G.703. + +**3.3 synchronization interface:** These interfaces are synchronous and network wander limits are specified using Maximum Time Interval Error (MTIE) and Time Deviation (TDEV) parameters with values given in this ITU-T Recommendation. + +## 4 Abbreviations + +This ITU-T Recommendation uses the following abbreviations. Additional abbreviations will be added. + +| | | +|--------|----------------------------------------------------------------------------------| +| CMI | Code Mark Inversion | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| MRTIE | Maximum Relative Time Interval Error | +| MS-AIS | Multiplex Section Alarm Indication Signal | +| MTIE | Maximum Time Interval Error | +| NE | Network Element | +| NNI | Network Node Interface | + +| | | +|-------|-------------------------------| +| pk-pk | Peak-to-Peak | +| RTIE | Relative Time Interval Error | +| SDH | Synchronous Digital Hierarchy | +| TDEV | Time Deviation | +| TIE | Time Interval Error | +| UI | Unit Interval | +| UNI | User Network Interface | + +## 5 Network limits for the maximum output jitter and wander at any hierarchical interface + +### 5.1 Network limits for jitter + +The limits given in Table 1 represent the maximum permissible levels of jitter at interfaces within a digital network. Jitter as measured over a 60 second interval shall not exceed the limits given in Table 1, when using the specified measurement filters. The limits shall be met for all operating conditions and regardless of the amount of equipment preceding the interface. In general, these network limits are compatible with the minimum tolerance to jitter that all equipment input ports are required to provide. Guidelines for the derivation of the parameters values of Table 1 are given in Appendix I. + +There is a close relationship between network limits and input tolerance such that the jitter measurement filter cut-off frequencies used in Table 1 have the same values as the jitter tolerance mask corner frequencies used in 6.1. Appendix I provides further information about this relationship. + +The high-pass measurement filters of Table 1 have a first-order characteristic and a roll-off of 20 dB/decade. The low-pass measurement filters have a maximally-flat, Butterworth characteristic and a roll-off of –60 dB/decade. + +ITU-T Recommendation O.172 contains a functional description of equipment appropriate for measurement of jitter in SDH systems. Further specifications for the frequency response of the jitter measurement function such as measurement filter accuracy and additional allowed filter poles are also given in ITU-T Recommendation O.172. + +**Table 1/G.825 – Maximum permissible jitter at network interfaces** + +| Interface | Measurement bandwidth,
–3 dB frequencies (Hz) | Peak-to-peak amplitude
(UI pp ) | +|------------------------|--------------------------------------------------|-----------------------------------------------| +| STM-1e
(Notes 1, 2) | 500 to 1.3 M | 1.5 | +| | 65 k to 1.3 M | 0.075 | +| STM-1
(Note 4) | 500 to 1.3 M | 1.5 | +| | 65 k to 1.3 M | 0.15 | +| STM-4
(Note 4) | 1 k to 5 M | 1.5 | +| | 250 k to 5 M | 0.15 | +| STM-16
(Note 4) | 5 k to 20 M | 1.5 | +| | 1 M to 20 M | 0.15 | + +**Table 1/G.825 – Maximum permissible jitter at network interfaces (*concluded*)** + +| Interface | Measurement bandwidth,
–3 dB frequencies (Hz) | Peak-to-peak amplitude
(UIpp) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|----------------------------------| +| STM-64
(Note 4) | 20 k to 80 M | 1.5 | +| | 4 M to 80 M | 0.15 (Note 3) | +| NOTE 1 – Electrical format CMI-encoded, according to G.703. | | | +| NOTE 2 – For networks deployed with G.813 Option II clocks or G.812 Type II, III or IV clocks, STM-1 requirements apply to STM-1e. | | | +| NOTE 3 – The effect of dispersion and non-linearities on the eye opening and on the choice of this value is for further study. | | | +| NOTE 4 – STM-1                                      1 UI = 6.43 ns
STM-4                                      1 UI = 1.61 ns
STM-16                                    1 UI = 0.402 ns
STM-64                                    1 UI = 0.100 ns | | | + +### 5.2 Network limits for wander + +STM-N interfaces are defined as synchronization interfaces. Network limits for wander at synchronization interfaces are specified in ITU-T Recommendation G.823 for networks based on the 2048 kbit/s hierarchy, and in ITU-T Recommendation G.824 for networks based on the 1544 kbit/s hierarchy. + +## 6 The specification of individual digital equipment + +To help ensure that the interconnection of digital equipment does not result in accumulated jitter that exceeds network limits, the jitter transfer and jitter generation characteristics of individual equipment are defined. Also to help ensure equipment can operate properly, given the specified network limits, jitter tolerance characteristics are defined. + +### 6.1 Jitter and wander tolerance for STM-N input ports + +This subclause specifies the jitter and wander tolerance for SDH input ports. Jitter and wander tolerance for PDH input ports to SDH equipment are specified in ITU-T Recommendations G.823 and G.824. + +In order to ensure that, in general, any equipment can be connected to any appropriate interface within a network, it is necessary to arrange that the input ports of all equipment are capable of accommodating levels of jitter and wander up to at least the minimum limits defined in 6.1.1 and 6.1.2. + +The jitter and wander tolerance of an SDH interface indicates the minimum level of phase noise that the input port shall accommodate whilst: + +- not causing any alarms; +- not causing any slips; and +- not causing any bit errors; except for optical STM-N interfaces at jitter frequencies above $f_p$ ( $f_p$ is 6.5 kHz for STM-1, 25 kHz for STM-4, 100 kHz for STM-16 and 400 kHz for STM-64), where an equivalent 1 dB optical power penalty shall not be exceeded. + +All digital input ports of equipment shall be able to tolerate a digital signal that has: + +- a) electrical characteristics in accordance with the requirements of ITU-T Recommendation G.703, or the optical characteristics of ITU-T Recommendations G.957 and G.691; +- b) a frequency offset (relative to the nominal value) within the range defined in Table 2; +- c) a sinusoidal phase deviation having an amplitude-frequency relationship, defined in the following subclauses, which indicates the appropriate limits for the different interfaces. + +In principle, these requirements shall be met regardless of the information content of the digital signal. However, for test purposes, the content of the signal with jitter and wander modulation should be a structured test sequence as defined in Annex A/O.172. + +When specifying or assessing interface tolerance, two equipment operating conditions can be distinguished: + +- asynchronous operation, where the receiving equipment is not being timed from a source that is synchronous with the interface under consideration. In this case, it is the equipment capability to accommodate phase variation on the incoming signal (in terms of clock recovery circuitry and synchronizer/desynchronizer buffers) that is of interest. +- synchronous operation, where the receiving equipment is being timed from a source that is synchronous with the interface under consideration. In this case, slip buffer dimension and operation is also of interest. + +Unless otherwise stated, the tolerance specifications in 6.1.1 and 6.1.2 apply to both asynchronous and synchronous operating conditions. + +The jitter and wander limit above 10 Hz reflects the maximum permissible jitter magnitude in a digital network. However, the limit below 10 Hz does not aim to represent the maximum permissible wander that might occur in practice. Below 10 Hz the limits are derived such that where necessary, the provision of this level of buffer storage at the input of equipment facilitates the accommodation of wander generated in a large proportion of real connections. + +For convenience of testing, the required tolerance is defined in terms of the peak-to-peak amplitude and frequency of sinusoidal jitter which modulates a digital test pattern. It is important to recognize that this test condition is not, in itself, intended to be representative of the type of jitter found in practice in a network. + +Guidance on the measurement set-up for input jitter and wander tolerance is provided in Appendix III/G.823. Instrumentation in accordance with ITU-T Recommendation O.172 is appropriate for generation of jitter and wander in SDH systems. + +**Table 2/G.825 – Maximum frequency offset at STM-N interfaces** + +| Maximum frequency offset (±ppm) | Example application | +|----------------------------------------|---------------------------------------------------------------------------------| +| 4.6 | SDH NEs deployed with G.813 Option I clocks | +| 20 | MS-AIS in SDH regenerator sections and NEs deployed with G.813 Option II clocks | + +Requirements for regenerators are provided in ITU-T Recommendation G.783. Appendix III provides additional information. + +#### 6.1.1 STM-N input wander tolerance + +STM-N interfaces used as synchronization interfaces shall meet wander tolerance specifications in ITU-T Recommendations G.812 and G.813. ITU-T Recommendations G.812 and G.813 contain requirements for two network types. For equipment deployed in networks based on the 1544 kbit/s hierarchy, wander tolerance requirements are specified in Option II of ITU-T Recommendation G.813 and for clock types II, III and IV contained in ITU-T Recommendation G.812. For SDH equipment deployed in networks based on the 2048 kbit/s hierarchy, wander tolerance requirements are specified in Option I of ITU-T Recommendation G.813 and for clock types I, V and VI in ITU-T Recommendation G.812. + +NOTE – Traffic interfaces are also required to tolerate frequency offsets of at least 20 ppm for the purposes of detection of MS-AIS. + +#### 6.1.2 STM-N input jitter tolerance + +Specific requirements for jitter tolerance for individual STM-N rates are given in the following subclauses. These requirements specify the minimum levels of jitter that must be accommodated at an STM-N interface. Guidance on test sequences suitable for SDH systems is provided in ITU-T Recommendation O.172. + +As noted in 6.1.1, SDH equipment can be deployed in different networks. Although the basic jitter tolerance requirements are the same for both networks, the low frequency region of the jitter tolerance requirement will differ to be compatible with the specific network wander requirements that are specified in ITU-T Recommendations G.824 and G.825. These differences are noted in the requirements below. + +##### 6.1.2.1 STM 1/1e jitter tolerance + +The level of jitter that must be accommodated by STM-1 and STM-1e SDH interfaces is specified in Tables 3 and 4 respectively, and are illustrated in Figures 1 and 2. Specifications are given for both optical (STM-1) and electrical (STM-1e) interfaces. Equipment deployed in existing networks may have jitter generation for STM-1e based on STM-1 requirements contained in ITU-T Recommendation G.813. Inter-working between older equipment and equipment meeting the STM-1e requirements in Table 4 is for further study. For networks based on the 1544 kbit/s hierarchy, STM-1e interfaces shall be required to meet the more stringent STM-1 jitter tolerance requirement. + +**Table 3/G.825 – STM-1 input jitter tolerance limit** + +| Frequency
f (Hz) | | Requirement
(Peak-Peak) | +|---------------------------------------|----------------------|-------------------------------| +| 2048 kbit/s networks | 1544 kbit/s networks | | +| – | $10 < f \leq 68.7$ | 10.9 UI | +| $10 < f \leq 19.3$ | – | 38.9 UI (0.25 $\mu\text{s}$ ) | +| $19.3 < f \leq 68.7$ | – | $750 f^{-1}$ UI | +| $68.7 < f \leq 500$ | | $750 f^{-1}$ UI | +| $500 < f \leq 6.5 \text{ k}$ | | 1.5 UI | +| $6.5 \text{ k} < f \leq 65 \text{ k}$ | | $9.8 \times 10^3 f^{-1}$ UI | +| $65 \text{ k} < f \leq 1.3 \text{ M}$ | | 0.15 UI | + +**Table 4/G.825 – STM-1e input jitter tolerance limit** + +| Frequency
f (Hz) | Requirement
(Peak-Peak) | +|--------------------------------------|-------------------------------| +| $10 < f \leq 19.3$ | 38.9 UI (0.25 $\mu\text{s}$ ) | +| $19.3 < f \leq 500$ | $750f^{-1}$ UI | +| $500 < f \leq 3.3\text{ k}$ (Note 2) | 1.5 UI | +| $3.3\text{ k} < f \leq 65\text{ k}$ | $4.9 \times 10^3 f^{-1}$ UI | +| $65\text{ k} < f \leq 1.3\text{ M}$ | 0.075 UI | + +NOTE 1 – STM-1e interface is CMI-encoded, according to ITU-T Recommendation G.703. + +NOTE 2 – When STM-1e interfaces are deployed in networks based on the 1544 kbit/s hierarchy they must meet the requirements for STM-1 in Table 3. + +![Figure 1/G.825 – STM-1 jitter tolerance graph. The Y-axis is 'Pk-Pk Phase Amplitude (UI)' on a logarithmic scale from 1.0E-01 to 1.0E+02. The X-axis is 'Frequency (Hz)' on a logarithmic scale from 1.0E+00 to 1.0E+07. The graph shows a solid line representing the jitter tolerance limit, which is constant at 38.9 UI from 10 Hz to 19.3 Hz, then decreases with a slope of -1 until 500 Hz, where it becomes constant at 1.5 UI until 3.3 kHz. It then decreases with a slope of -1 until 65 kHz, where it becomes constant at 0.075 UI until 1.3 MHz. A dashed horizontal line at 1.5 UI from 10 Hz to 68.7 Hz is labeled '(Note)'.](b05a8a3551db31147979064952179990_img.jpg) + +Figure 1/G.825 – STM-1 jitter tolerance graph. The Y-axis is 'Pk-Pk Phase Amplitude (UI)' on a logarithmic scale from 1.0E-01 to 1.0E+02. The X-axis is 'Frequency (Hz)' on a logarithmic scale from 1.0E+00 to 1.0E+07. The graph shows a solid line representing the jitter tolerance limit, which is constant at 38.9 UI from 10 Hz to 19.3 Hz, then decreases with a slope of -1 until 500 Hz, where it becomes constant at 1.5 UI until 3.3 kHz. It then decreases with a slope of -1 until 65 kHz, where it becomes constant at 0.075 UI until 1.3 MHz. A dashed horizontal line at 1.5 UI from 10 Hz to 68.7 Hz is labeled '(Note)'. + +NOTE – The dashed curve is the requirement for 1544 kbit/s networks for frequencies less than 68.7 Hz. + +**Figure 1/G.825 – STM-1 jitter tolerance** + +![Figure 2/G.825 – STM-1e jitter tolerance requirement graph. The Y-axis is 'Unit Intervals (UIpp)' on a logarithmic scale from 0.01 to 100. The X-axis is 'Frequency (Hz)' on a logarithmic scale from 1.0E+01 to 1.0E+07. The graph shows a solid line representing the jitter tolerance requirement, which is constant at 38.9 UI from 10 Hz to 19.3 Hz, then decreases with a slope of -1 until 500 Hz, where it becomes constant at 1.5 UI until 3.3 kHz. It then decreases with a slope of -1 until 65 kHz, where it becomes constant at 0.075 UI until 1.3 MHz.](8791f79b259a7463279c1aeb14c31580_img.jpg) + +Figure 2/G.825 – STM-1e jitter tolerance requirement graph. The Y-axis is 'Unit Intervals (UIpp)' on a logarithmic scale from 0.01 to 100. The X-axis is 'Frequency (Hz)' on a logarithmic scale from 1.0E+01 to 1.0E+07. The graph shows a solid line representing the jitter tolerance requirement, which is constant at 38.9 UI from 10 Hz to 19.3 Hz, then decreases with a slope of -1 until 500 Hz, where it becomes constant at 1.5 UI until 3.3 kHz. It then decreases with a slope of -1 until 65 kHz, where it becomes constant at 0.075 UI until 1.3 MHz. + +**Figure 2/G.825 – STM-1e jitter tolerance requirement +(applies to 2048 kbit/s networks only)** + +##### 6.1.2.2 STM-4 jitter tolerance + +The level of jitter that must be accommodated by STM-4 SDH interfaces is specified in Table 5 and illustrated in Figure 3. + +**Table 5/G.825 – STM-4 input jitter tolerance limit** + +| Frequency
f (Hz) | | Requirement
(Peak-Peak) | +|---------------------------------------|----------------------|-----------------------------| +| 2048 kbit/s networks | 1544 kbit/s networks | | +| – | $10 < f \leq 18.5$ | $277.5 f^{-1}$ UI | +| – | $18.5 < f \leq 100$ | 15 UI | +| $9.65 < f \leq 100$ | – | $1500 f^{-1}$ UI | +| $100 < f \leq 1000$ | | $1500 f^{-1}$ UI | +| $1 \text{ k} < f \leq 25 \text{ k}$ | | 1.5 UI | +| $25 \text{ k} < f \leq 250 \text{ k}$ | | $3.8 \times 10^4 f^{-1}$ UI | +| $250 \text{ k} < f \leq 5 \text{ M}$ | | 0.15 UI | + +![Figure 3/G.825 – STM-4 jitter tolerance. A log-log plot showing Pk-Pk Phase Amplitude (UI) versus Frequency (Hz). The y-axis ranges from 1.0E-01 to 1.0E+03 UI, and the x-axis ranges from 1.0E+00 to 1.0E+07 Hz. The plot shows a solid line representing the requirement for 2048 kbit/s networks and a dashed line for 1544 kbit/s networks. The solid line starts at approximately 150 UI at 10 Hz, decreases to 15 UI at 100 Hz, then to 1.5 UI at 1000 Hz, and finally to 0.15 UI at 250 kHz. The dashed line starts at approximately 27.75 UI at 10 Hz, decreases to 15 UI at 18.5 Hz, and then follows the solid line. A note indicates that the dashed curve is the requirement for 1544 kbit/s networks for frequencies less than 100 Hz.](411fa16c3211377525ba37c57784fee0_img.jpg) + +Figure 3/G.825 – STM-4 jitter tolerance. A log-log plot showing Pk-Pk Phase Amplitude (UI) versus Frequency (Hz). The y-axis ranges from 1.0E-01 to 1.0E+03 UI, and the x-axis ranges from 1.0E+00 to 1.0E+07 Hz. The plot shows a solid line representing the requirement for 2048 kbit/s networks and a dashed line for 1544 kbit/s networks. The solid line starts at approximately 150 UI at 10 Hz, decreases to 15 UI at 100 Hz, then to 1.5 UI at 1000 Hz, and finally to 0.15 UI at 250 kHz. The dashed line starts at approximately 27.75 UI at 10 Hz, decreases to 15 UI at 18.5 Hz, and then follows the solid line. A note indicates that the dashed curve is the requirement for 1544 kbit/s networks for frequencies less than 100 Hz. + +NOTE – The dashed curve is the requirement for 1544 kbit/s networks for frequencies less than 100 Hz. + +**Figure 3/G.825 – STM-4 jitter tolerance** + +##### 6.1.2.3 STM-16 jitter tolerance + +The level of jitter that must be accommodated by STM-16 SDH interfaces is specified in Table 6 and illustrated in Figure 4. + +**Table 6/G.825 – STM-16 input jitter tolerance limit** + +| Frequency
f (Hz) | | Requirement
(Peak-Peak) | +|------------------------------------|----------------------|-----------------------------| +| 2048 kbit/s networks | 1544 kbit/s networks | | +| – | $10 < f \leq 70.9$ | $1063.5 f^{-1}$ UI | +| – | $70.9 < f \leq 500$ | 15 UI | +| $10 < f \leq 12.1$ | – | 622 UI | +| $12.1 < f \leq 500$ | – | $7500 f^{-1}$ UI | +| $500 < f \leq 5\text{ k}$ | | $7500 f^{-1}$ UI | +| $5\text{ k} < f \leq 100\text{ k}$ | | 1.5 UI | +| $100\text{ k} < f \leq 1\text{ M}$ | | $1.5 \times 10^5 f^{-1}$ UI | +| $1\text{ M} < f \leq 20\text{ M}$ | | 0.15 UI | + +![Figure 4/G.825 – STM-16 jitter tolerance. A log-log plot showing Pk-Pk Phase Amplitude (UI) versus Frequency (Hz). The plot features a solid line representing the jitter tolerance limit and a dashed line representing the requirement for 1544 kbit/s networks for frequencies below 500 Hz. The solid line starts at 1000 UI at 10 Hz, decreases to 100 UI at 100 Hz, then to 10 UI at 1000 Hz, then to 1 UI at 10000 Hz, and finally to 0.15 UI at 1000000 Hz. The dashed line starts at 100 UI at 10 Hz, decreases to 10 UI at 100 Hz, and then follows the solid line for frequencies above 1000 Hz. A note indicates that the dashed curve is the requirement for 1544 kbit/s networks for frequencies less than 500 Hz.](177e8bc1c595b7fe3461d9919f87e044_img.jpg) + +Figure 4/G.825 – STM-16 jitter tolerance. A log-log plot showing Pk-Pk Phase Amplitude (UI) versus Frequency (Hz). The plot features a solid line representing the jitter tolerance limit and a dashed line representing the requirement for 1544 kbit/s networks for frequencies below 500 Hz. The solid line starts at 1000 UI at 10 Hz, decreases to 100 UI at 100 Hz, then to 10 UI at 1000 Hz, then to 1 UI at 10000 Hz, and finally to 0.15 UI at 1000000 Hz. The dashed line starts at 100 UI at 10 Hz, decreases to 10 UI at 100 Hz, and then follows the solid line for frequencies above 1000 Hz. A note indicates that the dashed curve is the requirement for 1544 kbit/s networks for frequencies less than 500 Hz. + +NOTE – The dashed curve is the requirement for 1544 kbit/s networks for frequencies less than 500 Hz. + +**Figure 4/G.825 – STM-16 jitter tolerance** + +##### 6.1.2.4 STM-64 jitter tolerance + +The level of jitter that must be accommodated by STM-64 SDH interfaces is specified in Table 7 and illustrated in Figure 5. + +For the purposes of practical conformance testing, the characteristics of the transmit eye mask need to be carefully considered. This is for further study. + +**Table 7/G.825 – STM-64 input jitter and wander tolerance limit** + +| Frequency
f (Hz) | | Requirement
(Peak-Peak) | +|-------------------------------------|----------------------|-------------------------------| +| 2048 kbit/s networks | 1544 kbit/s networks | | +| – | $10 < f \leq 296$ | $4446^{-1}$ UI | +| – | $296 < f \leq 2000$ | 15 UI | +| $10 < f \leq 12.1$ | – | 2490 UI (0.25 $\mu\text{s}$ ) | +| $12.1 < f \leq 2000$ | – | $3.0 \times 10^4 f^{-1}$ | +| $2000 < f \leq 20\text{ k}$ | | $3.0 \times 10^4 f^{-1}$ | +| $20\text{ k} < f \leq 400\text{ k}$ | | 1.5 UI | +| $400\text{ k} < f \leq 4\text{ M}$ | | $6.0 \times 10^5 f^{-1}$ UI | +| $4\text{ M} < f \leq 80\text{ M}$ | | 0.15 UI | + +![Figure 5/G.825 – STM-64 jitter tolerance. A log-log plot showing Pk-Pk Phase Amplitude (UI) versus Frequency (Hz). The y-axis ranges from 1.0E-01 to 1.0E+04 UI, and the x-axis ranges from 1.0E+00 to 1.0E+08 Hz. A solid line represents the requirement for 2048 kbit/s networks, and a dashed line represents the requirement for 1544 kbit/s networks for frequencies less than 2 kHz. The solid line starts at approximately 3000 UI at 10 Hz, decreases to 15 UI at 2000 Hz, then to 1.5 UI at 20 kHz, then to 0.15 UI at 4 MHz, and remains at 0.15 UI up to 80 MHz. The dashed line starts at approximately 500 UI at 10 Hz, decreases to 15 UI at 2000 Hz, and then follows the solid line for frequencies above 2 kHz.](b3df5964338063224492c01f09e4fed6_img.jpg) + +Figure 5/G.825 – STM-64 jitter tolerance. A log-log plot showing Pk-Pk Phase Amplitude (UI) versus Frequency (Hz). The y-axis ranges from 1.0E-01 to 1.0E+04 UI, and the x-axis ranges from 1.0E+00 to 1.0E+08 Hz. A solid line represents the requirement for 2048 kbit/s networks, and a dashed line represents the requirement for 1544 kbit/s networks for frequencies less than 2 kHz. The solid line starts at approximately 3000 UI at 10 Hz, decreases to 15 UI at 2000 Hz, then to 1.5 UI at 20 kHz, then to 0.15 UI at 4 MHz, and remains at 0.15 UI up to 80 MHz. The dashed line starts at approximately 500 UI at 10 Hz, decreases to 15 UI at 2000 Hz, and then follows the solid line for frequencies above 2 kHz. + +NOTE – The dashed curve is the requirement for 1544 kbit/s networks for frequencies less than 2 kHz. + +**Figure 5/G.825 – STM-64 jitter tolerance** + +### 6.2 Jitter and wander generation + +For SDH equipment, jitter and wander generation requirements are given in ITU-T Recommendations G.783, G.812 and G.813. Guidelines for the measurement of wander are included in Appendix II. + +### 6.3 Jitter and wander transfer + +Jitter and wander transfer for SDH equipment is dependent on the synchronization method used in each type of equipment. Jitter and wander transfer requirements for SDH equipment are specified in ITU-T Recommendations G.783, G.812 and G.813. + +## APPENDIX I + +### Relationship between network interface jitter requirements and input jitter tolerance + +### I.1 Network interface jitter requirements + +For all SDH bit rates, two network limits are specified in Table 1: one for a wide-band measurement filter and one for a high-band measurement filter. The general form of this specification is shown in Table I.1 and is applicable to all SDH rates. + +At any SDH network interface, the following output jitter specifications must be met: + +Timing jitter as measured over a 60-second interval with a band pass filter with a lower cut-off frequency $f_1$ and a minimum upper cut-off frequency $f_4$ shall not exceed $A_2$ Unit Intervals (UI) peak-to-peak. Also, timing jitter as measured over a 60-second interval with a band pass filter with a lower cut-off frequency $f_3$ and a minimum upper cut-off frequency $f_4$ shall not exceed $A_1$ Unit Intervals (UI) peak-to-peak. The roll off at lower cut-off frequency, $f_1$ and $f_3$ , shall be 20 dB/decade. The roll off at the upper cut-off frequency, $f_4$ , shall be $-60$ dB/decade in accordance with ITU-T Recommendation O.172. + +**Table I.1/G.825 – General form for SDH interface jitter requirements** + +| Measurement filter | Measurement bandwidth | Peak-to-peak amplitude (UI pp ) | +|--------------------|-----------------------|--------------------------------------------| +| Wide-band | $f_1$ to $f_4$ | $A_2$ | +| High-band | $f_3$ to $f_4$ | $A_1$ | + +The value of $f_1$ reflects the narrowest timing circuit cutoff frequency expected in a line system. The timing circuit may time a regenerator's output signal and could be implemented as a Phase-Locked Loop (PLL). Jitter at frequencies higher than the bandwidth of this PLL will be partially absorbed by the PLL's buffer. The portion not absorbed could cause transmission errors due to buffer spill. Jitter at frequencies lower than this bandwidth will simply pass through without affecting transmission performance. The value of $f_1$ therefore represents the narrowest bandwidth that might be used in this output timing circuit. The value of $f_3$ is related to the bandwidth of input timing acquisition circuitry. Jitter at frequencies higher than this bandwidth will constitute alignment jitter and will cause an optical power penalty due to its effect on the eye pattern. This high frequency jitter must therefore be limited to the same degree that equipment specifications limit optical power penalty through jitter tolerance. + +The value of $f_4$ reflects reasonable measurement limitations and is listed to establish minimum measurement bandwidth requirements. $f_4$ is chosen to include all expected, significant alignment jitter. A value one decade beyond the widest expected cutoff frequency was chosen (see ITU-T Recommendation G.783). + +The values of $A_1$ and $A_2$ are directly related to input sinusoidal jitter tolerance. These parameters have built-in margin and are reasonably conservative because: + +- 1) sinusoidal jitter represents worst case jitter with respect to input jitter tolerance; and +- 2) accumulated SDH line jitter will not be sinusoidal (instead, it will be noisy). + +### I.2 Input jitter tolerance of network equipment + +The general form of the weighting filters used for measuring output jitter at a network interface given in Table I.1 are reproduced below in Figure I.1. The filter responses are given in equations I.2-1 and I.2-2. + +![Figure I.1/G.825 – Weighting filters for measuring network interface output jitter. The graph shows two magnitude response curves, |H1(j2πft)| and |H2(j2πft)|, plotted against frequency f (Hz). The y-axis is labeled 1. The curve for |H1(j2πft)| starts at a low value, rises to 1 at frequency f1, and remains at 1 until f4. The curve for |H2(j2πft)| starts at a low value, rises to 1 at frequency f3, and remains at 1 until f4. Both curves drop to 0 at f4. A dashed line represents the combined mask, which is the lower of the two curves. The x-axis is labeled f (Hz) and has markers for f1, f3, and f4. A small text 'T1316860-99' is visible in the bottom right corner of the graph area.](b6750d26d3dd287a4a4d49b3670a44bd_img.jpg) + +Figure I.1/G.825 – Weighting filters for measuring network interface output jitter. The graph shows two magnitude response curves, |H1(j2πft)| and |H2(j2πft)|, plotted against frequency f (Hz). The y-axis is labeled 1. The curve for |H1(j2πft)| starts at a low value, rises to 1 at frequency f1, and remains at 1 until f4. The curve for |H2(j2πft)| starts at a low value, rises to 1 at frequency f3, and remains at 1 until f4. Both curves drop to 0 at f4. A dashed line represents the combined mask, which is the lower of the two curves. The x-axis is labeled f (Hz) and has markers for f1, f3, and f4. A small text 'T1316860-99' is visible in the bottom right corner of the graph area. + +Figure I.1/G.825 – Weighting filters for measuring network interface output jitter + +$$H_1(s) = \frac{s}{s + \omega_1} \cdot \frac{\omega_4^3}{s^3 + 2\omega_4 s^2 + 2\omega_4^2 s + \omega_4^3} \quad (I.2-1)$$ + +$$H_2(s) = \frac{s}{s + \omega_3} \cdot \frac{\omega_4^3}{s^3 + 2\omega_4 s^2 + 2\omega_4^2 s + \omega_4^3} \quad (I.2-2)$$ + +$$\omega_1 = 2\pi f_1 \quad \omega_3 = 2\pi f_3 \quad \omega_4 = 2\pi f_4$$ + +The first term of the function $H_1(s)$ represents the phase error transfer function $H_e(s)$ of some PLL, and its amplitude of $A_2 = 1.5$ UIpp represents its phase error tolerance. + +Then the corresponding input phase tolerance of the PLL is given by: + +$$A_{tol1}(f) = \frac{A_2}{|H_1(j2\pi f)|} \quad (I.2-3)$$ + +Similarly, the input phase tolerance corresponding to $H_2(s)$ and its amplitude of $A_1 = 0.1$ UIpp is given by: + +$$A_{tol2}(f) = \frac{A_1}{|H_2(j2\pi f)|} \quad (I.2-4)$$ + +These sinusoidal jitter tolerance masks are illustrated in Figure I.2. If unweighted sinusoidal jitter at a network interface satisfies *both* of these masks, it also satisfies (i.e. lies below) a single mask that is the lower of the two masks for each frequency. Such a combined mask is shown as a dashed curve in Figure I.3. + +![Figure I.2/G.825 – Upper bounds on sinusoidal jitter amplitude. A graph showing Amplitude (UIpp) on the y-axis and frequency f (Hz) on the x-axis. The y-axis has labels A1 (0.15) and A2 (1.5). The x-axis has labels f1, f3, and f4. Two curves are shown: A_tol1(f) (solid line) and A_tol2(f) (dashed line). A_tol1(f) starts at a high amplitude, decreases linearly to A2 at f1, and then remains constant at A2 until f4. A_tol2(f) starts at a high amplitude, decreases linearly to A1 at f3, and then remains constant at A1 until f4.](b2d16e07bfa79d67a8adabf7e26c7764_img.jpg) + +Figure I.2/G.825 – Upper bounds on sinusoidal jitter amplitude. A graph showing Amplitude (UIpp) on the y-axis and frequency f (Hz) on the x-axis. The y-axis has labels A1 (0.15) and A2 (1.5). The x-axis has labels f1, f3, and f4. Two curves are shown: A\_tol1(f) (solid line) and A\_tol2(f) (dashed line). A\_tol1(f) starts at a high amplitude, decreases linearly to A2 at f1, and then remains constant at A2 until f4. A\_tol2(f) starts at a high amplitude, decreases linearly to A1 at f3, and then remains constant at A1 until f4. + +**Figure I.2/G.825 – Upper bounds on sinusoidal jitter amplitude** + +Figure I.3 compares this combined mask with the STM-1(optical) input jitter/wander sinusoidal tolerance mask. They are the same in the range $19.3 < f < 1.3 \text{ MHz}$ . In the wander region of phase ( $f < 19.3 \text{ Hz}$ ), there are no interface specifications that use weighting filters to check the peak-to-peak phase. (The 10 Hz low-pass wander measurement filter might be considered a weighting filter, but for wander it is MTIE or TDEV that is measured rather than peak-to-peak phase). + +![Figure I.3/G.825 – Upper bound on sinusoidal output jitter at an STM-1(Optical) interface [lower of A_tol1(f) or A_tol2(f)] compared with input jitter/wander tolerance mask. A graph showing Amplitude (UIpp) on the y-axis and frequency f (Hz) on the x-axis. The y-axis has labels A1 (0.15), A2 (1.5), and 38.9. The x-axis has labels 0.125, 19.3, 500, 6.5k, 65k, and 1.3M. A solid line represents the lower of A_tol1(f) or A_tol2(f). A dashed line represents the input jitter/wander tolerance mask. The solid line is constant at 38.9 UIpp from 0.125 Hz to 19.3 Hz, then decreases linearly to A2 at 500 Hz, then decreases linearly to A1 at 65k Hz, and then remains constant at A1 until 1.3M Hz. The dashed line is constant at 38.9 UIpp from 0.125 Hz to 19.3 Hz, then decreases linearly to A2 at 500 Hz, then decreases linearly to A1 at 6.5k Hz, and then remains constant at A1 until 1.3M Hz. An arrow points to the solid line with the label 'Lower of A_tol1(f) or A_tol2(f)'. Another arrow points to the dashed line with the label 'Figure 1/G.825'.](1c427123350e0e73e2a109b79069314b_img.jpg) + +Figure I.3/G.825 – Upper bound on sinusoidal output jitter at an STM-1(Optical) interface [lower of A\_tol1(f) or A\_tol2(f)] compared with input jitter/wander tolerance mask. A graph showing Amplitude (UIpp) on the y-axis and frequency f (Hz) on the x-axis. The y-axis has labels A1 (0.15), A2 (1.5), and 38.9. The x-axis has labels 0.125, 19.3, 500, 6.5k, 65k, and 1.3M. A solid line represents the lower of A\_tol1(f) or A\_tol2(f). A dashed line represents the input jitter/wander tolerance mask. The solid line is constant at 38.9 UIpp from 0.125 Hz to 19.3 Hz, then decreases linearly to A2 at 500 Hz, then decreases linearly to A1 at 65k Hz, and then remains constant at A1 until 1.3M Hz. The dashed line is constant at 38.9 UIpp from 0.125 Hz to 19.3 Hz, then decreases linearly to A2 at 500 Hz, then decreases linearly to A1 at 6.5k Hz, and then remains constant at A1 until 1.3M Hz. An arrow points to the solid line with the label 'Lower of A\_tol1(f) or A\_tol2(f)'. Another arrow points to the dashed line with the label 'Figure 1/G.825'. + +**Figure I.3/G.825 – Upper bound on sinusoidal output jitter at an STM-1(Optical) interface [lower of $A_{tol1}(f)$ or $A_{tol2}(f)$ ] compared with input jitter/wander tolerance mask** + +## APPENDIX II + +### Measurement methodology for output wander of synchronous interfaces + +Instrumentation in accordance with ITU-T Recommendation O.172 is appropriate for measurement of wander parameters. + +When the signal is synchronous (i.e. normally PRC-traceable), and is used to carry synchronization, its wander is measured by comparing its phase with that of another PRC. The test procedure for measuring MTIE of a synchronous signal is shown in Figure II.1 (the standard estimator formula for calculating MTIE is given in Annex B/G.810). + +The PRC used for the wander measurement need not be the same as that used to originate the synchronous signal, for most measurement applications. However, it should be noted that the worst-case frequency difference between two PRCs could give rise to a phase difference of the order of 2 µs per day. + +![Block diagram of MTIE measurement of synchronous signals. A 'Source Reference' PRC connects to a 'Terminating Element', which is part of a 'Transport Network'. The output of the Transport Network goes to a 'Phase Detector'. A 'Measurement Reference' PRC also connects to the 'Phase Detector'. The output of the Phase Detector is 'Phase', which goes to a '10-Hz LPF'. The output of the 10-Hz LPF is 'Wander', which goes to a 'Calculate MTIE' block. The output of the 'Calculate MTIE' block is 'MTIE'. The diagram is labeled T1316890-99.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +``` +graph LR; PRC1[PRC Source Reference] --> TE[Terminating Element]; TE --> TN((Transport Network)); TN --> PD[Phase Detector]; PRC2[PRC Measurement Reference] --> PD; PD -- Phase --> LPF[10-Hz LPF]; LPF -- Wander --> MTIE_CALC[Calculate MTIE]; MTIE_CALC -- MTIE --> OUT[MTIE]; +``` + +Block diagram of MTIE measurement of synchronous signals. A 'Source Reference' PRC connects to a 'Terminating Element', which is part of a 'Transport Network'. The output of the Transport Network goes to a 'Phase Detector'. A 'Measurement Reference' PRC also connects to the 'Phase Detector'. The output of the Phase Detector is 'Phase', which goes to a '10-Hz LPF'. The output of the 10-Hz LPF is 'Wander', which goes to a 'Calculate MTIE' block. The output of the 'Calculate MTIE' block is 'MTIE'. The diagram is labeled T1316890-99. + +Figure II.1/G.825 – MTIE measurement of synchronous signals + +## APPENDIX III + +### SDH Line systems and Interworking implications + +ITU-T Recommendation G.783 identifies two different types of regenerators, Type A and Type B, which can be used in SDH line systems. The different regenerator types exhibit different jitter characteristics. Type B regenerators exhibit reduced jitter tolerance. Performance penalties due to excessive alignment jitter place restrictions on the use of both Type A and Type B equipment in the same SDH line system. Moreover, the amplitude/frequency characteristics of the accumulated jitter can adversely affect transmission-performance. These limitations must be taken into account by carrier entities who are administering the particular SDH line system. + +At network interfaces (e.g. those at international boundaries), STM-N signals must meet interface limits regardless of the individual carrier's equipment choice. It is therefore desirable that the interface requirement is compatible with the type of jitter expected to appear on both Type A and Type B line systems. + +### Interworking implications + +Taking into account the characteristics of the Type A and Type B regenerators and the above interface specifications, the following equipment interworking implications can be derived: + +- 1) the magnitude of jitter expected to accumulate on all SDH line systems employing only Type A equipment falls-within the bounds specified in Table 1; +- 2) the magnitude of jitter expected to accumulate on all SDH line systems employing only Type B equipment falls within the bounds specified in Table 1; +- 3) equipment exhibiting Type A jitter tolerance characteristics will tolerate that jitter which meets the limits given in Table 1; +- 4) equipment exhibiting Type B jitter tolerance characteristics will tolerate the jitter expected to accumulate on Type B SDH line systems. Such equipment, however, may require some jitter reduction for input signals that just approach the limits given for the appropriate line rates in Tables 3, 5, 6 or Table 7. This is expected to be the case when Type B equipment follows a chain of Type A regenerators. This represents the only interworking consideration required by the SDH Interface specifications proposed in this ITU-T Recommendation. + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/G/T-REC-G.8271.2-202105-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a39f13c51c76d252230899d1e5ebce6527435af9 --- /dev/null +++ b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6aef18f2fbea7a7c01eb645eef5f27ba43a09b59c3122d529876628aa27dd52a +size 35302 diff --git a/marked/G/T-REC-G.8271.2-202105-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f7ccde47e1c630dfd820f9a2c64c73de23d54dc --- /dev/null +++ b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:367b50e00990b2a2e0adfd91321521829b59931e68242de1ee38685bec451b6f +size 30819 diff --git a/marked/G/T-REC-G.8271.2-202105-I_PDF-E/29f586959675cafdf81cf934954908eb_img.jpg b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/29f586959675cafdf81cf934954908eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..770327f9cf6ac9c34bd8a19b2d44f13736cf38a9 --- /dev/null +++ b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/29f586959675cafdf81cf934954908eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31f41a139974d7ea57d1d01a41d33a304ff9810baf5ee74e2b53062f95a6a8c2 +size 41660 diff --git a/marked/G/T-REC-G.8271.2-202105-I_PDF-E/66c2bf11a8f117cddf67eff92d4c736c_img.jpg b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/66c2bf11a8f117cddf67eff92d4c736c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a66843fcd7b0b230b2eff1ead728de62d80c540 --- /dev/null +++ b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/66c2bf11a8f117cddf67eff92d4c736c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04365c6a3d0aa416d888f748b21822d1561998af3e09b1f559a11b5db29d59f0 +size 42286 diff --git a/marked/G/T-REC-G.8271.2-202105-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd04f2c068c2ac6764d83a1ca4b2e87bc09daac3 --- /dev/null +++ b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2329842c6822582b0da1b06ad396c79528339852e0074f87adca3cc7663ff2a +size 33047 diff --git a/marked/G/T-REC-G.8271.2-202105-I_PDF-E/79cb7fa0e9c78ec5cd0b0de977824f8d_img.jpg b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/79cb7fa0e9c78ec5cd0b0de977824f8d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53704332b3f935af3d08e22bd42c850281aa9492 --- /dev/null +++ b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/79cb7fa0e9c78ec5cd0b0de977824f8d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d4f1f837e018bf7130b19afffff3d83dac4c41a291f49c54d21375d1d7f3d59 +size 132923 diff --git a/marked/G/T-REC-G.8271.2-202105-I_PDF-E/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee5d7012cb208b67bef6190593bd497ba51778b2 --- /dev/null +++ b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc533e08b669b36248efb69fff51aa6a3bdf32f0e61ce16df8119b08c5ee6d7c +size 36620 diff --git a/marked/G/T-REC-G.8271.2-202105-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51fa47c6194fb3a6b6fac8f8edf983d27cba73c6 --- /dev/null +++ b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dfd2f1879c7abd9f932939e2ff1439040972eee9b22bf520ab1c56b86cf50b5 +size 39889 diff --git a/marked/G/T-REC-G.8271.2-202105-I_PDF-E/b10763be31553f31cbb795653b731a43_img.jpg b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/b10763be31553f31cbb795653b731a43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4768edc1bd5b9d2dea6cc786b1734b4256cc1ecb --- /dev/null +++ b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/b10763be31553f31cbb795653b731a43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a3531b7a61d6cd3f30ddff0f8e70161363f52a59bd1fe2325db8decffa9c329 +size 22863 diff --git a/marked/G/T-REC-G.8271.2-202105-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e32f9b8f1141bed243c16e02a6cd1411cbb87f1 --- /dev/null +++ b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_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.8271.2-202105-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b607887c0fb5e5b714a2fdb635365592a8d6c005 --- /dev/null +++ b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d0f7ff31162dc1f812a022d61c6b83c49a0b49718a80a52bd000a07e246d908 +size 42750 diff --git a/marked/G/T-REC-G.8271.2-202105-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..892660483b5154d5511c1f9da07cda2fac52579d --- /dev/null +++ b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1337ebc6ba97d605254a489f6a46dc4ef6d0f966ad481adc23b3d4a3644972ca +size 15072 diff --git a/marked/G/T-REC-G.8271.2-202105-I_PDF-E/raw.md b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fa8e737df6c7b9e9eedcb3a1559b9df16a8a6cbe --- /dev/null +++ b/marked/G/T-REC-G.8271.2-202105-I_PDF-E/raw.md @@ -0,0 +1,823 @@ + + +**ITU-T** + +**G.827.1.2/Y.1366.2** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(05/2021) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Packet over Transport aspects – Synchronization, quality +and availability targets + +SERIES Y: GLOBAL INFORMATION +INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, +NEXT-GENERATION NETWORKS, INTERNET OF +THINGS AND SMART CITIES + +Internet protocol aspects – Transport + +--- + +**Network limits for time synchronization in +packet networks with partial timing support +from the network** + +Recommendation ITU-T G.827.1.2/Y.1366.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 | +| 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.8271.2/Y.1366.2 + +# Network limits for time synchronization in packet networks with partial timing support from the network + +## Summary + +Recommendation ITU-T G.8271.2/Y.1366.2 specifies the maximum network limits of phase and time error that shall not be exceeded. It specifies the minimum equipment tolerance to phase and time error that shall be provided at the boundary of these packet networks at phase and time synchronization interfaces. It also outlines the minimum requirements for the synchronization function of network elements. + +Recommendation ITU-T G.8271.2/Y.1366.2 addresses the case of time and phase distribution across a network with the packet-based method with partial timing support to the protocol level from the network. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|---------------------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.8271.2/Y.1366.2 | 2017-08-13 | 15 | 11.1002/1000/13324 | +| 1.1 | ITU-T G.8271.2/Y.1366.2 (2017) Amd. 1 | 2018-03-16 | 15 | 11.1002/1000/13551 | +| 1.2 | ITU-T G.8271.2/Y.1366.2 (2017) Amd. 2 | 2018-11-29 | 15 | 11.1002/1000/13768 | +| 2.0 | ITU-T G.8271.2/Y.1366.2 | 2021-05-29 | 15 | 11.1002/1000/14638 | + +## Keywords + +Network limits, partial timing support, phase, precision time protocol, synchronization, time. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2021 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|--------------|-------------------------------------------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 3 | +| 6 | Network reference model ..... | 4 | +| 7 | Packet network limits ..... | 4 | +| 7.1 | Network limits at reference points A and L ..... | 5 | +| 7.2 | Network limit at reference point B..... | 5 | +| 7.3 | Network limits at reference point C ..... | 5 | +| 7.4 | Network limit at reference point D..... | 7 | +| Appendix I | Deployment scenarios for partial timing support networks..... | 8 | +| I.1 | APTS and PTS network use cases..... | 8 | +| I.2 | Full timing support network followed by an APTS network or PTS network
..... | 9 | +| I.3 | PTS network followed by an FTS network ..... | 10 | +| I.4 | APTS network followed by a PTS network..... | 10 | +| I.5 | APTS network followed by an FTS network ..... | 10 | +| I.6 | Use of PTS network to bridge between two FTS networks ..... | 11 | +| Appendix II | Considerations for handling precision time protocol traffic in networks with
partial timing support..... | 12 | +| II.1 | Network aspects..... | 12 | +| II.2 | Time error performance aspects ..... | 13 | +| Appendix III | The use of frequency to maintain precise time ..... | 14 | +| Appendix IV | Noise accumulation model in partially aware networks ..... | 16 | +| Bibliography | ..... | 17 | + + + +# **Network limits for time synchronization in packet networks with partial timing support from the network** + +## **1 Scope** + +This Recommendation specifies the maximum network limits of phase and time error that shall not be exceeded. It specifies the minimum equipment tolerance to phase and time error that shall be provided at the boundary of these packet networks at phase and time synchronization interfaces. It also outlines the minimum requirements for the synchronization function of network elements. + +This Recommendation addresses the distribution of time and phase across a network, using the packet-based method with partial timing support (PTS) to the protocol level from the network. In particular, it applies to the assisted partial timing support (APTS) and PTS architectures described in [ITU-T G.8275] and the precision time protocol (PTP) profile defined in [ITU-T G.8275.2]. + +This Recommendation addresses the following cases. + +### 1) APTS. + +In the APTS configuration, PTP is used as a backup timing source to a local time reference (e.g., primary reference time clock (PRTC) based on the global navigation satellite system (GNSS)) for durations up to 72 h. It is not intended to use PTP as the primary timing source. Network requirements take into consideration the dynamic time error (dTE) generated by the network. + +### 2) PTS from the network. + +In the PTS configuration, PTP is used as the primary source of time to the end application. In this mode, a local time reference (e.g., GNSS) is not available. + +Network requirements take into consideration the combination of both the constant time error (cTE) and dTE components generated by the network. + +A network that is based on the architecture defined in [ITU-T G.8265], and is designed to meet the network limits for frequency defined in [ITU-T G.8261.1], is not designed for the delivery of accurate time or phase, which requires much lower levels of packet delay variation (PDV) and asymmetry. The network limits specified in this Recommendation are for small, well-controlled networks (e.g., in-building or last-mile network segments), which can guarantee that the stringent PDV and asymmetry network limits are met. Further guidance can be found in Appendix II. + +The main focus of this Recommendation is to meet the requirements of Class 4 in [ITU-T G.8271], Table 1, i.e., a maximum absolute time error of 1.5 $\mu\text{s}$ . Other classes with less stringent requirements are for further study. + +The necessary clock specifications are for further study. + +The packet networks that are in the scope of this Recommendation are currently limited to the following types: + +- Ethernet: [IEEE 802.3] and [IEEE 802.1Q] +- Multiprotocol label switching (MPLS): [IETF RFC 3031] and [ITU-T G.8110] +- Internet protocol (IP): [IETF RFC 791] and [IETF RFC 2460] + +The use of other network types are for further study. + +The physical layer that is relevant to this specification is the Ethernet media type as defined in [IEEE 802.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 standalone document, the status of a Recommendation. + +- [ITU-T G.810] Recommendation ITU-T G.810 (1996), *Definitions and Terminology for Synchronization Networks*. +- [ITU-T G.8110] Recommendation ITU-T G.8110/Y.1370 (2005), *MPLS Layer Network Architecture*. +- [ITU-T G.8260] Recommendation ITU-T G.8260 (2020), *Definitions and Terminology for Synchronization in Packet Networks*. +- [ITU-T G.8261.1] Recommendation ITU-T G.8261.1/Y.1361.1 (2012), *Packet Delay Variation Network Limits Applicable to Packet-based Methods (Frequency Synchronization)*. +- [ITU-T G.8265] Recommendation ITU-T G.8265/Y.1365 (2010), *Architecture and Requirements for Packet-based Frequency Delivery*. +- [ITU-T G.8271] Recommendation ITU-T G.8271/Y.1366 (2020), *Time and Phase Synchronization Aspects of Telecommunication Networks*. +- [ITU-T G.8271.1] Recommendation ITU-T G.8271.1/Y.1366.1 (2020), *Network Limits for Time Synchronization in Packet Networks with full timing support from the network*. +- [ITU-T G.8272] Recommendation ITU-T G.8272/Y.1367 (2018), *Timing Characteristics of Primary Reference Time Clocks*. +- [ITU-T G.8273.4] Recommendation ITU-T G.8273.4/Y.1368.4 (2020), *Timing Characteristics of Telecom Boundary Clocks and Telecom Time Slave Clocks for Use with Partial Timing Support from the Network*. +- [ITU-T G.8275] Recommendation ITU-T G.8275/Y.1369 (2020), *Architecture and Requirements for Packet-based Time and Phase Distribution*. +- [ITU-T G.8275.1] Recommendation ITU-T G.8275.1/Y.1369.1 (2020), *Precision Time Protocol Telecom Profile for Phase/Time Synchronization with Full Timing Support from the Network*. +- [ITU-T G.8275.2] Recommendation ITU-T G.8275.2/Y.1369.2 (2020), *Precision Time Protocol Telecom Profile for Time/Phase Synchronization with Partial Timing Support from the Network*. +- [IEEE 802.1Q] IEEE 802.1Q-2018, *IEEE Standard for Local and Metropolitan Area Network--Bridges and Bridged Networks*. +- [IEEE 802.3] IEEE 802.3-2018, *IEEE Standard for Ethernet*. +- [IEEE 1588-2008] IEEE 1588-2008, *IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems*. +- [IEEE 1588-2019] IEEE 1588-2019, *IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems*. +- [IETF RFC 791] IETF RFC 791 (1981), *Internet Protocol (IP)*. +- [IETF RFC 2460] IETF RFC 2460 (1998), *Internet Protocol, Version 6 (IPv6) Specification*. +- [IETF RFC 3031] IETF RFC 3031 (2001), *Multiprotocol Label Switching Architecture*. + +## 3 Definitions + +The terms and definitions used in this Recommendation are contained in [ITU-T G.810] and [ITU-T G.8260] + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------|--------------------------------------------| +| APTS | Assisted Partial Timing Support | +| BCMA | Best Master Clock Algorithm | +| cTE | constant Time Error | +| dTE | dynamic Time Error | +| FTS | Full Timing Support | +| GNSS | Global Navigation Satellite System | +| IP | Internet Protocol | +| IWF | Interworking Function | +| IWF F-P | Interworking Function from FTS to PTS | +| IWF P-F | Interworking Function from PTS to FTS | +| MPLS | Multiprotocol Label Switching | +| PDV | Packet Delay Variation | +| PRS | Primary Reference Source | +| PRTC | Primary Reference Time Clock | +| PTP | Precision Time Protocol | +| PTS | Partial Timing Support | +| RAN | Radio Access Network | +| T-BC | Telecom Boundary Clock | +| T-BC-A | Telecom Boundary Clock – Partial Support | +| T-BC-P | Telecom Boundary Clock – Partial support | +| T-GM | Telecom Grandmaster | +| TLV | Type Length Variable | +| T-TSC | Telecom Time Slave Clock | +| T-TSC-A | Telecom Time Slave Clock – Assisted | +| T-TSC-P | Telecom Time Slave Clock – Partial support | + +## 5 Conventions + +Within this Recommendation, the following conventions are used: the term PTP refers to the protocol defined in [IEEE 1588-2008] and [IEEE 1588-2019]. + +The term PRTC refers to the PRTC-A specification defined in [ITU-T G.8272]. A PRTC-B could be substituted as an alternative. + +The term telecom boundary clock – assisted (T-BC-A) (e.g., by GNSS) refers to a device consisting of a boundary clock as defined in [IEEE 1588-2008] and [IEEE 1588-2019], assisted by a local time reference clock device, and with additional performance characteristics as specified in [ITU-T G.8273.4]. + +The term telecom boundary clock – partial support (T-BC-P) refers to a device consisting of a boundary clock as defined in [IEEE 1588-2008] and [IEEE 1588-2019], with only PTS at the protocol level from the network, and with additional performance characteristics specified in [ITU-T G.8273.4]. + +The term telecom time slave clock – assisted (T-TSC-A) (e.g., by GNSS) refers to a device consisting of a PTP slave only ordinary clock as defined in [IEEE 1588-2008] and [IEEE 1588-2019], assisted by a local time reference clock device, and with additional performance characteristics as specified in [ITU-T G.8273.4]. + +The term telecom time slave clock – partial support (T-TSC-P) refers to a device consisting of a PTP slave only ordinary clock as defined in [IEEE 1588-2008] and [IEEE 1588-2019], with only PTS at the protocol level from the network, and with additional performance characteristics as specified in [ITU-T G.8273.4]. + +The terms "dTE" and "time noise" are used interchangeably throughout this Recommendation to indicate jitter and wander components of the timing signal. + +# 6 Network reference model + +The general network reference model is described in [ITU-T G.8271]. + +# 7 Packet network limits + +This clause defines the network limits that apply to the packet network, i.e., reference points A, B, C and D in Figures 1 and 2. + +![Figure 1: Reference model for network limits for APTS. The diagram shows a sequence of components: PRTC, PRC (at point A) connected to T-GM (at point B), which is connected to a 'Partial timing support packet network' (between points B and C). This network connects to T-TSC-A (GNSS-assisted) (at point C), which is also connected to a 'Local time reference (e.g., GNSS)' via line L. The T-TSC-A connects to an 'End application' (at point D) via a triangle symbol representing a time noise source. The output is at point E. The diagram is labeled G.8271.2-Y.1366.2(21)_F01.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +``` + +graph LR + A[PRTC, PRC] --> TGM[T-GM] + TGM --> PTSN((Partial timing support packet network)) + PTSN --> TTSCA[T-TSC-A GNSS-assisted] + LTR[Local time reference e.g., GNSS] -- L --> TTSCA + TTSCA --> EA[End application] + + subgraph Reference Points + A_pt[A] -.-> A + B_pt[B] -.-> TGM + C_pt[C] -.-> TTSCA + D_pt[D] -.-> EA + E_pt[E] -.-> EA + end + +``` + +Figure 1: Reference model for network limits for APTS. The diagram shows a sequence of components: PRTC, PRC (at point A) connected to T-GM (at point B), which is connected to a 'Partial timing support packet network' (between points B and C). This network connects to T-TSC-A (GNSS-assisted) (at point C), which is also connected to a 'Local time reference (e.g., GNSS)' via line L. The T-TSC-A connects to an 'End application' (at point D) via a triangle symbol representing a time noise source. The output is at point E. The diagram is labeled G.8271.2-Y.1366.2(21)\_F01. + +**Figure 1 – Reference model for network limits for APTS** + +![Figure 2: Reference model for network limits for PTS. The diagram shows a sequence of components: PRTC (at point A) connected to T-GM (at point B), which is connected to a 'Partial timing support packet network' (between points B and C). This network connects to T-TSC-P (at point C). The T-TSC-P connects to an 'End application' (at point D) via a triangle symbol representing a time noise source. The output is at point E. The diagram is labeled G.8271.2-Y.1366.2(21)_F02.](b10763be31553f31cbb795653b731a43_img.jpg) + +``` + +graph LR + A[PRTC] --> TGM[T-GM] + TGM --> PTSN((Partial timing support packet network)) + PTSN --> TTSCP[T-TSC-P] + TTSCP --> EA[End application] + + subgraph Reference Points + A_pt[A] -.-> A + B_pt[B] -.-> TGM + C_pt[C] -.-> TTSCP + D_pt[D] -.-> EA + E_pt[E] -.-> EA + end + +``` + +Figure 2: Reference model for network limits for PTS. The diagram shows a sequence of components: PRTC (at point A) connected to T-GM (at point B), which is connected to a 'Partial timing support packet network' (between points B and C). This network connects to T-TSC-P (at point C). The T-TSC-P connects to an 'End application' (at point D) via a triangle symbol representing a time noise source. The output is at point E. The diagram is labeled G.8271.2-Y.1366.2(21)\_F02. + +**Figure 2 – Reference model for network limits for PTS** + +The two examples in Figures 1 and 2 are simplified. They represent use cases 1a and 1b in Appendix I. It is highlighted in Appendix I that in some deployment cases, the part of the network located between + +points C and D may contribute significantly to the total time error budget. In these cases, the network limits apply to point D. + +NOTE – The network limit applicable at reference point E is defined by the specific application per Table 1 of [ITU-T G.8271]. The applications corresponding to Class 4 (1.5 microseconds), according to Table 1 of [ITU-T G.8271], are currently considered in this Recommendation. + +## 7.1 Network limits at reference points A and L + +The network limits applicable at reference points A and L, i.e., at the output of the PRTC or the local time reference, are defined in [ITU-T G.8272]. In particular, according to [ITU-T G.8272] the maximum absolute time error (TE) is: + +$$\max|TE| \leq 100 \text{ ns}$$ + +NOTE 1 – This limit is applicable under normal, locked operating conditions. The limit under failure conditions at the PRTC is for further study. + +NOTE 2 – The network limit at point L may not be applicable in all cases. For example, if a GNSS receiver is embedded within the T-BC-A/T-TSC-A, this interface may not be accessible. + +NOTE 3 – The interface at reference point L can be either 1PPS or PTP. + +NOTE 4 – In the case that the interface at reference point L is PTP, the PTP profile and domain used at the interface may be: + +- the same as for the network between reference points B and C, in which case the normal BCMA (best master clock algorithm) for the profile applies, with higher priority assigned to the local time reference, +- or different, in which case the PTP domains operate independently, and the time source selection is performed at a higher layer than PTP. The local time reference is configured as the primary reference; details of the selection criteria are for further study. + +The dTE network limits applicable at the reference points A and L are specified in clause 6.1 of [ITU-T G.8272]. + +## 7.2 Network limit at reference point B + +In the case of a telecom grandmaster (T-GM) integrated in the PRTC, the network limit applicable at reference point B is the same as the limit applicable at reference point A, measured as described in [ITU-T G.8272]. + +In the case of a T-GM external to the PRTC, the network limit applicable at reference point B is for further study. + +## 7.3 Network limits at reference point C + +The limits for both APTS and PTS below use the metric pktSelected2wayTE as described in clause I.4.4.1 of [ITU-T G.8260]. The specific method of calculation is the "percentile average packet selection method" as described in clause I.3.2.2 of [ITU-T G.8260]. The percentile value is defined in the limit definitions below as "selection percentage". The window size is defined in the limit definitions below as "selection window". + +NOTE 1 – Transient events such as packet loss and re-routes may not be indicated by the pktSelected2wayTE metric when the transient events are of short duration compared with the length of the selection window used to compute the metric. + +NOTE 2 – The network may be determined to be non-compliant with the network limit requirements when exceptional transient events occur during the selection window (e.g., exceptional transient events that give rise to packet timing signal fail). The exact criteria to define such exceptional transient events is for further study. For details on the measurement methodology in relation to exceptional events, refer to clause I.5.3 of [ITU-T G.8260] "Exceptional events and impact on packet network limit". + +### 7.3.1 Packet network limits for APTS + +The limits given in this clause represent the maximum permissible levels of phase/time error and noise at interfaces within a packet network in charge of distributing phase/time synchronization per the applications corresponding to the Class 4 listed in Table 1 of [ITU-T G.8271]. + +The limits applicable to other classes at the reference point C are for further study. + +Two types of network limit are defined. Type I places less stringent requirements on the dTE generated by the network, but requires a correspondingly higher performance from the clock, while type II places more stringent requirements on the dTE generated by the network with a lower performance clock. + +The limits given below shall be met for all operating conditions (except during PTP rearrangements), regardless of the amount of equipment preceding the interface. In general, these network limits are compatible with the minimum tolerance to time error and noise that all equipment input ports are required to provide. + +The network limit is defined in terms of the peak-to-peak value of pktSelected2wayTE (see Appendix I of [ITU-T G.8260]). + +Considering the peak-to-peak value of pktSelected2wayTE as the limit makes sure that whatever the instantaneous value of pktSelected2wayTE when the GNSS source is lost, the absolute TE will remain within expected limits (either positive or negative) while PTP is the selected fall-back source. + +Any transient associated with switching from the local time reference to PTP and back is for further study. + +NOTE – See Appendix III for considerations on maintaining time with frequency. + +#### 7.3.1.1 Type I network limit + +The network limit value and the metric processing parameters that apply for a type I network are as follows: + +- Peak-to-peak pktSelected2wayTE < 1100 ns +- Selection window = 200 s +- Selection percentage = 0.25% +- Selection method: percentile average packet selection (see clause I.3.2.2 of [ITU-T G.8260]) +- Window step size: $\leq 20$ s + +The network limit calculation method implies that the Sync and Delay\_req packet rate must be at least 2 packets/s, in order to receive a valid packet in every selection window. However, the network limit might only be met by using a packet rate higher than 2 packets/s. For proper operation, the T-TSC-A should use a packet rate that is at least as high as the packet rate required for the network limit to be satisfied. It is not expected that any T-TSC-A will meet the relevant target performance requirements at lower packet rates. The appropriate packet rate used by the clocks in the network depends on the clock characteristics and on the target performance requirements. + +#### 7.3.1.2 Type II network limit + +The network limit value and the metric processing parameters that apply for a type II network are for further study. + +### 7.3.2 Packet network limits for PTS + +The limits given in this clause represent the maximum permissible levels of phase/time error and noise, at interfaces within a packet network in charge of distributing phase/time synchronization per the applications corresponding to the Class 4 listing in Table 1 of [ITU-T G.8271]. + +The limits applicable to other classes at reference point C are for further study. + +Two types of network limit are defined. Type I places less stringent requirements on the dTE generated by the network, but requires a correspondingly higher performance from the clock, while type II places more stringent requirements on the dTE generated by the network with a lower performance clock. + +The limits given in clauses 7.3.2.1 and 7.3.2.2 shall be met for all operating conditions (except during PTP rearrangements), regardless of the amount of equipment preceding the interface. In general, these network limits are compatible with the minimum tolerance to time error and noise that all equipment input ports are required to provide. + +The network limit is defined in terms of the maximum absolute value of pktSelected2wayTE (max|pktSelected2wayTE|) (see Appendix I of [ITU-T G.8260]). + +#### 7.3.2.1 Type I network limit + +The network limit value and the metric processing parameters that apply for a type I network are as follows: + +- $\max|\text{pktSelected2wayTE}| < 1\,100\text{ ns}$ +- Selection window = 200 s +- Selection percentage = 0.25% +- Selection method: percentile average packet selection (see clause I.3.2.2 of [ITU-T G.8260]) +- Window step size: $\leq 20\text{ s}$ + +#### 7.3.2.2 Type II network limit + +The network limit value and the metric processing parameters that apply for a type II network are for further study. + +## 7.4 Network limit at reference point D + +### 7.4.1 Network limits for APTS + +The network limit applicable at point D is dependent on the end application limit at reference point E. For the case where the end application limit is 1500 ns, when the T-TSC-A is not locked to the local time reference, the maximum absolute time error at reference point D is: + +$$\max|\text{TE}_L| \leq 1350\text{ ns}$$ + +This requirement is only applicable in the case of a T-TSC-A external to the end application. + +When the T-TSC-A is locked to the local time reference, the requirement at reference point D is given by the combination of the local time reference error, and the T-TSC-A noise generation when locked to the local time reference. The value for this requirement is for further study. + +A first-order low-pass measurement filter with a bandwidth of 0.1 Hz is applied to the TE samples measured at the 1PPS timing interface prior to evaluating the $\max|\text{TE}|$ . + +### 7.4.2 Network limits for PTS + +The network limit applicable at point D is dependent on the end application limit at reference point E. For a case where the end application limit is 1500 ns, and the holdover is provided by the network, the maximum absolute time error at reference point D is: + +$$\max|\text{TE}_L| \leq 1350\text{ ns}$$ + +The other case, where the holdover is provided by the end application, is for further study. + +This requirement is only applicable in the case of a T-TSC-P external to the end application. + +A first-order low-pass measurement filter with a bandwidth of 0.1 Hz is applied to the TE samples measured at the 1PPS timing interface prior to evaluating the $\max|\text{TE}|$ . + +# Appendix I + +## Deployment scenarios for partial timing support networks + +(This appendix does not form an integral part of this Recommendation.) + +Clauses I.1 to I.6 illustrate some of the example deployment scenarios that could use the PTS and APTS architectures. It is expected that it will not be possible to meet strict timing requirements with all of these deployment scenarios. + +In this appendix, the following convention is used for describing network reference points: + +- Reference point A – output from the PRTC +- Reference point B – output from the T-GM or the PTP master port of an interworking function (IWF) +- Reference point C – input to the telecom time slave clock (T-TSC) or the PTP slave port of an IWF +- Reference point D – output from the T-TSC +- Reference point E – output from end application +- Reference point L – output from local time reference + +For networks comprising multiple segments, an additional number is allocated denoting the network segment, and a suffix to denote the type of network segment (e.g., FTS or PTS). + +It should be noted that depending on the equipment being used, reference points A and D are often internal to the equipment and may not always be accessible for measurement purposes. + +## I.1 APTS and PTS network use cases + +The first scenario, labelled deployment case 1a, represents an APTS network (see Figure I.1). The T-TSC-A has available a local time reference (e.g., a PRTC or GNSS-based time source). This is the primary time source for synchronization. The T-TSC-A uses the PTP timing packets from the PTS network as a secondary time or frequency source for synchronization in the case of failure of the local time reference. This scenario is the one documented in clause 7. + +In Figures I.1 and I.2 a T-BC-P is shown in the middle of the packet network between the T-GM and the T-TSC-A or T-TSC-P. This is optional, but may prove useful to reduce noise accumulation in the PTP timing flow. The use of the T-BC-P and its impact on the performance budget is for further study. + +Similarly, a T-BC-A may also be used in the packet network in deployment case 1A. Using a T-BC-A in place of the T-TSC-A, where the PTP output port connects to the end application, is for further study. + +![Figure I.1: Deployment case 1a (CPRI — common public radio interface) diagram. The diagram shows a sequence of components from left to right: PRTC/PRC (Reference point A), T-GM (Reference point B), Packet network, T-BC-P, Packet network, T-TSC-A (GNSS-assisted) (Reference point C), Distributed architecture (e.g., CPRI) (Reference point D), and End application (Reference point E). A Local time reference (e.g., GNSS) (Reference point L) is connected to the T-TSC-A. A bracket labeled 'Partial timing support network' spans from Reference point B to Reference point C.](66c2bf11a8f117cddf67eff92d4c736c_img.jpg) + +The diagram illustrates the deployment case 1a for CPRI. It shows a linear sequence of components: PRTC/PRC (Reference point A) connected to T-GM (Reference point B), which is connected to a Packet network, then T-BC-P, then another Packet network, then T-TSC-A (GNSS-assisted) (Reference point C). The T-TSC-A is connected to a Distributed architecture (e.g., CPRI) (Reference point D), which is connected to an End application (Reference point E). A Local time reference (e.g., GNSS) (Reference point L) is also connected to the T-TSC-A. A bracket labeled 'Partial timing support network' spans from Reference point B to Reference point C. + +Figure I.1: Deployment case 1a (CPRI — common public radio interface) diagram. The diagram shows a sequence of components from left to right: PRTC/PRC (Reference point A), T-GM (Reference point B), Packet network, T-BC-P, Packet network, T-TSC-A (GNSS-assisted) (Reference point C), Distributed architecture (e.g., CPRI) (Reference point D), and End application (Reference point E). A Local time reference (e.g., GNSS) (Reference point L) is connected to the T-TSC-A. A bracket labeled 'Partial timing support network' spans from Reference point B to Reference point C. + +Figure I.1 – Deployment case 1a (CPRI — common public radio interface) + +In some instances, the T-TSC-A and the local time reference may be integrated within the end application. In that case, the network limit for reference point C will apply at the input to the end application, and reference point D may not be externally accessible. + +The second scenario, labelled deployment case 1b, represents a PTS network (see Figure I.2). The operator's time source information is provided (at interface A) using a PRTC. The timing information is sent into the PTP domain using a T-GM (at interface B). The PTP domain operates according to the [ITU-T G.8275.2] telecom profile for time/phase synchronization and contains a packet network consisting of a limited number of PTP-unaware network elements (switches/routers) and T-BC-Ps. The PTP timing information is terminated (at interface C) by a T-TSC-P and the time information is connected to the end application (at interface D). + +![Figure I.2: Deployment case 1b (CPRI — common public radio interface). The diagram shows a sequence of components: PRTC at interface A, T-GM at interface B, a 'Partial timing support network' (consisting of a Packet network, T-BC-P, and another Packet network) ending at interface C, T-TSC-P at interface D, and an End application at interface E. The End application is part of a 'Distributed architecture (e.g., CPRI)'. Reference points A, B, C, D, and E are marked with vertical dashed lines. The text 'G.8271.2-Y.1366.2(21)_FI.2' is at the bottom right.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) + +Figure I.2: Deployment case 1b (CPRI — common public radio interface). The diagram shows a sequence of components: PRTC at interface A, T-GM at interface B, a 'Partial timing support network' (consisting of a Packet network, T-BC-P, and another Packet network) ending at interface C, T-TSC-P at interface D, and an End application at interface E. The End application is part of a 'Distributed architecture (e.g., CPRI)'. Reference points A, B, C, D, and E are marked with vertical dashed lines. The text 'G.8271.2-Y.1366.2(21)\_FI.2' is at the bottom right. + +**Figure I.2 – Deployment case 1b (CPRI — common public radio interface)** + +If the T-TSC-A is integrated within the end application, the network limit for reference point C will apply at the input to the end application, and reference point D may not be externally accessible. + +## I.2 Full timing support network followed by an APTS network or PTS network + +In some instances, a full timing support (FTS) network (refer to [ITU-T G.8271.1]) may be deployed after the T-GM (e.g., in the core or metro network) and a PTS network may be deployed closer to the end application (in the metro or access network). This multiple-segment network approach may be used with both the APTS and PTS architectures. + +The APTS case (deployment case 2a) is illustrated in Figure I.3. In this scenario, while the network limit at reference point C2P may be the same as at reference point C in scenario 1a, some time error budget must be allocated to the portion of the network that is FTS (between interface B1F and C1F). The allocation of budget to each of the network sections is for further study. + +An IWF, containing a clock among other functions, would be needed to translate from the FTS profile ([ITU-T G.8275.1]) to the PTS profile ([ITU-T G.8275.2]) going downstream from the T-GM towards the end application. This is denoted IWF F-P in Figure I.3 below. Refer to [ITU-T G.8275] Appendix III for more details on a generic IWF. + +![Figure I.3: Deployment case 2a (CPRI — common public radio interface). The diagram shows a sequence of components: PRTC, PRC at interface A, T-GM at interface B, 'Segment 1' (Full timing support network) between B1F and C1F, IWF F-P at interface C1F, 'Segment 2' (Partial timing support network) between B2P and C2P, T-TSC-A (GNSS-assisted) at interface D, and an End application at interface E. A 'Local time reference (e.g., GNSS)' is connected to the T-TSC-A at interface L. The End application is part of a 'Distributed architecture (e.g., CPRI)'. Reference points A, B, B1F, C1F, B2P, C2P, D, and E are marked with vertical dashed lines. The text 'G.8271.2-Y.1366.2(21)_FI.3' is at the bottom right.](a7c51c18111139f9aca2805114108565_img.jpg) + +Figure I.3: Deployment case 2a (CPRI — common public radio interface). The diagram shows a sequence of components: PRTC, PRC at interface A, T-GM at interface B, 'Segment 1' (Full timing support network) between B1F and C1F, IWF F-P at interface C1F, 'Segment 2' (Partial timing support network) between B2P and C2P, T-TSC-A (GNSS-assisted) at interface D, and an End application at interface E. A 'Local time reference (e.g., GNSS)' is connected to the T-TSC-A at interface L. The End application is part of a 'Distributed architecture (e.g., CPRI)'. Reference points A, B, B1F, C1F, B2P, C2P, D, and E are marked with vertical dashed lines. The text 'G.8271.2-Y.1366.2(21)\_FI.3' is at the bottom right. + +**Figure I.3 – Deployment case 2a (CPRI — common public radio interface)** + +As noted above, the T-TSC and local time reference may be integrated into the end application, in which case reference point C2p occurs at the input to the end application and reference point D may not be externally accessible. + +Likewise, this mixture of FTS networks and PTS networks may occur with a PTS network, as illustrated in deployment case 2b shown in Figure I.4. + +![Figure I.4 – Deployment case 2b (CPRI — common public radio interface). The diagram shows a sequence of network elements: PRTC, T-GM, Segment 1 (Full timing support network), IWF F-P, Segment 2 (Partial timing support network), T-TSC-P, and End application. Reference points A, B1_F, C1_F, B2_p, C2_p, D, and E are marked. A distributed architecture (e.g., CPRI) is shown between the T-TSC-P and the End application. The diagram is labeled G.8271.2-Y.1366.2(21)_FI.4.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +The diagram illustrates the signal flow for deployment case 2b. It starts with a PRTC connected to a T-GM. Segment 1, labeled 'Full timing support network', is between the T-GM and an IWF F-P, with reference points B1F and C1F. Segment 2, labeled 'Partial timing support network', is between the IWF F-P and a T-TSC-P, with reference points B2p and C2p. The T-TSC-P is connected to a 'Distributed architecture (e.g., CPRI)' which then connects to the 'End application'. Reference points A, D, and E are also indicated. The diagram is labeled G.8271.2-Y.1366.2(21)\_FI.4. + +Figure I.4 – Deployment case 2b (CPRI — common public radio interface). The diagram shows a sequence of network elements: PRTC, T-GM, Segment 1 (Full timing support network), IWF F-P, Segment 2 (Partial timing support network), T-TSC-P, and End application. Reference points A, B1\_F, C1\_F, B2\_p, C2\_p, D, and E are marked. A distributed architecture (e.g., CPRI) is shown between the T-TSC-P and the End application. The diagram is labeled G.8271.2-Y.1366.2(21)\_FI.4. + +**Figure I.4 – Deployment case 2b (CPRI — common public radio interface)** + +NOTE – In both Figures I.3 and I.4 above, an optional T-BC-P clock may be present within the PTS network segment, similar to that shown in Figures I.1 and I.2. This is not shown in the diagrams for simplicity. + +## I.3 PTS network followed by an FTS network + +In some instances, a PTS network may be deployed after the T-GM (for example in the core or metro network) and an FTS network may be deployed closer to the end application (in the metro network, access network or radio access network (RAN) for the cases where the RAN is split based on different functions). The network limits and time error budgets associated with each section of the network are for further study. + +An interworking function (IWF P-F), containing a clock among other functions, would be needed to translate from the PTS profile ([ITU-T G.8275.2]) to the FTS profile ([ITU-T G.8275.1]) going downstream from the T-GM towards the end application. This should be denoted IWF P-F. Refer to [ITU-T G.8275] Appendix III for more details on a generic IWF. + +## I.4 APTS network followed by a PTS network + +In some instances, an APTS network may be deployed after the T-GM (e.g., in the core or metro network), with a small section using PTS closer to the end application (in the access or last-mile network). A T-BC-P assisted by a local time reference (e.g., a PRTC or GNSS time source) would be required between the two network segments. + +In this scenario, some time error budget must be allocated to the portion of the network following the time-assisted network element. The network limits and time error budgets associated with each section of the network are for further study. + +## I.5 APTS network followed by an FTS network + +In some instances, an APTS network may be deployed after the T-GM (for example in the core or metro network) and an FTS network may be deployed closer to the end application (in the metro network, access network, or RAN for the cases where the RAN is split based on different functions). + +For example, as shown in Figure I.5, an interworking function (IWF P-F), containing a clock among other functions, is deployed close to the edge of the network and provides synchronization to an access segment of the network with FTS. The IWF P-F has a local time reference (e.g., a PRTC or GNSS-based time source) that is used as the primary synchronization source for the FTS network. Additionally, the IWF P-F has a secondary synchronization source from the PTS network that may be used by the IWF P-F according to the APTS scheme. The IWF P-F would need to translate from the PTS profile + +([ITU-T G.8275.2]) to the FTS profile ([ITU-T G.8275.1]) going downstream from the T-GM towards the end application. + +![Figure I.5: APTS network followed by a full timing support network (CPRI — common public radio interface).](c85ded401105f62f2d6ff26b3b5eb4af_img.jpg) + +The diagram illustrates a timing distribution path. It starts with a PRTC/PRC connected to a T-GM at point A. A 'Local time reference (e.g., GNSS)' is connected to an IWF P-F (GNSS-assisted) block at point L. The path consists of Segment 1 (from B1p to C1p), which is a 'Partial timing support network', and Segment 2 (from B2F to C2F), which is a 'Full timing support network'. The IWF P-F block is located between these two segments. The path continues from the IWF P-F through Segment 2 to a T-TSC at point D. From the T-TSC, the path goes through a 'Distributed architecture (e.g., CPRI)' to an 'End application' at point E. The diagram is labeled G.8271.2-Y.1366.2(21)\_FI.5. + +Figure I.5: APTS network followed by a full timing support network (CPRI — common public radio interface). + +**Figure I.5 – APTS network followed by a full timing support network (CPRI — common public radio interface)** + +The network limits and time error budgets associated with each section of the network are for further study, but the noise accumulation over all the segments up to point C2F, including the IWFs, should stay within the overall network limit defined for reference point C in clause 7.3. + +The time error budget allocated to the FTS network (between reference points B2F and C2F in Figure I.5 above) is expected to be relatively small, in order to not significantly reduce the time error budget allocated to the PTS segment, while also allowing a few (e.g., 2 to 3) PTP-aware network elements to be present in the FTS segment. An FTS time error budget of the order of 200 ns (in terms of max|TE| between reference points B2F and C2F) could address several use cases of interest. For further information on how to meet this budget refer to Appendix V in [ITU-T G.8271.1]. + +## I.6 Use of PTS network to bridge between two FTS networks + +In some circumstances, an operator deploying an FTS architecture has to connect two network segments over a PTP-unaware network segment owned or operated by a third party operator. In this case, it may be necessary to use PTS across the third party network. The network limits and time error budgets associated with each section of the network are for further study. + +Figure I.6 illustrates the concept. An interworking function (IWF F-P), containing a clock among other functions, is needed to translate from the FTS profile ([ITU-T G.8275.1]) to the PTS profile ([ITU-T G.8275.2]) going downstream from the T-GM towards the end application. + +A second interworking function (IWF P-F), containing a clock among other functions, is needed to translate from the PTS profile ([ITU-T G.8275.2]) back to the FTS profile ([ITU-T G.8275.1]) going downstream from the T-GM towards the end application. + +![Figure I.6: Bridging across a PTS network (CPRI — common public radio interface).](29f586959675cafdf81cf934954908eb_img.jpg) + +The diagram illustrates a timing distribution path across three segments. It starts with a PRTC/PRC connected to a T-GM at point A. Segment 1 (from B1F to C1F) is an 'FTS network'. Segment 2 (from B2p to C2p) is a 'PTS network' and is labeled as a 'Bridging segment'. Segment 3 (from B3F to C3F) is an 'FTS network'. The path consists of an IWF F-P block between Segment 1 and Segment 2, and an IWF P-F block between Segment 2 and Segment 3. The path continues from the IWF P-F through Segment 3 to a T-TSC at point D. From the T-TSC, the path goes through a 'Distributed architecture (e.g., CPRI)' to an 'End application' at point E. The diagram is labeled G.8271.2-Y.1366.2(21)\_FI.6. + +Figure I.6: Bridging across a PTS network (CPRI — common public radio interface). + +**Figure I.6 – Bridging across a PTS network (CPRI — common public radio interface)** + +# Appendix II + +## Considerations for handling precision time protocol traffic in networks with partial timing support + +(This appendix does not form an integral part of this Recommendation.) + +In order to meet the stringent network limits specified in this Recommendation, careful planning is needed in order to control the PDV and delay asymmetry generated by the network. Such a controlled network would typically be a small-scale, local network (e.g., in-building or "last-mile" network segments, such as might be used for the connection of small cells). + +These guidelines are related to meeting the network limit of 1.1 $\mu\text{s}$ at reference point C. This is necessary to meet the end application requirement of a maximum absolute time error of 1.5 $\mu\text{s}$ (Class 4 in [ITU-T G.8271], Table 1). In cases where the end application requirements are less stringent (e.g., Class 2), the requirements on the network PDV and asymmetry are more relaxed. The details are for further study. + +## II.1 Network aspects + +The following aspects should be considered. + +- 1) The asymmetry and PDV generated by the network elements under applicable conditions should be characterized and validated. Such conditions should include: + - a) dynamic traffic load and frame lengths; + - b) network congestion; + - c) link failure and restoration; + - d) network element power cycle; + - e) network reroute of PTP packets. +- 2) It is recommended that PTP messages be assigned to a high quality of service in order to reduce the PDV created by other data carried over the network. However, it should be noted that even if PTP messages use the highest quality of service, they may not avoid all PDV due to effects including head of line blocking, queuing architectures and others. The details are described in Appendix I of [b-ITU-T G.8261]. +- 3) The link technology should not create excessive asymmetry or PDV. +- 4) Where possible, interface rate changes should be signalled by use of the INTERFACE\_RATE type length variable (TLV) defined in Annex D of [ITU-T G.8275.2]. This allows the delay asymmetry caused by the rate change to be compensated for. If the equipment does not support the INTERFACE\_RATE TLV, the effect of the asymmetry must be carefully considered. +- 5) The use of boundary clocks at key locations may be useful to reduce the accumulation of PDV. For example, a new network element containing a boundary clock between the PTP master and PTP slave(s) may be added. This is for further study. +- 6) The replacement of existing PTP-unaware network elements with network elements containing boundary clocks or transparent clocks would reduce the internal asymmetry and PDV introduced by the replaced network element, and additionally the boundary clock may be useful to reduce the overall accumulation of PDV. + +The network should be based on a very small number of PTP-unaware network elements. The number is strongly related to the specific network equipment, the transport technology and the management and control of the traffic load in the network. It should be noted that not all switching and routing technology is the same, and this can affect the level of PDV and delay asymmetry produced. Switches and routers + +have their own specific characteristics depending on their internal implementation. Some more complex network elements generate higher levels of PDV and asymmetry than smaller ones. + +Some trials have reported successful operation over three to five PTP-unaware network elements where the traffic load and asymmetry were well-controlled; other trials have reported poor performance even over one PTP-unaware network element. Depending on the specific characteristics of the network elements used, and the traffic load within the network, the network may not support time or phase synchronization using PTS. + +In addition, conditions in a network may change over time, e.g., as traffic load changes or as network asymmetry changes (this may occur in some technologies such as the optical transport network). Therefore one single measurement is not sufficient to fully characterize a network. Network monitoring is recommended to ensure the network limits are consistently met. + +## **II.2 Time error performance aspects** + +For APTS networks, it is the dTE created by the PDV in the network that is of interest. The cTE created by delay asymmetry in the network should be sufficiently stable, relative to the required performance. If this is met, the local time reference of the T-TSC-A may be used to compensate for the asymmetry created by the network. Compensation may be achieved by either: + +- 1) measuring the delay asymmetry while the local time reference is in operation, such that it is known in advance if the local time reference fails; +- 2) setting the correct time while the local time reference is in operation, and using the PTP flow as a source of frequency to maintain the time base when the local time reference is out of service. + +For PTS networks, the full time error created by the network is important, including both the cTE and dTE components. This is because there is no local time reference to compensate for the network delay asymmetry. + +# Appendix III + +## The use of frequency to maintain precise time + +(This appendix does not form an integral part of this Recommendation.) + +Frequency, which can be used to hold precise time, can be derived from PTP. Further, in the case of PTP derived frequency, it is possible to derive frequency using packets from a single direction. Thus, for frequency from PTP, three approaches are possible: + +- 1) use of the forward sequence; +- 2) use of the reverse sequence; +- 3) use of both the forward and reverse sequences together. + +In cases where one of the two sequences shows much less PDV than the other, focus on that sequence rather than on both is warranted. Such a situation is illustrated in Figure III.1. + +The limits for APTS are based on a peak-to-peak value of pktSelected2WayTE. In Appendix I of [ITU-T G.8260], the pktSelected2WayTE, expressed as $x_c'(t)$ , is described by Figure III.1. + +![Figure III.1 – Packet Selection. A block diagram showing two input sequences, x_F(t) and x_R(t), entering separate 'Packet selection' blocks. The outputs of these blocks, x_F'(t) and x_R'(t), are then combined in a 'Combination' block to produce the final output x_c'(t).](e636d7ccca0ad14c6b95201404324823_img.jpg) + +``` + +graph LR + xF["x_F(t)"] --> PS1["Packet selection"] + xR["x_R(t)"] --> PS2["Packet selection"] + PS1 --> xFp["x_F'(t)"] + PS2 --> xRp["x_R'(t)"] + xFp --> C["Combination"] + xRp --> C + C --> xcp["x_c'(t)"] + +``` + +G.8271.2-Y.1366.2(17)\_FIII.1 + +Figure III.1 – Packet Selection. A block diagram showing two input sequences, x\_F(t) and x\_R(t), entering separate 'Packet selection' blocks. The outputs of these blocks, x\_F'(t) and x\_R'(t), are then combined in a 'Combination' block to produce the final output x\_c'(t). + +**Figure III.1 – Packet Selection** + +Note that the packet selection is done independently on each one-way sequence with the results combined in each selection window. Thus the forward and reverse sequences are *both* constrained at the same time for each window. + +For APTS, time is normally supplied by GNSS, and in the event of GNSS loss turns to PTP to provide or hold time. Time can be maintained by stable frequency, particularly over short periods of time such as small multiples of the 100 s or 200 s selection windows described above. The source of stable frequency might be an internal oscillator in the APTS clock, a traceable frequency input such as from SyncE, or a frequency derived from PTP. + +The ability of a local oscillator to hold time is illustrated in Table III.1. + +**Table III.1 – Local oscillator types and phase drift** + +| | 10 ns | 50 ns | 100 ns | 500 ns | 1 μs | +|--------------------|----------|----------|-----------|-----------|-----------| +| ITU-T G.812 Type 1 | 0.22 h | 0.50 h | 0.70 h | 1.57 h | 2.22 h | +| ITU-T G.812 Type 2 | 1.15 h | 2.58 h | 3.65 h | 8.16 h | 11.55 h | +| ITU-T G.812 Type 4 | 0.11 h | 0.24 h | 0.33 h | 0.75 h | 1.05 h | +| ITU-T G.812 Type 4 | 1.11 min | 2.48 min | 3.51 min | 7.84 min | 11.09 min | +| ITU-T G.812 Type 5 | 0.30 h | 0.67 h | 0.94 h | 2.11 h | 2.98 h | +| ITU-T G.812 Type 6 | 4.00 min | 8.94 min | 12.65 min | 28.28 min | 40.00 min | +| ITU-T Opt 1 | 0.49 min | 1.10 min | 1.55 min | 3.46 min | 4.90 min | +| ITU-T Opt 2 | 0.32 min | 0.72 min | 1.02 min | 2.28 min | 3.23 min | + +The ability of a traceable frequency to hold time is illustrated in Table III.2. + +**Table III.2 – Traceable frequency phase drift** + +| | 10 ns | 50 ns | 100 ns | 1 µs | 10 µs | +|---------------------|----------|--------|--------|-----------|------------| +| Caesium (1E-12) | 2.8 h | 13.9 h | 27.8 h | 11.6 days | 115.7 days | +| ITU-T G.811 (1E-11) | 16.7 min | 1.4 h | 2.8 h | 1.2 days | 11.6 days | + +In the case of frequency derived from PTP, there are fairly common situations where stable frequency can be easily attained from PTP, though precise time is attained with greater difficulty. Such a situation is exemplified by Figure III.2, where blue shows the forward packet sequence and red shows the reverse packet sequence. + +![Figure III.2: A plot showing forward (blue) and reverse (red) packet sequences over time. The y-axis represents phase in usec, ranging from 0.00 to 55.0 usec, with a scale of 5.00 usec/div. The x-axis represents time in hours, ranging from 0.000 to 10.36 hours, with a scale of 1.00 hours/div. The blue sequence shows significant phase jitter, while the red sequence is relatively stable.](79cb7fa0e9c78ec5cd0b0de977824f8d_img.jpg) + +Two-Way Fwd/Rev PDV phase Pct Avg; Samples: 3730; Tau: 9.99998 s; A = 160; N = 3730; F = 2 + +55.0 usec + +5.00 usec/div + +0.00 sec + +0.000 hours + +1.00 hours/div + +10.36 hours + +G.8271.2-Y.1366.2(17)\_FIII.2 + +Figure III.2: A plot showing forward (blue) and reverse (red) packet sequences over time. The y-axis represents phase in usec, ranging from 0.00 to 55.0 usec, with a scale of 5.00 usec/div. The x-axis represents time in hours, ranging from 0.000 to 10.36 hours, with a scale of 1.00 hours/div. The blue sequence shows significant phase jitter, while the red sequence is relatively stable. + +**Figure III.2 – Examples of forward and reverse packet sequences** + +In this case, focusing on the reverse packets would yield a better frequency result. + +Further, there are times when the forward sequence is advantageous for holding time and other times, perhaps just a short time later, when the reverse sequence is advantageous for holding time. Perhaps in a series of 10 selection windows, 1-3 are better for forward, 4-7 better for reverse and 8-10 better for forward. + +Thus, while the limit based on peak-to-peak pktSelected2WayTE can suitably guarantee the presence of network conditions for APTS devices to deliver proper synchronization, a single one-way sequence can provide a stable frequency that can be used to assist in holding precise time. + +# Appendix IV + +## Noise accumulation model in partially aware networks + +(This appendix does not form an integral part of this Recommendation.) + +A partially aware network may contain several PTS clocks before the synchronization reaches the end application. Such a situation is illustrated in Figure IV.1, where there is one T-BC-P and one T-TSC-P in the synchronization chain. The accumulated time error accumulation is a function of the network PDV (as expressed in the metric $\max|\text{pktSelected2wayTE}|$ ), the transfer function of the PTS clock (expressed in terms of "gain peaking"), and the noise generation of the PTS clock. + +In the example below, the time error on the PTP input interface at point P2 is X ns, as expressed using the $\max|\text{pktSelected2wayTE}|$ metric. The time error on the output from the T-BC-P at point P3 is $(X + \text{Gain} + \text{Generation})$ , as expressed using $\max|\text{TE}|$ . + +![Figure IV.1: Example network showing noise accumulation model. The diagram shows a synchronization chain: T-GM (P1) -> Packet network -> P2 (input to T-BC-P) -> T-BC-P (P3 output) -> Packet network -> P4 (input to T-TSC-P) -> T-TSC-P (P5 output) -> End application. Annotations show time error accumulation at each point.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +The diagram illustrates a synchronization chain with the following components and points: + +- T-GM** (P1): The starting point of the synchronization chain. +- Packet network**: A network segment between T-GM and T-BC-P. +- P2**: The input interface of the T-BC-P. The time error here is $\max|\text{pktSelected2wayTE}| = X$ . +- T-BC-P**: A Transparent Boundary Clock (P). Its output interface is **P3**. The time error at P3 is $\max|\text{TE}| = X + \text{Gain} + \text{Generation}$ . +- Packet network**: A network segment between T-BC-P and T-TSC-P. +- P4**: The input interface of the T-TSC-P. The time error here is $\max|\text{pktSelected2wayTE}| = Y$ . +- T-TSC-P**: A Transparent Time Synchronization Clock (P). Its output interface is **P5**. The time error at P5 is $\max|\text{TE}| = Y + \text{Gain} + \text{Generation}$ . +- End application**: The final destination of the synchronization chain. + +Reference: G.8271.2-Y.1366.2(17)-Amd.2(18)\_FIV.1 + +Figure IV.1: Example network showing noise accumulation model. The diagram shows a synchronization chain: T-GM (P1) -> Packet network -> P2 (input to T-BC-P) -> T-BC-P (P3 output) -> Packet network -> P4 (input to T-TSC-P) -> T-TSC-P (P5 output) -> End application. Annotations show time error accumulation at each point. + +**Figure IV.1 – Example network showing noise accumulation model** + +The way these different parameters combine is for further study. + +Note that while this example shows the network limit using $\text{pktSelected2wayTE}$ , an implementation of a T-BC-P or T-TSC-P may use any number of design (selection, filtering) techniques not related to the network limit metric. Implementations may achieve better performance than shown in the example. + +# Bibliography + +[b-ITU-T G.8261] Recommendation ITU-T G.8261/Y.1361 (2020), *Timing and synchronization aspects in packet networks*. + + + +# 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.8272-202507-I_PDF-E/raw.md b/marked/G/T-REC-G.8272-202507-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9c104567b92c8228b698d8600d26e7016bc3bc65 --- /dev/null +++ b/marked/G/T-REC-G.8272-202507-I_PDF-E/raw.md @@ -0,0 +1,769 @@ + + +# Recommendation + +## **ITU-T G.8272 (07/2025)** + +SERIES G: Transmission systems and media, digital systems and networks + +Packet over Transport aspects – Synchronization, quality and availability targets + +## --- **Timing characteristics of primary reference time clocks** + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +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 | +| 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.8272 + +## Timing characteristics of primary reference time clocks + +## Summary + +Recommendation ITU-T G.8272 specifies the requirements for primary reference time clocks (PRTC) suitable for time, phase and frequency synchronization in packet networks. It defines the error allowed at the time output of the PRTC. These requirements apply under the normal environmental conditions specified for the equipment. + +This edition of the Recommendation provides the following updates: + +- Changed "time standard" to "time scale" and clarified the use of UTC. +- Replaced the term "calibration" with the more appropriate term "compensation". +- Modification to scope. +- New text added under clause 7 "Holdover". +- Modifications to Appendix III. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|-----------------------------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.8272/Y.1367 | 2012-10-29 | 15 | 11.1002/1000/11817 | +| 1.1 | ITU-T G.8272/Y.1367 (2012) Amd. 1 | 2013-08-29 | 15 | 11.1002/1000/12013 | +| 2.0 | ITU-T G.8272/Y.1367 | 2015-01-13 | 15 | 11.1002/1000/12393 | +| 2.1 | ITU-T G.8272/Y.1367 (2015) Amd. 1 | 2016-04-13 | 15 | 11.1002/1000/12813 | +| 3.0 | ITU-T G.8272/Y.1367 | 2018-11-29 | 15 | 11.1002/1000/13769 | +| 3.1 | ITU-T G.8272/Y.1367 (2018) Amd. 1 | 2020-03-15 | 15 | 11.1002/1000/14211 | +| 3.2 | ITU-T G.8272/Y.1367 (2018) Amd. 2 | 2022-11-13 | 15 | 11.1002/1000/15152 | +| 4.0 | ITU-T G.8272 | 2025-07-22 | 15 | 11.1002/1000/16379 | + +## Keywords + +PRTC, synchronization, time error, wander. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Time error, wander and jitter in locked mode ..... | 3 | +| 6.1 Time error in locked mode ..... | 3 | +| 6.2 Wander in locked mode..... | 4 | +| 6.3 Jitter ..... | 6 | +| 7 Holdover ..... | 6 | +| 8 Phase discontinuity ..... | 6 | +| 9 Interfaces..... | 6 | +| 9.1 Phase and time interfaces ..... | 7 | +| 9.2 Frequency interfaces..... | 7 | +| Appendix I – Measuring the performance of a PRTC or a PRTC combined with T-GM ..... | 9 | +| I.1 Factors influencing the performance of a GNSS-based PRTC ..... | 9 | +| I.2 Phase wander measurement..... | 10 | +| I.3 Time error measurements ..... | 11 | +| Appendix II – PRTC functional model ..... | 16 | +| Appendix III – Information exchanged over the time interface..... | 18 | +| Appendix IV – PRTC locations ..... | 19 | +| Bibliography..... | 21 | + + + +# Recommendation ITU-T G.8272 + +## Timing characteristics of primary reference time clocks + +# 1 Scope + +This Recommendation specifies the requirements for primary reference time clocks (PRTC) suitable for time, phase and frequency synchronization in packet networks. These requirements apply under the normal environmental conditions specified for the equipment. + +A typical PRTC provides the reference signal for time, phase and frequency synchronization for other clocks within a network or section of a network. In particular, the PRTC can also provide the reference signal to the telecom grandmaster (T-GM) within the network nodes where the PRTC is located. + +The PRTC provides a reference time signal traceable to a recognized timescale. + +NOTE – Mobile communication networks in time division duplex (TDD) mode need to be synchronized to the same time scale for the case that the TDD area is not isolated. For details, see Appendix VI of [ITU-T G.8271]. UTC is an appropriate solution, and is available and accessible worldwide. For details, see [bWRC-23 Res.655] and [b-ITU-R TF.486-2]. + +This Recommendation defines the PRTC output requirements. The accuracy of the PRTC should be maintained as specified in this Recommendation. + +This Recommendation also covers the case where a PRTC is integrated with a T-GM clock. In this case it defines the performance at the output of the combined PRTC and T-GM function, i.e., the precision time protocol (PTP) messages. + +This Recommendation defines two types of PRTCs, PRTC-A and PRTC-B. The time output of a PRTC-B is more accurate than that of a PRTC-A, and is therefore appropriate for applications where more accurate absolute time is required. In order to facilitate conformance to the relevant requirements, the PRTC-B is suitable for locations where it is possible to guarantee optimized environmental conditions (e.g., controlled temperature variation in indoor deployments). Typical examples are central location and large aggregation sites. However, this does not preclude other applications. + +# 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.703] Recommendation ITU-T G.703 (2016), *Physical/electrical characteristics of hierarchical digital interfaces*. +- [ITU-T G.810] Recommendation ITU-T G.810 (1996), *Definitions and terminology for synchronization networks*. +- [ITU-T G.811] Recommendation ITU-T G.811 (1997), *Timing characteristics of primary reference clocks*. +- [ITU-T G.812] Recommendation ITU-T G.812 (2004), *Timing requirements of slave clocks suitable for use as node clocks in synchronization networks*. + +- [ITU-T G.8260] Recommendation ITU-T G.8260 (2022), *Definitions and terminology for synchronization in packet networks*. +- [ITU-T G.8271] Recommendation ITU-T G.8271/Y.1366 (2020), *Time and phase synchronization aspects of telecommunication networks*. +- [IEEE 1588-2008] IEEE Std 1588-2008, *Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems*. +- [IEEE 1588-2019] IEEE 1588-2019, *IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +Definitions related to synchronization are contained in [ITU-T G.810] and [ITU-T G.8260]. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|------------------------------------| +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| MTIE | Maximum Time Interval Error | +| PRC | Primary Reference Clock | +| PRTC | Primary Reference Time Clock | +| PTP | Precision Time Protocol | +| RF | Radio Frequency | +| SSU | Synchronization Supply Unit | +| TDEV | Time Deviation | +| T-GM | Telecom Grand Master | +| ToD | Time of Day | +| UTC | Coordinated Universal Time | + +# 5 Conventions + +Within this Recommendation, the following conventions are used: + +The term "UTC time signal source" refers to the physical realizations of UTC that are based on UTC(k) (e.g., extracted from GNSS signals). See [ITU-T G.8260] for details on physical realizations of UTC. + +UTC(k) is the reference time scale realized in timing institutes (metrology and research institutes) which approximates UTC (see [ITU-T G.8260]). + +# 6 Time error, wander and jitter in locked mode + +The noise generation of a primary reference time clock (PRTC) is characterized by two main aspects: + +- the constant time error (time offset) at its output compared to a UTC time signal source; +- the amount of phase error (wander and jitter) produced at its output. + +For characterization of the second aspect described above (phase error) the calculation of the maximum time interval error (MTIE) and the time deviation (TDEV) is useful. + +Clause 6.1 defines the time error requirements applicable at the output of the PRTC, which corresponds to the combination of the two aspects described above (constant time error and phase error). No requirement is defined for the constant time error component taken alone; it is combined with the phase error and not separately measurable. + +Clauses 6.2 and 6.3 define the wander and jitter requirements applicable at the output of the PRTC, which correspond to the second aspect described above (phase error). + +The performance specified in clauses 6.1 and 6.2, also applies to the output of the combined PRTC and T-GM function when integrated into a single piece of equipment. Therefore, for both the PRTC-A and PRTC-B, there is no additional allowance for the inclusion of the T-GM function. The overall performance where the PRTC-B and T-GM are in separate pieces of equipment is outside the scope of this Recommendation. + +NOTE – Optimization of the noise inside the equipment is possible by combining the two functions. + +## 6.1 Time error in locked mode + +Under normal, locked operating conditions, the time output of the PRTC-A, or the combined PRTC-A and T-GM function, should be accurate to within 100 ns or better when verified against the applicable UTC time signal source. For the PRTC-A this value includes all the noise components, i.e., the constant time error (time offset) and the phase error (wander and jitter) of the PRTC-A. For the combined PRTC-A and T-GM function, time error samples are measured through a moving-average low-pass filter of at least 100 consecutive time error samples. This filter is applied by the test equipment to remove errors caused by timestamp quantization, or any quantization of packet position in the test equipment, before calculating the maximum time error. + +Under normal, locked operating conditions, the time output of the PRTC-B, or the combined PRTC-B and T-GM function, should be accurate to within 40 ns or better when verified against the applicable UTC time signal source. For the PRTC-B this value includes all the noise components, i.e., the constant time error (time offset) and the phase error (wander and jitter) of the PRTC-B. For the combined PRTC-B and T-GM function the time error samples are measured through a moving-average low-pass filter of at least 100 consecutive time error samples. This filter is applied by the test equipment to remove errors caused by timestamp quantization, or any quantization of packet position in the test equipment, before calculating the maximum time error. + +Normal, locked operating conditions mean that: + +- The PRTC is fully locked to the incoming reference time signal, and is not operating in warm-up; +- There are no failures or facility errors in the reference path, including but not limited to antenna failures; +- The environmental conditions are within the operating limits specified for the equipment; +- The equipment is properly commissioned and compensated for fixed offsets such as antenna cable length, cable amplifiers and receiver delays; +- The reference time signal (e.g., GNSS signal) is operating within limits, as determined by the relevant operating authorities; + +- If the reference time signal is operated over a radio system such as a GNSS, multipath reflections and interference from other local transmissions, such as jamming, must be minimized to an acceptable level; +- There are no extreme propagation anomalies, such as severe thunderstorms or solar flares; +- There may be GNSS constellation switching events, which need to be accommodated if this is required to meet the target performance. + +## 6.2 Wander in locked mode + +When the PRTC is in the normal, locked mode of operation, the wander, expressed in MTIE, measured using a similar configuration as the synchronized clock configuration defined in Figure 1a of [ITU-T G.810] (with the use of a time standard instead of a frequency standard), should have the following limits: + +**Table 1 – Wander generation (MTIE) for PRTC-A** + +| MTIE limit [ $\mu\text{s}$ ] | Observation interval $\tau$ [s] | +|------------------------------------|---------------------------------| +| $0.275 \times 10^{-3}\tau + 0.025$ | $0.1 < \tau \leq 273$ | +| 0.10 | $\tau > 273$ | + +**Table 2 – Wander generation (MTIE) for PRTC-B** + +| MTIE limit [ $\mu\text{s}$ ] | Observation interval $\tau$ [s] | +|------------------------------------|---------------------------------| +| $0.275 \times 10^{-3}\tau + 0.025$ | $0.1 < \tau \leq 54.5$ | +| 0.04 | $\tau > 54.5$ | + +The resultant requirements are shown in Figure 1. + +![Figure 1: MTIE as a function of an observation (integration) period. The graph shows two curves, PRTC-A and PRTC-B, on a log-log scale. The y-axis is MTIE in seconds (10ns to 1us) and the x-axis is observation interval tau in seconds (0.1 to 100M). PRTC-A starts at 0.025 us for 0.1s, rises to 100ns at 54.5s, and stays at 100ns. PRTC-B starts at 0.025 us for 0.1s, rises to 40ns at 54.5s, and stays at 40ns.](df476ed6ad0bb890c67aa63e7647d071_img.jpg) + +The graph plots MTIE (y-axis, logarithmic scale from 10ns to 1 $\mu\text{s}$ ) against observation interval $\tau$ (x-axis, logarithmic scale from 0.1 to 100M seconds). Two curves are shown: PRTC-A and PRTC-B. Both curves start at an MTIE of $0.025 \mu\text{s}$ for $\tau = 0.1 \text{ s}$ . PRTC-A increases linearly on the log-log plot until it reaches $100 \text{ ns}$ at $\tau = 54.5 \text{ s}$ , then remains constant at $100 \text{ ns}$ . PRTC-B increases linearly until it reaches $40 \text{ ns}$ at $\tau = 54.5 \text{ s}$ , then remains constant at $40 \text{ ns}$ . A vertical dashed line at $\tau = 54.5 \text{ s}$ marks the transition point for both curves. + +Figure 1: MTIE as a function of an observation (integration) period. The graph shows two curves, PRTC-A and PRTC-B, on a log-log scale. The y-axis is MTIE in seconds (10ns to 1us) and the x-axis is observation interval tau in seconds (0.1 to 100M). PRTC-A starts at 0.025 us for 0.1s, rises to 100ns at 54.5s, and stays at 100ns. PRTC-B starts at 0.025 us for 0.1s, rises to 40ns at 54.5s, and stays at 40ns. + +**Figure 1 – MTIE as a function of an observation (integration) period** + +NOTE 1 – For the 1 pulse-per-second (1PPS) output interface, the MTIE is applicable above a 1 second observation period. + +When the PRTC is in the normal, locked mode of operation, the wander, expressed in TDEV, measured using a similar configuration as the synchronized clock configuration defined in Figure 1a of [ITU-T G.810] (with the use of a time standard instead of a frequency standard), should have the following limits: + +**Table 3 – Wander generation (TDEV) for PRTC-A** + +| TDEV limit [ns] | Observation interval $\tau$ [s] | +|-----------------|---------------------------------| +| 3 | $0.1 < \tau \leq 100$ | +| $0.03 \tau$ | $100 < \tau \leq 1\,000$ | +| 30 | $1\,000 < \tau < 10\,000$ | + +**Table 4 – Wander generation (TDEV) for PRTC-B** + +| TDEV limit [ns] | Observation interval $\tau$ [s] | +|-----------------|---------------------------------| +| 1 | $0.1 < \tau \leq 100$ | +| $0.01 \tau$ | $100 < \tau \leq 500$ | +| 5 | $500 < \tau < 100\,000$ | + +The resultant requirements are shown in Figure 2. + +![Figure 2: TDEV as a function of an observation (integration) period. The graph shows two curves, PRTC-A and PRTC-B, on a log-log scale. The y-axis is TDEV in seconds (100ns to 100ps) and the x-axis is observation interval tau in seconds (0.1 to 100K). PRTC-A has a limit of 3 ns for 0.1 < tau <= 100 s, then increases linearly to 30 ns at 1000 s, and remains constant at 30 ns for 1000 < tau < 10000 s. PRTC-B has a limit of 1 ns for 0.1 < tau <= 100 s, then increases linearly to 5 ns at 500 s, and remains constant at 5 ns for 500 < tau < 100000 s.](b712e7522f1bb7135730c7d1abb46d43_img.jpg) + +Figure 2 is a log-log plot showing the Time Deviation (TDEV) as a function of the observation (integration) period $\tau$ in seconds. The y-axis represents TDEV in seconds, ranging from 100ps to 100ns. The x-axis represents $\tau$ in seconds, ranging from 0.1 to 100K. Two curves are plotted: PRTC-A and PRTC-B. PRTC-A shows a constant TDEV of 3 ns for $0.1 < \tau \leq 100$ s, then increases linearly to 30 ns at $\tau = 1\,000$ s, and remains constant at 30 ns for $1\,000 < \tau < 10\,000$ s. PRTC-B shows a constant TDEV of 1 ns for $0.1 < \tau \leq 100$ s, then increases linearly to 5 ns at $\tau = 500$ s, and remains constant at 5 ns for $500 < \tau < 100\,000$ s. + +Figure 2: TDEV as a function of an observation (integration) period. The graph shows two curves, PRTC-A and PRTC-B, on a log-log scale. The y-axis is TDEV in seconds (100ns to 100ps) and the x-axis is observation interval tau in seconds (0.1 to 100K). PRTC-A has a limit of 3 ns for 0.1 < tau <= 100 s, then increases linearly to 30 ns at 1000 s, and remains constant at 30 ns for 1000 < tau < 10000 s. PRTC-B has a limit of 1 ns for 0.1 < tau <= 100 s, then increases linearly to 5 ns at 500 s, and remains constant at 5 ns for 500 < tau < 100000 s. + +**Figure 2 – TDEV as a function of an observation (integration) period** + +NOTE 2 – For the 1PPS output interface, the TDEV is applicable above a 1 second observation period. + +The applicable MTIE and TDEV requirements for 1PPS output interfaces are based on the time interval error of the 1PPS signal taken at one sample per second and without any low-pass filtering. + +The applicable MTIE and TDEV requirements for 2 048 kHz, 2 048 kbit/s and 1 544 kbit/s output interfaces are measured through an equivalent 10 Hz, first-order, low-pass measurement filter, at a maximum sampling time $\tau_0$ of 1/30 seconds. + +The applicable MTIE and TDEV requirements for an Ethernet interface carrying PTP [IEEE 1588-2008] or [IEEE 1588-2019] messages are measured through a moving-average low-pass filter of at least 100 consecutive time error samples. This filter is applied by the test equipment to remove errors caused by timestamp quantization, or any quantization of packet position in the test equipment, before calculating the MTIE and TDEV. + +The minimum measurement period for TDEV is twelve times the integration period ( $T = 12\tau$ ). + +NOTE 3 – In the case of PTP, a sample is a single estimate of 2-way time error, calculated by combining the packets in forward and reverse directions. It is calculated by the test equipment measuring the difference between the time from the PRTC and the reference time. As an example, according to [b-ITU-T G.8275.1] the PTP message rate is 16 packets/second in each direction; therefore, there are 16 samples per second, calculated by combining a pair of packets in each direction. + +## 6.3 Jitter + +While most specifications in this Recommendation are independent of the output interface at which they are measured, this is not the case for jitter production; jitter generation specifications must utilize existing specifications that are currently specified differently for different interface rates. These requirements are stated separately for some of the interfaces identified in clause 9. The applicable jitter requirements for 2 048 kHz, 2 048 kbit/s, 1 544 kbit/s and 10 MHz output interfaces are defined in [ITU-T G.811]. + +The intrinsic jitter for the other interfaces identified in clause 9 is for further study. + +# 7 Holdover + +When a PRTC loses all its input phase and time references, it enters the phase/time holdover state. Under these circumstances, the PRTC may either rely on the holdover of a local oscillator, or on an optional external input frequency reference traceable to a primary reference clock (PRC), or on a combination of both. + +This requirement bounds the maximum excursions in the output timing signal. Additionally, it restricts the accumulation of the phase movement during input signal impairments or internal disturbances. + +The phase/time holdover requirements applicable to a PRTC are optional. When holdover is supported, it should comply with the holdover limits of one of the clock types as specified in clause 11.2 of [ITU-T G.812]. The type of clock depends on the specific application that needs to be supported. + +NOTE – The PRTC phase/time holdover requirements are optional because there can be various deployment scenarios. In some deployments, the PRTC relies on its local oscillator to provide long-term holdover. In other deployments, the PRTC could use backup input sources (e.g., sources available from the synchronization supply chain, such as packet-based PTP or physical-layer frequency). In other cases, redundancy can be provided by network design (e.g., multiple PRTCs). + +# 8 Phase discontinuity + +The phase discontinuity for a PRTC is for further study. + +# 9 Interfaces + +The requirements in this Recommendation are related to reference points which may be internal to the equipment or network equipment (NE) in which the PRTC is embedded and are, therefore, not necessarily available for measurement or analysis by the user. Consequently, the performance of the PRTC is not specified at these internal reference points, but rather at the external interfaces of the equipment. Note that not all the interfaces below need to be implemented on all equipment. + +See Appendix III concerning information exchanged over time interfaces. + +## 9.1 Phase and time interfaces + +### 9.1.1 Input interfaces for phase and time + +A PRTC has phase and time input interfaces if the optional UTC(*k*) insertion is used for the time reference (see Figure II.1): + +- ITU-T V.11-based time/phase input interface, as defined in [ITU-T G.703] and [ITU-T G.8271]; +- 1PPS 50 Ω phase-synchronization input interface as defined in [ITU-T G.703] and [ITU-T G.8271]. + +NOTE 1 – The ITU-T V.11-based time/phase interface has embedded 1PPS information. + +NOTE 2 – A 1PPS 50 Ω phase-synchronization input interface is the typical interface provided by UTC(*k*) time laboratories. As a 1PPS signal provides phase synchronization information only, time of day (ToD) needs to be provided by an additional interface. + +NOTE 3 – For both of these 1PPS interface types, the cable delay has to be compensated for. The cable delay compensation accuracy tolerance is $\pm 2$ ns. + +See Appendix III concerning information exchanged over time interfaces. + +### 9.1.2 Output interfaces for phase and time + +The output phase and time interfaces specified for the equipment in which the PRTC may be contained are: + +- ITU-T V.11-based time/phase distribution interface, as defined in [ITU-T G.703] and [ITU-T G.8271]; +- 1PPS 50 Ω phase-synchronization measurement interface, as defined in [ITU-T G.703] and [ITU-T G.8271]; +- Other interfaces are for further study; +- Ethernet interface carrying PTP messages. + +NOTE – Ethernet interfaces can combine synchronous Ethernet for frequency and PTP messages. + +## 9.2 Frequency interfaces + +In addition to phase and time interfaces, frequency interfaces may be used. At least one output frequency interface must be provided. The output frequency interfaces specified for the equipment in which the PRTC may be contained are: + +- 2 048 kHz interfaces according to [ITU-T G.703] with additional jitter and wander requirements as specified herein; +- 1 544 kbit/s interfaces according to [ITU-T G.703] with additional jitter and wander requirements as specified herein; +- 2 048 kbit/s interfaces according to [ITU-T G.703] with additional jitter and wander requirements as specified herein; +- Synchronous Ethernet interfaces; + +NOTE 1 – Ethernet interfaces can combine PTP messages and synchronous Ethernet. + +- ITU-T V.11-based time/phase distribution interface, as defined in [ITU-T G.703] and [ITU-T G.8271]; +- 1PPS 50 Ω phase-synchronization measurement interface, as defined in [ITU-T G.703] and [ITU-T G.8271]; + +- 10 MHz interfaces according to [ITU-T G.703]; + +NOTE 2 – Such interfaces may provide an improvement in phase noise performance for measurement purposes. + +- Other interfaces are for further study. + +The optional input frequency interfaces specified for the equipment in which the PRTC may be contained are for further study. + +# Appendix I + +## Measuring the performance of a PRTC or a PRTC combined with T-GM + +(This appendix does not form an integral part of this Recommendation.) + +The time error of a PRTC output is difficult to measure because time is a relative quantity. Unlike frequency, there is no such thing as a "time generator"; it always has to be compared to a standard such as UTC. Note that UTC itself is only known in retrospect, by comparing the outputs of many national reference time scales approximating UTC over a period of time. + +The performance of a PRTC and T-GM are highly dependent on the local oscillator characteristics, including frequency stability vs. temperature variation and aging. It is therefore recommended to test the performance of a PRTC at the applicable environmental conditions expected at the PRTC/T-GM location. + +NOTE 1 – The accuracy of the PRTC performance test is for further study. + +NOTE 2 – The test details of a PRTC combined with T-GM is in [b-ITU-T G.8273]. + +## I.1 Factors influencing the performance of a GNSS-based PRTC + +The most common type of PRTC is one that distributes the time using radio signals from a GNSS system. However, the performance of a GNSS system is dependent on a range of issues outside the control of the equipment vendor. Therefore, any vendor specification can only indicate what the equipment is capable of, rather than what performance the equipment will actually deliver in any given installation. + +In measuring the performance of a GNSS-based PRTC, under normal locked operating conditions, in addition to the conditions mentioned in clause 6.1, the following conditions should also be verified as far as possible: + +- the equipment is properly commissioned; +- the equipment is properly compensated for fixed offsets such as antenna cable length and cable amplifiers. For example, an antenna cable can produce a delay in the range of 4 to 5 ns/m, depending on the cable type; +- any 1PPS output signal delay compensation contained within the PRTC (such as that described in clause A.1.2 of [ITU-T G.8271]) is stable; +- the antenna has a clear view of the sky with minimal multipath distortion. + +In addition to these primary factors, there are some secondary conditions which may cause errors in the time distributed by a GNSS-based PRTC. These factors may be more difficult to quantify or to mitigate against. Secondary factors may include: + +- interference from ground level transmissions. While filters may be used to remove some ground level interference, this may not protect against local jamming. The presence of jamming may be verified by using interference detection equipment; +- atmospheric conditions such as thunderstorms, heavy rain or fog; +- solar interference such as sunspots and flares, which affect ionosphere delay. + +GNSS-based PRTCs may sometimes be deployed in locations where a clear view of the sky is not available, e.g., dense urban areas. When measuring the performance of PRTCs suitable for these locations, the following conditions should be included in the testing procedures: + +- multipath interference; +- dilution of precision (DOP); +- deep fading effect of the GNSS signal; + +- the number of directly-visible satellites: + - Before the measurement: The PRTC should complete self-survey under position-locked mode (see Note 1) with at least four directly visible satellites; + - During the measurement: in order to keep the PRTC to stay in position-locked mode, the number of directly-visible satellites should be at least 1 (see Note 2). + +NOTE 1 – "Position-locked mode" means that the receiver is known to be stationary, and this stationary condition is used in the position and time calculations. + +NOTE 2 – It is theoretically possible to maintain the time with one visible satellite for a stationary receiver after position and time has been acquired. When this condition cannot be met, the GNSS receiver is highly sensitive to multipath, satellite faults, or jamming, and therefore may be unreliable during such periods of low satellite visibility. + +## I.2 Phase wander measurement + +It is possible to measure the phase wander of a PRTC relative to a PRC-quality frequency reference, such as a caesium clock. A time interval counter is used to compare the phase of a 1PPS output signal from the PRTC against that of a PRC. The experimental set-up is shown in Figure I.1. + +![Diagram of the experimental set-up for measuring phase wander of a PRTC. A radio distributed PRTC signal (e.g., GNSS) is received by a PRTC under test. The PRTC under test outputs a 1PPS signal to a time interval counter. A PRC (e.g., Cs clock) also outputs a 1PPS signal to the same time interval counter. The time interval counter is connected to a data log. A measurement against an additional PRC to verify drift against the reference is also shown, with its own time interval counter and PRC Freq. Ref. connected to the data log.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +The diagram illustrates the experimental setup for measuring phase wander. At the top, an oval labeled "Radio distributed PRTC signal (e.g., GNSS)" has a dashed arrow pointing down to a box labeled "PRTC under test". The "PRTC under test" box has an output labeled "1PPS" pointing to a box labeled "Time interval counter". To the right, a box labeled "PRC Freq. Ref. e.g., Cs clock" also has an output labeled "1PPS" pointing to the same "Time interval counter". Below this, a large grey box labeled "Measurement against additional PRC to verify drift against reference" contains another "Time interval counter" and a "PRC Freq. Ref." box. The "PRTC under test" 1PPS output also connects to this second "Time interval counter". Both "Time interval counter" boxes have dashed arrows pointing down to a box labeled "Data log". + +Diagram of the experimental set-up for measuring phase wander of a PRTC. A radio distributed PRTC signal (e.g., GNSS) is received by a PRTC under test. The PRTC under test outputs a 1PPS signal to a time interval counter. A PRC (e.g., Cs clock) also outputs a 1PPS signal to the same time interval counter. The time interval counter is connected to a data log. A measurement against an additional PRC to verify drift against the reference is also shown, with its own time interval counter and PRC Freq. Ref. connected to the data log. + +**Figure I.1 – Measuring phase wander of a PRTC** + +Where a combined PRTC and T-GM function is to be tested, the time interval counter can be replaced by a packet timing monitor device, as shown in Figure I.2. + +![Diagram of the measurement setup for phase wander of a combined PRTC and T-GM. A 'Radio distributed PRTC signal (e.g., GNSS)' is received by a 'PRTC+T-GM under test'. This unit sends 'PTP' signals to a 'Packet timing monitor'. The 'Packet timing monitor' sends '1PPS' signals to a 'PRC Freq. Ref. e.g., Cs clock'. Both the 'Packet timing monitor' and the 'PRC Freq. Ref.' are connected to a 'Time interval counter'. The 'Time interval counter' is connected to a 'Data log'. A shaded box labeled 'Measurement against additional PRC to verify drift against reference' contains a second 'Packet timing monitor' and a second 'PRC Freq. Ref.'. The 'PRTC+T-GM under test' is also connected to this second 'Packet timing monitor'. The 'Data log' is connected to the second 'Packet timing monitor' and the second 'PRC Freq. Ref.'. The diagram is labeled 'G.8272-Y.1367(12)-Amd.1(13)_Fl.2'.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +Diagram of the measurement setup for phase wander of a combined PRTC and T-GM. A 'Radio distributed PRTC signal (e.g., GNSS)' is received by a 'PRTC+T-GM under test'. This unit sends 'PTP' signals to a 'Packet timing monitor'. The 'Packet timing monitor' sends '1PPS' signals to a 'PRC Freq. Ref. e.g., Cs clock'. Both the 'Packet timing monitor' and the 'PRC Freq. Ref.' are connected to a 'Time interval counter'. The 'Time interval counter' is connected to a 'Data log'. A shaded box labeled 'Measurement against additional PRC to verify drift against reference' contains a second 'Packet timing monitor' and a second 'PRC Freq. Ref.'. The 'PRTC+T-GM under test' is also connected to this second 'Packet timing monitor'. The 'Data log' is connected to the second 'Packet timing monitor' and the second 'PRC Freq. Ref.'. The diagram is labeled 'G.8272-Y.1367(12)-Amd.1(13)\_Fl.2'. + +**Figure I.2 – Measuring phase wander of a combined PRTC and T-GM** + +The wander of a caesium reference clock is extremely low, although it may have a slight offset to UTC frequency. For a PRC, this is guaranteed to be within 1 part in $10^{11}$ , but typical caesium references have much better performance. This frequency offset causes a tilt in the phase plot, which must be removed to reveal the wander performance of the PRTC. + +In order to distinguish between wander of the PRTC and that of the PRC, a second PRC can be used to make a three-way comparison. This is shown in Figures I.1 and I.2 by the components in the shaded boxes. This additional check may be omitted if not required. + +Since the caesium reference is only a source of frequency and not time, this experiment only indicates phase wander, and cannot measure the time error from the UTC time signal source. However, it does indicate that if the static error can be measured and calibrated out, the PRTC is capable of maintaining time within certain limits. + +## I.3 Time error measurements + +In order to determine the maximum time error of a PRTC, it is necessary to compare it to another source of accurate time. + +### I.3.1 Comparison against a reference receiver + +In the laboratory context, an accurate source of time might be another GNSS receiver of known uncertainty, or a "reference receiver". The experimental set-up is very similar to the wander measurement, but substituting the reference receiver for the caesium PRC. A time interval counter is used to compare the time difference of a 1PPS output signal from the PRTC against that of the reference receiver. The experimental set-up is shown in Figure I.3: + +![Figure I.3: Comparing time accuracy against a reference receiver. The diagram shows a 'Radio distributed PRTC signal (e.g., GNSS)' being received by a 'PRTC under test' and a 'Reference receiver'. Both send '1PPS' signals to a 'Time interval counter'. The 'Time interval counter' is connected to a 'Data log'. The diagram is labeled G.8272-Y.1367(12)-Amd.1(13)_Fl.3.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +graph LR + Signal([Radio distributed PRTC signal e.g., GNSS]) -.-> PRTC[PRTC under test] + Signal -.-> Ref[Reference receiver] + PRTC -- 1PPS --> TIC[Time interval counter] + Ref -- 1PPS --> TIC + TIC --> DL[Data log] + +``` + +G.8272-Y.1367(12)-Amd.1(13)\_Fl.3 + +Figure I.3: Comparing time accuracy against a reference receiver. The diagram shows a 'Radio distributed PRTC signal (e.g., GNSS)' being received by a 'PRTC under test' and a 'Reference receiver'. Both send '1PPS' signals to a 'Time interval counter'. The 'Time interval counter' is connected to a 'Data log'. The diagram is labeled G.8272-Y.1367(12)-Amd.1(13)\_Fl.3. + +**Figure I.3 – Comparing time accuracy against a reference receiver** + +For a combined PRTC and T-GM function, the time interval counter can be replaced by a packet timing monitor, as shown in Figure I.4: + +![Figure I.4: Comparing time accuracy of a PRTC and T-GM against a reference receiver. The diagram shows a 'Radio distributed PRTC signal (e.g., GNSS)' being received by a 'PRTC/T-GM under test' and a 'Reference receiver'. The 'PRTC/T-GM under test' sends a 'PTP' signal to a 'Packet timing monitor'. The 'Reference receiver' sends a '1PPS' signal to the 'Packet timing monitor'. The 'Packet timing monitor' is connected to a 'Data log'. The diagram is labeled G.8272-Y.1367(12)-Amd.1(13)_Fl.4.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +graph LR + Signal([Radio distributed PRTC signal e.g., GNSS]) -.-> PRTC[PRTC/T-GM under test] + Signal -.-> Ref[Reference receiver] + PRTC -- PTP --> PTM[Packet timing monitor] + Ref -- 1PPS --> PTM + PTM --> DL[Data log] + +``` + +G.8272-Y.1367(12)-Amd.1(13)\_Fl.4 + +Figure I.4: Comparing time accuracy of a PRTC and T-GM against a reference receiver. The diagram shows a 'Radio distributed PRTC signal (e.g., GNSS)' being received by a 'PRTC/T-GM under test' and a 'Reference receiver'. The 'PRTC/T-GM under test' sends a 'PTP' signal to a 'Packet timing monitor'. The 'Reference receiver' sends a '1PPS' signal to the 'Packet timing monitor'. The 'Packet timing monitor' is connected to a 'Data log'. The diagram is labeled G.8272-Y.1367(12)-Amd.1(13)\_Fl.4. + +**Figure I.4 – Comparing time accuracy of a PRTC and T-GM against a reference receiver** + +In this set-up, the reference receiver should ideally have a significantly better performance than the PRTC in order for the results to be valid. Since the PRTC time error specification is approaching the limits of what is possible relying on GNSS signal reception, this type of measurement is able to give an indication that the time accuracy is in the right area, rather than prove that the accuracy specification has been met. + +It should be noted that if the reference receiver performance is not significantly better than the PRTC under test, then it is impossible to verify if the equipment under test is within its specification. It can only be used for a basic test to quickly evaluate whether or not the PRTC has potential major problems. The reason is that if the reference receiver has the same performance as the PRTC, and even if it is co-located and has the same sky visibility, the measured MTIE, TDEV and max|TE| could be as much as twice the PRTC MTIE, TDEV, and max|TE| requirement or as small as zero. + +The reference receiver approach may be improved by using a collection of reference receivers. For example, if three receivers or more are used, it is possible to use a "majority voting" system to determine the performance of the PRTC under test. It is also possible to estimate the variance of individual receivers. The experimental set-up is shown in Figure I.5. + +![Diagram of Figure I.5: Comparing time accuracy against multiple reference receivers. A 'Radio distributed PRTC signal (e.g., GNSS)' is received by a 'PRTC under test' and three 'Reference receiver' units (A, B, and C). The 'PRTC under test' outputs an '1PPS' signal to three 'Time interval counter' units. Each 'Reference receiver' also outputs an '1PPS' signal to one of the 'Time interval counter' units. All three 'Time interval counter' units output to a 'Data log'.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +graph TD + Signal([Radio distributed PRTC signal e.g., GNSS]) + PRTC[PRTC under test] + R1[Reference receiver A] + R2[Reference receiver B] + R3[Reference receiver C] + T1[Time interval counter] + T2[Time interval counter] + T3[Time interval counter] + DataLog[Data log] + + Signal -.-> PRTC + Signal -.-> R1 + Signal -.-> R2 + Signal -.-> R3 + + PRTC -- 1PPS --> T1 + PRTC -- 1PPS --> T2 + PRTC -- 1PPS --> T3 + + R1 -- 1PPS --> T1 + R2 -- 1PPS --> T2 + R3 -- 1PPS --> T3 + + T1 --> DataLog + T2 --> DataLog + T3 --> DataLog + +``` + +Diagram of Figure I.5: Comparing time accuracy against multiple reference receivers. A 'Radio distributed PRTC signal (e.g., GNSS)' is received by a 'PRTC under test' and three 'Reference receiver' units (A, B, and C). The 'PRTC under test' outputs an '1PPS' signal to three 'Time interval counter' units. Each 'Reference receiver' also outputs an '1PPS' signal to one of the 'Time interval counter' units. All three 'Time interval counter' units output to a 'Data log'. + +G.8272-Y.1367(12)-Amd.1(13)\_Fl.5 + +**Figure I.5 – Comparing time accuracy against multiple reference receivers** + +For a combined PRTC and T-GM function, the time interval counters can be replaced by packet timing monitors. + +### I.3.2 Measurement against national reference time scales approximating UTC + +In order to prove that the time error relative to a given time standard is within acceptable limits, it is necessary to compare the PRTC to a much more accurate source of time. For example, this may be obtained from a national time laboratory. Either the measurement will need to be made at the laboratory itself, or an accurate time distribution system will need to be used, such as dedicated cable or fibre, or a GNSS common-view time service. This type of measurement may be used to characterize the performance of a reference receiver. The experimental set-up is shown in Figure I.6. + +![Diagram of Figure I.6: Measuring time accuracy against a national reference time scale. A 'Radio distributed PRTC signal (e.g., GNSS)' is received by a 'PRTC under test'. The 'PRTC under test' outputs an '1PPS' signal to a 'Time interval counter'. A 'National time scale' is connected to an 'Accurate time distribution (e.g., cable, fibre or GPS common-view service)', which in turn connects to a 'Time reference'. The 'Time reference' outputs an '1PPS' signal to the 'Time interval counter'. The 'Time interval counter' outputs to a 'Data log'.](a734898ce18e972938949637c32a34f4_img.jpg) + +``` + +graph TD + Signal([Radio distributed PRTC signal e.g., GNSS]) + PRTC[PRTC under test] + T1[Time interval counter] + TR[Time reference] + DataLog[Data log] + NT[National time scale] + ATD[Accurate time distribution e.g., cable, fibre or GPS common-view service] + + Signal -.-> PRTC + + PRTC -- 1PPS --> T1 + + NT --> ATD + ATD --> TR + + TR -- 1PPS --> T1 + + T1 --> DataLog + +``` + +Diagram of Figure I.6: Measuring time accuracy against a national reference time scale. A 'Radio distributed PRTC signal (e.g., GNSS)' is received by a 'PRTC under test'. The 'PRTC under test' outputs an '1PPS' signal to a 'Time interval counter'. A 'National time scale' is connected to an 'Accurate time distribution (e.g., cable, fibre or GPS common-view service)', which in turn connects to a 'Time reference'. The 'Time reference' outputs an '1PPS' signal to the 'Time interval counter'. The 'Time interval counter' outputs to a 'Data log'. + +G.8272-Y.1367(12)-Amd.1(13)\_Fl.6 + +**Figure I.6 – Measuring time accuracy against a national reference time scale** + +For a combined PRTC and T-GM function, the time interval counters can be replaced by a packet timing monitor. + +#### I.3.3 Comparison against a GNSS Simulator + +GNSS simulators generate a radio frequency (RF) signal, mimicking the signal that would be obtained from a satellite constellation, including the apparent "motion" of the satellites, the appearance and disappearance as they come up over the horizon and subsequently set. The simulator can be programmed with the "position" and "time" of the device under test at a given time and date, producing the correct satellite signals that would be observed from a receiver at that location and time. + +Some simulators are also capable of generating common signal impairments, such as might be caused by a limited sky view, atmospheric disturbance and multipath reflections. A full test of a PRTC should include the ability of the PRTC to withstand such impairments. + +A 1PPS output and time of day (ToD) output is also produced by the simulator, synchronized to the RF signals generated. This 1PPS/ToD signal may be compared to the output of a PRTC/T-GM under test to verify the accuracy of the device under test. + +This monitor compares the time and phase indicated by the PTP and 1PPS outputs from the device under test to the 1PPS/ToD generated by the simulator. Any difference between the two is the time or phase error produced by the device under test. A time interval counter is used to compare the time difference of a 1PPS output signal from the PRTC against that of the reference receiver. The experimental set-up is shown in Figure I.7. + +![Block diagram of Figure I.7: Comparing time accuracy of a PRTC against a GNSS simulator. A Frequency Reference (Freq. Ref.) is connected to a GNSS simulator. The GNSS simulator outputs an RF signal to a PRTC under test and a 1PPS/ToD signal to a Time interval counter. The PRTC under test outputs a 1PPS signal to the Time interval counter. The Time interval counter outputs a Data log. The diagram is labeled G.8272-Y.1367(15)_FI.7.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +``` +graph LR; FreqRef[Freq. Ref.] --> GNSS[GNSS simulator]; GNSS -- RF --> PRTC[PRTC under test]; GNSS -- "1PPS/ToD" --> TIC[Time interval counter]; PRTC -- "1PPS" --> TIC; TIC --> DL[Data log]; +``` + +Block diagram of Figure I.7: Comparing time accuracy of a PRTC against a GNSS simulator. A Frequency Reference (Freq. Ref.) is connected to a GNSS simulator. The GNSS simulator outputs an RF signal to a PRTC under test and a 1PPS/ToD signal to a Time interval counter. The PRTC under test outputs a 1PPS signal to the Time interval counter. The Time interval counter outputs a Data log. The diagram is labeled G.8272-Y.1367(15)\_FI.7. + +**Figure I.7 – Comparing time accuracy of a PRTC against a GNSS simulator** + +For a combined PRTC and T-GM function, the time interval counter can be replaced by a packet timing monitor, as shown in Figure I.8: + +![Block diagram of Figure I.8: Comparing time accuracy of a PRTC and T-GM against a GNSS simulator. A Frequency Reference (Freq. Ref.) is connected to a GNSS simulator. The GNSS simulator outputs an RF signal to a PRTC/T-GM under test and a 1PPS/ToD signal to a Packet timing monitor. The PRTC/T-GM under test outputs a PTP signal to the Packet timing monitor. The Packet timing monitor outputs a Data log. The diagram is labeled G.8272-Y.1367(15)-Err1(15)_FI.8.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +``` +graph LR; FreqRef[Freq. Ref.] --> GNSS[GNSS simulator]; GNSS -- RF --> PRTCTGM[PRTC/T-GM under test]; GNSS -- "1PPS/ToD" --> PTM[Packet timing monitor]; PRTCTGM -- "PTP" --> PTM; PTM --> DL[Data log]; +``` + +Block diagram of Figure I.8: Comparing time accuracy of a PRTC and T-GM against a GNSS simulator. A Frequency Reference (Freq. Ref.) is connected to a GNSS simulator. The GNSS simulator outputs an RF signal to a PRTC/T-GM under test and a 1PPS/ToD signal to a Packet timing monitor. The PRTC/T-GM under test outputs a PTP signal to the Packet timing monitor. The Packet timing monitor outputs a Data log. The diagram is labeled G.8272-Y.1367(15)-Err1(15)\_FI.8. + +**Figure I.8 – Comparing time accuracy of a PRTC and T-GM against a GNSS simulator** + +In this set-up, the alignment of the RF output and 1PPS signals from the GNSS simulator should ideally be better than 5 ns in order to prove the ITU-T G.8272 accuracy specification of less than 100 ns, the MTIE specification, and the TDEV specification have been met. + +As the measurements must be made over a long time period, the GNSS simulator should be driven by a stable frequency reference input, such as PRC or other stable atomic clock. The stability of this clock should be sufficient to ensure the wander is below the bandwidth of the PRTC under test. + +# Appendix II + +## PRTC functional model + +(This appendix does not form an integral part of this Recommendation.) + +A simplified model of the PRTC is provided in this appendix to describe its functionality and to define the various interfaces and functions that collectively define a PRTC. + +Figure II.1 represents a functional model and it is not intended to specify any specific implementation. + +![Figure II.1 – PRTC functional model diagram](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +The diagram illustrates the functional model of a PRTC. It shows the flow of time and frequency references through various internal blocks. On the left, a 'Time reference (e.g., GNSS signal)' enters a 'Time recovery block (e.g., GNSS engine)'. This block outputs 'Traceability information', 'Time', and 'Phase' to a 'Local timescale' block. An 'External frequency input reference (optional)' enters a 'Freq. I/F' block, which then connects to a 'Local frequency clock' block. This clock block outputs 'Traceability information' and 'Frequency' to the 'Local timescale' block. The 'Local timescale' block outputs 'Time reference', 'Phase reference', and 'Frequency reference' through 'Time I/F', 'Phase I/F', and 'Freq. I/F' blocks respectively. The entire system is labeled 'PRTC' at the top. A reference code 'G.8272-Y.1367(18)-Amd.2(22)\_FII.1' is shown at the bottom right of the diagram. + +Figure II.1 – PRTC functional model diagram + +Figure II.1 – PRTC functional model + +NOTE – The output interfaces shown in Figure II.1 correspond to logical interfaces; in some PRTC implementations, the time logical interface and the phase logical interface may be merged into the same phase/time physical interface. In addition to the time reference, the time logical interface may carry associated information on the traceability of the reference. + +The main function of a PRTC is to deliver a primary time reference to be used in time and/or phase synchronization of other clocks of the network. + +A PRTC receives a time reference from a system having access to a recognized reference time scale approximating UTC (e.g., from a global navigation satellite system or from a national laboratory participating in the generation of UTC) and delivers this reference signal to other clocks within a network or section of a network. + +In addition, a PRTC may include input frequency interfaces, but it must implement at least one output frequency interface. When connected to a frequency reference traceable to a PRC, the optional input frequency interface may be used to maintain the local representation of the timescale during outages of the input time reference (i.e., extend the phase/time holdover period of the clock). A possible use of the optional output frequency interface may be to measure the phase noise of the PRTC with traditional telecom signals. + +Finally, the PRTC may also deliver traceability information, reflecting the status of the clock (i.e., locked on its input reference signal, in holdover, etc.). The details of this traceability information are for further study. + +The functionality of the PRTC is defined based on the individual blocks in Figure II.1. A description of the functions is provided in Table II.1. Note that the specific grouping of the functions is for description only and is not intended to specify how the PRTC may be implemented. + +**Table II.1 – PRTC functions** + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Time recovery | Receives and processes the external time reference (e.g., from GNSS antenna).
Provides output signals to generate frequency, phase and time.
Provides traceability information. | +| Local frequency clock | The frequency clock generates the internally-used frequency timing signals.
In the case of loss of signal by the time recovery engine, the clock may either go into holdover, or switch to the optional incoming frequency reference (if present).
Details of this clock are for further study, although it is expected that the bandwidth will be significantly low given the output specification of the PRTC. | +| Local timescale | Maintains the local representation of the reference timescale, based on the frequency generated by the local frequency clock.
This block also generates the time and phase reference output signals. | +| I/F | Interface function necessary to generate a physical signal. | + +# Appendix III + +## Information exchanged over the time interface + +(This appendix does not form an integral part of this Recommendation.) + +The PRTC includes three output interfaces to carry frequency, phase and time. + +NOTE – These interfaces correspond to logical interfaces; in some PRTC implementations, the time logical interface and the phase logical interface may be merged into the same phase/time physical interface. + +The time interface supports the output of time and status information from the PRTC. The time and status information is carried in messages. The format of the messages is for further study. An example of information that could be transferred over the time interface is provided in Table III.1. + +**Table III.1 – Example of time and status information** + +| Name | Description | +|----------------------------------------|---------------------------------------------------------------------------------------------| +| Time | International atomic time (TAI), seconds. | +| Leap seconds | Leap seconds (offset between TAI and UTC). | +| Leap second addition/subtraction flags | Provides advance notification of the occurrence of a leap second. | +| Status | Provides an indication of whether the signal is locked, in holdover, or should not be used. | + +NOTE – TAI is maintained by the International Bureau of Weights and Measures (BIPM) using data from some 400 atomic clocks in over 80 national laboratories that maintain the best primary references. It is a pure paper time scale that has no physical realization at any location. It differs from UTC by the integer number of leap seconds. See Appendix II in [ITU-T G.8260]. + +# Appendix IV + +## PRTC locations + +(This appendix does not form an integral part of this Recommendation.) + +When considering phase/time distribution, the PRTC functions can be located at different positions, depending on the overall architecture that the network operator wishes to follow. In general, these can be summarized into the four generic locations A, B, C and D described in this clause, and illustrated in Figure IV.1. + +NOTE – A packet master/T-GM (not shown in the figure) is in general co-located with the PRTC, for instance, in case the PRTC delivers the time synchronization to remote locations. + +![Diagram illustrating generic locations for a PRTC function (A, B, C, D) within a network architecture. The diagram shows a Core network and a Backhaul network. Location A is a centralized PRTC co-located with a PRC in the Core network. Location B is a centralized PRTC not co-located with a PRC in the Core network. Location C is a PRTC in an aggregation site. Location D is a PRTC at the End application (e.g., base station). The legend indicates: PRTC (clock icon) provides a PRTC output time reference signal (solid red arrow); Time/phase synchronization path (dashed red arrow); PRC (wave icon) provides an optional frequency reference (dashed blue arrow).](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +The diagram illustrates four generic locations (A, B, C, D) for a PRTC function within a network architecture. The network is divided into a Core network and a Backhaul network, leading to an End application (e.g., base station). Location A shows a PRTC co-located with a PRC in the Core network. Location B shows a PRTC in the Core network not co-located with a PRC. Location C shows a PRTC in an aggregation site. Location D shows a PRTC at the End application. The legend defines the symbols: a clock icon for PRTC, a wave icon for PRC, a solid red arrow for PRTC output time reference signal, a dashed red arrow for Time/phase synchronization path, and a dashed blue arrow for Optional frequency reference (e.g., used to provide holdover during GNSS failures). The diagram is labeled G.8272-Y.1367(12)\_FIV.1. + +Diagram illustrating generic locations for a PRTC function (A, B, C, D) within a network architecture. The diagram shows a Core network and a Backhaul network. Location A is a centralized PRTC co-located with a PRC in the Core network. Location B is a centralized PRTC not co-located with a PRC in the Core network. Location C is a PRTC in an aggregation site. Location D is a PRTC at the End application (e.g., base station). The legend indicates: PRTC (clock icon) provides a PRTC output time reference signal (solid red arrow); Time/phase synchronization path (dashed red arrow); PRC (wave icon) provides an optional frequency reference (dashed blue arrow). + +Figure IV.1 – Generic locations for a PRTC function + +It should be noted that deploying the PRTC functions closer to the end application implies deploying a larger number of PRTC functions than in centralized locations, but it also has advantages. For instance, it simplifies the task of properly calibrating the asymmetry of the links from the PRTC to the end application. In this case, a smaller number of links would need to be calibrated in order to avoid the accumulation of excessive time error. + +### Case A: centralized PRTC co-located with PRC + +In case A, the PRTC is co-located with the PRC in the core network, and may receive a frequency reference from the PRC (the two functions may be integrated within the same equipment). The time synchronization reference is then delivered from the PRTC via the packet master all along the core network and the backhaul network, down to the end application (e.g., base station), for instance, using a time protocol such as PTP. + +### Case B: centralized PRTC not co-located with PRC + +In case B, the PRTC is located in the core network, but not co-located with the PRC; in general, the PRTC is in this case co-located with a synchronization supply unit (SSU) (the two functions may be integrated within the same equipment, typically a GNSS receiver is added to the SSU), and may receive a frequency reference from this SSU. The time synchronization reference is then delivered from the PRTC via a packet master (T-GM) all along the core network and the backhaul network, down to the end application (e.g., base station), for instance, using a time protocol such as PTP. + +### Case C: PRTCs in aggregation sites + +In case C, the PRTC is located in an aggregation site; typically a GNSS receiver is added to one of the last SSUs of the physical layer frequency chain. The time synchronization reference is then delivered from the PRTC via a packet master (T-GM) all along the backhaul network, down to the end application (e.g., base station), for instance, using a time protocol such as PTP. + +### **Case D: PRTCs at the edge of the network** + +In case D, the PRTC function is now located directly at the edge of the network (e.g., cell site); typically a GNSS receiver is directly connected to the end application (e.g., base stations). In this case, in general, the time synchronization reference is directly delivered from the PRTC to the end application (e.g., base station). + +# Bibliography + +- [b-ITU-T G.8273] Recommendation ITU-T G.8273/Y.1368 (2023), *Framework of phase and time clocks*. +- [b-ITU-T G.8275.1] Recommendation ITU-T G.8275.1/Y.1369.1 (2022), *Precision time protocol telecom profile for phase/time synchronization with full timing support from the network*. +- [b-ITU-R TF.486-2] Recommendation ITU-R TF.486-2 (1998), *Use of UTC frequency as reference in standard frequency and time signal emissions*. +- [b-WRC-23 Res.655] Resolution 655 (Rev.WRC-23) World Radiocommunication Conference (Dubai, 2023), *Definition of time scale and dissemination of time signals via radiocommunication systems*. + + + + + +## 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.8312-202012-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e32f9b8f1141bed243c16e02a6cd1411cbb87f1 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_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.8312-202012-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d97f827d81878c9a63ac53224f280153a9019e7 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26da0eff906329056215a7d1743edeaf54b6478d8c27652c61c22be966489b4e +size 67707 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..313fc4dc631b09114d9d38130474765950f8f74a --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31fe347512e748ea546b6fca12c5179d522992b4431d3a20a0ad0e779e82450a +size 21488 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/507e0ac3c85ae86ec1b85604d40fc249_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/507e0ac3c85ae86ec1b85604d40fc249_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17b10ea282a04411b1f57dbb64fa2bc2166296df --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/507e0ac3c85ae86ec1b85604d40fc249_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fce3469d601dba8a15141c5f6d59d7b652c78bd83b6bf96a1a577339d4dc4ce8 +size 19975 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..184dd30b5b29be6ecce3def2b84d336bc2384660 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b79f3c4d50f096d82db28d08ab859d4bfd768a58cae93fd8358f1128f188ecad +size 25652 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0eab3dae688040abae1ead476ec44ef32d6d1a10 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c4b25cf2492c9d4d650a00c4842ae2c3be4b33b64f447e68220f4140a89e0e4 +size 20181 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc809ba3aacbfd8c884bd7aa6c039bbac68ff211 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f51860369a096048d96755de81b2f467402f6b948e30561ada4237d82cf91cb +size 35262 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fff172ee800555247b2ee68a84c4211dea9faa6 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1c4b944e286b83eabe71b4fb682e5211de4a9fa187e97dc00f98bb986860e55 +size 25775 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..698ccbd9bf66f3f42a00d8679701d61f2ac7e6c6 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efc2075a0e66e9f71d950f58c91b28172476c6d16d064f37fe5cad33307b0a7b +size 24103 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a9916f69f908b3362d9537c0677444215aaa6b3 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67af92397b4bd276cbf03dd278441bb534a5b3ed4e1154f7e9759b1aa911900c +size 24718 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/965aaf7a8b454893b05799d266de6a69_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/965aaf7a8b454893b05799d266de6a69_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5039aa2e11d4a03eef9bfe5a135002aa044a70e --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/965aaf7a8b454893b05799d266de6a69_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce3fc5a149087aa4f346bbf3715df3c23e34a70dda28d9324622eeef8e018d8b +size 33242 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..319a0249a4fe9621d6e1d8105d6fc6aab484cdd2 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c05b0c4671a3a448f0a87c1a9a44ef7d64fc99f992c2241f8633d1279e512a9e +size 46961 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec19a3229f4d2bfe82352532af490d83d0f3df71 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cc804d0b492496cca39874dd5be2ca20018fd68b7ddcb35e44b6fff37dd3d54 +size 22166 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/a6cf7c02a60c336e0934b5ea40e35b49_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/a6cf7c02a60c336e0934b5ea40e35b49_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73f0fa9b08f7b25da68029d5505a8c42521a0fe7 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/a6cf7c02a60c336e0934b5ea40e35b49_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bff8f90ce194c66d5027e33e8c90a8257ee593bce2b58d467c84d5ee4e8c488 +size 10892 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acd5476ceea5ead63e6d24f680e899c218d50bc3 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8443b4f8b6bbd27ae782ae23be2310eebd15c694ff7abb8165ba5c0db5da6d9 +size 27408 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe175d5a9b833874003ce1885fb278cc264092de --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fee89c71c7dc497835d6f4c31e266d0528dcd4b7cb3416c8afb859ca24af6a59 +size 18643 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d33a91457b3877165891f25a45271e183c34aba6 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d221964c60a44839d46732c207761e1972f05c6dc5a24d24d2e21fd74d630a1c +size 34162 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/d17f75945bbb3feb84a153ecfedb9b81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50197d50f333ba2c1bb30886ff169373a1a8ebcd --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/d17f75945bbb3feb84a153ecfedb9b81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aac7abea9918f84f03e05feda8bf3bfe9be795ead546bcc3e9552c1f25f52f97 +size 47571 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f79399e3f3b61a6a3224bf8080e730435929bd26 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de7bd32ebd5697660551da5fa3ecfcd6dc7d01974cbf0dcffe2cabb0b0a8ed8e +size 12146 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/G/T-REC-G.8312-202012-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42c8ecbe8e457ea2e0ffa89f6a9b0c6b9ac4a6ce --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bf573824153d2b76eb3189d8bf22c7a59718b56695a802c5b23e60fe9fadf05 +size 22847 diff --git a/marked/G/T-REC-G.8312-202012-I_PDF-E/raw.md b/marked/G/T-REC-G.8312-202012-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cceacc3c12e8110cb6a8392297d8276603ad8758 --- /dev/null +++ b/marked/G/T-REC-G.8312-202012-I_PDF-E/raw.md @@ -0,0 +1,958 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.8312** + +(12/2020) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Packet over Transport aspects – Mobile network transport +aspects + +--- + +**Interfaces for metro transport networks** + +Recommendation ITU-T G.8312 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +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 white, bold, 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.8312 + +## Interfaces for metro transport networks + +## Summary + +Recommendation ITU-T G.8312 describes a transport technology for metro networks (MTNs), including transport of distributed radio access network (D-RAN) and centralized radio access network (C-RAN) traffic. This technology leverages existing and emerging pluggable Ethernet modules and reuses flex Ethernet (FlexE) implementation logic. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.8312 | 2020-12-22 | 15 | 11.1002/1000/14517 | + +## Keywords + +Frame formats, MTN, multiplexing, OAM. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2021 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 4 | +| 6 Metro transport network interfaces..... | 4 | +| 7 MTN section layer ..... | 5 | +| 7.1 Frame format ..... | 5 | +| 7.2 Rate adaptation ..... | 6 | +| 7.3 Processing blocks with uncorrected forward error correction errors ..... | 6 | +| 8 MTN path layer..... | 6 | +| 8.1 MTNP layer forwarding ..... | 6 | +| 8.2 MTNP OAM formats ..... | 7 | +| 8.3 OAM insertion..... | 9 | +| 8.4 OAM extraction..... | 10 | +| 9 MTN overhead description ..... | 11 | +| 9.1 Trail trace identifiers ..... | 11 | +| 9.2 MTNS overhead description..... | 12 | +| 9.3 MTNP overhead description..... | 13 | +| 10 MTN maintenance signals ..... | 18 | +| 10.1 MTNS maintenance signals..... | 18 | +| 10.2 MTNP maintenance signals..... | 18 | +| 11 MTN client mappings ..... | 18 | +| 11.1 Ethernet MAC based clients..... | 18 | +| Appendix I – Background on error marking in MTN ..... | 20 | +| I.1 Error marking ..... | 20 | +| I.2 Error contamination due to 66B block forwarding..... | 20 | + + + +## Recommendation ITU-T G.8312 + +## Interfaces for metro transport networks + +# 1 Scope + +This Recommendation specifies the rates and formats for use in metro transport network (MTN) digital layer networks: the MTN path (MTNP) layer and the MTN section (MTNS) layer, which support the transport of distributed radio access network (D-RAN) and centralized radio access network (C-RAN) traffic. It includes the following elements: + +- frame structures; +- functionality of the overhead; +- formats for mapping client signals (CSs). + +The MTNP layer provides flexible connections that carry client data and path operations, administration, and maintenance (OAM) in 64 bit/66 bit (64B/66B) blocks that are conformant to the encoding rules in clause 82 of [IEEE 802.3]. OAM functions include connectivity verification (CV), performance monitoring, path status and delay measurement (DM). Overhead to support MTNP layer protection is also supported. + +The MTNS layer operates over 50GBASE-R, 100GBASE-R, 200GBASE-R or 400GBASE-R server layers. The MTNS frame format is specified in a way that maximizes reuse of [OIF FLEXE IA] implementation logic, including support for bonding homogenous groups of 50GBASE-R, 100GBASE-R, 200GBASE-R, 400GBASE-R interfaces. The MTNS layer uses 64B/66B blocks that are conformant to the encoding rules in clause 82 of [IEEE 802.3], which allow the MTNS layer to be transported transparently over the lower layers of the Ethernet protocol stack. + +Functions and process flows associated with the interfaces specified lie outside the scope of this Recommendation. + +# 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.800] Recommendation ITU-T G.800 (2016), *Unified functional architecture of transport networks*. +- [ITU-T G.805] Recommendation ITU-T G.805 (2000), *Generic functional architecture of transport networks*. +- [ITU-T G.806] Recommendation ITU-T G.806 (2012), *Characteristics of transport equipment – Description methodology and generic functionality*. +- [ITU-T G.8310] Recommendation ITU-T G.8310 (2020), *Architecture of the metro transport network*. +- [ITU-T M.1400] Recommendation ITU-T M.1400 (2015), *Designations for interconnections among operators' network*. + +- [ITU-T T.50] Recommendation ITU-T T.50 (1992), *International reference alphabet (IRA) (formerly international alphabet No. 5 or IA5) – Information technology – 7-bit coded character set for information interchange.* +- [ISO 3166-1] ISO 3166-1:2020, *Codes for the representation of names of countries and their subdivisions – Part 1: Country code.* +- [IEEE 802.3] IEEE 802.3-2018, *IEEE Standard for Ethernet.* +- [IEEE 802.3cd] IEEE 802.3cd (2018), *IEEE Standard for Ethernet – Amendment 3: Media access control parameters for 50 Gb/s and physical layers and management parameters for 50 Gb/s, 100 Gb/s, and 200 Gb/s operation.* +- [IEEE 1588] IEEE 1588-2008, *IEEE Standard for a precision clock synchronization protocol for networked measurement and control systems.* +- [OIF FLEXE IA] Optical Internetworking Forum, IA Flex Ethernet 2.1 (2019), *Implementation agreement.* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **100GBASE-R** [IEEE 802.3] +- 3.1.2 **200GBASE-R** [IEEE 802.3] +- 3.1.3 **400GBASE-R** [IEEE 802.3] +- 3.1.4 **50GBASE-R** [IEEE 802.3cd] +- 3.1.5 **FlexE client** [OIF FLEXE IA] +- 3.1.6 **FlexE instance** [OIF FLEXE IA] +- 3.1.7 **low power idle (LPI) mode** [IEEE 802.3] +- 3.1.8 **MAC frame** [IEEE 802.3] +- 3.1.9 **ordered set** [IEEE 802.3] +- 3.1.10 **path** [ITU-T G.806] +- 3.1.11 **physical coding sublayer (PCS)** [IEEE 802.3] +- 3.1.12 **physical layer entity (PHY)** [IEEE 802.3] +- 3.1.13 **section** [ITU-T G.806] + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms. + +- 3.2.1 **Flex Ethernet implementation agreement; FlexE:** Agreement that provides a generic mechanism for supporting a variety of Ethernet MAC rates that may or may not correspond to any existing Ethernet PHY rate. + +NOTE – Paraphrased from [OIF FLEXE IA]. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +- IDM one-way Delay Measurement + +| | | +|--------|---------------------------------------------| +| 2DMM | two-way Delay Measurement | +| 2DMR | two-way Delay Measurement Response | +| AIS | Alarm Indication Signal | +| APS | Automatic Protection Switching | +| BER | Bit Error Ratio | +| BIP | Bit-Interleaved Parity | +| C-RAN | Centralized Radio Access Network | +| CRC-16 | Cyclic Redundancy Check-16 | +| CS | Client Signal | +| CV | Connectivity Verification | +| DAPI | Destination Access Point Identifier | +| DM | Delay Measurement | +| D-RAN | Distributed Radio Access Network | +| EoM | End of Message | +| FEC | Forward Error Correction | +| FlexE | Flex Ethernet | +| G/PCC | Geographic/Political Country Code | +| ICC | ITU Carrier Code | +| LF | Local False | +| LPI | Low Power Idle | +| LSB | Least Significant Bit | +| MAC | Medium Access Control | +| MCC | Management Communication Channel | +| MSB | Most Significant Bit | +| MTN | Metro Transport Network | +| MTNP | MTN Path | +| MTNS | MTN Section | +| OAM | Operations, Administration, and Maintenance | +| OCI | Open Connection Indication | +| PCS | Physical Coding Sublayer | +| PHY | Physical layer entity | +| RDI | Remote Defect Indication | +| REI | Remote Error Indication | +| RF | Remote False | +| S | Start | +| SAPI | Source Access Point Identifier | +| SoM | Start of Message | + +| | | +|------|---------------------------| +| T | Terminal | +| TLV | Type, Length, Value | +| TTI | Trail Trace Identifier | +| UAPC | Unique Access Point Code | +| UNI | User to Network Interface | + +# 5 Conventions + +This Recommendation uses the diagrammatic conventions defined in [ITU-T G.800] and [ITU-T G.805]. + +This Recommendation uses the textual conventions for block and sequence specified in [ITU-T G.8310] to identify information elements. + +This Recommendation uses the following conventions regarding bit values and transmission order. + +**Bit numbering:** Bits in an octet are numbered from 7 to 0, most significant bit (MSB) to least significant bit (LSB). Bits within a 66B block, other than the synchronization header, are numbered 0 to 63. + +**Transmission order:** The order of transmission of bytes in all the message diagrams in this Recommendation is first from left to right and then from top to bottom. The order of transmission of 66B blocks is from left to right, per the convention in Figure 82-3 of [IEEE 802.3]. + +**Value of reserved bit(s):** The value of an overhead bit, which is reserved or reserved for future international standardization, shall be set to "0". + +**Value of non-sourced bit(s):** Unless stated otherwise, any non-sourced bits shall be set to "0". + +This Recommendation uses the following abbreviations to indicate units or prefixes for units: + +**B:** Following the convention in [IEEE 802.3], B indicates “bit”. For example, a 66B block contains 66 bits. + +**K:** The binary prefix "Kibi", indicating 1 024. For example, 16 Kblocks is 16 384 blocks. + +# 6 Metro transport network interfaces + +An MTN comprises two non-recursive layer networks, path and section, as discussed in [ITU-T G.8310]. The relationship of MTN to [IEEE 802.3] and to [OIF FLEXE IA] is described in Annex A of [ITU-T G.8310]. The basic signal structure and information containment relationships for an MTN are shown in Figure 6-1. + +![Figure 6-1: Basic signal structure and information containment relationships for an MTN. The diagram is split into two parts. The left part, 'Basic signal structure', shows a stack of three layers: 'Clients' at the top, 'MTN path' in the middle, and 'Server' at the bottom. The right part, 'Information containment', shows a more detailed stack. At the top is a 'Client' box. Below it is the 'MTN path' layer, which contains two sub-boxes: 'MTNP OH' and 'MTN path payload'. Below the MTN path is the 'MTN section' layer, which contains two sub-boxes: 'MTNS OH' and 'MTN section payload'. At the bottom is a 'Server' box. Dashed lines indicate the flow of information from the Client through the MTN path and MTN section to the Server. A small label 'G.8312(20)_F6-1' is at the bottom right.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Figure 6-1: Basic signal structure and information containment relationships for an MTN. The diagram is split into two parts. The left part, 'Basic signal structure', shows a stack of three layers: 'Clients' at the top, 'MTN path' in the middle, and 'Server' at the bottom. The right part, 'Information containment', shows a more detailed stack. At the top is a 'Client' box. Below it is the 'MTN path' layer, which contains two sub-boxes: 'MTNP OH' and 'MTN path payload'. Below the MTN path is the 'MTN section' layer, which contains two sub-boxes: 'MTNS OH' and 'MTN section payload'. At the bottom is a 'Server' box. Dashed lines indicate the flow of information from the Client through the MTN path and MTN section to the Server. A small label 'G.8312(20)\_F6-1' is at the bottom right. + +**Figure 6-1 – Basic signal structure and information containment relationships for an MTN** + +Each client is a sequence of Ethernet medium access control (MAC) frames. The server layer is one or more Ethernet PHYs, operating at the same bit rate, that use the block coding specified by the PCS specified in clause 82 of [IEEE 802.3]. + +An MTN provides frame-based services to its clients. User to network interface (UNI) links are terminated by the UNI interfaces and only MAC frames are transported across the MTNP. + +# 7 MTN section layer + +The MTNS layer supports bidirectional, symmetric, point-to-point links that are constrained by the connectivity of the server layer over which it is carried. It supports transmission of frequency and time synchronization information. + +The adapted information for the MTNS layer is the MTNP layer characteristic information, rate-adapted to the MTNS layer clock. The characteristic information for the MTNS layer is the MTNS layer adapted information plus section overhead. + +## 7.1 Frame format + +The MTNS frame is the flex Ethernet (FlexE) overhead frame as specified in [OIF FLEXE IA]. A FlexE group consists of one or more PHYs, each carrying $q$ FlexE instances, as described in clause 6 of [OIF FLEXE IA]. Figure 7-1 illustrates the conceptual overhead frame structure of each FlexE instance within a FlexE group. The structure of the overhead in column 1 is described in Figures 24 and 25 of [OIF FLEXE IA]. + +![Figure 7-1: Conceptual view of the overhead frame structure of a FlexE instance. The diagram shows a grid of 8 rows and 20461 columns. Row 1 is the 'Overhead' row, with the first cell containing the number '0'. Rows 2 through 8 are part of the 'Payload' area. The payload is labeled as '(8 × 1023 × 20 66B blocks)'. The columns are numbered 1, 2, ..., Column #, ..., 20461. A small label 'G.8312(20)_F7-1' is at the bottom right.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +Figure 7-1: Conceptual view of the overhead frame structure of a FlexE instance. The diagram shows a grid of 8 rows and 20461 columns. Row 1 is the 'Overhead' row, with the first cell containing the number '0'. Rows 2 through 8 are part of the 'Payload' area. The payload is labeled as '(8 × 1023 × 20 66B blocks)'. The columns are numbered 1, 2, ..., Column #, ..., 20461. A small label 'G.8312(20)\_F7-1' is at the bottom right. + +**Figure 7-1 – Conceptual view of the overhead frame structure of a FlexE instance** + +The 66B blocks of the $q$ FlexE instances within a PHY are interleaved (see clause 6.5 of [OIF FLEXE IA]). + +The payload of the FlexE group is divided into calendar slots (see clause 6.8 of [OIF FLEXE IA]). MTNP layer signals are mapped into these calendar slots. + +The MTNS layer is always carried over Ethernet interfaces; as such, there are no unequipped FlexE instances or unavailable calendar slots in an MTNS interface (see clauses 6.6 and 6.9 of [OIF FLEXE IA]). Each calendar slot that is not used to carry an MTNP is filled with the pattern specified for the open connection indication (OCI) maintenance signal (see clause 10.2.2). + +### 7.1.1 MTNS connectivity verification + +MTNS layer connectivity verification (CV) is provided via a trail trace identifier (TTI). Since the frame format specified in [OIF FLEXE IA] does not include this information, the TTI is transported over the MTNS management communication channel (MCC). The encoding of the TTI for transport over the MCC lies outside the scope of this Recommendation. + +## 7.2 Rate adaptation + +Rate adaptation of each instance of the MTNP characteristic information to the MTNS layer clock is done via inserting or deleting idle blocks or deleting sequence-ordered sets according to the principles described in clause 82 of [IEEE 802.3], which allow insertion or deletion of groups of 8 idle characters or deletion of one of a pair of consecutive sequence-ordered sets. Since the MTN layers exist below the PCS encoder in clause 82 of [IEEE 802.3] (see Annex A of [ITU-T G.8310]), the idle insertion and deletion is performed on 66B blocks that contain eight idle characters rather than individual characters. Since a sequence-ordered set occupies an entire 66B block, deletion of sequence-ordered sets is also performed on a block basis. + +## 7.3 Processing blocks with uncorrected forward error correction errors + +For MTNS signals transported over 50GBASE-R or 100GBASE-R PHYs with forward error correction (FEC), the error-marking method must be different to that used for Ethernet (as specified in [IEEE 802.3]) to ensure that MTNPs in all calendar slots impacted by an FEC codeword with errors that cannot be corrected are marked. When the Reed-Solomon decoder determines that an FEC codeword contains errors that have not been corrected, every 66B block in the codeword is marked as an error (i.e., set to EBLOCK\_R). For example, this may be achieved by setting the synchronization header to 0b11 for all 66B blocks created from the codeword by the 256B/257B to 64B/66B transcoder. If this method is used, the bit error ratio (BER) monitoring state diagram shown in Figure 82-15 of [IEEE 802.3] shall be disabled. + +See Appendix I for additional background on error marking. + +# 8 MTN path layer + +The MTNP layer supports bidirectional, symmetric, point-to-point connectivity, including protection. The MTNP layer does not support transfer of the client timing or its own timing across an MTNS due to the possibility of idle block insertion or deletion in the adaptation to the MTNS layer. + +The adapted information for the MTNP layer is the client layer characteristic information, encoded as a sequence of 64B/66B blocks that use the block types and formats shown in Figure 82-5 of [IEEE 802.3]. The characteristic information for the MTNP layer is the MTNP layer adapted information plus the path overhead. + +An MTNP is carried over an integer number of $n$ 5 Gbit/s calendar slots within the MTNS layer. The nominal bit rate of the MTNP is $n \times 5$ Gbit/s. + +## 8.1 MTNP layer forwarding + +At an intermediate node, the MTNP characteristic information is extracted from the $n$ calendar slots to which it is assigned on the ingress MTNS, rate adaptation is performed as described in clause 7.2, + +and the MTNP characteristic information is inserted into the $n$ calendar slots to which it is assigned on the egress MTNS. The value of $n$ is the same for both ingress and egress MTNS. To prevent error-marked 66B blocks (see clause 7.3) and 66B blocks with invalid synchronization headers from propagating errors to other MTNP on the egress MTNS, any 66B block that has been error-marked or contains an invalid synchronization header will be replaced with an error control block /E/ (EBLOCK\_T). See Appendix I for additional background. + +## 8.2 MTNP OAM formats + +### 8.2.1 OAM structure + +The MTNP overhead is a set of messages that organizes the OAM information elements based on the OAM function and the required transmission frequency of that information. The three classes of message are: basic, automatic protection switching (APS) and low priority. + +These messages are conceptually similar to the type, length, value (TLV) structure. + +### 8.2.2 Message formats + +The format of the value bytes of each message is described in this clause. Because of the way messages are encoded for transmission (see clause 8.2.3), the number of value bytes is always even. + +#### 8.2.2.1 Basic message + +The basic message contains path status and error monitoring information. It consists of two value bytes. The format of the message is shown in Figure 8-1. + +![](e9d825d87c5f85c8dba0664eace96ef4_img.jpg) + +| | | | | | | | | | | | | | | | | +|--------------------|-----|-----|-----|-----|---|---|---|--------------------|---|---|---|---|---|---|---| +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| Value 1 | | | | | | | | Value 2 | | | | | | | | +| RES | RDI | LSB | REI | MSB | | | | Parity | | | | | | | | + +G.8312(20)\_F8-1 + +Figure 8-1 – Value bytes in a basic message + +#### 8.2.2.2 Low priority messages + +The set of low priority messages is listed in Table 8-1. + +Table 8-1 – Low priority messages + +| Message name | | Purpose | +|--------------|--|------------------------------------| +| CV | | MTNP connectivity verification | +| 1DM | | One-way delay measurement | +| 2DMM | | Two-way delay measurement | +| 2DMR | | Two-way delay measurement response | +| CS | | Client signal information | + +##### 8.2.2.2.1 MTNP connectivity verification value bytes + +The 34 value bytes for a CV message are shown in Figure 8-2. + +![](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|--|---------------------|---|---|---|---|---|---|---|---------------------|---|---|---|---|---|---|---|---------------------|---|---|---|---|---|---|---| +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| Value 1 | | | | | | | | | Value 32 | | | | | | | | Value 33 | | | | | | | | Value 34 | | | | | | | | +| TTI | | | | | | | | | | | | | | | | | RES | | | | | | | | CRC-12 | | | | | | | | + +G.8312(20)\_F8-2 + +**Figure 8-2 – Value bytes in a connectivity verification message** + +##### 8.2.2.2.2 One-way delay measurement and two-way delay measurement value bytes + +The 10 value bytes for a 1DM or 2DMM message are shown in Figure 8-3. + +![](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|--|--------------------|---|---|---|---|---|---|---|--------------------|---|---|---|---|---|---|---|---------------------|---|---|---|---|---|---|---| +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| Value 1 | | | | | | | | | Value 8 | | | | | | | | Value 9 | | | | | | | | Value 10 | | | | | | | | +| Tx-f-TS | | | | | | | | | | | | | | | | | RES | | | | | | | | CRC-12 | | | | | | | | + +G.8312(20)\_F8-3 + +**Figure 8-3 – Value bytes in 1DM and 2DMM messages** + +##### 8.2.2.2.3 Two-way delay measurement response value bytes + +The 26 value bytes for a 2DMR message are shown in Figure 8-4. + +![](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------|---|---|---|---|---|---|---|--|---------------------|---|---|---|---|---|---|---|---------------------|---|---|---|---|---|---|---|---------------------|---------------------|---|---|---|---|---|---|---| +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| Value 1 | | | | | | | | | Value 8 | | | | | | | | Value 9 | | | | | | | | | Value 16 | | | | | | | | +| Tx-f-TS | | | | | | | | | | | | | | | | | | | | | | | | | Rx-f-TS | | | | | | | | | +|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | +| Value 17 | | | | | | | | | Value 24 | | | | | | | | Value 25 | | | | | | | | Value 26 | | | | | | | | | +| Tx-b-TS | | | | | | | | | | | | | | | | | RES | | | | | | | | CRC-12 | | | | | | | | | + +G.8312(20)\_F8-4 + +**Figure 8-4 – Value bytes in a 2DMR message** + +##### 8.2.2.2.4 Client signal type value bytes + +The two value bytes for a CS message are shown in Figure 8-5. + +![](a6cf7c02a60c336e0934b5ea40e35b49_img.jpg) + +| | | | | | | | | | | | | | | | | +|--------------------|-----|---|---|--------|---|---|---|--------------------|---|---|---|---|---|---|---| +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| Value 1 | | | | | | | | Value 2 | | | | | | | | +| PT | RES | | | CRC-12 | | | | | | | | | | | | + +G.8312(20)\_F8-5 + +**Figure 8-5 – Value bytes in a CS message** + +#### 8.2.2.3 APS message + +The APS message is described in the same manner as the low priority messages. The four value bytes for the APS message are shown in Figure 8-6. + +![](507e0ac3c85ae86ec1b85604d40fc249_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|--------------------|---|---|---|---|---|---|---|--------------------|---|---|---|---|---|---|---|--------------------|---|---|---|---|---|---|---| +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| Value 1 | | | | | | | | Value 2 | | | | | | | | Value 3 | | | | | | | | Value 4 | | | | | | | | +| APS1 | | | | | | | | APS2 | | | | | | | | RES | | | | | | | | CRC-12 | | | | | | | | + +G.8312(20)\_F8-6 + +**Figure 8-6 – APS message format** + +The details of the APS protocol lie outside the scope of this Recommendation. + +### 8.2.3 Encoding MTNP OAM messages into 66B blocks + +MTNP OAM messages are encoded into ordered set blocks as specified in clause 82.2.3.9 of [IEEE 802.3]. The O code 0xC is used to identify an ordered set that contains MTNP OAM. A message can span multiple ordered set blocks. Table 8-2 shows the number of 66B blocks that are needed for each message. + +**Table 8-2 – Number of 66B blocks per message** + +| Message type | Blocks | +|--------------|--------| +| Basic | 1 | +| CV | 17 | +| 1DM | 5 | +| 2DMM | 5 | +| 2DMR | 13 | +| CS | 1 | +| APS | 2 | + +Figure 8-7 illustrates the high-level block structure into which the messages are encoded. To facilitate reassembly of the messages, the message type is included in each block, and each block also contains start of message (SoM) and end of message (EoM) indications. The length of a message is implicitly known based on the type and is not directly encoded into the block. Two value bytes from the message are mapped into bytes 2 and 3 of a block. + +![Figure 8-7: MTNP OAM 66B block structure. The diagram shows the bit-level layout of a 66-bit block. It starts with a 2-bit Sync field (1 0). Byte 0 (bits 2-9) contains the O-code 0x4B. Byte 1 (bits 10-17) contains control flags: SOM (Start of Message), EOM (End of Message), and the Message Type. Bytes 2 and 3 (bits 18-33) contain the Message-specific data (two value bytes). Byte 4 (bits 34-41) contains the O-code 0xC and 0x0. Bytes 5, 6, and 7 (bits 42-65) are reserved and set to 0x00.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +Figure 8-7: MTNP OAM 66B block structure. The diagram shows the bit-level layout of a 66-bit block. It starts with a 2-bit Sync field (1 0). Byte 0 (bits 2-9) contains the O-code 0x4B. Byte 1 (bits 10-17) contains control flags: SOM (Start of Message), EOM (End of Message), and the Message Type. Bytes 2 and 3 (bits 18-33) contain the Message-specific data (two value bytes). Byte 4 (bits 34-41) contains the O-code 0xC and 0x0. Bytes 5, 6, and 7 (bits 42-65) are reserved and set to 0x00. + +**Figure 8-7 – MTNP OAM 66B block structure** + +Figure 8-8 illustrates how a message with more than two value bytes is mapped into multiple MTNP OAM 66B blocks. For simplicity, only bytes 1-3 of the blocks are shown. + +![Figure 8-8: Mapping an MTNP OAM message into multiple MTNP OAM 66B blocks. The diagram shows a logical message consisting of a Type field followed by multiple value bytes (Value1, Value2, ..., Valuen-1, Valuen). This message is fragmented into multiple 66B blocks. Block 1 contains the SOM flag set, the Message Type, and the first two value bytes (Value1, Value2) in its Message-specific field. Subsequent blocks (up to Block n/2) contain the Message Type and subsequent pairs of value bytes. The final block (Block n/2) has the EOM flag set and contains the last two value bytes (Valuen-1, Valuen).](a7c51c18111139f9aca2805114108565_img.jpg) + +Figure 8-8: Mapping an MTNP OAM message into multiple MTNP OAM 66B blocks. The diagram shows a logical message consisting of a Type field followed by multiple value bytes (Value1, Value2, ..., Valuen-1, Valuen). This message is fragmented into multiple 66B blocks. Block 1 contains the SOM flag set, the Message Type, and the first two value bytes (Value1, Value2) in its Message-specific field. Subsequent blocks (up to Block n/2) contain the Message Type and subsequent pairs of value bytes. The final block (Block n/2) has the EOM flag set and contains the last two value bytes (Valuen-1, Valuen). + +**Figure 8-8 – Mapping an MTNP OAM message into multiple MTNP OAM 66B blocks** + +## 8.3 OAM insertion + +MTNP OAM blocks are inserted into the client block sequence with a nominal period of $T = n \times 16K$ blocks, where $i$ is the number of 5 Gbit/s calendar slots that the MTNP occupies. + +The insertion follows a regular pattern of opportunities as shown in Figure 8-9, where B, A and L represent opportunities to insert a block from a basic, APS or low priority message, respectively. The block positions shown in Figure 8-9 represent the nominal insertion points for the OAM blocks. + +![Figure 8-9: Pattern of insertion opportunities. A horizontal timeline with an arrow pointing right shows insertion points. Vertical lines mark points B, A, B, L, B, A, B, L. Below the timeline, intervals are labeled: 2T (n×32K) between the first B and A, T (n×16K) between A and the second B, T (n×16K) between the second B and L, and T (n×16K) between L and the third B. The label G.8312(20)_F8-9 is at the bottom right.](5cab96b2d23174c25919840ecd50aa48_img.jpg) + +Figure 8-9: Pattern of insertion opportunities. A horizontal timeline with an arrow pointing right shows insertion points. Vertical lines mark points B, A, B, L, B, A, B, L. Below the timeline, intervals are labeled: 2T (n×32K) between the first B and A, T (n×16K) between A and the second B, T (n×16K) between the second B and L, and T (n×16K) between L and the third B. The label G.8312(20)\_F8-9 is at the bottom right. + +**Figure 8-9 – Pattern of insertion opportunities** + +The sequence of low priority opportunities follows a regular pattern of 64 opportunities, as shown in Table 8-3. This results in an overall cycle of 256 OAM insertion opportunities. + +**Table 8-3 – Low priority opportunity pattern** + +| Low priority opportunity | Message | +|--------------------------|---------------| +| 1-17 | CV | +| 18 | CS | +| 19-31 | 1DM/2DMM/2DMR | +| 32-64 | Reserved | + +The 1DM, 2DMM and 2DMR messages share opportunities 19-31. In a given cycle of 64 low priority opportunities, only one of these messages may be transmitted. The first block of any of the DM messages is sent in low priority opportunity 19. + +The basic, CV and CS messages are sent at every opportunity. 1DM and 2DMM messages are sent when requested by the management system. 2DMR messages are sent in response to a 2DMM message. Nothing is sent in the unused DM opportunities or reserved opportunities. + +The actual insertion of each OAM block is delayed from the nominal insertion point so that the OAM block falls in the interpacket gap as shown in Figure 8-10. Delaying insertion of a block does not change the nominal insertion point of the next block. Idle blocks are removed as necessary from the client block sequence to compensate for the insertion of the MTNP OAM. + +![Figure 8-10: MTNP OAM block insertion illustration. A sequence of blocks is shown: ... I I O I I S D D D D D D D D D D D D D D D D D D D D T O I ... I S D D D ... D T I O I I ... The first O (MTNP path OAM block) is inserted after two I (Idle blocks). The second O is inserted after a T (Terminal control block). The time interval between the start of the first O and the start of the second O is labeled T. The time interval between the nominal insertion point (dashed line) and the actual insertion point of the second O is labeled ΔT. A legend at the bottom identifies: O MTNP path OAM block, I Idle block, S Start control block, T Terminal control block, D Data block. The label G.8312(20)_F8-10 is at the bottom right.](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg) + +Figure 8-10: MTNP OAM block insertion illustration. A sequence of blocks is shown: ... I I O I I S D D D D D D D D D D D D D D D D D D D D T O I ... I S D D D ... D T I O I I ... The first O (MTNP path OAM block) is inserted after two I (Idle blocks). The second O is inserted after a T (Terminal control block). The time interval between the start of the first O and the start of the second O is labeled T. The time interval between the nominal insertion point (dashed line) and the actual insertion point of the second O is labeled ΔT. A legend at the bottom identifies: O MTNP path OAM block, I Idle block, S Start control block, T Terminal control block, D Data block. The label G.8312(20)\_F8-10 is at the bottom right. + +**Figure 8-10 – MTNP OAM block insertion illustration** + +## 8.4 OAM extraction + +The MTNP OAM is recognized based on the 66B block being an ordered set with O code 0xC. Blocks matching this signature are extracted from the received block sequence and processed as OAM blocks. To compensate for the removed OAM blocks, idle blocks are inserted into the block sequence to maintain the same clock rate. + +# 9 MTN overhead description + +## 9.1 Trail trace identifiers + +A TTI is defined as a 32-byte string containing a 16-byte source access point identifier (SAPI) followed by a 16-byte destination access point identifier (DAPI). + +Each access point identifier consists of an all-zero byte, a 3-character international segment and a 12-character national segment, both of which are coded according to [ITU-T T.50], as shown in Figure 9-1. + +| International segment | | | | National segment | | | | | | | | | | | | +|-----------------------|----|---|---|------------------|------|------|------|------|------|----|----|----|----|----|----| +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | +| 0 | CC | | | ICC | UAPC | | | | | | | | | | | +| | | | | ICC | UAPC | | | | | | | | | | | +| | | | | ICC | | UAPC | | | | | | | | | | +| | | | | ICC | | | UAPC | | | | | | | | | +| | | | | ICC | | | | UAPC | | | | | | | | +| | | | | ICC | | | | | UAPC | | | | | | | + +G.8312(20)\_F9-1 + +**Figure 9-1 – Access point identifier formats** + +The international segment field provides a three-character ISO 3166-1 geographic/political country code (G/PCC). The country code shall be based on the three-character uppercase alphabetic ISO 3166-1 country code (e.g., USA, FRA). + +The national segment field consists of two subfields: the ITU carrier code (ICC) followed by a unique access point code (UAPC). + +The ICC is assigned to a network operator or service provider, maintained by the ITU-T Telecommunication Standardization Bureau (TSB) as per [ITU-T M.1400]. This code shall consist of 1-6 left-justified characters, alphabetic or leading alphabetic with trailing numeric. + +The UAPC shall be a matter for the organization to which the country code and ICC have been assigned, provided that uniqueness is guaranteed. This code shall consist of 6-11 characters, padded with the necessary trailing NUL characters to complete the 12-character national segment. + +The features of access point identifiers are: + +- each access point identifier must be globally unique in its layer network; +- where it may be expected that the access point may be required for path set-up across an inter-operator boundary, the access point identifier must be available to other network operators; +- the access point identifier should not change while the access point remains in existence; +- the access point identifier should be able to identify the country and network operator responsible for routing to and from the access point; +- the set of all access point identifiers belonging to a single administrative layer network should form a single access point identification scheme; +- the scheme of access point identifiers for each administrative layer network can be independent from the scheme in any other administrative layer network. + +## **9.2 MTNS overhead description** + +The MTNS layer overhead is determined primarily by reference to [OIF FLEXE IA]. The overhead frame is shown in Figures 24 and 25 of [OIF FLEXE IA]. Additional overhead specific to the MTNS is also specified in this clause. + +### **9.2.1 Frame alignment** + +Frame alignment and multiframe alignment overhead are described in clause 7.3.1 of [OIF FLEXE IA]. + +### **9.2.2 Group composition** + +The MTNS is based on a FlexE group. Each group has a number as described in clause 7.3.6 of [OIF FLEXE IA]. The overhead to identify the membership of the group is present in each FlexE instance, as described in clause 7.3.3 of [OIF FLEXE IA]. + +### **9.2.3 Calendar management** + +Two alternative calendar slot configurations are provided, as described in clause 7.3.4 of [OIF FLEXE IA]. + +The active calendar configuration is indicated as described in clause 7.3.2 of [OIF FLEXE IA]. + +A mechanism to coordinate changing between the two calendar configurations at the source and sink nodes is provided via the calendar request and calendar acknowledge bits as described in clause 7.3.4 of [OIF FLEXE IA]. + +### **9.2.4 Management communication channel** + +The MTNS MCC is provided by the FlexE shim-to-shim management channel described in clause 7.3.5 of [OIF FLEXE IA]. The format of the information in this channel lies outside the scope of this Recommendation. + +The FlexE section management channel described in clause 7.3.5 of [OIF FLEXE IA] is not used. + +### **9.2.5 Synchronization management channel** + +The MTNS synchronization management channel is provided by the FlexE synchronization management channel described in clause 7.3.5 of [OIF FLEXE IA]. The synchronization configuration bit described in clause 7.3.5 of [OIF FLEXE IA] is always set to 1. + +### **9.2.6 Remote PHY fault indication** + +A remote fault indication is provided for each PHY as described in clause 7.3.8 of [OIF FLEXE IA]. + +### **9.2.7 Reserved bits** + +Reserved bits are specified in clause 7.3.7 of [OIF FLEXE IA]. + +### **9.2.8 CRC-16** + +A CRC-16 for the MTNS overhead is provided, as described in clause 7.3.9 of [OIF FLEXE IA]. + +### **9.2.9 Trail trace identifier** + +A 32-byte TTI as specified in clause 9.1 provides CV for the MTNS. The TTI is transported over the MTNS MCC. The encoding of the TTI for transport over the MCC lies outside the scope of this Recommendation. + +## 9.3 MTNP overhead description + +### 9.3.1 Fields common to all messages + +#### 9.3.1.1 Start and end of message indicators + +An SoM indicator field is defined in bit 0 of the first byte of each 66B block. This field is set to "1" to indicate the first block in a message and is set to "0" in all subsequent blocks of the message for all messages other than the basic message. + +An EoM indicator field is defined in bit 1 of the first byte of each 66B block. This field is set to "1" to indicate the last block in a message and is set to "0" in all previous blocks of the message for all messages other than the basic message. + +Since the basic message occurs twice in the message sequence described in clause 8.3, the SoM is set to "1" and EoM to "0" for the basic message that precedes an APS opportunity, and SoM is set to "0" and EoM to "1" for the basic message that precedes a low priority opportunity. + +NOTE – The use of different SoM and EoM values for the basic message based on the position in the message sequence enables faster framing to the message sequence if there are no low priority messages or APS messages available to transmit. + +The possible combinations of SoM and EoM bits are shown in Table 9-1. + +**Table 9-1 – Start and end of message bits** + +| SoM | EoM | Meaning | +|-----|-----|------------------------------------------------------------------------------------------------------| +| 0 | 0 | Block of a multi-block message other than the first or last block | +| 0 | 1 | Last block of a multi-block message, or basic message preceding the low priority message opportunity | +| 1 | 0 | First block of a multi-block message, or basic message preceding the APS message opportunity | +| 1 | 1 | Single block message | + +#### 9.3.1.2 Message type + +Bits 2-7 of the first byte of each 66B block indicate the message type, as shown in Table 9-2. + +**Table 9-2 – MTNP OAM message types** + +| Message | | Type
(MSB.LSB) | +|---------------|------------------------------------|-------------------| +| Basic message | | 001111 | +| APS | | 010001 | +| Low priority | Connectivity verification | 110011 | +| | One-way delay measurement | 110101 | +| | Two-way delay measurement | 111001 | +| | Two-way delay measurement response | 110000 | +| | Client signal | 110110 | + +**Table 9-2 – MTNP OAM message types** + +| Message | | Type
(MSB.LSB) | +|----------|------------------------------|----------------------------------------------------------| +| | Reserved for future messages | 100001
100010
100100
101000
111010
111100 | +| Not used | | Other patterns | + +NOTE – Values not used are to maintain Hamming distance between allocated codepoints and to ensure that all low priority message types have the value 1 in the MSB. + +### 9.3.2 Basic message + +#### 9.3.2.1 Error detection code (MTN BIP) + +For path monitoring, a 1 -byte error detection code signal is defined in byte value2. The MTN bit-interleaved parity (BIP) is computed over the nominal $n \times 32K$ 66B block interval between basic messages. Since the insertion point for OAM 66B blocks is modified from the nominal position to ensure that the OAM 66B blocks are inserted between packets (see clause 8.3), the actual number of 66B blocks covered will vary. The actual number of 66B blocks covered is all 66B blocks after the previous basic message to the block immediately before the current basic message. The checksum is computed in two stages, as illustrated in Figure 9-2. The first stage computes even parity for each byte in the block and forms an 8-bit parity word from these parity bits. The second stage computes a bit interleaved parity by calculating even parity across each bit position of the nominal $n \times 32K$ parity words. The computation must ensure that any blocks that may be inserted or removed for rate adaptation (idle, LPI, local false (LF), remote false (RF) blocks) do not affect the checksum. + +NOTE – Based on the type of service being provided and the configuration of the network, some of the block types (other than idle) that can be inserted or deleted for rate adaptation may not be present in the block sequence. + +![Diagram illustrating the two-stage parity calculation process for MTN BIP across 32768 66B blocks. Stage 1: Each block (SH + Bytes 1-8) has an 8-bit per-block parity word calculated by even parity for each byte. Stage 2: The MTN BIP is calculated by even parity across each bit position (0-7) of the per-block parity words.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +The diagram shows the calculation of the MTN BIP across a nominal 32K block interval. It consists of two stages: + +- Stage 1:** For each of the 32768 66B blocks (labeled 1, 2, ..., 32768), an 8-bit per-block parity word is formed by calculating even parity for each byte in the block (SH, Byte 1 through Byte 8). This is represented by a row of 8 boxes with parity symbols (⊕). +- Stage 2:** The MTN BIP is formed by calculating even parity for each bit position (0 through 7) across all the per-block parity words. This is represented by a vertical stack of 8 boxes, one for each bit position, with parity symbols (⊕) indicating the result for each bit. + +The final output is the MTN BIP, which is an 8-bit word. The bit numbers 0 1 2 3 4 5 6 7 are shown at the bottom right. + +G.8312(20)\_F9-2 + +Diagram illustrating the two-stage parity calculation process for MTN BIP across 32768 66B blocks. Stage 1: Each block (SH + Bytes 1-8) has an 8-bit per-block parity word calculated by even parity for each byte. Stage 2: The MTN BIP is calculated by even parity across each bit position (0-7) of the per-block parity words. + +**Figure 9-2 – Parity calculation across a nominal 32K block interval** + +The MTN BIP computed for interval $i$ is inserted into basic message that follows interval $i + 2$ (see Figure 9-3). + +![Diagram showing MTN BIP insertion. Three intervals (i, i+1, i+2) are shown. Each interval contains '~n x 32K blocks' and a 'Basic message'. Arrows show the MTN BIP from the Basic message of interval i being inserted into the Basic message of interval i+2. A label 'G.8312(20)_F9-3' is present.](812e188283162af0b54fb3e30ffee51b_img.jpg) + +Diagram showing MTN BIP insertion. Three intervals (i, i+1, i+2) are shown. Each interval contains '~n x 32K blocks' and a 'Basic message'. Arrows show the MTN BIP from the Basic message of interval i being inserted into the Basic message of interval i+2. A label 'G.8312(20)\_F9-3' is present. + +**Figure 9-3 – MTN BIP insertion** + +#### 9.3.2.2 Remote defect indication + +A single bit remote defect indication (RDI) signal is defined in bit 3 of the value1 byte to convey the signal fail status detected by the MTNP termination sink in this node. + +The RDI bit is set to "1" if a defect in the received signal is detected; otherwise it is set to "0". + +#### 9.3.2.3 Remote error indication + +A four-bit remote error indication (REI) signal is defined in bits 4-7 of the value1 byte to convey the count of interleaved-bit blocks that have been detected in error. An MTNP termination sink computes the parity across each nominal 32K block interval in the same manner as the source node and compares the computed value to the value it receives from the source in the error detection code field 2 intervals later to determine the number of blocks that are in error. + +This field has nine legal values, namely zero to eight counted errors, as shown in Table 9-3. Other values can only result from some unrelated condition and are interpreted to mean zero errors. + +**Table 9-3 – REI field** + +| REI field (MSB to LSB)
7654 | Number of
counted errors | +|--------------------------------|-----------------------------| +| 0000 | 0 | +| 0001 | 1 | +| 0010 | 2 | +| 0011 | 3 | +| 0100 | 4 | +| 0101 | 5 | +| 0110 | 6 | +| 0111 | 7 | +| 1000 | 8 | + +#### 9.3.2.4 Reserved bits + +Bits 0-2 of the value1 byte are reserved. + +### 9.3.3 Low priority messages + +#### 9.3.3.1 Common elements + +##### 9.3.3.1.1 Cyclic redundancy check + +The last 12 bits of every low priority message (i.e., bits 4-7 of byte $value_{N-1}$ and bits 0-7 of byte $value_N$ ) contain a CRC-12. The CRC-12 protects the combined contents of the bits in bytes $value_1$ to $value_{N-2}$ plus the first 4 bits of byte $value_{N-1}$ as shown in Figure 9-4. The CRC field is generated using the polynomial $G(x) = x^{12} + x^{11} + x^3 + x^2 + x^1 + 1$ , with an initialization value of 0, where $x^{12}$ corresponds to the MSB and $x^0$ corresponds to the LSB. The CRC field is generated using the following mathematical steps. + +- 1) The $n$ bits of the protected field, taken in network transmission order, are considered to represent the coefficients of a polynomial $M(x)$ of degree $n - 1$ . (The first of the $n$ bits to be transmitted corresponds to the $x^{n-1}$ term.) +- 2) $M(x)$ is multiplied by $x^{12}$ and divided (modulo 2) by $G(x)$ , producing a remainder $R(x)$ of degree $n - 1$ or less. +- 3) The coefficients of $R(x)$ are considered to be a 12-bit sequence, where $x^{11}$ is the MSB. +- 4) The 12-bit sequence is the CRC-12, where the first bit of the CRC-12 to be transmitted is the coefficient of $x^{11}$ and the last bit transmitted is the coefficient of $x^0$ . + +The sink adaptation process performs steps 1-3 in the same manner as the source adaptation process, except that the $M(x)$ of step 1 includes the CRC-12 in received order and has degree $n + 12$ . In the absence of bit errors, the remainder shall be all zeros. The MTNP termination sink discards messages that have an invalid CRC. + +![Diagram of message bytes covered by a CRC. It shows a sequence of message blocks. Each block has a header with SOM and EOM flags, a Type field, and two data fields. The first block has Value1 and Value2. The second block has Value3 and Value4. A dashed line indicates intermediate blocks. The third block has Value_{N-3} and Value_{N-2}. The final block has a header with SOM and EOM flags, a Type field, a RES field, and a CRC-12 field. The CRC-12 field is split into two parts: the first part is labeled x^{11} and the second part is labeled x^0.](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +Diagram of message bytes covered by a CRC. It shows a sequence of message blocks. Each block has a header with SOM and EOM flags, a Type field, and two data fields. The first block has Value1 and Value2. The second block has Value3 and Value4. A dashed line indicates intermediate blocks. The third block has Value\_{N-3} and Value\_{N-2}. The final block has a header with SOM and EOM flags, a Type field, a RES field, and a CRC-12 field. The CRC-12 field is split into two parts: the first part is labeled x^{11} and the second part is labeled x^0. + +G.8312(20)\_F9-4 + +Figure 9-4 – Message bytes covered by a CRC + +##### 9.3.3.1.2 Reserved bits + +Bits 0-3 in the $value_{N-1}$ byte are reserved. + +#### 9.3.3.2 Connectivity verification message + +The CV message has 34 bytes. + +##### 9.3.3.2.1 Trail trace identifier + +Bytes $value_1$ to $value_{32}$ contain a 32-byte TTI as specified in clause 9.1. Each byte of the TTI is formatted LSB first into the CV message, as shown in Figure 9-5. + +![Diagram of the TTI field of a CV message. It shows a sequence of bytes. The first byte is Value1, with bits 0-7. Bit 0 is labeled LSB and bit 7 is labeled MSB. The byte is also labeled SAPI byte 0. The second byte is Value2, with bits 0-7. Bit 0 is labeled LSB and bit 7 is labeled MSB. The byte is also labeled SAPI byte 1. A dashed line indicates intermediate bytes. The 16th byte is Value16, with bits 0-7. Bit 0 is labeled LSB and bit 7 is labeled MSB. The byte is also labeled SAPI byte 15. The 17th byte is Value17, with bits 0-7. Bit 0 is labeled LSB and bit 7 is labeled MSB. The byte is also labeled DAPI byte 0. The 18th byte is Value18, with bits 0-7. Bit 0 is labeled LSB and bit 7 is labeled MSB. The byte is also labeled DAPI byte 1. A dashed line indicates intermediate bytes. The 32nd byte is Value32, with bits 0-7. Bit 0 is labeled LSB and bit 7 is labeled MSB. The byte is also labeled DAPI byte 15.](965aaf7a8b454893b05799d266de6a69_img.jpg) + +Diagram of the TTI field of a CV message. It shows a sequence of bytes. The first byte is Value1, with bits 0-7. Bit 0 is labeled LSB and bit 7 is labeled MSB. The byte is also labeled SAPI byte 0. The second byte is Value2, with bits 0-7. Bit 0 is labeled LSB and bit 7 is labeled MSB. The byte is also labeled SAPI byte 1. A dashed line indicates intermediate bytes. The 16th byte is Value16, with bits 0-7. Bit 0 is labeled LSB and bit 7 is labeled MSB. The byte is also labeled SAPI byte 15. The 17th byte is Value17, with bits 0-7. Bit 0 is labeled LSB and bit 7 is labeled MSB. The byte is also labeled DAPI byte 0. The 18th byte is Value18, with bits 0-7. Bit 0 is labeled LSB and bit 7 is labeled MSB. The byte is also labeled DAPI byte 1. A dashed line indicates intermediate bytes. The 32nd byte is Value32, with bits 0-7. Bit 0 is labeled LSB and bit 7 is labeled MSB. The byte is also labeled DAPI byte 15. + +G.8312(20)\_F9-5 + +Figure 9-5 – TTI field of a CV message + +#### 9.3.3.3 Delay measurement messages + +##### 9.3.3.3.1 Timestamp format and reference + +The format of the timestamps used in the DM messages is shown in Figure 9-6 and is based on that in [IEEE 1588]. The seconds field corresponds to the least significant 32 bits of the 48-bit seconds field of the [IEEE 1588] format. The nanoseconds field corresponds to the nanosecondsField of the [IEEE 1588] format. + +![Figure 9-6: Timestamp format diagram. It shows a 64-bit timestamp divided into two 32-bit fields: Nanoseconds and Seconds. Each field consists of four bytes. The Nanoseconds field contains bytes Value_i (LSB) through Value_{i+3} (MSB). The Seconds field contains bytes Value_{i+4} (LSB) through Value_{i+7} (MSB). Each byte shows bit positions 0 to 7.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------|-------------|--|--|--|--|--|--|-----|-----------------|--|--|--|--|--|--|-----|-----------------|---------|--|--|--|--|--|--|-----|-----------------|--|--|--|--|--|--|-----| +| 0 1 2 3 4 5 6 7 | | | | | | | | | 0 1 2 3 4 5 6 7 | | | | | | | | 0 1 2 3 4 5 6 7 | | | | | | | | | 0 1 2 3 4 5 6 7 | | | | | | | | +| $Value_i$ | | | | | | | | ... | $Value_{i+3}$ | | | | | | | | $Value_{i+4}$ | | | | | | | | ... | $Value_{i+7}$ | | | | | | | | +| LSB | Nanoseconds | | | | | | | | | | | | | | | MSB | LSB | Seconds | | | | | | | | | | | | | | | MSB | + +Figure 9-6: Timestamp format diagram. It shows a 64-bit timestamp divided into two 32-bit fields: Nanoseconds and Seconds. Each field consists of four bytes. The Nanoseconds field contains bytes Value\_i (LSB) through Value\_{i+3} (MSB). The Seconds field contains bytes Value\_{i+4} (LSB) through Value\_{i+7} (MSB). Each byte shows bit positions 0 to 7. + +**Figure 9-6 – Timestamp format** + +The timestamp values used in the DM messages are referenced to the time at which the first block of the low priority message sequence in Table 8-2 (i.e., the first block of the CV message) is transmitted or received. + +###### 9.3.3.3.2 One-way delay measurement + +The 1DM message has 10 value bytes. Bytes $value_1$ to $value_8$ contain the timestamp indicating the time at which the first block of the low priority message sequence containing the 1DM was transmitted (Tx-f-TS in Figure 8-3). + +The sink node compares the timestamp in the 1DM message to the time at which it received the first block of the low priority message sequence to compute the one-way delay. + +##### 9.3.3.3.3 Two-way delay measurement + +The 2DMM message has 10 value bytes. Bytes $value_1$ to $value_8$ contain the timestamp indicating the time at which the first block of the low priority message sequence containing the 2DMM was transmitted (Tx-f-TS in Figure 8-3). + +###### 9.3.3.3.4 Two-way delay measurement response message + +The 2DMR message has 26 value bytes. + +Bytes $value_1$ to $value_8$ contain the time stamp that was received in the Tx-f-TS field of the 2DMM message (Tx-f-TS in Figure 8-4). + +Bytes $value_9$ to $value_{16}$ contain the time stamp indicating when the first block of the low priority message sequence that contained the 2DMM was received (Rx-f-TS in Figure 8-4) by the node transmitting the 2DMR. + +Bytes $value_{17}$ to $value_{24}$ contain the timestamp indicating when the first block of the low priority message sequence that includes the 2DMR was transmitted (Tx-b-TS in Figure 8-4). + +The node that receives the 2DMR uses the three timestamps in the 2DMR message, plus the timestamp indicating the time at which the first block of the low priority message sequence that contains the 2DMR was received, to compute the delay. + +#### 9.3.3.5 Client signal type message + +The CS type message has two value bytes (see Figure 8-5). + +##### 9.3.3.5.1 Payload type indication + +Bits 0-1 of byte $value_1$ indicate the payload being carried by the MTNP. The possible values are shown in Table 9-3. + +**Table 9-3 – Payload type code points** + +| PT value (MSB.LSB) | Interpretation | +|---------------------------|-----------------------| +| 10 | | +| 00 | Reserved | +| 01 | Ethernet | +| 10 | Test signal | +| 11 | Reserved | + +##### **9.3.3.5.2 Reserved bits** + +Bits 2-3 of byte value1 are reserved. + +### **9.3.4 APS message** + +The APS message has four value bytes. + +#### **9.3.4.1 APS protocol** + +Bytes value1 and value2 carry the APS protocol. The details of the APS protocol lie outside the scope of this Recommendation. + +#### **9.3.4.2 Reserved bits and CRC-12** + +Bytes value3 and value4 carry the same common elements as low priority messages; see clause 9.3.3.1. + +# **10 MTN maintenance signals** + +## **10.1 MTNS maintenance signals** + +There are no maintenance signals specified for the MTNS layer. + +## **10.2 MTNP maintenance signals** + +### **10.2.1 Alarm indication signal** + +An MTNP alarm indication signal (AIS) is inserted as a continuous sequence of LF ordered sets (as specified in [IEEE 802.3]) at the nominal bit rate of the MTNP. At the MTNP termination sink, the signal may also include idle blocks that have been inserted by rate adaptation processes. + +### **10.2.2 Open connection indication** + +An MTNP OCI is a repeating sequence of 32 66B blocks at the nominal bit rate of the MTNP. The block sequence contains 31 /E/ blocks followed by an idle block. At the MTNP termination sink, the signal may have a different pattern due to rate adaptation that adds or removes idle blocks. + +# **11 MTN client mappings** + +## **11.1 Ethernet MAC based clients** + +Ethernet MAC frames can be carried over an MTNP as follows. + +Mapping the sequence of Ethernet MAC frame CSs to the MTNP layer is performed by encoding each MAC frame plus the interpacket gap into a sequence of 64B/66B blocks as specified in clauses 81 and 82.2.4 of [IEEE 802.3]. Each encoded MAC frame is bounded by a start (S) control block and a terminal (T) control block as shown in Figure 11-1. + +![Diagram of MTNP AI signal with mapped Ethernet MAC frame client. It shows two sequences of blocks. Each sequence starts with an optional Idle control block (I), followed by a Start control block (S), then 12 Data blocks (D), then a Terminal control block (T), and ends with an optional Idle control block (I). The blocks are represented by boxes: solid for S, T, and D, and dashed for I. Ellipses (...) are shown at the beginning and end of the sequences. A legend below the diagram identifies the blocks: S for Start control block, T for Terminal control block, D for Data block, and I for (Optional) Idle control block. The text 'G.8312(20)_F11-1' is in the bottom right corner.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +... [ I [ S [ D [ D [ D [ D [ D [ D [ D [ D [ D [ D [ T [ I ] ... [ I [ S [ D [ D [ D [ D [ D [ D [ D [ D [ D [ D [ T [ I ] ... + +[ S ] Start control block    [ T ] Terminal control block    [ D ] Data block    [ I ] (Optional) Idle control block    G.8312(20)\_F11-1 + +Diagram of MTNP AI signal with mapped Ethernet MAC frame client. It shows two sequences of blocks. Each sequence starts with an optional Idle control block (I), followed by a Start control block (S), then 12 Data blocks (D), then a Terminal control block (T), and ends with an optional Idle control block (I). The blocks are represented by boxes: solid for S, T, and D, and dashed for I. Ellipses (...) are shown at the beginning and end of the sequences. A legend below the diagram identifies the blocks: S for Start control block, T for Terminal control block, D for Data block, and I for (Optional) Idle control block. The text 'G.8312(20)\_F11-1' is in the bottom right corner. + +**Figure 11-1 – MTNP AI signal with mapped Ethernet MAC frame client** + +De-mapping is performed by decoding the sequences of 64B/66B blocks bounded by an S control block and a T control block to MAC frames as specified in clauses 82.2.17 and 81 of [IEEE 802.3]. + +The MTNP client sequence of Ethernet MAC frames may be an aggregation from multiple UNI interfaces, which terminate any link status indications. + +# Appendix I + +## Background on error marking in MTN + +(This appendix does not form an integral part of this Recommendation.) + +## I.1 Error marking + +For [IEEE 802.3] PHYs with FEC, four 64B/66B blocks are transcoded into one 256B/257B block before FEC encoding on the transmit side and transcoded back into 64B/66B blocks on the receiver side after FEC decoding. The 257B blocks are aggregated into FEC codewords based on the FEC algorithm that is used. When the FEC decoder fails to correct errors in a FEC codeword, [IEEE 802.3] specifies that some or all of the 64B/66B blocks that are transcoded out of the 256B/257B blocks in that FEC codeword will be marked with invalid synchronization headers (0b11). In the case of 50G and 100G PHYs, not every 66B block is marked. The error marking specified in [IEEE 802.3] is designed to ensure that every packet that has a 66B block in the uncorrected FEC code word has at least one 66B block with an invalid synchronization header, under the assumption that there is a single MAC associated with the PHY. The specific pattern of error marking is designed to avoid triggering the BER monitoring state machine (which will bring the link down) in Figure 82-15 of [IEEE 802.3] in response to a single uncorrectable FEC codeword. At the 66B decoder, blocks with invalid synchronization headers are replaced with /E/ characters, which causes the packet to be discarded. + +MTNS uses the calendar slot structure specified in [OIF FLEXE IA] to channelize the PHY(s) to support multiple MTNP, each of which is a carrying a separate MAC client. Since the error marking specified in [IEEE 802.3] for 50G and 100G PHYs with FEC is not designed for this application, it may not mark at least one block in every packet that is affected by a FEC codeword with uncorrected errors. The additional error marking specified in clause 7.3 ensures that every packet is error marked in a manner that is consistent with what [IEEE 802.3] would do. Because this additional error marking would trigger the BER monitoring state machine, that state machine must be disabled. [IEEE 802.3] also specifies that a link is brought down if there are three consecutive uncorrectable FEC codewords; this behaviour will ensure that persistent bit errors still bring the link down even though the BER monitoring state machine is disabled. + +## I.2 Error contamination due to 66B block forwarding + +MTN supports switching of the MTNP layer as a sequence of 66B blocks. When links with FEC are used, this requires the switching node to transcode incoming 256B/257B blocks to recover an MTNP 66B block Sequence, and after switching, transcode that sequence into an egress 256B/257B block that it may share with 66B block sequences from other MTNPs. [IEEE 802.3] specifies that if any 66B block used to form a 257B block has a corrupted synchronization header when the 257B block is transcoded back to four 66B blocks, all four 66B blocks that are re-created will have their synchronization header corrupted. Because of this behaviour, switching a block that has been marked (i.e., with a corrupted synchronization header) to another interface and then subsequently transcoding that block can lead to contamination of other MTNPs. Figure I.1 shows the formation of a 257B block from 66B blocks that originate from multiple MTNPs where one of the MTNPs contains a corrupted block. When this 257B block is transcoded back to the individual 66B blocks, all four of the blocks will be error marked. This situation is avoided in MTN by replacing all error-marked blocks with /E/ blocks. + +![Diagram illustrating the formation of a 257B block from multiple sources. A horizontal bar is divided into four segments labeled A, B, C, and D. Segment C is shaded black. An arrow from the text 'Stream from an interface with an uncorrectable FEC codeword' points to segment C. Three arrows from the text 'Streams from other interfaces that are error free' point to segments A, B, and D respectively.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +Stream from an interface with an uncorrectable FEC codeword + +Streams from other interfaces that are error free + +G.8312(20)\_FI.1 + +Diagram illustrating the formation of a 257B block from multiple sources. A horizontal bar is divided into four segments labeled A, B, C, and D. Segment C is shaded black. An arrow from the text 'Stream from an interface with an uncorrectable FEC codeword' points to segment C. Three arrows from the text 'Streams from other interfaces that are error free' point to segments A, B, and D respectively. + +**Figure I.1 – Illustration of forming a 257B block from multiple sources** + + + + + +# 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.8331-202202-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/G/T-REC-G.8331-202202-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e32f9b8f1141bed243c16e02a6cd1411cbb87f1 --- /dev/null +++ b/marked/G/T-REC-G.8331-202202-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.8331-202202-I_PDF-E/raw.md b/marked/G/T-REC-G.8331-202202-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..03611505a32ca2027c94daf9206a9f6acc6df7ab --- /dev/null +++ b/marked/G/T-REC-G.8331-202202-I_PDF-E/raw.md @@ -0,0 +1,498 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.8331** + +(02/2022) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Packet over Transport aspects – Mobile network transport +aspects + +# --- **Metro transport network linear protection** + +Recommendation ITU-T G.8331 + +## 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.831 + +# Metro transport network linear protection + +# Summary + +Recommendation ITU-T G.831 defines the operation of linear protection switching schemes for the metro transport network path layer, including the automatic protection switching (APS) protocol. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.831 | 2022-02-13 | 15 | 11.1002/1000/14916 | + +## Keywords + +APS, linear protection, MTN. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2022 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 2 | +| 6 | Protection architecture and characteristics ..... | 2 | +| 6.1 | Architecture class ..... | 2 | +| 6.2 | Architecture types..... | 3 | +| 6.3 | Switching types ..... | 3 | +| 6.4 | Operation types..... | 3 | +| 6.5 | Protection switching trigger ..... | 3 | +| 7 | Protection group commands ..... | 3 | +| 8 | Automatic protection switching protocol ..... | 3 | +| 8.1 | Automatic protection switching – specific information format ..... | 3 | +| 8.2 | Principle of 1-phase APS operation ..... | 4 | +| 8.3 | Revertive mode..... | 4 | +| 8.4 | Non-revertive mode..... | 5 | +| 8.5 | Transmission and acceptance of APS protocol ..... | 5 | +| 8.6 | Request type ..... | 5 | +| 8.7 | Protection types ..... | 6 | +| 8.8 | Requested signal..... | 6 | +| 8.9 | Bridged signal..... | 6 | +| 8.10 | Control of bridge ..... | 6 | +| 8.11 | Control of selector ..... | 6 | +| 8.12 | Signal Fail of the protection transport entity ..... | 6 | +| 8.13 | Equal priority requests..... | 6 | +| 8.14 | Command acceptance and retention..... | 7 | +| 8.15 | Hold-off timer..... | 7 | +| 8.16 | Wait-to-restore timer ..... | 7 | +| 8.17 | Exercise operation ..... | 7 | +| 8.18 | Failure of protocol defects..... | 7 | +| | Appendix I – Network objectives ..... | 9 | +| | Appendix II – Operation example of MTN linear protection protocol..... | 10 | +| | Bibliography..... | 11 | + + + +# Recommendation ITU-T G.831 + +# Metro transport network linear protection + +# 1 Scope + +This Recommendation defines the operation of 1+1 end-to-end uni/bidirectional linear protection switching schemes for the metro transport network (MTN) path layer, including the automatic protection switching (APS) protocol. The mechanism is based on the generic linear protection specifications in [ITU-T G.808.1]. + +# 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.800] Recommendation ITU-T G.800 (2016), *Unified functional architecture of transport networks*. +- [ITU-T G.808] Recommendation ITU-T G.808 (2016), *Terms and definitions for network protection and restoration*. +- [ITU-T G.808.1] Recommendation ITU-T G.808.1 (2014), *Generic protection switching - Linear trail and subnetwork protection*. +- [ITU-T G.8312] Recommendation ITU-T G.8312 (2020), *Interfaces for the metro transport network*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **1+1 (protection) architecture** [ITU-T G.808] +- 3.1.2 **active transport entity** [ITU-T G.808] +- 3.1.3 **APS protocol: 1-phase** [ITU-T G.808] +- 3.1.4 **bridge** [ITU-T G.808] +- 3.1.5 **forwarding end point** [ITU-T G.800] +- 3.1.6 **head-end** [ITU-T G.808] +- 3.1.7 **hold-off timer** [ITU-T G.808.1] +- 3.1.8 **non-revertive (protection) operation** [ITU-T G.808] +- 3.1.9 **normal traffic signal** [ITU-T G.808] +- 3.1.10 **null signal** [ITU-T G.808] +- 3.1.11 **permanent bridge** [ITU-T G.808] +- 3.1.12 **protected domain** [ITU-T G.808] + +- 3.1.13 protection class: individual** [ITU-T G.808] +- 3.1.14 protection class: trail-protection** [ITU-T G.808] +- 3.1.15 protection group** [ITU-T G.808] +- 3.1.16 protection transport entity** [ITU-T G.808] +- 3.1.17 revertive (protection) operation** [ITU-T G.808] +- 3.1.18 selector** [ITU-T G.808] +- 3.1.19 tail-end** [ITU-T G.808] +- 3.1.20 working transport entity** [ITU-T G.808] + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|--------------------------------| +| APS | Automatic Protection Switching | +| CRC | Cyclic Redundancy Check | +| DNR | Do Not Revert | +| EXER | Exercise | +| FS | Forced Switch | +| FwEP | Forwarding End Point | +| LO | LOckout of protection | +| MS | Manual Switch | +| MTN | Metro Transport Network | +| MTNP | Metro Transport Network Path | +| NR | No Request | +| SD | Signal Degrade | +| SF | Signal Fail | +| WTR | Wait-To-Restore | + +# **5 Conventions** + +None. + +# **6 Protection architecture and characteristics** + +## **6.1 Architecture class** + +In the metro transport network (MTN) path (MTNP), protection is end-to-end and individual trail protection is supported. For a description of individual trail protection, refer to clause 11.1.1 of [ITU-T G.808.1]. + +## 6.2 Architecture types + +MTNP provides 1+1 protection architecture as described in clause 7.1 of [ITU-T G.808.1]. + +## 6.3 Switching types + +MTNP provides both unidirectional and bidirectional switching as described in clause 8 of [ITU-T G.808.1]. + +## 6.4 Operation types + +MTNP linear protection supports both non-revertive and revertive operation types. For descriptions of non-revertive and revertive operation types, refer to clause 9 of [ITU-T G.808.1]. + +## 6.5 Protection switching trigger + +Protection switching action shall be invoked when any of the following conditions apply: + +- Operator control (e.g., Manual Switch (MS), Forced Switch (FS) and Lockout of protection (LO)) is initiated without a higher priority switch request being in effect; +- Signal Fail (SF) or Signal Degrade (SD) is declared on the active transport entity and the hold-off timer has expired, and any higher priority switch request is not in effect; +- A Wait-to-Restore (WTR) timer expires (in revertive operation) without a higher priority switch request being in effect; +- The received APS signal requests to switch and has a higher priority than any other local request. + +### 6.5.1 Signal fail declaration conditions + +SF is declared when the MTNP signal fail condition is detected. + +### 6.5.2 Signal degrade declaration conditions + +SD is declared when the MTNP signal degrade condition is detected. + +# 7 Protection group commands + +Protection group commands, such as LO, FS, MS, Exercise (EXER), Clear, Freeze, and Clear freeze, are provided as described in clause 19 of [ITU-T G.808.1]. + +# 8 Automatic protection switching protocol + +## 8.1 Automatic protection switching – specific information format + +The APS-specific information is carried over two APS bytes in an APS message. The format of the APS message is defined in [ITU-T G.832]. The APS-specific information received from the far end is accepted only when the received APS message contains a correct cyclic redundancy check (CRC). The format of the APS-specific information within each APS message is defined in Figure 8-1. + +| APS1 | | | | | | | | APS2 | | | | | | | | +|-------------------|---|---|---|------------|---|---|---|---------------------|---|---|---|-------------------|---|---|---| +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| Request/
state | | | | Prot. Type | | | | Requested
signal | | | | Bridged
signal | | | | +| | | | | A | B | D | R | | | | | | | | | + +Figure 8-1 – APS-specific information format + +Table 8-1 describes code points and values for the APS-specific information. + +**Table 8-1 – Code points and field values** + +| | | | | +|------------------|--------|----------------------------------|-----------------------------------------------| +| Request/State | 1111 | Lockout of protection (LO) | Highest priority | +| | 1110 | Signal Fail on Protection (SF-P) | ↑








| +| | 1101 | Forced Switch (FS) | | +| | 1011 | Signal Fail on Working (SF-W) | | +| | 1001 | Signal Degrade (SD) | | +| | 0111 | Manual Switch (MS) | | +| | 0101 | Wait-to-Restore (WTR) | | +| | 0100 | Exercise (EXER) | | +| | 0010 | Reverse Request (RR) | | +| | 0001 | Do Not Revert (DNR) | | +| | 0000 | No Request (NR) | Lowest priority | +| | Others | Reserved | | +| Protection type | A | 0 | No APS channel | +| | | 1 | APS channel | +| | B | 0 | 1+1 (permanent bridge) | +| | | 1 | Reserved | +| | D | 0 | Unidirectional switching | +| | | 1 | Bidirectional switching | +| | R | 0 | Non-revertive operation | +| | | 1 | Revertive operation | +| | | 0 | Null signal | +| | | 1 | Normal traffic signal | +| Requested signal | | 2-15 | Reserved | +| Bridged signal | | 0 | Reserved | +| | | 1 | Normal traffic signal | +| | | 2-15 | Reserved | + +For the protection architectures defined in this Recommendation, a 1-phase APS is used. + +## 8.2 Principle of 1-phase APS operation + +1-phase APS Protocol is defined in [ITU-T G.808]. The 1+1 linear protection switching algorithm is performed in network elements at both ends of a protected domain. Bidirectional switching is achieved by transmitting local switching requests to the far end via the "Request/State" in the first octet (APS1) of the APS-specific information (see Figure 8-1). The transmitted "Requested Signal" and "Bridged Signal" in the second octet (APS2) of the APS-specific information contain the local bridge/selector status information; a persistent mismatch between both ends may thus be detected and leads to an alarm. + +## 8.3 Revertive mode + +In the revertive mode of unidirectional protection switching operation, in conditions where normal traffic signal is being received via the protection transport entity, if local protection switching requests have been previously active and now become inactive, a local WTR state is entered. Since this state + +now represents the highest priority local request, it is indicated on the transmitted "Request/State" information and maintains the switch. + +In the case of bidirectional protection switching, a local WTR state is entered only when there is no higher priority of request received from the far end than that of the WTR state. + +This state normally times out and becomes a No Request (NR) state after the WTR timer has expired. The WTR timer is deactivated earlier if any local request of higher priority pre-empts this state. + +A switch to the protection transport entity may be maintained by a local WTR state or by a remote request (WTR or other) received via the "Request/State" information. Therefore, in a case where a bidirectional failure for the working transport entity has occurred and subsequent repair has taken place, the bidirectional reversion back to the working transport entity does not take place until WTR timers at both ends have expired. + +## **8.4 Non-revertive mode** + +In non-revertive mode of unidirectional protection switching operation, in conditions where normal traffic signal is being transmitted via the protection transport entity, if local protection switching requests have been previously active and now become inactive, a local Do Not Revert (DNR) state is entered. This state is indicated on the transmitted "Request/State" information and maintains the switch, thus preventing reversion back to the released selector position in non-revertive mode under NR conditions. + +In the case of bidirectional protection switching operation, a local DNR state is entered when there is no higher priority of request received from the far end than that of the DNR state, or when both the local state and far-end state are NR with the requested signal number 1. + +## **8.5 Transmission and acceptance of APS protocol** + +The APS messages are transported via the protection transport entity only, being inserted by the head-end of the protected domain and extracted by the tail-end of the protected domain. Although it may also be transmitted identically on the working transport entity, receivers should not assume so and should have the capability to ignore this information on the working transport entity. + +The APS messages are transmitted in every "A" opportunity within the BABL block insertion pattern defined in [ITU-T G.8312]. Note that the APS message consists of two 66B blocks, and complete messages are always transmitted; if the APS status changes during the transmission of a message, the status is updated in the next message. + +If no valid APS-specific information is received, the last valid received information remains applicable except in case of SF condition on the protection transport entity. + +## **8.6 Request type** + +The request types reflect the highest priority condition, command or state. In the case of unidirectional switching, this is the highest priority value determined from the near end only. In bidirectional switching, the sent "Request/State" shall indicate: + +- a) A reverse request (RR) if one of the following applies: + - I. the remote request is of higher priority; + - II. the requests are of the same level (and are higher priority than a NR/DNR) and the sent "Request/State" already indicates RR; + - III. the requests are of the same level (and are higher priority than a NR/DNR) and the sent "Request/State2" information does not indicate RR and the remote request indicates a lower requested signal number. +- b) The local request in all other cases. + +## 8.7 Protection types + +The valid configurations of the protection type are as specified below: + +- 000x: 1+1 unidirectional, no APS +- 100x: 1+1 unidirectional w/APS +- 101x: 1+1 bidirectional w/APS + +The default value for the protection type is all zeros, i.e., ABDR = 0b0000. Note that when the protection type has the default value, no APS messages are sent. + +If the "B" bit mismatches, the selector is released. This will result in a defect. + +Provided the "B" bit matches: + +- a) If the "A" bit mismatches, the side expecting APS will fall back to 1+1 unidirectional switching without APS communication; +- b) If the "D" bit mismatches, the bidirectional side will fall back to unidirectional switching; +- c) If the "R" bit mismatches, one side will clear switches to "WTR" and the other will clear to "DNR". The two sides will interwork and the traffic is protected; + +## 8.8 Requested signal + +This indicates the signal that the near-end requests be carried over the protection transport entity. + +For NR and LO, this can only be the null signal (0). For Exercise, this can be the null signal (0) when Exercise replaces NR, or the normal traffic signal (1) in the case where Exercise replaces DNR. For SF or SD, this will be the normal traffic signal, or the null signal to indicate that protection is failed or degraded. For all other requests, this will be the normal traffic signal requested to be carried over the protection transport entity. + +## 8.9 Bridged signal + +This indicates the signal that is bridged onto the protection transport entity. For 1+1 protection, the value of this field is always "1" to indicate the normal traffic signal. + +## 8.10 Control of bridge + +In 1+1 architectures, the normal traffic signal is permanently bridged to the protection transport entity. + +## 8.11 Control of selector + +In 1+1 unidirectional architectures (with or without APS communication), the selector is set entirely according to the highest priority local request. + +In 1+1 bidirectional architectures, the normal traffic signal will be selected from the protection transport entity when the outgoing "Requested Signal" indicates the normal traffic signal. + +## 8.12 Signal Fail of the protection transport entity + +Signal fail on the protection transport entity (SF-P) is higher priority than any defect that would cause the normal traffic signal to be selected from the protection transport entity. For a case when an APS signal is in use, a SF on the protection transport entity (over which the APS signal is routed) has priority over the FS. LO command has higher priority than SF-P; during failure conditions, lockout status is kept active. + +## 8.13 Equal priority requests + +In general, once a switch has been completed due to a request, it will not be overridden by another request of the same priority (first come, first served behaviour). When equal priority requests occur + +simultaneously, the conflict is resolved in favour of the request with the lower requested signal number. For a 1+1 protection architecture, this is relevant only when APS messages are enabled and for bidirectional switching. For example, SD for the null signal is considered to have higher priority than SD for the normal traffic signal, resulting in both tail-ends selecting the working transport entity. In 1+1 bidirectional switching, a request received over the APS channel with the null signal will always override an identical priority local request with the normal traffic signal. Equal priority requests for the same requested signal number from both sides of a bidirectional protection group are both considered valid, and equivalent to a received "RR" from a near-end processing standpoint. + +## 8.14 Command acceptance and retention + +The commands Clear, LO, FS, MS and EXER are accepted or rejected in the context of previous commands, the condition of the working and protection transport entities in a protection group, and (in bidirectional switching only) the received APS information. + +The Clear command is only valid if a near-end LO, FS, MS, or EXER command is in effect, or if a WTR state is present at the near end and rejected otherwise. This command will remove the near-end command or WTR state, allowing the next lower priority condition or (in bidirectional switching) APS request to be asserted. + +Other commands are rejected unless they are higher priority than the previously existing command, condition or (in bidirectional switching) APS request. If a new command is accepted, any previous, lower priority command that is overridden is forgotten. If a higher priority command overrides a lower priority condition or (in bidirectional switching) APS request, that other request will be reasserted if it still exists at the time the command is cleared. + +If a command is overridden by a condition or (in bidirectional switching) APS request, that command is forgotten. + +## 8.15 Hold-off timer + +A hold-off timer as defined in [ITU-T G.808.1] is supported. The value is configurable with a suggested range of 0 to 10 seconds in steps of 100 ms (accuracy of $\pm 5$ ms).1 + +## 8.16 Wait-to-restore timer + +A WTR timer as defined in [ITU-T G.808.1] is supported. The value is configurable with a suggested range of 5 to 12 minutes in steps of 1 minute. The default is 5 minutes. + +## 8.17 Exercise operation + +An Exercise command as defined in [ITU-T G.808.1] is supported. In 1-phase APS protocol, the valid response will be an RR with the corresponding requested and bridged signal numbers. When Exercise commands are input at both ends, an EXER, instead of RR, is transmitted from both ends. The standard response to DNR should be DNR rather than NR. When the exercise command is cleared, it will be replaced with NR or RR if the requested signal number is 0, and DNR or RR if the requested signal number is 1. + +## 8.18 Failure of protocol defects + +"Failure of protocol" situations for protection types requiring APS are as follows: + +- a) Fully incompatible provisioning (the "B" bit mismatch, described in clause 8.7); +- b) No match in sent "Requested Signal" and received "Requested Signal" in case of bidirectional switching for $> 50$ ms; + +--- + +1 There is no lower layer protection in MTN (i.e., no MTNS protection) and MTNP protection is end-to-end (i.e., no upstream path layer protection), so a hold-off timer value greater than 0 may not be needed. + +- c) Three consecutive APS messages are not received when there are no defects on the protection transport entity. + +Fully incompatible provisioning is detected by receiving only one APS message. + +If an unknown request or a request for an invalid signal number is received, it will be ignored. + +# Appendix I + +## Network objectives + +(This appendix does not form an integral part of this Recommendation.) + +The MTN linear protection mechanism protects path layer channels end-to-end. The protection mechanism should meet the following network objectives: + +- 1) MTN linear protection switching should be applicable to a MTNP, which provides connectivity between two forwarding end points (FwEP). Additional detail on the MTNP layer and related atomic functions can be obtained from [b-ITU-T G.8310]. Other entities to be protected are for further study. +- 2) The protection transport entity should be configured such that 100 per cent of the impaired normal traffic signal should be protected for a failure on a single working channel. +- 3) The transfer time $T_t$ , as defined in [ITU-T G.808], shall not exceed 50 ms. +- 4) The path layer working transport entity and protection transport entity should be periodically monitored. +- 5) Subsequent to a protection switching event, 66B blocks should be delivered in order. +NOTE – Subsequent to a protection switching event, 66B blocks may temporarily be lost or duplicated due to differential path delay. +- 6) Revertive and non-revertive switching should be provided as network operator options. +- 7) A mismatch between the bridge/selector positions of the near end and the far end should be detected. + - The bridge/selector mismatch for the local network element should be detected and reported. + - The bridge/selector mismatch should be cleared by a network operator action. +- 8) Operator requests such as LO, FS and MS commands should be supported. +- 9) Prioritized protection between SF and operator requests should be supported. +- 10) A provisionable "generic hold-off function" should be provided so as to delay the beginning of the protection switching action. +- 11) The path layer linear protection should not affect the switching action in other layers. + +# **Appendix II** + +# **Operation example of MTN linear protection protocol** + +(This appendix does not form an integral part of this Recommendation.) + +Operation examples of 1+1 unidirectional switching (Figure I.1) and 1+1 bidirectional switching (Figure I.2) shown in Appendix I of [ITU-T G.873.1] are applied to MTN linear protection. + +# Bibliography + +[b-ITU-T G.8310] Recommendation ITU-T G.8310 (2020), *Architecture of the metro transport network*. + + + + + +# 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.8371-202507-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.8371-202507-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/G/T-REC-G.8371-202507-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.8371-202507-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/G/T-REC-G.8371-202507-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18df2ab3d3bd8939024276bc76307770250e4d3a --- /dev/null +++ b/marked/G/T-REC-G.8371-202507-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b40495d540767a4d718103d4ed5625ecac2877c6d98c99e4ffe4c62de2be9110 +size 39695 diff --git a/marked/G/T-REC-G.8371-202507-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/G/T-REC-G.8371-202507-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..272468ef4ac07d6fa4ad881998c479cdc6a69228 --- /dev/null +++ b/marked/G/T-REC-G.8371-202507-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:088f049681bf00917af039ebb36130abecdcc90a54d1f497ac3ac69d8a895942 +size 44742 diff --git a/marked/G/T-REC-G.8371-202507-I_PDF-E/raw.md b/marked/G/T-REC-G.8371-202507-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5e9379a6ff99af742fff3bb2e6d52a2a946c0910 --- /dev/null +++ b/marked/G/T-REC-G.8371-202507-I_PDF-E/raw.md @@ -0,0 +1,334 @@ + + +# Recommendation **ITU-T G.831 (07/2025)** + +SERIES G: Transmission systems and media, digital systems and networks + +Packet over Transport aspects – Mobile network transport aspects + +--- + +## **Synchronization aspects of metro transport network** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +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.8371 + +## Synchronization aspects of metro transport network + +## Summary + +Recommendation ITU-T G.8371 describes the synchronization function of metro transport network (MTN) equipment and network in order to meet the frequency, phase and time requirement of IMT-2020/5G wireless applications. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.8371 | 2025-07-22 | 15 | 11.1002/1000/16326 | + +## Keywords + +MTN, time synchronization. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 General..... | 3 | +| 7 MTN synchronization requirements ..... | 3 | +| 8 MTN synchronization architecture ..... | 4 | +| 9 MTN synchronization solution requirements ..... | 4 | +| 9.1 MTN synchronization messaging channel and encapsulation..... | 4 | +| 9.2 Timestamp generation for MTN..... | 5 | +| 9.3 PTP profile for MTN ..... | 6 | +| 9.4 MTN synchronization network limit ..... | 6 | +| 9.5 MTN clock specification ..... | 6 | + + + +# Recommendation ITU-T G.8371 + +## Synchronization aspects of metro transport network + +## 1 Scope + +This Recommendation covers the synchronization aspects of metro transport network (MTN) transport network, including MTN synchronization requirements, aspects of MTN synchronization architecture, requirements on MTN synchronization messaging encapsulation, requirements on timestamp generation, and PTP profiles for MTN. This Recommendation includes the physical layer frequency synchronization and the PTP phase/time synchronization. + +NOTE – Synchronization aspects related to the transport of CBR over fgMTN are for further study. + +# 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.781](#)] Recommendation ITU-T G.781 (2024), *Synchronization layer functions for frequency synchronization based on the physical layer*. +- [[ITU-T G.810](#)] Recommendation ITU-T G.810 (1996), *Definitions and terminology for synchronization networks*. +- [[ITU-T G.8260](#)] Recommendation ITU-T G.8260 (2022), *Definitions and terminology for synchronization in packet networks*. +- [[ITU-T G.8261](#)] Recommendation ITU-T G.8261/Y.1361 (2019), *Timing and synchronization aspects in packet networks*. +- [[ITU-T G.8262.1](#)] Recommendation ITU-T G.8262.1/Y.1362.1 (2022), *Timing characteristics of enhanced synchronous equipment slave clock*. +- [[ITU-T G.8264](#)] Recommendation ITU-T G.8264/Y.1364 (2017), *Distribution of timing information through packet networks*. +- [[ITU-T G.8271.1](#)] Recommendation ITU-T G.8271.1/Y.1366.1 (2022), *Network limits for time synchronization in packet networks with full timing support from the network*. +- [[ITU-T G.8272](#)] Recommendation ITU-T G.8272 (2025), *Timing characteristics of primary reference time clocks*. +- [[ITU-T G.8272.1](#)] Recommendation ITU-T G.8272.1 (2024), *Timing characteristics of enhanced primary reference time clocks*. +- [[ITU-T G.8273.2](#)] Recommendation ITU-T G.8273.2/Y.1368.2 (2023), *Timing characteristics of telecom boundary clocks and telecom time synchronous clocks for use with full timing support from the network*. +- [[ITU-T G.8275.1](#)] Recommendation ITU-T G.8275.1/Y.1369.1 (2022), *Precision time protocol telecom profile for phase/time synchronization with full timing support from the network*. + +- [ITU-T G.8300] Recommendation ITU-T G.8300 (2020), *Characteristics of transport networks to support IMT-2020/5G*. +- [ITU-T G.8310] Recommendation ITU-T G.8310 (2020), *Architecture of the metro transport network*. +- [ITU-T G.8312] Recommendation ITU-T G.8312 (2020), *Interfaces for metro transport networks*. +- [ITU-T G.8312.20] Recommendation ITU-T G.8312.20 (2024), *Overview of fine grain MTN*. +- [ITU-T G.8321] Recommendation ITU-T G.8321 (2022), *Characteristics of metro transport network equipment functional blocks*. +- [ITU-T G.8331] Recommendation ITU-T G.8331 (2022), *Metro transport network linear protection*. +- [ITU-T G.8350] Recommendation ITU-T G.8350 (2022), *Management and control of metro transport networks*. +- [OIF FLEXE IA] Optical Internetworking Forum, IA Flex Ethernet 2.2 (2021), *Implementation agreement*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +Terms related to synchronization are defined in [ITU-T G.810] and [ITU-T G.8260]. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|--------------------------------------------| +| 1PPS | One Pulse Per Second | +| C-RAN | Centralized Radio Access Network | +| DM | Delay Measurement | +| D-RAN | Distributed Radio Access Network | +| ePRC | Enhanced Primary Reference Clock | +| ePRTC | Enhanced Primary Reference Time Clock | +| ESMC | Ethernet Synchronization Messaging Channel | +| FlexE | Flex Ethernet | +| GNSS | Global Navigation Satellite System | +| MTN | Metro Transport Network | +| MTNS | MTN Section | +| PHY | Physical layer entity | +| PMA | Physical Medium Attachment | +| PRC | Primary Reference Clock | + +| | | +|-------|-------------------------------------| +| PRTC | Primary Reference Time Clock | +| PTP | Precision Time Protocol | +| SSM | Synchronization Status Message | +| SyncE | Synchronous Ethernet | +| T-BC | Telecom Boundary Clock | +| T-GM | Telecom Grandmaster | +| TOD | Time of Day | +| TR | TimeReceiver or TIME_RECEIVER | +| TT | TimeTransmitter or TIME_TRANSMITTER | +| T-TSC | Telecom Time Synchronous Clock | + +## 5 Conventions + +None. + +# 6 General + +MTN (metro transport network) is a transport technology for metro networks, consisting of several non-recursive digital layers: the fgMTN path (fgMTNP) layer, the MTN path (MTNP) layer and the MTN section (MTNS) layer. It supports the transport of distributed radio access network (D-RAN) and centralized radio access network (C-RAN) traffic. This technology leverages existing and emerging pluggable Ethernet modules and reuses flex Ethernet (FlexE) implementation logic. + +Interface specifications of MTN and fgMTN are defined in [ITU-T G.8312]. The architecture of MTN is defined in [ITU-T G.8310]. Equipment functional blocks of MTN are defined in [ITU-T G.8321]. Linear protection specification of MTN is defined in [ITU-T G.8331]. Management and control aspects of MTN are defined in [ITU-T G.8350]. The overview of fine grain MTN is defined in [ITU-T G.8312.20]. + +To support mobile services, i.e., distributed radio access network (D-RAN) and distributed radio access network (C-RAN) traffic, MTN needs to support the distribution of time and frequency. This Recommendation defines the synchronization aspects of MTN including end-to-end synchronization requirements, and synchronization architecture and related solutions. + +# 7 MTN synchronization requirements + +MTN supports the physical layer frequency synchronization and the precision time protocol (PTP) phase/time synchronization. PTP frequency synchronization is not used in MTN. + +MTN synchronization requirements come from, but not limited to the following applications: + +- 1) 5G wireless transport: MTN standard is established to meet the requirements of IMT-2020/5G wireless transport [ITU-T G.8300], which should meet the requirements of time synchronization and frequency synchronization of wireless base stations. +- 2) One-way delay measurement: One-way delay measurement (DM) as defined in clauses 8.2.2.2.2 and 9.3.3.3.2 of [ITU-T G.8312] needs time synchronization. +- 3) Idle block insertion and removal: In principle, time synchronization between two MTN ports is not needed for idle block insertion and removal as defined in clauses 8.3 and 8.4 of [ITU-T G.8312], but if the frequency is synchronized, the occurrence of idle block insertion and removal is less frequent. + +- 4) Timing service for industries: The MTN network requires time synchronization to meet the time synchronization requirements of the fgMTN or MTN clients. These clients could be, for example, from power, finance or transportation industries. + +# 8 MTN synchronization architecture + +The frequency synchronization of MTN is distributed by the physical layer, and the phase/time synchronization of MTN is distributed by PTP. + +MTN synchronization uses the full-timing distribution architecture defined in [ITU-T G.8275]. MTN PTP clocks in MTN synchronization networks are T-GM with performance as specified in [ITU-T G.8272] or [ITU-T G.8272.1], and T-BC and telecom time synchronous clock (T-TSC) with performance as specified in [ITU-T G.8273.2]. + +The overall synchronization network is shown in Figure 8-1. The first MTN T-BC gets time synchronization from a T-GM that is integrated into the PRTC / ePRTC, via Ethernet interfaces (e.g., 1GE, 10GE, etc.). Other MTN T-BCs distribute time synchronization via MTN interfaces (e.g., 50GBASE-R, 100GBASE-R, 200GBASE-R and 400GBASE-R as defined in [ITU-T G.8312], or a grouping of these interfaces). + +MTN synchronization network also supports a stand-alone T-GM, which gets time synchronization from an ePRTC/PRTC via 1PPS+TOD. + +The frequency distribution is not necessarily congruent with the time distribution for MTN, and MTN nodes can also get frequency reference from another ePRC/PRC synchronization chain as shown in Figure 8-1. + +![Figure 8-1: MTN synchronization internetworking for T-GM integrated PRTC / ePRTC. The diagram shows a chain of nodes: ePRTC/PRTC (T-GM), MTN node (T-BC), MTN node (T-BC), MTN node (T-BC), MTN node (T-TSC), and End application. The T-GM is connected to GNSS and ePRC/PRC. The T-GM is connected to the first T-BC via a GE/10GE interface. The T-BCs are connected to each other via MTN interfaces (50GBASE-R, 100GBASE-R, 200GBASE-R, or 400GBASE-R). The T-TSC is connected to the End application via a GE/10GE interface. The legend indicates: PTP (dashed line with arrow), SyncE (dashed line with arrow), Frequency reference (solid line with dot), GE/10GE interface (solid line with dot), and MTN interface (50GBASE-R, 100GBASE-R, 200GBASE-R, or 400GBASE-R) (solid line with arrow).](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +The diagram illustrates the MTN synchronization architecture. It starts with a GNSS source connected to an ePRTC/PRTC (T-GM) block. Below the T-GM is an ePRC/PRC block. The T-GM is connected to a series of MTN nodes: three T-BC (Boundary Clock) nodes and one T-TSC (Telecom Time Synchronous Clock) node. The T-GM connects to the first T-BC via a GE/10GE interface. Subsequent T-BC nodes are connected via MTN interfaces (50GBASE-R, 100GBASE-R, 200GBASE-R, or 400GBASE-R). The final T-TSC node connects to an 'End application' via a GE/10GE interface. A legend at the bottom defines the connection types: PTP (dashed line with arrow), SyncE (dashed line with arrow), Frequency reference (solid line with dot), GE/10GE interface (solid line with dot), and MTN interface (50GBASE-R, 100GBASE-R, 200GBASE-R, or 400GBASE-R) (solid line with arrow). The diagram is labeled G.8371(25). + +Figure 8-1: MTN synchronization internetworking for T-GM integrated PRTC / ePRTC. The diagram shows a chain of nodes: ePRTC/PRTC (T-GM), MTN node (T-BC), MTN node (T-BC), MTN node (T-BC), MTN node (T-TSC), and End application. The T-GM is connected to GNSS and ePRC/PRC. The T-GM is connected to the first T-BC via a GE/10GE interface. The T-BCs are connected to each other via MTN interfaces (50GBASE-R, 100GBASE-R, 200GBASE-R, or 400GBASE-R). The T-TSC is connected to the End application via a GE/10GE interface. The legend indicates: PTP (dashed line with arrow), SyncE (dashed line with arrow), Frequency reference (solid line with dot), GE/10GE interface (solid line with dot), and MTN interface (50GBASE-R, 100GBASE-R, 200GBASE-R, or 400GBASE-R) (solid line with arrow). + +**Figure 8-1 – MTN synchronization internetworking for T-GM integrated PRTC / ePRTC** + +Synchronization messaging channel and encapsulation of MTN interfaces for PTP and ESMC messages are specified in clause 9.1. + +# 9 MTN synchronization solution requirements + +## 9.1 MTN synchronization messaging channel and encapsulation + +The mapping of SSM/PTP messages over MTN is performed as per [ITU-T G.8312]. + +The MTN synchronization messaging channel is provided in the sixth block of the MTNS overhead frame. The synchronization messaging channel is allocated across all the overhead frames of the multi-frame, and it provides a channel to transport SSM and PTP messages. + +An MTN group consists of one or more physical layer entities (PHYs). For the PHY that is being used for synchronization, the synchronization configuration bit in the first block of the MTNS overhead frame in the first instance is always set to 1. + +The SSM messages are encapsulated as ESMC Ethernet messages as specified in [ITU-T G.8264] and they are inserted in the synchronization messaging channel. The general PTP messages are encapsulated as Ethernet messages as specified in [ITU-T G.8275.1] and are inserted in the MTN synchronization messaging channel. + +PTP event messages are timestamped and encapsulated as Ethernet messages as specified in [ITU-T G.8275.1]. PTP event messages are inserted into the MTN synchronization messaging channel. + +SSM messages and PTP general messages are inserted into the MTN synchronization messaging channel as lower priority compared with PTP event messages. + +The synchronization requirement when there is a PHY faulty within a MTN group is for further study. + +## 9.2 Timestamp generation for MTN + +The timestamp generation for MTN is consistent with the [OIF FLEXE IA] specification. + +The message timestamp point for a PTP event message transported over the synchronization messaging channel of MTN overhead frame is the start of the MTNS overhead multi-frame, in which the first 66B block (the /S/ block) of the PTP event message is carried. The PTP event message can be inserted in the overhead of any frame of this multi-frame, if there is only one PTP event message in the overhead multi-frame. When there are multiple PTP event messages transported by MTNS overhead multi-frame, those PTP event messages should be allocated in different overhead frames. A PTP message may cross the multi-frame boundary. Figure 9-1 shows a timestamp diagram example and the relationship to the PTP message. + +![Figure 9-1: Timestamp diagram example and the relationship to the PTP message for MTNS. The diagram shows a horizontal timeline with five dashed boxes representing 'MTN section multiframe boundary'. Below the timeline, three boxes represent 'PTP event message'. Red vertical lines indicate the timestamp points for each PTP event message, which align with the start of an MTN section multiframe boundary. The first PTP event message starts before the first boundary, the second starts between the second and third boundaries, and the third starts between the fourth and fifth boundaries. The label G.8371(25) is in the bottom right corner.](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +The diagram illustrates the timing relationship between PTP event messages and MTN section multiframe boundaries. A horizontal timeline represents the sequence of frames. Five dashed rectangular boxes, each labeled "MTN section multiframe boundary", are positioned along the top of the timeline. Below the timeline, three solid rectangular boxes, each labeled "PTP event message", represent the occurrence of PTP messages. Red vertical lines extend from the start of each PTP event message box up to the timeline, indicating the timestamp point. These timestamp points align precisely with the start of an MTN section multiframe boundary. The first PTP message starts before the first boundary, the second starts between the second and third boundaries, and the third starts between the fourth and fifth boundaries. The label "G.8371(25)" is located in the bottom right corner of the diagram area. + +Figure 9-1: Timestamp diagram example and the relationship to the PTP message for MTNS. The diagram shows a horizontal timeline with five dashed boxes representing 'MTN section multiframe boundary'. Below the timeline, three boxes represent 'PTP event message'. Red vertical lines indicate the timestamp points for each PTP event message, which align with the start of an MTN section multiframe boundary. The first PTP event message starts before the first boundary, the second starts between the second and third boundaries, and the third starts between the fourth and fifth boundaries. The label G.8371(25) is in the bottom right corner. + +Figure 9-1 – Timestamp diagram example and the relationship to the PTP message for MTNS + +All PTP event messages are timestamped on egress and ingress interfaces. The timestamp is the time at which the event message timestamp point passes the reference plane. + +The message timestamp point needs to be at the alignment marker position or at an even lower position (e.g., physical medium attachment (PMA)). In the case of a multi-lane PHY, the PTP path data delay is measured using the timestamps of the lane with the maximum media propagation delay. In practice: + +- In the transmit direction, after the start of the MTNS overhead multi-frame are detected, the position is marked. The timestamp can be generated and inserted into the PTP event messages as the timestamps of the messages when the start of the MTNS overhead multi-frame is processed by egress at the alignment marker or PMA positions. Since the alignment markers for all lanes are transmitted at the same time conceptually, any marker in any lane can be used for timestamping. +- In the receive direction, all the candidate timestamp positions are recorded, and this information must be propagated up through the PHY functions so that once the start of the MTNS overhead multi-frame can be identified, the timestamp can be recorded as the receiving timestamp of all the PTP event messages in this MTNS overhead multi-frame. Alignment markers are present in all the lanes, but different lanes may be skewed from each other. The last received marker across all the lanes shall be used for timestamping. + +In the implementation, the timestamps may be generated at a point removed from the reference plane. Furthermore, the time offset from the reference plane is likely to be different for inbound and outbound event messages. To meet the accuracy requirement, the generated timestamps should be corrected for these offsets. Based on this model, the appropriate corrections are as follows: + +$$\langle \text{egressTimestamp} \rangle = \langle \text{egressMeasuredTimestamp} \rangle + \text{egressLatency}$$ + +$$\langle \text{ingressTimestamp} \rangle = \langle \text{ingressMeasuredTimestamp} \rangle - \text{ingressLatency}$$ + +where the actual timestamps $\langle \text{egressTimestamp} \rangle$ and $\langle \text{ingressTimestamp} \rangle$ measured at the reference plane are computed from the detected, i.e., measured, timestamps by their respective latencies. Failure to make these corrections results in a time offset between the time receiver (TR) and time transmitter (TT) clocks. + +## 9.3 PTP profile for MTN + +MTN networks shall use [ITU-T G.8275.1] for PTP time synchronization. Specific information for MTN is described in Annex I of [ITU-T G.8275.1]. + +For SyncE, the SSM message carried by MTN is Ethernet encapsulation, and shall follow the definition in [ITU-T G.8264]. Additional SyncE protocol requirements are as specified in [ITU-T G.781] and [ITU-T G.8264]. + +## 9.4 MTN synchronization network limit + +MTN networks shall meet the enhanced physical layer network limit specified in clause 9.2.1.4 of [ITU-T G.8261], and the PTP network limit specified in clause 7.3.2 of [ITU-T G.8271.1]. + +## 9.5 MTN clock specification + +The MTN nodes shall meet the eSEC specification defined by [ITU-T G.8262.1] and the T-BC Class C specification defined by [ITU-T G.8273.2]. + +The use of T-BC class D for MTN transport network is for further study. + + + +## 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.853.12-199903-I_PDF-E/raw.md b/marked/G/T-REC-G.853.12-199903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bc22ce541fc59f2f79d67134b99e64b97a530d9b --- /dev/null +++ b/marked/G/T-REC-G.853.12-199903-I_PDF-E/raw.md @@ -0,0 +1,507 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**G.853.12** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/99) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital transmission systems – Digital networks – +Management of transport network + +--- + +**Information viewpoint for pre-provisioned link +management** + +ITU-T Recommendation G.853.12 + +(Previously CCITT Recommendation) + +--- + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| INTERNATIONAL ANALOGUE CARRIER SYSTEM | | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TESTING EQUIPMENTS | | +| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 | +| DIGITAL TRANSMISSION SYSTEMS | | +| TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| General aspects | G.800–G.809 | +| Design objectives for digital networks | G.810–G.819 | +| Quality and availability targets | G.820–G.829 | +| Network capabilities and functions | G.830–G.839 | +| SDH network characteristics | G.840–G.849 | +| Management of transport network | G.850–G.859 | +| SDH radio and satellite systems integration | G.860–G.869 | +| Optical transport networks | G.870–G.879 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## **INFORMATION VIEWPOINT FOR PRE-PROVISIONED LINK MANAGEMENT** + +## **Summary** + +The pre-provisioned link management service provides functionality to add/remove transport entities (link connections or connection termination points) to/from client linking entities (links/link ends). The client linking entities have to be created using the topology management community (G.85x.3 series of Recommendations). The transport entities that could be potentially added to the client linking entity have to be provided using either the pre-provisioned adaptation management (G.85x.8 series of Recommendation) within topological linking entities or using the link management within client linking entities. + +### **Source** + +ITU-T Recommendation G.853.12 was prepared by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 26th of March 1999. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation the term *recognized operating agency (ROA)* includes any individual, company, corporation or governmental organization that operates a public correspondence service. The terms *Administration*, *ROA* and *public correspondence* are defined in the *Constitution of the ITU (Geneva, 1992)*. + +### INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1999 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +###### Page + +| | | | +|-----|--------------------------------------------------------------------|---| +| 1 | Scope ..... | 1 | +| 2 | References ..... | 1 | +| 3 | Definitions ..... | 1 | +| 4 | Abbreviations ..... | 1 | +| 5 | Conventions ..... | 2 | +| 6 | Class diagrams ..... | 2 | +| 6.1 | UML class diagram representing relationships between classes ..... | 2 | +| 6.2 | UML class diagram representing the inheritance hierarchy ..... | 4 | +| 7 | Label references ..... | 5 | +| 8 | Information object class definitions ..... | 5 | +| 8.1 | plmClientLink ..... | 5 | +| 8.2 | plmClientLinkEnd ..... | 5 | +| 8.3 | plmLayerNetworkDomain ..... | 6 | +| 8.4 | plmLinkConnection ..... | 6 | +| 8.5 | plmNetworkCTP ..... | 6 | +| 8.6 | plmProviderLink ..... | 6 | +| 8.7 | plmProviderLinkEnd ..... | 7 | +| 9 | Information relationship definitions ..... | 7 | +| 10 | Static schemas ..... | 7 | +| 11 | Dynamic schemas ..... | 7 | +| 12 | Attributes ..... | 7 | + + + +## **INFORMATION VIEWPOINT FOR PRE-PROVISIONED LINK MANAGEMENT** + +*(Geneva, 1999)* + +# **1 Scope** + +This Recommendation specifies the information viewpoint that is related to the pre-provisioned link management enterprise specification defined in Recommendation G.852.12. + +# **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. + +- [1] ITU-T Recommendation G.851.1 (1996), *Management of the transport network – Application of the RM-ODP framework.* +- [2] ITU-T Recommendation G.853.1 (1999), *Common elements of the information viewpoint for the management of a transport network.* +- [3] ITU-T Recommendation G.852.12 (1999), *Enterprise viewpoint for pre-provisioned link management.* +- [4] ITU-T Recommendation G.854.12 (1999), *Computational viewpoint for pre-provisioned link management.* +- [5] ITU-T Recommendation G.853.8 (1999), *Information viewpoint for pre-provisioned adaptation management.* +- [6] ITU-T Recommendation G.853.10 (1999), *Information viewpoint for pre-provisioned link connection management.* + +# **3 Definitions** + +None. + +## **4 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|-----|------------------------------| +| CTP | Connection Termination Point | +| Id | Identifier | +| imp | imported | +| LC | Link Connection | +| LE | Link End | + +LND Layer Network Domain +pam pre-provisioned adaptation management +plem pre-provisioned link connection management +plm pre-provisioned link management +SDH Synchronous Digital Hierarchy +WDM Wave Division Multiplexing + +# 5 Conventions + +None. + +## 6 Class diagrams + +## 6.1 UML class diagram representing relationships between classes + +![UML class diagram showing relationships between plmLayerNetworkDomain, plmProviderLink, plmClientLink, and plmLinkConnection classes. The diagram is arc-oriented with associations labeled like 'layerNetworkDomain IsMadeOf', 'linkHasLinkConnections', and 'representSameResourceAs'.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +``` + +classDiagram + class plmLayerNetworkDomain + class plmProviderLink + class plmClientLink + class plmLinkConnection + + plmLayerNetworkDomain "1..1 containerLND" -- "1..N element" plmProviderLink : layerNetworkDomain IsMadeOf + plmLayerNetworkDomain "1..1 containerLND" -- "1..N element" plmClientLink : layerNetworkDomain IsMadeOf + plmProviderLink "1..1 containerLink" -- "1..N elementLC" plmLinkConnection : linkHasLinkConnections + plmClientLink "1..1 containerLink" -- "1..N elementLC" plmLinkConnection : linkHasLinkConnections + plmLinkConnection "1..N resourceInfo" -- "1..N resourceInfo" plmLinkConnection : representSameResourceAs + +``` + +The diagram illustrates the following classes and their relationships: + +- plmLayerNetworkDomain**: The top-level class, shown as a box with three empty compartments. +- plmProviderLink** and **plmClientLink**: Subclasses that inherit from **plmLayerNetworkDomain**. The association is labeled *layerNetworkDomain IsMadeOf*. Multiplicity at the domain end is (1..1) containerLND, and at the link end is (1..N) element. +- plmLinkConnection**: A class that has associations with both **plmProviderLink** and **plmClientLink**. The association is labeled *linkHasLinkConnections*. Multiplicity at the link end is (1..1) containerLink, and at the connection end is (1..N) elementLC. +- Self-association on plmLinkConnection**: A relationship labeled *representSameResourceAs*. Multiplicity at both ends is (1..N) resourceInfo. + +T0411290-99 + +UML class diagram showing relationships between plmLayerNetworkDomain, plmProviderLink, plmClientLink, and plmLinkConnection classes. The diagram is arc-oriented with associations labeled like 'layerNetworkDomain IsMadeOf', 'linkHasLinkConnections', and 'representSameResourceAs'. + +Figure 1/G.853.12 – UML class diagram (arc-oriented view) + +![UML class diagram for plmLayerNetworkDomain showing relationships between containerLND, layerNetworkDomain, element, plmProviderLinkEnd, plmClientLinkEnd, containerLE, linkEndHasNetworkCTPs, elementCTP, and plmNetworkCTP.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +``` + +classDiagram + class plmLayerNetworkDomain + class plmProviderLinkEnd + class plmClientLinkEnd + class plmNetworkCTP + + plmLayerNetworkDomain "1..1" containerLND -- "1..N" element : layerNetworkDomain IsMadeOf + plmProviderLinkEnd "1..N" element -- "1..1" containerLND : layerNetworkDomain IsMadeOf + plmClientLinkEnd "1..N" element -- "1..1" containerLND : layerNetworkDomain IsMadeOf + plmNetworkCTP "1..N" elementCTP -- "1..1" containerLE : linkEndHasNetworkCTPs + plmProviderLinkEnd "1..1" containerLE -- "1..N" elementCTP : linkEndHasNetworkCTPs + plmClientLinkEnd "1..1" containerLE -- "1..N" elementCTP : linkEndHasNetworkCTPs + plmNetworkCTP "1..N" resourceInfo -- "1..N" resourceInfo : representSameResourceAs + +``` + +The diagram illustrates the point-oriented view of the UML class diagram for plmLayerNetworkDomain. It shows the following classes and relationships: + +- plmLayerNetworkDomain**: The top-level class, which has a relationship with **containerLND** (1..1) and **element** (1..N) via the association *layerNetworkDomain IsMadeOf*. +- plmProviderLinkEnd** and **plmClientLinkEnd**: These classes are associated with **containerLND** (1..1) and **element** (1..N) via the association *layerNetworkDomain IsMadeOf*. +- plmNetworkCTP**: This class is associated with **containerLE** (1..1) and **elementCTP** (1..N) via the association *linkEndHasNetworkCTPs*. +- representSameResourceAs**: This association relates two instances of **plmNetworkCTP** via their **resourceInfo** (1..N) attributes. + +T0411300-99 + +UML class diagram for plmLayerNetworkDomain showing relationships between containerLND, layerNetworkDomain, element, plmProviderLinkEnd, plmClientLinkEnd, containerLE, linkEndHasNetworkCTPs, elementCTP, and plmNetworkCTP. + +Figure 2/G.853.12 – UML class diagram (point-oriented view) + +## 6.2 UML class diagram representing the inheritance hierarchy + +![UML class diagram showing the inheritance hierarchy for G.853.1 classes. The root class is G.853.1: networkInformationTop with attribute resourceId. It has three subclasses: G.853.1: transportConnection, G.853.1: layerNetworkDomain, and G.853.1: networkCTP. Further subclasses include G.853.1: linkConnection, plmLayerNetworkDomain, and plmNetworkCTP. At the bottom, plmLinkConnection inherits from G.853.1: linkConnection. G.853.1: link and G.853.1: linkEnd both inherit from G.853.1: networkInformationTop. G.853.1: link has subclasses plmProviderLink and plmClientLink. G.853.1: linkEnd has subclasses plmClientLinkEnd and plmProviderLinkEnd. Attributes include signalIdentification, directionality, pointDirectionality, linkDirectionality, topologicalEndDirection, and pamAvailableLinkCapacity (imp).](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +``` + +classDiagram + class networkInformationTop["G.853.1: networkInformationTop"] { + resourceId + } + class transportConnection["G.853.1: transportConnection"] { + signalIdentification + directionality + } + class layerNetworkDomain["G.853.1: layerNetworkDomain"] { + signalIdentification + } + class networkCTP["G.853.1: networkCTP"] { + signalIdentification + pointDirectionality + } + class linkConnection["G.853.1: linkConnection"] { + } + class plmLayerNetworkDomain["plmLayerNetworkDomain"] { + } + class plmNetworkCTP["plmNetworkCTP"] { + } + class plmLinkConnection["plmLinkConnection"] { + } + class link["G.853.1: link"] { + signalIdentification + linkDirectionality + } + class linkEnd["G.853.1: linkEnd"] { + signalIdentification + topologicalEndDirection + } + class plmProviderLink["plmProviderLink"] { + } + class plmClientLink["plmClientLink"] { + pamAvailableLinkCapacity (imp) + } + class plmClientLinkEnd["plmClientLinkEnd"] { + pamAvailableLinkCapacity (imp) + } + class plmProviderLinkEnd["plmProviderLinkEnd"] { + } + + networkInformationTop <|-- transportConnection + networkInformationTop <|-- layerNetworkDomain + networkInformationTop <|-- networkCTP + transportConnection <|-- linkConnection + layerNetworkDomain <|-- plmLayerNetworkDomain + networkCTP <|-- plmNetworkCTP + linkConnection <|-- plmLinkConnection + networkInformationTop <|-- link + networkInformationTop <|-- linkEnd + link <|-- plmProviderLink + link <|-- plmClientLink + linkEnd <|-- plmClientLinkEnd + linkEnd <|-- plmProviderLinkEnd + +``` + +UML class diagram showing the inheritance hierarchy for G.853.1 classes. The root class is G.853.1: networkInformationTop with attribute resourceId. It has three subclasses: G.853.1: transportConnection, G.853.1: layerNetworkDomain, and G.853.1: networkCTP. Further subclasses include G.853.1: linkConnection, plmLayerNetworkDomain, and plmNetworkCTP. At the bottom, plmLinkConnection inherits from G.853.1: linkConnection. G.853.1: link and G.853.1: linkEnd both inherit from G.853.1: networkInformationTop. G.853.1: link has subclasses plmProviderLink and plmClientLink. G.853.1: linkEnd has subclasses plmClientLinkEnd and plmProviderLinkEnd. Attributes include signalIdentification, directionality, pointDirectionality, linkDirectionality, topologicalEndDirection, and pamAvailableLinkCapacity (imp). + +T0411310-99 + +Figure 3/G.853.12 – Inheritance hierarchy + +# 7 Label references + +**Table 1/G.853.12 – Label references** + +| Full label reference | Local label reference | +|-----------------------------------------------------------------------|----------------------------| +| <"Rec. G.853.1", INFORMATION_OBJECT:layerNetworkDomain> | layerNetworkDomain | +| <"Rec. G.853.1", INFORMATION_OBJECT:link> | link | +| <"Rec. G.853.1", INFORMATION_OBJECT:linkConnection> | linkConnection | +| <"Rec. G.853.1", INFORMATION_OBJECT:linkEnd> | linkEnd | +| <"Rec. G.853.1", INFORMATION_OBJECT:networkCTP> | networkCTP | +| <"Rec. G.853.1", INFORMATION_RELATIONSHIP:layerNetworkDomainIsMadeOf> | layerNetworkDomainIsMadeOf | +| <"Rec. G.853.1", INFORMATION_RELATIONSHIP:linkHasLinkConnections> | linkHasLinkConnections | +| <"Rec. G.853.1", INFORMATION_RELATIONSHIP:linkEndHasNetworkCTPs> | linkEndHasNetworkCTPs | +| <"Rec. G.853.1", INFORMATION_RELATIONSHIP:representSameResourceAs> | representSameResourceAs | +| <"Rec. G.853.8", ATTRIBUTE:pamAvailableLinkCapacity> | pamAvailableLinkCapacity | + +# 8 Information object class definitions + +## 8.1 plmClientLink + + + +### DEFINITION + +"This object class is derived from ." + +### ATTRIBUTE + + + +"The attribute represents the provisioned capacity that is not assigned1. This attribute is imported from "Rec G.853.8" COMMUNITY: pre-provisioned adaptation management." + +### RELATIONSHIP + + + + + +## 8.2 plmClientLinkEnd + + + +### DEFINITION + +"This object class is derived from ." + +### ATTRIBUTE + + + +"The attribute represents the provisioned capacity that is not assigned1. This attribute is imported from "Rec G.853.8" COMMUNITY: pre-provisioned adaptation management." + +### RELATIONSHIP + + + + + +1 This state is managed in the pre-provisioned linkConnection management community (plcm). + +## 8.3 plmLayerNetworkDomain + + + +### DEFINITION + +"This object class is derived from ." + +### ATTRIBUTE + +-- none additional + +### RELATIONSHIP + + + +## 8.4 plmLinkConnection + + + +### DEFINITION + +"This object class is derived from ." + +### ATTRIBUTE + +-- none additional + +### RELATIONSHIP + + + + + +## 8.5 plmNetworkCTP + + + +### DEFINITION + +"This object class is derived from ." + +### ATTRIBUTE + +-- none additional + +#### RELATIONSHIP + + + + + +## 8.6 plmProviderLink + + + +#### DEFINITION + +"This object class is derived from ." + +#### ATTRIBUTE + +-- none additional + +#### RELATIONSHIP + + + + +## **8.7 plmProviderLinkEnd** + + + +### **DEFINITION** + +"This object class is derived from ." + +#### **ATTRIBUTE** + +-- none additional + +### **RELATIONSHIP** + + + + + +## **9 Information relationship definitions** + +None additional. + +## **10 Static schemas** + +None. + +## **11 Dynamic schemas** + +None. + +## **12 Attributes** + +None. + + + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/G/T-REC-G.854.6-199903-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/G/T-REC-G.854.6-199903-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bca3bcfc8fa52f7a087ede74fc96b4ed261f842 --- /dev/null +++ b/marked/G/T-REC-G.854.6-199903-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57693fba8d6372314f5854d29911a566b103fa48c1a62ced1760329493b38b3c +size 27656 diff --git a/marked/G/T-REC-G.854.6-199903-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/G/T-REC-G.854.6-199903-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9512e3ae3ab66620469929478469015bb6e523a4 --- /dev/null +++ b/marked/G/T-REC-G.854.6-199903-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b0f00f511230ffb92f5df22541e27dd31c36fa5ec9a7bd6f08cad6e55868c05 +size 35447 diff --git a/marked/G/T-REC-G.854.6-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.854.6-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff --- /dev/null +++ b/marked/G/T-REC-G.854.6-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.854.6-199903-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg b/marked/G/T-REC-G.854.6-199903-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f82e5d88363c6edc51a178b0e244ce790fb0a09c --- /dev/null +++ b/marked/G/T-REC-G.854.6-199903-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50e24948e7c91b23dcdfe4a5d519e32e1cf12436c023a8e735c8adf29eb006e3 +size 24515 diff --git a/marked/G/T-REC-G.854.6-199903-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.854.6-199903-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5947bfe273e8694a40109fa8c761313d4dad97c1 --- /dev/null +++ b/marked/G/T-REC-G.854.6-199903-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91166417889ca7c5381343ae234cb80e2eb37cfccf475f78f33e765c3d869c57 +size 27787 diff --git a/marked/G/T-REC-G.854.6-199903-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/G/T-REC-G.854.6-199903-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..505969f3e08ec7ea15d809b965087014f604f824 --- /dev/null +++ b/marked/G/T-REC-G.854.6-199903-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d1ff15a32fdf72d3343be81b384b45d8a907799da711d88bd95cec3a526226a +size 61779 diff --git a/marked/G/T-REC-G.854.6-199903-I_PDF-E/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/G/T-REC-G.854.6-199903-I_PDF-E/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69d909e79dfa34695abe123f80faf17b66e17821 --- /dev/null +++ b/marked/G/T-REC-G.854.6-199903-I_PDF-E/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a1d8b7f57171c75177882aaacba6f2474573a7af9b7fdf683db6b3e979af7b1 +size 35275 diff --git a/marked/G/T-REC-G.854.6-199903-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/G/T-REC-G.854.6-199903-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90fb5a413fcc3e74904ecd4a57927e2e77270816 --- /dev/null +++ b/marked/G/T-REC-G.854.6-199903-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f4c0b434ee7e8c38ab80e79935f5b355da16d11dfd01c64dc2913d5f8fdb768 +size 27418 diff --git a/marked/G/T-REC-G.854.6-199903-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/G/T-REC-G.854.6-199903-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8459e3867c45b7765623fcf6a9242c329033cc50 --- /dev/null +++ b/marked/G/T-REC-G.854.6-199903-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:719af2df577a859fd9ae502a9d332e462fe3f5e471cf6f2e00e02ccbfa3282b7 +size 57984 diff --git a/marked/G/T-REC-G.854.6-199903-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/G/T-REC-G.854.6-199903-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65e365f234cc37f78fbbda9dc8f4b3475155dc28 --- /dev/null +++ b/marked/G/T-REC-G.854.6-199903-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63081eff7a572b9d46db2dba00a065f749ff6553b399f82c771e4c0750d5d15e +size 28086 diff --git a/marked/G/T-REC-G.854.6-199903-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/marked/G/T-REC-G.854.6-199903-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..106d373ebc23338bf4f28601daeb6a4d901f3b32 --- /dev/null +++ b/marked/G/T-REC-G.854.6-199903-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1cc2279e3ce0cc0bb68318cacfe5406a8e4b59458f77e70deec94497db4005e +size 24051 diff --git a/marked/G/T-REC-G.854.6-199903-I_PDF-E/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg b/marked/G/T-REC-G.854.6-199903-I_PDF-E/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f60636202f4d8e776ba741d793512e432ba624d6 --- /dev/null +++ b/marked/G/T-REC-G.854.6-199903-I_PDF-E/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a785e62757a44f00e70e43b5e829ab3bc78bd0b1877bf9fa87f2e8bbed30a1b +size 28881 diff --git a/marked/G/T-REC-G.854.6-199903-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg b/marked/G/T-REC-G.854.6-199903-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4eb20a3d53deaf1614bf786db498c31477a0f9c --- /dev/null +++ b/marked/G/T-REC-G.854.6-199903-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fe69a00d029caec02623349962cb37d3805412d2116c4949ca54e435d3a9347 +size 23932 diff --git a/marked/G/T-REC-G.854.6-199903-I_PDF-E/raw.md b/marked/G/T-REC-G.854.6-199903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..859c5ef8d21f7e1f560ae2005ab716b03faba537 --- /dev/null +++ b/marked/G/T-REC-G.854.6-199903-I_PDF-E/raw.md @@ -0,0 +1,1803 @@ + + +![ITU logo: A globe with the letters ITU and a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with the letters ITU and a lightning bolt. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.854.6** + +(03/99) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital transmission systems – Digital networks – +Management of transport network + +--- + +**Computational viewpoint for trail management** + +ITU-T Recommendation G.854.6 + +(Previously CCITT Recommendation) + +--- + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| INTERNATIONAL ANALOGUE CARRIER SYSTEM | | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TESTING EQUIPMENTS | | +| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 | +| DIGITAL TRANSMISSION SYSTEMS | | +| TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| General aspects | G.800–G.809 | +| Design objectives for digital networks | G.810–G.819 | +| Quality and availability targets | G.820–G.829 | +| Network capabilities and functions | G.830–G.839 | +| SDH network characteristics | G.840–G.849 | +| Management of transport network | G.850–G.859 | +| SDH radio and satellite systems integration | G.860–G.869 | +| Optical transport networks | G.870–G.879 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | + +For further details, please refer to ITU-T List of Recommendations. + +# **COMPUTATIONAL VIEWPOINT FOR TRAIL MANAGEMENT** + +## **Summary** + +Enterprise community actions covered by this specification: + +- set-up point-to-point trail; +- modify trail; +- release trail; +- create trail termination point; +- delete trail termination point; +- associate trail termination point with access group; +- disassociate trail termination point from access group; +- associate trail termination point with subnetwork; +- disassociate trail termination point from subnetwork; +- report trail set-up; +- report trail release; +- report trail modification; +- report trail termination point creation; +- report trail termination point deletion; +- report association of trail termination point with access group; +- report disassociation of trail termination point from access group; +- report association of trail termination point with subnetwork; +- report disassociation of trail termination point from subnetwork. + +## **Source** + +ITU-T Recommendation G.854.6 was prepared by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 26th of March 1999. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation the term *recognized operating agency (ROA)* includes any individual, company, corporation or governmental organization that operates a public correspondence service. The terms *Administration*, *ROA* and *public correspondence* are defined in the *Constitution of the ITU (Geneva, 1992)*. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1999 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | Page | +|----------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References ..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations ..... | 1 | +| 5 Conventions ..... | 2 | +| 6 Label references ..... | 2 | +| 7 Interfaces ..... | 3 | +| 7.1 Query interfaces ..... | 3 | +| 7.2 Operational interfaces ..... | 4 | +| 7.2.1 Trail provisioning interface ..... | 4 | +| 7.3 Reporting interfaces ..... | 16 | +| 7.3.1 Trail provisioning reporting interface ..... | 16 | +| 7.4 ASN.1 supporting productions ..... | 25 | + + + +## Recommendation G.854.6 + +# COMPUTATIONAL VIEWPOINT FOR TRAIL MANAGEMENT + +(Geneva, 1999) + +# 1 Scope + +This computational viewpoint specification is related to the trail management enterprise specification defined in Recommendation G.852.6 and the trail management information specification defined in Recommendation G.853.6. + +# 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. + +- [1] ITU-T Recommendation G.851.1 (1996), *Management of the transport network – Application of the RM-ODP framework*. +- [2] ITU-T Recommendation G.853.1 (1999), *Common elements of the information viewpoint for the management of a transport network*. +- [3] ITU-T Recommendation G.852.6 (1999), *Enterprise viewpoint for trail management*. +- [4] ITU-T Recommendation G.853.6 (1999), *Information viewpoint for trail management*. + +# 3 Definitions + +None. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|---------|-------------------------------------------------| +| ASN.1 | Abstract Syntax Notation One | +| Id | Identifier | +| Ifce | Interface | +| inv | invariant | +| ITU | International Telecommunication Union | +| layerND | layerNetwork Domain | +| LC | LinkConnection | +| ND | Network Domain | +| RM-ODP | Reference Model for Open Distributed Processing | + +tm trail management + +TTP Trail Termination Point + +# 5 Conventions + +In order to increase the readability of the behaviour in the operations: + +- parameters are written in **bold**; +- elements defined in the information viewpoint specification are written in *italic*. + +# 6 Label references + +| Full label reference | Local label reference | +|-------------------------------------------------------------------------------------------|------------------------------------------------| +| <"Rec. G.853.6", INFORMATION_OBJECT: tmAccessGroup> | tmAccessGroup | +| <"Rec. G.853.6", INFORMATION_OBJECT: tmLayerNetworkDomain> | tmLayerNetworkDomain | +| <"Rec. G.853.6", INFORMATION_OBJECT: tmNetworkTTP> | tmNetworkTTP | +| <"Rec. G.853.6", INFORMATION_OBJECT: tmSubnetwork> | tmSubnetwork | +| <"Rec. G.853.6", INFORMATION_OBJECT: tmSubnetworkConnection> | tmSubnetworkConnection | +| <"Rec. G.853.6", INFORMATION_OBJECT: tmSubnetworkTP> | tmSubnetworkTP | +| <"Rec. G.853.6", INFORMATION_OBJECT: tmTrafficDescriptor> | tmTrafficDescriptor | +| <"Rec. G.853.6", INFORMATION_OBJECT: tmTrail> | tmTrail | +| <"Rec. G.853.6", INFORMATION_OBJECT: tmTrailServiceCharacteristics> | tmTrailServiceCharacteristics | +| <"Rec.G.853.1", INFORMATION_RELATIONSHIP: accessGroupIsMadeOfNetworkTTPs> | accessGroupIsMadeOfNetworkTTPs | +| <"Rec. G.853.1", INFORMATION_RELATIONSHIP: layerNetworkDomainIsMadeOf> | layerNetworkDomainIs MadeOf | +| <"Rec.G.853.1", INFORMATION_RELATIONSHIP: subnetworkConnectionIsTerminatedByPointToPoint> | subnetworkConnectionIsTerminatedByPointToPoint | +| <"Rec.G.853.1", INFORMATION_RELATIONSHIP: subnetworkIsDelimitedBy> | subnetworkIsDelimitedBy | +| <"Rec.G.853.1", INFORMATION_RELATIONSHIP: subnetworkTPIsRelatedToExtremity> | subnetworkTPIsRelatedToExtremity | +| <"Rec. G.853.6", INFORMATION_RELATIONSHIP: tmTrailHasImmediateTrafficDescriptor> | tmTrailHasImmediateTrafficDescriptor | +| <"Rec.G.853.6", INFORMATION_RELATIONSHIP: tmTrailHasTSC> | tmTrailHasTSC | +| <"Rec.G.853.1", INFORMATION_RELATIONSHIP: trailIsTerminatedByPointToPoint> | trailIsTerminatedByPointToPoint | +| <"Rec. G.853.1", INFORMATION_ATTRIBUTE: directionality> | directionality | +| <"Rec. G.853.1", INFORMATION_ATTRIBUTE: resourceId> | resourceId | +| <"Rec.G.853.1", INFORMATION_ATTRIBUTE: signalIdentification> | signalIdentification | +| <"Rec.G.853.1", INFORMATION_ATTRIBUTE: userLabel> | userLabel | +| <"Rec. G.854.3", INTERFACE: commonReportResourceIdChangeIfce> | commonReportResourceIdChangeIfce | +| <"Rec. G.854.3", INTERFACE: commonResourceIfce> | commonResourceIfce | + +| Full ASN.1 production reference | Local label reference | +|-------------------------------------------------------------|-----------------------| +| <"Rec. X.721:1992: Attribute-ASN.1 Module": SimpleNameType> | SimpleNameType | +| <"Rec. X.680:1997: GraphicString"> | GraphicString | + +# 7 Interfaces + +This specification does not define operations which change the userLabel of the resources or report this change to the notification receiver because they do not change the state of the system. Their exact signature will be developed as part of the engineering viewpoint specification with the concerned technology. + +## 7.1 Query interfaces + +This specification refers to interfaces that allow get access to identification and properties of resources involved in the "trail management" community. As the invocation of the contained operations do not modify any state, there is no interest to develop them explicitly. Their exact signature will be developed as part of the engineering viewpoint, with the concerned technology. These interfaces are listed in Table 1 with the information they allow access to. + +**Table 1/G.854.6 – Query interfaces** + +| Interface name | Information object | Attributes and relationships | +|---------------------------------|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| tmAccessGroupQueryIfce | |



| +| tmLayerNetworkDomainQueryIfce | |

| +| tmNetworkTTPQueryIfce | |






| +| tmSubnetworkConnectionQueryIfce | |



| +| tmSubnetworkQueryIfce | |


| + +**Table 1/G.854.6 – Query interfaces (concluded)** + +| Interface name | Information object | Attributes and relationships | +|----------------------------------------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| tmSubnetworkTPQueryIfce | |





| +| tmTrafficDescriptorQueryIfce | |
| +| tmTrailQueryIfce | |






| +| tmTrailServiceCharacteristicsQueryIfce | |

| + +## 7.2 Operational interfaces + +### 7.2.1 Trail provisioning interface + +The trail provisioning interface manages the immediate set-up, release and modification of point-to-point trails as well as the creation and deletion of network TTPs and the association and disassociation of network TTPs with/from access groups and subnetworks. The interface is required to satisfy the enterprise requirements stated in: + +<"Recommendation G.852.6, "COMMUNITY trail management, ACTION: setup point-to-point trail">, <"Recommendation G.852.6, "COMMUNITY trail management, ACTION: release trail">, <"Recommendation G.852.6, "COMMUNITY trail management, ACTION: modify trail">, <"Recommendation G.852.6, "COMMUNITY trail management, ACTION: create trail termination point">, <"Recommendation G.852.6, "COMMUNITY trail management, ACTION: delete trail termination point">, <"Recommendation G.852.6, "COMMUNITY trail management, ACTION: associate trail termination point with access group">, <"Recommendation G.852.6, "COMMUNITY trail management, ACTION: disassociate trail termination point from access group">, <"Recommendation G.852.6, "COMMUNITY trail management, ACTION: associate trail termination point with subnetwork">, <"Recommendation G.852.6, "COMMUNITY trail management, ACTION: disassociate trail termination point from subnetwork"> + +By inheriting the properties of the commonResourceIfce, the trailProvisioningIfce provides the capability to change the resource identifier of the resources involved. + +``` +COMPUTATIONAL INTERFACE trailProvisioning Ifce{ + DERIVED FROM + OPERATION { + ; + ; + ; + ; + + ; + ; + ; + ; + } +} +``` + +#### 7.2.1.1 Set-up point-to-point trail + +``` + +OPERATION setupPointToPointTrail { + INPUT_PARAMETERS + aEnd: AEndChoice ::= CHOICE { + networkTTP NetworkTTPChoice, + accessGroup AccessGroupChoice}; + zEnd: ZEndChoice ::= CHOICE { + networkTTP NetworkTTPChoice, + accessGroup AccessGroupChoice}; + layerND: LayerNetworkDomainChoice; + dir: Directionality; + suppliedUserIdentifier: UserIdentifier; + -- zero length string or 0 implies none supplied. + serviceCharacteristics: TrailServiceCharacteristicsId; + -- reference can be used to determine any QOS or routing characteristics; + trafficDescriptor: ImmediateTrafficDescriptorId; + suppliedUserLabel: GraphicString; + -- zero length string implies none supplied + + OUTPUT_PARAMETERS + newTrail: TrailChoice; + connectedAEndNetworkTTP: NetworkTTPChoice; + connectedZEndNetwrkTTP: NetworkTTPChoice; + + RAISED_EXCEPTIONS + networkTTPsNotPartOfLayerND: SequenceOf NetworkTTPChoice; + -- the list contains one element when only one point is incorrect, i.e. is not part of the + -- layerNetworkDomain. + aEndNetworkTTPConnected:NetworkTTPChoice; + networkTTPsInAEndAccessGroupConnected: AccessGroupChoice; + zEndNetworkTTPConnected: NetworkTTPChoice; + networkTTPsInZEndAccessGroupConnected: AccessGroupChoice; + userIdentifierNotUnique: UserIdentifier; + failureToSetUserIdentifier: NULL; + failureToCreateTrail: NULL; + invalidTransportServiceCharacteristics: NULL; + invalidTrafficDescriptor: NULL; +``` + +##### BEHAVIOUR SEMI\_FORMAL + +##### PARAMETER\_MATCHING + +networkTTP: ; +accessGroup: ; +layerND: ; +dir: ; +suppliedUserIdentifier: ; +serviceCharacteristics: ; +trafficDescriptor: ; +suppliedUserLabel: ; +newTrail: ; +connectedAEndNetworkTTP: ; +connectedZEndNetworkTTP: ; + +##### PRE\_CONDITIONS + +inv\_layerNDContainment + +"**aEnd** and **zEnd** are referring to element in a <*layerNetworkDomainIsMadeOf*> relationship where **layerND** refers to *containerLND*." + +inv\_freeAEndNetworkTTP + +"If **aEnd** is a networkTTP, this networkTTP must not refer to *a\_endNTTP* or *z\_endNTTP* in any <*trailIsTerminatedByPointToPoint*> relationship." + +inv\_freeAEndAccessGroupMember + +"If **aEnd** is an accessGroup, at least one networkTTP referring to *elementTTP* in an <*accessGroupIsMadeOfNetworkTTPs*> relationship where this accessGroup refers to *containerAG*, must not refer to *a\_endNTTP* or *z\_endNTTP* in any <*trailIsTerminatedByPointToPoint*> relationship." + +![UML Class Diagram showing relationships between tmTrail, tmNetworkTTP, and tmAccessGroup for both A-end and Z-end.](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +``` + +classDiagram + direction BT + class tmTrail { + <> + } + class tmNetworkTTP_A { + a_endNTTP + } + class tmAccessGroup_A { + containerAG + } + tmNetworkTTP_A "1..1" -- "transportEntityTrail" tmTrail : trailIsTerminatedByPointToPoint + tmAccessGroup_A "1..1" -- "elementTTP (1..N)" tmNetworkTTP_A : accessGroupIsMadeOfNetworkTTPs + + class tmNetworkTTP_Z { + z_endNTTP + } + class tmAccessGroup_Z { + containerAG + } + tmNetworkTTP_Z "1..1" -- "transportEntityTrail" tmTrail : trailIsTerminatedByPointToPoint + tmAccessGroup_Z "1..1" -- "elementTTP (1..N)" tmNetworkTTP_Z : accessGroupIsMadeOfNetworkTTPs + +``` + +inv\_freeAEndAccessGroupMember          inv\_freeZEndAccessGroupMember + +UML Class Diagram showing relationships between tmTrail, tmNetworkTTP, and tmAccessGroup for both A-end and Z-end. + +inv\_freeZEndNetworkTTP + +"If **zEnd** is a networkTTP, this networkTTP must not refer to *a\_endNTTP* or *z\_endNTTP* in any <*trailIsTerminatedByPointToPoint*> relationship." + +inv\_freeZEndAccessGroupMember + +"If **zEnd** is an accessGroup, at least one networkTTP referring to *elementTTP* in an <*accessGroupIsMadeOfNetworkTTPs*> relationship where this accessGroup refers to *containerAG*, must not refer to *a\_endNTTP* or *z\_endNTTP* in any <*trailIsTerminatedByPointToPoint*> relationship." + +``` + +inv_uniqueUserIdentifier + "suppliedUserIdentifier shall not be equal to of any element in the + relationship where layerND refers to containerLND." + +POST_CONDITIONS +inv_agreedUserIdentifier + " of referred to by newTrail is equal to suppliedUserIdentifier, if it is supplied." + +inv_connectedTrail + "connectedAEndNetworkTTP, connectedZEndNetworkTTP and newTrail must respectively refer to + a_endNTTP, z_endNTTP and transportEntityTrail in a relationship." + +inv_transportServiceCharacteristics + "newTrail and serviceCharacteristics must refer to transportQualifiedTrail and transportQualifierTSC in + a relationship." + +inv_trafficDescriptor + "newTrail and trafficDescriptor must refer to trailID and immediateTrafficDescriptorTrail in a + relationship." + +EXCEPTIONS + IF PRE_CONDITION inv_layerNDContainment NOT_VERIFIED RAISE_EXCEPTION + networkTTPsNotPartOfLayerND; + IF PRE_CONDITION inv_freeAEndNetworkTTP NOT_VERIFIED RAISE_EXCEPTION + aEndNetworkTTPConnected ; + IF PRE_CONDITION inv_freeAEndAccessGroupMember NOT_VERIFIED + RAISE_EXCEPTION networkTTPsInAEndAccessGroupConnected ; + IF PRE_CONDITION inv_freeZEndNetworkTTP NOT_VERIFIED RAISE_EXCEPTION + zEndNetworkTTPConnected ; + IF PRE_CONDITION inv_freeZEndAccessGroupMember NOT_VERIFIED + RAISE_EXCEPTION networkTTPsInZEndAccessGroupConnected ; + IF PRE_CONDITION inv_uniqueUserIdentifier NOT_VERIFIED RAISE_EXCEPTION + userIdentifierNotUnique; + IF POST_CONDITION inv_agreedUserIdentifier NOT VERIFIED RAISE_EXCEPTION + failureToSetUserIdentifier; + IF POST_CONDITION inv_connectedTrail NOT_VERIFIED RAISE_EXCEPTION + failureToCreateTrail; + IF POST_CONDITION inv_transportServiceCharacteristics NOT_VERIFIED + RAISE_EXCEPTION invalidTransportServiceCharacteristics; + IF POST_CONDITION inv_trafficDescriptor NOT_VERIFIED RAISE_EXCEPTION + invalidTrafficDescriptor; +} + +``` + +#### 7.2.1.2 Release trail + +``` + + +OPERATION releaseTrail { + INPUT_PARAMETERS + trail: TrailChoice; + layerND: LayerNetworkDomainChoice; + + OUTPUT_PARAMETERS + trail: TrailChoice; + + RAISED_EXCEPTIONS + unknownTrail: TrailChoice; + trailConnected: NULL; + failureToReleaseTrail: NULL; +} + +``` + +BEHAVIOUR +SEMI\_FORMAL + +##### PARAMETER\_MATCHING + +trail: ; +layerND: ; + +##### PRE\_CONDITIONS + +inv\_existingTrail + +"**trail** must refer to *element* in the relationship where **layerND** refers to *containerLND*." + +inv\_trailConnected + +"**trail** must not refer to *transportEntityTrail* in a relationship." + +##### POST\_CONDITIONS + +inv\_trailReleased + +"**trail** must not refer to any *element* in a relationship." + +##### EXCEPTIONS + +IF PRE\_CONDITION inv\_existingTrail NOT\_VERIFIED RAISE\_EXCEPTION + +unknownTrail; + +IF PRE\_CONDITION inv\_trailConnected NOT\_VERIFIED RAISE\_EXCEPTION + +trailConnected; + +IF POST\_CONDITION inv\_trailReleased NOT\_VERIFIED RAISE\_EXCEPTION failureToReleaseTrail; + +} + +#### 7.2.1.3 Modify trail + + + +OPERATION modifyTrail { + +##### INPUT\_PARAMETERS + +trail: TrailChoice; + +layerND: LayerNetworkDomainChoice; + +newTrafficDescriptor: ImmediateTrafficDescriptorId; + +newServiceCharacteristics: TrailServiceCharacteristicsId; + +##### OUTPUT\_PARAMETERS + +agreedTrafficDescriptor: ImmediateTrafficDescriptorId; + +-- *The old trafficDescriptor is maintained if the new one cannot be supported* + +agreedServiceCharacteristics: TrailServiceCharacteristicsId; + +-- *The old serviceCharacteristics is maintained if the new one cannot be supported* + +##### RAISED\_EXCEPTIONS + +unknownTrail: TrailChoice; + +invalidServiceCharacteristicsRequested: NULL; + +invalidTrafficDescriptorRequested: NULL; + +BEHAVIOUR + +SEMI\_FORMAL + +##### PARAMETER\_MATCHING + +trail: ; + +layerND: ; + +newTrafficDescriptor: ; + +newServiceCharacteristics: ; + +agreedTrafficDescriptor: ; + +agreedServiceCharacteristics: ; + +##### PRE\_CONDITIONS + +inv\_existingTrail + +"**trail** must refer to element in a relationship where **layerND** being the containerLND." + +##### POST\_CONDITIONS + +inv\_agreedServiceCharacteristics + +"**trail** and **agreedServiceCharacteristics** must be involved as *transportQualifiedTrail* and *transportQualifierTSC* in a relationship." + +inv\_agreedTrafficDescriptor + +"**trail** and **agreedTrafficDescriptor** must be involved as *trailTD* and *immediateTrafficDescriptorTrail* in a relationship." + +##### EXCEPTIONS + +IF PRE\_CONDITION inv\_existingTrail NOT\_VERIFIED RAISE\_EXCEPTION + +unknownTrail; + +IF POST\_CONDITION inv\_agreedServiceCharacteristics NOT\_VERIFIED RAISE\_EXCEPTION + +invalidServiceCharacteristicsRequested; + +IF POST\_CONDITION inv\_agreedTrafficDescriptor NOT\_VERIFIED RAISE\_EXCEPTION + +invalidTrafficDescriptorRequested; + +} + +#### 7.2.1.4 Create networkTTP + + + +OPERATION createNetworkTTP { + +##### INPUT\_PARAMETERS + +layerND: LayerNetworkDomainChoice; + +pointDir: PointDirectionality; + +suppliedUserIdentifier: UserIdentifier; + +-- zero length string or 0 implies none supplied. + +suppliedUserLabel: GraphicString; + +-- zero length implies none supplied. + +##### OUTPUT\_PARAMETERS + +networkTTP: NetworkTTPChoice; + +##### RAISED\_EXCEPTIONS + +userIdentifierNotUnique: UserIdentifier; + +failureToCreateNetworkTTP: NULL; + +failureToSetUserIdentifier: NULL; + +##### BEHAVIOUR + +##### SEMI\_FORMAL + +##### PARAMETER\_MATCHING + +layerND: INFORMATION OBJECT: tmLayerNetworkDomain> + +suppliedUserIdentifier: + +pointDir: + +networkTTP: + +suppliedUserLabel: + +##### PRE\_CONDITIONS + +inv\_uniqueUserIdentifier + +"**suppliedUserIdentifier** shall not be equal to *resourceId* of any element in a relationship where **layerND** refers to *containerLND*." + +##### POST\_CONDITIONS + +inv\_existingNetworkTTP + +"**networkTTP** and **layerND** must respectively refer to *element* and *containerLND* in a ** relationship." + +inv\_agreedUserIdentifier + +"*resourceId* of *tmNetworkTTP* referenced by **networkTTP** is equal to **suppliedUserIdentifier**, if it is supplied." + +##### EXCEPTIONS + +IF PRE\_CONDITION inv\_uniqueUserIdentifier NOT\_VERIFIED RAISE\_EXCEPTION +userIdentifierNotUnique; + +IF POST\_CONDITION inv\_existingNetworkTTP NOT\_VERIFIED RAISE\_EXCEPTION +failureToCreateNetworkTTP; + +IF POST\_CONDITION inv\_agreedUserIdentifier NOT\_VERIFIED RAISE\_EXCEPTION +failureToSetUserIdentifier; + +} + +#### 7.2.1.5 Delete networkTTP + + + +OPERATION deleteNetworkTTP { + +##### INPUT\_PARAMETERS + +layerND: LayerNetworkDomainChoice; + +networkTTP: NetworkTTPChoice; + +##### OUTPUT\_PARAMETERS + +-- none + +##### RAISED\_EXCEPTIONS + +invalidNetworkTTP: NetworkTTPChoice; + +networkTTPTerminatesTrail: NetworkTTPChoice; + +networkTTPAssociatedWithSubnetwork: NetworkTTPChoice; + +networkTTPAssociatedWithAccessGroup: NetworkTTPChoice; + +failureToDeleteNetworkTTP: NULL; + +##### BEHAVIOUR + +##### SEMI\_FORMAL + +##### PARAMETER\_MATCHING + +layerND: ; + +networkTTP: ; + +##### PRE\_CONDITIONS + +inv\_existingNetworkTTP + +"**networkTTP** must refer to *element* in a ** relationship where **layerND** refers to *containerLND*." + +inv\_noTrailTermination + +"**networkTTP** may not refer to a *endNTTP* or *z\_endNTTP* in any ** relationship." + +inv\_noSubnetworkAssociation + +"The **networkTTP** shall not refer to *extremity* of a ** relationship where *abstractionSNTP* references *elementSNTP* of a ** relationship." + +![UML Class Diagram showing relationships between subnetwork, subnetworkTP, and networkTTP classes.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +classDiagram + class subnetwork + class subnetworkTP + class networkTTP + + subnetwork "1..1" containerSN -- "1..N" elementSNTP : subnetworkIsDelimitedBy + elementSNTP "1..N" abstractionSNTP -- "1..1" extremity : subnetworkTPsRelatedToExtremity + extremity -- networkTTP + +``` + +UML Class Diagram showing relationships between subnetwork, subnetworkTP, and networkTTP classes. + +inv\_noSubnetworkAssociation + +" + +inv\_noAccessGroupAssociation + +"**networkTTP** may not refer to *elementTTP* in an ** relationship." + +POST\_CONDITIONS + +inv\_noNetworkTTP + +"**networkTTP** does not refer to *element* in any ** relationship ." + +EXCEPTIONS + +IF PRE\_CONDITION inv\_existingNetworkTTP NOT\_VERIFIED RAISE\_EXCEPTION +invalidNetworkTTP; + +IF PRE\_CONDITION inv\_noTrailTermination NOT\_VERIFIED RAISE\_EXCEPTION +networkTTPTerminatesTrail; + +IF PRE\_CONDITION inv\_noSubnetworkAssociation NOT\_VERIFIED RAISE\_EXCEPTION +networkTTPAssociatedWithSubnetwork; + +IF PRE\_CONDITION inv\_noAccessGroupAssociation NOT\_VERIFIED RAISE\_EXCEPTION +networkTTPAssociatedWithAccessGroup; + +IF POST\_CONDITION inv\_noNetworkTTP NOT\_VERIFIED RAISE\_EXCEPTION +failureToDeleteNetworkTTP; + +} + +#### 7.2.1.6 Associate networkTTP with access group + + + +OPERATION associateNetworkTTPWithAccessGroup{ + +INPUT\_PARAMETERS + +layerND: LayerNetworkDomainChoice; +accessGroup: AccessGroupChoice; +networkTTP: NetworkTTPChoice; + +OUTPUT\_PARAMETERS + +-- none + +RAISED\_EXCEPTIONS + +networkTTPAndAccessGroupNotCompatible: NULL; +networkTTPAlreadyAssociated: NULL; +failureToAssociateNetworkTTP: NULL; + +##### BEHAVIOUR + +##### SEMI\_FORMAL + +##### PARAMETER\_MATCHING + +layerND: ; +accessGroup: ; +networkTTP:; + +##### PRE\_CONDITIONS + +inv\_networkTTPAndAccessGroupExistingAndCompatible + +"**networkTTP** and **accessGroup** shall refer to *element* of the same relationship where **layerND** refers to *containerLND*." + +inv\_networkTTPNotAlreadyAssociated + +"**networkTTP** shall not refer to *elementTTP* in any relationship." + +##### POST\_CONDITIONS + +inv\_networkTTPAssociated + +"**networkTTP** refers to *elementTTP* in an relationship where **accessGroup** refers to *containerAG*." + +##### EXCEPTIONS + +IF PRE\_CONDITION inv\_networkTTPAndAccessGroupExistingAndCompatible NOT\_VERIFIED +RAISE\_EXCEPTION + +networkTTPAndAccessGroupNotCompatible; + +IF PRE\_CONDITION inv\_networkTTPNotAlreadyAssociated NOT\_VERIFIED\_RAISE\_EXCEPTION +networkTTPAlreadyAssociated; + +IF POST\_CONDITION inv\_networkTTPAssociated NOT\_VERIFIED RAISE\_EXCEPTION +failureToAssociateNetworkTTP; + +} + +#### 7.2.1.7 Disassociate networkTTP from access group + + + +OPERATION disassociateNetworkTTPfromAccessGroup { + +##### INPUT\_PARAMETERS + +layerND: LayerNetworkDomainChoice; +accessGroup: AccessGroupChoice; +networkTTP: NetworkTTPChoice; + +##### OUTPUT\_PARAMETERS + +-- none + +##### RAISED\_EXCEPTIONS + +networkTTPAndAccessGroupNotCompatible: NULL; +networkTTPNotAssociated: NULL; +failureToDisassociate: NULL; + +##### BEHAVIOUR + +##### SEMI\_FORMAL + +##### PARAMETER\_MATCHING + +layerND: ; +accessGroup: ; +networkTTP: ; + +##### PRE\_CONDITIONS + +inv\_networkTTPAssociated + +"**networkTTP** refers to *elementTTP* of relationship where **accessGroup** refers to *containerAG*." + +``` + +POST_CONDITIONS +inv_networkTTPDisassociated + "networkTTP shall not refer to elementTTP in an relationship + where accessGroup refers to containerTTP." + +EXCEPTIONS + IF PRE_CONDITION inv_networkTTPAndAccessGroupExistingAndCompatible NOT_VERIFIED + RAISE_EXCEPTION + networkTTPAndAccessGroupNotCompatible; + IF PRE_CONDITION inv_networkTTPAssociated NOT_VERIFIED RAISE_EXCEPTION + networkTTPNotAssociated; + IF POST_CONDITION inv_networkTTPDisassociated NOT_VERIFIED RAISE_EXCEPTION + failureToDisassociate; +} + +``` + +#### 7.2.1.8 Associate networkTTP with subnetwork + +``` + + +OPERATION associateNetworkTTPWithSubnetwork { + INPUT_PARAMETERS + layerND: LayerNetworkDomainChoice; + subnetwork: SubnetworkChoice; + networkTTP: NetworkTTPChoice; + + OUTPUT_PARAMETERS + -- none + + RAISED_EXCEPTIONS + networkTTPAndSubnetworkNotCompatible: NULL; + networkTTPAssociated: NetworkTTPChoice; + failureToAssociateNetworkTTP: NULL; + + BEHAVIOUR + SEMI_FORMAL + PARAMETER_MATCHING + layerND: ; + subnetwork: ; + networkTTP: ; + + PRE_CONDITIONS + inv_networkTTPAndSubnetworkExistingAndCompatible + "networkTTP and subnetwork shall refer to element of the same + relationship where layerND refers to containerLND." + + inv_networkTTPNotAssociated + "The networkTTP shall not refer to extremity of a relationship + where abstractionSNTP references elementSNTP of a relationship." + + POST_CONDITIONS + inv_networkTTPAssociated + "networkTTP refers to extremity of a relationship where + abstractionSNTP, which is a subnetworkTP, is also referencing elementSNTP of a + relationship where subnetwork refers to containerSN." + +``` + +![UML Class Diagram for inv_networkTTPNotAssociated](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +classDiagram + class subnetwork + class subnetworkTP + class networkTTP + subnetwork "1..1" containerSN -- "(1..N)" elementSNTP : subnetworkIsDelimitedBy + subnetworkTP "1..N" abstractionSNTP -- "(1..1)" extremity : subnetworkTPIsRelatedToExtremity + networkTTP + +``` + +UML Class Diagram for inv\_networkTTPNotAssociated + +inv\_networkTTPNotAssociated + +![UML Class Diagram for inv_networkTTPAssociated](5445597cceefaca1ac89e710fe339325_img.jpg) + +``` + +classDiagram + class subnetwork + class subnetworkTP + class networkTTP + subnetwork "1..1" containerSN -- "(1..N)" elementSNTP : subnetworkIsDelimitedBy + subnetworkTP "1..N" abstractionSNTP -- "(1..1)" extremity : subnetworkTPIsRelatedToExtremity + networkTTP + +``` + +UML Class Diagram for inv\_networkTTPAssociated + +inv\_networkTTPAssociated + +" + +##### EXCEPTIONS + +``` + + IF PRE_CONDITION inv_networkTTPAndSubnetworkExistingAndCompatible NOT_VERIFIED + RAISE_EXCEPTION + networkTTPAndSubnetworkNotCompatible; + IF PRE_CONDITION inv_networkTTPNotAssociated NOT_VERIFIED + RAISE_EXCEPTION + networkTTPAssociated; + IF POST_CONDITION inv_networkTTPAssociated NOT_VERIFIED + RAISE_EXCEPTION + failureToAssociateNetworkTTP; + } + +``` + +#### 7.2.1.9 Disassociate networkTTP from subnetwork + + + OPERATION disassociateNetworkTTPfromSubnetwork { + +##### INPUT\_PARAMETERS + +``` + + layerND: LayerNetworkDomainChoice; + subnetwork: SubnetworkChoice; + networkTTP: NetworkTTPChoice; + +``` + +##### OUTPUT\_PARAMETERS + +``` + + -- none + +``` + +##### RAISED\_EXCEPTIONS + +``` + + networkTTPAndSubnetworkNotCompatible: NULL; + networkTTPNotAssociated: NTTPId + networkTTPConnected: NULL; + failureToDisassociate: NULL; + +``` + +##### BEHAVIOUR + +##### SEMI\_FORMAL + +##### PARAMETER\_MATCHING + +``` + + layerND: ; + subnetwork: + networkTTP: ; + +``` + +##### PRE\_CONDITIONS + +``` + + inv_networkTTPAssociated + +``` + +"**networkTTP** refers to *extremity* of a relationship where *abstractionSNTP*, which is a **subnetworkTP**, is also *elementSNTP* of a relationship where **subnetwork** refers to *containerSN*. + +![UML Class Diagram for inv_networkTTPNotAssociated showing subnetwork, subnetworkTP, and networkTTP with dashed boxes.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +``` + +classDiagram + class subnetwork { + } + class subnetworkTP { + } + class networkTTP { + } + + subnetwork "1..1" -- "1..N" subnetworkTP : subnetworkIsDelimitedBy + note for subnetwork "containerSN" + note for subnetworkTP "elementSNTP" + + subnetworkTP "1..N" -- "1..1" networkTTP : subnetworkTPIsRelatedToExtremity + note for subnetworkTP "abstractionSNTP" + note for networkTTP "extremity" + +``` + +UML Class Diagram for inv\_networkTTPNotAssociated showing subnetwork, subnetworkTP, and networkTTP with dashed boxes. + +**inv\_networkTTPNotAssociated** + +![UML Class Diagram for inv_networkTTPAssociated showing subnetwork, subnetworkTP, and networkTTP with solid boxes.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +``` + +classDiagram + class subnetwork { + } + class subnetworkTP { + } + class networkTTP { + } + + subnetwork "1..1" -- "1..N" subnetworkTP : subnetworkIsDelimitedBy + note for subnetwork "containerSN" + note for subnetworkTP "elementSNTP" + + subnetworkTP "1..N" -- "1..1" networkTTP : subnetworkTPIsRelatedToExtremity + note for subnetworkTP "abstractionSNTP" + note for networkTTP "extremity" + +``` + +UML Class Diagram for inv\_networkTTPAssociated showing subnetwork, subnetworkTP, and networkTTP with solid boxes. + +**inv\_networkTTPAssociated** + +" + +inv\_networkTTPNotAssociated + +"abstractionSNTP (which is a **subnetworkTP**) of a relationship where **networkTTP** refers to extremity, shall not reference a\_endSNTP or z\_endSNTP of a relationship. + +![UML Class Diagram for inv_networkTTPNotConnected showing subnetworkConnection, subnetworkTP, and networkTTP.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +``` + +classDiagram + class subnetworkConnection { + } + class subnetworkTP { + } + class networkTTP { + } + + subnetworkConnection "1..1" -- "1..1" subnetworkTP : subnetworkConnectionIsTerminatedByPointToPoint + note for subnetworkConnection "transportEntity a_endSNTP / z_endSNTP" + + subnetworkTP "1..N" -- "1..1" networkTTP : subnetworkTPIsRelatedToExtremity + note for subnetworkTP "abstractionSNTP" + note for networkTTP "extremity" + +``` + +UML Class Diagram for inv\_networkTTPNotConnected showing subnetworkConnection, subnetworkTP, and networkTTP. + +**inv\_networkTTPNotConnected** + +" + +##### **POST\_CONDITIONS** + +inv\_networkTTPNotAssociated + +<"**networkTTP** shall not refer to *extremity* of a relationship where *abstractionSNTP* references *elementSNTP* of a relationship. " + +##### **EXCEPTIONS** + +IF PRE\_CONDITION inv\_networkTTPAndSubnetworkExistingAndCompatible NOT\_VERIFIED +RAISE\_EXCEPTION +    networkTTPAndSubnetworkNotCompatible; +IF PRE\_CONDITION inv\_networkTTPAssociated NOT\_VERIFIED RAISE\_EXCEPTION +    networkTTPNotAssociated; +IF PRE\_CONDITION inv\_networkTTPNotConnected NOT\_VERIFIED RAISE\_EXCEPTION +    networkTTPConnected; +IF POST\_CONDITION inv\_networkTTPNotAssociated NOT\_VERIFIED RAISE\_EXCEPTION +    failureToDisassociate; + +} + +## 7.3 Reporting interfaces + +### 7.3.1 Trail provisioning reporting interface + +The trail provisioning reporting interface reports the immediate set-up, release and modification of point-to-point trails as well as the creation and deletion of network TTPs and the association and disassociation of network TTPs with access groups and subnetworks. The interface is required to satisfy the enterprise requirements stated in: + +<"Recommendation G.852.6,"COMMUNITY trail management, ACTION: report trail setup>, +<"Recommendation G.852.6,"COMMUNITY trail management, ACTION: report trail release>, +<"Recommendation G.852.6,"COMMUNITY trail management, ACTION: report trail modification>, +<"Recommendation G.852.6,"COMMUNITY trail management, ACTION: report trail termination point creation>, +<"Recommendation G.852.6,"COMMUNITY trail management, ACTION: report trail termination point deletion>, +<"Recommendation G.852.6,"COMMUNITY trail management, ACTION: report association of trail termination point with access group>, +<"Recommendation G.852.6,"COMMUNITY trail management, ACTION: report disassociation of trail termination point from access group>, +<"Recommendation G.852.6,"COMMUNITY trail management, ACTION: report association of trail termination point with subnetwork>, +<"Recommendation G.852.6,"COMMUNITY trail management, ACTION: report disassociation of trail termination point from subnetwork>. + +By inheriting the properties of the the trailProvisioningReportingIfce provides the capability of reporting the change of the resource identifier of the resources involved. + +``` +COMPUTATIONAL INTERFACE trailProvisioningReportingIfce { + DERIVED FROM + OPERATION { + ; + ; + ; + ; + ; + ; + ; + ; + ; + } +} +``` + +#### 7.3.1.1 Report point-to-point trail set-up + +``` + +OPERATION reportPointToPointTrailSet_up{ + INPUT_PARAMETERS + newTrail: TrailChoice; + connectedAEndNetworkTTP: NetworkTTPChoice; + connectedZEndNetworkTTP: NetworkTTPChoice; + layerND: LayerNetworkDomainChoice; + + OUTPUT_PARAMETERS + -- none + + RAISED EXCEPTIONS + -- none +} +``` + +BEHAVIOUR +SEMI\_FORMAL + +PARAMETER\_MATCHING + +newTrail: ; +connectedAEndNetworkTTP: ; +connectedZEndNetworkTTP: ; +layerND: ; + +TRIGGERING CONDITIONS + +PRE\_CONDITIONS + +inv\_layerNDContainment + +"**connectedAEndNetworkTTP** and **connectedZEndNetworkTTP** are referencing *element* in a + relationship where **layerND** is referencing *containerLND*." + +POST\_CONDITIONS + +inv\_connectedTrail + +"**connectedAEndNetworkTTP**, **connectedZEndNetworkTTP** and **newTrail** respectively reference +*a\_endNTTP*, *z\_endNTTP* and *transportEntityTrail* in a +relationship." + +EXCEPTIONS + +-- none + +} + +#### 7.3.1.2 Report trail release + + + +OPERATION reportTrailRelease { + +INPUT\_PARAMETERS + +trail: TrailChoice; +layerND: LayerNetworkDomainChoice; + +OUTPUT\_PARAMETERS + +-- none + +RAISED EXCEPTIONS + +-- none + +BEHAVIOUR + +SEMI\_FORMAL + +PARAMETER\_MATCHING + +trail: ; +layerND: ; + +TRIGGERING CONDITIONS + +PRE\_CONDITIONS + +inv\_connectedTrail + +"**trail** must refer to *transportEntityTrail* in a relationship." + +POST\_CONDITIONS + +inv\_disconnectedTrail + +"**trail** is not allowed participating in a relationship referencing +*transportEntityTrail*." + +EXCEPTIONS + +-- none + +} + +#### 7.3.1.3 Report trail modification + + + +OPERATION reportTrailModification { + +##### INPUT\_PARAMETERS + +trail: TrailChoice; +layerND: LayerNetworkDomainChoice; +newTrafficDescriptor: ImmediateTrafficDescriptorId ; +newServiceCharacteristics: TrailServiceCharacteristicsId; +agreedTrafficDescriptor: ImmediateTrafficDescriptorId ; +agreedServiceCharacteristics: TrailServiceCharacteristicsId; + +##### OUTPUT\_PARAMETERS + +-- none + +##### RAISED EXCEPTIONS + +-- none + +##### BEHAVIOUR + +##### SEMI\_FORMAL + +##### PARAMETER\_MATCHING + +trail: ; +layerND: ; +newTrafficDescriptor: ; +newServiceCharacteristics: ; +agreedTrafficDescriptor: ; +agreedServiceCharacteristics: ; + +##### TRIGGERING CONDITIONS + +###### PRE\_CONDITIONS + +inv\_newServiceCharacteristics + +"**trail** and **newServiceCharacteristics** must not be involved as *transportQualifiedTrail* and *transportQualifierTSC* in a relationship." + +inv\_newTrafficDescriptor + +"**trail** and **newTrafficDescriptor** must not be involved as *trailTD* and *immediateTrafficDescriptorTrail* in a relationship." + +###### POST\_CONDITIONS + +inv\_agreedServiceCharacteristics + +"**trail** and **agreedServiceCharacteristics** must be involved as *transportQualifiedTrail* and *transportQualifierTSC* in a relationship." + +inv\_agreedTrafficDescriptor + +"**trail** and **agreedTrafficDescriptor** must be involved as *trailTD* and *immediateTrafficDescriptorTrail* in a relationship." + +##### EXCEPTIONS + +-- none + +} + +#### 7.3.1.4 Report networkTTP creation + + +OPERATION reportNetworkTTPCreation { +    INPUT\_PARAMETERS +        networkTTP: NetworkTTPChoice; +        layerND: LayerNetworkDomainChoice; +        pointDir: PointDirectionality; + +    OUTPUT\_PARAMETERS +        -- none + +    RAISED\_EXCEPTIONS +        -- none + +    BEHAVIOUR +    SEMI-FORMAL +        PARAMETER\_MATCHING +            networkTTP: ; +            layerND: ; +            pointDir: ; + +        TRIGGERING\_CONDITIONS +        PRE\_CONDITIONS +            -- none + +        POST\_CONDITIONS +            inv\_existingNetworkTTP +            "**networkTTP** must refer to *element* in a relationship where +            **layerND** refers to *containerLND*." + +    EXCEPTIONS +        -- none +} + +#### 7.3.1.5 Report networkTTP deletion + + +OPERATION reportNetworkTTPDeletion { +    INPUT\_PARAMETERS +        networkTTP: NetworkTTPChoice; +        layerND: LayerNetworkDomainChoice; + +    OUTPUT\_PARAMETERS +        -- none + +    RAISED\_EXCEPTIONS +        -- none +} + +##### BEHAVIOUR SEMI-FORMAL + +##### PARAMETER\_MATCHING + +networkTTP: ; +layerND: ; + +##### TRIGGERING\_CONDITIONS + +##### PRE\_CONDITIONS + +inv\_existingNetworkTTP + +"**networkTTP** must refer to *element* in a relationship where **layerND** refers to *containerLND*." + +inv\_noTrailTermination + +"**networkTTP** may not refer to *a\_endNTTP* or *z\_endNTTP* in any relationship." + +inv\_noSubnetworkAssociation + +"**networkTTP** shall not refer to *extremity* of a relationship where *abstractionSNTP* references *elementSNTP* of a relationship." + +![UML Class Diagram showing the hierarchy for networkTTP. At the top is a dashed box labeled 'subnetwork'. Below it is a dashed box labeled 'subnetworkTP'. At the bottom is a solid box labeled 'networkTTP'. Associations are shown between 'subnetwork' and 'subnetworkTP' (multiplicity 1..1 at subnetwork, 1..N at subnetworkTP, role 'elementSNTP', association 'subnetworkIsDelimitedBy'), and between 'subnetworkTP' and 'networkTTP' (multiplicity 1..N at subnetworkTP, 1..1 at networkTTP, role 'extremity', association 'subnetworkTPIsRelatedToExtremity'). The role 'containerSN' is also indicated on the 'subnetwork' side of the first association.](ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg) + +``` + +classDiagram + class subnetwork + class subnetworkTP + class networkTTP + + subnetwork "1..1" -- "1..N" subnetworkTP : elementSNTP, subnetworkIsDelimitedBy + subnetworkTP "1..N" -- "1..1" networkTTP : extremity, subnetworkTPIsRelatedToExtremity + subnetwork --- containerSN + +``` + +UML Class Diagram showing the hierarchy for networkTTP. At the top is a dashed box labeled 'subnetwork'. Below it is a dashed box labeled 'subnetworkTP'. At the bottom is a solid box labeled 'networkTTP'. Associations are shown between 'subnetwork' and 'subnetworkTP' (multiplicity 1..1 at subnetwork, 1..N at subnetworkTP, role 'elementSNTP', association 'subnetworkIsDelimitedBy'), and between 'subnetworkTP' and 'networkTTP' (multiplicity 1..N at subnetworkTP, 1..1 at networkTTP, role 'extremity', association 'subnetworkTPIsRelatedToExtremity'). The role 'containerSN' is also indicated on the 'subnetwork' side of the first association. + +inv\_noSubnetworkAssociation + +" + +inv\_noAccessGroupAssociation + +"**networkTTP** may not refer to *elementTTP* in an relationship." + +##### POST\_CONDITIONS + +inv\_noNetworkTTP + +"**networkTTP** does not refer to *element* in a relationship." + +##### EXCEPTIONS + +-- none + +} + +#### 7.3.1.6 Report association of networkTTP with access group + + + +OPERATION reportAssociationOfNetworkTTPWithAccessGroup { + +##### INPUT\_PARAMETERS + +layerND: LayerNetworkDomainChoice; + +accessGroup: AccessGroupChoice; + +networkTTP: NetworkTTPChoice; + +##### OUTPUT PARAMETERS + +-- none + +##### RAISED EXCEPTIONS + +-- none + +##### BEHAVIOUR + +###### SEMI-FORMAL + +##### PARAMETER\_MATCHING + +layerND: ; + +accessGroup: ; + +networkTTP: ; + +##### TRIGGERING\_CONDITIONS + +###### PRE\_CONDITIONS + +inv\_networkTTPAndAccessGroupExistingAndCompatible + +"**networkTTP** and **accessGroup** shall refer to *element* of the same + + relationship where **layerND** refers to *containerLND*." + +inv\_networkTTPNotAlreadyAssociated + +"**networkTTP** shall not refer to *elementTTP* in any relationship." + +###### POST\_CONDITIONS + +inv\_networkTTPAssociated + +"**networkTTP** refers to *elementTTP* of an relationship where **accessGroup** refers to *containerAG*." + +##### EXCEPTIONS + +-- none + +} + +#### 7.3.1.7 Report disassociation of networkTTP from access group + + + +OPERATION reportDisassociationOfNetworkTTPFromAccessGroup { + +##### INPUT\_PARAMETERS + +layerND: LayerNetworkDomainChoice; + +accessGroup: AccessGroupChoice; + +networkTTP: NetworkTTPChoice; + +##### OUTPUT PARAMETERS + +-- none + +##### RAISED\_EXCEPTIONS + +-- none + +BEHAVIOUR +SEMI-FORMAL + +##### PARAMETER\_MATCHING + +layerND: ; +accessGroup: ; +networkTTP: ; + +##### TRIGGERING\_CONDITIONS + +###### PRE\_CONDITIONS + +inv\_networkTTPAssociated +"networkTTP refers to *elementTTP* of an relationship +where **accessGroup** refers to *containerAG*." + +###### POST\_CONDITIONS + +inv\_networkTTPDisassociated +"networkTTP shall not refer to *elementTTP* in an +relationship where **accessGroup** refers to *containerAG*." + +##### EXCEPTIONS + +-- none + +} + +#### 7.3.1.8 Report association of networkTTP with subnetwork + + +OPERATION reportAssociationOfNetworkTTPWithSubnetwork { + +##### INPUT\_PARAMETERS + +layerND: LayerNetworkDomainChoice; +subnetwork: SubnetworkChoice; +networkTTP: NetworkTTPChoice; + +##### OUTPUT PARAMETERS + +-- none + +##### RAISED EXCEPTIONS + +-- none + +BEHAVIOUR +SEMI-FORMAL + +##### PARAMETER\_MATCHING + +layerND: ; +subnetwork: ; +networkTTP: ; + +##### TRIGGERING\_CONDITIONS + +###### PRE\_CONDITIONS + +inv\_networkTTPAndSubnetworkExistingAndCompatible +"networkTTP and **subnetwork** shall refer to *element* of the same + relationship where **layerND** refers to *containerLND*." + +inv\_networkTTPNotAssociated +"networkTTP shall not refer to *extremity* of a relationship +where *abstractionSNTP* references *elementSNTP* of a relationship." + +![Two UML class diagrams illustrating network associations. The left diagram shows a dashed box for 'subnetwork' connected to 'elementSNTP' via 'containerSN' (1..1) and 'subnetworkIsDelimitedBy' (1..N). 'elementSNTP' is connected to a dashed box for 'subnetworkTP' via 'abstractionSNTP' (1..N) and 'subnetworkTPsRelatedToExtremity' (1..1). 'subnetworkTP' is connected to 'networkTTP' via 'extremity' (1..1). The right diagram shows a solid box for 'subnetwork' connected to 'elementSNTP' via 'containerSN' (1..1) and 'subnetworkIsDelimitedBy' (1..N). 'elementSNTP' is connected to a solid box for 'subnetworkTP' via 'abstractionSNTP' (1..N) and 'subnetworkTPsRelatedToExtremity' (1..1). 'subnetworkTP' is connected to 'networkTTP' via 'extremity' (1..1). Below the diagrams are the labels 'inv_networkTTPNotAssociated' and 'inv_networkTTPAssociated'.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +Two UML class diagrams illustrating network associations. The left diagram shows a dashed box for 'subnetwork' connected to 'elementSNTP' via 'containerSN' (1..1) and 'subnetworkIsDelimitedBy' (1..N). 'elementSNTP' is connected to a dashed box for 'subnetworkTP' via 'abstractionSNTP' (1..N) and 'subnetworkTPsRelatedToExtremity' (1..1). 'subnetworkTP' is connected to 'networkTTP' via 'extremity' (1..1). The right diagram shows a solid box for 'subnetwork' connected to 'elementSNTP' via 'containerSN' (1..1) and 'subnetworkIsDelimitedBy' (1..N). 'elementSNTP' is connected to a solid box for 'subnetworkTP' via 'abstractionSNTP' (1..N) and 'subnetworkTPsRelatedToExtremity' (1..1). 'subnetworkTP' is connected to 'networkTTP' via 'extremity' (1..1). Below the diagrams are the labels 'inv\_networkTTPNotAssociated' and 'inv\_networkTTPAssociated'. + +###### POST\_CONDITIONS + +inv\_networkTTPAssociated + +"**networkTTP** refers to *extremity* of a ** relationship where *abstractionSNTP*, which is a **subnetworkTP**, is also *elementSNTP* of a ** relationship where **subnetwork** refers to *containerSN*." + +##### EXCEPTIONS + +-- none + +} + +#### 7.3.1.9 Report disassociation of networkTTP from subnetwork + + + OPERATION reportDisassociationOfNetworkTTPFromSubnetwork { + +##### INPUT\_PARAMETERS + +layerND: LayerNetworkDomainChoice; + subnetwork: SubnetworkChoice; + networkTTP: NetworkTTPChoice; + +##### OUTPUT\_PARAMETERS + +-- none + +##### RAISED\_EXCEPTIONS + +-- none + +##### BEHAVIOUR + +###### SEMI-FORMAL + +##### PARAMETER\_MATCHING + +layerND: ; + subnetwork: ; + networkTTP: ; + +##### TRIGGERING\_CONDITIONS + +###### PRE\_CONDITIONS + +inv\_networkTTPAssociated + +"**networkTTP** refers to *extremity* of a ** relationship where *abstractionSNTP*, which is a **subnetworkTP**, is also *elementSNTP* of a ** relationship where **subnetwork** refers to *containerSN*." + +![UML Class Diagram for inv_networkTTPNoAssociated](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +``` + +classDiagram + class subnetwork { + <> + } + class subnetworkTP { + <> + } + class networkTTP + subnetwork "1..1" -- "1..N" subnetworkTP : subnetworkIsDelimitedBy + note for subnetwork "containerSN" + note for subnetworkTP "elementSNTP" + subnetworkTP "1..N" -- "1..1" networkTTP : subnetworkTPsRelatedToExtremity + note for subnetworkTP "abstractionSNTP" + note for networkTTP "extremity" + +``` + +UML Class Diagram for inv\_networkTTPNoAssociated + +inv\_networkTTPNoAssociated + +![UML Class Diagram for inv_networkTTPAssociated](fa01531ea2c45beeb4036005da3037a4_img.jpg) + +``` + +classDiagram + class subnetwork + class subnetworkTP + class networkTTP + subnetwork "1..1" -- "1..N" subnetworkTP : subnetworkIsDelimitedBy + note for subnetwork "containerSN" + note for subnetworkTP "elementSNTP" + subnetworkTP "1..N" -- "1..1" networkTTP : subnetworkTPsRelatedToExtremity + note for subnetworkTP "abstractionSNTP" + note for networkTTP "extremity" + +``` + +UML Class Diagram for inv\_networkTTPAssociated + +inv\_networkTTPAssociated + +" + +inv\_networkTTPNotConnected + +"abstractionSNTP (which is a **subnetworkTP**) of a relationship where **networkTTP** refers to extremity, shall not reference a\_endSNTP or z\_endSNTP of a relationship." + +![UML Class Diagram for inv_networkTTPNotConnected](24c9e038a791677ed33100667b64f7e6_img.jpg) + +``` + +classDiagram + class subnetworkConnection { + <> + } + class subnetworkTP + class networkTTP + subnetworkConnection "1..1" -- "1..1" subnetworkTP : subnetworkConnectionIsTerminatedByPointToPoint + note for subnetworkConnection "transportEntity a_endSNTP / z_endSNTP" + subnetworkTP "1..N" -- "1..1" networkTTP : subnetworkTPsRelatedToExtremity + note for subnetworkTP "abstractionSNTP" + note for networkTTP "extremity" + +``` + +UML Class Diagram for inv\_networkTTPNotConnected + +inv\_networkTTPNotConnected + +" + +###### POST\_CONDITIONS + +inv\_networkTTPNotAssociated + +"**networkTTP** shall not refer to *extremity* of a relationship where *abstractionSNTP* references *elementSNTP* of a relationship." + +##### EXCEPTIONS + +-- none + +} + +## 7.4 ASN.1 supporting productions + +In this specification, when an interface name is used within an ASN.1 production, the same label will be used, starting with a capital letter. The complete ASN.1 type definition for this query interface (e.g. use of ObjectIdentifier, INTEGER, ...) will be developed as part of the engineering viewpoint, with the concerned technology. + +``` +AccessGroupChoice ::= CHOICE { + tmAccessGroupQueryIfce TmAccessGroupQueryIfce, + userIdentifier UserIdentifier } ; + +ImmediateTrafficDescriptorId ::= TmTrafficDescriptorQueryIfce; + +LayerNetworkDomainChoice ::= CHOICE { + tmLayerNetworkDomainQueryIfce TmLayerNetworkDomainQueryIfce, + userIdentifier UserIdentifier } ; + +NetworkTTPChoice ::= CHOICE { + tmNetworkTTPQueryIfce TmNetworkTTPQueryIfce, + userIdentifier UserIdentifier} ; + +SequenceOfNetworkTTPChoice ::= SEQUENCE OF { + a_endNetworkTTP NetworkTTPChoice, + z_endNetworkTTP NetworkTTPChoice } ; + +SubnetworkChoice ::= CHOICE { + tmSubnetworkQueryIfce TmSubnetworkQueryIfce, + userIdentifier UserIdentifier} ; + +TrailChoice ::= CHOICE { + tmTrailQueryIfce TmTrailQueryIfce, + userIdentifier UserIdentifier} ; + +TrailServiceCharacteristicsId ::= TmTrailServiceCharacteristisQueryIfce; + +UserIdentifier ::= SimpleNameType; +``` + + + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..284eed19aa4504e244cb67bd8df0308fded5e470 --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fde02d4624b41469cc5ae1ec01669052c9ebf94835f69fbe6e273f2379d25c8 +size 22283 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f91fd368f3d4dd380b2b2068dcab3a079b8bf3b --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:556fc09d3d2eb1a25d3093df29a17ea51d75b4dfeac468a7bc27c05944336cdb +size 7524 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/0908107b858fa3783d10d93b3a3444b2_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/0908107b858fa3783d10d93b3a3444b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..143364737e44220d393f6ad2bd302d635f0d0fdb --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/0908107b858fa3783d10d93b3a3444b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16037617b707e031b58f713f9056039b14375dc6b666e0d8705b0f473f0dc174 +size 12842 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9af9cbe95ff1591f10c44d8abcd618f50bd0108 --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46248a6a8629356ed08da7df2a8090637b5442042b3870521c00d41613976171 +size 47825 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e878b24d9f1dec9248141b6a448cd32b75eed6b --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1428ab1765c398e80b987dc4c4a36a6a800bde0706add909f1e622215456ca61 +size 47683 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a675960d39d719fac0ce0fff637e677526fdd7b --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba7bd77e9a96af4db1b1a9c18538af7debf322523a2fda799eacfafbbd49c823 +size 51998 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e868e8f59153e6035efa8379c3173e0e52c9abaa --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ecd33d44e63cd141a8123a66f8ebf6ef6cab7a17385836c75476564434a90dc +size 53866 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..897ec89fca6b7c5439282473d256ffec997f8828 --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c87b17fa60ba61c28578823c9e0f1d6d6cfdd269ae8f3819adc01716d21a67d9 +size 30191 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e59fe4f91a446beaee00d5cbae4e6057ad02c98c --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ea7d4a9df19198428891595d56bdda5f7d62eac8e3ad8a49bf67f59600679fa +size 73827 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..668205b3666556eb606b0228244a7cc08217d362 --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f46c38f198606834997af718a4cb4201e94acef6283e9836c6153a19f53f206 +size 100915 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/50214d232017279410e9c9db8eb75119_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/50214d232017279410e9c9db8eb75119_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8401371f504df1e8102bea7b692d6a5190ae365 --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/50214d232017279410e9c9db8eb75119_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1e79c8207a60cc1142f16ab54739582ef5ee59a6fed977309c606bbf8b59c57 +size 27996 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/5478f70a6cef3e5672b2b22d28830cfb_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/5478f70a6cef3e5672b2b22d28830cfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5fa6760ca6f511435f60073e31b6be99eea9ca5 --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/5478f70a6cef3e5672b2b22d28830cfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59704c250dd315613a05ec797235f8aae98ac23c12ce57eb7475f75cc5e48334 +size 74335 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/67d03c9e89620d73e3786c869e559752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1b162c05f7910e5d25cca15154cd3ae16bcadbe --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/67d03c9e89620d73e3786c869e559752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db173a32323a14df320eaceeb118d6e6925997d3d9eddacc8acc2fa07c1045f9 +size 63443 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/6cc85a2b62fd8a2a3faab29730f20e81_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/6cc85a2b62fd8a2a3faab29730f20e81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4ea81e129357fe78f07cc3f2302f65db19ed4f8 --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/6cc85a2b62fd8a2a3faab29730f20e81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9107e50dcc65715c1fc16fd9fe8f02dcfbf1208afd84ab6cfc68a97c737fd6b +size 62723 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6e5ab1de1d8893526261a2ed1c8036984861bee --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65e1ab30c0430be2a9b9d05efde63e75d298ba708321edfc9d916252503047cc +size 66119 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3aa56dad240154ab4289718b21e7e5e44ac42e1a --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7962c713e6e05bfc8318d7d23e628e39654effede08b221fdc173748126eb36 +size 72810 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e20acb37c31b317fa147b5a021afe649fdd9a6cb --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:feb0dc8baa59d4142de797f16ac134f9363f1c207c71edb92fdf38b650fa53aa +size 19316 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/8269648391c59363ea61243864a2adf7_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74d6ada8024509cdc8e838087c500ffa3851741f --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01325e84cea37a6d7662c02bd637af045cbd14589bd9dae8c8b189441ebc7d16 +size 45251 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60db5bc2c06af07e88941d203d02d3420e99f691 --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bce564b56cdb3bc36d75ab61dbc4ff397f8f0b2aacfc32ece8d2d6130c03f66 +size 68877 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff13827e56c202f72c86032722b7c9d39d647613 --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb6f8a109b4c729f8a314abe206e666b0cd489fdf9a6afb3237a3d7fbbb8e256 +size 38373 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/b05bae46f7079e5c9b1da38adb2319e8_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/b05bae46f7079e5c9b1da38adb2319e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c907277b64ac83af532e71589becb6e4b7c8d49a --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/b05bae46f7079e5c9b1da38adb2319e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:100ce21f3aae2cb5ba63d23d1c37f603f89c052be7fa192c467fa5c2a8bb1b66 +size 19455 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da26c3cfc619343ca784cdf2014a9a3eee1fae41 --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab6ae0edcb3d6baa74e6ea7f38d4dc11c19360a92f1567beecea63695172ef6b +size 57933 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba8233ee879b4fc4a3a2ddd903dfdf6e8950f1ee --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9085a1921c8f1a78519ec941fcb71ba36e0ed8b7b18b51fef1a9e7a9a71fe4e3 +size 61209 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/e05122559f56af5699789b7118d8fe87_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/e05122559f56af5699789b7118d8fe87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40ff4e8ddad32c4edc4c69e2314b457b56d9a59d --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/e05122559f56af5699789b7118d8fe87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eadba3341736bd034ffaa5eeb9ab24b3e166f5f4f180ce4297305e157a61c2ea +size 31780 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4726b81cdbdb75ca10f71db3246658a64953832f --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4258d6e90310f8fb7d999ad8099cd8cf6ab1ca993a48ec20cb6a49d82dac819e +size 30014 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/f732d3320afe06d979aabbd366184254_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/f732d3320afe06d979aabbd366184254_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfdbe343e5fe3e69b4124206e73c5deed56883c2 --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/f732d3320afe06d979aabbd366184254_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:557c9e0fb64bb429cc2243d0aafd03d9ab49182721a7ce6b239a699146f4d118 +size 63758 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.872-202403-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e26445be34b3f6af2b90b74fe2dde296dad485dc --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e832b97f34d68acd871ae2d9be38a46377277122347dbd17a84fd94f2f3c4ded +size 60482 diff --git a/marked/G/T-REC-G.872-202403-I_PDF-E/raw.md b/marked/G/T-REC-G.872-202403-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2c13c145aff27c76e64a38dcd77eca5c29eb0b46 --- /dev/null +++ b/marked/G/T-REC-G.872-202403-I_PDF-E/raw.md @@ -0,0 +1,1620 @@ + + +# Recommendation **ITU-T G.872 (03/2024)** + +SERIES G: Transmission systems and media, digital +systems and networks + +Digital networks – Optical transport networks + +# --- **Architecture of the optical transport network** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +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 | +| General aspects | G.800-G.809 | +| Design objectives for digital networks | G.810-G.819 | +| Synchronization, quality and availability targets | G.820-G.829 | +| Network capabilities and functions | G.830-G.839 | +| SDH network characteristics | G.840-G.849 | +| Management of transport network | G.850-G.859 | +| SDH radio and satellite systems integration | G.860-G.869 | +| Optical transport networks | G.870-G.879 | +| 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.872 + +# Architecture of the optical transport network + +## Summary + +Recommendation ITU-T G.872 describes the functional architecture of the optical transport network (OTN) using the modelling methodology described in Recommendations ITU-T G.800, ITU-T G.805 and ITU-T G.807. OTN functionality is described from a network level viewpoint, considering the characteristic information of OTN clients, client/server layer associations, networking topology, layer network functionality and optical media network structure, which provide multiplexing, routing and supervision of digital clients. The digital layers of the OTN use the frame formats defined in ITU-T G.709. The media portion of the network is described in terms of media constructs, media elements and optical signal maintenance entities. + +Revision 6.0 adds description of fine grain OTN (fgOTN). The description of a flexible optical transport network (FlexO) is enhanced to reflect additional functionality in the 2024 series of ITU-T G.709.x Recommendations. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|---------------------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.872 | 1999-02-26 | 13 | 11.1002/1000/4576 | +| 2.0 | ITU-T G.872 | 2001-11-29 | 15 | 11.1002/1000/5606 | +| 2.1 | ITU-T G.872 (2001) Amd. 1 | 2003-12-14 | 15 | 11.1002/1000/7064 | +| 2.2 | ITU-T G.872 (2001) Cor. 1 | 2005-01-13 | 15 | 11.1002/1000/7483 | +| 2.3 | ITU-T G.872 (2001) Amd. 2 | 2010-07-29 | 15 | 11.1002/1000/10880 | +| 3.0 | ITU-T G.872 | 2012-10-29 | 15 | 11.1002/1000/11786 | +| 3.1 | ITU-T G.872 (2012) Amd. 1 | 2013-11-06 | 15 | 11.1002/1000/11986 | +| 4.0 | ITU-T G.872 | 2017-01-12 | 15 | 11.1002/1000/13086 | +| 5.0 | ITU-T G.872 | 2019-12-22 | 15 | 11.1002/1000/13999 | +| 5.1 | ITU-T G.872 (2019) Amd. 1 | 2021-01-13 | 15 | 11.1002/1000/14522 | +| 6.0 | ITU-T G.872 | 2024-03-08 | 15 | 11.1002/1000/15804 | + +## Keywords + +Optical transport network (OTN), OTN functional architecture. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|--------------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere..... | 2 | +| 3.2 Terms defined in this Recommendation ..... | 3 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 5 | +| 5.1 Notational..... | 5 | +| 5.2 Information structures and interfaces..... | 5 | +| 5.3 Diagrammatic..... | 5 | +| 6 Functional architecture of the OTN..... | 5 | +| 7 OTN digital layers..... | 7 | +| 7.1 Optical data unit layer network ..... | 8 | +| 7.2 Optical transport unit (OTU) layer network..... | 13 | +| 7.3 Client/server associations ..... | 15 | +| 7.4 Flexible OTN interfaces ..... | 16 | +| 8 Architecture of the media network supporting the OTN digital layers ..... | 19 | +| 8.1 Media constructs..... | 19 | +| 8.2 Media element ..... | 20 | +| 8.3 Optical tributary signals..... | 20 | +| 8.4 Management of optical signals ..... | 22 | +| 8.5 Management of media and signals ..... | 22 | +| 8.6 Modulator/demodulator and termination functions ..... | 22 | +| 8.7 Client/server associations ..... | 22 | +| 9 Media network topology..... | 23 | +| 10 Management..... | 23 | +| 10.1 Capabilities ..... | 23 | +| 10.2 Connection supervision techniques ..... | 25 | +| 10.3 Connection supervision applications ..... | 26 | +| 11 OTN survivability techniques..... | 26 | +| Annex A Fine grain flexible optical data unit path layer network ..... | 27 | +| A.1 Fine grain flexible optical data unit path layer network ..... | 27 | +| A.2 Client/server associations ..... | 30 | +| A.3 Management ..... | 31 | +| A.4 OTN survivability techniques..... | 31 | +| Appendix I Relationship between optical channel and optical tributary signal terminology . | 32 | +| Appendix II Use of optical transport networks to carry Flex Ethernet ..... | 34 | + +| | Page | +|-----------------------------------------------------------------------------------|-------------| +| II.1 Overview of Flex Ethernet ..... | 34 | +| II.2 FlexE unaware ..... | 34 | +| II.3 FlexE aware ..... | 34 | +| II.4 FlexE terminating ..... | 35 | +| Appendix III Examples of views of an optical data unit layer network..... | 36 | +| Appendix IV Examples of multi-domain optical transport network applications ..... | 39 | +| Bibliography ..... | 41 | + +# Architecture of the optical transport network + +# 1 Scope + +This Recommendation describes the functional architecture of optical transport networks (OTNs) using the modelling methodology described in [ITU-T G.800] and [ITU-T G.805] for the digital layer networks, and [ITU-T G.807] for the optical media network. OTN functionality is described from a network-level viewpoint. This takes into account the characteristic information (CI) of OTN clients, the client/server layer associations, network topology, the optical media network structure and the layer network functionalities that provide multiplexing, routing, supervision, performance assessment and network survivability for digital clients. The digital layers of the OTN use the frame formats specified in [ITU-T G.709]. The media portion of the network is described in terms of media constructs, media elements and optical signal maintenance entities described in [ITU-T G.807]. This Recommendation provides the functional description of OTN that support digital clients. The support of analogue signals as clients lies outside the scope of this Recommendation. + +# 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.694.1] Recommendation ITU-T G.694.1 (2020), *Spectral grids for WDM applications: DWDM frequency grid*. +- [ITU-T G.694.2] Recommendation ITU-T G.694.2 (2003), *Spectral grids for WDM applications: CWDM wavelength grid*. +- [ITU-T G.695] Recommendation ITU-T G.695 (2018), *Optical interfaces for coarse wavelength division multiplexing applications*. +- [ITU-T G.698.1] Recommendation ITU-T G.698.1 (2023), *Multichannel DWDM applications with single-channel optical interfaces*. +- [ITU-T G.698.2] Recommendation ITU-T G.698.2 (2018), *Amplified multichannel dense wavelength division multiplexing applications with single channel optical interfaces*. +- [ITU-T G.709] Recommendation ITU-T G.709/Y.1331 (2020), *Interfaces for the optical transport network (OTN)*. +- [ITU-T G.709.1] Recommendation ITU-T G.709.1 (2024), *Flexible OTN common elements*. +- [ITU-T G.709.2] Recommendation ITU-T G.709.2/Y.1331.2 (2018), *OTU4 long-reach interface*. +- [ITU-T G.709.3] Recommendation ITU-T G.709.3 (2024), *Flexible OTN B100G long-reach interfaces*. +- [ITU-T G.709.4] Recommendation ITU-T G.709.4/Y.1331.4 (2020), *OTU25 and OTU50 short-reach interfaces*. +- [ITU-T G.709.5] Recommendation ITU-T G.709.5 (2024), *Flexible OTN short-reach interfaces*. + +- [ITU-T G.709.6] Recommendation ITU-T G.709.6 (2024), *Flexible OTN B400G long-reach interfaces*. +- [ITU-T G.709.20] Recommendation ITU-T G.709.20 (2024), *Overview of fine grain OTN*. +- [ITU-T G.798] Recommendation ITU-T G.798 (2023), *Characteristics of optical transport network hierarchy equipment functional blocks*. +- [ITU-T G.800] Recommendation ITU-T G.800 (2016), *Unified functional architecture of transport networks*. +- [ITU-T G.805] Recommendation ITU-T G.805 (2000), *Generic functional architecture of transport networks*. +- [ITU-T G.807] Recommendation ITU-T G.807 (2020), *Generic functional architecture of the optical media network*. +- [ITU-T G.873.1] Recommendation ITU-T G.873.1 (2017), *Optical transport network: Linear protection*. +- [ITU-T G.873.2] Recommendation ITU-T G.873.2 (2015), *ODUk shared ring protection*. +- [ITU-T G.873.3] Recommendation ITU-T G.873.3 (2017), *Optical transport network – Shared mesh protection*. +- [ITU-T G.874] Recommendation ITU-T G.874 (2020), *Management aspects of optical transport network elements*. +- [ITU-T G.875] Recommendation ITU-T G.875 (2020), *Optical transport network: Protocol-neutral management information model for the network element view*. +- [ITU-T G.959.1] Recommendation ITU-T G.959.1 (2024), *Optical transport network physical layer interfaces*. +- [ITU-T G.7712] Recommendation ITU-T G.7712/Y.1703 (2019), *Architecture and specification of data communication network*. +- [ITU-T G.8023] Recommendation ITU-T G.8023 (2018), *Characteristics of equipment functional blocks supporting Ethernet physical layer and Flex Ethernet interfaces*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **access point**: [ITU-T G.805]. +- 3.1.2 **adaptation**: [ITU-T G.805]. +- 3.1.3 **adapted information**: [ITU-T G.805]. +- 3.1.4 **administrative domain**: [ITU-T G.805]. +- 3.1.5 **characteristic information**: [ITU-T G.805]. +- 3.1.6 **connection**: [ITU-T G.805]. +- 3.1.7 **connection supervision**: [ITU-T G.805]. +- 3.1.8 **fgODUflex(p)**: [ITU-T G.709]. +- 3.1.9 **forwarding point (FP)**: [ITU-T G.800]. +- 3.1.10 **layer network**: [ITU-T G.805]. + +- 3.1.11 **link**: [ITU-T G.805]. +- 3.1.12 **media channel**: [ITU-T G.807]. +- 3.1.13 **media channel assembly (MCA)**: [ITU-T G.807]. +- 3.1.14 **media channel group (MCG)**: [ITU-T G.807]. +- 3.1.15 **media subnetwork**: [ITU-T G.807]. +- 3.1.16 **media layer access point (M-AP)**: [ITU-T G.807]. +- 3.1.17 **media layer adapted information (M-AI)**: [ITU-T G.807]. +- 3.1.18 **network connection**: [ITU-T G.805]. +- 3.1.19 **network media channel (NMC)**: [ITU-T G.807]. +- 3.1.20 **ODUflex(fgTS,n)**: [ITU-T G.709]. +- 3.1.21 **ODUk(fgTS)**: [ITU-T G.709]. +- 3.1.22 **optical data unit (ODU)**: [ITU-T G.709]. +- 3.1.23 **optical payload unit (OPU)**: [ITU-T G.709]. +- 3.1.24 **optical transport network**: [ITU-T G.709]. +- 3.1.25 **optical transport unit (OTU)**: [ITU-T G.709]. +- 3.1.26 **optical tributary signal (OTSi)**: [ITU-T G.959.1]. +- 3.1.27 **optical tributary signal assembly (OTSiA)**: [ITU-T G.807]. +- 3.1.28 **optical tributary signal group (OTSiG)**: [ITU-T G.807]. +- 3.1.29 **optical tributary signal overhead (OTSiG-O)**: [ITU-T G.807]. +- 3.1.30 **OSC**: [ITU-T G.807]. +- 3.1.31 **subnetwork**: [ITU-T G.805]. +- 3.1.32 **topological component**: [ITU-T G.805]. +- 3.1.33 **trail**: [ITU-T G.805]. +- 3.1.34 **transitional link**: [ITU-T G.800]. +- 3.1.35 **transport entity (TE)**: [ITU-T G.800]. +- 3.1.36 **transport processing function**: [ITU-T G.805]. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|----------------------------| +| AI | Adapted Information | +| AP | Access Point | +| BIP | Bit-Interleaved Parity | +| CBR | Constant Bit Rate | +| CI | Characteristic Information | +| CP | Connection Point | + +| | | +|-----------|-----------------------------------------------| +| ECC | Embedded Communication Channel | +| ETCy | Ethernet Coding sublayer for physical layer y | +| FEC | Forward Error Correction | +| fgODUflex | Fine Grain Flexible Optical Data Unit | +| FlexE | Flex Ethernet | +| FlexO | Flexible Optical transport network | +| FP | Forwarding Point | +| MAC | Media Access Control | +| M-AI | Media layer Adapted Information | +| M-AP | Media layer Access Point | +| MCA | Media Channel Assembly | +| MCG | Media Channel Group | +| M/D | Modulator/Demodulator | +| MSI | Multiplex Structure Identifier | +| NMC | Network Media Channel | +| NMCG | Network Media Channel Group | +| OAM | Operations, Administration and Maintenance | +| OCh | Optical Channel | +| ODU | Optical Data Unit | +| OMS | Optical Multiplex Section | +| OMS-O | Optical Multiplex Section Overhead | +| OPU | Optical Payload Unit | +| OSME | Optical Signal Maintenance Entity | +| OTN | Optical Transport Network | +| OTS | Optical Transmission Section | +| OTS-O | Optical Transmission Section Overhead | +| OTSi | Optical Tributary Signal | +| OTSiA | Optical Tributary Signal Assembly | +| OTSiG | Optical Tributary Signal Group | +| OTSiG-O | Optical Tributary Signal Group Overhead | +| OTU | Optical Transport Unit | +| PKT | Packet | +| TCM | Tandem Connection Monitoring | +| TE | Transport Entity | +| TS | Tributary Slot | +| TTI | Trail Trace Identifier | + +# 5 Conventions + +## 5.1 Notational + +The forwarding point (FP), defined in [ITU-T G.800], is used in this Recommendation and is equivalent to the connection point (CP), defined in [ITU-T G.805] that is used in [ITU-T G.709] and [ITU-T G.798]. + +The term modulator/demodulator is used to describe a bidirectional function that consists of a pair of collocated modulator and demodulator functions. + +The term media layer access point, defined in [ITU-T G.807], is used in this Recommendation to identify the reference point between an adaptation function and a modulator/demodulator function. [ITU-T G.798] uses the term access point (AP) to identify this reference point. + +The suffix -O is used to identify the non-associated overhead that corresponds to a group of optical signals, e.g., optical tributary signal group overhead (OTSiG-O) or optical multiplex section overhead (OMS-O). + +The following conventions are used for optical data unit (ODU): + +- ODUk is used to indicate an ODU0, ODU1, ODU2, ODU2e, ODU3, ODU4, ODUflex, ODU25u, ODU25, ODU50u or ODU50; +- ODUj is used to indicate an ODUk where $k > j$ . This convention is used when two ODUk information structures are described (e.g., for ODUk multiplexing); +- ODUCn is used to indicate an ODUCn + - n is a positive integer; +- ODU is used to indicate either an ODUk or ODUCn. + +The following conventions are used for the optical transport unit (OTU): + +- OTUk is used to indicate an OTU1, OTU2, OTU3 or OTU4; +- OTUCn is used to indicate an OTUCn + - n is a positive integer; +- OTU is used to indicate an OTUk, OTU25u, OTU25, OTU50u, OTU50 or OTUCn + +## 5.2 Information structures and interfaces + +FlexO-x(e) is shorthand for FlexO-x or FlexO-xe, with the e suffix indicating optimization for Ethernet payloads. + +Similarly, FlexO-n(e) is shorthand for FlexO-n or FlexO-ne. + +## 5.3 Diagrammatic + +This Recommendation uses diagrammatic conventions described in [ITU-T G.800], [ITU-T G.805] and [ITU-T G.807]. + +# 6 Functional architecture of the OTN + +The OTN provides transport, aggregation, routing, supervision and survivability for digital clients that are processed in the digital domain and carried across optical media. These OTN functions are described from a network level viewpoint using the generic principles specified in [ITU-T G.800] and [ITU-T G.805] for the digital layers, and [ITU-T G.807] for the media network. Specific aspects concerning the OTN layered structure, characteristic information (CI), client/server layer associations, network topology, layer network functionality and media are provided in this + +Recommendation. A number of other ITU-T Recommendations provide detailed information on the implementation of the OTN, e.g: + +- [ITU-T G.709], [ITU-T G.709.1], [ITU-T G.709.2], [ITU-T G.709.3], [ITU-T G.709.4], [ITU-T G.709.5] and [ITU-T G.709.6] provide the rates and formats used in the OTN; +- [ITU-T G.798] specifies equipment functional blocks; +- [ITU-T G.873.1], [ITU-T G.873.2] and [ITU-T G.873.3] describe linear, ring and shared mesh protection, respectively; +- [ITU-T G.874] and [ITU-T G.875] specify the management interface; +- [ITU-T G.695], [ITU-T G.698.1], [ITU-T G.698.2] and [ITU-T G.959.1] specify the physical interfaces; +- [ITU-T G.694.1] and [ITU-T G.694.2] specify the frequency grid for dense wavelength division multiplexing interfaces and the wavelength grid for coarse wavelength division multiplexing interfaces, respectively. + +In accordance with [ITU-T G.805] and [ITU-T G.800], the digital layers of the OTN are decomposed into independent transport layer networks, where each layer network can be separately partitioned in a way that reflects the internal structure of that layer network. The OTN consists of the digital layers, optical signals and the media network, all of which may be managed as a single multi-layer entity. The structure of the OTN is provided in Figure 6-1. + +![](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +| | | | | | | +|---------------------------------------------------------------------------------------------------|--------------------------|------------------------------------------------------------|---------------------------|-------------------------|--| +| Ethernet clients | | Digital clients of the OTN
(Including Ethernet clients) | | | | +| Ethernet-optimized
FlexO | fgODUflex | | OTN digital layer | | | +| | ODU
(ODUj/ODUk/ODUCn) | | | | | +| | OTUCn | OTU/OTUCn | | | | +| | FlexO | | | | | +| OTSiA | | | OTN optical media signals | OTN optical media layer | | +| Media constructs, OMS/OTS optical signal maintenance entities non-associated overhead information | | | OTN optical media network | | | + +G.872(24) + +**Figure 6-1 – Overview of the OTN** + +The digital layers of the OTN (ODU, OTU) provide the capability to multiplex and maintain digital clients. Ethernet clients may be mapped directly to FlexO. An OTU is supported by one optical tributary signal assembly (OTSiA) and the OTSiA supports one OTU. + +NOTE – Mapping between the terminologies for optical channel (OCh) and optical tributary signal (OTSi) is provided in Appendix I. + +The OTSiA is a management/control abstraction that represents the optical tributary signal group (OTSiG) management/control abstraction and the non-associated OTSiG-O; see [ITU-T G.807]. The OTSiG represents one or more optical tributary signals (OTSis). + +Below the OTSi is the optical media network, which contains the media constructs that provide the ability to configure the media channels that guide the OTSi through the media network, see [ITU-T G.807]. + +The OTSiA that supports the OTU, together with the associated media channels, may be managed as a part of an OTN network. While the optical media layer (OTSiA and media network) described in [ITU-T G.807] may support other clients, such clients are not a part of the OTN. In some cases, the + +OTSiA may not support certain monitoring functions (e.g., path trace). In this case, OTU monitoring functions may be used to provide the full operations, administration and maintenance (OAM), and fault management capabilities of the OTN. + +The configuration of the media channels to support an OTSiA and monitoring of the OTSiA is described in [ITU-T G.807]. + +The OTN digital layers are described in clause 7. The generic aspects of the media layer (OTSiA and media network) are described in [ITU-T G.807], and the OTN specific aspects of the media layer are described in clause 8. + +# 7 OTN digital layers + +The digital layers of the OTN are divided into the OTU layer and a hierarchy of one or more ODU layers. A fine grain flexible optical data unit (fgODUflex) layer that is a client to the ODUk layer is described in Annex A. An OTU layer supports one ODU layer network as the client, and provides monitoring capability for the OTSiG. + +NOTE 1 – The OTSiG is described in [ITU-T G.807]. Mapping between terminologies for OTSi and OCh is provided in Appendix I of [ITU-T G.807]. + +The relationship between the ODUk and OTUk is shown in Figure 7-1. + +![Figure 7-1: Client/server association of the digital OTN layers without ODU multiplexing. The diagram shows two parallel vertical stacks of layers. The top stack represents the ODU layer network, starting with 'ODUk/Client_A Source' at the top, followed by 'ODUk AP', 'ODUk_TT Source', 'ODUk FP', and 'ODUk/Client_A Sink' at the bottom. Horizontal dashed lines connect the APs (ODUk trail) and the FPs (ODUk network connection). The bottom stack represents the OTU layer network, starting with 'OTUk/ODU_A Source' at the top, followed by 'OTUk AP', 'OTUk_TT Source', 'OTUk FP', and 'OTUk/ODU_A Sink' at the bottom. Horizontal dashed lines connect the APs (OTUk trail) and the FPs (OTUk network connection). Vertical double-headed arrows on the left indicate the boundaries of the 'ODU layer network' and the 'OTU layer network'. The diagram is labeled G.872(17)_F7-1 at the bottom right.](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +Figure 7-1: Client/server association of the digital OTN layers without ODU multiplexing. The diagram shows two parallel vertical stacks of layers. The top stack represents the ODU layer network, starting with 'ODUk/Client\_A Source' at the top, followed by 'ODUk AP', 'ODUk\_TT Source', 'ODUk FP', and 'ODUk/Client\_A Sink' at the bottom. Horizontal dashed lines connect the APs (ODUk trail) and the FPs (ODUk network connection). The bottom stack represents the OTU layer network, starting with 'OTUk/ODU\_A Source' at the top, followed by 'OTUk AP', 'OTUk\_TT Source', 'OTUk FP', and 'OTUk/ODU\_A Sink' at the bottom. Horizontal dashed lines connect the APs (OTUk trail) and the FPs (OTUk network connection). Vertical double-headed arrows on the left indicate the boundaries of the 'ODU layer network' and the 'OTU layer network'. The diagram is labeled G.872(17)\_F7-1 at the bottom right. + +**Figure 7-1 – Client/server association of the digital OTN layers without ODU multiplexing** + +NOTE 2 – As described in clause 5.1 the FP is used in this Recommendation and is equivalent to the CP that is used in [ITU-T G.709] and [ITU-T G.798]. + +An ODUk may support a single (non-OTN) client as shown in Figure 7-1. An ODU (ODUk or ODUCn as described in clause 5.1) may support a heterogeneous assembly of lower rate ODUk clients using ODUk multiplexing as shown by the adaptation between the ODU and ODUj layer networks in Figure 7-2. ODUk multiplexing is described in clause 7.1.1. + +![Diagram illustrating the client/server association of the digital OTN layers with ODU multiplexing. The diagram shows three layers of network associations: ODUj, ODU, and OTU. Each layer consists of a source and a sink connected by a trail and a network connection. The ODUj layer is at the top, followed by the ODU layer, and then the OTU layer at the bottom. Each layer has its own set of components: AP (Adapter/Processor), TT (Termination Point), and FP (Frame Processor). The ODUj layer is associated with the ODUj trail and ODUj network connection. The ODU layer is associated with the ODU trail and ODU network connection. The OTU layer is associated with the OTU trail and OTU network connection. The diagram also includes vertical arrows indicating the ODUj, ODU, and OTU layer networks. A reference code G.872(19)_F7-2 is shown at the bottom right.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +G.872(19)\_F7-2 + +Diagram illustrating the client/server association of the digital OTN layers with ODU multiplexing. The diagram shows three layers of network associations: ODUj, ODU, and OTU. Each layer consists of a source and a sink connected by a trail and a network connection. The ODUj layer is at the top, followed by the ODU layer, and then the OTU layer at the bottom. Each layer has its own set of components: AP (Adapter/Processor), TT (Termination Point), and FP (Frame Processor). The ODUj layer is associated with the ODUj trail and ODUj network connection. The ODU layer is associated with the ODU trail and ODU network connection. The OTU layer is associated with the OTU trail and OTU network connection. The diagram also includes vertical arrows indicating the ODUj, ODU, and OTU layer networks. A reference code G.872(19)\_F7-2 is shown at the bottom right. + +**Figure 7-2 – Client/server association of the digital OTN layers with ODU multiplexing** + +The currently supported set of clients and servers is provided in clause 7.1.2. + +## 7.1 Optical data unit layer network + +The ODU layer network provides end-to-end transport of digital client information across the OTN. The description of the supported client layer networks lies outside the scope of this Recommendation. A description of the use of the OTN to carry Flex Ethernet (FlexE) is provided in Appendix II. + +The CI of an ODU layer network is described in terms of the frame structure specified in [ITU-T G.709], and is composed of: + +- the optical payload unit (OPU), which is the payload area of the ODU that is used to transport the digital client(s); and +- the ODU and OPU overhead area for the transport of the associated overhead. + +NOTE 1 – An ODUCn consists of n interleaved ODUC frame structures that support a single OPUCn payload area and n instances of the ODUC overhead and OPUC overhead. + +Details of the format are provided in [ITU-T G.709]. + +The topological components of the ODU layer network are ODUk subnetworks and ODU links. The links are supported by either an OTU trail or a server ODU trail. As described in clause 7.1.1, an ODU server supports a heterogeneous assembly of ODUks. The ODUk subnetwork may provide connections for any ODUk. The tributary slot (TS) size supported by a server ODU and the bit rate of the client ODUk are modelled as parameters. This allows the ODU layer network to be viewed as a single layer network. When attempting to find a route for a particular ODUk, these parameters are used to identify the subset of the topological components in the ODU layer network that may be used to support that ODUk, this is illustrated in Appendix III. + +NOTE 2 – The usage restriction may be based on the capability of the resource (e.g., a link with a 2.5 Gbit/s TS cannot support an ODU0 connection) or the restriction may be based on management policy (e.g., only ODU4 connections are allowed to use an ODUCn link). + +NOTE 3 – This approach allows the topology of an ODUk specific layer network to be generated from that of the ODU layer network. + +These parameters also allow the number of TSs that an ODU will occupy on an ODU link connection (i.e., within a server ODU) to be determined. Each client ODU is mapped into an integer number of server ODU TS. + +NOTE 4 – This may lead to inefficient use of bandwidth when the bit rate of the client ODU is less than that of a TS in the server ODU. (See Tables 7-2 and 7-4.) + +To provide end-to-end networking, the following capabilities are included in the ODU layer network: + +- ODUk connection rearrangement for flexible network routing; +- ODU overhead processes to verify the integrity of the client adapted information (AI); +- ODU OAM functions, including network survivability. + +The ODU layer network contains the following topological components, transport processing functions and transport entities (see Figure 7-3 for ODUk and Figure 7-4 for ODUCn). The interlayer adaptation functions are described in clause 7.3. + +Topological components: + +- ODUk subnetwork; +- access group; +- ODU link. + +Transport processing functions: + +- ODU trail termination source; +- ODU trail termination sink. + +Transport entities: + +- ODU trail; +- ODU network connection; +- ODU link connection; +- ODUk subnetwork connection. + +![Figure 7-3: ODuk layer network example. This diagram illustrates the network architecture for ODuk. At the top, an 'ODU AP' is connected to an 'ODUk TT Source' (represented by a triangle) on the left and an 'ODUk TT Sink' (represented by a triangle) on the right. A dashed line labeled 'ODU trail' connects the two ODU APs. Below the ODUk TT Source, there is an 'ODUk FP' (Framing Point) connected to an 'ODUk subnetwork connection' (represented by an oval). This subnetwork connection is linked to an 'ODUk link connection' (represented by a rectangle with two circles), which is then connected to another 'ODUk subnetwork connection'. This second subnetwork connection is linked to another 'ODUk link connection', which is finally connected to a third 'ODUk subnetwork connection'. This third subnetwork connection is linked to an 'ODUk FP', which is connected to an 'ODU AP' on the right. Below the subnetwork connections, there are labels 'ODUk subnetwork', 'ODUk FP', 'ODUk subnetwork', 'ODUk FP', and 'ODUk subnetwork' with blue arrows pointing up to the corresponding subnetwork connections. The diagram is labeled 'G.872(17)_F7-3' in the bottom right corner.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Figure 7-3: ODuk layer network example. This diagram illustrates the network architecture for ODuk. At the top, an 'ODU AP' is connected to an 'ODUk TT Source' (represented by a triangle) on the left and an 'ODUk TT Sink' (represented by a triangle) on the right. A dashed line labeled 'ODU trail' connects the two ODU APs. Below the ODUk TT Source, there is an 'ODUk FP' (Framing Point) connected to an 'ODUk subnetwork connection' (represented by an oval). This subnetwork connection is linked to an 'ODUk link connection' (represented by a rectangle with two circles), which is then connected to another 'ODUk subnetwork connection'. This second subnetwork connection is linked to another 'ODUk link connection', which is finally connected to a third 'ODUk subnetwork connection'. This third subnetwork connection is linked to an 'ODUk FP', which is connected to an 'ODU AP' on the right. Below the subnetwork connections, there are labels 'ODUk subnetwork', 'ODUk FP', 'ODUk subnetwork', 'ODUk FP', and 'ODUk subnetwork' with blue arrows pointing up to the corresponding subnetwork connections. The diagram is labeled 'G.872(17)\_F7-3' in the bottom right corner. + +**Figure 7-3 – ODuk layer network example** + +![Figure 7-4: ODUCn layer network example. This diagram illustrates the network architecture for ODUCn. At the top, an 'ODU AP' is connected to an 'ODUCn TT Source' (represented by a triangle) on the left and an 'ODUCn TT Sink' (represented by a triangle) on the right. A dashed line labeled 'ODU trail' connects the two ODU APs. Below the ODUCn TT Source, there is an 'ODUCn FP' (Framing Point) connected to an 'ODUCn link connection' (represented by a rectangle with two circles). This link connection is connected to another 'ODUCn link connection', which is then connected to a third 'ODUCn link connection'. This third link connection is connected to an 'ODUCn FP', which is connected to an 'ODU AP' on the right. Below the link connections, there is a label 'ODUCn FP' with a blue arrow pointing up to the middle link connection. The diagram is labeled 'G.872(17)_F7-4' in the bottom right corner.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +Figure 7-4: ODUCn layer network example. This diagram illustrates the network architecture for ODUCn. At the top, an 'ODU AP' is connected to an 'ODUCn TT Source' (represented by a triangle) on the left and an 'ODUCn TT Sink' (represented by a triangle) on the right. A dashed line labeled 'ODU trail' connects the two ODU APs. Below the ODUCn TT Source, there is an 'ODUCn FP' (Framing Point) connected to an 'ODUCn link connection' (represented by a rectangle with two circles). This link connection is connected to another 'ODUCn link connection', which is then connected to a third 'ODUCn link connection'. This third link connection is connected to an 'ODUCn FP', which is connected to an 'ODU AP' on the right. Below the link connections, there is a label 'ODUCn FP' with a blue arrow pointing up to the middle link connection. The diagram is labeled 'G.872(17)\_F7-4' in the bottom right corner. + +**Figure 7-4 – ODUCn layer network example** + +The ODUCn FP represents the location of ODUCn regeneration and allows ODUCn tandem connection monitoring (TCM). + +NOTE 5 – As described in clause 5.1, the FP is used in this Recommendation and is equivalent to the CP that is used in [ITU-T G.709] and [ITU-T G.798]. + +### 7.1.1 ODuk multiplexing + +In order to allow the transport of several lower bit rate ODuk clients over a higher bit rate ODU server, time division multiplexing of ODUs is specified. The ODU clients and servers are described in Table 7-2. + +The TS of the ODU server may be allocated to any combination of ODuk clients up to the capacity of the server ODU. + +The heterogeneous multiplexing of ODUs supports various network architectures, including those that are optimized to minimize stranded capacity to minimize the number of managed entities, support carrier's carrier scenarios or enable ODU0/ODUflex traffic to transit a region of the network that does not support these capabilities. Some examples of carrier (multi-domain) applications of a carrier are given in Appendix IV. + +### 7.1.2 ODU clients and servers + +ODUs, OTUs, and TS are specified in [ITU-T G.709]. + +The set of ODU servers and their non-OTN clients is provided in Table 7-1. + +**Table 7-1 – ODU servers and their non-OTN clients** + +| ODU server | non-OTN clients | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODU0 | 1.25 Gbit/s bit rate area | +| ODU1 | 2.5 Gbit/s bit rate area | +| ODU2 | 10 Gbit/s bit rate area | +| ODU2e | 10.3125 Gbit/s bit rate area | +| ODU25u | none | +| ODU25 | none | +| ODU3 | 40 Gbit/s bit rate area | +| ODU50u | none | +| ODU50 | none | +| ODU4 | 100 Gbit/s bit rate area | +| ODUflex | Constant bit rate (CBR) clients greater than 2.5 Gbit/s, or GFP-F mapped packet (PKT) clients greater than 1.25 Gbit/s, or IMP mapped 64B/66B encoded clients | +| ODUCn | None | + +NOTE – ODU25u, ODU25, ODU50u, ODU50 and ODUCn support a limited set of non-OTN clients (e.g., NULL, PRBS and proprietary use clients) as defined in [ITU-T G.709]. + +The set of ODU servers and their ODU clients is provided in Table 7-2. + +**Table 7-2 – ODU servers and their ODU clients** + +| ODU server | ODU clients | +|-------------------|----------------------------------------------| +| ODU1 | ODU0 | +| ODU2 | ODU0, ODU1, ODUflex | +| ODU25u | ODU0, ODU1, ODU2, ODU2e, ODUflex | +| ODU25 | ODU0, ODU1, ODU2, ODU2e, ODUflex | +| ODU3 | ODU0, ODU1, ODU2, ODU2e, ODUflex | +| ODU50u | ODU0, ODU1, ODU2, ODU2e, ODU3, ODUflex | +| ODU50 | ODU0, ODU1, ODU2, ODU2e, ODU3, ODUflex | +| ODU4 | ODU0, ODU1, ODU2, ODU2e, ODU3, ODUflex | +| ODUCn | ODU0, ODU1, ODU2, ODU2e, ODU3, ODU4, ODUflex | + +NOTE 1 – The ODU2 and ODU3 servers only support ODU0 and ODUflex clients if the ODU2 or ODU3 server has 1.25 Gbit/s TS (see Table 7-4). +NOTE 2 –ODU2e and ODUflex cannot be used as a server. +NOTE 3 – An ODU server does not support ODU25u, ODU25, ODU50u, ODU50 or ODUCn clients. + +The set of OTU servers and their ODU clients is provided in Table 7-3. + +**Table 7-3 – OTU servers and their ODU clients** + +| OTU server | ODU client | +|------------|------------| +| OTU0 | ODU0 | +| OTU1 | ODU1 | +| OTU2 | ODU2 | +| OTU25u | ODU25u | +| OTU25 | ODU25 | +| OTU3 | ODU3 | +| OTU50u | ODU50u | +| OTU50 | ODU50 | +| OTU4 | ODU4 | +| OTUCn | ODUCn | +| OTUCn-M | ODUCn | + +NOTE 1 – The OTUCn-M is described in clause 7.2. +NOTE 2 – OTU servers have not been defined for ODU2e or ODUflex. + +The total number of TS available in a server ODU (when carrying one or more ODUk client(s)), is provided in Table 7-4. + +**Table 7-4 – Number of tributary slots for each ODU** + +| ODU server | Nominal TS capacity | | | +|------------|---------------------|----------------|----------------| +| | 1.25 Gbit/s | 2.5 Gbit/s | 5 Gbit/s | +| ODU1 | 2 | not applicable | not applicable | +| ODU2 | 8 | 4 | not applicable | +| ODU25u | 20 | not applicable | not applicable | +| ODU25 | 20 | not applicable | not applicable | +| ODU3 | 32 | 16 | not applicable | +| ODU50u | 40 | not applicable | not applicable | +| ODU50 | 40 | not applicable | not applicable | +| ODU4 | 80 | not applicable | not applicable | +| ODUCn | not applicable | not applicable | $20 \times n$ | + +NOTE 1 – An ODUCn supports a maximum of $10 \times n$ ODUk clients. +NOTE 2 – ODU0, ODU2e or ODUflex do not support ODU clients and therefore do not support TSs. + +### 7.1.3 ODU trail termination + +The following generic processes may be assigned to the ODU trail termination: + +- validation of connectivity integrity; +- assessment of transmission quality; +- transmission defect detection and indication. + +The requirements for these processes are outlined in clause 10. + +There are three types of ODU trail termination: + +- ODU bidirectional trail termination: consists of a pair of collocated ODU trail termination source and sink functions; +- ODU trail termination source: accepts (AI from a client layer network at its input, inserts the ODU trail termination overhead as a separate and distinct logical data stream and presents the CI of the ODU layer network at its output; +- ODU trail termination sink: accepts the CI of the ODU layer network at its input, extracts the separate and distinct logical data stream containing the ODU trail termination overhead and presents the AI at its output. + +### 7.1.4 ODU transport entities + +Network connections, subnetwork connections, link connections, tandem connections and trails are as described in [ITU-T G.800]. + +#### 7.1.4.1 ODU tandem connections + +The ODU overhead includes information to support monitoring the end-to-end ODU trail and up to six levels of tandem connections. The ODU path OH is terminated where the ODU is assembled and disassembled. The tandem connection overhead is added and terminated at the end of each tandem connection. + +NOTE – In normal operation, the monitored tandem connections may be nested, cascaded or both. For test purposes the monitored tandem connections may overlap. Overlapped monitored connections must be operated in a non-intrusive mode. + +### 7.1.5 ODU topological components + +Layer network, subnetworks, links (including transitional links) and access groups are as described in [ITU-T G.800]. + +The ODUk subnetwork provides flexibility within the ODUk layer network. ODUk CI is routed between input FPs and output FPs. + +The ODU layer does not provide flexible connectivity for ODUCn; as such there is no ODUCn subnetwork. + +## 7.2 Optical transport unit (OTU) layer network + +The OTU layer network provides for the transport of ODU client signals through an OTU trail. + +The CI of an OTU layer network is composed of: + +- the OTU payload area that carries a single ODU as a client; +- the OTU overhead area. + +NOTE 1 – An OTUCn carries n instances of the OTUC overhead. + +An OTUCn with a bit rate that is not an integer multiple of 100 Gbit/s is described as an OTUCn-M that carries n instances of OTUC overhead, ODUC overhead and OPUC overhead, together with M 5 Gbit/s OPUCn TS. An ODUCn-M and OPUCn-M are not specified. When an OTUCn-M is used to carry an ODUCn (20n–M), TSs are marked as unavailable in the OPUCn multiplex structure identifier (MSI), to limit the bandwidth available to that supported by the OTUCn-M. + +Details of the format are provided in [ITU-T G.709]. + +The capabilities of this layer network include: + +- OTU overhead processes to confirm the integrity of the client AI and conditioning for its transport over an OTSiG; +- OTU OAM functions. + +NOTE 2 – Flexible connectivity of an OTU may be provided by the media network described in clause 8. + +The OTU layer network contains the following transport processing functions and transport entities (see Figure 7-5 for the OTU and Figure 7-6 for the OTUCn). The interlayer adaptation functions are described in clause 7.3. + +Transport processing functions: + +- OTU trail termination source; +- OTU trail termination sink. + +Transport entities: + +- OTU trail; +- OTU network connection; +- OTUCn link connection. + +![Figure 7-5 – OTU layer network example. This diagram shows two OTU nodes connected by two parallel dashed lines. The top dashed line is labeled 'OTU trail' and connects two 'OTU AP' (Adaptation Point) entities, each represented by a circle with two small squares. The bottom dashed line is labeled 'OTU network connection' and connects two 'OTU FP' (Framing Point) entities, also represented by a circle with two small squares. Between the AP and FP at each node is a triangle labeled 'OTU TT Source' on the left and 'OTU TT Sink' on the right. The diagram is labeled 'G.872(17)_F7-5' at the bottom right.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +Figure 7-5 – OTU layer network example. This diagram shows two OTU nodes connected by two parallel dashed lines. The top dashed line is labeled 'OTU trail' and connects two 'OTU AP' (Adaptation Point) entities, each represented by a circle with two small squares. The bottom dashed line is labeled 'OTU network connection' and connects two 'OTU FP' (Framing Point) entities, also represented by a circle with two small squares. Between the AP and FP at each node is a triangle labeled 'OTU TT Source' on the left and 'OTU TT Sink' on the right. The diagram is labeled 'G.872(17)\_F7-5' at the bottom right. + +Figure 7-5 – OTU layer network example + +![Figure 7-6 – OTUCn layer network example. This diagram shows two OTUCn nodes connected by three parallel dashed lines. The top dashed line is labeled 'OTUCn trail' and connects two 'OTUCn AP' entities. The middle dashed line is labeled 'OTUCn network connection' and connects two 'OTUCn FP' entities. The bottom dashed line is labeled 'OTUCn link connection' and connects two 'OTUCn link connection' entities, each represented by a circle with two small squares. Between the AP and FP at each node is a triangle labeled 'OTUCn TT Source' on the left and 'OTUCn TT Sink' on the right. A blue double-headed arrow points from the label 'OTUCn FP' to the two 'OTUCn link connection' entities. The diagram is labeled 'G.872(17)_F7-6' at the bottom right.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +Figure 7-6 – OTUCn layer network example. This diagram shows two OTUCn nodes connected by three parallel dashed lines. The top dashed line is labeled 'OTUCn trail' and connects two 'OTUCn AP' entities. The middle dashed line is labeled 'OTUCn network connection' and connects two 'OTUCn FP' entities. The bottom dashed line is labeled 'OTUCn link connection' and connects two 'OTUCn link connection' entities, each represented by a circle with two small squares. Between the AP and FP at each node is a triangle labeled 'OTUCn TT Source' on the left and 'OTUCn TT Sink' on the right. A blue double-headed arrow points from the label 'OTUCn FP' to the two 'OTUCn link connection' entities. The diagram is labeled 'G.872(17)\_F7-6' at the bottom right. + +Figure 7-6 – OTUCn layer network example + +Figure 7-6 shows the case where regeneration is performed below the OTUCn layer, in this case ODUCn TCM is not supported. + +### 7.2.1 OTU trail termination + +The following generic processes are assigned to the OTU trail termination: + +- validation of connectivity integrity; +- assessment of transmission quality; + +- transmission defect detection and indication. + +The capabilities of these processes are outlined in clause 10. + +There are three types of OTU trail termination: + +- OTU bidirectional trail termination: consists of a pair of collocated OTU trail termination source and sink functions; +- OTU trail termination source: accepts AI from an ODU network at its input, inserts the OTU trail termination overhead as a separate and distinct logical data stream and presents the CI of the OTU layer network at its output; +- OTU trail termination sink: accepts the CI of the OTU layer network at its input, extracts the separate and distinct logical data stream containing the OTU trail termination overhead and presents the AI at its output. + +### **7.2.2 OTU transport entities** + +Network connections, link connections and trails are as described in [ITU-T G.800]. + +### **7.2.3 OTU topological components** + +Layer networks, links and access groups are as described in [ITU-T G.800]. + +## **7.3 Client/server associations** + +A principal feature of the OTN is the possibility of supporting a wide variety of circuit and PKT client layer networks. The current set of supported clients is provided in [ITU-T G.709]. + +The structure of the OTN digital layer networks and the adaptation functions are shown in Figures 7-1 and 7-2. For the purposes of description, the interlayer adaptation is named using the server/client relationship. A full description of the adaptation functions is provided in [ITU-T G.798]. + +### **7.3.1 ODU/client adaptation** + +The ODU/client adaptation is considered to consist of two types of processes: client-specific processes and server-specific processes. The description of the client-specific processes lies outside the scope of this Recommendation. The ODU servers are specified in Table 7-1. + +The bidirectional ODU/client adaptation function is performed by a collocated pair of source and sink ODU/client adaptation functions. + +The ODU/client adaptation source performs the following processes between its input and output: + +- all the processing required to adapt the client signal to the ODU payload area – the processes are dependent upon the particular client signal; +- generation and termination of management/maintenance signals as described in clause 10. + +The ODU/client adaptation sink performs the following processes between its input and output: + +- recovery of the client signal from the ODU payload area – the processes are dependent upon the particular client/server relationship; +- generation and termination of management/maintenance signals as described in clause 10. + +A detailed description is provided in [ITU-T G.798]. + +### **7.3.2 ODU/ODU adaptation** + +The bidirectional ODU/ODU adaptation function is performed by a collocated pair of source and sink ODU/ODU adaptation functions. The ODU/ODU adaptations are specified in Table 7-2. + +The ODU/ODU adaptation source performs the following processes between its input and output: + +- multiplexing lower rate ODUk clients to form a higher bit rate ODU server; +- generation and termination of management/maintenance signals as described in clause 10. + +The ODU/ODU adaptation sink performs the following processes between its input and output: + +- demultiplexing the lower rate ODUk clients from the higher rate ODU server; +- generation and termination of management/maintenance signals as described in clause 10. + +A detailed description is provided in [ITU-T G.798]. + +### 7.3.3 OTU/ODU adaptation + +The bidirectional OTU/ODU adaptation function is performed by a collocated pair of source and sink OTU/ODU adaptation functions. The OTU servers are specified in Table 7-3. + +The OTU/ODU adaptation source performs the following processes between its input and output: + +- mapping the ODU into the OTU payload area – the processes are dependent upon the particular implementation of the client/server relationship. + +The OTU/ODU adaptation sink performs the following processes between its input and output: + +- recovery of the ODU signal from the OTU payload area – the processes are dependent upon the particular implementation of the client/server relationship. + +A detailed description is provided in [ITU-T G.798]. + +## 7.4 Flexible OTN interfaces + +Naming conventions for FlexO defined in [ITU-T G.709.1] are used in this clause. + +The frame format for the flexible optical transport network (FlexO) interface, as specified in [ITU-T G.709.1], and used in [ITU-T G.709.3], [ITU-T G.709.5] and [ITU-T G.709.6], may be used to implement the media layer adapted information (M-AI)/OTUCn adaptation function as shown in Figure 7-7. The FlexO frame format supports multiplexing of one or more OTUCn over a group of FlexO instances that is transported by one FlexO-x--m interface group, where x is a positive integer equal to the interface bit rate divided by 100G and m is the number of interfaces. The FlexO-x--m interface group bonds (i.e., combines) m standard-rate interfaces to provide a contiguous capacity of $m \times x \times 100\text{G}$ . + +![Functional block diagram showing the mapping of OTUCn to a FlexO group. At the top, OTUCn1 and OTUCnp signals enter a 'FlexO-n/OTUCn' block. This block fans out to multiple 'FlexO #1', 'FlexO #x', 'FlexO #(n-x+1)', and 'FlexO #n' blocks, collectively labeled 'FlexO-n, n<=m*x'. Below these, signals pass through 'FlexO-x/FlexO' adaptation blocks into 'FlexO-x' blocks, collectively labeled 'm FlexO-x'. These then go through 'M-AI/FlexO-x' and 'M-AI' blocks to 'M/D' (modulator/demodulator) blocks. The M/D blocks interface with an 'OTSiG' (Optical Transport Signal Group). The diagram is labeled G.872(24).](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +``` + +graph TD + OTUCn1[OTUCn1] --> FlexOnOTUCn[FlexO-n/OTUCn] + OTUCnp[OTUCnp] --> FlexOnOTUCn + FlexOnOTUCn --> F1[FlexO #1] + FlexOnOTUCn --> Fx[FlexO #x] + FlexOnOTUCn --> Fnx1[FlexO #n-x+1] + FlexOnOTUCn --> Fn[FlexO #n] + subgraph FlexO_Group [FlexO-n, n ≤ m*x] + F1 + Fx + Fnx1 + Fn + end + F1 & Fx --> FxF1[FlexO-x/FlexO] + Fnx1 & Fn --> FxF2[FlexO-x/FlexO] + FxF1 --> Fx1[FlexO-x] + FxF2 --> Fx2[FlexO-x] + subgraph m_FlexO_x [m FlexO-x] + Fx1 + Fx2 + end + Fx1 --> MAIFx1[M-AI/FlexO-x] + Fx2 --> MAIFx2[M-AI/FlexO-x] + MAIFx1 --> MAI1[M-AI] + MAIFx2 --> MAI2[M-AI] + MAI1 --> MD1[M/D] + MAI2 --> MD2[M/D] + MD1 & MD2 --- OTSiG((OTSiG)) + style FlexO_Group fill:none,stroke-dasharray: 5 5 + style m_FlexO_x fill:none,stroke-dasharray: 5 5 + +``` + +M/D: modulator/demodulator + +Functional block diagram showing the mapping of OTUCn to a FlexO group. At the top, OTUCn1 and OTUCnp signals enter a 'FlexO-n/OTUCn' block. This block fans out to multiple 'FlexO #1', 'FlexO #x', 'FlexO #(n-x+1)', and 'FlexO #n' blocks, collectively labeled 'FlexO-n, n<=m\*x'. Below these, signals pass through 'FlexO-x/FlexO' adaptation blocks into 'FlexO-x' blocks, collectively labeled 'm FlexO-x'. These then go through 'M-AI/FlexO-x' and 'M-AI' blocks to 'M/D' (modulator/demodulator) blocks. The M/D blocks interface with an 'OTSiG' (Optical Transport Signal Group). The diagram is labeled G.872(24). + +**Figure 7-7 – Mapping an OTUCn to FlexO group where each FlexO-x- interface is carried by one OTSi** + +Figure 7-7 shows the case where each FlexO-x- interface is carried by a single OTSi, e.g., by using the OTSi class DP-DQPSK 100G as specified in [ITU-T G.698.2]. Alternatively, each FlexO-x- interface may be inversely multiplexed over y OTSi, e.g., the four channel NRZ OTL4.4 short-haul interface specified in [ITU-T G.695] may be used. In this case, the FlexO-x--m interface group is carried by $m \times y$ OTSi. + +To align the aggregate rate of the OTUCn clients to the payload capacity of the FlexO-x--m interface group, each FlexO instance (transported by a FlexO-x--m interface group) may carry one OTUC from the OTUCn clients or it may be unequipped. Details of the processes used to implement FlexO interfaces are provided in clause 15 of [ITU-T G.798]. + +The use of the FlexO-x- frame format in conjunction with one of the interfaces specified in, for example, [ITU-T G.695] or [ITU-T G.698.2], provides a fully standardized optical interface. + +### 7.4.1 Ethernet optimized OTN + +Ethernet clients with rates in multiples of 100GE may be adapted directly to FlexO. Figure 7-8 shows Ethernet clients mapped to Ethernet optimized FlexO-xe interfaces. Ethernet coding sublayer for physical layer y (ETCy) is specified in [ITU-T G.802.3] and for the adaptation in Figure 7-8, y takes the values 100GR, 200GR, 400GR, or 800GR. All OTSi carrying FlexO-xe are in the same OTSiG. + +![Diagram illustrating the mapping of Ethernet to Ethernet optimized FlexO interfaces. The diagram shows a hierarchy of interfaces: at the top, two ETcy inputs connect to a FlexO-ne/ETcy interface; this interface has multiple outputs (labeled 1, x, ..., (n-x+1), ..., n) that connect to individual FlexO #1, FlexO #x, FlexO #(n-x+1), and FlexO #n units, which are grouped as FlexO-ne, n ≤ m*x; these units connect to FlexO-xe/FlexO interfaces, which are further connected to FlexO-xe units, grouped as m FlexO-xe; these FlexO-xe units connect to M-AI/FlexO-xe interfaces, which are connected to M-AI units, which in turn connect to M/D (Media Dependent) units; finally, the M/D units connect to an OTSiG optical signal. The diagram is labeled G.872(24).](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +Diagram illustrating the mapping of Ethernet to Ethernet optimized FlexO interfaces. The diagram shows a hierarchy of interfaces: at the top, two ETcy inputs connect to a FlexO-ne/ETcy interface; this interface has multiple outputs (labeled 1, x, ..., (n-x+1), ..., n) that connect to individual FlexO #1, FlexO #x, FlexO #(n-x+1), and FlexO #n units, which are grouped as FlexO-ne, n ≤ m\*x; these units connect to FlexO-xe/FlexO interfaces, which are further connected to FlexO-xe units, grouped as m FlexO-xe; these FlexO-xe units connect to M-AI/FlexO-xe interfaces, which are connected to M-AI units, which in turn connect to M/D (Media Dependent) units; finally, the M/D units connect to an OTSiG optical signal. The diagram is labeled G.872(24). + +**Figure 7-8 – Mapping Ethernet to Ethernet optimized FlexO interfaces** + +The use of the FlexO-x(e)- frame format in conjunction with one of the interfaces specified in, for example, [ITU-T G.695] or [ITU-T G.698.2], provides a fully standardized optical interface. + +### 7.4.2 FlexO regeneration + +As a section layer, FlexO can be regenerated when carrying either Ethernet or OTUCn clients. The regeneration is done per FlexO-x interface. When a regenerator is used, all *m* interfaces in a group are regenerated. This is illustrated in Figure 7-9, in which *m* FlexO-x interfaces are used for the multiple OTUCn clients. When the client is Ethernet, the FlexO-xe is regenerated. + +![Figure 7-9 – FlexO regeneration diagram showing two identical signal paths. Each path starts with OTUCn_i signals entering a FlexO-n/OTUCn_i block (1 to n), followed by a FlexO block (n to n), then a FlexO-x/FlexO block (1 to x), then a FlexO-x block (x to m), and finally an M-AI/FlexO-x block (m to m). The output of the M-AI/FlexO-x block goes to an M/D block, which outputs an OTSi(G) signal. The OTSi(G) signals from both M/D blocks are connected by a horizontal line. Above the M-AI/FlexO-x blocks, a line labeled FlexO-x connects the second and third blocks. The reference Y.2776(24) is shown at the bottom right.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +Figure 7-9 – FlexO regeneration diagram showing two identical signal paths. Each path starts with OTUCn\_i signals entering a FlexO-n/OTUCn\_i block (1 to n), followed by a FlexO block (n to n), then a FlexO-x/FlexO block (1 to x), then a FlexO-x block (x to m), and finally an M-AI/FlexO-x block (m to m). The output of the M-AI/FlexO-x block goes to an M/D block, which outputs an OTSi(G) signal. The OTSi(G) signals from both M/D blocks are connected by a horizontal line. Above the M-AI/FlexO-x blocks, a line labeled FlexO-x connects the second and third blocks. The reference Y.2776(24) is shown at the bottom right. + +Figure 7-9 – FlexO regeneration + +# 8 Architecture of the media network supporting the OTN digital layers + +The architecture of the media network is described using media constructs (see clause 8.1) to represent the different functions that are present in the media network. Media constructs operate on the signal envelope (e.g., amplify or attenuate the signal, or constrain or direct the media channel) and are not aware of the information being carried. Media constructs do not modulate or demodulate the signal and therefore do not process the digital information that it carries. + +A full description of the generic functional architecture of the media network is provided in [ITU-T G.807]. + +## 8.1 Media constructs + +The following media constructs used to describe the architecture of the media network are described in [ITU-T G.807]: + +- media port; +- media channel; +- media channel group (MCG); +- media channel assembly; +- media subnetwork; +- optical amplifier; +- fibre; +- optical parameter monitor (OPM-x); +- optical signal maintenance entity (OSME). + +## 8.2 Media element + +For the purposes of management and control, the media network is represented by a set of media elements. An instance of a media element encompasses the functionality represented by one or more of the media constructs. A media element is described in clause 7.2 of [ITU-T G.807]. + +## 8.3 Optical tributary signals + +As described in clause 10 of [ITU-T G.807], an OTU is supported by a set of one or more OTSiGs that are represented by OTSiG management/control abstraction together with non-associated OTSiG-O. The OTSiG and OTSiG-O are represented by the OTSiA management/control abstraction – an OTSiA carries one OTU. As described in clause 10.1 of [ITU-T G.807], each uni-directional OTSi is carried in an independent network media channel between the media port of a modulator and that of a demodulator. The set of media channels that support the members of the OTSiG may be represented as a network media channel group (NMCG). + +The case where the OTU is carried by a single OTSi is shown in Figure 8-1. + +![Diagram illustrating the mapping of an OTU to an OTSiG that contains one OTSi.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +The diagram shows the signal flow from an OTU (Optical Transport Unit) down to a network media channel group (NMCG). At the top, an OTU is connected to a Forwarding Point (FP) via an OTU CI (Container Interface). The FP is connected to an M-AI/OTU (Media Access Interface/OTU) block. This block is connected to a Media layer access point (M-AP) via an M-AI (Media Access Interface). The M-AP is connected to a Modulator (M) block, which receives 'Media layer adapted information'. The output of the Modulator is an OTSiG (Optical Transport Signal Group), which contains an OTSi (Optical Transport Signal). This OTSi is mapped to a Media port, which is part of a Network Media Channel (NMC). The NMC is part of a Network Media Channel Group (NMCG). The diagram is labeled G.872(19)-Amd.1(21)\_F8-1. + +Diagram illustrating the mapping of an OTU to an OTSiG that contains one OTSi. + +**Figure 8-1 – Mapping an OTU to an OTSiG that contains one OTSi** + +The case where an OTU is carried by more than one OTSi is illustrated in Figure 8-2. + +![Figure 8-2: Mapping an OTU to an OTSiG that contains more than one OTSi. The diagram shows an OTU at the top connected via FP and OTU CI to an M-AI/OTU block. Below this, multiple instances of M-AI are shown, with one instance labeled 'M-AI' and another 'M-AP'. These connect to two 'M' blocks. The left 'M' block is labeled '1' and the right 'M' block is labeled 'n'. Below the 'M' blocks, OTSiG and OTSi labels are present. The bottom section shows a 'Media port' connected to a blue line representing the NMC (Network Media Channel), which then splits into NMCG (Network Media Channel Group). The diagram is labeled G.872(19)-Amd.1(21)_F8-2.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +Figure 8-2: Mapping an OTU to an OTSiG that contains more than one OTSi. The diagram shows an OTU at the top connected via FP and OTU CI to an M-AI/OTU block. Below this, multiple instances of M-AI are shown, with one instance labeled 'M-AI' and another 'M-AP'. These connect to two 'M' blocks. The left 'M' block is labeled '1' and the right 'M' block is labeled 'n'. Below the 'M' blocks, OTSiG and OTSi labels are present. The bottom section shows a 'Media port' connected to a blue line representing the NMC (Network Media Channel), which then splits into NMCG (Network Media Channel Group). The diagram is labeled G.872(19)-Amd.1(21)\_F8-2. + +**Figure 8-2 – Mapping an OTU to an OTSiG that contains more than one OTSi** + +The OTSiG may have non-associated OTSiG-O. The combination of the OTSiG and OTSiG-O is represented by the OTSiA management/control abstraction (which is not present in the media network). This is illustrated in Figure 8-3. + +![Figure 8-3: Mapping an OTU to an OTSiA with non-associated OTSiG-O. This diagram is similar to Figure 8-2 but includes an additional 'OTSiG-O' block on the right. The 'M-AI/OTU' block connects to 'Multiple instances of M-AI', which then connect to 'M' blocks (labeled 1 and n). Below the 'M' blocks, OTSiG and OTSiA labels are present. The 'OTSiG-O' block is connected to the 'M' blocks and has an output labeled 'OTSiG-O'. The bottom section shows a 'Media port' connected to a blue line representing the NMC, which then splits into NMCG. The diagram is labeled G.872(19)-Amd.1(21)_F8-3.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Figure 8-3: Mapping an OTU to an OTSiA with non-associated OTSiG-O. This diagram is similar to Figure 8-2 but includes an additional 'OTSiG-O' block on the right. The 'M-AI/OTU' block connects to 'Multiple instances of M-AI', which then connect to 'M' blocks (labeled 1 and n). Below the 'M' blocks, OTSiG and OTSiA labels are present. The 'OTSiG-O' block is connected to the 'M' blocks and has an output labeled 'OTSiG-O'. The bottom section shows a 'Media port' connected to a blue line representing the NMC, which then splits into NMCG. The diagram is labeled G.872(19)-Amd.1(21)\_F8-3. + +**Figure 8-3 – Mapping an OTU to an OTSiA with non-associated OTSiG-O** + +The digital payload processing functions related to the OTU termination, M-AI/OTU adaptation and OTSiG-O termination use the processes specified in [ITU-T G.798] and the frame formats defined in + +[ITU-T G.709]. The frame format and forward error correction (FEC) are specified in the ITU-T G.709.x series of Recommendations. + +NOTE – As described in clause 10.2.1 of [ITU-T G.807], the OTSi may support two independent digital clients, one of which is the OTU, and the other may be the OTSiG-O. + +Figures 8-1, 8-2 and 8-3 give an overview of the payload processing functions that provide the interface to the media. The client of the OTSiA (the OTU) is presented to the M-AI/OTU adaptation function. The OTSi is generated from the M-AI by a modulator and converted back to the M-AI by a demodulator. The OTSi is carried in a network media channel. + +The OTN uses the frequency grids specified in [ITU-T G.694.1] and the wavelength grids specified in [ITU-T G.694.2] for media channels. + +## **8.4 Management of optical signals** + +### **8.4.1 OMS and OTS media channel group** + +The optical transmission section (OTS) MCG and optical multiplex section (OMS) MCG are described in clause 7.3.3 of [ITU-T G.807] as topological constructs that are used for management control purposes. The management and monitoring of these entities is also described in clause 8.2 of [ITU-T G.807]. + +NOTE – The terms OMS media link and OTS media link used in the 2017 version (Edition 4.0) of this Recommendation have been replaced with the terms OMS MCG and OTS MCG in [ITU-T G.807]. + +### **8.4.2 OSC** + +The OSC is described in clause 12 of [ITU-T G.807]. + +### **8.4.3 Optical signal maintenance entities** + +OSMEs are described in clause 8.2 of [ITU-T G.807]. + +### **8.4.4 Media channels and OSMEs** + +The relationship between media channels and OSMEs is described in clause 8.2 of [ITU-T G.807]. + +## **8.5 Management of media and signals** + +### **8.5.1 Management of media channels** + +The management of media channels is described in clause 7.4 of [ITU-T G.807]. + +### **8.5.2 Assignment of signals to media channels** + +The assignment of signals to media channels is described in clause 10.1.1 of [ITU-T G.807]. + +### **8.5.3 Management of OTSiA connections** + +The management of OTSiA connections is described in clause 10.3.1 of [ITU-T G.807]. + +## **8.6 Modulator/demodulator and termination functions** + +The modulator/demodulator and the termination functions in the media network are described in clause 13 of [ITU-T G.807]. + +## **8.7 Client/server associations** + +### **8.7.1 M-AI/OTU adaptation function** + +The bidirectional M-AI/OTU adaptation function is performed by a collocated pair of source and sink M-AI/OTU adaptation functions. + +The M-AI/OTU adaptation source performs the following processes between its input and output. + +- The source accepts the output of the OTU trail termination and performs the processing required to generate one or more instances of M-AI. The actual processes required are dependent upon the particular implementation of the client/server. Forward error correction is an optional feature, which may be required if impairments (e.g., bit errors) are expected in the M-AI at the output of the demodulator. +- The source generates any OTSiG-O that is required. + +The M-AI/OTU adaptation sink performs the following processes between its input and output- + +- The sink accepts the M-AI from one or more demodulators and recovers the OTU CI. The actual processes are dependent upon the particular implementation of the client/server relationship. Forward error correction is an optional feature. + +NOTE – Some of these processes may rely on information extracted from the OTSi by the demodulator. + +- The sink accepts and processes any OTSi overhead from the OTSiG-O trail termination function. + +### **8.7.2 OMS-O/OTSiG-O adaptation function** + +The OMS-O/OTSiG-O adaptation function is described in clause 14.2 of [ITU-T G.807]. + +### **8.7.3 OTS-O/OMS-O adaptation function** + +The optical transmission section overhead (OTS-O)/OMS-O adaptation function is described in clause 14.3 of [ITU-T G.807]. + +### **8.7.4 M-AI/OTS-O adaptation** + +The M-AI/OTS-O adaptation function is described in clause 14.4 of [ITU-T G.807]. + +# **9 Media network topology** + +The OTN digital layers can support unidirectional and bidirectional point-to-point connections, and unidirectional point-to-multipoint connections as described in [ITU-T G.805]. + +The media can be configured to provide point-to-point and point-to-multipoint media channels. A media channel may support the propagation of a signal in one or both directions. A bidirectional OTSi is supported by two network media channels (one for each direction of propagation). Media topology is described in clause 7.3 of [ITU-T G.807]. + +# **10 Management** + +This clause provides an overview of the fault, performance and configuration management capabilities provided by the OTN. The full set of capabilities are described in [ITU-T G.709] and [ITU-T G.798]. + +The OTN digital layers (ODU, OTU) use digital overhead to provide OAM, which can report on the status of the layer and may be used to infer the status of the server layer. + +A media network that is deployed as a part of an OTN network uses the management capabilities (including media monitoring and non-associated overhead) described in clause 15 of [ITU-T G.807] and the OSC described in clause 12 of [ITU-T G.807]. + +## **10.1 Capabilities** + +### **10.1.1 Fault, configuration and performance management** + +The OTN provides support for fault, configuration and performance management end to end, within an administrative domain and between the boundaries of administrative domains. + +The OTN shall provide the capability to: + +- interconnect reference points e.g., FP (with compatible CI) and media ports that will support compatible OTSi; +- detect and isolate faults and initiate recovery actions where applicable; +- support single-ended maintenance; +- detect and report misconnections; +- report any interruptions within a layer to the upstream and downstream entities in that layer; +- detect performance degradation and verify quality of service. + +### **10.1.2 Client/server interaction** + +The server detects and indicates to the client layer when the M-AI or optical signal is not present. + +To avoid unnecessary, inefficient or conflicting survivability actions, escalation strategies (e.g., introduction of hold-off times and alarm suppression methods) may be required: + +- within a layer; +- between a server and client layer. + +### **10.1.3 Adaptation management** + +Adaptation management refers to the set of processes for managing the adaptation of a client layer network to and from the server layer network. + +### **10.1.4 Connection and MCG supervision** + +#### **10.1.4.1 Continuity supervision** + +Continuity supervision refers to the set of processes for monitoring the continuity of an entity (e.g., connection, trail, MCG). + +In general, a continuity fault in a server is indicated to a client through server signal fail indication. + +Continuity supervision of media is described in clause 15 of [ITU-T G.807]. + +#### **10.1.4.2 Connectivity supervision** + +Connectivity supervision refers to the set of processes for monitoring the integrity of the routing of a MCG or a connection between source and sink trail terminations. + +Connectivity supervision is necessary to confirm proper routing of a connection between trail termination source and sink during the connection set-up process. Furthermore, connectivity supervision is needed to ensure that connectivity is maintained while the connection is active. + +Connectivity supervision of MCGs is described in clause 15 of [ITU-T G.807]. + +A trail trace identifier (TTI) is necessary to ensure that the signal received by a trail termination sink originates from the intended trail termination source. A TTI is provided at the: + +- OTU layer to ensure proper OTU layer connections; +- ODU layer to ensure proper ODU layer connections; +- OTS-O layer to ensure proper connectivity of the OTS MCG; +- OTSiG-O layer to ensure proper connectivity of the NMCG. + +NOTE – OTSiG-O TTI is not supported in equipment that complies with Edition 5 (or earlier editions) of [ITU-T G.709]. + +#### **10.1.4.3 Maintenance information** + +Maintenance information refers to the set of processes for indicating defects in a connection that is part of a trail. The defect indications are given in the downstream and upstream directions of a bidirectional trail. + +An overview of the maintenance information for the media network is described in clause 15 of [ITU-T G.807], detailed information is provided in [ITU-T G.709] and [ITU-T G.798]. + +Four maintenance information processes are identified for the digital layers: + +- forward defect indication; +- backward defect indication; +- payload missing indication; +- open connection indication. + +These processes enable defect localization and single-ended maintenance. + +#### **10.1.4.4 Subnetwork/tandem/unused connection supervision** + +Supervision for subnetwork connections, tandem connections and unused connections is required for the ODU layer. Connection supervision techniques and applications are listed in clauses 10.2 and 10.3. + +### **10.1.5 Connection quality supervision** + +Connection quality supervision refers to the set of processes for monitoring the performance of a connection. Generic processes include parameter measurement, collection, filtering and processing. Connection quality supervision, by means of BIP-8, is only supported for the ODU and OTU layer networks. Delay measurement is also supported by the ODU layer. + +### **10.1.6 Management communications** + +Management communications are transported via an embedded communication channel (ECC) as specified in [ITU-T G.7712]. The ECC may be supported by one of the ODU or OTU general communication channels, FlexO communication channels, or by the OSC (see clause 12 of [ITU-T G.807]). + +### **10.1.7 Frequency and time synchronization** + +The communication of time and frequency information between adjacent network elements is supported by the OTUk, FlexO and OSC. + +## **10.2 Connection supervision techniques** + +Connection supervision is the process of monitoring the integrity of a given connection in the digital layers of the OTN. Integrity may be verified by means of detecting and reporting connectivity and transmission performance defects for a given connection. [ITU-T G.805] defines four types of monitoring techniques for connections: + +- inherent monitoring; +- non-intrusive monitoring; +- intrusive monitoring; +- sublayer monitoring. + +## **10.3 Connection supervision applications** + +### **10.3.1 Unused connections** + +In order to detect the inadvertent opening of a subnetwork connection in a subnetwork, ODU overhead includes an indication of whether an ODU TS is occupied or not (OPU MSI). See [ITU-T G.798] for further details. + +### **10.3.2 Connection monitoring** + +ODU connection monitoring may be applied to: + +- a network connection; +- a subnetwork connection, establishing a serving operator administrative domain tandem connection; +- a link connection, establishing a service requesting administrative domain tandem connection or a protected domain tandem connection; +- a link connection (by means of the OTU), for fault and performance degradation detection for network maintenance purposes. + +ODU connection monitoring can be established for a number of nested connections, up to the maximum level specified by [ITU-T G.709]. The number of connection monitoring levels that can be used by each operator or user involved in an ODU connection must be mutually agreed between these operators and users. + +# **11 OTN survivability techniques** + +It is expected that survivability techniques will only be used in the OTN for the ODUk layer network and the media. + +For ODU transport entities, digital overhead is used to detect faults or performance degradations (see clause 10); these events may be used to trigger the replacement of the failed transport entity (TE) with a protection TE. + +Survivability techniques for the media network are described in clause 16 of [ITU-T G.807] + +Specific survivability techniques include protection (specified in the ITU-T G.873.x series of Recommendations) and restoration, such as being controlled by an automatically switched optical network or a software-defined network. Details of these techniques lie outside the scope of this Recommendation. + +# Annex A + +## Fine grain flexible optical data unit path layer network + +(This annex forms an integral part of this Recommendation.) + +The fgODUflex path layer network (see [ITU-T G.709.20]) is a client to the ODUk layers. + +The relationship between the fgODUflex and ODUk is shown in Figure A.1. The fgODUflex layer is a client of the ODUk layer (k=0, 1, 2, flex). + +![Figure A.1: Client/server association of the fgODUflex and ODUk. The diagram shows two vertical stacks of network layers. The top stack represents the fgODUflex layer network, starting with 'fgODUflex/Client_A source' at the top, followed by 'fgODUflex_AP', 'fgODUflex_TT source', 'fgODUflex_FP', and 'ODUk/fgODUflex_A source'. The bottom stack represents the ODUk layer network, starting with 'ODUk/fgODUflex_A sink' at the top, followed by 'ODUk_AP', 'ODUk_TT sink', 'ODUk_FP', and 'fgODUflex/Client_A sink' at the bottom. Horizontal dashed lines connect corresponding interfaces between the two stacks: 'fgODUflex trail' between fgODUflex_AP units, 'fgODUflex network connection' between fgODUflex_FP units, and 'ODUk trail' and 'ODUk network connection' between ODUk_AP and ODUk_FP units respectively. Vertical double-headed arrows on the left indicate the boundaries of the 'fgODUflex layer network' and the 'ODUk layer network'. A small label 'G.872(24)' is at the bottom right.](5478f70a6cef3e5672b2b22d28830cfb_img.jpg) + +Figure A.1: Client/server association of the fgODUflex and ODUk. The diagram shows two vertical stacks of network layers. The top stack represents the fgODUflex layer network, starting with 'fgODUflex/Client\_A source' at the top, followed by 'fgODUflex\_AP', 'fgODUflex\_TT source', 'fgODUflex\_FP', and 'ODUk/fgODUflex\_A source'. The bottom stack represents the ODUk layer network, starting with 'ODUk/fgODUflex\_A sink' at the top, followed by 'ODUk\_AP', 'ODUk\_TT sink', 'ODUk\_FP', and 'fgODUflex/Client\_A sink' at the bottom. Horizontal dashed lines connect corresponding interfaces between the two stacks: 'fgODUflex trail' between fgODUflex\_AP units, 'fgODUflex network connection' between fgODUflex\_FP units, and 'ODUk trail' and 'ODUk network connection' between ODUk\_AP and ODUk\_FP units respectively. Vertical double-headed arrows on the left indicate the boundaries of the 'fgODUflex layer network' and the 'ODUk layer network'. A small label 'G.872(24)' is at the bottom right. + +Figure A.1 – Client/server association of the fgODUflex and ODUk + +The currently supported set of clients and servers for fine grain OTN) is provided in clause A.1.1. + +## A.1 Fine grain flexible optical data unit path layer network + +The fgODUflex path layer network provides end-to-end transport of digital client information across the OTN. The description of the supported client layer networks lies outside the scope of this Recommendation. + +The CI of an fgODUflex layer network is described in terms of the frame structure defined in [ITU-T G.709], and is composed of: + +- the fine grain flexible optical payload unit (fgOPUflex) which is the payload area of the fgODUflex that is used to transport the digital client(s); and +- the fgODUflex and fgOPUflex overhead area for the transport of the associated overhead. + +Details of the format are provided in [ITU-T G.709]. + +The topological components of the fgODUflex layer network are fgODUflex subnetworks, fgODUflex access groups and fgODUflex links. The links are supported by a server ODU trail. The fgODUflex subnetwork may provide connections for fgODUflex. The TS size supported by a server ODU (ODUk(fgTS)/ODUflex(fgTS,n)) and the bit rate of the client fgODUflex are modelled as parameters. These parameters allow the number of TSs that an fgODUflex will occupy on an ODU link connection (i.e., within a server ODU) to be determined. Each client fgODUflex is mapped into an integer number of server ODU TS. + +To provide end-to-end networking, the following capabilities are included in the fgODUflex layer network: + +- fgODUflex connection rearrangement for flexible network routing; +- fgODUflex overhead processes to verify the integrity of the client AI; +- fgODUflex OAM functions, including network survivability. + +The fgODUflex layer network contains the following topological components, transport processing functions and transport entities (see Figure A.2). The interlayer adaptation functions are described in clause 7.3. + +Topological components: + +- fgODUflex layer network; +- fgODUflex subnetwork; +- fgODUflex access group; +- fgODUflex link. + +Transport processing functions: + +- fgODUflex trail termination source; +- fgODUflex trail termination sink. + +Transport entities: + +- fgODUflex trail; +- fgODUflex network connection; +- fgODUflex link connection; +- fgODUflex subnetwork connection. + +![Figure A.2 – fgODUflex layer network example. A layered architectural diagram showing the relationship between Access Points (AP), Trail Termination (TT) points, Forwarding Points (FP), and Subnetwork Connections. At the top, a dashed line represents the 'fgODUflex trail' between two 'fgODUflex_AP' points. Below these are 'fgODUflex_TT source' and 'fgODUflex_TT sink' represented by triangles. These connect to 'fgODUflex_FP' points. A dashed line between FPs represents the 'fgODUflex network connection'. At the bottom, three 'fgODUflex subnetwork connection' ovals are linked together, with blue arrows pointing from 'fgODUflex subnetwork' labels to the connections and 'fgODUflex_FP' labels between them.](f732d3320afe06d979aabbd366184254_img.jpg) + +``` + +graph TD + subgraph "fgODUflex trail" + AP1[fgODUflex_AP] -.- AP2[fgODUflex_AP] + end + AP1 --- TT_src[fgODUflex_TT source] + AP2 --- TT_sink[fgODUflex_TT sink] + TT_src --- FP1[fgODUflex_FP] + TT_sink --- FP2[fgODUflex_FP] + subgraph "fgODUflex network connection" + FP1 -.- FP2 + end + FP1 --- SNC1([fgODUflex subnetwork connection]) + SNC1 --- FP3[fgODUflex_FP] + FP3 --- SNC2([fgODUflex subnetwork connection]) + SNC2 --- FP4[fgODUflex_FP] + FP4 --- SNC3([fgODUflex subnetwork connection]) + SNC3 --- FP2 + + SN1[fgODUflex subnetwork] --> SNC1 + SN2[fgODUflex subnetwork] --> SNC2 + SN3[fgODUflex subnetwork] --> SNC3 + +``` + +Figure A.2 – fgODUflex layer network example. A layered architectural diagram showing the relationship between Access Points (AP), Trail Termination (TT) points, Forwarding Points (FP), and Subnetwork Connections. At the top, a dashed line represents the 'fgODUflex trail' between two 'fgODUflex\_AP' points. Below these are 'fgODUflex\_TT source' and 'fgODUflex\_TT sink' represented by triangles. These connect to 'fgODUflex\_FP' points. A dashed line between FPs represents the 'fgODUflex network connection'. At the bottom, three 'fgODUflex subnetwork connection' ovals are linked together, with blue arrows pointing from 'fgODUflex subnetwork' labels to the connections and 'fgODUflex\_FP' labels between them. + +**Figure A.2 – fgODUflex layer network example** + +### A.1.1 fgODUflex clients and servers + +fgODUflex is specified in [ITU-T G.709]. + +The set of fgODUflex servers and their non-OTN clients is provided in Table A.1. + +**Table A.1 – fgODUflex servers and their non-OTN clients** + +| fgODUflex server | non-OTN clients | +|------------------|----------------------------------------------------| +| fgODUflex | CBR and PKT clients at rates less than 1.23 Gbit/s | + +The set of fgODUflex clients and their ODU servers is provided in Table A.2. + +**Table A.2 – fgODUflex client and their servers** + +| ODU server | ODU clients | +|----------------|--------------------------------| +| ODU0 | fgODUflex | +| ODUflex (NOTE) | fgODUflex | +| ODU1 | ODU0, fgODUflex | +| ODU2 | ODU0, ODU1, ODUflex, fgODUflex | + +NOTE – Generic mapping procedure-mapped fgODUflex clients to ODUflex(fgTS,n) which is $n \times 1\,244\,160$ kbit/s ( $n = 3$ to 7). + +The total number of fgTS available in a server ODU (when carrying one or more ODUk client(s)), is provided in Table A.3. + +**Table A.3 – Number of tributary slots for each ODU** + +| ODU server | Nominal fgTS capacity (10 Mbit/s) | +|------------------|-----------------------------------| +| ODU0(fgTS) | 119 | +| ODU1(fgTS) | 238 | +| ODUflex(fgTS, 3) | 357 | +| ODUflex(fgTS, 4) | 476 | +| ODUflex(fgTS, 5) | 595 | +| ODUflex(fgTS, 6) | 714 | +| ODUflex(fgTS, 7) | 833 | +| ODU2(fgTS) | 952 | + +### A.1.2 fgODUflex trail termination + +The following generic processes may be assigned to the fgODUflex trail termination: + +- validation of connectivity integrity; +- assessment of transmission quality; +- transmission defect detection and indication. + +The requirements for these processes are outlined in clause 10. + +There are three types of fgODUflex trail termination: + +- fgODUflex bidirectional trail termination: consists of a pair of collocated fgODUflex trail termination source and sink functions; + +- fgODUflex trail termination source: accepts AI from a client layer network at its input, inserts the fgODUflex trail termination overhead as a separate and distinct logical data stream and presents the CI of the fgODUflex layer network at its output; +- fgODUflex trail termination sink: accepts the CI of the fgODUflex layer network at its input, extracts the separate and distinct logical data stream containing the fgODUflex trail termination overhead and presents the AI at its output. + +### A.1.3 fgODUflex transport entities + +Network connections, subnetwork connections, link connections, tandem connections and trails are as described in [ITU-T G.800]. + +#### A.1.3.1 fgODUflex tandem connections + +The fgODUflex overhead includes information to support monitoring the end-to-end fgODUflex trail and up to two levels of tandem connections. The fgODUflex path OH is terminated where the fgODUflex is assembled and disassembled. The tandem connection overhead is added and terminated at the end of each tandem connection. + +NOTE – In normal operation, the monitored tandem connections may be nested, cascaded or both. For test purposes the monitored tandem connections may overlap. Overlapped monitored connections must be operated in a non-intrusive mode. + +### A.1.4 fgODUflex topological components + +Layer network, subnetworks, links (including transitional links) and access groups are as described in [ITU-T G.800]. + +The fgODUflex subnetwork provides flexibility within the fgODUflex layer network. fgODUflex CI is routed between input and output FPs. + +## A.2 Client/server associations + +### A.2.1 fgODUflex/client adaptation + +The fgODUflex/client adaptation is considered to consist of two types of process: client-specific and server-specific. The description of client-specific processes lies outside the scope of this Recommendation. The fgODUflex servers are specified in Table A.1. + +The bidirectional fgODUflex/client adaptation function is performed by a collocated pair of source and sink fgODUflex/client adaptation functions. + +The fgODUflex/client adaptation source performs the following processes between its input and output: + +- all the processing required to adapt the client signal to the fgODUflex payload area – the processes are dependent upon the particular client signal; +- generation and termination of management/maintenance signals as described in clause 10. + +The fgODUflex/client adaptation sink performs the following processes between its input and output: + +- recovery of the client signal from the fgODUflex payload area – the processes are dependent upon the particular client/server relationship; +- generation and termination of management/maintenance signals as described in clause 10. + +### A.2.2 ODU/fgODUflex adaptation + +The bidirectional ODU/fgODUflex adaptation function is performed by a collocated pair of source and sink ODU/fgODUflex adaptation functions. The ODU/fgODUflex adaptations are specified in Table 7-2. + +The ODU/fgODUflex adaptation source performs the following processes between its input and output: + +- multiplexing lower rate fgODUflex clients to form a higher bit rate ODU server; +- generation and termination of management/maintenance signals as described in clause 10. + +The ODU/fgODUflex adaptation sink performs the following processes between its input and output: + +- demultiplexing the lower rate fgODUflex clients from the higher rate ODU server; +- generation and termination of management/maintenance signals as described in clause 10. + +## **A.3 Management** + +The fgODUflex digital layer uses digital overhead to provide OAM as described in clause 10 for the ODU layer, which can report on the status of the layer and may be used to infer the status of the server layer. + +- A TTI is provided at the fgODUflex layer to ensure proper fgODUflex layer connections. +- Supervision for subnetwork connections, tandem connections and unused connections is required for the fgODUflex layer. Connection supervision techniques and applications are listed in clauses 10.2 and 10.3. +- Connection quality supervision refers to the set of processes for monitoring the performance of a connection. Generic processes include parameter measurement, collection, filtering and processing. Connection quality supervision, by means of BIP-8, is supported for fgODUflex layer networks. Delay measurement is also supported by the fgODUflex layer. + +## **A.4 OTN survivability techniques** + +For fgODUflex transport entities, digital overhead is used to detect faults or performance degradations (see clause 10) these events may be used to trigger the replacement of a failed by a protection TE. + +# Appendix I + +## Relationship between optical channel and optical tributary signal terminology + +(This appendix does not form an integral part of this Recommendation.) + +The mapping from the OCh terminology to the OTSi terminology is provided in Table I.1 and Figure I.1. + +**Table I.1 – Mapping between OCh and OTSi terminology** + +| OCh term | OTSi term | Number of OTSi in the OTSiG | +|---------------------------|------------------|-----------------------------| +| OCh-P | OTSi | 1 | +| none | OTSi | >1 | +| OCh-P | OTSiG | 1 | +| none | OTSiG | >1 | +| OCh-O | OTSiG-O | See Note | +| OCh | OTSiA | 1 | +| none | OTSiA | >1 | +| OCh-P connection function | Media subnetwork | not applicable | + +NOTE – The OCh-O supports a subset of the capabilities provided by the OTSiG-O. These differences are described in detail in [ITU-T G.709]. + +![A schematic diagram showing the relationship between OCh and OTSi terminology in an optical network. It illustrates the flow of signals from an OTU through various optical components like filters, amplifiers, and subnetworks, with corresponding terminology labels on the right side.](77959075c823bb5169480d7b8ff82a63_img.jpg) + +The diagram illustrates the relationship between OCh and OTSi terminology in an optical network. It shows the flow of signals from an OTU through various optical components, with corresponding terminology labels on the right side. + +**Left Side (OCh Terminology):** + +- OTU +- Digital-lane/OTU (OCh/OTU) +- OTSi (OCh-P) +- Media subnetwork (OCh-P) +- OTSi filter +- Optical amplifier +- OSC filter + +**Right Side (OTSiG Terminology):** + +- AI\_TSF +- OTSiG-O (OCh-O) +- OMS-O/OTSiG-O (OMS-O/OCh-O) +- OMS-O +- OTS-O +- Digital-lane/OTS-O (OSC/OTS-O) +- OSC + +**Other Labels and Connections:** + +- OTSi\* (OCh-P) and OTSiA\* (OCh) point to the OTSi (OCh-P) block. +- OTSiG-O (OCh-O) points to the OTSiG-O (OCh-O) block. +- Power (P) inputs are shown for the Optical amplifier and OSC filter. +- Loss of Signal (LOS) indicators are shown: OMS LOS and OTS LOS. +- Signal flow is indicated by solid blue lines with diamond-shaped connectors. + +G.872(19)\_FI.1 + +A schematic diagram showing the relationship between OCh and OTSi terminology in an optical network. It illustrates the flow of signals from an OTU through various optical components like filters, amplifiers, and subnetworks, with corresponding terminology labels on the right side. + +\* NOTE – This figure only applies when the OTSiG contains a single OTSi + +**Figure I.1 – Relationship between OCh and OTSi terminology** + +# Appendix II + +## Use of optical transport networks to carry Flex Ethernet + +(This appendix does not form an integral part of this Recommendation.) + +## II.1 Overview of Flex Ethernet + +FlexE provides two, essentially independent, capabilities as follows. + +#### – **Bonding:** + +The ability to bond existing Ethernet physical interfaces (PHYs) allows, for example, a 400G media access control (MAC) to be supported over four bonded 100GBASE-R PHYs. The set of PHYs that are bonded are referred to as a FlexE group. + +#### – **Support of sub-rate clients:** + +FlexE allows a PHY to support MAC clients at rates of 10, 40 or $m \times 25$ Gbit/s, the bit rate of these MAC clients is not constrained to correspond to an existing Ethernet PHY rate. The allocation of the capacity of the PHY is managed by a calendar. The calendar can allocate the PHY capacity to a combination of MAC clients, up to the capacity of the PHY, e.g: + +- a 100GBASE-R PHY can support two 25 Gbit/s and five 10 Gbit/s MAC clients; or +- two bonded 100GBASE-R PHYs can be used to support one 150 Gbit/s MAC client (with the remainder of the PHY calendar slots marked as unused). + +The capabilities of FlexE are specified in [b-OIF FlexE IA], the mapping of FlexE into an ODUk (via OPUflex) is specified in [ITU-T G.709]. + +Ethernet PHY interfaces to the OTN, which are used for FlexE, may operate in one of the three modes described in clauses II.2 to II.4. + +## II.2 FlexE unaware + +In this case, the OTN is unaware of FlexE. This case allows, for example, an OTN network that only supports OTU4s to be used to carry FlexE clients with a bit rate in excess of 100 Gbit/s. + +The payload from each Ethernet PHY is independently mapped (using a PCS codeword transparent mapping) into the appropriate ODUk, which is carried by an OTU (see clause 7). + +If the FlexE group is carried over more than one OTU, to control the differential delay between the members of the FlexE group, all OTUs must then be co-routed through the media network e.g., carried over the same OMS MCG. + +## II.3 FlexE aware + +In this case, the OTN is aware of FlexE but the FlexE group is not terminated. This case supports, for example, applications where the bit rate carried by an OTU does not match the bit rate of the Ethernet PHY or is not an exact multiple of the Ethernet PHY rate. + +The equipped FlexE instances from one or more of the Ethernet PHYs in the same FlexE group are mapped into an ODUflex, the contents of the "UNAVAILABLE" calendar slots are discarded as described in the following. + +If the FlexE group is mapped into more than one ODUflex (each carried over an OTU) then, to control the differential delay between the members of the FlexE group, all OTUs must be co-routed through the media network e.g., carried over the same OMS MCG. + +The transport network discards unequipped FlexE instances and bits from the unavailable calendar slots at the ingress to the OTN network. The unequipped FlexE instances and bits from unavailable calendar slots (that were discarded at the ingress) are re-inserted with fixed values at the egress of the OTN network (to restore the original Ethernet PHY bit rate). + +## **II.4 FlexE terminating** + +In this case the FlexE is fully terminated, the members of the FlexE group are aligned (i.e., the differential delay is compensated) and the FlexE clients are extracted. Each FlexE client is then mapped into an ODUflex. Each of the FlexE clients (carried in an ODUflex) may be routed to a different destination. + +# Appendix III + +## Examples of views of an optical data unit layer network + +(This appendix does not form an integral part of this Recommendation.) + +This appendix provides examples of how the topology of an ODU layer network may be viewed either independent of k or to provide a view for a specific value of k. + +Figure III.1 shows the topology of a simple ODU network; this view is independent of the value of k. + +![Figure III.1: Example of an ODU network. A diagram showing four subnetworks (A, B, C, D) connected by five links. Subnetwork A is on the left, B is at the bottom, C is on the right, and D is at the top. Link 1 connects A and D, link 2 connects A and C, link 3 connects A and B, link 4 connects D and C, and link 5 connects B and C.](e05122559f56af5699789b7118d8fe87_img.jpg) + +``` +graph LR; A((ODUk subnetwork A)) ---|ODUk link 1| D((ODUk subnetwork D)); A ---|ODUk link 2| C((ODUk subnetwork C)); A ---|ODUk link 3| B((ODUk subnetwork B)); D ---|ODUk link 4| C; B ---|ODUk link 5| C; +``` + +G.872(17)\_FIII.1 + +Figure III.1: Example of an ODU network. A diagram showing four subnetworks (A, B, C, D) connected by five links. Subnetwork A is on the left, B is at the bottom, C is on the right, and D is at the top. Link 1 connects A and D, link 2 connects A and C, link 3 connects A and B, link 4 connects D and C, and link 5 connects B and C. + +**Figure III.1 – Example of an ODU network** + +A link or subnetwork may not be able to support all values of k because of limitations in the resources that support it or a decision by the network operator. Because of these limitations for a specific value of k, some links and subnetworks may be removed from the topology. Considering the example in Figure III.1, if links 1 and 5 cannot support an ODU4 but all other links and subnetworks can, then the topology for an ODU4 would be reduced as shown in Figure III.2. + +![Figure III.2: Example of an ODU4 network. A diagram showing the same four subnetworks (A, B, C, D) as Figure III.1, but with links 1 and 5 removed. Link 1 (between A and D) and link 5 (between B and C) are absent, leaving links 2, 3, and 4.](50214d232017279410e9c9db8eb75119_img.jpg) + +``` +graph LR; A((ODUk subnetwork A)) ---|ODUk link 2| C((ODUk subnetwork C)); A ---|ODUk link 3| B((ODUk subnetwork B)); D((ODUk subnetwork D)) ---|ODUk link 4| C; +``` + +G.872(17)\_FIII.2 + +Figure III.2: Example of an ODU4 network. A diagram showing the same four subnetworks (A, B, C, D) as Figure III.1, but with links 1 and 5 removed. Link 1 (between A and D) and link 5 (between B and C) are absent, leaving links 2, 3, and 4. + +**Figure III.2 – Example of an ODU4 network** + +If some regions of a network cannot support particular ODUj connections, for example as shown in Figure III.3, subnetwork B cannot support ODU0 connections. With this topology, it is not possible to support an ODU0 connection between ODUk subnetworks A and C. + +![Diagram of a limited capability ODuk subnetwork. Three ovals labeled 'ODUk subnetwork A', 'ODUk subnetwork B', and 'ODUk subnetwork C' are arranged in a triangle. A line labeled 'ODUk link 3' connects A and B, and a line labeled 'ODUk link 5' connects B and C. The reference 'G.872(17)_FIII.3' is in the bottom right.](798679874d1c29f8343506a156c79d7e_img.jpg) + +Diagram of a limited capability ODuk subnetwork. Three ovals labeled 'ODUk subnetwork A', 'ODUk subnetwork B', and 'ODUk subnetwork C' are arranged in a triangle. A line labeled 'ODUk link 3' connects A and B, and a line labeled 'ODUk link 5' connects B and C. The reference 'G.872(17)\_FIII.3' is in the bottom right. + +**Figure III.3 – Limited capability ODuk subnetwork** + +To allow ODU0 to be carried between ODUk subnetwork A and C, an ODUk connection can be established, as shown in Figure III.4. + +![Diagram of ODUj link construction. It shows three subnetworks: A, B, and C. Subnetworks A and C are connected to B via 'ODUk link 3' and 'ODUk link 5' respectively. A direct 'ODU0 link' is shown between A and C, which is supported by a dashed 'ODUk trail'. Below the subnetworks, there are representations of ODUk interfaces and internal structures. The reference 'G.872(17)_FIII.4' is in the bottom right.](8269648391c59363ea61243864a2adf7_img.jpg) + +Diagram of ODUj link construction. It shows three subnetworks: A, B, and C. Subnetworks A and C are connected to B via 'ODUk link 3' and 'ODUk link 5' respectively. A direct 'ODU0 link' is shown between A and C, which is supported by a dashed 'ODUk trail'. Below the subnetworks, there are representations of ODUk interfaces and internal structures. The reference 'G.872(17)\_FIII.4' is in the bottom right. + +**Figure III.4 – ODUj link construction** + +The ODUk trail supports an ODU0 link, which then appears in an ODUk topology, as shown in Figure III.5. + +![Diagram of a modified ODuk topology. Three ovals labeled 'ODUk subnetwork A', 'ODUk subnetwork B', and 'ODUk subnetwork C' are arranged in a triangle. A line labeled 'ODUk link 6' connects A and C, a line labeled 'ODUk link 3' connects A and B, and a line labeled 'ODUk link 5' connects B and C. The reference 'G.872(17)_FIII.5' is in the bottom right.](030c758fd425016b03290c8f11bef69d_img.jpg) + +Diagram of a modified ODuk topology. Three ovals labeled 'ODUk subnetwork A', 'ODUk subnetwork B', and 'ODUk subnetwork C' are arranged in a triangle. A line labeled 'ODUk link 6' connects A and C, a line labeled 'ODUk link 3' connects A and B, and a line labeled 'ODUk link 5' connects B and C. The reference 'G.872(17)\_FIII.5' is in the bottom right. + +**Figure III.5 – Modified ODuk topology** + +For the ODU0 topology, ODUk subnetwork B and ODUk links 3 and 5 are removed, resulting in the ODU0 topology shown in Figure III.6. + +![Diagram of the ODU0 topology. Two ovals labeled 'ODUk subnetwork A' and 'ODUk subnetwork C' are connected by a single line labeled 'ODU0 link'. The reference 'G.872(17)_FIII.6' is in the bottom right.](0908107b858fa3783d10d93b3a3444b2_img.jpg) + +Diagram of the ODU0 topology. Two ovals labeled 'ODUk subnetwork A' and 'ODUk subnetwork C' are connected by a single line labeled 'ODU0 link'. The reference 'G.872(17)\_FIII.6' is in the bottom right. + +**Figure III.6 – ODU0 topology** + +The topology for other values of k would be as shown in Figure III.7. The capacities of ODUk links 3 and 5 are reduced by the capacity used by the ODU0 link. + +![Diagram of ODUk topology showing three subnetworks (A, B, C) connected in a chain. Subnetwork A is connected to B via ODUk link 3, and B is connected to C via ODUk link 5.](b05bae46f7079e5c9b1da38adb2319e8_img.jpg) + +``` + +graph LR + A([ODUk subnetwork A]) --- L3(ODUk link 3) --- B([ODUk subnetwork B]) + B --- L5(ODUk link 5) --- C([ODUk subnetwork C]) + +``` + +The diagram illustrates an ODUk topology with three subnetworks: ODUk subnetwork A, ODUk subnetwork B, and ODUk subnetwork C. Subnetwork A is connected to subnetwork B via ODUk link 3, and subnetwork B is connected to subnetwork C via ODUk link 5. The subnetworks are represented by ovals, and the links are represented by lines connecting them. A small text label G.872(17)\_FIII.7 is located to the right of the diagram. + +G.872(17)\_FIII.7 + +Diagram of ODUk topology showing three subnetworks (A, B, C) connected in a chain. Subnetwork A is connected to B via ODUk link 3, and B is connected to C via ODUk link 5. + +**Figure III.7 – ODUk topology** + +# Appendix IV + +## Examples of multi-domain optical transport network applications + +(This appendix does not form an integral part of this Recommendation.) + +This appendix provides an example of the use of OTNs in multi-domains where two disjoint domains in the network of carrier A (domain A1 and domain A2) are interconnected through the network of another carrier (domain B). The interconnection is supported by an ODUk. Carrier A multiplexes several (lower rate) ODUj services into this ODUk. This ODUk may be carried across domain B in several different ways, the following three scenarios illustrate these options. + +In scenario 1, shown in Figure IV.1, the ODUk is carried directly by an OTUk in domain B. + +![Diagram of Multi-domain OTN scenario 1 showing three domains: Domain A1, Domain B, and Domain A2. Domain A1 and A2 are connected via Domain B. In Domain A1, an ODU SN is connected to an ODUk/ODUj block, which is connected to an ODUk block. In Domain A2, an ODU SN is connected to an ODUk/ODUj block, which is connected to an ODUk block. A dashed line labeled 'ODUk trail' connects the ODUk block in Domain A1 to the ODUk block in Domain A2. Domain B contains two OTUk/ODUk blocks, each connected to an ODU SN. A dashed line labeled 'OTUj trail' connects the two OTUk/ODUk blocks. The ODUk block in Domain A1 is connected to the first OTUk/ODUk block in Domain B, and the ODUk block in Domain A2 is connected to the second OTUk/ODUk block in Domain B. The text 'G.872(17)_FIV.1' is in the bottom right corner.](67d03c9e89620d73e3786c869e559752_img.jpg) + +The diagram illustrates a multi-domain OTN scenario across three domains: Domain A1, Domain B, and Domain A2. Domain A1 and Domain A2 are connected via Domain B. In Domain A1, an ODU SN is connected to an ODUk/ODUj block, which is connected to an ODUk block. In Domain A2, an ODU SN is connected to an ODUk/ODUj block, which is connected to an ODUk block. A dashed line labeled 'ODUk trail' connects the ODUk block in Domain A1 to the ODUk block in Domain A2. Domain B contains two OTUk/ODUk blocks, each connected to an ODU SN. A dashed line labeled 'OTUj trail' connects the two OTUk/ODUk blocks. The ODUk block in Domain A1 is connected to the first OTUk/ODUk block in Domain B, and the ODUk block in Domain A2 is connected to the second OTUk/ODUk block in Domain B. The text 'G.872(17)\_FIV.1' is in the bottom right corner. + +Diagram of Multi-domain OTN scenario 1 showing three domains: Domain A1, Domain B, and Domain A2. Domain A1 and A2 are connected via Domain B. In Domain A1, an ODU SN is connected to an ODUk/ODUj block, which is connected to an ODUk block. In Domain A2, an ODU SN is connected to an ODUk/ODUj block, which is connected to an ODUk block. A dashed line labeled 'ODUk trail' connects the ODUk block in Domain A1 to the ODUk block in Domain A2. Domain B contains two OTUk/ODUk blocks, each connected to an ODU SN. A dashed line labeled 'OTUj trail' connects the two OTUk/ODUk blocks. The ODUk block in Domain A1 is connected to the first OTUk/ODUk block in Domain B, and the ODUk block in Domain A2 is connected to the second OTUk/ODUk block in Domain B. The text 'G.872(17)\_FIV.1' is in the bottom right corner. + +Figure IV.1 – Multi-domain OTN scenario 1 + +In scenario 2, shown in Figure IV.2, ODUk is carried by a higher rate ODU in domain B. + +![Figure IV.2 – Multi-domain OTN scenario 2. This diagram shows three domains: Domain A1, Domain A2, and Domain B. Domain A1 and A2 each contain an ODU SN, an ODUk/ODUj multiplexer, and an ODUk component. A dashed line labeled 'ODUk trail' connects the ODUk components in A1 and A2. Domain B contains two ODU SNs, two ODU/ODUk multiplexers, and two ODU components. A dashed line labeled 'ODU trail' connects the ODU components in Domain B. Solid lines connect the ODUk components in A1 and A2 to the ODU/ODUk multiplexers in Domain B. A label 'G.872(17)_FIV.2' is in the bottom right.](6cc85a2b62fd8a2a3faab29730f20e81_img.jpg) + +``` + +graph TD + subgraph Domain_A1 [Domain A1] + SN1((ODU SN)) --- AD1[ODUk/ODUj] + AD1 --- CP1(( )) + CP1 --- TT1[\ ODUk /] + end + + subgraph Domain_B [Domain B] + SNB1((ODU SN)) --- ADB1[ODU/ODUk] + ADB1 --- CPB1(( )) + CPB1 --- TTB1[\ ODU /] + + SNB2((ODU SN)) --- ADB2[ODU/ODUk] + ADB2 --- CPB2(( )) + CPB2 --- TTB2[\ ODU /] + + CPB1 -.-|ODU trail| CPB2 + end + + subgraph Domain_A2 [Domain A2] + SN2((ODU SN)) --- AD2[ODUk/ODUj] + AD2 --- CP2(( )) + CP2 --- TT2[\ ODUk /] + end + + TT1 --- ADB1 + ADB2 --- TT2 + CP1 -.-|ODUk trail| CP2 + +``` + +Figure IV.2 – Multi-domain OTN scenario 2. This diagram shows three domains: Domain A1, Domain A2, and Domain B. Domain A1 and A2 each contain an ODU SN, an ODUk/ODUj multiplexer, and an ODUk component. A dashed line labeled 'ODUk trail' connects the ODUk components in A1 and A2. Domain B contains two ODU SNs, two ODU/ODUk multiplexers, and two ODU components. A dashed line labeled 'ODU trail' connects the ODU components in Domain B. Solid lines connect the ODUk components in A1 and A2 to the ODU/ODUk multiplexers in Domain B. A label 'G.872(17)\_FIV.2' is in the bottom right. + +**Figure IV.2 – Multi-domain OTN scenario 2** + +Figure IV.3 illustrates scenario 2 with the addition of TCM in domain B. This allows carrier B to directly monitor the service being provided to carrier A. + +![Figure IV.3 – Multi-domain OTN scenario 3. This diagram is similar to Figure IV.2 but includes TCM in Domain B. Domain A1 and A2 remain the same. Domain B now features an 'ODUk TCM trail' (dashed line) that connects the entry and exit points of the service in Domain B. Below this, the 'ODU trail' (dashed line) connects the ODU components. The ODU SNs in Domain B are connected to the ODU/ODUk multiplexers, which are in turn connected to the ODU components. A label 'G.872(17)_FIV.3' is in the bottom right.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +``` + +graph TD + subgraph Domain_A1 [Domain A1] + SN1((ODU SN)) --- AD1[ODUk/ODUj] + AD1 --- CP1(( )) + CP1 --- TT1[\ ODUk /] + end + + subgraph Domain_B [Domain B] + CP_TCM1(( )) -.-|ODUk TCM trail| CP_TCM2(( )) + CP_TCM1 --- SNB1((ODU SN)) + CP_TCM2 --- SNB2((ODU SN)) + + SNB1 --- ADB1[ODU/ODUk] + ADB1 --- CPB1(( )) + CPB1 --- TTB1[\ ODU /] + + SNB2 --- ADB2[ODU/ODUk] + ADB2 --- CPB2(( )) + CPB2 --- TTB2[\ ODU /] + + CPB1 -.-|ODU trail| CPB2 + end + + subgraph Domain_A2 [Domain A2] + SN2((ODU SN)) --- AD2[ODUk/ODUj] + AD2 --- CP2(( )) + CP2 --- TT2[\ ODUk /] + end + + TT1 --- CP_TCM1 + CP_TCM2 --- TT2 + CP1 -.-|ODUk trail| CP2 + +``` + +Figure IV.3 – Multi-domain OTN scenario 3. This diagram is similar to Figure IV.2 but includes TCM in Domain B. Domain A1 and A2 remain the same. Domain B now features an 'ODUk TCM trail' (dashed line) that connects the entry and exit points of the service in Domain B. Below this, the 'ODU trail' (dashed line) connects the ODU components. The ODU SNs in Domain B are connected to the ODU/ODUk multiplexers, which are in turn connected to the ODU components. A label 'G.872(17)\_FIV.3' is in the bottom right. + +**Figure IV.3 – Multi-domain OTN scenario 3** + +# Bibliography + +- [b-OIF FlexE IA] Physical and Link Layer Working Group (2021). *Flex Ethernet 2.2 implementation agreement* (OIF-FLEXE-2.2). Fremont, CA: OIF. 61 pp. Available [viewed 2024-04-29] at: + + + + + +# 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.911-199704-I_PDF-E/raw.md b/marked/G/T-REC-G.911-199704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b34d9b2bbebd7a9fa893324bb5d5d97b24fe8e4d --- /dev/null +++ b/marked/G/T-REC-G.911-199704-I_PDF-E/raw.md @@ -0,0 +1,1268 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.911** + +(04/97) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital transmission systems – Digital sections and digital +line system – Parameters for optical fibre cable systems + +--- + +**Parameters and calculation methodologies for +reliability and availability of fibre optic systems** + +ITU-T Recommendation G.911 + +(Previously CCITT Recommendation) + +--- + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| INTERNATIONAL ANALOGUE CARRIER SYSTEM | | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 | +| DIGITAL TRANSMISSION SYSTEMS | | +| TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | +| 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.999 | + +For further details, please refer to ITU-T List of Recommendations. + +## **ITU-T RECOMMENDATION G.911** + +# **PARAMETERS AND CALCULATION METHODOLOGIES FOR RELIABILITY AND AVAILABILITY OF FIBRE OPTIC SYSTEMS** + +## **Summary** + +This Recommendation identifies a minimum set of parameters necessary to characterize the reliability and availability of fibre optic systems. Different parameters are given for system reliability and maintenance, for active optic device reliability, for passive optical device reliability, and for optical fibre and cable reliability. This Recommendation also provides guidelines and methods for calculating the predicted reliability of devices, units and systems. Examples are included. + +###### **Source** + +ITU-T Recommendation G.911 was revised by ITU-T Study Group 15 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 8th of April 1997. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1997 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +# CONTENTS + +| | | Page | +|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| 1 | Introduction..... | 1 | +| 2 | Parameters related to reliability and availability of fibre optic systems ..... | 1 | +| 2.1 | Fibre optic system availability and maintenance reliability-related parameters..... | 1 | +| 2.2 | Active optical device reliability parameters..... | 2 | +| 2.3 | Passive optical device reliability parameters ..... | 2 | +| 2.4 | Optical fibre and cable reliability parameters..... | 3 | +| 3 | Definitions ..... | 3 | +| 4 | Steady-state reliability prediction method of devices, units and fibre optic systems in serial configuration ..... | 5 | +| 4.1 | Purpose and scope..... | 5 | +| 4.2 | Applications of the predicted failure rate method..... | 5 | +| 4.2.1 | Equipment manufacturers/suppliers ..... | 6 | +| 4.2.2 | Equipment owners and network operators ..... | 6 | +| 4.3 | Guidelines ..... | 6 | +| 4.3.1 | Definition of failure ..... | 6 | +| 4.3.2 | Operating conditions..... | 6 | +| 4.3.3 | Environmental description..... | 6 | +| 4.3.4 | Adjusting the estimates given by this method ..... | 6 | +| 4.4 | Steady-state failure rate prediction method ..... | 7 | +| 4.4.1 | Applicability of the method..... | 7 | +| 4.4.2 | Device steady-state failure rate ( $\lambda_{si}$ ) ..... | 7 | +| 4.4.3 | Unit steady-state failure rate ( $\lambda_S$ )..... | 7 | +| 4.4.4 | Line system steady-state failure rate ( $\lambda_{sys}$ ) ..... | 7 | +| 5 | Calculation methodologies for fibre optic system devices, units and systems in serial configuration regarding reliability and maintenance parameters..... | 8 | +| 5.1 | Plug-in circuit pack MTBF ..... | 8 | +| 5.2 | System MTBF (terminal and repeater) ..... | 9 | +| 5.3 | Frequency of scheduled maintenance actions..... | 9 | +| 5.4 | Random failure rate..... | 9 | +| 5.5 | Infant mortality factor ..... | 10 | +| 6 | Calculation methodology of availability and maintenance parameters of fibre optic systems with line protection..... | 10 | +| 6.1 | General considerations – Line protection and network protection ..... | 10 | + +| | Page | | +|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 6.2 | State-space methodology to determine availability and maintenance parameters in fibre optic systems with line protection..... | 10 | +| 6.2.1 | Step 1 – Inputs ..... | 10 | +| 6.2.2 | Step 2 – From the above inputs determine ..... | 11 | +| 6.2.3 | Step 3 – Calculating system reliability-related measures..... | 14 | +| 6.3 | Options of fibre systems with line protection..... | 14 | +| 6.3.1 | One-for-one (1 + 1) link protection ..... | 14 | +| 6.3.2 | One-for- $N$ ( $N + 1$ ) link protection..... | 15 | +| 6.3.3 | Rings..... | 15 | +| 7 | Reference circuits for end-to-end channel availability of line systems on optical fibres ..... | 15 | +| 8 | Allocation methodology for end-to-end unavailability objectives..... | 17 | +| 8.1 | Contributors to unavailability – Considerations regarding SDH and PDH systems on optical fibres ..... | 17 | +| 8.2 | Allocation methodology..... | 17 | +| Appendix I | – Determination of unit steady-state failure rate – Example..... | 20 | +| I.1 | Unit description (example) ..... | 20 | +| I.2 | Reliability parameters of devices (example)..... | 20 | +| I.3 | Unit steady-state failure rate (FITs)..... | 20 | +| Appendix II | – Study case channel availability for a $4 \times 140$ Mbit/s repeater link on optical fibres with "3 + 1" line protection..... | 21 | +| II.1 | Description..... | 21 | +| II.2 | Results – Unavailability (minutes/year) per 140 Mbit/s channel..... | 22 | +| Appendix III | – Study case – Channel availability for a point-to-point fibre connection in the local network with "1 + 1" line protection, with and without cable-path redundancy | 23 | +| III.1 | Description..... | 23 | +| III.1.1 | Nature of the problem..... | 23 | +| III.1.2 | Type of connections..... | 24 | +| III.2 | Results..... | 26 | + +# PARAMETERS AND CALCULATION METHODOLOGIES FOR RELIABILITY AND AVAILABILITY OF FIBRE OPTIC SYSTEMS + +(revised in 1997) + +# 1 Introduction + +This Recommendation provides details of the parameters needed to characterize and the procedures to predict and calculate fibre optic system reliability, including reliability of the devices and availability of channels transmitted through the systems. The emphasis is on single-mode fibre systems (see Figure 1). + +![Flowchart showing the structure of Recommendation G.911. It starts with a base box 'Parameters, definitions and methodology to determine the failure rate of devices, units and fibre optic systems in serial configuration' (Clauses 2 to 4). This leads to two parallel paths. The left path goes through 'Methodology regarding reliability-related measures of elements and systems in serial configuration' (Clauses 4 and 5) to 'Results' (Failure rates, Mean time to repair) via 'Study case in Appendix I'. The right path goes through 'Methodology regarding reliability-related measures of fibre optic links with line protection' (Clause 6) to 'Results' (End-to-end channel/system availability, Frequency of repair actions, Cost of maintenance estimates) via 'Study cases in Appendices II and III'. Inputs to the right methodology box include 'Repair rates (input)' and 'Architecture and models of line protection (input)'.](d793cf7c174b89eb024d132f00679787_img.jpg) + +``` +graph TD; Base["Parameters, definitions and methodology to determine the failure rate of devices, units and fibre optic systems in serial configuration
Clauses 2 to 4"]; Base -- "Clauses 4 and 5" --> LeftMethod["Methodology regarding reliability-related measures of elements and systems in serial configuration"]; Base --> RightMethod["Methodology regarding reliability-related measures of fibre optic links with line protection
Clause 6"]; Input["Repair rates (input)
Architecture and models of line protection (input)"] --> RightMethod; LeftMethod -- "Study case in Appendix I" --> LeftResults["Results
- Failure rates
- Mean time to repair"]; RightMethod -- "Study cases in Appendices II and III" --> RightResults["Results
- End-to-end channel/system availability
- Frequency of repair actions
- Cost of maintenance estimates"]; +``` + +T1506460-90 + +Flowchart showing the structure of Recommendation G.911. It starts with a base box 'Parameters, definitions and methodology to determine the failure rate of devices, units and fibre optic systems in serial configuration' (Clauses 2 to 4). This leads to two parallel paths. The left path goes through 'Methodology regarding reliability-related measures of elements and systems in serial configuration' (Clauses 4 and 5) to 'Results' (Failure rates, Mean time to repair) via 'Study case in Appendix I'. The right path goes through 'Methodology regarding reliability-related measures of fibre optic links with line protection' (Clause 6) to 'Results' (End-to-end channel/system availability, Frequency of repair actions, Cost of maintenance estimates) via 'Study cases in Appendices II and III'. Inputs to the right methodology box include 'Repair rates (input)' and 'Architecture and models of line protection (input)'. + +Figure 1/G.911 – How to use Recommendation G.911 + +# 2 Parameters related to reliability and availability of fibre optic systems + +## 2.1 Fibre optic system availability and maintenance reliability-related parameters + +This subclause gives the system service parameters and system maintenance parameters. The values may be provided in study cases and are for further study. It is anticipated, however, that different + +parameters/values may be required for the various system applications, including point-to-point long/medium distance, local networks, etc. (see Tables 1 and 2). + +**Table 1/G.911** + +| System service parameter | Units | +|---------------------------------------------------------------------|-----------------------------------| +| Mean system availability a) | Min/yr unavailability | +| Mean channel availability | Min/yr unavailability per channel | +| Operation system interface availability | Min/yr unavailability | +| a) In order to estimate the quantity of spares required. | | + +**Table 2/G.911** + +| System service parameter | Units | +|---------------------------------------------------------------------|-----------------| +| System MTBF (such as terminals, repeaters and media) | Years | +| Plug-in circuit pack MTBF a) | Years | +| Frequency of scheduled maintenance actions | Events per year | +| Random failure rate | Events per year | +| Infant mortality factor | Dimensionless | +| MTBF ( mean time between failures ) | | +| a) In order to estimate the quantity of spares required. | | + +### 2.2 Active optical device reliability parameters + +This subclause includes reliability parameters for characterizing active fibre optic devices such as lasers, LEDs and detectors. The values may be provided in study cases and are for further study (see Table 3). + +**Table 3/G.911** + +| Active optical device reliability parameter | Units | +|------------------------------------------------------|-------| +| Median Life (ML) | Years | +| Standard deviation ( $\sigma$ ) | | +| Wear-out failure rate at 10 years ( $\lambda_{10}$ ) | FITs | +| Wear-out failure rate at 20 years ( $\lambda_{20}$ ) | FITs | +| Wear-out activation energy ( $E_n$ ) | eV | +| Random (steady-state) failure rate ( $\lambda_r$ ) | FITs | +| Random failure activation energy ( $E_n$ ) | eV | + +### 2.3 Passive optical device reliability parameters + +This subclause includes the necessary reliability parameters for characterizing passive fibre optic devices such as connectors, splices and splitters. Identification of the parameters and their values are for further study (see Table 4). + +**Table 4/G.911** + +| Passive optical device reliability parameter | Units | +|-----------------------------------------------------|--------------| +| | | + +## 2.4 Optical fibre and cable reliability parameters + +This subclause includes the necessary reliability parameters for characterizing installed optical fibres and cables. These parameters distinguish extrinsic failure modes and intrinsic failure modes. Extrinsic failure modes, such as cable dig-ups or installation/maintenance errors, dominate the overall reliability. Intrinsic modes, such as fibre fatigue or cable degradation, are typically only a small fraction of total reliability. Clarification of these modes, extrinsic versus intrinsic, in actual cases is under study. Assessment or prediction methods are also under study (see Table 5). + +**Table 5/G.911** + +| Optical fibre and cable reliability parameter | Units | +|------------------------------------------------------|---------------| +| Extrinsic mode failure rate | FITs/cable-km | +| Intrinsic mode cable failure rate | FITs/cable-km | +| Intrinsic mode fibre failure rate | FITs/fibre-km | + +# 3 Definitions + +This clause includes definitions for the reliability parameters for characterizing fibre optic systems and device reliability. + +**3.1 item; entity** (such as a system or a channel): Any part, device, sub-system, functional unit, equipment or system that can be individually considered. + +**3.2 constant failure rate period:** That possible period in the life of a non-repaired item during which the failure rate is approximately constant. + +NOTE – In any particular case it is necessary to explain what is meant "by approximately constant". + +**3.3 availability performance:** The ability of an item to be in a state to perform a required function at a given instant of time or at any instant of time within a given time interval, assuming that the external resources, if required, are provided. + +NOTE 1 – This ability depends on the combined aspects of the reliability performance, the maintainability performance and the maintenance support performance of an item. + +NOTE 2 – In the definition of the item, the external resources required must be delineated. + +NOTE 3 – The term availability is used as an availability performance measure. + +**3.4 instantaneous availability:** The probability that an item is in an up-state at a given instant of time, $t$ . + +**3.5 mean availability:** The normalized integral of the instantaneous availability in a given time interval $(t_1, t_2)$ . + +**3.6 mean time between failures (MTBF):** The expectation of the time between failures. + +**3.7 early failure period (infant mortality):** That possible early period in the life of an item, beginning at a given instant of time and during which the instantaneous failure intensity for a repaired item or the instantaneous failure rate for a non-repaired item decreases rapidly. + +NOTE – In any particular case, it is necessary to explain what is meant by "decreases rapidly". + +**3.8 infant mortality factor (IMF):** Ratio of the expected number of failures in a specific early period (e.g. the first year) of service to the expected number of failures in a period of the same length of time in steady-state operation (before wear out). + +**3.9 median life (ML):** With respect to optoelectronic devices, the median life refers to the point, on a lognormal probability plot of device times-to-failure at which 50% of the devices fail earlier and 50% of the devices fail later. + +**3.10 standard deviation ( $\sigma$ ):** With respect to optoelectronic devices, the standard deviation refers to the normal mathematical expression for this statistic as calculated from the natural logarithms of the device times-to-failure. + +**3.11 wear-out failure period:** That possible later period in the life of a repaired item during which the instantaneous failure intensity for a repaired item or the instantaneous failure rate for a non-repaired item increases rapidly. + +NOTE – In any particular case, it is necessary to explain what is meant by "increases rapidly". + +**3.12 wear-out failure rate:** The wear-out failure rate is a measure of the number of items that fail per unit time due to wear-out mechanisms. It is not calculated directly for optoelectronic devices, but is obtained from the statistical expectation for a lognormal distribution for which the median life and standard deviation have been estimated. + +**3.13 wear-out failures:** A failure whose probability of occurrence increases with the passage of time, as a result of processes inherent in the item. + +**3.14 activation energy ( $E_a$ ):** The minimum centre-of-mass kinetic energy required before a chemical reaction can occur. Normally expressed in units of electron volts (eV). Used as a part of the early life Arrhenius acceleration factor. + +**3.15 Arrhenius acceleration factor:** An expression detailing the relationship between failure times at two different temperatures. + +$$\frac{t_1}{t_2} = e^{\frac{E_0}{k} \left( \frac{1}{T_1} - \frac{1}{T_2} \right)}$$ + +where: + +$t_{1,2}$ is the time to failure, + +$E_0$ is the activation energy in electron volts (eV), + +$k$ Boltzman constant, $8.6 \times 10^{-5}$ eV/K, + +$T_{1,2}$ is the absolute temperature, K. + +**3.16 random failure rate:** The random failure rate is a measure of the number of units that fail per unit time due to a variety of fabrication or (more often) assembly defects not associated with the usual wear-out mechanism(s). A common assumption for optoelectronic devices is that the collection of random failure mechanisms can be roughly modelled by an exponential distribution. In that case, the failure rate is not obtained directly from the data, but is obtained from the (one-sided) statistical expectation for an exponential distribution for a given level of confidence (e.g. a 60% confidence limit). + +**3.17 maintenance time:** The time interval during which a maintenance action is performed on an item either manually or automatically, including technical delays and logistic delays. + +**3.18 mean time to repair (MTTR):** The total corrective maintenance time divided by the total number of corrective maintenance actions during a given period of time. + +**3.19 frequency of maintenance actions:** The inverse of the mean time interval between the starts of successive maintenance actions over a given time period (in events per a given period of time). + +**3.20 FITs (failures in time):** Normally expressed as failures per billion device hours. + +**3.21 steady-state availability:** The steady-state availability is the limit of $A(t)$ when $t$ goes to infinity. Being $A(t)$ the probability that the item is operating at a specified time $t$ and is given by: + +$$A(t) = \text{Probability } (X(t) = 1)$$ + +where: + +$X(t)$ denotes the state at time $t$ of a system undergoing maintenance. If the system is operating at time $t$ then $X(t) = 1$ , if not, then $X(t) = 0$ . + +# **4 Steady-state reliability prediction method of devices, units and fibre optic systems in serial configuration** + +## **4.1 Purpose and scope** + +As used here, reliability is a measure of the frequency of equipment failure as a function of time. Reliability has impact on maintenance cost and on the continuity of service. Reliability predictions can be used to assist in deciding which product from a list of competing products should be purchased. As a result, it is essential that reliability predictions from competing products be based on common procedures (see Note 1). + +The purpose of this procedure for reliability prediction is to recommend a common procedure for reliability prediction. The method is intended to be applicable to electronic units/systems, in general, and for those units/systems to be used with fibre cables in particular. + +This reliability prediction method is based in a failure-rate "parts count" approach (see Note 2). + +NOTE 1 – It is important to recognize that failure rates of component parts may be based on standards that may be different from one manufacturer to another (such discrepancies can arise from differences in generic failure rates and other factors related to environment, stress, quality, etc.). + +NOTE 2 – Other methods exist for reliability prediction purposes, including: + +- statistical estimates based upon combining data from a laboratory test with predictions from the "parts count" method; +- statistical estimates of in-service reliability based upon field tracking studies. + +The scope is limited to hardware-related failures under steady-state conditions. The infant mortality factor prediction method is for further study. Complex systems with reliability objectives for individual functions or for various states of reduced service capability are outside the scope of this Recommendation. + +## **4.2 Applications of the predicted failure rate method** + +It may be used in the following situations. + +### **4.2.1 Equipment manufacturers/suppliers** + +The method contains instructions for product suppliers to follow when providing predictions of their product's reliability. + +The supplier may employ another method (see above) for reliability prediction of devices, units and systems in serial configuration; however, the parts-count is also needed as reference method. + +### **4.2.2 Equipment owners and network operators** + +It can be used by equipment owners and/or network operators to perform the following tasks: + +- a) To request and evaluate the reliability of products to be purchased. Reliability predictions provide data for life cycle cost analysis. +- b) To measure service-affecting parameters related to the product reliability. + +By combining reliability predictions with maintenance parameters (such as mean time to repair), the following service-affecting parameters can be calculated: + +- frequency of outages in steady-state; + - frequency of maintenance actions; + - expected value of the downtime per year. +- c) To provide a measure of line system reliability as it affects maintenance activity. For example, predictions of the frequency of maintenance and/or repair actions can be obtained. + +## **4.3 Guidelines** + +### **4.3.1 Definition of failure** + +The definition of failures should be made specific. The definition of failure is a critical element in predicting system reliability. For simple equipment the definition of failure is usually clear. + +Faults in complex equipment (as could be the case of line system in fibre cables) may distinguish between those affecting maintenance or repair and those affecting service (e.g. "major fault" $\text{BER} > 10^{-4}$ ). + +### **4.3.2 Operating conditions** + +The physical environment in which the units/systems will be used should be described, including: + +- temperature and humidity, and their variations; +- single or redundant line facility; +- commercial power outages; +- EMI, lightning. + +### **4.3.3 Environmental description** + +Failure rates vary as a function of the intended operating environment. The appropriate environmental failure rate multiplication factor(s) should be specified. If the overall system will be exposed to more than one environment, each factor should be specified as appropriate. + +### **4.3.4 Adjusting the estimates given by this method** + +Although the method specified here is intended to be the reference one, this does not preclude use of other technically-sound sources of data and/or technically-sound engineering techniques in estimating device, unit or system failure rate. This could include (as mentioned above) device manufacturer's data, unit supplier data, reliability physics considerations and engineering analysis. + +This adjusting of the estimates given by the reference method may be particularly useful for new technology devices where no substantial field data may exist. + +## 4.4 Steady-state failure rate prediction method + +### 4.4.1 Applicability of the method + +This method applies whenever the supplier wishes to take advantage of device or unit burn-in. + +The failure intensity corresponding to failures affecting maintenance represents the quantity of repairs to be made per unit of time, and is equal to the sum of the failure rates of all the devices building the considered item. + +For non-redundant items, the failure intensity corresponding to failures affecting service represents the quantity of service impairments per unit of time, and is equal to the sum of the failure rates of the devices whose failure affect the service. + +For redundant items, the methods for deriving the service affecting failure intensity depends on the type of redundancy as well as on the way the redundancy is implemented. + +### 4.4.2 Device steady-state failure rate ( $\lambda_{si}$ ) + +For this general situation the steady-state failure rate is given by: + +$$\lambda_{si} = N_i \mu_{gi} \pi_{qi} \pi_{si} \pi_{ti}$$ + +where: + +- $N_i$ is the quantity of $i$ th device; +- $\mu_{gi}$ is the generic failure rate for the $i$ th device; +- $\pi_{qi}$ is the quality factor for the $i$ th device (see Note); +- $\pi_{si}$ is the stress factor for the $i$ th device (see Note); +- $\pi_{ti}$ is the temperature factor for the $i$ th device due to normal operating temperature during steady-state. A distinction must be made between environment temperature and intrinsic temperature of the device/unit. + +NOTE – Those factors may be different by each network operator standard or manufactures standard. + +### 4.4.3 Unit steady-state failure rate ( $\lambda_s$ ) + +The unit steady-state failure rate is the sum of the device steady-state failure rates: + +$$\lambda_s = \pi_e \sum_{i=1}^{i=N} \lambda_{si}$$ + +where: + +- $N$ is the number of different $N_i$ devices in the unit; +- $\pi_e$ is the environmental failure rate multiplicative factor. + +NOTE – An example is given in Appendix I. + +### 4.4.4 Line system steady-state failure rate ( $\lambda_{sys}$ ) + +If the specified reliability parameters failure criteria, equipment configuration and operating conditions indicate that a serial reliability model is appropriate, the total system failure rate ( $\lambda_{sys}$ ) will be the sum of all of the unit steady-state failure rates ( $\lambda_s$ ) that is: (see Note 2) + +$$\lambda_{sys} = \sum_{j=1}^{J=M} \lambda_s(j)$$ + +where: + +$\lambda_s(j)$ is the unit steady-state failure rate for unit $j$ ; + +$M$ is the number of units. + +NOTE 1 – Unit steady-state failure rates are assumed to reflect only service affecting failures. + +NOTE 2 – In the case of redundant systems, redundant equipment and/or unit/panel constitution, the sum of all of the failure rates ( $\lambda_s$ ) is not appropriate in terms of total system reliability. The production method to be used in such situations is under study. + +# 5 Calculation methodologies for fibre optic system devices, units and systems in serial configuration regarding reliability and maintenance parameters + +## 5.1 Plug-in circuit pack MTBF + +The Mean Time Between Failures (MTBF) is the steady-state expectation of the time between failures. Mathematically, the MTBF (in years per failure) is related to the failure rate (in FITs or failures per $10^9$ hours) as follows: + +$$M = \frac{(1.14 \cdot 10^5)}{F}$$ + +where $M$ is the MTBF (in years per failure) and $F$ is the failure rate (in FITs). + +The plug-in circuit pack MTBF is calculated by summing the failure rate for each of the elements that comprise the circuit pack. For example, Table 6 shows the calculation for a circuit pack having one packaged laser with a failure rate of 1500 FITs, five integrated circuits each with a failure rate of 300 FITs, four resistors each with a failure rate of 123 FITs, seven capacitors each with a failure rate of 57 FITs and a connector and printed wiring board, each with a failure rate of 27 FITs. + +The unit FIT rates for the elements comprising the circuit pack can be calculated in a number of ways. The calculation methodology shall be detailed when reporting plug-in circuit pack MTBF. + +**Table 6/G.911 – Example of plug-in circuit pack MTBF calculation** + +| Device type | Quantity | Unit FIT rate | Total FITs | +|------------------------------------------------------------|----------|---------------|------------| +| Packaged laser | 1 | 1500 | 1500 | +| Integrated circuits | 5 | 300 | 1500 | +| Resistors | 4 | 123 | 492 | +| Capacitor | 7 | 57 | 399 | +| Connector | 1 | 27 | 27 | +| PWB | 1 | 27 | 27 | +| Total | | | 3945 | +| $MTBF = \frac{1.14 \cdot 10^5}{3945} = 28.9 \text{ years}$ | | | | + +## 5.2 System MTBF (terminal and repeater) + +The Mean Time Between Failures (MTBF) is the steady-state expectation of the time between failures. Mathematically, the MTBF (in years per failure) is related to the failure rate (in FITs or failures per $10^9$ hours) as follows: + +$$M = \frac{(1.14 \cdot 10^5)}{F}$$ + +where $M$ is the MTBF (in years per failure) and $F$ is the failure rate (in FITs). + +The system MTBF is calculated by summing the failure rate for each of the plug-in circuit packs (and other equipment that is not on plug-in circuit packs) that comprise the system. For example, Table 7 shows the calculation for a system having five channel packs each with a failure rate of 8000 FITs, four power supplies each with a failure rate of 6500 FITs, four regenerators each with a failure rate of 12 050 FITs, a microprocessor board with a failure rate of 12 300 FITs and a monitor board with a failure rate of 3400 FITs. + +**Table 7/G.911 – Example of system MTBF calculation** + +| Device type | Quantity | Unit FIT rate | Total FITs | +|--------------------------------------------------------------------------------|----------|---------------|------------| +| Channel pack | 5 | 8 000 | 40 000 | +| Power supply | 4 | 6 500 | 26 000 | +| Regenerator | 4 | 12 050 | 48 200 | +| Microprocessor board | 1 | 12 300 | 12 300 | +| Monitor board | 1 | 3 400 | 3 400 | +| Total | | | 129 900 | +| $\text{MTBF} = \frac{1.14 \cdot 10^5}{1.299 \cdot 10^5} = 0.878 \text{ years}$ | | | | + +## 5.3 Frequency of scheduled maintenance actions + +The frequency of scheduled maintenance actions is the mean time interval between the starts of successive scheduled preventive maintenance actions. It is determined by calculating the interval between successive scheduled maintenance actions. For example, if a fibre optic system supplier requires scheduled maintenance actions to occur every six months, the frequency of maintenance actions would be two events per year. + +## 5.4 Random failure rate + +The random failure rate is a measure of the number of units that fail per unit time due to a variety of fabrication or (more often) assembly defects not associated with the usual wear-out mechanism(s). The system random failure rate is determined by summing the random failure rate for each of the elements that comprise the system including service affecting failures, non-service affecting failures and all scheduled and unscheduled maintenance actions. The random failure rates for the elements comprising the system can be calculated in a number of ways. The calculation methodology shall be detailed when reporting system random failure rates. + +## **5.5 Infant mortality factor** + +The Infant Mortality Factor (IMF) is the ratio of the expected number of failures in the first period of service to the expected number of failures in a steady-state year. It is calculated based on two parameters. The expected number of failures in the first period is calculated by determining the area under the Weibull infant mortality curve over a first time period beginning with the time service is first applied by the customer. The Weibull curve is determined based on the sum of those curves for the elements in the system. The expected number of failures during a steady-state year is calculated by determining the random failure rate and converting to failures per year. + +# **6 Calculation methodology of availability and maintenance parameters of fibre optic systems with line protection** + +## **6.1 General considerations – Line protection and network protection** + +Protection in telecommunication transmission is largely concerned with providing degrees of redundancy to increase the overall availability of end-to-end customer circuits. This is necessary because the net availability performance obtained by cascading large numbers of network elements is incompatible with the expectations of many customers. + +The goal of a redundant network is a high level of circuit availability as perceived by the customer, but this, of course, can only be achieved at some cost to the operator. In simplest terms this extra cost is due to the increased hardware needed to provide standby circuits through the network. However two other important cost factors must be allowed for, namely the cost of control mechanisms (e.g. software) used to ensure that failed circuits are restored and the cost of extra maintenance staff needed to repair the additional faulty equipment resulting from the increase in network hardware. + +Protection methods in telecommunication may be categorized in terms of path availability, response time and complexity. Generally fast, simple methods such as "N + 1" link protection have been preferred since they reduce unavailability by about one order of magnitude, compared with unprotected systems (see Appendixes II and III), at minimal additional cost. Also link protection systems may be readily automated to give further significant improvements with minimal hardware for protection switches, signalling and control. Ring protection is a special case of "1 + 1" protection where traffic may be routed in both directions around the ring. + +More complex protection schemes involve networking, either by simple triangularization (using a fixed set of pre-programmed make-good paths), or global re-routing, that requires a full knowledge of the network for the by-pass of failed equipment. Both link and network protection are applicable to meshed networks but require complex signalling and control software. However, the apparent improvement in circuit availability offered by networking may be offset by the additional complexity of software and vulnerability under catastrophic situations (natural or man-made). + +## **6.2 State-space methodology to determine availability and maintenance parameters in fibre optic systems with line protection** + +The methodology is further illustrated through samples of Appendixes II and III. The method is composed of three steps which are described below: + +### **6.2.1 Step 1 – Inputs** + +Step 1 deals with the information needed to work out the other steps. That information includes: + +- a) random (steady state) failure rates of the various devices/network elements; +- b) repair rates based on MTTRs of the various elements and sub-systems; + +- c) architectural configuration of the line protection scheme. + +### 6.2.2 Step 2 – From the above inputs determine + +- d) *The set of states* + +A mathematically tractable probability model that can account for many simultaneously-active events processed in a complex system is a continuous-time, homogeneous Markov chain. What follows deals with such Markov approach. + +Each state corresponds to a specific condition of the system, for example: "component A is failed", "failure detected", "loss of redundancy", "repair in progress", and "system failed". + +- e) *Breaking state-transition diagram* + +Systems are frequently first described by reliability block diagrams that define what combinations of system elements are needed to provide a system function. For example, Figure 2 shows a parallel system with two components ( $\lambda_A$ and $\lambda_B$ ) which are the components failure rates. Transition paths depicting repair are left for simplicity in Figure 2. + +A bar on the top of the component means that such component is failed. The states $\bar{A}$ , B and A, $\bar{B}$ mean a component has failed but the system still works. The state $\bar{A}$ , $\bar{B}$ is a system failed state. The equivalent summary Markov model merges the two failed-component states, but the identity of the failure causing component is lost. + +A practical system may have $K$ sub-systems and each sub-system has $m$ replaceable or on-site variable components, where $K$ is typically 1, 2 or 3 and $m$ ranges from a few upwards to one hundred. The detailed Markov model would have $2^{K \times m}$ states, not counting any intermediate states added to model detection, maintenance and repair. This state-space explosion is typically contained by truncation of the Markov model to represent no more than $K$ concurrent failures, and only those combinations of component failure-causing system failure. When component failure rates are orders of magnitude smaller than component failure detection, failure recovery and repair rates, the truncation usually has negligible effect on the accuracy of the model for predicting measures of system reliability. + +If a system can suffer two or more concurrent component failures, the repair can occur simultaneously (simultaneous repair). Figure 3 depicts Markov model in the above system [Figure 2 when it is assumed that repairs can be concurrent (this strategy is in fact applicable to fibre optic transmission systems)]. + +![Reliability block diagram showing two components, A and B, in a parallel configuration. Component A has a failure rate λ_A and component B has a failure rate λ_B.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +Reliability block diagram showing two components, A and B, in a parallel configuration. Component A has a failure rate λ\_A and component B has a failure rate λ\_B. + +![Detail Markov model diagram showing four states: AB (both working), A-bar B (A failed, B working), A B-bar (A working, B failed), and A-bar B-bar (both failed). Transitions are labeled with failure rates λ_A and λ_B.](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg) + +``` + + graph TD + AB((AB)) -- λ_A --> ABarB((A-bar B)) + AB -- λ_B --> ABarB((A B-bar)) + ABarB -- λ_B --> ABarBBar((A-bar B-bar)) + ABarB -- λ_A --> ABarBBar + +``` + +Detail Markov model diagram showing four states: AB (both working), A-bar B (A failed, B working), A B-bar (A working, B failed), and A-bar B-bar (both failed). Transitions are labeled with failure rates λ\_A and λ\_B. + +Detail Markov model + +![Summary Markov model diagram showing three states: 0 (both working), 1 (one failed), and 2 (both failed). Transitions are labeled with λ_A = λ_B, 2λ, and λ.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + + graph TD + 0((0)) -- "λ_A = λ_B" --> 1((1)) + 1 -- λ --> 2((2)) + +``` + +Summary Markov model diagram showing three states: 0 (both working), 1 (one failed), and 2 (both failed). Transitions are labeled with λ\_A = λ\_B, 2λ, and λ. + +T1506470-90 + +Summary Markov model + +**Figure 2/G.911 – Examples of reliability block diagrams** + +![Figure 3/G.911 – Description of Markov model. The diagram shows a system with two components, A and B, in parallel. Above them is a schematic showing A and B in parallel between two nodes, with failure rates λ_A and λ_B. Below are two Markov models. The 'Detail Markov model' on the left has four states: 'A B' (top), 'A-bar B' (left), 'A B-bar' (right), and 'A-bar B-bar' (bottom). Transitions are labeled with failure rates λ and repair rates μ. The 'Summary Markov model' on the right has three states: '0' (top), '1' (middle), and '2' (bottom). Transitions are labeled with 2λ, μ, λ, and 2μ. Above the summary model are the constraints λ_A = λ_B and μ_A = μ_B. A note at the bottom right of the summary model reads 'T1506480-90'.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +Detail Markov model with failure and repair paths + +Summary Markov model with failure and repair paths + +Figure 3/G.911 – Description of Markov model. The diagram shows a system with two components, A and B, in parallel. Above them is a schematic showing A and B in parallel between two nodes, with failure rates λ\_A and λ\_B. Below are two Markov models. The 'Detail Markov model' on the left has four states: 'A B' (top), 'A-bar B' (left), 'A B-bar' (right), and 'A-bar B-bar' (bottom). Transitions are labeled with failure rates λ and repair rates μ. The 'Summary Markov model' on the right has three states: '0' (top), '1' (middle), and '2' (bottom). Transitions are labeled with 2λ, μ, λ, and 2μ. Above the summary model are the constraints λ\_A = λ\_B and μ\_A = μ\_B. A note at the bottom right of the summary model reads 'T1506480-90'. + +NOTE – $\lambda$ stands for failure rates, and $\mu$ for repair rates. + +**Figure 3/G.911 – Description of Markov model** + +f) *The probabilities and the frequencies of the various states* + +The limiting state probability of state "j" (the long run proposition of time the system spends in state "j") of a Markov model is given by: + +$$P_j = \lim_{t \rightarrow \infty} t^{-1} [\text{Total time spent in state "j" during } (0, t)].$$ + +The $P_j$ s factors of a Markov model are calculated using the steady-state equilibrium principle illustrated in Figure 4. As elapsed time grows indefinitely large, an $L$ -state Markov model reaches a condition of equilibrium in which a set of $L$ simultaneous linear equations, one for each state as shown in Figure 4, hold. If the constrain $P_1 + P_2 + \dots + P_L = 1$ is added to the set, then $P_j$ s can be calculated. However, care must be taken to avoid round-off problems when there are differences among the transition rates of several orders of magnitude. + +Once the $P_j$ s are calculated, the limiting (long-run) frequency of each state "j" in a Markov model can be found using the relationship: + +$$F_j = \lim_{t \rightarrow \infty} t^{-1} [\text{Number of visits to state "j" during } (0, t)] \\ = (\theta_1 + \theta_2 + \dots + \theta_m) P_j.$$ + +![Diagram illustrating the steady-state equilibrium principle for Markov models. A central state 'J' is shown with incoming arrows from states 1, 2, ..., H, labeled with rates λ1, λ2, ..., λH. Outgoing arrows from state 'J' lead to states 1, 2, ..., m, labeled with rates θ1, θ2, ..., θm. The diagram is labeled 'L-state model' and 'T1506490-90'. Below the diagram, the flow in and flow out are given as: Flow in = (λ1 · P1 + λ2 · P2 + ... + λH · PH) / Pj; Flow out = (θ1 + θ2 + ... + θm) Pj.](83852ec55d4802521a727926336bedab_img.jpg) + +$$\frac{\lambda_1 \cdot P_1 + \lambda_2 \cdot P_2 + \dots + \lambda_H \cdot P_H}{P_j} \quad \frac{(\theta_1 + \theta_2 + \dots + \theta_m) P_j}{P_j}$$ + Flow in                      Flow out + +Diagram illustrating the steady-state equilibrium principle for Markov models. A central state 'J' is shown with incoming arrows from states 1, 2, ..., H, labeled with rates λ1, λ2, ..., λH. Outgoing arrows from state 'J' lead to states 1, 2, ..., m, labeled with rates θ1, θ2, ..., θm. The diagram is labeled 'L-state model' and 'T1506490-90'. Below the diagram, the flow in and flow out are given as: Flow in = (λ1 · P1 + λ2 · P2 + ... + λH · PH) / Pj; Flow out = (θ1 + θ2 + ... + θm) Pj. + +**Figure 4/G.911 – The steady-state equilibrium principle for Markov models** + +### 6.2.3 Step 3 – Calculating system reliability-related measures + +Once the probabilities and frequencies of the states are calculated, many useful measures of system availability and maintainability can be obtained, with the help of the following expression: + +$$\text{reliability-related measures} = \sum_j (a_j \times F_j + b_j \times P_j)$$ + +- g) *Unavailability*: $b_j = 1$ if state "j" is a system failed state, 0 otherwise; $a_j = 0$ . +- h) *Frequency of system failure*: $a_j = 1$ if state "j" is a system- failed state, 0 otherwise; $b_j = 0$ . +- i) *Downtime per unit time per channel (customer)*: $a_j = 0$ ; $b_j = N_j/N$ where $N_j$ is number of customers (channels) without service in state "j", $N$ is the total number of customers (channels). +- j) *Maintenance cost per unit time*: $a_j =$ set-up cost for maintenance activity begun in state "j"; $b_j =$ cost per unit time of maintenance activity in state "j". + +## 6.3 Options of fibre systems with line protection + +### 6.3.1 One-for-one (1 + 1) link protection + +This method of protecting a path is simple to provide, control and understand and consequently is widely used. + +In its simplest form the traffic from the source is transmitted simultaneously over both bearers and the decision to switch between main and standby is taken at the receiving location; in this situation only "loss of signal" or similar indications are required to initiate changeover and no command and control information need to be passed between the two sites. After the failed main bearer is repaired and made available for service it is re-designated as the new "standby". In this way a fault only + +causes one interruption to customer service and the process of restoration does not introduce a second break. + +One-for-one protection gives its best performance if the main and standby routes are completely separated thereby minimizing the risk of common mode failures (see Appendix III). Because of the simplicity of this protection technique it can ensure the fastest make-good time with the least need for sophisticated monitoring and control equipment. + +On the down-side, one-for-one protection is a very inefficient use of network equipment since 50% is always in a standby mode waiting to be used. + +### 6.3.2 One-for- $N$ ( $N + 1$ ) link protection + +This protection technique is an extension of the above technique and addresses the question of inefficient usage of standby equipment. Working on the premise that the failure rate of a route is low enough to ensure that simultaneous failure of two or more routes in a group of $N$ is still highly unlikely, it is possible to share the standby route amongst $N$ working routes (see Appendix II). + +Compared with one-for-one protection this method makes a more cost-effective use of equipment but requires slightly more sophisticated control and cannot offer the same level of availability. Diverse routing of main and standby paths is also much harder to achieve. + +### 6.3.3 Rings + +Ring architectures are sometimes considered to be a class of their own but conceptually the protection offered by a ring can be analysed in terms of one-for-one protection. Whereas one-for-one protection does not immediately imply complete physical diversity between main and standby routes, a ring is usually understood to offer two separate directions of communication. + +There are a variety of ring structures each with a range of control/management strategies capable of ensuring autonomous self-healing operation. + +The principal advantage of rings is in their flexibility for providing bandwidth at any node on the ring in response to unforeseen demand, thereby overcoming some of the rigid planning rules associated with simpler point-to-point links. + +# 7 Reference circuits for end-to-end channel availability of line systems on optical fibres + +A distinction needs to be made between line systems based on the plesiochronous (PDH) and the synchronous (SDH) digital hierarchy standards. SDH equipments provide new flexibility which affects objectives and modelling methods because: + +- SDH systems may have multiple channel interfaces (e.g. 1.5 Mbit/s, 2 Mbit/s, ..., 155 Mbit/s), compared with only one interface per PDH line system. +- SDH products may merge several functions, including digital cross connecting, Add/dropping, and transport into the same SDH network element. On the other hand, digital cross-connect systems and add/drop systems are separate from PDH line terminal. + +Therefore, in a SDH-based reference circuit there is no need to allocate unavailability for multiplexing equipments. + +The proposed Reference Circuits (RCs) for end-to-end availability allocation of line systems on optical fibres are shown in diagrams a) and b) of Figure 5. They are applicable to interoffice applications. Concrete numbers for the end-to-end availability may be included into Appendices I, II and III. + +The RCs are generic enough to enable a number of repeaters and intermediate offices to be included between end offices. For a given RC length, however, the same unavailability per channel (minutes/year) is recommended for SDH and PDH reference circuits because: + +- 1) to allow for a gradual introduction of SDH equipment into a PDH-based network; and +- 2) to assure that the SDH network availability objectives are consistent with the existing PDH network availability objectives. + +![Diagram (a) showing a reference circuit for end-to-end channel unavailability in PDH systems in optical fibres. It consists of two 'Office' blocks connected by a series of repeaters (R) via optical fibres. The left Office contains MUX (PDH), DCC, and LT. The right Office contains LT, DCC, and MUX (PDH). The total length is L (km). The end-to-end channel unavailability is T minutes/year. Channel interfaces are shown at the far ends.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) + +Diagram (a) illustrates a reference circuit for end-to-end channel unavailability in PDH systems in optical fibres. It shows two 'Office' blocks at the ends, each containing a MUX (PDH), DCC, and LT. These are connected by a series of repeaters (R) via optical fibres. The total length of the circuit is labeled $L$ (km). The end-to-end channel unavailability is indicated as $T$ minutes/year. Channel interfaces are shown at the far ends of the circuit. + +Diagram (a) showing a reference circuit for end-to-end channel unavailability in PDH systems in optical fibres. It consists of two 'Office' blocks connected by a series of repeaters (R) via optical fibres. The left Office contains MUX (PDH), DCC, and LT. The right Office contains LT, DCC, and MUX (PDH). The total length is L (km). The end-to-end channel unavailability is T minutes/year. Channel interfaces are shown at the far ends. + +a) Reference circuit for end-to-end channel unavailability in PDH systems in optical fibres + +![Diagram (b) showing a reference circuit for end-to-end channel(s) unavailability in SDH systems. It consists of two 'Office' blocks connected by a series of repeaters (R) via optical fibres. The left Office contains a Network element (SDH). The right Office contains a Network element (SDH). The total length is L (km). The end-to-end channel(s) unavailability is T minutes/year. Channel interfaces are shown at the far ends.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +Diagram (b) illustrates a reference circuit for end-to-end channel(s) unavailability in SDH systems. It shows two 'Office' blocks at the ends, each containing a Network element (SDH). These are connected by a series of repeaters (R) via optical fibres. The total length of the circuit is labeled $L$ (km). The end-to-end channel(s) unavailability is indicated as $T$ minutes/year. Channel interfaces are shown at the far ends of the circuit. + +Diagram (b) showing a reference circuit for end-to-end channel(s) unavailability in SDH systems. It consists of two 'Office' blocks connected by a series of repeaters (R) via optical fibres. The left Office contains a Network element (SDH). The right Office contains a Network element (SDH). The total length is L (km). The end-to-end channel(s) unavailability is T minutes/year. Channel interfaces are shown at the far ends. + +b) Reference circuit for end-to-end channel(s) unavailability in SDH systems + +T1506600-91 + +- PDH Plesiochronous Digital Hierarchy +- SDH Synchronous Digital Hierarchy +- (R) Repeater +- Optical fibre +- DCC Digital Cross-Connect +- LT Line Terminal + +Figure 5/G.911 – Reference circuit for end-to-end channel unavailability + +# 8 Allocation methodology for end-to-end unavailability objectives + +## 8.1 Contributors to unavailability – Considerations regarding SDH and PDH systems on optical fibres + +The factors contributing to the end-to-end channel unavailability include: + +- a) multiplexers (not applicable to SDH equipment); +- b) optical media (cable, splices, connectors, etc.); +- c) line terminals and repeaters, including allocations for: + - hardware failures; and + - software and man-made procedural errors. + +*Multiplexers* – In the SDH systems, there is no need for a separate allocation to multiplexing equipments because the SDH standards include a method for mapping channels into the SDH payload. + +*Optical cables, terminals and repeaters* – Up until now, the reported data from telephone operating companies show that the optical media have a greater impact on unavailability than the terminals and repeaters. + +*Hardware failures and software and man-made procedural errors* – SDH systems are more software driven than PDH systems, because: + +- the hardware per channel is decreased; +- the amount of software is increased; and +- traffic rearranging is expected to be extensively used. + +Therefore it may be sensible to increase the proportion of unavailability allocated to software and procedural errors in SDH than in PDH systems. + +## 8.2 Allocation methodology + +Based on the above considerations, end-to-end unavailability allocation among relevant contributors are proposed as shown in diagrams a) (PDH systems) and b) (SDH systems) of Figure 6. + +The proportion of unavailability allocated to the various contributors is expected to differ for SDH as compared to PDH systems, as shown in Table 8. + +**Table 8/G.911 – Unavailability allocation to the various contributors +in a reference circuit for end-to-end channel unavailability** + +| Contributing factor | (PDH) | (SDH) | Comment | +|----------------------------|------------------------------------------------------------------------------------|----------------|---------------------------------| +| Multiplexers | A p | Not applicable | | +| Cable media | B p | B s | Similar values | +| Terminals and repeaters | C p | C s | Similar proportions | +| Hardware | D p | D s | D p > D s | +| Software and procedural | E p | E s | E p < E s | +| T | End-to-end channel unavailability (Min/year) | | | +| A | Unavailability proportion (%) allocated to multiplexers | | | +| B | Unavailability proportion (%) allocated to cable | | | +| C | Unavailability proportion (%) allocated to terminals and repeaters | | | +| D | Unavailability proportion (%) allocated to hardware failures | | | +| E | Unavailability proportion (%) allocated to software and man-made procedural errors | | | +| p | Denotes Plesiochronous Digital Hierarchy (PDH) systems | | | +| s | Denotes Synchronous Digital Hierarchy (SDH) systems | | | + +![Flowchart for End-to-end unavailability allocation methodology – Plesiochronous Digital Hierarchy (PDH) systems. The process starts with 'End-to-unavailability objective', which splits into 'Multiplexers' (Ap%) and 'Interfaces to line systems' ((100 - Ap)%). 'Interfaces to line systems' further splits into 'Optical cable media' (Bp%) and 'Line terminals and regenerators' ((100 - Bp)(%) = (Cp)%). 'Line terminals and regenerators' then splits into 'Software and procedural errors' (Dp%) and 'Hardware' (Ep(%) = (100 - Dp)%).](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +``` + +graph TD + A[End-to-unavailability objective] -- "Ap(%)" --> B[Multiplexers] + A -- "(100 - Ap)%" --> C[Interfaces to line systems] + C -- "Bp(%)" --> D[Optical cable media] + C -- "(100 - Bp)(%) = (Cp)%" --> E[Line terminals and regenerators] + E -- "Dp(%)" --> F[Software and procedural errors] + E -- "Ep(%) = (100 - Dp)%" --> G[Hardware] + +``` + +Flowchart for End-to-end unavailability allocation methodology – Plesiochronous Digital Hierarchy (PDH) systems. The process starts with 'End-to-unavailability objective', which splits into 'Multiplexers' (Ap%) and 'Interfaces to line systems' ((100 - Ap)%). 'Interfaces to line systems' further splits into 'Optical cable media' (Bp%) and 'Line terminals and regenerators' ((100 - Bp)(%) = (Cp)%). 'Line terminals and regenerators' then splits into 'Software and procedural errors' (Dp%) and 'Hardware' (Ep(%) = (100 - Dp)%). + +**a) End-to-end unavailability allocation methodology – Plesiochronous Digital Hierarchy (PDH) systems** + +![Flowchart for End-to-end unavailability allocation methodology – Synchronous Digital Hierarchy (SDH) systems. The process starts with 'End-to-unavailability objective', which splits into 'Optical cable media' (Bs(%) and 'Terminals and regenerators' (Cs(%) = (100 - Bs)%). 'Terminals and regenerators' then splits into 'Software and procedural errors' (Ds(%) and 'Hardware' (Es(%) = (100 - Ds)%).](552265bdbcf6d43d341fd018a9076269_img.jpg) + +``` + +graph TD + A[End-to-unavailability objective] -- "Bs(%)" --> B[Optical cable media] + A -- "Cs(%) = (100 - Bs)%" --> C[Terminals and regenerators] + C -- "Ds(%)" --> D[Software and procedural errors] + C -- "Es(%) = (100 - Ds)%" --> E[Hardware] + +``` + +T1506620-91 + +Flowchart for End-to-end unavailability allocation methodology – Synchronous Digital Hierarchy (SDH) systems. The process starts with 'End-to-unavailability objective', which splits into 'Optical cable media' (Bs(%) and 'Terminals and regenerators' (Cs(%) = (100 - Bs)%). 'Terminals and regenerators' then splits into 'Software and procedural errors' (Ds(%) and 'Hardware' (Es(%) = (100 - Ds)%). + +**b) End-to-end unavailability allocation methodology – Synchronous Digital Hierarchy (SDH) systems** + +**Figure 6/G.911 – End-to-end unavailability allocation methodology** + +# APPENDIX I + +## Determination of unit steady-state failure rate – Example + +This is an example of the methodology described in 4.3. This example evaluates the unit steady-state failure rate, it does not attempt to suggest any specific reliability objective either for the various devices or for the unit in itself. In this example an environmental failure-rate multiplicative fact ( $\pi_e$ ) equal to 2.0 will be employed (see Note 1 of I.3). + +## I.1 Unit description (example) + +| Device type | Quantity ( $N_i$ ) | +|-------------------------------------------|--------------------| +| Laser, 1300 nm | 1 | +| Transistor, Si, PNP, $\leq 0.6$ W | 10 | +| IC, digital, bipolar (hermetic, 30 gates) | 8 | +| IC, digital, NMOS (hermetic, 200 gates) | 6 | +| Capacitor, discrete, ceramic | 6 | + +### I.2 Reliability parameters of devices (example) + +| Device type (# $i$ ) | $X_{qi}$
(FITs) | $\pi_{qi}$ | $\pi_{si}$ | $\pi_j^a)$ | # $i$ | +|----------------------------------------------|--------------------|------------|------------|------------|-------| +| Laser, 1300 nm | 20 000 | 0.5 | 1.0 | 1.5 | 1 | +| Transistor, Si, PNP, $\leq 0.6$ W | 25 | 1.0 | 1.0 | 1.2 | 2 | +| IC, digital, bipolar
(hermetic, 30 gates) | 10 | 1.0 | 1.0 | 1.2 | 3 | +| IC, digital, NMOS
(hermetic, 200 gates) | 130 | 1.0 | 1.0 | 1.2 | 4 | +| Capacitor, discrete, ceramic | 12 | 1.0 | 1.0 | 1.0 | 5 | + +a) See Note 2 of I.3. + +## I.3 Unit steady-state failure rate (FITs) + +Following the procedure described in 4.2 and 4.3, the unit steady-state failure rate is given: + +$$\begin{aligned}\lambda_s &= (\pi_e) \{ (N_1)(15\,000) + (N_2)(30) + (N_3)(12) + (N_4)(156) + (N_5)(12) \} \\ &= (2) \times (16\,404) = 32\,808 \text{ FITs}\end{aligned}$$ + +NOTE 1 – This is a typical value for unit to be installed in remote terminal and/or customer premise areas subject to shock and vibration, or temperature and humidity variations. For atmospheric controlled environments (like central offices) a $\pi_e$ equal to 1.0 is more appropriate. + +NOTE 2 – In this example the units operating temperature is assumed to be not higher than 45-50° C. + +# APPENDIX II + +## Study case channel availability for a $4 \times 140$ Mbit/s repeater link on optical fibres with "3 + 1" line protection + +This is just an example of the methodology described in clause 6. That example does not attempt to suggest or recommend any specific reliability objective. + +### II.1 Description + +Figure II.1 shows a system in the configuration " $N + 1$ ". It consists of $N$ digital line systems on optical fibre operating in parallel with an additional identical reserve system. For the purposes of this case study, the digital line system is made up of a pair of line multiplexer-terminals and by the optical fibre cables with their regenerators. The line systems operate at 565 Mbit/s, made up of four 140 Mbit/s channels. + +![Diagram of system configuration 'N + 1' showing N active systems and 1 protection system.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +The diagram illustrates a system configuration labeled "N + 1", consisting of N active digital line systems and one protection system. Each system is shown as a horizontal path between two line multiplexer-terminals. The top system is detailed: on the left, "Channel 1" through "Channel M" enter a terminal containing a MUX, TR, DMUX, and RX. A PS (Power Supply) is connected to the bottom of this terminal. The output of the terminal enters a "Fibre cable + repeater" block via a repeater (indicated by a circle with an arrow). The output of the fibre cable enters another repeater, which then connects to the right-hand terminal. This terminal contains a RX, DMUX, TR, and MUX, with a PS connected to its bottom. The output of this terminal splits back into "Channel 1" through "Channel M". Below this top system, there are N identical active systems, represented by simplified terminal blocks and a central "N" label. At the bottom, there is a "Protection system", also represented by simplified terminal blocks and a central label. The diagram is signed "T1506500-90" in the bottom right corner. + +Diagram of system configuration 'N + 1' showing N active systems and 1 protection system. + +**Figure II.1/G.911 – Example – System configuration " $N + 1$ "** +**("N" active and 1 reserve)** + +Figure II.2 shows a diagram of states for the particular case of three active systems ( $N = 3$ ) plus one reserve system. The diagram shows the possible situations which can arise owing to the occurrence of failures in the digital line terminals or in the repeaters. + +The reserve system, either partly or wholly, takes over the traffic of any of the line systems in service which breaks down. If the failure occurs in a channel unit (at 140 Mbit/s), then one of the four channel units of the protection system comes into service. If the failure occurs either in the repeaters or in the line multiplexer-terminals, so that a whole system is affected, then the whole of its traffic (four 140 Mbit/s channels) is transferred to the reserve system. If in the case of a failure on a channel + +or an entire system the traffic cannot be transferred to the reserve system (because it has already taken over the traffic of another faulty system), then the traffic on this channel or system would remain in a state of unavailability. + +Figure II.2 also shows the transition from one state to another, according to the failure rate (number of failures per time unit) and repair rate (inverse value of average time taken to repair a failure). + +![Markov diagram for system configuration 'N + 1' showing six states and their transitions. State 1 (All well) is the top state. State 2 (Activated 1 channel unit of reserve) and State 3 (Activated 4 channel units of reserve) are below it. State 4 (1 channel down), State 5 (1 channel down), and State 6 (4 channels down) are at the bottom. Transitions are labeled with failure rates (lambda_C, lambda_B) and repair rates (mu).](b235edb1dbe659e2782c9a0e47775ca4_img.jpg) + +``` + + graph TD + 1((All well +①)) -- "16 λ_C" --> 2((Activated 1 channel unit of reserve +②)) + 2 -- "μ" --> 1 + 1 -- "4 λ_B" --> 3((Activated 4 channel units of reserve +③)) + 3 -- "μ" --> 1 + 2 -- "3 λ_C" --> 4((1 channel down +④)) + 4 -- "2 μ" --> 2 + 2 -- "3 λ_B" --> 5((1 channel down +⑤)) + 5 -- "μ" --> 2 + 3 -- "3 λ_C" --> 5 + 5 -- "μ" --> 3 + 3 -- "3 λ_B" --> 6((4 channels down +⑥)) + 6 -- "2 μ" --> 3 + +``` + +T1506510-90 + +Markov diagram for system configuration 'N + 1' showing six states and their transitions. State 1 (All well) is the top state. State 2 (Activated 1 channel unit of reserve) and State 3 (Activated 4 channel units of reserve) are below it. State 4 (1 channel down), State 5 (1 channel down), and State 6 (4 channels down) are at the bottom. Transitions are labeled with failure rates (lambda\_C, lambda\_B) and repair rates (mu). + +$\mu$ Repairs/hour + +$\lambda_C$ Channel unit failure + +$\lambda_B (\lambda_{MUX} + \lambda_{DMUX} + \lambda_{TX} + \lambda_{RX} + \lambda_{PS}) + \text{No. repeaters} \times (2\lambda_{TX} + 2\lambda_{RX} + \lambda_{PS})$ + +TX Optical transmitter + +RX Optical receiver + +PS Power supply unit + +Example: M4 . (4 channels of 140 Mbit/s per line terminal) = 16 + +$N (+1) = 3 \text{ active } (+1 \text{ reserve}) = 3 + 1$ + +**Figure II.2/G.911 – System configuration "N + 1" – Markov diagram** + +### II.2 Results – Unavailability (minutes/year) per 140 Mbit/s channel + +The results given below are based on a "3 + 1" configuration for digital line systems on optical fibre operating at 565 Mbit/s. Unavailability was obtained statistically by estimating the probability of the states which can give rise to the loss of a 140 Mbit/s channel (i.e. states 4, 5 and 6 illustrated in Figure II.2). + +Figure II.3 shows unavailability per 140 Mbit/s channel according to: + +- repair time per failure; +- number of repeaters in the system. + +The results were based on the following failure rates: + +- failure rate per channel unit (140 Mbit/s) = 6 000 FITs; +- failure rate of line multiplexer-terminal (without counting channel units) = 42 000 FITs; +- failure rate per regenerator = 42 000 FITs. + +![Line graph showing Unavailability (minutes/year) vs Number of repeaters for a '3 + 1' protection configuration. The y-axis is logarithmic from 10^-2 to 10^3. The x-axis shows 0, 10, and 20 repeaters. Two lines are plotted: one for 0.25 Rep/h (solid circles) and one for 0.0083 Rep/h (open squares).](20727e57890be6da5692a02d13c0a8ec_img.jpg) + +Unavailability per 140 Mbit/s channel + +"3 + 1" protection configuration + 4 × 140 Mbit/s line-terminal + +| Number of repeaters | Unavailability (minutes/year) at 0.25 Rep/h | Unavailability (minutes/year) at 0.0083 Rep/h | +|---------------------|---------------------------------------------|-----------------------------------------------| +| 0 | ~1 | ~0.01 | +| 10 | ~50 | ~5 | +| 20 | ~150 | ~15 | + +T1506520-90 + +● 0.25 Rep/h + □ 0.0083 Rep/h + +Line graph showing Unavailability (minutes/year) vs Number of repeaters for a '3 + 1' protection configuration. The y-axis is logarithmic from 10^-2 to 10^3. The x-axis shows 0, 10, and 20 repeaters. Two lines are plotted: one for 0.25 Rep/h (solid circles) and one for 0.0083 Rep/h (open squares). + +**Figure II.3/G.911 – Unavailability for 140 Mbit/s channel** + +# APPENDIX III + +## **Study case – Channel availability for a point-to-point fibre connection in the local network with "1 + 1" line protection, with and without cable-path redundancy** + +This is an example of the methodology described in clause 6. That example does not attempt to suggest or recommend any specific reliability objective. + +### **III.1 Description** + +### **III.1.1 Nature of the problem** + +The widespread deployment of optical fibres in the telecommunication networks and the increasing traffic carried on individual fibres have raised concerns about the need for line terminals and cable redundancy to reduce service interruptions in the event of cable cut or line equipment failure. In the access network, this is even more critical because users do not have alternate path connections via another central office (as it may be the case in connection among central offices). + +These approaches are motivated by practical considerations. For instance, banks and brokerage firms have a very high priority for network reliability. Even in the current narrow-band environment, these businesses may have dual 1:1 protection via the same path or alternate path for many of their connection links. This provides one-for-one backup links, with automatic or handy switchover to a + +backup link when a link failure occurs. In a broadband environment, when a cable cut might eliminate multiple 155 Mbit/s communication lines, these concerns would probably be even higher. + +This Appendix describes and evaluates the reliability issues and the impact on customer connection availability for the following five types of connections (see III.1.2): + +- connections with no redundancy; +- connections with line equipment redundancy and manual switchover; +- connections with line equipment redundancy and automatic switchover; +- connections with cable redundancy; and +- connections with line equipment and cable redundancy. + +### III.1.2 Type of connections + +The connections between Central Office (CO) and Customer Premises (CP) are implemented with single-mode fibres. Each fibre is used for unidirectional transmission, thereby requiring the deployment of fibres in pairs to achieve duplex connections. The equipment-redundancy approach assumes 1:1 protection for Optical Line Terminating Multiplexers (OLTMs). Cable redundancy assumes an alternate path is provided via a physically diverse route. Manual switching assumes that there is a certain time, between the failure and switch, in which the connection is unavailable, and, in the automatic switching, this time is 0. + +The five alternative connection approaches are: + +- Connections with no redundancy [Figure III.1 a)]. +- Connections with line equipment redundancy and manual switchover [Figure III.1 b)]. The design provides protection against terminal equipment failure at the CO and CP. However, the system is vulnerable to fibre cable failure. Switching time is considered. +- Connections with line equipment redundancy and automatic switchover [Figure III.1 c)]. This is the same case as before but the switching time is 0. +- Connections with cable redundancy [Figure III.1 d)]. This alternative assumes that working and protection fibres follow physically separate paths to the same CO. This design provides protection against fibre cable failures. The fibre cable switching is automatic. +- Connections with line equipment and cable redundancy [Figure III.1 e)]. This design provides protection against terminal equipment failure and fibre cable failures. This alternative is divided in two: (e1) with automatic switchover and (e2) without automatic switchover. + +![Five diagrams (a, b, c, d, e) showing different network configurations between a Central Office (CO) and a Customer Premises (CP) using OLTMs and switches. Diagram (a) shows a basic connection. Diagrams (b) and (c) show terminal equipment redundancy with manual and automatic switchover respectively. Diagrams (d) and (e) show combinations of terminal equipment and cable redundancy with automatic switchover.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +(CO) (CP) + +**a) No redundancy** + +(CO) (CP) + +**b) Connection with terminal equipment redundancy and manual switchover** + +(CO) (CP) + +**c) Connection with terminal equipment redundancy and automatic switchover** + +(CO) (CP) + +**d) Connection with cable redundancy** + +(CO) (CP) + +**e1) Connection with terminal equipment and cable redundancy and automatic switchover** + +(CO) (CP) + +**e2) Connection with line – Equipment and cable redundancy** + +Five diagrams (a, b, c, d, e) showing different network configurations between a Central Office (CO) and a Customer Premises (CP) using OLTMs and switches. Diagram (a) shows a basic connection. Diagrams (b) and (c) show terminal equipment redundancy with manual and automatic switchover respectively. Diagrams (d) and (e) show combinations of terminal equipment and cable redundancy with automatic switchover. + +T1506630-91 + +**Figure III.1/G.911 – Type of corrections considered** + +## III.2 Results + +To quantify and compare the reliability performance of the five connection approaches described above, this subclause provides the unavailability (in minutes per year per 2 Mbit/s channel), based on Markov models. + +Figure III.2 considers the unprotected system. The system is inoperative if any of the two network elements has a failure. + +![Figure III.2/G.911 – No redundancy and its Markov model. The diagram shows a block diagram of an OLT and a Cable in series, and a Markov state transition diagram with four states.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +The block diagram shows an OLTM with failure rate $\lambda_1$ and a Cable with failure rate $\lambda_2$ connected in series. The Markov model has four states: 1 (All working), 2 (OLTM fails (su)), 3 (Cable fails (su)), and 4 (OLTM and cable fail (su)). Transitions are: 1 to 2 ( $\lambda_1$ ), 1 to 3 ( $\lambda_2$ ), 2 to 1 ( $\mu_1$ ), 3 to 1 ( $\mu_2$ ), 2 to 4 ( $\lambda_2$ ), 3 to 4 ( $\lambda_1$ ), 4 to 2 ( $\mu_2$ ), and 4 to 3 ( $\mu_1$ ). + +- 1 All working +- 2 OLTM fails (su) +- 3 Cable fails (su) +- 4 OLTM and cable fail (su) + +su system unavailable + +Figure III.2/G.911 – No redundancy and its Markov model. The diagram shows a block diagram of an OLT and a Cable in series, and a Markov state transition diagram with four states. + +**Figure III.2/G.911 – No redundancy and its Markov model** + +Figure III.3 shows the OLTMs redundancy approach and manual switchover. In the normal operating state (1), both the working and the protection terminal equipment at the CO and CP are fully operational. When one of the two units has a failure (state 2), the other unit takes over manually in a determinate time during which the system is inoperative. The system can be restored to state 1 if the switch is done. The system is also inoperative (state 3) if both units fail or the cable loop between CO and CP fails. + +![Figure III.3/G.911 – Connection with terminal equipment redundancy and manual switchover and its Markov model. The diagram shows a block diagram with two OLTMs in parallel followed by a Cable, and a Markov state transition diagram with six states.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) + +The block diagram shows two OLTMs (failure rate $\lambda_1$ ) in parallel, followed by a Cable (failure rate $\lambda_2$ ). The Markov model has six states: 1 (All working), 2 (Working OLTM fails, Waiting manual switch (su)), 3 (OLTM unprotected), 4 (Cable fails (su)), 5 (One OLTM and cable fail (su)), and 6 (Both OLTMs fail (su)). Transitions are: 1 to 2 ( $\lambda_1$ ), 1 to 4 ( $\lambda_2$ ), 2 to 3 ( $\mu_3$ ), 3 to 1 ( $\mu_1$ ), 3 to 4 ( $\lambda_2$ ), 3 to 6 ( $\lambda_1$ ), 4 to 1 ( $\mu_2$ ), 4 to 5 ( $\mu_1$ ), 5 to 3 ( $\mu_2$ ), 5 to 4 ( $\mu_1$ ), 6 to 3 ( $2\mu_1$ ), and 6 to 4 ( $\lambda_1$ ). + +- 1 All working +- 2 Working OLTM fails +Waiting manual switch (su) +- 3 OLTM unprotected +- 4 Cable fails (su) +- 5 One OLTM and cable fail (su) +- 6 Both OLTMs fail (su) + +Figure III.3/G.911 – Connection with terminal equipment redundancy and manual switchover and its Markov model. The diagram shows a block diagram with two OLTMs in parallel followed by a Cable, and a Markov state transition diagram with six states. + +**Figure III.3/G.911 – Connection with terminal equipment redundancy and manual switchover and its Markov model** + +Figure III.4 shows the OLTMs redundancy approach and automatic switchover. In the normal operating state (1), both the working and the protection terminal equipment at the CO and CP are fully operational. When one of the two units has a failure (state 2), the other unit automatically takes + +over and provides continuous operation. The system can be restored to state 1 if the unit is restored. The system is inoperative (state 3) if both units fail, or the cable loop between CO and CP fails. + +![Schematic and Markov model for terminal equipment redundancy. The schematic shows two OLTMs in parallel, each with failure rate λ1, connected in series with a Cable with failure rate λ2. The Markov model has six states: 1 (All working), 2 (One OLTM fails), 3 (Cable fails), 4 (One OLTM and cable fail), 5 (Both OLTMs fail), and 6 (Both OLTMs and cable fail). Transitions are labeled with failure rates (λ) and repair rates (μ).](c76da2d73c064464051d1583fd80bb6b_img.jpg) + +1 All working + 2 One OLTM fails (*automatic switch*) + 3 Cable fails (*su*) + 4 One OLTM and cable fail (*su*) + 5 Both OLTMs fail (*su*) + 6 Both OLTMs and cable fail (*su*) + +T1514130-93 + +Schematic and Markov model for terminal equipment redundancy. The schematic shows two OLTMs in parallel, each with failure rate λ1, connected in series with a Cable with failure rate λ2. The Markov model has six states: 1 (All working), 2 (One OLTM fails), 3 (Cable fails), 4 (One OLTM and cable fail), 5 (Both OLTMs fail), and 6 (Both OLTMs and cable fail). Transitions are labeled with failure rates (λ) and repair rates (μ). + +**Figure III.4/G.911 – Connection with terminal equipment redundancy and automatic switchover and its Markov model** + +Figure III.5 shows the cable redundancy approach. In the normal operating state (1), both cables are fully operational. When one of the two cables has a failure (state 2), the other cable automatically takes over and provides continuous operation. The system can be restored to state 1 if the cable is restored. The system is inoperative (state 3) if both cables fail or the terminal equipment between CO and CP fails. + +![Schematic and Markov model for cable redundancy. The schematic shows one OLTM with failure rate λ1 connected in series with two Cables in parallel, each with failure rate λ2. The Markov model has six states: 1 (All working), 2 (One cable fails), 3 (OLTM fails), 4 (One OLTM and cable fail), 5 (Both cables fail), and 6 (Both cables and OLTM fail). Transitions are labeled with failure rates (λ) and repair rates (μ).](3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg) + +1 All working + 2 One cable fails (*automatic switch*) + 3 OLTM fails (*su*) + 4 One OLTM and cable fail (*su*) + 5 Both cables fail (*su*) + 6 Both cables and OLTM fail (*su*) + +T1514140-93 + +Schematic and Markov model for cable redundancy. The schematic shows one OLTM with failure rate λ1 connected in series with two Cables in parallel, each with failure rate λ2. The Markov model has six states: 1 (All working), 2 (One cable fails), 3 (OLTM fails), 4 (One OLTM and cable fail), 5 (Both cables fail), and 6 (Both cables and OLTM fail). Transitions are labeled with failure rates (λ) and repair rates (μ). + +**Figure III.5/G.911 – Connection with cable redundancy and its Markov model** + +Figure III.6a shows the terminal equipment and cable redundancy approach. In normal operation both working and protection equipment and cable are fully operational. State 2 depicts those situations in which one OLTM or one cable loop fails. The other unit automatically takes over and provides continuous operation. The system can be restored to state 1 if the fail is restored. The system is inoperative (state 3) if both cables or both OLTM fail. + +Figure III.6b shows the OLTMs and cable redundancy approach. In normal operation both working and protection equipment and cable are fully operational. States 2 and 3 depict those situations in which one OLTM or one cable loop fails, respectively. State 4 refers to the situations in which both + +an OLT and one cable loop fails, however, those faults being placed in different paths. The system is inoperative in state 5. + +![Schematic diagram of a system with OLT and Cable redundancy. Two parallel OLT blocks, each containing two units with failure rate λ1, are connected in series with two parallel Cable blocks, each containing two units with failure rate λ2.](399a5af4f606059626c92c92279d54b7_img.jpg) + +Schematic diagram of a system with OLT and Cable redundancy. Two parallel OLT blocks, each containing two units with failure rate λ1, are connected in series with two parallel Cable blocks, each containing two units with failure rate λ2. + +- 1 All working +- 2 One OLT fails +- 3 One cable fails +- 4 Both OLTs fail (su) +- 5 One OLT and one cable fail +- 6 Both cables fail (su) + +![Markov state transition diagram for the system in Figure III.6a. States are numbered 1 to 6. Transitions are labeled with failure rates (λ1, λ2) and repair rates (μ1, μ2). State 1 is the top state (All working). Transitions: 1 to 2 (2λ1), 1 to 3 (2λ2), 2 to 1 (μ1), 2 to 3 (2λ2), 2 to 4 (λ1), 2 to 5 (μ2), 3 to 1 (μ2), 3 to 2 (μ1), 3 to 4 (2λ1), 3 to 5 (2λ1), 3 to 6 (2μ2), 4 to 1 (2λ1), 4 to 2 (λ1), 4 to 5 (2μ1), 5 to 1 (μ2), 5 to 2 (μ2), 5 to 3 (μ1), 5 to 6 (λ2).](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +Markov state transition diagram for the system in Figure III.6a. States are numbered 1 to 6. Transitions are labeled with failure rates (λ1, λ2) and repair rates (μ1, μ2). State 1 is the top state (All working). Transitions: 1 to 2 (2λ1), 1 to 3 (2λ2), 2 to 1 (μ1), 2 to 3 (2λ2), 2 to 4 (λ1), 2 to 5 (μ2), 3 to 1 (μ2), 3 to 2 (μ1), 3 to 4 (2λ1), 3 to 5 (2λ1), 3 to 6 (2μ2), 4 to 1 (2λ1), 4 to 2 (λ1), 4 to 5 (2μ1), 5 to 1 (μ2), 5 to 2 (μ2), 5 to 3 (μ1), 5 to 6 (λ2). + +T1514150-93 + +NOTE – These groups do not represent all possible situations. + +**Figure III.6a/G.911 – Connection with terminal equipment and cable redundancy and automatic switchover and its Markov method** + +![Schematic diagram of a system with Cable and OLT redundancy. Two parallel OLT blocks, each containing two units with failure rate λ1, are connected in series with two parallel Cable blocks, each containing two units with failure rate λ2.](8658cfab6a458b4a80ab2e384c61ff89_img.jpg) + +Schematic diagram of a system with Cable and OLT redundancy. Two parallel OLT blocks, each containing two units with failure rate λ1, are connected in series with two parallel Cable blocks, each containing two units with failure rate λ2. + +- 1 All working +- 2 One OLT fails +- 3 One cable fails +- 4 Both OLTs fail (su) +- 5 One OLT and one cable fail on separate path (su) +- 6 Both cables fail (su) + +![Markov state transition diagram for the system in Figure III.6b. States are numbered 1 to 6. Transitions are labeled with failure rates (λ1, λ2) and repair rates (μ1, μ2). State 1 is the top state (All working). Transitions: 1 to 2 (2λ1), 1 to 3 (2λ2), 2 to 1 (μ1), 2 to 3 (λ2), 2 to 4 (λ1), 2 to 5 (μ2), 3 to 1 (μ2), 3 to 2 (μ1), 3 to 4 (2λ1), 3 to 5 (λ1), 3 to 6 (2μ2), 4 to 1 (2λ1), 4 to 2 (λ1), 4 to 5 (2μ1), 5 to 1 (μ2), 5 to 2 (μ2), 5 to 3 (μ1), 5 to 6 (λ2).](1841f348dfa81a3438d4e1f8465d9ac7_img.jpg) + +Markov state transition diagram for the system in Figure III.6b. States are numbered 1 to 6. Transitions are labeled with failure rates (λ1, λ2) and repair rates (μ1, μ2). State 1 is the top state (All working). Transitions: 1 to 2 (2λ1), 1 to 3 (2λ2), 2 to 1 (μ1), 2 to 3 (λ2), 2 to 4 (λ1), 2 to 5 (μ2), 3 to 1 (μ2), 3 to 2 (μ1), 3 to 4 (2λ1), 3 to 5 (λ1), 3 to 6 (2μ2), 4 to 1 (2λ1), 4 to 2 (λ1), 4 to 5 (2μ1), 5 to 1 (μ2), 5 to 2 (μ2), 5 to 3 (μ1), 5 to 6 (λ2). + +T1514160-93 + +NOTE – These groups do not represent all possible situations. + +**Figure III.6b/G.911 – Connection with cable and OLT redundancy and its Markov model** + +Table III.1 shows the list of steady-state failure rates, repair rates and handy switching times. + +**Table III.1/G.911 – Steady-state failure rates, repair rates and +handy switching times** + +| | | +|----------------------------------------------------|---------------------------------------| +| Steady-state failure rate of OLTM ( $\lambda_1$ ) | 23 000-57 000 FITs; MTBF = 2-5 years | +| Steady-state failure rate of cable ( $\lambda_2$ ) | 11 500-23 000 FITs; MTBF = 5-10 years | +| Repair rate of OLTM ( $\mu_1$ ) | (1-2 per day) | +| Repair rate of cable ( $\mu_2$ ) | (0.5-1 per day) | +| Manual switching time ( $1/\mu_3$ ) | (0.5-4 hours) | + +Tables III.2 to III.6 list the results of the different cases. + +**Table III.2/G.911 – Performance of unprotected broadband +customer local connections** + +| (1/\lambda_1)
years
| (1/\lambda_2)
years
| (1/\mu_1)
days
| (1/\mu_2)
days
| 2 Mbit/s channel unavailability
(minutes/year)
| +|---------------------------------------------|---------------------------------------------|----------------------------------------|----------------------------------------|-----------------------------------------------------------| +| 2 | 5 | 0.5 | 1 | 647 | +| 2 | 10 | 0.5 | 1 | 504 | +| 5 | 5 | 0.5 | 1 | 432 | +| 5 | 10 | 0.5 | 1 | 289 | +| | | | | | +| 2 | 5 | 1 | 2 | 1294 | +| 2 | 10 | 1 | 2 | 1006 | +| 5 | 5 | 1 | 2 | 863 | +| 5 | 10 | 1 | 2 | 576 | + +**Table III.3/G.911 – Performance of customer access connection with terminal equipment redundancy and manual switchover** + +| (1/λ1)
years
| (1/λ2)
years
| (1/μ1)
days
| (1/μ2)
days
| (1/μ1)
hours
| 2 Mbit/s channel unavailability
(minutes/years)
| +|------------------------------------|------------------------------------|-----------------------------------|-----------------------------------|------------------------------------|------------------------------------------------------------| +| 2 | 5 | 0.5 | 1 | 0.5 | 303 | +| 2 | 10 | 0.5 | 1 | 0.5 | 159 | +| 5 | 5 | 0.5 | 1 | 0.5 | 294 | +| 5 | 10 | 0.5 | 1 | 0.5 | 150 | +| 2 | 5 | 1 | 2 | 0.5 | 591 | +| 2 | 10 | 1 | 2 | 0.5 | 304 | +| 5 | 5 | 1 | 2 | 0.5 | 582 | +| 5 | 10 | 1 | 2 | 0.5 | 294 | +| 2 | 5 | 0.5 | 1 | 1 | 318 | +| 2 | 10 | 0.5 | 1 | 1 | 174 | +| 5 | 5 | 0.5 | 1 | 1 | 300 | +| 5 | 10 | 0.5 | 1 | 1 | 156 | +| 2 | 5 | 1 | 2 | 1 | 606 | +| 2 | 10 | 1 | 2 | 1 | 319 | +| 5 | 5 | 1 | 2 | 1 | 587 | +| 5 | 10 | 1 | 2 | 1 | 300 | + +**Table III.4/G.911 – Performance of customer access connection with terminal equipment redundancy and manual switchover** + +| (1/λ1)
years
| (1/λ2)
years
| (1/μ1)
days
| (1/μ2)
days
| 2 Mbit/s channel unavailability
(minutes/year)
| +|------------------------------------|------------------------------------|-----------------------------------|-----------------------------------|-----------------------------------------------------------| +| 2 | 5 | 0.5 | 1 | 288 | +| 2 | 10 | 0.5 | 1 | 144 | +| 5 | 5 | 0.5 | 1 | 288 | +| 5 | 10 | 0.5 | 1 | 144 | +| 2 | 5 | 1 | 2 | 576 | +| 2 | 10 | 1 | 2 | 289 | +| 5 | 5 | 1 | 2 | 576 | +| 5 | 10 | 1 | 2 | 288 | + +**Table III.5/G.911 – Performance of customer access connection with cable redundancy** + +| (1/λ1)
years
| (1/λ2)
years
| (1/μ1)
days
| (1/μ2)
days
| 2 Mbit/s channel unavailability
(minutes/year)
| +|------------------------------------|------------------------------------|-----------------------------------|-----------------------------------|-----------------------------------------------------------| +| 2 | 5 | 0.5 | 1 | 360 | +| 2 | 10 | 0.5 | 1 | 360 | +| 5 | 5 | 0.5 | 1 | 144 | +| 5 | 10 | 0.5 | 1 | 144 | +| 2 | 5 | 1 | 2 | 720 | +| 2 | 10 | 1 | 2 | 719 | +| 5 | 5 | 1 | 2 | 288 | +| 5 | 10 | 1 | 2 | 288 | + +**Table III.6/G.911 – Performance of customer access** + +**a) Performance of customer access connection with terminal equipment and cable redundancy and automatic switchover** + +| (1/λ1)
years
| (1/λ2)
years
| (1/μ1)
days
| (1/μ2)
days
| 2 Mbit/s channel unavailability
(minutes/year)
| +|------------------------------------|------------------------------------|-----------------------------------|-----------------------------------|-----------------------------------------------------------| +| 2 | 5 | 0.5 | 1 | 0.40 | +| 2 | 10 | 0.5 | 1 | 0.29 | +| 5 | 5 | 0.5 | 1 | 0.20 | +| 5 | 10 | 0.5 | 1 | 0.08 | +| 2 | 5 | 1 | 2 | 1.61 | +| 2 | 10 | 1 | 2 | 1.14 | +| 5 | 5 | 1 | 2 | 0.79 | +| 5 | 10 | 1 | 2 | 0.31 | + +#### **b) Performance of customer access connection with cable and terminal equipment redundancy** + +| (1/λ1)
years
| (1/λ2)
years
| (1/μ1)
days
| (1/μ2)
days
| 2 Mbit/s channel unavailability
(minutes/year)
| +|------------------------------------|------------------------------------|-----------------------------------|-----------------------------------|-----------------------------------------------------------| +| 2 | 5 | 0.5 | 1 | 0.80 | +| 2 | 10 | 0.5 | 1 | 0.48 | +| 5 | 5 | 0.5 | 1 | 0.35 | +| 5 | 10 | 0.5 | 1 | 0.16 | +| 2 | 5 | 1 | 2 | 3.18 | +| 2 | 10 | 1 | 2 | 1.92 | +| 5 | 5 | 1 | 2 | 1.42 | +| 5 | 10 | 1 | 2 | 0.63 | + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communication | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/G/T-REC-G.952-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.952-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec927aa28872ab95f0a5b889515cd45616085677 --- /dev/null +++ b/marked/G/T-REC-G.952-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32842e55f1f7e5fae5b4d9e35bbd3dbc54ce125577b374e28bcca57790328a04 +size 7513 diff --git a/marked/G/T-REC-G.952-198811-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg b/marked/G/T-REC-G.952-198811-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc80ead8eac084d8def283cba4f13376f0b50795 --- /dev/null +++ b/marked/G/T-REC-G.952-198811-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cc432457ba0289a3ba5ba6c462cc979513c61e763574ac0bf72aa82c79eda43 +size 64950 diff --git a/marked/G/T-REC-G.952-198811-I_PDF-E/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg b/marked/G/T-REC-G.952-198811-I_PDF-E/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e583ce1ae5a82c54fb77c2a4f500e75cddf73b6 --- /dev/null +++ b/marked/G/T-REC-G.952-198811-I_PDF-E/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c7829a40718f9d9b28f30b53548bfcfc5bd2620e43e1536b1289939e29aa161 +size 51980 diff --git a/marked/G/T-REC-G.952-198811-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/G/T-REC-G.952-198811-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d56524dcb4c42bbc99826939dfecf4a12f6a2356 --- /dev/null +++ b/marked/G/T-REC-G.952-198811-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be620b6268a01c1dc4a45127777b4a212709659dfe65575081c75eb5f66b59cb +size 55243 diff --git a/marked/G/T-REC-G.952-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/G/T-REC-G.952-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69b5948eb0e9ceb4e98fca59c84750c56ae5e1be --- /dev/null +++ b/marked/G/T-REC-G.952-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c49a9f806abc569e2b4d602a117336cd468d1c31d42affcb4ec87046d30f537 +size 74461 diff --git a/marked/G/T-REC-G.952-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.952-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d0fd239c956abcbbac38ffb450022da6f2a16bba --- /dev/null +++ b/marked/G/T-REC-G.952-198811-I_PDF-E/raw.md @@ -0,0 +1,310 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.952** + +# **DIGITAL SECTIONS AND DIGITAL LINE SYSTEMS** --- + +## **DIGITAL LINE SYSTEMS BASED ON THE 2048 KBIT/S HIERARCHY ON SYMMETRIC PAIR CABLES** + +**ITU-T Recommendation G.952** + +(Extract from the *Blue Book*) + +--- + +### NOTES + +1 ITU-T Recommendation G.952 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 LINE SYSTEMS BASED ON THE 2048 kbit/s HIERARCHY ON SYMMETRIC PAIR CABLES** + +*(Malaga-Torremolinos, 1984; amended at Melbourne, 1988)* + +### **1 General** + +This Recommendation covers digital line systems for the transmission of signals based on the 2048 kbit/s hierarchy on symmetric pair cables and includes systems operating at the following bit rates: + +2 048 kbit/s + +8 448 kbit/s + +34 368 kbit/s + +The requirement for overall performance and interfaces of the corresponding digital line sections are given in Recommendation G.921. + +### **2 Transmission medium** + +The system can be operated on symmetrical pair cables of various wire diameters and cable constructions including those given in Recommendations G.611, 612 and 613. + +*Note - 34 368 kbit/s systems should be operated on high performance cables and may require one cable for each direction of transmission.* + +### **3 Protection against interference from external sources** + +The digital line system can be disturbed by interference from telephone circuits carried within the same cable and by a switch when repeaters are installed in switching centres. Examples of possible ways of reducing the effect of this type of interference are the reduction of repeater section length near switching centres, segregation of pairs, the use of particular line codes, etc. + +### **4 Overall design features** + +#### **4.1 *Availability*** + +The availability objective of the system should be derived taking into account the availability requirement for the hypothetical reference digital section as given in draft Recommendation G.801. + +#### **4.2 *Reliability*** + +MTBF values should be specified for the line system as a whole taking into account the requirements concerning availability. + +#### **4.3 *Repeater crosstalk-noise figures*** + +Repeater crosstalk-noise figures are defined in Annex A, together with suggested measurement techniques. Crosstalk-noise figures quantify the performance of digital regenerators which are subject to crosstalk interference. They are functions of BER, line system line code, cable characteristics, environmental conditions, and repeater spacing loss $A_0$ (at half the line system baud rate). + +At a BER = $10^{-x}$ and over a loss range $A_1 \leq A_0 \leq A_2$ , crosstalk-noise figures should meet the following specifications: + +- a) NEXT-Noise Figure $[R_N] \leq CA_0 + D^*$ +- b) FEXT-Noise Figure $[R_F] \leq E^*$ . + +\* It has not been possible to recommend specific values for parameters $x$ , $A_1$ , $A_2$ , $C$ , $D$ , and $E$ . + +Examples of the values used by some Administrations for 2 Mbit/s systems are given below: + +| Example | $x$ | $A_1$ | $A_2$ | $C$ | $D$ | $E$ | Test method | +|---------|-----|-------|-------|-----|------|------|-------------| +| i | 6 | 5 | 40 | 1.1 | 14.7 | 17.5 | a | +| ii | 7 | 10 | 40 | 1.0 | 19 | - | b | +| iii | 7 | 7 | 38 | 1.0 | 18 | - | b | + +Note 1 - In example ii, a filter with a centre frequency of 1020 kHz and a bandwidth of 3.1 kHz is employed. + +Note 2 - The values do not include any allowance for the effects of jitter. + +#### 4.4 Error performance + +The design objective for the error ratio of the individual repeater should take into account the network performance objectives given in Recommendation G.821. + +### 5 Specific design features + +#### 5.1 Type of power feeding + +Although CCITT does not recommend the use of a specific remote power-feeding system for this symmetrical line system, in practice only the constant current d.c. feeding via the phantom circuits of the two symmetrical pairs of a system is used. + +This symmetrical cable system may be subject to induced voltages and currents caused by lightning, power lines, railways, etc. + +Precautions must be taken to protect the staff from any possible danger arising from the normal operating voltages and remote power-feed currents as well as from the induced voltages and currents. + +Many national Administrations have issued detailed rules and regulations for the protection of persons. It is obligatory in most cases to meet these rules and regulations. In addition the CCITT Directives [1] give guidance on these problems. + +Precautions are also needed for the protection of the equipment against induced voltages and currents. The equipment should therefore be designed in such a way that it passes the tests specified in Recommendation K.17 [2]. + +#### 5.2 Repeater spacing and cable fill + +A specific repeater spacing cannot be recommended, but general considerations concerning system planning are contained in Annex B to this Recommendation. + +#### 5.3 Maintenance strategy + +##### 5.3.1 Type of supervision and fault location + +In-service monitoring or out-of-service fault location can be used. + +##### 5.3.2 Fault conditions and consequent actions + +The following fault conditions should be detected in addition to those specified in Recommendation G.921 for the relevant digital sections, and the associated consequent actions should be taken: + +- a) failure of remote power feeding - +a prompt maintenance alarm should be generated, if practicable. +- b) low error ratio threshold exceeded - +this threshold is $1 \cdot 10^{-5}$ for systems at 2048 and 8448 kbit/s +and $1 \cdot 10^{-6}$ for systems at higher bit rates; + +a deferred maintenance alarm should be generated to signify that performance is deteriorating. + +## ANNEX A + +(to Recommendation G.952) + +### Definition and measurement of repeaters crosstalk-noise figures + +#### A.1 Definition + +- a) NEXT-Noise Figure $[R_N]$ + +$$[R_N] = [I_N] - [N_0]$$ + +$$I_N = \int_0^{\infty} |f/f_0|^{3/2} |E(f)|^2 P(f) df$$ + +$I_N$ = mean square near-end crosstalk (NEXT) voltage produced by a single interfering regenerator that would appear at the decision point if the NEXT loss were 0 dB at half the line system baud rate. + +$N_0$ = mean square NEXT interference voltage at decision point which procedures specified BER, and depends on parameters which affect the decision process and reflects impairments arising from intersymbol interference and offsets from the optimum position of the decision threshold levels and sampling instants at the regenerator decision point. + +$E(f)$ = regenerator equalizer frequency transfer function. + +$P(f)$ = power spectral density (single sided) of line system line code. + +$f_0$ = half line system baud rate. + +and quantities in square brackets are in dB, i.e. + +$[X] = 10 \log_{10} |X|$ . + +b) FEXT-Noise Figure $[R_F]$ + +$$[R_F] = [I_F] - [N_0]$$ + +$$I_F = \int_0^{\infty} |f/f_0|^2 |E(f)|^2 |G(f)|^2 P(f) df$$ + +$I_F$ = mean square far-end crosstalk (FEXT) voltage produced by a single interfering regenerator that would appear at the decision point if the FEXT loss were 0 dB at half the line system baud rate. + +$N_0$ = mean square FEXT interference voltage at decision point which produces specified BER, and depends on parameters which affect the decision process and reflects impairments arising from intersymbol interference and offsets from the optimum position of the decision threshold levels and sampling instants at the regenerator decision points. + +$E(f)$ , $P(f)$ , $f_0$ as in a), and + +$G(f)$ = frequency transfer function of cable. + +#### A.2 Measurement + +Method a) directly relates to the definition of crosstalk-noise figure and is therefore the reference measuring method. Methods b) and c) are the possible practical alternatives. Method c) avoids the use of a selective filter. + +##### Method a) + +The NEXT-Noise Figure and FEXT-Noise Figure can be measured using the configuration shown in Figure A-1/G.952, with the Function Switch in the N and F position, respectively. The measurement consists of equating the r.m.s. voltages at A and A1, setting the artificial line to the desired loss $A_0$ , and then adjusting the variable attenuator until the desired BER = $10^{-x}$ is achieved. The value of the attenuator, $[R]$ dB, is then the NEXT-Noise Figure or FEXT-Noise Figure for the desired $A_0$ and BER. + +![Block diagram of NEXT and FEXT-Noise Figure measurement setup. A test signal passes through a regenerator to point A. At A, it splits: one path goes through a summer, an artificial line, another summer, and a regenerator under test to a bit error ratio meter; the other path goes through a differential RMS meter. A wideband noise source passes through a variable gain amplifier to point A1. At A1, it splits: one path goes through a line code simulating filter and a variable attenuator [R] to a NEXT Network; the other path goes through a FEXT Network. A function switch can connect the FEXT Network output to the first summer at A, or the NEXT Network output to the second summer before the regenerator under test. Labels include [Regenerator]a), Test signal, A, Artificial line, Regenerator under test, Bit error ratio, CCITT-T.54870, f0 = Half clock rate, Differential RMS, FEXT Network, NEXT Network, Wideband noise source, Variable gain amplifier, Line code simulating filter, A1, [R], Variable attenuator, and Function switch with F and N positions.](43fec6623ab9cb223a9ff74e2d2a4402_img.jpg) + +Block diagram of NEXT and FEXT-Noise Figure measurement setup. A test signal passes through a regenerator to point A. At A, it splits: one path goes through a summer, an artificial line, another summer, and a regenerator under test to a bit error ratio meter; the other path goes through a differential RMS meter. A wideband noise source passes through a variable gain amplifier to point A1. At A1, it splits: one path goes through a line code simulating filter and a variable attenuator [R] to a NEXT Network; the other path goes through a FEXT Network. A function switch can connect the FEXT Network output to the first summer at A, or the NEXT Network output to the second summer before the regenerator under test. Labels include [Regenerator]a), Test signal, A, Artificial line, Regenerator under test, Bit error ratio, CCITT-T.54870, f0 = Half clock rate, Differential RMS, FEXT Network, NEXT Network, Wideband noise source, Variable gain amplifier, Line code simulating filter, A1, [R], Variable attenuator, and Function switch with F and N positions. + +a) The regenerator can be omitted if the test signal generator provides the appropriate pulse shape. + +FIGURE A-1/G.952 +NEXT and FEXT-Noise Figure measurement + +##### *Method b)* + +The NEXT-Noise Figure $[R_N]$ can be measured using "input S/N ratio" test sets by employing the test set in a "manual mode" and performing external measurements with a selective filter, see Figure A-2/G.952. The measurement consists of: + +- i) set artificial line to 0 dB and using selective measure test signal power $[S_0]$ dBm. +- ii) Set artificial line to desired loss $A_0$ , adjust variable attenuator until desired BER = $10^{-x}$ is obtained, switch off test signal, and using selective filter, measure noise power $[P]$ dBm. +- iii) Then $[R_N] = [S_0] - [P]$ for desired $A_0$ and BER. + +*Note* - The degrading effect of clock jitter on NEXT-Noise Figure and FEXT-Noise Figure should be measured by superimposing appropriate jitter on the test signal. + +![Block diagram of NEXT-noise figure measurement using input S/N test set. A dashed box labeled 'Input S/N test set "manual mode"' contains a 'Test signal' block, an 'Artificial line' block, a 'Wideband noise' block, a block labeled |P_R(f)|^{1/2} |f/f_0|^{3/2}, and a 'Variable attenuator' block. The test signal and the output of the variable attenuator are summed at a junction. The output of the junction is connected to a 'Regenerator under test' block labeled E(f), which outputs to a 'Bit error ratio' block. The output of the junction is also connected to a 'Selective filter' block labeled F(f), which outputs to a 'True RMS' block. A label f_0 = \text{half clock rate} is present. A label 'Power spectral density P_R(f)' points to the artificial line. A label 'Power spectral density = k P_R(f) |f/f_0|^{3/2}' points to the output of the variable attenuator. The diagram is labeled 'CCITT-54880'.](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg) + +Block diagram of NEXT-noise figure measurement using input S/N test set. A dashed box labeled 'Input S/N test set "manual mode"' contains a 'Test signal' block, an 'Artificial line' block, a 'Wideband noise' block, a block labeled $|P_R(f)|^{1/2} |f/f_0|^{3/2}$ , and a 'Variable attenuator' block. The test signal and the output of the variable attenuator are summed at a junction. The output of the junction is connected to a 'Regenerator under test' block labeled $E(f)$ , which outputs to a 'Bit error ratio' block. The output of the junction is also connected to a 'Selective filter' block labeled $F(f)$ , which outputs to a 'True RMS' block. A label $f_0 = \text{half clock rate}$ is present. A label 'Power spectral density $P_R(f)$ ' points to the artificial line. A label 'Power spectral density $= k P_R(f) |f/f_0|^{3/2}$ ' points to the output of the variable attenuator. The diagram is labeled 'CCITT-54880'. + +FIGURE A-2/G.952 + +NEXT-noise figure measurement using input S/N test set + +##### *Method c)* + +The NEXT-Noise Figure $[R_N]$ can be measured using "input S/N ratio" test sets in "manual mode" with the insertion of an additional variable attenuator between the test signal and the artificial line, as shown in Figure A-3/G.952. + +The measurement procedure is as follows: + +- i) set the artificial line to 0 dB loss and the additional variable attenuator to $A$ dB loss; +- ii) regulate the variable gain amplifier until the power level of the variable attenuator input is equal to $[Q1] - A$ dB, the power level of the artificial line output; +- iii) set the artificial line to $A$ dB loss and the additional variable attenuator to 0 dB loss; +- iv) adjust the variable attenuator until the desired BER = $10^{-x}$ is reached. The attenuation value of the attenuator is $[\alpha N]$ dB; +- v) calculate $[R_N] = [\alpha N] + A - [W_N]$ + +$$\text{where } [W_N] = 10 \log_{10} \left[ \int_0^\infty P_R(f) df / \int_0^\infty \left| \frac{f}{f_0} \right|^{3/2} P_R(f) df \right]$$ + +in which $P_R(f)$ = spectral power density (single sided) of line code. + +In would be better to obtain $W_N$ by measurement. Of course, the value of $W_N$ can also be calculated according to $P_R(f)$ of AMI or HDB3 in a certain frequency range, for example, $W_N = -3.59$ dB in the range from 0 to 10 240 kHz. + +![Block diagram of NEXT-noise figure measurement using input S/N test set. The diagram shows a 'Test signal' passing through a 'Power level [Q]' point and an 'Additional variable attenuator' (A or 0). This signal enters a dashed box labeled 'Input S/N test set ](2ee59e629035d641140e55f4d215b0d7_img.jpg) + +Block diagram of NEXT-noise figure measurement using input S/N test set. The diagram shows a 'Test signal' passing through a 'Power level [Q]' point and an 'Additional variable attenuator' (A or 0). This signal enters a dashed box labeled 'Input S/N test set + +FIGURE A-3/G.952 + +**NEXT-noise figure measurement using input S/N test set** + +## ANNEX B + +(to Recommendation G.952) + +### Guidance notes for the satisfactory achievement of the error performance objectives + +B.1 To comply with the Network Performance Objectives (NPO) it is necessary to take into account many interrelated factors. Figure B-1/G.952 illustrates diagrammatically the interrelationship between all the factors that impact on this matter. The basis upon which digital line system installation planning guidelines are formulated is dependent on the circumstances of each Administration. For example, some Administrations may have cables with favourable characteristics, whilst at the same time the network may experience serious levels of unquantifiable interference (network effects). An Administration must, therefore, make a judgment as to the significance of each effect in their network and formulate cable utilization guidelines which satisfy the digital line section error performance requirements. + +![Flowchart showing factors impacting on the error performance of a digital line system on symmetrical pairs. The central box is 'Cable fill calculations and/or repeaters spacing calculations'. Above it, 'Range of repeater variable gain', 'Repeater crosstalk noise figure', 'Synchronous/plesiochronous factors', 'Cable characteristics', and 'Installation planning factors' all point to it. Below it, 'Equipment design objective for digital line system' points to it. To the left, 'Other sources of quantifiable interference' points to it. To the right, 'Jitter influence' points to it. Below 'Equipment design objective for digital line system', 'Network performance objective for digital section' and 'Network effects (i.e. an allowance for unquantifiable extraneous interference)' both point to it. The diagram is labeled CCITT-S0331.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +``` + +graph TD + subgraph Top + direction TB + R[Range of repeater variable gain] + RC[Repeater crosstalk noise figure] + SF[Synchronous/plesiochronous factors] + C[Cable characteristics] + IF[Installation planning factors] + end + subgraph Bottom + direction BT + NP[Network performance objective for digital section] + NE[Network effects i.e. an allowance for unquantifiable extraneous interference] + ED[Equipment design objective for digital line system] + end + OS[Other sources of quantifiable interference] + J[Jitter influence] + CF[Cable fill calculations and/or repeaters spacing calculations] + + R --> CF + RC --> CF + SF --> CF + C --> CF + IF --> CF + NP --> ED + NE --> ED + ED --> CF + OS --> CF + J --> CF + +``` + +CCITT-S0331 + +Flowchart showing factors impacting on the error performance of a digital line system on symmetrical pairs. The central box is 'Cable fill calculations and/or repeaters spacing calculations'. Above it, 'Range of repeater variable gain', 'Repeater crosstalk noise figure', 'Synchronous/plesiochronous factors', 'Cable characteristics', and 'Installation planning factors' all point to it. Below it, 'Equipment design objective for digital line system' points to it. To the left, 'Other sources of quantifiable interference' points to it. To the right, 'Jitter influence' points to it. Below 'Equipment design objective for digital line system', 'Network performance objective for digital section' and 'Network effects (i.e. an allowance for unquantifiable extraneous interference)' both point to it. The diagram is labeled CCITT-S0331. + +FIGURE B-1/G.952 + +Factors impacting on the error performance of a digital line system on symmetrical pairs + +The following notes highlight a number of important considerations concerning the formulation of system installation planning guidelines. + +*Note 1* - In the process of establishing cable utilization guidelines the crosstalk-noise figure is the only parameter describing the intrinsic quality of the regenerator under crosstalk interference conditions. This parameter, which is based on the *average* power spectral density of the total crosstalk interference, provides a useful approximation to the system's immunity to crosstalk from plesiochronous data streams, and is the correct measure for synchronous data streams provided the phases of the disturbing systems are randomized. It is also based on an assumption of random data on the disturbing systems and therefore cannot be applied to the case of repetitive data patterns. However the use of scramblers effectively makes almost all data patterns appear to be random [3]. + +*Note 2* - In an operational environment, regenerators may be subject to other sources of interference which are difficult to quantify and which may induce errors. In some instances specific interference mechanisms have been quantified and appropriate limits and testing procedures are reflected in national specifications. These aspects are currently under study within CCITT and as operational experience is gained it might be possible to introduce further tests that accommodate these other interference mechanisms. + +*Note 3* - Maximum cable utilization should be based on complying with the network performance objective. To satisfy this objective Administrations may adopt one of the following approaches: + +- i) In circumstances where Administrations are able to judge the significance of the "network effects" cable fill calculations should be based on an objective determined by discounting "network effects" from the network performance objective. +- ii) In circumstances where Administrations are not able to judge the significance of the network effects, cable fill calculations should be based on the equipment design objective. + +*Note 4* - The use of a reduced line symbol rate code provides a more favourable crosstalk environment, and this feature will impact on cable fill calculations. + +*Note 5* - When changing from a plesiochronous to a synchronous network operation, some cable crosstalk couplings and relative phasings of the system clocks lead to increases in system margins whilst others lead to reduced system margins by up to a maximum of 3 dB for practical systems. It is believed that there are more cases with increased margin than reduced margin and that there is therefore no need to introduce any extra margin when changing from plesiochronous to synchronous operations [3]. + +Scramblers may be used to ensure that the interference from several identical repetitive sequences does not exceed the levels occurring with random data. + +## References + +- [1] CCITT Manual *Directives concerning the protection of telecommunication lines against harmful effects from electric power and electrified railway lines*, ITU, Geneva, 1988. +- [2] CCITT Recommendation *Tests on power-fed repeaters using solid state devices in order to check the arrangements for protection from external interference*, Vol. IX, Rec. K.17. +- [3] SMITH, B.M. and POTTER, P. G. [June 1986] - Design Criteria for Crosstalk Interference between Digital Signals in Multipair Cable, *IEEE Trans. Commun.*, Vol. COM-34, No. 6. \ No newline at end of file diff --git a/marked/G/T-REC-G.961-199303-I_PDF-E/raw.md b/marked/G/T-REC-G.961-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d027475c3f48d62e64dd004352873b1c5a9e593a --- /dev/null +++ b/marked/G/T-REC-G.961-199303-I_PDF-E/raw.md @@ -0,0 +1,4893 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.961** + +(03/93) + +**DIGITAL SECTIONS AND DIGITAL LINE SYSTEMS** + +--- + +**DIGITAL TRANSMISSION SYSTEM ON +METALLIC LOCAL LINES FOR ISDN +BASIC RATE ACCESS** + +**ITU-T Recommendation G.961** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +ITU-T Recommendation G.961 was revised by the ITU-T Study Group XVIII (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). + +--- + +# NOTES + +1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. + +In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. + +2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +*Page* + +| | | | +|------------|--------------------------------------------------------------------|----| +| 1 | General ..... | 1 | +| 1.1 | Scope ..... | 1 | +| 1.2 | Definition..... | 1 | +| 1.3 | Objectives ..... | 2 | +| 1.4 | Abbreviations..... | 2 | +| 2 | Functions..... | 3 | +| 2.1 | B-channel..... | 3 | +| 2.2 | D-channel..... | 3 | +| 2.3 | Bit timing..... | 3 | +| 2.4 | Octet timing ..... | 3 | +| 2.5 | Frame alignment ..... | 4 | +| 2.6 | Activation from LT or NT1 ..... | 4 | +| 2.7 | Deactivation..... | 4 | +| 2.8 | Power feeding..... | 4 | +| 2.9 | Operations and maintenance..... | 4 | +| 3 | Transmission medium ..... | 4 | +| 3.1 | Description..... | 4 | +| 3.2 | Minimum ISDN requirements ..... | 5 | +| 3.3 | DLL physical characteristics ..... | 5 | +| 3.4 | DLL electrical characteristics ..... | 5 | +| 4 | System performance..... | 8 | +| 4.1 | Performance requirements..... | 8 | +| 4.2 | Performance measurements ..... | 8 | +| 5 | Transmission method ..... | 13 | +| 6 | Activation/deactivation ..... | 14 | +| 6.1 | General..... | 14 | +| 6.2 | Physical representation of signals..... | 14 | +| 7 | Operation and maintenance..... | 14 | +| 7.1 | Operation and maintenance functions..... | 14 | +| 7.2 | C L channel..... | 14 | +| 7.3 | Transfer mode of operation and maintenance links ..... | 14 | +| 8 | Power feeding..... | 15 | +| 8.1 | General..... | 15 | +| 8.2 | Power feeding options ..... | 15 | +| 8.3 | Power feeding and recovery methods..... | 15 | +| 8.4 | DLL resistance..... | 15 | +| 8.5 | Wetting current ..... | 15 | +| 8.6 | LT aspects..... | 17 | +| 8.7 | Power requirements of NT1 and regenerator..... | 17 | +| 8.8 | Current transient limitation..... | 17 | +| 9 | Environmental conditions ..... | 17 | +| 9.1 | Climatic conditions..... | 17 | +| 9.2 | Protection..... | 17 | +| 9.3 | Electromagnetic compatibility ..... | 18 | +| Appendix I | – Electrical characteristics of an MMS 43 transmission system..... | 18 | +| I.1 | Line code ..... | 18 | +| I.2 | Symbol rate..... | 19 | + +| | Page | | +|----------------------------------------------------------------------------------------------|--------------------------------------------------------|-----| +| I.3 | Frame structure ..... | 19 | +| I.4 | Frame word ..... | 19 | +| I.5 | Frame alignment procedure ..... | 19 | +| I.6 | Multiframe ..... | 20 | +| I.7 | Frame offset at NT1 ..... | 20 | +| I.8 | C L - channel ..... | 20 | +| I.9 | Scrambling ..... | 20 | +| I.10 | Activation/deactivation ..... | 21 | +| I.11 | Jitter ..... | 29 | +| I.12 | Transmitter output characteristics ..... | 30 | +| I.13 | Transmitter/receiver termination ..... | 30 | +| Annex A – Extension functions and requirements for a line system with MMS 43 line code ..... | | 33 | +| Appendix II – Core requirements for a system using 2B1Q line code ..... | | 33 | +| II.1 | Line code ..... | 33 | +| II.2 | Line baud rate ..... | 33 | +| II.3 | Frame structure ..... | 34 | +| II.4 | Frame word ..... | 34 | +| II.5 | Frame alignment procedure ..... | 35 | +| II.6 | Multiframe ..... | 35 | +| II.7 | Frame offset between LT-NT1 and NT1-LT frames ..... | 35 | +| II.8 | C L -channel ..... | 35 | +| II.9 | Scrambling ..... | 43 | +| II.10 | Start-up and control ..... | 43 | +| II.11 | Jitter ..... | 60 | +| II.12 | Transmitter output characteristics of NT1 and LT ..... | 61 | +| II.13 | Transmitter/receiver termination ..... | 63 | +| Annex A – Extension functions of the system using 2B1Q line code ..... | | 66 | +| Appendix III – Core functions and requirements for a line system using a TCM method ..... | | 81 | +| III.1 | Line code ..... | 81 | +| III.2 | Line baud rate ..... | 82 | +| III.3 | Frame structure ..... | 82 | +| III.4 | Frame word ..... | 82 | +| III.5 | Frame alignment procedure ..... | 86 | +| III.6 | Multiframe ..... | 86 | +| III.7 | Frame offset between LT-NT1 and NT1-LT frames ..... | 86 | +| III.8 | C L -channel ..... | 89 | +| III.9 | Scrambling ..... | 92 | +| III.10 | Activation/deactivation ..... | 92 | +| III.11 | Jitter ..... | 113 | +| III.12 | Transmitter output characteristics of NT1 and LT ..... | 114 | +| III.13 | Transmitter/receiver termination ..... | 116 | +| Annex A – Extension functions and requirements for a line system using a TCM method ..... | | 118 | +| Appendix IV – Basic access transmission system using SU32 line code ..... | | 120 | +| IV.0 | General ..... | 120 | +| IV.1 | Line code ..... | 120 | +| IV.2 | Symbol rate ..... | 120 | +| IV.3 | Frame structure ..... | 121 | +| IV.4 | Frame word ..... | 122 | +| IV.5 | Frame alignment procedure ..... | 123 | +| IV.6 | Multiframe ..... | 123 | +| IV.7 | Frame offset between LT-NT1 and NT1-LT frames ..... | 123 | +| IV.8 | C L -channel ..... | 123 | +| IV.9 | Scrambling ..... | 125 | + +| | Page | +|---------------------------------------------------------------|-------------| +| IV.10 Activation/deactivation ..... | 125 | +| IV.11 Jitter ..... | 132 | +| IV.12 Transmitter output characteristic of the NT or LT ..... | 132 | +| IV.13 Transmitter/receiver termination ..... | 134 | + +# **DIGITAL TRANSMISSION SYSTEM ON METALLIC LOCAL LINES FOR ISDN BASIC RATE ACCESS** + +*(Melbourne, 1988, revised in Helsinki, 1993)* + +# **1 General** + +## **1.1 Scope** + +This Recommendation covers the characteristics and parameters of a digital transmission system at the network side of the NT1 to form part of the access digital section for the ISDN basic rate access. The specification of transmission system characteristics at the network side of the NT1 does not correspond to a reference point defined in the reference configuration for ISDN user-network interfaces in Recommendation I.411. + +The system will support the + +- full duplex; +- bit sequence independent + +transmission of two B-channels and one D-channel as defined in Recommendation I.412 and the supplementary functions of the access digital section defined in Recommendation I.603 for operation and maintenance. + +This Recommendation describes 4 transmission systems using different line codes and transmission methods. They are given in Appendices I to IV as examples following the understanding that only one system should be recommended and provided in an annex to this Recommendation when this is achieved in future. + +NOTE – The main aspects which have made it impossible to achieve this objective are for example: + +- local line electrical conditions; +- maintenance requirements and line testing; +- EMC requirements; +- safety and protection requirements; +- local network evolution aspects. + +The individual appendices to this Recommendation distinguish core specifications from extension specifications. The extension specifications are given in an annex to the relevant appendix. + +The core specifications consist of those aspects which are expected to be common to all applications using a particular type of transmission technique. They correspond to the functions usually provided within typical VLSI transceiver integrated circuits or are associated with the transmission characteristics at the 2-wire port. + +The extension functions generally correspond to NT/LT functions which are in some cases provided external to the transceiver integrated circuits. Where a definition of an extension function is provided and the application is specified in the relevant annex it is strongly recommended that the application is not changed unless there is a need to change the definition of the function itself. + +The terminology used in this Recommendation is contained in Recommendations I.112 and G.701. + +## **1.2 Definition** + +Figure 1 shows the boundaries of the digital transmission system in relation to the access digital section. + +The concept of the access digital section is used in order to allow a functional and procedural description and a definition of the network requirements. Note that the reference points T and V1 are not identical and therefore the access digital section is not symmetric. + +The concept of a digital transmission system is used in order to describe the characteristics of an implementation, using a specific medium, in support of the access digital section. + +![Diagram showing the boundaries of a digital transmission system and an access digital section. The diagram includes four boxes: TE, NT1, LT, and ET. A dashed line connects TE to NT1, and another dashed line connects NT1 to LT. A solid line connects LT to ET. A horizontal double-headed arrow labeled 'Digital transmission system (Note)' spans from the NT1 box to the LT box. A horizontal double-headed arrow labeled 'Access digital section' spans from a 'Reference point T' (located between TE and NT1) to a 'Reference point V1' (located between LT and ET). The text 'T1814280-92/d01' is in the bottom right corner.](fc46871d72c65d3381d9201646d23439_img.jpg) + +Diagram showing the boundaries of a digital transmission system and an access digital section. The diagram includes four boxes: TE, NT1, LT, and ET. A dashed line connects TE to NT1, and another dashed line connects NT1 to LT. A solid line connects LT to ET. A horizontal double-headed arrow labeled 'Digital transmission system (Note)' spans from the NT1 box to the LT box. A horizontal double-headed arrow labeled 'Access digital section' spans from a 'Reference point T' (located between TE and NT1) to a 'Reference point V1' (located between LT and ET). The text 'T1814280-92/d01' is in the bottom right corner. + +NOTE – In this Recommendation digital transmission system refers to a line system using metallic lines. The use of one intermediate regenerator may be required. + +FIGURE 1/G.961 + +### **Access digital section and transmission system boundaries** + +## 1.3 Objectives + +Considering that the access digital section between the local exchange and the customer is one key element of the successful introduction of ISDN into the network the following requirements for the specification have been taken into account: + +- to meet the error performance specified in Recommendation G.960; +- to operate on existing 2-wire unloaded lines, open wires being excluded; +- the objective is to achieve 100% cable fill for ISDN basic access without pair selection, cable rearrangements or removal of bridged taps (BT) which exist in many networks; +- the objective to be able to extend ISDN basic access provided services to the majority of customers without the use of regenerators. In the remaining few cases special arrangements may be required; +- coexistence in the same cable unit with most of the existing services like telephony and voice band data transmission; +- various national regulations concerning EMI should be taken into account; +- power feeding from the network under normal or restricted conditions via the basic access shall be provided where the Administration provides this facility; +- the capability to support maintenance functions shall be provided. + +## 1.4 Abbreviations + +A number of abbreviations are used in this Recommendation. Some of them are commonly used in the ISDN reference configuration while others are created only for this Recommendation. The latter are given below: + +| | | +|----------------|--------------------------------------------------------------------------------| +| BER | bit error ratio | +| BT | bridged tap | +| CISPR | Comité international spécial de perturbation radioélectrique (now part of IEC) | +| C L | control channel of the line system | +| ECH | echo cancellation | +| EMI | electro-magnetic interference | +| DLL | digital local line | + +| | | +|------|-----------------------------| +| DTS | digital transmission system | +| NEXT | near-end crosstalk | +| PSL | power sum loss | +| TCM | time compression multiplex | +| UI | unit interval | + +## 2 Functions + +Figure 2 shows the functions of the DTS on metallic local lines. + +![Diagram showing the functions of the digital transmission system between an NT1 and an LT. The NT1 side lists functions: 2 B-channels, D channel, Bit timing, Octet timing, Frame alignment, Activation, Deactivation, Power feeding, and Operations and maintenance. Arrows indicate the direction of each function between the NT1 and LT. '2 B-channels', 'D channel', 'Bit timing', 'Octet timing', 'Frame alignment', 'Activation', 'Deactivation', and 'Operations and maintenance' have bidirectional arrows. 'Power feeding' has an arrow pointing from LT to NT1, labeled '(Note 2)'.](d0abac95583b52a3b35f74a215567334_img.jpg) + +| NT1 | | LT | +|----------------------------|------------|----| +| 2 B-channels | ↔ | | +| D channel | ↔ | | +| Bit timing | ↔ | | +| Octet timing | ↔ | | +| Frame alignment | ↔ | | +| Activation | ↔ | | +| Deactivation | ↔ | | +| Power feeding | ← (Note 2) | | +| Operations and maintenance | ↔ | | + +T1820120-93/d02 + +Diagram showing the functions of the digital transmission system between an NT1 and an LT. The NT1 side lists functions: 2 B-channels, D channel, Bit timing, Octet timing, Frame alignment, Activation, Deactivation, Power feeding, and Operations and maintenance. Arrows indicate the direction of each function between the NT1 and LT. '2 B-channels', 'D channel', 'Bit timing', 'Octet timing', 'Frame alignment', 'Activation', 'Deactivation', and 'Operations and maintenance' have bidirectional arrows. 'Power feeding' has an arrow pointing from LT to NT1, labeled '(Note 2)'. + +#### NOTES + +- 1 The optional use of one regenerator must be foreseen. +- 2 This function is optional. + +FIGURE 2/G.961 +**Functions of the digital transmission system** + +## 2.1 B-channel + +This function provides, for each direction of transmission, two independent 64 kbit/s channels for use as B-channels (as defined in Recommendation I.412). + +### 2.2 D-channel + +This function provides, for each direction of transmission, one D-channel at a bit rate of 16 kbit/s, (as defined in Recommendation I.412). + +### 2.3 Bit timing + +This function provides bit (signal element) timing to enable the receiving equipment to recover information from the aggregate bit stream. Bit timing for the direction NT1 to LT shall be derived from the clock received by the NT1 from the LT. + +### 2.4 Octet timing + +This function provides 8 kHz octet timing for the B-channels. It shall be derived from frame alignment. + +### 2.5 Frame alignment + +This function enables the NT1 and the LT to recover the time division multiplexed channels. + +### 2.6 Activation from LT or NT1 + +This function restores the DTS between the LT and NT1 to its normal operational status. Procedures required to implement this function are described in 6. + +Activation from the LT could apply to the access digital section only (partial activation) or to the access digital section plus the customer equipment. In case the customer equipment is not connected, the access digital section can still be activated. + +NOTE – The functions required for operation and maintenance of the NT1 and one regenerator (if required) and for some activation/deactivation procedures are combined in one transport capability to be transmitted along with the 2B + D-channels. This transport capability is named the $C_L$ -channel. + +### 2.7 Deactivation + +This function is specified in order to permit the NT1 and the regenerator (if it exists) to be placed in a low power consumption mode or to reduce intrasystem crosstalk to other systems. The procedures and exchange of information are described in 6. This deactivation can only be initiated by the exchange (ET). See also note to 2.6. + +### 2.8 Power feeding + +This optional function provides for remote power feeding of one regenerator (if required) and NT1. The provision of wetting current is recommended (see 8.5). + +NOTE – The provision of line feed power to the user-network interface, normal or restricted power feeding as defined in Recommendation I.430 is required by some Administrations. + +### 2.9 Operations and maintenance + +This function provides the recommended actions and information described in Recommendation I.603. + +The following categories of functions have been identified: + +- maintenance command (e.g. loopback control in the regenerator or the NT1); +- maintenance information (e.g. line errors); +- indication of fault conditions; +- information regarding power feeding in NT1. + +See Note to 2.6. + +# 3 Transmission medium + +## 3.1 Description + +The transmission medium over which the DTS is expected to operate, is the local line distribution network. + +A local line distribution network employs cables of pairs to provide services to customers. + +In a local line distribution network, customers are connected to the local exchange via local lines. + +A metallic local line is expected to be able to simultaneously carry bi-directional digital transmission providing ISDN basic access between LT and NT1. + +To simplify the provision of ISDN basic access, a DTS must be capable of satisfactory operation over the majority of metallic local lines without requirement of any special conditioning. Maximum penetration of metallic local lines is obtained by keeping ISDN requirements at a minimum. + +In the following, the term Digital Local Line (DLL) is used to describe a metallic local line that meets minimum ISDN requirements. + +## 3.2 Minimum ISDN requirements + +- No loading coils. +- No open wires. +- When BTs are present, some restrictions may apply. Typical allowable BT configurations are discussed in 4.2.1. + +## 3.3 DLL physical characteristics + +In addition to satisfying the minimum ISDN requirements, a DLL is typically constructed of one or more twisted-pair segments that are spliced together. In a typical local line distribution network, these twisted-pair segments occur in different types of cables as described in Figure 3. + +![Diagram of the DLL physical model showing the connection between an NT1 and an LT through various cable segments and connection points.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +The diagram illustrates the physical model of a Digital Loop (DLL). It shows a sequence of components connected in series from left to right: an NT1 (Network Termination 1) unit, an 'Installation cable', a 'Cross-connect point', a 'Distribution cable', another 'Cross-connect point', a 'Main cable', a 'Main distribution frame', and an 'LT' (Line Termination) unit. An 'Exchange cable' is shown branching off from the 'Main cable' before the 'Main distribution frame'. The diagram is labeled with 'T1820130-93/d03' near the LT unit. + +Diagram of the DLL physical model showing the connection between an NT1 and an LT through various cable segments and connection points. + +FIGURE 3/G.961 +DLL physical model + +## 3.4 DLL electrical characteristics + +### 3.4.1 Insertion loss + +The DLL will have non-linear loss versus frequency characteristic. For any DLL of a particular gauge mix, with no BTs and with an insertion loss of $x$ dB at 80 kHz, the typical behaviour of its insertion loss versus frequency is depicted in Figure 4. + +### 3.4.2 Group delay + +Typical ranges of values of DLL group delay as a function of frequency are shown in Figure 5. + +### 3.4.3 Characteristic impedance + +Typical ranges of values of the real and imaginary parts of the characteristic impedance of twisted pairs in different types of cables are shown in Figure 6. + +### 3.4.4 Near-end crosstalk (NEXT) + +The DLL will have finite crosstalk coupling loss to other pairs sharing the same cable. Worst-case NEXT power sum loss (PSL) varies from 44 to 57 dB at 80 kHz (refer to 4.2.2). + +The DLL loss and PSL ranges have been independently specified. However, it is not required that all points in both ranges be satisfied simultaneously. A combined DLL loss/PSL representation is shown in Figure 7 to define the combined range of operation. + +### 3.4.5 Unbalance about earth + +The DLL will have finite balance about earth. Unbalance about earth is described in terms of longitudinal conversion loss. Worst-case values are shown in Figure 8. + +![Figure 4/G.961: Typical insertion loss characteristic without presence of BTs. The graph plots DLL loss (linear scale) in dB on the y-axis against Frequency (log scale) in kHz on the x-axis. The y-axis has labels 0.25x, 0.50x, 0.75x, x, 1.25x, 1.50x, and 1.75x. The x-axis has labels 1, 2, 3, 4, 5, 8, 10, 20, 30, 40, 50, 80, 100, 200, 300 kHz. A shaded region represents the loss range, which is relatively flat around 0.5x from 2 kHz to 80 kHz, and then increases sharply above 80 kHz. A vertical line is drawn at 80 kHz. The text 'T1820140-93/d04' is in the bottom right corner.](d48475a25698b1c0592e4cfe07138f2a_img.jpg) + +Figure 4/G.961: Typical insertion loss characteristic without presence of BTs. The graph plots DLL loss (linear scale) in dB on the y-axis against Frequency (log scale) in kHz on the x-axis. The y-axis has labels 0.25x, 0.50x, 0.75x, x, 1.25x, 1.50x, and 1.75x. The x-axis has labels 1, 2, 3, 4, 5, 8, 10, 20, 30, 40, 50, 80, 100, 200, 300 kHz. A shaded region represents the loss range, which is relatively flat around 0.5x from 2 kHz to 80 kHz, and then increases sharply above 80 kHz. A vertical line is drawn at 80 kHz. The text 'T1820140-93/d04' is in the bottom right corner. + +NOTE – The maximum value of $x$ ranges from 37 dB to 50 dB at 80 kHz. The minimum value could be close to zero. + +FIGURE 4/G.961 +**Typical insertion loss characteristic without presence of BTs** + +![Figure 5/G.961: Typical group delay characteristic. The graph plots DLL group delay (log scale) in μs on the y-axis against Frequency (log scale) in kHz on the x-axis. The y-axis has labels 10⁻¹ T, 1 T, and 10 T. The x-axis has labels 10⁻¹, 1, 10, 80, 100, 1000 kHz. A shaded region represents the group delay range, which starts high (around 10 T) at low frequencies and decreases to a narrow band around 1 T at 80 kHz and above. A vertical line is drawn at 80 kHz. The text 'T1820150-93' is in the bottom right corner.](ff2492be4fa814905acbad18f261b8a5_img.jpg) + +Figure 5/G.961: Typical group delay characteristic. The graph plots DLL group delay (log scale) in μs on the y-axis against Frequency (log scale) in kHz on the x-axis. The y-axis has labels 10⁻¹ T, 1 T, and 10 T. The x-axis has labels 10⁻¹, 1, 10, 80, 100, 1000 kHz. A shaded region represents the group delay range, which starts high (around 10 T) at low frequencies and decreases to a narrow band around 1 T at 80 kHz and above. A vertical line is drawn at 80 kHz. The text 'T1820150-93' is in the bottom right corner. + +NOTE – The maximum value of one-way group delay ( $T$ ) ranges from 30 to 60 microseconds at 80 kHz. + +FIGURE 5/G.961 +**Typical group delay characteristic** + +![Graph showing typical ranges of values of real and imaginary parts of characteristic impedance versus frequency. The y-axis is impedance in Ohms (Ω) on a linear scale from -500 to 500. The x-axis is frequency in kHz on a log scale from 0.1 to 400. The real part ranges from approximately 100 Ω to 500 Ω, and the imaginary part ranges from approximately -500 Ω to 0 Ω. The graph is labeled T1820160-93/d06.](36ac3e730a00d3f42d3400f5709f641a_img.jpg) + +Ω + +Real part (linear scale) + +Imaginary part (linear scale) + +500 +400 +300 +200 +100 +0 +-100 +-200 +-300 +-400 +-500 + +0.1 1 10 100 400 kHz + +T1820160-93/d06 + +Frequency (log scale) + +Graph showing typical ranges of values of real and imaginary parts of characteristic impedance versus frequency. The y-axis is impedance in Ohms (Ω) on a linear scale from -500 to 500. The x-axis is frequency in kHz on a log scale from 0.1 to 400. The real part ranges from approximately 100 Ω to 500 Ω, and the imaginary part ranges from approximately -500 Ω to 0 Ω. The graph is labeled T1820160-93/d06. + +FIGURE 6/G.961 +Typical ranges of values of real and imaginary parts +of characteristic impedance + +![Graph showing the combined representation of DLL loss/PSL range of operation. The y-axis is DLL loss at 80 kHz in dB on a linear scale from 0 to 50. The x-axis is Power sum loss at 80 kHz in dB on a linear scale from 0 to 57. The graph shows a shaded region representing the combined DLL loss/PSL range of operation, bounded by a dashed line and a solid line. The graph is labeled T1820170-93/d07.](f176174c2978785e86a8352bd45e322e_img.jpg) + +dB + +50 + +DLL loss at 80 kHz (linear scale) + +37 + +Combined DLL loss/PSL range of operation + +0 44 57 dB + +(linear scale) + +T1820170-93/d07 + +Power sum loss at 80 kHz + +Graph showing the combined representation of DLL loss/PSL range of operation. The y-axis is DLL loss at 80 kHz in dB on a linear scale from 0 to 50. The x-axis is Power sum loss at 80 kHz in dB on a linear scale from 0 to 57. The graph shows a shaded region representing the combined DLL loss/PSL range of operation, bounded by a dashed line and a solid line. The graph is labeled T1820170-93/d07. + +FIGURE 7/G.961 +Combined representation of DLL loss/PSL range of operation + +![Figure 8/G.961: Worst-case longitudinal conversion loss versus frequency. The graph shows a linear decrease in conversion loss (dB) as frequency (kHz) increases on a log scale. The y-axis is labeled 'dB' and 'Longitudinal conversion loss (linear scale)'. The x-axis is labeled 'Frequency (log scale)' and has markers at 8, 80, and 800 kHz. A horizontal dashed line at 44 dB intersects the vertical dashed line at 80 kHz. A solid line with a 'Slope 5 dB/decade' starts at 8 kHz and decreases. The text 'T1820180-93/d08' is in the bottom right corner.](dd0f5301a5a6dd7c319701302110de88_img.jpg) + +Figure 8/G.961: Worst-case longitudinal conversion loss versus frequency. The graph shows a linear decrease in conversion loss (dB) as frequency (kHz) increases on a log scale. The y-axis is labeled 'dB' and 'Longitudinal conversion loss (linear scale)'. The x-axis is labeled 'Frequency (log scale)' and has markers at 8, 80, and 800 kHz. A horizontal dashed line at 44 dB intersects the vertical dashed line at 80 kHz. A solid line with a 'Slope 5 dB/decade' starts at 8 kHz and decreases. The text 'T1820180-93/d08' is in the bottom right corner. + +FIGURE 8/G.961 +**Worst-case longitudinal conversion loss versus frequency** + +### 3.4.6 Impulse noise + +The DLL will have impulse noise resulting from other systems sharing the same cable as well as from other sources. + +## 4 System performance + +## 4.1 Performance requirements + +Performance limits for the access digital section are specified in 4/G.960. The DTS performance must be such that these performance limits are met. For that purpose, a DTS is required to pass specific laboratory performance tests that are defined in the next subclauses. + +## 4.2 Performance measurements + +Laboratory performance measurement of a particular DTS requires the following preparations: + +- definition of a number of DLL models to represent physical and electrical characteristics encountered in local line distribution networks; +- simulation of the electrical environment caused by finite crosstalk coupling loss to other pairs in the same cable; +- simulation of the electrical environment caused by impulse noise; +- specification of laboratory performance tests to verify that the performance limits referred to in 4.1 will be met. + +### 4.2.1 DLL physical models + +For the purposes of laboratory testing of performance of a DTS providing ISDN basic access, some models representative of DLLs to be encountered in a particular local line distribution network are required. The maximum loss in each model is optionally set between 37 and 50 dB at 80 kHz to satisfy requirements of the particular network. Similarly, the lengths of BTs are optionally set within the range defined in Figure 9. + +![Diagram showing six physical models (a-f) for DLL laboratory testing. Each model is a horizontal line representing a cable with specific length and gauge segments. Model a) is 0.0 dB. Model b) is x dB with a gauge of 0.4, 0.5, or 0.6 mm. Model c) consists of four segments: 0.25x dB (0.4 mm), 0.25x dB (0.5 mm), 0.25x dB (0.6 mm), and 0.25x dB (0.4 mm). Model d) consists of three segments: 0.05x dB (0.4 mm), 0.9x dB (0.6 or 0.8 mm), and 0.05x dB (0.4 mm). Model e) consists of three segments: 0.2x dB (0.4 mm), 0.4x dB (0.4 mm), and 0.2x dB (0.4 mm), with three bridge taps (BT1, BT2, BT3) of 0-0.5 km/0.4mm. Model f) consists of three segments: 0.5x dB (0.4 mm), 0.2x dB (0.5 mm), and 0.1x dB (0.6 mm), with five bridge taps (BT1-BT5) of varying lengths and gauges. A reference code T1820190-93/d09 is present.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +a) 0.0 dB + +b) $x$ dB +0.4, 0.5 or 0.6 mm + +c) $0.25x$ dB (0.4 mm) | $0.25x$ dB (0.5 mm) | $0.25x$ dB (0.6 mm) | $0.25x$ dB (0.4 mm) + +d) $0.05x$ dB (0.4 mm) | $0.9x$ dB (0.6 or 0.8 mm) | $0.05x$ dB (0.4 mm) + +e) $0.2x$ dB (0.4 mm) | $0.4x$ dB (0.4 mm) | $0.2x$ dB (0.4 mm) + BT1 = 0-0.5 km/0.4mm + BT2 = 0-0.5 km/0.4mm + BT3 = 0-0.5 km/0.4mm + +f) $0.5x$ dB (0.4 mm) | $0.2x$ dB (0.5 mm) | $0.1x$ dB (0.6 mm) + BT1 = 0-0.15 km/0.5mm + BT2 = 0-0.3 km/0.5mm + BT3 = 0-0.5 km/0.5mm + BT4 = 0-0.3 km/0.5mm + BT5 = 0-0.15 km/0.5mm + +T1820190-93/d09 + +Diagram showing six physical models (a-f) for DLL laboratory testing. Each model is a horizontal line representing a cable with specific length and gauge segments. Model a) is 0.0 dB. Model b) is x dB with a gauge of 0.4, 0.5, or 0.6 mm. Model c) consists of four segments: 0.25x dB (0.4 mm), 0.25x dB (0.5 mm), 0.25x dB (0.6 mm), and 0.25x dB (0.4 mm). Model d) consists of three segments: 0.05x dB (0.4 mm), 0.9x dB (0.6 or 0.8 mm), and 0.05x dB (0.4 mm). Model e) consists of three segments: 0.2x dB (0.4 mm), 0.4x dB (0.4 mm), and 0.2x dB (0.4 mm), with three bridge taps (BT1, BT2, BT3) of 0-0.5 km/0.4mm. Model f) consists of three segments: 0.5x dB (0.4 mm), 0.2x dB (0.5 mm), and 0.1x dB (0.6 mm), with five bridge taps (BT1-BT5) of varying lengths and gauges. A reference code T1820190-93/d09 is present. + +#### NOTES + +- 1 The value of $x$ varies from 37 to 50 dB at 80 kHz. +- 2 Equivalent gauges can be used. For example 0.6 mm is equivalent to AWG 22. AWG stands for American Wire Gauge. + +FIGURE 9/G.961 +**DLL physical models for laboratory testing** + +### **4.2.2 Intrasystem crosstalk modelling** + +#### **4.2.2.1 Definition of intrasystem crosstalk** + +Crosstalk noise in general results due to finite coupling loss between pairs sharing the same cable, especially those pairs that are physically adjacent. Finite coupling loss between pairs causes a vestige of the signal flowing on one DLL (disturber DLL) to be coupled into an adjacent DLL (disturbed DLL). This vestige is known as crosstalk noise. Near-end crosstalk (NEXT) is assumed to be the dominant type of crosstalk. Intrasystem NEXT or self NEXT results when all pairs interfere with each other in a cable carrying the same DTS. Intersystem NEXT results when pairs carrying different DTSs interfere with each other. Definition of intersystem NEXT is not part of this Recommendation. + +Intrasystem NEXT noise coupled into a disturbed DLL from a number of DLL disturbers is represented as being due to an equivalent single disturber DLL with a coupling loss versus frequency characteristic known as PSL. Worst-case PSL encountered in a local line distribution network is defined in Figure 10. All DLLs are assumed to have fixed resistance terminations of $R_o$ ohms. The range of $R_o$ is 110 to 150 ohms. + +![Figure 10/G.961: Worst-case power sum loss (PSL) graph. The y-axis is PSL (linear scale) in dB, with a value of 44-57 indicated. The x-axis is Frequency (log scale) in kHz, with a value of 80 indicated. A straight line with a slope of 15 dB/decade is shown, passing through the point (80 kHz, 44-57 dB). The graph is labeled T1820200-93/d10.](71ab4df17511d75261da8d462d643b1a_img.jpg) + +Figure 10/G.961: Worst-case power sum loss (PSL) graph. The y-axis is PSL (linear scale) in dB, with a value of 44-57 indicated. The x-axis is Frequency (log scale) in kHz, with a value of 80 indicated. A straight line with a slope of 15 dB/decade is shown, passing through the point (80 kHz, 44-57 dB). The graph is labeled T1820200-93/d10. + +FIGURE 10/G.961 +Worst-case power sum loss (PSL) + +#### 4.2.2.2 Measurement arrangement + +Simulation of intrasystem NEXT noise is necessary for performance testing of DTSs. Intrasystem noise coupled into the receiver of the disturbed DLL depends on: + +- Power spectrum of the transmitted digital signal. The power spectrum is a function of the line code and the transmit filter. +- Spectrum shaping due to the PSL characteristic of Figure 10. + +The measurement arrangement of Figure 11 can be used for testing of performance with intrasystem crosstalk noise. + +![Figure 11/G.961: Crosstalk noise simulation and testing diagram. A central horizontal line labeled 'DLL Under test' connects two boxes labeled 'NT1 or LT' on the left and 'LT or NT1' on the right. Below the right box, a vertical chain of five boxes (numbered 1 to 5) is connected. Box 1 is labeled 'White noise source', box 2 is 'Calibrated attenuator', box 3 is 'Line code and transmit shaping', box 4 is 'Power sum loss shaping', and box 5 is 'Noise insertion circuit'. Arrows indicate the signal flow from box 1 up to box 5, and then into the 'LT or NT1' box. The diagram is labeled T1820210-93/d11.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +Figure 11/G.961: Crosstalk noise simulation and testing diagram. A central horizontal line labeled 'DLL Under test' connects two boxes labeled 'NT1 or LT' on the left and 'LT or NT1' on the right. Below the right box, a vertical chain of five boxes (numbered 1 to 5) is connected. Box 1 is labeled 'White noise source', box 2 is 'Calibrated attenuator', box 3 is 'Line code and transmit shaping', box 4 is 'Power sum loss shaping', and box 5 is 'Noise insertion circuit'. Arrows indicate the signal flow from box 1 up to box 5, and then into the 'LT or NT1' box. The diagram is labeled T1820210-93/d11. + +FIGURE 11/G.961 +Crosstalk noise simulation and testing + +The measurement arrangement in Figure 11 is described in the following: + +- Box 1 represents a white noise source of constant spectral density. Spectrum is flat from 100 Hz to 500 kHz rolling off afterwards at a rate $\geq 20$ dB/decade. +- Box 2 is a variable attenuator. +- Box 3 is a filter that shapes the power spectrum to correspond to a particular line code and a particular transmit filter. + +- d) Box 4 is a filter that shapes the power spectrum according to the PSL characteristic of Figure 10. +- e) Box 5 is a noise insertion circuit which couples the simulated crosstalk noise into the DLL without disturbing its performance. The insertion circuit therefore must be of sufficiently high output impedance relative to the magnitude of the characteristic impedance of the DLL under test. A value of $\geq 4.0$ kohm in the frequency range 0 to 1000 kHz is recommended. + +Boxes 3, 4 and 5 in Figure 11 are conceptual. Depending on the particular realization, they could possibly be combined into one circuit. The measurement arrangement in Figure 11 is calibrated according to the following steps: + +- a) By terminating the output of Box 5 with a resistor of a value of $R_o/2$ ohm, and measuring the true r.m.s. (root-mean-square) voltage across it in a bandwidth extending from 100 Hz to over 500 kHz. The power dissipated in the $R_o/2$ resistor is 3 dB higher than the power coupled into the receiver of the DLL under test. +- b) The shape of the noise spectrum measured across the $R_o/2$ resistor should be within: + - $\pm 1$ dB for values within 0 dB to 10 dB down from the theoretical peak; + - $\pm 3$ dB for values within 10 dB to 20 dB down from the theoretical peak; +for measurement purposes a resolution bandwidth of $\leq 10$ kHz is recommended. +- c) The peak factor of the noise voltage across the $R_o/2$ resistor should be $\geq 4$ . This in turn fixes the dynamic range requirements of the circuits used in the measurement arrangement. + +With the specified calibrated measurement arrangement, intrasystem crosstalk noise due to a worst-case PSL can be injected into the DLL under test while monitoring its performance. The noise level can be increased or decreased to determine positive or negative performance margins. + +### 4.2.3 Impulse noise modelling + +**4.2.3.1 Definition of impulse noise:** Impulse noise energy appears concentrated in random short time intervals during which it attains substantial levels. For the rest of the time impulse noise effects are negligible. The induced noise parameters that should be evaluated are given in Recommendation K.23. + +#### 4.2.3.2 Measurement arrangement + +Figure 12 shows a possible arrangement for impulse noise testing. + +![Block diagram of impulse noise simulation and testing. A horizontal line represents the DLL under test, connecting a box on the left labeled 'NT1 or LT' to a box on the right labeled 'LT or NT1'. A vertical line with an arrow points from a 'Noise insertion circuit' (Box 2) to the line near the right-hand box. Below Box 2, an 'Impulse noise source' (Box 1) points an arrow upward into Box 2. The diagram is labeled T1820220-93.](b90144cfbb81a2d610d920240fda689d_img.jpg) + +``` + +graph TD + subgraph DLL_Under_Test [DLL Under test] + NT1[NT1 or LT] --- LT[LT or NT1] + end + INS[1 Impulse noise source] --> NIC[2 Noise insertion circuit] + NIC --> LT + +``` + +Block diagram of impulse noise simulation and testing. A horizontal line represents the DLL under test, connecting a box on the left labeled 'NT1 or LT' to a box on the right labeled 'LT or NT1'. A vertical line with an arrow points from a 'Noise insertion circuit' (Box 2) to the line near the right-hand box. Below Box 2, an 'Impulse noise source' (Box 1) points an arrow upward into Box 2. The diagram is labeled T1820220-93. + +FIGURE 12/G.961 +**Impulse noise simulation and testing** + +The impulse noise source in Figure 12 is for further study. Two possible classes of impulse noise signals are described in the following: + +- white noise of flat spectral density level of $5-10 \mu\text{V}/\sqrt{\text{Hz}}$ and a bandwidth $> 4$ times the Nyquist frequency of the particular system. The peak factor of the noise must be $> 4$ ; +- a particular waveform, as represented in Figure 13. + +![Figure 13/G.961: Possible waveform to simulate impulse noise. The diagram shows a voltage level versus time plot. The vertical axis is labeled 'Voltage level' with markers for +A, 0, and -A. The horizontal axis is labeled 'Time'. The waveform consists of a rectangular pulse. The pulse width is labeled T1 with a double-headed arrow. The period of the pulse is labeled T2 with a double-headed arrow. The text 'T1820230-93/d13' is at the bottom right of the plot.](f4d72193f77f6646a2a1f4baaa927154_img.jpg) + +Figure 13/G.961: Possible waveform to simulate impulse noise. The diagram shows a voltage level versus time plot. The vertical axis is labeled 'Voltage level' with markers for +A, 0, and -A. The horizontal axis is labeled 'Time'. The waveform consists of a rectangular pulse. The pulse width is labeled T1 with a double-headed arrow. The period of the pulse is labeled T2 with a double-headed arrow. The text 'T1820230-93/d13' is at the bottom right of the plot. + +A Peak level, provisionally set to 100 mV +T1 Pulse width, provisionally set to 3 baud periods +T2 Period $\gg$ T1 + +NOTE – In some local line distribution networks and as a national option, crosstalk noise performance tests are considered sufficient to evaluate a particular digital transmission system. In such cases proper DLL engineering rules are applied to guard against impulse noise. + +FIGURE 13/G.961 +**Possible waveform to simulate impulse noise** + +### 4.2.4 Performance tests + +Five types of tests are required to describe the overall performance of a particular DTS to qualify it for operation over the local line distribution network modelled in this Recommendation. + +#### 4.2.4.1 Dynamic range + +Dynamic range performance describes the ability of a particular DTS to operate with received signals varying in level over a wide range. DLL models a) and b) in Figure 9 have a loss varying from very low (0 dB) to very high (37-50 dB at 80 kHz). + +When testing with DLL models a) and b) in Figure 9, no errors should be observed in any 15 minutes (provisional) measuring interval when monitoring any B-channel. + +Specification of data sequences to be used for this measurement are for further study. + +#### 4.2.4.2 Immunity to echoes + +The remaining DLL models in Figure 9 are used to test performance of DTSs in the presence of BTs and/or diameter changes. + +In each model, no errors should be observed in any 15 minutes (provisional) measuring interval when monitoring any B-channel. + +Specification of data sequences to be used for this measurement are for further study. + +#### 4.2.4.3 Intrasystem crosstalk + +Using the crosstalk arrangement described in 4.2.2.2 with simulated crosstalk noise injected in each DLL model in Figure 9 the observed bit error ratio (BER) should be $\leq 10^{-6}$ (provisional). + +When BER measurements are performed in a B-channel, a measuring interval of at least 15 minutes (provisional) is required. + +In each DLL model, performance margins are determined. Definition of a minimum positive performance margin is left for further study. This is required to account for additional DLL loss due to splices, and environmental effects (e.g. temperature change). + +Specification of data sequences to be used for this measurement are for further study. + +NOTE – With a burst-synchronized TCM transmission method this performance test is not required (see 5). + +#### 4.2.4.4 Impulse noise + +For further study. + +#### 4.2.4.5 Longitudinal voltages induced from power lines + +For further study. + +## 5 Transmission method + +The transmission system provides for duplex transmission on 2-wire metallic local lines. Duplex transmission shall be achieved through the use of Echo Cancellation (ECH) or Time Compression Multiplex (TCM). + +With the ECH method, illustrated in Figure 14, the echo canceller produces a replica of the echo of the transmitted signal that is subtracted from the total received signal. The echo is the result of imperfect balance of the hybrid and impedance discontinuities in the line. The maximum allowable loss of operation for the ECH method generally depends on the noise environment as well as the NEXT PSL. + +![Functional diagram of the ECH method showing two transceivers connected by a 2-wire DLL. Each transceiver contains a transmitter (TX), a receiver (RX), an echo canceller (EC), and a hybrid (HB). The diagram is labeled 'Part of NT1' and 'Part of LT'.](e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg) + +The diagram illustrates the ECH method functional architecture. It consists of two main blocks, 'Part of NT1' on the left and 'Part of LT' on the right, connected by a '2-wire DLL'. Each block contains a transmitter (TX), a receiver (RX), an echo canceller (EC), and a hybrid (HB). In the 'Part of NT1' block, the TX output is connected to the HB, which is connected to the DLL. The HB also receives a signal from the DLL and sends it to the EC. The EC subtracts the transmitted signal (from the TX) from the received signal (from the HB) to cancel the echo. The RX receives the output of the EC. The 'Part of LT' block has a similar architecture. The rate R is indicated for both the input and output of each transceiver. The diagram is labeled 'T1820240-93/d14'. + +Functional diagram of the ECH method showing two transceivers connected by a 2-wire DLL. Each transceiver contains a transmitter (TX), a receiver (RX), an echo canceller (EC), and a hybrid (HB). The diagram is labeled 'Part of NT1' and 'Part of LT'. + +FIGURE 14/G.961 +ECH method functional diagram + +With the TCM or “burst mode” method, illustrated in Figure 15, transmissions on the DLL are separated in time (bursts). Blocks of bits (bursts) are sent alternatively in each direction. Bursts are passed through buffers at each transceiver terminal such that the bit stream at the input and output of the TCM transceiver terminal is continuous at the rate R. The bit rate on the line is required to be greater than 2R to provide for an idle interval between bursts which is necessary to allow for transmission delay and transmitter/receiver turn-around (switching of Sn and Se in Figure 15). The maximum allowable loss of operation for the TCM method generally depends on the noise environment but is independent of the NEXT PSL assuming that the transmitted bursts from the central office are synchronized for systems sharing the same cable. + +This assumption made for the TCM system is based on clearly defined planning rules for installation and operation of the local network to prevent systems with great difference in line loss from using pairs in the same quad or neighbouring quads. Due to the higher frequency spectrum of a TCM system and the high output signal level, greater care must be paid that other transmission systems in the same cable, sensitive in this frequency band, are not effected. + +![Functional diagram of the TCM method showing the internal components of NT1 and LT connected by a 2-wire DLL. The NT1 part includes a TX, RX, BUF, and Sn switch. The LT part includes a RX, BUF, TX, and Se switch. Both sides show 'Rate R' input/output.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +The diagram illustrates the functional architecture of the TCM method. It consists of two main blocks: 'Part of NT1' on the left and 'Part of LT' on the right, connected by a '2-wire DLL'. + Inside the 'Part of NT1' block, an external signal enters a 'BUF' (Buffer) block, which then connects to a 'TX' (Transmitter) block. The 'TX' block is connected to a switch labeled 'Sn'. A return path consists of an 'RX' (Receiver) block connected to the 'Sn' switch, followed by another 'BUF' block. Both the incoming and outgoing paths are bracketed and labeled 'Rate R'. + Inside the 'Part of LT' block, the '2-wire DLL' connects to a switch labeled 'Se'. From 'Se', one path goes to an 'RX' block followed by a 'BUF' block, and the other path goes to a 'TX' block followed by a 'BUF' block. Both outgoing paths are bracketed and labeled 'Rate R'. + Below the diagram is a legend: + TX Transmitter + RX Receiver + EC Echo canceller + HB Hybrid + BUF Buffer + The diagram is identified by the code 'T1820250-93/d15' in the bottom right corner. + +Functional diagram of the TCM method showing the internal components of NT1 and LT connected by a 2-wire DLL. The NT1 part includes a TX, RX, BUF, and Sn switch. The LT part includes a RX, BUF, TX, and Se switch. Both sides show 'Rate R' input/output. + +FIGURE 15/G.961 +**TCM method functional diagram** + +# 6 Activation/deactivation + +## 6.1 General + +The functional capabilities of the activation/deactivation procedure are specified in Recommendation G.960. The transmission system has to meet the requirements specified in Recommendation G.960. In particular, it has to make provision to convey the signals defined in Recommendation G.960 which are required for the support of the procedures. + +## 6.2 Physical representation of signals + +The signals used in the DTS are system-dependent and can be found in the appendices to this Recommendation. + +## 7 Operation and maintenance + +## 7.1 Operation and maintenance functions + +The operation and maintenance functions in the DTS using metallic local lines for the ISDN basic rate access, are defined in Recommendation G.960. + +## 7.2 $C_L$ channel + +**7.2.1 $C_L$ channel definition:** This channel is conveyed by the DTS in both directions between LT and NT1 via a possible regenerator. It is used to transfer information concerning operation, maintenance and activation/deactivation of the DTS and of the access digital section. + +Even though some of these functions have an optional status, the $C_L$ channel shall have the capability to convey the necessary information to perform the function. + +### 7.2.2 $C_L$ channel requirements + +For further study. + +The minimum number of functions (optional or mandatory) the $C_L$ channel should support is for further study. + +## 7.3 Transfer mode of operation and maintenance links + +For further study. + +## 8 Power feeding + +## 8.1 General + +This subclause deals with power feeding of the NT1, one regenerator (if required), and the provision of power to the user-network interface according to Recommendation I.430 under normal and restricted conditions. + +When activation/deactivation procedures are applied, power down modes at the NT1, regenerator (if required) and the LT are defined. + +## 8.2 Power feeding options + +Power feeding options under normal and restricted conditions are considered. For this purpose, a restricted condition is entered after failure of AC mains power at the NT1 location. + +- a) Power feeding of NT1 under normal conditions will be provided using one of the following options: + - AC mains powering; + - remote powering from the network (or via a regenerator, if required). + +In both cases the NT1 may provide power to the user-network interface according to Recommendation I.430. This power is derived from AC mains or remotely from the network. + +- b) Power feeding of NT1 under restricted conditions, when provided, employs one of the following optional sources: + - back-up battery; + - remote powering from the network (or via a regenerator, if required). + +In both cases the NT1 may provide power to the user-network interface according to Recommendation I.430. + +Power feeding options are chosen to satisfy national regulations. + +## 8.3 Power feeding and recovery methods + +Two power feeding and recovery methods are possible and are described in Figure 16. + +When no regenerator is present on the DLL connecting the LT and the NT1, for each case in Figure 16 the power source could be either a constant voltage source with current limiting or a constant current source with voltage limiting. + +When a regenerator is present, both methods of power feeding and recovery in Figure 16 remain applicable. However, when a constant voltage source is used at the LT, the regenerator power sink is connected in parallel to the DLLs and when a constant current source is used at the LT, the regenerator power sink is connected in series with the DLLs. The resulting configurations are shown in Figure 17. + +## 8.4 DLL resistance + +This parameter is a particular subject of the individual local network and therefore out of the scope of this Recommendation. Its maximum value depends on the LT output voltage, the power consumption of the NT1 and regenerator (if required) and the power feeding arrangement for the user-network interface. + +## 8.5 Wetting current + +The NT1 shall provide a DC termination to allow a minimum wetting current to flow (the value has to be defined) including the power down mode or in case of local power feeding of the NT1. + +Wetting current, also known as sealing current, is provided to prevent the degradation of transmission on metallic facilities which may result from the oxidation of wire splices. + +![Circuit diagrams for series and parallel power feeding and recovery. Diagram (a) shows a series method where an LT or NT1 is connected to a power source/sink via a transformer and a capacitor, with a DLL on the output. Diagram (b) shows a parallel method with two capacitors and a transformer, also with a DLL on the output. A note indicates that one capacitor may be sufficient.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +LT +or +NT1 + +DLL + +Power source +or power sink + +(Note) + +T1814290-92/d16 + +Circuit diagrams for series and parallel power feeding and recovery. Diagram (a) shows a series method where an LT or NT1 is connected to a power source/sink via a transformer and a capacitor, with a DLL on the output. Diagram (b) shows a parallel method with two capacitors and a transformer, also with a DLL on the output. A note indicates that one capacitor may be sufficient. + +a) Series power feeding and recovery + +b) Parallel power feeding and recovery + +NOTE – The use of one capacitor may be sufficient as long as the longitudinal conversion loss requirements is satisfied. + +FIGURE 16/G.961 +**Power feeding and recovery methods** + +![Circuit diagram for regenerator powering from a constant voltage source at LT. It shows a regenerator connected to a power sink, with DLLs on both input and output sides.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +DLL + +Power sink + +Circuit diagram for regenerator powering from a constant voltage source at LT. It shows a regenerator connected to a power sink, with DLLs on both input and output sides. + +a) Regenerator powering from constant voltage source at LT + +![Circuit diagram for regenerator powering from a constant current source at LT. It is similar to the previous diagram but represents a constant current source at the LT.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +DLL + +Power sink + +Circuit diagram for regenerator powering from a constant current source at LT. It is similar to the previous diagram but represents a constant current source at the LT. + +b) Regenerator powering from constant current source at LT + +![Circuit diagram for regenerator powering from a constant current source at LT, showing a different configuration with two capacitors and a transformer.](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) + +DLL + +Power sink + +T1820260-93/d17 + +Circuit diagram for regenerator powering from a constant current source at LT, showing a different configuration with two capacitors and a transformer. + +FIGURE 17/G.961 +**Powering at regenerator** + +## 8.6 LT aspects + +A current limitation for voltage source configuration or a voltage limitation for current source configuration is required. The values shall take into account the relevant IEC Publications and national safety regulations. + +According to IEC 449, Amendment 1 (1979) the maximum voltage allowed for transmission systems on local lines is set at 120 V DC. Even in the case of a fault in the power supply the voltage at the LT shall be less than 120 V DC or the limit defined in a national safety regulation. + +The maximum continuous current shall be limited to less than 60 mA. Short-term overflow of the feeding current may be tolerated (charging condition of the capacitor of DC/DC converter in NT1). + +## 8.7 Power requirements of NT1 and regenerator + +### 8.7.1 Power requirements of NT1 + +- Active state without powering of user-network interface according to Recommendation I.430 or when normal mode power is supplied: $\leq 500$ mW. +- Active state including restricted mode powering of the user-network interface as defined in Recommendation I.430: $\leq 1100$ mW. + +The value includes a possible overload or short circuit condition at the user-network interface. + +- Deactivated state without powering of the user-network interface or when normal mode power is supplied: $\leq 120$ mW. + +NOTE – For a time period until the end of 1994, NTs which cannot meet these requirements may consume $\leq 600$ mW for case a) and $\leq 1300$ mW for case b), subject to the safe provision of that power by the LT. + +### 8.7.2 Power requirements of regenerator + +- Active state: $\leq 1000$ mW. +- Deactivated state: $\leq 180$ mW. + +NOTE – For the active state the target value of $\leq 750$ mW should be reached in the long term. + +## 8.8 Current transient limitation + +The rate of change of current drawn by the NT1 or regenerator, when fitted, shall not exceed 1 mA/μs. + +This limit shall apply under all normal operating conditions including activation and deactivation. However, the limit does not apply during initial application of power to the equipment. + +# 9 Environmental conditions + +## 9.1 Climatic conditions + +Climatograms applicable to the operation of NT1 and LT equipment in weather protected and non-weather protected locations can be found in IEC Publication 721-3. The choice of classes is under national responsibility. + +## 9.2 Protection + +### 9.2.1 Isolation + +Isolation between various points at the NT1 can be identified: + +- between line interface and T reference point; +- between line interface or T reference point and AC mains (this is generally defined in IEC Guide 105 and IEC Publication 950 but the test requirements may be different in various countries); +- between line interface and the protective ground of AC mains. + +### 9.2.2 Overvoltage protection + +- To conform with Recommendations K.12, K.20 for LT. +- To conform with Recommendations K.12, K.21 for NT1. + +## 9.3 Electromagnetic compatibility + +### 9.3.1 Susceptibility, radiated and conducted emission levels for LT or NT1 equipment + +This is outside the scope of this Recommendation. CISPR Publication 22 and national regulations have to be considered. + +### 9.3.2 Limitation of the output power to the line + +Due to limited longitudinal conversion, loss of the line at high frequencies and the limitation of radiation according to CISPR Publication 22 and national regulations, the output power shall be limited. The specific values are outside the scope of this Recommendation. + +# Appendix I + +## Electrical characteristics of an MMS 43 transmission system + +(This appendix does not form an integral part of this Recommendation) + +## I.1 Line code + +For each direction of transmission the line code is a Modified Monitoring State Code mapping 4 bits into 3 ternary symbols with levels +, 0 or – (MMS 43). Details of the coding scheme are given in Figure I.1. Note that the numbers in the columns for each of the 4 alphabets S1 . . . S4 give the numbers of the alphabet to be used for the coding of the next block of 4 bits. The bits and symbols standing left are those transmitted or received first. + +| | S1 | S2 | S3 | S4 | +|-------|---------|---------|---------|---------| +| 0001 | 0 - + 1 | 0 - + 2 | 0 - + 3 | 0 - + 4 | +| 0111 | - 0 + 1 | - 0 + 2 | - 0 + 3 | - 0 + 4 | +| 0100 | - + 0 1 | - + 0 2 | - + 0 3 | - + 0 4 | +| 0010 | + - 0 1 | + - 0 2 | + - 0 3 | + - 0 4 | +| 1011 | + 0 - 1 | + 0 - 2 | + 0 - 3 | + 0 - 4 | +| 1110 | 0 + - 1 | 0 + - 2 | 0 + - 3 | 0 + - 4 | +|
| | | | | +| 1001 | + - + 2 | + - + 3 | + - + 4 | - - - 1 | +| 0011 | 0 0 + 2 | 0 0 + 3 | 0 0 + 4 | - - 0 2 | +| 1101 | 0 + 0 2 | 0 + 0 3 | 0 + 0 4 | - 0 - 2 | +| 1000 | + 0 0 2 | + 0 0 3 | + 0 0 4 | 0 - - 2 | +| 0110 | - + + 2 | - + + 3 | - - + 2 | - - + 3 | +| 1010 | + + - 2 | + + - 3 | + - - 2 | + - - 3 | +| 1111 | + + 0 3 | 0 0 - 1 | 0 0 - 2 | 0 0 - 3 | +| 0000 | + 0 + 3 | 0 - 0 1 | 0 - 0 2 | 0 - 0 3 | +| 0101 | 0 + + 3 | - 0 0 1 | - 0 0 2 | - 0 0 3 | +| 1100 | + + + 4 | - + - 1 | - + - 2 | - + - 3 | + +T1814870-02/d18 + +NOTE – A received ternary block 000 is decoded as binary 0000. + +FIGURE I.1/G.961 + +### **MMS 43-Code** + +## **I.2 Symbol rate** + +The symbol rate is 120 kbaud. + +### **I.2.1 Clock symbol requirements** + +#### **I.2.1.1 NT1 free running clock accuracy** + +The tolerance of the free running NT1 clock is $\pm 100$ ppm. + +#### **I.2.1.2 LT clock tolerance** + +The tolerance of the clock signal provided at the LT is $\pm 1$ ppm. + +## **I.3 Frame structure** + +Each frame contains a frame word, 2B + D data and the $C_L$ -channel. Multiframes are not used. + +### **I.3.1 Frame length** + +The length of each frame is 120 ternary symbols corresponding to 1 ms. Each frame has 108 symbols (corresponding to 144 bits) carrying 2B + D data. + +### **I.3.2 Symbol allocation LT to NT1** + +In the direction LT to NT1 the 120 symbols of each frame are used as follows: + +- Symbols 1 to 84: 2B + D; +- Symbol 85: $C_L$ -channel; +- Symbols 86 to 109: 2B + D +- Symbols 110 to 120: frame word. + +The channel allocation to the symbols 1 to 84 and 86 to 109 and the structure of the frame shall be as follows: + +8 consecutive blocks of B1 + B2 + D, in total 144 bits, shall be scrambled and coded into 108 ternary symbols according to Figure I.1. The first B1 channel shall start with symbol number 1. + +After 84 of such coded symbols the $C_L$ -channel-symbol shall be inserted continued with the remaining 24 coded symbols. The 11 symbols forming the frame word shall be added after symbol 109. + +### **I.3.3 Symbol allocation NT1 to LT** + +In the direction NT1 to LT, the frame structure is identical to that of the direction LT to NT1. + +The frame transmitted by the NT1 is synchronized to that received from the LT. + +## **I.4 Frame word** + +### **I.4.1 Frame word in direction LT to NT1** + +The frame word in the direction LT to NT1 is + ++++--++--+- + +### **I.4.2 Frame word in direction NT1 to LT** + +The frame word in the direction NT1 to LT is + +-++--++-+++ + +## **I.5 Frame alignment procedure** + +The transmission system is considered to be synchronous if the frame word has been identified in the same position for 4 immediately succeeding frames. Loss of synchronization is assumed, if the detected frame position does not coincide with the expected position during 60 . . . 200 successive frames. + +## I.6 Multiframe + +Not used. + +## I.7 Frame offset at NT1 + +On the line at the NT1 the frame word transmitted by the NT1 occurs $60 \pm 1$ symbols (0.5 ms) later than that received at the NT1 input, measured between the first symbols of each frame word. + +## I.8 CL- channel + +### I.8.1 Bit rate + +The bit rate for the CL-channel (maintenance-channel) is 1 kbit/s. + +### I.8.2 Structure + +No specific structure is defined for transparent messages. + +### I.8.3 Protocols and procedures + +Transparent messages in the CL-channel use “0” and “-” polarity of the CL-symbol of the line signal. “0” and “+” polarity are used to request a loopback 2B + D in the NT1 or an intermediate repeater. Transparent use of the CL- channel may override these loopback commands. + +Continuous “0” polarity is used as idle code. + +The command/information channel protocol shall use “0” and “+” polarity codings. + +Loopback commands are coded as follows: + +- Loopback 1A activation (in regenerator): continuous “+0”; +- Loopback 2 activation (in NT1): continuous “+”; +- Loopback deactivation: continuous “0”. + +An activation or deactivation command is identified when 8 consecutive symbols according to the coding rule have been detected. + +#### a) *Transmission error detection and report* + +Transmission errors shall be detected by monitoring frames received with one or more line code violations. An errored frame detected by the NT1 shall be reported back to the LT by setting one CL- symbol to “+” polarity. + +#### b) *Transparent channel* + +The transparent channel shall use “-” polarity for ZERO, “0” and “+” polarity shall be interpreted as ONE. “0” or “+” polarity shall be considered as idle code. + +Messages of the transparent channel shall have priority. + +## I.9 Scrambling + +In order to minimize correlation between incoming and transmitted symbols scrambling is used. Scrambling is applied only to the 2B + D-channels. + +The scrambling polynomial is different in both NT1 to LT and LT to NT1 directions. + +- In direction LT to NT1: $1 \oplus x^{-5} \oplus x^{-23}$ +- In direction NT1 to LT: $1 \oplus x^{-18} \oplus x^{-23}$ , + +$\oplus$ is the modulo two sum and $x^{-k}$ is the scrambled data delayed by $k$ symbol intervals. + +## **I.10 Activation/deactivation** + +Activation/deactivation is provided to enable the use of a power down state especially for applications, where the NT1 is powered from the LT via the local line. Activation from the power state may be initiated from both ends using a 7.5 kHz burst signal. Collisions are handled through appropriate duration and repetition rate of these bursts. + +The procedures on the line system support the procedures at reference point T for call control in accordance with Recommendation I.430 and the operation of loopbacks 1 (in the LT), 1A (in the regenerator) and 2 (in the NT1) in accordance with Recommendation I.603. The loopbacks are transparent. + +Timer 1 and timer 2, as defined in Recommendation I.430, are located as follows: + +- Timer 1 in the ET layer 1 or the ET; +- Timer 2 in the NT1. + +The activation of the line system for maintenance purposes e.g. error performance monitoring, is possible, even if no TE is connected to the interface at T reference point. + +Transmission of INFO 2 on the interface of T reference point is initiated when the line system is synchronized in the direction LT to NT1. + +### **I.10.1 Signals used for activation** + +To provide means to control/indicate progress during activation/deactivation across the local line the following signal elements are used: + +SIG 0 NT1 to LT and LT to NT1 + +No signal. + +SIG 1W NT1 to LT + +Awake signal (7.5 kHz tone); signals the layer 1 entity in the local exchange that it has to enter the power-up state and provide for the activation of the line system and the interface at T reference point. + +This signal is also used as awake acknowledge on the receipt of SIG 2W. + +SIG 2W LT to NT1 + +Awake signal (7.5 kHz tone); signals the NT1 that it has to enter the power-up state and prepare for synchronization on an incoming signal from the LT. + +This signal is also used as awake acknowledge on the receipt of SIG 1W. + +SIG 1 NT1 to LT + +Signal which contains framing information and allows the synchronization of the receiver in the LT. It informs the LT that the NT1 has synchronized on SIG 2. + +SIG 2 LT to NT1 + +Signal which contains framing information and allows the synchronization of the receiver in the NT1. + +SIG 1A NT1 to LT + +Signal similar to SIG 1 but without framing information. + +SIG 3 NT1 to LT + +Signal which contains framing information and allows the synchronization of the receiver in the LT. It indicates to the ET that the interface at T reference point is synchronized in both directions of transmission (except in the case of loopback 2 and 1A). + +SIG 4H LT to NT1 + +Signal which requires the NT1 to establish full layer 1 information transfer capability in both directions of transmission. + +SIG 4 LT to NT1 + +Signal which contains framing information and operational data on B and D channels. + +SIG 5 NT1 to LT + +Signal which contains framing information and operational data on B and D channels. + +SIG 2-L2 LT to NT1 + +Signal similar to SIG 2, but includes a loopback 2 request. + +SIG 4H-L2 LT to NT1 + +Signal which requires the NT1 to operate loopback 2 and to establish layer 1 information transfer capability in the direction LT to TE (transparent loopback 2). + +SIG 4-L2 Signal similar to SIG 4, but includes a loopback 2 request. + +All SIGs, except SIG 1W and SIG 2W, are continuous signals. The awake signals SIG 1W and SIG 2W are sent for a specified period of time only, but may be repeated if no acknowledgement is received. The repetition times are specified in a way to assure a proper interworking with the normal activation procedure. + +The loopback requests are transmitted making use of the $C_L$ channel. All other SIGs do not require the $C_L$ channel. + +The $C_L$ channel is provided with all SIGs except SIG 0, SIG 1W, SIG 2W and SIG 1A. + +### **I.10.2 Definition of internal timers** + +In the state transition tables and arrow diagrams the following internal timers are used: + +Tn1 = 13 ms: timer to supervise repetition of the awake signal SIG 2W from the LT + +TI1 = 7 ms: timer to supervise repetition of the awake signal SIG 1W from the NT1 + +TI2 = 1 ms: timer which defines the duration of SIG 4H and SIG 4H-L2 + +TI3 = 1 ms: timer which assures that, under non-failure conditions, the PH-AI is passed first in the TE and then in the LT/ET. This protects the first layer 2 frame (layer 3 – SETUP message) from the network side. + +TI4 = 12 ms: timer used to start transmission of SIG 2 when loopback 1 is requested. + +TI5 = 0.1 . . . 1 s: timer to supervise the deactivation procedure (within ET). + +### **I.10.3 Description of the activation procedure** + +In Figure I.2 the activation/deactivation procedures are described for the non-failure situation. + +Timer T1 (located in ET layer 1) and Timer T2 (located in NT1) are as specified in Recommendation I.430; the functional elements (FE) are defined in 5.4.1.3/G.960, and the primitives in 5.4.2.2/G.960 and 5.4.2.3/G.960. + +### **I.10.4 NT1 state transition table** + +The NT1 state transition table is described in Table I.1. INFOs on the interface at T reference point are related to SIGs on the line system and vice versa. + +![Sequence diagram for activation from network side. It shows the interaction between a T interface, NT1, LT, ET layer 1, and ET. The NT1 sends INFO 0, INFO 2, INFO 3, and INFO 4. The LT sends SIG 0, SIG 2W, SIG 1W, SIG 2, SIG 1A, SIG 1, SIG 3, SIG 4H, SIG 5, and SIG 4. The ET layer 1 sends FE 1, FE 3, and FE 4. The ET sends PH-AR, MPH-LSAI, and PH/MPH-AI. A timer T1 is shown. The NT1 also shows a timer Tn1.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +Sequence diagram for activation from network side. It shows the interaction between a T interface, NT1, LT, ET layer 1, and ET. The NT1 sends INFO 0, INFO 2, INFO 3, and INFO 4. The LT sends SIG 0, SIG 2W, SIG 1W, SIG 2, SIG 1A, SIG 1, SIG 3, SIG 4H, SIG 5, and SIG 4. The ET layer 1 sends FE 1, FE 3, and FE 4. The ET sends PH-AR, MPH-LSAI, and PH/MPH-AI. A timer T1 is shown. The NT1 also shows a timer Tn1. + +a) Activation from network side + +![Sequence diagram for activation from user side. It shows the interaction between a T interface, NT1, LT, ET layer 1, and ET. The NT1 sends INFO 0, INFO 1, INFO 2, INFO 3, and INFO 4. The LT sends SIG 0, SIG 1W, SIG 2W, SIG 2, SIG 1A, SIG 1, SIG 3, SIG 4H, SIG 5, and SIG 4. The ET layer 1 sends FE 2, FE 3, and FE 4. The ET sends MPH-AWI, MPH-LSAI, and PH/MPH-AI. A timer T11 is shown. The NT1 also shows a timer Tn1.](b235edb1dbe659e2782c9a0e47775ca4_img.jpg) + +Sequence diagram for activation from user side. It shows the interaction between a T interface, NT1, LT, ET layer 1, and ET. The NT1 sends INFO 0, INFO 1, INFO 2, INFO 3, and INFO 4. The LT sends SIG 0, SIG 1W, SIG 2W, SIG 2, SIG 1A, SIG 1, SIG 3, SIG 4H, SIG 5, and SIG 4. The ET layer 1 sends FE 2, FE 3, and FE 4. The ET sends MPH-AWI, MPH-LSAI, and PH/MPH-AI. A timer T11 is shown. The NT1 also shows a timer Tn1. + +b) Activation from user side + +![Sequence diagram for deactivation. It shows the interaction between a T interface, NT1, LT, ET layer 1, and ET. The NT1 sends INFO 4, INFO 3, INFO 0, and INFO 0. The LT sends SIG 4, SIG 5, SIG 0, and SIG 0. The ET layer 1 sends FE 5, FE 6, and FE 4. The ET sends MPH-DR, PH-DI, and MPH-DI. A timer T2 is shown. The NT1 also shows a timer Tn1.](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +Sequence diagram for deactivation. It shows the interaction between a T interface, NT1, LT, ET layer 1, and ET. The NT1 sends INFO 4, INFO 3, INFO 0, and INFO 0. The LT sends SIG 4, SIG 5, SIG 0, and SIG 0. The ET layer 1 sends FE 5, FE 6, and FE 4. The ET sends MPH-DR, PH-DI, and MPH-DI. A timer T2 is shown. The NT1 also shows a timer Tn1. + +c) Deactivation + +T1820270-93/d19 + +FIGURE I.2/G.961 +Activation/deactivation procedures: arrow diagrams +(non-failure situations) + +TABLE I.1/G.961 + +NT1 state transition table + +| State → | NT 1.1 | NT 1.2 | NT 1.3 | NT 1.4 | NT 1.5 | NT 1.6 | NT 1.7 | NT 1.8 | NT 1.9 | NT 1.10 | NT 2.1 | NT 2.2 | +|-------------------------------|-------------------|--------|--------|------------------|------------------|------------------|------------------|--------|------------------|--------------------|------------------|--------------------| +| Transmit
signal | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 2 | INFO 2 | INFO 4 | INFO 0 | INFO 2 | INFO X
(Note 2) | INFO 2 | INFO 4
(Note 4) | +| Receive
signal | SIG 0 | SIG 1W | SIG 1W | SIG 1A | SIG 1 | SIG 3 | SIG 5 | SIG 0 | SIG 5 | SIG 0
(Note 3) | SIG 3 | SIG 5
(Note 5) | +| INFO 0 | – | – | – | – | – | – | NT 1.9 | NT 1.1 | – | – | – | – | +| INFO 1 | NT 1.2 | – | – | – | – | – | / | – | – | / | – | / | +| INFO 3 | / | / | / | / | NT 1.6 | – | – | – | NT 1.7 | / | – | – | +| SIG 0 | – | – | – | ST.T2;
NT 1.8 | ST.T2;
NT 1.8 | ST.T2;
NT 1.8 | ST.T2;
NT 1.8 | – | ST.T2;
NT 1.8 | ST.T2;
NT 1.8 | ST.T2;
NT 1.8 | ST.T2;
NT 1.8 | +| SIG 2W | ST.Tn1;
NT 1.3 | NT 1.4 | / | / | / | / | / | – | / | / | / | / | +| SIG 2 | / | – | – | NT 1.5 | – | – | / | / | / | / | NT 1.6
or – | / | +| SIG 4H | / | / | / | / | / | NT 1.7 | – | / | / | / | NT 1.7 | / | +| SIG 4 | / | / | / | / | / | / | – | / | – | – | / | NT 1.7 | +| Exp. of T2
(Note 1) | – | – | – | – | – | – | – | NT 1.1 | – | – | – | – | +| Lost framing
T interface | / | / | / | / | / | – | NT 1.9 | – | – | – | / | / | +| Lost framing
line system | / | / | / | / | NT 1.10 | NT 1.10 | NT 1.10 | / | NT 1.10 | – | NT 1.10 | NT 1.10 | +| Exp. of internal
timer Tn1 | / | / | NT 1.4 | / | / | / | / | / | / | / | / | / | + +TABLE I.1/G.961 (end) + +NT1 state transition table + +| State | NT 1.1 | NT 1.2 | NT 1.3 | NT 1.4 | NT 1.5 | NT 1.6 | NT 1.7 | NT 1.8 | NT 1.9 | NT 1.10 | NT 2.1 | NT 2.2 | +|-----------------|--------|--------|--------|--------|----------------|----------------|--------|--------|--------|--------------------|--------|--------------------| +| Transmit signal | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 2 | INFO 2 | INFO 4 | INFO 0 | INFO 2 | INFO X
(Note 2) | INFO 2 | INFO 4
(Note 4) | +| Receive signal | SIG 0 | SIG 1W | SIG 1W | SIG 1A | SIG 1 | SIG 3 | SIG 5 | SIG 0 | SIG 5 | SIG 0
(Note 3) | SIG 3 | SIG 5
(Note 5) | +| SIG 2-L2 | / | – | – | NT 2.1 | NT 2.1
or – | NT 2.1
or – | / | / | / | / | – | / | +| SIG 4H-L2 | / | / | / | / | / | NT 2.2 | – | / | / | / | NT 2.2 | – | +| SIG 4-L2 | / | / | / | / | / | / | NT 2.2 | / | NT 2.2 | NT 2.2 | / | – | + +– No state change. + +/ Impossible by the definition of peer-to-peer physical layer procedures or system internal reasons. + +ST.Tx; NTy Start Timer x; enter state NT y. + +##### NOTES + +1 Timer T2 as defined in Recommendation I.430. + +2 INFO X: signal with no framing information i.e. binary ZERO's. + +3 Any other signal which produces an error indication on the LT side is allowed, especially loss of framing or excessive error rate. + +4 The D-Echo bit is set to binary ZERO. + +5 The B- and D-channels are looped back to the network side. + +The following states are used: + +- NT 1.1 Deactivated state (low power consumption mode). No signal is transmitted. +- NT 1.2 The NT1 sends the awake signal SIG 1W to the LT, on the receipt of INFO 1 from the user side, and waits for the receipt of the awake acknowledge signal SIG 2W from the LT. +- NT 1.3 On receipt of the awake signal SIG 2W, the NT1 responds with SIG 1W and starts transmission of SIG 1A on expiry of timer Tn1, unless a new awake signal SIG 2W from the LT is received. +- NT 1.4 After completion of the awake procedure, the NT1 waits for SIG 2 to synchronize its receiver. +- NT 1.5 The receiver on the network side is synchronized. The NT1 sends SIG 1 to the LT and INFO 2 to the user side to initiate the activation of the interface of reference point T. It waits for the receipt of INFO 3. +- NT 1.6 The interface at T reference point is synchronized in both directions of transmission. The NT1 sends SIG 3 to the LT and waits for the receipt of SIG 4H. +- NT 1.7 The NT1 is fully active and sends INFO 4 to the user side and SIG 5 to the LT. The B and D channels are operational. +- NT 1.8 Pending deactivation state. The NT1 sends INFO 0 to the user side to deactivate the interface at reference point T and SIG 0 to the LT. It waits for the receipt of INFO 0 or expiry of timer T2 to enter state NT 1.1. +- NT 1.9 This state is entered on loss of signal or loss of framing at the T interface. No indication is sent to the LT, in accordance with Note 3 to Table 4/I.430. +- NT 1.10 This state is entered on loss of framing at the line side. An indication is forwarded to the user side (INFO X) and to the network side (SIG 0). + +The following states support activation when loopback 2 is requested: + +- NT 2.1 The receiver on the network side is synchronized. The NT1 sends SIG 3 to the LT and INFO 2 to the user side (transparent loopback). It waits for the receipt of SIG 4H-L2 from the LT. +- NT 2.2 The NT1 is fully active and sends INFO 4 to the user side (transparent loopback) and SIG 5 to the LT. Loopback 2 is operated and receive data 2B + D are sent to the LT. + +### **I.10.5 LT state transition table** + +The LT state transition table is described in Table I.2. SIGs on the line system are related to function elements (FEs) on the V1 reference point. + +The following states are used: + +- LT 1.1 Deactivated state. No signal is transmitted. +- LT 1.2 On receipt of the awake signal SIG 1W, the LT responds with SIG 2W and starts transmission of SIG 2 on expiry of timer Tl1, unless a new awake signal SIG 1W from the NT1 is received. +- LT 1.3 The LT sends the awake signal SIG 2W to the NT1, on the receipt of FE 1, and waits for the awake acknowledge signal SIG 1W from the NT1. +- LT 1.4 The LT sends SIG 2 to the NT1 and waits for SIG 1 or SIG 3 to synchronize its receiver. When the LT is synchronized and has detected SIG 1, it issues FE 3. +- LT 1.5 The line transmission system is synchronized in both directions of transmission. The LT waits for the receipt of SIG 3. + +TABLE I.2/G.961 + +**LT state transition table** + +| State → | LT 1.1 | LT 1.2 | LT 1.3 | LT 1.4 | LT 1.5 | LT 1.6 | LT 1.7 | LT 1.8 | LT 2.1 | LT 2.2 | LT 2.3 | LT 2.4 | +|---------------------------|----------------------------|--------|--------|-------------------|-------------------|-----------------|------------|-----------------|--------|--------|-----------------|--------| +| Transmit signal | | | | | | | | | | | | | +| Receive signal | SIG 0 | SIG 2W | SIG 2W | SIG 2 | SIG 2 | SIG 4H | SIG 4 | SIG 0 | SIG 2W | SIG 2 | SIG 4H | SIG 4 | +| FE 1 | LT 1.3 | – | – | – | – | – | – | – | – | – | – | – | +| FE 5 | : | LT 1.8 | LT 1.8 | LT 1.8 | LT 1.8 | LT 1.8 | LT 1.8 | – | LT 1.8 | LT 1.8 | LT 1.8 | LT 1.8 | +| SIG 0 | – | – | – | – | FE 7;
– | FE 7;
– | FE 7;
– | FE 6;
LT 1.1 | – | – | – | – | +| SIG 1W | ST.TI1;
FE 2;
LT 1.2 | : | LT 1.4 | / | / | / | / | – | – | / | / | / | +| SIG 1 | / | / | / | FE 3;
LT 1.5 | – | / | / | – | / | – | – | – | +| SIG 3 | / | / | / | ST.TI2;
LT 1.6 | ST.TI2;
LT 1.6 | – | – | – | / | – | – | – | +| Exp. of intern. timer TI1 | – | LT 1.4 | – | – | – | – | – | – | – | – | – | – | +| Exp. of intern. timer TI2 | – | – | – | – | – | FE 7;
LT 1.4 | – | – | – | – | FE 4;
LT 2.4 | – | +| Lost framing line system | / | / | / | / | FE 7;
– | FE 7;
– | FE 7;
– | – | / | / | / | / | + +TABLE I.2/G.961 (end) + +LT state transition table + +| State → | LT 1.1 | LT 1.2 | LT 1.3 | LT 1.4 | LT 1.5 | LT 1.6 | LT 1.7 | LT 1.8 | LT 2.1 | LT 2.2 | LT 2.3 | LT 2.4 | +|-------------------------------|----------------------------------------------------------------------------------------------------|--------|----------------|----------------|----------------|--------|--------|--------|--------|-------------------|--------|--------| +| Transmit signal | | | | | | | | | | | | | +| Receive signal | SIG 0 | SIG 2W | SIG 2W | SIG 2 | SIG 2 | SIG 4H | SIG 4 | SIG 0 | SIG 2W | SIG 2 | SIG 4H | SIG 4 | +| FE 4 | ST.TI4;
LT 2.1 | – | LT 2.2
or – | LT 2.2
or – | LT 2.2
or – | – | – | LT 2.1 | : | : | : | : | +| Exp. of intern. timer TI4 | – | – | – | – | – | – | – | – | LT 2.2 | – | – | – | +| Rec. synch. on looped b. sig. | / | / | / | – | – | – | – | – | / | ST.TI2;
LT 2.3 | – | – | +| – | No state change. | | | | | | | | | | | | +| / | Impossible by the definition of peer-to-peer physical layer procedures or system internal reasons. | | | | | | | | | | | | +| : | Impossible by the definition of the physical layer. | | | | | | | | | | | | +| a, b; LT x | Perform action/issue message a and b; enter state LTx. | | | | | | | | | | | | +| ST.Tlx | Start Timer Tlx. | | | | | | | | | | | | + +- LT 1.6 The line transmission system and the interface at T reference point are synchronized in both directions of transmission. The LT sends SIG 4H until the expiry of timer TI2. +- LT 1.7 Fully active state. The LT sends SIG 4 to the NT1 and issues FE 4. The B and D channels are fully operational. +- LT 1.8 Pending deactivation state. The LT sends SIG 0 to the NT1 to deactivate the line system and the interface at T reference point. It waits for the receipt of SIG 0 to enter state LT 1.1 and to issue FE 6. + +The following states support activation when loopback 1 is requested: + +- LT 2.1 The LT sends the awake signal SIG 2W to the NT1 (transparent loopback), on the receipt of FE 9, and starts transmission of SIG 2 on expiry of timer TI4. +- LT 2.2 The LT has operated loopback 1 and is synchronizing its receiver on the looped back signal. +- LT 2.3 The LT sends SIG 4H until the expiry of timer TI2. +- LT 2.4 The LT is fully active and sends SIG 4 to the NT1 (transparent loopback). Loopback 1 is operated. + +The LT state transition table is not affected by loopback 2 and 1A requests. The corresponding control signals are transferred across channels $C_{V_1}$ and $C_L$ . + +### **I.10.6 Activation times** + +For definition of activation times see 5.5/G.960. + +- a) Maximum activation time for activation occurring immediately after a deactivation: + - without regenerator: 210 ms + - with regenerator: 420 ms. +- b) Maximum time for activation occurring after the first powering of a line: + - without regenerator: 1.5 s + - with regenerator: 3 s. + +## **I.11 Jitter** + +Jitter tolerances shall assure that the maximum network limit of jitter (see Recommendation G.823) is not exceeded. + +Furthermore, the limits of Recommendation I.430 must be supported by the jitter limits of the transmission system on local lines. + +The jitter limits given below must be satisfied regardless of the length of the local line and the inclusion of repeaters, provided that they are covered by the transmission media characteristic (see 3). The limits must be met regardless of the transmitted signal. A suitable test sequence is for further study (see 4/G.823). + +### **I.11.1 Limits of maximum tolerable input jitter** + +The amplitude of the jitter at the NT1 input shall be limited by the template given in Figure I.3. + +### **I.11.2 Output jitter of NT1 in absence of input jitter** + +When measured with a highpass filter with a 30 Hz cut-off frequency, the jitter at the output of the NT1 shall not exceed 0.02 UIpp. Without a filter, the jitter shall not exceed 0.1 UIpp. + +### **I.11.3 Timing extraction jitter** + +The jitter at the output of the NT1 shall closely follow the input jitter. Therefore, the jitter transfer function of the NT1 shall be less than $\pm 1$ dB in the frequency range 3 Hz to 30 Hz. + +![Figure I.3/G.961: Minimum tolerable sinusoidal input jitter. The graph shows Jitter amplitude (pp) on the y-axis versus Jitter frequency on the x-axis. The y-axis has labels 0.25 UI and 0.025 UI. The x-axis has labels 3 Hz, 30 Hz, and 10 kHz. The plot starts at 0.25 UI at 3 Hz, decreases with a slope of 20 dB/decade to 0.025 UI at 30 Hz, and remains constant at 0.025 UI up to 10 kHz. A dashed line indicates the 0.25 UI level from 3 Hz to 30 Hz. Another dashed line indicates the 0.025 UI level from 30 Hz to 10 kHz. The text 'T1820280-93/d20' is in the bottom right corner.](24b549c0c4b79c515b244625cf4f4978_img.jpg) + +Figure I.3/G.961: Minimum tolerable sinusoidal input jitter. The graph shows Jitter amplitude (pp) on the y-axis versus Jitter frequency on the x-axis. The y-axis has labels 0.25 UI and 0.025 UI. The x-axis has labels 3 Hz, 30 Hz, and 10 kHz. The plot starts at 0.25 UI at 3 Hz, decreases with a slope of 20 dB/decade to 0.025 UI at 30 Hz, and remains constant at 0.025 UI up to 10 kHz. A dashed line indicates the 0.25 UI level from 3 Hz to 30 Hz. Another dashed line indicates the 0.025 UI level from 30 Hz to 10 kHz. The text 'T1820280-93/d20' is in the bottom right corner. + +$$1 \text{ UI} = 1/120 \text{ kHz} = 8.\bar{3} \text{ } \mu\text{s}$$ + +FIGURE I.3/G.961 +Minimum tolerable sinusoidal input jitter + +### I.11.4 Test conditions for jitter measurements + +For further study. + +## I.12 Transmitter output characteristics + +### I.12.1 Pulse amplitude + +The amplitude of a transmitted single pulse shall be $2 \text{ V} \pm 0.2 \text{ V}$ with a load impedance of 150 ohm. + +### I.12.2 Pulse shape + +The shape of a transmitted single pulse shall fit the mask given in Figure I.4. + +### I.12.3 Signal power + +Not specified. + +### I.12.4 Power spectrum + +The upper bound of the power spectral density shall be limited according to Figure I.5. + +### I.12.5 Transmitter signal nonlinearity + +Not specified. + +## I.13 Transmitter/receiver termination + +### I.13.1 Impedance + +The nominal output/input impedance of the NT1 and LT shall be 150 ohms. + +### I.13.2 Return loss + +The return loss against 150 ohms $\pm 1\%$ measured for NT1 or LT shall exceed the limits given in Figure I.6. + +![Pulse mask for transmitted single pulse graph showing voltage (U) vs time (t).](152efae989544ee653283e8de26cc9b1_img.jpg) + +The graph shows a pulse mask for a transmitted single pulse. The vertical axis is voltage (U) and the horizontal axis is time (t). The pulse has a rise time from 10 mV to 2.2 V, a peak at 2.2 V, a fall time to -0.8 V, and a recovery to 0.2 V. Time markers include $-\frac{12}{8}T$ , $-\frac{9}{8}T$ , $-\frac{5}{8}T$ , 0, $\frac{3}{8}T$ , T, 2T, 8T, 29T, and 30T. A break in the time axis is shown between 2T and 8T. The label T1820290-93/d21 is present. + +Pulse mask for transmitted single pulse graph showing voltage (U) vs time (t). + +$$T = \frac{1}{120 \text{ kHz}} = 8.3 \text{ } \mu\text{s}$$ + +FIGURE 1.4/G.961 +Pulse mask for transmitted single pulse + +![Limits of transmit power spectrum graph showing dB(uV) vs Frequency (f).](c53adc66eab40abd5f8b9107d950ad04_img.jpg) + +The graph shows the limits of the transmit power spectrum. The left vertical axis is dB(μV) from 90 to 115. The right vertical axis is mV from 50 to 632. The horizontal axis is Frequency (f) on a logarithmic scale from 10^2 to 10^5 kHz. The spectrum is limited by a line with a 5 dB/decade slope, starting at 115 dB(μV) at 10^2 kHz and decreasing to approximately 98 dB(μV) at 10^5 kHz. A measurement bandwidth of 9 kHz is indicated. The label T1820300-93/d22 is present. + +Limits of transmit power spectrum graph showing dB(uV) vs Frequency (f). + +FIGURE 1.5/G.961 +Limits of transmit power spectrum + +![Figure I.6/G.961: NT1 and LT return loss graph. The y-axis is 'Return loss' in dB (0 to 16) and the x-axis is 'Frequency (f)' in kHz (5 to 100). The graph shows a line starting at 5 kHz, 5 dB, rising to 16 dB at 12.5 kHz, staying at 16 dB until 50 kHz, and then falling to 10 dB at 100 kHz.](f24d06b5e3b1d8ae12d4893e7619f6f5_img.jpg) + +| Frequency (kHz) | Return loss (dB) | +|-----------------|------------------| +| 5 | 5 | +| 12.5 | 16 | +| 50 | 16 | +| 100 | 10 | + +Figure I.6/G.961: NT1 and LT return loss graph. The y-axis is 'Return loss' in dB (0 to 16) and the x-axis is 'Frequency (f)' in kHz (5 to 100). The graph shows a line starting at 5 kHz, 5 dB, rising to 16 dB at 12.5 kHz, staying at 16 dB until 50 kHz, and then falling to 10 dB at 100 kHz. + +FIGURE I.6/G.961 +NT1 and LT return loss + +### **I.13.3 Longitudinal conversion loss** + +The longitudinal conversion loss at the line interface for LT and NT1 shall exceed the limits given in Figure I.7. + +![Figure I.7/G.961: Longitudinal conversion loss graph. The y-axis is 'Loss' in dB (0 to 40) and the x-axis is 'Frequency (f)' in Hz (logarithmic scale from 10^4 to 10^6). The graph shows a line starting at 5 kHz, 28 dB, rising to 40 dB at 20 kHz, staying at 40 dB until 150 kHz, and then falling with a slope of 5 dB/decade to 36 dB at 1 MHz.](a0fdaf0b566e05f53f0085cf41e2dbad_img.jpg) + +| Frequency (Hz) | Loss (dB) | +|-----------------------|-----------| +| 5 × 10 3 | 28 | +| 2 × 10 4 | 40 | +| 1.5 × 10 5 | 40 | +| 10 6 | 36 | + +Figure I.7/G.961: Longitudinal conversion loss graph. The y-axis is 'Loss' in dB (0 to 40) and the x-axis is 'Frequency (f)' in Hz (logarithmic scale from 10^4 to 10^6). The graph shows a line starting at 5 kHz, 28 dB, rising to 40 dB at 20 kHz, staying at 40 dB until 150 kHz, and then falling with a slope of 5 dB/decade to 36 dB at 1 MHz. + +FIGURE I.7/G.961 +Longitudinal conversion loss + +# Annex A + +## Extension functions and requirements for a line system with MMS 43 line code + +(This annex does not form an integral part of this Recommendation) + +No extension functions and requirements have been defined yet. + +# Appendix II + +## Core requirements for a system using 2B1Q line code + +(This appendix does not form an integral part of this Recommendation) + +## II.1 Line code + +The line code shall be 2B1Q (2 binary, 1 quaternary). This is a 4-level code and is used without redundancy. + +The bit stream entering the NT1 from the interface at reference point T (or entering the LT from the ET) shall be grouped into pairs of bits for conversion to quaternary symbols that are called quats. Figure II.1 shows the relationship of the bits in the B- and D-channels to quats. The B- and D-channel bits are scrambled before coding. $M_1$ through $M_6$ bits of the $C_L$ -channel are also paired, coded and scrambled in the same way. + +Each successive pair of scrambled bits in the binary data stream is converted to a quaternary symbol to be output from the transmitters, as specified below: + +| First bit
(sign) | Second bit
(magnitude) | Quaternary symbol
(quat) | +|---------------------|---------------------------|-----------------------------| +| 1 | 0 | +3 | +| 1 | 1 | +1 | +| 0 | 1 | -1 | +| 0 | 0 | -3 | + +At the receiver, each quaternary symbol is converted to a pair of bits by reversing the table above, descrambled, and formed into a bit stream representing B- and D-channels and a $C_L$ -channel containing $M$ bits for maintenance and other purposes. The bits in the B- and D-channels are properly placed by reversing the relationship in Figure II.1. + +## II.2 Line baud rate + +The line symbol rate is 80 kbauds. + +### II.2.1 Clock tolerance + +#### II.2.1.1 NT1 clock tolerance + +The tolerance of the free running NT1 clock is $\pm 100$ ppm. + +#### II.2.1.2 LT clock tolerance + +The tolerance of the clock provided at the LT is $\pm 5$ ppm. + +| Data | Time → | | | | | | | | D | +|-------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------| +| | B 1 | | | | B 2 | | | | | +| Bit Pairs | $b_{11} b_{12}$ | $b_{13} b_{14}$ | $b_{15} b_{16}$ | $b_{17} b_{18}$ | $b_{21} b_{22}$ | $b_{23} b_{24}$ | $b_{25} b_{26}$ | $b_{27} b_{28}$ | $d_1 d_2$ | +| Quat # (relative) | $q_1$ | $q_2$ | $q_3$ | $q_4$ | $q_5$ | $q_6$ | $q_7$ | $q_8$ | $q_9$ | +| # Bits | 8 | | | | 8 | | | | 2 | +| # Quats | 4 | | | | 4 | | | | 1 | + +T1814300-92/d25 + +$b_{11}$ First bit of B1 octet as received at reference point T + $b_{18}$ Last bit of B1 octet as received at reference point T + $b_{21}$ First bit of B2 octet as received at reference point T + $b_{28}$ Last bit of B2 octet as received at reference point T + $d_1 d_2$ Consecutive D-channel bits ( $d_1$ is first bit of pair as received at reference point T) + $q_i$ $i$ th quat relative to start of given 18-bit 2B + D data field + +NOTE – There are 12 2B + D 18-bit fields per 1.5 ms basic frame. + +FIGURE II.1/G.961 +2B1Q encoding of 2B + D bit fields + +## II.3 Frame structure + +A frame shall be 120 quaternary symbols transmitted within a nominally 1.5 ms interval. Each frame contains a frame word, 2B + D data and CL-channel bits shown in Figure II.2. + +### II.3.1 Frame length + +The number of 2B + D slots in a frame is 12. Each slot contains 18 bits. + +### II.3.2 Bit allocation in direction LT-NT1 + +The bit allocation of the frames is shown in Figures II.1 and II.2. + +### II.3.3 Bit allocation in direction NT1-LT + +See II.3.2. + +## II.4 Frame word + +The frame word is used to allocate bit positions to the B, D, and CL-channels. It may be also used for baud synchronization. + +### II.4.1 Frame word in direction LT-NT1 + +The code for the frame word in all frames except the first in a multiframe shall be: + +$$FW = +3 +3 -3 -3 -3 +3 -3 +3 +3$$ + +The code for the frame word of the first frame of a multiframe shall be an inverted frame word (IFW): + +$$IFW = -3 -3 +3 +3 +3 -3 +3 -3 -3$$ + +### II.4.2 Frame word in direction NT1-LT + +See II.4.1. + +![Diagram of frame structure showing a 1.5 ms duration divided into three parts: FW/IFW, 12 x (2B + D), and CL. Below the diagram is a table detailing the function, number of quats, quat positions, number of bits, and bit positions for each part.](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg) + +| Frame | FW/IFW | 12 × (2B + D) | C L | +|----------------|------------|---------------|----------------| +| Function | Frame word | 2B + D | Overhead | +| # Quats | 9 | 108 | 3 | +| Quat positions | 1-9 | 10-117 | 118-120 | +| # Bits | 18 | 216 | 6 | +| Bit positions | 1-18 | 19-234 | 235-240 | + +Diagram of frame structure showing a 1.5 ms duration divided into three parts: FW/IFW, 12 x (2B + D), and CL. Below the diagram is a table detailing the function, number of quats, quat positions, number of bits, and bit positions for each part. + +T1814310-92/d26 + +Symbols and abbreviations: + +| | | +|----------------|---------------------------------------------------------------------| +| quat | Quaternary symbol = 1 baud | +| -3, -1, +1, +3 | Symbol names | +| 2B + D | Customer data channels B 1 , B 2 and D | +| FW | Frame Word (9-Symbol Code) = +3 +3 -3 -3 -3 +3 -3 +3 +3 | +| IFW | Inverted (or complementary) frame word = -3 -3 +3 +3 +3 -3 +3 -3 -3 | +| C L | M-channel bits, M 1 to M 6 | + +NOTE – Frames in the NT1-to -Network direction are offset from frames in the Network-to -NT1 direction by $60 \pm 2$ quats. + +FIGURE II.2/G.961 +**Frame structure of 2B1Q transmission system** + +## II.5 Frame alignment procedure + +A unique frame alignment procedure is not specified. However, the time limits specified in II.10 shall be met. + +## II.6 Multiframe + +To enable the allocation of the CL-channel bits over more than one frame, a multiframe is used. The start of the multiframe is determined by the inverted frame word (IFW). The number of frames in a multiframe is eight. + +### II.6.1 Multiframe word in direction NT1-LT + +See II.4.1. + +### II.6.2 Multiframe word in direction LT-NT1 + +See II.4.1. + +## II.7 Frame offset between LT-NT1 and NT1-LT frames + +The NT1 shall synchronize transmitted frames with received frames (LT-NT1 direction). Transmitted frames shall be offset with respect to received frames by $60 \pm 2$ quaternary symbols (i.e. about 0.75 ms). + +## II.8 CL-channel + +The CL-channel consists of the last three symbols (6 bits) in each basic frame of the multiframe. + +### II.8.1 Bit rate + +The bit rate for the CL-channel is 4 kbit/s. + +### II.8.2 Structure + +Forty-eight bits of a multiframe are used for the $C_L$ -channel and are referred to as M bits. + +Twenty-four bits per multiframe (2 kbit/s) are allocated to an embedded operations channel (EOC) which supports operations communications needs between the network and the NT1. + +Twelve bits per multiframe (1 kbit/s) are allocated to a cyclic redundancy check (CRC) function. + +Twelve bits per multiframe (1 kbit/s) are allocated to other functions and spare bits as shown in Figure II.3. + +| | | Framing | 2B + D | $C_L$ (overhead) bits $M_1$ - $M_6$ | | | | | | | +|----------------|-----------------|----------------|--------|-------------------------------------|-------------------|-------------------|-----------------|-------------------|-------------------|-------| +| | | Quat positions | 1-9 | 10-117 | 118 s | 118 m | 119 s | 119 m | 120 s | 120 m | +| | | Bits positions | 1-18 | 19-234 | 235 | 236 | 237 | 238 | 239 | 240 | +| Multiframe No. | Basic frame No. | Frame word | 2B + D | $M_1$ | $M_2$ | $M_3$ | $M_4$ | $M_5$ | $M_6$ | | +| LT to NT1 | | | | | | | | | | | +| A | 1 | IFW | 2B + D | EOC a1 | EOC a2 | EOC a3 | ACT | 1 | 1 | | +| | 2 | FW | 2B + D | EOC dm | EOC i1 | EOC i2 | DEA | 1 | FEFE | | +| | 3 | FW | 2B + D | EOC i3 | EOC i4 | EOC i5 | 1 | CRC 1 | CRC 2 | | +| | 4 | FW | 2B + D | EOC i6 | EOC i7 | EOC i8 | 1 | CRC 3 | CRC 4 | | +| | 5 | FW | 2B + D | EOC a1 | EOC a2 | EOC a3 | 1 | CRC 5 | CRC 6 | | +| | 6 | FW | 2B + D | EOC dm | EOC i1 | EOC i2 | 1 | CRC 7 | CRC 8 | | +| | 7 | FW | 2B + D | EOC i3 | EOC i4 | EOC i5 | UOA | CRC 9 | CRC 10 | | +| | 8 | FW | 2B + D | EOC i6 | EOC i7 | EOC i8 | AIB | CRC 11 | CRC 12 | | +| B, C, ... | | | | | | | | | | | +| NT1 to LT | | | | | | | | | | | +| 1 | 1 | IFW | 2B + D | EOC a1 | EOC a2 | EOC a3 | ACT | 1 | 1 | | +| | 2 | FW | 2B + D | EOC dm | EOC i1 | EOC i2 | PS 1 | 1 | FEFE | | +| | 3 | FW | 2B + D | EOC i3 | EOC i4 | EOC i5 | PS 2 | CRC 1 | CRC 2 | | +| | 4 | FW | 2B + D | EOC i6 | EOC i7 | EOC i8 | NTM | CRC 3 | CRC 4 | | +| | 5 | FW | 2B + D | EOC a1 | EOC a2 | EOC a3 | CSO | CRC 5 | CRC 6 | | +| | 6 | FW | 2B + D | EOC dm | EOC i1 | EOC i2 | 1 | CRC 7 | CRC 8 | | +| | 7 | FW | 2B + D | EOC i3 | EOC i4 | EOC i5 | SAI | CRC 9 | CRC 10 | | +| | 8 | FW | 2B + D | EOC i6 | EOC i7 | EOC i8 | 1* | CRC 11 | CRC 12 | | +| 2, 3, ... | | | | | | | | | | | + +ACT    Activation bit (set to ONE during activation) + +AIB    Alarm indication bit (ZERO indicates interruption) + +CRC    Cyclic redundancy check: covers 2B + D and $M_4$ + +1    Most significant bit +2    Next most significant bit +etc. + +CSO    Cold-start-only bit (ONE indicates cold-start-only) + +DEA    Deactivation bit (set to ZERO to announce deactivation) + +EOC Embedded operations channel + +- a Address bit +- dm Data/message indicator +- i information (data/message) + +FEFE Far end block error bit (ZERO for errored multiframe) + +NTM NT1 in test mode bit (ZERO indicates test mode) + +PS1, PS2 Power status bits (ZERO indicates power problems) + +quat Pair of bits forming quaternary symbol + +- s Sign bit (first) in quat +- m Magnitude bit (second) in quat + +SAI S-activation indicator bit (optional, set = 1 for S/T activity) + +UOA DLL-only-bit (optional, set = 1 to activate S/T) + +1 Reserve bit for future standard; set = ONE + +1\* Network indicator bit; reserved for network use, set = ONE + +2B + D User data, bits 19-234 in basic frame + +M CL-channel, bits 235-240 in basic frame + +FW/IFW Frame word/inverted frame word, bits 1-18 in frame + +###### NOTES + +- 1 8 × 1.5 ms. Basic frames → 12 ms. Multiframe. +- 2 NT1-to-Network multiframe delay offset from Network-to-NT1 multiframe by 60 ± 2 quats (about 0.75 ms). +- 3 All bits other than the frame work are scrambled. + +FIGURE II.3/G.961 + +#### 2B1Q multiframe technique and overhead bit assignments + +### II.8.3 Protocol and procedures + +The CL-channel functions (M bits) specified below are based on the bit allocation for the multiframe defined in Figure II.3. + +#### II.8.3.1 Error monitoring function + +##### II.8.3.1.1 Cyclic redundancy check (CRC) + +The CRC bits are the M5 and M6 bits in frames 3 through 8 of the multiframe. The CRC is an error detection code that shall be generated from the appropriate bits in the multiframe and inserted into the bit stream by the transmitter. At the receiver a CRC calculated from the same bits shall be compared with the CRC value received in the bit stream. If the two CRCs differ, there has been at least one error in the covered bits in the multiframe. + +##### II.8.3.1.2 CRC algorithms + +The cyclic redundancy check (CRC) code shall be computed using the polynomial: + +$$P(x) = x^{12} \oplus x^{11} \oplus x^3 \oplus x^2 \oplus x \oplus 1$$ + +where + +⊕ = modulo 2 summation. + +One method of generating the CRC code for a given multiframe is illustrated in Figure II.4. At the beginning of a multiframe all register cells are cleared. The multiframe bits to be covered by the CRC are then clocked into the generator from the left. During bits which are not covered by the CRC (FW, IFW, M1, M2, M3, M5, M6) the state of the CRC generator is frozen and no change in state of any of the stages takes place. After the last multiframe bit to be covered by the CRC is clocked into REGISTER CELL 1, the 12 register cells contain the CRC code of the next multiframe. Between this point and the beginning of the next multiframe, the register cell contents are stored for transmission in the CRC field of the next multiframe. Notice that multiframe bit CRC1 resides in REGISTER CELL 12, CRC2 in REGISTER CELL 11, etc. + +NOTE – The binary ONEs and ZEROs from the interface at the T reference point, and corresponding bits from the network (across the V1 reference point), must be treated as binary ONEs and ZEROs, respectively, for the computation of the CRC. + +##### **II.8.3.1.3 Bits covered by the CRC** + +The CRC bits shall be calculated from the bits in the D-channel, both B-channels, and the M4 bits. + +#### **II.8.3.2 Other CL-channel functions** + +A number of transceiver operations and maintenance functions are handled by M4, M5, and M6 bits in the multiframe. These bits are defined in the following subclauses. To reflect a change in status, a new value for M4 bits shall be repeated in at least three consecutively transmitted multiframes. + +##### **II.8.3.2.1 Far end block error (FEBE) bit, mandatory** + +The FEBE bits shall be the M6 bits in the second basic frame of the multiframes transmitted by either transceiver. The FEBE bit shall be set to ONE if there are no CRC errors in the multiframe and ZERO if the multiframe contains a CRC error. The FEBE bit shall be placed in the next available outgoing multiframe and transmitted back to the originator. The FEBE bits may be monitored to determine the performance of the far end receiver. + +##### **II.8.3.2.2 The ACT bit, mandatory** + +The ACT bit is the M4 bit in the first frame of multiframes transmitted by either transceiver. The ACT bit is used as a part of the start-up sequence to communicate readiness for layer 2 communication progress (see II.10.5). If a Loopback 2 (2B + D) is requested, the ACT bit (from NT to LT) is set to binary ONE after time T7 (see Figure II.6) as part of the loopback start-up sequence to communicate readiness to loopback data. This use of the ACT bit for Loopback 2 is recommended. However, some existing implementations may not set ACT = 1 for Loopback 2. + +##### **II.8.3.2.3 The DEA bit, mandatory** + +The DEA bit is the M4 bit in the second frame of multiframes transmitted from the LT (see II.3 and Figure II.3). The DEA bit is used by the LT to communicate to the NT1 its intention to deactivate (see II.10.1.5.2). To permit reliable detection of the DEA bit when indicating the intention to deactivate, its corresponding status (binary ZERO) shall be transmitted in at least three successive multiframes before terminating transmission of signal. + +##### **II.8.3.2.4 NT1 power status bits** + +The M4 bits in the second and third basic frames of multiframes transmitted by the NT1 (Figure II.3) are reserved for NT1 power status indication; their use is optional. When not used, these bits shall be set to ONE in SN3. See Annex A to Appendix II. + +##### **II.8.3.2.5 NT1 test mode indicator (NTM) bit** + +The M4 bit in the fourth basic frame of multiframes transmitted by the NT1 to the network (Figure II.3) is reserved for NT1 test mode indication; its use is optional. If this function is not used, the bit shall be set to ONE in SN3. See Annex A to Appendix II. + +![Schematic diagram of a CRC-12 generator showing 12 register cells, adders, latches, and control lines.](cbb2d311b20781a595488445ded48d0a_img.jpg) + +``` + +graph LR + DataInput[Data input] --> Adder1((+)) + Adder1 --> Reg1[Regist. cell 1 clear] + Reg1 --> Adder2((+)) + Adder2 --> Reg2[Regist. cell 2 clear] + Reg2 --> Adder3((+)) + Adder3 --> Reg3[Regist. cell 3 clear] + Reg3 --> Adder4((+)) + Adder4 --> Reg4[Regist. cell 4 clear] + Reg4 --> Reg5[Regist. cell 5 clear] + Reg5 --> Reg6[Regist. cell 6 clear] + Reg6 --> Reg7[Regist. cell 7 clear] + Reg7 --> Reg8[Regist. cell 8 clear] + Reg8 --> Reg9[Regist. cell 9 clear] + Reg9 --> Reg10[Regist. cell 10 clear] + Reg10 --> Reg11[Regist. cell 11 clear] + Reg11 --> Adder12((+)) + Adder12 --> Reg12[Regist. cell 12 clear] + + Reg1 --> Latch12[Latch enable] --> CRC12[CRC 12] + Reg2 --> Latch11[Latch enable] --> CRC11[CRC 11] + Reg3 --> Latch10[Latch enable] --> CRC10[CRC 10] + Reg4 --> Latch9[Latch enable] --> CRC9[CRC 9] + Reg5 --> Latch8[Latch enable] --> CRC8[CRC 8] + Reg6 --> Latch7[Latch enable] --> CRC7[CRC 7] + Reg7 --> Latch6[Latch enable] --> CRC6[CRC 6] + Reg8 --> Latch5[Latch enable] --> CRC5[CRC 5] + Reg9 --> Latch4[Latch enable] --> CRC4[CRC 4] + Reg10 --> Latch3[Latch enable] --> CRC3[CRC 3] + Reg11 --> Latch2[Latch enable] --> CRC2[CRC 2] + Reg12 --> Latch1[Latch enable] --> CRC1[CRC 1] + + Reg12 -- Feedback --> Adder1 + Reg12 -- Feedback --> Adder2 + Reg12 -- Feedback --> Adder3 + Reg12 -- Feedback --> Adder4 + Reg12 -- Feedback --> Adder12 + + BMF[Beginning of multiframe] --> Reg1 & Reg2 & Reg3 & Reg4 & Reg5 & Reg6 & Reg7 & Reg8 & Reg9 & Reg10 & Reg11 & Reg12 + EMF[End of multiframe] --> Latch12 & Latch11 & Latch10 & Latch9 & Latch8 & Latch7 & Latch6 & Latch5 & Latch4 & Latch3 & Latch2 & Latch1 + +``` + +The diagram illustrates a CRC-12 generator architecture. It consists of 12 register cells, labeled 'Regist. cell 1 clear' through 'Regist. cell 12 clear'. The data flow starts with 'Data input' entering the first adder node (+). This node also receives feedback from the output of the last register cell (cell 12). Adders are placed before cells 1, 2, 3, 4, and 12. The outputs of the register cells are connected in a chain. Each register cell output is also connected to a 'Latch enable' block. These blocks produce the final CRC outputs, labeled CRC 12 down to CRC 1. Two control signals, 'Beginning of multiframe' (connected to register clear inputs) and 'End of multiframe' (connected to latch enable inputs), manage the timing of the calculation. + +Schematic diagram of a CRC-12 generator showing 12 register cells, adders, latches, and control lines. + +T1814320-92/d27 + +FIGURE II.4/G.961 +**CRC-12 generator** + +##### **II.8.3.2.6 Cold-start-only (CSO) bit** + +The M4 bit in the fifth frame of the multiframe transmitted by an NT1 is reserved for cold-start-only indication; its use is optional. If this function is not used, this bit shall be set to ZERO in SN3. See Annex A to Appendix II. + +##### **II.8.3.2.7 DLL-only-activation (UOA) bit** + +The M4 bit in the seventh basic frame of multiframes transmitted by an LT is reserved for DLL-only-activation; its use is optional. If this function is not used, this bit shall be set to ONE in SL2 and SL3. See Annex A to Appendix II. + +##### **II.8.3.2.8 S/T-interface-activity-indicator (SAI) bit** + +The M4 bit in the seventh basic frame of the multiframes transmitted by an NT1 is reserved for S/T-interface-activity-indication; its use is optional. If this function is not used, this bit shall be set to ONE in SN3. See Annex A to Appendix II. + +##### **II.8.3.2.9 Alarm indicator bit (AIB)** + +The M4 bit in the eighth basic frame of the multiframes transmitted by the network toward the NT1 is reserved for the alarm indicator bit; its use is optional. If this function is not used, the AIB bit shall be set to ONE in SN3. See Annex A to Appendix II. + +##### **II.8.3.2.10 Network indicator bit (NIB) for network use** + +The NIB bit shall be the M4 bit in the eighth basic frame of multiframes transmitted by the NT1 toward the network. The NT1 shall always set this bit to binary ONE in SN3. + +NOTE – The use of NIB at the LT or in the REG is beyond the scope of this Recommendation. + +##### **II.8.3.2.11 Reserved bits** + +All bits in M4, M5, and M6 not otherwise assigned are reserved for future standardization. Reserved bits shall be set to ONE before scrambling. + +#### **II.8.3.3 Embedded operations channel (EOC) functions** + +Twenty-four bits per multiframe (2 kbit/s) are allocated to an embedded operations channel (EOC) which supports operations communications needs between the network and the NT1. + +NOTE – The use of the EOC functions for REG mode and the necessary messages is beyond the scope of this Recommendation. + +##### **II.8.3.3.1 EOC frame** + +The EOC frame shall be composed of 12 bits synchronized to the multiframe (see Table II.1). + +TABLE II.1/G.961 + +**The EOC frame layout** + +| Bits | 3 | 1 | 8 | +|-------------------|---------------|--------------------|------------| +| Function provided | Address field | Data/msg indicator | Info field | + +The three-bit address field may be used to address up to seven locations. Only the specification of addresses of messages for the NT1 are within the scope of this Recommendation. The additional addresses are for intermediate network elements where the system is used to extend access involving carrier systems. + +The data/message indicator bit shall be set to ONE to indicate that the information field contains an operations message; it shall be set to ZERO to indicate that the information field contains numerical data. Up to 256 messages may be encoded in the information field. + +Exactly two EOC frames shall be transmitted per multiframe consisting of all M1, M2, and M3 bits (see Figure II.3). + +##### II.8.3.3.2 Mode of operation + +The EOC protocol operates in a repetitive command/response mode. Three identical properly-addressed consecutive messages shall be received before an action is initiated. Only one message, under the control of the network, shall be outstanding (not yet acknowledged) on a complete Basic Access EOC at any one time. + +The network shall continuously send an appropriately addressed message. In order to cause the desired action in the addressed element, the network shall continue to send the message until it receives three identical consecutive EOC frames from the addressed device that agree with the transmitted EOC frame. When the network is trying to activate an EOC function, autonomous messages from the NT1 will interfere with confirmation of receipt of a valid EOC message. The sending by the NT1 and receipt by the network of three identical consecutive properly-addressed Unable to Comply messages constitutes notification to the network that the NT1 does not support the requested function, at which time the network may abandon its attempt. + +The addressed element shall initiate action when, and only when, three identical, consecutive, and properly-addressed EOC frames that contain a message recognized by the addressed element, have been received. The NT1 shall respond to all received messages. The response should be an echo of the received EOC frame towards the network with two exceptions described below. Any reply or echoed EOC frame shall be in the next available returning EOC frame, which allows a processing delay of approximately 0.75 ms. + +If the NT1 does not recognize the message (data/message bit set to binary ONE) in a properly-addressed EOC frame, rather than echo, on the third and all subsequent receipts of that same correctly-addressed EOC frame, it shall return the Unable to Comply message in the next available EOC frame. + +If the NT1 receives EOC frames with addresses other than its own address (000), or the broadcast address (111), it shall, in the next available EOC frame, return an EOC frame toward the network containing the Hold State message and its own address (the NT1, address, 000). + +If an NT1, not implementing EOC data transfer functions, receives a data byte (Data/message bit set to binary ZERO) in a properly-addressed EOC frame, rather than echo on the third and subsequent receipts of that same correctly-addressed EOC frame, it shall return the Unable to Comply message in the next available EOC frame. + +The protocol specification has made no provision for autonomous messages from the NT1. + +All actions to be initiated at the NT1 shall be latching, permitting multiple EOC-initiated actions to be in effect simultaneously. A separate message shall be transmitted by the network to unlatch. + +##### II.8.3.3.3 Addressing + +An NT1 shall recognize either of two addresses, an NT1 and a broadcast address. These addresses are as follows: + +| | Node | Address | +|-----------|-------------|---------| +| | NT1 | 000 | +| Broadcast | (all nodes) | 111 | + +An NT1 shall use the address 000 in sending the Unable to Comply message. + +##### II.8.3.3.4 Definition of required EOC functions + +- 1) **operate 2B + D loopback:** This function directs the NT1 to loop back the user-data (2B + D) bit stream toward the network. This loopback may be transparent or non-transparent but in either case will continue to provide sufficient signal to allow the TE to maintain synchronization to the NT1. +- 2) **operate B1-channel (or B2-channel) loopback:** This function directs the NT1 to loop back an individual B-channel toward the network. The individual B-channel loopback can provide per-channel maintenance capabilities without totally disrupting service to the customer. This loopback is transparent. The implementation and operation of the individual B-channel loopbacks is optional. +- 3) **return to normal:** The purpose of this message is to release all outstanding EOC controlled operations and to reset the EOC processor to its initial state. +- 4) **unable to comply acknowledgement:** This will be the confirmation that the NT1 has validated the receipt of an EOC message, but that the EOC message is not in the menu of the NT1. +- 5) **request corrupt CRC:** This message requests the sending of corrupt CRCs toward the network, until cancelled with return to normal. +- 6) **notify of corrupted CRC:** This message notifies the NT1 that intentionally corrupted CRCs will be sent from the network until cancellation is indicated by return to normal. +- 7) **hold state:** This message is sent by the network to maintain the NT1 EOC processor and any active EOC controlled operations in their present state. This message may also be sent by the NT1 toward the network to indicate that the NT1 has received an EOC frame with an improper address. + +##### II.8.3.3.5 Codes for required EOC functions + +Table II.2 shows the codes for each of the EOC functions defined in II.8.3.3.4. + +TABLE II.2/G.961 + +###### Messages required for command/response EOC mode + +| Message | Origin (o) & destination (d) | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---------|-----| +| | Message code | Network | NT1 | +| Operate 2B + D loopback | 0101 0000 | o | d | +| Operate B 1 -channel loopback a) | 0101 0001 | o | d | +| Operate B 2 -channel loopback a) | 0101 0010 | o | d | +| Request corrupted CRC | 0101 0011 | o | d | +| Notify of corrupted CRC | 0101 0100 | o | d | +| Return to normal | 1111 1111 | o | d | +| Hold state | 0000 0000 | d/o | o/d | +| Unable to comply acknowledgement | 1010 1010 | d | o | +| a) The use of B 1 - and B 2 -channel loopbacks is optional. However, the loopback codes are reserved for these functions. | | | | + +Sixty-four EOC messages have been reserved for non-standard applications in the following four blocks of 16 codes each (x is ONE or ZERO): 0100 xxxx, 0011 xxxx, 0010 xxxx, 0001 xxxx. Another 64 EOC message codes have been reserved for internal network use in the following four blocks of 16 codes each (x is ONE or ZERO): 0110 xxxx, 0111 xxxx, 1000 xxxx, 1001 xxxx. All remaining codes not defined in Table II.2 and not reserved for non-standard applications or for internal network use are reserved for future standardization. Thus, 120 codes associated with the NT1 (000) and broadcast (111) addresses, are available for future standardization, i.e. 256 total codes, minus eight defined codes from the table, minus 64 codes for non-standard applications, minus 64 codes for internal network use. + +NOTE – The reservation of codes for non-standard applications does not in any way endorse their use. Any use of such messages shall not interfere with the EOC protocol. An NT1 and an LT that support messages for non-standard applications may not function properly together. + +## II.9 Scrambling + +The data stream in each direction of transmission shall be scrambled with a 23rd-order polynomial (see Figure II.5) prior to the insertion of FW. + +In the LT-NT1 direction the polynomial shall be: + +$$1 \oplus x^{-5} \oplus x^{-23}$$ + +where + +$\oplus$ = modulo 2 summation. + +In the NT1-LT direction the polynomial shall be: + +$$1 \oplus x^{-18} \oplus x^{-23}$$ + +where + +$\oplus$ = modulo 2 summation. + +The binary data stream shall be recovered in the receiver by applying the same polynomial to the scrambled data as was used in the transmitter. + +NOTE – Binary ONEs and ZEROs entering the NT1 receiver from the interface at reference point T, or entering the LT side transceiver from the network, must appear as binary ONEs and ZEROs respectively, at the input of the scrambler. Also, during transmission/reception of the frame word or inverted frame word, the state of the scrambler must remain unchanged. (Caution: It is common for the input bits to be all ONEs, e.g. during idle periods or during start-up. For the ONEs to become scrambled, the initial state of the scrambling shift register must not be all ONEs.) + +## II.10 Start-up and control + +This subclause gives requirements for the start-up and turn-off processes, including examples of activation/deactivation requests, indicators of activation and deactivation, and indicators of errors. The transmission system is capable of loopbacks but these are not illustrated by examples. A specification of a procedure enabling the transmission system to be activated without activating the interface at reference point T is given in Annex A to Appendix II on extension functions. + +The following definitions are for the purpose of clarifying requirements that are to follow: + +- 1) **total activation:** The word activation is used here to describe a process that includes the start-up process as given in 2) below and activation as given in Recommendation I.430. +- 2) **start-up:** A process characterized by a sequence of signals produced by the LT and by the NT1. Start-up results in establishment of the master-slave mode, i.e. synchronization of the receivers and the training of equalizers and echo cancellers to the point that two-way transmission requirements are met. +- 3) **warm-start:** The start-up process that applies to transceivers meeting the optional warm-start activation-time requirements after they have once been synchronized and have subsequently responded to a deactivation request. Warm-start applies only if there have been no changes in line characteristics and equipment. Transceivers that meet warm-start requirements are called warm-start transceivers. + +NT1 transmit scrambler (NT1 to LT) + +![Block diagram of NT1 transmit scrambler (NT1 to LT) showing a sequence of delay blocks (x^-1) and XOR gates. Input D_i is XORed with feedback from the 18th and 23rd delays to produce D_s.](ae0a735d106290c594b0bafb1f5e72e7_img.jpg) + +$$D_s = D_i \oplus D_s \cdot x^{-18} \oplus D_s \cdot x^{-23}$$ + +Block diagram of NT1 transmit scrambler (NT1 to LT) showing a sequence of delay blocks (x^-1) and XOR gates. Input D\_i is XORed with feedback from the 18th and 23rd delays to produce D\_s. + +NT1 transmit scrambler (LT to NT1) + +![Block diagram of NT1 transmit scrambler (LT to NT1) showing a sequence of delay blocks (x^-1) and XOR gates. Input D_i is XORed with feedback from the 5th and 23rd delays to produce D_s.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +$$D_s = D_i \oplus D_s \cdot x^{-5} \oplus D_s \cdot x^{-23}$$ + +Block diagram of NT1 transmit scrambler (LT to NT1) showing a sequence of delay blocks (x^-1) and XOR gates. Input D\_i is XORed with feedback from the 5th and 23rd delays to produce D\_s. + +LT receive descrambler (NT1 to LT) + +![Block diagram of LT receive descrambler (NT1 to LT) showing a sequence of delay blocks (x^-1) and XOR gates. Input D_o is XORed with feedback from the 18th and 23rd delays to produce D_s.](1ce027dfd26183da52137cf990213724_img.jpg) + +$$D_o = D_s \cdot (1 \oplus x^{-18} \oplus x^{-23})$$ + +Block diagram of LT receive descrambler (NT1 to LT) showing a sequence of delay blocks (x^-1) and XOR gates. Input D\_o is XORed with feedback from the 18th and 23rd delays to produce D\_s. + +NT1 receive descrambler (LT to NT1) + +![Block diagram of NT1 receive descrambler (LT to NT1) showing a sequence of delay blocks (x^-1) and XOR gates. Input D_o is XORed with feedback from the 5th and 23rd delays to produce D_s.](a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg) + +$$D_o = D_s \cdot (1 \oplus x^{-5} \oplus x^{-23})$$ + +T1814330-92/d28 + +Block diagram of NT1 receive descrambler (LT to NT1) showing a sequence of delay blocks (x^-1) and XOR gates. Input D\_o is XORed with feedback from the 5th and 23rd delays to produce D\_s. + +FIGURE II.5/G.961 +Scrambler and descrambler + +- 4) **cold-start:** The start-up process that applies to transceivers that either do not meet optional warm-start activation-time requirements, or have not been continuously in a deactive state that resulted from a deactivation request to the NT1. Cold start also applies if there have been changes in line characteristics or equipment or both. A cold start shall always start from the RESET state. +- 5) **cold-start-only:** NT1 transceivers that do not meet optional warm-start activation-time requirements (see II.10.6) are called cold-start-only transceivers. The use of cold-start-only transceivers is optional. +- 6) **full operational status:** Full operational status of a transceiver means that it has: + - a) acquired bit timing (for NT1); bit timing phase (for LT), and frame synchronization from the incoming signal from the other transceiver; + - b) recognized the incoming multiframe marker; and + - c) fully converged both echo canceller and equalizer coefficients. +- 7) **deactivation:** The word deactivation is used here to describe a process that includes the turn-off process as given in 8) below and deactivation of the S/T interface as given in Recommendation I.430. +- 8) **turn-off:** The process by which a pair of fully operational transceivers transition to the RESET state. +- 9) **RESET:** The RESET state consists of two sub-states: the RECEIVE RESET and the FULL RESET states. In other subclauses of this Recommendation, the term RESET is used to refer to the FULL RESET state. + +RESET has no implications about the state of convergence of the equalizer or echo canceller coefficients of the transceiver. + +For specific transceiver implementations, RESET states (or sub-states) may mean different and possibly multiple internal states. + +- 10) **FULL RESET:** The FULL RESET state is one in which a transceiver has detected the loss of signal from the far end and is not transmitting (sending signal to the DLL). + +The FULL RESET state shall also be entered following power up. + +While in FULL RESET, NT1s may initiate transmission only if responding to a new power off/on cycle or to a new request for service from the customer terminal (TE). Under all other conditions, where the transceivers have been turned off (see II.10.1.5.2), the NT1s shall remain quiet, i.e. they shall not start transmitting any signal until they have received the TL signal (start-up tone) from the network. + +- 11) **RECEIVE RESET:** The RECEIVE RESET state is a transient state in which NT1 has detected the loss of signal from the far end and is not transmitting (sending signal to the DLL). In addition, the transceiver is not permitted to initiate the start-up sequence (send wake-up tone) but shall be capable of responding to the start-up sequence (detecting wake-up tone). Unless it responds to a wake-up tone, an NT1 must remain in this state for at least 40 ms after detecting the loss of received signal, as specified in II.10.1.5.2 and II.10.2, after which time the transceiver shall enter the FULL RESET state. +- 12) **power down state:** While in RESET state, an NT1 may be in this condition. The NT1 consumes less power but is capable of detecting TL from the network side and/or INFO 1 from the user side. +- 13) **transparency:** The word transparency is used in this Recommendation to mean that the B1-, B2-, D-channel (2B + D) bits received by the transceiver on the interface are passed to the TE at the NT and to the network at the LT. Likewise, when a transceiver is transparent, 2B + D bits sent to the transceiver at the LT from within the network or at the NT from the TE are transmitted on the interface. Conversely, when a transceiver is not transparent, 2B + D bits received on the interface are not passed along to the + +TE at the NT or to the network at the LT. Likewise, when a transceiver is not transparent, 2B + D bits from within the network at the LT or from the TE at the NT are not transmitted on the interface. Transparency applies separately to each transceiver. Conditions for transparency are discussed in II.10.3.4. + +### II.10.1 Signals used for start-up and control + +#### II.10.1.1 Signals during start-up + +Figure II.6 defines the signals produced by the transceivers during start-up. These signals apply during both types of start up; i.e. cold start, and warm start. During start-up, all signals at the interface shall consist of sequences of symbols of the shape defined in II.12.2. + +With the exception of the wake-up tones (TN and TL), the scrambler shall be used in the normal way in formulating the signals. For example, Figure II.7 shows ONEs for B- and D-channel bits and the overhead bits in the signal SN1. These ONEs are scrambled before coding, producing random pulses in these positions at the interface. + +Except where noted otherwise in Figure II.7, all the pulse sequences are framed and multiframed in accordance with the normal frame structure shown in Figures II.1, II.2 and II.3, and all pulses represent scrambled bits except those in the frame word. The signals TN and TL are 10 kHz tones generated by repeating the following unscrambled and unframed symbol pattern: + +![Timing diagram for transceiver start-up showing signal sequences for NT1 and Network over time intervals A, B, C, and D, with state transitions T0 through T7.](753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg) + +... +3 +3 +3 +3 −3 −3 −3 −3 ... + +The diagram illustrates the start-up sequence for transceivers across four time intervals: A, B, C, and D. The top horizontal line represents signals from NT1 to Network, and the bottom horizontal line represents signals from Network to NT1. + +- Interval A:** Starts at T0. Duration $\leq 4$ ms. NT1 transmits TN (6 frames) followed by an optional SN1. +- Interval B:** Starts at T2. Duration $\leq 480$ ms. Network transmits TL (2 frames) followed by SL1 (opcional). +- Interval C:** Starts at T4. NT1 transmits SN2. +- Interval D:** Starts at T6. NT1 transmits SN3. Network transmits SL2 during interval C and SL3 starting at T7. + +Timing constraints shown in the diagram: + +- $A + C \leq 5$ s for cold start +- $A + C \leq 150$ ms for warm start +- $B + D \leq 10$ s for cold start +- $B + D \leq 150$ ms for warm start + +Reference: T1814340-92/d29. + +Timing diagram for transceiver start-up showing signal sequences for NT1 and Network over time intervals A, B, C, and D, with state transitions T0 through T7. + +Time: Description of event or state: + +- T0 RESET state. +- T1 Network and NT1 are awake. +- T2 NT1 discontinues transmission, indicating that the NT1 is ready to receive signal. +- T3 Network responds to termination of signal and begins transmitting signal toward the NT1. +- T4 Network begins transmitting SL2 toward the NT1, indicating that the network is ready to receive SN2. +- T5 NT1 begins transmitting SN2 toward the network, indicating that NT1 has acquired FW frame and detected SL2. +- T6 NT1 has acquired multiframe marker, and fully operational. +- T7 Network has acquired multiframe marker, and is fully operational. + +FIGURE II.6/G.961 +**State sequence for transceiver start-up** + +| Signal | Frame word (FW) | Multiframe (IFW) | 2B + D | M | Start | Stop | Times (frames) | +|--------|-----------------|------------------|---------------------|--------|-------|------|----------------| +| TN | ±3 Y | ±3 Y | ±3 Y | ±3 Y | ♦ | ♦ | 6 | +| SN1 | Present | Absent | 1 | 1 | T1 | T2 | – | +| SN2 | Present | Absent | 1 | 1 | T5 | T6 | – | +| SN3 | Present | Present | Normal + | Normal | T6 | * | – | +| TL | ±3 Y | ±3 Y | ±3 Y | ±3 Y | ♦ | ♦ | 2 | +| SL1 | Present | Absent | 1 | 1 | T3 | T4 | – | +| SL2 | Present | Present | 0 | Normal | T4 | T7 | – | +| SL3 | Present | Present | Normal + | Normal | T7 | * | – | + +Y Tones have alternating pattern of four +3 symbols followed by four –3 symbols, and no FW. + +♦ See Figures II.6 and II.10.1.3 for start and/or stop time of this signal. + +TN, TL Tones produced by NT1 or LT, respectively (see II.10.1.1). + +SNx, SLx Pulse patterns produced by NT1 or LT, respectively. + +Tx Notation refers to transition instants defined in Figure II.6. + +Absent Under multiframe this notation means only that FW is transmitted instead of IFW. + +Normal Normal means that the M bits are transmitted onto the 2-wire line as required during normal operation; e.g. valid CRC bits, EOC bits, and indicator bits are transmitted. + +Normal+ Except to perform a loopback, 2B + D bits shall remain in the previous state (SN2 or SL2) until both ACT bits indicate full transparency of the B- and D-channels (i.e. the 2B + D bits of SN3 and SL3 shall remain set to ONE and ZERO, respectively, until transparency is achieved at both ends of the DLL). + +\* Signals SN3 and SL3 continue indefinitely (or until turn-off). + +FIGURE II.7/G.961 + +##### Definitions of signal during start-up + +#### II.10.1.2 Line rate during start-up + +During start-up, the network shall produce symbols at the nominal line rate within the tolerance specified in II.2.1.2. + +The symbol rate from the NT1 shall be 80 kbauds ± 100 ppm. + +#### II.10.1.3 Start-up sequence + +Figure II.6 shows the sequence of signals at the interface that are generated by the transceivers. The transition points in the sequence are also defined in Figure II.7. For further information on the events at the interface at reference point T, the reader is referred to Recommendation I.430. + +#### **II.10.1.4 Wake-up** + +When transceivers are in the RESET state or are deactive as a result of responding to a deactivation request, either transceiver may initiate start-up by sending a tone as defined in Figure II.7. + +#### **II.10.1.5 Progress indicators** + +##### **II.10.1.5.1 Start-up** + +In the NT1 to LT direction, the ACT bit remains set to ZERO until the customer equipment indicates progress in getting ready to transmit. The corresponding action at the T reference point in the customer equipment is receipt of the signal INFO 3. To communicate this progress indication, ACT from the NT1 is set to ONE. Assuming INFO 3 occurs before T6 and T7, this progress indication shall not affect overhead symbols at the interface until T6, when the NT1 overhead bits are allowed to be normal, and may not be detected by the LT until T7. + +After event T7 (Figure II.6) and after ACT = ONE is received from the NT1, the LT sets the ACT bit to ONE to communicate readiness for layer 2 communication (see II.8.3.2.2). + +##### **II.10.1.5.2 Deactivation** + +All transceivers shall cease transmission following loss of received signal. There are different turn-off procedures for transceivers that have achieved full operational status than for transceivers that have not (see II.10.2). + +The network may take advantage of the capabilities of warm-start NT1s by announcing turn-off. In announcing turn-off, the network shall change DEA from binary ONE to ZERO in at least three consecutive multiframes before ceasing transmission. It shall cease transmission before sending the DEA bit in the multiframe following the multiframe in which DEA = ZERO is sent for the last time. + +During multiframes with DEA = ZERO, the NT1 has time to prepare for turn-off. + +After the warm-start NT1 has prepared itself for turn-off, it shall upon detection of loss of signal from the network, cease transmission and enter the RECEIVE RESET state within 40 ms of the occurrence of the transition to no signal at its interface. As specified in II.10.2, unless it responds to a TL signal from the network, it shall not initiate the transmission of wake-up tone for a period of at least 40 ms after it ceases transmission, and then it shall enter the FULL RESET state. + +The network side transceiver, after announcing turn-off and ceasing transmission, shall enter the FULL RESET state upon detection of loss of received signal from the NT1. + +Although NT1s are not permitted to initiate turn-off, the LT shall respond to loss of signal as stated above. + +### **II.10.2 Timers** + +Timers shall be used to determine entry into the RESET states. Upon the occurrence of any of the following conditions: + +- 1) failure to complete start-up within 15 s (warm or cold start); +- 2) loss of received signal for more than 480 ms; or +- 3) loss of synchronization for more than 480 ms, + +a transceiver shall cease transmission and, as specified in II.10.2, shall enter the RECEIVE RESET state and remain for at least 40 ms (unless it responds to a wake-up tone), after which it shall enter the FULL RESET state. The manner of entering the RECEIVE RESET state is different for the different conditions listed above. + +For conditions 1) or 3), it shall cease transmission and then, upon the subsequent detection of the loss of received signal, the transceiver shall enter the RECEIVE RESET state. Its response time to a loss of signal (after conditions 1) or 3) have been satisfied) shall be such that it shall enter the RECEIVE RESET state and be capable of responding to the initiation of wake-up tone by the far-end transceiver within 40 ms after the far-end transceiver ceases transmission. + +For condition 2), the transceiver shall immediately enter the RECEIVE RESET state. + +For conditions 2) and 3), these requirements apply to transceivers after multiframe synchronization is achieved (see T6 and T7 in Figure II.6). + +In addition, an NT1 shall enter the FULL RESET state if the signal is not received within 480 ms after it ceases the transmission of TN, or SN1 if it is sent (see T2 to T3 in Figures II.6 and II.7). + +### **II.10.3 Description of the start-up procedure** + +#### **II.10.3.1 Start-up from customer equipment** + +While the NT1 and LT remain in the deactive state as a result of receiving and responding to a deactivation request, or while they are in RESET, a request for activation from the customer equipment shall result in the TN signal (tone) being sent from the NT1 toward the LT. The LT, on receiving TN shall remain silent until detection of cessation of signal from the NT1. The rest of the sequence then follows as indicated in Figures II.6 and II.7. If the LT happens to try to activate at the same time, it may send a TL tone during the TN tone without harm. + +For cold-start-only NT1s, start-up shall be attempted upon NT1 power-up. After an unsuccessful start-up attempt, the NT1 DLL transceiver may enter FULL RESET. + +While in the RESET state, NT1 may initiate transmission only if responding to a new power off/on cycle or a new service request. Under all other conditions where the system has been deactivated, the NT1s shall remain quiet, i.e. they shall not start transmitting any signal until the NT1 has received the TL signal from the LT. + +#### **II.10.3.2 Start-up from the network** + +While the NT1 and LT remain in the deactive state as a result of receiving and responding to a deactivation request, or while they are in RESET, a request for activation from the LT shall result in the TL signal being sent from the LT toward the NT1. The NT1, on receiving TL shall respond with TN within 4 ms from the beginning of TL. The rest of the sequence then follows as indicated in Figures II.6 and II.7. + +#### **II.10.3.3 Sequence charts** + +Examples of sequence charts for start-up by both terminal and ET equipment are given in Figures II.8 and II.9. + +#### **II.10.3.4 Transparency** + +Transparency of the transmission in both directions by the NT1 shall be provided after the NT1 achieves full operational status (T6), and both ACT = ONE from the LT and DEA = ONE. Full operational status of the NT1 means that the NT1 has: + +- 1) acquired bit timing and frame synchronization from the incoming signal from the LT; +- 2) recognized the multiframe marker from the LT; and +- 3) fully converged both its echo canceller and equalizer coefficients. + +![Sequence diagram showing the total activation initiated by the exchange between an LT (Line Terminal) and an NT1 (Network Terminal 1). The diagram includes lifelines for L2, ET, L1, U, L1, NT1, L1, S/T, L1, TE, and L2. Key messages include Start M5, TL, SL0, TN, SN1, SN0, SL1, DEA=1, UOA=1, SL2, FW Sync, SN2, IFW Sync, SN3, Stop M5, SL3, SAI=1, ACT=1, 2B + D = N, Start M4, Stop M4, INFO 0, INFO 2, INFO 3, and INFO 4. The process involves multiple exchanges of control and data signals to establish synchronization and activate the channels.](89f8aefc01866631793087542316cef2_img.jpg) + +T1814350-92/d30 + +Sequence diagram showing the total activation initiated by the exchange between an LT (Line Terminal) and an NT1 (Network Terminal 1). The diagram includes lifelines for L2, ET, L1, U, L1, NT1, L1, S/T, L1, TE, and L2. Key messages include Start M5, TL, SL0, TN, SN1, SN0, SL1, DEA=1, UOA=1, SL2, FW Sync, SN2, IFW Sync, SN3, Stop M5, SL3, SAI=1, ACT=1, 2B + D = N, Start M4, Stop M4, INFO 0, INFO 2, INFO 3, and INFO 4. The process involves multiple exchanges of control and data signals to establish synchronization and activate the channels. + +###### NOTES + +- 1 Receipt of INFO3 and SL3 at the NT1 can theoretically occur in either order. +- 2 For symbols and abbreviations see Table II.5. +- 3 The reading of the UOA bit is necessary only when the option “DLL-only turn-on” is implemented. + +FIGURE II.8/G.961 +**Total activation initiated by the exchange** + +Transparency of the transmission in both directions at the LT shall be provided when the LT: + +- 1) achieves full operational status (T7); +- 2) detects the presence of the multiframe marker from the NT1; and +- 3) receives ACT = ONE from the NT1. + +Full operational status at the LT means that the LT has: + +- 1) acquired bit timing phase of the incoming signal from the NT1, and frame synchronization; +- 2) recognized the multiframe marker from the NT1; +- 3) fully converged both its echo canceller and equalizer coefficients. + +At the LT, transparency of the B- and D-channels shall occur at any time during either the first LT transmitted superframe with ACT = ONE or during the last LT transmitted superframe with ACT = ZERO. Transparency occurs at the transition from all zeros to “normal” in the B- and D-channels in SL3. For example, referring to Figure II.1, suppose superframe A is the last transmit superframe with ACT = ZERO, superframe B is the first transmit superframe with ACT = ONE, and superframes C and D continue with ACT = ONE. The transition to transparency may occur not later than the first bit of superframe C. This means that all B- and D-channel bits in superframes C and D shall be transmitted transparently, provided that conditions for transparency have been maintained. + +![Sequence diagram showing the total activation initiated by terminal equipment (TE) in an ISDN interface. Lifelines are L2, ET, L1, U, L1, NT1, L1, S/T, L1, TE, L2. The sequence starts with 'Start M5' from ET to L1, followed by a series of messages (TN, SN1, SN0, SL1, DEA=1, UOA=1, SL2, FW Sync, SN2, SAI=1, IFW Sync, SN3, IFW Sync) from L1 to U. U then sends 'Start M4' to NT1. NT1 sends 'INFO 1' to TE. TE sends 'INFO 2' to NT1. NT1 sends 'Stop M4' to U. U sends 'Stop M5' to ET. ET sends 'FE4' to L2. NT1 sends 'INFO 3' to TE. TE sends 'INFO 4' to NT1. NT1 sends 'ACT=1' to U. U sends '2B + D = N' to L1. L1 sends 'SN3' to U. U sends 'ACT=1' to L1. L1 sends 'FE4' to ET. The diagram ends with 'T1814360-92/d31'.](a2251e3bbfcd726b68cc50b091e53b02_img.jpg) + +Sequence diagram showing the total activation initiated by terminal equipment (TE) in an ISDN interface. Lifelines are L2, ET, L1, U, L1, NT1, L1, S/T, L1, TE, L2. The sequence starts with 'Start M5' from ET to L1, followed by a series of messages (TN, SN1, SN0, SL1, DEA=1, UOA=1, SL2, FW Sync, SN2, SAI=1, IFW Sync, SN3, IFW Sync) from L1 to U. U then sends 'Start M4' to NT1. NT1 sends 'INFO 1' to TE. TE sends 'INFO 2' to NT1. NT1 sends 'Stop M4' to U. U sends 'Stop M5' to ET. ET sends 'FE4' to L2. NT1 sends 'INFO 3' to TE. TE sends 'INFO 4' to NT1. NT1 sends 'ACT=1' to U. U sends '2B + D = N' to L1. L1 sends 'SN3' to U. U sends 'ACT=1' to L1. L1 sends 'FE4' to ET. The diagram ends with 'T1814360-92/d31'. + +###### NOTES + +- 1 Receipt of INFO3 and SL3 at the NT1 can theoretically occur in either order. +- 2 For symbols and abbreviations see Table II.5. +- 3 The reading of the UOA bit is necessary only when the option "DLL-only turn-on" is implemented. + +FIGURE II.9/G.961 +**Total activation initiated by terminal equipment** + +At the LT, transparency of the B- and D-channels in the LT-to-network direction may occur at a different time than transparency in the LT-to-NT direction. However, in both directions the LT shall become transparent during the two transmit superframes A and B described in the example. The NT may not yet have achieved transparency during this interval. + +After both the LT and the NT1 achieve transparency in both directions, the ACT bits shall continue to reflect the state of readiness of the LT and the terminal equipment for layer 2 communication. The ACT bit in the NT1-to-LT direction shall reflect the status of the NT1 side of the interface. Whenever either end, for any reason, loses its readiness to communicate at layer 2 (e.g. the terminal is unplugged), that end shall set its transmitted ACT bit to ZERO. A change of status of this bit shall be repeated in at least three consecutive transmitted multiframes. + +### II.10.4 State transition table for the NT1 + +Table II.3 provides an example of a state transition table for the NT1 as a function of INFOs, SIGs, and timers. For symbols, abbreviations and notes to this table, see Table II.5. + +### II.10.5 State transition table for the LT + +Table II.4 provides an example of a state transition table for the LT as a function of FEs, SIGs, and timers. For symbols, abbreviations and notes to this table, see Table II.5. + +TABLE II.3/G.961 + +#### State transition table for the NT1 as a function of INFOs, SIGs and timers + +| Event
↓ | State name | Power off | Full reset | Alerting | EC training (optional) | EC converged | FW sync | IFW sync | Pending active | Active | Pending deactivation | Tear down | TE inactive | Receive reset | L2 operated TE active (Note 23) | L2 operated TE inactive (Note 23) | +|-----------------------------------------------------------|------------------------------|-----------|---------------------|------------|------------------------|--------------|----------|-------------|------------------|-------------|----------------------|-----------|-------------|------------------|---------------------------------|-----------------------------------| +| | State code (Fig. II.6 event) | NT0 | NT1 (T0) | NT2 | NT3 (T1) | NT4 (T2) | NT5 (T5) | NT6 (T6) | NT7 | NT8 | NT9 | NT10 | NT11 | NT12 | NT7A | NT11A | +| | Signal → LT | SN0 | SN0 | TN | SN1 | SN0 | SN2 | SN3 ACT = 0 | SN3 ACT = 1 | SN3 ACT = 1 | SN3 (Note 8) | SN0 | SN3 ACT = 0 | SN0 | SN3 ACT = 1 | SN3 ACT = 1 | +| | Signal → TE (Note 7) | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 2 | INFO 2 (Note 22) | INFO 4 | | INFO 0 | INFO 2 | INFO 0 | INFO 4 (Note 17) | INFO 2 (Note 17) | +| Power on | | ST.M4 NT2 | – | – | – | – | – | – | – | – | – | – | – | – | – | – | +| Loss of power (Note 1) | | – | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | +| Received new INFO 1 signal (Notes 2 and 3) | | / | ST.M4 NT2 (Note 12) | – | – | – | – | – | / | / | – | – | / | – | / | – | +| Received INFO 3 signal (ACT = 0, DEA = 1) (Notes 2 and 4) | | / | / | / | / | / | / | NT7 | – | – | – | – | NT7 | – | – | NT7A | +| Received INFO 0 or S/T loss of sync (Notes 2 and 5) | | / | – | – | – | – | – | – | NT11 | NT11 | – | – | – | – | NT11A | – | +| End of tone TN (9 ms) | | / | / | NT3 or NT4 | / | / | / | / | / | / | / | / | / | / | / | / | +| Received tone TL | | / | ST.M4 NT2 | – | / | / | / | / | / | / | / | / | / | ST.M4 STP.M6 NT2 | / | / | + +TABLE II.3/G.961 (cont.) + +#### State transition table for the NT1 as a function of INFOs, SIGs and timers + +| Event
↓ | State name | Power off | Full reset | Alerting | EC training (optional) | EC converged | FW sync | IFW sync | Pending active | Active | Pending deactivation | Tear down | TE inactive | Receive reset | L2 operated TE active (Note 23) | L2 operated TE inactive (Note 23) | +|----------------------------------------------------|------------------------------|-----------|------------|----------|------------------------|--------------|------------|-------------|------------------|-------------|-----------------------------------------|-----------|-------------|---------------|---------------------------------|-----------------------------------| +| | State code (Fig. II.6 event) | NT0 | NT1 (T0) | NT2 | NT3 (T1) | NT4 (T2) | NT5 (T5) | NT6 (T6) | NT7 | NT8 | NT9 | NT10 | NT11 | NT12 | NT7A | NT11A | +| | Signal → LT | SN0 | SN0 | TN | SN1 | SN0 | SN2 | SN3 ACT = 0 | SN3 ACT = 1 | SN3 ACT = 1 | SN3 (Note 8) | SN0 | SN3 ACT = 0 | SN0 | SN3 ACT = 1 | SN3 ACT = 1 | +| | Signal → TE (Note 7) | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 2 | INFO 2 (Note 22) | INFO 4 | | INFO 0 | INFO 2 | INFO 0 | INFO 4 (Note 17) | INFO 2 (Note 17) | +| Echo canceller converged | | / | – | – | NT4 | – | – | – | – | – | – | – | – | – | – | – | +| FW sync and detect SL2 | | / | / | / | / | NT5 | – | – | – | – | – | – | – | / | – | – | +| IFW sync (SL2) | | / | / | / | / | / | STP.M4 NT6 | – | – | – | – | – | – | / | – | – | +| Received DEA = 0 (SL2 or SL3) (Note 6) | | / | / | / | / | / | / | NT9 | NT9 | NT9 | – | – | NT9 | / | NT9 | NT9 | +| Received (SL2 or SL3) ACT = 0 and DEA = 1 (Note 1) | | / | / | / | / | / | / | – | – | NT7 | NT6, NT7, NT7A, NT11 or NT11A (Note 13) | – | – | / | – | – | +| Received (SL3) ACT = 1 and DEA = 1 (Note 1) | | / | / | / | / | / | / | – | NT8 | – | NT8 (Note 13) | – | – | / | – | – | +| Loss of synchronization (> 480 ms) (Note 1) | | / | / | / | / | / | / | NT10 | NT10 | NT10 | NT10 | – | NT10 | – | NT10 | NT10 | + +TABLE II.3/G.961 (end) + +State transition table for the NT1 as a function of INFOs, SIGs and timers + +| Event
↓ | State name | Power off | Full reset | Alerting | EC training (optional) | EC converged | FW sync | IFW sync | Pending active | Active | Pending deactivation | Tear down | TE inactive | Receive reset | L2 operated TE active (Note 23) | L2 operated TE inactive (Note 23) | +|--------------------------------------------------------------|------------------------------|-----------|------------|----------|------------------------|--------------|----------|-------------|------------------|-------------|----------------------|------------|-------------|---------------|---------------------------------|-----------------------------------| +| | State code (Fig. II.6 event) | NT0 | NT1 (T0) | NT2 | NT3 (T1) | NT4 (T2) | NT5 (T5) | NT6 (T6) | NT7 | NT8 | NT9 | NT10 | NT11 | NT12 | NT7A | NT11A | +| | Signal → LT | SN0 | SN0 | TN | SN1 | SN0 | SN2 | SN3 ACT = 0 | SN3 ACT = 1 | SN3 ACT = 1 | SN3 (Note 8) | SN0 | SN3 ACT = 0 | SN0 | SN3 ACT = 1 | SN3 ACT = 1 | +| | Signal → TE (Note 7) | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 2 | INFO 2 (Note 22) | INFO 4 | | INFO 0 | INFO 2 | INFO 0 | INFO 4 (Note 17) | INFO 2 (Note 17) | +| Loss of signal (> 480 ms) (Notes 1 and 11) | | / | / | / | / | STP.M4 NT1 | – | ST.M6 NT12 | ST.M6 NT12 | ST.M6 NT12 | / | / | ST.M6 NT12 | – | ST.M6 NT12 | ST.M6 NT12 | +| Expiry of timer M4 (15 seconds) (Note 1) | | / | / | / | NT10 | NT10 | NT10 | / | / | / | / | / | / | – | / | / | +| Loss of signal (< 40 ms) | | / | / | / | / | – | – | – | – | – | ST.M6 NT12 | ST.M6 NT12 | – | / | – | – | +| Expiry of timer M6 (40 ms) (Note 1) | | / | / | / | / | / | / | / | / | / | / | / | / | NT1 | / | / | +| Received EOC (SL3) Loopback 2 (L2) request (Notes 18 and 23) | | / | / | / | / | / | / | NT11A | NT7A | NT7A | / | / | NT11A | / | – | – | +| Received EOC Return to normal request (Note 23) | | / | / | / | / | / | / | / | / | – | – | – | – | / | NT7 | NT11 | + +NOTE – For symbols, abbreviations, and notes, see Table II.5. + +TABLE II.4/G.961 + +#### **State transition table for the LT as a function of FEs, SIGs and timers** + +| Event
↓ | State name | Power off | Full reset | Alerting | Awake | EC training (optional) | EC converged | FW sync | IFW sync | Active | Deactivation alerting | Tear down | Pending deactivation | Receive reset | L2 set (Note 23) | +|---------------------------------------------------------------|------------------------------|---------------------|------------|---------------|------------|------------------------|---------------------------|---------------------------|----------------------------------------|---------------------------|---------------------------|------------|------------------------|---------------|----------------------------------------| +| | State code (Fig. II.6 event) | LT0 | LT1 (T0) | LT2 | LT3 (T1) | LT4 (T3) | LT5 (T4) | LT6 | LT7 (T7) | LT8 | LT9 | LT10 | LT11 | LT12 | LT8A | +| | Signal → NT | SL0 | SL0 | TL | SL0 | SL1 | SL2
DEA = 1
ACT = 0 | SL2
DEA = 1
ACT = 0 | SL3
DEA = 1
ACT = 0
(Note 19) | SL3
DEA = 1
ACT = 1 | SL3
DEA = 0
ACT = 0 | SL0 | SL0 | SL0 | SL3
DEA = 1
ACT = 1
(Note 18) | +| Power on | LT1 | – | – | – | – | – | – | – | – | – | – | – | – | – | | +| Loss of power (Note 1) | – | LT0
FE7 | LT0
FE7 | LT0
FE7 | LT0
FE7 | LT0
FE7 | LT0
FE7 | LT0
FE7 | LT0
FE7 | LT0
FE7 | LT0
FE7 | LT0
FE7 | LT0
FE7 | LT0
FE7 | | +| Activation request (FE1) or Loopback 2 request (FE8) (Note 1) | – | ST.M5
LT2
FE2 | – | – | – | – | – | – | – | – | – | – | – | – | | +| Deactivation request (FE5) (Notes 1 and 9) | – | – | – | – | – | – | – | LT9 | LT9 | – | – | – | – | LT9 | | +| End of tone (TL) (3 ms)
Continue FE1 or FE8 | / | / | LT3 | / | / | / | / | / | / | / | / | / | / | / | | +| Received tone TN
Continue FE1 or FE8 | / | ST.M5
LT3 | – | – | / | / | / | / | / | / | / | / | ST.M5
STP.M7
LT3 | / | | +| Loss of signal energy (TN or SN1)
Continue FE1 or FE8 | / | / | – | LT4 or
LT5 | – | / | / | / | / | / | / | / | / | / | | + +TABLE II.4/G.961 (cont.) + +#### State transition table for the LT as a function of FEs, SIGs and timers + +| Event
↓ | State name | Power off | Full reset | Alerting | Awake | EC training (optional) | EC converged | FW sync | IFW sync | Active | Deactivation alerting | Tear down | Pending deactivation | Receive reset | L2 set (Note 23) | +|-------------------------------------------------|------------------------------|-----------|------------|----------|------------------|------------------------|---------------------------|---------------------------|-------------------------------------|---------------------------|---------------------------|-----------|----------------------|---------------|-------------------------------------| +| | State code (Fig. II.6 event) | LT0 | LT1 (T0) | LT2 | LT3 (T1) | LT4 (T3) | LT5 (T4) | LT6 | LT7 (T7) | LT8 | LT9 | LT10 | LT11 | LT12 | LT8A | +| | Signal → NT | SL0 | SL0 | TL | SL0 | SL1 | SL2
DEA = 1
ACT = 0 | SL2
DEA = 1
ACT = 0 | SL3
DEA = 1
ACT = 0 (Note 19) | SL3
DEA = 1
ACT = 1 | SL3
DEA = 0
ACT = 0 | SL0 | SL0 | SL0 | SL3
DEA = 1
ACT = 1 (Note 18) | +| Echo canceller converged
Continue FE1 or FE8 | | / | – | – | – | LT5 | – | – | – | – | – | – | – | – | – | +| FW sync (SN2 or SN3)
Continue FE1 or FE8 | | / | / | / | / | / | LT6 | – | – | – | – | – | – | / | – | +| IFW sync (SN3)
Continue FE1 or FE8 | | / | / | / | / | / | / | STP.M5
LT7 | – | – | – | – | – | / | – | +| Received ACT = 0 (SN3)
(Note 1) (Note 21) | | / | / | / | / | / | / | / | FE3 | LT7 | – | – | – | / | LT7 | +| Received ACT = 1 (SN3)
Continue FE1 (Note 1) | | / | / | / | / | / | / | / | LT8
FE4 | – | – | – | – | / | – | +| Loss of synchronization
(> 480 ms) (Note 1) | | / | / | / | / | / | / | / | LT10
FE7 | LT10
FE7 | LT10
FE7 | – | – | – | LT10
FE7 | +| Loss of signal
(> 480 ms) (Note 1) | | / | / | / | LT1
(Note 16) | / | – | – | ST.M7
LT12
FE7 | ST.M7
LT12
FE7 | ST.M7
LT12
FE7 | – | – | – | ST.M7
LT12
FE7 | + +TABLE II.4/G.961 (end) + +#### State transition table for the LT as a function of FEs, SIGs and timers + +| Event
↓ | State name | Power off | Full reset | Alerting | Awake | EC training (optional) | EC converged | FW sync | IFW sync | Active | Deactivation alerting | Tear down | Pending deactivation | Receive reset | L2 set (Note 23) | +|-------------------------------------------------------------------|------------------------------|-----------|------------|----------|-------------|------------------------|---------------------------|---------------------------|-------------------------------------|---------------------------|---------------------------|---------------|----------------------|---------------|-------------------------------------| +| | State code (Fig. II.6 event) | LT0 | LT1 (T0) | LT2 | LT3 (T1) | LT4 (T3) | LT5 (T4) | LT6 | LT7 (T7) | LT8 | LT9 | LT10 | LT11 | LT12 | LT8A | +| | Signal → NT | SL0 | SL0 | TL | SL0 | SL1 | SL2
DEA = 1
ACT = 0 | SL2
DEA = 1
ACT = 0 | SL3
DEA = 1
ACT = 0 (Note 19) | SL3
DEA = 1
ACT = 1 | SL3
DEA = 0
ACT = 0 | SL0 | SL0 | SL0 | SL3
DEA = 1
ACT = 1 (Note 18) | +| End of last superframe with DEA = 0 (Note 10) | | / | / | / | / | / | / | / | / | / | LT11 | / | / | / | / | +| Expiry of timer M5 (15 seconds) (Note 1) | | / | / | / | LT10
FE7 | LT10
FE7 | LT10
FE7 | LT10
FE7 | / | / | / | / | / | / | / | +| Absence of signal < 40 ms (Note 1) | | / | – | / | / | / | – | – | – | – | – | ST.M7
LT12 | LT1
FE6 | – | – | +| Expiry of timer M7 (40 ms) (Note 1) | | / | / | / | / | / | / | / | / | / | / | / | / | LT1
FE6 | / | +| Loopback 2 request (FE8) Receiver ACT = 1 (SN3) (Notes 18 and 23) | | / | / | / | / | / | / | / | LT8A
FE4 | – | – | – | – | – | – | +| Return to normal request (Note 23) | | – | – | – | – | – | – | – | – | – | – | – | – | – | LT7
(Note 20) | + +NOTE – For symbols, abbreviations, and notes, see Table II.5. + +TABLE II.5/G.961 + +#### **Symbols, abbreviations and notes for Tables II.3 and II.4** + +#### Symbols and abbreviations + +| | | +|----------|-----------------------------------------------------------------| +| – | No change, no action | +| / | Impossible or prohibited situation under normal circumstances | +| FE1 | Activate access (Note 1) – PH-AR | +| FE2 | Access activation initiated (Note 1) – MPH-AWI | +| FE3 | Access digital section activated (Note 1) – MPH-DSAI | +| FE4 | Access activated or loopback operated (Note 1) – PH-MPH-AI | +| FE5 | Deactivate access (Note 1) – PH/MPH-DR | +| FE6 | Access deactivated (Note 1) – PH/MPH-DI | +| FE7 | LOS/LFA in DS or loss of power at NT (Note 1) – PH/MPH-EI | +| FE8 | Activate loopback 2 (Note 1) – MPH-L2AR | +| NTn | Go to state NTn | +| LTn | Go to state LTn | +| L2 | Loopback 2 | +| ST.Mn | Start timer Mn | +| STP.Mn | Stop timer Mn | +| SLn, SNn | Signals defined in Figures II.6 and II.7 (SL0, SN0 = no signal) | +| Tn | Events defined in Figures II.6 and II.7 | + +###### NOTES + +- 1 Primitives are the subject of continuing study and are significant only in combined LT/ET implementations. +- 2 These events are initiated at the T reference point (see Tables 6/I.430 and 4/I.430). +- 3 This condition represents an activation request event. +- 4 This condition indicates that the user data path (2B + D channels) in the TE-to-NT direction is transparent to user data. +- 5 This condition indicates that the user data path (2B + D channels) in the TE-to-NT direction is not transparent to user data. +- 6 This event takes priority over received ACT = ZERO for warm-start NTs. This event could be ignored for cold-start-only NTs. +- 7 S/T INFO signals are shown as transmit signals in Table II.3 which does not directly control these signals. They are included for information only. +- 8 The signals output in this state remain unchanged from signals output during the preceding state. (For example, ACT = ZERO if states NT6 or NT11 preceded, or ACT = ONE if states NT7 or NT8 preceded.) +- 9 This event will cause turn-off of the NT independent of whether the transmitter is cold-start-only or warm-start. +- 10 This event occurs after transmitting at least three superframes with DEA = ZERO. See II.10.1 5.2. +- 11 When in state NT4, absence of signal > 480 ms causes transition to state NT1. +- 12 When INFO 1 remains continuous after the NT fails to bring up the network side and returns to state NT1, the NT does not again go to state NT2 unless a new transition from INFO 0 to INFO 1 is received. See II.10.10 and Recommendation I.430. +- 13 The transceiver should return to the state from which it entered state NT9 unless the UOA or ACT bits have changed. +- 14 The text for this note has been removed. + +TABLE II.5/G.961 (end) + +#### **Symbols, abbreviations and notes for Tables II.3 and II.4** + +###### NOTES + +15 This note applies only for Table A.II.3, and the text is provided in Table A.II.4. + +16 When in state LT3 absence of signal > 480 ms causes transition to state LTI. + +17 The NT makes the transition from SN2 to SN3 transmitted toward the network upon confirmation of the loopback 2 request. In the same general time frame, the NT sends ACT = ONE toward the network, following the timing rules for transparency given in II.10.3.4. Subsequently, the NT sets loopback 2, upon confirmation of the transition of the signal from the network from SL2 to SL3. + +Whether the LT should reply to the ACT = ONE signal from the NT with ACT = ONE toward the NT, and whether the NT should wait for confirmation of ACT = ONE from the network before setting the loopback are for further study. + +During loopback 2, the B- and D-channels in SN3 contain the information from corresponding channels in SL3. M bits are not looped back. loopback 2 is a transparent loopback, meaning that the B- and D-channels in SL3 are also put into INFO 4 toward the TE. In state NT/A, transition to INFO 4 (from INFO 2) toward the TE is made at the same time as the transition to SN3 toward the network. However, when the TE is inactive (NT11A), INFO 2 is sent. It is not necessary to wake up the TE in this case, and indeed the purpose of the test may be to determine whether the NT is functioning properly even though communication with the TE is impossible (eg. when the TE has lost power or has become disconnected). Some existing implementations may not set ACT = ONE for loopback 2. + +18 The EOC request shall not be sent before T7 (when the LT has achieved IFW sync). Before T7 EOC echoes are not received at the LT. Once T7 is reached the loopback 2 request may be sent by the network, using the EOC protocol defined in II.8.3.3.2. Once the LT confirms the receipt of SN3 and ACT = ONE from the NT, it should make the transition to SL3 (see Figure II.7). At that same time, the test signal to be used in the B- and D-channels may be sent th SL3. See Note 17 for further discussion. + +19 The LT sends SL2 until transparency is achieved as described in II.10.3.4. + +20 For warm-start transceivers, the return-to-normal request is usually accompanied by a deactivation request (FE5), and when loopback 2 has been released, the LT transitions from LT8A to LT7 where, as shown in Table II.4, a number of additional transitions are available. For example, when the deactivation request has accompanied the return-to-normal request, the state quickly transitions to LT9 and eventually to LT1 or LT12 where an FE6 is sent to the ET after expiry of timer M7, and the access is deactivated. + +Cold-start-only transceivers normally remain active when loopback 2 is released, and transparency depends on readiness for layer 2 communication at both ends, and the consequent setting of ACT bits in both directions. For example, the LT may move quickly from LT8A to LT7 (as shown) and then to LT8 if both ends are ready. + +21 On receiving ACT = ZERO in SN3 while in state LT8 (active) or in a state LT8A (loopback 2 set) the LT returns to state LT7. The ET maintains either FE1 or FE8 depending of whether it came from LT8 or LT8A respectively. In state LT8. receipt of ACT = ZERO means loss of layer 2 communication with the TE. + +22 In state NT7, SN3 is sent only when transparency for layer 2 communication or for a loopback is achieved. Otherwise SN2 is sent. + +23 Aspects relating to loopback 2 are provisional. + +### **II.10.6 Activation times** + +The LT and the NT1 shall complete the start-up process, including synchronization and training of equalizers to the point of meeting performance criteria within the following lengths of time: transceivers shall synchronize within 300 ms on warm starts and within 15 s on cold starts. The 15 s cold-start time requirement is apportioned such that the NT1 is allowed 5 s and the LT is allowed 10 s. For warm starts the 300 ms start-up time requirement is apportioned equally between the NT1 and the LT, 150 ms each. See Figure II.6 for details. + +NOTE – The 300 ms requirement applies to laboratory tests only. No 300 ms timer is involved in actual in-service DLLs. See definitions in II.10 for warm and cold starts. + +As indicated in Figure II.6, the start time requirements cover the time span from wake-up tone to T7, and do not include time for activation of customer terminal equipment. All activation times apply only to the DLL, and do not apply to the entire customer access link where carrier systems may be involved. + +NOTE – The value in Recommendation G.960 is 15 s. This is a 95% value. + +## II.11 Jitter + +Jitter tolerances are intended to ensure that the limits of Recommendation I.430 (Figure 9/I.430) are supported by the jitter limits of the transmission system on local lines. The jitter limits given below must be satisfied regardless of the length of the local line and the inclusion of one regenerator, provided that they are covered by the transmission media characteristics (see 3). The limits shall be met regardless of the bit patterns in the B-, D- and $C_L$ -channels. + +Jitter is specified in terms of unit intervals (UI) of the nominal 80 kbaud signal (12.5 $\mu\text{s}$ ). + +### II.11.1 Input signal jitter tolerance + +The NT1 shall meet the performance objectives with wander/jitter at the maximum magnitude indicated in Figure II.10, for single jitter frequencies in the range of 0.1 Hz to 20 kHz, on the LT output signal with the received signal baud rate in the range of 80 kbauds $\pm 5$ ppm. The NT1 shall also meet the performance objectives with wander per day on the LT output of up to 1.44 UI peak-to-peak where the maximum rate of change of phase is 0.06 UI/hour. + +![Figure II.10/G.961: Permissible sinusoidal NT1 input signal jitter. The graph shows peak-to-peak jitter (UI) on the y-axis (logarithmic scale from 0.001 to 1.0) versus jitter frequency (Hz) on the x-axis (logarithmic scale from 0.1 to 20,000). The jitter limit is 0.30 UI from 0.1 Hz to 0.5 Hz, then decreases with a 20 dB/decade slope to 0.008 UI at 19 Hz, and remains constant at 0.008 UI up to 20,000 Hz.](e2b57ed20df1cf724e0188b64870fe05_img.jpg) + +| Jitter frequency (Hz) | Peak-to-peak jitter (UI) | +|-----------------------|--------------------------| +| 0.1 | 0.30 | +| 0.5 | 0.30 | +| 19 | 0.008 | +| 20,000 | 0.008 | + +Figure II.10/G.961: Permissible sinusoidal NT1 input signal jitter. The graph shows peak-to-peak jitter (UI) on the y-axis (logarithmic scale from 0.001 to 1.0) versus jitter frequency (Hz) on the x-axis (logarithmic scale from 0.1 to 20,000). The jitter limit is 0.30 UI from 0.1 Hz to 0.5 Hz, then decreases with a 20 dB/decade slope to 0.008 UI at 19 Hz, and remains constant at 0.008 UI up to 20,000 Hz. + +NOTE – Unit interval (UI) = 12.5 $\mu\text{s}$ . + +FIGURE II.10/G.961 +Permissible sinusoidal NT1 input signal jitter + +### II.11.2 NT1 output jitter limitations + +With the wander/jitter as specified in II.11.1, superimposed on the NT1 input signal, the jitter on the transmitted signal of the NT1 towards the LT shall conform to the following, with the received signal baud rate in the range of 80 kbauds $\pm 5$ ppm, as described in II.2.1.2. + +- 1) The jitter shall be equal to or less than 0.04 UI peak-to-peak and less than 0.01 UI r.m.s. when measured with a high-pass filter having a 6 dB/octave roll-off below 80 Hz. + +- 2) The jitter in the phase of the output signal (the signal transmitted towards the LT) relative to the phase of the input signal (from the LT) shall not exceed 0.05 UI peak-to-peak and 0.015 UI r.m.s. when measured with a band-pass filter having a 6 dB per octave roll-off above 40 Hz and below 1.0 Hz. (Note that the 1.0 Hz cut-off assures that the average difference in the phase of the input and output signals is subtracted.) This requirement applies with superimposed jitter in the phase of the input signal as specified in II.11.1 for single frequencies up to 19 Hz. +- 3) The maximum (peak) departure of the phase of the output signal from its nominal difference (long-term average) from the phase of the input signal (from the LT) shall not exceed 0.1 UI. This requirement applies during normal operation including following a “warm start”. (Note that this means that, if deactivated and subsequently activated in conformance with the “warm start” requirements, the long-term average difference in phase of the output signal from the phase of the input signal shall be essentially unchanged.) + +### II.11.3 LT input signal jitter tolerance + +The LT shall operate satisfactorily with input signal jitter equal to the worst case NT1 output signal jitter allowed by the limits set in II.11.2. + +### II.11.4 LT output jitter and synchronization + +The output signals from the LT shall not exceed the NT1 input signal jitter tolerance limits stated in II.11.2. This requirement shall be met while maintaining data synchronization with the network. + +### II.11.5 Test conditions for jitter measurements + +Due to bidirectional transmission on the two-wire line and due to severe intersymbol interference, no well-defined signal transitions are available at the NT1 two-wire point. + +Two possible solutions are proposed: + +- 1) a test point in the NT1 is provided to measure jitter with an undisturbed signal; +- 2) a standard LT transceiver including an artificial transmission line is defined as a test instrument. + +## II.12 Transmitter output characteristics of NT1 and LT + +The following specifications apply with a load impedance of 135 ohms resistive over a frequency band of 0 Hz to 160 kHz. + +### II.12.1 Pulse amplitude + +The nominal peak of the largest pulse shall be 2.5 volts (see Figure II.11). + +### II.12.2 Pulse shape + +The transmitted pulse shall have the shape specified in Figure II.11. The pulse mask for the four quaternary symbols shall be obtained by multiplying the normalized pulse mask shown in Figure II.11 by 2.5 V, $5/6$ V, $-5/6$ V or $-2.5$ V. When the signal consists of a framed sequence of symbols with a synchronization word and equiprobable symbols in all other positions, the nominal average power is 13.5 dBm. + +### II.12.3 Signal power + +The average power of a signal consisting of a framed sequence of symbols with a frame word and equiprobable symbols at all other positions, should be between 13.0 dBm and 14.0 dBm over the frequency band from 0 Hz to 80 kHz. + +![Figure II.11/G.961: Normalized output pulse from NT1 or LT. The figure includes a pulse waveform diagram and a table of voltage values for different bit levels.](7e5f8a1e5575ef87a54c9c091eaaa66d_img.jpg) + +The figure shows a normalized output pulse waveform. The top part shows a zoomed-in view of the rising and falling edges of a pulse, with parameters A, B, C, and D defined. The bottom part shows the full pulse shape over time, with parameters A, F, G, H, and E defined. The pulse duration is T = 12.5 μs. + +| | | +3 | +1 | -1 | -3 | +|---|-------|----------|------------|------------|----------| +| A | 0.01 | 0.025 V | 0.0833 V | -0.0833 V | -0.025 V | +| B | 1.05 | 2.625 V | 0.8750 V | -0.8750 V | -2.625 V | +| C | 1.00 | 2.5 V | 5/6 V | -5/6 V | -2.5 V | +| D | 0.95 | 2.375 V | 0.79127 V | -0.79127 V | -2.375 V | +| E | 0.03 | 0.075 V | 0.025 V | -0.025 V | -0.075 V | +| F | -0.01 | -0.025 V | -0.00833 V | 0.00833 V | 0.025 V | +| G | -0.12 | -0.3 V | -0.1 V | 0.1 V | 0.3 V | +| H | -0.05 | -0.125 V | -0.04167 V | 0.04167 V | 0.125 V | + +Figure II.11/G.961: Normalized output pulse from NT1 or LT. The figure includes a pulse waveform diagram and a table of voltage values for different bit levels. + +NOTE – Compliance of transmitted pulses within boundaries of the pulse mask is not sufficient to assure compliance with the power spectral density requirement and the absolute power requirement. Compliance with the requirements in II.12.3 and II.12.4 is also required. + +FIGURE II.11/G.961 +Normalized output pulse from NT1 or LT + +### II.12.4 Power spectral density + +The upper bound of the power spectral density of the transmitted signal shall be as shown in Figure II.12. Measurements to verify compliance with this requirement are to use a noise power bandwidth of 1.0 kHz. + +### II.12.5 Transmitter linearity + +#### II.12.5.1 Requirements + +This is a measure of the deviations from ideal pulse heights and the individual pulse non-linearity. The transmitted and received signals shall have sufficient linearity so that the residual r.m.s. non-linearity is at least 36 dB below the r.m.s. signal at the interface. + +#### II.12.5.2 Linearity test method + +With the transceiver (LT or NT1) terminated in a 135-ohm resistance through a zero-length loop, and driven by an arbitrary binary sequence, the voltage appearing across the resistance is filtered (anti-alias), sampled and converted to digital form ( $V_{out}$ ) with a precision of no less than 12 bits (see Figure II.13). These samples are compared with the output of an adjustable linear filter, the input of which is the scrambled, framed, and linearly-encoded transmitter input. The signals at the subtractor may both be in digital form, or they may both be in analogue form. + +![Figure II.12/G.961: Upper bound of power spectral density of signal from NT1 and LT. The graph shows Power spectral density (dBm/Hz) on the y-axis (from -90 to -20) versus Frequency (kHz) on the x-axis (logarithmic scale from 1 to 1000). The curve is flat at -30 dBm/Hz from 1 kHz to 50 kHz, then decreases with a slope of -50 dB/decade until it reaches -80 dBm/Hz at 500 kHz, where it remains flat until 1000 kHz. A dashed horizontal line is shown at -80 dBm/Hz.](c2e29ea8ce248c31df2f0aba049d018c_img.jpg) + +| Frequency (kHz) | Power Spectral Density (dBm/Hz) | +|-----------------|---------------------------------| +| 1 | -30 | +| 50 | -30 | +| 500 | -80 | +| 1000 | -80 | + +Figure II.12/G.961: Upper bound of power spectral density of signal from NT1 and LT. The graph shows Power spectral density (dBm/Hz) on the y-axis (from -90 to -20) versus Frequency (kHz) on the x-axis (logarithmic scale from 1 to 1000). The curve is flat at -30 dBm/Hz from 1 kHz to 50 kHz, then decreases with a slope of -50 dB/decade until it reaches -80 dBm/Hz at 500 kHz, where it remains flat until 1000 kHz. A dashed horizontal line is shown at -80 dBm/Hz. + +FIGURE II.12/G.961 +**Upper bound of power spectral density of signal from NT1 and LT** + +The linear digital filter input (“Quaternary Input Data” in Figure II.13) can be considered a linearity standard. It may be produced from the transmitter output by an errorless receiver (with no descrambler), or from the scrambled transmitter input data if it is available. If the samples input to the adjustable filter are available in digital form, no additional A/D converter is required. Whether analogue or digital, these samples are required to be in the ratio 3:1:-1:-3, to an accuracy of at least 12 bits. + +The sampling rate of the samplers and filters may be higher than the symbol rate, and generally will be several times the symbol rate for good accuracy. Alternatively, the sample rate may be at the symbol rate, but the r.m.s. values are obtained by averaging over all sample phases relative to the transmitter signal. + +Because the anti-alias filter, sampler, and A/D converter operating on the transmitter output may introduce a loss or gain, proper calibration requires determining $\langle V_{out}^2 \rangle$ at the filter output, as shown in Figure II.13, rather than the mean-squared value of the transmitter output itself. + +## II.13 Transmitter/receiver termination + +### II.13.1 Impedance + +The nominal driving point impedance at the interface toward the NT1 shall be 135 ohms. + +### II.13.2 Return loss + +The return loss with respect to 135 ohms, over a frequency band from 1 kHz to 200 kHz, shall be as shown in Figure II.14. + +![Block diagram of transmitter linearity measurement. An arbitrary binary sequence is input to a 2B1Q transmitter. The output is connected to a zero-length loop terminated with a 135 ohm resistor at the interface. The signal from the loop is processed by an anti-alias filter, sampler, and A/D converter to produce V_out. Simultaneously, quaternary input data is processed by an adaptive linear filter. The outputs of the adaptive filter and the A/D converter are subtracted. The squared difference is averaged to get , and the squared output is averaged to get . The ratio of these two averages is calculated to determine the linearity, which should be less than -36 dB. A note indicates the filter is adjusted to minimize the mean squared difference. Reference T1814400-92/d35 is shown.](af6c3f383ddc0c142cdd7e186cc78199_img.jpg) + +Block diagram of transmitter linearity measurement. An arbitrary binary sequence is input to a 2B1Q transmitter. The output is connected to a zero-length loop terminated with a 135 ohm resistor at the interface. The signal from the loop is processed by an anti-alias filter, sampler, and A/D converter to produce V\_out. Simultaneously, quaternary input data is processed by an adaptive linear filter. The outputs of the adaptive filter and the A/D converter are subtracted. The squared difference is averaged to get , and the squared output is averaged to get . The ratio of these two averages is calculated to determine the linearity, which should be less than -36 dB. A note indicates the filter is adjusted to minimize the mean squared difference. Reference T1814400-92/d35 is shown. + +FIGURE II.13/G.961 +Measurement of transmitter linearity + +### II.13.3 Longitudinal conversion loss + +#### II.13.3.1 Longitudinal balance + +The longitudinal balance (of impedance to ground) is given by: + +$$LBal = 20 \log \left( \frac{e_1}{e_m} \right) \text{ dB}$$ + +where + +$e_1$ = the applied longitudinal voltage (referenced to the building or safety ground of the NT1); + +$e_m$ = the resultant metallic voltage appearing across a 135-ohm termination. + +The balance shall be $> 20$ dB at frequencies up to 5 Hz. The minimum requirement increases above 5 Hz at 20 dB per decade to 55 dB at 281.2 Hz. The balance shall be $> 55$ dB between 281.2 Hz and 40 000 Hz. Above 40 000 Hz, the minimum requirement decreases at 20 dB per decade. See Figure II.15. + +Figure II.16 defines a measurement method for longitudinal balance. For direct use of this test configuration, measurement should be performed with the NT1 powered up but inactive (no transmitted signal). + +![Graph of Return loss (dB) vs Frequency (kHz) for FIGURE II.14/G.961. The y-axis ranges from -10 to 30 dB. The x-axis is logarithmic from 1 to 1000 kHz. The curve starts at 0 dB at 1 kHz, rises to 20 dB at 10 kHz, stays at 20 dB until 25 kHz, then falls to 0 dB at 250 kHz, and continues to decrease.](8605b43090d582ea5046e1804178a7d8_img.jpg) + +| Frequency (kHz) | Return loss (dB) | +|-----------------|------------------| +| 1 | 0 | +| 10 | 20 | +| 25 | 20 | +| 250 | 0 | +| 1000 | -10 | + +T1814410-92/d36 + +Graph of Return loss (dB) vs Frequency (kHz) for FIGURE II.14/G.961. The y-axis ranges from -10 to 30 dB. The x-axis is logarithmic from 1 to 1000 kHz. The curve starts at 0 dB at 1 kHz, rises to 20 dB at 10 kHz, stays at 20 dB until 25 kHz, then falls to 0 dB at 250 kHz, and continues to decrease. + +FIGURE II.14/G.961 +Minimum return loss + +![Graph of Longitudinal balance (dB) vs Frequency (kHz) for FIGURE II.15/G.961. The y-axis ranges from 25 to 45 dB. The x-axis is logarithmic with markers at 0.5, 5, 60, and 190 kHz. The curve starts at 25 dB at 0.5 kHz, rises to 45 dB at 5 kHz, stays at 45 dB until 60 kHz, then falls to 35 dB at 190 kHz.](14294c70b5a0effb6bdaf09c46bbdc9f_img.jpg) + +| Frequency (kHz) | Longitudinal balance (dB) | +|-----------------|---------------------------| +| 0.5 | 25 | +| 5 | 45 | +| 60 | 45 | +| 190 | 35 | + +T1814420-92/d37 + +Graph of Longitudinal balance (dB) vs Frequency (kHz) for FIGURE II.15/G.961. The y-axis ranges from 25 to 45 dB. The x-axis is logarithmic with markers at 0.5, 5, 60, and 190 kHz. The curve starts at 25 dB at 0.5 kHz, rises to 45 dB at 5 kHz, stays at 45 dB until 60 kHz, then falls to 35 dB at 190 kHz. + +FIGURE II.15/G.961 +Minimum longitudinal balance requirement + +![Circuit diagram for measuring longitudinal balance of an NT1. The NT1 is connected to a measuring set (well balanced) which is connected to a longitudinal signal generator. The measuring set includes two 67.5 Ω resistors and a voltmeter measuring the voltage e_m. The signal generator is connected to the measuring set and measures the voltage e_l.](99698c448635861b7dc8d352f87a1b2b_img.jpg) + +The diagram shows an NT1 device connected to a 'Measuring set (well balanced)'. The measuring set contains two resistors, each labeled $67.5^{\text{a)}} \Omega$ , connected in a bridge configuration. A voltmeter measures the voltage $e_m$ across the bridge. A 'Longitudinal signal generator' is connected to the measuring set, and its output voltage is labeled $e_l$ . The diagram is labeled 'T1814430-92/d38'. + +Circuit diagram for measuring longitudinal balance of an NT1. The NT1 is connected to a measuring set (well balanced) which is connected to a longitudinal signal generator. The measuring set includes two 67.5 Ω resistors and a voltmeter measuring the voltage e\_m. The signal generator is connected to the measuring set and measures the voltage e\_l. + +a) These resistors should be matched to better than 0.03% tolerance. + +FIGURE II.16/G.961 +**Measurement method for longitudinal balance** + +# **Annex A** (to Appendix II) + +## **Extension functions of the system using 2B1Q line code** + +### **A.II.1 Introduction** + +The functions described in this annex are optional. + +### **A.II.2 NT1 power status bits** + +The power status bits shall be the $M_4$ bits in the second and third basic frames of multiframe transmitted by the NT1 (Figure II.3). The use of this function is optional. When the $PS_1$ and $PS_2$ bits are used to convey the status of primary or secondary power sources, they shall be used as defined in Table A.II.1. See II.8.3.2.4. If these bits are not used, they shall be set to ONE in SN3. + +### **A.II.3 NT1 test mode indicator (NTM) bit** + +The NT1 test mode indicator bit shall be the $M_4$ bit in the fourth basic frame of multiframe transmitted by the NT1 to the network (Figure II.3). The use of this function is optional. The NT1 is considered to be in a test mode when the D-channel or either one of the B-channels are involved in a customer locally-initiated maintenance action. While in test mode, the NT1 may be unavailable for service or the NT1 may be unable to perform actions requested by EAC messages. If the function is used, the bit shall be a binary ONE to indicate normal operation and a ZERO to indicate test mode. If the function is not used, the bit shall be set to ONE in SN3. See II.8.3.2.5. + +TABLE A.II.1/G.961 + +#### **Power status bit assignments and definitions** + +| NT1 status | PS 1 & PS 2 binary values | Definition | +|---------------------|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| All power normal | 11 | Primary and back-up battery (if provided) power supplies are both normal. Normal power at T reference point, if provided. | +| Secondary power out | 10 | Primary power is normal, but the back-up battery (if provided) is marginal, unavailable, or has failed. Normal power at T reference point, if provided. | +| Primary power out | 01 | Primary power is marginal or has failed. Back-up battery (if provided) is normal. Voltage at T reference point (if provided) is less than 34 V or reversed. | +| Dying gasp | 00 | Both primary power and back-up battery (if provided) are marginal or have failed. Voltage at T reference point (if provided) is less than 34 V or reversed. The NT1 may shortly cease normal operation. | + +### **A.II.4 Cold-start-only (CSO) bit** + +The CSO bit is the M4 bit in the fifth frame of the multiframe transmitted by an NT1. The use of this function is optional. It may be used to indicate the start-up capabilities of the NT1 transceiver. If the NT1 has a cold-start-only transceiver, as defined in II.10 5), this bit is set to ONE. Otherwise, this bit shall be set to ZERO in SN3. See II.8.3.2.6. + +### **A.II.5 DLL-only-activation (UOA) bit** + +The UOA bit shall be the M4 bit in the seventh basic frame of the multiframes transmitted by an LT. The use of this function is optional. It shall be used to request the NT1 to activate or deactivate the S/T interface (if present). If the S/T interface is to be activated, this bit may be set to binary ONE. Otherwise, this bit may be set to binary ZERO. If the function is not used, the bit shall be set to ONE in SL2 and SL3. See II.8.3.2.7. + +### **A.II.6 S/T-interface-activity-indicator (SAI) bit** + +The SAI bit shall be the M4 bit in the seventh basic frame of the multiframes transmitted by an NT1. The use of this function is optional. It may be used to indicate to the network when there is activity at the S/T reference point. If there is activity (INFO 1 or INFO 3) at the S/T reference point, this bit may be set to ONE. Otherwise it may be set to ZERO. If this function is not used, the bit shall be set to ONE in SN3. See II.8.3.2.8. + +### **A.II.7 Alarm indicator bit (AIB)** + +The AIB bit shall be the M4 bit in the eighth basic frame of the multiframes transmitted by the network toward the NT1. The use of this function is optional. When the transmission path for D-, B1-, and B2-channels has been established all the way to the local exchange, a binary ONE may be forwarded to the NT1. Failure or interruption of an intermediate transmission system which transports the D-, B1-, and B2-channels shall result in forwarding ZERO to the NT1. Such failures may include loss of signal, loss of frame synchronization/carrier link or basic access DLL, and transmission terminal failure. Intermediate transmission interruptions may include loopbacks at intermediate points or absence of provisioning of an intermediate transmission system. If this function is not used, the bit shall be set to ONE in SN3. See II.8.3.2.4. + +### **A.II.8 Longitudinal output voltage** + +The longitudinal component of the NT1 output signal has an r.m.s. voltage, in any 4 kHz bandwidth averaged in any one second period, less than −50 dBv over the frequency range 100 Hz to 170 kHz, and less than −80 dBv the range from 170 kHz to 270 kHz. Compliance with this limitation is required with a longitudinal termination having an impedance equal to or greater than a 100-ohm resistor in series with a 0.15 μF capacitor. + +Figure A.II.1 defines a measurement method for longitudinal output voltage. For direct use of this test configuration, the NT1 should be able to generate a signal in the absence of a signal from the LT. + +![Circuit diagram for measuring longitudinal output voltage of an NT1. The NT1 block has two output lines. Each line goes through a 67.5 Ω resistor (labeled 67.5^a). These two paths then join and connect to a series combination of a 0.15 μF capacitor and a 100 Ω resistor. A spectrum analyzer is connected in parallel with the 100 Ω resistor. The NT1 and the bottom of the 100 Ω resistor/spectrum analyzer circuit are connected to ground symbols. The diagram is labeled T1814440-92/d39.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +T1814440-92/d39 + +Circuit diagram for measuring longitudinal output voltage of an NT1. The NT1 block has two output lines. Each line goes through a 67.5 Ω resistor (labeled 67.5^a). These two paths then join and connect to a series combination of a 0.15 μF capacitor and a 100 Ω resistor. A spectrum analyzer is connected in parallel with the 100 Ω resistor. The NT1 and the bottom of the 100 Ω resistor/spectrum analyzer circuit are connected to ground symbols. The diagram is labeled T1814440-92/d39. + +a) These resistors should be better than 0.1% tolerance. + +FIGURE A.II.1/G.961 +**Measurement method for longitudinal output voltage** + +The ground reference for these measurements is the building ground. + +### **A.II.9 NT1 maintenance modes** + +The NT1 Quiet Mode (QM) functionality within an NT1 (or customer equipment containing the NT1 functionality) will assure that an NT1 will not attempt a start-up or will not initiate transmission during metallic loop tests conducted by the network. The Insertion Loss Measurement Test (ILMT) will cause a known test signal to be generated by an NT1. This test will be used in network measurements of DLL transmission characteristics and may provide the ability to determine, from a single-ended test of the metallic loop, if the loop can support DLL transmission. + +Figure A.II.2 NT1 loop testing states, illustrates the various NT1 states associated with both the NT1 Quiet Mode and the Insertion Loss Measurement Test. + +![State transition diagram for NT1 loop testing states. The diagram shows three states: 'Enter/exit' (top), 'Quiet mode' (bottom left), and 'ILMT' (bottom right). Transitions are labeled with numbers 6, 8, and 10. 'Enter/exit' to 'Quiet mode' is labeled 6. 'Quiet mode' to 'Enter/exit' is labeled 10. 'Enter/exit' to 'ILMT' is labeled 8. 'ILMT' to 'Enter/exit' is labeled 10. 'Quiet mode' to 'ILMT' is labeled 6. 'ILMT' to 'Quiet mode' is labeled 8. There are self-loops on 'Quiet mode' and 'ILMT' labeled 6 and 8 respectively. External transitions to 'Enter/exit' are labeled 'TO'. A legend defines the signals: ILMT (Insertion Loss Measurement Test, Scrambled, framed 2B1Q), Insertion Loss Signal (6, 8, 10), Trigger Signal (Number of pulses within trigger signal, dc or low frequency ac pulses), TO (Timeout = 75 seconds). The diagram is labeled T1814450-92/d40.](29043c6ca27a7cfbc757a5d2eb029d33_img.jpg) + +ILMT Insertion Loss Measurement Test + Insertion Loss Signal Scrambled, framed 2B1Q + 6, 8, 10 Number of pulses within trigger signal + Trigger Signal dc or low frequency ac pulses + TO Timeout = 75 seconds + +T1814450-92/d40 + +State transition diagram for NT1 loop testing states. The diagram shows three states: 'Enter/exit' (top), 'Quiet mode' (bottom left), and 'ILMT' (bottom right). Transitions are labeled with numbers 6, 8, and 10. 'Enter/exit' to 'Quiet mode' is labeled 6. 'Quiet mode' to 'Enter/exit' is labeled 10. 'Enter/exit' to 'ILMT' is labeled 8. 'ILMT' to 'Enter/exit' is labeled 10. 'Quiet mode' to 'ILMT' is labeled 6. 'ILMT' to 'Quiet mode' is labeled 8. There are self-loops on 'Quiet mode' and 'ILMT' labeled 6 and 8 respectively. External transitions to 'Enter/exit' are labeled 'TO'. A legend defines the signals: ILMT (Insertion Loss Measurement Test, Scrambled, framed 2B1Q), Insertion Loss Signal (6, 8, 10), Trigger Signal (Number of pulses within trigger signal, dc or low frequency ac pulses), TO (Timeout = 75 seconds). The diagram is labeled T1814450-92/d40. + +NOTE – As a result of a power off/on cycle, the NT1 exits the maintenance mode and attempts start-up as described in II.10 10). All knowledge of previous maintenance modes is lost. + +FIGURE A.II.2/G.961 +**NT1 loop testing states** + +#### A.II.9.1 NT1 Quiet Mode + +The NT1 Quiet Mode implementation shall be as follows: + +- 1) The NT1 shall unconditionally enter the Quiet Mode upon receipt of six consecutive pulses in the trigger signal. Once triggered, the function shall latch until either timeout or turnoff. +- 2) While in the Quiet Mode, the NT1 shall cease all transmission and not attempt start-up. +- 3) The NT1 Quiet Mode duration shall be 75 seconds. If no trigger signal is received to change the NT1 state during the 75-second QM duration, the NT1 shall exit the maintenance mode. Upon exiting the maintenance mode, the NT1 and the network shall be responsible for operation described in II.10.3.1 and II.10.3.2. +- 4) A receipt of six consecutive pulses in the trigger signal during Quiet Mode shall cause the NT1 to return to the start of the Quiet Mode state. (The Quiet Mode would then continue for another 75 seconds until either timeout or receipt of a new trigger signal that would alter the NT1 state.) + +- 5) A receipt of eight consecutive pulses in the trigger signal during Quiet Mode shall cause the NT1 to enter the Insertion Loss Measurement Test state. +- 6) A receipt of ten consecutive pulses in the trigger signal during Quiet Mode shall cause the NT1 to exit the maintenance mode [see 3) above]. +- 7) If the NT1 receives one through five, seven, nine or greater than ten consecutive pulses in the trigger signal, then the state change command is not valid and no action is taken by the NT1. + +#### **A.II.9.2 Insertion Loss Measurement Test** + +The Insertion Loss Measurement Test implementation shall be as follows: + +- 1) The receipt by the NT1 of eight consecutive pulses in the trigger signal (see A.II.9.3, A.II.9.4 and A.II.9.5) shall unconditionally initiate the Insertion Loss Measurement Test. Once triggered, the function shall latch until either timeout or turnoff. The NT1 shall not attempt start-up during the Insertion Loss Measurement Test. +- 2) While in the Insertion Loss Measurement Test state, the NT1 shall generate a scrambled, framed, 2B1Q signal. SN1 and SN2 (see II.9) are examples of scrambled, framed, 2B1Q signals suitable for the Insertion Loss Measurement Test signal. +- 3) The Insertion Loss Measurement Test duration shall be 75 seconds. Upon exiting the maintenance mode the NT1 and the network shall be responsible for operation as described in II.10.3.1 and II.10.3.2. +- 4) Receipt of eight consecutive pulses in the trigger signal during the Insertion Loss Measurement Test duration shall cause the NT1 to return to the start of the Insertion Loss Measurement Test. (The ILMT would then continue for 75 seconds until timeout or receipt of a new trigger signal to alter the NT1 state.) +- 5) A receipt of six consecutive pulses in the trigger signal during Insertion Loss Measurement Test shall cause the NT1 to enter the Quiet Mode state. +- 6) A receipt of ten consecutive pulses in the trigger signal during Insertion Loss Measurement Test shall cause the NT1 to exit the maintenance mode [see 3) above]. +- 7) If the NT1 receives one through five, seven, nine or greater than ten consecutive pulses in the trigger signal, then the state change command is not valid and no action is taken by the NT1. + +#### **A.II.9.3 NT1 Quiet Mode and Insertion Loss Measurement Test trigger signal** + +The NT1 shall be capable of detecting the following two types of signals: The NT1 shall respond to either + +- 1) dc signalling that begins with a steady current flow (start interval) followed by six, eight or ten pulses sent as breaks in the current and ends with steady dc current flow (stop interval); or +- 2) ac signalling that begins with no current flow (start interval, less than 200 $\mu$ A dc) followed by six, eight or ten half cycles or a 2 to 3 Hz sine wave, and ends with no current flow (stop interval). When receiving the ac signalling, the NT1 shall count each half cycle of the same wave as one pulse. + +A valid test trigger signal shall consist of a valid start interval followed by either six, eight or ten consecutive pulses followed by a valid stop interval. Unless an entire trigger sequence consisting of a start interval, pulses and stop interval is received, the NT1 shall take no action. + +A stop interval may be followed by a start interval without any intervening breaks. Signals on the loop before the start interval or after the stop interval shall not affect the NT1 trigger detection function. + +The start and stop intervals shall be $\geq 500$ ms. The NT1 shall be capable of detecting and validating the trigger signal and entering into the desired state required by the number of pulses transmitted. + +A request for the same or a new state shall occur no sooner than one second after the beginning of the preceding stop interval. On receipt of a valid signal, the NT1 shall transit from one state to the requested state within 500 ms. + +The pulse detector in the NT1 shall be implemented so that there is no aliasing for pulse rates up to 64 pulses per second. + +#### **A.II.9.4 dc signalling format** + +The dc signal shall begin with a steady current flow with pulses sent as breaks in the current. These pulses shall: + +- 1) be applied to the NT1 by test equipment in the network at a pulse speed of 4 to 8 pps; +- 2) have a 40-60% break; +- 3) have source voltage of 43.5 to 56 volts; and +- 4) have source resistance of 200 to 4000 ohms (includes test system, test trunk, loop, and margin resistance). + +#### **A.II.9.5 Low frequency ac signalling format** + +The ac signal shall consist of six, eight or ten half cycles of 2 to 3 Hz sine wave. Each half cycle of the sine wave is equivalent to one pulse described in subclause I.9.4. This sine wave shall: + +- 1) be applied to the NT1 by test equipment in the network at a frequency between 2 and 3 Hz; +- 2) have peak voltage between 60 and 62 volts; and +- 3) have a source resistance between 900 and 4500 ohms (ac source, test system, test trunk, loop, and margin resistance). + +**A.II.9.6** Tables A.II.2 and A.II.3 give examples of finite state matrices associated with activation/deactivation. Figures A.II.3 to A.II.7 give additional information on the activation/deactivation process and the turn-on process. + +Table A.II.4 contains symbols, abbreviations and notes to Tables A.II.2 and A.II.3. + +TABLE A.II.2/G.961 + +##### Activation/deactivation: NT (“H”) finite state matrix (DLL-only turn-on option) + +| Event | State name | Power off | Full reset | Alerting | EC training (optional) | EC converged | SW sync | ISW sync | ISW sync CALL | Pending Active | Active | UOA active | S/T deactivation | UOA and TE CALL | Pending deactivation | Tear down | TE inactive | Receive reset | +|--------------------------------------------------------------------|----------------------------|--------------|------------------------|------------|------------------------|--------------|----------|---------------------------------------|----------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|----------------------|---------------|-------------------------------------|------------------------| +| | State code (Fig. 17 event) | NT0 | NT1 (T0) | NT2 | NT3 (T1) | NT4 (T2) | NT5 (T3) | NT6(a) (T6) | NT6 (T6) | NT7 | NT8 | NT8(a) | NT8(b) | NT8(c) | NT9 | NT10 | NT11 | NT12 | +| | Signal→LT | SN0 | SN0 | TN | SN1 | SN0 | SN2 | SN3
ACT = 0
SAI=1or 0
INFO 0 | SN3
ACT = 0
SAI=1 or 0
INFO 2 | SN3
ACT = 1
SAI = 1
INFO 2 | SN3
ACT = 1
SAI = 1
INFO 4 | SN3
ACT = 0
SAI = 0
INFO 0 | SN3
ACT = 0
SAI = 0
INFO 0 | SN3
ACT = 0
SAI = 1
INFO 0 | SN3 (Note 8) | SN0
INFO 0 | SN3
ACT = 0
SAI = 0
INFO 2 | SN0
INFO 0 | +| ↓ Signal→TE (Note 7) | | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 2 | INFO 2 | INFO 4 | INFO 0 | INFO 0 | INFO 0 | | INFO 0 | INFO 2 | INFO 0 | +| Power on | | ST.M4
NT2 | – | – | – | – | – | – | – | – | – | – | – | – | – | – | – | – | +| Loss of power (Note 1) | | – | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | NT0 | +| Received new S/T INFO 1 signal (Notes 2 and 3) | | / | ST.M4
NT2 (Note 12) | – | – | – | – | – | – | / | / | NT8(c) | NT8(c) | – | – | – | / | – | +| Received INFO 3 signal (UOA = 1, ACT = 0, DEA = 1) (Notes 2 and 4) | | / | / | / | / | / | / | / | NT7 | – | – | / | – | / | – | – | NT7 | – | +| Received INFO 0 or S/T loss of sync (Notes 2 and 5) | | / | – | – | – | – | – | – | – | NT11 | NT11 | / | NT8(a) | / | – | – | – | – | +| End of tone TN (9 ms) | | / | / | NT8 or NT1 | / | / | / | / | / | / | / | / | / | / | / | / | / | / | +| Received tone TL | | / | ST.M4
NT2 | – | / | / | / | / | / | / | / | / | / | / | / | / | / | ST.M4
STP.M6
NT2 | + +TABLE A.II.2/G.961 (cont.) + +##### Activation/deactivation: NT (“H”) finite state matrix (DLL-only turn-on option) + +| Event
↓ | State name | Power off | Full reset | Alerting | EC training (optional) | EC converged | SW sync | ISW sync | ISW sync CALL | Pending Active | Active | UOA active | S/T deactivation | UOA and TE CALL | Pending deactivation | Tear down | TE inactive | Receive reset | +|------------------------------------------------------|--------------------------------------|-----------|------------|----------|------------------------|--------------|---------------|-------------------------------|-------------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|--------------------------|-----------|----------------------------|---------------| +| | Code de l'état (événement Figure 17) | NT0 | NT1 (T0) | NT2 | NT3 (T1) | NT4 (T2) | NT5 (T3) | NT6(a) (T6) | NT6 (T6) | NT7 | NT8 | NT8(a) | NT8(b) | NT8(c) | NT9 | NT10 | NT11 | NT12 | +| | Signal→LT | SN0 | SN0 | TN | SN1 | SN0 | SN2 | SN3 ACT = 0 SAI=1 or 0 INFO 0 | SN3 ACT = 0 SAI=1 or 0 INFO 2 | SN3 ACT = 1 SAI = 1 INFO 2 | SN3 ACT = 1 SAI = 1 INFO 4 | SN3 ACT = 0 SAI = 0 INFO 0 | SN3 ACT = 0 SAI = 0 INFO 0 | SN3 ACT = 0 SAI = 1 INFO 0 | SN3 (Note 8) | SN0 | SN3 ACT = 0 SAI = 0 INFO 2 | SN0 | +| | Signal→TE (Note 7) | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 2 | INFO 2 | INFO 4 | INFO 0 | INFO 0 | INFO 0 | | INFO 0 | INFO 2 | INFO 0 | +| Echo converged | | / | – | – | NT4 | – | – | – | – | – | – | – | – | – | – | – | – | – | +| SW and detect SL2 | | / | / | / | / | NT6 | – | – | – | – | – | – | – | – | – | – | – | / | +| ISW sync (SL2) | | / | / | / | / | / | STP.M4 NT6(a) | – | – | – | – | – | – | – | – | – | – | / | +| Received (SL2 or SL3) DEA = 0 (Note 6) | | / | / | / | / | / | / | NT9 | NT9 | NT9 | NT9 | NT9 | NT9 | NT9 | – | – | NT9 | / | +| Received (SL2 or SL3) UOA = 0 and DEA = 1 | | / | / | / | / | / | / | NT8(a) or NT8(c) | NT8(a) or NT8(c) | NT8(b) | NT8(b) | – | – | – | Previous state (Note 13) | – | NT8(a) | – | +| Received (SL2 or SL3) UOA = 1, ACT = 0 and DEA = 1 | | / | / | / | / | / | / | NT6 | – | – | NT7 | NT6 | – | NT6 | Previous state (Note 13) | – | – | / | +| Received (SL3) UOA = 1, ACT = 1 and DEA = 1 (Note 1) | | / | / | / | / | / | / | – | – | NT8 FEA | – | – | – | – | Previous state (Note 13) | – | – | / | + +TABLE A.II.2/G.961 (end) + +##### Activation/deactivation: NT (“H”) finite state matrix (DLL-only turn-on option) + +| Event ↓ | State name | Power off | Full reset | Alerting | EC training (optional) | EC converged | SW sync | ISW sync | ISW sync CALL | Pending Active | Active | UOA active | S/T deactivation | UOA and TE CALL | Pending deactivation | Tear down | TE inactive | Receive reset | +|---------------------------------------------|---------------------------|-----------|------------|----------|------------------------|--------------|----------|-------------------|-------------------|----------------|----------------|----------------|------------------|-----------------|----------------------|------------|----------------|---------------| +| | State code Fig. 17 event) | NT0 | NT1 (T0) | NT2 | NT3 (T1) | NT4 (T2) | NT5 (T3) | NT6(a) (T6) | NT6 (T6) | NT7 | NT8 | NT8(a) | NT8(b) | NT8(c) | NT9 | NT10 | NT11 | NT12 | +| | Signal→LT | SN0 | SN0 | TN | SN1 | SN0 | SN2 | SN3 ACT = 0 | SN3 ACT = 0 | SN3 ACT = 1 | SN3 ACT = 1 | SN3 ACT = 0 | SN3 ACT = 0 | SN3 ACT = 0 | SN3 (Note 8) | SN0 | SN3 ACT = 0 | SN0 | +| Signal→TE (Note 7) | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | SAI=1 or 0 INFO 0 | SAI=1 or 0 INFO 2 | SAI = 1 INFO 2 | SAI = 1 INFO 4 | SAI = 0 INFO 0 | SAI = 0 INFO 0 | SAI = 1 INFO 0 | | INFO 0 | SAI = 0 INFO 2 | INFO 0 | +| Loss of synchronization.(> 480 ms) (Note 1) | | / | / | / | / | / | / | NT10 | NT10 | NT10 | NT10 | NT10 | NT10 | NT10 | NT10 | – | NT10 | – | +| Loss of signal (> 480 ms) (Notes 1 and 11) | | / | / | / | / | STP.M4 NT1 | – | ST.M6 NT12 | ST.M6 NT12 | ST.M6 NT12 | ST.M6 NT12 | ST.M6 NT12 | ST.M6 NT12 | ST.M6 NT12 | / | / | ST.M6 NT12 | – | +| Expiry of timer M4 (15 seconds) (Note 1) | | / | / | / | NT10 | NT10 | NT10 | / | / | / | / | / | / | / | / | / | / | – | +| Loss of signal < 40 ms | | / | / | / | / | – | – | – | – | – | – | – | – | – | ST.M6 NT12 | ST.M6 NT12 | – | / | +| Expiry of timer M6 (40 ms) (Note 1) | | / | / | / | / | / | / | / | / | / | / | / | / | / | / | / | / | NT1 | + +NOTE – For symbols, abbreviations and notes, see Table A.II.4. + +TABLE A.II.3/G.961 + +#### **Activation/deactivation: LT (“J”) finite state matrix (DLL-only turn-on option)** + +| Event
↓ | State name | Power off | Full reset | Alerting | Awake | EC training (optional) | EC converged CALL | SW sync CALL | ISW sync CALL | Active | EC converged UOA | SW sync UOA | DDL active | Desactivation S/T | Desactivation alerting | Tear down | Pending deactivation | Receive reset | +|--------------------------------------------|----------------------------|-----------|--------------------|----------|---------|------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|---------------------------|-----------|----------------------|-----------------------| +| | State code (Fig. 17 event) | J0 | J1 (T0) | J2 | J3 (T1) | J4 (T3) | J5 (T4) | J6 | J7 (T7) | J8 | J5(a) (T4) | J6(a) | J8(a) | J7(a) | J9 | J10 | J11 | J12 | +| | Signal→NT | SL0 | SL0 | TL | SL0 | SL1 | SL2
DEA = 1
ACT = 0
UOA = 1 | SL2
DEA = 1
ACT = 0
UOA = 1 | SL3
DEA = 1
ACT = 0
UOA = 1 | SL3
DEA = 1
ACT = 1
UOA = 1 | SL2
DEA = 1
ACT = 0
UOA = 0 | SL2
DEA = 1
ACT = 0
UOA = 0 | SL3
DEA = 1
ACT = 0
UOA = 0 | SL3
DEA = 1
ACT = 0
UOA = 0 | SL3
DEA = 0
ACT = 0 | SL0 | SL0 | SL0 | +| Power on | | J1 | – | – | – | – | – | – | – | – | – | – | – | – | – | – | – | – | +| Low of power (Note 1) | | – | J0 FE7 | J0 FE7 | J0 FE7 | J0 FE7 | J0 FE7 | J0 FE7 | J0 FE7 | J0 FE7 | J0 FE7 | J0 FE7 | J0 FE7 | J0 FE7 | J0 FE7 | J0 FE7 | J0 FE7 | J0 FE7 | +| Activation request (FE1) (Note 1) | | – | ST.M6
J2
FE2 | – | – | – | – | – | – | – | J5 | J6 | J7 | J7 | – | – | – | – | +| U-only turn-on request (FE11) (Note 1) | | / | ST.M6
J2
FE2 | – | – | – | J5(a) | J6(a) | J7(a) | J7(a) | – | – | – | – | – | – | – | – | +| Deactivation request (FE5) (Notes 1 and 9) | | – | – | – | – | – | – | – | J9 | J9 | – | – | J9 | J9 | – | – | – | – | +| End of tone TL (3 ms) | | / | / | J3 | / | / | / | / | / | / | / | / | / | / | / | / | / | / | +| Received tone TN | | / | ST.M6
J3 | – | – | / | / | / | / | / | / | / | / | / | / | / | / | ST.M6
STP.M7
J3 | + +TABLE A.II.3/G.961 (cont.) + +#### Activation/deactivation: LT (“J”) finite state matrix (DLL-only turn-on option) + +| Event
↓ | State name | Power off | Full reset | Alerting | Awake | EC training (optional) | EC converged CALL | SW sync CALL | ISW sync CALL | Active | EC converged UOA | SW sync UOA | DDL active | Deactivation S/T | Deactivation alerting | Tear down | Pending deactivation | Receive reset | +|--------------------------------------------|----------------------------|-----------|------------|----------|-----------------|------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|---------------------------|-----------|----------------------|---------------| +| | State code (Fig. 17 event) | J0 | J1 (T0) | J2 | J3 (T1) | J4 (T3) | J5 (T4) | J6 | J7 (T7) | J8 | J5(a) (T4) | J6(a) | J8(a) | J7(a) | J9 | J10 | J11 | J12 | +| | Signal→NT | SL0 | SL0 | TL | SL0 | SL1 | SL2
DEA = 1
ACT = 0
UOA = 1 | SL2
DEA = 1
ACT = 0
UOA = 1 | SL3
DEA = 1
ACT = 0
UOA = 1 | SL3
DEA = 1
ACT = 1
UOA = 1 | SL2
DEA = 1
ACT = 0
UOA = 0 | SL2
DEA = 1
ACT = 0
UOA = 0 | SL3
DEA = 1
ACT = 0
UOA = 0 | SL3
DEA = 1
ACT = 0
UOA = 0 | SL3
DEA = 0
ACT = 0 | SL0 | SL0 | SL0 | +| Loss of signal energy (TN or SN1) | | / | – | – | J4, J6 or J6(a) | – | / | / | / | / | / | / | / | / | / | / | / | / | +| Echo canceller converged and FE11 (Note 1) | | / | – | – | – | J5(a) | – | – | – | – | – | – | – | – | – | – | – | – | +| Echo canceller converged and FE1 (Note 1) | | / | – | – | – | J6 | – | – | – | – | – | – | – | – | – | – | – | – | +| SW sync (SN2 or SN3) | | / | / | / | / | / | J6 | – | – | – | J6(a) | – | – | – | – | – | – | – | +| ISW sync (SN3) (Note 1) | | / | / | / | / | / | / | STP.M6
J7 | – | – | / | STP.M6
J8(a)
FE3 | – | – | – | – | – | – | +| Received (SN3) ACT = 0 (Note 1) | | / | / | / | / | / | / | / | FE3 | J7
FE7 | / | / | – | J8(a)
FE3 | – | – | – | – | +| Received (SN3) ACT = 1 (Note 1) | | / | / | / | / | / | / | / | J8
FE4 | – | / | / | / | – | – | – | – | – | + +TABLE A.II.3/G.961 (end) + +#### Activation/deactivation: LT (“J”) finite state matrix (DLL-only turn-on option) + +| Event
↓ | State name | Power off | Full reset | Alerting | Awake | EC training (optional) | EC converged CALL | SW sync CALL | ISW sync CALL | Active | EC converged UOA | SW sync UOA | DDL active | Deactivation S/T | Deactivation alerting | Tear down | Pending deactivation | Receive reset | +|------------------------------------------------|----------------------------|-----------|------------|----------|-----------------|------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|---------------------------|--------------|----------------------|---------------| +| | State code (Fig. 17 event) | J0 | J1 (T0) | J2 | J3 (T1) | J4 (T3) | J5 (T4) | J6 | J7 (T7) | J8 | J5(a) (T4) | J6(a) | J8(a) | J7(a) | J9 | J10 | J11 | J12 | +| | Signal→NT | SL0 | SL0 | TL | SL0 | SL1 | SL2
DEA = 1
ACT = 0
UOA = 1 | SL2
DEA = 1
ACT = 0
UOA = 1 | SL3
DEA = 1
ACT = 0
UOA = 1 | SL3
DEA = 1
ACT = 1
UOA = 1 | SL2
DEA = 1
ACT = 0
UOA = 0 | SL2
DEA = 1
ACT = 0
UOA = 0 | SL3
DEA = 1
ACT = 0
UOA = 0 | SL3
DEA = 1
ACT = 0
UOA = 0 | SL3
DEA = 0
ACT = 0 | SL0 | SL0 | SL0 | +| Received (SN3)
SAI = 1
(Note 1) | | / | / | / | / | / | / | / | – | – | / | / | J7
FE1
(Note 15) | – | – | – | – | – | +| Loss of synchronisation (> 480 ms)
(Note 1) | | / | / | / | / | / | / | / | J10
FE7 | J10
FE7 | / | / | J10
FE7 | J10
FE7 | J10
FE7 | – | – | – | +| Loss of signal (> 480 ms)
(Note 1) | | / | / | / | J1
(Note 16) | / | – | – | ST.M7
J12
FE7 | ST.M7
J12
FE7 | – | – | ST.M7
J12
FE7 | ST.M7
J12
FE7 | ST.M7
J12
FE7 | – | – | – | +| End of last superframe with DEA = 0 (Note 10) | | / | / | / | / | / | / | / | / | / | / | / | / | / | J11 | / | / | / | +| Expiry of timer M5 (15 seconds)
(Note 1) | | / | / | / | J10
FE7 | J10
FE7 | J10
FE7 | J10
FE7 | / | / | J10
FE7 | J10
FE7 | / | / | / | / | / | / | +| Absence of signal (< 40 ms)
(Note 1) | | / | – | / | / | / | – | – | – | – | – | – | – | – | – | ST.M7
J12 | J1
FE6 | – | +| Expiry of timer M7 (40 ms)
(Note 1) | | / | / | / | / | / | / | / | / | / | / | / | / | / | / | / | / | J1
FE6 | + +NOTE – For symbols, abbreviations, and notes, see Table A.II.4. + +TABLE A.II.4/G.961 + +#### **Symbols, abbreviations and notes for Tables A.II.2 and A.II.3** + +#### Symbols and abbreviations + +| | | +|---------|-----------------------------------------------------------------| +| – | No change, no action | +| / | Impossible or prohibited situation under normal circumstances | +| FE1 | Activate access (Note 1) – PH-AR | +| FE2 | Access activation initiated (Note 1) – MPH-AWI | +| FE3 | Access digital section activated (Note 1) – MPH-DSAI | +| FE4 | Access activated or loopback operated (Note 1) – PH/MPH-AI | +| FE5 | Deactivate access (Note 1) – PH/MPH-DR | +| FE6 | Access deactivated (Note 1) – PH/MPH-DI | +| FE7 | LOS/FA in DS or loss of power at NT (Note 1) – PH/MPH-EI | +| FE8 | Activate loopback 2 (Note 1) – MPH-L2AR | +| FE11 | DLL-only turn-on request (Note 1) – MPH-DSAR | +| NTn | Go to state NTn | +| LTn | Go to state LTn | +| L2 | Loopback 2 | +| ST.Mn | Start timer Mn | +| STP.Mn | Stop timer Mn | +| SLn,SNn | Signals defined in Figures II.6 and II.7 (SL0, SN0 = no signal) | +| Tn | Events defined in Figures II.6 and II.7 | + +#### NOTES + +- 1 Primitives are the subject of continuing study and are significant only in combined LT/ET implementations. +- 2 These events are initiated at the T reference point (see Tables 6/I.430 and 4/I.430). +- 3 This condition represents an Activation request event. +- 4 This condition indicates that the user data path (2B + D channels) in the TE-to-NT direction is transparent to user data. +- 5 This condition indicates that the user data path (2B + D channels) in the TE-to-NT direction is not transparent to user data. +- 6 This event takes priority over received ACT = ZERO for warm-start NTs. This event could be ignored for cold-start-only NTs. +- 7 S/T INFO signals are shown as transmit signals in Table II.3 which does not directly control these signals. They are included for information only. +- 8 The signals output in this state remain unchanged from signals output during the preceding state. (For example, ACT = ZERO if states NT6 or NT11 preceded, or ACT = ONE if states NT7 or NT8 preceded.) +- 9 This event will cause turn-off of the NT independent of whether the transmitter is cold-start-only or warm-start. +- 10 This event occurs after transmitting at least three superframes with DEA = ZERO. See II.10.1.5.2. +- 11 When in state NT4, absence of signal > 480 ms causes transition to state NT1. +- 12 When INFO 1 remains continuous after the NT fails to bring up the network side and returns to state NT1, the NT does not again go to state NT2, unless a new transition from INFO 0 to INFO 1 is received. See II.10.10 and Recommendation I.430. +- 13 The transceiver should return to the state from which it entered state NT9, unless the UOA or ACT bit(s) have changed. +- 14 The text for this note has been removed. +- 15 The network is permitted to choose no action rather than sending FE1 and transferring to state J7. For example, when the access link is undergoing maintenance, no action is an appropriate response. +- 16 When in state J3, absence of signal > 480 ms causes transition to state J1. + +![Sequence diagram for Figure A.II.3/G.961 showing a change from DLL-only to total activation initiated by exchange (AR).](5e05915b2a93a3b404422e0966a7c924_img.jpg) + +This sequence diagram illustrates the interaction between an AR (Access Router) and an AI (Access Interface) via intermediate nodes L1, U, NT, S/T, and TE. The sequence of messages is as follows: + +- The AR sends a message labeled **UOA=1** to the U node. +- The U node forwards this as **SL3** to the NT node. +- The NT node receives it as **UOA=1** and sends **INFO 2** to the TE node. +- The TE node then sends **INFO 3** back to the NT node. +- The NT node receives **INFO 3** and sends **SAI=1** to the U node. +- The U node receives **SAI=1** and sends **ACT=1** to the L1 node. +- The L1 node receives **ACT=1** and sends **SN3** to the AR node. +- The AR node receives **SN3** and sends **ACT=1** to the AI node. +- The AI node receives **ACT=1** and sends **2B + D = N** to the L1 node. +- The L1 node receives **2B + D = N** and sends **SN3** to the AR node. +- The AR node receives **SN3** and sends **2B + D = N** to the NT node. +- The NT node receives **2B + D = N** and sends **ACT=1** to the U node. +- The U node receives **ACT=1** and sends **INFO 4** to the TE node. +- The TE node receives **INFO 4** and sends it to the AI node. + +T1814460-92/d41 + +Sequence diagram for Figure A.II.3/G.961 showing a change from DLL-only to total activation initiated by exchange (AR). + +#### NOTES + +- 1 Receipt of INFO3 and SL3 at the NT can theoretically occur in either order. +- 2 For symbols and abbreviations see Table A.II.4. + +FIGURE A.II.3/G.961 +**Change from DLL-only to total activation initiated by exchange (AR)** + +![Sequence diagram for Figure A.II.4/G.961 showing a change from DLL-only to total activation initiated by terminal equipment (INFO 1).](64cda8ce20067bc360ce2f3a5c9352b7_img.jpg) + +This sequence diagram illustrates the interaction between an AR (Access Router) and an AI (Access Interface) via intermediate nodes L1, U, NT, S/T, and TE. The sequence of messages is as follows: + +- The TE node sends **INFO 1** to the NT node. +- The NT node receives **INFO 1** and sends **SAI=1** to the U node. +- The U node receives **SAI=1** and sends **SN3** to the L1 node. +- The L1 node receives **SN3** and sends **SAI=1** to the AR node. +- The AR node receives **SAI=1** and sends **UOA=1** to the U node. +- The U node receives **UOA=1** and sends **SL3** to the NT node. +- The NT node receives **SL3** and sends **UOA=1** to the TE node. +- The TE node receives **UOA=1** and sends **INFO 2** to the NT node. +- The NT node receives **INFO 2** and sends **ACT=1** to the U node. +- The U node receives **ACT=1** and sends **SN3** to the L1 node. +- The L1 node receives **SN3** and sends **ACT=1** to the AR node. +- The AR node receives **ACT=1** and sends **ACT=1** to the AI node. +- The AI node receives **ACT=1** and sends **2B + D = N** to the L1 node. +- The L1 node receives **2B + D = N** and sends **SN3** to the AR node. +- The AR node receives **SN3** and sends **2B + D = N** to the NT node. +- The NT node receives **2B + D = N** and sends **ACT=1** to the U node. +- The U node receives **ACT=1** and sends **INFO 3** to the TE node. +- The TE node receives **INFO 3** and sends **INFO 4** to the AI node. + +T1814470-92/d42 + +Sequence diagram for Figure A.II.4/G.961 showing a change from DLL-only to total activation initiated by terminal equipment (INFO 1). + +###### NOTES + +- 1 Receipt of INFO3 and SL3 at the NT can theoretically occur in either order. +- 2 For symbols and abbreviations see Table A.II.4. + +FIGURE A.II.4/G.961 +**Change from DLL-only to total activation initiated by terminal equipment (INFO 1)** + +![Sequence diagram for Figure A.II.5/G.961 showing the change from DLL-only to total activation initiated by exchange (UTR).](caeb1637753f79f4cd005eda3768d1d5_img.jpg) + +This sequence diagram illustrates the interaction between a User Terminal (UT) and a Network Terminal (NT) to initiate total activation. The sequence starts with the UT sending a UOA=0 message to the NT via the L1 interface. The NT responds with INFO 0. The UT then sends a message containing SN3, ACT=0, SAI=0, and 2B + D = 1. The NT replies with SL3. The UT receives SN3 and ACT=0 from the NT. The diagram includes lifelines for L2, ET, L1, U, L1, NT, L1, S/T, L1, TE, and L2. Reference T1814480-92/d43 is noted at the bottom right. + +Sequence diagram for Figure A.II.5/G.961 showing the change from DLL-only to total activation initiated by exchange (UTR). + +NOTE – For symbols and abbreviations see Table A.II.4. + +FIGURE A.II.5/G.961 +**Change from DLL-only to total activation initiated by exchange (UTR)** + +![Sequence diagram for Figure A.II.6/G.961 showing the total deactivation process (DR).](c07e21a8d65991db04263322f859c94f_img.jpg) + +This sequence diagram illustrates the total deactivation process (DR). It begins with the DR (Data Request) entity sending ACT=0 and DEA=0 messages to the NT via the L1 interface. The NT responds with SL3 and SL0. A vertical timing constraint of ≤40 ms is shown between the NT's response and the next message. The NT then sends SN0 to the DR. Another vertical timing constraint of ≤40 ms is shown between the SN0 message and the Rcv.R message. The Rcv.R message is followed by a 40 ms duration and a RESET message. The NT sends INFO 0 to the DR. Another vertical timing constraint of ≤40 ms is shown between the INFO 0 message and the Rcv.R message. The Rcv.R message is followed by a 40 ms duration and a RESET message. The diagram includes lifelines for L2, ET, L1, U, L1, NT, L1, S/T, L1, TE, and L2. Reference T1814490-92/d44 is noted at the bottom right. + +Sequence diagram for Figure A.II.6/G.961 showing the total deactivation process (DR). + +NOTE – For symbols and abbreviations see Table A.II.4. + +FIGURE A.II.6/G.961 +**Total deactivation process (DR)** + +![Timing diagram for DLL-only turn-on process initiated by the exchange from Reset (UTR).](5cc4a2ef554f31ea0577731931007fff_img.jpg) + +The diagram illustrates the sequence of events for a DLL-only turn-on process. It features several vertical lines representing time axes for different components: L2, ET, L1, U, L1, NT, L1, S/T, INFO 0, INFO 0, L1, TE, and L2. The process begins at the UTR (Upper Terminal Reference) point. + +Key elements include: + + +- Start M5**: Initiated at the UTR, with a signal labeled 'Start M5' pointing to the L1 line. +- Signals on L1**: A series of signals are shown on the L1 line, including 'TN', 'SN1', 'SN0', 'DEA=1', 'UOA=0', 'SL1', 'SL2', 'SN2', 'SAI=0', 'SW Sync.', 'SN3', '2B + D = 1', 'ISW Sync.', 'a)', '2B + D = 0', and 'SL3'. +- Start M4**: Initiated at the NT line, with a signal labeled 'Start M4' pointing to the L1 line. +- Stop M4**: Located at the NT line, with a signal labeled 'Stop M4' pointing to the L1 line. +- Stop M5**: Located at the UTR line, with a signal labeled 'Stop M5' pointing to the L1 line. +- Other labels**: 'UTR', 'UT1', 'L2', 'ET', 'U', 'NT', 'S/T', 'INFO 0', 'INFO 0', 'L1', 'TE', 'L2' are present at the top. A reference code 'T1814500-92/d45' is at the bottom right. + +Timing diagram for DLL-only turn-on process initiated by the exchange from Reset (UTR). + +a) Except to perform a loopback, 2B + D bits shall remain in the previous state (SN2 or SL2) until both ACT bits indicate full transparency of B- and D-channels. See Figure II.7. Transparency required to perform loopbacks is independent of the ACT bits. + +NOTE – For symbols and abbreviations see Table A.II.4. + +FIGURE A.II.7/G.961 + +**DLL-only turn-on process initiated by the exchange from Reset (UTR)** + +# Appendix III + +## Core functions and requirements for a line system using a TCM method + +(This appendix does not form an integral part of this Recommendation) + +## III.1 Line code + +For both transmission directions, the line code shall be AMI (*alternate mark inversion*). The coding scheme is performed in such a way that a binary ZERO is represented by no line signal (“0”), while a binary ONE is alternately represented by a positive or negative pulse (“+1” or “-1”). + +The binary ONEs and ZEROs from the interface at the T reference point and the corresponding bits from the network (across V1 reference point) must be treated as binary ONEs and ZEROs, respectively. + +The binary ONE and ZERO are represented below by “1” and “0”, respectively, but the above-defined AMI code rule shall be applied for the binary ONE. + +## III.2 Line baud rate + +The line baud rate is 320 kbaud. + +### III.2.1 Clock requirements + +#### III.2.1.1 NT1 free running clock accuracy + +The accuracy of the free running clock in the NT1 shall be $\pm 50$ ppm. + +#### III.2.1.2 NT1 clock tolerance + +The NT1 shall accept a clock accuracy from the LT of $\pm 10$ ppm. + +#### III.2.1.3 LT clock tolerance + +The LT shall accept a clock accuracy from the ET of $\pm 10$ ppm. + +## III.3 Frame structure + +A frame shall be 377 bits transmitted within a 1.178 ms interval. The frame repetition period shall be 2.5 ms. Each frame contains a frame word, 2B + D-channels, CL-channel and a parity bit as shown below. + +![Diagram of frame structure showing timing and bit fields.](7fe4241eea8865aa6d2686d711c13ba6_img.jpg) + +The diagram illustrates the timing and structure of a frame. At the top, two horizontal lines with arrows indicate time intervals: the top line is labeled '2.5 ms' and the bottom line is labeled '1.178 ms'. Below these, a table shows the sequence of fields in a frame: + +| | | | | | | +|------------|-------------------------|-------------------------------|---|-------|------------| +| Frame word | C L -channel | 20 times
(2B + D)
slots | P | Space | Frame word | +|------------|-------------------------|-------------------------------|---|-------|------------| + +Diagram of frame structure showing timing and bit fields. + +P Parity bit: The P bit is used to get an even number of "1"s in a frame; so it is set to "1" or "0" when the number of "1"s in a frame is odd or even, respectively. + +### III.3.1 Frame length + +The number of 2B + D slots in a frame is 20. Each slot contains 18 bits. + +### III.3.2 Bit allocation in direction LT-NT1 + +The bit allocation of the frame is shown in Figure III.1. See also Figure III.3. + +### III.3.3 Bit allocation in direction NT1-LT + +The bit allocation of the frame is shown in Figure III.2. See also Figure III.3. + +## III.4 Frame word + +The frame word is used to allocate bit position to the 2B + D + CL-channels. + +It may also be used for adjustment of adaptive line equalizer under the frame alignment state. + +### III.4.1 Frame word in direction LT-NT1 + +The code for the frame word in all frames shall be: + +FW = "100000M0"; + +where M is alternately "1" or "0" in each frame. See also Figure III.3. + +FIGURE III.1/G.961 +**Bit allocation in direction LT-NT1** + +| Bit positions | 1 ~ 8 | 9 | 10 | 11 ~ 13 | 14 ~ 16 | XX
(Note) | YY
(Note) | ZZ
(Note) | VV
(Note) | 377 | 378 ~ 800 | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------|----------------|--------------|----------|-------------------------|--------------|-------------------------|--------------|------------|------------------------|--|--|--|--|--| +| Functions | Frame word | Control bit | Multiframe bit | Control bits | CRC bits | B 1 -channel | D-channel | B 2 -channel | D-channel | Parity bit | Space (no line signal) | | | | | | +| | | C L -channel | | | | | | | | | | | | | | | +| NOTE – XX = (17 + 18 n ) until (24 + 18 n ) where n = 0 ~ 19.
YY = 25 + 18 n where n = 0 ~ 19.
ZZ = (26 + 18 n ) until (33 + 18 n ) where n = 0 ~ 19.
VV = 34 + 18 n where n = 0 ~ 19. | | | | | | | | | | | | | | | | | + +FIGURE III.2/G.961 + +#### **Bit allocation in direction NT1-LT** + +| Bit positions | 1 ~ 8 | 9 | 10 | 11 ~ 13 | 14 ~ 16 | XX
(Note) | YY
(Note) | ZZ
(Note) | VV
(Note) | 377 | 378 ~ 800 | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------|----------------|------------------|----------|-------------------------|--------------|-------------------------|--------------|------------|------------------------|--|--|--|--|--| +| Functions | Frame word | Information bit | Multiframe bit | Information bits | CRC bits | B 1 -channel | D-channel | B 2 -channel | D-channel | Parity bit | Space (no line signal) | | | | | | +| | | C L -channel | | | | | | | | | | | | | | | +| NOTE – XX = (17 + 18 n ) until (24 + 18 n ) where n = 0 ~ 19.
YY = 25 + 18 n where n = 0 ~ 19.
ZZ = (26 + 18 n ) until (33 + 18 n ) where n = 0 ~ 19.
VV = 34 + 18 n where n = 0 ~ 19. | | | | | | | | | | | | | | | | | + +![Diagram showing frame and multiframe structure and CL channel bits assignments. It includes a top-level frame diagram with 20 slots, a detailed bit breakdown for LT to NT1 and NT1 to LT directions, and a legend for bit fields like H1, H2, H3, C1, C2, AP, S, k1-k12, AI, T1, T2, T3, TC1, TC2, FEBE, Q1-Q4, ID1, ID2.](d1ad05f1189b0d80188fee24ae33c112_img.jpg) + +1 burst franc (377 bits, 1.178 mscf) + +20 slots (360 bits) for 2B+D channels \*\* +(\*\*Scrambled and CRC checked bits) + +8 bits 8 bits 18 bits + +Frame word CL channel Slot No. 1 Slot No. 2 Slot No. 3 Slot No. 19 Slot No. 20 P + +Parity bit P (1bit) + +LT → NT1 direction + +| | | | | | | | | | +|-----------------|------|----------------|----|----|----|-----|-----|-----| +| 1 0 0 0 0 0 M 0 | OF S | F 1 | AR | DR | AP | k1 | k2 | k3 | +| | OF S | F 2 | H1 | H2 | H3 | k4 | k5 | k6 | +| | OF S | F 3 | AR | DR | AP | k7 | k8 | k9 | +| | OF S | F 4 | C1 | C2 | S | k10 | k11 | k12 | + +NT1 → LT direction + +| | | | | | | | | | +|-----------------|----|----------------|-----|-----|------|-----|-----|-----| +| 1 0 0 0 0 0 0 M | AI | F 1 | Q1 | Q2 | ID1 | k1 | k2 | k3 | +| | AI | F 2 | T1 | T2 | T3 | k4 | k5 | k6 | +| | AI | F 3 | Q3 | Q4 | ID2 | k7 | k8 | k9 | +| | AI | F 4 | TC1 | TC2 | FEBE | k10 | k11 | k12 | + +B1 B1 B1 B1 B1 B1 B1 B1 D B2 B2 B2 B2 B2 B2 B2 B2 D +1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 2 + +H1, H2, H3 Loopback 2 request bits + "H1, H2, H3" = "1, 1, 1"; Loopback 2 request + "H1, H2, H3" = "1, 0, 0"; Loopback 21 request for B1 Channel (optional use) + "H1, H2, H3" = "0, 1, 0"; Loopback 22 request for B2 Channel (optional use) + +C1, C2 Loopback C request bits (optional use) + "C1, C2" = "1, 0"; Loopback C request for B1 Channel (optional use) + "C1, C2" = "0, 1"; Loopback C request for B2 Channel (optional use) + +AP Indication bit of active approval of network side + "1"; Active approval indication + +S Spare bits of the I.430 interface (optional use) + +k1 ~ k12 CRC-12 check bits + +AI INFO 3 receipt indication bit + "1"; Indication of receiving INFO 3 + +T1, T2, T3 Loopback 2 active indication bits + "T1, T2, T3" = "1, 1, 1"; Loopback 2 active + "T1, T2, T3" = "1, 0, 0"; Loopback 21 active for B1 Channel (optional use) + "T1, T2, T3" = "0, 1, 0"; Loopback 22 active for B2 Channel (optional use) + +TC1, TC2 Loopback C active indication bits (optional use) + "TC1, TC2" = "1, 0"; Loopback C active for B1 Channel (optional use) + "TC1, TC2" = "0, 1"; Loopback C active for B2 Channel (optional use) + +FEBE Far end block error indication bit + "1";Errored multiframe + +Q1 ~ Q4 Spare bits of the I.430 interface (optional use) + +ID1, ID2 Reserved bits + +M Alternately "1" or "0" in each frame + +OF S LT frame synchronization indication bit + "1"; Frame alignment state + "0"; Loss of frame alignment state + +"F1, F2, F3, F4" Multiframe word "1, 0, 0, 0" + +AR Activation request to the I.430 interface + "1"; Activation request + +DR Deactivation request bit to the I.430 interface + "1"; Deactivation request + +T1814510-92/d46 + +Diagram showing frame and multiframe structure and CL channel bits assignments. It includes a top-level frame diagram with 20 slots, a detailed bit breakdown for LT to NT1 and NT1 to LT directions, and a legend for bit fields like H1, H2, H3, C1, C2, AP, S, k1-k12, AI, T1, T2, T3, TC1, TC2, FEBE, Q1-Q4, ID1, ID2. + +FIGURE III.3/G.961 + +Frame and multiframe structure and CL channel bits assignments + +### III.4.2 Frame word in direction NT1-LT + +The code for the frame word in all frames shall be: + +FW = "1000000M"; + +where M is alternately "1" or "0" in each frame. See also Figure III.3. + +## III.5 Frame alignment procedure + +The frame alignment procedure is defined as follows. Refer also to Figure III.4. + +### 1) *Frame alignment state* + +The transmission system is considered to be in the frame alignment state if the frame word has been identified at the same position for 3 consecutive frames. + +### 2) *Loss of frame alignment state* + +The transmission system is considered to be in the loss of frame alignment state if the frame word has not been identified at the expected frame position for 6 frames before identifying the frame word at the expected frame position for 12 frames. + +## III.6 Multiframe + +To enable bit allocation of the CL-channel over more than one frame, a multiframe structure may be used. The start of the multiframe is determined by a multiframe word. The total number of frames in a multiframe is 4. + +### III.6.1 Multiframe word in direction LT-NT1 + +The multiframe is identified by a multiframe word allocated over 4 consecutive frames under the frame alignment state. The multiframe word is defined by the bits of the 10-th bit position of a frame (refer to Figure III.1 in direction LT-NT1 and Figure III.2 in direction NT1-LT) over 4 consecutive frames. The code for the multiframe word shall be: + +MFW = "1000" + +as shown in Figure III.3. + +The multiframe alignment procedure is defined as follows by referring to the bit allocation shown in Figure III.3. When the bit of the 10-th bit position of a frame is detected as "1" under the frame alignment state, the bit is recognized as the F1 bit of the multiframe word and this triggers the storage of the corresponding CL-channel bits in registers. The bits corresponding to F2, F3 and F4 bit positions are detected as "0"s, then the CL-channel bit values in the register are available, otherwise they are abandoned and set to idle. + +### III.6.2 Multiframe word in direction NT1-LT + +See III.6.1. + +## III.7 Frame offset between LT-NT1 and NT1-LT frames + +The NT1 shall synchronize its frame on the frame received in the direction LT to NT1 and will transmit its frame with an offset. Relative frame position at the NT1 input/output is as follows. The first bit of each frame transmitted from the NT1 towards the LT shall be delayed by 383 to 384 bit periods with respect to the first bit of the frame received from the LT. This relationship is shown in Figure III.5. + +The LT shall transmit a frame in each 2.5 ms burst repetition period. The first bit of the next frame transmitted from the LT towards the NT1 shall be delayed by 800 bit periods with respect to the first bit of the transmitting frame from the LT towards the NT1. + +A low pass filter used at the NT1 transmitter defined in III.12.2 might cause output pulse signal delay. An additional delay of up to a quarter of a bit period is permissible to the relative frame position at the NT1 input/output defined in Figure III.5. + +![State transition diagram for frame alignment showing states: Hunting, Confirming, and Synchronizing. Transitions are based on frame word detection and counter values (OK and NG). Solid oval Dashed oval](401f020d9ab5904f584424eabb596d2c_img.jpg) + +``` + +stateDiagram-v2 + direction TB + + Hunting : Hunting + Confirming_R : Confirming + Synchronizing : Synchronizing + Confirming_L : Confirming + + [*] --> Hunting : Upon entering this state OK/NG counters are cleared to 0 (OK:0, NG:0) + + Hunting --> Confirming_R : When a frame word is detected, change the state and 1 is added to OK counter (OK: +1) + + Confirming_R --> Confirming_R : When a frame word is detected at the expected frame position, 1 is added to OK counter (OK: +1) + Confirming_R --> Synchronizing : When the value of OK counter is equal to 3, change the state (OK: 3) + + Synchronizing --> Synchronizing : When a frame word is detected at the expected frame position, OK/NG counters are cleared to 0 (OK: 0, NG: 0) + Synchronizing --> Hunting : When a frame word is not detected at the expected frame position, change the state (NG: +1) + Synchronizing --> Confirming_L : When the value of OK counter is equal to 12, change the state (OK: 12) + + Confirming_L --> Confirming_L : When a frame word is detected at the expected frame position, 1 is added to OK counter (OK: +1) + Confirming_L --> Confirming_L : When a frame word is not detected at the expected frame position, 1 is added to NG counter (NG: +1) + Confirming_L --> Hunting : When the value of NG counter is equal to 6, change the state (NG: 6) + Confirming_L --> Hunting : When a frame word is not detected at the expected frame position, change the state + +``` + +**Legend:** + +- Frame alignment state +- Loss of frame alignment state + +T1814520-92/d47 + +State transition diagram for frame alignment showing states: Hunting, Confirming, and Synchronizing. Transitions are based on frame word detection and counter values (OK and NG). Solid oval Dashed oval + +FIGURE III.4/G.961 +**Method of frame alignment** + +![Timing diagram showing frame offsets between LT 2W-port and NT1 2W-port burst frames over an 800 T period.](8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg) + +The diagram illustrates the timing relationship between burst frames at an LT 2W-port and an NT1 2W-port over a total duration of 800 T. The LT 2W-port frames are shown at the top, and the NT1 2W-port frames are shown below. Dashed lines connect corresponding input and output frames between the two ports. + +- LT 2W-port:** + - An **Output burst frame** starts at the beginning of the 800 T period and has a duration of 377 T. + - An **Input burst frame** starts 377 T after the first output frame and also has a duration of 377 T. + - A third **Output burst frame** is shown starting at the 800 T mark. +- NT1 2W-port:** + - An **Input burst frame** starts 0~16 T after the beginning of the 800 T period and has a duration of 377 T. + - An **Output burst frame** starts 6~7 T after the input frame and has a duration of 377 T. + - A third **Input burst frame** starts 0~16 T after the output frame and has a duration of 7~40 T. + +Timing parameters are labeled at the bottom: 0~16 T, 377 T, 6~7 T, 377 T, 0~16 T, and 7~40 T. A reference code T1814530-92/d48 is present in the bottom right. + +Timing diagram showing frame offsets between LT 2W-port and NT1 2W-port burst frames over an 800 T period. + +NOTE – T = 3.125 μs (transmitted one bit period). + +FIGURE III.5/G.961 +Frame offset between LT-NT1 and NT1-LT frames + +## III.8 $C_L$ -channel + +### III.8.1 Bit rate + +The bit rate for the $C_L$ -channel is 3.2 kbit/s. + +### III.8.2 Structure + +- 1) 32 bits in a multiframe (3.2 kbit/s) are used for the $C_L$ -channel. +- 2) 4 bits per multiframe (0.4 kbit/s) are allocated to the multiframe word. +- 3) 16 bits per multiframe (1.6 kbit/s) are allocated to operation, maintenance, other functions and reserved bits as shown in Figure III.3. +- 4) 12 bits per multiframe (1.2 kbit/s) are allocated a cyclic redundancy check (CRC) code. + +### III.8.3 Protocols and procedures + +The $C_L$ -channel functions specified below are based on the bit allocation for the multiframe defined in Figure III.3. + +#### III.8.3.1 Error monitoring function + +##### III.8.3.1.1 Cyclic redundancy check (CRC) + +The CRC bits are k1 through k12 bits of the multiframe. The CRC is an error detection code that shall be generated from the appropriate bits in the multiframe and inserted into the bit stream by the transmitter. At the receiver a CRC calculated from the same bit shall be compared with the CRC value received in the bit stream. If the two CRCs differ, there has been at least one error in the covered multiframe bits. + +##### III.8.3.1.2 CRC algorithms + +The CRC code shall be computed using the polynomial: + +$$G(x) = x^{12} (+) x^6 (+) x^4 (+) x (+) 1$$ + +where (+) is modulo 2 summation. + +One method of generating the CRC code for a given multiframe is illustrated in Figure III.6. At the beginning of a multiframe all register cells are cleared to “0”. The multiframe bits to be covered by the CRC are then clocked into the generator from the left. During bits which are not covered by the CRC (FW, MFW, $C_L$ -channel bits and parity bit), the state of the CRC registers is frozen and no change in state of any of the stages takes place. After the last multiframe bit to be covered by the CRC is clocked into the generator, the 12 register cells contain the CRC code of this multiframe. Between this point and the beginning of the next multiframe, register cell are stored for transmission in the CRC field of the next multiframe. Note that multiframe bit k1 resides in REGISTER CELL 12, k2 in REGISTER CELL 11, etc. + +NOTE - The binary ONEs and ZEROs from the interface at the T reference point and corresponding bits across $V_1$ interface must be treated as binary ONEs and ZEROs, respectively, for the computation of CRC. + +##### III.8.3.1.3 Bits covered by CRC + +CRC bits shall be calculated from 2B + D channel bits before scrambling. + +#### III.8.3.2 Other $C_L$ -channel functions + +Several operation and maintenance functions are handled by the $C_L$ -channel bits in the multiframe shown in Figure III.3. These bits are available in SIGs 6, 7, 9, 13 and 15 in direction LT-NT1 and SIGs 8, 10, 11, 12 and 14 in direction NT1-LT defined in III.10.1. The definitions of these bits are given below. + +**III.8.3.2.1 far end block error reporting bit (FEBE):** The far end block error reporting bit shall be the FEBE bit in the fourth frame of the multiframe transmitted in direction NT1-LT. The FEBE bit shall be set to “1” if the multiframe contains a CRC error and “0” if there are no CRC errors in the multiframe. The FEBE shall be placed in the next available outgoing multiframe and transmitted back to the originator. The FEBE bits may be monitored by the network side to determine the performance of the far end receiver. + +![Block diagram of a CRC-12 generator. The diagram shows 12 register cells, each labeled 'Register cell n clear' (n=1 to 12), connected in a chain. Data input enters the first register cell through an adder. The output of each register cell is connected to an adder before the next register cell. The outputs of the register cells are also connected to 'Latch enable' blocks. The 'Latch enable' blocks are connected to outputs k12, k11, k10, k9, k8, k7, k6, k5, k4, k3, k2, and k1. Control signals 'Beginning of multiframe' and 'End of multiframe' are shown. A feedback path is shown from the output of the last register cell back to the first adder. The diagram is labeled T1814540-92/d49.](b3d488012fdceacab867cf24c5efef05_img.jpg) + +The diagram illustrates a CRC-12 generator circuit. It consists of 12 register cells, each labeled 'Register cell n clear' (n=1 to 12), connected in a chain. The data input enters the first register cell through an adder. The output of each register cell is connected to an adder before the next register cell. The outputs of the register cells are also connected to 'Latch enable' blocks. The 'Latch enable' blocks are connected to outputs k12, k11, k10, k9, k8, k7, k6, k5, k4, k3, k2, and k1. Control signals 'Beginning of multiframe' and 'End of multiframe' are shown. A feedback path is shown from the output of the last register cell back to the first adder. The diagram is labeled T1814540-92/d49. + +Block diagram of a CRC-12 generator. The diagram shows 12 register cells, each labeled 'Register cell n clear' (n=1 to 12), connected in a chain. Data input enters the first register cell through an adder. The output of each register cell is connected to an adder before the next register cell. The outputs of the register cells are also connected to 'Latch enable' blocks. The 'Latch enable' blocks are connected to outputs k12, k11, k10, k9, k8, k7, k6, k5, k4, k3, k2, and k1. Control signals 'Beginning of multiframe' and 'End of multiframe' are shown. A feedback path is shown from the output of the last register cell back to the first adder. The diagram is labeled T1814540-92/d49. + +NOTE – k1 ~ k12 are CRC-12 bits generated from the data in multiframe. + +FIGURE III.6/G.961 +**CRC-12 generator** + +**III.8.3.2.2 line system active indication bit (OFS):** The line system active indication bit shall be the OFS (Office-side Frame Synchronization) bit in the multiframe transmitted in direction LT-NT1. The OFS bit shall be set to "1" when the LT is in the frame alignment state and set to "0" when the LT enters the loss of frame alignment state. + +**III.8.3.2.3 T interface activation request bit (AR):** The bit for the activation request to the interface at the T reference point shall be the AR (Activation Request) bit in the first and third frames of the multiframe transmitted in direction LT-NT1. The AR bit shall be set to "1" when the activation request function element FE 1 is issued from the ET to the LT and set to "0" when the deactivation request function element FE 5 is issued from the ET to the LT. + +When the NT1 detects AR = "1" under the condition of OFS = "1" and while not receiving INFO 3, INFO 2 shall be sent towards the interface at the T reference point. + +**III.8.3.2.4 T interface active indication bit (AI):** The bit for the active indication of the interface at the T reference point shall be the AI (Active Indication) bit in the multiframe transmitted in direction NT1-LT. The AI bit shall be set to "1" when the NT1 receives INFO 3 from the TE and set to "0" when the NT1 does not receive INFO 3 from the TE. In case of loopback 2 operation, the AI bit shall be set to "1" when the T interface side of the NT1 is in the frame alignment state and set to "0" when it is in the loss of frame alignment state for the loopbacked bit stream. + +**III.8.3.2.5 active approval bit (AP):** The active approval bit shall be the AP (Active Approval) bits in the first and third frames of the multiframe transmitted in direction LT-NT1. The AP bit shall be set to "1" when the INFO 4 sending permission function element FE 13 is issued from the ET to the LT and set to "0" when the deactivation request function element FE 5 is issued from the ET to the LT. + +When the NT1 detects AP = "1" under the condition of receiving INFO 3, INFO 4 shall be sent towards the interface at the T reference point. + +**III.8.3.2.6 T interface deactivation request (DR):** The bit for the deactivation request to the interface at the T reference point shall be the DR (Deactivation Request) bit in the first and third frames of the multiframe transmitted in direction LT-NT1. The DR bit shall be set to "1" when an optional function element of the deactivation request to the interface at the T reference point only is issued from the ET to the LT. + +When the NT1 detects DR = "1" under the condition of OFS = "1", INFO 0 shall be sent towards the interface at the T reference point. + +**III.8.3.2.7 loopback 2 operation bits (H1, H2, H3):** The loopback 2 request bits shall be the H1, H2 and H3 bits in the second frame of the multiframe transmitted in direction LT-NT1. The code word "H1,H2,H3" shall be set to "1,1,1" when the loopback 2 activation request function element FE 8 is issued from the ET to the LT. + +This request directs the NT1 to loopback the user-data 2B + D bit stream towards the network. + +**III.8.3.2.8 loopback 2 active indication bits (T1, T2, T3):** The loopback 2 active indication bits shall be the T1, T2 and T3 bits in the second frame of the multiframe transmitted in direction NT1-LT. The code word "T1,T2,T3" is set to "1,1,1" when the code word "H1,H2,H3" is detected as "1,1,1" by the NT1. + +##### **III.8.3.2.9 Reserved bits** + +###### **III.8.3.2.9.1 Reserved bits for optional functions** + +Optional functions are handled by the CL-channel. These functions are defined in Annex A to Appendix III of this Recommendation. The reserved bits for the use of optional functions are defined below. + +The loopback 21 is operated by the code word "H1,H2,H3" and the active indication is reported by the code word "T1,T2,T3". + +Any code allocation to the code words "H1,H2,H3" and "T1,T2,T3" is reserved for this optional loopback 21 function. When not used, these code words shall be set to "0,0,0"s, excepting the use for the loopback 2 operation defined in III.8.3.2.7 and III.8.3.2.8. + +The C1 and C2 bits are reserved for the loopback C operation, and the TC1 and TC2 bits are reserved for the loopback C active indication. When not used, these bits shall be set to "0"s. + +The S bit in the fourth frame of the multiframe transmitted in direction LT-NT1 and the Q1, Q2, Q3, Q4 bits in the first and third frames of the multiframe in direction NT1-LT are reserved for transferring the spare bits S (in direction NT1-TE) and Q1, Q2, Q3, Q4 (in direction TE-NT1) defined on the interface at the T reference point. When not used, the S bit shall be set to "0" and the Q1, Q2, Q3, Q4 bits shall be set to "1"s. + +###### III.8.3.2.9.2 Reserved bits for future standardization + +All bits in the multiframe not otherwise assigned are reserved bits for future standardization. These bits are the ID1 bit in the first frame of the multiframe transmitted in direction NT1-LT and the ID2 bit in the third frame of the multiframe transmitted in direction NT1-LT. These bits shall be set to "0"s. + +#### III.8.3.3 Definition of transfer mode of CL-channel bits + +The transfer and sending modes and detection algorithm of the CL-channel bits of the OFS, AR, AI, AP, DR, H1, H2, H3, T1, T2, T3, C1, C2, TC1, TC2 shall conform to the definition below. See also Annex A to Appendix III as for the H1, H2, H3, T1, T2 and T3 bits. + +- 1) Transfer mode: bit-oriented. +- 2) Sending mode: continuous. +- 3) Detection algorithm: + - The bits in a multiframe are available when they are detected under the multiframe alignment state. + - In the loss of multiframe alignment state, the bits contained in the multiframe are abandoned and are set to "0"s, except for the Q1, Q2, Q3, Q4 bits which are set to "1"s. + - Identification is confirmed by detecting identical bits over 3 consecutive cycles. This identification is done on each bit by using the bit values given by the above-defined detection algorithm. +- 4) Duration of control invocation is as long as sending control is identified. +- 5) Duration of information invocation is as long as causing event is identified. + +## III.9 Scrambling + +Scrambling is applied only to the 2B + D-channel bits prior to the insertion of the frame word and CL-channel bits. The scrambling polynomial is the same in both directions (LT-NT1 and NT1-LT). A 9-th order polynomial is used. The scrambling polynomial shall be: + +$$P(x) = 1 (+) x^{-4} (+) x^{-9}$$ + +and the scrambled data transmitted shall be: + +$$D_0 = D_1 (+) P(x)$$ + +where (+) is modulo 2 summation. See also Figure III.7. + +## III.10 Activation/deactivation + +This subclause gives requirements for the activation and deactivation procedures and signals used for activation and deactivation. + +The following definitions are for the purpose of clarifying requirements for the activation/deactivation of the line system defined here. + +- 1) The procedures on the line system support the procedures on the interface at the T reference point for call control in accordance with Recommendation I.430 and the operation of loopback 1 (in the LT), 2 (in the NT1) and other optional loopbacks in accordance with Recommendation I.603. The loopbacks 1 and 2 are non-transparent. + +###### NOTES + +- 1 A non-transparent loopback 1 is provided by transmitting no line signal in direction LT-NT1. +- 2 A non-transparent loopback 2 is provided by sending no signal (INFO 0) from the NT1 to the interface at the T reference point. + +![Diagram of an LT/NT1 transmit scrambler and receive descrambler. It shows a series of nine register cells, each labeled with an initial value: ('0'), ('1'), ('1'), ('0'), ('1'), ('0'), ('0'), ('0'), ('0'). Each cell contains an x^{-1} operator. The output of the ninth cell is connected to a summation node (circle with a cross) which also receives an external input D_1. The output of this node is D_0. A feedback path branches off from the output of the fourth cell, goes through another summation node, and then loops back to the input of the first cell.](b3335932702b8668e62791e9fd12c9ff_img.jpg) + +Diagram of an LT/NT1 transmit scrambler and receive descrambler. It shows a series of nine register cells, each labeled with an initial value: ('0'), ('1'), ('1'), ('0'), ('1'), ('0'), ('0'), ('0'), ('0'). Each cell contains an x^{-1} operator. The output of the ninth cell is connected to a summation node (circle with a cross) which also receives an external input D\_1. The output of this node is D\_0. A feedback path branches off from the output of the fourth cell, goes through another summation node, and then loops back to the input of the first cell. + +T1814550-92/d50 + +NOTE – At the beginning of a frame all register cells are cleared and loaded with initial values defined above each register as (“0”) or (“1”) in the figure. + +FIGURE III.7/G.961 +**LT/NT1 transmit scrambler and receive descrambler** + +- 2) The system provides the activation of both the line system and the interface at the T reference point, and the deactivation of both the line system and the interface at the T reference point. The line system only activation, where the full information transfer capability is available while the interface at the T reference point remains deactivated, is not provided. + +The extension to provide this activation mode may, however, be possible when the INFO 1 receipt indication from the NT1 to the network is performed by one of the reserved bits in the $C_L$ -channel in direction NT1-LT defined in III.8.3.2.9.2. + +- 3) Activation/deactivation is provided to enable the use of a power down state especially for applications, where the NT1 is powered from the LT via the local line. The power down state is equal to the deactivated state and in the deactivated state, no line signal is present on the local line. But the power feeding to the interface at the T reference point is provided in accordance with the restricted power conditions defined in Recommendation I.430 even in the deactivated state by the power fed to the NT1 via the local line, taking into account the call origination from a designated TE. The minimum supplying power to the interface at the T reference point in the deactivated state shall be 420 mW. In the deactivated state, the NT1 consumes just enough power to detect SIG 3 (awake signal) from the LT and INFO 1 from the interface at the T reference point. + +In the activated state, the power feeding to the interface at the T reference point is also provided in accordance with the restricted power conditions defined in Recommendation I.430. The maximum permissible power consumption of the NT1 from the line, where the NT1 is powered from the LT via the local line, shall be less than or equal to 1000 mW including restricted mode powering of the interface at the T reference point. + +- 4) Two types of start-up processes such as warm-start and cold-start defined in 5.5/G.960 are not defined. The adoption of the warm-start realizes shorter activation times from the deactivated state to the activated state. When both the cold-start and warm-start are supported, the ET layer 1 may be required to handle two timer T1 values. The line system defined here must meet the activation times defined in III.10.6, including the first powering of the NT1 from the LT via the local line, which corresponds to the values of the activation times for the warm-start. +- 5) A master/slave relationship is assumed between the LT and NT1, so that, even if the NT1 starts to request activation, it is always the LT (under ET acknowledgement) that assumes the initiative of continuing the procedure and then the transmission. + +- 6) During activation, appropriate signals are sent to speed up the convergence of the line equalizer and bit and frame synchronization. +- 7) Sending of INFO 2 to the interface at the T reference point is initiated after the line system is synchronized in both directions LT-NT1 and NT1-LT. This conforms to 5.3.1.6 b)/G.960. In this case, to avoid premature sending of INFO 4, a delay time (since the receipt of INFO 3) may be implemented in the ET layer 1, and the additional function element FE 13 is defined to inform the line system of permission to initiate sending INFO 4. See Note 4 to Table 6/I.430 and 5.3.1.4/G.960. +- 8) After a temporary power-off of the NT1, which the NT1 might encounter at a temporary short or opening of the line, the line system may not restore the operation in progress before this interruption happens even after this interruption is removed, assuming activation from the user side and that TEs fell into INFO 0 sending state. This is because the NT1 forgets that the activation was initiated from the user side so that the NT1 should initiate to send INFO 2, and is also because TEs fell into INFO 0 sending state. To avoid this, the activation request function element FE 1 may be issued from the ET layer 1 to the LT after the ET received the activation initiated indication function element FE 2 from the LT even in case of activation from the user side. This makes the line system to enter the same state as activation from the network side. + +### III.10.1 Signals used for activation + +During the activation/deactivation procedures, the following specific signals (SIGs) are exchanged over the local line between the LT and NT1. There are three kinds of signals; the first are the signals that do not use the frame structure defined in III.3, the second are the signals that conform to the frame structure and are transceived before frame synchronization establishment of the line system (the $C_L$ -channel bits are not available), and the others are the signals that conform to the frame structure and are transceived after the line system enters the frame synchronization state (the $C_L$ -channel bits are available). + +The definitions of the signals are given below, and lists of SIGs conforming to the frame structure are shown in Tables III.1 and III.2. + +- 1) *Signals not using the frame structure* + +SIG 0      LT to NT1 and NT1 to LT + +No line signal. + +SIG 1      LT to NT1 + +**line system deactivate signal:** A signal to request that the layer entity in the NT1 has to enter the power-down state. It deactivates both the line system and the interface at the T reference point. + +This signal is continuous up to the appearance of SIG 3. The method of realizing this signal is to use feeding d.c. voltage polarity on the local line where the NT1 is powered from the LT via the local line. + +SIG 2a      NT1 to LT + +**awake (acknowledgement) signal:** A signal to invoke the LT and ET layer 1 so that they initiate the activation of the line system and the interface at T reference point. This signal is invoked by the receipt of INFO 1 across the T reference point in the NT1. + +This signal is also used as awake acknowledgement of SIG 3. + +This signal is continuous during the period that SIG 3 appears. The method of realizing this signal is to use feeding d.c. flow in the local line where the NT1 is powered from the LT via the local line. + +SIG 2b      NT1 to LT + +**complementary SIG 2a:** A signal which corresponds to that SIG 2a does not appear. + +SIG 3      LT to NT1 + +TABLE III.1/G.961 + +#### Signals in direction LT-NT1 conforming to the frame structure + +| SIGs | Direction | FW | C L -channel in direction (NT1 ← LT) | | | | | | | | | | 2B + D-channels | +|--------------------|-----------|-----|-------------------------------------------------|-----|----------|-----|-----|---------------|-------------------|-------|-----|-----|-------------------| +| | | | OFS | MFW | AR | DR | AP | 111, 112, 113 | S | CRC | C1 | C2 | | +| SIG 4 | NT1 ← LT | av. | "0" | "0" | "0" | "0" | "0" | "0, 0, 0" | "0" | "0" | "0" | "0" | t. p. | +| SIG 6 | NT1 ← LT | av. | "1" | av. | (Note 1) | "0" | "0" | "0, 0, 0" | inop.
(Note 2) | disp. | "0" | "0" | inop.
(Note 2) | +| SIG 7 | NT1 ← LT | av. | "1" | av. | (Note 1) | "0" | "1" | "0, 0, 0" | op.
(Note 2) | disp. | "0" | "0" | op. | +| SIG 9 | NT1 ← LT | av. | "1" | av. | "0" | "0" | "0" | "1, 1, 1" | op.
(Note 2) | disp. | "0" | "0" | op. | +| SIG 13
(Note 3) | NT1 ← LT | av. | "1" | av. | "0" | "1" | "0" | "0, 0, 0" | inop.
(Note 2) | disp. | "0" | "0" | inop.
(Note 2) | +| SIG 15
(Note 3) | NT1 ← LT | av. | "1" | av. | "0" | "0" | "0" | "0, 0, 0" | inop.
(Note 2) | disp. | "0" | "0" | inop.
(Note 2) | + +av. Available +t. p. Training pattern +inop. Inoperative data +op. Operational data + +NOTES + +- 1 AR = "1" when FE 1 is received, +AR = "0" when FE 1 is not received. +- 2 Even in inoperative case, data across V1 interface is transmitted to the NT1. +- 3 Use is a network option. + +TABLE III.2/G.961 + +#### Signals in direction NT1-LT conforming to the frame structure + +| SIGs | Direction | FW | C L -channel in direction (NT1 → LT) | | | | | | | | | | 2B + D-channels | +|--------|------------------|-----|-------------------------------------------------|-----|------------|------|----------------|-----|-----|-----|-----|-----|-----------------| +| | | | AI | MFW | T1, T2, T3 | FEBE | Q1, Q2, Q3, Q4 | CRC | TC1 | TC2 | ID1 | ID2 | | +| SIG 5 | NT1 → LT | av. | "0" | "0" | "0, 0, 0" | "0" | "0"s | "0" | "0" | "0" | "0" | "0" | t. p. | +| SIG 8 | NT1 → LT | av. | "1" | av. | "0, 0, 0" | av. | "1"s | av. | "0" | "0" | "0" | "0" | all "1"s | +| SIG 10 | NT1 → LT | av. | "1" | av. | "1, 1, 1" | av. | op. | av. | "0" | "0" | "0" | "0" | op. | +| SIG 11 | NT1 → LT | av. | "1" | av. | "0, 0, 0" | av. | op. | av. | "0" | "0" | "0" | "0" | op. | +| SIG 12 | NT1 → LT | av. | "0" | av. | "1, 1, 1" | av. | "1"s | av. | "0" | "0" | "0" | "0" | all "1"s | +| SIG 14 | NT1 → LT | av. | "0" | av. | "0, 0, 0" | av. | "1"s | av. | "0" | "0" | "0" | "0" | all "1"s | +| av. | Available | | | | | | | | | | | | | +| t. p. | Training pattern | | | | | | | | | | | | | +| op. | Operational data | | | | | | | | | | | | | + +**awake (acknowledgement) signal:** A signal to invoke the NT1 layer 1 so that it enters the power up state and prepares for synchronization on an incoming signal from the LT. + +This signal is also used as awake acknowledgement of SIG 2a. + +This signal is continuous up to the appearance of SIG 1. The method of realizing this signal is to use feeding d.c. voltage polarity on the local line where the NT1 is powered from the LT via the local line. The voltage polarity of this signal is the reverse of that of SIG 1. + +#### 2) *Signals conforming to the frame structure* + +(CL-channel bits are not available) + +SIG 4 LT to NT1 + +**training signal:** A signal to speed up convergence of the line equalizer and bit and frame synchronization in the NT1. The signal structure shall conform to the frame structure and contain the frame word. The CL-channel bits shall be set to "0"s. An example of realizing this signal is illustrated in Figure III.8. + +This signal is also transmitted when the LT enters the loss of frame alignment state under the condition that activation has been requested. + +SIG 5 NT1 to LT + +**training signal:** A signal to speed up convergence of the line equalizer and bit and frame synchronization in the LT. The signal structure shall conform to the frame structure and contain the frame word. The CL-channel bits shall be set to "0"s. An example of realizing this signal is illustrated in Figure III.9. + +This signal informs the LT that the NT1 has synchronized on SIG 4. + +![Diagram of training signal structure for SIG 4 (LT to NT1). It shows a 16-bit frame word: 1 0 0 0 0 0 M 0 0 0 0 0 0 0 0, followed by '+ 45 times', and then a 16-bit frame word: 1 0 0 0 0 0 0 0 + P. Below the second frame word is the text 'T1814560-92/d51'.](2e18ae7359d8c32e96919956f238ecc5_img.jpg) + +Diagram of training signal structure for SIG 4 (LT to NT1). It shows a 16-bit frame word: 1 0 0 0 0 0 M 0 0 0 0 0 0 0 0, followed by '+ 45 times', and then a 16-bit frame word: 1 0 0 0 0 0 0 0 + P. Below the second frame word is the text 'T1814560-92/d51'. + +NOTE – M is "0" / "1" alternating bit in every frame. P is a parity bit and is set to P = M in the training signal. + +FIGURE III.8/G.961 +**Training signal in direction LT-NT1** + +#### 3) *Signals conforming to the frame structure* + +(CL-channel bits are available) + +SIG 6 LT to NT1 + +**line system active indication signal:** A signal which informs the line system activation establishment to the NT1. This signal orders the NT1 to initiate the activation of the interface at the T reference point by sending INFO 2. + +This signal contains the frame word, multiframe word, and the CRC bits in the CL-channel. The OFS bit in the CL-channel is set to "1". The AR bit in the CL-channel is set to "1" when the active request function element FE 1 is received in the LT, or is set to "0" when the active request function element FE 1 is not received in the LT. The other CL-channel bits, except the S bit, are set to "0"s. The S and 2B + D-channel bits may contain inoperative data. + +SIG 7 LT to NT1 + +![Diagram showing the structure of a training signal. It consists of a 16-bit frame word (1 0 0 0 0 0 M 0 0 0 0 0 0 0 0) repeated 45 times, followed by a 9-bit frame word (1 0 0 0 0 0 0 0 0) and a parity bit P. The text 'T1814570-92/d52' is shown below the second frame word.](21ea5add6a61cc951b5c43ddffefb3ff_img.jpg) + +T1814570-92/d52 + +Diagram showing the structure of a training signal. It consists of a 16-bit frame word (1 0 0 0 0 0 M 0 0 0 0 0 0 0 0) repeated 45 times, followed by a 9-bit frame word (1 0 0 0 0 0 0 0 0) and a parity bit P. The text 'T1814570-92/d52' is shown below the second frame word. + +NOTE – M is “0” / “1” alternating bit in every frame. P is a parity bit and is set to P = M in the training signal. + +FIGURE III.9/G.961 +**Training signal in direction NT1-LT** + +**normal operation signal:** A signal which allows the NT1 to establish the full layer 1 information transfer capability available between the TE and ET by sending INFO 4 towards the interface at the T reference point under the condition of the receipt of INFO 3. + +This signal contains the frame word, multiframe word, and CRC bits in the CL-channel. The OFS and AP bits in the CL-channel are set to “1”s. The AR bit in the CL-channel is set to “1” when the activation request function element FE 1 is received in the LT, or is set to “0” when the activation request function element FE 1 is not received in the LT. The S bit across the V1 interface is conveyed by the S bit in the CL-channel if the network provides this transfer function. The other CL-channel bits are set to “0”s. The 2B + D-channel bits contain operational data. + +SIG 8      NT1 to LT + +**INFO 3 receipt indication signal:** A signal which indicates the receipt of INFO 3 by the NT1 and requires the LT and ET to provide the full layer 1 information transfer capability available between the TE and ET. This signal is invoked by the receipt of INFO 3 from the interface at the T reference point. This signal is also used as the loopback 2 deactivating signal. + +This signal contains the frame word, multiframe word, FEBE bit and CRC bits in the CL-channel. The AI bit in the CL-channel is set to “1” and the Q1, Q2, Q3 and Q4 bits in the CL-channel are set to “1”s. The other CL-channel bits are set to “0”s. The 2B + D-channel bits may be set to all “1”s. + +SIG 9      LT to NT1 + +**loopback 2 operation signal:** A signal which informs the line system activation establishment to the NT1, and requires the NT1 to operate loopback 2. + +This signal contains the frame word, multiframe word, S bit and CRC bits in the CL-channel. The OFS and H1, H2, H3 bits in the CL-channel are set to “1”s. The other CL-channel bits are set to “0”s. The 2B + D-channel bits contain operational data. + +SIG 10     NT1 to LT + +**loopback 2 operation signal:** A signal which indicates that the loopback 2 is established in the NT1. + +This signal contains the frame word, multiframe word, FEBE bit and CRC bits in the CL-channel. The T1, T2, T3 and AI bits in the CL-channel are set to “1”s. The 2B + D-channel and Q1, Q2, Q3, Q4 bits contains operational data. The other CL-channel bits are set to “0”s. If the loopback is normally operated in the NT1, the 2B + D-channels bits in this signal correspond to the 2B + D-channel data received at the NT1, and the Q1, Q2, Q3 and Q4 bits in this signal correspond to the S bit data received at the NT1. + +SIG 11     NT1 to LT + +**normal operation signal:** A signal which is transmitted upon receipt of SIG 7. + +This signal contains the frame word, multiframe word, FEBE bit and CRC bits in the CL-channel. The AI bit in the CL-channel is set to "1". The 2B + D-channel and Q1, Q2, Q3, Q4 bits contain operational data. The other CL-channel bits are set to "0"s. + +SIG 12 NT1 to LT + +**loopback 2 activating indication signal:** A signal which indicates that the NT1 receives the loopback 2 activation request and is activating the loopback 2. + +This signal contains the frame word, multiframe word, FEBE bit and CRC bits in the CL-channel. The T1, T2, T3, Q1, Q2, Q3 and Q4 bits in the CL-channel are set to "1"s. The other CL-channel bits are set to "0"s. The 2B + D-channel bits may be set to all "1"s. + +SIG 13 LT to NT1 + +**T interface deactivate signal:** A signal requiring the deactivation of the interface at the T reference point by sending INFO 0. + +This signal contains the frame word, multiframe word and CRC bits in the CL-channel. The OFS and DR bits in the CL-channel are set to "1"s. The other CL-channel bits, except the S bit, are set to "0". The S and 2B + D-channel bits may contain inoperative data. + +Use of this signal is a network option. This signal makes it possible to deactivate the interface at the T reference point without deactivating the line system, and from this state, the network can activate the loopback 2 or reactivate the interface at the T reference point. Activation from the user side is not accepted while this signal is being received at the NT1. + +SIG 14 NT1 to LT + +**INFO 2 sending indication signal:** A signal which indicates that the NT1 is in the state of activating the interface at the T reference point by sending INFO 2. This signal is sent both when the activation of the interface is initiated and when the interface entered the loss of frame alignment state under the line system active state. This signal is also used as acknowledgement of the T interface deactivate signal SIG 13. When SIG 14 is used as acknowledgement of SIG 13, INFO 2 sending is inhibited by SIG 13 and INFO 0 is sent towards the interface at the T reference point. + +This signal contains the frame word, multiframe word, FEBE bit and CRC bits in the CL-channel. The Q1, Q2, Q3 and Q4 bits in the CL-channel are set to "1"s. The other CL-channel bits are set to "0"s. The 2B + D-channel bits may be set to all "1"s. + +This signal is intended for FEBE reporting in an early stage of the activation procedure. This signal can be replaced by SIG 5 if the FEBE reporting function in the early stage of the activation procedure is not required. + +SIG 15 LT to NT1 + +**loopback 2 deactivate signal:** A signal which requests the deactivation of the loopback 2. + +This signal contains the frame word, multiframe word and CRC bits in the CL-channel. The OFS bit in the CL-channel is set to "1". The other CL-channel bits, except the S bit, are set to "0"s. The S and 2B + D-channel bits may contain inoperative data. + +Use of this signal is a network option. This signal makes it possible to deactivate the loopback 2 in the NT1 without deactivating the line system and from this state, the network can activate the interface at the T reference point or reactivate the loopback 2. Activation from the user side may be initiated when INFO 1 is received at the NT1. + +**III.10.2 Definition of timers:** Timer T1 and timer T2 defined in Recommendation I.430 are used. The locations of the timers are as follows: + +- Timer T1; in the ET layer 1; +- Timer T2; in the LT. + +The values of timer T1 and timer T2 shall conform to the specifications defined in 6.2.5/I.430. An example of a timer T1 value is 1.0 sec, and the activation times of the line system shall be defined by taking this value into account. + +NOTE - As an implementation option, timer T2 may be implemented in the ET layer 1. In this case an additional functional element needs to be defined to inform the line system of the expiry of timer T2. + +### III.10.3 Description of the activation procedure + +Activation and deactivation procedures are illustrated by arrow diagrams below. The arrow diagrams are illustrated for the non-failure situation. + +- 1) Activation from the network side: +See Figure III.10. +- 2) Activation from the user side: +See Figure III.11. +- 3) Deactivation from the network side: +See Figure III.12. +- 4) Activation of loopback 2: +See Figure III.13. + +NOTE - Definition of the function elements (FEs) across the V1 reference point is given in 5/G.960. FEs used for activation/deactivation are shown in Table III.3. + +![Sequence diagram showing activation from the network side between TE, NT1, LT, and ET entities.](34d7353cac3d344f71ad82bd1eda40d1_img.jpg) + +``` + +sequenceDiagram + participant TE + participant NT1 + participant LT + participant ET + TE->>NT1: INFO 0 + NT1->>TE: INFO 0 + NT1->>LT: SIG 0, 1 + NT1->>LT: SIG 0, 2b + ET->>LT: FE 1 + LT->>NT1: SIG 3, 4 + NT1->>LT: SIG 2a + ET->>LT: FE 2 + NT1->>LT: SIG 5 + NT1->>LT: SIG 6 + ET->>LT: FE 3 + LT->>NT1: SIG 14 + NT1->>TE: INFO 2 + TE->>NT1: INFO 3 + NT1->>LT: SIG 8 + ET->>LT: FE 4 + ET->>LT: FE 13 + LT->>NT1: SIG 7 + NT1->>TE: INFO 4 + NT1->>LT: SIG 11 + +``` + +The diagram illustrates the activation procedure from the network side across four entities: TE (Terminal Equipment), NT1 (Network Termination 1), LT (Line Termination), and ET (Exchange Termination). The sequence shows bidirectional INFO signals between TE and NT1, SIG signals between NT1 and LT, and FE (Function Element) signals between LT and ET. Key steps include initial INFO 0 exchange, followed by a series of SIG and FE messages leading to INFO 2, INFO 3, and finally INFO 4 signaling full activation. + +T1816590-92/d53 + +Sequence diagram showing activation from the network side between TE, NT1, LT, and ET entities. + +**FIGURE III.10/G.961** +**Activation from the network side** + +![Sequence diagram for activation from the user side showing interactions between TE, NT1, LT, and ET.](9687bd5e8b62cadba093b0d1b70536cd_img.jpg) + +This sequence diagram illustrates the activation process from the user side. The participants are TE (Terminal Equipment), NT1 (Network Termination 1), LT (Line Termination), and ET (Exchange Termination). The sequence of messages is as follows: + +- TE sends INFO 0 to NT1. +- NT1 responds with SIG 0, 1 to TE. +- TE sends another INFO 0 to NT1. +- NT1 responds with SIG 0, 2b to TE. +- TE sends INFO 1 to NT1. +- NT1 responds with SIG 2a to TE. +- NT1 also sends SIG 3, 4 to LT. +- LT sends FE 2 to ET. +- ET sends FE 1 (Note) back to LT. +- NT1 sends SIG 5 to LT. +- TE sends INFO 2 to NT1. +- NT1 responds with SIG 6 to TE. +- NT1 also sends SIG 14 to LT. +- LT sends FE 3 to ET. +- TE sends INFO 3 to NT1. +- NT1 responds with SIG 8 to TE. +- NT1 also sends SIG 7 to LT. +- LT sends FE 4 to ET. +- TE sends INFO 4 to NT1. +- NT1 responds with SIG 11 to TE. +- LT sends FE 13 to ET. + +T1816600-92/d54 + +Sequence diagram for activation from the user side showing interactions between TE, NT1, LT, and ET. + +NOTE – Network option. + +FIGURE III.11/G.961 +Activation from the user side + +![Sequence diagram for deactivation from the network side showing interactions between TE, NT1, LT, and ET.](e18841eb4a995df8354a793459e12fd0_img.jpg) + +This sequence diagram illustrates the deactivation process from the network side. The participants are TE, NT1, LT, and ET. The sequence of messages is as follows: + +- TE sends INFO 4 to NT1. +- NT1 responds with SIG 7 to TE. +- TE sends INFO 3 to NT1. +- NT1 responds with SIG 11 to TE. +- TE sends INFO 0 to NT1. +- NT1 responds with SIG 0. 1 to TE. +- TE sends another INFO 0 to NT1. +- NT1 responds with SIG 0. 2b to TE. +- NT1 also sends SIG 0. 1 to LT. +- LT sends FE 5 to ET. +- LT sends a 'Start T2' message to ET. +- NT1 sends SIG 0. 1 to LT. +- LT sends a 'Stop T2' message to ET. +- LT sends FE 6 to ET. + +T1816610-92/d55 + +Sequence diagram for deactivation from the network side showing interactions between TE, NT1, LT, and ET. + +FIGURE III.12/G.961 +Deactivation from the network side + +![Sequence diagram showing activation of loopback 2. Lifelines: TE, NT1, LT, ET. Arrows show INFO 0, SIG 0, 1, SIG 0, 2b, SIG 3, 4, SIG 2a, SIG 5, SIG 9, SIG 12, SIG 10, FE 8, FE 2, FE 3, FE 4. Reference point T is at the NT1/LT interface. FE 8 is sent from LT to ET.](301f4a188198a15b1415d54545b07e0d_img.jpg) + +T1816620-92 + +Sequence diagram showing activation of loopback 2. Lifelines: TE, NT1, LT, ET. Arrows show INFO 0, SIG 0, 1, SIG 0, 2b, SIG 3, 4, SIG 2a, SIG 5, SIG 9, SIG 12, SIG 10, FE 8, FE 2, FE 3, FE 4. Reference point T is at the NT1/LT interface. FE 8 is sent from LT to ET. + +FIGURE III.13/G.961 +**Activation of loopback 2** + +TABLE III.3/G.961 + +#### **The repertoire of function elements associated with the activation/deactivation procedures** + +| FEs | Direction | Repertoire | +|-----------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------| +| FE 1 | LT ← ET | Activation request for the line system and the interface at the T reference point | +| FE 2 | LT → ET | Activation initiated indication | +| FE 3 | LT → ET | Line system activated indication | +| FE 4 | LT → ET | T interface or loopback activated indication | +| FE 5 | LT ← ET | Deactivation request for the line system and the interface at the T reference point | +| FE 6 | LT → ET | Line system and T interface deactivated indication | +| FE 7 | LT → ET | Loss of frame alignment (LFA) or malfunction at the line system | +| FE 8 | LT ← ET | Activation request for the loopback 2 | +| FE 9 | LT ← ET | Activation request for the loopback 1 | +| FE 12 | LT → ET | Loss of frame alignment (LFA) at the interface at the T reference point or LFA for the loopbacked signal at the T interface side of the NT1 | +| FE 13
(Note) | LT ← ET | Permission to send INFO 4 towards the interface at the T reference point | + +NOTE – See Note 4 to Table 6/I.430 and 5.3.1.4/G.960. + +### III.10.4 NT1 state transition table + +NT1 state transition table as a function of INFOs and SIGs is defined in Table III.4. + +The following states are used. + +#### NT 1.0 + +Deactivated state (power down state). + +The NT1 is in the power down mode and sends no line signal SIG 0 to the LT and no signal (INFO 0) towards the interface at the T reference point upon receipt of the line system deactivate signal SIG 1 from the LT, and waits for INFO 1 from the interface at the T reference point or the awake signal SIG 3 from the LT. + +#### NT 1.1 + +Activation initiating state for the activation from the user side. + +The NT1 sends the awake signal SIG 2a to the LT upon receipt of INFO 1 from the interface at the T reference point, and waits for the awake acknowledgement signal SIG 3 from the LT. + +#### NT 1.2 + +Line system activating state at the NT1, and also activation initiating state for the activation from the network side. This is also lost framing and reframing state at the NT1 line side. + +The NT1 enters the power up mode upon receipt of SIG 3 (the awake acknowledgement signal in case of activation from the user side, or the awake signal in case of activation from the network side), and waits to synchronize its receiver of the line system to the training signal SIG 4 from the LT. The NT1 continues to send the awake signal SIG 2a to the LT in case of activation from the user side (if the receipt of INFO 1 was recognized in the NT1), or sends the awake acknowledgement signal SIG 2a to the LT in case of activation from the network side. No other signal is transmitted from the NT1. + +#### NT 1.3 + +Line system activated state at the NT1 and line system activating state at the LT. This is also lost framing and reframing state at the LT line side. + +The NT1 enters the line system activated state, and waits for the LT to enter the line system activated state. The NT1 sends training signal SIG 5 to the LT, and waits for the receipt of the line system active indication signal SIG 6 or the loopback 2 operation signal SIG 9 from the LT. + +#### NT 1.4 + +Line system fully activated and T interface activating state, and also T interface lost framing and reframing state. + +Both the NT1 and LT enter the line system activated state, and the NT1 initiates the activation of the interface at the T reference point. The NT1 sends INFO 2 towards the interface at the T reference point and the INFO 2 sending indication signal SIG 14 to the LT upon receipt of the line system active indication signal SIG 6 from the LT, and waits for the receipt of INFO 3 from the interface at the T reference point. + +#### NT 1.5 + +Pending access activation state. + +The NT1 sends the INFO 3 receipt indication signal SIG 8 to the LT upon receipt of INFO 3 from the interface at the T reference point, and waits for the normal operation signal SIG 7 from the LT. This is the waiting state that allows slow TEs to become ready to receive INFO 4. See Note 4 to Table 6/I.430 and 5.3.1.4/G.960. + +TABLE III.4/G.961 + +#### NT1 state transition table + +| State number | | NT 1.0 | NT 1.1 | NT 1.2 | NT 1.3 | NT 1.4 | NT 1.5 | NT 1.6 | NT 1.7 | NT 1.8 | NT 2.1 | NT 2.2 | NT 2.3 | +|------------------------------|----------------|--------------------|--------------------------|--------------------------------------------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------------------------------|---------------------------|--------------------------|---------------------------|-----------------------------------------------------------------------------------|---------------------------|--------------------------| +| State name | | Access deactivated | DTS activation | | | UNI activation | | Access activated | Access deactivation | | Loopback 2 activation | Loopback 2 activated | Loopback 2 deactivating | +| | | | Initiation awaken | Initiated
(or)
Network defect at NT1 | DTS synch
NT1 ← LT
(or)
Network defect at LT | DTS activated
NT1 ← LT
NT1 → LT
.....
UNI activation initiated
TE ← NT1
(or)
LFA at UNI
TE → NT1 | UNI synch
TE ← NT1
TE → NT1 | | UNI deactivating | Pending DTS deactivation | DTS activated
NT1 ← LT
NT1 → LT
.....
Loopback 2 activation initiated | | | +| | | SIG sent | SIG 2b
.....
SIG 0 | SIG 2a
.....
SIG 0 | SIG 2a
.....
SIG 5 | SIG 2a
.....
SIG 14 | SIG 2a
.....
SIG 8 | SIG 2a
.....
SIG 11 | SIG 2a
.....
SIG 8 | SIG 2a
.....
SIG 14 | SIG 2a
.....
SIG 12 | SIG 2a
.....
SIG 10 | SIG 2a
.....
SIG 8 | +| | | INFO sent | INFO 0 | INFO 0 | INFO 0 | INFO 2 | INFO 2 | INFO 4 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | INFO 0 | +| Event | Internal state | G1 | G1 | G1 | G1 | G2 | (Note 1) | G3 | G4 | G4 | G1 | G1 | G1 | +| Receiving INFO 1 | | NT 1.1 | – | – | – | – | / | / | – | – | – | – | – | +| SIG 3 | | NT 1.2 | NT 1.2 | – | – | – | – | – | – | – | – | – | – | +| SIG 4 | | – | – | NT 1.3
(Note 2) | – | NT 1.3 | NT 1.3 | NT 1.3 | NT 1.3 | NT 1.3 | NT 1.3 | NT 1.3 | NT 1.3 | +| DTS synchronized
NT1 ← LT | | / | / | NT 1.3 | – | – | – | – | – | – | – | – | – | +| SIG 6 | | / | / | / | NT 1.4 | – | – | NT 1.5 | /
(Note 3) | /
(Note 3) | /
(Note 4) | /
(Note 4) | /
(Note 4) | +| Receiving INFO 3 | | / | / | / | / | NT 1.5 | – | – | – | – | / | / | / | +| SIG 7 | | / | / | / | / | – | NT 1.6 | – | /
(Note 3) | /
(Note 3) | /
(Note 4) | /
(Note 4) | /
(Note 4) | +| SIG 1 | | – | – | NT 1.0 | NT 1.0 | NT 1.0 | NT 1.0 | NT 1.0 | NT 1.0 | NT 1.0 | NT 1.0 | NT 1.0 | NT 1.0 | +| SIG 13 | | / | / | / | NT 1.8 | NT 1.8 | NT 1.7 | NT 1.7 | – | – | /
(Note 5) | /
(Note 5) | /
(Note 5) | +| SIG 9 | | / | / | / | NT 2.1 | /
(Note 6) | /
(Note 6) | /
(Note 6) | /
(Note 6) | /
(Note 6) | – | – | NT 2.1 | + +| | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--------|---|--------|--------|-----------------|-----------------|-----------------|--------|--------|--------|--------| +| Loopback 2 activated in NT1 (Note 7) | / | / | / | / | / | / | / | / | / | NT 2.2 | – | / | +| SIG 15 | / | / | / | | | | | | – | NT 1.8 | NT 2.3 | – | +| Loopback 2 deactive in NT1 (Note 8) | / | / | / | / | / | / | / | / | / | – | NT 2.1 | NT 1.8 | +| Receiving INFO 0 | – | NT 1.0 | – | – | – | NT 1.4 (Note 9) | NT 1.4 (Note 9) | NT 1.8 (Note 9) | – | – | – | – | +| LFA at UNI
TE → NT1 | / | / | / | / | – | NT 1.4 | NT 1.4 | NT 1.8 | – | – | – | – | +| SIG 0 (Note 10) | – | – | – | NT 1.2 | NT 1.2 | NT 1.2 | NT 1.2 | NT 1.2 | NT 1.2 | NT 1.2 | NT 1.2 | NT 1.2 | +| LFA at DTS
NT1 ← LT | / | / | – | NT 1.2 | NT 1.2 | NT 1.2 | NT 1.2 | NT 1.2 | NT 1.2 | NT 1.2 | NT 1.2 | NT 1.2 | +| – No change, no action
Impossible by the definition of the layer 1 service
/ Impossible situation
NOTES
1 Transition state from G2 to G3, see Note 4 to Table 6/I.430.
2 Detection of SIG 4 is identical to the event “DTS synchronized in direction LT–NT1” in this case.
3 If this signal is detected, change to NT 1.4 when AR = “1”, and no state change when AR = “0”.
4 If this signal is detected, change to NT 1.4 when AR = “1”, and change state as when SIG 15 is detected when AR = “0”.
5 If this signal is detected, change state as when SIG 15 is detected.
6 If this signal is detected, change to NT 2.1.
7 The NT1 is in the frame alignment state for the loopbacked signal.
8 The NT1 is in the loss of frame alignment state for the loopbacked signal.
9 As an implementation option, this event may be merged in the event “LFA at UNI”.
10 As an implementation option, this event may be merged in the event “LFA at DTS in direction LT-NT1”. | | | | | | | | | | | | | + +#### **NT 1.6** + +T interface activated state. + +The NT1 sends INFO 4 towards the interface at the T reference point and the normal operation signal SIG 11 to the LT upon receipt of the normal operation signal SIG 7 from the LT, and waits for the line system deactivate signal SIG 1 or the T interface deactivate signal SIG 13 from the LT. + +#### **NT 1.7** + +T interface deactivating state. + +The NT1 sends INFO 0 towards the interface at the T reference point and the INFO 3 receipt indication signal SIG 8 to the LT upon receipt of the T interface deactivate signal SIG 13 from the LT and waits for the line system deactivate signal SIG 1 from the LT or the receipt of INFO 0 from the interface at the T reference point. + +#### **NT 1.8** + +Pending line system deactivation state. + +The NT1 sends INFO 0 towards the interface at the T reference point and the T interface deactivated signal SIG 14 (the acknowledgement of SIG 13) to the LT upon receipt of INFO 0 from the interface at the T reference point, and waits for the line system deactivate signal SIG 1 from the LT. + +#### **NT 2.1** + +Line system fully activated and loopback 2 activating state. + +Both the NT1 and LT enter the line system activated state. The NT1 initiates provision of the loopback 2 in the NT1 and sends the loopback 2 activating indication signal SIG 12 to the LT upon receipt of the loopback 2 operation signal SIG 9 from the LT, and waits for loopback 2 establishment in the NT1. + +#### **NT 2.2** + +Loopback 2 activated state. + +The NT1 sends the loopback 2 operation signal SIG 10 to the LT on loopback 2 establishment in the NT1, and waits for the line system deactivate signal SIG 1 or the loopback 2 deactivate signal SIG 15 from the LT. + +#### **NT 2.3** + +Loopback 2 deactivating state + +The NT1 sends the loopback 2 deactivating signal SIG 8 to the LT upon receipt of the loopback 2 deactivate signal SIG 15 from the LT, and waits for the line system deactivate signal SIG 1 from the LT or the loopback 2 deactivation completion in the NT1. + +### **III.10.5 LT state transition table** + +LT state transition table as a function of FEs, SIGs and internal timer T2 is defined in Table III.5. + +The following states are used. + +#### **LT 1.0** + +Deactivated state. + +The LT sends the no line signal SIG 0 and the line system deactivate signal SIG 1 to the NT1, and the line system and the T interface deactivated indication function element FE 6 to the ET upon expiry of timer T2 and waits for the awake signal SIG 2a from the NT1 or the T interface and line system activation request function element FE 1 or the loopback 1/2 activation request function elements FE 9/8 from the ET. + +#### **LT 1.1** + +Line system activation initiated state. + +The LT initiates line system activation by sending the awake signal SIG 3 and the training signal SIG 4 to the NT1 upon receipt of the line system and T interface activation request function element FE 1 from the ET, and waits for the awake acknowledgement signal 2a from the NT1. + +#### **LT 1.2** + +Line system activating state. + +The LT initiates line system activation by sending the awake (acknowledgement) signal SIG 3 and the training signal SIG 4 to the NT1, and the activation initiated indication function element FE 2 to the ET upon receipt of the awake (acknowledgement) signal SIG 2a from the NT1, and waits to synchronize its receiver of the line system to the training signal SIG 5 from the NT1. + +#### **LT 1.3** + +Line system fully activated and T interface activating state. + +The LT sends the line system active indication signal SIG 6 to the NT1, and the line system active indication function element FE 3 to the ET upon synchronizing its receiver of the line system to the training signal SIG 5 from the NT1, and waits for the INFO 3 receipt indication signal SIG 8 from the NT1. + +#### **LT 1.4** + +Pending INFO 4 sending state. + +The LT sends the T interface activated indication function element FE 4 to the ET upon receipt of the INFO 3 receipt indication signal SIG 8 from the NT1, and waits for the INFO 4 sending permission function element FE 13 from the ET. This is the waiting state that allows slow TEs to become ready to receive INFO 4. See Note 4 to Table 6/L.430 and 5.3.1.4/G.960. + +#### **LT 1.5** + +T interface activated state. + +The LT sends the normal operation signal SIG 7 to the NT1 upon receipt of the INFO 4 sending permission function element FE 13 from the ET, and waits for the deactivation request function element FE 5 from the ET. + +#### **LT 1.6** + +Line system and T interface deactivating state. + +The LT sends no line signal SIG 0 and the line system deactivate signal SIG 1 to the NT1 upon receipt of the deactivation request function element FE 5, and waits for expiry of timer T2 in the LT. + +#### **LT 1.7a** + +T interface lost framing and reframing state a). + +The LT sends the line system active indication signal SIG 6 to the NT1 and the T interface LFA indication function element FE 12 to the ET upon receipt of the INFO 2 sending indication signal SIG 14 from the NT1 before the LT enters LT 1.5, and waits for the INFO 3 receipt indication signal SIG 8 from the NT1 or the INFO 4 sending permission function element FE 13. + +#### **LT 1.7b** + +T interface lost framing and reframing state b). + +The LT sends the normal operation signal SIG 7 to the NT1 and the T interface LFA indication function element FE 12 to the ET upon receipt of the INFO 2 sending indication signal SIG 14 from the NT1 after the LT enters LT 1.5, and waits for the normal operation signal SIG 11 from the NT1. + +#### **LT 1.8a** + +Line system lost framing and reframing state. + +The LT sends the training signal SIG 4 to the NT1 and the line system LFA indication function element FE 7 to the ET when its receiver of the line system enters the loss of frame alignment state, or upon receipt of SIG 2b (= disappearance of SIG 2a) under the condition that the activation function element FE 1 has been received, and waits for SIG 2a from the NT1. + +#### **LT 1.8b** + +Line system malfunction state. + +The LT sends the line system deactivate signal SIG 1 to the NT1 and the line system malfunction function element FE 7 to the ET upon receipt of SIG 2b (= disappearance of SIG 2a) under the condition that the activation request function element FE 1 has not been received, and waits for the deactivation request function element FE 5 from the ET. + +#### **LT 2.1** + +Line system activation initiated state. + +The LT initiates line system activation by sending the awake signal SIG 3 and the training signal SIG 4 to the NT1 upon receipt of the loopback 2 activation request function element FE 8 from the ET, and waits for the awake acknowledgement signal 2a from the NT1. + +#### **LT 2.2** + +Line system activating state. + +The LT enters the line system activating state by sending the awake signal SIG 3 and the training signal SIG 4 to the NT1 and issues the activation initiated indication function element FE 2 to the ET upon receipt of the awake acknowledgement signal SIG 2a from the NT1, and waits for synchronization of its receiver of the line system to the training signal SIG 5 from the NT1. + +#### **LT 2.3** + +Line system fully activated and loopback 2 activating state. + +The LT sends the loopback 2 operation signal SIG 9 to the NT1 and the line system active indication function element FE 3 to the ET upon receiver synchronization to the training signal SIG 5 from the NT1, and waits for the loopback 2 operation signal SIG 10 from the NT1. + +#### **LT 2.4** + +Loopback 2 activated state. + +The LT sends the loopback 2 active indication function element FE 4 to the ET upon receipt of the loopback 2 operation signal SIG 10 from the NT1, and waits for the deactivation request function element FE 5 from the ET. + +TABLE III.5/G.961 + +#### LT state transition table + +| State number | | LT 1.0 | LT 1.1 | | LT 1.2 | LT 1.3 | | LT 1.4 | | LT 1.5 | LT 1.6 | LT 1.7a | LT 1.7b | LT 1.8a | LT 1.8b | +|-----------------------------|----------------|--------------------|-----------------------------|-------------------------|-------------------------|---------------------------------------------------------------------------------------|------------------------------------------|--------|--|-------------------------------|----------------------------------|----------------------------------|-------------------------|------------------------------------|-------------------------| +| State name | | Access deactivated | DTS activation (T1 running) | | | UNI activation (T1 running) | | | | Access activated (T1 stopped) | Access deactivation (T2 running) | LFA at UNI TE → NT1 (T1 running) | | Network defect at DTS (T1 running) | | +| | | | Initiated | Activating | | DTS activated
NT1 ← LT
NT1 → LT
.....
UNI activation initiated
TE ← NT | UNI synchronized
TE ← NT1
TE → NT1 | | | | | Before access activated | After access activated | LFA at DTS | Malfunction at DTS | +| | | FE sent | FE 6 | | FE 2 | FE 3 | FE 4 | | | FE 4 | FE 4 | FE 12 | FE 12 | FE 7 | FE 7 | +| | | SIG sent | SIG 1
.....
SIG 0 | SIG 3
.....
SIG 4 | SIG 3
.....
SIG 4 | SIG 3
.....
SIG 6 | SIG 3
.....
SIG 6 | | | SIG 3
.....
SIG 7 | SIG 1
.....
SIG 0 | SIG 3
.....
SIG 6 | SIG 3
.....
SIG 7 | SIG 3
.....
SIG 4 | SIG 1
.....
SIG 0 | +| Event | Internal state | G1 | G1 | G1 | | G2 | (Note 1) | | | G3 | G4 | (Note 1) | G2 | G1 | G1 | +| FE 1 | | LT 1.1 | – | – | – | – | – | | | – | | – | – | – | – | +| SIG 2a | | LT 1.2 | LT 1.2 | – | – | – | – | | | – | – | – | – | LT 1.2 | / | +| SIG 5 | | / | / | LT 1.3 (Note 2) | / | / | / | | | / | / | / | / | / | / | +| DTS synchronized NT1 → LT | | / | / | LT 1.3 | – | – | – | | | – | – | – | – | / | / | +| SIG 8 | | / | / | / | LT 1.4 | – | / | | | – | LT 1.4 | / | / | / | / | +| FE 13 | | | | | | LT 1.5 | – | | | – | – | LT 1.7b | – | – | – | +| SIG 11 | | / | / | / | / | / | / | | | – | – | / | LT 1.5 | / | / | +| FE 5 | | – | LT 1.6 | LT 1.6 | LT 1.6 | LT 1.6 | LT 1.6 | | | LT 1.6 | – | LT 1.6 | LT 1.6 | LT 1.6 | LT 1.6 | +| Expiry of timer T2 (Note 3) | | / | / | / | / | / | / | | | / | LT 1.0 | / | / | / | / | +| FE 8 | | LT 2.1 | | | | | | | | | | | | | | +| SIG 12 | | / | / | / | / | / | / | | | / | – | / | / | / | / | +| SIG 10 | | / | / | / | / | / | / | | | / | – | / | / | / | / | + +TABLE III.5/G.961 (cont.) + +#### LT state transition table + +| State number | | LT 1.0 | LT 1.1 | LT 1.2 | LT 1.3 | LT 1.4 | LT 1.5 | LT 1.6 | LT 1.7a | LT 1.7b | LT 1.8a | LT 1.8b | +|---------------------|----------------|--------------------|-----------------------------|-------------------------|---------------------------------------------------------------------------------------|------------------------------------------|-------------------------------|----------------------------------|----------------------------------|-------------------------|------------------------------------|-------------------------| +| State name | | Access deactivated | DTS activation (T1 running) | | UNI activation (T1 running) | | Access activated (T1 stopped) | Access deactivation (T2 running) | LFA at UNI TE → NT1 (T1 running) | | Network defect at DTS (T1 running) | | +| | | | Initiated | Activating | DTS activated
NT1 ← LT
NT1 → LT
.....
UNI activation initiated
TE ← NT | UNI synchronized
TE ← NT1
TE → NT1 | | | Before access activated | After access activated | LFA at DTS | Malfunction at DTS | +| | | FE sent | FE 6 | | FE 2 | FE 3 | FE 4 | FE 4 | FE 12 | FE 12 | FE 7 | FE 7 | +| | | SIG sent | SIG 1
.....
SIG 0 | SIG 3
.....
SIG 4 | SIG 3
.....
SIG 4 | SIG 3
.....
SIG 6 | SIG 3
.....
SIG 7 | SIG 1
.....
SIG 0 | SIG 3
.....
SIG 6 | SIG 3
.....
SIG 7 | SIG 3
.....
SIG 4 | SIG 1
.....
SIG 0 | +| Event | Internal state | G1 | G1 | G1 | G2 | (Note 1) | G3 | G4 | (Note 1) | G2 | G1 | G1 | +| SIG 14 | | / | / | / | – | LT 1.7a | LT 1.7b | – | – | – | / | / | +| SIG 0 (Note 4) | | – | – | – | LT 1.8a | LT 1.8a | LT 1.8a | – | LT 1.8a | LT 1.8a | – | – | +| LFA at DTS NT1 → LT | | / | / | / | LT 1.8a | LT 1.8a | LT 1.8a | – | LT 1.8a | LT 1.8a | – | – | +| SIG 2b | | – | LT 1.8a | (Note 5) | (Note 5) | (Note 5) | (Note 5) | – | (Note 5) | (Note 5) | (Note 5) | – | + +TABLE III.5/G.961 (cont.) + +#### **LT state transition table** + +| State number | | LT 2.1 | LT 2.2 | LT 2.3 | LT 2.4 | LT 2.5 | LT 2.6 | LT 2.7 | +|------------------------------------------|----------------|--------------------------------|--------------------|------------------------------------------------------------------------------------------------------|-----------------------------------------|----------------------------------------------------|---------------------------------------|-----------------------| +| State name | | DTS activation
(T1 running) | | Loopback 2
activation
(T1 running) | Loopback 2
activated
(T1 stopped) | Loopback 2
defect
in the NT1
(T1 running) | Network defect at DTS
(T1 running) | | +| | | Initiated | Activating | DTS activated
$1 \leftarrow LT$
$NT1 \rightarrow LT$

Loopback 2 activation
initiated | | | LFA at DTS | Malfunction
at DTS | +| | FE sent | FE 6 | FE 2 | FE 3 | FE 4 | FE 12 | FE 7 | FE 7 | +| | SIG sent | SIG 3

SIG 4 | SIG 3

SIG 4 | SIG 3

SIG 9 | SIG 3

SIG 9 | SIG 3

SIG 9 | SIG 3

SIG 4 | SIG 3

SIG 4 | +| | Internal state | G1 | G1 | G1 | G1 | G1 | G1 | G1 | +| Event | | | | | | | | | +| FE 1 | | | | | | | | | +| SIG 2a | | LT 2.2 | – | – | – | – | – | LT 2.2 | +| SIG 5 | | / | LT 2.3
(Note 2) | / | / | / | LT 2.3
(Note 2) | / | +| DTS synchronized
$NT1 \rightarrow LT$ | | / | LT 2.3 | – | – | – | LT 2.3 | / | +| SIG 8 | | / | / | / | / | / | / | / | +| FE 13 | | | | | | | | | +| SIG 11 | | / | / | / | / | / | / | / | +| FE 5 | | LT 1.6 | LT 1.6 | LT 1.6 | LT 1.6 | LT 1.6 | LT 1.6 | LT 1.6 | +| Expiry of timer T2
(Note 3) | | / | / | / | / | / | / | / | +| FE 8 | | – | – | – | – | – | – | – | +| SIG 12 | | / | / | – | LT 2.5 | – | / | / | +| SIG 10 | | / | / | LT 2.4 | – | LT 2.4 | / | / | +| SIG 14 | | / | / | / | / | / | / | / | + +TABLE III.5/G.961 (end) + +#### LT state transition table + +| State number | | LT 2.1 | LT 2.2 | LT 2.3 | LT 2.4 | LT 2.5 | LT 2.6 | LT 2.7 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|--------------------------------|-------------------------|-----------------------------------------------------------------------------------------|-----------------------------------------|----------------------------------------------------|---------------------------------------|-------------------------| +| | State name | DTS activation
(T1 running) | | Loopback 2
activation
(T1 running) | Loopback 2
activated
(T1 stopped) | Loopback 2
defect
in the NT1
(T1 running) | Network defect at DTS
(T1 running) | | +| | | Initiated | Activating | DTS activated
NT1 ← LT
NT1 → LT
.....
Loopback 2
activation
initiated | | | LFA at DTS | Malfunction
at DTS | +| | FE sent | FE 6 | FE 2 | FE 3 | FE 4 | FE 12 | FE 7 | FE 7 | +| | SIG sent | SIG 3
.....
SIG 4 | SIG 3
.....
SIG 4 | SIG 3
.....
SIG 9 | SIG 3
.....
SIG 9 | SIG 3
.....
SIG 9 | SIG 3
.....
SIG 4 | SIG 3
.....
SIG 4 | +| Event | Internal state | G1 | G1 | G1 | G1 | G1 | G1 | G1 | +| SIG 0
(Note 4) | | – | – | LT 2.6 | LT 2.6 | LT 2.6 | – | – | +| LFA at DTS
NT1 → LT | | / | / | LT 2.6 | LT 2.6 | LT 2.6 | – | – | +| SIG 2b | | LT 2.7 | LT 2.7 | LT 2.7 | LT 2.7 | LT 2.7 | LT 2.7 | – | +|

– No change, no action
Impossible by the definition of the layer 1 service
/ Impossible situation
NOTE – No state change if the event occurs in a box defined by “/”.
NOTES
1 Transition state from G2 to G3, see Note 4 to Table 6/1.430.
2 Detection of SIG 5 is identical to the event “DTS synchronized in direction NT1-LT” in this case.
3 As an implementation option, the expiry of the timer may be informed by an additional FE from ET layer 1.
4 As an implementation option, this event may be merged in the event “LFA at DTS in direction NT1-LT”.
5 Change to LT 1.8a when FE 1 has been received after the last receipt of FE 5, otherwise, change to LT 1.8b.

| | | | | | | | | + +#### LT 2.5 + +Loopback 2 defect state. + +The LT sends the loopback 2 defect indication function element FE 12 to the ET upon receipt of the loopback 2 activating signal SIG 12 from the NT1 after the LT entered DS 2.4, and waits for the loopback 2 operation signal SIG 10 from the NT1. + +#### LT 2.6 + +Line system lost framing and reframing state. + +The LT sends the training signal SIG 4 to the NT1 and the line system LFA indication function element FE 7 to the ET when its receiver of the line system enters the loss of frame alignment state, and waits for synchronization of its receiver of the line system to the training signal SIG 5 from the NT1. This state is identical to LT 2.2 except for the function element issued. + +#### LT 2.7 + +Line system malfunction state. + +The LT sends the training signal SIG 4 to the NT1 and the line system malfunction function element FE 7 to the ET upon receipt of SIG 2b (= disappearance of SIG 2a), and waits for SIG 2a from the NT1. + +### III.10.6 Activation times + +The LT and NT1 shall complete the start-up process, including the first powering of the NT1 (where the NT1 is powered from the LT via the local line) and the training of the equalizer and synchronization, within 250 ms normally and 300 ms in the worst-case. Start-up time requirement is apportioned 150 ms to the NT1 and 100 ms to the LT in normal-case, and 150 ms to the NT1 and 150 ms to the LT in the worst-case. These specific values are also applied to the permissible frame alignment recovery times when the system enters the loss of frame alignment state after activated. + +## III.11 Jitter + +To assure the achievement of the jitter requirements of Recommendation I.430, the jitter of the timing signal recovered at the NT1 clock shall not exceed the limits given in 8.3/I.430. + +Jitter tolerance is intended to ensure that the limits of Recommendation I.430 are supported by the jitter limits of the transmission system on local lines. The jitter limits given below must be satisfied regardless of the length of the local line, provided that they are covered by the transmission media characteristics (see 3). The limits must be met regardless of bit patterns in the B-, D- and CL-channels. + +Jitter is specified in terms of unit intervals (UI) of nominal 320 kbaud signal. + +### III.11.1 NT1 input signal jitter tolerance + +The NT1 shall meet the performance objective with wander/jitter at the maximum magnitudes indicated in Figure III.14, for single jitter frequencies in the range of 3 Hz to 80 kHz, superimposed on the test signal source. The NT1 shall also meet the performance objectives with wander per day of up to 1.0 UI peak-to-peak where the maximum rate of change of phase is 1.0 UI/hour. + +![Graph of Peak-to-peak jitter (UI) vs Jitter frequency (Hz). The graph shows a piecewise linear function: a horizontal line at J2 from 0 to F1, a downward sloping line with a 20 dB/decade roll-off from (F1, J2) to (F2, J1), and a horizontal line at J1 from F2 to F3. Dashed lines connect the axes to the graph points.](6eafd5abfb13fb29e6d819d2a1a3f6b2_img.jpg) + +Graph of Peak-to-peak jitter (UI) vs Jitter frequency (Hz). The graph shows a piecewise linear function: a horizontal line at J2 from 0 to F1, a downward sloping line with a 20 dB/decade roll-off from (F1, J2) to (F2, J1), and a horizontal line at J1 from F2 to F3. Dashed lines connect the axes to the graph points. + +$$1 \text{ UI} = \frac{1}{320 \text{ kHz}} = 3.125 \text{ } \mu\text{s}$$ + +| F 1 | F 2 | F 3 | J 1 | J 2 | +|----------------|----------------|----------------|----------------|----------------| +| 3 Hz | 30 Hz | 80 Hz | 0.083 UI | 0.83 UI | + +T1814620-92/d57 + +FIGURE III.14/G.961 +**Minimum tolerable jitter on NT1 impact signal** + +### **III.11.2 NT1 output jitter limitations** + +With the wander/jitter as specified in III.11.1 superimposed on the NT1 input signal, the jitter on the transmitted signal from the NT1 towards the LT shall be equal to or less than 0.083 UI peak-to-peak when measured with a high-pass filter having a 20 dB/decade roll-off below 90 Hz. + +### **III.11.3 LT input signal jitter tolerance** + +The LT shall operate satisfactorily with input signal jitter equal to the maximum permissible NT1 output signal jitter defined in III.11.2. + +### **III.11.4 LT output jitter limitations** + +The output signals from the LT shall not exceed the NT1 input signal jitter tolerance limits defined in III.1.1. + +### **III.11.5 Test conditions for jitter measurements** + +Due to bi-directional transmission on the 2-wire and due to severe intersymbol interference, no well defined signal transitions are available at the NT1 2-wire point. + +Two possible solutions are considered: + +- 1) A test point in the NT1 is provided to measure jitter with an undisturbed signal. +- 2) A standard LT transceiver including an artificial local line is defined as a test instrument. + +## **III.12 Transmitter output characteristics of NT1 and LT** + +The following specifications apply with a load impedance of 110 ohms resistive. + +### III.12.1 Pulse amplitude + +The zero to peak nominal amplitude of the pulse shall be 6 V and the tolerance shall be +20%/-10%. + +### III.12.2 Pulse shape + +The transmitted pulse shape shall meet the shaped rectangular pulse with $6\text{ V} \pm 10\%$ amplitude and $1.56\text{ microsecond} \pm 10\%$ width using a low pass filter having a cut-off frequency of greater than 640 kHz and a roll-off of greater than or equal to 12 dB/octave. The pass-band loss of the filter is assumed to be 0 dB. The resultant pulse shape shall conform to the pulse mask of Figure III.15. + +![Figure III.15/G.961 Transmitter output pulse mask. A diagram showing the upper and lower boundaries for a pulse signal over time.](71b27fa0ca760ce920d8fa6561ced693_img.jpg) + +The diagram illustrates the transmitter output pulse mask with the following key features: + +- Vertical Axis (Amplitude):** Marked at 0%, 5%, 10%, 20%, 25%, 50%, and 100%. +- Horizontal Axis (Time):** Divided into three main segments: 0.78125 μs, 1.5625 μs, and a final segment containing a 1.5625 μs marker. +- Top Timing Markers:** Relative to a 0% and 100% reference line. To the left of 0%: 40%, 10%. To the right of 0%: 40%, 30%, 10%. To the left of 100%: 45%, 35%, 10%. To the right of 100%: 55%, 50%, 10%. +- Pulse Mask Boundaries:** Two solid lines define the upper and lower limits. The pulse rises from 0% at the start of the first time segment, plateaus near 100% between the 0% and 100% reference lines, and then falls, ending with a tail that settles between 5% and 7% amplitude. +- Specific Tolerances:** Vertical arrows indicate tolerances such as 20% and 10% at the 100% level, and 5% and 7% at the tail end. + +Figure III.15/G.961 Transmitter output pulse mask. A diagram showing the upper and lower boundaries for a pulse signal over time. + +T1814630-92/d58 + +FIGURE III.15/G.961 +Transmitter output pulse mask + +### III.12.3 Signal power + +The average power shall be between 14.5 dBm and 17.1 dBm. + +### III.12.4 Power spectrum + +The upper bound of the power spectral density shall be within the template in Figure III.16. + +![Figure III.16/G.961: Upper bound of power spectral density of signal. The graph shows Power spectral density (dBm/Hz) on the y-axis (from -90 to -10) versus Frequency (kHz) on the x-axis (logarithmic scale from 1 to 1000). The power spectral density is constant at -30 dBm/Hz from 1 kHz to 160 kHz. At 160 kHz, it begins to decrease with a slope of 20 dB/decade, reaching approximately -45 dBm/Hz at 1000 kHz.](8aef7252a3c6e5078b68c083fbc8bf3e_img.jpg) + +The graph shows the upper bound of the power spectral density. The y-axis is labeled 'Power spectral density' and 'dBm/Hz', with values from -90 to -10 in increments of 10. The x-axis is labeled 'Frequency' and 'kHz', with values 1, 5, 10, 50, 100, 500, and 1000. A horizontal line is at -30 dBm/Hz from 1 kHz to 160 kHz. At 160 kHz, a vertical dashed line is drawn. From 160 kHz to 1000 kHz, a line with a negative slope is shown, labeled '20 dB/decade'. At 1000 kHz, another vertical dashed line is drawn. The label 'T1816630-92/d59' is in the bottom right corner. + +Figure III.16/G.961: Upper bound of power spectral density of signal. The graph shows Power spectral density (dBm/Hz) on the y-axis (from -90 to -10) versus Frequency (kHz) on the x-axis (logarithmic scale from 1 to 1000). The power spectral density is constant at -30 dBm/Hz from 1 kHz to 160 kHz. At 160 kHz, it begins to decrease with a slope of 20 dB/decade, reaching approximately -45 dBm/Hz at 1000 kHz. + +FIGURE III.16/G.961 +Upper bound of power spectral density of signal + +### III.12.5 Transmitter signal non-linearity + +The deviation between positive and negative pulse heights shall be less than 5%. + +## III.13 Transmitter/receiver termination + +### III.13.1 Impedance + +- 1) The nominal input impedance looking toward the NT1 or LT shall be 110 ohms. +- 2) The nominal output impedance looking toward the NT1 or LT shall be less than 110 ohms when driving pulses, and shall be 110 ohms when not driving pulses. + +### III.13.2 Return loss + +The return loss of the impedance with respect to 110 ohms shall exceed the loss indicated by the template in Figure III.17. + +### III.13.3 Longitudinal conversion loss + +The minimum longitudinal conversion loss shall exceed the loss indicated by the template in Figure III.18. + +![Graph of Return loss (dB) vs Frequency (kHz) for Figure III.17/G.961. The y-axis ranges from -15 to 25 dB. The x-axis is logarithmic from 1 to 1000 kHz. The curve starts at -5 dB at 1 kHz, rises with a 20 dB/decade slope to 15 dB at 10 kHz, stays flat at 15 dB until 160 kHz, and then falls with a 20 dB/decade slope to 0 dB at 1000 kHz.](275e23ab47d6247e41acc8d41cfcafbe_img.jpg) + +Figure III.17/G.961 shows the minimum return loss of impedance. The graph plots Return loss (dB) on the y-axis (from -15 to 25) against Frequency (kHz) on a logarithmic x-axis (from 1 to 1000). The curve starts at -5 dB at 1 kHz, rises with a 20 dB/decade slope to 15 dB at 10 kHz, remains constant at 15 dB until 160 kHz, and then falls with a 20 dB/decade slope to 0 dB at 1000 kHz. + +Graph of Return loss (dB) vs Frequency (kHz) for Figure III.17/G.961. The y-axis ranges from -15 to 25 dB. The x-axis is logarithmic from 1 to 1000 kHz. The curve starts at -5 dB at 1 kHz, rises with a 20 dB/decade slope to 15 dB at 10 kHz, stays flat at 15 dB until 160 kHz, and then falls with a 20 dB/decade slope to 0 dB at 1000 kHz. + +FIGURE III.17/G.961 +Minimum return loss of impedance + +![Graph of Longitudinal conversion loss (dB) vs Frequency (kHz) for Figure III.18/G.961. The y-axis ranges from 0 to 70 dB. The x-axis is logarithmic from 0.01 to 1000 kHz. The curve is 0 dB until 0.05 kHz, jumps to 60 dB, stays flat until 160 kHz, and then falls with a 20 dB/decade slope to 45 dB at 1000 kHz.](a45bada58cb83d0191ed06b2b229d99c_img.jpg) + +Figure III.18/G.961 shows the minimum conversion loss. The graph plots Longitudinal conversion loss (dB) on the y-axis (from 0 to 70) against Frequency (kHz) on a logarithmic x-axis (from 0.01 to 1000). The curve is 0 dB until 0.05 kHz, jumps to 60 dB, remains constant until 160 kHz, and then falls with a 20 dB/decade slope to 45 dB at 1000 kHz. + +Graph of Longitudinal conversion loss (dB) vs Frequency (kHz) for Figure III.18/G.961. The y-axis ranges from 0 to 70 dB. The x-axis is logarithmic from 0.01 to 1000 kHz. The curve is 0 dB until 0.05 kHz, jumps to 60 dB, stays flat until 160 kHz, and then falls with a 20 dB/decade slope to 45 dB at 1000 kHz. + +FIGURE III.18/G.961 +Minimum conversion loss + +# **Annex A** (to Appendix III) + +## **Extension functions and requirements for a line system using a TCM method** + +(This annex does not form an integral part of this Recommendation) + +### **A.III.1 Optional functions supported by the CL-channel** + +Definitions of optional functions handled by the CL-channel are described below. The definitions are based on the bit allocation for the multiframe defined in Figure III.3. + +#### **A.III.1.1 Optional loopback operation functions** + +##### **A.III.1.1.1 Loopback 21 operation function** + +This function directs the NT1 to loopback an individual B-channel towards the network. The individual B-channel loopback can provide per-channel maintenance capabilities without totally disrupting service to the users. This loopback is non-transparent for the loopbacked B-channel. The NT1 sends all "1"s for the loopbacked B-channel bits towards the interface at the T reference point. + +The loopback 21 is controlled and operated by the network by using the code word "H1,H2,H3" allocated in the multiframe transmitted in direction LT-NT1. + +The loopback 21 active indication is informed to the network by the code word "T1,T2,T3" allocated in the multiframe transmitted in direction NT1-LT. + +The code values for the loopback 21 operation request and active indication are given in Table A.III.1. The code word "T1,T2,T3" shall set to the same code value as is detected by the code word "H1,H2,H3" at the NT1. + +##### **A.III.1.1.2 Loopback C operation function** + +This function directs the NT1 to loopback an individual B-channel towards the user. The individual B-channel loopback can provide per-channel maintenance capabilities without totally disrupting service to the users. The NT1 transmits all "1"s for the loopbacked B-channel bits towards the LT before scrambling. + +The loopback C is controlled and operated by the network by using the C1 and C2 bits allocated in the multiframe transmitted in direction LT-NT1. When the NT1 detects C1 = "1", the B1-channel loopback C is commenced in the NT1. When the NT1 detects C2 = "1", the B2-channel loopback C is commenced in the NT1. + +The loopback C active indication is informed to the network by the TC1 and TC2 bits allocated in the multiframe transmitted in direction NT1-LT. The TC1 and TC2 bits shall set to the same values as are detected by the C1 and C2 bits respectively. + +##### **A.III.1.1.3 Definition of CL-channel bit transfer mode for optional loopback control and indication** + +Two possible implementation options are defined. + +- First: A code value of the code word "H1,H2,H3" or "T1,T2,T3" is detected by using each bit value detected and identified on the bit-oriented basis defined in III.8.3.3. +- Second: A code value is detected by using the word value formed by 3 bits ("H1,H2,H3" or "T1,T2,T3") in the same multiframe on a word-by-word basis. Identification is confirmed by detecting identical word value over three consecutive cycles. + +In both options sending mode is continuous, duration of control/information invocation is as long as sending-control/causing-event is identified. + +TABLE A.III.1/G.961 + +###### **Assigned code and function of "H1,H2,H3" and "T1,T2,T3"** + +| "H1,H2,H3" | Function | +|----------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| "0,0,1" | operate D-channel loopback 2 1 (Note 1) | +| "0,1,0" | operate B 2 -channel loopback 2 1 | +| "0,1,1" | operate B 2 - and D-channels loopback 2 1 (Note 1) | +| "1,0,0" | operate B 1 -channel loopback 2 1 | +| "1,0,1" | operate B 1 - and D-channels loopback 2 1 (Note 1) | +| "1,1,0" | operate B 1 - and B 2 -channels loopback 2 1 (Note 2) | +| "1,1,1" | operate loopback 2 (see III.8.3.2.7) | +| "T1,T2,T3" | Function | +| "0,0,1" | D-channel loopback 2 1 active indication | +| "0,1,0" | B 2 -channel loopback 2 1 active indication | +| "0,1,1" | B 2 - and D-channels loopback 2 1 active indication | +| "1,0,0" | B 1 -channel loopback 2 1 active indication | +| "1,0,1" | B 1 - and D-channels loopback 2 1 active indication | +| "1,1,0" | B 1 - and B 2 -channels loopback 2 1 active indication | +| "1,1,1" | loopback 2 active indication (see III.8.3.2.8) | +| NOTES
1 Not defined in Recommendation I.603. The ET may not support this function.
2 Use is a network option. | | + +#### **A.III.1.2 Optional transfer function of spare bits of the T interface** + +The S bit in the fourth frame of the multiframe transmitted in direction LT-NT1 and the Q1, Q2, Q3, Q4 bits in the first and third frames of the multiframe in direction NT1-LT provide the transfer function of the spare bits S (in direction NT1-TE) and Q1, Q2, Q3, Q4 (in direction TE-NT1) defined on the interface at the T reference point. + +The bit rate of the spare bit in direction NT1-TE on the interface at the T reference point (the S bit) is 4 kbit/s, but the line system has a transfer capability of only 100 bit/s. Thus, on the interface at the T reference point, the same bit conveyed by the S bit on the line system is repeated 40 times. + +The bit rate of the spare bits in direction TE-NT1 on the interface at the T reference point (the Q1, Q2, Q3, Q4 bits) is 200 bit/s, but the line system has a transfer capability of only 100 bit/s. Thus, on the line system, every second bit of each Q1, Q2, Q3, Q4 bit on the interface at the T reference point is conveyed. + +# Appendix IV + +# Basic access transmission system using SU32 line code + +(This appendix does not form an integral part of this Recommendation) + +## IV.0 General + +The SU32 standard will support the full duplex, transparent transmission of two 64 kbit/s B-channels and one 16 kbit/s D-channel over symmetric pair cables using echo cancelling techniques. In addition to transparent 2B + D transmission, 5.3 kbit/s capacity is provided for an auxiliary channel supporting data CRC, control, supervisory and maintenance functions. The bit stream is encoded for transmission using a high performance ternary SU32 (substitutional 3B2T) conditional block code, filtered and transmitted to line at a baud rate of 108 kbauds. An orthogonal timing signal is superimposed on the line code for symbol sampling; which does not compromise either the line code efficiency or performance. A unique synchronization word is used to achieve frame synchronization. Fast and reliable activation is ensured by means of a binary handshake procedure, for separate training of canceller and equalizer. + +## IV.1 Line code + +The binary data is encoded into a ternary form using the SU32 line code. This is based on the fixed and unconditional 3B2T line code and modified as follows. Each binary triplet is converted to a ternary duplet and is transmitted unless it is identical to the previously transmitted duplet. If current and previous duplets are identical, then the unused code word "00" is transmitted in its place. The SU32 coding rule is shown in Table IV.1. In this table, the left most bit is the first into the encoder and the left most symbol the first out of the encoder. + +TABLE IV.1/G.961 + +### SU32 coding (substitutional 3B2T) + +| Binary I/P | Ternary O/P | Binary I/P | Ternary O/P | +|------------|-------------|------------|-------------| +| 000 | -- | 100 | 0- | +| 001 | -0 | 101 | +- | +| 010 | -+ | 110 | +0 | +| 011 | 0+ | 111 | ++ | + +### Decoding + +Decoding of the received signal is the inverse of the coding process. + +### Tolerance to line polarity inversion + +The code is symmetric so that inversion of the ternary data results in an inversion of the decoded binary data. Thus polarity correction due to cable inversion can be applied either to scrambled or unscrambled binary data, or to ternary data. Both transmitted and received polarity correction is performed at the NT1. + +## IV.2 Symbol rate + +The symbol rate is determined by the line code, the bit rate of the information stream and the frame structure. The symbol rate is 108 kbauds. + +### IV.2.1 Clock tolerance + +#### IV.2.1.1 NT1 free running clock accuracy + +The tolerance of the NT free running clock shall be $\pm 192$ ppm. + +#### IV.2.1.2 Tolerance of the free running clock in the LT + +The free running clock in the LT will be phase locked to the exchange clock having a frequency tolerance of $\pm 50$ ppm thus permitting operation with any equipment meeting Recommendation G.703. + +## IV.3 Frame structure + +There are two states of operation of the transmission system, steady state and training state. The frame structure covered in this subclause is for the steady state (information transfer). + +The B1-, B2-, D- and $C_L$ -channels map directly from binary bits through the scrambler into the ternary frame structure. The SU32 code table is designed to exclude certain uniquely identifiable code sequences, which are exploited for synchronization purposes. + +#### *Multiframe: Multiframe word and location* + +The 12 ms multiframe is identified every sixteenth 3/4 ms frame by replacing the CRC data symbol (No. 79) with a ternary “0”. In all other frames, this symbol is binary valued. This, combined with the frame synchronization word preceding it, uniquely identifies the position of the start of the superframe. + +#### *Multiframe format* + +A multiframe consists of sixteen 81-ternary-symbol 0.75 ms frames. + +| | | | | +|--------------------|------------|-------------------|-----------------------------| +| 6 frames of 2B + D | Frame word | CRC 1 | $C_L$ -channel 1 | +| 6 frames of 2B + D | Frame word | CRC 2 | $C_L$ -channel 2 | +| 6 frames of 2B + D | Frame word | CRC 3 | $C_L$ -channel 3 | +| 6 frames of 2B + D | Frame word | CRC 4 | $C_L$ -channel 4 | +| 6 frames of 2B + D | Frame word | CRC 5 | $C_L$ -channel 5 | +| 6 frames of 2B + D | Frame word | CRC 6 | $C_L$ -channel 6 | +| 6 frames of 2B + D | Frame word | CRC 7 | $C_L$ -channel 7 | +| 6 frames of 2B + D | Frame word | CRC 8 | $C_L$ -channel 8 | +| 6 frames of 2B + D | Frame word | CRC 9 | $C_L$ -channel 1 | +| 6 frames of 2B + D | Frame word | CRC 10 | $C_L$ -channel 2 | +| 6 frames of 2B + D | Frame word | CRC 11 | $C_L$ -channel 3 | +| 6 frames of 2B + D | Frame word | CRC 12 | $C_L$ -channel 4 | +| 6 frames of 2B + D | Frame word | CRC 13 | $C_L$ -channel 5 | +| 6 frames of 2B + D | Frame word | CRC 14 | $C_L$ -channel 6 | +| 6 frames of 2B + D | Frame word | CRC 15 | $C_L$ -channel 7 | +| 6 frames of 2B + D | Frame word | “0” | $C_L$ -channel 8 | + +1 ..... 72, 73 . . . 78 . . . 79 . . . 80 ..... 81 + +<----- 750 $\mu$ sec transmission frame -----> + +#### 12 ms multiframe structure + +NOTE - B1-, B2-, D- and $C_L$ -channel data is scrambled. CRC data and frame words are not scrambled. + +### IV.3.1 Frame length + +There are six (2B + D) slots in each 3/4 ms 81 symbol frame. + +### IV.3.2 Binary bit allocation in direction LT to NT + +The following binary bit ordering is applied before scrambling. + +| | | | | | | | | | | | | | | | | | | | +|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|----------------|----------------| +| B1 1 | B1 2 | B1 3 | B1 4 | B1 4 | B1 5 | B1 6 | B1 7 | B1 8 | B2 1 | B2 2 | B2 3 | B2 4 | B2 5 | B2 6 | B2 7 | B2 8 | D 1 | D 2 | +| B1 1 | B1 2 | B1 3 | B1 4 | B1 4 | B1 5 | B1 6 | B1 7 | B1 8 | B2 1 | B2 2 | B2 3 | B2 4 | B2 5 | B2 6 | B2 7 | B2 8 | D 1 | D 2 | +| B1 1 | B1 2 | B1 3 | B1 4 | B1 4 | B1 5 | B1 6 | B1 7 | B1 8 | B2 1 | B2 2 | B2 3 | B2 4 | B2 5 | B2 6 | B2 7 | B2 8 | D 1 | D 2 | +| B1 1 | B1 2 | B1 3 | B1 4 | B1 4 | B1 5 | B1 6 | B1 7 | B1 8 | B2 1 | B2 2 | B2 3 | B2 4 | B2 5 | B2 6 | B2 7 | B2 8 | D 1 | D 2 | +| B1 1 | B1 2 | B1 3 | B1 4 | B1 4 | B1 5 | B1 6 | B1 7 | B1 8 | B2 1 | B2 2 | B2 3 | B2 4 | B2 5 | B2 6 | B2 7 | B2 8 | D 1 | D 2 | +| B1 1 | B1 2 | B1 3 | B1 4 | B1 4 | B1 5 | B1 6 | B1 7 | B1 8 | B2 1 | B2 2 | B2 3 | B2 4 | B2 5 | B2 6 | B2 7 | B2 8 | D 1 | D 2 | +| C L1 | C L2 | C L3 | | | | | | | | | | | | | | | | | + +The binary data is scrambled as defined in IV.9 and ternary encoded. It is then multiplexed into the following frame format. + +| | | | | | | | | | | | | +|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| T 1 | T 2 | T 3 | T 4 | T 5 | T 6 | T 7 | T 8 | T 9 | T 10 | T 11 | T 12 | +| T 13 | T 14 | T 15 | T 16 | T 17 | T 18 | T 19 | T 20 | T 21 | T 22 | T 23 | T 24 | +| T 25 | T 26 | T 27 | T 28 | T 29 | T 30 | T 31 | T 32 | T 33 | T 34 | T 35 | T 36 | +| T 37 | T 38 | T 39 | T 40 | T 41 | T 42 | T 43 | T 44 | T 45 | T 46 | T 47 | T 48 | +| T 49 | T 50 | T 51 | T 52 | T 53 | T 54 | T 55 | T 56 | T 57 | T 58 | T 59 | T 60 | +| T 61 | T 62 | T 63 | T 64 | T 65 | T 66 | T 67 | T 68 | T 69 | T 70 | T 71 | T 72 | +| 0 | 0 | 0 | 0 | 0 | 0 | CRC | T 73 | T 74 | | | | + +### IV.3.3 Binary bit allocation in direction NT1 to LT + +The frame structure and order of bits in the NT1 to LT direction is identical to that used in the LT to NT1 direction specified in IV.3.2. + +## IV.4 Frame word + +The frame word of six ternary zeros terminated by the binary CRC15 bit (as illustrated in the above frame format) is used to define the 0.75 ms frame boundaries. Note that once every superframe, a ternary zero is substituted for the binary CRC check bit. The frame word is unique and cannot be emulated by any 2B + D data pattern. + +The frame word specified above is the same in both directions of transmission. + +## IV.5 Frame alignment procedure + +The frame alignment function is specified in the activation sequence. 2B + D transmission cannot commence unless frame alignment has been achieved. Initial frame alignment is considered to have been achieved when the cumulative total of correct versus incorrectly received 7-bit frame words exceeds four. In steady state operation, this cumulative count is maintained but limited to a maximum of 64. Frame alignment loss is flagged if this cumulative total falls below two. + +## IV.6 Multiframe + +The multiframe structure has been described in the frame structure of IV.3. + +## IV.7 Frame offset between LT-NT1 and NT1-LT frames + +No specific phase requirements are necessary between frames in the LT-NT1 and NT1-LT directions. + +## IV.8 CL-channel + +An embedded protected operations channel (EPOC) of 4 kbit/s is partially allocated to supervisory and maintenance functions. Significant spare capacity and undefined bits remain for both future allocation of messages as well as specific national requirements. + +This channel is protected by a 6-bit CRC check and compelled protocol which provides that all messages are repeated every 6 ms. + +### IV.8.1 Bit rate + +Twenty-four bits per 6 ms multiframe (4 kbit/s) are allocated to an embedded protected operations channel (EPOC). This supports supervisory and maintenance functions between the network and the NT1 and includes spare capacity for user-defined functions. Additionally, a further 1.33 kbit/s is allocated to provide an error detecting CRC15 and 12 ms framing to the CL-channel. + +### IV.8.2 Structure + +Within each 12 frame, the operations channel sends two consecutive messages of 24 bits. Each 24-bit message comprises: + +- 1 bit Ready for data/data valid (R); +- 5 bits Maintenance channel (M); +- 9 bits Supervisory channel (S); +- 3 bits Unassigned bits (500 bit/s subsidiary channel); +- 6 bits Cyclic redundancy check field (CRC). + +The structure of the CL-channel is as follows: + +![Diagram of the C_L-channel structure showing 24 bits (00-24) over a 6 ms period. Bit 00 is Subsidiary, 01 is Ready (R), 02-06 are Maintenance (M), 07-15 are Supervisory (S), and 16-24 are CRC.](92680434cb39f8b185a9326048e754bb_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|----------|----|-----------------|----|----|-----------------|----|----|----|----|----|-----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | +| Subsid. | R | Maintenance (M) | | | Supervisory (S) | | | | | | CRC | | | | | | | | | | | | | | +| ← 6 ms → | | | | | | | | | | | | | | | | | | | | | | | | | + +Diagram of the C\_L-channel structure showing 24 bits (00-24) over a 6 ms period. Bit 00 is Subsidiary, 01 is Ready (R), 02-06 are Maintenance (M), 07-15 are Supervisory (S), and 16-24 are CRC. + +#### IV.8.2.1 Maintenance messages + +In the ET to NT1 direction 9 of the 32 possible command messages are allocated. An identical message is returned in the NT1 to ET direction as an acknowledgement. + +| ET to NT1 maintenance message codes | | | | | | | +|-------------------------------------|---------------------------------------------------------------------|----------------|----------------|----------------|----------------|----------------| +| No. | Message | 5-bit code | | | | | +| | | M 1 | M 2 | M 3 | M 4 | M 5 | +| 1 | No loopback (null message)/remove loopback | 1 | 1 | 1 | 1 | 1 | +| 2 | Provide loopback B 1 at NT1 | 1 | 1 | 0 | 1 | 1 | +| 3 | Provide loopback B 2 at NT1 | 1 | 0 | 1 | 1 | 1 | +| 4 | Provide loopback B 1 + B 2 at NT1 | 1 | 0 | 0 | 1 | 1 | +| 5 | Provide loopback B 1 + B 2 + D at NT1 | 1 | 0 | 0 | 0 | 1 | +| 6 | Provide loopback B 1 at regenerator | 0 | 0 | 1 | 1 | 1 | +| 7 | Provide loopback B 2 at regenerator | 0 | 1 | 0 | 1 | 1 | +| 8 | Provide loopback B 1 + B 2 at regenerator | 0 | 1 | 1 | 1 | 1 | +| 9 | Provide loopback B 1 + B 2 + D at regenerator | 0 | 1 | 1 | 0 | 1 | + +##### *Supervisory sub-channel message formats* + +A 9-bit field is available in each direction of transmission to allow supervisory information to be provided. This contains an 8-bit data/address field and a one-bit flag used to indicate whether or not the 8-bit field contains valid data. + +| ET to NT1 supervisory message command codes | | | +|---------------------------------------------|-------------------------------------------|-------------| +| No. | Supervisory message and destination | S-interface | +| 1 | No supervisory information requested | 1 1111 1111 | +| 2 | ET AGC value | 0 0000 0100 | +| 3 | ET eye closure | 0 0000 0101 | +| 4 | ET eye height | 0 0000 0110 | +| 5 | ET CRC error count | 0 0000 0111 | +| 6 | NT1 AGC value | 0 0001 0000 | +| 7 | NT1 eye closure | 0 0001 0001 | +| 8 | NT1 eye height | 0 0001 0010 | +| 9 | NT1 CRC error count | 0 0001 0011 | +| 11 | Regenerator LT-side receiver AGC | 0 0000 1000 | +| 12 | Regenerator LT-side receiver eye closure | 0 0000 1001 | +| 13 | Regenerator LT-side receiver eye height | 0 0000 1010 | +| 14 | Regenerator LT-side receiver CRC count | 0 0000 1011 | +| 15 | Regenerator NT1-side receiver AGC | 0 0000 1100 | +| 16 | Regenerator NT1-side receiver eye closure | 0 0000 1101 | +| 17 | Regenerator NT1-side receiver eye height | 0 0000 1110 | +| 18 | Regenerator NT1-side CRC count | 0 0000 1111 | + +### IV.8.3 Protocols and procedures + +The maintenance channel is used to set loop backs from the LT. When a maintenance message has been received free from error and implemented, the same message is echoed back from the NT1 to the LT. + +The supervisory channel is designed to be used as a compelled system, with a command sent by the LT end until the expected response is received. A delimiting idle message of nine ONEs is employed. All valid messages and responses set the first bit of the nine supervisory bits to a ONE. An 8-bit word can therefore be securely passed across this channel. An example use of the supervision channel is for reporting eye closure information from the NT1 to the LT. + +### IV.8.4 CL-channel performing + +With a mean 144 kbit/s error rate of 1 in 1000, characterized by a mean burst size of ten, the following performance will be achieved: + +- a) 99.8% of all messages will be conveyed within 6 ms. +- b) No more than one message per hour shall be conveyed in more than 18 ms. +- c) The mean erroneous error message rate is less than one per hour with a maximum time to correction of 18 ms. + +## IV.9 Scrambling + +B1-, B2-, D- and C-channel binary data is scrambled as follows: + +- a) NT to LT scrambler polynomial + +$$1 \oplus x^{-18} \oplus x^{-23} \text{ (where } \oplus \text{ denotes exclusive OR);}$$ + +- b) LT to NT scrambler polynomial + +$$1 \oplus x^{-5} \oplus x^{-23}$$ + +## IV.10 Activation/deactivation + +### IV.10.1 Signals used for activation + +Figure IV.1 illustrates the activation sequence initiated by the ET in terms of function elements (FE) and INFOs. + +Figure IV.2 illustrates the activation sequence initiated by the user in terms of function elements (FE) and INFOs. + +![](f431b5db0c635c95318cff1adbe10c05_img.jpg) + +| TE | T | NT1 | LT | V 1 | ET Layer 1 | +|-----------------|---|-------------------------------|----------------------|----------------|--------------------| +| INFO 0 | | INFO 0 | READY FOR ACTIVATION | | ACTIVATE (PH - AR) | +| | | | Detect FE1 | | FE1 | +| | | Detect activation | Activation sequence | | | +| | | In-synch. | | | | +| | | Return sync. frames | In synch. | | | +| Detect INFO 2 | | Transmit INFO 2 | Send FE3 | | Receive FE3 | +| Transmit INFO 3 | | Detect INFO 3 | | | MPH - DSAI | +| | | Transmit ready for data (RFD) | Detect RFD | | | +| | | | Send FE4 (PH - AI) | | Receive FE4 | +| | | | | | PH/MPH - AI | +| | | | Detect data valid | | Send data valid | +| | | Detect data valid | Send data valid | | | +| Detect INFO 4 | | Transmit INFO 4 | | | | +| INFO 3 | | | | | | + +T1820330-93/d62 + +FIGURE IV.1/G.961 +**Activation from the network side** + +![Sequence diagram showing activation from the user side across five lifelines: TE, T, NT1, LT, and ET Layer 1. The process involves INFO 0, ACTIVATE, and various frame transmissions and detections between the entities.](4ef412e08808c40e0beb7808d36b9379_img.jpg) + +``` + +sequenceDiagram + participant TE + participant T + participant NT1 + participant LT + participant ET_Layer_1 as ET Layer 1 + + Note right of TE: INFO 0 + Note right of TE: ACTIVATE + TE->>NT1: Transmit INFO 1 + Note right of NT1: INFO 0 + NT1->>NT1: Detect INFO 1 + NT1->>LT: Send wake-up + Note right of LT: READY FOR ACTIVATION + LT->>LT: Detect wake-up + LT->>ET_Layer_1: Send FE2 (line signal detect) + ET_Layer_1->>LT: Receive FE2 (MPH – AWI) + LT->>LT: Detect FE1 + ET_Layer_1->>LT: FE1 + NT1->>LT: In-synch. + LT->>NT1: Send activation sequence + NT1->>NT1: In synch. + NT1->>LT: Return synch. frames + LT->>NT1: In synch. + NT1->>TE: Transmit INFO 2 + TE->>NT1: Detect INFO 2 + NT1->>NT1: Detect INFO 3 + TE->>NT1: Transmit INFO 3 + NT1->>TE: Transmit ready for data (RFD) + LT->>NT1: Detect RFD + LT->>ET_Layer_1: Send FE4 + ET_Layer_1->>LT: Receive FE4 + Note right of ET_Layer_1: MPH – DSAI + Note right of ET_Layer_1: PH/MPH – AI + LT->>LT: Detect data valid + LT->>NT1: Send data valid + NT1->>NT1: Detect data valid + NT1->>TE: Transmit INFO 4 + TE->>NT1: Detect INFO 4 + Note right of TE: INFO 3 + +``` + +Sequence diagram showing activation from the user side across five lifelines: TE, T, NT1, LT, and ET Layer 1. The process involves INFO 0, ACTIVATE, and various frame transmissions and detections between the entities. + +T1820340-93/d63 + +FIGURE IV.2/G.961 +Activation from the user side + +The definition of the function elements, LT states and NT states used in the activation figures and the state transition tables in this appendix is as follows. + +| Definition of FE's LT's and NT's | | +|----------------------------------|-------------------------------------------------------------------------------------------------------------------------| +| | Function elements (FE) | +| FE1 | Activation request for the interface from the ET. | +| FE2 | Line signal detected on the digital section. | +| FE3 | The digital section is activated (in synchronization). | +| FE4 | The user network at the T reference point is activated or a loopback is operated. | +| FE5 | Deactivation request for the digital section. | +| FE6 | The digital section and the interface at the T reference point has been deactivated. | +| FE7 | Error indication. (Loss of synchronization or no line signal detect). | +| | NT1 states | +| NT1 | The NT1 is ready for activation. | +| NT2 | The NT1 is executing the digital section training sequence. | +| NT3 | The NT1 is in synchronization with the LT and the LT to NT1 digital section is capable of error free data transmission. | +| NT4 | Equivalent to state NT3 plus synchronization of the interface at the T reference point. | +| NT5 | The 2B + D data channel through the digital section and across the T reference point is fully operational. | +| NT6 | The NT1 has sent an activate request to the LT and is waiting for a response. | +| NT7 | The NT1 is not active but is not ready for activation. | +| | LT states | +| LT1 | The LT is ready for activation. | +| LT2 | The LT is executing the digital section training sequence. | +| LT3 | The digital section has been correctly activated and is synchronized in both directions. | +| LT4 | Both the digital section and the interface at the T reference point are correctly activated and synchronized. | +| LT5 | The 2B + D data channel through the digital section and across the T reference point is fully operational. | +| LT7 | The LT has ceased transmission over the digital section and is waiting for all line signals to disappear. | + +The response of the digital section to the activation request FE1 from the ET or the activation request INFO 1 from the TE is to signal across the digital section by the transmission of a quarter baud rate (27 kHz) wake-up tone. + +In the NT1 to LT direction, the duration of this wake-up tone shall not be less than 32 complete cycles of the repetitive data pattern +--+. The tone shall not exceed 10 ms in duration. + +In the LT to NT1 direction, the duration of the wake-up tone shall not be less than 32 complete cycles of the repetitive data pattern +--+. The tone shall not exceed 10 ms in duration. + +**IV.10.2 Definition of internal timers:** The activation procedure shall nominally take 120 ms to the point where error free framed transmission can commence. + +In the event of the activation procedure failing, or loss of synchronization on either the interface at the T reference point or on the transmission system described herein, a timer is required in the NT to terminate operation. This time shall not exceed 65 ms measured from the point of loss of synchronization; or in the case of activation, measured from the time at which synchronization should be achieved. + +It is not essential to employ a timer for the identification of failure to activate or loss of synchronization signalled to the LT. However, where there is no external control of the deactivation procedure applied to the two wire LT termination, a timer not exceeding 65 ms from the time of loss of synchronization or as measured from the time at which activation should have been achieved should be employed. + +### IV.10.3 Activation procedure + +Table IV.2 shows the training sequence signals that should be transmitted to line by the LT and NT1. At the LT, offsets are measured in baud periods from the end of the wake-up tone transmission. At the NT1, offsets are measured in baud periods from the detection of the end of the wake-up tone. For correct operation, it is necessary that the time from the LT completing the wake-up tone burst, to the NT1 detecting the end of wake-up tone is less than or equal to 32 bauds. + +The conditional step between the NT1 acquiring synchronization and returning ternary data is included to provide a mechanism by which the optional alignment of LT to NT1 and NT1 to LT frame words can be achieved. + +TABLE IV.2/G.961 + +#### Activation training sequence + +| Offset (bauds) | Duration (bauds) | LT timing signal | LT data | NT timing signal | NT data | +|--------------------|-------------------|------------------|---------------------|------------------|---------------------| +| 0 | 64 | OFF | None | OFF | None | +| 64 | 512 | ON | None | OFF | None | +| 576 | 512 | OFF | None | ON | None | +| 1 088 | 512 | ON | None | OFF | None | +| 1 600 | 512 | OFF | None | ON | None | +| 2 112 | 4096 | ON | PRBS | OFF | None | +| 6 208 | 32 | ON | None | OFF | None | +| 6 240 | 4064 | ON | None | OFF | PRBS | +| 10 304 | (405)
(Note 1) | ON | Ternary
(Note 1) | OFF | None | +| 10 709
(Note 1) | (405)
(Note 2) | ON | Ternary
(Note 2) | OFF | Ternary
(Note 2) | + +PRBS stands for a 511-bit pseudo-random binary sequence generated by the polynomial $(1 \oplus x^{-4} \oplus x^{-9})$ . + +##### NOTES + +1 The transmission of ternary data from the LT to the NT1 from this time onwards is continuous. The NT1 will not return ternary data until it has achieved synchronization, the figure of 405 bauds and the subsequent offset to the next row is intended as a guide to the normal duration for this process. + +2 Ternary transmission from NT1 to LT implies that error-free transmission and frame synchronization have been achieved in the NT. Following the LT acquiring synchronization, full duplex 2B + D transmission can commence + +### IV.10.4 State transition table of the NT + +See Table IV.3. + +TABLE IV.3/G.961 + +#### State transition of the NT + +| State | | NT1
Ready for
activation | NT2 Training | NT3
Wait for T | NT4
Wait for
data valid | NT5
Steady state | NT6
TE activation | NT7
Pending
deactivation | +|--------------------------------|----------------------------------|--------------------------------|--------------|-------------------|-------------------------------|---------------------|----------------------|--------------------------------| +| Signal
transmitted
to TE | | I0 | I0 | I2 | I2 | I4 | I0 | | +| Events | | | | | | | | | +| Source | Event | | | | | | | | +| LT | Activate
indication [FE1] | NT2 | – | – | – | – | NT2 | – | +| NT1 | In synch. [FE3] | / | NT3 | – | – | – | / | – | +| TE | INFO 3 | / | / | NT4 | – | – | / | – | +| NT1 | Data valid | / | / | / | NT5 | – | / | – | +| TE | Activate
indication
INFO 1 | NT6 | / | / | / | / | / | – | +| NT1 | Loss of synch.
[FE3] | – | NT7 | NT7 | NT7 | NT7 | – | – | +| NT1 | No line signal
detect on DS | – | – | – | – | – | – | NT1 | + +– No change +/ Impossible +[] Remote source event +DS Digital system + +### IV.10.5 State transition table of the LT + +See Table IV.4. + +TABLE IV.4/G.961 + +State transition table of the LT + +| State | LT1
Ready for
activation | LT2
Training | LT3
Dig. sect.
active | LT4
T-ref in
synch. | LT5
Steady state | | LT7
Pending
deact. | +|----------------------------------------------------------------------------------|--------------------------------|-----------------|-----------------------------|---------------------------|---------------------|------------|--------------------------| +| | Signal
transmitted
to DS | Inactive | Training
sequence | Steady
state | Steady
state | | Inactive | +| Events | | | | | | | | +| Source Event
ET FE1
(Activate request) | | LT2 | / | / | / | / | – | +| LT DS
in-synch. | | / | FE3
LT3 | – | – | – | / | +| LT FE2
No line activity
LSD → False | | / | – | – | – | – | LT1 | +| NT1 [INFO 3]
Ready for data | | / | / | FE4
LT4 | – | – | / | +| LT
DS loss of
synchronization | | / | FE7
LT7 | FE7
LT7 | FE7
LT7 | FE7
LT7 | – | +| ET FE5
Deactivation request | | / | FE7
LT7 | FE7
LT7 | FE7
LT7 | FE7
LT7 | – | +| ET
Data valid | | / | / | / | LT5 | – | – | +| – No change
/ Impossible
[ ] Remote source event
LSD Line signal detect | | | | | | | | + +### IV.10.6 Activation times + +The “cold-start” and “warm-start” times will be 120 ms ± 10 ms with all cable combinations permissible. This reliable and repeatable activation time is a result of the specific activation sequence specified in this SU32 standard. + +## IV.11 Jitter + +Jitter performance must be sufficient for the purpose of providing the clock for interface at the T reference point transmission function in accordance with Recommendation I.430. + +The SU32 proposal features an orthogonal timing signal superimposed on the data. This leads to stable and low jitter digital phase locked loop timing circuitry being easily achieved. + +### IV.11.1 to IV.11.3 + +For further study. + +## IV.12 Transmitter output characteristic of the NT or LT + +### IV.12.1 Pulse amplitude + +The nominal pulse amplitude shall be zero to peak 1.8 volts. The tolerance on this peak pulse amplitude shall be such that signal power and amplitude versus frequency spectrum performance is as specified in IV.12. + +### IV.12.2 Pulse shape + +The pulse shape is determined by the pulse mask of Figure IV.3. + +![Figure IV.3/G.961: Single pulse mask – 108 kbauds transmitter pulse shaping. The graph shows the amplitude relative to peak pulse height (%) versus time t (symbol periods). The pulse rises from 0% at -0.7T to 100% at -0.3T, stays at 100% until +0.3T, and then falls back to 0% at 0.7T. The mask is defined by shaded regions representing upper and lower bounds. The y-axis ranges from -30% to 100% with major ticks every 20%. The x-axis ranges from -1.5T to 16T with major ticks every 0.2T. A text box specifies T = 1 / 108 kHz = 9.259259 μs, Amplitude relative to peak pulse height V100% to give +10 dBm across 140 Ω, and Time t = 0 at peak of pulse.](caa75c3f07d6318059c4802105a104d7_img.jpg) + +Amplitude relative to peak pulse height + +$T = \frac{1}{108 \text{ kHz}} = 9.259259 \mu\text{s}$ + +Amplitude relative to peak pulse height + $V_{100\%}$ to give +10 dBm across $140 \Omega$ +Time $t = 0$ at peak of pulse + +Time $t$ (symbol periods) + +T1820350-93/d64 + +Figure IV.3/G.961: Single pulse mask – 108 kbauds transmitter pulse shaping. The graph shows the amplitude relative to peak pulse height (%) versus time t (symbol periods). The pulse rises from 0% at -0.7T to 100% at -0.3T, stays at 100% until +0.3T, and then falls back to 0% at 0.7T. The mask is defined by shaded regions representing upper and lower bounds. The y-axis ranges from -30% to 100% with major ticks every 20%. The x-axis ranges from -1.5T to 16T with major ticks every 0.2T. A text box specifies T = 1 / 108 kHz = 9.259259 μs, Amplitude relative to peak pulse height V100% to give +10 dBm across 140 Ω, and Time t = 0 at peak of pulse. + +FIGURE IV.3/G.961 +Single pulse mask – 108 kbauds transmitter pulse shaping + +### IV.12.4 Power spectrum + +SU32 has a code spectrum modified by the conditional code rule compared to random ternary signalling. The theoretical power spectrum when using SU32 having full width rectangular pulse shaping with transformer coupling is given in Figure IV.4. + +Limits for the transmitted power spectral density are given in Figure IV.5. + +#### *Power levels* + +Signals sent to line must conform to the following criteria, under all operating conditions with 140 ohms resistive termination: + +- a) The maximum total transmit power, averaged in any 1 second period must not exceed +11 dBm. +- b) The maximum transmit power average in any 1 second period in any 3 kHz band, below 100 kHz, must be less than 0 dBm. This limit extends down to DC (excluding power feed). +- c) The nominal recommended transmit power will be +9.5 dBm with a tolerance of $\pm 1$ dB. + +![Graph of Power spectral density (pW/Hz) vs Frequency (kHz) for SU32 line code. The curve starts at 40 pW/Hz at 0 kHz, rises to a peak of approximately 51 pW/Hz at 25 kHz, and then declines to 30 pW/Hz at 100 kHz.](8d8015c25a486fa5e809961823c33437_img.jpg) + +Conditions: 10mW transmit power +Transformer coupling assumed +Full width rectangular pulses + +| Frequency (kHz) | Power spectral density (pW/Hz) | +|-----------------|--------------------------------| +| 0 | 40 | +| 10 | 49 | +| 20 | 50.5 | +| 25 | 51 | +| 30 | 50 | +| 40 | 48 | +| 50 | 45 | +| 60 | 43 | +| 70 | 41 | +| 80 | 38 | +| 90 | 34 | +| 100 | 30 | + +T1820360-93/d65 + +Graph of Power spectral density (pW/Hz) vs Frequency (kHz) for SU32 line code. The curve starts at 40 pW/Hz at 0 kHz, rises to a peak of approximately 51 pW/Hz at 25 kHz, and then declines to 30 pW/Hz at 100 kHz. + +FIGURE IV.4/G.961 +On line power spectral density of SU32 line code + +![Figure IV.5/G.961: Transmitted power spectral density specification. The graph plots power spectral density in dBm/3 kHz on the y-axis (from -80 to +20) against frequency in Hz on a logarithmic x-axis (from 1 kHz to 10 MHz). The specification is shown as a shaded region. The upper boundary of the shaded region is 0 dBm/3 kHz from 1 kHz to 100 kHz, then decreases linearly to -60 dBm/3 kHz at 1 MHz, and remains constant at -60 dBm/3 kHz up to 10 MHz.](f1cce5478f5773de5432c5fd3d2c4a62_img.jpg) + +| Frequency (Hz) | PSD (dBm/3 kHz) | +|----------------|-----------------| +| 1 kHz | 0 | +| 100 kHz | 0 | +| 1 MHz | -60 | +| 10 MHz | -60 | + +Figure IV.5/G.961: Transmitted power spectral density specification. The graph plots power spectral density in dBm/3 kHz on the y-axis (from -80 to +20) against frequency in Hz on a logarithmic x-axis (from 1 kHz to 10 MHz). The specification is shown as a shaded region. The upper boundary of the shaded region is 0 dBm/3 kHz from 1 kHz to 100 kHz, then decreases linearly to -60 dBm/3 kHz at 1 MHz, and remains constant at -60 dBm/3 kHz up to 10 MHz. + +T1820370-93/d66 + +FIGURE IV.5/G.961 +**Transmitted power spectral density specification** + +## IV.13 Transmitter/receiver termination + +### IV.13.1 Impedance + +The nominal output/input impedance looking towards the NT shall be 140 ohms. The nominal output/input impedance looking towards the LT shall be 140 ohms. + +### IV.13.2 Return loss + +For further study. + +### IV.13.3 Longitudinal conversion loss + +The longitudinal conversion loss in the range 100 Hz to 1.6 times the symbol rate ( $f_0$ ) shall exceed 46 dB. For a frequency $10 \text{ MHz} > f > 1.6 f_0$ , the longitudinal loss shall exceed $46 - 40 \log (f/1.6 f_0)$ dB or 24 dB whichever is greater. \ No newline at end of file diff --git a/marked/G/T-REC-G.9730.2-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.9730.2-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/G/T-REC-G.9730.2-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.9730.2-202408-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/G/T-REC-G.9730.2-202408-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d39f470950609d19a3b43932c41c9419a90bfad --- /dev/null +++ b/marked/G/T-REC-G.9730.2-202408-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c8441a04efedc2265d725cebade441eccc61e33820693153e3072d94a9bb1a8 +size 113244 diff --git a/marked/G/T-REC-G.9730.2-202408-I_PDF-E/raw.md b/marked/G/T-REC-G.9730.2-202408-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9327ca1552bb1c0856d2f0c58b0317cd76aa9959 --- /dev/null +++ b/marked/G/T-REC-G.9730.2-202408-I_PDF-E/raw.md @@ -0,0 +1,386 @@ + + +# Recommendation**ITU-T G.9730.2 (08/2024)** + +SERIES G: Transmission systems and media, digital systems and networks + +Access networks – Metallic access networks + +--- + +### **Scientific monitoring and reliable telecommunication submarine cable systems** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +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 | +| 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.9730.2 + +## Scientific monitoring and reliable telecommunication submarine cable systems + +## Summary + +Recommendation ITU-T G.9730.2 identifies the capabilities and features of fibre optical submarine telecommunication cable systems equipped with scientific monitoring sensors along the length of the undersea optical cables (i.e., SMART cables). It describes at a high-level the characteristics and requirements of a scientific monitoring and reliable telecommunication (SMART) cable system (e.g., no interference between telecommunications and sensing functions, reliability of each function, operations and maintenance, general attributes of a power and communication interface). + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.9730.2 | 2024-08-29 | 15 | 11.1002/1000/16051 | + +## Keywords + +Ocean observation, optical transmission system, scientific monitoring, SMART, submarine cables. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 SMART submarine cable system description..... | 2 | +| 7 System requirements..... | 3 | +| 7.1 Sensors..... | 3 | +| 7.2 Power feeding..... | 5 | +| 7.3 Communication ..... | 5 | +| 7.4 Design life and fault isolation..... | 6 | +| 7.5 Maintenance ..... | 6 | +| 7.6 Environmental requirements ..... | 6 | +| 7.7 Mechanical requirements..... | 6 | +| 7.8 Deployment ..... | 7 | +| 7.9 System operation ..... | 7 | +| 7.10 Timing ..... | 7 | +| 7.11 Sensor data processing and storage (SDPS)..... | 7 | +| 7.12 Monitoring..... | 7 | +| Bibliography..... | 8 | + + + +# Recommendation ITU-T G.9730.2 + +## Scientific monitoring and reliable telecommunication submarine cable systems + +# 1 Scope + +This Recommendation provides the capabilities and features of optical submarine telecommunication cable systems equipped with scientific monitoring sensors located along the length of the optical submarine cables. + +It describes the qualitative high-level characteristics and requirements of scientific monitoring and reliable telecommunication (SMART) cables using optical submarine cables to enable both telecommunication and sensing functionalities for ocean and climate monitoring as well as disaster warning. + +The Recommendation describes functional blocks, interfaces between various sensor sets and submarine cables and defines the predominant rules between the telecommunication and sensing functionality of the SMART cables concerning interference, powering, operation and maintenance. + +This Recommendation relies on existing Recommendations [b-ITU-T G.971], [ITU-T G.972], [b-ITU-T G.975.1], [b-ITU-T G.976], [ITU-T G.977], [ITU-T G.977.1], [ITU-T G.978] and [b-ITU-T G.979] for telecommunication aspects. + +# 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.972] Recommendation ITU-T G.972 (2024), *Definition of terms relevant to optical fibre submarine cable systems*. +- [ITU-T G.977] Recommendation ITU-T G.977 (2015), *Characteristics of optically amplified optical fibre submarine cable systems*. +- [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*. +- [ITU-T G.978] Recommendation ITU-T G.978 (2010), *Characteristics of optical fibre submarine cables*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the terms defined in [ITU-T G.972]. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 sensor:** An element of the system that measures a physical property of the environment and returns an observed value. + +- 3.2.2 sensor set:** A group of co-located sensors consisting of at least one temperature sensor, one pressure sensor and three accelerometers (each sensing one axis). +- 3.2.3 sensor subsystem:** Those components of the submarine cable system, including submerged plant and terminal equipment, whose sole purpose is the collection, transmission, storage and presentation of sensor data. +- 3.2.4 scientific subsystem:** Monitoring subsystem using sensors or sensor sets with their dedicated power supply and data transmission components. +- 3.2.5 telecommunication functions:** Functions and aspects of the cable system that are not related to sensing. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------------------------| +| BER | Bit Error Rate | +| BU | Branching Unit | +| DFOS | Distributed Fibre Optic Sensing | +| GSNR | Generalized Signal to Noise Ratio | +| OSNR | Optical Signal to Noise Ratio | +| PFE | Power Feeding Equipment | +| SMART | Scientific Monitoring and Reliable Telecommunications | +| SDPS | sensor data processing and storage | +| UTC | Universal Time Coordinated | + +# **5 Conventions** + +None. + +# **6 SMART submarine cable system description** + +A SMART submarine cable system incorporates, in addition to the telecommunication system, various sensors (e.g., temperature, pressure and three-axis acceleration sensors.) at predetermined intervals or dedicated geographical portions of the cable. Sensor sets are nominally located with at most one per repeater span. However other arrangements may be considered as depicted in Figure 1. + +The system provides continuous power for the sensors and transmits data from the sensors to one or more land stations. The equipment for receiving, storing and forwarding the data generated by the sensors is provided at the land station. Branch cable segments could also be equipped with sensors (see Figure 1). + +![Figure 1: Examples of SMART submarine cable systems. The figure shows seven diagrams (a-g) of submarine cable configurations between two land stations. A legend at the bottom defines the symbols: a blue square for an 'Optical submarine repeater', a blue square with a green rectangle for an 'Optical submarine repeater with scientific monitoring subsystem', and a green rectangle for a 'Submarine scientific monitoring subsystem'. Diagrams a, b, and d show various combinations of these repeaters. Diagrams c and e show repeaters and separate green scientific subsystems. Diagrams f and g show branching configurations using a 'BU' (Branching Unit) to connect to additional land stations or scientific subsystems.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +G.9730.2(24) + +Figure 1: Examples of SMART submarine cable systems. The figure shows seven diagrams (a-g) of submarine cable configurations between two land stations. A legend at the bottom defines the symbols: a blue square for an 'Optical submarine repeater', a blue square with a green rectangle for an 'Optical submarine repeater with scientific monitoring subsystem', and a green rectangle for a 'Submarine scientific monitoring subsystem'. Diagrams a, b, and d show various combinations of these repeaters. Diagrams c and e show repeaters and separate green scientific subsystems. Diagrams f and g show branching configurations using a 'BU' (Branching Unit) to connect to additional land stations or scientific subsystems. + +a) Each submarine repeater incorporates a scientific monitoring sub system, b) some of the submarine repeaters incorporate scientific monitoring subsystems, c) optical telecommunications and scientific monitoring are not collocated in the same repeater housing, d) submarine repeaters incorporating scientific monitoring subsystem are located in dedicated geographical areas to be monitored, e) submarine cable combining all described configurations, f) a branch of the submarine cables system uses submarine repeaters with scientific monitoring subsystems, g) a branch of submarine cable is dedicated to scientific monitoring. + +**Figure 1 – Examples of SMART submarine cable systems** + +# 7 System requirements + +## 7.1 Sensors + +### 7.1.1 Sensor types + +Sensors could be incorporated at one or multiple points along the cable within the scientific subsystems. Each scientific subsystem uses at least three co-located sensors consisting of one temperature sensor, one pressure sensor and a three-axis accelerometer. Seismometer and additional sensors or instruments could be used depending on other scientific monitoring applications such as salinity and acoustics/hydrophone sensors. A subset of the sensors could be used in systems that only require tracking of seismic activity (in this case temperature sensors would not be needed). It is also feasible that the optical fibre by itself could be used for distributed fibre optic sensing (DFOS) with dedicated equipment on the land station. + +#### 7.1.1.1 Temperature sensor + +The main parameters of the temperature sensor are: + +- Range [min, max] +- Initial accuracy + +- Stability (drift) +- Sampling rate +- Sample resolution + +#### **7.1.1.2 Pressure sensor** + +The main parameters of the pressure sensor are: + +- Range [min, max] +- Overpressure tolerance +- Accuracy +- Maximum allowable drift after a settling in period +- Accuracy after drift correction +- Hysteresis +- Repeatability +- Sampling rate +- Noise floor +- Sample resolution + +#### **7.1.1.3 Accelerometer** + +The main parameters of the 3-axis accelerometer are: + +- Configuration +- Response range +- Resonance frequency +- Full scale range +- Noise floor +- Amplitude response +- Linearity +- Cross-axis sensitivity +- Sampling rate +- Sample resolution + +#### **7.1.1.4 Seismometer** + +The main parameters of the seismometer are: + +- Configuration +- Frequency bandwidth +- Dynamic range +- Noise floor +- Sensitivity +- Clip level +- Sampling rate +- Sample resolution + +### **7.1.2 Location of the sensor** + +Several locations could be considered for the sensors: + +- The scientific monitoring subsystem could share the submarine repeater housing with telecommunication components. +- The scientific monitoring subsystem could be deployed in an external pod (a separate nearby housing supporting pressure and temperature sensors and connected to the electronics in the main housing). +- The scientific monitoring subsystem could be also incorporated in a dedicated repeater housing. +- The scientific monitoring subsystem could be also incorporated in a dedicated submarine node (a dedicated housing designed for scientific subsystem). + +### **7.1.3 Sensor performance** + +Although sensor performance requirements depend on the agreed upon sensor specifications, the following should be considered: + +- Variations arising from the measurement circuitry. +- The aging of measurement circuit components. +- Realistic geopositioning accuracy. +- Realistic orientation deviation from absolute earth reference. +- Environmental variations, including depth, ambient temperature and seabed conditions. + +## **7.2 Power feeding** + +The scientific subsystem provides the power required for the sensors as well as data sampling and communication functions. + +Adding SMART capabilities to the optical submarine transmission cable system will increase the power consumption of the system. The design of the power feeding equipment (PFE) supports these additional power requirements. + +## **7.3 Communication** + +### **7.3.1 General** + +There are no specific requirements regarding the communication method employed by the system supplier to transfer data and commands between the sensors and the land station(s). + +Dedicated fibre pair(s) could be used to connect the scientific monitoring subsystems to the land stations. Out of band or in band channels could also serve as the communication channel carrying the data and the commands between the sensors and the land stations. + +Security is a critical aspect for both telecommunication and sensing data traffic. The system needs to ensure the appropriate data communication protections. + +### **7.3.2 Data communication format** + +Communications between the scientific subsystem and end users could use proprietary communication formats or industry standard technologies. + +### **7.3.3 Latency** + +The main latency largely depends on the propagation delay through the fibre. Scientific monitoring subsystems incur an additional latency for collecting, processing and transferring sensor data to the land stations. The total latency is minimized to improve the disaster early warning detection systems. + +### **7.3.4 Performance** + +Adding SMART capabilities shall have no net impact on the telecommunication performance of an optical fibre submarine cable system. The performance is usually defined by optical signal to noise ratio (OSNR), generalized signal to noise ratio (GSNR), bit error rate (BER) and Q factor in the power budget table (see [ITU-T G.977] and [ITU-T G.977.1]). It is expected that SMART submarine cable systems using dedicated fibre pair(s) for scientific monitoring will have no impact on the performance of other telecommunication fibres. However, SMART submarine cables using, for example, out of band or in band channels to carry the sensor data could introduce a small penalty on telecommunication performance. In this case, any allocation to the system power budget because of the scientific subsystem is identified and the system performance measured at system commissioning should consider this impairment. + +## **7.4 Design life and fault isolation** + +The addition of the scientific subsystem shall have no impact on the telecommunication system design life. The scientific subsystem shall be designed such that failures in the scientific subsystem do not impact the telecommunication system, or at a minimum only impact the telecommunication system in extremely unlikely circumstances. Failures in the scientific subsystem shall not require intervention. + +The scientific subsystem may or may not have the same design life as the telecommunication system. For example, it may be acceptable for sensors to go out of calibration before the 25-year design life of the telecommunication system, perhaps on the assumption that another cable will have been placed on the same route before then or that external calibration can be performed (e.g., using ship-lowered instruments, or autonomous undersea vehicles). The system must continue to meet the communication performance requirements for its entire design life. + +The scientific subsystem shall be fault tolerant. The failure of a single sensor shall have no impact on the performance of other sensors. The failure of the scientific subsystem components at a single location shall not prevent data from being gathered from other locations. + +It is assumed that failed sensors or scientific subsystem components will not be repaired unless necessary to restore telecommunication functions (as opposed to scientific instrument communication functions). Thus, failure of any sensor, data processor or communication module does not result in a ship repair. + +## **7.5 Maintenance** + +The scientific subsystem shall have no impact on the ability to recover and repair the submarine cable system. A variety of vessels and methods may be used to recover and repair the system over its lifetime. The added weight of the scientific subsystem must be considered during system design to ensure changes to recovery conditions are within acceptable limits. It must be assumed that any impact on the scientific subsystem because of the repair operation will not be rectified. For example, repeaters may be re-laid in different positions or at different orientations with no attempt made to replicate the original installation conditions. + +## **7.6 Environmental requirements** + +The scientific subsystem shall be designed under the same environmental requirements as the overall telecommunication cable system for the transport, installation and operation of the system. + +## **7.7 Mechanical requirements** + +The scientific subsystem shall meet the same mechanical requirements as the overall optical submarine transmission cable system according to [ITU-T G.978]. + +## **7.8 Deployment** + +The scientific subsystem shall be compatible with conventional optical transmission submarine cable installation methods. + +## **7.9 System operation** + +The inclusion of scientific subsystems shall have no impact on operation of the telecommunication submarine cable system, including supervisory performance, element management and network management. + +## **7.10 Timing** + +Timing and synchronization are essential for the scientific subsystem. The scientific subsystem records the time (Universal Time Coordinated (UTC) or other suitable external reference) at which the data is recorded by a sensor. + +## **7.11 Sensor data processing and storage (SDPS)** + +The network management system stores the recorded sensor data and provides an interface to the client for their transfer. + +Data is reported in natural units, e.g., °C for temperature, m/s2 for acceleration, and Pa for pressure. + +## **7.12 Monitoring** + +The state of each scientific subsystem is controlled and monitored from the land stations via the maintenance controller. + +## Bibliography + +- [b-ITU-T G.971] Recommendation ITU-T G.971 (2024), *General features of optical fibre submarine cable systems.* +- [b-ITU-T G.975.1] Recommendation ITU-T G.975.1 (2004), *Forward error correction for high bit-rate DWDM submarine systems.* +- [b-ITU-T G.976] Recommendation ITU-T G.976 (2010), *Test methods applicable to optical fibre submarine cable systems.* +- [b-ITU-T G.979] Recommendation ITU-T G.979 (2016), *Characteristics of monitoring systems for optical submarine cable systems.* + + + +## 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.983.3-200103-I_PDF-E/042af54276c75e7b7b48a3af1f0a84e5_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/042af54276c75e7b7b48a3af1f0a84e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61a6fcdc8b250af6ea6efeb97af6d100fa938820 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/042af54276c75e7b7b48a3af1f0a84e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a2f34bd8eec7cd7482734cd913c84ea762722f2915fa12ad314f03c66819929 +size 45079 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fafebd163198ebe0bdfccf1b3610af5ef2cdc28 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d3742cc645a83a00668aa08fc7dd0344b3815cd99a99b3d52ababfdeb535e1a +size 49430 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8b2e53c9c9ddf3f391b86a3c0c3a9ca84ad50af --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6686deebae83c49a5be90fef62b42d03dc57e60bd0533a3ca8ab09598b6abe2b +size 51697 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/08f6ace0c83e7394657fa372b47aec04_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/08f6ace0c83e7394657fa372b47aec04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c3ffd8c4882cd317d1a70aec568588d1ebebb08 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/08f6ace0c83e7394657fa372b47aec04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a226b9c244fd89f6a4cb73f1ad3d480368e7af79a45c254243e9cbe3be933b5f +size 44833 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12c0dfa3d05c2d4f8d54726947d3db78aa85db9e --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa55c7634fcb2690143deb6ecb1c5bf12fe5774d023e11563d0aeaee809d6f79 +size 54547 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a11a86a363ef74e27093ad80fe62343ecd96232 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:694f23da890fca8869deae7cad680e674a3a55648ec579f5201e1f837726bca2 +size 54326 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/1c427123350e0e73e2a109b79069314b_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/1c427123350e0e73e2a109b79069314b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4695b945de7ea94f008d2d545239b10540059667 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/1c427123350e0e73e2a109b79069314b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23867fb416a12948988cbe8820c99aa972c44018c9b05fcd28cb498987235c96 +size 208499 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48d56161d8678558c876c6194aa21fd070d7be9a --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46e4b517b37a092faed9242390c725039546ef0c11bde63e61937302d7b74e65 +size 65044 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2468dfa77e8d32611a5fe8a2ebb904676994eeb54463226fd865698560c960c +size 8232 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7eeb991ab1a558c532fc87fb122ed029529b4b8 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a844815a6cf7b64825478860a90d5b95c6ca6eab758da81e3fe0cf5a243b29cc +size 202024 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef93ca48f4d18604a018f5ea1a5c4738e496d1e9 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:906b71a611a20438657959532ba8d3716abc598f19b78745c2e83914fdd29066 +size 51498 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..648c2af9cef2b4aa896adbd753860dc95539b457 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b10932cc428e9be63712247de5b7611f599f41100fcefa7ec3dda27bb73a8730 +size 58358 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6244e8bff9393003a99dccf63e43c98612de94b1 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58b8f829e42930c49022ead84fc56737c02a53c1ca0d2b1fc933497b0c7bbcc7 +size 50882 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..740a611dd7e7d274713abaf471884481409ff6d8 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:955c5009022a536077eb0a1cafb96cc5f3d41a3a342ed9f4c8685433d54bcae8 +size 40202 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/772cc583a60eeb058cc19de48269ad22_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/772cc583a60eeb058cc19de48269ad22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..123a0fd3f3d9a03847e7c203dc8f843dc1274748 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/772cc583a60eeb058cc19de48269ad22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:032adc4fee14573e5232455c91bc120748aec85457c8777e1091ecae979cd06b +size 45554 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f19eed6a068018df5cd8a181d21e2bc38795888c --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51a0ec6a1b9642cbf0b00bfe16627f701ddee23a280b37f6842d9d6e950350c0 +size 76391 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67678fe3964b7279a1a5940b76825f13a5e3c845 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49932ef26927de5d2083e5bea40f60b58378b2bea03732d3522aefc20253ae7f +size 45925 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcbf12b789db5dc53c573481d1384045a024a9f1 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ad82879a93a9bfaa7cb090505413e3ca5a6717d6d90403545fe84b757b9da6c +size 65480 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e134eb56a8250fa4590f1de24bd764bc671c5392 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9d310160ec9887893fbc7435f5a338846bbc8b6251a7e07ab2f867be780e98a +size 64243 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47249c2ccce76d6d8ad8cdc89635b6f6aa892ef7 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbe45e29df8a20faf5f1315959835ea4538b5023b0b904625147bb5f17c00ff9 +size 45359 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/db5deafdae53dbc7d5972957f708c691_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/db5deafdae53dbc7d5972957f708c691_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db6d40b542e05d5043f8c2f19535c86de30179bd --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/db5deafdae53dbc7d5972957f708c691_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b82beecb0e6d82686f64846ee013f4eacaf44f61d8aa030cf9402a456ba1aa11 +size 48637 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d9c557ac62bd6cd087767004168eed6ac8f9688 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:367030e235cdeaca77f8ba52e55576790f33f48382d08cfe4dfe0e7c0b6cc752 +size 29737 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36ed258eb7785d3980f3c5d705d85fdaeedda644 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eeeaccf2e7cbf4cf84c087751ff5af3a7612afec9d909aac9570cbc4b41dbc8c +size 47325 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/e05122559f56af5699789b7118d8fe87_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/e05122559f56af5699789b7118d8fe87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12ba2a3f33a25200c2591dc572e78f2bf71c5365 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/e05122559f56af5699789b7118d8fe87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e27063be406f522ad05fa44ddacf296c3c723dbfebed75928d8d29b894ddc9d6 +size 39916 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86e53b0297835c327c11a3faa902c2ef5f2a5542 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d9b2a07e3bd9290a5aa7f1f72ebe50a6f7d24ea9e7db177fe517ae660c465ba +size 205335 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a259477b3c0a36ae0cdbfbc6075eec36381db576 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffa342678f62e915fe4b1efdce2b52efc7fc5f8a27ce779fb7c8ba8705558951 +size 81075 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg b/marked/G/T-REC-G.983.3-200103-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f62cb45ca22199b9fccb1e9a90ba8ab03aaf8405 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cf125a9ee4cbd29185ffa013603db3c26dccb5d46c06ff60a0a9040bb77bbae +size 63239 diff --git a/marked/G/T-REC-G.983.3-200103-I_PDF-E/raw.md b/marked/G/T-REC-G.983.3-200103-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5839f5d744e3b0e9d91a2a27a891cc9863d31bc3 --- /dev/null +++ b/marked/G/T-REC-G.983.3-200103-I_PDF-E/raw.md @@ -0,0 +1,2038 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.983.3** + +(03/2001) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital sections and digital line system – Optical line +systems for local and access networks + +--- + +**A broadband optical access system with +increased service capability by wavelength +allocation** + +ITU-T Recommendation G.983.3 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TESTING EQUIPMENTS | G.500–G.599 | +| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 | +| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 | +| 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 | +| Access networks | G.990–G.999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **A broadband optical access system with increased service capability by wavelength allocation** + +## **Summary** + +This Recommendation defines new wavelength allocations to distribute ATM-PON signals and additional service signals simultaneously. New wavelength bands for additional services are made available by constraining the current ATM-PON downstream wavelength to a portion of downstream optical spectrum originally specified in ITU-T G.983.1. The new bands have potential to provide unidirectional and bidirectional services. The wavelength allocation defined in this Recommendation enables the distribution of video broadcast services or data services. The general optical characteristics of these services are taken into account. However, the detailed specifications of these services, such as modulation scheme, signal format, and so on are beyond the scope of this Recommendation. + +###### **Source** + +ITU-T Recommendation G.983.3 was prepared by ITU-T Study Group 15 (2001-2004) and approved under the WTSA Resolution 1 procedure on 15 March 2001. + +# FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +# CONTENTS + +| | | Page | +|-------|---------------------------------------------------------------------------------|------| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Abbreviations..... | 2 | +| 4 | Definitions ..... | 4 | +| 5 | Architecture of the optical access network ..... | 5 | +| 5.1 | Network architecture..... | 5 | +| 5.1.1 | FTTCab/C/B scenario..... | 6 | +| 5.1.2 | FTTH scenario ..... | 6 | +| 5.2 | Reference configuration..... | 6 | +| 5.2.1 | Service Node Interface ..... | 8 | +| 5.2.2 | Interface at the reference points S/R and R/S..... | 8 | +| 5.3 | Functional blocks..... | 8 | +| 5.4 | ONU functional block..... | 9 | +| 5.4.1 | Optical Distribution Network interface ..... | 9 | +| 5.4.2 | Multiplexing ..... | 9 | +| 5.4.3 | User Port..... | 9 | +| 5.4.4 | ONU powering ..... | 9 | +| 5.5 | Optical Line Termination functional block ..... | 9 | +| 5.6 | Optical Distribution Network functional block ..... | 10 | +| 6 | Services..... | 10 | +| 7 | User Network Interface and Service Node Interface ..... | 11 | +| 8 | Optical network requirements..... | 11 | +| 8.1 | Layered structure of optical network ..... | 11 | +| 8.2 | Physical medium dependent layer requirements for the wavelength allocation..... | 11 | +| 8.3 | Physical medium dependent layer requirements for the ATM-PON..... | 13 | +| 8.3.1 | Digital signal nominal bit rate ..... | 13 | +| 8.3.2 | Physical media and transmission method..... | 18 | +| 8.3.3 | Bit rate ..... | 18 | +| 8.3.4 | Line code ..... | 19 | +| 8.3.5 | Operating wavelength..... | 19 | +| 8.3.6 | Transmitter at $O_{ld}$ and $O_{ru}$ ..... | 19 | +| 8.3.7 | Optical path between $O_{ld}/O_{ru}$ and $O_{rd}/O_{lu}$ ..... | 19 | +| 8.3.8 | Receiver at $O_{rd}$ and $O_{lu}$ ..... | 20 | +| 8.4 | Physical medium dependent layer requirements for the Enhancement Band..... | 20 | + +| | Page | +|--------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| 9 | Operations Administration and Maintenance (OAM) functionality..... 21 | +| 10 | Performance ..... 21 | +| 11 | Environmental condition..... 21 | +| 12 | Safety ..... 21 | +| Appendix I – Optical interface parameters examples for ODN..... | 22 | +| I.1 | Introduction..... 22 | +| I.2 | Examples..... 22 | +| Appendix II – Deployment scenarios..... | 23 | +| II.1 | Introduction..... 23 | +| II.2 | Configuration examples..... 23 | +| II.2.1 | Case 1: Reception of Basic Band only ..... 23 | +| II.2.2 | Case 2: Reception of Basic Band and Enhancement Band signals by
separate ONUs..... 25 | +| II.2.3 | Case 3: Reception of Basic Band and Enhancement Band signals by
integrated ONUs..... 25 | +| II.2.4 | Case 4: Arrangement of WDMs to minimize upstream path loss ..... 26 | +| II.2.5 | Case 5: ODNs with reduced attenuation range for Enhancement Band..... 27 | +| II.2.6 | Example in case of insufficiency of loss budget between E-ONU and E-
OLT ..... 28 | +| Appendix III – Isolation between the Basic Band and the Enhancement Band ..... | 28 | +| III.1 | Introduction..... 28 | +| III.2 | Example for required isolation at Basic Band receiver from Enhancement Band
signal..... 30 | +| III.2.1 | Video services..... 30 | +| III.2.2 | DWDM services ..... 33 | +| III.3 | Example of isolation classes ..... 34 | +| III.4 | Deployment examples..... 35 | +| III.4.1 | Model to be considered..... 35 | +| III.4.2 | In case of 64-QAM ..... 37 | +| III.4.3 | Filter characteristics..... 39 | +| Appendix IV – Effect of optical return loss of ODN..... | 40 | +| IV.1 | Introduction..... 40 | +| IV.2 | Effect of ODN optical return loss in the Basic Band..... 41 | +| IV.2.1 | Reflectance model to be considered ..... 41 | +| IV.2.2 | Influence of reflectance into ONU receiver ..... 42 | +| IV.2.3 | Influence of reflectance into OLT receiver (in the signal region)..... 42 | + +| | Page | +|-----------------------------------------------------------------------------------------------------------|-------------| +| IV.2.4 Influence of reflectance into OLT receiver (in the no signal region) ..... | 44 | +| IV.2.5 Summary in effects of ODN optical return loss in the Basic Band ..... | 44 | +| IV.3 Influence of reflectance from Enhancement Band to Basic Band ..... | 47 | +| IV.3.1 Influence of reflectance into OLT receiver from Enhancement Band ..... | 47 | +| Appendix V – Optical parameters for reference point (c) and (e) and two example
deployment cases ..... | 50 | +| V.1 Introduction ..... | 50 | +| V.2 Optical level diagram examples ..... | 50 | +| V.2.1 Case 1: ODN centric view of optical parameters ..... | 50 | +| V.2.2 Case 2: Equipment centric view of optical parameters ..... | 50 | + +NOTE – This Recommendation uses the term "ONU" to refer to both ONTs and ONUs. Any reference to ONUs includes ONTs as well within this Recommendation. + +# **A broadband optical access system with increased service capability by wavelength allocation** + +# **1 Scope** + +This Recommendation describes some extended functions for the ATM-PON system defined in ITU-T G.983.1. + +This Recommendation describes the Broadband Passive Optical Network (BPON) system that uses wavelength division multiplexing techniques (WDM). These WDM techniques allow operators to provide additional services without disturbing the basic ATM-PON system. + +This Recommendation defines new wavelength allocations to distribute ATM-PON signals and additional service signals simultaneously. New wavelength bands for additional services are made available by constraining the current ATM-PON downstream wavelength to a portion of downstream optical spectrum originally specified in ITU-T G.983.1. The new bands have potential to provide unidirectional and bidirectional services. The wavelength allocation defined in this Recommendation enables the distribution of video broadcast services or data services, and the general optical characteristics of these services are taken into account. However, the detailed specifications of these services, such as modulation scheme, signal format, and so on are beyond the scope of this Recommendation. + +This Recommendation defines new reference points and optical interface parameters because of the new WDM and/or optical power splitter/combining functions needed at OLT and/or ONU sites. + +However, the reference points and Optical Access Network (OAN) described in this Recommendation will remain compatible with the existing ITU-T G.982 and G.983.1. + +This Recommendation also defines new environmental conditions required for the ONU equipment. These conditions are required for outside plant applications of the ATM-PON system. + +This Recommendation describes the relevant differences from ITU-T G.983.1. However, sections that specify the TC layer are not included in this Recommendation, because they are not relevant to WDM enhancements. The specifications of the TC layer are given by other Recommendations, such as ITU-T G.983.1. + +# **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. References cited in ITU-T G.983.1 also apply to this Recommendation but are not reproduced here to avoid redundancy. + +- [1] ITU-T G.692 (1998), *Optical interfaces for multichannel systems with optical amplifiers*. +- [2] ITU-T G.983.1 (1998), *Broadband optical access systems based on Passive Optical Networks (PON), plus Corrigendum 1 (1999)*. +- [3] ITU-T G.983.2 (2000), *ONT management and control interface specification for ATM PON*. +- [4] ITU-T G.959.1 (2001), *Optical transport network physical layer interfaces*. + +# 3 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|--------|-----------------------------------------------| +| AF | Adaptation Function | +| AM-VSB | Amplitude Modulation-Vestigial Side Band | +| APS | Automatic Protection Switching | +| ATM | Asynchronous Transfer Mode | +| BER | Bit Error Ratio | +| BIP | Bit Interleaved Parity | +| B-ISDN | Broadband Integrated Services Digital Network | +| BPON | Broadband Passive Optical Networks | +| CID | Consecutive Identical Digit | +| CNR | Carrier-to-Noise Ratio | +| CPE | Cell Phase Error | +| CRC | Cyclic Redundancy Check | +| DSL | Digital Subscriber Line | +| DWDM | Dense Wavelength Division Multiplexing | +| E/O | Electrical/Optical | +| E-OLT | Enhancement Band-Optical Line Termination | +| E-ONU | Enhancement Band-Optical Network Unit | +| FP-LD | Fabry-Perot Laser Diode | +| FTTB/C | Fibre to the Building/Curb | +| FTTCab | Fibre to the Cabinet | +| FTTH | Fibre to the Home | +| HEC | Header Error Control | +| IEC | International Electrotechnical Commission | +| ISDN | Integrated Services Digital Network | +| LAN | Local Area Network | +| LCD | Loss of Cell Delineation | +| LCF | Laser Control Field | +| LSB | Least Significant Bit | +| LT | Line Terminal | +| MAC | Media Access Control | +| MLM | Multi-Longitudinal Mode | +| MSB | Most Significant Bit | +| NRZ | Non Return to Zero | +| NT | Network Termination | +| O/E | Optical/Electrical | + +| | | +|-------|-----------------------------------------------------------------------| +| OAM | Operation, Administration and Maintenance | +| OAN | Optical Access Network | +| ODF | Optical Distribution Frame | +| ODN | Optical Distribution Network | +| OLT | Optical Line Termination | +| ONT | Optical Network Termination | +| ONU | Optical Network Unit | +| OpS | Operations System | +| ORL | Optical Return Loss | +| PLOAM | Physical Layer OAM | +| PON | Passive Optical Network | +| PRBS | Pseudo-Random Bit Sequence | +| PST | PON Section Trace | +| PSTN | Public Switched Telephone Network | +| QAM | Quadrature Amplitude Modulation | +| QoS | Quality of Service | +| QPSK | Quadrature Phase Shift Keying | +| RAU | Request Access Unit | +| RIN | Relative Intensity Noise | +| RMS | Root Mean Square | +| RXCF | Receiver Control Field | +| SCM | Sub-Carrier Multiplexing | +| SDH | Synchronous Digital Hierarchy | +| SLM | Single-Longitudinal Mode | +| SN | Serial Number | +| SNI | Service Node Interface | +| TC | Transmission Convergence | +| TDMA | Time Division Multiple Access | +| UI | Unit Interval | +| UNI | User Network Interface | +| UPC | Usage Parameter Control | +| VC | Virtual Channel | +| VP | Virtual Path | +| VPI | Virtual Path Identifier | +| WDM | Wavelength Division Multiplexing | +| WF1 | Wavelength division multiplexing and/or optical combining functions 1 | +| WF2 | Wavelength division multiplexing and/or optical splitting functions 2 | + +# 4 Definitions + +This Recommendation defines the following terms: + +- 4.1 diplex working:** Bidirectional communication using a different wavelength for each direction of transmission over a single fibre. +- 4.2 duplex working:** Bidirectional communication using the same wavelength for both directions of transmission over a single fibre. +- 4.3 logical reach:** The logical reach is defined as the maximum length that can be achieved for a particular transmission system independent of optical budget. +- 4.4 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. +- 4.5 Optical Distribution Network (ODN):** An ODN provides the optical transmission means from the OLT towards the users, and vice versa. It utilizes passive optical components. +- 4.6 Optical Line Termination (OLT):** An OLT provides the network-side interface of the OAN, and is connected to one or more ODNs. +- 4.7 Optical Network Termination (ONT):** An ONU used for FTTH and includes the User Port function. +- 4.8 Optical Network Unit (ONU):** An ONU provides (directly or remotely) the user-side interface of the OAN, and is connected to the ODN. +- 4.9 user port function:** The User Port Function (UPF) adapts the specific UNI requirements to the core and management functions. The AN may support a number of different accesses and user network interfaces which require specific functions according to the relevant interface specification and the access bearer capability requirements, i.e. bearers for information transfer and protocols. +- 4.10 verification:** It is possible for a malicious user to masquerade as other ONU and use the network if the user knows that the ONU is power-off. Verification is a function to check whether the connected ONU is masqueraded by a malicious user. +- 4.11 Wavelength Division Multiplexing (WDM):** Bidirectional multiplexing using different optical wavelength for up and downstream signals and multiplexing using different optical wavelength for Basic Band, Enhancement Band and Future Band signals. +- 4.12 basic band:** Wavelength region allocated for the ATM-PON downstream capabilities. +- 4.13 enhancement band:** Wavelength region allocated for new additional service capabilities, which include at least video services and Dense Wavelength Division Multiplexing (DWDM) services. +- 4.14 future band:** Reserved wavelength region for future use. +- 4.15 E-OLT:** OLT, which provides additional service capabilities including video services and DWDM services in Enhancement Band. +- 4.16 E-ONU:** ONU, which provides additional service capabilities including video services and DWDM services in Enhancement Band. +- 4.17 WF1:** WDM and/or optical combining/splitting functions, which separate/combine wavelength and/or split/combine optical power for ATM-PON transport service and additional services. It is located between ODN and the OLT. +- 4.18 WF2:** WDM and/or optical combining/splitting functions, which separate/combine wavelength and/or split/combine optical power for ATM-PON transport service and additional services. It is located between ODN and the ONU. + +**4.19 WDM-L:** WDM, which separate/combine 1.3 μm region and 1.5 μm region, and is located in OLT side. + +**4.20 WDM-N:** WDM, which separate/combine 1.3 μm region and 1.5 μm region, and is located in ONU side. + +**4.21 BPON:** Broadband Passive Optical Network (BPON). BPONs are one-to-n broadband optical transmission systems. BPONs can transparently transport any type of data, for example voice, video, IP data, etc. The BPON is able to carry data regardless of the type of data link frame (i.e. not only native ATM but also HDL Ethernet frame, etc.). + +# 5 Architecture of the optical access network + +## 5.1 Network architecture + +The optical section of a local access network system could be either a point-to-point, active, or passive point-to-multipoint architecture. Figure 1 shows the architectures considered, which range from Fibre to the Home (FTTH), through Fibre to the Building/Curb (FTTB/C) to Fibre to the Cabinet (FTTCab). The Optical Access Network (OAN) is common to all architectures shown in Figure 1, hence commonality in this system has the potential to generate large worldwide volumes. The FTTB/C and FTTCab network options are predominantly different only as a result of implementation, as a result they can be treated the same in this Recommendation. + +![Diagram of network architectures: FTTH, FTTB/C, and FTTCab. FTTH shows a direct fibre connection from ONT to OLT. FTTB/C and FTTCab show a copper connection from NT to ONU, followed by a fibre connection from ONU to OLT. The diagram is divided into 'Home network' (left of UNI) and 'Access network' (right of UNI).](08441fa90c5fd11994626f662ac13f19_img.jpg) + +The diagram illustrates three network architectures: FTTH, FTTB/C, and FTTCab. Each architecture is shown as a horizontal line representing the network path. FTTH: A box labeled 'ONT' is connected to a box labeled 'OLT' via a line labeled 'Fibre'. FTTB/C: A box labeled 'NT' is connected to a box labeled 'ONU' via a line labeled 'Copper'. The 'ONU' is then connected to the 'OLT' via a line labeled 'Fibre'. FTTCab: Similar to FTTB/C, but the 'ONU' is located further away from the 'OLT'. The 'OLT' is a large vertical box on the right. The 'UNI' (User Network Interface) is marked at the left end of the 'Access network' section. The 'SNI' (Service Network Interface) is marked at the right end of the 'Access network' section. The 'Home network' is the section to the left of the 'UNI'. + +UNI + +SNI + +Home network + +Access network + +FTTH + +ONT + +Fibre + +OLT + +NT + +Copper + +ONU + +FTTB/C + +FTTCab + +ONU + +NT + +Copper + +ONU + +Fibre + +T1528110-98 + +ONU Optical Network Unit +ONT Optical Network Termination +OLT Optical Line Termination +NT Network Termination + +Diagram of network architectures: FTTH, FTTB/C, and FTTCab. FTTH shows a direct fibre connection from ONT to OLT. FTTB/C and FTTCab show a copper connection from NT to ONU, followed by a fibre connection from ONU to OLT. The diagram is divided into 'Home network' (left of UNI) and 'Access network' (right of UNI). + +**Figure 1/G.983.3 – Network architecture** + +### 5.1.1 FTTCab/C/B scenario + +See 5.1.1/G.983.1. + +### 5.1.2 FTTH scenario + +FTTH; Fibre to the Home service drivers are similar to those of the previous scenarios and are determined by: + +- Indoor ONUs can be considered, resulting in more favourable environmental conditions. +- Some changes of intermediate ONU may be required to upgrade access network capabilities to accommodate future evolution of broadband and multimedia services. +- Maintenance is easy, because it requires maintenance only for fibre systems, and all fibre systems are regarded as more reliable than hybrid fibre-metallic ones. +- FTTH is a driver for the development of advanced optoelectronics technologies. The greater volume in production of optical modules will also accelerate the reduction in cost. + +When these factors can be fully exploited they may counterbalance a slightly higher per line cost. In that situation the FTTH scenario may be regarded as economically feasible even in the short term. + +## 5.2 Reference configuration + +The general reference configuration from ITU-T G.983.1 is shown in Figure 2a. + +The specific reference configuration for this Recommendation is shown in Figure 2b which provides clarification of the new specification based on the revised wavelength allocation. + +The ODN offers one or more optical paths between one OLT and one or more ONUs. Each optical path is defined between reference points S and R in a specific wavelength window. 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. + +This clause describes the reference architecture for supporting Broadband transmission over a PON. This system consists of Optical Line Termination (OLT), Optical Network Unit (ONU), Wavelength division multiplexing and/or optical combining/splitting functions (WF1 and WF2) for the new wavelength allocation plan defined in this Recommendation and fibre cable which has a Passive Optical Network (PON) configuration with a passive optical splitter. + +One fibre is passively split between multiple ONUs who share the capacity of one fibre. Because of the passive splitting, special actions are required with respect to privacy and security. Moreover, in the upstream direction a TDMA protocol is required. + +WF1 and WF2 are used for separating/combining wavelengths and/or splitting/combining optical power for ATM-PON transport service and additional services such as video broadcast. These may be integrated into or provided as external optical component parts connected to the OLT and the ONU. Therefore, WF1 and WF2 could be regarded as a part of the OLT and the ONU. In the case of integration into the OLT or the ONU, reference points (c) and (e) in Figure 2b are regarded as internal reference points of the OLT and the ONU respectively. + +Functionality required for WF1 and WF2 will vary depending upon the particular system configuration, regulations, service strategy, and geographic conditions for each telecom operator. These configurations based on scenarios by operators are described in Appendix II. + +![Diagram of reference configuration for an ATM based PON. At the top, 'Access Network System Management Functions' are connected to a 'Q3' interface. Below this, a bracket labeled '(T_B)/(T) reference point' spans over two ONUs and an AF. The top ONU is connected to the management functions via its R/S interface. The bottom ONU is connected to an AF, which is connected to a UNI. The bottom ONU's IF_PON interface is connected to an ODN. The ODN's S/R interface is connected to an OLT. The OLT's IF_PON interface is connected to the ODN. The OLT's SNI interface is connected to a 'Service node function'. A bracket labeled '(V_B)/(V) reference point' is located below the OLT and Service node function.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +Diagram of reference configuration for an ATM based PON. At the top, 'Access Network System Management Functions' are connected to a 'Q3' interface. Below this, a bracket labeled '(T\_B)/(T) reference point' spans over two ONUs and an AF. The top ONU is connected to the management functions via its R/S interface. The bottom ONU is connected to an AF, which is connected to a UNI. The bottom ONU's IF\_PON interface is connected to an ODN. The ODN's S/R interface is connected to an OLT. The OLT's IF\_PON interface is connected to the ODN. The OLT's SNI interface is connected to a 'Service node function'. A bracket labeled '(V\_B)/(V) reference point' is located below the OLT and Service node function. + +- ONU Optical Network Unit +- ODN Optical Distribution Network +- OLT Optical Line Termination +- AF Adaptation Function +- S Point on the optical fibre just after the OLT[Downstream]/ONU[Upstream] optical connection point (i.e. optical connector or optical splice). +- R Point on the optical fibre just before the ONU[Downstream]/OLT[Upstream] optical connection point (i.e. optical connector or optical splice). +- (a) Reference point – This reference point is added to differentiate the AF from the ONU. + +T1528120-98 + +**Figure 2a/G.983.3 – Reference configuration for an ATM based PON** + +![Figure 2b/G.983.3 – Reference configuration for a Broadband PON. The diagram illustrates the architecture of a Broadband Passive Optical Network (PON). On the left side, User Network Interfaces (UNI) connect to various Optical Network Units (ONUs). One path shows a UNI connecting to an ONU and an E-ONU, which then connect to a Wavelength division multiplexing function (WF2) before reaching the Optical Distribution Network (ODN) at reference points (e) and (f). Another path shows a UNI connecting through an Adaptation Function (AF) to an ONU and then to a WF2, reaching the ODN at reference point (a). A third path shows a (T_B)/(T) reference point connecting to an ONU and WF2. The ODN is the central hub, connected to the ONU side via R/S and S/R points and the IF_PON interface. On the right side, the ODN connects to the Optical Line Termination (OLT) side via S/R and R/S points and the IF_PON interface. A WF1 block connects to an OLT and an E-OLT at reference points (c) and (d). These connect via a Service Node Interface (SNI) to the Service node function. A (V_B)/(V) reference point is indicated on the far right.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + ++ Q3 +Access Network System Management Functions + +``` + +graph LR + subgraph "Access Network System Management Functions" + Q3 + end + UNI --- ONU1[ONU] + UNI --- EONU[E-ONU] + ONU1 --- WF2_1[WF2] + EONU --- WF2_1 + WF2_1 -- "(e), (f)" --- ODN + + UNI2[UNI] --- AF --- ONU2[ONU] --- WF2_2[WF2] -- "(a)" --- ODN + TB["(T_B)/(T)"] --- ONU3[ONU] --- WF2_3[WF2] --- ODN + + ODN -- "IF_PON (S/R, R/S)" --- WF1 + WF1 -- "(c)" --- OLT + WF1 -- "(d)" --- EOLT[E-OLT] + OLT --- SNI --- SNF[Service node function] + EOLT --- SNI + SNF --- VB["(V_B)/(V)"] + +``` + +- ONU Optical Network Unit (which may include WF2 and/or E-ONU) +- E-ONU Optical Network Unit for Enhancement Band usage (which may be integrated into ONU) +- ODN Optical Distribution Network +- OLT Optical Line Termination (which may include WF1 and/or E-OLT) +- E-OLT Optical Line Termination for Enhancement Band usage (which may be integrated into OLT) +- AF Adaptation Function +- WF1 Wavelength division multiplexing and/or optical power splitting/combining Function at OLT side +- WF2 Wavelength division multiplexing and/or optical power splitting/combining Function at ONU side +- S Point on the optical fibre just after the OLT[Downstream]/ONU[Upstream] optical connection point (i.e. optical connector or optical splice), assuming that WF1 and WF2 are included in the OLT and the ONU respectively. +- R Point on the optical fibre just before the ONU[Downstream]/OLT[Upstream] optical connection point (i.e. optical connector or optical splice), assuming that WF1 and WF2 are included in the OLT and the ONU respectively. +- (a) Reference point – This reference point is added to differentiate the AF from the ONU. +- (b) Intentionally not used to avoid confusion with the index of broadband. +- (c) Reference point – This reference point is added to differentiate the WF1 from the OLT. +- (d) Reference point – This reference point is added to differentiate the WF1 from the E-OLT. +- (e) Reference point – This reference point is added to differentiate the WF2 from the ONU. +- (f) Reference point – This reference point is added to differentiate the WF2 from the E-ONU. + +T1543820-01 + +Figure 2b/G.983.3 – Reference configuration for a Broadband PON. The diagram illustrates the architecture of a Broadband Passive Optical Network (PON). On the left side, User Network Interfaces (UNI) connect to various Optical Network Units (ONUs). One path shows a UNI connecting to an ONU and an E-ONU, which then connect to a Wavelength division multiplexing function (WF2) before reaching the Optical Distribution Network (ODN) at reference points (e) and (f). Another path shows a UNI connecting through an Adaptation Function (AF) to an ONU and then to a WF2, reaching the ODN at reference point (a). A third path shows a (T\_B)/(T) reference point connecting to an ONU and WF2. The ODN is the central hub, connected to the ONU side via R/S and S/R points and the IF\_PON interface. On the right side, the ODN connects to the Optical Line Termination (OLT) side via S/R and R/S points and the IF\_PON interface. A WF1 block connects to an OLT and an E-OLT at reference points (c) and (d). These connect via a Service Node Interface (SNI) to the Service node function. A (V\_B)/(V) reference point is indicated on the far right. + +**Figure 2b/G.983.3 – Reference configuration for a Broadband PON** + +### 5.2.1 Service Node Interface + +See ITU-T G.902. + +### 5.2.2 Interface at the reference points S/R and R/S + +This interface at the reference points S/R and R/S is defined as $IF_{PON}$ . This is a PON-specific interface that supports all the protocol elements necessary to allow the transmission between OLT and ONUs. + +## 5.3 Functional blocks + +See 5.3/G.983.1. + +## 5.4 ONU functional block + +As an example, the FTTH ONU is active and decouples the access network delivery mechanism from the in-house distribution. The ONU consists of ODN interface, User Port, Transmission, Services, Customers Multiplexing (MUX)/demultiplexing functions and powering, which is described in Figure 3. + +![Figure 3/G.983.3 – Example of ONU functional blocks. The diagram shows the internal architecture of an ONU, divided into three main shells: Service shell, Core shell, and Common shell. The Service shell contains two 'User Port Function' blocks, one at the top and one at the bottom, separated by four asterisks (*). The Core shell contains three main blocks: 'Customer and services multiplex/demultiplex function', 'Transmission multiplex/demult. function', and 'ODN interface function'. The Common shell contains 'Power' and 'OAM' blocks. The entire structure is flanked by 'Customer' on the left and 'ODN' on the right, with horizontal lines indicating interfaces. A label 'T1528130-98' is at the bottom right.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +The diagram illustrates the functional blocks of an ONU. It is organized into three horizontal sections: Service shell, Core shell, and Common shell. The Service shell at the top contains two 'User Port Function' blocks, one above and one below a set of four asterisks (\*). The Core shell in the middle contains three blocks: 'Customer and services multiplex/demultiplex function', 'Transmission multiplex/demult. function', and 'ODN interface function'. The Common shell at the bottom contains 'Power' and 'OAM' blocks. The entire assembly is flanked by 'Customer' on the left and 'ODN' on the right, with horizontal lines indicating interfaces. A label 'T1528130-98' is at the bottom right. + +Figure 3/G.983.3 – Example of ONU functional blocks. The diagram shows the internal architecture of an ONU, divided into three main shells: Service shell, Core shell, and Common shell. The Service shell contains two 'User Port Function' blocks, one at the top and one at the bottom, separated by four asterisks (\*). The Core shell contains three main blocks: 'Customer and services multiplex/demultiplex function', 'Transmission multiplex/demult. function', and 'ODN interface function'. The Common shell contains 'Power' and 'OAM' blocks. The entire structure is flanked by 'Customer' on the left and 'ODN' on the right, with horizontal lines indicating interfaces. A label 'T1528130-98' is at the bottom right. + +Figure 3/G.983.3 – Example of ONU functional blocks + +### 5.4.1 Optical Distribution Network interface + +The ODN interface handles the optoelectronic conversion process. The ODN interface extracts ATM cells from the downstream PON payload and inserts ATM cells into the upstream PON payload based on synchronization acquired from the downstream frame timing. + +The ODN interface may handle the separation/combination of designated wavelengths and/or the optical splitter/combiner. + +### 5.4.2 Multiplexing + +Multiplexer (MUX) multiplexes service interfaces to ODN interface. Only valid ATM cells can be passed through the MUX, so many VPs can share the assigned upstream bandwidth effectively. + +### 5.4.3 User Port + +The User Port interfaces over UNI to a terminal. The User Port may handle inserting ATM cells into the upstream payload and extracting ATM cells from the downstream payload. In addition, the User Port may interface for video delivery and/or additional service from the OLT to customers. + +### 5.4.4 ONU powering + +ONU powering may be implementation dependent. + +## 5.5 Optical Line Termination functional block + +The OLT is connected to the switched networks via standardized interfaces (VB5.x, V5.x, NNI's). At the distribution side, it presents optical accesses according to the agreed requirements, in terms of bit rate, power budget, etc. + +The OLT consists of three parts: the service port function; ODN interface; and MUX for VP grooming (see Figure 4). This combination is not intended to preclude the Virtual Channel (VC) layer function in the OLT. VC layer function is for further study. + +### 1) *Service port function* + +The function interfaces to service nodes. The service port function may handle inserting ATM cells into the upstream SDH payload and extracting ATM cells from the downstream SDH payload. The function may be duplicated, then a protection switching function is necessary. + +### 2) *MUX* + +The MUX provides VP connections between the service port function and the ODN interface and different VPs are assigned to different services at IFPON. Various information such as main contents, signalling, and OAM flows are exchanged by using VCs of the VP. + +### 3) *ODN interface* + +The ODN interface handles the optoelectronic conversion process. The ODN interface handles inserting ATM cells into the downstream PON payload and extracting ATM cells from the upstream PON payload. In addition, the ODN interface may handle the separation/combination of designated wavelengths and/or the optical splitter/combiner. + +![Functional block diagram of an OLT showing Core shell and Service shell components.](36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg) + +The diagram illustrates the functional blocks of an OLT, divided into two main shells: the Core shell and the Service shell. + +- Core shell:** + - Contains two **ODN Interface Function** blocks, one at the top and one at the bottom, each with three asterisks (\*) below it. + - A central **Transmission MUX/demux.** block. + - An **ATM cross-connect function** block to the right of the MUX. + - At the bottom, there are two blocks: **Power** and **OAM**. +- Service shell:** + - Contains two **Service Port Function** blocks, one at the top and one at the bottom, each with three asterisks (\*) below it. + +External connections on the right side of the Service shell include: + +- A group of five asterisks (\*) labeled **Core Network**. +- A **V5.x/VB Interface**. +- A **Local exchange**. + +Functional block diagram of an OLT showing Core shell and Service shell components. + +T1528140-98 + +Figure 4/G.983.3 – Example of OLT functional blocks + +## 5.6 Optical Distribution Network functional block + +See 5.6/G.983.1. + +# 6 Services + +Such a high speed access system could provide the complete range of all currently known and new services being discussed for the residential subscribers and business customers. Here transmission system's service independence has to be regarded. + +These services cover a broad range of network requirements like bit rate, symmetry/asymmetry or delay, and range from video distribution, with varying degrees of interactivity, to electronic data transfer, LAN interconnection, transparent Virtual Paths, and so on. + +What specific services should be provided is clearer to some operators than to others and depends heavily on the particular regulatory conditions of each operators' markets, as well as on the own markets potential. How these services are delivered in a cost effective way is a function not only of legal conditions, but also of factors including existing telecommunications infrastructure, dwelling distribution and residential and business customers mix. + +In spite of this varied market background there are some features which have been perceived as common to all parties. They can be summarized as follows: + +- some services require bit rates higher than those supported by PSTN and basic ISDN. These services are best delivered on fibre-based or fibre hybrid networks; +- as the services evolve and newer services are introduced, the bandwidth and management requirements will increase. This requires the access network to be flexible and easily upgradable; +- additional services, such as video distribution service overlaid ATM-PON, can be provided in an appropriate manner using the WDM scheme, where necessary. The choice of video modulation type will have an impact on the system requirements, but the video modulation system is beyond the scope of this Recommendation. + +# 7 User Network Interface and Service Node Interface + +The location of UNI and SNI is preliminary given in the reference configuration (see Table 1). + +Other types of services such as video broadcast are for further study. + +**Table 1/G.983.3 – UNI and SNI** + +| Service type | UNI standard | SNI standard | +|----------------------------------|--------------|---------------| +| Defined in ITU-T G.982 | ITU-T G.902 | ITU-T G.902 | +| – Digital broadband video system | | ITU-T G.967.1 | +| – Multimedia services | ITU-T I.432 | ITU-T G.967.2 | +| – VP leased line | IEEE 802.3 | | +| – ATM SVC | | | + +# 8 Optical network requirements + +## 8.1 Layered structure of optical network + +See 8.1/G.983.1. + +## 8.2 Physical medium dependent layer requirements for the wavelength allocation + +The wavelength of the ATM-PON downstream signal (single fibre system) is in the 1.5 µm band and that of the ATM-PON upstream signal is in the 1.3 µm band in ITU-T G.983.1. This Recommendation defines the new wavelength allocation to enable additional new services using the wavelength band defined in ITU-T G.983.1. The ATM-PON downstream wavelength band shall be compressed within the original 1.5 µm band and new wavelength bands shall be assigned for new additional services. + +Figure 5 and Table 2 define the new wavelength allocation. This reduces the ATM-PON downstream allocation currently defined in ITU-T G.983.1 to a portion of the available downstream optical spectrum. This portion for the ATM-PON shall be referred to as the "Basic Band". An additional wavelength band will then be made available and be referred to as the "Enhancement Band." Uses for the Enhancement Band include at least video services and Wavelength Division Multiplexing (WDM) services. A guardband separates the Basic Band from the Enhancement Band. The interference between signals in these two bands causes signal degradation to each other, which shall be kept negligible. Required isolation between these bands depends on optical power level, modulation scheme and so on. An example of WDM filters is described in Appendix III. + +The specifications for Future L Band in the 1.5 $\mu\text{m}$ band, and the "Reserved for Allocation by ITU-T" band in the Intermediate region, are for further study. + +NOTE – Wavelengths in Enhancement Band may be used not only for downstream but also for upstream signal transmission in the WDM scheme. + +![Diagram of the 1.3 μm wavelength band showing the G.983.1 Upstream Band from 1260 nm to 1360 nm. Diagram of the Intermediate wavelength band from 1360 nm to 1480 nm, showing a reserved region for ITU-T allocation between guardbands. Diagram of the 1.5 μm wavelength band showing the Basic Band (ATM-PON Downstream), Enhancement Band, and Future L Band (Reserved for ITU-T) separated by guardbands.](1c427123350e0e73e2a109b79069314b_img.jpg) + +1.3 $\mu\text{m}$ wavelength band (Upstream) + +G.983.1 Upstream Band (unchanged at 100 nm bandpass) + +1260 1280 1300 1320 1340 1360 + +Intermediate wavelength band (Upstream and/or Downstream) + +Guardband Reserved for allocation by ITU-T Guardband + +1360 1380 1400 1420 1440 1460 1480 + +1.5 $\mu\text{m}$ wavelength band (Upstream and/or Downstream) + +Basic Band Enhancement Band Future L Band + +ATM-PON Downstream Guardband Reserved for allocation by ITU-T + +$\lambda_1$ $\lambda_2$ $\lambda_3$ $\lambda_4$ $\lambda_5$ $\lambda_6$ + +Legend: + +- Upstream Window (no change) +- Basic Band (constrained APON band) +- Enhancement Band (other uses) +- For future use + +$\lambda_1$ - $\lambda_6$ Defined in Table 2 + +T1543830-01 + +Diagram of the 1.3 μm wavelength band showing the G.983.1 Upstream Band from 1260 nm to 1360 nm. Diagram of the Intermediate wavelength band from 1360 nm to 1480 nm, showing a reserved region for ITU-T allocation between guardbands. Diagram of the 1.5 μm wavelength band showing the Basic Band (ATM-PON Downstream), Enhancement Band, and Future L Band (Reserved for ITU-T) separated by guardbands. + +**Figure 5/G.983.3 – Wavelength allocation** + +**Table 2/G.983.3 – Parameters for wavelength allocation in Figure 5** + +| Items | Notation | Unit | Nominal value | Application examples | +|------------------------------|----------|------|-------------------|---------------------------------------------------------------| +| 1.3 µm wavelength band | | | | | +| Lower limit | – | nm | 1260 | For use in ATM-PON upstream. | +| Upper limit | – | nm | 1360 | | +| Intermediate wavelength band | | | | For future use | +| Lower limit | – | nm | 1360 | – Reserved band including guardbands for allocation by ITU-T. | +| Upper limit | λ1 | nm | 1480 | | +| Basic Band | | | | | +| Lower limit | λ1 | nm | 1480 | For use in ATM-PON downstream. | +| Upper limit | λ2 | nm | 1500 | | +| Enhancement Band (Option 1) | | | | | +| Lower limit | λ3 | nm | 1539 | For additional digital service use. | +| Upper limit | λ4 | nm | 1565 | | +| Enhancement Band (Option 2) | | | | | +| Lower limit | λ3 | nm | 1550 | For video distribution service. | +| Upper limit | λ4 | nm | 1560 | | +| Future L Band | | | | | +| Lower limit | λ5 | nm | For further study | For future use
– Reserved band for allocation by ITU-T. | +| Upper limit | λ6 | nm | | | + +NOTE 1 – The central frequencies in the Enhancement Band for DWDM application shall be based on the frequency grid given in ITU-T G.959.1 and G.692. + +NOTE 2 – The value of isolation between the Basic Band signal and the Enhancement Band signal is not decided uniquely, because system configuration varies by regulations, service strategy, and geographic conditions as well as offered services in the Enhancement Band. + +Here, isolation should be interpreted as both the ratio of leaked Basic Band signal to E-ONU or E-OLT from Basic Band signal and the ratio of leaked Enhancement Band signal to ONU or OLT from Enhancement Band signal at WF1 or WF2. Both types of isolation should be defined separately. + +Common use of WDM filters is expected for cost reduction through large volume production. The isolation examples required in typical cases are described in Appendix III. + +NOTE 3 – Isolation value recommended for between the Basic Band signal and the Enhancement Band signals (Option 1) is for further study. + +NOTE 4 – Isolation value recommended for between the Basic Band signal and the Enhancement Band signals (Option 2) is for further study. + +NOTE 5 – Applied filter has appropriate loss characteristics to achieve required isolation. However, loss characteristics outside the 1480-1580 nm range (e.g. in the future L Band) is for further study. + +## 8.3 Physical medium dependent layer requirements for the ATM-PON + +### 8.3.1 Digital signal nominal bit rate + +The transmission line rate should be a multiple of 8 kHz. The target standardized system will have the following nominal line rates: + +- Option 1: Symmetric 155.52 Mbit/s for FTTCab/C/B/H. +- Option 2: Asymmetric 155.52 Mbit/s upstream/622.08 Mbit/s downstream for FTTCab/C/B. + +Parameters to be defined are categorized by downstream and upstream, and nominal bit rate as shown in Table 3. + +**Table 3/G.983.3 – Relation between parameter categories and tables** + +| Transmission direction | Nominal bit rate | Table | +|------------------------|------------------|-----------------------------------| +| Downstream | 155.52 Mbit/s | Table 4b (downstream, 155 Mbit/s) | +| | 622.08 Mbit/s | Table 4c (downstream, 622 Mbit/s) | +| Upstream | 155.52 Mbit/s | Table 4d (upstream, 155 Mbit/s) | + +All parameters are specified as follows, and shall be in accordance with Table 4a (ODN), Table 4b (downstream, 155 Mbit/s), Table 4c (downstream, 622 Mbit/s) and Table 4d (upstream, 155 Mbit/s). These tables will be globally referred to as Table 4 in this Recommendation unless more precision is needed. There are 6 kinds of ONUs and they are distinguished by bit rates of 155.52 Mbit/s and 622.08 Mbit/s and by optical path loss of Class A, Class B, and Class C (defined in ITU-T G.982). Some parameters described in Table 4 are described in Appendix I as examples for implementation. + +The specification in Table 4 does not include the Maximum reflectance of equipment measured at transmitter wavelength and the Maximum reflectance of equipment measured at receiver wavelength for the E-ONU and E-OLT. Reflection from E-ONU and E-OLT may cause signal degradation in the ATM-PON transmission. The specifications for E-ONU and E-OLT reflectances at the 1.3 µm upstream and at the Basic Band downstream wavelengths are for further study. + +All parameter values specified are worst-case values, assumed to be met over the range of standard operating conditions (e.g. 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. + +All parameters are specified for IFPON and relevant optical parameters for reference points of (c) and (e) in Figure 2b are described in Appendix V. + +Attenuation range in the ODN may be reduced for some application area such as new-built field or limited area. In this case, required optical parameters will be relaxed and enhance applicability of optical modules compliant to ITU-T G.983.1. Appendix V also describes the example case of reduced attenuation range of the ODN. + +**Table 4a/G.983.3 – Physical medium dependant layer parameters of ODN** + +| Items | Unit | Specification | +|---------------------------------------------------|------|-------------------------------------------------------------------------------------------------------| +| Fibre type | – | 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 | +| Max differential logical reach | km | 20 | +| Maximum fibre distance between S/R and R/S points | km | 20 | +| Minimum supported split ratio | – | Restricted by path loss and ONU addressing limits.
PON with passive splitters (16 or 32 way split) | +| Bidirectional transmission | – | 1-fibre WDM (2-fibre system is beyond the scope of this Recommendation) | +| Maintenance wavelength | nm | to be defined | + +**Table 4b/G.983.3 – Optical interface parameters of 155 Mbit/s downstream direction for the Basic Band** + +| Items | Unit | Specifications | | | +|---------------------------------------------------------------------------|--------|----------------------|---------|---------| +| OLT Transmitter (optical interface OId) | | | | | +| Nominal bit rate | Mbit/s | 155.52 | | | +| Operating wavelength | nm | 1480-1500 | | | +| Line code | – | Scrambled NRZ | | | +| Mask of the transmitter eye diagram | – | See Figure 6/G.983.1 | | | +| Maximum reflectance of equipment, measured at transmitter wavelength | dB | NA | | | +| Minimum ORL of ODN at O Id and O Iu (Notes 1 and 2) | dB | more than 32 | | | +| ODN Class | | Class A | Class B | Class C | +| Mean launched power MIN | dBm | Note 4 | Note 4 | Note 4 | +| Mean launched power MAX | dBm | Note 4 | Note 4 | Note 4 | +| Launched optical power without input to the transmitter | dBm | NA | | | +| Extinction ratio | dB | more than 10 | | | +| Tolerance to the transmitter incident light power | dB | more than –15 | | | +| If MLM Laser – Maximum RMS width | nm | 1.8 | | | +| If SLM Laser – Maximum –20 dB width (Note 3) | nm | 1 | | | +| If SLM Laser – Minimum side mode suppression ratio | dB | 30 | | | + +**Table 4b/G.983.3 – Optical interface parameters of 155 Mbit/s +downstream direction for the Basic Band (*concluded*)** + +| Items | Unit | Specifications | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------------|---------|---------| +| | | | | | +| ONU Receiver (optical interface Ord) | | | | | +| Maximum reflectance of equipment, measured at receiver wavelength | dB | less than –20 | | | +| Bit error ratio | – | less than $10^{-10}$ | | | +| ODN Class | | Class A | Class B | Class C | +| Minimum sensitivity | dBm | Note 4 | Note 4 | Note 4 | +| Minimum overload | dBm | Note 4 | Note 4 | Note 4 | +| Consecutive identical digit immunity | bit | more than 72 | | | +| Jitter tolerance | – | See Figure 9/G.983.1 | | | +| Tolerance to the reflected optical power | dB | 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/G.983.1.
NOTE 2 – The values on ONU transmitter reflectance for the case that 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 IV.
NOTE 3 – Values of maximum –20 dB width, and minimum side mode suppression ratio are referred to in ITU-T G.957.
NOTE 4 – Tentative parameters are described in Appendix I. | | | | | + +**Table 4c/G.983.3 – Optical interface parameters of 622 Mbit/s +downstream direction for the Basic Band** + +| Items | Unit | Specifications | | | +|---------------------------------------------------------------------------|--------|----------------------|---------|---------| +| | | | | | +| OLT Transmitter (optical interface Old) | | | | | +| Nominal bit rate | Mbit/s | 622.08 | | | +| Operating wavelength | nm | 1480-1500 | | | +| Line code | – | Scrambled NRZ | | | +| Mask of the transmitter eye diagram | – | See Figure 6/G.983.1 | | | +| Maximum reflectance of equipment, measured at transmitter wavelength | dB | NA | | | +| Minimum ORL of ODN at O lu and O ld (Notes 1 and 2) | dB | more than 32 | | | +| ODN Class | | Class A | Class B | Class C | +| Mean launched power MIN | dBm | Note 4 | Note 4 | Note 4 | +| Mean launched power MAX | dBm | Note 4 | Note 4 | Note 4 | +| Launched optical power without input to the transmitter | dBm | NA | | | +| Extinction ratio | dB | more than 10 | | | +| Tolerance to the transmitter incident light power | dB | more than –15 | | | +| If MLM Laser – Maximum RMS width | nm | NA | | | + +**Table 4c/G.983.3 – Optical interface parameters of 622 Mbit/s +downstream direction for the Basic Band (*concluded*)** + +| Items | Unit | Specifications | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------------|---------|---------| +| If SLM Laser – Maximum –20 dB width (Note 3) | nm | 1 | | | +| If SLM Laser – Minimum side mode suppression ratio | dB | 30 | | | +| ONU Receiver (optical interface Ord) | | | | | +| Maximum reflectance of equipment, measured at receiver wavelength | dB | less than –20 | | | +| Bit error ratio | – | less than $10^{-10}$ | | | +| ODN Class | | Class A | Class B | Class C | +| Minimum sensitivity | dBm | Note 4 | Note 4 | Note 4 | +| Minimum overload | dBm | Note 4 | Note 4 | Note 4 | +| Consecutive identical digit immunity | bit | more than 72 | | | +| Jitter tolerance | – | See Figure 9/G.983.1 | | | +| Tolerance to the reflected optical power | dB | 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/G.983.1. | | | | | +| NOTE 2 – The values on ONU transmitter reflectance for the case that 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 IV. | | | | | +| NOTE 3 – Values of maximum –20 dB width, and minimum side mode suppression ratio are referred to in ITU-T G.957. | | | | | +| NOTE 4 – Tentative parameters are described in Appendix I. | | | | | + +**Table 4d/G.983.3 – Optical interface parameters of 155 Mbit/s upstream direction** + +| Items | Unit | Specifications | | | +|---------------------------------------------------------------------------|--------|-------------------------------|---------|---------| +| ONU Transmitter (optical interface Oru) | | | | | +| Nominal bit rate | Mbit/s | 155.52 | | | +| Operating wavelength | nm | 1260-1360 | | | +| Line code | – | Scrambled NRZ | | | +| Mask of the transmitter eye diagram | – | See Figure 7/G.983.1 | | | +| Maximum reflectance of equipment, measured at transmitter wavelength | dB | less than –6 | | | +| Minimum ORL of ODN at O ru and O rd (Notes 1 and 2) | dB | more than 32 | | | +| ODN Class | | Class A | Class B | Class C | +| Mean launched power MIN | dBm | Note 4 | Note 4 | Note 4 | +| Mean launched power MAX | dBm | Note 4 | Note 4 | Note 4 | +| Launched optical power without input to the transmitter | dBm | less than Min sensitivity –10 | | | +| Extinction ratio | dB | more than 10 | | | + +**Table 4d/G.983.3 – Optical interface parameters of 155 Mbit/s upstream direction (concluded)** + +| Items | Unit | Specifications | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------|---------|---------|--|--|--| +| Tolerance to the transmitter incident light power | dB | more than –15 | | | | | | +| If MLM Laser – Maximum RMS width | nm | 5.8 | | | | | | +| If SLM Laser – Maximum –20 dB width (Note 3) | nm | 1 | | | | | | +| If SLM Laser – Minimum side mode suppression ratio | dB | 30 | | | | | | +| Jitter transfer | – | See Figure 8/G.983.1 | | | | | | +| Jitter generation from 0.5 kHz to 1.3 MHz | UI p-p | 0.2 | | | | | | +| OLT Receiver (optical interface Olu) | | | | | | | | +| Maximum reflectance of equipment, measured at receiver wavelength | dB | less than –20 | | | | | | +| Bit error ratio | – | less than $10^{-10}$ | | | | | | +| ODN Class | | Class A | Class B | Class C | | | | +| Minimum sensitivity | dBm | Note 4 | Note 4 | Note 4 | | | | +| Minimum overload | dBm | Note 4 | Note 4 | Note 4 | | | | +| Consecutive identical digit immunity | bit | more than 72 | | | | | | +| Jitter tolerance | – | NA | | | | | | +| Tolerance to the reflected optical power | dB | 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/G.983.1. | | | | | | | | +| NOTE 2 – The values of ONU transmitter reflectance for the case that 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 IV. | | | | | | | | +| NOTE 3 – Values of maximum –20 dB width, and minimum side mode suppression ratio are referred to in ITU-T G.957. | | | | | | | | +| NOTE 4 – Tentative parameters are described in Appendix I. | | | | | | | | + +### 8.3.2 Physical media and transmission method + +#### 8.3.2.1 Transmission medium + +This specification is based on the fibre described in ITU-T G.652. + +#### 8.3.2.2 Transmission direction + +The signal is transmitted both upstream and downstream through the transmission medium. + +#### 8.3.2.3 Transmission methodology + +Bidirectional transmission is accomplished by use of Wavelength Division Multiplexing (WDM) technique of 1310 nm region and Basic Band (1480-1500 nm) region wavelengths on a single fibre. + +### 8.3.3 Bit rate + +See 8.2.3/G.983.1. + +### **8.3.4 Line code** + +See 8.2.4/G.983.1. + +### **8.3.5 Operating wavelength** + +#### **8.3.5.1 Downstream direction** + +The operating wavelength range for the downstream direction on single fibre systems shall be 1480-1500 nm. + +#### **8.3.5.2 Upstream direction** + +The operating wavelength range for the upstream direction shall be 1260-1360 nm. + +### **8.3.6 Transmitter at Old and Oru** + +All parameters are specified as follows, and shall be in accordance with Table 4. + +See the following clauses in ITU-T G.983.1 for each item: + +- 8.2.6.1 for Source type; +- 8.2.6.2 for Spectral characteristics; +- 8.2.6.3 for Mean launched power; +- 8.2.6.3.1 for Launched optical power without input to the transmitter; +- 8.2.6.4 for Minimum extinction ratio; +- 8.2.6.6 for Mask of transmitter eye diagram; +- 8.2.6.6.1 for OLT transmitter; and +- 8.2.6.6.2 for ONU transmitter. + +#### **8.3.6.1 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 Old/Oru. It shall be in accordance with Table 4. + +#### **8.3.6.2 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 4. + +### **8.3.7 Optical path between Old/Oru and Ord/Olu** + +See the following clauses in ITU-T G.983.1 for each item: + +- 8.2.7.2 for Minimum optical return loss of the cable plant at point R/S, including any connector; and +- 8.2.7.3 for Maximum discrete reflectance between points S and R. + +#### **8.3.7.1 Attenuation range** + +Three classes of attenuation ranges are being specified as defined in ITU-T G.982: + +- 5-20 dB: Class A; +- 10-25 dB: Class B; +- 15-30 dB: Class C. + +Attenuation specifications are assumed to be worst-case values including losses due to splices, connectors, optical attenuators (if used) or other passive optical devices, and any additional cable margin to cover allowances for: + +- 1) future modifications to the cable configuration (additional splices, increased cable lengths, etc.); +- 2) fibre cable performance variations due to environmental factors; and +- 3) degradation of any connector, optical attenuators (if used) or other passive optical devices between points S and R, when provided. + +#### **8.3.7.2 Dispersion** + +Systems considered limited by dispersion have maximum values of dispersion (ps/nm) specified in Table 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. + +Systems considered limited by attenuation do not have maximum dispersion values specified and are indicated in Table 4 with the entry "NA" (not applicable). + +### **8.3.8 Receiver at $O_{rd}$ and $O_{lu}$** + +All parameters are specified as follows, and shall be in accordance with Table 4. + +See the following clauses in ITU-T G.983.1 for each item: + +- 8.2.8.1 for Minimum sensitivity; +- 8.2.8.2 for Minimum overload; +- 8.2.8.3 for Maximum optical path penalty; +- 8.2.8.5 for Differential optical path loss; +- 8.2.8.6 for Clock extraction capability; +- 8.2.8.7 for Jitter performance; +- 8.2.8.7.1 for Jitter transfer; +- 8.2.8.7.2 for Jitter tolerance; +- 8.2.8.7.3 for Jitter generation; +- 8.2.8.8 for Consecutive identical digit (CID) immunity; +- 8.2.8.9 for Tolerance to reflected power; and +- 8.2.8.10 for Transmission quality and error performance. + +#### **8.3.8.1 Maximum reflectance of receiver equipment, 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 4. + +## **8.4 Physical medium dependent layer requirements for the Enhancement Band** + +Optical parameters, line code, modulation scheme and so on for the Enhancement Band are out of scope of this Recommendation. + +However, reflection from ONU and OLT may cause signal degradation in the Enhancement Band services. Therefore the Maximum reflectance of equipment measured at transmitter wavelength and the Maximum reflectance of equipment measured at receiver wavelength for the ONU and the OLT should be specified in the Enhancement Band wavelength. The specification for reflectance of the ONU and OLT are for further study. + +# 9 Operations Administration and Maintenance (OAM) functionality + +See clause 9/G.983.1. + +# 10 Performance + +See clause 10/G.983.1. + +# 11 Environmental condition + +For the OLT and indoor ONU, the conditions of IEC 60721-3-3 are recommended. For the outdoor ONU, the conditions of IEC 60721-3-4, with the expanded environmental range (4.1E) specified in ETS 300 019-1-4, are recommended. + +The conditions of IEC 60801-2 and 60801-3 for electro magnetic compatibility are recommended. + +Examples of the applied environmental conditions for the OLT and ONU temperature and relative humidity are described in Table 5. The other environmental conditions such as environmental pollutants and chemicals are for further study. + +**Table 5/G.983.3 – Examples of environmental conditions** + +| Applied example | Temperature (C) | | Relative humidity (%) | | Remarks | +|----------------------|--------------------|------------------|-----------------------|------------------|----------------------------| +| | Normal | Short term | Normal | Short term | | +| OLT | 5 to 40 | 0 to 50 (Note 1) | 5 to 85 | 5 to 90 (Note 1) | IEC 60721-3-3 class 3k3 | +| Indoor ONU | –5 to 45 | – | 5 to 95 | – | IEC 60721-3-3 class 3k5 | +| Outdoor ONU (Note 2) | –45 to 45 (Note 3) | – | 8 to 100 | – | ETS 300 019-1-4 class 4.1E | + +NOTE 1 – Option 1: short term refers to a period of not more than 72 consecutive hours and a total of not more than 15 days in one year. + +Option 2: short term refers to a period of not more than 12 consecutive hours and a total of not more than four days in one year. + +NOTE 2 – The environmental conditions for the ONU are environmental conditions outside the ONU enclosure, and assume that the ONU (including housing/cabinet) is provided by a single supplier and is located in a conventional indoor or outdoor setting. Environmental conditions for ONUs that are located in other settings (e.g. inside an operator-provided cabinet or a non-conditioned indoor environment such as an attic or garage) are for future study. + +NOTE 3 – In many instances, network operators are willing to relax the low temperature requirement to –40 degrees. + +# 12 Safety + +Safety is defined in ITU-T G.983.1. + +# APPENDIX I + +## Optical interface parameters examples for ODN + +## I.1 Introduction + +Tentative optical parameters for ODN are described below (see Table 4) and are given in this Appendix I as examples for implementation. If appropriate parameters are approved and entered into Table 4, this Appendix will be removed. + +## I.2 Examples + +Specified numerical values described in the following table indicate tentative values for items described in Table 4. + +**Table I.1/G.983.3 – Optical interface parameters of 155 Mbit/s downstream direction for the Basic Band** + +| Items | Unit | Specifications | | | +|-----------------------------------------------------------|------|----------------|---------|---------| +| OLT Transmitter (optical interface Old) | | | | | +| ODN Class | | Class A | Class B | Class C | +| Mean launched power MIN | dBm | -7.5 | -2.5 | -0.5 | +| Mean launched power MAX | dBm | -3 | +2 | +4 | +| ONU Receiver (optical interface Ord) | | | | | +| ODN Class | | Class A | Class B | Class C | +| Minimum sensitivity | dBm | -28.5 | -28.5 | -31.5 | +| Minimum overload | dBm | -8 | -8 | -11 | + +**Table I.2/G.983.3 – Optical interface parameters of 622 Mbit/s downstream direction for the Basic Band** + +| Items | Unit | Specifications | | | +|-----------------------------------------------------------|------|----------------|---------|---------| +| OLT Transmitter (optical interface Old) | | | | | +| ODN Class | | Class A | Class B | Class C | +| Mean launched power MIN | dBm | -5.5 | -0.5 | -0.5 | +| Mean launched power MAX | dBm | -1 | +4 | +4 | +| ONU Receiver (optical interface Ord) | | | | | +| ODN Class | | Class A | Class B | Class C | +| Minimum sensitivity | dBm | -26.5 | -26.5 | -31.5 | +| Minimum overload | dBm | -6 | -6 | -11 | + +**Table I.3/G.983.3 – Optical interface parameters of 155 Mbit/s +upstream direction** + +| Items | Unit | Specifications | | | +|-----------------------------------------------------------------------------------------------------------------------------|------|----------------|---------|-------------------| +| ONU Transmitter (optical interface Oru) | | | | | +| ODN Class | | Class A | Class B | Class C
(Note) | +| Mean launched power MIN | dBm | -7.5 | -5.5 | -3.5 | +| Mean launched power MAX | dBm | 0 | +2 | +4 | +| OLT Receiver (optical interface Olu) | | | | | +| ODN Class | | Class A | Class B | Class C
(Note) | +| Minimum sensitivity | dBm | -28.5 | -31.5 | -34.5 | +| Minimum overload | dBm | -5 | -8 | -11 | +| NOTE – The values proposed for the upstream Class C are best estimates. They are therefore subject to change in the future. | | | | | + +# APPENDIX II + +## Deployment scenarios + +## II.1 Introduction + +It is assumed that various system configurations or scenarios will be introduced by telecom operators. These system configurations or scenarios are influenced by regulations, service strategy, and the geographic conditions for each telecom operator. These configurations include pure WDM-based overlays and those which rely on FDM techniques to separate the Basic Band and Enhancement Band signals. + +Configuration examples are described below. + +## II.2 Configuration examples + +### II.2.1 Case 1: Reception of Basic Band only + +If customers do not require additional services such as video service etc. over the Enhancement Band under the wavelength allocation of Figure 5, then two system configurations would be as shown in Figures II.1 and II.2. In the case of Figure II.1, the WDM blocking filter may be needed to prevent the signal in the Enhancement Band from reaching the ONU. In the case of Figure II.2, an FDM-based approach, newer version ONUs, which are equipped with an electrical bandsplit filter, are required. + +![Block diagram of Figure II.1/G.983.3 showing the reception of the basic band only by a blocking filter. On the left, an ONU (for Basic Band) contains Logic, Tx, Rx, and WDM-N components. The output of the WDM-N passes through a Blocking Filter. The output of the Blocking Filter is connected to a WDM (WF1) or Combiner. This combiner receives two inputs from the right: one from an OLT (for Basic Band) and another from an E-OLT (for Enhancement Band). The OLT (for Basic Band) contains WDM-L, Tx, Rx, and Logic components. The E-OLT (for Enhancement Band) contains a Tx component. The diagram is labeled T1543840-01.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +Block diagram of Figure II.1/G.983.3 showing the reception of the basic band only by a blocking filter. On the left, an ONU (for Basic Band) contains Logic, Tx, Rx, and WDM-N components. The output of the WDM-N passes through a Blocking Filter. The output of the Blocking Filter is connected to a WDM (WF1) or Combiner. This combiner receives two inputs from the right: one from an OLT (for Basic Band) and another from an E-OLT (for Enhancement Band). The OLT (for Basic Band) contains WDM-L, Tx, Rx, and Logic components. The E-OLT (for Enhancement Band) contains a Tx component. The diagram is labeled T1543840-01. + +Figure II.1/G.983.3 – Reception of Basic Band only by blocking filter + +![Block diagram of Figure II.2/G.983.3 showing the reception of the basic band only by an FDM-based approach. On the left, an ONU (for Basic Band) contains Logic, Lo, Hi, Tx, Rx, and WDM-N components. The output of the WDM-N passes through a Combiner (first stage of 2:N splitter). This combiner receives two inputs from the right: one from an OLT (for Basic Band) and another from an E-OLT (for Enhancement Band). The OLT (for Basic Band) contains WDM-L, Tx, Rx, and Logic components. The E-OLT (for Enhancement Band) contains a Tx component. The diagram is labeled T1543850-01.](dcf37c460c66ec011dbe6ca08de44ff9_img.jpg) + +Block diagram of Figure II.2/G.983.3 showing the reception of the basic band only by an FDM-based approach. On the left, an ONU (for Basic Band) contains Logic, Lo, Hi, Tx, Rx, and WDM-N components. The output of the WDM-N passes through a Combiner (first stage of 2:N splitter). This combiner receives two inputs from the right: one from an OLT (for Basic Band) and another from an E-OLT (for Enhancement Band). The OLT (for Basic Band) contains WDM-L, Tx, Rx, and Logic components. The E-OLT (for Enhancement Band) contains a Tx component. The diagram is labeled T1543850-01. + +Figure II.2/G.983.3 – Reception of Basic Band only by FDM-based approach + +### II.2.2 Case 2: Reception of Basic Band and Enhancement Band signals by separate ONUs + +If operators provide both ATM-PON and additional services such as video service etc. in separate equipment modules, the WDM-based system configuration would be Figure II.3. + +![Figure II.3/G.983.3 – Reception of Basic Band and Enhancement Band signals by separate ONUs. The diagram shows a separate ONU for the Basic Band and an E-ONU for the Enhancement Band connected to a central WDM (WF2) unit. The WDM (WF2) is connected to a WDM (WF1) or Combiner, which is then connected to an OLT for the Basic Band and an E-OLT for the Enhancement Band. The ONU (for Basic Band) contains Logic, Tx, Rx, and WDM-N components. The E-ONU (for Enhancement Band) contains an Rx component. The OLT (for Basic Band) contains WDM-L, Tx, Rx, and Logic components. The E-OLT (for Enhancement Band) contains a Tx component. A small text 'T1543860-01' is visible in the bottom right corner of the diagram.](14252bcd35912bd656e98b16b2ee51c0_img.jpg) + +Figure II.3/G.983.3 – Reception of Basic Band and Enhancement Band signals by separate ONUs. The diagram shows a separate ONU for the Basic Band and an E-ONU for the Enhancement Band connected to a central WDM (WF2) unit. The WDM (WF2) is connected to a WDM (WF1) or Combiner, which is then connected to an OLT for the Basic Band and an E-OLT for the Enhancement Band. The ONU (for Basic Band) contains Logic, Tx, Rx, and WDM-N components. The E-ONU (for Enhancement Band) contains an Rx component. The OLT (for Basic Band) contains WDM-L, Tx, Rx, and Logic components. The E-OLT (for Enhancement Band) contains a Tx component. A small text 'T1543860-01' is visible in the bottom right corner of the diagram. + +**Figure II.3/G.983.3 – Reception of Basic Band and Enhancement Band signals by separate ONUs** + +### II.2.3 Case 3: Reception of Basic Band and Enhancement Band signals by integrated ONUs + +If operators provide both ATM-PON and additional services such as video service etc. in the same equipment, then two system configurations would be as shown in Figures II.4 and II.5. Figure II.4 shows a WDM-based approach. This type's ONUs are equipped with WDM filter. Figure II.5 shows FDM-based approach. This type's ONUs are equipped with electrical bandsplit filter. + +![Figure II.4/G.983.3 – Reception of Basic Band and Enhancement Band signals by integrated ONUs (WDM-based approach). The diagram shows an integrated ONU (Basic Band and Video Receiver) connected to a central WDM (WF2) unit. The WDM (WF2) is connected to a WDM (WF1) or Combiner, which is then connected to an OLT (combined Basic Band and Enhancement Band). The ONU contains two main sections: 'for Basic Band' (Logic, Tx, Rx, WDM-N) and 'for Enhancement Band' (Rx). The OLT also contains two main sections: 'for Basic Band' (WDM-L, Tx, Rx, Logic) and 'or Enhancement Band' (Tx). A small text 'T1543870-01' is visible in the bottom right corner of the diagram.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) + +Figure II.4/G.983.3 – Reception of Basic Band and Enhancement Band signals by integrated ONUs (WDM-based approach). The diagram shows an integrated ONU (Basic Band and Video Receiver) connected to a central WDM (WF2) unit. The WDM (WF2) is connected to a WDM (WF1) or Combiner, which is then connected to an OLT (combined Basic Band and Enhancement Band). The ONU contains two main sections: 'for Basic Band' (Logic, Tx, Rx, WDM-N) and 'for Enhancement Band' (Rx). The OLT also contains two main sections: 'for Basic Band' (WDM-L, Tx, Rx, Logic) and 'or Enhancement Band' (Tx). A small text 'T1543870-01' is visible in the bottom right corner of the diagram. + +**Figure II.4/G.983.3 – Reception of Basic Band and Enhancement Band signals by integrated ONUs (WDM-based approach)** + +![Block diagram of the FDM-based approach for receiving Basic and Enhancement Band signals. On the left, an ONU (for Basic Band and Enhancement Band) contains a Logic block, a Pass band Amp, a Hi block, a Lo block, a Tx block, an Rx block, and a WDM-N block. The ONU is connected to a Combiner (first stage of 2:N splitter). The Combiner is connected to an OLT (for Basic Band) and an E-OLT (for Enhancement Band). The OLT contains a WDM-L block, a Tx block, an Rx block, and a Logic block. The E-OLT contains a Tx block. The diagram is labeled T1543880-01.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +The diagram illustrates the signal flow for receiving Basic and Enhancement Band signals using an FDM-based approach. On the left, the ONU (for Basic Band and Enhancement Band) is shown with its internal components: Logic, Pass band Amp, Hi, Lo, Tx, Rx, and WDM-N. The ONU's output is connected to a Combiner (first stage of 2:N splitter). The Combiner's output is split into two paths: one to the OLT (for Basic Band) and another to the E-OLT (for Enhancement Band). The OLT contains a WDM-L block, a Tx block, an Rx block, and a Logic block. The E-OLT contains a Tx block. The diagram is labeled T1543880-01. + +Block diagram of the FDM-based approach for receiving Basic and Enhancement Band signals. On the left, an ONU (for Basic Band and Enhancement Band) contains a Logic block, a Pass band Amp, a Hi block, a Lo block, a Tx block, an Rx block, and a WDM-N block. The ONU is connected to a Combiner (first stage of 2:N splitter). The Combiner is connected to an OLT (for Basic Band) and an E-OLT (for Enhancement Band). The OLT contains a WDM-L block, a Tx block, an Rx block, and a Logic block. The E-OLT contains a Tx block. The diagram is labeled T1543880-01. + +**Figure II.5/G.983.3 – Reception of Basic Band and Enhancement Band signals by integrated ONUs (FDM-based approach)** + +### II.2.4 Case 4: Arrangement of WDMs to minimize upstream path loss + +This arrangement is aimed at minimizing the upstream path loss (at 1300 nm) when an Enhancement Band is added. In this case WDM-L and WDM-N separate the 1300 nm and 1500 nm bands and WF1 and WF2 split the 1500 nm band. This allows existing upstream transmitters and receivers to be used without a change in the end-to-end loss. The performance of WF1 and WF2 needs only to be specified in the 1500 nm band since 1300 nm signals are eliminated. It avoids the problem of near-end crosstalk when the Enhancement Band carries a downstream-only service. It avoids problems of reflections in the Basic Band being a problem to the Enhancement Band receivers. A disadvantage of this approach is that it is unsuitable for use with Basic Band electro-optic modules that incorporate G.983.1 WDMs. + +![Figure II.6/G.983.3 – Arrangement of WDMs to minimize upstream path loss. The diagram shows two optical network units (ONUs) on the left and an optical line terminal (OLT) on the right, connected via an optical distribution network (ODN). The top ONU contains an 'ONU (Basic Band)' and an 'E-ONU' connected to a 'WF2' filter, which is connected to a 'WDM-N' unit. The bottom ONU contains an 'AF' (attenuator/filter) connected to an 'ONU (Basic Band)' and a 'WF2' filter, which is connected to a 'WDM-N' unit. Both 'WDM-N' units connect to the 'ODN'. The 'ODN' connects to the 'OLT' through 'R/S' (receive/split) and 'S/R' (split/receive) interfaces. The 'OLT' contains a 'WDM-L' unit connected to a 'WF1' filter, which is connected to an 'OLT (Basic Band)' and an 'E-OLT'. The 'OLT (Basic Band)' is connected to a 'Service Node function' via an 'SNI' (service network interface). Reference points '(T_B)/(T)' are indicated at the far left and far right of the diagram. A label 'T1543890-01' is present in the bottom right corner of the diagram area.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +Figure II.6/G.983.3 – Arrangement of WDMs to minimize upstream path loss. The diagram shows two optical network units (ONUs) on the left and an optical line terminal (OLT) on the right, connected via an optical distribution network (ODN). The top ONU contains an 'ONU (Basic Band)' and an 'E-ONU' connected to a 'WF2' filter, which is connected to a 'WDM-N' unit. The bottom ONU contains an 'AF' (attenuator/filter) connected to an 'ONU (Basic Band)' and a 'WF2' filter, which is connected to a 'WDM-N' unit. Both 'WDM-N' units connect to the 'ODN'. The 'ODN' connects to the 'OLT' through 'R/S' (receive/split) and 'S/R' (split/receive) interfaces. The 'OLT' contains a 'WDM-L' unit connected to a 'WF1' filter, which is connected to an 'OLT (Basic Band)' and an 'E-OLT'. The 'OLT (Basic Band)' is connected to a 'Service Node function' via an 'SNI' (service network interface). Reference points '(T\_B)/(T)' are indicated at the far left and far right of the diagram. A label 'T1543890-01' is present in the bottom right corner of the diagram area. + +**Figure II.6/G.983.3 – Arrangement of WDMs to minimize upstream path loss** + +### II.2.5 Case 5: ODNs with reduced attenuation range for Enhancement Band + +A problem for some operators arises when an existing Class C ODN is deployed. This is specified to have 30 dB path loss in both the 1300 and 1500 nm windows. Existing Basic Band transceivers will not have sufficient power budget when WDM components are added externally. + +Case 4 could avoid this problem for the upstream path when the upstream and downstream transmitters and receivers are available as separate modules. + +The downstream path will have additional losses for the WDMs in the 1500 nm band which could be as high as 1.5 dB at each end. This means that the 1500 nm transmitters and receivers need 3 dB extra power budget. One way of compensating this 3 dB is to apply a modified Class C, which takes into account the differential losses of the fibre in the 1300 and 1500 nm windows. The maximum loss at 1300 nm is 30 dB and the maximum loss at 1500 nm is 27 dB. Many existing Class C ODNs and all Class C with reduced attenuation range could meet a specification having less than 27 dB loss in the 1480-1580 nm band and less than 30 dB loss in the 1260-1360 nm band. + +### II.2.6 Example in case of insufficiency of loss budget between E-ONU and E-OLT + +In case of insufficiency of loss budget between E-ONU and E-OLT, it is possible to shorten the distance between E-ONU and E-OLT. Figure II.7 shows an example. In that case, output from E-OLT is inputted to second stage of splitter. + +![Figure II.7/G.983.3 – Arrangement in case of insufficiency of loss budget between E-ONU and E-OLT. The diagram shows a network topology where an ONU and an E-ONU are connected to a WDM (WF2) filter. The WDM filter has a reflector/splitter (R/S) output. The ONU is connected to the WDM filter via point E, and the E-ONU is connected via point F. The WDM filter's R/S output is connected to a splitter. One output of this splitter is connected to an OLT via point C, and the other output is connected to an E-OLT via point D. The E-OLT's output is connected to a second stage of splitter. The diagram is labeled T1543900-01.](dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg) + +The diagram illustrates a fiber optic network arrangement. On the left, two optical units, ONU and E-ONU, are connected to a Wavelength Division Multiplexer (WDM) labeled (WF2). The ONU connects at point E, and the E-ONU connects at point F. The WDM has a reflector/splitter (R/S) output. This output connects to a first splitter. One output of this first splitter connects to an Optical Line Terminal (OLT) at point C. The other output of the first splitter connects to an Ethernet Optical Line Terminal (E-OLT) at point D. The E-OLT's output is then connected to a second splitter. The diagram is labeled T1543900-01. + +Figure II.7/G.983.3 – Arrangement in case of insufficiency of loss budget between E-ONU and E-OLT. The diagram shows a network topology where an ONU and an E-ONU are connected to a WDM (WF2) filter. The WDM filter has a reflector/splitter (R/S) output. The ONU is connected to the WDM filter via point E, and the E-ONU is connected via point F. The WDM filter's R/S output is connected to a splitter. One output of this splitter is connected to an OLT via point C, and the other output is connected to an E-OLT via point D. The E-OLT's output is connected to a second stage of splitter. The diagram is labeled T1543900-01. + +**Figure II.7/G.983.3 – Arrangement in case of insufficiency of loss budget between E-ONU and E-OLT** + +# APPENDIX III + +## Isolation between the Basic Band and the Enhancement Band + +## III.1 Introduction + +The Enhancement Band can be used for many different types of services, such as video distribution and digital high bit-rate services. + +Each service (characterized by modulation format or bit rate, the amount of carriers or amount of wavelengths) will require its own Enhancement Band receiver sensitivity and allowable cross-talk from the Basic Band signal. + +These parameters, together with the total optical power in the Enhancement Band, will in turn determine the necessary isolation value at the Enhancement Band receiver from the Basic Band signal, and the necessary isolation value at the Basic Band receiver from the Enhancement Band signal. + +In general, "Isolation" is defined as the loss difference between two wavelengths measured at the same port. Required Isolation for WDM filter such as WF1 and WF2 should be estimated considering reflections of equipment and/or ODN. The effect of reflections is described in Appendix IV. + +This appendix provides some initial calculations of the optical characteristics of the Enhancement Band services. These are used to find example isolation values of the Basic Band from the Enhancement Band. Such examples may be useful to vendors in guiding their development efforts. However, the exact requirements of the isolation values, and the isolation required by the enhancement signals from the Basic Band depend on many factors that are out of the scope of this Recommendation. Any system design will need to do a complete accounting of all these factors to arrive at a complete optical isolation specification. + +Isolation to be considered is schematically shown in Figure III.1. + +![Schematic diagram of optical isolation at WDM-L, WDM-N, WF1, and WF2 components in a PON system. The diagram shows signal paths for Basic and Enhancement bands between an ONU/E-ONU and an OLT/E-OLT through WDM filters. Detailed insets show the internal signal flow and isolation characteristics of each component.](e451401f8fa77b466f401d5fce15b26c_img.jpg) + +The diagram illustrates the signal paths and isolation characteristics of WDM components in a PON system. At the top, an ONU (for Basic Band) and an E-ONU (for Enhancement Band) are connected to a WDM filter (WF2). WF2 is connected via a splitter to another WDM filter (WF1), which is then connected to an OLT (for Basic Band) and an E-OLT (for Enhancement Band). Green arrows indicate the primary signal flow: Basic Band (downstream) from OLT to ONU, and Basic Band (upstream) from ONU to OLT. Enhancement Band signals flow from E-OLT to E-ONU and back. + +Below the main schematic, four detailed insets show the internal signal flow and isolation for each component: + +- WDM-N (at the ONU side):** Shows the separation of Basic Band (downstream, red) and Basic Band (upstream, grey) signals. It also highlights isolation from the Enhancement Band (leak signal, blue) and reflection signals (red arrows). +- WF2:** Shows the isolation between the Basic Band (downstream, red) and Basic Band (upstream, grey) signals, as well as the Enhancement Band (blue). It details leak signals and reflection signals. +- WF1:** Shows the isolation at the OLT side, separating Basic Band (downstream, red) and Basic Band (upstream, grey) signals from the Enhancement Band (blue) and reflection signals. +- WDM-L (at the OLT side):** Shows the isolation for the OLT's Basic Band signals (downstream, red; upstream, grey) from the Enhancement Band (blue) and reflection signals. + +Schematic diagram of optical isolation at WDM-L, WDM-N, WF1, and WF2 components in a PON system. The diagram shows signal paths for Basic and Enhancement bands between an ONU/E-ONU and an OLT/E-OLT through WDM filters. Detailed insets show the internal signal flow and isolation characteristics of each component. + +T1543910-01 + +Figure III.1/G.983.3 – Isolation at WDM-L, WDM-N, WF1 and WF2 + +The type of service and its characteristics will determine isolation performances of WF1 and WF2. As the optical power of the Basic Band signal will vary with the PON system class (A, B, C), the isolation values will also be different for the different ODN classes. + +Out of the many different service and class scenarios, several isolation classes could then be defined. The following tables illustrate several service scenarios. The scenarios have to be analysed for each PON Class. + +The following notations are used in this appendix: + +| | | +|--------------|--------------------------------------------------------------------| +| $L_{ODN-BB}$ | Optical loss of Basic Band in the ODN | +| $L_{ODN-EB}$ | Optical loss of Enhancement Band in the ODN | +| $P_{BB}$ | Optical power of Basic Band signal at the input to the ONU | +| $P_{EB}$ | Optical Power of Enhancement Band signal at the input to the E-ONU | +| F.F.S | for further study | + +The following assumptions are taken for the examples: + +- $L_{ODN-BB} = L_{ODN-EB}$ . +- The allowable cross-talk at the Basic Band receiver [at reference points (c) and (e)] from the Enhancement Band signal is assumed to be at least 10 dB lower than the lowest Basic Band signal. + +NOTE – This assumption should be modified to some higher value than 10 dB, for example to 13 dB, because the total optical noise to the receiver consists of multiple reflections as well as leak optical power. Permissible total noise may be 10 dB lower than the lowest signal level, but permissible noise power for each noise component is for further study. Therefore, the following are tentatively described on the assumption that each noise component be at least 10 dB lower than the signal. + +- Assuming following WF1 and WF2 insertion losses: 0 dB – 1.5 dB. + +## III.2 Example for required isolation at Basic Band receiver from Enhancement Band signal + +### III.2.1 Video services + +Required isolation depends on the minimum power required by the receiver to produce a usable signal plus the total amount of system tolerance (transmitter, fibre, and optical component loss variations). For subcarrier multiplexed video systems, the carrier-to-noise ratio (CNR) is given by Equation (III-1). + +$$CNR = \frac{1}{2B} \cdot \frac{m^2}{RIN + \frac{2e}{i} + \frac{4kT}{i^2 R}} \quad (III-1)$$ + +Here $B$ is the channel bandwidth, $m$ is the per-channel modulation index, $RIN$ is the relative intensity noise of the transmitter, $e$ is the charge of the electron, $i$ is the detected photocurrent, $kT$ is the Boltzman factor, and $R$ is the receiver impedance. The assumed values for all these parameters are given in the following table: + +| | | +|---------------------------------|--------| +| RIN (dB/Hz) | –150.0 | +| Receiver Temperature (K) | 300.0 | +| Receiver Impedance ( $\Omega$ ) | 75.0 | +| Receiver Responsivity (A/W) | 0.85 | +| RMS OMI | 25% | + +The required SNR depends on the signal format being considered. The values assumed here are given in the following table: + +| Channel Format | (dB) | +|-----------------------------------------------|-----------| +| QPSK | 16 | +| 16-QAM | 22 | +| 64-QAM | 28 | +| 256-QAM | 34 | +| AM-VSB | 44 (Note) | +| NOTE – The value given for AM-VSB is the CNR. | | + +The RMS optical modulation index (*OMI*), along with *N*, the number of channels, can be used to compute *m*, by using Equation (III-2). The responsivity is used to convert the photocurrent to optical power. + +$$m = OMI \sqrt{\frac{2}{N}} \quad (\text{III-2})$$ + +Equation (III-1) can be re-arranged as shown in Equation (III-3). This gives a quadratic in photocurrent, and the solution to this equation then can be converted into the required optical power, *PEB*, at the point between the E-ONU and WF2, shown in Table III.1. + +$$\left( RIN - \frac{m^2}{2B \cdot CNR} \right) i^2 + 2ei + \frac{4kT}{R} = 0 \quad (\text{III-3})$$ + +**Table III.1/G.983.3 – *PEB*, minimal power of Enhancement Band signal at the input to the E-ONU** + +| Transmission System | Carrier Format | Number of carriers | Carrier BW (MHz) | Required Power (dBm) | +|---------------------|----------------|--------------------|------------------|----------------------| +| SCM | AM-VSB | 40 | 4.5 | -7.7 | +| | | | 6.5 | -6.7 | +| | QPSK | 60 | 18 | -18.3 | +| | 64-QAM | 110 | 5.2 | -13.6 | +| | | | 7.0 | -13.0 | +| | 256-QAM | 110 | 5.2 | -10.5 | +| | | | 7.0 | -9.8 | +| FM Conversion | AM-VSB | 40 | 4.5 | -14.1 | +| | | | 6.5 | -11.5 | +| | 64-QAM | 110 | 5.2 | -16.7 | +| | | | 7.0 | -14.3 | +| | 256-QAM | 110 | 5.2 | -13.3 | +| | | | 7.0 | -10.1 | + +The isolation values at WF2 (the ratio of leaked Enhancement Band signal to ONU from Enhancement Band signal at common port of WF2) are obtained from: + +$$\text{Isolation of WF2} = P_{\text{EB req}} + R_{\Delta} + T_{\Delta} - P_{\text{BB min}} + 13 \text{ dB},$$ + +where $R_{\Delta}$ and $T_{\Delta}$ are the dynamic range tolerances of the receiver and transmitter. We assume values of $R_{\Delta} = 2 \text{ dB}$ , and $T_{\Delta} = 1 \text{ dB}$ . + +For example, if the minimum required enhancement power at the E-ONU receiver, $P_{\text{EB req}} = -10 \text{ dBm}$ and $P_{\text{BB min}} = -30 \text{ dBm}$ , then required isolation = 36 dB. + +The resulting isolation at WF2 is specified in Table III.2. These are assuming that $P_{\text{BB min}} = -30 \text{ dBm}$ , which is true for class B equipment. Note that the above calculation assumes that the enhancement and Basic Band signals suffer the same insertion loss through WF2. + +**Table III.2/G.983.3 – Isolation requirements at Basic Band receiver from Enhancement Band** + +| Transmission System | Carrier Format | Number of carriers | Carrier BW (MHz) | Required Isolation (dB) | +|---------------------|----------------|--------------------|------------------|-------------------------| +| SCM | AM-VSB | 40 | 4.5 | 38.3 | +| | | | 6.5 | 39.3 | +| | QPSK | 60 | 18 | 27.7 | +| | 64-QAM | 110 | 5.2 | 32.4 | +| | | | 7.0 | 33.0 | +| | 256-QAM | 110 | 5.2 | 35.5 | +| | | | 7.0 | 36.2 | +| FM Conversion | AM-VSB | 40 | 4.5 | 31.9 | +| | | | 6.5 | 34.5 | +| | 64-QAM | 110 | 5.2 | 29.3 | +| | | | 7.0 | 31.7 | +| | 256-QAM | 110 | 5.2 | 32.7 | +| | | | 7.0 | 35.9 | + +The isolation required at WF1 is driven by the reflections in the PON, which can be either $-32 \text{ dB}$ or $-20 \text{ dB}$ . The video transmitter will most likely be operating near the SBS limit of the fibre, implying a maximum launch power of $+17 \text{ dBm}$ . With a reflection loss of $-20 \text{ dB}$ , the reflection can be as high as $-3 \text{ dBm}$ . If the signal must be 13 dB higher than the interference, then the combined isolation of the WF1 and diplexer must be 40 dB. If PON reflectance of $-32 \text{ dB}$ is assumed, then the isolation of WF1 and diplexer must be 28 dB. + +Note that the above isolations assume that the video and Basic Band signals overlap in electrical frequency. This is not necessarily true, and in some notable cases, such as the QPSK video, the video signal is entirely out of band. In these cases, the video signal only impairs the Basic Band signal via increased shot and relative intensity noise. This can reduce the required isolation greatly, in some cases to the point where no optical isolation is required at all. + +### III.2.2 DWDM services + +The provision of DWDM services over the PON will also place requirements on the isolation of filters WF1 and WF2. The starting point again is the sensitivities of the receivers that would be used for the DWDM upgrade. Table III.3 below gives the typical values for optical receivers, and also for the filters that are required to demultiplex the individual channels. + +**Table III.3/G.983.3 – The typical values for optical receivers and filters** + +| Table a – Data Rate | SDH-1 | SDH-4 | GbE | SDH-16 | +|--------------------------------------------|--------------|--------------|------------|---------------| +| Maximum overload (PIN photodiode) (dBm) | -8 | -7 | -6 | -4 | +| Minimum sensitivity (PIN photodiode) (dBm) | -36 | -31 | -25 | -20 | +| Maximum overload (APD) (dBm) | NA | -10 | -9 | -9 | +| Minimum sensitivity (APD) (dBm) | NA | -38 | -33 | -29 | + +| Table b – Number of Channels | 1 | 8 | 16 | 32 | +|----------------------------------------|----------|----------|-----------|-----------| +| 200 GHz Filter max loss (dB) | 2 | 3.5 | 5 | NA | +| 100 GHz Filter Max loss (dB) | 2.5 | 4.5 | 6.5 | 8.5 | +| Basic/Enhancement Filter max loss (dB) | 1 | NA | NA | NA | + +By building hypothetical loss budgets using these numbers, one can derive the maximum launched powers (per channel) at both ends of the PON. The result depends on the speed and number of channels, as shown in Table III.4. Note that the upstream launch powers are higher than the downstream powers because the upstream channels must pass through the lossy multichannel WDM demultiplexer, while the downstream channels only pass through a single WDM filter. + +**Table III.4/G.983.3 – The maximal Tx power of Enhancement Band signal at IFPON** + +**a – just after the WF1 going downstream** + +| Channels | PIN (dBm) | | APD (dBm) | | +|-----------------|------------------|--------------|------------------|---------------| +| | SDH-1 | SDH-4 | GbE | SDH-16 | +| 4 | -4.5 | 0.5 | -1.5 | 2.5 | +| 8 | -4.5 | 0.5 | -1.5 | 2.5 | +| 16 | -4.0 | 1.0 | -1.0 | 3.0 | + +**b – just after WF2 going upstream** + +| Channels | PIN (dBm) | | APD (dBm) | | +|-----------------|------------------|--------------|------------------|---------------| +| | SDH-1 | SDH-4 | GbE | SDH-16 | +| 4 | -2.0 | 3.0 | 1.0 | 4.8 | +| 8 | -1.5 | 3.5 | 1.5 | 5.0 | +| 16 | 2.0 | 7.0 | 5.0 | 6.8 | + +The isolation values are obtained by first computing the maximum Enhancement Band power entering either WF1 or WF2. The two sources of this power are the forward path power (upstream in the case of WF1) and the reflection path power (downstream in the case of WF1). These powers are summed arithmetically, including the multiplier for the number of channels involved, and produce the interfering power. The worst case of this interfering power is then compared with the worst case of the Basic Band power. Their difference plus 13 dB is then the required isolation. The isolations for WF1 and WF2 are specified in Table III.5 assuming a class B PON. Note that the isolation stated for WF1 also includes whatever isolation that the diplexer provides inside the OLT, hence the actual isolation required of WF1 is actually less. + +**Table III.5/G.983.3 – Isolation requirements at Basic Band receiver from Enhancement Band** + +#### **a – for WF1** + +| Channels | PIN (dB) | | APD (dB) | | +|----------|----------|-------|----------|--------| +| | SDH-1 | SDH-4 | GbE | SDH-16 | +| 4 | 37.3 | 42.3 | 40.3 | 44.0 | +| 8 | 40.7 | 45.7 | 43.7 | 47.3 | +| 16 | 47.1 | 52.1 | 50.1 | 52.0 | + +#### **b – for WF2** + +| Channels | PIN (dB) | | APD (dB) | | +|----------|----------|-------|----------|--------| +| | SDH-1 | SDH-4 | GbE | SDH-16 | +| 4 | 20.8 | 25.8 | 23.8 | 27.8 | +| 8 | 24.0 | 29.0 | 27.0 | 30.8 | +| 16 | 28.6 | 33.6 | 31.6 | 34.6 | + +## **III.3 Example of isolation classes** + +Possible isolation classes for the ONU WF2 filter are shown in Table III.6. It would appear that 30 dB of isolation is sufficient for most all of the DWDM upgrades, and some of the video upgrades. Hence, this could define the first class of isolation. For exceptional cases of DWDM upgrade, or for many of the video upgrades, 40 dB of isolation is required. This could define the second class of isolation. + +**Table III.6/G.983.3 – Isolation Classes** + +| | | Guaranteed Isolation | | +|-----------------|--------|----------------------|--------------------| +| | | at EB from BB (dB) | at BB from EB (dB) | +| Isolation Class | Case 1 | F.F.S | 30 | +| | Case 2 | F.F.S | 40 | +| | Case 3 | F.F.S | F.F.S | + +## III.4 Deployment examples + +This clause shows examples of WDM filters' characteristics such as power loss and isolation in deploying this system. + +### III.4.1 Model to be considered + +Figure III.2 shows an example of model. + +In order to calculate the value of isolation, the SNR of three receivers such as OLT-Rx, ONU-Rx and E-Rx should be considered. For that, each amount of interference optical power and the power of signal should be considered. + +![Figure III.2/G.983.3 – Model for calculation. This diagram shows a network model with two main sites: ONU site and OLT site. The ONU site contains ONU Tx, ONU Rx, and E-Rx connected to a WDM-N filter. The WDM-N filter has Port T (connected to ONU Tx), Port R (connected to ONU Rx), and Port E (connected to E-Rx). Port A of WDM-N is connected to Port C of WDM (WF2). The ODN (Optical Distribution Network) is represented by a pink oval between Port C of WDM (WF2) and Port C of WDM (WF1). Port A of WDM (WF1) is connected to Port T of WDM-L. The OLT site contains OLT Tx, ONU Rx, and E-Tx connected to the WDM-L filter. The WDM-L filter has Port T (connected to OLT Tx), Port R (connected to ONU Rx), and Port E (connected to E-Tx). A label 'T1543920-01' is present in the bottom right corner of the diagram area.](e05122559f56af5699789b7118d8fe87_img.jpg) + +Figure III.2/G.983.3 – Model for calculation. This diagram shows a network model with two main sites: ONU site and OLT site. The ONU site contains ONU Tx, ONU Rx, and E-Rx connected to a WDM-N filter. The WDM-N filter has Port T (connected to ONU Tx), Port R (connected to ONU Rx), and Port E (connected to E-Rx). Port A of WDM-N is connected to Port C of WDM (WF2). The ODN (Optical Distribution Network) is represented by a pink oval between Port C of WDM (WF2) and Port C of WDM (WF1). Port A of WDM (WF1) is connected to Port T of WDM-L. The OLT site contains OLT Tx, ONU Rx, and E-Tx connected to the WDM-L filter. The WDM-L filter has Port T (connected to OLT Tx), Port R (connected to ONU Rx), and Port E (connected to E-Tx). A label 'T1543920-01' is present in the bottom right corner of the diagram area. + +**Figure III.2/G.983.3 – Model for calculation** + +#### III.4.1.1 SNR of OLT-Rx + +Figure III.3 shows the noise signals received at OLT-Rx receiver. + +![Figure III.3/G.983.3 – Noise signals at OLT-Rx. This diagram illustrates the noise signals at the OLT-Rx receiver. The ODN is connected to WDM WF1, which is connected to WDM-L. The WDM-L filter has Port T (connected to OLT Tx), Port R (connected to OLT Rx), and Port E (connected to E-Tx). The OLT Rx receives several signals: Su (Basic Band Signal (upstream)), XL (Amount of interference optical power for OLT Receiver), XLdl (Leak signal of downstream), XLdr (Reflection signal of downstream), XLvl (Leak signal of video), and XLvr (Reflection signal of video). The signals are represented by dashed lines with arrows pointing to the OLT Rx. A label 'T1543930-01' is present in the bottom right corner of the diagram area.](23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg) + +Su Basic Band Signal (upstream) + XL Amount of interference optical power for OLT Receiver + XLdl Leak signal of downstream + XLdr Reflection signal of downstream + XLvl Leak signal of video + XLvr Reflection signal of video + +Figure III.3/G.983.3 – Noise signals at OLT-Rx. This diagram illustrates the noise signals at the OLT-Rx receiver. The ODN is connected to WDM WF1, which is connected to WDM-L. The WDM-L filter has Port T (connected to OLT Tx), Port R (connected to OLT Rx), and Port E (connected to E-Tx). The OLT Rx receives several signals: Su (Basic Band Signal (upstream)), XL (Amount of interference optical power for OLT Receiver), XLdl (Leak signal of downstream), XLdr (Reflection signal of downstream), XLvl (Leak signal of video), and XLvr (Reflection signal of video). The signals are represented by dashed lines with arrows pointing to the OLT Rx. A label 'T1543930-01' is present in the bottom right corner of the diagram area. + +**Figure III.3/G.983.3 – Noise signals at OLT-Rx** + +Then, amount of Interference optical power is given by Equation (III-4). + +$$XL[\text{dBm}] = 10 \times \log(XL[\text{mW}]) \quad (\text{III-4})$$ + +where: + +$$XL[\text{mW}] = XL_{dl}[\text{mW}] + XL_{dr}[\text{mW}] + XL_{vl}[\text{mW}] + XL_{vr}[\text{mW}]$$ + +So, if the reflected optical power is at least 10 dB lower than the signal power, then Equation (III-5) is satisfied. + +$$Su[\text{dBm}] - XL[\text{dBm}] \geq 10[\text{dB}] \quad (\text{III-5})$$ + +#### III.4.1.2 SNR of ONU-Rx + +Figure III.4 shows the noise signals received at ONU-Rx receiver. + +![Diagram of noise signals at ONU-Rx receiver. The diagram shows an optical network with components: ONU Tx, ONU Rx, WDM-N, WDM WF2, ODN, E-Rx, and SD. Signal paths are shown with solid and dashed lines. Red dashed lines represent upstream signals (XNul, XNur) from the ODN towards the ONU Rx. Blue dashed lines represent downstream signals (XNvl, XNvr) from the ODN towards the ONU Rx. The WDM-N and WDM WF2 components are shown as rectangular blocks. The ODN is shown as an oval. The E-Rx and SD components are shown as rectangular blocks. The ONU Tx and ONU Rx are shown as rectangular blocks. The diagram is labeled T1543940-01.](bc9d0c0b02cbe628b1b6548cc1107734_img.jpg) + +T1543940-01 + +| | | +|------|-------------------------------------------------------| +| Sd | Basic Band (downstream) | +| XN | Amount of interference optical power for ONU Receiver | +| XNul | Leak signal of upstream | +| XNur | Reflection signal of upstream | +| XNvl | Leak signal of video | +| XNvr | Reflection signal of video | + +Diagram of noise signals at ONU-Rx receiver. The diagram shows an optical network with components: ONU Tx, ONU Rx, WDM-N, WDM WF2, ODN, E-Rx, and SD. Signal paths are shown with solid and dashed lines. Red dashed lines represent upstream signals (XNul, XNur) from the ODN towards the ONU Rx. Blue dashed lines represent downstream signals (XNvl, XNvr) from the ODN towards the ONU Rx. The WDM-N and WDM WF2 components are shown as rectangular blocks. The ODN is shown as an oval. The E-Rx and SD components are shown as rectangular blocks. The ONU Tx and ONU Rx are shown as rectangular blocks. The diagram is labeled T1543940-01. + +**Figure III.4/G.983.3 – Noise signals at ONU-Rx** + +Then, amount of Interference optical power is given by Equation (III-6). + +$$XN[\text{dBm}] = 10 \times \log(XN[\text{mW}]) \quad (\text{III-6})$$ + +where: + +$$XN[\text{mW}] = XN_{ul}[\text{mW}] + XN_{ur}[\text{mW}] + XN_{vl}[\text{mW}] + XN_{vr}[\text{mW}]$$ + +So, if the reflected optical power is at least 10 dB lower than the signal power, then Equation (III-7) is satisfied. + +$$Sd[\text{dBm}] - XN[\text{dBm}] \geq 10[\text{dB}] \quad (\text{III-7})$$ + +#### III.4.1.3 SNR of E-Rx + +Figure III.5 shows the noise signals received at E-Rx receiver. + +![Diagram of noise signals at E-Rx receiver. The diagram shows an ONU Tx and ONU Rx connected to a WDM-N. The WDM-N is connected to a WDM WF2, which is connected to an ODN. The E-Rx is connected to the WDM WF2. The diagram illustrates various noise signals: XEul (leak signal of upstream), XEur (reflection signal of upstream), XEdl (leak signal of downstream), XEdr (reflection signal of downstream), and SV (video signal). The diagram is labeled T1543950-01.](f5a5f52bc25d95a7f616290c99e88ae6_img.jpg) + +Sv Video signal + XE Amount of interference optical power for E-ONU Receiver + XEul Leak signal of upstream + XEur Reflection signal of upstream + XEdl Leak signal of downstream + XEdr Reflection signal of downstream + +Diagram of noise signals at E-Rx receiver. The diagram shows an ONU Tx and ONU Rx connected to a WDM-N. The WDM-N is connected to a WDM WF2, which is connected to an ODN. The E-Rx is connected to the WDM WF2. The diagram illustrates various noise signals: XEul (leak signal of upstream), XEur (reflection signal of upstream), XEdl (leak signal of downstream), XEdr (reflection signal of downstream), and SV (video signal). The diagram is labeled T1543950-01. + +**Figure III.5/G.983.3 – Noise signals at E-Rx** + +Then, amount of Interference optical power (XE) is given by Equation (III-8). + +$$XE[\text{dBm}] = 10 \times \log(XE[\text{mW}]) \quad (\text{III-8})$$ + +where: + +$$XE[\text{mW}] = XEul[\text{mW}] + XEur[\text{mW}] + XEdl[\text{mW}] + XEdr[\text{mW}]$$ + +So, Equation (III-9) is satisfied. + +$$Sv[\text{dBm}] - XE[\text{dBm}] \geq (*)[\text{dB}] \quad (\text{III-9})$$ + +(\*) It depends on the specification of video signal. Refer to III.4.2.3. + +### III.4.2 In case of 64-QAM + +– Assumption of the Basic Band signal + +- 155 Mbit/s Class B + +$$P_{\text{out}}(\text{ATM-OLT}) = -2.5 \text{ to } +2 \text{ [dBm]} \text{ @ODN-I/F}$$ + +$$P_{\text{in}}(\text{ATM-OLT}) = -8 \text{ to } -31.5 \text{ [dBm]} \text{ @ODN-I/F}$$ + +$$P_{\text{out}}(\text{ATM-ONU}) = -5.5 \text{ to } +2 \text{ [dBm]} \text{ @ODN-I/F}$$ + +$$P_{\text{in}}(\text{ATM-ONU}) = -8 \text{ to } -28.5 \text{ [dBm]} \text{ @ODN-I/F}$$ + +- All WDM insertion loss of through port for all wavelengths is 0 to 1.5 dB +- ORL of ODN is 32 dB, ORL of Equipment at receiver wavelength is 20 dB + +- Assumption of the 64-QAM signal: + - 64-QAM modulation and 40 carriers for video (27.4 dB SNR is required) + +$$P_{\text{out}}(\text{video}) = +7 \text{ to } +10 \text{ [dBm]} \text{ @ODN I/F}$$ + +$$P_{\text{in}}(\text{video}) = 0 \text{ to } -18 \text{ [dBm]} \text{ @ODN I/F}$$ + - Frequency Range: 54 MHz ~ 750 MHz + - Carrier Spacing: 6 MHz + - Required SNR: 28 dB + +#### III.4.2.1 Calculation of OLT-Rx + +$$S_u \text{ [dBm]} = -31.5 \text{ [dBm]} - 1.5 \text{ [dB]} - 1.5 \text{ [dB]}$$ + +$$XL_{\text{dl}} \text{ [dBm]} = +2 \text{ [dBm]} - LLTR_d \text{ [dB]}$$ + +$$XL_{\text{dr}} \text{ [dBm]} = +2 \text{ [dBm]} - 32 \text{ [dB]} - 0 \text{ [dB]} - LLAR_d \text{ [dB]}$$ + +$$XL_{\text{vl}} \text{ [dBm]} = +10 \text{ [dBm]} - LWF1EA_v \text{ [dB]} - LLAR_v \text{ [dB]}$$ + +$$XL_{\text{vr}} \text{ [dBm]} = +10 \text{ [dBm]} - 32 \text{ [dB]} - LWF1CA_v \text{ [dB]} - LLAR_v \text{ [dB]}$$ + +From Equation III-4 and Equation III-5, an example of WDM characters are as follows: + +$$LLTR_d = 50 \text{ [dB]} \text{ (Loss of downstream in WDM-L from Port T to port R)}$$ + +$$LLAR_d = 20 \text{ [dB]} \text{ (Loss of downstream in WDM-L from Port A to port R)}$$ + +$$LWF1EA_v = 50 \text{ [dB]} \text{ (Loss of video in WDM-WF1 from Port E to port A)}$$ + +$$LLAR_v = 20 \text{ [dB]} \text{ (Loss of video in WDM-L from Port A to port R)}$$ + +$$LWF1CA_v = 20 \text{ [dB]} \text{ (Loss of video in WDM-WF1 from Port C to port A)}$$ + +#### III.4.2.2 Calculation of ONU-Rx + +$$S_d \text{ [dBm]} = -28.5 \text{ [dBm]} - 1.5 \text{ [dB]} - 1.5 \text{ [dB]}$$ + +$$XN_{\text{ul}} \text{ [dBm]} = +2 \text{ [dBm]} - LNTR_u \text{ [dB]}$$ + +$$XN_{\text{ur}} \text{ [dBm]} = +2 \text{ [dBm]} - 32 \text{ [dB]} - 0 \text{ [dB]} - LNAR_u \text{ [dB]}$$ + +$$XN_{\text{vl}} \text{ [dBm]} = (-18 \text{ [dBm]} + 3 \text{ [dB]}) - LWF2CA_v \text{ [dB]} - 0 \text{ [dB]}$$ + +$$XN_{\text{vr}} \text{ [dBm]} = (-18 \text{ [dBm]} + 3 \text{ [dB]}) - 0 \text{ [dB]} - 20 \text{ [dB]} - LWF2EA_v \text{ [dB]} - 0 \text{ [dB]}$$ + +$$3 \text{ [dB]} = +10 \text{ [dBm]} - (+7 \text{ [dBm]})$$ + +From Equation III-6 and Equation III-7, examples of WDM characteristics are as follows: + +$$LNTR_u = 50 \text{ [dB]} \text{ (Loss of upstream in WDM-N from Port T to port R)}$$ + +$$LNAR_u = 20 \text{ [dB]} \text{ (Loss of upstream in WDM-N from Port A to port R)}$$ + +$$LWF2CA_v = 29 \text{ [dB]} \text{ (Loss of video in WDM-WF2 from Port C to port A)}$$ + +$$LWF2EA_v = 20 \text{ [dB]} \text{ (Loss of video in WDM-WF2 from Port E to port A)}$$ + +#### III.4.2.3 Calculation of E-Rx + +S/X for video receiver requires 27.4 dB to transmit 40 carriers with -18 dBm received power. So, Equation (III-9 *bis*) is satisfied. + +$$S_v \text{ [dBm]} - XE \text{ [dBm]} \geq 27.4 \text{ dB} \quad (\text{III-9 bis})$$ + +$$S_v \text{ [dBm]} = -18 \text{ [dBm]} - 1.5 \text{ [dB]}$$ + +$$XEul [dBm] = +2 [dBm] - LWF2AEu [dB]$$ + +$$XEur [dBm] = +2 [dBm] - 32 [dB] - LWF2CEu [dB]$$ + +$$XEdl [dBm] = (-27.5 [dBm] + 4.5 [dB]) - LWF2Ced [dB]$$ + +$$XEdr [dBm] = (-27.5 [dBm] + 4.5 [dB]) - 0 [dB] - 20 [dB] - LWF2AEd [dB]$$ + +$$4.5 [dB] = +2 [dBm] - (-2.5 [dBm])$$ + +From Equation (III-8) and Equation (III-9 *bis*), examples of WDM characters are as follows: + +LWF2AEu = 50 [dB] (Loss of upstream in WDM-WF2 from Port A to port E) + +LWF2CEu = 31.5 [dB] (Loss of upstream in WDM-WF2 from Port C to port E) + +LWF2Ced = 31.5 [dB] (Loss of downstream in WDM-WF2 from Port C to port E) + +LWF2AEd = 20 [dB] (Loss of downstream in WDM-WF2 from Port A to port E) + +### III.4.3 Filter characteristics + +From an estimation of III.4.2.1, III.4.2.2 and III.4.2.3, required filter characteristics are shown in Tables III.7 and III.8. + +**Table III.7/G.983.3 – Required filter characteristics (OLT side)** + +| WF1 | | | | | WDM-L | | | | | +|---------|------|------------|-----|-----|-------|------|------------|-----|-----| +| | Port | Wavelength | Min | Max | | Port | Wavelength | Min | Max | +| LWF1Acd | A→C | Down | 0 | 1.5 | LLTAd | T→A | Down | 0 | 1.5 | +| LWF1CAu | C→A | Up | 0 | 1.5 | LLARu | A→R | Up | – | 1.5 | +| LWF1CEv | C→E | Video | 0 | 1.5 | LLATv | A→T | Video | – | – | +| LWF1Ced | C→E | Down | – | – | LLARd | A→R | Down | 20 | – | +| LWF1CEu | C→E | Up | – | – | LLATu | A→T | Up | – | – | +| LWF1CAv | C→A | Video | 20 | – | LLARv | A→R | Video | 20 | – | +| LWF1AEd | A→E | Down | – | – | LLTRd | T→R | Down | 50 | – | +| LWF1AEu | A→E | Up | – | – | LLRTu | R→T | Up | – | – | +| LWF1EAv | E→A | Video | 50 | – | LLTRv | T→R | Video | – | – | + +**Table III.8/G.983.3 – Required filter characteristics (ONU side)** + +| WF2 | | | | | WDM-N | | | | | +|---------|------|------------|------|-----|-------|------|------------|-----|-----| +| | Port | Wavelength | Min | Max | | Port | Wavelength | Min | Max | +| LWF2Acu | A→C | Up | 0 | 1.5 | LNTAu | T→A | Up | 0 | 1.5 | +| LWF2CAd | C→A | Down | 0 | 1.5 | LNARd | A→R | Down | – | 1.5 | +| LWF2CEv | C→E | Video | 0 | 1.5 | LNARv | A→T | Video | 0 | – | +| LWF2CEu | C→E | Up | 31.5 | – | LNARu | A→R | Up | 20 | – | + +**Table III.8/G.983.3 – Required filter characteristics (ONU side) (concluded)** + +| WF2 | | | | | WDM-N | | | | | +|---------|------|------------|------|-----|-------|------|------------|-----|-----| +| | Port | Wavelength | Min | Max | | Port | Wavelength | Min | Max | +| LWF2CEd | C→E | Down | 31.5 | – | LNATd | A→T | Down | – | – | +| LWF2CAv | C→A | Video | 29 | – | LNATv | A→R | Video | – | – | +| LWF2AEu | A→E | Up | 50 | – | LNTRu | T→R | Up | 50 | – | +| LWF2AEd | A→E | Down | 20 | – | LNRTd | R→T | Down | – | – | +| LWF2EAv | E→A | Video | 20 | – | LNTTv | T→R | Video | – | – | + +Isolation is defined as the loss difference between two wavelengths measured at the same port. Therefore, we can calculate "Isolation" using Tables III.7 and III.8. + +**Isolation at WDM-WF1: Isolate Basic Band upstream signal from Enhancement band signal.** + +$$\text{LWF1CAv(min) [dB]} - \text{LWF1CAu(max) [dB]} = 20 \text{ [dB]} - 1.5 \text{ [dB]} = \mathbf{18.5 \text{ [dB]}}$$ + +**Isolation at WDM-WF2: Isolate Enhancement Band signal from Basic band upstream signal.** + +$$\text{LWF2CEu(min) [dB]} - \text{LWF2CEv(max) [dB]} = 31.5 \text{ [dB]} - 1.5 \text{ [dB]} = \mathbf{30 \text{ [dB]}}$$ + +**Isolation at WDM-WF2: Isolate Enhancement Band signal from Basic Band downstream signal.** + +$$\text{LWF2CEd(min) [dB]} - \text{LWF2CEv(max) [dB]} = 31.5 \text{ [dB]} - 1.5 \text{ [dB]} = \mathbf{30 \text{ [dB]}}$$ + +**Isolation at WDM-WF2: Isolate Basic Band downstream signal from Enhancement Band signal.** + +$$\text{LWF2CAv(min) [dB]} - \text{LWF2CAd(max) [dB]} = 29 \text{ [dB]} - 1.5 \text{ [dB]} = \mathbf{27.5 \text{ [dB]}}$$ + +# APPENDIX IV + +## Effect of optical return loss of ODN + +## IV.1 Introduction + +Each network model has its own optical return loss (ORL) of ODN and BPON is sensitive to the ORL of ODN. This appendix describes the relationship among some types of reflectance to be considered, WDM isolation of ONU and OLT, and ONU equipment reflectance for transmitter and receiver for each case that ORL of ODN is 32 dB and 20 dB. + +The fundamental consideration has already been described in Appendix II/G.983.1. Similar consideration is applicable and extended for BPON ODN including effects by Enhancement Band, E-ONU, and E-OLT. + +In the calculation of optical parameters, we assume that ONU and E-ONU equipment reflectance for receiver is –20 dB and OLT and E-OLT equipment reflectance for receiver is –20 dB. This appendix describes condition equations and calculation results for the reflectance, which restrict the parameters. + +NOTE – Permissible total noise to the receiver, which consists of multiple reflections as well as leaked optical power, may be 10 dB lower than the lowest signal level. Since the permissible noise power for each noise component is for further study, thus the following clauses IV.2 and IV.3 are tentatively described on the assumption that each noise component be at least 10 dB lower than the signal. This assumption should be modified and interpreted to some higher value than 10 dB, for example to 13 dB, according to the permissible noise power assigned to each noise component such as reflections and leaked power. + +## IV.2 Effect of ODN optical return loss in the Basic Band + +### IV.2.1 Reflectance model to be considered + +![Figure IV.1/G.983.3 – Reflectance model to be considered. The diagram shows an optical network with an OLT on the right and multiple ONUs on the left. The OLT contains a transmitter (TX) and receiver (RX) connected to a WDM-I. An Enhancement Band OLT is also connected to the WDM-I. The WDM-I is connected to a splitter via a WF1 filter. The splitter has two output paths: one leading to a WF2 filter and then to an ONU, and another leading to another WF2 filter and then to an Enhancement Band E-ONU. The ONUs also contain TX and RX connected to a WDM-N. Various optical parameters are labeled: PO_ru (optical output power of ONU transmitter), Ronu_t (ONU transmitter equipment reflectance), Reonu_r (E-ONU receiver equipment reflectance), Rupper (ORL of ODN at O_ru and O_rd), Rdown (ORL of ODN at O_ld and O_lu), POld (optical output power of OLT transmitter), PEold (optical output power of E-OLT transmitter), and IF_PON (interface point). Reference points (c) and (d) are marked near the OLT, and reference point (e) is marked near the ONUs. A note at the bottom left specifies minimum attenuation: 5 dB for Class A, 10 dB for Class B, and 15 dB for Class C. The diagram is labeled T1543960-01.](ec3647789b5c38fb686f2a0833324e79_img.jpg) + +minimum attenuation is: + 5 dB for Class A + 10 dB for Class B + 15 dB for Class C + +Figure IV.1/G.983.3 – Reflectance model to be considered. The diagram shows an optical network with an OLT on the right and multiple ONUs on the left. The OLT contains a transmitter (TX) and receiver (RX) connected to a WDM-I. An Enhancement Band OLT is also connected to the WDM-I. The WDM-I is connected to a splitter via a WF1 filter. The splitter has two output paths: one leading to a WF2 filter and then to an ONU, and another leading to another WF2 filter and then to an Enhancement Band E-ONU. The ONUs also contain TX and RX connected to a WDM-N. Various optical parameters are labeled: PO\_ru (optical output power of ONU transmitter), Ronu\_t (ONU transmitter equipment reflectance), Reonu\_r (E-ONU receiver equipment reflectance), Rupper (ORL of ODN at O\_ru and O\_rd), Rdown (ORL of ODN at O\_ld and O\_lu), POld (optical output power of OLT transmitter), PEold (optical output power of E-OLT transmitter), and IF\_PON (interface point). Reference points (c) and (d) are marked near the OLT, and reference point (e) is marked near the ONUs. A note at the bottom left specifies minimum attenuation: 5 dB for Class A, 10 dB for Class B, and 15 dB for Class C. The diagram is labeled T1543960-01. + +**Figure IV.1/G.983.3 – Reflectance model to be considered** + +The following notations are used in this appendix: + +| | | +|---------------|--------------------------------------------------------| +| $P_{Oru\_n}$ | Optical output power of ONU #n transmitter at $O_{ru}$ | +| $P_{Old}$ | Optical output power of OLT transmitter at $O_{ld}$ | +| $P_{EOld}$ | Optical output power of E-OLT transmitter at $O_{ld}$ | +| $Ronu\_t$ | ONU transmitter equipment reflectance | +| $Rolt\_t$ | OLT transmitter equipment reflectance | +| $Reonu\_r$ | E-ONU receiver equipment reflectance | +| $Rupper$ | ORL of ODN at $O_{ru}$ and $O_{rd}$ | +| $Rdown$ | ORL of ODN at $O_{ld}$ and $O_{lu}$ | +| $L_{ODN\_BB}$ | Optical loss of Basic Band in the ODN | +| $L_{ODN\_EB}$ | Optical loss of Enhancement Band in the ODN | +| $L_{WF1}$ | Insertion loss of WF1 | +| $L_{WF2}$ | Insertion loss of WF2 | +| $Iolt\_t$ | WDM isolation for OLT transmitter | +| $Iolt\_r$ | WDM isolation for OLT receiver | +| $Ionu\_r$ | WDM isolation for ONU receiver | +| $I_{WF1}$ | WF1 isolation for Basic Band | +| $I_{WF2}$ | WF2 isolation for Basic Band | + +These values are all treated as positive in this appendix. + +The following assumptions are taken for the examples: + +- $L_{ODN-BB} = L_{ODN-EB}$ +- Minimum insertion loss for WF1 and WF2 is equal to 0 dB. +- Insertion loss between the port at reference point (c) and the port at IFPON side of WF1 is identical for upstream/downstream 1.3 µm, and upstream/downstream 1.5 µm Basic Band wavelengths. +- Insertion loss between the port at reference point (e) and the port at IFPON side of WF2 is identical for upstream/downstream 1.3 µm, and upstream/downstream 1.5µm Basic Band wavelengths. + +### IV.2.2 Influence of reflectance into ONU receiver + +Figure IV.2 shows the path of reflected signal to be considered. Equation (IV-1) must be satisfied: + +$$P_{Oru\_1} - R_{upper} - I_{onu\_r} < (\text{permissible interference optical power}) \quad (\text{IV-1})$$ + +Assuming permissible interference optical power is equal to (minimum sensitivity –10 dB), permissible interference optical power = $P_{min}(A,B,C) - 10$ dB. $P_{min}(A,B,C)$ means minimum sensitivity at reference point (e) for Class A, B, C described in Table V.1. + +Then $I_{onu\_r}$ is estimated and summarized in Table IV.1. + +![Figure IV.2/G.983.3 – Model for incidence into ONU receiver. The diagram shows an optical network with an OLT on the right connected via WF1 and WDM-L to TX and RX. On the left, multiple ONUs (ONU#1, E-ONU, ONU#n) are connected via WF2 and WDM-N to TX and RX. A central splitter is connected to the OLT side through WF1 and to the ONUs through WF2. Reference point (e) is marked on the ONU#1 side, and IF_PON is marked at the splitter. The ODN (Optical Distribution Network) is indicated between the ONUs and the splitter. A reflected signal path is shown from the splitter back to the ONU#1 receiver (RX) through the WDM-N and WF2 components. The label T1543970-01 is present in the bottom right corner of the diagram area.](772cc583a60eeb058cc19de48269ad22_img.jpg) + +Figure IV.2/G.983.3 – Model for incidence into ONU receiver. The diagram shows an optical network with an OLT on the right connected via WF1 and WDM-L to TX and RX. On the left, multiple ONUs (ONU#1, E-ONU, ONU#n) are connected via WF2 and WDM-N to TX and RX. A central splitter is connected to the OLT side through WF1 and to the ONUs through WF2. Reference point (e) is marked on the ONU#1 side, and IF\_PON is marked at the splitter. The ODN (Optical Distribution Network) is indicated between the ONUs and the splitter. A reflected signal path is shown from the splitter back to the ONU#1 receiver (RX) through the WDM-N and WF2 components. The label T1543970-01 is present in the bottom right corner of the diagram area. + +Figure IV.2/G.983.3 – Model for incidence into ONU receiver + +### IV.2.3 Influence of reflectance into OLT receiver (in the signal region) + +The analysis for the influence of reflectance into OLT receiver is performed in two conditions; one is that the reflected signal overlaps the upstream burst signal region and the other is that the reflected signal is in the delay measurement window where there is no signal. + +In the signal region, the following three cases are to be considered. + +#### IV.2.3.1 Case 1 + +Figure IV.3 shows the path of reflectance signals. Equation (IV-2) must be satisfied: + +$$\begin{aligned} &(\text{maximum difference of burst signal optical levels}) - R_{\text{upper}} - 2L_{\text{WF2}} - R_{\text{onu\_t}} \quad (\text{IV-2}) \\ &< (\text{permissible interference optical power ratio}) \end{aligned}$$ + +Assuming permissible interference optical power ratio is $-10$ dB, we obtain the results (see Table IV.1). Here, loss of $L_{\text{WF2}}$ is assumed as $0$ dB to estimate the worst case. + +![Figure IV.3/G.983.3 – Model 1 for incidence into OLT receiver. This schematic diagram shows the optical path from multiple ONUs (ONU#1, E-ONU, ONU#n) through wavefronters (WF2) and a central splitter to an OLT. ONU#1 contains TX and RX components connected to a WDM-N. A reflectance signal is shown originating from the RX of ONU#1, passing through WDM-N, WF2, and reflecting off the central splitter. The path is labeled with 'Reference point (e)', 'IF_PON', 'P_Onu_1', 'Rupper', and 'ODN'. The OLT side includes WF1, WDM-L, TX, and RX. A label 'T1543980-01' is present in the bottom right.](7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg) + +Figure IV.3/G.983.3 – Model 1 for incidence into OLT receiver. This schematic diagram shows the optical path from multiple ONUs (ONU#1, E-ONU, ONU#n) through wavefronters (WF2) and a central splitter to an OLT. ONU#1 contains TX and RX components connected to a WDM-N. A reflectance signal is shown originating from the RX of ONU#1, passing through WDM-N, WF2, and reflecting off the central splitter. The path is labeled with 'Reference point (e)', 'IF\_PON', 'P\_Onu\_1', 'Rupper', and 'ODN'. The OLT side includes WF1, WDM-L, TX, and RX. A label 'T1543980-01' is present in the bottom right. + +Figure IV.3/G.983.3 – Model 1 for incidence into OLT receiver + +#### IV.2.3.2 Case 2 + +Figure IV.4 shows the path of reflectance signals. Equation (IV-3) must be satisfied: + +$$\begin{aligned} &(\text{maximum difference of burst signal optical levels}) - R_{\text{olt\_t}} - R_{\text{down}} - 2 L_{\text{WF1}} - 2I_{\text{olt\_t}} \quad (\text{IV-3}) \\ &< (\text{permissible interference optical power}) \end{aligned}$$ + +Assuming permissible interference optical power is equal to $-10$ dB, we obtain the results (see Table IV.1). To estimate the worst case of $I_{\text{olt\_t}}$ , loss of $L_{\text{WF1}}$ is assumed as $0$ dB. + +![Figure IV.4/G.983.3 – Model 2 for incidence into OLT receiver. This schematic diagram shows the optical path from ONUs (ONU#1, E-ONU, ONU#n) through WF2 and a central splitter to an OLT. ONU#1 contains TX and RX components connected to a WDM-N. A reflectance signal is shown originating from the RX of ONU#1, passing through WDM-N, WF2, the central splitter, WF1, and WDM-L, and reflecting off the RX of the OLT. The path is labeled with 'Reference point (e)', 'IF_PON', 'Rolt_t', 'Rdown', and 'ODN'. A label 'T1543990-01' is present in the bottom right.](042af54276c75e7b7b48a3af1f0a84e5_img.jpg) + +Figure IV.4/G.983.3 – Model 2 for incidence into OLT receiver. This schematic diagram shows the optical path from ONUs (ONU#1, E-ONU, ONU#n) through WF2 and a central splitter to an OLT. ONU#1 contains TX and RX components connected to a WDM-N. A reflectance signal is shown originating from the RX of ONU#1, passing through WDM-N, WF2, the central splitter, WF1, and WDM-L, and reflecting off the RX of the OLT. The path is labeled with 'Reference point (e)', 'IF\_PON', 'Rolt\_t', 'Rdown', and 'ODN'. A label 'T1543990-01' is present in the bottom right. + +Figure IV.4/G.983.3 – Model 2 for incidence into OLT receiver + +#### IV.2.3.3 Case 3 + +Figure IV.5 shows the path of reflectance signals. Equation (IV-4) must be satisfied: + +$$P_{\text{Old}} - R_{\text{down}} - I_{\text{olt\_r}} < (\text{permissible interference optical power}) \quad (\text{IV-4})$$ + +Assuming permissible interference optical power is equal to minimum sensitivity $-10$ dB, we obtain the results (see Table IV.1). + +![Figure IV.5/G.983.3 – Model 3 for incidence into OLT receiver. The diagram shows an optical network with an OLT on the right and multiple ONUs (ONU#1, E-ONU, ONU#n) on the left. ONU#1 contains TX and RX connected to a WDM-N. E-ONU and ONU#n are connected to WDM-N via WF2 splitters. The WDM-N is connected to a central optical splitter via WF2 splitters. The central splitter is connected to the OLT via WF1 splitters. The OLT contains TX and RX connected to a WDM-L. The diagram indicates the path of reflectance signals from the OLT RX through the WDM-L, WF1, central splitter, WF2, and WDM-N to the ONU TX. The ODN (Optical Distribution Network) is shown between the central splitter and the ONUs. Reference points (e) and IF_PON are marked. The label T1544000-01 is present in the bottom right.](08f6ace0c83e7394657fa372b47aec04_img.jpg) + +Figure IV.5/G.983.3 – Model 3 for incidence into OLT receiver. The diagram shows an optical network with an OLT on the right and multiple ONUs (ONU#1, E-ONU, ONU#n) on the left. ONU#1 contains TX and RX connected to a WDM-N. E-ONU and ONU#n are connected to WDM-N via WF2 splitters. The WDM-N is connected to a central optical splitter via WF2 splitters. The central splitter is connected to the OLT via WF1 splitters. The OLT contains TX and RX connected to a WDM-L. The diagram indicates the path of reflectance signals from the OLT RX through the WDM-L, WF1, central splitter, WF2, and WDM-N to the ONU TX. The ODN (Optical Distribution Network) is shown between the central splitter and the ONUs. Reference points (e) and IF\_PON are marked. The label T1544000-01 is present in the bottom right. + +Figure IV.5/G.983.3 – Model 3 for incidence into OLT receiver + +### IV.2.4 Influence of reflectance into OLT receiver (in the no signal region) + +In the no signal region, main cases of reflectance to be considered are the following two cases. + +#### IV.2.4.1 Case 1 + +Figure IV.3 shows the path of reflectance signals. Equation (IV-5) must be satisfied: + +$$P_{\text{Oru\_n}} - R_{\text{upper}} - 2L_{\text{WF2}} - R_{\text{onu\_t}} - (\text{minimum optical path attenuation}) < (\text{determination level as no signal}) \quad (\text{IV-5})$$ + +Assuming determination level as no signal is equal to minimum sensitivity $-10$ dB, we obtain the results (see Table IV.1). To estimate the worst case of $R_{\text{onu\_t}}$ , loss of $L_{\text{WF2}}$ is assumed as $0$ dB. + +#### IV.2.4.2 Case 2 + +Figure IV.5 shows the path of reflectance signals. Equation (IV-6) must be satisfied: + +$$P_{\text{Old}} - R_{\text{down}} - I_{\text{olt\_r}} < (\text{determination level as no signal}) \quad (\text{IV-6})$$ + +Assuming determination level as no signal is equal to minimum sensitivity $-10$ dB, we obtain the results (see Table IV.1). + +### IV.2.5 Summary in effects of ODN optical return loss in the Basic Band + +The calculation method mentioned above is available for the case that ODN reflectance is $-20$ dB. Table IV.1 shows the requirement for optical parameters when minimum ORL of ODN is $32$ dB and $20$ dB. + +WDM isolation parameter is implementation matter, and values concerning WDM isolation parameters in Table IV.1 are just informative. This appendix includes ONU and OLT equipment reflectance. Considering the characteristic of the WDM, $R_{onu\_t}$ is equal to the reflectance of ONU measured at transmitter wavelength. + +When ORL of ODN is 32 dB, ONU transmitter equipment reflectance must be less than incident optical power. It shall be 6 dB, which is available in an ordinary FP-LD module. + +In the case that ORL of ODN is 20 dB, ONU transmitter equipment reflectance must be less than 13.5 dB. + +As mentioned above, maximum ONU transmitter equipment reflectance is sensitive to the value of ORL of ODN, which depends on the network built by the common carrier. In the case that ORL of ODN is 32 dB and 20 dB, values of equipment reflectance for ONU transmitter in Table IV.1 are applicable. In the other case, the appropriate value is derived by means of the calculation method mentioned above. + +**Table IV.1/G.983.3 – Values for ONU transmitter equipment reflectance** + +| Min ORL of ODN | Class | Optical parameters | Required characteristics | | | | | | +|----------------|-------|-------------------------------------------|--------------------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | A a) | B a) | C a) | D a) | E a) | F a) | +| 32 dB | A | WDM isolation for ONU receiver | 6.5 | | | | | | +| | | WDM isolation for ONU transmitter | | | | | | | +| | | WDM isolation for OLT receiver | | | | 3.5 | | 3.5 | +| | | WDM isolation for OLT transmitter | | | NA | | | | +| | | Equipment reflectance for ONU transmitter | | 0.5 | | | 1.5 | | +| | B | WDM isolation for ONU receiver | 8.5 | | | | | | +| | | WDM isolation for ONU transmitter | | | | | | | +| | | WDM isolation for OLT receiver | | | | 11.5 | | 11.5 | +| | | WDM isolation for OLT transmitter | | | NA | | | | +| | | Equipment reflectance for ONU transmitter | | 0.5 | | | 1.5 | | +| | C | WDM isolation for ONU receiver | 13.5 | | | | | | +| | | WDM isolation for ONU transmitter | | | | | | | +| | | WDM isolation for OLT receiver | | | | 16.5 | | 16.5 | +| | | WDM isolation for OLT transmitter | | | NA | | | | +| | | Equipment reflectance for ONU transmitter | | 0.5 | | | 1.5 | | +| 20 dB | A | WDM isolation for ONU receiver | 18.5 | | | | | | +| | | WDM isolation for ONU transmitter | | | | | | | +| | | WDM isolation for OLT receiver | | | | 15.5 | | 15.5 | +| | | WDM isolation for OLT transmitter | | | 3.3 | | | | +| | | Equipment reflectance for ONU transmitter | | 12.5 | | | 13.5 | | +| | B | WDM isolation for ONU receiver | 20.5 | | | | | | +| | | WDM isolation for ONU transmitter | | | | | | | +| | | WDM isolation for OLT receiver | | | | 23.5 | | 23.5 | +| | | WDM isolation for OLT transmitter | | | 3.3 | | | | +| | | Equipment reflectance for ONU transmitter | | 12.5 | | | 13.5 | | +| | C | WDM isolation for ONU receiver | 25.5 | | | | | | +| | | WDM isolation for ONU transmitter | | | | | | | +| | | WDM isolation for OLT receiver | | | | 28.5 | | 28.5 | +| | | WDM isolation for OLT transmitter | | | 3.3 | | | | +| | | Equipment reflectance for ONU transmitter | | 12.5 | | | 13.5 | | + +a) A, B, C, D, E and F represent Equation (IV-1), Equation (IV-2), Equation (IV-3), Equation (IV-4), Equation (IV-5) and Equation (IV-6), respectively. + +## IV.3 Influence of reflectance from Enhancement Band to Basic Band + +### IV.3.1 Influence of reflectance into OLT receiver from Enhancement Band + +Service using Enhancement Band signals may degrade quality of the Basic Band (ATM-PON) service, and vice versa. Three types of reflection of Enhancement Band signals are considered. One is the reflection from the ODN, and the others are those from the E-ONU and the blocking filter. + +#### IV.3.1.1 Case 1 + +Figure IV.6 shows the path of reflectance signals from ODN. Equation (IV-7) must be satisfied: + +$$P_{Eold} - R_{down} - I_{olt\_r} - I_{WF1} < (\text{determination level as no signal}) \quad (\text{IV-7})$$ + +Assuming determination level as no signal is equal to minimum sensitivity $-10$ dB, we obtain the condition for $I_{WF1}$ . Example for required isolation of $I_{WF1}$ is shown in Table IV.2. Example conditions refer to Table IV.1 and Table V.1. + +![Figure IV.6/G.983.3 – Model 4 for incidence into OLT receiver. The diagram shows a network topology with ONUs (ONU#1, ONU#n) connected via WDM-N and WF2 filters to a central ODN. E-ONUs are also connected to the ODN. The ODN is connected to an OLT via WF1 and WDM-L filters. The OLT has TX and RX components. The diagram includes labels for IF_PON, Rdown, and a reference point (f).](db5deafdae53dbc7d5972957f708c691_img.jpg) + +The diagram illustrates the optical network topology for Model 4. On the left, multiple ONUs (ONU#1, ONU#n) are connected to a central Optical Distribution Network (ODN) through Wavelength Division Multiplexers (WDM-N) and Waveform Filters (WF2). Each ONU contains a Transmitter (TX) and a Receiver (RX). E-ONUs are also connected to the ODN. The ODN is represented by a central circle with multiple input/output points. The ODN is connected to an Optical Line Terminal (OLT) on the right through a Waveform Filter (WF1) and a Wavelength Division Multiplexer (WDM-L). The OLT contains a TX and a RX. The diagram includes labels for the Interference Factor (IF\_PON), the Downstream Reflectance (Rdown), and a Reference point (f) located near the ODN. The text 'T1544010-01' is visible in the bottom right corner. + +Figure IV.6/G.983.3 – Model 4 for incidence into OLT receiver. The diagram shows a network topology with ONUs (ONU#1, ONU#n) connected via WDM-N and WF2 filters to a central ODN. E-ONUs are also connected to the ODN. The ODN is connected to an OLT via WF1 and WDM-L filters. The OLT has TX and RX components. The diagram includes labels for IF\_PON, Rdown, and a reference point (f). + +Figure IV.6/G.983.3 – Model 4 for incidence into OLT receiver + +Table IV.2/G.983.3 – ORL versus Isolation at WF1 + +| Min ORL of ODN | Class | Example conditions | | | Required $I_{WF1}$ (dB) | +|----------------|-------|--------------------|-------------------|-----------------|-------------------------| +| | | $P_{Eold}$ (dBm) | $I_{olt\_r}$ (dB) | $P_{min}$ (dBm) | | +| 32 dB | A | +16 | 3.5 | -28.5 | 19 | +| | B | | 11.5 | -31.5 | 14 | +| | C | | 16.5 | -34.5 | 12 | +| 20 dB | A | | 15.5 | -28.5 | 19 | +| | B | | 23.5 | -31.5 | 14 | +| | C | | 28.5 | -34.5 | 12 | + +#### IV.3.1.2 Case 2 + +Figure IV.7 shows the path of reflectance signals from E-ONU. Equation (IV-8) must be satisfied: + +$$\sum (P_{Eold} - 2 L_{ODN-EB} - Reonu\_r) - I_{olt\_r} - I_{WF1} < (\text{determination level as no signal}) \quad (IV-8)$$ + +Here, the first $\sum$ (summation) denotes reflection from all connected E-ONUs. In other words, + +$$P_{Eold} - 2 L_{ODN-EB} - Reonu\_r + 10 \times \text{Log}N - I_{olt\_r} - I_{WF1} < (\text{determination level as no signal}).$$ + +Here, N shows the number of connected E-ONUs. + +Assuming determination level as no signal is equal to minimum sensitivity $-10$ dB, we obtain the condition for $I_{WF1}$ . Example for required isolation of $I_{WF1}$ is shown in Table IV.3. Minimum loss of ODN and appropriate number of N is assumed. Example conditions refer to Tables IV.1 and V.1. + +![Figure IV.7/G.983.3 – Model 5 for incidence into OLT receiver. The diagram shows a network topology with an OLT on the right containing TX, RX, and WDM-L components, connected to an E-OLT. On the left, multiple ONUs (ONU#1, ONU#n, E-ONU) are connected via WDM-N and WF2 filters. A central optical splitter is shown with a 'Reference point (f)'. Arrows indicate signal paths and reflections, with labels for IF_PON, Rdown, and ODN.](3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg) + +Figure IV.7/G.983.3 – Model 5 for incidence into OLT receiver. The diagram shows a network topology with an OLT on the right containing TX, RX, and WDM-L components, connected to an E-OLT. On the left, multiple ONUs (ONU#1, ONU#n, E-ONU) are connected via WDM-N and WF2 filters. A central optical splitter is shown with a 'Reference point (f)'. Arrows indicate signal paths and reflections, with labels for IF\_PON, Rdown, and ODN. + +Figure IV.7/G.983.3 – Model 5 for incidence into OLT receiver + +Table IV.3/G.983.3 – ORL versus Isolation at WF1 + +| Min ORL of ODN | Assumption conditions | | | | | | | Required I WF1 (dB) | +|----------------|-----------------------|------------------|----------------|-------------------------|-------------------------|------------------------|--------------|--------------------------------| +| | ODN Class | Loss of ODN (dB) | No. of E-ONU N | P Eold (dBm) | I olt_r (dB) | P min (dBm) | Reonu_r (dB) | | +| 32 dB | A | 5 | 2 | +16 | 3.5 | -28.5 | 20 | 24 | +| | B | 10 | 8 | | 11.5 | -31.5 | | 15 | +| | C | 15 | 32 | | 16.5 | -34.5 | | 9 | +| 20 dB | A | 5 | 2 | +16 | 15.5 | -28.5 | 20 | 12 | +| | B | 10 | 8 | | 23.5 | -31.5 | | 3 | +| | C | 15 | 32 | | 28.5 | -34.5 | | NA | + +#### IV.3.1.3 Case 3 + +Deployment scenarios described in Appendix II demonstrate configuration example of mixture in ONUs served by Basic Band only and ONUs served both by Basic Band and Enhancement Band. In this case, Blocking filters for Basic Band only users may be applied. Some type of Blocking filter may cause reflections to degrade signal quality. + +Figure IV.8 shows the path of reflection signals from Blocking filters. Equation (IV-9) must be satisfied: + +$$\sum (P_{EOId} - 2 L_{ODN-EB} - R_{WF2\_r}) - I_{olt\_r} - I_{WF1} < (\text{determination level as no signal}) \quad (IV-9)$$ + +Here, $R_{WF2\_r}$ means the reflectance of the Blocking filter and the first $\sum$ (summation) denotes reflection from all connected Blocking Filters. In other words, + +$$P_{EOId} - 2 L_{ODN-EB} - R_{WF2\_r} + 10 \times \text{Log}N - I_{olt\_r} - I_{WF1} < (\text{determination level as no signal}).$$ + +Here, N shows the number of connected blocking filters. + +Assuming determination level as no signal is equal to minimum sensitivity $-10$ dB, we obtain the condition for $R_{WF2\_r}$ . An example for required reflectance of $R_{WF2\_r}$ is shown in Table IV.4. Minimum loss of ODN and appropriate number of N is assumed. Isolation of $I_{WF1}$ is assumed to be larger value among those in Tables IV.2 and IV.3. Example conditions refer to Tables IV.1 and V.1. + +![Figure IV.8/G.983.3 – Model 6 for incidence into OLT receiver. The diagram shows an optical network with multiple ONUs (ONU#1 to ONU#n) connected via WDM-N and blocking filters (WF2) to a central optical fiber. The fiber connects to an OLT via WDM-L and WF1. Reflection signals are shown originating from the blocking filters and being received by the OLT's RX. The diagram includes labels for IF_PON, ODN, and E-OLT. A small text 'T1544030-01' is visible in the bottom right corner of the diagram area.](408c4798ea60469e0728a7cbbd598668_img.jpg) + +Figure IV.8/G.983.3 – Model 6 for incidence into OLT receiver. The diagram shows an optical network with multiple ONUs (ONU#1 to ONU#n) connected via WDM-N and blocking filters (WF2) to a central optical fiber. The fiber connects to an OLT via WDM-L and WF1. Reflection signals are shown originating from the blocking filters and being received by the OLT's RX. The diagram includes labels for IF\_PON, ODN, and E-OLT. A small text 'T1544030-01' is visible in the bottom right corner of the diagram area. + +Figure IV.8/G.983.3 – Model 6 for incidence into OLT receiver + +Table IV.4 – ORL versus Isolation at WF1 + +| Min ORL of ODN | Assumption conditions | | | | | | | Required $R_{WF2\_r}$ (dB) | +|----------------|-----------------------|------------------|----------------|------------------|-------------------|-----------------|----------------|----------------------------| +| | ODN Class | Loss of ODN (dB) | No. of E-ONU N | $P_{EOId}$ (dBm) | $I_{olt\_r}$ (dB) | $P_{min}$ (dBm) | $I_{WF1}$ (dB) | | +| 32 dB | A | 5 | 2 | +16 | 3.5 | -28.5 | 24 | 20 | +| | B | 10 | 8 | | 11.5 | -31.5 | 15 | 20 | +| | C | 15 | 32 | | 16.5 | -34.5 | 12 | 17 | +| 20 dB | A | 5 | 2 | +16 | 15.5 | -28.5 | 19 | 13 | +| | B | 10 | 8 | | 23.5 | -31.5 | 14 | 9 | +| | C | 15 | 32 | | 28.5 | -34.5 | 12 | 5 | + +# APPENDIX V + +## Optical parameters for reference point (c) and (e) and two example deployment cases + +## V.1 Introduction + +The optical power parameters for reference points of (c) and (e) shown here are examples to guide implementation. + +## V.2 Optical level diagram examples + +### V.2.1 Case 1: ODN centric view of optical parameters + +Optical parameters examples for IFPON are assumed to be the same as those described in Appendix I and the attenuation range of the ODN is compliant to ITU-T G.982. + +In this case, example optical power level diagrams are shown below: + +WDM loss of WF1 = 0 dB to 1.5 dB, WDM loss of WF2 = 0 dB to 1.5 dB. + +Optical path penalty of 1 dB is included at the reference points of R/S and S/R at IFPON. + +**Table V.1/G.983.3 – Optical power level diagram (example)** + +| | Ref.(e) | | IF PON
(O ru , O rd ) | | ODN loss | | IF PON
(O lu , O ld ) | | Ref.(c) | | +|---------------------|---------|-----|-----------------------------------------------------------|-----|----------|-----|-----------------------------------------------------------|-----|---------|-----| +| Unit | dBm | | dBm | | dB | | dBm | | dBm | | +| Range | Min | Max | Min | Max | Min | Max | Min | Max | Min | Max | +| Downstream | | | | | | | | | | | +| 155M Class A | -30 | -8 | -28.5 | -8 | 5 | 20 | -7.5 | -3 | -6 | -3 | +| 155M Class B | -30 | -8 | -28.5 | -8 | 10 | 25 | -2.5 | 2 | -1 | 2 | +| 155M Class C | -33 | -11 | -31.5 | -11 | 15 | 30 | -0.5 | 4 | 1 | 4 | +| 622M Class A | -28 | -6 | -26.5 | -6 | 5 | 20 | -5.5 | -1 | -4 | -1 | +| 622M Class B | -28 | -6 | -26.5 | -6 | 10 | 25 | -0.5 | 4 | 1 | 4 | +| 622M Class C | -33 | -11 | -31.5 | -11 | 15 | 30 | -0.5 | 4 | 1 | 4 | +| Upstream | | | | | | | | | | | +| 155M Class A | -6 | 0 | -7.5 | 0 | 5 | 20 | -28.5 | -5 | -30 | -5 | +| 155M Class B | -4 | 2 | -5.5 | 2 | 10 | 25 | -31.5 | -8 | -33 | -8 | +| 155M Class C | -2 | 4 | -3.5 | 4 | 15 | 30 | -34.5 | -11 | -36 | -11 | + +### V.2.2 Case 2: Equipment centric view of optical parameters + +Optical parameters for reference points of (c) and (e) are same as those specified in ITU-T G.983.1 and the attenuation range of the ODN is reduced from that in ITU-T G.982. + +The purpose of this clause is to survey the BPON applicability of optical modules compliant to ITU-T G.983.1. Maximum variation of the attenuation range in the ODN is reduced in order to + +compensate for the extra dynamic range induced by WF1 and WF2. Applied ODN parameters are shown in Table V.2. + +With regards to ODN Class A, optical parameters are not specified in ITU-T G.983.1, thus the case of Class A is not described. + +**Table V.2/G.983.3 – Physical medium dependant layer parameters of ODN** + +| Items | Unit | Specification | +|---------------------------------------------------|------|-------------------------------------------------------------------------------------------------------| +| Fibre type | – | ITU-T G.652 | +| Attenuation range | dB | Reduced Class B with attenuation range: 10-22
Reduced Class C with attenuation range: 15-27 | +| Differential optical path loss | dB | 12 | +| Maximum optical path penalty | dB | 1 | +| Max differential logical reach | km | 20 | +| Maximum fibre distance between S/R and R/S points | km | 20 | +| Minimum supported split ratio | – | Restricted by path loss and ONU addressing limits.
PON with passive splitters (16 or 32 way split) | +| Bidirectional transmission | – | 1-fibre WDM (2-fibre system is beyond the scope of this Recommendation) | +| Maintenance wavelength | nm | To be defined | + +In this case, example optical power level diagrams are shown below: + +WDM loss of WF1 = 0 dB to 1.5 dB, WDM loss of WF2 = 0 dB to 1.5 dB. + +Optical path penalty of 1 dB is included at the reference points of R/S and S/R at IFPON. + +**Table V.3/G.983.3 – Optical power level diagram (example)** + +| | Ref.(e) | | IF PON
(O ru , O rd ) | | ODN loss | | IF PON
(O lu , O ld ) | | Ref.(c) | | +|-----------------------------|---------|-----|-----------------------------------------------------------|-----|----------|-----|-----------------------------------------------------------|-----|---------|-----| +| Unit | dBm | | dBm | | dB | | dBm | | dBm | | +| Range | Min | Max | Min | Max | Min | Max | Min | Max | Min | Max | +| Downstream | | | | | | | | | | | +| 155M reduced Class B | –30 | –8 | –28.5 | –8 | 10 | 22 | –5.5 | 2 | –4 | 2 | +| 155M reduced Class C | –33 | –11 | –31.5 | –11 | 15 | 27 | –3.5 | 4 | –2 | 4 | +| 622M reduced Class B | –28 | –6 | –26.5 | –6 | 10 | 22 | –3.5 | 4 | –2 | 4 | +| 622M reduced Class C | –33 | –11 | –31.5 | –11 | 15 | 27 | –3.5 | 4 | –2 | 4 | +| Upstream | | | | | | | | | | | +| 155M reduced Class B | –4 | 2 | –5.5 | 2 | 10 | 22 | –28.5 | –8 | –30 | –8 | +| 155M reduced Class C | –2 | 4 | –3.5 | 4 | 15 | 27 | –31.5 | –11 | –33 | –11 | + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/G/T-REC-G.987-201206-I_PDF-E/3468bcffa38de23cef94bfb460ccb301_img.jpg b/marked/G/T-REC-G.987-201206-I_PDF-E/3468bcffa38de23cef94bfb460ccb301_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb1b4b1652c08ab047aea2a17ef528d38a5b5faa --- /dev/null +++ b/marked/G/T-REC-G.987-201206-I_PDF-E/3468bcffa38de23cef94bfb460ccb301_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2db1630118852823ad5402461973ceaf1062125d12154930a1c169728b667ac +size 53618 diff --git a/marked/G/T-REC-G.987-201206-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.987-201206-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e0fadd2c9d79739bb8e83534093d2412b2c5b95 --- /dev/null +++ b/marked/G/T-REC-G.987-201206-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e85d7a23af567ac11960c0b89d0090453c2ac8a6a5f80251f545c9e8d391cee0 +size 31039 diff --git a/marked/G/T-REC-G.987-201206-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/G/T-REC-G.987-201206-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..255d1baf042fef26c6ee2f3c5fc2de09a984ef82 --- /dev/null +++ b/marked/G/T-REC-G.987-201206-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7dafced39c873c12565d2b7134be10304b855ed684e6c3bef9155c89b07fcd2 +size 78717 diff --git a/marked/G/T-REC-G.987-201206-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/G/T-REC-G.987-201206-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13b420e8e2dff03f04e06e9a3ea42e391ed488e2 --- /dev/null +++ b/marked/G/T-REC-G.987-201206-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72ebf46ceef77088bb23e5e05ae447fda09fd91bf1f1173d5264501a22d9b02c +size 4034 diff --git a/marked/G/T-REC-G.987-201206-I_PDF-E/de2d3e89ee4dd60958b64426cd3a81ca_img.jpg b/marked/G/T-REC-G.987-201206-I_PDF-E/de2d3e89ee4dd60958b64426cd3a81ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab8453dd3deab08354ef3c09b98e31e1804aa8aa --- /dev/null +++ b/marked/G/T-REC-G.987-201206-I_PDF-E/de2d3e89ee4dd60958b64426cd3a81ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a89a793c8d96c9505d8d147aa3371934395cd2d7c1300b1fc5cbc9c2b8a69f29 +size 39163 diff --git a/marked/G/T-REC-G.987-201206-I_PDF-E/raw.md b/marked/G/T-REC-G.987-201206-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..79daa7abf578c422b618a7e59e0e7e39a5a0c587 --- /dev/null +++ b/marked/G/T-REC-G.987-201206-I_PDF-E/raw.md @@ -0,0 +1,642 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.987** + +(06/2012) + +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 network (XG-PON) systems: Definitions, abbreviations and acronyms** + +Recommendation ITU-T G.987 + +## 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 | +| 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** + +# **10-Gigabit-capable passive optical network (XG-PON) systems: Definitions, abbreviations and acronyms** + +## **Summary** + +Recommendation ITU-T G.987 contains the common definitions, acronyms, abbreviations and conventions of the ITU-T G.987.x-series Recommendations. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T G.987 | 2010-01-29 | 15 | +| 2.0 | ITU-T G.987 | 2010-10-07 | 15 | +| 3.0 | ITU-T G.987 | 2012-06-13 | 15 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|--------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Optical access architecture terms ..... | 2 | +| 3.3 Optical parameters, power and loss budget terms ..... | 3 | +| 3.4 Transmission convergence layer terms ..... | 4 | +| 4 Abbreviations and acronyms ..... | 6 | +| 5 Conventions ..... | 12 | +| 5.1 Optical access concepts ..... | 12 | +| 5.2 Power and loss budget parameters ..... | 13 | +| 5.3 Sensitivity and overload in the presence of FEC..... | 14 | +| 5.4 Reach and distance ..... | 14 | +| 5.5 Use of the term PON ..... | 15 | +| 5.6 Use of the term ODN..... | 15 | +| 5.7 Use of the terms ONU and ONT ..... | 16 | +| 5.8 Use of the terms T-CONT and Alloc-ID ..... | 16 | +| 5.9 Use of the terms bandwidth assignment and bandwidth allocation ..... | 17 | +| Bibliography..... | 18 | + + + +## Recommendation ITU-T G.987 + +# 10-Gigabit-capable passive optical network (XG-PON) systems: Definitions, abbreviations and acronyms + +# 1 Scope + +This Recommendation contains the common definitions, acronyms, abbreviations and conventions of the ITU-T G.987.x series Recommendations. + +# 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.902] Recommendation ITU-T G.902 (1995), *Framework Recommendation on functional access networks (AN) – Architecture and functions, access types, management and service node aspects.* +- [ITU-T G.987.1] Recommendation ITU-T G.987.1 (2010), *10 Gigabit-capable passive optical networks (XG-PON): General requirements.* +- [ITU-T G.987.2] Recommendation ITU-T G.987.2 revised (2010), *10 Gigabit-capable passive optical networks (XG-PON): Physical media dependent (PMD) layer specification.* +- [ITU-T G.987.3] Recommendation ITU-T G.987.3 (2010), *10 Gigabit-capable passive optical networks (XG-PON): Transmission convergence (TC) layer specification.* +- [ITU-T G.988] Recommendation ITU-T G.988 (2010), *ONU management and control interface (OMCI) specification.* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 access network (AN)** [ITU-T G.902]: An implementation comprising those entities (such as cable plant, transmission facilities, etc.) which provide the required transport bearer capabilities for the provision of telecommunications services between a service node interface (SNI) and each of the associated user-network interfaces (UNI). +- 3.1.2 Ethernet LAN service (E-LAN)** [b-MEF 6.1]: An Ethernet service type that is based on a multipoint-to-multipoint Ethernet virtual connection. +- 3.1.3 Ethernet line service (E-Line)** [b-MEF 6.1]: An Ethernet service type that is based on a point-to-point Ethernet virtual connection. +- 3.1.4 Ethernet tree service (E-Tree)** [b-MEF 6.1]: An Ethernet service type that is based on a rooted-multipoint Ethernet virtual connection. + +- 3.1.5 Ethernet virtual connection (EVC)** [b-MEF 6.1]: An association of UNIs to which the exchange of service frames is limited. +- 3.1.6 service node (SN)** [ITU-T G.902]: A network element that provides access to various switched and/or permanent telecommunication services. +- 3.1.7 service node interface (SNI)** [ITU-T G.902]: An interface which provides customer access to a service node. +- 3.1.8 user-network interface (UNI)** [b-ITU-T I.112]: The interface between the terminal equipment and a network termination at which interface the access protocols apply. +- 3.1.9 1:1 VLAN** [b-DSLF TR-101]: A VLAN forwarding paradigm involving a one-to-one mapping between user port and VLAN. The uniqueness of the mapping is maintained in the access node and across the aggregation network. +- 3.1.10 N:1 VLAN** [b-DSLF TR-101]: A VLAN forwarding paradigm involving many-to-one mapping between user ports and VLAN. The user ports may be located in the same or different access nodes. + +## 3.2 Optical access architecture terms + +This Recommendation defines the following terms: + +- 3.2.1 gigabit-capable passive optical network (G-PON)**: A PON system supporting transmission rates in excess of 1.0 Gbit/s in at least one direction, and implementing the suite of protocols specified in the ITU-T G.984.x series Recommendations. +- 3.2.2 next generation PON (NG-PON)**: In the context of ITU-T standards development activity, a generic term referencing the PON system evolution beyond G-PON. The concept of NG-PON currently includes NG-PON1, where the ODN is maintained from B-PON and G-PON, and NG-PON2, where a redefinition of the ODN is allowed from that defined in B-PON and G-PON. +- 3.2.3 optical access network (OAN)**: A part of an access network whose network elements are interconnected by optical communication channels. + +NOTE – An OAN may or may not extend all the way to the UNI, so that the user-side interface of the OAN does not necessarily coincide with the UNIs of the AN. + +- 3.2.4 optical distribution network (ODN)**: A point-to-multipoint optical fibre infrastructure. A *simple* ODN is entirely passive and is represented by a single-rooted point-to-multipoint tree of optical fibres with splitters, combiners, filters, and possibly other passive optical components. A *composite* ODN consists of two or more passive *segments* interconnected by active devices, each of the segments being either an optical trunk line segment or an optical distribution segment. A passive optical distribution segment is a simple ODN itself. Two ODNs with distinct roots can share a common subtree. +- 3.2.5 optical distribution segment (ODS)**: A simple ODN, that is, a point-to-multipoint optical fibre infrastructure that is entirely passive and is represented by a single-rooted tree of optical fibres with splitters, combiners, filters, and possibly other passive optical components. +- 3.2.6 optical line termination (OLT)**: A network element in an ODN-based optical access network that terminates the root of at least one ODN and provides an OAN SNI. +- 3.2.7 optical network terminal (ONT)**: An ONU supporting a single subscriber. +- 3.2.8 optical network unit (ONU)**: A network element in an ODN-based optical access network that terminates a leaf of the ODN and provides an OAN UNI. +- 3.2.9 optical trunk line (OTL)**: A passive point-to-point segment of a composite ODN. + +**3.2.10 passive optical network (PON) system:** A combination of network elements in an ODN-based optical access network that includes an OLT and multiple ONUs and implements a particular coordinated suite of physical medium dependent layer, transmission convergence layer, and management protocols. + +**3.2.11 10-gigabit-capable passive optical network (XG-PON):** A PON system supporting nominal transmission rates on the order of 10 Gbit/s in at least one direction, and implementing the suite of protocols specified in the ITU-T G.987.x series Recommendations. XG-PON is a subclass of NG-PON1. + +**3.2.12 XG-PON1:** A variant of XG-PON system that operates at a nominal line rate of 10 Gbit/s downstream and 2.5 Gbit/s upstream. + +**3.2.13 XG-PON2:** A variant of XG-PON system that operates at a nominal line rate of 10 Gbit/s downstream and upstream. + +## **3.3 Optical parameters, power and loss budget terms** + +**3.3.1 attenuation:** The total relative optical power loss of an optical signal propagating through the ODN. Attenuation is caused by absorption and scattering of light in the fibre (caused by fibre impurities and imperfections, fluctuations of the refractive index, material dispersion), as well as connectors, splices, splitters, wavelength couplers, attenuators, and other passive optical components. + +**3.3.2 differential fibre distance:** The absolute difference between the fibre distances of two particular ONUs connected to the same OLT PON interface. + +**3.3.3 dispersion:** A physical phenomenon comprising the dependence of the phase or group velocity of a light wave in the medium on its propagation characteristics such as optical frequency (wavelength) or polarization mode. + +**3.3.4 dynamic range:** An optical receiver characteristic that represents the difference between the worst-case sensitivity (i.e., maximum over the operating conditions) and the worst-case overload (i.e., minimum over the operating conditions), and is usually expressed as a ratio of the former to the latter. + +**3.3.5 extinction ratio:** With respect to a digital signal generated by an optical source (laser diode), the ratio of the two optical power levels corresponding to the high and low intensities of light emission. + +**3.3.6 fibre distance:** The overall length of fibre (and, if applicable, equivalent fibre runs representing delay-inducing components) between the R/S and S/R reference points. + +**3.3.7 mean optical launch power:** An optical transmitter characteristic expressing the average optical power of an optical signal transmitted into the fibre and carrying a given digital sequence. When specified as a range, the minimum mean launch power provides the power level that the transmitter should guarantee at all times, and the maximum mean launch power provides the power level that the transmitter should never exceed. When applied to burst mode transmission, the term pertains to the time interval during which the transmitter is fully active, and excludes possible starting and ending transient behaviour. + +**3.3.8 nominal line rate:** The total number of bits that can be physically transferred per unit of time over a communication link. Nominal line rate accounts for useful data as well as for all possible protocol overheads and necessarily exceeds the effective data rate on any given protocol level. + +**3.3.9 optical path penalty (OPP):** The apparent reduction of receiver sensitivity due to distortion of the signal waveform during its transmission over the optical path. The optical path penalty accounts for total degradations including the effects of reflections, intersymbol interference, mode partition noise, and laser chirp. + +**3.3.10 optical return loss (ORL):** The total reflection at the source reference point of the optical signal propagation path associated with both discrete reflections at the refractive index discontinuities and distributed backscattering, such as Rayleigh scattering, along the path. Optical return loss is measured as a ratio of the transmitted power to the reflected power. + +**3.3.11 overload:** A receiver parameter that characterizes the maximum value of the average received optical power to achieve the BER at or below the specified reference level. + +**3.3.12 reflectance:** The reflection from any single discrete reflection point in the optical signal propagation path, which is defined to be the ratio of the reflected optical power present at a point, to the optical power incident to that point. + +**3.3.13 sensitivity:** A receiver parameter that characterizes the minimum value of the average received optical power to achieve the BER at or below the specified reference level. + +**3.3.14 tolerance to reflected power (receiver):** A receiver parameter that characterizes the minimum admissible ratio of the average optical input power incident at the receiver to the average reflected power regarded as a noise. + +**3.3.15 tolerance to reflected power (transmitter):** A transmitter parameter that characterizes the maximum admissible ratio of the average reflected optical transmit power incident at the transmitter to the average optical transmit power. + +**3.3.16 wavelength conversion (WC):** A technology used to convert the frequency (wavelength) of the input optical signal into an output frequency (wavelength) from a predefined wavelength grid. In the case that the input and output frequencies (wavelengths) are distinct, *true wavelength conversion* takes place, whereas if the input and output frequencies are identical, *wavelength-transparent* WC function is used, where the frequency of the optical signal does not change when passing through the WC function. + +## **3.4 Transmission convergence layer terms** + +**3.4.1 activation:** A set of distributed procedures executed by the OLT and the ONUs that allows an inactive ONU to join or resume operations on the PON. The activation process includes three phases: parameter learning, serial number acquisition, and ranging. + +**3.4.2 activation cycle:** A time interval between ONU's consecutive entries into the initial state (O1). + +**3.4.3 bandwidth allocation:** An upstream transmission opportunity granted by the OLT for a specified time interval to a specified traffic-bearing entity within an ONU. + +**3.4.4 dynamic bandwidth assignment (DBA):** A process by which the OLT distributes upstream PON capacity between the traffic-bearing entities within ONUs, based on dynamic indication of their traffic activity and their configured traffic contracts. + +**3.4.5 effective key length:** The number of randomly generated bits of a cryptographic key. The effective key length may be less than the nominal key length of a particular cryptosystem, if a part of the key is replaced by a well-known bit pattern. + +**3.4.6 embedded OAM:** An operation and management channel between the OLT and the ONUs that utilizes the structured overhead fields of the downstream XGTC frame and upstream XGTC burst and supports time-sensitive functions. + +**3.4.7 equalization delay (EqD):** The requisite delay assigned by the OLT to an individual ONU in order to ensure that the ONU's transmissions are precisely aligned on a common OLT-based upstream frame reference. The ONU's equalization delay is assigned as a result of ranging and is subject to in-service updates in the course of burst arrival phase monitoring. + +**3.4.8 ONU management and control interface (OMCI):** An operation and management channel between the OLT and an ONU that is message-based and employs an extendable management information base. + +**3.4.9 physical layer OAM (PLOAM):** An operation and management channel between the OLT and the ONUs that is close to real time and is based on a fixed set of messages. + +**3.4.10 quiet window:** A time interval during which the OLT suppresses all bandwidth allocations to in-service ONUs in order to avoid collisions between their upstream transmissions and the transmissions from ONUs whose burst arrival time is uncertain. The OLT opens a quiet window to allow new ONUs to join the PON and to perform ranging of specific ONUs. + +**3.4.11 ranging:** A procedure of measuring the logical distance between the OLT and any of its subtending ONUs with the objective to determine and assign the appropriate equalization delay, which is necessary to align the ONU's upstream transmissions on a common OLT-based upstream frame reference. Ranging is performed during ONU activation and may be performed while the ONU is in service. + +**3.4.12 ranging grant:** An allocation structure that is addressed to the default Alloc-ID of the ONU and has the PLOAMu flag set. A ranging grant does not specify a data allocation and has the GrantSize of zero. + +**3.4.13 requisite delay:** A general term denoting the total extra delay the OLT may require an ONU to apply to the upstream transmission beyond the ONU's regular response time. The purpose of requisite delay is to compensate for variation of propagation and processing delays of individual ONUs, and to avoid or reduce the probability of collisions between upstream transmissions. + +**3.4.14 serial number grant:** An allocation structure that is addressed to the broadcast Alloc-ID and has the PLOAMu flag set. A serial number grant does not specify a data allocation and has the GrantSize of zero. + +**3.4.15 status reporting DBA (SR-DBA):** A method of dynamic bandwidth assignment that infers the dynamic activity status of the traffic-bearing entities within ONUs based on explicit buffer occupancy reports communicated over the embedded OAM channel. + +**3.4.16 traffic-monitoring DBA (TM-DBA):** A method of dynamic bandwidth assignment that infers the dynamic activity status of the traffic-bearing entities within ONUs based on observation of idle XGEM frame transmissions during upstream bursts. + +**3.4.17 transmission container (T-CONT):** A traffic-bearing object within an ONU that represents a group of logical connections, is managed via the ONU management and control channel (OMCC), and, through its TC layer Alloc-ID, is treated as a single entity for the purpose of upstream bandwidth assignment on the PON. + +**3.4.18 XG-PON encapsulation method (XGEM):** A data frame transport scheme used in XG-PON systems that is connection-oriented and that supports fragmentation of user data frames into variable sized transmission fragments. + +**3.4.19 XG-PON transmission convergence (XGTC) layer:** A protocol layer of the XG-PON protocol suite that is positioned between the physical media dependent (PMD) layer and the XG-PON clients. The XGTC layer is composed of the XGTC service adaptation sublayer, the XGTC framing sublayer, and the XGTC PHY adaptation sublayer. + +**3.4.20 XGEM port:** An abstraction in the XGTC service adaptation sublayer representing a logical connection associated with a specific client packet flow. + +**3.4.21 XGTC framing sublayer:** A sublayer of the XG-PON transmission convergence layer that supports the functions of XGTC frame/burst encapsulation and delineation, embedded OAM processing, and Alloc-ID filtering. + +**3.4.22 XGTC PHY adaptation sublayer:** A sublayer of the XG-PON transmission convergence layer that supports the functions of physical synchronization and delineation, forward error correction (FEC), and scrambling. + +**3.4.23 XGTC service adaptation sublayer:** A sublayer of the XG-PON transmission convergence layer that supports the functions of SDU (user data and OMCI traffic) fragmentation and reassembly, XGEM encapsulation, XGEM frame delineation, and XGEM Port-ID filtering. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|----------|------------------------------------------| +| AES | Advanced Encryption Standard | +| AIS | Alarm Indication Signal | +| Alloc-ID | Allocation Identifier | +| AN | Access Network | +| ANI | Access Node Interface | +| AO | Allocation Overhead | +| APS | Automatic Protection Switching | +| ASE | Amplified Spontaneous Emission | +| ATA | Analog Telephony Adaptor (VoIP) | +| ATM | Asynchronous Transfer Mode | +| AVC | Attribute Value Change | +| BCH | Bose-Chaudhuri-Hocquenghem (code) | +| BE | Best Effort (service category) | +| BER | Bit-Error Ratio | +| BES | Block Errored Second | +| BITS | Building Integrated Timing Source | +| BM-to-CM | Burst Mode to Continuous Mode | +| B-PON | Broadband Passive Optical Network | +| BW | Bandwidth | +| BWmap | Bandwidth Map | +| CAS | Channel Associated Signalling | +| CBS | Committed Block Size | +| CBU | Cell-site Backhauling Unit (ONU type) | +| CES | Circuit Emulation Service | +| CID | Consecutive Identical Digits | +| CIR | Committed Information Rate | +| CLEI | Common Language Equipment Identification | + +| | | +|-----------|--------------------------------------------------------------------| +| CM | Continuous Mode | +| CMAC | Cipher-based Message Authentication Code | +| CM-to-BM | Continuous Mode to Burst Mode | +| CMXGPON_D | Continuous Mode XG-PON downstream bit-stream signal | +| CMXGPON_U | Continuous Mode XG-PON upstream bit-stream signal | +| CO | Central Office | +| CPE | Customer Premises Equipment | +| CRC | Cyclic Redundancy Check | +| CTR | Counter (block cipher mode) | +| CW | Continuous Wave | +| DA | Destination Address | +| DBA | Dynamic Bandwidth Assignment | +| DBRu | Upstream Dynamic Bandwidth Report (indicator bit) | +| DF | Deactivation Failure | +| DFB | Distributed Feedback (laser type) | +| DG | Dying Gasp | +| DHCP | Dynamic Host Configuration Protocol | +| DOW | Drift of Window | +| DSL | Digital Subscriber Line | +| DWDM | Dense Wavelength Division Multiplexing | +| EAP | Extensible Authentication Protocol | +| ECB | Electronic CodeBook (block cipher mode) | +| EDFA | Erbium-Doped Fibre Amplifier | +| E-LAN | Ethernet LAN service | +| E-Line | Ethernet Line service | +| EMS | Element Management System | +| EONU | Embedded Optical Network Unit | +| EPON | Ethernet Passive Optical Network | +| ER | Extinction Ratio | +| ESMC | Ethernet Synchronization Messaging Channel | +| E-Tree | Ethernet Tree Service | +| EVC | Ethernet Virtual Connection | +| FCAPS | Fault, Configuration, Accounting, Performance, Security management | +| FCS | Frame Check Sequence | +| FEC | Forward Error Correction | +| FFS | For Further Study | +| FSM | Finite State Machine | + +| | | +|---------|-----------------------------------------------------------------------------------| +| FTTCell | Fibre to the Cell site base stations | +| FTTx | Fibre to the x (B – building, business; H – home; C – cabinet, curb, P –premises) | +| FWI | Forced Wakeup Indication | +| GEM | G-PON Encapsulation Method | +| G-PON | Gigabit-capable Passive Optical Network | +| GTC | G-PON Transmission Convergence (protocol layer) | +| HEC | Hybrid Error Correction | +| HLend | Header Length – downstream | +| IANA | Internet Assigned Numbers Authority | +| ID | Identifier | +| IFC | Intra-Frame Counter | +| IGMP | Internet Group Management Protocol | +| IK | Integrity Key | +| ILOS | Intermittent Loss of Signal | +| IP | Internet Protocol | +| IPTV | Internet Protocol TV | +| KEK | Key Encryption Key | +| LAN | Local Area Network | +| LF | Last Fragment | +| LoB | Loss of Burst | +| LoDS | Loss of Downstream Synchronization | +| LoOC | Loss of OMCI Channel | +| LoPC | Loss of PLOAM Channel | +| LoS | Loss of Signal | +| LSB | Least Significant Bit (not to be used when the meaning is least significant byte) | +| MAC | Media Access Control | +| MDU | Multi Dwelling Unit (ONU type) | +| ME | Managed Entity | +| MEF | Metro Ethernet Forum | +| MIB | Management Information Base | +| MIC | Message Integrity Check | +| MLD | Multicast Listener Discovery (protocol) | +| MLM | Multi Longitude Mode (laser type) | +| MoCA | Multimedia over Coax Alliance | +| MSB | Most Significant Bit (not to be used when the meaning is most significant byte) | +| MSK | Master Session Key | + +| | | +|-------|-----------------------------------------------------------| +| MTU | Maximum Transmission Unit | +| NA | Non-Assured (service category) | +| NAT | Network Address Translation | +| NGA | Next Generation Access | +| NMS | Network Management System | +| NRZ | Non-Return to Zero (line code) | +| NTP | Network Timing Protocol | +| OA | Optical Amplifier | +| OAM | Operation, Administration, and Management | +| OAN | Optical Access Network | +| OBF | Optical Bandpass Filter | +| ODF | Optical Distribution Frame | +| ODN | Optical Distribution Network | +| ODS | Optical Distribution Segment | +| OEO | Optical-Electronic-Optical (conversion) | +| OFDR | Optical Frequency-Domain Reflectometer | +| OLT | Optical Line Terminal | +| OMCC | ONU Management and Control Channel | +| OMCI | ONU Management and Control Interface | +| ONT | Optical Network Terminal | +| ONU | Optical Network Unit | +| OPEX | Operational Expenditure | +| OPP | Optical Path Penalty | +| ORL | Optical Return Loss | +| OSS | Operations Support System | +| OSSP | Organizational Specific Slow Protocol | +| OTDR | Optical Time-Domain Reflectometer | +| OTL | Optical Trunk Line | +| PBS | Peak Block Size | +| PDU | Protocol Data Unit | +| PHY | Physical interface | +| PIR | Peak Information Rate | +| PIT | PON-ID type | +| PLI | Payload Length Indication | +| PLOAM | Physical Layer Operations, Administration and Maintenance | +| PM | Performance Monitoring | +| PMD | Physical Medium Dependent (protocol layer) | + +| | | +|--------|-------------------------------------------------------------------| +| PON | Passive Optical Network | +| PON-ID | Passive Optical Network Identifier | +| POTS | Plain Old Telephone Service | +| PPPoE | Point-to-Point Protocol over Ethernet | +| PRC | Primary Reference Clock | +| PSBd | Downstream Physical Synchronization Block | +| PSBu | Upstream Physical Synchronization Block | +| PSK | Pre-shared Secret Key | +| PSN | Packet Switched Network | +| PST | PON Section Trace (PLOAM message) | +| PSync | Physical Synchronization Sequence | +| PTP | Precision Timing Protocol | +| QoS | Quality of Service | +| R/S | Reference point at the interface of the ONU to the ODN | +| R'/S' | Reference point at the interface of the Reach extender to the OTL | +| RE | Reach Extender | +| RF | Radio Frequency | +| RG | Residential Gateway | +| RMS | Root Mean Square | +| RNC | Radio Network Controller | +| RS | Reed-Solomon (block code) | +| RSOA | Reflective Semiconductor Optical Amplifier | +| RTC | Real Time Clock (protocol) | +| RTCP | RTP Control Protocol | +| RTD | Round-Trip Delay | +| RTP | Real-time Transport Protocol | +| Rx | Receiver | +| S'/R' | Reference point at the interface of Reach extender to ODN | +| S/R | Reference point at the interface of the OLT to the ODN | +| SA | Sleep Allowed (PLOAM message) | +| SA | Source Address | +| SBU | Small Business Unit (ONU type) | +| SD | Signal Degrade | +| SDU | Service Data Unit | +| SeqNo | Sequence Number | +| SES | Severely Errored Second (-L: -line, -P: path, -FE: far-end) | +| SF | Signal Fail | + +| | | +|--------|-----------------------------------------| +| SFC | SuperFrame Counter | +| SFD | Start Frame Delimiter | +| SFU | Single Family Unit (ONU type) | +| SIP | Session Initiation Protocol | +| SK | Session Key | +| SLM | Single Longitude Mode (laser type) | +| SN | Serial Number | +| SN | Service Node | +| SNI | Service Node Interface | +| SNMP | Simple Network Management Protocol | +| SNR | Signal to Noise Ratio | +| SOA | Semiconductor Optical Amplifier | +| SR | Sleep Request (PLOAM message) | +| SR | Status Reporting | +| SRS | Stimulated Raman Scattering | +| SUF | Start-up Failure | +| TBD | To be defined | +| TC | Transmission Convergence | +| T-CONT | Transmission Container | +| TCP | Transmission Control Protocol | +| TDM | Time Division Multiplexing | +| TIW | Transmission Interference Warning | +| TLS | Transparent LAN Service | +| TM | Traffic Monitoring | +| ToD | Time of Day | +| TOL | Transmit optical level | +| Tx | Transmitter | +| UDP | User Datagram Protocol | +| UI | Unit Interval | +| UNI | User Network Interface | +| VBES | VLAN-based Business Ethernet Services | +| VDSL | Very high speed Digital Subscriber Line | +| VID | VLAN Identifier | +| VLAN | Virtual Local Area Network | +| VoIP | Voice over IP | +| VPN | Virtual Private Network | +| V-Rx | Video Receiver | + +| | | +|--------|------------------------------------------------------------------------------| +| VSSN | Vendor-Specific Serial Number | +| V-Tx | Video Transmitter | +| WBF | Wavelength Blocking Filter | +| WC | Wavelength Conversion | +| WC-RE | WC-enabled Reach Extender | +| WDM | Wavelength Division Multiplexing | +| WDM1 | Wavelength Division Multiplexor 1 (coexistence device) | +| WDM1r | Wavelength Division Multiplexor 1 revised (coexistence device) | +| WDM1rn | Wavelength Division Multiplexor 1 revised – narrow-band (coexistence device) | +| WFQ | Weighted Fair Queuing | +| WRR | Weighted Round Robin | +| X/S | Crosstalk-to-Signal ratio | +| XGEM | XG-PON Encapsulation Method | +| XG-PON | 10-Gigabit-capable Passive Optical Network | +| XGTC | XG-PON Transmission Convergence (protocol layer) | + +# 5 Conventions + +## 5.1 Optical access concepts + +This Recommendation adopts the basic definition of access network (AN) provided by [ITU-T G.902] and formalizes the definition of optical distribution network, deriving the key PON-related definitions based on these two concepts. An example of an access network architecture satisfying the ITU-T G.987 definition system is shown in Figure 5-1. + +![Figure 5-1: Reference access network architecture diagram. It shows a PON System containing an OLT connected to an SNI. The OLT is connected to an ODN (composite) which includes an ODS and an OTL. The ODN (composite) is connected to an ONU. The ONU is connected to a Splitter, which is connected to an RE. The RE is connected to an ODN (simple) which includes an ODS = ODN (simple) and a Splitter. The Splitter is connected to three ONUs. The ONUs are connected to a UNI. The Access network (AN) [ITU-T G.902] is shown as a dashed line enclosing the ODN (simple) and the ONUs. The diagram is labeled G.987.1(10)_F5-1.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +Figure 5-1: Reference access network architecture diagram. It shows a PON System containing an OLT connected to an SNI. The OLT is connected to an ODN (composite) which includes an ODS and an OTL. The ODN (composite) is connected to an ONU. The ONU is connected to a Splitter, which is connected to an RE. The RE is connected to an ODN (simple) which includes an ODS = ODN (simple) and a Splitter. The Splitter is connected to three ONUs. The ONUs are connected to a UNI. The Access network (AN) [ITU-T G.902] is shown as a dashed line enclosing the ODN (simple) and the ONUs. The diagram is labeled G.987.1(10)\_F5-1. + +Figure 5-1 – Reference access network architecture + +## 5.2 Power and loss budget parameters + +The relationships between power and loss budget parameters are captured in Figure 5-2. + +![Figure 5-2: Relationship between power budget and loss budget parameters diagram. It is a graph with 'Loss budget' on the left and 'Power budget' on the right. The left side shows 'Maximum OPP' and 'Max allowed loss' (which includes distance attenuation, splitter loss, total connector loss, total fusion splice loss, WDM1r loss, and Raman loss). The right side shows 'Max Tx launch power', 'Min Tx launch power', '0 dBm', 'Rx overload', and 'Rx sensitivity'. A diagonal line represents 'Min required loss'. The 'Dynamic range' is indicated between 'Rx overload' and 'Rx sensitivity'. The diagram is labeled G.987(12)_F5-2.](3468bcffa38de23cef94bfb460ccb301_img.jpg) + +Figure 5-2: Relationship between power budget and loss budget parameters diagram. It is a graph with 'Loss budget' on the left and 'Power budget' on the right. The left side shows 'Maximum OPP' and 'Max allowed loss' (which includes distance attenuation, splitter loss, total connector loss, total fusion splice loss, WDM1r loss, and Raman loss). The right side shows 'Max Tx launch power', 'Min Tx launch power', '0 dBm', 'Rx overload', and 'Rx sensitivity'. A diagonal line represents 'Min required loss'. The 'Dynamic range' is indicated between 'Rx overload' and 'Rx sensitivity'. The diagram is labeled G.987(12)\_F5-2. + +Figure 5-2 – Relationship between power budget and loss budget parameters + +The details of the dynamic range concept definition are illustrated in Figure 5-3. The receiver sensitivity and overload are defined, respectively, as the minimum and maximum average received optical power at which the BER at the receiver output remains at or below the specified reference level. The observed values of receiver sensitivity and overload may vary as the operating conditions change. The operation conditions that affect receiver sensitivity and overload may include the transmitter extinction ratio, connector degradations, effects of ageing, etc. In definition of the dynamic range, both receiver sensitivity and receiver overload are represented by their respective worst-case values, i.e., maximum sensitivity and minimum overload over the range of operating conditions. + +![Figure 5-3: Rx output BER as a function of received optical power, and the definition of dynamic range. The graph shows a U-shaped curve representing BER versus Power. A horizontal line indicates the 'Reference BER level'. The curve intersects this line at two points. The left intersection is labeled 'Sensitivity variation' and the right is 'Overload variation'. The region between these two points, where the BER is below the reference level, is labeled 'Dynamic range: worst-case sensitivity and worst-case overload'. The graph is labeled G.987(12)_F5-3.](de2d3e89ee4dd60958b64426cd3a81ca_img.jpg) + +Figure 5-3: Rx output BER as a function of received optical power, and the definition of dynamic range. The graph shows a U-shaped curve representing BER versus Power. A horizontal line indicates the 'Reference BER level'. The curve intersects this line at two points. The left intersection is labeled 'Sensitivity variation' and the right is 'Overload variation'. The region between these two points, where the BER is below the reference level, is labeled 'Dynamic range: worst-case sensitivity and worst-case overload'. The graph is labeled G.987(12)\_F5-3. + +**Figure 5-3 – Rx output BER as a function of received optical power, and the definition of dynamic range** + +## 5.3 Sensitivity and overload in the presence of FEC + +To simplify optical component verification, [ITU-T G.987.2] specifies the sensitivity and overload at the high reference BER level, which corresponds to the Rx output and the FEC decoder input. It is assumed that the FEC algorithms specified, respectively, for continuous mode downstream and burst mode upstream transmission are sufficiently strong to achieve the BER level of $10^{-12}$ or better at the FEC decoder output. See [b-ITU-T G-Sup.39] for further discussion. + +## 5.4 Reach and distance + +The ITU-T G.987.x series of Recommendations addresses the linear extent parameters of XG-PON using the single concept of fibre distance. An ONU is characterized by its fibre distance, and for each pair of ONUs on the same OLT PON interface, the differential fibre distance is the difference between the two individual fibre distances. Each specific PMD layer parameter set contains a provision to support a specific maximum fibre distance. The XG-PON TC layer specification contains a provision to support specific ranges of maximum fibre distance and maximum differential fibre distance. These ranges can be configurable for a given system. One can expect that for each XG-PON deployment, the configured TC layer maximum fibre distance will match the maximum fibre distance supported by the selected PMD layer parameter set. Fibre distance concepts are illustrated in Figure 5-4. + +![Figure 5-4 – Fibre distance concepts. A diagram showing a central OLT (Optical Line Terminal) connected to multiple ONUs (Optical Network Units). The OLT is at the center of a circle. The minimum distance to an ONU is labeled ONU_min. The maximum distance to an ONU is labeled ONU_max. The maximum differential fibre distance is indicated by a double-headed arrow between the OLT and the outer edge of the circle. The maximum fibre distance is indicated by a single-headed arrow from the OLT to the outer edge of the circle. The diagram is labeled G.987(12)_F5-4.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Figure 5-4 – Fibre distance concepts. A diagram showing a central OLT (Optical Line Terminal) connected to multiple ONUs (Optical Network Units). The OLT is at the center of a circle. The minimum distance to an ONU is labeled ONU\_min. The maximum distance to an ONU is labeled ONU\_max. The maximum differential fibre distance is indicated by a double-headed arrow between the OLT and the outer edge of the circle. The maximum fibre distance is indicated by a single-headed arrow from the OLT to the outer edge of the circle. The diagram is labeled G.987(12)\_F5-4. + +**Figure 5-4 – Fibre distance concepts** + +The physical reach system parameter of the ITU-T G.984 series of Recommendations corresponds to the maximum fibre distance supported by the system PMD layer. The logical reach system parameter of the ITU-T G.984 series corresponds to the maximum fibre distance supported by the system TC layer. + +## 5.5 Use of the term PON + +Historically, the term PON was introduced to describe a point-to-multipoint fibre infrastructure composed of exclusively passive optical components. This strict-sense usage was soon naturally extended to include a fibre-in-the-loop communication system employing such an infrastructure and using time-division multiplexing to share the available digital bandwidth among many subscribers (TDM PON). As new types of PON-based systems were introduced, leveraging various TDM transport mechanisms (B-PON, G-PON, EPON) or alternative multi-access methods (WDM-PON), it became common to use the word PON with appropriate qualification in reference to the specific architectural variations. While the term remained overloaded, referring in different contexts to a network, a system, architecture or technology, all the referenced entities shared a common attribute of containing, using or relying upon a fibre infrastructure with no active (electronic) components between the central office interface and the user equipment interface. More recently, introduction of active reach extenders within the optical distribution network as defined in [b-ITU-T G.984.6] created a paradoxical situation when an infrastructural component of a G-PON system may not be entirely passive, that is, nominally, no longer a PON. Thus, it became apparent that the excessive overloading of what was once meant to be a precise term may adversely impact the clarity of a technical presentation. + +This current series of Recommendations deliberately restricts the usage of the term PON to the contexts where it denotes a system, that is, a combination of network elements including at least one OLT and multiple ONUs interconnected by an ODN that implements a particular coordinated suite of physical medium dependent layer, transmission convergence layer, and management protocols. It also strives to provide a consistent, unambiguous, and extensible definition system that allows supporting efficient communication on the subject. + +## 5.6 Use of the term ODN + +In the ITU-T G.983 B-PON and ITU-T G.984 G-PON series of Recommendations (prior to [b-ITU-T G.984.6]), the term optical distribution network (ODN) refers to a passive point-to-multipoint distribution means extending from the user-facing interface of the OLT to the + +network-facing interfaces of the ONUs. The introduction of active reach extenders and the concept of dual-homing call for a revision of the term's scope and usage, as the fibre-based distribution network extending between the OLT and ONU interfaces may be neither point-to-multipoint nor strictly passive. + +This current series of Recommendations endorses a generalized usage of the term ODN to denote a point-to-multipoint fibre infrastructure, which is not required to be entirely passive. In the contexts where the internal structure of the ODN is not a concern, it is the ODN that interconnects the OLT and the ONUs to form a PON system. In the contexts where the internal structure of the ODN is relevant, two types of ODNs can be distinguished. A *simple* ODN is entirely passive and is represented by a single-rooted point-to-multipoint tree of optical fibres with splitters, combiners, filters, and possibly other passive optical components. A *composite* ODN consists of two or more *segments* interconnected by active devices, each of the segments being either an optical trunk line segment or an optical distribution segment. A passive optical distribution segment in is a simple ODN itself. The definition allows two ODNs with distinct roots to share a common subtree, thus supporting the notions of dual-homing and protection within the definition system. + +## 5.7 Use of the terms ONU and ONT + +Throughout the ITU-T G.987.x series of Recommendations, the network element interfacing the end-user access facilities and the ODN is referred to as an ONU, or an optical network unit, irrespective of the number and type of user interfaces or the depth of fibre deployment. Historically, the term ONT, or optical network terminal/termination, has been used either interchangeably with ONU or with the particular semantics of "an ONU that is used for fibre to the home (FTTH) and includes the user port function" (see [b-ITU-T G.983.1]), or "a single-subscriber ONU" (see [b-ITU-T G.984.1] and other documents of the ITU-T G.984 series). This Recommendation follows the latter approach in defining ONT. Note, however, that while this definition captures one established trade interpretation of the term, the concept itself is not used as a part of the ITU-T G.987 reference access architecture. + +Outside of the ITU-T G.987.x series scope, alternative interpretations may apply and, therefore, the reader is advised to clarify the exact meaning of the term in each specific context. In particular, in some external contexts, the term ONT may be used generically to refer to any device terminating a leaf of the ODN. + +## 5.8 Use of the terms T-CONT and Alloc-ID + +A transmission container (T-CONT) is an OMCI managed entity representing a group of logical connections that appear as a single entity for the purpose of upstream bandwidth assignment in a PON system. + +For a given ONU, the number of supported T-CONTs is fixed. The ONU autonomously creates all the supported T-CONT instances during ONU activation or upon OMCI MIB reset. The OLT uses the OMCC to discover the number of T-CONT instances supported by a given ONU and to manage those instances. + +The *Allocation identifier* (*Alloc-ID*) is a 14 bit number that the OLT assigns to an ONU to identify a traffic-bearing entity that is a recipient of upstream bandwidth allocations within that ONU. Such a traffic-bearing entity is usually represented by a T-CONT, but may also be represented by an internal non-managed structure. + +Each ONU is assigned at least its default Alloc-ID and may be explicitly assigned additional Alloc-IDs per OLT's discretion. + +To activate a T-CONT instance for carrying the upstream user traffic, the OLT has to establish a mapping between the T-CONT instance and an Alloc-ID, which was previously assigned to the given ONU via the PLOAM messaging channel. Mapping of T-CONTs to Alloc-IDs is performed + +via the OMCC. The OMCC itself is mapped, in the upstream direction, to the default Alloc-ID. This mapping is fixed; it cannot be managed via the OMCI MIB and it should survive OMCI MIB reset. + +In many cases the mapping between T-CONTs and Alloc-IDs is one-to-one, strictly speaking, it is the Alloc-ID, not a T-CONT, which is visible at the TC layer of the system. + +## **5.9 Use of the terms bandwidth assignment and bandwidth allocation** + +The term "bandwidth assignment" refers to the distribution of the upstream PON capacity between the ONUs' traffic-bearing entities using certain isolation and fairness criteria. In static bandwidth assignment, the said criteria are based exclusively on the provisioned parameters of the traffic contracts, and the bandwidth is assigned on the timescale of the individual service provisioning. In dynamic bandwidth assignment, the activity status of the traffic-bearing entities is taken into consideration along with the parameters of the traffic contracts, and the bandwidth assignment is periodically refined. + +The term "bandwidth allocation", on the other hand, denotes the process of granting individual transmission opportunities to the ONUs' traffic-bearing entities on the timescale of a single PHY frame. The process of bandwidth allocation uses the assigned bandwidth values as an input and produces the per-frame bandwidth maps as an output. It also accounts for PLOAM messaging and DBRu overhead requirements and the short-term disturbances associated with the creation of quiet windows for serial number acquisition and ranging purposes. + +# 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.1] Recommendation ITU-T G.984.1 (2008), *Gigabit-capable passive optical networks (GPON): General characteristics*. +- [b-ITU-T G.984.6] Recommendation ITU-T G.984.6 (2008), *Gigabit-capable passive optical networks (GPON): Reach extension*. +- [b-ITU-T G-Sup.39] ITU-T G-series Recommendations – Supplement 39 (2008), *Optical system design and engineering considerations*. +- [b-ITU-T I.112] Recommendation ITU-T I.112 (1993), *Vocabulary of terms for ISDNs*. +- [b-DSLF TR-101] Broadband Forum (formerly, DSL Forum) Technical Report TR-101 (2006), *Migration to Ethernet Based DSL Aggregation*. +- [b-MEF 6.1] MEF Technical Specification MEF 6.1 (2008), *Ethernet Services Definitions – Phase 2*. + + + +## 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.989.1-201303-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg b/marked/G/T-REC-G.989.1-201303-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec5fe921b1811e21e30b6023c5f38fbb0e2a2f84 --- /dev/null +++ b/marked/G/T-REC-G.989.1-201303-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4eff9866d9f9035f97a9e563660dd1bc27d21a251719dc204047318dd5df9f90 +size 101808 diff --git a/marked/G/T-REC-G.989.1-201303-I_PDF-E/7bed2d7c96d86bf922295a1252da52a5_img.jpg b/marked/G/T-REC-G.989.1-201303-I_PDF-E/7bed2d7c96d86bf922295a1252da52a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a20d72b8383b2b580648f28a1850970c5f3f0913 --- /dev/null +++ b/marked/G/T-REC-G.989.1-201303-I_PDF-E/7bed2d7c96d86bf922295a1252da52a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b475afae054f2fc15989cf52b48a7cc28b1a8ec3c1de9883a2030e2e279eab7 +size 59745 diff --git a/marked/G/T-REC-G.989.1-201303-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/G/T-REC-G.989.1-201303-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..007c1980afcf79b08af620838765a70ed49e48db --- /dev/null +++ b/marked/G/T-REC-G.989.1-201303-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7892cfc054d8d59fafada3a72928ddf9db33ed3643414bb601a1b26920859dbf +size 6560 diff --git a/marked/G/T-REC-G.989.1-201303-I_PDF-E/8a597e344d10e36bbb2f243f6c4e74c6_img.jpg b/marked/G/T-REC-G.989.1-201303-I_PDF-E/8a597e344d10e36bbb2f243f6c4e74c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bc08122ef0a0374df67ef0c971e39c8f1f77a71 --- /dev/null +++ b/marked/G/T-REC-G.989.1-201303-I_PDF-E/8a597e344d10e36bbb2f243f6c4e74c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d3ee2b1ce917b51a45f53d72b6c5e40357fce74f7c6e3c82f5d733b14931160 +size 47156 diff --git a/marked/G/T-REC-G.989.1-201303-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/marked/G/T-REC-G.989.1-201303-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc9089085612b0ce79c15341ac56947a30f23a86 --- /dev/null +++ b/marked/G/T-REC-G.989.1-201303-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7884d9fc2e4aa5611b25f471b75010103b663081e2e66b8529f7ecb902b7f5e1 +size 25946 diff --git a/marked/G/T-REC-G.989.1-201303-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/G/T-REC-G.989.1-201303-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbb463dbad8d84277aeb6957c0fc20b662ccfa56 --- /dev/null +++ b/marked/G/T-REC-G.989.1-201303-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e4794c6db5538d3a7c648de57042756e9504603bfc5059b17e5afba8b752f5b +size 33274 diff --git a/marked/G/T-REC-G.989.1-201303-I_PDF-E/raw.md b/marked/G/T-REC-G.989.1-201303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..db5f30a54aa78f738bdeeca25142e750eee25cb8 --- /dev/null +++ b/marked/G/T-REC-G.989.1-201303-I_PDF-E/raw.md @@ -0,0 +1,662 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.989.1** + +(03/2013) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital sections and digital line system – Optical line +systems for local and access networks + +# --- **40-Gigabit-capable passive optical networks (NG-PON2): General requirements** + +Recommendation ITU-T G.989.1 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font. + +ITU logo + +## ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600–G.699 | +| 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 | +| 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.989.1** + +# **40-Gigabit-capable passive optical networks (NG-PON2): General requirements** + +## **Summary** + +Recommendation ITU-T G.989 series describes 40-Gigabit-capable passive optical network (NG-PON2) systems in an optical access network for residential, business, mobile backhaul and other applications. + +Recommendation ITU-T G.989.1 addresses the general requirements of 40-Gigabit-capable passive optical network (NG-PON2) systems, in order to guide and motivate the physical layer and the transmission convergence layer specifications. This Recommendation includes principal deployment configurations, migration scenarios from legacy PON systems, and system requirements. This Recommendation also includes the service and operational requirements to provide a robust and flexible optical access network supporting all access applications. + +The physical layer specifications for the NG-PON2 physical media dependent (PMD) layer are described in Recommendation ITU-T G.989.2. The transmission convergence (TC) layer is described in Recommendation ITU-T G.987.3, with unique modifications for NG-PON2 systems captured in Recommendation ITU-T G.989.3. The ONU management and control interface (OMCI) specifications are described in Recommendation ITU-T G.988 for NG-PON2 extensions. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T G.989.1 | 2013-03-09 | 15 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | NG-PON2 specific terms..... | 2 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Architecture ..... | 4 | +| 5.1 | System overview ..... | 4 | +| 5.2 | Network reference architecture ..... | 4 | +| 6 | Migration ..... | 5 | +| 6.1 | Co-existence, stacking and overlay ..... | 6 | +| 6.2 | Migration path options ..... | 8 | +| 6.3 | Support for legacy ODN..... | 8 | +| 7 | Service requirements ..... | 9 | +| 7.1 | Service specific requirements..... | 9 | +| 7.2 | User node interfaces (UNIs)..... | 9 | +| 7.3 | Service node interfaces (SNIs) ..... | 10 | +| 7.4 | Access node interfaces (ANIs) ..... | 11 | +| 7.5 | System flexibility..... | 11 | +| 8 | Physical layer requirements ..... | 11 | +| 8.1 | Capacity (per feeder and per user)..... | 11 | +| 8.2 | Fibre reach (passive and active) ..... | 12 | +| 8.3 | Split ratio (ONUs per ODN)..... | 12 | +| 8.4 | Optical spectrum issues and availability ..... | 13 | +| 9 | System requirements..... | 14 | +| 9.1 | Colourless ONUs..... | 14 | +| 9.2 | Spectral flexibility ..... | 14 | +| 9.3 | Rogue ONU/OLT detection and mitigation ..... | 14 | +| 9.4 | Resilience and redundancy requirements ..... | 14 | +| 9.5 | Reach extender requirements ..... | 15 | +| 9.6 | Power reduction..... | 15 | +| 9.7 | OAM functions..... | 16 | +| 9.8 | Provisioning and management ..... | 16 | +| 9.9 | Environmental and physical requirements ..... | 16 | +| 9.10 | Eye safety ..... | 16 | +| 9.11 | Interoperability ..... | 17 | +| | Bibliography..... | 18 | + + + +## Recommendation ITU-T G.989.1 + +# 40-Gigabit-capable passive optical networks (NG-PON2): General requirements + +# 1 Scope + +This Recommendation describes the general requirements of NG-PON2 systems supporting a 40-Gbit/s capable aggregate downstream capacity for residential, business, mobile backhaul, and other applications. This Recommendation includes the principal deployment configurations, migration scenarios from legacy PON systems, and system requirements. This Recommendation also includes the service and operational requirements to provide for a robust and flexible optical access network supporting all access applications. + +The NG-PON2 system is capable of meeting the needs of a wide range of networks in diverse markets and is deployable in numerous applications in an efficient manner. As much as possible, this Recommendation maintains characteristics from legacy PON systems: [ITU-T G.982], [ITU-T G.983], [ITU-T G.984], and [ITU-T G.987] series of Recommendations. This is to promote backward compatibility with existing optical distribution networks (ODNs) that comply with those Recommendations and re-use established technical capabilities as much as possible. This Recommendation also describes smooth migration scenarios from legacy PON systems to NG-PON2 systems. Furthermore, NG-PON2 systems are expected to meet bandwidth growth and enable new revenue streams on legacy ODNs as well as supporting greenfield applications over new ODNs. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.652] Recommendation ITU-T G.652 (2005), *Characteristics of a single-mode optical fibre cable*. +- [ITU-T G.902] Recommendation ITU-T G.902 (1995), *Framework Recommendation on functional access networks (AN) – Architecture and functions, access types, management and service node aspects*. +- [ITU-T G.982] Recommendation ITU-T 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 ITU-T G.983.1 (2005), *Broadband optical access systems based on Passive Optical Networks (PON)*. +- [ITU-T G.983.2] Recommendation ITU-T G.983.2 (2005), *ONT management and control interface specification for B-PON*. +- [ITU-T G.983.3] Recommendation ITU-T G.983.3 (2001), *A broadband optical access system with increased service capability by wavelength allocation*. +- [ITU-T G.984.1] Recommendation ITU-T G.984.1 (2008), *Gigabit-capable Passive Optical Networks (GPON): General characteristics*. + +- [ITU-T G.984.2] Recommendation ITU-T G.984.2 (2008), *Gigabit-capable Passive Optical Networks (GPON): Physical Media Dependent (PMD) layer specifications.* +- [ITU-T G.984.3] Recommendation ITU-T G.984.3 (2008), *Gigabit-capable Passive Optical Networks (GPON): Transmission convergence layer specification.* +- [ITU-T G.984.4] Recommendation ITU-T G.984.4 (2008), *Gigabit-capable Passive Optical Networks (GPON): ONT management and control interface specification.* +- [ITU-T G.984.5] Recommendation ITU-T G.984.5 (2007), *Gigabit-capable Passive Optical Networks (GPON): Enhancement band for Gigabit-capable Passive Optical Networks.* +- [ITU-T G.987] Recommendation ITU-T G.987 (2012), *10-Gigabit-capable Passive Optical Networks (XG-PON) systems: Definitions, abbreviations and acronyms.* +- [ITU-T G.987.1] Recommendation ITU-T G.987.1 (2010), *10-Gigabit-capable Passive Optical Networks (XG-PON): General requirements.* +- [ITU-T G.987.2] Recommendation ITU-T G.987.2 (2010), *10-Gigabit-capable Passive Optical Networks (XG-PON): Physical Media Dependent (PMD) layer specification.* +- [ITU-T G.987.3] Recommendation ITU-T G.987.3 (2010), *10-Gigabit-capable Passive Optical Networks (XG-PON): Transmission convergence (TC) layer specification.* +- [ITU-T G.988] Recommendation ITU-T G.988 (2010), *ONU management and control interface specification (OMCI).* +- [ITU-T J.185] Recommendation ITU-T J.185 (2012), *Transmission equipment for transferring multi-channel television signals over optical access networks by frequency modulation conversion.* +- [ITU-T J.186] Recommendation ITU-T J.186 (2008), *Transmission equipment for multi-channel television signals over optical access networks by sub-carrier multiplexing (SCM).* +- [IEC 60825-2] IEC International Standard 60825-2 (2004), *Safety of laser products – Part 2: Safety of optical fibre communication systems (OFCS).* +- [IEEE 802.3] IEEE 802.3-2012, *IEEE Standard for Information Technology – Telecommunications and Information exchange between systems – Local and metropolitan area networks – Specific requirements, Part 3: Ethernet.* + +# 3 Definitions + +See clause 3 of [ITU-T G.987]. + +## 3.1 NG-PON2 specific terms + +This Recommendation uses the following NG-PON2 specific definitions: + +**3.1.1 TWDM PON:** A time and wavelength division multiplexing passive optical network (TWDM PON) is a multiple wavelength PON solution in which each wavelength is shared between multiple optical network units (ONUs) by employing time division multiplexing and multiple access mechanisms. + +**3.1.2 PtP WDM:** Point-to-point wavelength division multiplexing (PtP WDM) is a multiple wavelength PON solution that provides a dedicated wavelength per ONU in both downstream and upstream directions. The defining characteristic of a PtP WDM is that each ONU is served by one or more dedicated wavelengths. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following NG-PON2 specific abbreviations and acronyms: + +| | | +|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| ANI | Access Node Interface | +| APC | Angled Physical Contact | +| BBU | Baseband Unit | +| CD | Chromatic Dispersion | +| CE | Coexistence Element | +| CPRI | Common Public Radio Interface | +| eNode B | Evolved Node Base station | +| FTTx | Fibre to the x (B – building, business; H – home; C – cabinet, curb) | +| G-PON | Gigabit-capable Passive Optical Network, [ITU-T G.984.x]. Unless explicitly stated otherwise, this term also refers generically to [ITU-T G.987] XG-PON. | +| LTE | Long Term Evolution | +| MDU/SFU | Multi-Dwelling Unit/Single-Family Unit | +| ODN | Optical Distribution Network | +| ODS | Optical Distribution Segment | +| OLT | Optical Line Terminal | +| ONU | Optical Network Unit | +| PON | Passive Optical Network | +| PtP WDM | Point-to-Point Wavelength Division Multiplexing | +| QoS | Quality of Service | +| RE | Reach Extender | +| RF | Radio Frequency | +| RRU | Remote Radio Unit | +| R'/S' | Reach extender interface to optical trunk line [ITU-T G.988] | +| SMF | Single Mode Fibre | +| S'/R' | Reach extender interface to optical distribution network [ITU-T G.988] | +| TC | Transmission Convergence | +| TWDM | Time and Wavelength Division Multiplexing | +| UNI | User Node Interface | +| UPC | Ultra Physical Contact | +| WDM | Wavelength Division Multiplexing | +| XG-PON | 10-Gigabit Passive Optical Network [ITU-T G.987] | + +# 5 Architecture + +## 5.1 System overview + +The following provides an overview of NG-PON2 system requirements. Additional requirement details are provided in specific sections within this Recommendation. + +NG-PON2 systems requirements include support for: + +- Multiple wavelength channel TWDM architecture +- 4-8 TWDM channel pairs (each channel pair comprising one downstream and one upstream wavelength channel), configurable for incremental growth starting from one deployed channel pair (i.e., not all channel pairs need to be active); for example, "pay as you grow" capability of TWDM channels populating in the OLT. +- Downstream and upstream nominal line rates per channel: + - 10 Gbit/s downstream and 10 Gbit/s upstream + - 10 Gbit/s downstream and 2.5 Gbit/s upstream + - 2.5 Gbit/s downstream and 2.5 Gbit/s upstream +- Passive fibre reach of at least 40 km and maximum differential fibre distance of up to 40 km with configurable maximum differential fibre distance as 20 km and optionally 40 km, +- Capability to reach 60 km, preferably with passive outside plant +- Support for a split ratio of at least 1:256 + +NG-PON2 systems require flexibility to balance trade-offs in speed, distance, and split ratios for various applications. The set of parameter combinations that are supported by the system must include: + +- 40 Gbit/s downstream capacity and 20 km reach with at least 1:64 split +- 10 Gbit/s upstream capacity and 20 km reach with at least 1:64 split +- Access to peak rates of 10/2.5 Gbit/s downstream/upstream +- Longer distances with lower split ratios are also possible + +NG-PON2 systems may also support: + +- 40 Gbit/s upstream capacity with 10 Gbit/s per upstream channel and 20 km reach with at least 1:64 split +- 2.5 Gbit/s per downstream channel and 2.5 Gbit/s per upstream channel with 40 km reach and 1:32 split +- 10 Gbit/s per downstream channel and 10 Gbit/s per upstream channel with 40 km reach and 1:32 split +- Access to peak rates of 10/10 Gbit/s downstream/upstream +- Tunable point-to-point WDM with the capability to co-exist with other PON systems + +## 5.2 Network reference architecture + +Figure 5-1 depicts the functional optical access network architecture and reference points that apply to NG-PON2 systems with legacy systems coexistence. The ODN consists of the splitter and the coexistence element (WDM) and, optionally, reach extenders may also be used in the ODN. + +The optical technologies specified for NG-PON2 systems shall be compatible with legacy power splitting ODNs (that is an ODN that may contain power splitters and a coexistence element). Optical technologies that specifically require wavelength filtering in the ODN are precluded from this Recommendation. NG-PON2 systems also support new (greenfield) ODNs that may consist of wavelength filters only, or a combination of both wavelength and power splitters. + +![Functional reference architecture and points for NG-PON2 system coexistence with legacy systems. The diagram shows the flow from Service Network Interface (SNI) to User Network Interface (UNI) through an Optical Distribution Network (ODN). On the SNI side, various components like RF video HE, OTDR, GPON OLT, XGPON OLT, and multiple NG-PON2 OLTs (Port-1 to Port-n) are connected. These connect to a central 'CEx' (co-existence element) or a 'WM' (wavelength multiplexer). The 'CEx' connects to a 'Splitter' in the ODN. The 'Splitter' then connects to various ONUs on the UNI side, including GPON ONU, XGPON ONU, NGPON2 ONU, and combinations with RF video (GPON + RF ONU, XGPON + RF ONU, NGPON2 + RF ONU). Interfaces are labeled as IF_Video, IF_OTDR, IF_GPON, IF_XGPON, and IF_NGPON2. A key defines the abbreviations: CG = Channel group, CP = Channel pair, CEx = Instance of co-existence element, HE = Head end, WM = Wavelength multiplexer. The diagram is labeled G.989.1(13)_F5-1.](5b4e774d63e0e0ed73801a9247755e5f_img.jpg) + +Key: + CG = Channel group + CP = Channel pair + CEx = Instance of co-existence element + HE = Head end + WM = Wavelength multiplexer + +G.989.1(13)\_F5-1 + +Functional reference architecture and points for NG-PON2 system coexistence with legacy systems. The diagram shows the flow from Service Network Interface (SNI) to User Network Interface (UNI) through an Optical Distribution Network (ODN). On the SNI side, various components like RF video HE, OTDR, GPON OLT, XGPON OLT, and multiple NG-PON2 OLTs (Port-1 to Port-n) are connected. These connect to a central 'CEx' (co-existence element) or a 'WM' (wavelength multiplexer). The 'CEx' connects to a 'Splitter' in the ODN. The 'Splitter' then connects to various ONUs on the UNI side, including GPON ONU, XGPON ONU, NGPON2 ONU, and combinations with RF video (GPON + RF ONU, XGPON + RF ONU, NGPON2 + RF ONU). Interfaces are labeled as IF\_Video, IF\_OTDR, IF\_GPON, IF\_XGPON, and IF\_NGPON2. A key defines the abbreviations: CG = Channel group, CP = Channel pair, CEx = Instance of co-existence element, HE = Head end, WM = Wavelength multiplexer. The diagram is labeled G.989.1(13)\_F5-1. + +**Figure 5-1 – Functional reference architecture and points for NG-PON2 system coexistence with legacy systems** + +# 6 Migration + +PON systems such as G-PON [ITU-T G.984] series, XG-PON [ITU-T G.987] series and 1G-EPON [IEEE 802.3] have been standardized and are now being deployed worldwide. With the ever-increasing bandwidth demand from consumer and business applications, the most general requirement for an NG-PON2 system is to provide higher bandwidth than these legacy PON systems. In addition, given the major investments made to deploy these legacy PON systems (including the fibre infrastructure), NG-PON2 systems must be able to protect these investments by ensuring seamless and smooth migration capability for subscribers to NG-PON2 systems. Coexistence is enabled through the wavelength band plan which also provides the optional overlay capability of broadcast TV on a separate wavelength. + +There are several migration scenarios to meet different network needs. These scenarios reflect recognition that differing service introduction strategies might affect requirements for the NG-PON2 system specifications. This clause describes two likely migration scenarios: + +### PON brownfield migration scenario + +PON brownfield scenario in this Recommendation refers to the deployment scenario where a PON system has already been deployed and this existing fibre infrastructure is leveraged to offer higher + +bandwidth carrier services or other features, using NG-PON2 systems. Some subscribers to an existing PON system might require an upgrade to such a higher speed tier service and it might be beneficial to move these subscribers over to the NG-PON2 system, while other subscribers remain on the legacy PON. It is likely that two or three PON generations will continue to coexist for a relatively long time. + +In a slightly different migration scenario, it may be desirable to replace an existing PON with NG-PON2 completely. In this case, it would still be useful to operate both legacy PON and NG-PON2 systems at the same time on the ODN and update customers one at a time. The timeframe for this type of upgrade is generally much shorter. + +General requirements for this scenario are as follows: + +- Coexistence between legacy PON and NG-PON2 systems on the same fibre must be supported for the situation where the fibre resource is not necessarily abundant. +- Service interruption for the non-upgrade subscribers should be minimal (if at all). +- NG-PON2 systems must support/emulate all legacy PON services in the case of full migration. +- Legacy PON systems include GPON, XG-PON1, GEAPON and 10G-EPON. + +### PON greenfield migration scenario + +Upgrading the access network to FTTx infrastructure is a significant investment for service providers and takes a long time to fully realize. When NG-PON2 technology becomes mature, it may be desirable to use NG-PON2 systems to replace copper-based infrastructure or to deploy in a brand new development area for the benefit of higher bandwidth, higher splitting ratios, and other capabilities. An area where PON had not been previously deployed is referred to as "PON greenfield". This scenario may help service providers achieve better economics while supporting the same or better bandwidth offer per user as previous PON systems. In this scenario, the requirement of coexistence with legacy PONs is not necessary. + +## 6.1 Co-existence, stacking and overlay + +Several concepts have been used in the GPON and XG-PON Recommendations that may generate uncertainty in increasingly complex environments. Table 6-1 captures the meaning assumed in this document. + +**Table 6-1 – Definitions of legacy compatibility terminology** + +| | Definitions | Options | Impact on WL plan | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|----------------------------------------------| +| ODN re-use | Ability to re-use existing ODN/ODS plant as is ("legacy" optical budget to be supported) |
  • * Existing RE
  • * Existing OTL
  • * co-existence
| – | +| Stacking | Ability for a generation of independent PON systems based on the same TC to share part or all of the ODN/ODS through WDM. PMD for each stacked system only differs through wavelength allocations |
  • * WL selected devices
| Definition of a "stacking dedicated" WL plan | + +**Table 6-1 – Definitions of legacy compatibility terminology** + +| | Definitions | Options | Impact on WL plan | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| Co-existence | Ability for two PON system generations to operate simultaneously on at least one section of the fibre plant. Requires the definition of specific filter isolation values when different transmission standards are used simultaneously. |
  • * WDM domain as for legacy PONs
  • * TDM domain as for XG-PON1/ XG-PON2
  • * on ODN/ODS
  • * on RE
  • * on OTL
| Compliance to a co-existence WL plan (e.g., Amd.1 of [ITU-T G.984.5]) or a multi-rate TC layer | +| Overlay | Different services are multiplexed by WDM to PONs, e.g., RF-Video. | – | – | + +Smooth migration from one PON technology to another on the same ODN provides for an enhanced end customer experience by minimizing the disruption of the existing optical plant. Co-existence facilitates a smooth migration from legacy PON to NG-PON2 systems. Without this co-existence capability, customers may have to wait longer to move their service and all customers on an ODN may experience unacceptable service disruption if parts of the passive infrastructure must be exchanged/reconfigured. The coexistence of two PON generations could enable a flexible migration and/or on-demand deployment of new PON connections without service interruption. For maximum flexibility, NG-PON2 systems must allow co-existence with both GPON and XG-PON1 on the same ODN. + +To facilitate co-existence, an NG-PON2 system must be capable of reusing existing legacy PON optical power splitters and must also operate in usable spectrum not occupied by legacy PONs in a particular deployment. However, an NG-PON2 system could re-use the spectrum allocated to legacy PON systems if not co-existing with those PONs. NG-PON2 systems must allow co-existence over the whole, end-to-end ODN including co-existence over the feeder fibre (see Figure 6-1). The end-to-end ODN of NG-PON2 is delimited by R'/S' to S'/R' reference points as shown in Figure 5-1 which are analogous to R'/S' to S'/R' as defined in [ITU-T G.984.1] and [ITU-T G.987.1]. NG-PON2 systems support power-based splitting ODNs; however, other types of ODNs may apply in greenfield applications. Appropriate filtering must be installed in ONUs to eliminate interference between the co-existing generations of PON. Furthermore, any interference due to fibre non-linearity should also be taken into account. + +![Diagram of ODN co-existence scenario showing Legacy OLT and NG-PON2 OLT connected to a CEx, which is connected to a Splitter, which is connected to multiple Legacy ONU and NG-PON2 ONU units.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +``` + +graph LR + subgraph OLTs + LO[Legacy OLT] + NP2O[NG-PON2 OLT] + end + LO --- CEx{CEx} + NP2O --- CEx + CEx --- S((Splitter)) + S --- LOU1[Legacy ONU] + S --- NP2U1[NG-PON2 ONU] + S --- LOU2[Legacy ONU] + S --- NP2U2[NG-PON2 ONU] + S --- NP2U3[NG-PON2 ONU] + +``` + +Key: +CEx = Instance of co-existence element + +G.989.1(13)\_F6-1 + +Diagram of ODN co-existence scenario showing Legacy OLT and NG-PON2 OLT connected to a CEx, which is connected to a Splitter, which is connected to multiple Legacy ONU and NG-PON2 ONU units. + +**Figure 6-1 – ODN co-existence scenario** + +The co-existence of NG-PON2 systems with legacy RF-video overlay must be supported. RF-video overlay defined in [ITU-T J.185] or [ITU-T J.186] will continue to be used into the foreseeable future to support video delivery. Many legacy PON deployments use RF-video overlay for video + +delivery; therefore, co-existence will enable easy migration to NG-PON2 systems. This requirement should not increase system complexity when RF-video overlay is not required. + +## 6.2 Migration path options + +NG-PON2 systems must allow a technology migration on existing infrastructure without any prolonged service interruption. It must be capable of upgrading single customers on demand and it must support a migration path from GPON to NG-PON2 and a migration path from XG-PON1 to NG-PON2. + +In order to realize the migration path, there are three options which differ in the level of flexibility: + +### Straight migration + +This covers a straight migration path in line with the PON generation order from GPON over XG-PON1 to NG-PON2. This requires a finalized migration from GPON to XG-PON1 before starting with the NG-PON2 upgrade. This migration option could be realized by removing the GPON from the ODN and re-using the GPON wavelength windows to enable an NG-PON2 technology coexisting with XG-PON. + +### Flexible migration + +Flexible migration covers a direct migration path from GPON to NG-PON2. Flexible migration requires an NG-PON2 system that can also co-exist with GPON. + +### All-embracing migration + +The highest level of flexibility is realized by an NG-PON2 system that enables co-existence of GPON, XG-PON1 and NG-PON2. The all-embracing option is the most challenging due to the wide range of optical wavelength bands required. The ability of NG-PON2 systems to co-exist with GPON and XG-PON1 systems will allow greater flexibility to upgrade to XG-PON1 in the near term and enable migration to NG-PON2 in the future. It will also enable migration from GPON directly to NG-PON2. This is the most desirable option as it makes the legacy ODN future proof and offers operators a high level of flexibility. + +In any migration case including co-existence, the legacy ONU and OLT must remain unchanged and should not require any additional filters to protect them against NG-PON2 signals. In the event that extra filtering is required, this should preferably be at the OLT where access may be easier and not the ONU to avoid truck rolls. The attenuation of any additional devices, i.e., the CEx referenced in Figure 5-1, must also remain similar to that introduced by WDM1r devices in order not to compromise the legacy optical budget. Whichever migration scenario is chosen, it must be possible to migrate a customer from GPON/XG-PON1 to NG-PON2 through a replacement of the ONU. + +## 6.3 Support for legacy ODN + +The total expenditure for FTTH deployment is dominated by the infrastructure investments. Given that many networks already use power splitter based ODNs to carry Gigabit-class PON technology, it is mandatory that NG-PON2 systems be compatible with these legacy ODNs. Some ODNs use connectors extensively, with as many as nine connectors between the OLT and the ONU (eight angled physical contact (APC) connectors in the ODN and one ultra physical contact (UPC) connector at the OLT). NG-PON2 systems must be able to accommodate the resulting back reflections and connector loss impairments but does not require more stringent reflection tolerance than already defined in BPON/GPON standards; [ITU-T G.983.x], [ITU-T G.984.x]. The access infrastructure has a very long lifetime (20 years or more) and there must be an upgrade path for this deployed infrastructure throughout its life. It is advantageous for NG-PON2 systems to allow a system upgrade on existing infrastructure without any protracted service interruption. NG-PON2 systems must be able to accommodate flexibility in terms of stages and number of splits in each + +stage no matter what splitting technology is used (whether power splitting, wavelength splitting, or a combination of both). + +A non-wavelength selective ODN may be preferred in order to obtain a system independent distribution network. With this approach there are no barriers for flexible wavelength upgrades and further usage of the fibre spectrum. Filters inside the ODN define wavelength windows that limit flexibility and can increase network planning complexity. + +# 7 Service requirements + +## 7.1 Service specific requirements + +NG-PON2 systems are required to fully support various services for residential subscribers, business customers, mobile and fixed backhauling, and other applications through its high quality of service and high bit-rate capability, and must at least meet the system requirements as defined in clause 7 of [ITU-T G.987.1] (including synchronization, quality of service (QoS), etc.). Further, NG-PON2 systems may achieve better delay and jitter performance. NG-PON2 systems must support legacy services, such as POTS and T1/E1 using emulation and/or simulation, high speed private line (framed and unframed), and emerging packet-based services. The emulation option delivers packet-formatted traffic through the PON network, i.e., between the OLT and ONU, and possibly through some level of aggregation, then converts back to the relevant legacy format to hand it off to the legacy network. The simulation option is an end-to-end packet delivery starting at CPE terminal adaptation device or ONU, to the NG-PON access and the NGN packet network. An Ethernet packet size up to 9 000 bytes must be supported. Optical business services such as wavelength services and OTN must be supported. + +## 7.2 User node interfaces (UNIs) + +UNI is defined as the interface that includes the following conditions: + +- interconnection between the access network and the customer; +- described by a well-known standard; +- includes a physical layer aspect. + +Some UNIs are provided via an adaptation function, so it is not mandatory that the ONU support those interfaces. + +Example of UNIs, physical interfaces and services that they provide are shown in Table 7-1. + +**Table 7-1 – Examples of UNI and services** + +| UNI (Note 1) | Physical interface (Note 2) | Service (Note 3) | +|-----------------------------------------------------|-----------------------------|----------------------| +| 10 Mbit/s/100 Mbit/s/1 Gbit/s Ethernet [IEEE 802.3] | 10/100/1000BASE | Ethernet | +| MoCA 2.0 | – | MoCA 2.0 | +| 1 Gbit/s fibre UNI | – | Ethernet | +| 10 Gbit/s fibre UNI | 10BASE | Ethernet | +| [b-ITU-T G.8261];
[b-ITU-T G.8262] | – | Synchronous Ethernet | +| [b-ITU-T Q.552] | – | POTS | +| ISDN [b-ITU-T I.430] | – | ISDN | +| [b-ITU-T V.35] | – | – | +| [b-ITU-T G.9960] | – | – | + +**Table 7-1 – Examples of UNI and services** + +| UNI (Note 1) | Physical interface (Note 2) | Service (Note 3) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-----------------------| +| VDSL2 [b-ITU-T G.993.2],
ADSL2plus [b-ITU-T G.992.5] | xDSL | xDSL | +| [b-ITU-T G.703] | PDH | DS3, E1, E3 | +| [b-ATIS 0900102] and
[b-ATIS 0600107] | PDH | T1, DS0, DS1, DS3 | +| SDH/SONET | | OC3-OC192, STM1-STM64 | +| OTN [b-ITU-T G.872],
[b-ITU-T G.709] | | OTU1, OTU2 | +| CPRI/OBSAI (Open Base
Station Architecture Initiative) | | | +| NOTE 1 – There are many other services accommodated in XG-PON, but those services do not have specified UNIs.
NOTE 2 – Each item in the "Physical interface" column is illustrated by the corresponding entry in the "UNI" column.
NOTE 3 – The column labelled "Service" shows which services can be supported by the physical interface. | | | + +## 7.3 Service node interfaces (SNIs) + +SNI is defined as the interface that includes the following conditions: + +- interconnection between the access network and the service node; +- described by a well-known standard; +- includes a physical layer aspect. + +Example of SNIs, physical interfaces and services that they provide are shown in Table 7-2. + +**Table 7-2 – Examples of SNIs and services** + +| SNI (Note 1) | Physical interface (Note 2) | Service (Note 3) | +|--------------------------------------------|-----------------------------|------------------------------------------| +| 1 GigE [IEEE 802.3] | 1000BASE | Ethernet | +| 10 GigE [IEEE 802.3] | 10GBASE | Ethernet | +| 40 GigE [IEEE 802.3] | 40GBASE | Ethernet | +| 100 GigE [IEEE 802.3] | 100GBASE | Ethernet | +| [b-ITU-T G.8261];
[b-ITU-T G.8262] | - | SyncE | +| [b-ITU-T G.965] | V5.2 | POTS, | +| [b-ITU-T G.703] | PDH, STM-1e | DS3, E1, E3, STM-1, DS1, DS0 | +| [b-ITU-T G.957] | STM-1,4,16,64 | E1, E3, DS1, DS3, GFP, E4,
STM-n, DS0 | +| [b-ATIS 0600107] | PDH | DS0, DS1, DS3 | +| SDH/SONET | SDH/SONET | OC3-OC192 , STM1-STM64 | +| OTN [b-ITU-T G.872] and
[b-ITU-T G.709] | OTN | OTU1, OTU2, OTU3 | + +**Table 7-2 – Examples of SNIs and services** + +| SNI
(Note 1)
| Physical interface
(Note 2)
| Service
(Note 3)
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------------------| +| CPRI/OBSAI (Open Base Station Architecture Initiative) | | | +| NOTE 1 – There are many other services accommodated in XG-PON, but those services do not have specified SNIs.
NOTE 2 – Each item in the "Physical interface" column is illustrated by the corresponding entry in the "SNI" column.
NOTE 3 – The column labelled "Service" shows which services can be supported by the physical interface. | | | + +## **7.4 Access node interfaces (ANIs)** + +Flexible system configurations are required to improve equipment utilisation and lower capital and inventory costs. To this end, NG-PON2 systems must support flexible and agnostic interfaces to the optical access network to enable the OLT network element to accommodate multiple access technologies. This objective may be achieved by using pluggable interfaces. + +## **7.5 System flexibility** + +Leveraging next generation fibre infrastructure across many market segments, such as business, residential, and mobile backhaul will improve the system attractiveness. Therefore NG-PON2 systems must offer functionality suitable for residential multi-dwelling unit and single-family unit (MDU/SFU), business, and mobile backhaul customers and applications. Moreover, system flexibility must also be made possible by supporting different customer types on the same PON in a flexible way, which otherwise might need to be served separately using for example, point-to-point fibre deployment. + +# **8 Physical layer requirements** + +## **8.1 Capacity (per feeder and per user)** + +NG-PON2 systems shall be capable of offering significantly more capacity per customer than current GPON and XG-PON1 systems. NG-PON2 systems shall be able to support at least 40 Gbit/s aggregate capacity per feeder fibre in the downstream direction and at least 10 Gbit/s aggregate capacity in the upstream direction. Up to 160 Gbit/s in the downstream direction and up to 80 Gbit/s in the upstream direction is a target ceiling capacity. Typically any NG-PON2 ONU shall be able to support at most 10 Gbit/s service, whereas the actual capability per ONU on the PON will depend on engineering choices concerning split ratio adopted and the application mix considered (e.g., FTTH, FTTB, Mobile backhaul). For example, some scenarios may require a 100 Mbit/s service to be effectively provided on the same PON as a 10 Gbit/s service. NG-PON2 systems shall be able to support ONUs with 10 Gbit/s symmetrical capacity. The NG-PON2 system must offer such service mixes to enable the sharing of common infrastructure. The system must provide efficient traffic sharing among residential, business, and other customers; and should offer an upgrade to greater bandwidths without foreseeable technology roadblocks or bottlenecks. + +NG-PON2 system capacity requirements are driven by the various access services that could be delivered by such systems. The envisaged services drive the need for different sustained and peak data rates, as well as different symmetry ratios between upstream and downstream data rates. For example, business services or mobile backhaul will require sustained and symmetric 1 Gbit/s data rates or higher, whilst residential customers may be less bandwidth demanding and require the available peak bandwidths for short durations only. Overall, a move to more symmetric services is anticipated and NG-PON2 systems that increase the level of service rate symmetry, e.g., between 2:1 and 1:1 (downstream: upstream) service rates, are desirable. Furthermore, NG-PON2 systems must efficiently deliver service mixes consisting of services with both low and high levels of symmetry, which can be as high as 1:1 and as low as 100:1. NG-PON2 system will thus enable the provisioning of services that are tailored to meet different customers' needs over a common infrastructure. + +Example services demanding higher data rates include serving MDUs, enterprise connectivity, distributed eNodeB, and mobile backhaul. With respect to mobile backhaul, increased capacity is required to meet expected LTE data rates in the region of up to 300 Mbit/s and increasing to 1 Gbit/s for LTE-Advanced. In addition, it may be cost effective and increase mobile capacity of the wireless infrastructure to introduce a distributed eNodeB architecture. In supporting distributed eNodeB applications, it may be beneficial to leverage NG-PON2 systems to support the high speed transport (e.g., CPRI with up to 9.83 Gbit/s) between BBU (Baseband Unit) and RRUs (Remote Radio Unit). + +It is impossible to precisely predict what service evolution will occur over the next decade given the number of unknown factors and the many global markets and deployment models. Therefore, NG-PON2 systems must be scalable enough to support any reasonably expected outcome. + +## **8.2 Fibre reach (passive and active)** + +NG-PON2 systems must support a fibre reach of at least 40 km without mid-span reach extenders. NG-PON2 systems also need to support the maximum differential fibre distance of up to 40 km, with configurable maximum differential fibre distances as 20 km and 40 km. NG-PON2 systems must also be backward compatible with already deployed infrastructure (CO locations, ducts, fibre cables, etc.) + +NG-PON2 systems must also be capable of reaching 60 km with reach extenders if needed. Even longer reach (e.g., 60-100 km) NG-PON2 systems could facilitate CO consolidation and other network architectures and capabilities. + +## **8.3 Split ratio (ONUs per ODN)** + +Optical distribution networks exploiting power splitters are typically deployed today with a split ratio in the range of 1:16 to 1:128. NG-PON2 systems may run over legacy power split ODNs, wavelength routing, or combinations of wavelength routing and power splitting. NG-PON2 systems should be flexible enough to support cost-effective deployments over a variety of ODNs. NG-PON2 OLTs must support a split ratio of at least 1:256. Specific application and network engineering choices may require higher split ratios; therefore, the NG-PON2 OLT core design should not preclude supporting higher split ratios. + +Support for a higher number of ONUs per ODN enables a high degree of infrastructure sharing and node consolidation if used in conjunction with longer reach. However, it is recognized that it may be necessary to trade-off the sharing gain against increasing system complexity and power budget limitations. In some deployment scenarios the physical split ratio may be increased by using reach extension for enhanced loss budget. + +## 8.4 Optical spectrum issues and availability + +Access networks largely employ ITU-T G.652 single mode fibres (SMFs). As is well known, the characteristics of SMF are wavelength dependent. Figure 8-1 shows the attenuation of SMF over wavelength range of interest along with the defined ITU-T bands. The attenuation of an optical signal is lowest in the C-Band and lower L-Band. + +![Figure 8-1: Single mode fibre attenuation and chromatic dispersion. The graph plots Attenuation (dB/km) on the left Y-axis (0 to 1) and Chromatic dispersion (ps/nm/km) on the right Y-axis (-15 to 25) against Wavelength (nm) from 1250 to 1650. Three curves are shown: old fibre (pre 1990) in orange, new fibre (~ 2000) in purple, and new fibre (post 2003) in cyan. The attenuation curves show a peak around 1380 nm for the old fibre. The chromatic dispersion curve (purple) shows a zero-crossing at approximately 1310 nm. The graph is divided into O-band, E-band, S-band, C-band, L-band, and U-band regions.](7bed2d7c96d86bf922295a1252da52a5_img.jpg) + +Figure 8-1: Single mode fibre attenuation and chromatic dispersion. The graph plots Attenuation (dB/km) on the left Y-axis (0 to 1) and Chromatic dispersion (ps/nm/km) on the right Y-axis (-15 to 25) against Wavelength (nm) from 1250 to 1650. Three curves are shown: old fibre (pre 1990) in orange, new fibre (~ 2000) in purple, and new fibre (post 2003) in cyan. The attenuation curves show a peak around 1380 nm for the old fibre. The chromatic dispersion curve (purple) shows a zero-crossing at approximately 1310 nm. The graph is divided into O-band, E-band, S-band, C-band, L-band, and U-band regions. + +Figure 8-1 – Single mode fibre attenuation and chromatic dispersion + +Chromatic dispersion (CD), which can limit system reach as signal line rates increase, is also wavelength dependent with a zero value at $\sim 1310$ nm for SMF. The wavelength variation of CD is also shown in Figure 8-1. + +One further aspect concerning the wavelength options concerns the availability of opto-electronic components. For example, commonly available Erbium doped fibre amplifiers (EDFAs) work in the C and L bands, whereas, semiconductor optical amplifiers (SOAs) can be made to work in any of the bands of interest. However, semiconductor optoelectronic components vary in terms of performance depending on the operating wavelength e.g., laser temperature performance or photodiode responsivity. + +Wavelength plans (Figure 8-2) of the legacy PON systems that NG-PON2 systems may need to co-exist with must be considered relative to migration and co-existence requirements. + +![Figure 8-2: Wavelength plans of legacy PON systems. The diagram shows a wavelength spectrum from 1260 nm to 1640 nm, divided into O-Band, E-Band, S-Band, C-Band, L-Band, and U-Band. Various legacy PON systems are mapped to specific wavelength ranges: 10GE/XG-PON U/S (1260-1280 nm), GPON U/S (Narrow/Reduced) (1280-1300 nm), B/GPON GE-PON U/S (1300-1340 nm), B/GPON GE-PON D/S (1480-1500 nm), RF-Video (1540-1560 nm), and 10GE/XG-PON D/S (1560-1580 nm).](8a597e344d10e36bbb2f243f6c4e74c6_img.jpg) + +Figure 8-2: Wavelength plans of legacy PON systems. The diagram shows a wavelength spectrum from 1260 nm to 1640 nm, divided into O-Band, E-Band, S-Band, C-Band, L-Band, and U-Band. Various legacy PON systems are mapped to specific wavelength ranges: 10GE/XG-PON U/S (1260-1280 nm), GPON U/S (Narrow/Reduced) (1280-1300 nm), B/GPON GE-PON U/S (1300-1340 nm), B/GPON GE-PON D/S (1480-1500 nm), RF-Video (1540-1560 nm), and 10GE/XG-PON D/S (1560-1580 nm). + +Figure 8-2 – Wavelength plans of legacy PON systems + +A further factor that limits the available spectrum are the legacy filter characteristics built into deployed systems. Most significant may be the RF-video filter which may require guardbands that occupy most of the C-band where the fibre loss is low and EDFAs could be used. + +# **9 System requirements** + +## **9.1 Colourless ONUs** + +In order to facilitate flexibility and reduce operational expenditures due to inventory management, deployed ONUs must be 'colourless', i.e., they are not specific to a certain wavelength. Colourless ONUs do not require the management of multiple ONU types that scale in number with the number of wavelengths used on the PON. This significantly reduces the provisioning time and cost compared to ONUs which are coloured. + +## **9.2 Spectral flexibility** + +An efficient approach to support various deployment scenarios and network applications is to utilize a degree of spectral flexibility in the NG-PON2 system. Such flexibility can enable the support of different customer types and PON systems on the same ODN in a flexible way. There are diverse access applications that drive the need for a range of sustained and peak rates, different delay/jitter requirements, as well as different downstream/upstream ratios, all parameters which combined lead to various launched power and sensitivity. Furthermore, the NG-PON2 system should allow the use of spectral flexibility to enable capacity upgrades in a progressive or modular way as demand grows. Flexible channel counts for both TWDM and PtP WDM (e.g., 4, 8, and 16) should be supported to facilitate capacity increase. Additionally, spectral flexibility must facilitate a range of co-existence scenarios that avoid interference with legacy systems and subsequently enable new wavelength bands when these legacy systems are decommissioned. + +To meet the above requirements, the NG-PON2 system must offer the possibility to access multiple wavelengths, groups of wavelengths, or wavelength bands that can be physically and logically separated and driven independently, either by a single OLT or by multiple independent OLTs, with fully independent operation. This requirement should not increase complexity in system not requiring such flexibility options. + +## **9.3 Rogue ONU/OLT detection and mitigation** + +NG-PON2 systems should be able to monitor transmissions at the OLT and ONU to guard against ONUs or OLTs that exhibit rogue behaviour (e.g., an ONU transmitting in another ONU's timeslot/wavelength or an OLT transmitting in another OLT's wavelength band). The rogue ONU prevention, detection, isolation and mitigation guidelines defined in [b-ITU-T G-Sup.49], should be followed. Further considerations may be required for the OLT. + +## **9.4 Resilience and redundancy requirements** + +PON resilience will become more important in supporting business applications and high value consumer applications, such as IPTV, especially in the node consolidation scenario. Node consolidation/bypass creates a high number of subscriber lines on the highly centralized access node. A redundancy mechanism is required to avoid service disruption to potentially thousands of users in the event of fibre cable or equipment failure. Besides the usual hardware redundancy requirements at the OLT and in the backhaul transmission equipment (towards the metro/core), networks require feeder and/or OTL line redundancy options to avoid large scale customer outages as well as full redundancy for business services requiring end-to-end type C protection. NG-PON2 systems must support the resilience options defined in clause 14 of [ITU-T G.984.1] including duplex and dual parenting duplex system configuration as well as the extensions described in + +Appendices II and III of [ITU-T G.984.1]. For PON redundancy, use cases and guidelines are defined in [b-ITU-T G-Sup.51]. + +Figure 9-1 shows an example of fibre path diversity ensuring resilience against cuts in the most vulnerable part of the access network. The redundant feeder fibre could terminate at a diverse CO location, or at the same CO location as the primary OLT. + +![Diagram of NG-PON2 resilience scenario showing Primary OLT, Secondary OLT (Optional), Splitter, and NG-PON2 ONU connected to various premises.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +The diagram illustrates an NG-PON2 resilience scenario. On the left, there are two OLTs: 'Primary OLT' and 'Secondary OLT (Optional)'. Both are labeled 'NG-PON2 OLT'. Fibres from both OLTs connect to a central 'Splitter'. From the splitter, a single fibre connects to an 'NG-PON2 ONU'. This ONU is then connected to three different types of premises, represented by icons: a house, a radio tower, and a large building. The text 'G.989.1(13)\_F9-1' is located at the bottom right of the diagram. + +Diagram of NG-PON2 resilience scenario showing Primary OLT, Secondary OLT (Optional), Splitter, and NG-PON2 ONU connected to various premises. + +**Figure 9-1 – NG-PON2 resilience scenario** + +Redundant splitters, especially in the highest level of hierarchy, may also be deployed and should be supported. Typically, redundancy requirements become less stringent for the customer premises, unless the end customer is, for example, a large scale enterprise or premium user. In the redundant architecture, rapid restoration may be required. For instance, service interruption time must be less than 50 ms for enterprise or premium users. + +## 9.5 Reach extender requirements + +NG-PON2 systems must also be capable of reaching 60 km with reach extenders if needed. Preferably this could be achieved whilst maintaining passive outside plant, however, it is recognized that this may be technically challenging so options for mid-span reach extenders may be needed. + +Use of a reach extender should not necessitate that the OLT or the ONU be different or modified. Thus NG-PON2 systems must provide PMD and TC layers capable of working transparently with and without a reach extender. Mid-span reach extenders must be remotely manageable through an OLT to enable configuration and monitoring functions for maintenance and fault location. Additionally reach extender based scenarios must also be compatible with co-existence scenarios, resilience and redundancy options. + +Furthermore, being remotely located in the outside network, the reach extender should have minimal power requirements and must be able to operate over outdoor temperature ranges. The following are informative examples of environmental requirements: + +- ATIS-0600010.01.2008: (Class 4 Unprotected Environment) $-40^{\circ}\text{C}$ to either $+46^{\circ}\text{C}$ ambient plus solar loading, or $+70^{\circ}\text{C}$ ambient +- Telcordia GR-487 $-40^{\circ}\text{C}$ to either $+46^{\circ}\text{C}$ ambient plus solar loading, or $+70^{\circ}\text{C}$ ambient +- ETSI ETS 300 019-1-4: (Class 4.1E: Non-weather protected locations – extended) $-45^{\circ}\text{C}$ to $+45^{\circ}\text{C}$ ambient plus solar loading + +## 9.6 Power reduction + +Power saving in telecommunication network systems has become an increasingly important concern in the interest of reducing operational costs and reducing the network contribution to greenhouse gas emission. NG-PON2 systems must be designed in the most energy-efficient way. This applies to the OLT side and even more to the ONU side since the energy consumption is not shared at the ONU except for FTTC/B. In some instances, the primary objective of the power saving function in access networks is to maintain the lifeline service(s), such as a voice service, as long as possible through the use of a backup battery when electricity service goes out. A lifeline interface must be + +sustainable for at least eight hours after mains power outage, and options such as allowing four hours of talk time while an ONU is in sleep mode for an extended period (e.g., one week) should be offered. Therefore, the NG-PON2 system shall support improving energy efficiency whilst maintaining compatibility with the service requirements. Mechanisms derived from [b-ITU-T G-Sup.45] and specified in [ITU-T G.987] series may be appropriate or new mechanisms may be required depending on the chosen technology. NG-PON2 systems must aim to reduce power consumption during normal operation without sacrificing service quality and user experience. + +## 9.7 OAM functions + +High levels of security are required from NG-PON2 systems and these systems must be at least as secure as XG-PON1. In multiple service applications, enhanced security may be required to distinguish data between services in the OLT and ONUs must be subject to more secure authentication. The NG-PON2 ONUs must be remotely manageable and support auto-configuration functions. The NG-PON2 system must provide full FCAPS (Fault, Configuration, Accounting, Performance, and Security) management capability for the ONU. + +The TWDM channels in the NG-PON2 system must support DBA for efficient sharing of bandwidth. This is not required for the PtP WDM channels. + +NG-PON2 systems must support PON supervision features that enable enhanced customer experience through early identification and location of faults (including splitter) at the physical, PON and service layers. This could include as examples ODN monitoring/checking and end-to-end performance monitoring up to the Ethernet layer. Optical layer monitoring must not impact PON operation nor limit co-existence with legacy PON systems and their associated monitoring systems e.g., OTDR. + +## 9.8 Provisioning and management + +Given the significant effort already expended in defining a converged management framework across optical access systems, ONU management in NG-PON2 systems must be based on OMCI [ITU-T G.988] suitably augmented with NG-PON2 specific MEs. + +## 9.9 Environmental and physical requirements + +Outdoor operation may be needed in many of the envisaged applications for NG-PON2 systems; thus ONUs shall operate over outdoor temperature ranges. The following are informative examples of environmental requirements: + +- ATIS-0600010.01.2008: (Class 4 Unprotected Environment) –40°C to either +46°C ambient plus solar loading, or +70°C ambient +- Telcordia GR-487 –40°C to either +46°C ambient plus solar loading, or +70°C ambient +- ETSI ETS 300 019-1-4: (Class 4.1E: Non-weather protected locations – extended) –45°C to +45°C ambient plus solar loading + +Optionally, the OLT should also be able to operate over the extended outside temperature range. + +## 9.10 Eye safety + +With the capacity increases and demands on enhanced loss budgets it is expected that an NG-PON2 system could launch significantly higher total power into the feeder fibres when compared to previous PON generations. All necessary mechanisms must be provided to ensure that no eye damage can be caused to end users unaware of the risks associated with a fibre termination inside the home or customer premises, including labelling and safety locking mechanisms if necessary. The system must meet all applicable requirements for the classification, service group designation, and accessibility to ensure the safe operation and servicing of the optical fibre communication system at each node. Since the NG-PON2 system could co-exist with other PON generations + +and RF video, the total optical power resulting from all the different wavelengths on the fibre must be within the safe operation range specified at each location, for example Class 1M at restricted access areas (OLT and RE) and Class 1 at unrestricted access areas such as the home (ONU) shown in [IEC 60825-2]. + +## **9.11 Interoperability** + +The NG-PON2 standard must support interoperability between the OLT and ONU. All relevant interfaces to facilitate interoperability shall be defined in the appropriate ITU-T Recommendations. + +# Bibliography + +- [b-ITU-T G.703] Recommendation ITU-T G.703 (2001), *Physical/electrical characteristics of hierarchical digital interfaces*. +- [b-ITU-T G.709] Recommendation ITU-T G.709/Y.1331 (2012), *Interfaces for the optical transport network*. +- [b-ITU-T G.872] Recommendation ITU-T G.872 (2012), *Architecture of optical transport networks*. +- [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.965] Recommendation ITU-T G.965 (2001), *V-interfaces at the digital local exchange (LE) – V5.2 interface (based on 2048 kbit/s) for the support of access network (AN)*. +- [b-ITU-T G.992.5] Recommendation ITU-T G.992.5 (2009), *Asymmetric digital subscriber line 2 transceivers (ADSL2) – Extended bandwidth ADSL2 (ADSL2plus)*. +- [b-ITU-T G.993.2] Recommendation ITU-T G.993.2 (2011), *Very high speed digital subscriber line transceivers 2 (VDSL2)*. +- [b-ITU-T G.8261] Recommendation ITU-T G.8261/Y.1361 (2008), *Timing and synchronization aspects in packet networks*. +- [b-ITU-T G.8262] Recommendation ITU-T G.8262/Y.1362 (2010), *Timing characteristics of a synchronous Ethernet equipment slave clock*. +- [b-ITU-T G.9960] Recommendation ITU-T G.9960 (2011), *Unified high-speed wireline-based home networking transceivers – System architecture and physical layer specification*. +- [b-ITU-T G-Sup.39] ITU-T G-series Recommendations – Supplement 39 (2008), *Optical system design and engineering considerations*. +- [b-ITU-T G-Sup.49] ITU-T G-series Recommendations – Supplement 49 (2011), *Rogue optical network unit (ONU) considerations*. +- [b-ITU-T G-Sup.51] ITU-T G-series Recommendations – Supplement 51 (2012), *Passive optical network protection considerations*. +- [b-ITU-T I.430] Recommendation ITU-T I.430 (1995), *Basic user-network interface – Layer 1 specification*. +- [b-ITU-T Q.552] Recommendation ITU-T Q.552 (2001), *Transmission characteristics at 2-wire analogue interfaces of digital exchange*. +- [b-ITU-T V.35] Recommendation ITU-T V.35 (1984) (obsolete), *Data transmission at 48 kbit/s using 60-108 kHz group band circuits*. +- [b ATIS 0600107] ATIS-0600107.2002(R2011), *Digital Hierarchy – Formats Specifications*. +- [b-ATIS 0900102] ATIS-0900102.1993(R2010), *Digital Hierarchy – Electrical Interfaces*. + + + +# 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.989.2-201902-I_PDF-E/0815887c5918cf1ba7b3a1cdab3d154f_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/0815887c5918cf1ba7b3a1cdab3d154f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf3f4d052d5209eba43e7fdf77226a3c26cb9a13 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/0815887c5918cf1ba7b3a1cdab3d154f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47a2b4b2e1ad9a8aef1acef1227a5843631c37e8edb0a7909e1a23bf9e8b26ad +size 16937 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/0bbbad069459da54c1cdef84c90b316a_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/0bbbad069459da54c1cdef84c90b316a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be828e292a7579768d938e3ffd69b9eb22369d87 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/0bbbad069459da54c1cdef84c90b316a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fff12c10ef24c1f41053b6682ebf4b4f07849367535f1c682c3d64a0e85ba88e +size 24417 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/0bd23f00e0632855cfef9274f1ab93d8_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/0bd23f00e0632855cfef9274f1ab93d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..757793d5a8a6174db50a9936f7f2ab36276239df --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/0bd23f00e0632855cfef9274f1ab93d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70206461b54f3bb0b52f0b29c57ae7de31d7c41a7fdf01f3d3e9c208f68ee32a +size 47032 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/0ff74f5b84bfe2303c9204d4feb60d5f_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/0ff74f5b84bfe2303c9204d4feb60d5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9152a5c92418dd51fae121216c3b517934a1826 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/0ff74f5b84bfe2303c9204d4feb60d5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d61f5a048b99b8947e3de73d62cbc935565a30ee90f785cf6827d664f2e45b6 +size 33229 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0240ce51574cbe80e0b9e71dfabe935c26f1de2c --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ece5e451cdf23950bbdd8b832a382ec6202f8efde13b3da5d47f3d2d3ec6c84d +size 22823 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/183007754364096b2d89f42200cf870f_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/183007754364096b2d89f42200cf870f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eab50b10c67666c8a0571d36d846e71fade718b8 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/183007754364096b2d89f42200cf870f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a011d0ef27ecef1e8de6b1ce4d32ada05f07429f1a70eaec93d30b9d1aa8c629 +size 47832 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/1ef2b5e267d1196dd7375ea783d5ff59_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/1ef2b5e267d1196dd7375ea783d5ff59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41dd68e2f9f33217716814d36158695c826c0a62 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/1ef2b5e267d1196dd7375ea783d5ff59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8097d9a6a5c8161b120ac3bea3d38b9a528725e31d52da571eac1b3ea13c1b87 +size 42693 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/1f00478b5b295fba8ced45856b00de5e_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/1f00478b5b295fba8ced45856b00de5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a7bd67214b263188ec97d57e9f65c4af6ef86f1 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/1f00478b5b295fba8ced45856b00de5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a854992159bc49597edd4c28aa9df85dbb08470f7d08564e412d1872faa2da87 +size 72197 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/235e996e83e7d5198cf9d909f5713cdd_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/235e996e83e7d5198cf9d909f5713cdd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8582a1077840ca1dbae95cc2fc95fc713853d88 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/235e996e83e7d5198cf9d909f5713cdd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0164604af5fa77636b92871206adfa33952d809079505776858c0363459433db +size 29651 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/26d0c0482ad7f4f026a58ecc0b468980_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/26d0c0482ad7f4f026a58ecc0b468980_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7743aa71af5f053e9e6c04383bc31d1766d42a25 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/26d0c0482ad7f4f026a58ecc0b468980_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86f5d5da62c2fdf7f1e70c25d2931d08c1f67fb43b63cb548d3263655b0b1f89 +size 54839 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/33d66c42e2c44378aaab641502989484_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/33d66c42e2c44378aaab641502989484_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..808808864b92eef4e653c0306245d606a8255734 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/33d66c42e2c44378aaab641502989484_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f15352985b2269f8391c482842a5353b0702aafc68358c5bccda9727a47dd72e +size 33759 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/34b047489058d6400b412cd0ae2334ba_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/34b047489058d6400b412cd0ae2334ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c736a53d4de5e6303cf73dfa456148cc07d43de1 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/34b047489058d6400b412cd0ae2334ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b68ed5b6e214c7870f945081111ac5f86ba05c46f3d966497884702998c11786 +size 56728 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/37b60927a495651a09fddd8861e70a20_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/37b60927a495651a09fddd8861e70a20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8173cefd7d7fe3b98ffe1f6a68e5c093a455765 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/37b60927a495651a09fddd8861e70a20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfcd50d1750f4c431ee6a3bb8de3a7ab9091e036034d633cc3e90b1d812f1456 +size 44918 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1b5fc6a86361291d5de6b7aa3ae831a9a3d88d7 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd0cf9fb09774d6a7809c68ff46af13551546b5124adfefed0d1b41d199772aa +size 16548 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/4c86e4dfdc04db280a2a1ab345358130_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/4c86e4dfdc04db280a2a1ab345358130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f271abd2a9bc6c8e353d4a567b9cb1b8af99074 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/4c86e4dfdc04db280a2a1ab345358130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:195336ef92360afb5d7e72bce14314c3ab2d70cbb6e809bd1c0d9dc698e7ad5e +size 38927 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/558e8decddf44d5f246b09396086ce02_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/558e8decddf44d5f246b09396086ce02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e58ebfd3d80977ccb15ee1c9460a8725390e11d9 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/558e8decddf44d5f246b09396086ce02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eff81e113153b0deeb3ed3f0d2f0f8fa984008619808c0cdcdb03ff5e316b224 +size 56587 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/596fee0cab582cfa9ee3d008ff657854_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/596fee0cab582cfa9ee3d008ff657854_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a2b9b2791f5411bcef33e99bad6950eb79c570d --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/596fee0cab582cfa9ee3d008ff657854_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:659f99147e3aea3433140cb086cc4570bb1a5298acb356dd3a85ea2ce6fb6c0b +size 67848 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..834f24a8970db3ddd099f4ba10bea11a045c5d47 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d73516f45470bd9c4b8adb1b6713fa82d7ad35fcb85dd86f87030df8da475cc6 +size 36694 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/709203a3712ad0608d7f64dd69fa7db0_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/709203a3712ad0608d7f64dd69fa7db0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc7046d623e65e01dc234e2ee7dfa2f0def7ec70 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/709203a3712ad0608d7f64dd69fa7db0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e347c3fc68d45bd78513eced4a8a63c2d5aa605b09540efc327166836513378 +size 53694 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/771c18f874d31c59c3b8c4e247be16ca_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/771c18f874d31c59c3b8c4e247be16ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8d2c1432bad2b809f85a17c2a4183789e767a1d --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/771c18f874d31c59c3b8c4e247be16ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db1d197be6b51b2ce32588833bf17f0576bd3e64a751b2a0ee81a0a98d39d617 +size 15141 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/796573504cfca9cbe974cf7a125c0494_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/796573504cfca9cbe974cf7a125c0494_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9908a1b6040b7e07b07c07b5707ab422cb90aef2 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/796573504cfca9cbe974cf7a125c0494_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81ec2bcd48c534534d54c3cc06de7d38cd8473957f8d056488636eb8a0c3ac73 +size 50515 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/7b7596fb5ef925025341a9aacb6f2be7_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/7b7596fb5ef925025341a9aacb6f2be7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89424c168a5ac0fa0360f992c6df61e0c812182b --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/7b7596fb5ef925025341a9aacb6f2be7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4be7aee7e1dc51093830e2cababcab04435d38546e6a3cd39f59a3f117359c5d +size 74948 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/7f228001c8c028ac077fb5def89326e8_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/7f228001c8c028ac077fb5def89326e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61abb435074629052eec1e8e5e79f6858dc38ec3 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/7f228001c8c028ac077fb5def89326e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ac4184f16ba790aa06ec57d6c4fcc763231d7b46daed1f939c163cef12c1ab0 +size 28207 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/801306729c5725ff06ca853a9139cd0b_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/801306729c5725ff06ca853a9139cd0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d40866edeb21604ea9d24cf1e5a098ee649749b --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/801306729c5725ff06ca853a9139cd0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1b3b4819fd3def71117d29c98cd0ef6d4658f059b4c0a856a5b60943f890fa0 +size 16086 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/851d99765a6fe09d94a024c53bd9fe40_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/851d99765a6fe09d94a024c53bd9fe40_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7825ece61be122c323c11f3060b865db591d9206 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/851d99765a6fe09d94a024c53bd9fe40_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9690d3107c83238425351c9bcc097e7000f42fc9b4e9bc3f93228d34b850307 +size 66009 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/86c32700ca76b0bc4154f5d9e07aab0e_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/86c32700ca76b0bc4154f5d9e07aab0e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b44538eb882f9a9614dcbabb24d8cdd6b34a750e --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/86c32700ca76b0bc4154f5d9e07aab0e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04e4bd2d361918052688902f0418224ccb4e0617ad44a2c2b69aa4192965016a +size 111528 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/886963464425186f4a465fa8155d2a3c_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/886963464425186f4a465fa8155d2a3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d05def96023856bf28f8532a828f23b5fafc08eb --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/886963464425186f4a465fa8155d2a3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf785c6e9f769fa7a71dac8c059d6616aa3d2d0d9009500697d5d8b2c71137a3 +size 57486 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/8a781a0a8c956859f63a1ca7f2bb1644_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/8a781a0a8c956859f63a1ca7f2bb1644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c0b3a78f1c5405699113e4d91cf8fbb256a7a3c --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/8a781a0a8c956859f63a1ca7f2bb1644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cff234c9479dcd41983b8c33e4157e43675e8ded9e0493931c4db2044731fabd +size 38439 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/8d91c13d9c584af8129133d91ecb4bb9_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/8d91c13d9c584af8129133d91ecb4bb9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..898a09153326221ad553a2877f4a22700b311b2c --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/8d91c13d9c584af8129133d91ecb4bb9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0784f6a4f5a9b61abcb8ec06e2aa35c51cf1d930703a78f1b410154c27c8d1a +size 41967 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/8f38356601e137ac471fc4771b9c5a5c_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/8f38356601e137ac471fc4771b9c5a5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be0b56506875cee984809c21973b224d4f58a396 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/8f38356601e137ac471fc4771b9c5a5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd240aea952df59434609dc63ca5eadc19bb1f2989a372d7f2e8e802fd1b779c +size 46774 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/9ab8ed615ae503cf1b4da66bff9c18a9_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/9ab8ed615ae503cf1b4da66bff9c18a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaba449be5a138dbd9c8f4f76c53a5c0ee094a10 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/9ab8ed615ae503cf1b4da66bff9c18a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8ecfe60e3a764f4013c1139ef783775b90a80598687803c4306a1c6cd32cbe2 +size 51215 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/9b91dbfe5949fa9a6216c2599aa95290_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/9b91dbfe5949fa9a6216c2599aa95290_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92577d6a50891a43d43b7a4c78099e7d4c18e531 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/9b91dbfe5949fa9a6216c2599aa95290_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:947dfc87c91e51b3f8d73e1b0c70f108a6569eb540d82a7d877e63f32401832e +size 40910 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/9c80cf99954eb0142f694456d39fae4b_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/9c80cf99954eb0142f694456d39fae4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c31f928bd617fde11d19857f79f666b931fc2be --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/9c80cf99954eb0142f694456d39fae4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bac954145ad6f960c1f71e44757e6242c55199dda29f5e8ca37059ad7712e6d0 +size 42592 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a11cb11416cec938d92cb28d86c57cd2cef82bb9 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acb86b2e64b6964168d48594939cf8631f4c474671c93df95be05513923a5b84 +size 16259 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adbf9f5c034cbc42db074760010bbabfa1d9e5ea --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dee2df745b38e08f0313607425463f5f9a89f554e84df2c8ecbfdba6d252fe68 +size 67983 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61904c12b802df120c05ae72cd89a3ef2690dd5b --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3f7510ab78ce9e9cb2d4e8558b0de5ac645aba1e095a2b999841612076a60c4 +size 4136 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/a3ee9a6f9fa9251ee0cac2d16e67e620_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/a3ee9a6f9fa9251ee0cac2d16e67e620_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b940e0688602ee818f3d3d215191689f04cd90a4 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/a3ee9a6f9fa9251ee0cac2d16e67e620_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5870bb9bd1b15d0ca1eb78ad30dc1429f5d42cbef0a95f836dd588337ff8b392 +size 53315 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/a4cb63f5debf833e6069e99143a2b624_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/a4cb63f5debf833e6069e99143a2b624_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3536c9e89722b9f36e1cd8fdf26e9f074e102783 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/a4cb63f5debf833e6069e99143a2b624_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c79ed1c78da2e13b6465cbff099ef7f81a4ce4b98ad78099b5177890eb8c80c5 +size 15786 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/ad555483986d7170a46ce72d164b5bc8_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/ad555483986d7170a46ce72d164b5bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..602e795599d76075a737c33063373557e8fdc939 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/ad555483986d7170a46ce72d164b5bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:036a18e62de1f4c0dba0901c2d5485ceec0058ddd1fa15b1f01dfc12039ac8ed +size 49271 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/b8dc609f35d8251ff4e4ea111a9943bd_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/b8dc609f35d8251ff4e4ea111a9943bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2747563b7a2c95d5f99d3e1eb3f2ca85a3448db --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/b8dc609f35d8251ff4e4ea111a9943bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22d573b5611a8baef1d1b72390d7cb3726b84eb65a3d0c3f670738f68ce57d3b +size 42063 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45133396036ee88a112cdd1eb438b16046229cce --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96ee1bbdb03961bcbc246ab7c15213a401ea417f73c6fcae82aa674fd9914d17 +size 14915 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5deab26460465fcb0b3fd90160ea4ffa8c7d41cd --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:392675a379a64adbf752464489687bc758b3a3eaba7061ecef6d9c751c798cc4 +size 40213 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/d7ce27646f87a7bec81474bed33145ef_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/d7ce27646f87a7bec81474bed33145ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b077b28968a8fba6e5014b39f98aedd0a5120c2b --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/d7ce27646f87a7bec81474bed33145ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba13153a0041c3ffb5d429709f65f0d4135c41c6b20261a55622fa3c2986c7f1 +size 15523 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/dd00cc2325415c09afb8bf178f60f33b_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/dd00cc2325415c09afb8bf178f60f33b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04e737763a0ebb79ac8e04d7ce4150d08e781e1c --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/dd00cc2325415c09afb8bf178f60f33b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff5737ad16a51cbc18246fc4c1f95e8ffda23f7d8bfd6b95ee7960224c8cea9a +size 69775 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/dfb7b1135e92a91d2c81546f16a50947_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/dfb7b1135e92a91d2c81546f16a50947_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2406c26e396e56262da4c37b6577b513978b35f --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/dfb7b1135e92a91d2c81546f16a50947_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:793491999699d22f21d15edf4c5ae3e1005a7479a031f42bfbc9c6e08fb24634 +size 15891 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/e76a2834f1b3fc9987bab47ed9607caa_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/e76a2834f1b3fc9987bab47ed9607caa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aae90f4b3a2ebbd4ad58bbc42fbf0e6874537677 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/e76a2834f1b3fc9987bab47ed9607caa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9907ac5893181858401403430c3ccdee6a5ae665b7c1965600da8f584737bd3 +size 93167 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/e91633da5160c8af51a4ace6d3347f53_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/e91633da5160c8af51a4ace6d3347f53_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bc0509db5bb559c5e33fa07b7285543e23685bd --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/e91633da5160c8af51a4ace6d3347f53_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:803428d58ad927d547fe9ce70afb88817363d8091bae79a83fb8aea059792015 +size 15308 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/efedc464aaba06e85f269d26c98fee90_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/efedc464aaba06e85f269d26c98fee90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3882a5c8c922c122d21bfb974348461bd206741f --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/efedc464aaba06e85f269d26c98fee90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56c2011cd57e9208378e3b3741412de9808d42ec2b8f7a8679bfbd5161b2601e +size 27041 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/f24d06b5e3b1d8ae12d4893e7619f6f5_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/f24d06b5e3b1d8ae12d4893e7619f6f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e03dd77afe051218c05ab5e31d51a8d3eb604b75 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/f24d06b5e3b1d8ae12d4893e7619f6f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ba3c2f2fbf340fae8417b2dd3ace5d5e0942e8ed64f951ce9cb5a946ecb9c44 +size 33482 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/f899c67120dc04a5e5a5c2d94461a077_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/f899c67120dc04a5e5a5c2d94461a077_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5a4ed5e0daad901361082cf9962d4449ab1b5a6 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/f899c67120dc04a5e5a5c2d94461a077_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f974e1ec013a67bf12dce5b4ced40b20ff977468d30b0960f1d89db092b22be +size 14692 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3eb1b54f2646d4202ac300c3d2d253109a977357 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fdbcd58fec4a036b178e727ec0bd96fbbaae7c8c91e4a64680fae93594d1f7c +size 16184 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/fe2b982e7b73e8c8d5ba45509c306882_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/fe2b982e7b73e8c8d5ba45509c306882_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e4cac0822514ddf01b557d6b813717d8efe41a5 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/fe2b982e7b73e8c8d5ba45509c306882_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0d8ba7dfebb95a7adde5f8069f5500fcdd85f7d797323f4ac182b9b50a5eb2f +size 44382 diff --git a/marked/G/T-REC-G.989.2-201902-I_PDF-E/fe655d77258397f7242c2df72b965b56_img.jpg b/marked/G/T-REC-G.989.2-201902-I_PDF-E/fe655d77258397f7242c2df72b965b56_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cd5186e72a8d5917ae7b0dd5fe93add7a94f6f9 --- /dev/null +++ b/marked/G/T-REC-G.989.2-201902-I_PDF-E/fe655d77258397f7242c2df72b965b56_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f2570411e54bb9eef2bde03e276dd243a22bcce9eb20fd890188280454e3c42 +size 32218 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/08f5fade508b5badd6175fa5e482132f_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/08f5fade508b5badd6175fa5e482132f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e2b2abd5b063d8d9f8cff8e49cf86d90d30ca3b --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/08f5fade508b5badd6175fa5e482132f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7cce3f9eadedb475f20bc9d1c6df34867c2783c32c934c69df83dcc7b15b7ea8 +size 92180 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3f51724d3e0138c7cb7385fe154aaa8db760825 --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:065480f7014d9f1284b67d51b217b41934238f4bd77da0ec88cb51ee6fe08557 +size 4078 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e9058bda21d81e1fe0898a6b2e6906019058eea --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2243ad142e266ef8f77bb5b6853b37aa896c5c94ae98fc08072729411d554e6 +size 57081 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08f425dc2a009265a17b8d0270a70643c5dbffa0 --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5ea36d2f616f9d974e07b22ce1aa7b1686bcf5b8765fc24a3f40955c264cda7 +size 56741 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41dae6f435a7ee0bad8c639efea72f17346a2546 --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a3a37f3bc9dc56e456b79f35c06cce12003090899a7fa4ce44b61722a339192 +size 43791 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e89002370b3c851ea288dab7e6e54ba182945ee --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4707e694912cd387dfa8935e5772344c643fa25a57a7ffaf4d745ed04dae6daa +size 39219 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d07dc4a416677741c96121e6a79b15f939bcb7d --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:536dcb29214c26c649d000648182a35bf494615e3e7721ad6b624e14706ab73d +size 54421 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/90ee16ccc0ad16aeca48087797d7b07f_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/90ee16ccc0ad16aeca48087797d7b07f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fa5d6f9199e438ae6e138a544d5e473ba46ccd0 --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/90ee16ccc0ad16aeca48087797d7b07f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ba52d43e329f7e1e073355beeea866be1fa24c857e5a612b433a4efbb4690a1 +size 14529 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/9d47fe89bc71acebde670ea760ee6ffb_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/9d47fe89bc71acebde670ea760ee6ffb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed9fce071b21fef9fba8601cd0cf45ffc5efeb13 --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/9d47fe89bc71acebde670ea760ee6ffb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e92aed26d4fe4483e33f51d8d29959332df87101853d340cbaea99115954af13 +size 26727 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/a57d566566ac81d4832e5000924f5e84_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/a57d566566ac81d4832e5000924f5e84_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4be80fdf6bf9fcbec5b0faf2c074ce8ebc971d02 --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/a57d566566ac81d4832e5000924f5e84_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18051a2d5e4a502c10ffe0191813f2907d9a56b781d846a131559a8d4c7a0ac6 +size 80529 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..153cfadc966aec75069a2060526eef6994fc76b7 --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a499875046ac098f126f4165d0cec7199c23a2f11603f2243c6fa52f7bcaf144 +size 51852 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71436c3f7afc66323cf8086c745b1fe4958ee546 --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6daca5608902dd3549f13ae7aebbec7f26e8ad736064690d6d7290d1af76192a +size 143053 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad8fe8f0e5871ffa938b5f4ba3c5139ff0b96536 --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13b316826c1c9ba6dd0b6dc76ec53ee4a8d2b0c30737351683bbf1e1e65ba606 +size 32777 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0145bc45285fc814913b4990345b1c5778224d8 --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d78f7351746714860573764b2b3935e57b54795f32d45ac50521a734e98f1a1e +size 46659 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7263326dec84e24123376e3b1882fa6f02864471 --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68dfc856980392b42d11d5eeb99fe2aec2f3c543e6f3b663da39fa148024ae37 +size 34821 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/fc7c83167c4e9e614f40e52b39ef735d_img.jpg b/marked/G/T-REC-G.997.1-201902-I_PDF-E/fc7c83167c4e9e614f40e52b39ef735d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d64c1ce07ca06f7554d1b5ad0ea030074f14696e --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/fc7c83167c4e9e614f40e52b39ef735d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:825367c8d9cbc698aad1de16ae00b6c4dadf40e95818f733f2b553662a023c61 +size 33451 diff --git a/marked/G/T-REC-G.997.1-201902-I_PDF-E/raw.md b/marked/G/T-REC-G.997.1-201902-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b84d3945a497cf760766b0fd9120930e340a2ea1 --- /dev/null +++ b/marked/G/T-REC-G.997.1-201902-I_PDF-E/raw.md @@ -0,0 +1,5967 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.997.1** + +(02/2019) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital sections and digital line system – Metallic access +networks + +--- + +**Physical layer management for digital +subscriber line transceivers** + +Recommendation ITU-T G.997.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 | +| 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.997.1 + +## Physical layer management for digital subscriber line transceivers + +## Summary + +Recommendation ITU-T G.997.1 specifies: + +- the physical layer management for asymmetric digital subscriber line (ADSL) and very high speed digital subscriber line 2 (VDSL2) transmission systems; +- means of communication on a transport transmission channel defined in the physical layer (see Recommendations ITU-T G.992.1, ITU-T G.992.2, ITU-T G.992.3, ITU-T G.992.4, ITU-T G.992.5 and ITU-T G.993.2; +- network element (NE) content and syntax for configuration, fault and performance management. + +This edition of Recommendation ITU-T G.997.1: + +- includes the management information base (MIB) elements for the physical layer management of Recommendation ITU-T G.993.2 and additional MIB elements for the physical layer management of Recommendations ITU-T G.992.3 and ITU-T G.992.5; +- adds support for Annex N of ITU-T G.993.2 power spectral density (PSD) masks; +- adds support of maximum error-free throughput (MAXEFTR) and extends the specification of error-free bits counter and minimum error-free throughput (MINEFTR) the parameters to apply to lines with retransmission inactive. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|-----------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.997.1 | 1999-07-02 | 15 | 11.1002/1000/4723 | +| 2.0 | ITU-T G.997.1 | 2003-05-22 | 15 | 11.1002/1000/6283 | +| 2.1 | ITU-T G.997.1 (2003) Amd. 1 | 2003-12-14 | 15 | 11.1002/1000/7081 | +| 2.2 | ITU-T G.997.1 (2003) Amd. 2 | 2005-01-13 | 15 | 11.1002/1000/7492 | +| 3.0 | ITU-T G.997.1 | 2005-09-06 | 15 | 11.1002/1000/8550 | +| 4.0 | ITU-T G.997.1 | 2006-06-06 | 15 | 11.1002/1000/8768 | +| 4.1 | ITU-T G.997.1 (2006) Cor. 1 | 2006-12-14 | 15 | 11.1002/1000/8994 | +| 4.2 | ITU-T G.997.1 (2006) Amd. 1 | 2006-12-14 | 15 | 11.1002/1000/8995 | +| 4.3 | ITU-T G.997.1 (2006) Amd. 2 | 2007-11-22 | 15 | 11.1002/1000/9168 | +| 4.4 | ITU-T G.997.1 (2006) Amd. 3 | 2008-08-22 | 15 | 11.1002/1000/9389 | +| 5.0 | ITU-T G.997.1 | 2009-04-22 | 15 | 11.1002/1000/9676 | +| 5.1 | ITU-T G.997.1 (2009) Cor. 1 | 2009-11-13 | 15 | 11.1002/1000/10417 | +| 5.2 | ITU-T G.997.1 (2009) Amd. 1 | 2010-06-11 | 15 | 11.1002/1000/10416 | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +| | | | | | +|-----|-----------------------------|------------|----|------------------------------------| +| 5.3 | ITU-T G.997.1 (2009) Amd. 2 | 2010-11-29 | 15 | 11.1002/1000/11016 | +| 5.4 | ITU-T G.997.1 (2009) Amd. 3 | 2011-06-22 | 15 | 11.1002/1000/11130 | +| 5.5 | ITU-T G.997.1 (2009) Cor. 2 | 2011-10-29 | 15 | 11.1002/1000/11397 | +| 5.6 | ITU-T G.997.1 (2009) Amd. 4 | 2011-12-16 | 15 | 11.1002/1000/11398 | +| 5.7 | ITU-T G.997.1 (2009) Amd. 5 | 2012-02-13 | 15 | 11.1002/1000/11504 | +| 6.0 | ITU-T G.997.1 | 2012-06-13 | 15 | 11.1002/1000/11645 | +| 6.1 | ITU-T G.997.1 (2012) Amd. 1 | 2012-12-07 | 15 | 11.1002/1000/11798 | +| 6.2 | ITU-T G.997.1 (2012) Amd. 2 | 2013-04-22 | 15 | 11.1002/1000/11893 | +| 6.3 | ITU-T G.997.1 (2012) Amd. 3 | 2013-08-29 | 15 | 11.1002/1000/11996 | +| 6.4 | ITU-T G.997.1 (2012) Amd. 4 | 2015-02-13 | 15 | 11.1002/1000/12374 | +| 6.5 | ITU-T G.997.1 (2012) Amd. 5 | 2015-11-06 | 15 | 11.1002/1000/12566 | +| 6.6 | ITU-T G.997.1 (2012) Amd. 6 | 2016-03-29 | 15 | 11.1002/1000/12798 | +| 6.7 | ITU-T G.997.1 (2012) Cor. 1 | 2016-11-13 | 15 | 11.1002/1000/13108 | +| 6.8 | ITU-T G.997.1 (2012) Amd. 7 | 2017-12-07 | 15 | 11.1002/1000/13336 | +| 7.0 | ITU-T G.997.1 | 2016-11-13 | 15 | 11.1002/1000/13346 | +| 7.1 | ITU-T G.997.1 (2016) Amd. 1 | 2017-12-07 | 15 | 11.1002/1000/13514 | +| 7.2 | ITU-T G.997.1 (2016) Cor. 1 | 2018-03-16 | 15 | 11.1002/1000/13533 | +| 7.3 | ITU-T G.997.1 (2016) Amd. 2 | 2018-05-22 | 15 | 11.1002/1000/13536 | +| 8.0 | ITU-T G.997.1 | 2019-02-22 | 15 | 11.1002/1000/13751 | + +## Keywords + +VDSL transceivers, ADSL transceivers, management, performance monitoring + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2019 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|------------------------------------------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Overview..... | 6 | +| 5.1 Physical layer management mechanisms ..... | 8 | +| 6 Operations, administration and maintenance communications channel..... | 9 | +| 6.1 Requirements on the physical media dependent layer for the bit-oriented clear embedded operations channel..... | 10 | +| 6.2 Requirements on the physical media dependent layer for the message-oriented clear embedded operations channel..... | 10 | +| 6.3 Data link layer ..... | 11 | +| 6.4 The simple network management protocol protocol ..... | 14 | +| 8 Management information base elements ..... | 16 | +| 7.1 Failures ..... | 19 | +| 7.2 Performance monitoring functions ..... | 21 | +| 7.3 Configuration functions..... | 35 | +| 7.4 Inventory information..... | 75 | +| 7.5 Test, diagnostic and status parameters ..... | 78 | +| 7.6 Network management elements partitioning..... | 102 | +| Appendix I – Processing examples ..... | 142 | +| I.1 Illustration of transmitter processing..... | 142 | +| I.2 Illustration of receiver processing ..... | 143 | +| Appendix II – Downstream power back-off ..... | 144 | +| II.1 Introduction ..... | 144 | +| II.2 Description of the downstream power back-off method ..... | 145 | +| Bibliography..... | 147 | + +## Recommendation ITU-T G.997.1 + +## Physical layer management for digital subscriber line transceivers + +# 1 Scope + +This Recommendation specifies the physical layer management for asymmetric digital subscriber line (ADSL) and very high speed digital subscriber line 2 (VDSL2) transmission systems based on the usage of indicator bits and embedded operations channel (EOC) messages specified in the ITU-T G.992.x series of Recommendations and in [ITU-T G.993.2], and the clear EOC specified in this Recommendation. + +This Recommendation specifies network management elements content for configuration, fault and performance management. + +The mechanisms to provide operations, administration and maintenance (OAM) functions, and to generate OAM flows F1, F2 and F3, depend on the transport mechanism of the physical layer transmission system, as well as on the supervision functions contained within the physical layer termination functions of equipment. This Recommendation specifies only flow F3 – transmission path level. + +For interrelationships of this Recommendation with other Recommendations of the ITU-T G.99x-series, see [ITU-T G.995.1]. + +# 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.992.1] Recommendation ITU-T G.992.1 (1999), *Asymmetric digital subscriber line (ADSL) transceivers*. +- [ITU-T G.992.2] Recommendation ITU-T G.992.2 (1999), *Splitterless asymmetric digital subscriber line (ADSL) transceivers*. +- [ITU-T G.992.3] Recommendation ITU-T G.992.3 (2009), *Asymmetric digital subscriber line transceivers 2 (ADSL2)*. +- [ITU-T G.992.4] Recommendation ITU-T G.992.4 (2002), *Splitterless asymmetric digital subscriber line transceivers 2 (splitterless ADSL2)*. +- [ITU-T G.992.5] Recommendation ITU-T G.992.5 (2009), *Asymmetric digital subscriber line 2 (ADSL2) transceivers – Extended bandwidth ADSL2 (ADSL2plus)*. +- [ITU-T G.993.2] Recommendation ITU-T G.993.2 (2019), *Very high speed digital subscriber line transceivers 2 (VDSL2)*. +- [ITU-T G.993.5] Recommendation ITU-T G.993.5 (2019), *Self-FEXT cancellation (vectoring) for use with VDSL2 transceivers*. +- [ITU-T G.994.1] Recommendation ITU-T G.994.1 (2018), *Handshake procedures for digital subscriber line transceivers*. + +- [ITU-T G.995.1] Recommendation ITU-T G.995.1 (2001), *Overview of digital subscriber line (DSL) Recommendations*. +- [ITU-T G.998.4] Recommendation ITU-T G.998.4 (2018), *Improved impulse noise protection for digital subscriber line (DSL) transceivers*. +- [ITU-T I.610] Recommendation ITU-T I.610 (1999), *B-ISDN operation and maintenance principles and functions*. +- [ITU-T T.35] Recommendation ITU-T T.35 (2000), *Procedure for the allocation of ITU-T defined codes for non-standard facilities*. +- [IETF RFC 1157] IETF RFC 1157 (1990), *A simple network management protocol (SNMP)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 anomaly** [ITU-T G.992.1]: A discrepancy between the actual and desired characteristics of an item. The desired characteristic may be expressed in the form of a specification. An anomaly may or may not affect the ability of an item to perform a required function. + +**3.1.2 bearer channel** [ITU-T G.992.1]: A user data stream of a specified data rate that is transported transparently by an ADSL system. + +NOTE – Bearer channel is also referred to as frame bearer. + +**3.1.3 defect** [ITU-T G.993.2]: A limited interruption in the ability of an item to perform a required function. It may or may not lead to maintenance action depending on the results of additional analysis. Successive anomalies causing a decrease in the ability of an item to perform a required function are considered a defect. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 accumulation period**: Period of time used by the network management system to accumulate sufficient number of parameter samples. + +**3.2.2 clear embedded operations channel**: An octet oriented data channel multiplexed in the physical layer transmission frame structure. + +**3.2.3 failure**: Termination of the ability of an item to perform a required function. + +NOTE – After failure, the item has a fault. Analysis of successive anomalies or defects affecting the same item can lead to the item being considered as "failed". + +**3.2.4 full initialization**: Any type of initialization procedure specified in relevant Recommendations, except short initialization. + +**3.2.5 masked subcarrier**: A subcarrier that is not transmitted during initialization and showtime. + +**3.2.6 MEDLEY set**: A set of subcarriers used during the digital subscriber line initialization. + +NOTE – This set is defined in the respective Recommendations. + +**3.2.7 net data rate**: As defined in the ITU-T G.992.x-series of Recommendations and in [ITU-T G.993.2]. + +**3.2.8 short initialization**: A shortened type of initialization procedure, as specified in clause 7.2.1.3.3 and that includes fast retrain, as specified in [ITU-T G.992.2], and short initialization, as specified in [ITU-T G.992.3] and [ITU-T G.992.4]. + +### **3.2.9 showtime:** + +NOTE – As defined in the respective DSL Recommendation. + +**3.2.10 x-type digital subscriber line (xDSL):** Any of the various types of digital subscriber line technology. + +NOTE – Based on [ITU-T G.992.3]. + +**3.2.11 $\alpha$ -interface, $\beta$ -interface:** Interface between the physical media specific-transmission convergence (PMS-TC) and the transport protocol specific-transmission convergence (TPS-TC) sub-layers of the x-type digital subscriber line transceiver unit (xTU), as specified in [ITU-T G.995.1] and the relevant Recommendations. + +**3.2.12 $\gamma$ -interface:** Application interface of the x-type digital subscriber line transceiver unit (xTU), as specified in [ITU-T G.995.1] and the relevant Recommendations. + +**3.2.13 VDSL2-LR mode:** Operation according to [ITU-T G.993.2] Annex D or [ITU-T G.993.5] Annex B. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|----------------------------------------------------| +| ADSL | Asymmetric Digital Subscriber Line | +| AME | ADSL Management Entity | +| AN | Access Node | +| ASCII | American Standard Code for Information Interchange | +| ATM | Asynchronous Transfer Mode | +| ATTNDR | Attainable Net Data Rate | +| ATU | ADSL Transceiver Unit | +| ATU-C | ADSL Transceiver Unit-Central office end | +| ATU-R | ADSL Transceiver Unit-Remote side | +| BER | Bit Error Ratio | +| CL | Capabilities List | +| CLR | Capabilities List Request | +| CO-MIB | Central Office-Management Information Base | +| CRC | Cyclic Redundancy Check | +| CV-C | Code Violation-Channel | +| CV-CFE | Code Violation-Channel Far-End | +| DMT | Discrete Multitone | +| DPBO | Downstream Power Back-Off | +| DTU | Data Transfer Unit | +| EOC | Embedded Operations Channel | +| ES | Errored Second | +| ES-L | Errored Second-Line | +| ES-LFE | Errored Second-Line Far-End | + +| | | +|----------|----------------------------------------------| +| ETR | Expected Throughput | +| FEFE | Far-End Block Error | +| FEC | Forward Error Correction | +| FEC-C | Forward Error Correction-Channel | +| FEC-CFE | Forward Error Correction-Channel Far-End | +| FECS-L | Forward Error Correction Second-Line | +| FECS-LFE | Forward Error Correction Second-Line Far-End | +| FEXT | Far-End Crosstalk | +| FFEC | Far-end Forward Error Correction | +| HDLC | High-level Data Link Control | +| HEC | Header Error Control | +| ID | Identifier | +| IMA | Inverse Multiplexing over ATM | +| INM | Impulse Noise Monitoring | +| INP | Impulse Noise Protection | +| ISDN | Integrated Services Digital Network | +| LCD | Loss of Cell Delineation | +| LCD-FE | Far-End Loss of Cell Delineation | +| LDR | Loop Diagnostics mode Results | +| LDS | Loop Diagnostics mode Status | +| LDSF | Loop Diagnostic mode Status Forced | +| LINIT | Line Initialization | +| LOF | Loss of Frame | +| LOF-FE | Far-End Loss of Frame | +| LOS | Loss of Signal | +| LOS-FE | Far-End Loss of Signal | +| LOSS-L | LOS Second-Line | +| LPR | Loss of Power | +| LPR-FE | Far-End Loss of Power | +| LSB | Least Significant Bit | +| MAXEFTR | Maximum Error-Free Throughput | +| MDIO | Management Data Input/Output | +| ME | Management Entity | +| MIB | Management Information Base | +| MINFTR | Minimum Error-Free Throughput | +| MSB | Most Significant Bit | +| MUF | Maximum Usable Frequency | + +| | | +|----------|----------------------------------------------------------------| +| NCD | No Cell Delineation | +| NCD-FE | Far-End No Cell Delineation | +| NE | Network Element | +| NEXT | Near-End Crosstalk | +| NMS | Network Management System | +| NT | Network Termination | +| OAM | Operations, Administration and Maintenance | +| OLR | On-Line Reconfiguration | +| ONU | Optical Network Unit | +| OOS | Out of Sync | +| OOS-FE | Far-End Out of Sync | +| PDU | Protocol Data Unit | +| PM | Performance Monitoring | +| PMD | Physical Media Dependent | +| PMSF | Power Management State Forced | +| PMS-TC | Physical Media Specific-Transmission Convergence | +| POTS | Plain Old Telephone Service | +| PSD | Power Spectral Density | +| PTM | Packet Transfer Mode | +| RDI | Remote Defect Indication | +| REIN | Repetitive Electrical Impulse Noise | +| RFI | Remote Failure Indication | +| RIPOLICY | Re-Initialization Policy | +| ROC | Robust Overhead Channel | +| SEF | Severely Errored Frame | +| SES | Severely Errored Second | +| SNMP | Simple Network Management Protocol | +| SNR | Signal-to-Noise Ratio | +| SOS | Save Our Showtime | +| SRA | Seamless Rate Adaptation | +| STM | Synchronous Transfer Mode | +| TC | Transmission Convergence | +| TCM-ISDN | Time Compression Multiplex-Integrated Services Digital Network | +| TE | Terminal Equipment | +| TPS-TC | Transport Protocol Specific-Transmission Convergence | +| TR | Threshold Report | +| UAS | Unavailable Second | + +| | | +|-------|-------------------------------------------| +| UAS-L | Unavailable Second-Line | +| VCE | Vectoring Control Entity | +| VDSL2 | Very high speed Digital Subscriber Line 2 | +| VME | VDSL2 Management Entity | +| VTU | VDSL2 Transceiver Unit | +| VTU-O | VDSL2 Transceiver Unit-central Office | +| VTU-R | VTU at the Remote site | +| xDSL | x-type Digital Subscriber Line | +| xTU | xDSL Transceiver Unit | +| xTU-C | xDSL Transceiver Unit-Central office end | +| xTU-R | xDSL Transceiver Unit at the remote side | + +# 5 Overview + +Figure 5-1 shows the system reference model for this Recommendation. + +![Figure 5-1 – System reference model. The diagram shows a network architecture with a Home network on the left connected to a Transceiver Unit (TU) containing a Management entity, PHY, and ATU-R. This is connected via a line to another TU containing a Management entity, ATU-C, PHY, and connected to a Broadband network on the right. A Network Management System (NMS) is connected to the second TU's Management entity via a Q-interface. Management flows are indicated by dashed arrows between the Management entities and the NMS. Reference points T/S, T-R, U-R, U-C, V-C, and V are marked along the line.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Diagram details: The diagram illustrates the system reference model. On the left, a 'Home network' cloud is connected to two 'TE' (Terminal Equipment) boxes. These are connected to a Transceiver Unit (TU) on the left. This TU contains a 'Management entity' (oval), a 'PHY' (Physical Layer) block, and an 'ATU-R' (Remote Transceiver Unit). The TU is connected to a line. Reference points 'T/S' (Transceiver System), 'T-R' (Transceiver Remote), and 'U-R' (User Remote) are marked. The line connects to another TU on the right. This TU contains a 'Management entity' (oval), an 'ATU-C' (Central Transceiver Unit), a 'PHY' block, and is connected to a 'Broadband network' cloud. Reference points 'U-C' (User Central), 'V-C' (Vendor Central), and 'V' (Vendor) are marked. Above the right TU, a 'NMS' (Network Management System) cloud is connected via a 'Q' interface. Dashed arrows indicate management flows: from the NMS to the right Management entity, and from both the right and left Management entities to each other. A legend at the bottom left shows a dashed double-headed arrow labeled 'Management flow in ITU-T Rec. G.997.1'. The diagram is labeled 'G.997.1(19)\_F5-1' in the bottom right. + +Figure 5-1 – System reference model. The diagram shows a network architecture with a Home network on the left connected to a Transceiver Unit (TU) containing a Management entity, PHY, and ATU-R. This is connected via a line to another TU containing a Management entity, ATU-C, PHY, and connected to a Broadband network on the right. A Network Management System (NMS) is connected to the second TU's Management entity via a Q-interface. Management flows are indicated by dashed arrows between the Management entities and the NMS. Reference points T/S, T-R, U-R, U-C, V-C, and V are marked along the line. + +**Figure 5-1 – System reference model** + +There are four management interfaces specified in this Recommendation. + +The Q-interface is at the access node (AN) for network management systems (NMSs). All the parameters specified in this Recommendation apply at the Q-interface. The Q-interface provides the interface between the NMS of the operator and the management entity (ME) in the AN. + +The near-end parameters supported in the ME at the AN are derived from the xDSL transceiver unit-central office end1 (i.e., at the network operator) (xTU-C) while the far-end parameters from the xDSL + +1 A generic term referring to both the ADSL transceiver unit-central office end (ATU-C) of the ITU-T G.992.x series of Recommendations and the VDSL2 transceiver unit-central office or NE end (in the optical network unit (ONU) per [ITU-T G.993.2], i.e., network operator (VTU-O) of [ITU-T G.993.2]). + +transceiver unit at the remote side2 (i.e., at the subscriber end of the loop) (xTU-R) can be derived by either of two mechanisms over the U-interface: + +- indicator bits and EOC messages can be used to generate the required xTU-R parameters in the ME of the AN; +- the OAM channel and protocol (specified in clause 6) can be used to retrieve the parameters from the xTU-R, when requested by the ME of the AN. + +Outside the scope of this Recommendation are: specification of the transport of the management instrumentation over the Q-interface; coding of the management information transferred over the Q-interface. + +Two management interfaces, the loop interface-central office end (U-C) at the xTU-C and loop interface-remote side (i.e., subscriber end of the loop) (U-R) at the xTU-R, are specified. Their main purposes are to provide: + +- at the xTU-C: the xTU-C near-end parameters for the xTU-R to retrieve over the U-interface; +- at the xTU-R: the xTU-R near-end parameters for the xTU-C to retrieve over the U-interface. + +This Recommendation specifies (see clause 6) a method for the communication of the xDSL transceiver unit (xTU) parameters specified in clause 7 over the U-interface. + +NOTE 1 – In this Recommendation, U-C and U-R refer to the management interfaces that apply to the appropriate physical reference points specified in corresponding Recommendations. In [ITU-T G.993.2], the reference point U-C is referred to as U-O. + +At the T/S-interface, a subset of the parameters specified in this Recommendation may apply. The purpose is to indicate the ADSL or VDSL2 link status to the terminal equipment (TE). These parameters are maintained by the ME of the network termination (NT) and are made available over the T/S-interface. + +The G-interface refers to the management flows from the ME on the NT directly to the NMS when that flow crosses the U-C- and U-R-interface, but the management flow is not mediated by the ME on the AN. The specification of the protocols to support flows that cross the G-interface lies outside the scope of this Recommendation. The parameters supported at the G-interface are a superset of those supported at the T/S-interface and they are maintained by the ME of the NT. + +The far-end parameters (from the xTU-C) can be derived by either of two mechanisms over the U-interface: + +- indicator bits and EOC messages, which are provided at the physical media dependent (PMD) layer, can be used to generate the required xTU-C parameters in the ME of the NT; +- the OAM channel and protocol (specified in clause 6) can be used to retrieve the parameters from the xTU-C, when requested by the ME of the NT. + +Outside the scope of this Recommendation are: specification of the transport of this management information over the T/S-interfaces; coding of the management information transferred over the T/S-interface. + +Depending on the transceiver Recommendation (e.g., [ITU-T G.992.1] or [ITU-T G.992.2]), some of the parameters may not apply (i.e., fast data stream parameters for [ITU-T G.992.2]). + +Specific parameters may be applicable to specific transceiver Recommendations. Tables 7-10 to 7-41 provide the applicability of any specific parameter to any particular Recommendation in the ITU-T G.992.x series of Recommendations or to [ITU-T G.993.2]. + +--- + +2 A generic term referring to both the ADSL transceiver unit-remote side (ATU-R; i.e., subscriber end of the loop) of the ITU-T G.992.x series of Recommendations and the VTU at the remote site (i.e., subscriber end of the loop) (VTU-R) of [ITU-T G.993.2]. + +NOTE 2 – Throughout this Recommendation, the use of the term xTU-C refers to both ATU-C and VTU-O, while the term xTU-R refers to both ATU-R and VTU-R. + +## 5.1 Physical layer management mechanisms + +OAM for ATM networks are specified generally in [ITU-T I.610]. This Recommendation uses this model for both ATM and packet transfer mode (PTM). The physical layer contains the three lowest OAM levels, as outlined in Figure 5-2. The allocation of the OAM flows is as follows: + +- F1: regenerator section level; +- F2: digital section level; +- F3: transmission path level. + +![Diagram illustrating the OAM hierarchical levels (F1 to F5) and their relationship with the ATM and Physical layers. The diagram shows five horizontal levels: F5 (Virtual channel level), F4 (Virtual path level), F3 (Transmission path level), F2 (Digital section level), and F1 (Regenerator section level). F1 to F3 are grouped under the 'Physical layer', and F4 to F5 are grouped under the 'ATM layer'. Endpoints are marked with concentric circles, and connecting points are marked with open circles. Dashed arrows show the flow of OAM between levels.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +The diagram illustrates the hierarchical structure of OAM levels. It is divided into two main layers: the ATM layer (top) and the Physical layer (bottom), separated by a horizontal dash-dot line. + +- ATM layer:** Contains level F5 (Virtual channel level) and level F4 (Virtual path level). +- Physical layer:** Contains level F3 (Transmission path level), level F2 (Digital section level), and level F1 (Regenerator section level). + +Each level is represented by a horizontal line with nodes. Concentric circles represent 'Endpoint of corresponding levels', and open circles represent 'Connecting point of corresponding levels'. Dashed arrows indicate the hierarchical relationship and flow between the levels, showing how lower-level segments compose higher-level paths. On the left, vertical arrows indicate the span of the ATM and Physical layers. + +G.997.1(19)\_F5-2 + +Diagram illustrating the OAM hierarchical levels (F1 to F5) and their relationship with the ATM and Physical layers. The diagram shows five horizontal levels: F5 (Virtual channel level), F4 (Virtual path level), F3 (Transmission path level), F2 (Digital section level), and F1 (Regenerator section level). F1 to F3 are grouped under the 'Physical layer', and F4 to F5 are grouped under the 'ATM layer'. Endpoints are marked with concentric circles, and connecting points are marked with open circles. Dashed arrows show the flow of OAM between levels. + +**Figure 5-2 – Operations, administration and maintenance hierarchical levels and their relationship with the asynchronous transfer mode layer and physical layer** + +The physical levels F1 to F3 in this Recommendation are coupled with upper levels F4 and F5 from the fault management perspective. When an F3 fault (e.g., loss of signal (LOS)) is detected, it is reported to the NMS, but an F4/F5, as specified in [ITU-T I.610], fault is generated as well. + +The OAM levels F1 to F3 cover the part of the system referred to as xDSL LINE in Figure 5-3. This part includes analogue processing and digital processing for the metallic transmission medium. Levels F1 to F3 provide performance monitoring (PM) of both analogue and digital line-related entities. The x-type digital subscriber line (xDSL) LINE is delimited by the two end points V-D (or $\alpha$ ) and T-D (or $\beta$ ) as presented in Figure 5-3. The xDSL LINE is defined between the V-D (or $\alpha$ ) and the T-D (or $\beta$ ) reference points. + +The xDSL ATM PATH is defined between: a) the logical interface between an ADSL transceiver unit-central office end (ATU-C; i.e., network operator) and a digital network element (NE), such as one or more switching systems (V-C or $\gamma_c$ ); and b) an interface between ATU-R and switching layer (ATM, STM or PTM) (T-R or $\gamma_r$ ) reference points. + +The xDSL PTM PATH is defined between the V-C (or $\gamma_c$ ) and T-R (or $\gamma_r$ ) reference points. + +The xDSL STM PATH is for further study. + +![Figure 5-3: xDSL LINE and xDSL ATM or PTM PATH definition diagram. The diagram shows a symmetric xDSL system with a central U-interface. On the left (V-C side), two ATM interfaces (ATM0 and ATM1) connect to Cell TC blocks. These blocks output AS01, LS01, AS11, and LS11 signals to a Mux. The Mux also receives a 'Clear EOC' signal. The output of the Mux goes through 'Digital processing' and 'Analogue processing' blocks to the U-interface. On the right (T-R side), the signal passes through another 'Analogue processing' and 'Digital processing' block to a second Mux. This Mux outputs IAS0, LS0, AS1, and LS1 signals to two Cell TC blocks, which then connect to ATM0 and ATM1 interfaces. Below the diagram, a double-headed arrow labeled 'ADSL LINE' spans from the V-D interface to the T-D interface. Another double-headed arrow labeled 'ADSL ATM PATH' spans from the V-C interface to the T-R interface. The reference code 'G.997.1(19)_F5-3' is in the bottom right corner.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +Figure 5-3: xDSL LINE and xDSL ATM or PTM PATH definition diagram. The diagram shows a symmetric xDSL system with a central U-interface. On the left (V-C side), two ATM interfaces (ATM0 and ATM1) connect to Cell TC blocks. These blocks output AS01, LS01, AS11, and LS11 signals to a Mux. The Mux also receives a 'Clear EOC' signal. The output of the Mux goes through 'Digital processing' and 'Analogue processing' blocks to the U-interface. On the right (T-R side), the signal passes through another 'Analogue processing' and 'Digital processing' block to a second Mux. This Mux outputs IAS0, LS0, AS1, and LS1 signals to two Cell TC blocks, which then connect to ATM0 and ATM1 interfaces. Below the diagram, a double-headed arrow labeled 'ADSL LINE' spans from the V-D interface to the T-D interface. Another double-headed arrow labeled 'ADSL ATM PATH' spans from the V-C interface to the T-R interface. The reference code 'G.997.1(19)\_F5-3' is in the bottom right corner. + +**Figure 5-3 – xDSL LINE and xDSL ATM or PTM PATH definition** + +# 6 Operations, administration and maintenance communications channel + +This clause specifies an optional OAM communication channel across the U-interface (see Figure 6-1). If this channel is implemented, the xTU-C and the xTU-R may use it to transport physical layer OAM messages. If either the xTU-C or the xTU-R does not have the capability of this OAM channel, the far-end parameters, defined in clause 7, at the xTU-C shall be derived from the indicator bits and EOC messages defined in the ITU-T G.992.x-series of Recommendations and in [ITU-T G.993.2]. Support for the OAM communication channel specified in this clause will be indicated during initialization by messages specified in [ITU-T G.994.1] for [ITU-T G.992.1] and [ITU-T G.992.2]. + +NOTE 1 – In those cases where neither the xTU-R nor the xTU-C implements this communication channel, there are some reduced physical layer OAM capabilities (see clause 7). + +The ITU-T G.992.x-series of Recommendations and [ITU-T G.993.2] may provide one of two mechanisms to transport physical layer OAM messages. + +- For [ITU-T G.992.1] and [ITU-T G.992.2], the mechanism is a bit-oriented clear EOC and the channel shall meet the requirements specified in clause 6.1. The data link layer shall be as specified in clause 6.3. +- For [ITU-T G.992.3], [ITU-T G.992.4], [ITU-T G.992.5] and [ITU-T G.993.2], the mechanism is a message-oriented clear EOC and the channel shall meet the requirements specified in clause 6.2. The data link layer shall be as specified in clauses 7.8.2.3, 7.8.2.4 and 9.4.1.8 of [ITU-T G.992.3] for [ITU-T G.992.3], [ITU-T G.992.4] and [ITU-T G.992.5]; and as specified in clauses 8.2 and 11.2.3 of [ITU-T G.993.2] for [ITU-T G.993.2]. + +See Figure 6-2. + +![Figure 6-1: Operations, administration and maintenance communication channel layers for bit-oriented clear embedded operations channel diagram. The diagram shows two protocol stacks connected by a 'U-interface'. The left stack is for the ATU-R and includes a MIB (Management Information Base) connected to an SNMP block, which is connected to an HDLC block, which is connected to a Clear EOC block, which is connected to a Bit transmission block. The right stack is for the ATU-C and has the same structure. The U-interface is shown as a horizontal line connecting the Bit transmission blocks of both stacks. The reference code 'G.997.1(19)_F6-1' is in the bottom right corner.](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +Figure 6-1: Operations, administration and maintenance communication channel layers for bit-oriented clear embedded operations channel diagram. The diagram shows two protocol stacks connected by a 'U-interface'. The left stack is for the ATU-R and includes a MIB (Management Information Base) connected to an SNMP block, which is connected to an HDLC block, which is connected to a Clear EOC block, which is connected to a Bit transmission block. The right stack is for the ATU-C and has the same structure. The U-interface is shown as a horizontal line connecting the Bit transmission blocks of both stacks. The reference code 'G.997.1(19)\_F6-1' is in the bottom right corner. + +**Figure 6-1 – Operations, administration and maintenance communication channel layers for bit-oriented clear embedded operations channel** +**MIB: management information base** + +![Diagram of Operations, administration and maintenance communication channel layers for message-oriented clear embedded operations channel. It shows two entities, ATU-C and ATU-R, connected by a U-interface. Each entity has a stack of layers: Overhead channel, HDLC, Clear EOC Msg, and SNMP. A Management Information Base (MIB) is shown for each entity, with arrows indicating its connection to the SNMP layer.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +The diagram illustrates the protocol stack for message-oriented clear embedded operations channels (EOC) between an ATU-C (Client) and an ATU-R (Remote). Both units are connected via a U-interface. Each unit contains a stack of four layers: Overhead channel (bottom), HDLC, Clear EOC Msg, and SNMP (top). A Management Information Base (MIB) is associated with each unit, with an arrow pointing from the MIB to the SNMP layer. The diagram is labeled G.997.1(19)\_F6-2. + +Diagram of Operations, administration and maintenance communication channel layers for message-oriented clear embedded operations channel. It shows two entities, ATU-C and ATU-R, connected by a U-interface. Each entity has a stack of layers: Overhead channel, HDLC, Clear EOC Msg, and SNMP. A Management Information Base (MIB) is shown for each entity, with arrows indicating its connection to the SNMP layer. + +**Figure 6-2 – Operations, administration and maintenance communication channel layers for message-oriented clear embedded operations channel** +**MIB: management information base** + +NOTE 2 – In Figures 6-1 and 6-2, the MIB is related to the xTU. + +## 6.1 Requirements on the physical media dependent layer for the bit-oriented clear embedded operations channel + +In order to support the physical layer OAM protocols defined in this Recommendation, a physical layer Recommendation shall provide a full duplex data channel for support of the data link layer specified in clause 6.3. + +The clear EOC serves the function of a physical layer of the protocol stack specified in this Recommendation for [ITU-T G.992.2] and [ITU-T G.992.1]. + +- 1) The clear EOC shall be a part of the protocol overhead for the particular xDSL Recommendation. +- 2) The clear EOC shall be available to carry traffic whenever the xDSL protocol is in a normal transmission mode (e.g., "showtime"). +- 3) The clear EOC shall be available regardless of the specific configuration options or run time adaptation of an ATU-C and ATU-R that are communicating. +- 4) The clear EOC shall be terminated in the ATU-R and the ATU-C. +- 5) The clear EOC shall support traffic of at least 4 kbit/s. +- 6) The clear EOC shall support delineation of individual octets in order to support the link level protocol defined in clause 7.1. +- 7) The clear EOC should not support error correction or detection, which are rather supported by use of the OAM stack defined in this Recommendation. +- 8) The clear EOC should not guarantee the delivery of data carried over the channel. +- 9) The clear EOC should not support retransmission of data upon error. +- 10) The clear EOC should not acknowledge the receipt of data by the far end of the link. +- 11) The clear EOC should not require a specific initialization procedure. It can be assumed to be operational whenever the two modems are in synchronization for "showtime" transport of data. + +## 6.2 Requirements on the physical media dependent layer for the message-oriented clear embedded operations channel + +In order to support the physical layer OAM protocols defined in this Recommendation, a physical layer Recommendation shall provide a full duplex data channel for support of the simple network management protocol (SNMP) defined in clause 6.4. + +- 1) The clear EOC shall be a part of the protocol overhead for the particular xDSL Recommendation. +- 2) The clear EOC shall be available to carry traffic whenever the xDSL protocol is in a normal transmission mode (e.g., "showtime", specified in the relevant Recommendations). +- 3) The clear EOC shall be available regardless of the specific configuration of an xTU-C and xTU-R that are communicating. +- 4) The clear EOC shall be terminated in the xTU-R and the xTU-C. +- 5) The clear EOC shall support a bit rate of at least 4 kbit/s. +- 6) The clear EOC shall support delineation of messages through high-level data link control (HDLC) in order to support the link level protocol defined in clause 7.1. +- 7) The clear EOC should not support retransmission of data upon error. +- 8) The clear EOC should not require a specific initialization procedure. It can be assumed to be operational whenever the two modems are in synchronization for "showtime" transport of data. + +## 6.3 Data link layer + +For the transport mechanism, an HDLC-like mechanism is specified with the characteristics detailed in clauses 6.3.1 to 6.3.7. The specified method is based on [b-ISO/IEC 13239]. The requirements in clauses 6.3.1 to 6.3.7 apply only to the bit-oriented clear EOC. + +NOTE – For [ITU-T G.992.3], [ITU-T G.992.4] and [ITU-T G.992.5], the data link layer uses the clear EOC messages embedded in the overhead channel as specified in clauses 7.8.2.3, 7.8.2.4 and 9.4.1.8 of [ITU-T G.992.3]. For [ITU-T G.993.2], the data link layer uses the clear EOC messages embedded in the overhead channel as defined in clauses 8.2 and 11.2.3 of [ITU-T G.993.2]. + +The main differences between the ITU-T G.997.1 data link layer and the ITU-T G.992.3/ITU-T G.993.2 clear EOC protocol are: + +- the address field and control field are specified in clause 7.8.2.4 of [ITU-T G.992.3] or clause 8.2.4.1 of [ITU-T G.993.2]; +- the two first bytes of the payload are always 0816 and 0116 to indicate a clear EOC command; +- each clear EOC command is acknowledged by the far end xTU. + +### 6.3.1 Format convention + +The basic format convention used for messages is illustrated in Figure 6-3. Bits are grouped into octets. The bits of each octet are shown horizontally and are numbered from 1 to 8. Octets are displayed vertically and are numbered from 1 to *N*. + +The octets are transmitted in ascending numerical order. + +The frame check sequence (FCS) field spans two octets: Bit 1 of the first octet is the most significant bit (MSB) and bit 8 of the second octet is the least significant bit (LSB) (see Figure 6-4). + +![](90ee16ccc0ad16aeca48087797d7b07f_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +|---|---|---|---|---|---|---|---|----------| +| | | | | | | | | 1 | +| | | | | | | | | 2 | +| | | | | | | | | ... | +| | | | | | | | | N | + +Figure 6-3 – Format convention + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +|-------|---|---|---|---|---|---|----------|-------| +| $2^8$ | | | | | | | $2^{15}$ | 1 | +| $2^0$ | | | | | | | $2^7$ | 2 | + +**Figure 6-4 – FCS mapping convention** + +### 6.3.2 Operations, administration and maintenance frame structure + +The frame structure is as depicted in Figure 6-5. + +| | | +|---------------------|-------------------------------------| +| $7E_{16}$ | Opening flag | +| $FF_{16}$ | Address field | +| $03_{16}$ | Control field | +| Information payload | Max 510 bytes | +| FCS | Frame check sequence (first octet) | +| FCS | Frame check sequence (second octet) | +| $7E_{16}$ | Closing flag | + +**Figure 6-5 – Operations, administration and maintenance frame structure** + +The opening and closing flag sequence shall be the octet $7E_{16}$ . The address and control field of the frame shall be coded as $FF_{16}$ and $03_{16}$ , respectively. + +Transparency of the information payload to the flag sequence and the frame check sequence are described in clause 6.3.3. + +### 6.3.3 Octet transparency + +In this approach, any data that is equal to $7E_{16}$ ( $01111110_2$ ) (flag sequence) or $7D_{16}$ (control escape) shall be escaped as described in the following. + +After frame check sequence (FCS) computation, the transmitter examines the entire frame between the two flag sequences. Any data octets that are equal to the flag sequence ( $7E_{16}$ ) or the control escape ( $7D_{16}$ ) are replaced by a two-octet sequence consisting of the control escape octet followed by the original octet exclusive-ORed with hexadecimal $0x20$ (this is bit 5 complemented, where the bit positions are numbered 76543210). In summary, the following substitutions are made: + +- a data octet of $7E_{16}$ is encoded as two octets $7D_{16}$ , $5E_{16}$ ; +- a data octet of $7D_{16}$ is encoded as two octets $7D_{16}$ , $5D_{16}$ . + +On reception, prior to FCS computation, each control escape octet ( $7D_{16}$ ) is removed, and the subsequent octet is exclusive-ORed with hexadecimal $20_{16}$ (unless the following octet is $7E_{16}$ , which is the flag, and indicates the end of frame, i.e., an abort has occurred). In summary, the subsequent substitutions are made: + +- a sequence of $7D_{16}$ , $5E_{16}$ is replaced by the data octet $7E_{16}$ ; +- a sequence of $7D_{16}$ , $5D_{16}$ is replaced by the data octet $7D_{16}$ ; +- a sequence of $7D_{16}$ , $7E_{16}$ aborts the frame. + +Note that since octet stuffing is used, the data frame is guaranteed to have an integral number of octets. + +### 6.3.4 Frame check sequence + +The FCS field is 16 bits (2 octets) in length. As defined in [b-ISO/IEC 13239], it shall be the one's complement of the sum (modulo 2) of: + +- a) the remainder of $x^k$ ( $x^{15} + x^{14} + x^{13} + x^{12} + x^{11} + x^{10} + x^9 + x^8 + x^7 + x^6 + x^5 + x^4 + x^3 + x^2 + x + 1$ ) divided (modulo 2) by the generator polynomial $x^{16} + x^{12} + x^5 + 1$ , where $k$ is the number of bits in the frame existing between, but not including, the last bit of the final opening flag and the first bit of the FCS, excluding octets inserted for transparency; and +- b) the remainder of the division (modulo 2) by the generator polynomial $x^{16} + x^{12} + x^5 + 1$ , of the product of $x^{16}$ by the content of the frame existing between, but not including, the last bit of the final opening flag and the first bit of the FCS, excluding octets inserted for transparency. + +As a typical implementation at the transmitter, the initial content of the register of the device computing the remainder of the division is preset to all binary 1s and is then modified by division by the generator polynomial (as described in a and b)) on the information field. The one's complement of the resulting remainder is transmitted as the 16-bit FCS. + +As a typical implementation at the receiver, the initial content of the register of the device computing the remainder of the division is preset to all binary 1s. The final remainder, after multiplication by 16 and then division (modulo 2) by the generator polynomial $x^{16} + x^{12} + x^5 + 1$ of the serial incoming protected bits after removal of the transparency octets and the FCS, will be $0001110100001111_2$ ( $x^{15}$ through $x^0$ , respectively) in the absence of transmission errors. + +The FCS is calculated over all bits of the address, control, and information payload fields of the frame. + +The register used to calculate the cyclic redundancy check (CRC) shall be initialized to the value $FFFF_{16}$ , both at the transmitter and the receiver. + +The LSB of the FCS is sent first, followed by the MSB. + +On the receiver a message received without errors results in a CRC calculation of $F0B8_{16}$ . + +### 6.3.5 Invalid frames + +The following conditions result in an invalid frame: + +- frames that are too short (less than 4 octets in between flags, not including transparency octets); +- frames that contain a control escape octet followed immediately by a flag (i.e., $7D_{16}$ , $7E_{16}$ ). +- frames that contain control escape sequences other than $7D_{16}$ , $5E_{16}$ and $7D_{16}$ , $5D_{16}$ . + +Invalid frames shall be discarded. The receiver shall immediately start looking for the beginning flag of a subsequent frame. + +### 6.3.6 Synchronism + +The OAM frame structure transport is octet synchronous. Octet transport and synchronism for this transport is defined in accordance with the transmission convergence (TC) layer. + +### 6.3.7 Time fill + +Inter-frame time fill shall be accomplished by inserting additional flag octets ( $7E_{16}$ ) between the closing and the subsequent opening flag on the EOC transport channel. Inter-octet time fill is not supported. + +## 6.4 The simple network management protocol protocol + +If implemented, SNMP messages shall be used as the message encoding over the HDLC data link channel defined in clause 6.2, for [ITU-T G.992.1] and [ITU-T G.992.2]; or over the clear EOC message embedded in the overhead channel for [ITU-T G.992.3], [ITU-T G.992.4], [ITU-T G.992.5] and [ITU-T G.993.2]. + +### 6.4.1 Simple network management protocol message mapping in HDLC frames + +This clause applies only to Recommendations specifying a bit-oriented clear EOC (e.g., [ITU-T G.992.1] and [ITU-T G.992.2]). + +The SNMP messages are placed directly in HDLC frames together with the protocol identifier (ID) (see Figure 6-6). The protocol ID is two bytes ahead of the SNMP message. The two bytes contain the ethertype SNMP value 814C16 as defined in [b-IETF RFC 1700]. A single HDLC frame is used to transport each SNMP message. + +![Diagram of HDLC frame structure showing the mapping of an SNMP message. The frame consists of an Open flag (7E), a Header (FF 03), an Information payload, two FCS fields, and a Close flag (7E). The Information payload contains a Protocol identifier (81 4C) followed by the SNMP message. The total length of the HDLC frame is ≤ 514 bytes, and the SNMP message length is ≤ 508 bytes. The FCS fields are labeled as CRC.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +| | | | | | | | | | | | | | +|-----------|--------|----|-------------------------------------------------|----|--------------|--|-----|-----|------------|--|--|--| +| | | | HDLC frame ≤ 514 bytes | | | | | | | | | | +| 7E | FF | 03 | Information payload | | | | FCS | FCS | 7E | | | | +| Open flag | Header | | | | | | CRC | | Close flag | | | | +| | | | SNMP message ≤ 508 bytes | | | | | | | | | | +| | | | 81 | 4C | SNMP message | | | | | | | | +| | | | Protocol identifier for SNMP 814C 16 | | | | | | | | | | + +Diagram of HDLC frame structure showing the mapping of an SNMP message. The frame consists of an Open flag (7E), a Header (FF 03), an Information payload, two FCS fields, and a Close flag (7E). The Information payload contains a Protocol identifier (81 4C) followed by the SNMP message. The total length of the HDLC frame is ≤ 514 bytes, and the SNMP message length is ≤ 508 bytes. The FCS fields are labeled as CRC. + +G.997.1(19)\_F6-6 + +**Figure 6-6 – Operations, administration and maintenance communication channel protocol over the U-interface** + +The length of an SNMP message shall be ≤508 bytes. + +Due to the transparency mechanism described in clause 6.3.3, the number of bytes actually transmitted between opening and closing flags may be higher than 514. + +### 6.4.2 Simple network management protocol message mapping in clear embedded operations channel messages + +This clause applies only to Recommendations specifying message-oriented clear EOC messages (e.g., [ITU-T G.992.3], [ITU-T G.992.4], [ITU-T G.992.5] and [ITU-T G.993.2]). + +The SNMP messages are placed directly in the clear EOC messages together with the protocol ID (see Figure 6-7). The protocol ID is two bytes prepended to the SNMP message. The two bytes contain the ethertype SNMP value 814C16 as defined in [b-IETF RFC 1700]. A single HDLC frame is used to transport each SNMP message. + +![Diagram of the Operations, administration and maintenance communication channel protocol over the U-interface. The diagram shows a 'Clear EOC message' frame structure. The frame starts with an 'Open flag' (7E), followed by a 'Header' consisting of 'Ad field', 'Cntrl field', and 'EOC Command indicator' (01). The 'Information payload' contains an 'SNMP message'. The 'SNMP message' is further detailed with 'Protocol identifier for SNMP 814C'H' (81, 4C) and the 'SNMP message' itself. The frame ends with 'FCS', 'FCS', and a 'Close flag' (7E). Labels 'CRC' and 'EOC Command indicator' are also present.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +G.997.1(19)\_F6-7 + +Diagram of the Operations, administration and maintenance communication channel protocol over the U-interface. The diagram shows a 'Clear EOC message' frame structure. The frame starts with an 'Open flag' (7E), followed by a 'Header' consisting of 'Ad field', 'Cntrl field', and 'EOC Command indicator' (01). The 'Information payload' contains an 'SNMP message'. The 'SNMP message' is further detailed with 'Protocol identifier for SNMP 814C'H' (81, 4C) and the 'SNMP message' itself. The frame ends with 'FCS', 'FCS', and a 'Close flag' (7E). Labels 'CRC' and 'EOC Command indicator' are also present. + +**Figure 6-7 – Operations, administration and maintenance communication channel protocol over the U-interface** + +The length of an SNMP message shall be $\leq 508$ bytes. + +Due to the transparency mechanism described in clause 6.3.3, the number of bytes actually transmitted between opening and closing flags may be greater than 516. + +### 6.4.3 Protocol based on simple network management protocol + +The SNMP protocol as specified in [IETF RFC 1157] consists of four types of operation, which are used to manipulate management information. These are: + +- Get used to retrieve specific management information. +- Get-Next used to retrieve, via traversal of the MIB, management information. +- Set used to alter management information. +- Trap used to report extraordinary events. + +The four operations are implemented using five types of protocol data unit (PDU): + +- GetRequest-PDU used to request a Get operation. +- GetNextRequest-PDU used to request a Get-Next operation. +- GetResponse-PDU used to respond to a Get, Get-Next, or Set operation. +- SetRequest-PDU used to request a Set operation. +- Trap-PDU used to report a Trap operation. + +If implemented, SNMP messages shall be used according to the requirements specified in clauses 6.4.3.1 to 6.4.3.5. + +#### 6.4.3.1 Use of embedded operations channel + +The ADSL or VDSL2 OAM channel will be used to send HDLC-encapsulated SNMP messages between ADSL management entities (AMEs) or VDSL2 management entities (VMEs) on both sides of the line. An AME or VME residing in the xTU-R and xTU-C will send and interpret these SNMP messages. This ADSL or VDSL2 OAM channel is used for requests, responses and traps, differentiated according to the SNMP PDU type. + +#### 6.4.3.2 Message format + +The message format specified in [ITU-T G.992.1] shall be used, i.e., SNMP version 1. + +All SNMP messages shall use the community name "ADSL", i.e., the OCTET STRING value: "4144534C16". This string shall be used for all Recommendations covered by this Recommendation. + +In all SNMP traps, the agent-addr field (which has syntax NetworkAddress), shall always have the IpAddress value: 0.0.0.0. + +In all SNMP traps, the time-stamp field in the Trap-PDU shall contain the value of an AME or VME MIB object at the time of trap generation. + +In any standard SNMP trap, the enterprise field in the Trap-PDU shall contain the value of the agent's sysObjectID MIB object (sysObjectID is defined in the system group of MIB-II). + +#### **6.4.3.3 Message sizes** + +All ADSL and VDSL2 OAM implementations shall be able to support SNMP messages of size up to, and including, 508 octets. + +#### **6.4.3.4 Message response time** + +Response time refers to the time elapsed from the submission of an SNMP message (e.g., GetRequest, GetNextRequest or SetRequest message) by an AME or VME across an ADSL or VDSL2 interface to the receipt of the corresponding SNMP message (e.g., GetResponse message) from the adjacent AME or VME. An SNMP GetRequest, GetNextRequest or SetRequest message is specified in this context as a request concerning a single object. + +The AME and VME shall support maximum response times of 1 s for 95% of all SNMP GetRequests, GetNextRequests or SetRequests containing a single object received from an adjacent AME or VME independent of the ADSL or VDSL2 interface's physical line rate. + +#### **6.4.3.5 Object value data correctness** + +Data correctness refers to the maximum time elapsed since an object value in the ADSL or VDSL2 interface MIB was known to be current. The following specifies the requirements on the data correctness of the ADSL or VDSL2 OAM objects and the event notifications. + +The ADSL and VDSL2 interface MIB objects shall have a maximum data correctness of 30 s. + +The AME and VME shall support event notifications (i.e., SNMP traps) for generic SNMP events within 2 s of the event detection by the AME. + +# **8 Management information base elements** + +The MIB contains six types of information: + +- fault monitoring – failures (alarm indications); +- fault monitoring – threshold crossing (alert messages); +- PM parameters (counters); +- configuration parameters; +- inventory parameters; +- test, diagnostic and status parameters. + +Figure 7-1 shows the in-service PM process. The primitives are specified in the physical layer of the ITU-T G.992.x-series of ITU-T Recommendations and [ITU-T G.993.2]. + +![Figure 7-1 – In-service performance monitoring process flowchart. The diagram shows the flow from Primitives (Defect, Anomaly) to Storage (Current, Previous, Recent) and Thresholding, leading to outputs like Alarm indications, Alert messages, and Current data. A vertical double-headed arrow on the left indicates the 'Scope of ITU-T G.997.1'.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +``` + +graph TD + subgraph Primitives + Defect[Defect] + Anomaly[Anomaly] + end + subgraph Storage + Current[Current] + Previous[Previous] + Recent[Recent] + end + Defect --> Anomaly + Defect --> Failure[Failure] + Anomaly --> GenParams[Generate parameters] + Failure --> Thresholding[Thresholding] + GenParams --> Current + Current --> Previous + Previous --> Recent + Thresholding --> Current + Failure --> Alarm[Alarm indications] + Thresholding --> Alert[Alert messages] + Current --> Data[Current data] + Recent --> Historic[Historic data] + Historic --> G997_1_19_F7_1[G.997.1(19)_F7-1] + Scope[Scope of ITU-T G.997.1] + style Defect fill:none,stroke:none + style Anomaly fill:none,stroke:none + style Failure fill:none,stroke:none + style GenParams fill:none,stroke:none + style Current fill:none,stroke:none + style Previous fill:none,stroke:none + style Recent fill:none,stroke:none + style Thresholding fill:none,stroke:none + style Alarm fill:none,stroke:none + style Alert fill:none,stroke:none + style Data fill:none,stroke:none + style Historic fill:none,stroke:none + style G997_1_19_F7_1 fill:none,stroke:none + style Scope fill:none,stroke:none + +``` + +Figure 7-1 – In-service performance monitoring process flowchart. The diagram shows the flow from Primitives (Defect, Anomaly) to Storage (Current, Previous, Recent) and Thresholding, leading to outputs like Alarm indications, Alert messages, and Current data. A vertical double-headed arrow on the left indicates the 'Scope of ITU-T G.997.1'. + +**Figure 7-1 – In-service performance monitoring process** + +As an AN can handle a large number of xTU-Cs (e.g., hundreds or perhaps thousands of ADSL or VDSL2 lines), provisioning every parameter on every xTU-C may become burdensome. In response, two modes have been created to define ADSL and VDSL2 equipment configuration data profiles, as well as a mechanism to associate these profiles to the equipment. Profile tables may be implemented in one of two ways, but not simultaneously. + +- MODE-I: Dynamic Profiles – profiles used by one or multiple ADSL/VDSL2 lines. + +Implementations using this mode will enable the operator of the system to dynamically create and delete profiles as needed. One or more ADSL/VDSL2 lines may be configured to share parameters of a single profile (e.g., `adslLineConfProfileName = 'silver'`) by setting its `adslLineConfProfile` object to the index value of this profile. If a change is made to the profile, all lines that refer to it will be reconfigured to the changed parameters. Before a profile can be deleted or taken out of service, it shall be first unreferenced from all associated lines. + +- MODE-II: Static profiles – one profile per ADSL/VDSL2 physical line. + +Implementations with this mode will automatically create a profile one-for-one with each ADSL/VDSL2 line. The name of this profile is a system generated read-only object whose value is equivalent to the index of the line. The management agent in the AN will not allow the operator of the system to create/delete profiles in this mode. + +NOTE 1 – For more details on the use of profiles, refer to [b-IETF RFC 2662]. + +NOTE 2 – The 'data profiles' discussed in this clause are not the 'profiles' discussed in clause 6 of [ITU-T G.993.2]. This clause discusses the use of a 'profile' to simplify the configuration of an xDSL transceiver in the field. Clause 6 of [ITU-T G.993.2] is a discussion of a technique to specify the native capabilities (e.g., the particular subset of [ITU-T G.993.2]) supported by a particular VDSL2 transceiver. + +At the Q-interface, a line is configured by linking the following information to the line (see Figure 7-2): + +- one line configuration profile (see Table 7-14) for the line; +- one channel configuration profile (see Table 7-16) for each downstream and each upstream bearer channel; +- one data path configuration profile (see Table 7-18) for each downstream and each upstream bearer channel. + +![Figure 7-2: Overview of the MIB elements provided for each line. The diagram shows the relationship between Configuration data and Operational data. Configuration data includes Line config. profile, Channel config. profile, and Data path config. profile. Operational data is divided into four sections: CONFIGURATION, FAULT MONITORING, PERFORMANCE MONITORING, and INVENTORY. Arrows indicate that configuration profiles are instantiated into operational data elements.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +The diagram illustrates the relationship between Configuration data and Operational data for each line. On the left, under 'Configuration data', there are three boxes: 'Line config. profile', 'Channel config. profile', and 'Data path config. profile'. The latter two are shown as stacked boxes. Arrows point from each of these configuration boxes to the 'CONFIGURATION' section of the 'Operational data' on the right. The 'Operational data' is organized into four dashed boxes: 'CONFIGURATION', 'FAULT MONITORING', 'PERFORMANCE MONITORING', and 'INVENTORY'. The 'CONFIGURATION' section contains 'Line failures', 'Line threshold crossing', 'Data path failures', 'Channel threshold crossing', and 'Data path threshold crossing'. The latter three are shown as stacked boxes. The 'FAULT MONITORING' section contains 'Line PM counters', 'Channel PM counters', 'Data path PM counters', 'Line test, diag. and status', and 'Channel test, diag. and status'. The latter three are shown as stacked boxes. The 'PERFORMANCE MONITORING' section contains 'Line inventory'. The 'INVENTORY' section is empty. + +Channel and data path configuration profile is instantiated once per bearer channel in any direction. The same number of instances is used to report operational data. + +G.997.1(19)\_F7-2 + +Figure 7-2: Overview of the MIB elements provided for each line. The diagram shows the relationship between Configuration data and Operational data. Configuration data includes Line config. profile, Channel config. profile, and Data path config. profile. Operational data is divided into four sections: CONFIGURATION, FAULT MONITORING, PERFORMANCE MONITORING, and INVENTORY. Arrows indicate that configuration profiles are instantiated into operational data elements. + +**Figure 7-2 – Overview of the MIB elements provided for each line** + +Some or all of the configuration parameters contained in the line, channel and data path configuration profiles linked to the line may be written or read, depending on the interface under consideration: + +Q-interface: management interface towards the xTU-C, from the network side perspective; + +U-C-interface: management interface towards the xTU-C, from the xTU-R perspective; + +U-R-interface: management interface towards the xTU-R, from the xTU-C perspective; + +T/S-interface: management interface towards the xTU-R, from the premises side perspective (interface between ADSL network termination and customer installation or home network). + +In clause 7.6, a detailed list is given of the management elements applying to each of these interfaces, with indications whether they are mandatory or optional and whether they can be read, written or both. + +As an AN can handle a large number of lines (e.g., hundreds or perhaps thousands of ADSL or VDSL2 lines), maintaining the PM and the test, diagnostic and status information (see Figure 7-2) for every line may become burdensome. Although access to all mandatory management elements shall be supported at all times for all ports on the AN at the Q-interface (see Figure 5-1), the elements may not be maintained within the ME of the AN simultaneously for all lines at all times. Although reasonable performance shall be provided at the Q-interface for access to the management elements of any line, this Recommendation does not specify specific performance requirements at this interface. + +## 7.1 Failures + +Any failure specified in this clause shall be conveyed to the NMS by the xTU-C (over the Q-interface) and may be conveyed by the xTU-R over the T/S-interface after it is detected. + +The near-end failure detections shall be provided at the xTU-C and shall be provided at the xTU-R. + +The far-end failure detections shall be provided at the xTU-C (xTU-R is at the far-end), and may be provided at the xTU-R (xTU-C is at the far-end). + +### 7.1.1 Line failures + +#### 7.1.1.1 Line near-end failures + +##### 7.1.1.1.1 Loss of signal failure + +An LOS failure is declared after $2.5 \pm 0.5$ s of contiguous LOS defect or if an LOS defect is present when the criteria for loss of frame (LOF) failure declaration have been met (see LOF specification in clause 7.1.1.1.2). An LOS failure is cleared after $10 \pm 0.5$ s of no LOS defect. + +##### 7.1.1.1.2 Loss of frame failure + +An LOF failure is declared after $2.5 \pm 0.5$ s of contiguous severely errored frame (SEF) defect, except when an LOS defect or failure is present (see LOS specifica in clause 7.1.1.1.1). A LOF failure is cleared when an LOS failure is declared or after $10 \pm 0.5$ s of no SEF defect. + +##### 7.1.1.1.3 Loss of power failure + +A loss of power (LPR) failure is declared after $2.5 \pm 0.5$ s of contiguous near-end LPR primitive presence. An LPR failure is cleared after $10 \pm 0.5$ s of no near-end LPR primitive presence. + +##### 7.1.1.1.4 Loss of margin failure + +An LOM failure is declared when a re-initialization is triggered by a persistent near-end *lom* defect, except when an LOS or LOF defect or failure is present (see LOS and LOF specifications in clauses 7.1.1.1.1 and 7.1.1.1.2). An LOM failure is cleared when an LOS or LOF failure is declared or after $10 \pm 0.5$ s of no LOM defect. + +#### 7.1.1.2 Line far-end failures + +##### 7.1.1.2.1 Far-end loss of signal failure + +A far-end loss of signal (LOS-FE) failure is declared after $2.5 \pm 0.5$ s of contiguous far-end LOS defects or if a far-end LOS defect is present when the criteria for LOF failure declaration have been met (see LOF specification in clause 7.1.1.2.2). A far-end LOS failure is cleared after $10 \pm 0.5$ s of no far-end LOS defect. + +##### 7.1.1.2.2 Far-end loss of frame failure + +A far-end loss of frame (LOF-FE) failure is declared after $2.5 \pm 0.5$ s of contiguous remote defect indication (RDI) defects, except when a far-end LOS defect or failure is present (see LOS specification in clause 7.1.1.2.1). A far-end LOF failure is cleared when a far-end LOS failure is declared or after $10 \pm 0.5$ s of no RDI defect. + +##### 7.1.1.2.3 Far-end loss of power failure + +A far-end loss of power (LPR-FE) failure is declared after the occurrence of an LPR-FE primitive followed by $2.5 \pm 0.5$ s of contiguous near-end LOS defects. An LPR-FE failure is cleared after $10 \pm 0.5$ s of no near-end LOS defect. + +##### **7.1.1.2.4 Loss of margin failure** + +A far-end loss of margin (LOM-FE) failure is declared when a re-initialization is triggered by a persistent far-end *lom* defect, except when an LOS-FE or LOF-FE defect or failure is present (see LOS and LOF specifications in clauses 7.1.1.2.1 and 7.1.1.2.2). A far-end LOM failure is cleared when a far-end LOS or LOF failure is declared, or after $10 \pm 0.5$ s of no far-end LOM defect. + +#### **7.1.1.3 Line initialization failure** + +If the line is forced to the L0 state (or into loop diagnostic mode) and an attempt to reach the L0 state (or to successfully complete the loop diagnostic procedures) fails (after a vendor discretionary number of retries or within a vendor discretionary timeout), then an initialization failure occurs. An initialization failure cause and last successful transmitted state are given by the line initialization (LINIT) failure (see clause 7.5.1.6). A LINIT failure shall be conveyed to the NMS by the xTU-C (over the Q-interface) and should be conveyed to the NMS by the xTU-R (over the T/S-interface) after it is detected. + +### **7.1.2 Channel failures** + +No channel failures are specified. + +### **7.1.3 Synchronous transfer mode data path failures** + +Synchronous transfer mode (STM) data path failures are for further study. + +### **7.1.4 Asynchronous transfer mode data path failures** + +#### **7.1.4.1 Asynchronous transfer mode data path near-end failures** + +##### **7.1.4.1.1 No cell delineation failure** + +A no cell delineation (NCD) failure is declared when an NCD anomaly persists for more than $2.5 \pm 0.5$ s after the start of showtime. An NCD failure terminates when no NCD anomaly is present for more than $10 \pm 0.5$ s. + +##### **7.1.4.1.2 Loss of cell delineation failure** + +A loss of cell delineation (LCD) failure is declared when an LCD defect persists for more than $2.5 \pm 0.5$ s. An LCD failure terminates when no LCD defect is present for more than $10 \pm 0.5$ s. + +#### **7.1.4.2 Asynchronous transfer mode data path far-end failures** + +##### **7.1.4.2.1 Far-end no cell delineation failure** + +A far-end no cell delineation (NCD-FE) failure is declared when an NCD-FE anomaly persists for more than $2.5 \pm 0.5$ s after the start of showtime. An NCD-FE failure terminates when no NCD-FE anomaly is present for more than $10 \pm 0.5$ s. + +##### **7.1.4.2.2 Far-end loss of cell delineation failure** + +A far-end loss of cell delineation (LCD-FE) failure is declared when an LCD-FE defect persists for more than $2.5 \pm 0.5$ s. An LCD-FE failure terminates when no LCD-FE defect is present for more than $10 \pm 0.5$ s. + +### **7.1.5 Packet transfer mode data path failures** + +#### **7.1.5.1 Packet transfer mode data path near-end failures** + +##### **7.1.5.1.1 Out of sync failure** + +An out of sync (OOS) failure is declared when an *oos-n* anomaly persists for more than $2.5 \pm 0.5$ s. An OOS failure terminates when no *oos-n* anomaly is present for more than $10 \pm 0.5$ s. + +#### 7.1.5.2 Packet transfer mode data path far-end failures + +##### 7.1.5.2.1 Far-end out of sync failure + +A far-end out of sync (OOS-FE) failure is declared when an oos-*f* anomaly persists for more than $2.5 \pm 0.5$ s. An OOS-FE failure terminates when no oos-*f* anomaly is present for more than $10 \pm 0.5$ s. + +## 7.2 Performance monitoring functions + +Near-end PM functions shall be provided at the xTU-C and at the xTU-R. Far-end PM functions shall be provided at the xTU-C (xTU-R is at the far-end) and are optional at the xTU-R (xTU-C is at the far-end). + +If the line is forced to the L0 state (see clause 7.3.1.1.3), then PM counters shall be active, irrespective of the actual power management state of the line (see clause 7.5.1.5). If the line is forced to the L3 state, then all PM counters shall be frozen, including the unavailable second (UAS) counter. + +### 7.2.1 Line performance monitoring parameters + +This clause defines a set of line PM parameters. Support of the performance parameters in an NE is indicated as mandatory (M) or optional (O) in Table 7-1. + +#### 7.2.1.1 Near-end line performance monitoring parameters + +##### 7.2.1.1.1 Forward error correction second-line + +The forward error correction second-line (FECS-L) parameter is a count of 1 s intervals with one or more forward error correction (FEC) anomalies summed over all received bearer channels. + +##### 7.2.1.1.2 Errored second-line + +The errored second-line (ES-L) parameter is a count of 1 s intervals with one or more CRC-8 anomalies summed over all received bearer channels, or one or more LOS defects, or one or more SEF defects, or one or more LPR defects. + +##### 7.2.1.1.3 Severely errored second-line + +The severely errored second-line (SES-L) parameter is a count of severely errored seconds (SESs). An SES is declared if, during a 1 s interval, there are 18 or more CRC-8 anomalies in one or more of the received bearer channels, or one or more LOS defects, or one or more SEF defects, or one or more LPR defects. If [ITU-T G.998.4] is supported and retransmission is enabled in the near-end received direction, a SES is also declared if, during a 1 s interval, there is one or more severe loss of error-free throughput (*seftr*) defect in the near-end received direction. + +If the relevant Recommendation (e.g., [ITU-T G.992.3], [ITU-T G.992.5] and [ITU-T G.993.2]) supports 1 s normalized CRC-8 anomaly counter increment, the 1 s counter used to declare SES shall increment with this value instead of incrementing by one for each CRC-8 anomaly. + +If a common CRC is applied over multiple bearer channels, then each related CRC-8 anomaly shall be counted only once for the whole set of bearer channels over which the CRC is applied. + +##### 7.2.1.1.4 LOS second-line + +The LOS second-line (LOSS-L) parameter is a count of 1 s intervals containing one or more LOS defects. + +##### 7.2.1.1.5 Unavailable second-line + +The unavailable second-line (UAS-L) parameter is a count of 1 s intervals for which the xDSL line is unavailable. + +If re-initialization policy (RIPOLICY) is not supported or is not defined for the mode used, or the actual value of RIPOLICY equals 0, the xDSL line becomes unavailable at the onset of 10 contiguous SES-Ls. These 10 SES-Ls shall be included in unavailable time. Once unavailable, the xDSL line becomes available at the onset of 10 contiguous seconds with no SES-Ls. These 10 s with no SES-Ls shall be excluded from unavailable time. + +If the actual value of RIPOLICY equals 1, the xDSL line becomes unavailable at the onset of REINIT\_TIME\_THRESHOLD contiguous SES-Ls. These REINIT\_TIME\_THRESHOLD SES-Ls shall be included in unavailable time. + +Independent of the RIPOLICY, the xDSL line becomes also unavailable when the near-end receiver stops processing showtime symbols, in order to prepare for re-initialization. All contiguous SES-Ls until this moment shall be included in the unavailable time. After initialization or re-initialization, the xDSL line becomes available immediately at the start of showtime. + +Some parameter counts are inhibited during unavailability – see clause 7.2.7.13. + +##### 7.2.1.1.6 "leftr" defects seconds counter + +If retransmission is used in a given transmit direction, this parameter is a count of the seconds with a near-end "leftr" defect present (see clause 11.4.1 of [ITU-T G.998.4] for the specification of this counter). + +The near-end counter is only defined in upstream. + +The ME shall generate a 15 min and 24 h performance history. + +##### 7.2.1.1.7 Error-free bits counter + +If retransmission is used in a given transmit direction, this parameter is a count of the number of error-free bits passed over the $\beta_1$ reference point, divided by $2^{16}$ . If retransmission is not used in a given transmit direction and if the "*Extended rate statistics*" option is supported, this counter is the accumulated NDR, divided by $2^{16}$ (see clause 11.4.2 of [ITU-T G.998.4] for the specification of this counter). + +NOTE – An error-free bits counter and UAS can be used to compute the mean EFTR or the mean NDR. + +The near-end counter is only defined in upstream. + +The ME shall generate a 15 min and 24 h performance history. + +NOTE – When retransmission is not used, the bits are not guaranteed error free. + +##### 7.2.1.1.8 Minimum error-free throughput + +If retransmission is used in a given transmit direction, the minimum error-free throughput (MINEFTR) parameter reports the minimum of the EFTR observed over the 15 min or 24 h accumulation period. If retransmission is not used in a given transmit direction and if the "*Extended rate statistics*" option is supported, this parameter reports the minimum of NDR observed over the 15 min or 24 h accumulation period (see clause 11.4.3 of [ITU-T G.998.4] for the specification of this parameter). + +The value is reported in bits per second. + +The near-end value is only defined in upstream. + +The ME shall generate a 15 min and 24 h performance history. + +The ME shall read the ITU-T G.998.4 EFTR\_min (at least) every 15 min to determine the minimum EFTR or NDR over the 15 min and 24 h intervals. + +NOTE – When retransmission is not used, the throughput is not guaranteed error free. + +##### **7.2.1.1.9 Maximum error-free throughput** + +The maximum error-free throughput (MAXEFTR) parameter shall be reported if "Extended Rate Statistics" option is supported. If retransmission is used in a given transmit direction, this MAXEFTR parameter reports the maximum of the EFTR observed over the 15 min or 24 h accumulation period; otherwise, this parameter reports the maximum of NDR observed over the 15 min or 24 h accumulation period. (See clause 11.4.4 of [ITU-T G.998.4] for the definition of this parameter.) + +The value is reported in bits per second. + +The near-end value is only defined in upstream. + +The ME shall generate a 15 min and 24 h performance history. + +The ME shall read the ITU-T G.998.4 EFTR\_max (at least) every 15 min to determine the maximum EFTR or NDR over the 15 min and 24 h intervals. + +NOTE – When retransmission is not used, the throughput is not guaranteed error free. + +#### **7.2.1.2 Far-end line performance monitoring parameters** + +##### **7.2.1.2.1 Forward error correction second-Line far-end** + +The forward error correction second-line far-end (FECS-LFE) parameter is a count of 1 s intervals with one or more far-end forward error correction (FFEC) anomalies summed over all transmitted bearer channels. + +##### **7.2.1.2.2 Errored second-line far-end** + +The errored second-line far-end (ES-LFE) parameter is a count of 1 s intervals with one or more far-end block error (FEBE) anomalies summed over all transmitted bearer channels, or one or more LOS-FE defects, or one or more RDI defects, or one or more LPR-FE defects. + +##### **7.2.1.2.3 Severely errored second-line far-end** + +The severely errored second-line far-end (SES-LFE) parameter is a count of SESs. An SES is declared if, during a 1 s interval, there are 18 or more FEBE anomalies in one or more of the transmitted bearer channels, or one or more far-end LOS defects, or one or more RDI defects, or one or more LPR-FE defects. If [ITU-T G.998.4] is supported and retransmission is enabled in the far-end received direction, an SES-LFE is also declared if, during a 1 s interval, there is one or more severe loss of error-free throughput (*seftr*) defect in the far-end received direction. + +If the relevant Recommendation (e.g., [ITU-T G.992.3], [ITU-T G.992.5] or [ITU-T G.993.2]) supports 1 s normalized CRC-8 anomaly counter increment, the 1 s counter used to declare SES shall increment with this value instead of incrementing by one for each FEBE anomaly. + +If a CRC is applied over multiple bearer channels, then each related FEBE anomaly shall be counted only once for the whole set of related bearer channels. + +##### **7.2.1.2.4 LOS second-line far-end** + +The LOS second-line far-end (LOSS-LFE) parameter is a count of 1 s intervals containing one or more far-end LOS defects. + +##### **7.2.1.2.5 Unavailable seconds-line far-end** + +The unavailable seconds-line far-end (UAS-LFE) parameter is a count of 1 s intervals for which the far-end xDSL line is unavailable. + +If the actual value of RIPOLICY equals 0, the far-end xDSL line becomes unavailable at the onset of 10 contiguous SES-LFEs. These 10 SES-LFEs shall be included in unavailable time. Once unavailable, the far-end xDSL line becomes available at the onset of 10 contiguous seconds with no SES-LFEs. These 10 s with no SES-LFEs shall be excluded from unavailable time. + +If the actual value of RIPOLICY equals 1, the xDSL line becomes unavailable at the onset of REINIT\_TIME\_THRESHOLD contiguous SES-LFEs. These REINIT\_TIME\_THRESHOLD SES-LFEs shall be included in unavailable time. + +Independent of the RIPOLICY, the xDSL line becomes also unavailable when the near-end receiver stops processing showtime symbols, in order to prepare for re-initialization. All contiguous SES-LFEs until this moment shall be included in the unavailable time. After initialization or re-initialization, the xDSL line becomes available immediately at the start of showtime. + +Some parameter counts are inhibited during unavailability – see clause 7.2.7.13. + +##### 7.2.1.2.6 "leftr" defects seconds counter + +If retransmission is used in a given transmit direction, this parameter is a count of the seconds with a near-end "leftr" defect present (see clause 11.4.1 of [ITU-T G.998.4] for the specification of this counter). + +The far-end counter is only defined in downstream. + +The ME shall generate a 15 min and 24 h performance history. + +##### 7.2.1.2.7 Error-free bits counter + +If retransmission is used in a given transmit direction, this parameter is a count of the number of error-free bits passed over the $\beta_1$ reference point, divided by $2^{16}$ . If retransmission is not used in a given transmit direction and if "*Extended rate statistics*" option is supported, this counter is the accumulated NDR, divided by $2^{16}$ (see clause 11.4.2 of [ITU-T G.998.4] for the specification of this counter). + +NOTE – Error-free bits counter and UAS can be used to compute the mean EFTR or the mean NDR. + +The far-end counter is only defined in downstream. + +The ME shall generate a 15 min and 24 h performance history. + +NOTE – When retransmission is not used the bits are not guaranteed error free. + +##### 7.2.1.2.8 Minimum error-free throughput + +If retransmission is used in a given transmit direction, the MINEFTR parameter reports the minimum of the EFTR observed over the 15 min or 24 h accumulation period. If retransmission is not used in a given transmit direction and if "*Extended Rate Statistics*" option is supported, this parameter reports the minimum of NDR observed over the 15 min or 24 h accumulation period (see clause 11.4.3 of [ITU-T G.998.4] for the definition of this parameter). + +The value is reported in bits per second. + +The far-end value is only defined in downstream. + +The ME shall generate a 15 min and 24 h performance history. + +The ME shall read the ITU-T G.998.4 EFTR\_min (at least) every 15 min to determine the minimum EFTR or NDR over the 15 min and 24 h intervals. + +NOTE – When retransmission is not used, the throughput is not guaranteed error free. + +##### 7.2.1.1.9 Maximum error-free throughput + +The MAXEFTR parameter shall be reported if the extended rate statistics option is supported. If retransmission is used in a given transmit direction, the MAXEFTR parameter reports the maximum of the EFTR observed over the 15 min or 24 h accumulation period; otherwise, this parameter reports the maximum of NDR observed over the 15 min or 24 h accumulation period. (See clause 11.4.4 of [ITU-T G.998.4] for specification of this parameter.) + +The value is reported in bits per second. + +The far-end value is only defined in downstream. + +The ME shall generate a 15 min and 24 h performance history. + +The ME shall read the ITU-T G.998.4 EFTR\_max (at least) every 15 min to determine the maximum EFTR or NDR over the 15 min and 24 h intervals. + +NOTE – When retransmission is not used, the throughput is not guaranteed error free. + +#### **7.2.1.3 Line initialization performance monitoring parameters** + +##### **7.2.1.3.1 Full initialization count** + +This parameter is a count of the total number of full initializations attempted on the line (successful and failed) during the accumulation period. Parameter procedures shall be as specified in clause 7.2.7. + +##### **7.2.1.3.2 Failed full initialization count** + +This performance parameter is a count of the total number of failed full initializations during the accumulation period. A failed full initialization is when showtime is not reached at the end of the full initialization procedure. + +Parameter procedures shall be as specified in clause 7.2.7. + +##### **7.2.1.3.3 Short initialization count** + +This parameter is a count of the total number of fast retrains or short initializations attempted on the line (successful and failed) during the accumulation period. Parameter procedures shall be as specified in clause 7.2.7. + +Fast retrain is defined in [ITU-T G.992.2]. + +Short initialization is defined in [ITU-T G.992.3] and [ITU-T G.992.4]. + +##### **7.2.1.3.4 Failed short initialization count** + +This performance parameter is a count of the total number of failed fast retrains or short initializations during the accumulation period. A failed fast retrain or short initialization is when showtime is not reached at the end of the fast retrain or short initialization procedure, e.g., when: + +- a CRC error is detected; +- a time-out occurs; +- a fast retrain profile is unknown. + +Parameter procedures shall be as specified in clause 7.2.7. + +#### **7.2.1.4 Near-end impulse noise performance monitoring parameters** + +##### **7.2.1.4.1 Impulse noise monitoring INPEQ histogram 1..17** + +The impulse noise monitoring (INM) INPEQ histogram 1..17 (INMINPEQ1..17-L) parameter is a count of the near-end INMAINPEQi anomalies occurring on the line during the accumulation period. This parameter is subject to inhibition – see clause 7.2.7.13. + +##### **7.2.1.4.2 Impulse noise monitoring total measurement** + +The INM total measurement (INMME-L) parameter is a count of the near-end INMAME anomalies occurring on the line during the accumulation period. This parameter is subject to inhibition – see clause 7.2.7.13. + +##### **7.2.1.4.3 Impulse noise monitoring IAT histogram 0..7** + +The INM IAT histogram 0..7 (INMIAT0..7-L) parameter is a count of the near-end INMAIATi anomalies occurring on the line during the accumulation period. This parameter is subject to inhibition – see clause 7.2.7.13. + +#### **7.2.1.5 Far-end impulse noise performance monitoring parameters** + +##### **7.2.1.5.1 Impulse noise monitoring INPEQ histogram 1..17** + +The INM INPEQ histogram 1..17 (INMINPEQ1..17-LFE) parameter is a count of the far-end INMAINPEQi anomalies occurring on the line during the accumulation period. This parameter is subject to inhibition – see clause 7.2.7.13. + +##### **7.2.1.5.2 Impulse noise monitoring total measurement** + +The INM total measurement (INMME-LFE) parameter is a count of the far-end INMAME anomalies occurring on the line during the accumulation period. This parameter is subject to inhibition – see clause 7.2.7.13. + +##### **7.2.1.5.3 Impulse noise monitoring IAT histogram 0..7** + +The INM IAT histogram 0..7 (INMIAT0..7-LFE) parameter is a count of the far-end INMAIATi anomalies occurring on the line during the accumulation period. This parameter is subject to inhibition – see clause 7.2.7.13. + +#### **7.2.1.6 Near-end initiated on-line reconfiguration performance monitoring parameters** + +##### **7.2.1.6.1 Near-end successful save our showtime count** + +The near-end successful save our showtime (SOS) count (SOS-SUCCESS-NE) parameter is a count of the total number of successful SOS procedures initiated by the near-end xTU on the line during the accumulation period. Parameter procedures shall be as specified in clause 7.2.7. + +Successful SOS is defined in clause 11.3.1.5 of [ITU-T G.993.2]. + +##### **7.2.1.6.2 Near-end successful seamless rate adaptation count** + +The near-end successful seamless rate adaptation (SRA) count (SRA-SUCCESS-NE) parameter is a count of the total number of successful SRA procedures initiated by the near-end xTU on the line during the accumulation period. Parameter procedures shall be as specified in clause 7.2.7. + +Successful SRA is defined in clause 11.3.1.5 of [ITU-T G.993.2]. + +#### **7.2.1.7 Far-end initiated on-line reconfiguration performance monitoring parameters** + +##### **7.2.1.7.1 Far-end successful save our showtime count** + +The far-end successful SOS count (SOS-SUCCESS-FE) parameter is a count of the total number of successful SOS procedures initiated by the far-end xTU on the line during the accumulation period. Parameter procedures shall be as specified in clause 7.2.7. + +Successful SOS is defined in clause 11.3.1.6 of [ITU-T G.993.2]. + +##### **7.2.1.7.2 Far-end successful seamless rate adaptation count** + +The far-end successful SRA count (SRA-SUCCESS-FE) parameter is a count of the total number of successful SRA procedures initiated by the far-end xTU on the line during the accumulation period. Parameter procedures shall be as specified in clause 7.2.7. + +Successful SRA is specified in clause 11.3.1.6 of [ITU-T G.993.2]. + +#### 7.2.1.8 Short interruption performance monitoring parameters + +##### 7.2.1.8.1 Loss of power interruption count + +The loss of power interruption count (LPR\_INTRPT) parameter is a count of the number of *lpr\_intrpt* anomalies occurring during the accumulation period. Those anomalies are specified in clause 11.3.1.1 of [ITU-T G.993.2]. Only the counters on the current and previous 24 h intervals shall be supported. A special value indicates that this counter is not active on the line. Threshold reports (TRs) for this counter are not specified. + +##### 7.2.1.8.2 Host-reinit interruption count + +The host-reinit interruption count (HRI\_INTRPT) parameter is a count of the number of *hri\_intrpt* anomalies occurring during the accumulation period. Those anomalies are specified in clause 11.3.1.1 of [ITU-T G.993.2]. Only the counters on the current and previous 24 h intervals shall be supported. A special value indicates that this counter is not active on the line. TRs for this counter are not specified. + +##### 7.2.1.8.3 Spontaneous interruption count + +The spontaneous interruption count (SPONT\_INTRPT) parameter is a count of the number of *spont\_intrpt* anomalies occurring during the accumulation period. Those defects are specified in clause 11.3.1.1 of [ITU-T G.993.2]. Only the counters on the current and previous 24 h intervals shall be supported. A special value indicates that this counter is not active on the line. TRs are specified for the 24 h interval counter only. + +### 7.2.2 Channel performance monitoring parameters + +This clause specifies a set of channel PM parameters. Support of the performance parameters in an NE is indicated as mandatory (M) or optional (O) in Table 7-2. + +#### 7.2.2.1 Channel near-end performance monitoring parameters + +##### 7.2.2.1.1 Code violation-channel + +The code violation-channel (CV-C) parameter is a count of CRC-8 anomalies (the number of incorrect CRCs) occurring in the bearer channel during the accumulation period. This parameter is subject to inhibiting – see clause 7.2.7.13. + +If the CRC is applied over multiple bearer channels, then each related CRC-8 anomaly shall increment each of the counters related to the individual bearer channels. + +##### 7.2.2.1.2 Forward error correction-channel + +The forward error correction-channel (FEC-C) parameter is a count of FEC anomalies (the number of corrected code words) occurring in the bearer channel during the accumulation period. This parameter is subject to inhibition – see clause 7.2.7.13. + +If FEC is applied over multiple bearer channels, then each related FEC anomaly shall increment each of the counters related to the individual bearer channels. + +##### 7.2.2.1.3 Uncorrected data transfer unit-channel + +The uncorrected data transfer unit- (DTU-) channel (RTXUC-C) parameter is a count of *rtx-uc* anomalies (the number of uncorrected DTUs) occurring in the bearer channel during the accumulation period. + +##### 7.2.2.1.4 Retransmitted data transfer unit-channel + +The retransmitted DTU-channel (RTXTX-C) parameter is a count of *rtx-tx* anomalies (the number of retransmitted DTUs, see clause 12 of [ITU-T G.998.4]), occurring in the bearer channel during the accumulation period. + +#### **7.2.2.2 Channel far-end performance monitoring parameters** + +##### **7.2.2.2.1 Code violation-channel far-end** + +The code violation-channel far-end (CV-CFE) parameter is a count of FEBE anomalies occurring in the bearer channel during the accumulation period. This parameter is subject to inhibition – see clause 7.2.7.13. + +If the CRC is applied over multiple bearer channels, then each related FEBE anomaly shall increment each of the counters related to the individual bearer channels. + +##### **7.2.2.2.2 Forward error correction-Channel far-end** + +The forward error correction-channel far-end (FEC-CFE) parameter is a count of FFEC anomalies occurring in the bearer channel during the accumulation period. This parameter is subject to inhibition – see clause 7.2.7.13. + +If FEC is applied over multiple bearer channels, then each related FFEC anomaly shall increment each of the counters related to the individual bearer channels. + +##### **7.2.2.2.3 Uncorrected data transfer unit-channel far-end** + +The uncorrected DTU-channel far-end (RTXUC-CFE) parameter is a count of far-end rtx-uc anomalies (the number of uncorrected DTUs) occurring in the bearer channel during the accumulation period. + +##### **7.2.2.2.4 Retransmitted data transfer unit-channel far-end** + +The retransmitted DTU-channel far-end (RTXTX-CFE) parameter is a count of far-end rtx-tx anomalies (the number of retransmitted DTUs, see clause 12 of [ITU-T G.998.4]) occurring in the bearer channel during the accumulation period. + +### **7.2.3 Synchronous transfer mode data path performance monitoring parameters** + +The STM channel PM parameters are for further study. + +### **7.2.4 Asynchronous transfer mode data path performance monitoring parameters** + +This clause specifies a set of ATM data path PM parameters using cell transfer outcomes. Support of the performance parameters in an NE is indicated as mandatory (M) or optional (O) in Table 7-3. + +NOTE – The far-end parameters cannot be supported using only the indicator bits or EOC messages specified in [ITU-T G.992.1] or [ITU-T G.992.2]. They may be provided using the OAM communication channel specified in clause 6. + +#### **7.2.4.1 Asynchronous transfer mode data path near-end performance monitoring parameters** + +##### **7.2.4.1.1 Near-end header error control violation count** + +The near-end HEC\_violation\_count (HEC-P) performance parameter is a count of the number of occurrences of a near-end header error control (HEC) anomaly in the ATM data path. + +##### **7.2.4.1.2 Near-end delineated total cell count** + +The near-end delineated\_total\_cell\_count (CD-P) performance parameter is a count of the total number of cells passed through the cell delineation and HEC function process operating on the ATM data path while in the SYNC state. + +##### **7.2.4.1.3 Near-end user total cell count** + +The near-end User\_total\_cell\_count (CU-P) performance parameter is a count of the total number of cells in the ATM data path delivered at the V-C (for the xTU-C) or T-R (for the xTU-R) interface. + +##### 7.2.4.1.4 Near-end idle cell bit error count + +The near-end idle\_bit\_error\_count (IBE-P) performance parameter is a count of the number of bit errors in the idle cell payload received in the ATM data path at the near-end. + +NOTE – The idle cell payload is specified in [b-ITU-T I.361] and the b-ITU-T I.432.x series of Recommendations. + +#### 7.2.4.2 Asynchronous transfer mode data path far-end performance monitoring parameters + +##### 7.2.4.2.1 Far-end header error control violation count + +The far-end HEC\_violation\_count (HEC-PFE) performance parameter is a count of the number of occurrences of a far-end HEC anomaly in the ATM data path + +##### 7.2.4.2.2 Far-end delineated total cell count (CD-PFE) + +The far-end delineated\_total\_cell\_count (CD-PFE) performance parameter is a count of the total number of cells passed through the cell delineation process and HEC function operating on the ATM data path while in the SYNC state. + +##### 7.2.4.2.3 Far-end user total cell count + +The far-end user\_total\_cell\_count (CU-PFE) performance parameter is a count of the total number of cells in the ATM data path delivered at the V-C (for the xTU-C) or T-R (for the xTU-R) interface. + +##### 7.2.4.2.4 Far-end idle cell bit error count + +The far-end idle\_bit\_error\_count (IBE-PFE) performance parameter is a count of the number of bit errors in the idle cell payload received in the ATM data path at the far-end. + +### 7.2.5 Packet transfer mode data path performance monitoring parameters + +This clause defines a set of PTM data path PM parameters. Support of the performance parameters in an NE is indicated as mandatory (M) or optional (O) in Table 7-4. + +#### 7.2.5.1 Packet transfer mode data path near-end performance monitoring parameters + +##### 7.2.5.1.1 Near-end CRC error count + +The near-end CRC error count (CRC-P) performance parameter is a count of the number of occurrences of a CRC-*n* anomaly in the PTM data path at the near-end. + +The CRCP-P performance parameter is a count of the number of occurrences of a CRC-*np* anomaly in the PTM data path at the near-end. + +##### 7.2.5.1.2 Near-end coding violations count + +The near-end coding violations count (CV-P) performance parameter is a count of the number of occurrences of a cv-*n* anomaly in the PTM data path at the near-end. + +The CVP-P performance parameter is a count of the number of occurrences of a cv-*np* anomaly in the PTM data path at the near-end. + +#### 7.2.5.2 Packet transfer mode data path far-end performance monitoring parameters + +NOTE 1 – The far-end counters are not supported by the indicator bits or EOC messages specified in the ITU-T G.992.x-series of Recommendations or in [ITU-T G.993.2]. They may be provided if the higher layer protocol running over this PTM-TC provides means (that lie outside the scope of this Recommendation) to retrieve far-end PTM-TC surveillance primitives from the far-end, or through the OAM communication channel specified in clause 6. + +NOTE 2 – In [b-IEEE 802.3], the Ethernet management function (residing above the $\gamma$ -reference point) maps the near-end surveillance primitives and counters (obtained over the $\gamma$ -interface through access to clause 45 management data input/output (MDIO) registers) into MIB objects defined in clause 30. MIB objects are exchanged with the far-end using the Ethernet OAM PDU format and protocol defined in clause 57. + +##### 7.2.5.2.1 Far-end CRC error count + +The far-end CRC error count (CRC-PFE) performance parameter is a count at the far-end of the number of occurrences of a CRC-*n* anomaly (as observed by the far-end) in the PTM data path. + +The far-end CRCP-PFE performance parameter is a count at the far-end of the number of occurrences of a CRC-*np* anomaly (as observed by the far-end) in the PTM data path. + +##### 7.2.5.2.2 Far-end coding violations count + +The far-end coding violations count (CV-PFE) performance parameter is a count at the far-end of the number of occurrences of a cv-*n* anomaly (as observed by the far-end) in the PTM data path. + +The far-end CVP-PFE performance parameter is a count of the number of occurrences of a cv-*np* anomaly (as observed by the far-end) in the PTM data path. + +### 7.2.6 Performance monitoring data collection + +Parameters, failures, and signals etc. are specified in the foregoing and in Tables 7-1, 7-2, 7-3 and 7-4. Functions are indicated as mandatory (M) or optional (O). Mandatory functions shall be met for PM. Optional functions should be provided according to the user needs. + +**Table 7-1 – Line performance monitoring parameter definitions** + +| Name | End | Use at xTU-C | Use at xTU-R | Specification | +|----------------------------|------|--------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FECS-L | Near | M | M | FEC $\geq 1$ for one or more bearer channels. | +| FECS-LFE | Far | M | O | FFEC $\geq 1$ for one or more bearer channels. | +| ES-L | Near | M | M | CRC-8 $\geq 1$ for one or more bearer channels
OR LOS $\geq 1$ OR SEF $\geq 1$ OR LPR $\geq 1$ | +| ES-LFE | Far | M | O | FEFE $\geq 1$ for one or more bearer channels
OR LOS-FE $\geq 1$ OR RDI $\geq 1$ OR LPR-FE $\geq 1$ | +| SES-L | Near | M | M | CRC-8 $\geq 18$ for one or more bearer channels
OR LOS $\geq 1$ OR SEF $\geq 1$ OR LPR $\geq 1$
Further conditions, see clause 7.2.1.1.3. | +| SES-LFE | Far | M | O | FEFE $\geq 18$ for one or more bearer channels
OR LOS-FE $\geq 1$ OR RDI $\geq 1$ OR LPR-FE $\geq 1$
Further condition, see clause 7.2.1.2.3 | +| LOSS-L | Near | O | O | LOS $\geq 1$ | +| LOSS-LFE | Far | O | O | LOS-FE $\geq 1$ | +| UAS-L | Near | M | M | A second of unavailability | +| UAS-LFE | Far | M | O | A second of unavailability | +| INMINPEQ i -L | Near | O | | Count of INMAINPEQ i -L anomalies on the line | +| INMINPEQ i -LFE | Far | O | | Count of INMAINPEQ i -LFE anomalies on the line | +| INMIAT i -L | Near | O | | Count of INMAIAT i -L anomalies on the line | +| INMIAT i -LFE | Far | O | | Count of INMAIAT i -LFE anomalies on the line | +| INMME-L | Near | O | | Count of INMAME-L anomalies on the line | +| INMME-LFE | Far | O | | Count of INMAME-LFE anomalies on the line | + +**Table 7-1 – Line performance monitoring parameter definitions** + +| Name | End | Use at xTU-C | Use at xTU-R | Specification | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------------|--------------|---------------| +| NOTE 1 – Note that OR represents a logical OR of two conditions.
NOTE 2 – Unavailability specifications are presented in clauses 7.2.1.1.5 and 7.2.1.2.5.
NOTE 3 – If a common CRC or FEC is applied over multiple bearer channels, then each related CRC-8 or FEC anomaly shall be counted only once for the whole set of bearer channels over which the CRC or FEC is applied.
NOTE 4 – If the relevant Recommendation supports 1s normalized CRC counter increments, these increments shall be used instead of an increment of one for each CRC-8 and FEBE anomaly to declare SES. | | | | | + +**Table 7-2 – Channel performance monitoring parameter definitions** + +| Name | End | Use at xTU-C | Use at xTU-R | Specification | +|--------|------|--------------|--------------|------------------------------------------------| +| CV-C | Near | M | M | Count of CRC-8 anomalies in the bearer channel | +| CV-CFE | Far | M | O | Count of FEBE anomalies in the bearer channel | +| EC-C | Near | M | M | Count of FEC anomalies in the bearer channel | +| EC-CFE | Far | M | O | Count of FFEC anomalies in the bearer channel | + +**Table 7-3 – Asynchronous transfer mode data path performance monitoring parameter definitions** + +| Name | End | Use at xTU-C | Use at xTU-R | Specification | +|---------|------|--------------|--------------|-------------------------------------------------------------| +| HEC-P | Near | M | M | Count of HEC anomalies in the bearer channel | +| HEC-PFE | Far | M | O | Count of FHEC anomalies in the bearer channel | +| CD-P | Near | M | M | Count of delineated cells in the bearer channel | +| CD-PFE | Far | M | O | Count of delineated cells in the bearer channel | +| CU-P | Near | M | M | Count of cells to user in the bearer channel | +| CU-PFE | Far | M | O | Count of cells to user in the bearer channel | +| IBE-P | Near | M | M | Count of idle cell payload bit errors in the bearer channel | +| IBE-PFE | Far | M | O | Count of idle cell payload bit errors in the bearer channel | + +**Table 7-4 – Packet transfer mode data path performance monitoring parameter definitions** + +| Name | End | Use at xTU-C | Use at xTU-R | Specification | +|----------|------|--------------|--------------|------------------------------------------------------------------------------| +| CRC-P | Near | M | M | Count of non-pre-emptive packets with CRC error in the bearer channel | +| CRC-PFE | Far | M | O | Count of non-pre-emptive packets with CRC error in the bearer channel | +| CRCP-P | Near | M | M | Count of pre-emptive packets with CRC error in the bearer channel | +| CRCP-PFE | Far | M | O | Count of pre-emptive packets with CRC error in the bearer channel | +| CV-P | Near | M | M | Count of non-pre-emptive packets with coding violation in the bearer channel | + +**Table 7-4 – Packet transfer mode data path performance monitoring parameter definitions** + +| Name | End | Use at xTU-C | Use at xTU-R | Specification | +|---------|------|--------------|--------------|------------------------------------------------------------------------------| +| CV-PFE | Far | M | O | Count of non-pre-emptive packets with coding violation in the bearer channel | +| CVP-P | Near | M | M | Count of pre-emptive packets with coding violation in the bearer channel | +| CVP-PFE | Far | M | O | Count of pre-emptive packets with coding violation in the bearer channel | + +The line PM parameters (Table 7-1) are observed for the downstream and upstream directions. In the downstream direction, the near-end line PM parameters are observed by the xTU-R and far-end line PM parameters are observed by the xTU-C. In the upstream direction, near-end line PM parameters are observed by the xTU-C and far-end line PM parameters are observed by the xTU-R. + +For a downstream bearer channel, near-end channel (Table 7-2), ATM data path (Table 7-3, if applicable), and PTM data path (Table 7-4, if applicable) PM parameters are observed by the xTU-R and far-end PM parameters are observed by the xTU-C. For an upstream bearer channel, near-end channel and ATM data path PM parameters are observed by the xTU-C and far-end PM parameters are observed by the xTU-R. + +### 7.2.7 Procedures for performance monitoring functions + +The functions specified in this clause can be performed inside or outside the NE. + +#### 7.2.7.1 Line transmission states + +A line can be in one of two transmission states: + +- unavailable state; +- available state. + +The transmission state is determined from filtered SES/non-SES data. Unavailable state is specified in clause 7.2.1.1.5. An xDSL line is in the available state when it is not in the unavailable state. + +#### 7.2.7.2 Threshold reports + +A TR is an unsolicited error performance report from an ME over the Q-interface and from the xTU-R over the U-interface with respect to either a 15 min or 24 h evaluation period. TRs can only occur when the concerned direction is in the available state. At the Q-interface, TRs for near-end and far-end errored second (ES), SES and UAS parameters are mandatory, and TRs for the other defined parameters are optional except for INM parameters, LPR\_INTRPT, HRI\_INTRPT, for which TRs are not defined. TRs are not provided at the T/S-interface. + +TR1s shall occur within 10 s after the 15 min threshold is reached or exceeded. + +TR2s shall occur within 10 s after the 24 h threshold is reached or exceeded. + +#### 7.2.7.3 Unavailable and available state filters + +The unavailable state filter is a 10 s rectangular sliding window with a 1 s granularity of the slide. + +The available state filter is also a 10 s rectangular sliding window with a 1 s granularity of the slide. + +#### 7.2.7.4 TR1 filter + +The TR1 filter is a 15 min rectangular fixed window. The start and end times for the 15 min rectangular fixed windows shall fall on the hour and at 15, 30 and 45 min after the hour. + +#### 7.2.7.5 TR2 filter + +The TR2 filter is a 24 h rectangular fixed window. The start and end times for the 24 h rectangular fixed windows shall fall on a 15 min window boundary. + +#### 7.2.7.6 Evaluation of TR1 + +The parameters are counted separately, second by second, over each 15 min rectangular fixed window period. The threshold values should be programmable over the range 0 to 900 with default values. The default values are given in [b-ITU-T M.2100] and [b-ITU-T M.2101]. + +A threshold can be crossed at any second within the 15 min rectangular fixed window. As soon as a threshold is crossed, a TR1 as appropriate should be sent to the NMS together with a date/time-stamp. Moreover, performance events should continue to be counted to the end of the current 15 min period, at which time the current parameter counts are stored in the history registers and the current parameter registers are reset to zero. + +#### 7.2.7.7 Evaluation of TR2 + +The parameters are counted separately over each 24 h period. The threshold values should be programmable over the range 0 to 86 400 with default values. + +The NE shall recognize a 24 h threshold crossing within 15 min of its occurrence. The threshold crossing shall be given the date/time-stamp of the moment of recognition. A TR2 as appropriate should be sent to the NMS with the date/time-stamp. Moreover, performance events should continue to be counted to the end of the current 24 h period, at which time the parameter counts are stored in the history registers and the current parameter registers are reset to zero. + +#### 7.2.7.8 Threshold report evaluation during transmission state changes + +Care should be taken to ensure that TRs are correctly generated and parameter counters are correctly processed during changes in the transmission state. This implies that all TRs should be delayed by 10 s (see [b-ITU-T M.2120]). + +#### 7.2.7.9 Performance history storage in network elements + +The parameters for ME performance history storage at the Q-interface that shall be supported are ES, SES and UAS. Performance history storage for the other defined parameters is optional. + +There shall be a current 15 min register (which can also facilitate the TR1 filter) plus a further $N$ 15 min history registers for each parameter in each ME. The $N$ 15 min history registers are used as a stack, i.e., the value held in each register is pushed down the stack one place at the end of each 15 min period, and the oldest register value at the bottom of the stack is discarded. + +The value of $N$ for the parameters ES, SES and UAS shall be at least 16. For the other parameters, the value of $N$ shall be at least 1 (i.e., only current and previous values are required). If INM parameters are supported, the value of $N$ for those parameters shall be 1. + +There shall be a current 24 h register (which can also facilitate the TR2 filter) plus one previous 24 h register for each parameter. + +As a minimum, an invalid data flag shall be provided for each stored interval for each direction for each monitored transmission entity. An example follows. + +An invalid data flag is set to indicate that the data stored is incomplete or otherwise invalid when the data: + +- in the previous and recent intervals has been accumulated over a period of time that is greater or less than the nominal accumulation period duration; +- in the current interval is suspect because a terminal is restarted or a register is reset in the middle of an accumulation period; + +- is incomplete in an accumulation period. e.g., an incoming transmission failure or defect may prevent complete collection of far-end performance reports. + +The invalid data flag is not set as a result of register saturation. + +#### 7.2.7.10 Register size + +The minimum register size is 16 bits. The maximum register sizes are vendor discretionary. When the maximum value of a register is reached, the register shall remain at that maximum value until it is reset or the value is transferred or discarded, as described in this clause. + +#### 7.2.7.11 Parameter counts + +All parameter counts shall be actual counts for the 15 min filtering period. + +Although all parameter counts should (ideally) also be actual for the 24 h filtering periods, it is recognized that it might be desirable to limit register sizes. In such cases, register overflow may occur, in which case, the registers shall hold their maximum value for the parameter considered until the registers are read and reset at the end of the 24 h period. An implementation involving setting and resetting an overflow bit may be used. + +If the AN-ME does not force the line into the L3 state, then PM counters shall be active, irrespective of the actual link state of the line. + +If the AN-ME forces the line into the L3 state, then all PM counters shall be frozen, including the UAS counter. + +The time when the PM counters are frozen shall be excluded from the accumulation period (see clause 7.2.7.9). + +NOTE – The AN-ME may force the line into the L3 state, e.g., when the line is configured with AdminStatus="down", during loop diagnostics mode (see clause 7.3.1.1.8), or during a single-ended line test (SELT) measurement (see ITU-T G.996.2). + +#### 7.2.7.12 Date/time stamping of reports + +The date/time-stamping accuracy of reports, together with the method of maintaining the accuracy, is under study. + +The format for date/time stamps is as follows: + +- 15 min window will be stamped year, month, day, hour, minute; +- 24 h window will be stamped year, month, day, hour; +- unavailable time events will be stamped year, month, day, hour, minute, second; +- alarms will be stamped either at the declaration of the alarm by the equipment or at the exact time of the event (to be decided) with year, month, day, hour, minute, second. + +Equipment clock accuracy requirements are for further study. + +#### 7.2.7.13 Inhibiting performance monitoring parameters + +For a given monitored entity, the accumulation of certain performance parameters is inhibited during periods of unavailability, during SESs or during seconds containing defects on that monitored entity. Inhibiting a given monitored entity (e.g., ADSL ATM data path) is not explicitly affected by conditions on any other monitored entity (xDSL line). The inhibiting rules are as follows. + +- UAS and failure count parameters shall not be inhibited. +- *left* defect seconds counter and MINEFTR shall not be inhibited. +- INM parameters shall be inhibited during a 1 s interval, if they contain one or more LOS defects, or one or more SEF defects, or one or more LPR defects. + +SES-L, SES-LFE, ES-L, ES-LFE, LOSS-L and LOSS-LFE counters shall be inhibited only during unavailable time, even if the unavailable time is declared retroactively. + +NOTE – An implementation may count the SES-L, ES-L and LOSS-L during the contiguous SES-L leading to the declaration of UAS-L and subtract them at the onset of the declaration of UAS-L. The same may apply for the LOSS-LFE. See Figure 4 of [b-ITU-T M.2100]. + +- All other performance parameter counts shall be inhibited during UAS and SES. Inhibition shall be retroactive to the onset of unavailable time and shall end retroactively to the end of unavailable time. + +## 7.3 Configuration functions + +### 7.3.1 Line configuration parameters + +#### 7.3.1.1 State configuration parameters + +##### 7.3.1.1.1 xTU transmission system enabling + +The xTU transmission system enabling (XTSE) configuration parameter defines the transmission system types to be allowed by the near-end xTU on this line. This parameter only applies to the Q-interface. It is coded in a bit-map representation (0 if not allowed, 1 if allowed), with the following specification. + +###### | Bit | Representation | |-----|----------------| |-----|----------------| + +###### *Octet 1* + +| | | +|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Regional standards (see Note) | +| 2 | Regional standards (see Note) | +| 3 | ITU-T G.992.1 operation over plain old telephone service (POTS; one of the services using the voiceband; sometimes used as a descriptor for all voiceband services) non-overlapped spectrum (see Annex A of [ITU-T G.992.1]) | +| 4 | ITU-T G.992.1 operation over POTS overlapped spectrum (see Annex A of [ITU-T G.992.1]) | +| 5 | ITU-T G.992.1 operation over the integrated services digital network (ISDN) non-overlapped spectrum (see Annex B of [ITU-T G.992.1]) | +| 6 | ITU-T G.992.1 operation over ISDN overlapped spectrum (see Annex B of [ITU-T G.992.1]) | +| 7 | ITU-T G.992.1 operation in conjunction with TCM-ISDN non-overlapped spectrum (see Annex C of [ITU-T G.992.1]) | +| 8 | ITU-T G.992.1 operation in conjunction with TCM-ISDN overlapped spectrum (see Annex C of [ITU-T G.992.1]) | + +###### *Octet 2* + +| | | +|----|---------------------------------------------------------------------------------------------------------------| +| 9 | ITU-T G.992.2 operation over POTS non-overlapped spectrum (see Annex A of [ITU-T G.992.2]) | +| 10 | ITU-T G.992.2 operation over POTS overlapped spectrum (see Annex B of [ITU-T G.992.2]) | +| 11 | ITU-T G.992.2 operation in conjunction with TCM-ISDN non-overlapped spectrum (see Annex C of [ITU-T G.992.2]) | +| 12 | ITU-T G.992.2 operation in conjunction with TCM-ISDN overlapped spectrum (see Annex C of [ITU-T G.992.2]) | +| 13 | Reserved | +| 14 | Reserved | +| 15 | Reserved | +| 16 | Reserved | + +###### *Octet 3* + +- 17 Reserved +- 18 Reserved +- 19 ITU-T G.992.3 operation over POTS non-overlapped spectrum (see Annex A of [ITU-T G.992.3]) +- 20 ITU-T G.992.3 operation over POTS overlapped spectrum (see Annex A of [ITU-T G.992.3]) +- 21 ITU-T G.992.3 operation over ISDN non-overlapped spectrum (see Annex B of [ITU-T G.992.3]) +- 22 ITU-T G.992.3 operation over ISDN overlapped spectrum (see Annex B of [ITU-T G.992.3]) +- 23 ITU-T G.992.3 operation in conjunction with TCM-ISDN non-overlapped spectrum (see Annex C of [ITU-T G.992.3]) +- 24 ITU-T G.992.3 operation in conjunction with TCM-ISDN overlapped spectrum (see Annex C of [ITU-T G.992.3]) + +###### *Octet 4* + +- 25 ITU-T G.992.4 operation over POTS non-overlapped spectrum (see Annex A of [ITU-T G.992.4]) +- 26 ITU-T G.992.4 operation over POTS overlapped spectrum (see Annex A of [ITU-T G.992.4]) +- 27 Reserved +- 28 Reserved +- 29 ITU-T G.992.3 all digital mode operation with non-overlapped spectrum (see Annex I of [ITU-T G.992.3]) +- 30 ITU-T G.992.3 all digital mode operation with overlapped spectrum (see Annex I of [ITU-T G.992.3]) +- 31 ITU-T G.992.3 all digital mode operation with non-overlapped spectrum (see Annex J of [ITU-T G.992.3]) +- 32 ITU-T G.992.3 all digital mode operation with overlapped spectrum (see Annex J of [ITU-T G.992.3]) + +###### *Octet 5* + +- 33 ITU-T G.992.4 all digital mode operation with non-overlapped spectrum (see Annex I of [ITU-T G.992.4]) +- 34 ITU-T G.992.4 all digital mode operation with overlapped spectrum (see Annex I of [ITU-T G.992.4]) +- 35 ITU-T G.992.3 reach extended operation over POTS, mode 1 (non-overlapped, wide upstream) (see Annex L of [ITU-T G.992.3]) +- 36 ITU-T G.992.3 reach extended operation over POTS, mode 2 (non-overlapped, narrow upstream) (see Annex L of [ITU-T G.992.3]) +- 37 ITU-T G.992.3 reach extended operation over POTS, mode 3 (overlapped, wide upstream) (see Annex L of [ITU-T G.992.3]) +- 38 ITU-T G.992.3 reach extended operation over POTS, mode 4 (overlapped, narrow upstream) (see Annex L of [ITU-T G.992.3]) +- 39 ITU-T G.992.3 extended upstream operation over POTS non-overlapped spectrum (see Annex M of [ITU-T G.992.3]) +- 40 ITU-T G.992.3 extended upstream operation over POTS overlapped spectrum (see Annex M of [ITU-T G.992.3]) + +###### Octet 6 + +- 41 ITU-T G.992.5 operation over POTS non-overlapped spectrum (see Annex A of [ITU-T G.992.5]) +- 42 ITU-T G.992.5 operation over POTS overlapped spectrum (see Annex A of [ITU-T G.992.5]) +- 43 ITU-T G.992.5 operation over ISDN non-overlapped spectrum (see Annex B of [ITU-T G.992.5]) +- 44 ITU-T G.992.5 operation over ISDN overlapped spectrum (see Annex B of [ITU-T G.992.5]) +- 45 ITU-T G.992.5 operation in conjunction with TCM-ISDN non-overlapped spectrum (see Annex C of [ITU-T G.992.5]) +- 46 ITU-T G.992.5 operation in conjunction with TCM-ISDN overlapped spectrum (see Annex C of [ITU-T G.992.5]) +- 47 ITU-T G.992.5 all digital mode operation with non-overlapped spectrum (see Annex I of [ITU-T G.992.5]) +- 48 ITU-T G.992.5 all digital mode operation with overlapped spectrum (see Annex I of [ITU-T G.992.5]) + +###### Octet 7 + +- 49 ITU-T G.992.5 all digital mode operation with non-overlapped spectrum (see Annex J of [ITU-T G.992.5]) +- 50 ITU-T G.992.5 all digital mode operation with overlapped spectrum (see Annex J of [ITU-T G.992.5]) +- 51 ITU-T G.992.5 extended upstream operation over POTS non-overlapped spectrum (see Annex M of [ITU-T G.992.5]) +- 52 ITU-T G.992.5 extended upstream operation over POTS overlapped spectrum (see Annex M of [ITU-T G.992.5]) +- 53 Reserved +- 54 Reserved +- 55 Reserved +- 56 Reserved + +###### Octet 8 + +- 57 ITU-T G.993.2 Region A (North America) (see Annex A of [ITU-T G.993.2]) +- 58 ITU-T G.993.2 Region B (Europe) (see Annex B of [ITU-T G.993.2]) +- 59 ITU-T G.993.2 Region C (Japan) (see Annex C of [ITU-T G.993.2]) +- 60 ITU-T G.993.2 Region D (China) (see Annex N of [ITU-T G.993.2]). +- 61 Reserved +- 62 Reserved +- 63 Reserved +- 64 Reserved + +NOTE – It is recommended that bit 1 be used for [b-ATIS 0600413]. It is recommended that bit 2 be used for Annex C of [b-ETSI TS 101 388]. + +##### 7.3.1.1.2 Asymmetric digital subscriber line transceiver unit impedance state forced + +The ADSL transceiver unit impedance state forced (AISF) configuration parameter defines the impedance state to be forced on the near-end ADSL transceiver unit (ATU). It applies only to the T/S-interface. It is coded as an integer value with the following assignments. + +- 1 Force the near-end ATU to the disabled state +- 2 Force the near-end ATU to the inactive state +- 3 Force the near-end ATU to the active state + +Impedance states apply only to Annex A of [ITU-T G.992.3] operation mode and are specified in clause A.4.1 of [ITU-T G.992.3]. + +##### 7.3.1.1.3 Power management state forced + +The power management state forced (PMSF) configuration parameter defines the line states to be forced by the near-end xTU on this line. It is coded as an integer value with the following specification. + +- 0 Force the line to transition from the L3 idle state to the L0 full-on state (i.e., both xTUs are in showtime). This transition requires the (short or full) initialization procedures. After reaching the L0 state, the line may transition into or exit from the L2 low power state (if L2 state is defined and enabled). If the L0 state is not reached (after a vendor discretionary number of retries or within a vendor discretionary timeout), then an initialization failure occurs. Whenever the line is in the L3 state, attempts shall be made to transition to the L0 state until it is forced into another state through this configuration parameter. +- 2 Force the line to transition from L0 full on to L2 low power state. This transition requires the entry into L2 mode. This is an out-of-service test value for triggering the L2 mode and is valid only for Recommendations supporting L2 mode. +- 3 Force the line to transition from the L0 full-on or L2 low power state to the L3 idle state. This transition requires the (orderly) shutdown procedure. After reaching the L3 state, the line shall remain in the L3 idle state until it is forced into another state through this configuration parameter. + +Forced line state transitions require the line to enter or exit the L3 idle state. These transitions are not restricted by the power management state enabling parameter value. + +NOTE – This configuration parameter maps to the AdminStatus of the line, which is part of the GeneralInformationGroup object group specified in [b-IETF RFC 2233], and may not need to be duplicated in the ADSL MIB. See also [b-IETF RFC 2662]. The administrative status of the line is up when the line is forced to the L0 state and is down when the line is forced to the L3 state. + +##### 7.3.1.1.4 Power management state enabling + +The power management state enabling (PMMMode) configuration parameter specifies the line states the xTU-C or xTU-R may autonomously transition to on this line. It is coded in a bit-map representation (0 if not allowed, 1 if allowed) with following assignments. + +bit 0 L3 state (idle state) + +bit 1 L1/L2 state (low power state) + +NOTE – L1/L2 state may not be defined in some ITU-T Recommendations. + +##### 7.3.1.1.5 Minimum L0 time interval between L2 exit and next L2 entry + +The minimum L0 time interval between L2 exit and next L2 entry (L0-TIME) parameter represents the minimum time (in seconds) between an exit from the L2 state and the next entry into the L2 state. It ranges from 0 s to 255 s. + +##### 7.3.1.1.6 Minimum L2 time interval between L2 entry and first L2 trim + +The minimum L2 time interval between L2 entry and first L2 trim (L2-TIME) parameter represents the minimum time (in seconds) between an entry into the L2 state and the first power trim in the L2 state and between two consecutive power trims in the L2 state. It ranges from 0 s to 255 s. + +##### **7.3.1.1.7 Maximum aggregate transmit power reduction per L2 request or L2 power trim** + +The maximum aggregate transmit power reduction per L2 request or L2 power trim (L2-ATPR) parameter represents the maximum aggregate transmit power reduction, in decibels, that can be performed in the L2 request (i.e., at the transition of the L0 to L2 state) or through a single power trim in the L2 state. It ranges from 0 dB to 31 dB in steps of 1 dB. + +##### **7.3.1.1.8 Loop diagnostic mode status forced** + +The loop diagnostic mode status forced (LDSF) configuration parameter determines whether the line should be forced into the loop diagnostic mode by the near-end xTU on this line. It is coded as an integer value with the following assignments. + +- 0 Inhibits the near-end xTU from performing loop diagnostic mode procedures on the line. Loop diagnostic mode procedures may still be initiated by the far-end xTU +- 1 Forces the near-end xTU to perform the loop diagnostic procedures + +Upon the NMS forcing the loop diagnostics mode on the line, the AN shall force the line to the L3 state before it forces the near-end xTU to perform the loop diagnostic mode procedures. Only while the line power management state is the L3 state (see clause 7.5.1.5), can the near-end xTU be forced to perform the loop diagnostic mode procedures. + +If the loop diagnostics mode status and results status (LDS and LDR, see clauses 7.5.1.46 and 7.5.1.47) MIB elements are not supported, then upon successful completion of the loop diagnostic mode procedures, the AN shall set the LDSF MIB element to 0, and the xTUs shall return to the idle state. The loop diagnostic data shall be available at least until the NMS no longer forces the loop diagnostic mode. If the loop diagnostic mode procedures cannot be completed successfully (after a vendor discretionary number of retries or within a vendor discretionary timeout), then an initialization failure shall occur. + +If the LDS and LDR (see clauses 7.5.1.46 and 7.5.1.47) MIB elements are supported, then upon successful completion of the loop diagnostic mode procedures, the AN shall set the LDS to "inactive" and the LDR to "loop-diagnostics-succeeded-results-valid", and the xTUs shall return to the idle state. The loop diagnostic mode data shall be available at least until the NMS no longer forces the loop diagnostic mode. If the loop diagnostic mode procedures cannot be completed successfully (after a vendor discretionary number of retries or within a vendor discretionary timeout), then the AN shall set the LDS to "inactive" and the LDR to "loop diagnostics failed results invalid", and the xTUs shall return to the idle state. + +##### **7.3.1.1.9 Total maximum aggregate transmit power reduction in L2** + +The total maximum aggregate transmit power reduction in L2 (L2-ATPRT) parameter represents the total maximum aggregate transmit power reduction, in decibels, that can be performed in an L2 state. This is the sum of all reductions of L2 request (i.e., at transition of L0 to L2 state) and power trims. It ranges from 0 dB to 31 dB in steps of 1 dB. + +##### **7.3.1.1.10 Automode cold start forced** + +This parameter is specified in order to improve testing of the performance of xTUs supporting automode when it is enabled in the MIB. The valid values are 0 and 1. A change in value of this parameter indicates a change in loop conditions applied to the devices under test. The xTUs shall reset any historical information used for automode, for shortening ITU-T G.994.1 handshake or for shortening the initialization procedure. + +Automode is defined as the case where multiple operation-modes are enabled in the MIB in the XTSE line configuration parameter (see 8.3.1.1.1) and where the selection of the operation-mode to be used for transmission does not only depend on the common capabilities of both xTUs (as exchanged in [ITU-T G.994.1]), but depends also on achievable data rates under given loop conditions. + +This parameter is mandatory at the Q-interface for modems supporting automode. + +##### **7.3.1.1.11 VDSL2 profiles enabling** + +The VDSL2 profiles enabling (PROFILES) configuration parameter contains the ITU-T G.993.2 profiles to be allowed by the near-end xTU on this line. It is coded in a bit-map representation (0 if not allowed, 1 if allowed) with the following specification. + +###### **Bit      Representation** + +###### *Octet 1* + +| | | +|---|---------------------------| +| 1 | ITU-T G.993.2 profile 8a | +| 2 | ITU-T G.993.2 profile 8b | +| 3 | ITU-T G.993.2 profile 8c | +| 4 | ITU-T G.993.2 profile 8d | +| 5 | ITU-T G.993.2 profile 12a | +| 6 | ITU-T G.993.2 profile 12b | +| 7 | ITU-T G.993.2 profile 17a | +| 8 | ITU-T G.993.2 profile 30a | + +###### *Octet 2* + +| | | +|---|---------------------------| +| 1 | ITU-T G.993.2 profile 35b | +| 2 | reserved by ITU-T | +| 3 | reserved by ITU-T | +| 4 | reserved by ITU-T | +| 5 | reserved by ITU-T | +| 6 | reserved by ITU-T | +| 7 | reserved by ITU-T | +| 8 | reserved by ITU-T | + +##### **7.3.1.1.12 Re-Initialization policy selection** + +###### **7.3.1.1.12.1 Downstream re-initialization policy selection** + +The downstream RIPOLICY selection (RIPOLICYds) parameter indicates which policy shall be applied to determine the triggers for re-initialization in the downstream direction (see clause 12.1.4 of [ITU-T G.993.2] and clauses 7.3.1.1.13 and 7.2.1.1.5). + +If RIPOLICYds=1 is configured and it is detected during ITU-T G.993.2 initialization that RIPOLICYds=1 is not supported in the downstream direction by either XTU, they shall fallback to RIPOLICYds=0. + +The valid values for RIPOLICYds are 0 and 1. + +###### **7.3.1.1.12.2 Upstream re-initialization policy selection** + +The upstream RIPOLICY selection (RIPOLICYus) parameter indicates which policy shall be applied to determine the triggers for re-initialization in the upstream direction (see clause 12.1.4 of [ITU-T G.993.2] and clauses 7.3.1.1.13 and 7.2.1.1.5). + +If RIPOLICYus=1 is configured and it is detected during ITU-T G.993.2 initialization that RIPOLICYus=1 is not supported in the upstream direction by either XTU, they shall fallback to RIPOLICYus=0. + +The valid values for RIPOLICYus are 0 and 1. + +##### **7.3.1.1.13 SES- based re-initialization threshold** + +###### **7.3.1.1.13.1 Downstream SES- based re-initialization threshold** + +The REINIT\_TIME\_THRESHOLDDs parameter determines the downstream threshold for re-initialization based on SES to be used by the VDSL2 transceiver unit (VTU) receiver when RIPOLICY 1 is used in downstream (see clause 12.1.4 of [ITU-T G.993.2]). + +The valid range is from 5 to 31. + +###### **7.3.1.1.13.2 Upstream SES- based re-initialization threshold** + +The REINIT\_TIME\_THRESHOLDDus parameter determines the upstream threshold for re-initialization based on SES, to be used by the VTU receiver when RIPOLICY 1 is used in upstream (see clause 12.1.4 of [ITU-T G.993.2]). + +The valid range is from 5 to 31. + +#### **7.3.1.2 Power/power spectral density configuration parameters** + +##### **7.3.1.2.1 Downstream maximum nominal power spectral density** + +The downstream maximum nominal power spectral density (MAXNOMPSDDs) parameter represents the maximum nominal transmit power spectral density (PSD) in the downstream direction during initialization and showtime, in decibels with reference to 1 mW per hertz. A single MAXNOMPSDDs parameter is defined per mode enabled in the XTSE line configuration parameter. It ranges from –60 dBm/Hz to –30 dBm/Hz, with 0.1 dBm/Hz steps. + +##### **7.3.1.2.2 Upstream maximum nominal power spectral density** + +The upstream maximum nominal power spectral density (MAXNOMPSDus) parameter represents the maximum nominal transmit PSD in the upstream direction during initialization and showtime, in decibels with reference to 1 mW per hertz. A single MAXNOMPSDus parameter is defined per mode enabled in the XTSE line configuration parameter. It ranges from –60 dBm/Hz to –30 dBm/Hz, with 0.1 dBm/Hz steps. + +##### **7.3.1.2.3 Downstream maximum nominal aggregate transmit power** + +The downstream maximum nominal aggregate transmit power (MAXNOMATPDs) parameter represents the maximum nominal aggregate transmit power in the downstream direction during initialization and showtime, in decibels with reference to 1 mW. It ranges from 0 dBm to 25.5 dBm, with 0.1 dBm steps. + +##### **7.3.1.2.4 Upstream maximum nominal aggregate transmit power** + +The upstream maximum nominal aggregate transmit power (MAXNOMATPus) parameter represents the maximum nominal aggregate transmit power in the upstream direction during initialization and showtime, in decibels with reference to 1 mW. It ranges from 0 dBm to 25.5 dBm, with 0.1 dB steps. + +##### **7.3.1.2.5 Upstream maximum aggregate receive power** + +The upstream maximum aggregate receive power (MAXRXPWRus) parameter represents the maximum upstream aggregate receive power over a set of subcarriers, in decibels with reference to 1 mW, as specified in the relevant Recommendation. The xTU-C shall request an upstream power cutback such that the upstream aggregate received power over that set of subcarriers is at or below the configured maximum value. It ranges from –25.5 dBm to 25.5 dBm, with 0.1 dB steps. A special value is used to indicate that no upstream maximum aggregate receive power limit is to be applied (i.e., the maximum value is infinite). + +##### 7.3.1.2.6 Downstream subcarrier masking + +The downstream subcarrier masking (CARMASKds) configuration parameter is an array of boolean values, $sc(i)$ . Each entry $sc(i)$ determines whether a subcarrier with index $i$ is masked on this line in the downstream direction, for $i$ ranging from 0 to NSCds-1. It is coded as 1 if the subcarrier is masked and 0 if the subcarrier is not masked. + +NSCds is the highest subcarrier index that can be transmitted in the downstream direction. For [ITU-T G.992.3], [ITU-T G.992.4], and [ITU-T G.992.5], it is specified in the corresponding Recommendations. For [ITU-T G.992.1], NSCds = 256 and for [ITU-T G.992.2], NSCds = 128. + +##### 7.3.1.2.7 Upstream subcarrier masking + +The upstream subcarrier masking (CARMASKus) configuration parameter is an array of Boolean values $sc(i)$ . Each entry $sc(i)$ defines whether transmission of subcarrier with index $i$ is masked on this line in the upstream direction, for $i$ ranging from 0 to NSCus-1. It is coded as 1 if the subcarrier is masked and 0 if the subcarrier is not masked. + +NSCus is the highest subcarrier index that can be transmitted in the upstream direction. For [ITU-T G.992.3], [ITU-T G.992.4] and [ITU-T G.992.5], it is specified in the corresponding Recommendation. For Annex A of [ITU-T G.992.1] and [ITU-T G.992.2], NSCus = 32 and for Annex B of [ITU-T G.992.1], NSCus = 64. + +##### 7.3.1.2.8 VDSL2 subcarrier masking + +The VDSL2 subcarrier masking (VDSL2-CARMASK) configuration parameter specifies the restrictions, additional to the band plan, to determine the set of subcarriers allowed for transmission in both upstream and downstream directions. + +The VDSL2-CARMASK shall describe the unmasked subcarriers as one or more frequency bands. Each band is represented by start and stop subcarrier indices with a subcarrier spacing of 4.312 5 kHz. The valid range of subcarrier indices specifying the VDSL2-CARMASK is from 0 to at least the index of the highest allowed subcarrier in both transmission directions among all profiles enabled by the parameter PROFILES (see clause 7.3.1.1.11). Up to 32 bands may be specified. Other subcarriers shall be masked. + +For profiles using 8.625 kHz tone spacing, the odd subcarrier indices $i_{4.312\ 5}$ in VDSL2-CARMASK shall be transformed into actual subcarrier indices $i_{8.625}$ using the following rule: + +- for the start frequency of each band: $i_{8.625} = (i_{4.312\ 5} + 1)/2$ +- for the stop frequency of each band: $i_{8.625} = (i_{4.312\ 5} - 1)/2$ . + +##### 7.3.1.2.9 Downstream power spectral density mask + +The downstream PSD mask (PSDMASKds) configuration parameter defines the downstream PSD mask applicable at the U-C2 reference point as defined in the respective Recommendation. A modified PSD mask, as defined in clause 7.3.1.2.13, may apply at the U-C2 reference point. This MIB PSD mask may impose PSD restrictions in addition to the limit PSD mask specified in the relevant Recommendation (e.g., [ITU-T G.992.5] and [ITU-T G.993.2]). + +NOTE – In [ITU-T G.993.2], the PSDMASKds parameter is referred to as MIBMASKds. + +The downstream PSD mask in the central office-management information base (CO-MIB) shall be specified through a set of breakpoints. Each breakpoint shall consist of a subcarrier index $t$ , with a subcarrier spacing of 4.312 5 kHz, and a MIB PSD mask level (expressed in decibels with reference to 1 mW per hertz) at that subcarrier. The set of breakpoints can then be represented as $[(t_1, \text{PSD}_1), (t_2, \text{PSD}_2), \dots, (t_N, \text{PSD}_N)]$ . The subcarrier index shall be coded as an unsigned integer. The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz to -127.5 dBm/Hz, in steps of 0.5 dBm/Hz, with a valid range from 0 to -95 dBm/Hz. The maximum number of breakpoints is 32. + +The requirements for a valid set of breakpoints are specified in the relevant Recommendations (e.g., [ITU-T G.992.5] and [ITU-T G.993.2]). + +##### 7.3.1.2.10 Remote failure indication bands + +For [ITU-T G.992.5], the remote failure indication bands (RFIBANDS) configuration parameter determines the subset of downstream PSD mask breakpoints, as specified in PSDMASKds, that shall be used to notch a remote failure indication (RFI) band. This subset consists of couples of consecutive subcarrier indices belonging to breakpoints: $[t_i; t_i + 1]$ , corresponding to the low level of the notch. The specific interpolation around these points is specified in the relevant Recommendations (e.g., [ITU-T G.992.5]). The CO-MIB shall define the RFI notches using breakpoints in PSDMASKds as specified in the relevant Recommendations (e.g., [ITU-T G.992.5]). + +For [ITU-T G.993.2], this configuration parameter determines the bands where the PSD shall be reduced as specified in clause 7.2.1.2 of [ITU-T G.993.2]. Each band shall be represented by a start and stop subcarrier index with a subcarrier spacing of 4.312 5 kHz. Up to 16 bands may be specified. This parameter defines the RFI bands for both upstream and downstream directions. + +##### 7.3.1.2.11 Upstream power spectral density mask selection + +This configuration parameter determines which upstream PSD mask is enabled. This parameter is used only for Annexes J and M of [ITU-T G.992.3] and [ITU-T G.992.5]. As only one selection parameter is defined in the MIB, the same selection value applies to all relevant modes enabled in the XTSE line configuration parameter. Its value ranges from 1 to 9 and selects the mask with the assignments in Table 7-5. + +**Table 7-5 – Assignments of values of upstream power spectral density mask selection parameter for Annex J of [ITU-T G.992.3] and Annex M of [ITU-T G.992.5]** + +| Upstream PSD mask selection value | Selected mask | | +|-----------------------------------|----------------------------|----------------------------| +| | Annex J of [ITU-T G.992.3] | Annex M of [ITU-T G.992.5] | +| 1 | ADLU-32 | EU-32 | +| 2 | ADLU-36 | EU-36 | +| 3 | ADLU-40 | EU-40 | +| 4 | ADLU-44 | EU-44 | +| 5 | ADLU-48 | EU-48 | +| 6 | ADLU-52 | EU-52 | +| 7 | ADLU-56 | EU-56 | +| 8 | ADLU-60 | EU-60 | +| 9 | ADLU-64 | EU-64 | + +##### 7.3.1.2.12 Upstream power spectral density mask + +The upstream PSD mask (PSDMASKus) configuration parameter determines the upstream PSD mask applicable at the U-R2 reference point as specified in the respective Recommendation. This MIB PSD mask may impose PSD restrictions in addition to the limit PSD mask specified in the relevant Recommendations (e.g., [ITU-T G.992.3], [ITU-T G.993.2]). + +NOTE – In [ITU-T G.993.2], the PSDMASKus parameter is referred to as MIBMASKus and does not include breakpoints to shape US0. + +The upstream PSD mask in the CO-MIB shall be specified through a set of breakpoints. Each breakpoint shall consist of a subcarrier index $t$ , with a subcarrier spacing of 4.312 5 kHz, and a MIB PSD mask level (expressed in decibels with reference to 1 mW per hertz) at that subcarrier. + +The set of breakpoints can then be represented as $[(t_1, \text{PSD}_1), (t_2, \text{PSD}_2), \dots, (t_N, \text{PSD}_N)]$ . The subcarrier index shall be coded as an unsigned integer. The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz to -127.5 dBm/Hz, in steps of 0.5 dBm/Hz, with a valid range from 0 to -95 dBm/Hz. The maximum number of breakpoints is four for [ITU-T G.992.3] and 16 for [ITU-T G.993.2]. + +The requirements for a valid set of breakpoints are specified in the relevant Recommendations (e.g., [ITU-T G.992.3] or [ITU-T G.993.2]). + +##### 7.3.1.2.13 Downstream power back-off-Shaped (DPBOSHAPED) + +This clause provides a set of line configuration parameters and a procedure to generate a modified downstream MIB PSD mask. The modified PSD mask shall be used instead of PSDMASKds to configure the downstream PSD mask applicable at the U-C2 reference point. An example of application of this method is described in Appendix II. + +###### a) Downstream power back-off configuration parameters + +###### a.1) Assumed exchange PSD mask + +The assumed exchange PSD mask (DPBOEPSD) parameter determines the PSD mask that is assumed to be permitted at the exchange. This parameter shall use the same format as PSDMASKds. + +The maximum number of breakpoints for DPBOEPSD is 16. + +###### a.2) E-side electrical length + +The E-side electrical length (DPBOESEL) configuration parameter determines the assumed electrical length of cables (E-side cables) connecting exchange-based DSL services to a remote flexibility point (cabinet), which hosts the xTU-C that is subject to spectrally shaped downstream power back-off (DPBO) depending on this length. For this parameter, the electrical length is defined as the loss, in decibels, of an equivalent length of hypothetical cable at a reference frequency determined by the network operator or in spectrum management regulations. DPBOESEL shall be coded as an unsigned integer representing an electrical length from 0 dB to 255.5 dB in steps of 0.5 dB. All values in the range are valid. + +If DPBOESEL is set to zero, the DPBO in this clause shall be disabled. + +###### a.3) E-side cable model + +The E-side cable model (DPBOESCM) configuration parameter specifies a cable model in terms of three scalars DPBOESCMA, DPBOESCMB and DPBOESCMC that shall be used to describe the frequency dependent loss of E-side cables using the formula: + +$$\text{ESCM}(f) = \left( \text{DPBOESCM}_A + \text{DPBOESCM}_B \cdot \sqrt{f} + \text{DPBOESCM}_C \cdot f \right) \cdot \text{DPBOESEL}$$ + +where ESCM is expressed in decibels and $f$ is expressed in megahertz. Parameters DPBOESCMA, DPBOESCMB, DPBOESCMC shall be coded as unsigned integers representing a scalar value from -1 to 1.5 in steps of $2^{-8}$ . All values in the range are valid. + +###### a.4) Minimum usable signal + +The minimum usable signal (DPBOMUS) determines the assumed minimum usable receive PSD mask, in decibels with reference to 1 mW per hertz, for exchange based services, used to modify parameter DPBOFMAX specified in a.6). It shall be coded as an unsigned integer representing a PSD mask level from 0 dBm/Hz to -127.5 dBm/Hz in steps of 0.5 dB. All values in the range are valid. + +NOTE – The PSD mask level is 3.5 dB above the signal PSD level. + +###### *a.5) DPBO span minimum frequency* + +The DPBO span minimum frequency (DPBOFMIN) determines the minimum frequency from which the DPBO shall be applied. It ranges from 0 kHz to 883 2 kHz in steps of 4.312 5 kHz. + +###### *a.6) DPBO span maximum frequency* + +The DPBO span maximum frequency (DPBOFMAX) determines the maximum frequency at which DPBO may be applied. It ranges from 138 kHz to 35 323.687 5 kHz in steps of 4.312 5 kHz. + +###### **b) Downstream power back-off variables derived from PDMASKds** + +These variables are not directly accessible through the Q-interface and shall be derived in the AN from the PSDMASKds parameter. + +###### *b.1) DPBO maximum PSD mask* + +If the set of breakpoints determining PSDMASKds ( $t_i$ , $PSD_i$ ) are monotonic in frequency, i.e., $t_i \leq t_{i+1}$ for $0 < i \leq 32$ , then $DPBOPSDMASKds = PSDMASKds$ . + +If there exists in the set of breakpoints PSDMASKds ( $t_i$ , $PSD_i$ ) a single violation of monotonic frequency sequence, i.e., $t_d > t_{d+1}$ , then the DPBO maximum PSD mask, $DPBOPSDMASKds = PSDMASKds (t_i, PSD_i)$ , $0 < i \leq d$ . + +###### *b.2) DPBO low frequency override* + +The DPBO low frequency override (DPBOLFO) parameter determines the PSD mask that overrides DPBO at low frequencies. If there exists in the set of breakpoints PSDMASKds ( $t_i$ , $PSD_i$ ) a single violation of monotonic frequency sequence, i.e., $t_d > t_{d+1}$ , then $DPBOLFO = PSDMASKds (t_i, PSD_i)$ , $d < i \leq 32$ . Otherwise, $DPBOLFO$ shall be assumed to be $-91.5$ dBm/Hz or less everywhere. + +###### **c) Procedure to derive the modified downstream power spectral density mask** + +From the parameters defined in section b) and the PSDMASKds, a modified PSD mask after DPBO shall be derived using the following method: + +- The predicted attenuated exchange PSD mask ( $PEPSD(f)$ ) is determined by: + +$$PEPSD(f) = DPBOEPSD(f) - (DPBOESCMA + DPBOESCM B \cdot \sqrt{f} + DPBOESCM C \cdot f) \cdot DPBOESEL$$ + +- The maximum usable frequency (MUF) is defined as the highest frequency for which the $PEPSD(f)$ is greater than $DPBOMUS$ . +- The minimum PSD mask, $DPBOMPSD(f)$ , is defined between frequencies $DPBOFMIN$ and $F_1 = \min(DPBOFMAX, MUF)$ as: + +$$DPBOMPSD(f) = \begin{cases} \max[DPBOLFO(f), -91.5] \text{ dBm/Hz} & \text{for } f \leq F_1 - 175 \text{ kHz} \\ \max[DPBOLFO(f), \frac{11.5}{175}(f - F_1) - 80] \text{ dBm/Hz} & \text{for } F_1 - 175 \text{ kHz} < f < F_1 \end{cases}$$ + +where $f$ is expressed in kilohertz. + +- The DPBO is applied so that at each frequency the resultant PSD mask is equal to: + +$$RESULTMASKds(f) = \begin{cases} \max[\min(DPBOPSDMASKds(f), PEPSD(f)), DPBOMPSD(f)] & \text{DPBOFMIN} \leq f \leq F_1 \\ DPBOPSDMASKds(f) & \text{Otherwise} \end{cases}$$ + +- Finally, a modified PSD mask shall be set as close as possible to, but everywhere less than, the $RESULTMASKds$ . This mask shall comply with the constraints of the relevant Recommendations. Its computation is vendor discretionary. This modified mask is applied to the xTU-C. + +##### 7.3.1.2.14 Upstream power back-off shaped (UPBOSHAPED) + +Upstream power back-off (UPBO) is specified in [ITU-T G.993.2] to provide spectral compatibility between loops of different lengths deployed in the same binder. The upstream transmit PSD mask, UPBOMASKus, is specified in clause 7.2.1.3.2 of [ITU-T G.993.2]. + +The ITU-T G.993.2 UPBO configuration parameters $a$ , $b$ , and the reference electrical lengths $kl_{0\_REF}$ shall be set by the NMS in the CO-MIB. The parameter $kl_0$ may be determined during initialization by the VTUs or forced by the CO-MIB. + +###### a) Upstream power back-off configuration parameters + +###### a.1) Upstream power back-off reference PSD per band + +The upstream power back-off reference PSD per band (UPBOPSD-pb) parameter defines the UPBO reference PSD used to compute the upstream power back-off for each upstream band except US0. A UPBOPSD defined for each band shall consist of two parameters $[a, b]$ . Parameter $a$ ranges from 40 dBm/Hz to 80.95 dBm/Hz in steps of 0.01 dBm/Hz; and parameter $b$ ranges from 0 dB/Hz to 40.95 dBm/Hz in steps of 0.01 dBm/Hz. The UPBO reference PSD at the frequency $f$ expressed in megahertz shall be equal to $-a - b\sqrt{f}$ . The set of parameter values $a = 40$ dBm/Hz, $b = 0$ dBm/Hz is a special configuration to disable UPBO in the respective upstream band. + +###### a.2) Upstream electrical length + +The upstream electrical length (UPBOKL) parameter defines the electrical length expressed in decibels at 1 MHz, $kl_0$ , configured by the CO-MIB. The value ranges from 0 dB to 128 dB in steps of 0.1 dB. + +###### a.3) Force CO-MIB electrical length + +The force CO-MIB electrical length (UPBOKLF) parameter is a flag that forces the VTU-R to use the electrical length of the CO-MIB (UPBOKL) to compute the UPBO. The value shall be forced if the flag is set to 1. Otherwise, the VTUs shall determine the electrical length. + +###### a.4) UPBO reference electrical length per band + +The UPBO reference electrical length per band (UPBOKLREF-pb) parameter determines the UPBO reference electrical length used to compute the upstream power back-off for each upstream band except US0, for the optional equalized far-end crosstalk (FEXT) UPBO method. The value ranges from 1.8 dB to 63.5 dB in steps of 0.1 dB with special value 0. The use of the special value 0 is described in clause 7.2.1.3.2 of [ITU-T G.993.2]. + +###### a.5) Alternative electrical length estimation mode + +The alternative electrical length estimation mode (AELE-MODE) parameter determines the UPBO electrical length estimation mode to be used in the alternative electrical length estimation method (ELE-M1) in clause 7.2.1.3.2.2 of [ITU-T G.993.2]. The value of this parameter is 0, 1, 2 or 3. + +###### a.6) UPBO electrical length threshold percentile + +The UPBO electrical length threshold percentile (UPBOELMT) parameter determines the UPBO electrical length minimum threshold percentile, in per cent, used in the alternative electrical length estimation method (ELE-M1) in clause 7.2.1.3.2.2 of [ITU-T G.993.2]. It is set by network management via the CO-MIB. The parameter ranges from 0% to 15% in steps of 1%. This value is communicated to the VTU-R in accordance with [ITU-T G.994.1] at start-up. + +##### 7.3.1.2.15 VDSL2 power spectral density mask class selection (CLASSMASK) + +In order to reduce the number of configuration possibilities, the limit PSD masks are grouped into the following PSD mask classes: + +- class 998-30 Annex A of [ITU-T G.993.2]: D-32, D-48, D-64, D-128 + +- class 998-35b Annex A of [ITU-T G.993.2]: D-32, D-48, D-64, D-128 +- class 997-M1c Annex B of [ITU-T G.993.2]: 997-M1c-A-7 +- class 997-M1x Annex B of [ITU-T G.993.2]: 997-M1x-M +- class 997-M2x Annex B of [ITU-T G.993.2]: 997E17-M2x-A, 997E30-M2x-NUS0 +- class 998-M2x Annex B of [ITU-T G.993.2]: 998-M2x-A, 998-M2x-M, 998-M2x-B, 998-M2x-NUS0, 998E17-M2x-NUS0, 998E17-M2x-NUS0-M, 998E30-M2x-NUS0, 998E30-M2x-NUS0-M, 998E17-M2x-A +- class 998ADE-M2x Annex B of [ITU-T G.993.2]: 998-M2x-A, 998-M2x-M, 998-M2x-B, 998-M2x-NUS0, 998ADE17-M2x-A, 998ADE17-M2x-B, 998ADE17-M2x-M, 998ADE17-M2x-NUS0-M, 998ADE30-M2x-NUS0-A, 998ADE30-M2x-NUS0-M +- class 998-B Annex C of [ITU-T G.993.2]: POTS-138b, POTS-276b (clause C.2.1.1 of [ITU-T G.993.2]), TCM-ISDN (clause C.2.1.2 of [ITU-T G.993.2]) +- class 998-CO Annex C of [ITU-T G.993.2]: POTS-138co, POTS-276co (clause C.2.1.1 of [ITU-T G.993.2]) +- class 998E35-M2x Annex B of [ITU-T G.993.2]: 998-M2x-A, 998-M2x-M, 998-M2x-B, 998-M2x-NUS0, 998E17-M2x-NUS0, 998E17-M2x-NUS0-M, 998E17-M2x-A, 998E35-M2x-A +- class 998ADE35-M2x Annex B of [ITU-T G.993.2]: 998-M2x-A, 998-M2x-M, 998-M2x-B, 998-M2x-NUS0, 998ADE17-M2x-A, 998ADE17-M2x-B, 998ADE17-M2x-M, 998ADE17-M2x-NUS0-M, 998ADE35-M2x-A, 998ADE35-M2x-B, 998ADE35-M2x-M +- class CN-M2x Annex N of [ITU-T G.993.2]: CN17-M2x-A, CN17-M2x-B, CN17-M2x-M, CN17-M2x-NUS0-M, CN35-M2x-A, CN35-M2x-B, CN35-M2x-M, CN35-M2x-NUS0-M + +Each class is designed such that the PSD levels of each limit PSD mask of a specific class are equal in their respective passband above 552 kHz. + +One CLASSMASK parameter is determined from the relevant annex of [ITU-T G.993.2] enabled in the XTSE. It selects a single PSD mask class per the relevant annex of [ITU-T G.993.2] that is activated at the VTU-O. The coding is as indicated in Table 7-6. + +**Table 7-6 – Determination of values of CLASSMASK from the relevant annex of [ITU-T G.993.2]** + +| Parameter value | Annex A of [ITU-T G.993.2] | Annex B of [ITU-T G.993.2] | Annex C of [ITU-T G.993.2] | Annex N of [ITU-T G.993.2] | +|-----------------|----------------------------|----------------------------|----------------------------|----------------------------| +| 1 | 998-30 | 997-M1c | 998-B | CN-M2x | +| 2 | 998-35b | 997-M1x | 998-CO | | +| 3 | | 997-M2x | | | +| 4 | | | | | +| 5 | | 998-M2x | | | +| 6 | | 998ADE-M2x | | | +| 7 | | | | | +| 8 | | 998E35-M2x | | | +| 9 | | 998ADE35-M2x | | | + +NOTE – A single PSD mask class shall be selected from the relevant annex of [ITU-T G.993.2]. + +##### **7.3.1.2.16 VDSL2 limit power spectral density masks and band plans enabling** + +The VDSL2 limit PSD masks and band plans enabling (LIMITMASK) configuration parameter contains the ITU-T G.993.2 limit PSD masks of the selected PSD mask class, enabled by the near-end xTU on this line for each class of profiles. One LIMITMASK parameter is determined from the relevant annex of [ITU-T G.993.2] enabled in the XTSE. + +The profiles are grouped in the following profile classes: + +- class 8: profiles 8a, 8b, 8c, 8d +- class 12: profiles 12a, 12b +- class 17: profile 17a +- class 30: profile 30a +- class 35: profile 35b + +For each profile class, several limit PSD masks of the selected PSD mask class (CLASSMASK) may be enabled. The enabling parameter is coded in a bit-map representation (0 if the associated mask is not allowed, 1 if it is allowed). + +The parameter has the bit definitions for each PSD mask class as indicated in Table 7-7. + +**Table 7-7 – Determination of bits of LIMITMASK for each CLASSMASK from the relevant annex of [ITU-T G.993.2]** + +| Bit number | Profile class | PSD mask classes | | | | | | | | | | | | +|----------------|---------------|------------------|---------|----------|------------|---------|---------|---------|------------|--------------|-----------|------------|---------------| +| | | Annex A | | Annex B | | | | | | | Annex C | | Annex N | +| | | 998-30 | 998-35b | 998-M2x | 998ADE-M2x | 997-M1x | 997-M1c | 997-M2x | 998E35-M2x | 998ADE35-M2x | 998-B | 998-CO | CN-M2x | +| Octet 1 | | | | | | | | | | | | | | +| 1 | 8 | D-32 | D-32 | M2x-A | M2x-A | | M1c-A-7 | | M2x-A | M2x-A | POTS-138b | POTS_138co | CN17-M2x-A | +| 2 | 8 | D-48 | D-48 | M2x-B | M2x-B | | | | M2x-B | M2x-B | TCM-ISDN | POTS_276co | CN17-M2x-B | +| 3 | 8 | | | M2x-M | M2x-M | M1x-M | | | M2x-M | M2x-M | POTS_276b | | CN17-M2x-M | +| 4 | 8 | | | M2x-NUS0 | M2x-NUS0 | | | | M2x-NUS0 | M2x-NUS0 | | | CN17-M2x-NUS0 | +| 5 | 8 | | | | | | | | | | | | | +| 6 | 8 | | | | | | | | | | | | | +| 7 | 8 | | | | | | | | | | | | | +| 8 | 8 | | | | | | | | | | | | | +| Octet 2 | | | | | | | | | | | | | | +| 1 | 8 | D-64 | D-64 | | | | | | | | | | | +| 2 | 8 | D-128 | D-128 | | | | | | | | | | | +| 3 | 8 | | | | | | | | | | | | | +| 4 | 8 | | | | | | | | | | | | | +| 5 | 8 | | | | | | | | | | | | | +| 6 | 8 | | | | | | | | | | | | | +| 7 | 8 | | | | | | | | | | | | | +| 8 | 8 | | | | | | | | | | | | | + +**Table 7-7 – Determination of bits of LIMITMASK for each CLASSMASK from the relevant annex of [ITU-T G.993.2]** + +| Bit number | Profile class | PSD mask classes | | | | | | | | | | | | +|----------------|---------------|------------------|---------|----------|------------|---------|---------|---------|------------|--------------|-----------|-------------|---------------| +| | | Annex A | | Annex B | | | | | | | Annex C | | Annex N | +| | | 998-30 | 998-35b | 998-M2x | 998ADE-M2x | 997-M1x | 997-M1c | 997-M2x | 998E35-M2x | 998ADE35-M2x | 998-B | 998-CO | CN-M2x | +| Octet 3 | | | | | | | | | | | | | | +| 1 | 12 | D-32 | D-32 | M2x-A | M2x-A | | | | M2x-A | M2x-A | POTS-138b | POTS_ 138co | CN17-M2x-A | +| 2 | 12 | D-48 | D-48 | M2x-B | M2x-B | | | | M2x-B | M2x-B | TCM-ISDN | POTS_ 276co | CN17-M2x-B | +| 3 | 12 | | | M2x-M | M2x-M | M1x-M | | | M2x-M | M2x-M | POTS_276b | | CN17-M2x-M | +| 4 | 12 | | | M2x-NUS0 | M2x-NUS0 | | | | M2x-NUS0 | M2x-NUS0 | | | CN17-M2x-NUS0 | +| 5 | 12 | | | | | | | | | | | | | +| 6 | 12 | | | | | | | | | | | | | +| 7 | 12 | | | | | | | | | | | | | +| 8 | 12 | | | | | | | | | | | | | +| Octet 4 | | | | | | | | | | | | | | +| 1 | 12 | D-64 | D-64 | | | | | | | | | | | +| 2 | 12 | D-128 | D-128 | | | | | | | | | | | +| 3 | 12 | | | | | | | | | | | | | +| 4 | 12 | | | | | | | | | | | | | +| 5 | 12 | | | | | | | | | | | | | +| 6 | 12 | | | | | | | | | | | | | +| 7 | 12 | | | | | | | | | | | | | +| 8 | 12 | | | | | | | | | | | | | + +**Table 7-7 – Determination of bits of LIMITMASK for each CLASSMASK from the relevant annex of [ITU-T G.993.2]** + +| Bit number | Profile class | PSD mask classes | | | | | | | | | | | | +|----------------|---------------|------------------|---------|----------------|------------------|---------|---------|-----------|----------------|------------------|-----------|--------|---------------| +| | | Annex A | | Annex B | | | | | | | Annex C | | Annex N | +| | | 998-30 | 998-35b | 998-M2x | 998ADE-M2x | 997-M1x | 997-M1c | 997-M2x | 998E35-M2x | 998ADE35-M2x | 998-B | 998-CO | CN-M2x | +| Octet 5 | | | | | | | | | | | | | | +| 1 | 17 | D-32 | D-32 | E17-M2x-NUS0 | ADE17-M2x-A | | | E17-M2x-A | E17-M2x-NUS0 | ADE17-M2x-A | POTS-138b | | CN17-M2x-A | +| 2 | 17 | D-48 | D-48 | E17-M2x-NUS0-M | ADE17-M2x-B | | | | E17-M2x-NUS0-M | ADE17-M2x-B | TCM-ISDN | | CN17-M2x-B | +| 3 | 17 | | | E17-M2x-A | ADE17-M2x-NUS0-M | | | | E17-M2x-A | ADE17-M2x-NUS0-M | POTS_276b | | CN17-M2x-M | +| 4 | 17 | | | | ADE17-M2x-M | | | | | ADE17-M2x-M | | | CN17-M2x-NUS0 | +| 5 | 17 | | | | | | | | | | | | | +| 6 | 17 | | | | | | | | | | | | | +| 7 | 17 | | | | | | | | | | | | | +| 8 | 17 | | | | | | | | | | | | | +| Octet 6 | | | | | | | | | | | | | | +| 1 | 17 | D-64 | D-64 | | | | | | | | | | | +| 2 | 17 | D-128 | D-128 | | | | | | | | | | | +| 3 | 17 | | | | | | | | | | | | | +| 4 | 17 | | | | | | | | | | | | | +| 5 | 17 | | | | | | | | | | | | | +| 6 | 17 | | | | | | | | | | | | | +| 7 | 17 | | | | | | | | | | | | | +| 8 | 17 | | | | | | | | | | | | | + +**Table 7-7 – Determination of bits of LIMITMASK for each CLASSMASK from the relevant annex of [ITU-T G.993.2]** + +| Bit
number | Profile
class | PSD mask classes | | | | | | | | | | | | +|----------------|------------------|------------------|---------|------------------------|--------------------------|---------|---------|----------------------|------------|------------------|-----------|--------|---------| +| | | Annex A | | Annex B | | | | | | | Annex C | | Annex N | +| | | 998-30 | 998-35b | 998-M2x | 998ADE-
M2x | 997-M1x | 997-M1c | 997-M2x | 998E35-M2x | 998ADE35-
M2x | 998-B | 998-CO | CN-M2x | +| Octet 7 | | | | | | | | | | | | | | +| 1 | 30 | D-32 | | E30-
M2x-
NUS0 | ADE30-
M2x-
NUS0-A | | | E30-
M2x-
NUS0 | | | POTS-138b | | | +| 2 | 30 | D-48 | | E30-
M2x-
NUS0-M | ADE30-
M2x-
NUS0-M | | | | | | TCM-ISDN | | | +| 3 | 30 | | | | | | | | | | POTS_276b | | | +| 4 | 30 | | | | | | | | | | | | | +| 5 | 30 | | | | | | | | | | | | | +| 6 | 30 | | | | | | | | | | | | | +| 7 | 30 | | | | | | | | | | | | | +| 8 | 30 | | | | | | | | | | | | | +| Octet 8 | | | | | | | | | | | | | | +| 1 | 30 | D-64 | | | | | | | | | | | | +| 2 | 30 | D-128 | | | | | | | | | | | | +| 3 | 30 | | | | | | | | | | | | | +| 4 | 30 | | | | | | | | | | | | | +| 5 | 30 | | | | | | | | | | | | | +| 6 | 30 | | | | | | | | | | | | | +| 7 | 30 | | | | | | | | | | | | | +| 8 | 30 | | | | | | | | | | | | | + +**Table 7-7 – Determination of bits of LIMITMASK for each CLASSMASK from the relevant annex of [ITU-T G.993.2]** + +| Bit number | Profile class | PSD mask classes | | | | | | | | | | | | +|-------------------------------------------------|---------------|------------------|---------|---------|------------|---------|---------|---------|------------|--------------|---------|--------|---------------| +| | | Annex A | | Annex B | | | | | | | Annex C | | Annex N | +| | | 998-30 | 998-35b | 998-M2x | 998ADE-M2x | 997-M1x | 997-M1c | 997-M2x | 998E35-M2x | 998ADE35-M2x | 998-B | 998-CO | CN-M2x | +| Octet 9 | | | | | | | | | | | | | | +| 1 | 35 | | D-32 | | | | | | E35-M2x-A | ADE35-M2x-A | | | CN35-M2x-A | +| 2 | 35 | | D-48 | | | | | | | ADE35-M2x-B | | | CN35-M2x-B | +| 3 | 35 | | D-64 | | | | | | | ADE35-M2x-M | | | CN35-M2x-M | +| 4 | 35 | | D-128 | | | | | | | | | | CN35-M2x-NUS0 | +| 5 | 35 | | | | | | | | | | | | | +| 6 | 35 | | | | | | | | | | | | | +| 7 | 35 | | | | | | | | | | | | | +| 8 | 35 | | | | | | | | | | | | | +| NOTE – All unassigned bits are reserved by ITU. | | | | | | | | | | | | | | + +##### 7.3.1.2.17 VDSL2 US0 disabling + +The VDSL2 US0 disabling (US0DISABLE) configuration parameter indicates whether the use of US0 is disabled for each limit PSD mask enabled in the LIMITMASK parameter. One US0DISABLE parameter is specified per the relevant Annex of [ITU-T G.993.2] enabled in the XTSE. + +For each limit PSD mask enabled in the LIMITMASK parameter, a bit shall indicate whether US0 is disabled. The disabling parameter is coded as a bit-map. The bit is set to 1 if US0 is disabled for the associated limit mask. The bit-map has the same structure as the LIMITMASK parameter. + +##### 7.3.1.2.18 VDSL2 US0 PSD mask + +The VDSL2 US0 PSD mask (US0MASK) parameter contains the US0 PSD masks to be allowed by the near-end xTU on the line. This parameter is only specified for Annex A of [ITU-T G.993.2]. It is represented as a bitmap (0 if not allowed and 1 if allowed) with the definitions of Table 7-8. + +**Table 7-8 – Specification of bits of US0MASK for Annex A of [ITU-T G.993.2]** + +| Bit | Annex A of [ITU-T G.993.2] US0MASK | +|----------------|------------------------------------| +| Octet 1 | | +| 1 | EU-32 | +| 2 | EU-36 | +| 3 | EU-40 | +| 4 | EU-44 | +| 5 | EU-48 | +| 6 | EU-52 | +| 7 | EU-56 | +| 8 | EU-60 | +| Octet 2 | | +| 1 | EU-64 | +| 2 | EU-128 | +| 3 | reserved by ITU | +| 4 | reserved by ITU | +| 5 | reserved by ITU | +| 6 | reserved by ITU | +| 7 | reserved by ITU | +| 8 | reserved by ITU | +| Octet 3 | | +| 1 | ADLU-32 | +| 2 | ADLU-36 | +| 3 | ADLU-40 | +| 4 | ADLU-44 | +| 5 | ADLU-48 | +| 6 | ADLU-52 | +| 7 | ADLU-56 | +| 8 | ADLU-60 | + +**Table 7-8 – Specification of bits of US0MASK for Annex A of [ITU-T G.993.2]** + +| Bit | Annex A of [ITU-T G.993.2] US0MASK | +|----------------|------------------------------------| +| Octet 4 | | +| 9 | ADLU-64 | +| 10 | ADLU-128 | +| 11 | reserved by ITU | +| 12 | reserved by ITU | +| 13 | reserved by ITU | +| 14 | reserved by ITU | +| 15 | reserved by ITU | +| 16 | reserved by ITU | + +NOTE 1 – Valid combinations of US0MASK and LIMITMASK are described in [ITU-T G.993.2]. +NOTE 2 – More than one mask may be enabled simultaneously. If no US0 PSD masks are enabled, the line is configured without US0 support. + +#### 7.3.1.3 Noise margin configuration parameters + +The configuration parameters in clauses 7.3.1.3.1 to 7.3.1.3.6 are specified to control the noise margin in the receive direction in the xTU. A downstream noise margin applies to the xTU-R, an upstream noise margin applies to the xTU-C. + +NOTE – The noise margin should be controlled to ensure operation at the target bit error ratio (BER) for each of the received bearer channels, or better. Figure 7-3 shows the relationship between these parameters. + +![](68a5a1a1a761c652b4b4c56da7cf9914_img.jpg) + +| | | +|------------------------|------------------------------------------------------------------------------------------------------------------| +| Maximum noise margin | Reduce transmit power
-----
Increase data rate if noise margin > Upshift noise margin for upshift interval | +| Upshift noise margin | -----
Steady state operation | +| Target noise margin | -----
Steady state operation | +| Downshift noise margin | -----
Decrease data rate if noise margin < Downshift noise margin for downshift interval | +| Minimum noise margin | -----
Increase transmit power. If not possible – reinitialize | + +G.997.1(19)\_F7-3 + +NOTE 1 – Upshift noise margin, and downshift noise margin are only supported for rate adaptive mode. + +NOTE 2 – Minimum noise margin $\leq$ Downshift noise margin $\leq$ Target noise margin $\leq$ Upshift noise margin $\leq$ Maximum noise margin. + +**Figure 7-3 – Noise margins** + +##### 7.3.1.3.1 Downstream target noise margin + +The downstream target noise margin (TARSNRMs) is the noise margin that the xTU-R receiver shall achieve, relative to the BER requirement for each of the downstream bearer channels, or better, to successfully complete initialization. The target noise margin ranges from 0 dB to 31 dB, with 0.1 dB steps. + +##### **7.3.1.3.2 Upstream target noise margin** + +The upstream target noise margin (TARSNRMus) is the noise margin that the xTU-C receiver shall achieve, relative to the BER requirement for each of the upstream bearer channels, or better, to successfully complete initialization. The target noise margin ranges from 0 dB to 31 dB, with 0.1 dB steps. + +##### **7.3.1.3.3 Downstream maximum noise margin** + +The downstream maximum noise margin (MAXSNRMds) is the maximum noise margin the xTU-R receiver shall try to sustain. If the noise margin is above this level, the xTU-R shall request the xTU-C to reduce the xTU-C transmit power to get a noise margin below this limit (if this functionality is supported by the relevant DSL Recommendation – see Note 1). The maximum noise margin ranges from 0 dB to 31 dB with 0.1 dB steps. A special value is used to indicate that reduction in transmit power is not required for the purpose of reducing the noise margin below the maximum noise margin limit (i.e., the maximum noise margin value is infinite). + +NOTE 1 – This functionality should be supported by ADSL transmission systems. This functionality is supported by ADSL2 transmission systems. + +NOTE 2 – The transmit power may be reduced for other reasons. + +##### **7.3.1.3.4 Upstream maximum noise margin** + +The upstream maximum noise margin (MAXSNRMus) is the maximum noise margin the xTU-C receiver shall try to sustain. If the noise margin is above this level, the xTU-C shall request the xTU-R to reduce the xTU-R transmit power to get a noise margin that is below this limit (if this functionality is supported by the relevant DSL Recommendation – see Note 1). The maximum noise margin ranges from 0 dB to 31 dB, with 0.1 dB steps. A special value is used to indicate that reduction in transmit power is not required for the purpose of reducing the noise margin below the maximum noise margin limit (i.e., the maximum noise margin value is infinite). + +NOTE 1 – This functionality should be supported by ADSL transmission systems. This functionality is supported by ADSL2 transmission systems. + +NOTE 2 – The transmit power may be reduced for other reasons. + +##### **7.3.1.3.5 Downstream minimum noise margin** + +The downstream minimum noise margin (MINSNRMds) is the minimum noise margin the xTU-R receiver shall tolerate. If the noise margin falls below this level, the xTU-R shall request the xTU-C to increase the xTU-C transmit power. If an increase to xTU-C transmit power is not possible, a loss of margin (LOM) defect occurs, the xTU-R shall fail and attempt to re-initialize and the NMS shall be notified. The minimum noise margin ranges from 0 dB to 31 dB, with 0.1 dB steps. + +##### **7.3.1.3.6 Upstream minimum noise margin** + +The upstream minimum noise margin (MINSNRMus) is the minimum noise margin the xTU-C receiver shall tolerate. If the noise margin falls below this level, the xTU-C shall request the xTU-R to increase the xTU-R transmit power. If an increase of xTU-R transmit power is not possible, a loss of margin (LOM) defect occurs, the xTU-C shall fail and attempt to re-initialize and the NMS shall be notified. The minimum noise margin ranges from 0 dB to 31 dB, with 0.1 dB steps. + +#### **7.3.1.4 Rate adaptation configuration parameters** + +The configuration parameters in clauses 7.3.1.4.1 to 7.3.1.4.10 are specified to manage the rate-adaptive behaviour in the transmit direction for both the xTU-C and the xTU-R. An xTU-C rate adaptation mode applies to the upstream direction. An xTU-R rate adaptation mode applies to the downstream direction. + +##### 7.3.1.4.1 Downstream rate adaptation mode + +The downstream rate adaptation mode (RA-MODEds) parameter specifies the mode of operation of a rate-adaptive xTU-C in the transmit direction. The parameter can take four values: mode 1, 2, 3 or 4. + +NOTE 1 – Modes 1 and 2 both are mandatory modes. The commonality between modes 1 and 2 is that both are characterized by a constant data rate in showtime. The difference between modes 1 and 2 is that mode 1 fixes this data rate at the configured minimum data rate, whereas with mode 2 forces the modem subsystem to fix the data rate within the range determined by the configured minimum and maximum data rates. In the case of ITU-T G.998.4 operation, the "data rate" is replaced in this Note by "expected throughput (ETR)". + +**Mode 1:** MANUAL – Data rate/ETR changed manually. + +Support of this mode is mandatory. + +###### 7.3.1.4.1.1 If ITU-T G.998.4 retransmission is not used in the downstream direction + +The downstream minimum data rate parameter (see clause 7.3.2.1.1) specifies the exact data rate the xTU-C transmitter shall operate at for each of the bearer channels. + +NOTE 2 – The downstream minimum data rate parameter value shall override the configured maximum data rate parameter value (see clause 7.3.2.1.3). + +Although the xTU-C and the line might be able to support a higher data rate, the xTU-C shall not transmit a higher data rate than that requested for each of the bearer channels. + +*At startup* + +- a) For [ITU-T G.992.1] and [ITU-T G.992.2], the channel initialization policy is defined in this paragraph. The ATUs shall initialize with a downstream noise margin that is at least as large as the specified downstream target noise margin, TARSNRMds (see clause 7.3.1.3.1), relative to the required BER for each of the downstream bearer channels, or better. + +If the xTU-C fails to achieve the downstream minimum data rate for one of the bearer channels, the xTU-C will fail to initialize, and the NMS is notified. + +- b) For operational modes other than [ITU-T G.992.1] or [ITU-T G.992.2], the channel initialization policy is defined in the relevant Recommendation and controlled by the CIPOLICY parameter (see clause 7.3.2.10). + +*At showtime* + +The xTU-C transmitter shall maintain the specified downstream minimum data rate for each bearer channel. + +###### 7.3.1.4.1.2 If ITU-T G.998.4 retransmission is used in the downstream direction + +The downstream MINETR\_RTX parameter (see clause 7.3.2.1.8) specifies the exact ETR the xTU-C transmitter shall operate at. + +NOTE 3 – The downstream MINETR\_RTX parameter value shall override the configured downstream MAXETR\_RTX parameter value (see clause 7.3.2.1.9). + +*At startup* + +The channel initialization policy is specified in clause 11.5 of [ITU-T G.998.4]. + +*At showtime* + +The xTU-C transmitter shall maintain the specified downstream minimum ETR. + +**Mode 2:** AT\_INIT – Data rate/ETR automatically selected at startup only and does not change after that. + +Support of this mode is mandatory. + +###### 7.3.1.4.1.3 If ITU-T G.998.4 retransmission is not used in the downstream direction + +The downstream minimum data rate parameter (see clause 7.3.2.1.1) and downstream maximum data rate parameter (see clause 7.3.2.1.3) specify the data rate range within which the xTU-C transmitter shall operate at for each of the bearer channels. The data rate is determined during initialization and remains constant during the subsequent showtime phase. + +###### *At startup* + +- a) For [ITU-T G.992.1] and [ITU-T G.992.2], the channel initialization policy is defined in this paragraph. The ATUs shall initialize at a downstream data rate in the range between minimum data rate and maximum data rate and with a downstream noise margin that is at least as large as the specified downstream target noise margin, TARSNRMds (see clause 7.3.1.3.1), relative to the required BER for each of the bearer channels, or better. If the xTU-C fails to achieve the downstream minimum data rate for one of the bearer channels, the xTU-C will fail to initialize, and the NMS is notified. + +If the xTU-C transmitter is able to support a higher downstream data rate at initialization, the excess data rate will be distributed amongst the downstream bearer channels according to the ratio (0% to 100%) specified by the rate adaptation ratio parameter for each bearer channel (adding up to 100% over all bearer channels). When the downstream maximum data rate is achieved in one of the bearer channels, then the remaining excess bit rate is assigned to the other bearer channels, still according to their relative rate adaptation ratio parameters. + +As long as the downstream data rate is below the downstream maximum data rate for one of the bearer channels, data rate increase shall take priority over transmit power reduction. + +- b) For operational modes other than [ITU-T G.992.1] or [ITU-T G.992.2], the channel initialization policy is defined in the relevant Recommendation and controlled by the CIPOLICY parameter (see clause 7.3.2.10). + +###### *At showtime* + +During showtime, no downstream data rate adaptation is allowed. The downstream data rate selected during initialization for each of the bearer channels shall be maintained. + +###### 7.3.1.4.1.4 If ITU-T G.998.4 retransmission is used in the downstream direction + +The downstream MINETR\_RTX parameter (see clause 7.3.2.1.8) and downstream MAXETR\_RTX parameter (see clause 7.3.2.1.9) specify the range of the ETR within which the xTU-C transmitter shall operate. + +The ETR is determined during initialization and remains constant during the subsequent showtime phase. + +###### *At startup* + +The channel initialization policy is defined in [ITU-T G.998.4] (see clause 11.5 of [ITU-T G.998.4]). + +###### *At showtime* + +During showtime, no downstream data rate adaptation is allowed. The downstream ETR, which has been selected during initialization, shall be maintained. + +**Mode 3: DYNAMIC** – Data rate/ETR is automatically selected at initialization and is continuously adapted during operation (showtime). The DYNAMIC rate adaptation mode is optional. All related configuration parameters are also optional. + +###### 7.3.1.4.1.5 If ITU-T G.998.4 retransmission is not used in the downstream direction + +###### *At startup* + +In mode 3, the xTU-C shall start up as in mode 2. + +###### *At showtime* + +###### - *Rate range* + +During showtime, rate adaptation is allowed with respect to the rate adaptation ratio for distributing the excess data rate amongst the bearer channels (see mode 2), and assuring that the downstream minimum data rate remains available at the required BER for each of the bearer channels or better. The downstream data rate can vary between the downstream minimum data rate, and the downstream maximum data rate. + +###### - *Procedure* + +SRA may be performed, when the conditions specified by the SRA trigger parameters are satisfied. + +If operating in ITU-T G.992.3 or ITU-T G.992.5, the detailed SRA on-line reconfiguration (OLR) procedure is specified [ITU-T G.992.3] with trigger conditions specified as follows. + +Downstream rate adaptation is performed when the conditions specified for downstream upshift noise margin and downstream upshift interval – or for downstream downshift noise margin and downstream downshift interval – are satisfied. This means: + +- For an upshift action: Allowed when the downstream noise margin is above the downstream upshift noise margin during downstream minimum time interval for upshift rate adaptation (i.e., upon RAU anomaly – see [ITU-T G.992.3]). +- For a downshift action: Allowed when the downstream noise margin is below the downstream downshift noise margin during downstream minimum time interval for downshift rate adaptation (i.e., upon RAD anomaly – see [ITU-T G.992.3]). + +As long as the downstream data rate is below the downstream maximum data rate for one of the bearer channels, data rate increase shall take priority over transmit power reduction. + +If operating in accordance with [ITU-T G.993.2], the detailed SRA OLR procedure and the trigger conditions are specified in [ITU-T G.993.2]. As long as the downstream data rate is below the downstream maximum data rate for one of the bearer channels, data rate increase shall take priority over transmit power reduction. + +###### - *Fallback* + +If in [ITU-T G.993.2], it is detected at startup that SRA is not supported in the downstream direction by either XTU, the XTUs shall fallback to mode 2. This shall be reported by the downstream actual rate adaptation mode parameter, ACT-RA-MODEds (see clause 7.5.1.33.1). + +###### 7.3.1.4.1.6 In case ITU-T G.998.4 retransmission is used in the downstream direction + +###### - *At startup* + +In mode 3, the xTU-C shall start up as in mode 2. + +###### - *At showtime* + +SRA OLR procedures are defined in [ITU-T G.998.4]. + +###### - *Rate range* + +The downstream MINETR\_RTX parameter (see clause 7.3.2.1.8) and downstream MAXETR\_RTX parameter (see clause 7.3.2.1.9) specify the range of the ETR within which the xTU-C transmitter shall operate. The ETR is determined during initialization and updated in showtime upon OLR. + +If ETR reaches its maximum value MAXETR\_RTX, the NDR may be further increased without increasing the ETR. The downstream MAXNDR\_RTX parameter (see clause 7.3.2.1.10) specifies maximum allowed value for the net data rate (NDR), within which the xTU-C transmitter shall operate. The NDR is determined during initialization and updated in showtime upon OLR. + +###### - *Procedure* + +SRA may be performed, when the conditions specified by the SRA trigger parameters are satisfied. + +If operating in accordance with [ITU-T G.992.3] or [ITU-T G.992.5], the detailed SRA OLR procedure is specified in [ITU-T G.998.4] with the same trigger conditions as those specified if ITU-T G.998.4 retransmission is not used (see clause 7.3.1.4.1.5). + +If operating in accordance with [ITU-T G.993.2], the detailed SRA OLR procedure is specified in [ITU-T G.998.4] with trigger conditions specified in clause C.3.3 of [ITU-T G.998.4]. As long as the downstream NDR is below the downstream MAXNDR\_RTX, data rate increase shall take priority over transmit power reduction. + +###### - *Fallback* + +If operating in accordance with [ITU-T G.993.2] and it is detected at startup that SRA is not supported in the downstream direction by either XTU, they shall fallback to RA-Mode = 2. This shall be reported by the downstream actual rate adaptation mode parameter, ACT-RA-MODEs (see clause 7.5.1.33.1). + +NOTE – If operating in accordance with [ITU-T G.992.3], SRA support is not exchanged at startup. Therefore, it is not possible to determine the actual RA-MODE at the start of showtime. Therefore, the parameter ACT-RA-MODE is not specified in [ITU-T G.992.3]. + +**Mode 4: DYNAMIC with SOS** – Data rate/ETR is automatically selected at initialization and may be continuously adapted during operation (showtime) by SOS and SRA. The rate adaptation mode 4 is optional. In this mode, enabling of SOS and SRA is mandatory. + +###### 7.3.1.4.1.7 If ITU-T G.998.4 retransmission is not used in the downstream direction + +###### *At startup* + +In mode 4, the xTU-C shall start up as in mode 2. + +###### *At showtime* + +###### - *Procedure* + +SRA behaviour shall be identical to that described for mode 3, unless the actual data rate is below the minimum data rate as a result of an SOS procedure. + +Additionally, SOS may be performed, when the conditions specified by the SOS trigger parameters are satisfied. The detailed SOS OLR procedure is specified in [ITU-T G.993.2]. + +###### - *Fallback* + +If at startup it is detected that SOS is not supported in the downstream direction by either XTU, but SRA is supported by both XTUs, the XTUs shall fallback to mode 3. This shall be reported by the downstream actual rate adaptation mode parameter, ACT-RA-MODEs (see clause 7.5.1.33.1). + +If at startup it is detected that SOS is not supported in the downstream direction by either XTU, and SRA is not supported by either XTU, the XTUs shall fallback to mode 2. This shall be reported by the downstream actual rate adaptation mode parameter, ACT-RA-MODEs (see clause 7.5.1.33.1). + +###### **7.3.1.4.1.8 If ITU-T G.998.4 retransmission is used in the downstream direction** + +###### *At startup* + +In mode 4, the xTU-C shall start up as in mode 2. + +###### *At showtime* + +SRA and SOS OLR procedures are defined in [ITU-T G.998.4]. + +###### - *Procedure* + +If it is detected at startup that SOS and SRA is supported in the downstream direction by both XTUs then the following procedure applies. + +- SRA may be performed as described for mode 3. +- Additionally, SOS may be performed. The detailed SOS OLR procedure is specified in [ITU-T G.998.4] with trigger conditions and rate constraints specified in clause C.3.3 of [ITU-T G.998.4]. +- Additionally, SRA may be performed as a result of an SOS procedure. The detailed SRA OLR procedure is specified in [ITU-T G.998.4] with trigger conditions and rate constraints specified in clause C.3.3 of [ITU-T G.998.4]. + +###### - *Fallback* + +If it is detected at startup that SOS is not supported in the downstream direction by either XTUs, but SRA is supported by both XTUs, the XTUs shall fallback to mode 3. This shall be reported by the downstream actual rate adaptation mode parameter, ACT-RA-MODEds (see clause 7.5.1.33.1). + +If it is detected at startup that SOS is not supported in the downstream direction by either XTUs, and that SRA is not supported in the downstream direction by either XTUs, the XTUs shall fallback to mode 2. This shall be reported by the downstream actual rate adaptation mode parameter, ACT-RA-MODEds (see clause 7.5.1.33.1). + +##### **7.3.1.4.2 Upstream rate adaptation mode** + +The upstream rate adaptation mode (RA-MODEus) parameter specifies the mode of operation of a rate-adaptive xTU-R in the transmit direction. The parameter is used only if the rate-adaptive functionality is supported, and can take four values (mode 1 = MANUAL, mode 2 = AT\_INIT, mode 3 = DYNAMIC, mode 4 = DYNAMIC with SOS). The definition of each of the values is identical to its definition in the downstream rate adaptation mode (with xTU-C replaced by xTU-R and downstream replaced by upstream). + +##### **7.3.1.4.3 Downstream upshift noise margin** + +If the downstream noise margin is above the downstream upshift noise margin (RA-USNRMds) and stays above that for more than the time specified by the downstream minimum upshift rate adaptation interval, the xTU-R shall attempt to increase the downstream net data rate. The downstream upshift noise margin ranges from 0 dB to 31 dB, with 0.1 dB steps. + +##### **7.3.1.4.4 Upstream upshift noise margin** + +If the upstream noise margin is above the upstream upshift noise margin (RA-USNRMus) and stays above that for more than the time specified by the upstream minimum upshift rate adaptation interval, the xTU-C shall attempt to increase the upstream net data rate. The upstream upshift noise margin ranges from 0 dB to 31 dB, with 0.1 dB steps. + +##### **7.3.1.4.5 Downstream minimum time interval for upshift rate adaptation** + +The downstream minimum time interval for upshift rate adaptation (RA-UTIMEEds) parameter determines the interval of time the downstream noise margin should stay above the downstream upshift noise margin before the xTU-R shall attempt to increase the downstream net data rate. The time interval ranges from 0 s to 16 383 s with steps of 1 s. + +##### **7.3.1.4.6 Upstream minimum time interval for upshift rate adaptation** + +The upstream minimum time interval for upshift rate adaptation (RA-UTIMEUs) parameter determines the interval of time the upstream noise margin should stay above the upstream upshift noise margin before the xTU-C shall attempt to increase the upstream net data rate. The time interval ranges from 0 s to 16 383 s with steps of 1 s. + +##### **7.3.1.4.7 Downstream downshift noise margin** + +If the downstream noise margin is below the downstream downshift noise margin (RA-DSNRMds) and stays below that for more than the time specified by the downstream minimum downshift rate adaptation interval, the xTU-R shall attempt to decrease the downstream net data rate. The downstream downshift noise margin ranges from 0 dB to 31 dB, with 0.1 dB steps. + +##### **7.3.1.4.8 Upstream downshift noise margin** + +If the upstream noise margin is below the upstream downshift noise margin (RA-DSNRMus) and stays below that for more than the time specified by the upstream minimum downshift rate adaptation interval, the xTU-C shall attempt to decrease the upstream net data rate. The upstream downshift noise margin ranges from 0 dB to 31 dB, with 0.1 dB steps. + +##### **7.3.1.4.9 Downstream minimum time interval for downshift rate adaptation** + +The downstream minimum time interval for downshift rate adaptation (RA-DTIMEEds) parameter determines the interval of time the downstream noise margin should stay below the downstream downshift noise margin before the xTU-R shall attempt to decrease the downstream net data rate. The time interval ranges from 0 s to 16 383 s with steps of 1 s. + +##### **7.3.1.4.10 Upstream minimum time interval for downshift rate adaptation** + +The upstream minimum time interval for downshift rate adaptation (RA-DTIMEUs) parameter determines the interval of time the upstream noise margin should stay below the upstream downshift noise margin before the xTU-C shall attempt to decrease the upstream net data rate. The time interval ranges from 0 s to 16 383 s with steps of 1 s. + +#### **7.3.1.5 Line overhead configuration parameters** + +These parameters are used for testing purposes. + +##### **7.3.1.5.1 Minimum overhead rate upstream** + +The minimum overhead rate upstream (MSGMINus) parameter determines the minimum rate of the message based overhead that shall be maintained by the xTU in the upstream direction. MSGMINus is expressed in bits per second and ranges from 4 000 to 248 000 bit/s with 1 000 bit/s steps. Valid values are specified in the relevant ITU-T Recommendation, e.g., [ITU-T G.992.3] and [ITU-T G.993.2]. + +##### **7.3.1.5.2 Minimum overhead rate downstream** + +The minimum overhead rate downstream (MSGMINds) parameter determines the minimum rate of the message based overhead that shall be maintained by the xTU in the downstream direction. MSGMINds is expressed in bits per second and ranges from 4 000 bit/s to 248 000 bit/s with 1 000 bit/s steps. Valid values are specified in the relevant ITU-T Recommendation, e.g., [ITU-T G.992.3] and [ITU-T G.993.2]. + +#### 7.3.1.6 Cyclic extension configuration parameter + +##### 7.3.1.6.1 Optional cyclic extension flag + +The optional cyclic extension flag (CEFLAG) parameter is a bit that enables the use of the optional cyclic extension values. If the bit is set to 1, the optional cyclic extension values may be used. Otherwise, the cyclic extension shall be forced to the mandatory length ( $5N/32$ ). + +#### 7.3.1.7 Virtual noise configuration parameters + +##### 7.3.1.7.1 Downstream signal-to-noise ratio mode + +The downstream signal-to-noise ratio mode (SNRMODEds) parameter enables the transmitter referred virtual noise in the downstream direction. If set to 1, the virtual noise is disabled. If set to 2, the virtual noise is enabled. For [ITU-T G.993.2], if set to 4, the virtual noise together with the virtual noise scaling factor is enabled. The value of 3 is reserved by ITU-T. + +##### 7.3.1.7.2 Upstream signal-to-noise ratio mode + +The upstream signal-to-noise ratio mode (SNRMODEus) parameter enables the transmitter referred virtual noise in the upstream direction. If set to 1, the virtual noise is disabled. If set to 2, the transmitter referred virtual noise is enabled. For [ITU-T G.993.2], if set to 3, the receiver referred virtual noise is enabled. For [ITU-T G.993.2], if set to 4, the receiver referred virtual noise together with the virtual noise scaling factor is enabled. + +##### 7.3.1.7.3 Downstream virtual noise + +The downstream virtual noise (VNds) configuration parameter defines the downstream transmitter referred virtual noise (TXREFVNdS). The TXREFVNdS shall be specified through a set of breakpoints. Each breakpoint shall consist of a subcarrier index $t$ , with a subcarrier spacing of 4.312 5 kHz, and a noise PSD level (expressed in decibels with reference to 1 mW per hertz) at that subcarrier. The set of breakpoints can then be represented as $[(t_1, \text{PSD}_1), (t_2, \text{PSD}_2), \dots, (t_N, \text{PSD}_N)]$ . The subcarrier index shall be coded as an unsigned integer. The noise level ranges from $-40$ dBm/Hz to $-140$ dBm/Hz in steps of 0.5 dBm/Hz. A special value indicates a noise level of 0 W/Hz. The maximum number of breakpoints is 32. The same TXREFVNdS format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT TXREFVNdS and near-end crosstalk (NEXT) TXREFVNdS. + +To comply with [ITU-T G.992.3] or [ITU-T G.992.5], no more than 15 breakpoints shall be configured below the upper edge of the passband of every mode enabled for [ITU-T G.992.3] and [ITU-T G.992.5]. + +###### 7.3.1.7.3.1 Far-end crosstalk downstream transmitter referred virtual noise + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the downstream transmitter referred virtual noise (see clause 7.3.1.7.3) specified for FEXTR duration is defined as FEXT downstream transmitter referred virtual noise (FEXT TXREFVNdS). + +###### 7.3.1.7.3.2 Near- end crosstalk downstream transmitter referred virtual noise + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the downstream transmitter referred virtual noise (see clause 7.3.1.7.3) specified for NEXTR duration is defined as NEXT downstream transmitter referred virtual noise (NEXT TXREFVNdS). + +##### 7.3.1.7.4 Upstream virtual noise + +If SNRM\_MODE = 2, the upstream virtual noise (VNus) configuration parameter determines the upstream transmitter referred virtual noise (TXREFVNus). For [ITU-T G.993.2], if SNRM\_MODE is equal to 3 or 4, this configuration parameter determines the upstream receiver referred virtual noise (RXREFVNus). The VNus shall be specified through a set of breakpoints. Each breakpoint shall + +consist of a subcarrier index $t$ , with a subcarrier spacing of 4.312 5 kHz, and a noise PSD level (expressed in decibels with reference to 1 mW per hertz) at that subcarrier. The set of breakpoints can then be represented as $[(t_1, \text{PSD}_1), (t_2, \text{PSD}_2), \dots, (t_N, \text{PSD}_N)]$ . The subcarrier index shall be coded as an unsigned integer. The noise level ranges from $-40$ dBm/Hz to $-140$ dBm/Hz in steps of 0.5 dBm/Hz. A special value indicates a noise level of 0 W/Hz. The maximum number of breakpoints is 16. + +For [ITU-T G.992.3] or [ITU-T G.992.5], no more than three breakpoints shall be configured below the upper edge of the passband of every mode enabled for [ITU-T G.992.3] and [ITU-T G.992.5]. + +##### **7.3.1.7.5 Upstream virtual noise scaling factor** + +If SNRM\_MODE = 4, the upstream virtual noise scaling factor (RXREFVNSFus) configuration parameter determines the upstream receiver-referred virtual noise scaling factor. The valid values for the receiver-referred virtual noise scaling factor range from $-64.0$ dB to $63.5$ dB, in steps of 0.5 dB. + +##### **7.3.1.7.6 Downstream virtual noise scaling factor** + +If SNRM\_MODE = 4, the downstream virtual noise scaling factor (TXREFVNSFds) configuration parameter determines the downstream transmitter referred virtual noise scaling factor. The valid values for the transmitter referred virtual noise scaling factor range from $-64.0$ dB to $63.5$ dB, in steps of 0.5 dB. + +#### **7.3.1.8 Line performance monitoring parameter thresholds** + +All supported line PM parameters (counters, see Table 7-1) shall have an individual 15 min and 24 h threshold parameter except for the error-free bits counter and MINEFTR for which threshold parameters are not specified. + +#### **7.3.1.9 Impulse noise monitoring configuration parameters** + +The following configuration parameters are specified to control the impulse noise monitor in the receive direction in the xTU. A downstream impulse noise monitor applies to the xTU-R, an upstream impulse noise monitor applies to the xTU-C. + +##### **7.3.1.9.1 Impulse noise monitoring interarrival time offsetImpulse noise monitoring** + +The INM interarrival time offset (INMIATO) is the interarrival time offset that the xTU receiver shall use to determine in which bin of the interarrival time histogram the IAT is reported. The valid values for INMIATO ranges from 3 to 511 discrete multitone (DMT) symbols in steps of 1 DMT symbol. + +##### **7.3.1.9.2 Impulse noise monitoring interarrival time step** + +The INM interarrival time step (INMIATS) is the interarrival time step that the xTU receiver shall use to determine in which bin of the interarrival time histogram the IAT is reported. The valid values for INMIATS ranges from 0 to 7 in steps of 1. + +##### **7.3.1.9.3 Impulse noise monitoring cluster continuation value** + +The INM cluster continuation value (INMCC) is the cluster continuation value that the xTU receiver shall use in the cluster indication process specified in the relevant ITU-T Recommendation. The valid values for INMCC range from 0 to 64 DMT symbols in steps of one DMT symbol. + +##### **7.3.1.9.4 Impulse noise monitoring equivalent impulse noise protection mode** + +The INM equivalent impulse noise protection (INP) mode (INM\_INPEQ\_MODE) is the INM equivalent INP mode that the xTU receiver shall use in the computation of the Equivalent INP, as specified in the relevant ITU-T Recommendation. The valid values for INM\_INPEQ\_MODE are 0, 1, 2, 3, and 4. + +##### **7.3.1.9.5 Impulse noise monitoring equivalent impulse noise protection format** + +The INM equivalent INP format (INM\_INPEQ\_FORMAT) is the INM equivalent INP format that the xTU receiver shall use in to scale the INPEQ histogram, as specified in the relevant ITU-T Recommendation. The valid values for INM\_INPEQ\_FORMAT are 0 (linear), 1 (logarithmic). + +##### **7.3.1.9.6 Impulse noise monitoring enable** + +The INM enable (INM\_ENABLE) is the enable/disable of the INM facility in both directions, as specified in the relevant ITU-T Recommendation. The valid values for INM\_ENABLE are 0 (disabled), 1 (enabled). If INM is disabled, all other configuration parameters for INM are not applicable. + +NOTE – If INM is disabled in the MIB, the transceiver may use vendor-discretionary values taken from the range of valid values for the control parameters of INM. + +#### **7.3.1.10 save our showtime line related configuration parameters** + +##### **7.3.1.10.1 Downstream save our showtime time window** + +The downstream SOS time window (SOS-TIME-ds) parameter is used in the specification of the receiver initiated SOS (see clause 13.4.3 of [ITU-T G.993.2]). If the value of this parameter is not zero, the standard SOS triggering criteria are enabled, and the value corresponds to the duration of the time window used in the standard SOS triggering criteria in the downstream direction. See [ITU-T G.993.2] for detailed usage rules. + +The special value zero indicates that the standard SOS triggering criteria are disabled, i.e., vendor discretionary values may be used instead of the values configured in the MIB for the following parameters: SOS-NTONES-ds, SOS-CRC-ds, SOS-TIME-ds. + +This parameter applies in the downstream direction. The valid range of non-zero values is from 64 ms to 16 320 ms in steps of 64 ms. + +##### **7.3.1.10.2 Upstream save our showtime time window** + +The upstream SOS time window (SOS-TIME-us) parameter is used in the specification of the receiver-initiated SOS (see clause 13.4.3 of [ITU-T G.993.2]). If the value of this parameter is not zero, the standard SOS triggering criteria are enabled, and the value corresponds to the duration of the time window used in the standard SOS triggering criteria in the upstream direction. See [ITU-T G.993.2] for detailed usage rules. + +The special value zero indicates that the standard SOS triggering criteria are disabled, i.e., vendor discretionary values may be used instead of the values configured in the MIB for the following parameters: SOS-NTONES-us, SOS-CRC-us, SOS-TIME-us. + +This parameter applies in the upstream direction. The valid range of non-zero values is from 64 ms to 16 320 ms in steps of 64 ms. + +##### **7.3.1.10.3 Downstream minimum percentage of degraded tones** + +The downstream minimum percentage of degraded tones (SOS-NTONES-ds) parameter is the minimum percentage of tones in the downstream MEDLEY SET that must be degraded in order to arm the first sub-condition of the standard SOS triggering criteria (see clause 13.4.3.2 of [ITU-T G.993.2]) in the downstream direction. The parameter SOS-NTONES-ds is a percentage of tones. See [ITU-T G.993.2] for detailed usage rules. The valid range of values is from 1 to 100 in steps of 1. Use of the special value 0 is described in clause 13.4.3.2 of [ITU-T G.993.2]. + +##### **7.3.1.10.4 Upstream minimum percentage of degraded tones** + +The upstream minimum percentage of degraded tones (SOS-NTONES-us) parameter is the minimum percentage of tones in the upstream MEDLEY SET that must be degraded in order to arm the first sub-condition of the standard SOS triggering criteria (see clause 13.4.3.2 of [ITU-T G.993.2]) in the upstream direction. The parameter SOS-NTONES-us is a percentage of tones. See [ITU-T G.993.2] for detailed usage rules. The valid range of values is from 1 to 100 in steps of 1. Use of the special value 0 is described in clause 13.4.3.2 of [ITU-T G.993.2]. + +##### **7.3.1.10.5 Downstream minimum number of normalized CRC anomalies** + +The downstream minimum number of normalized CRC anomalies (SOS-CRC-ds) parameter is the minimum number of normalized CRC anomalies received in SOS-TIME-ds seconds in order to arm the second sub-condition of the standard SOS triggering criteria (see clause 13.4.3.2 of [ITU-T G.993.2]) in the downstream direction. See [ITU-T G.993.2] for detailed usage rules. The valid range of SOS-CRC values is 0.02 to $((2^{16})-1) \times 0.02$ , in steps of 0.02. + +##### **7.3.1.10.6 Upstream minimum number of normalized CRC anomalies** + +The upstream minimum number of normalized CRC anomalies (SOS-CRC-us) parameter is the minimum number of normalized CRC anomalies received in SOS-TIME-us seconds in order to arm the second sub-condition of the standard SOS triggering criteria (see clause 13.4.3.2 of [ITU-T G.993.2]) in the upstream direction. See [ITU-T G.993.2] for detailed usage rules. The valid range of SOS-CRC values is 0.02 to $((2^{16})-1) \times 0.02$ , in steps of 0.02. + +##### **7.3.1.10.7 Downstream maximum number of save our showtime** + +The downstream maximum number of SOS (MAX-SOS-ds) parameter is used in ITU-T G.993.2 deactivation (see clause 12.1.4 of [ITU-T G.993.2]). If the number of successful SOS procedures in the downstream direction performed within a 120 s interval exceeds MAX-SOS-ds, the modem shall transition to the L3 state. See [ITU-T G.993.2] for detailed usage rules (see clause 12.1.4 of [ITU-T G.993.2]). The valid range of values is 1 to 15. Use of the special value 0 is described in clause 12.1 of [ITU-T G.993.2]. + +##### **7.3.1.10.8 Upstream maximum number of save our showtime (MAX-SOS-us)** + +The upstream maximum number of SOS (MAX-SOS-us) parameter is used in ITU-T G.993.2 deactivation (see clause 12.1.4 of [ITU-T G.993.2]). If the number of successful SOS procedures in the upstream direction performed within a 120 s interval exceeds MAX-SOS-us, the modem shall transition to the L3 state. See [ITU-T G.993.2] for detailed usage rules (see clause 12.1.4 of [ITU-T G.993.2]). The valid range of values is 1 to 15. Use of the special value 0 is described in clause 12.1 of [ITU-T G.993.2]. + +##### **7.3.1.10.9 Downstream signal-to-noise ratio margin offset of robust overhead channel** + +The downstream SNR margin offset of the robust overhead channel (ROC) (SNRMOFFSET-ROC-ds) parameter is the signal-to-noise ratio (SNR) margin offset for the ROC channel in the downstream direction. The parameter is used in the specification of the channel initialization policy (see clause 12.3.7.1 of [ITU-T G.993.2]). + +The valid range of SNR margin offset values is from 0 to 31 dB, with 0.1 dB steps. + +##### **7.3.1.10.10 Upstream signal-to-noise ratio margin offset of robust overhead channel** + +The upstream SNR margin offset of ROC (SNRMOFFSET-ROC-us) parameter is the SNR margin offset for the ROC channel in the upstream direction. The parameter is used in the specification of the channel initialization policy (see clause 12.3.7.1 of [ITU-T G.993.2]). + +The valid range of SNR margin offset values is from 0 to 31 dB, with 0.1 dB steps. + +##### 7.3.1.10.11 Downstream minimum impulse noise protection of robust overhead channel + +The downstream minimum INP of ROC (INPMIN-ROC-ds) parameter contains the minimum INP to apply on the ROC in the downstream direction expressed in multiples of equivalent $4k$ DMT symbol length (denoted $T_{4k}$ , see clause 10.4.4 of [ITU-T G.993.2]). The minimum INP is an integer ranging from 0 to 8. + +##### 7.3.1.10.12 Upstream minimum impulse noise protection of robust overhead channel + +The upstream minimum INP of ROC (INPMIN-ROC-us) parameter contains the minimum INP to apply on the robust ROC in the upstream direction expressed in multiples of $T_{4k}$ . The minimum INP is an integer ranging from 0 to 8. + +#### 7.3.1.11 Retransmission mode + +The retransmission mode (RTX\_MODE) parameter controls the mode of operation of ITU-T G.998.4 retransmission in a given transmit direction. The parameter in downstream is RTX\_MODE\_ds, and the parameter in upstream is RTX\_MODE\_us. In [ITU-T G.992.3] and [ITU-T G.992.5], only the downstream parameter RTX\_MODE\_ds is relevant, the value in the upstream direction shall be ignored. In [ITU-T G.993.2], both parameters are relevant. + +This parameter has four valid values as follows. + +- 0: RTX\_FORBIDDEN: ITU-T G.998.4 retransmission not allowed +- 1: RTX\_PREFERRED: ITU-T G.998.4 retransmission is preferred by the operator (i.e., if ITU-T G.998.4 RTX capability is supported by both XTUs, the XTUs shall select ITU-T G.998.4 operation for this direction) +- 2: RTX\_FORCED: Force the use of the ITU-T G.998.4 retransmission (i.e., if ITU-T G.998.4 RTX capability in this direction is not supported by both XTUs or not selected by the XTUs, an initialization failure shall result) +NOTE – Due to the optionality of ITU-T G.998.4 retransmission in the upstream direction, the use of RTX\_FORCED in upstream may lead to initialization failure, even if the XTU supports ITU-T G.998.4 (in downstream). +- 3: RTX\_TESTMODE: Force the use of the ITU-T G.998.4 retransmission in test mode (i.e., if ITU-T G.998.4 RTX capability is not supported by both XTUs or not selected by the XTUs, an initialization failure shall result). + +#### 7.3.1.12 "leftr" defect threshold + +If retransmission is used in a given transmit direction, "leftr" defect threshold (LEFTR\_THRESH) specifies the threshold for declaring a near-end "leftr" defect (see clause 11.1.12 of [ITU-T G.998.4] for the definition of this threshold). + +The value is coded as a fraction of the NDR with a valid range from 0.01 to 0.99 with increments of 0.01. A special value means the ETR shall be used as the default threshold for declaring a "leftr" defect. + +#### 7.3.1.13 Line configuration parameters for [ITU-T G.993.5] + +##### 7.3.1.13.1 Vectoring frequency-band control + +The vectoring frequency-band control upstream (VECTOR\_BAND\_CONTROLus) configuration parameter is an array of pairs of sub-carrier indices ( $a(i)$ , $b(i)$ ). Each pair specifies a frequency band starting from sub-carrier index $a(i)$ and ending at sub-carrier index $b(i)$ (including both start and end points) in which upstream FEXT cancellation for the line is not required. Up to eight frequency bands may be configured. The same value of this parameter shall be set for all lines of the same vector group. + +##### 7.3.1.13.2 Vectoring frequency-band control downstream + +The vectoring frequency-band control downstream (VECTOR\_BAND\_CONTROLds) configuration parameter is an array of pairs of sub-carrier indices ( $a(i)$ , $b(i)$ ). Each pair specifies a frequency band starting from sub-carrier index $a(i)$ and ending at sub-carrier index $b(i)$ (including both start and end points) in which downstream FEXT cancellation for the line is not required. Up to eight frequency bands may be configured. The same value of this parameter shall be set for all lines of the same vector group. + +##### 7.3.1.13.3 Far-end crosstalk cancellation line priorities upstream + +The FEXT cancellation line priorities upstream (FEXT\_CANCEL\_PRIORITYus) parameter specifies line priority for the line in the vectored group in the upstream direction, as defined in [ITU-T G.993.5]. Two line priorities are specified as low and high. + +##### 7.3.1.13.4 Far-end crosstalk cancellation line priorities downstream + +The FEXT cancellation line priorities downstream (FEXT\_CANCEL\_PRIORITYds) parameter specifies line priority for the line in the vectored group in the downstream direction, as defined in [ITU-T G.993.5]. Two line priorities are specified as low and high. + +##### 7.3.1.13.5 Far-end crosstalk cancellation enabling/disabling upstream + +FEXT cancellation enabling/disabling upstream (FEXT\_CANCEL\_ENABLEus) has a value of 1 to enable and a value of 0 to disable FEXT cancellation in the upstream direction from all the other vectored lines into the line in the vectored group. + +##### 7.3.1.13.6 Far-end crosstalk cancellation enabling/disabling downstream + +FEXT cancellation enabling/disabling downstream (FEXT\_CANCEL\_ENABLEds) has a value of 1 to enable and a value of 0 to disable FEXT cancellation in the downstream direction from all the other vectored lines into the line in the vectored group. + +##### 7.3.1.13.7 Downstream requested XLIN subcarrier group size + +The downstream requested XLIN subcarrier group size (XLINGREQds) parameter is the requested value of XLINGds. The valid values are 1, 2, 4, 8, 16, 32, and 64. + +##### 7.3.1.13.8 Upstream requested XLIN subcarrier group size + +The upstream requested XLIN subcarrier group size (XLINGREQus) parameter is the requested value of XLINGus. + +##### 7.3.1.13.9 Vectoring mode enable + +The vectoring mode enable (VECTORMODE\_ENABLE) configuration parameter determines the vectoring initialization type to be allowed by the VTU-O on the line. + +It is coded in a bit-map representation (0 if not allowed, 1 if allowed), with the following definition. + +- bit 0: initialization in ITU-T G.993.2 mode with neither Annex X nor Annex Y enabled +- bit 1: initialization in Annex X of ITU-T G.993.2 +- bit 2: initialization in Annex Y of ITU-T G.993.2 +- bit 3: initialization in ITU-T G.993.5 +- bit 4 to 7: reserved by ITU-T + +If ITU-T G.993.2 is enabled in the XTSE (octet 8), then at least one of the bits 0-3 shall be set to 1. + +NOTE – If bit 0 is set to 0, the system is not allowed to operate in any ITU-T G.993.2 modes except those where Annex X, Annex Y or [ITU-T G.993.5] are enabled. + +#### **7.3.1.14 MAXDELAYOCTET-split parameter** + +The line configuration parameter MAXDELAYOCTET-split (MDOSPLIT) determines the percentage of the MAXDELAYOCTET\_ext if operating in ITU-T G.998.4 or MAXDELAYOCTET in other cases allocated to the downstream direction. All of the remaining MAXDELAYOCTET or MAXDELAYOCTET\_ext shall be allocated for use in the upstream direction. + +The detailed specification is in [ITU-T G.993.2] and [ITU-T G.998.4]. + +MDOSPLIT shall be expressed as a percentage, with a valid range from 5% to 95% inclusive, in steps of 1%. The value 0% is valid only if the maximum downstream interleaving delay is configured with the special value S1 (see clause 7.3.2.2) and retransmission is disabled in the downstream direction. The value 100% is valid only if the maximum upstream interleaving delay is configured with the special value S1 (see clause 7.3.2.2) and retransmission is disabled in the upstream direction. A special value shall indicate that the VTU-O is allowed to use a vendor discretionary algorithm. + +NOTE – The special value is introduced to ensure backwards compatibility. + +#### **7.3.1.15 Attainable net data rate configuration parameters** + +##### **7.3.1.15.1 Attainable net data rate method** + +The attainable net data rate (ATTNDR) method (ATTNDR\_METHOD) parameter specifies the method to be used for the calculation of the ATTNDR in the downstream and upstream direction. + +The parameter can take three values: 0, 1 and 2. + +For detailed definition see clause 11.4.1.1.7 of [ITU-T G.993.2]. + +##### **7.3.1.15.2 Attainable net data rate MAXDELAYOCTET-split** + +The ATTNDR MAXDELAYOCTET-split (ATTNDR\_MDOSPLIT) line configuration parameter determines the percentage of the MAXDELAYOCTET\_ext if operating in ITU-T G.998.4 or MAXDELAYOCTET in other cases allocated to the downstream direction to be used in the improved method for calculation of the ATTNDR. All of the remaining MAXDELAYOCTET\_ext or MAXDELAYOCTET shall be allocated for use in the upstream direction. + +The detailed specification is in [ITU-T G.993.2] and [ITU-T G.998.4]. + +The valid values are identical to the values of the line configuration parameter MDOSPLIT (see clause 7.3.1.14). + +#### **7.3.1.16 VDSL2-LR configuration parameter** + +##### **7.3.1.16.1 VDSL2-LR enable** + +The VDSL2-LR enable (VDSL2-LR\_ENABLE) parameter specifies which VDSL2-LR operation types are allowed. The parameter is encoded as a bitmap representation (0 is not allowed, 1 is allowed): + +- bit 0: short loop operation type +- bit 1: medium loop operation type. +- bit 2: long loop operation type + +If no operation type is allowed, the VDSL2-LR mode, i.e., operation according to Annex D of [ITU-T G.993.2] or Annex B of [ITU-T G.993.5], is disabled. If at least one operation type is allowed, the VDSL2-LR mode is enabled. + +For detailed specification of this parameter, see clause B.10.1.1 of [ITU-T G.993.5]. + +#### **7.3.1.17 STRONGFEXT MODE configuration parameter** + +##### **7.3.1.17.1 STRONGFEXT mode (STRONGFEXT\_MODE)** + +The STRONGFEXT mode (STRONGFEXT\_MODE) parameter specifies whether operation according to G.993.5 Annex A is disabled, preferred, forced, or forced above 17 MHz. The parameter can take four values: 0 (disabled), 1 (preferred), 2 (forced) and 3 (forced above 17 MHz). + +For detailed specification of this parameter, see clause A.8.1.1 of [ITU-T G.993.5]. + +### **7.3.2 Channel configuration parameters** + +#### **7.3.2.1 Data rate configuration parameters** + +These data rate parameters refer to the transmit direction for both the xTU-C and the xTU-R and apply to the configuration of an individual upstream or downstream bearer channel. The two data rate parameters define the data rate minimum and maximum bounds as specified by the operator of the system (the operator of the xTU-C). It is assumed that the xTU-C and the xTU-R will interpret the value set by the operator as appropriate for the specific implementation of xDSL between the xTU-C and the xTU-R in setting the line rates. The ranges of the data rate configuration parameters are not specified. The NMS used by the operator to manage the xTU-R and the xTU-C may implement its own limits on the allowed values for the desired bit rate parameters based on the particulars of the system managed. The definition of such a system lies outside the scope of this Recommendation. + +##### **7.3.2.1.1 Minimum data rate** + +If retransmission is not used in a given transmit direction, this parameter specifies the minimum net data rate for the bearer channel as desired by the operator of the system. The rate is coded in steps of 1 000 bit/s. + +##### **7.3.2.1.2 Minimum reserved data rate** + +This parameter specifies the minimum reserved net data rate for the bearer channel as desired by the operator of the system. The rate is coded in steps of 1 000 bit/s. + +This parameter is optional. It is used only if the rate adaptation mode is set to DYNAMIC. + +##### **7.3.2.1.3 Maximum data rate** + +If retransmission is not used in a given transmit direction, this parameter specifies the maximum net data rate for the bearer channel as desired by the operator of the system. The data rate is coded in steps of 1 000 bit/s. + +##### **7.3.2.1.4 Rate adaptation ratio** + +This parameter, expressed as a percentage, specifies the ratio that shall be taken into account for the bearer channel when performing rate adaptation in the transmission direction of the bearer channel. The ratio is defined as a percentage in the 0 to 100 range. A ratio of 20% means that 20% of the available data rate (in excess of the minimum data rate summed over all bearer channels) will be assigned to this bearer channel and 80% to the other bearer channels. + +The sum of rate adaptation ratios over all bearers in one direction shall be equal to 100%. + +##### **7.3.2.1.5 Minimum data rate in low power state** + +This parameter specifies the minimum net data rate for the bearer channel as desired by the operator of the system during the low power state (L1/L2). The power management low power states L1 and L2 are defined in [ITU-T G.992.2] and [ITU-T G.992.3], respectively. The data rate is coded in steps of 1 000 bit/s. + +##### 7.3.2.1.6 Minimum save our showtime data rate + +The minimum SOS data rate (MIN-SOS-DR) parameter specifies the minimum net data rate for the bearer channel required for a valid SOS request in the direction of the bearer channel. The value shall be coded as an unsigned integer representing the data rate as a multiple of 8 kbit/s. + +##### 7.3.2.1.7 Clause intentionally left blank + +##### 7.3.2.1.8 Minimum expected throughput for retransmission + +If retransmission is used in a given transmit direction, the minimum ETR for retransmission (MINETR\_RTX) parameter specifies the minimum ETR for the bearer channel (as specified in clause 11.1.1 of [ITU-T G.998.4]). + +The rate is coded in steps of 1 000 bit/s. + +##### 7.3.2.1.9 Maximum expected throughput for retransmission + +If retransmission is used in a given transmit direction, the maximum ETR for retransmission (MAXETR\_RTX) parameter specifies the maximum ETR for the bearer channel (as specified in clause 11.1.2 of [ITU-T G.998.4]). + +The rate is coded in steps of 1 000 bit/s. + +##### 7.3.2.1.10 Maximum net data rate for retransmission + +If retransmission is used in a given transmit direction, the maximum net data rate for retransmission (MAXNDR\_RTX) parameter specifies the maximum net data rate for the bearer channel (as specified in clause 11.1.3 of [ITU-T G.998.4]). + +The data rate is coded in steps of 1 000 bit/s. + +#### 7.3.2.2 Maximum interleaving delay + +If retransmission is not used in a given transmit direction, this parameter is the maximum one-way interleaving delay introduced by the physical media specific-transmission convergence (PMS-TC) between the $\alpha$ and the $\beta$ reference points, in the direction of the bearer channel. The one-way interleaving delay is defined in individual ADSL Recommendations as $\lceil S \times D \rceil / 4$ ms, where $S$ is the $S$ -factor and $D$ is the interleaving depth and the ceiling brackets $\lceil \dots \rceil$ denote rounding to the higher integer. + +The xTUs shall choose the $S$ and $D$ values such that the actual one-way interleaving delay (see actual interleaving delay status parameter in clause 7.5.2.3) is less than or equal to the configured maximum interleaving delay. The delay ranges from 2 ms to 63 ms by steps of 1 ms. Three special values, $S0$ , $S1$ and $S2$ , are specified. The value $S0$ indicates no delay bound is being imposed. The value $S1$ indicates the fast latency path shall be used in the ITU-T G.992.1 operating mode and $S$ and $D$ shall be selected such that $S \leq 1$ and $D = 1$ in [ITU-T G.992.2], [ITU-T G.992.3], [ITU-T G.992.4], [ITU-T G.992.5] and [ITU-T G.993.2] operating modes. The value $S2$ indicates a delay bound of 1 ms in [ITU-T G.993.2]. + +NOTE – A single maximum delay value is configured for operation without ITU-T G.998.4 retransmission mode. As a consequence, xTUs supporting multiple xDSL Recommendations will use the configured value regardless of the xDSL operating mode actually being selected at LINIT. + +#### 7.3.2.3 Minimum impulse noise protection + +If retransmission is not used in a given transmit direction, the minimum INP (INPMIN) parameter specifies the minimum INP for the bearer channel if it is transported over DMT symbols with a subcarrier spacing of 4.312 5 kHz. The impulse noise protection is expressed in DMT symbols with a subcarrier spacing of 4.312 5 kHz and can take the values $\frac{1}{2}$ and any integer from 0 to 16, inclusive. + +If the xTU does not support the configured INPMIN value, it shall use the nearest supported INP greater than INPMIN. + +##### **7.3.2.3.1 Special requirements for [ITU-T G.992.1]** + +It is optional to apply the INPMIN parameter in the case of [ITU-T G.992.1]. If INPMIN is supported, the ATU-C shall offer to the ATU-R a range of combinations of framing parameters (C-RATES-1 and C-RATES-RA options) during initialization, which provide an ACTINP value equal to or greater than the INPMIN value specified over the Q-interface. The ACTINP value for [ITU-T G.992.1] is defined in clause 7.5.2.4. + +#### **7.3.2.4 Minimum impulse noise protection for system using 8.625 kHz subcarrier spacing** + +If retransmission is not used in a given transmit direction, the minimum INP for system using 8.625 kHz subcarrier spacing (INPMIN8) parameter specifies the minimum INP for the bearer channel if it is transported over DMT symbols with a subcarrier spacing of 8.625 kHz. The INP is expressed in DMT symbols with a subcarrier spacing of 8.625 kHz and can take any integer value from 0 to 16, inclusive. + +#### **7.3.2.5 Force framer setting for impulse noise protection** + +If retransmission is not used in a given transmit direction, the force framer setting for INP (FORCEINP) parameter indicates that the framer settings of the bearer shall be selected such that the INP computed according to the formula specified in the relevant Recommendation is greater than or equal to the minimal INP requirement. + +This flag shall have the same value for all the bearers of one line in the same direction. + +#### **7.3.2.6 Maximum bit error ratio** + +If retransmission is not used in a given transmit direction, this parameter specifies the maximum bit error ratio for the bearer channel as desired by the operator of the system. The bit error ratio can take the values $10^{-3}$ , $10^{-5}$ or $10^{-7}$ . + +NOTE – ATUs supporting multiple ADSL Recommendations may use or ignore the configured value depending on the operating mode actually being selected at LINIT. In [ITU-T G.992.3], [ITU-T G.992.4] and [ITU-T G.992.5], the ATUs will use the configured value. In [ITU-T G.992.1] and [ITU-T G.992.2], ATUs operate with the maximum bit error ratio fixed to $10^{-7}$ , regardless of the configured value. + +#### **7.3.2.7 Channel performance monitoring parameter thresholds** + +All supported channel PM parameters (counters, see Table 7-2) shall have an individual 15 min and 24 h threshold parameter. + +#### **7.3.2.8 Channel data rate thresholds** + +The data rate threshold parameter procedures shall be as specified in clause 7.2.7. + +##### **7.3.2.8.1 Data rate threshold upshift** + +If retransmission is not used in a given transmit direction, this parameter is a threshold on the net data rate upshift achieved over one or more bearer channel data rate adaptations. An upshift rate change alarm (event) is triggered when the actual data rate exceeds the data rate at the last entry into showtime by more than the threshold. The data rate threshold is coded in bits per second. + +##### **7.3.2.8.2 Data rate threshold downshift** + +If retransmission is not used in a given transmit direction, this parameter is a threshold on the net data rate downshift achieved over one or more bearer channel data rate adaptations. A downshift rate change alarm (event) is triggered when the actual data rate is below the data rate at the last entry into showtime by more than the threshold. The data rate threshold is coded in bits per second. + +#### **7.3.2.9 Maximum delay variation** + +The maximum delay variation (DVMAX) parameter specifies the maximum value for the delay variation allowed in an OLR procedure. + +It ranges from 0.1 ms to 25.4 ms in steps of 0.1 ms. + +A special value indicates that no delay variation bound is imposed. + +#### **7.3.2.10 Channel initialization policy selection** + +If retransmission is not used in a given transmit direction, the channel initialization policy selection (CIPOLICY) parameter indicates which policy shall be applied to determine the transceiver configuration parameters at initialization. The valid values for CIPOLICY are 0, 1 and 2. They are specified in the respective Recommendations. + +#### **7.3.2.11 Maximum delay for retransmission** + +If retransmission is used in a given transmit direction, the maximum delay for retransmission (DELAYMAX\_RTX) parameter specifies the maximum for the instantaneous delay due to the effect of retransmission only (see [ITU-T G.998.4] for detailed specification). The delay ranges from 1 ms to 63 ms by steps of 1 ms. + +NOTE – A single maximum delay value is configured for operation in ITU-T G.998.4 retransmission mode. As a consequence, xTUs supporting multiple xDSL Recommendations in conjunction with [ITU-T G.998.4] will use the configured value regardless of the xDSL operating mode actually being selected at LINIT. + +#### **7.3.2.12 Minimum delay for retransmission** + +If retransmission is used in a given transmit direction, the minimum delay for retransmission (DELAYMIN\_RTX) parameter specifies the minimum for the instantaneous delay due to the effect of retransmission only (see [ITU-T G.998.4] for detailed specification). The delay ranges from 0 ms to 63 ms by steps of 1 ms. + +NOTE – A single minimum delay value is configured for operation in ITU-T G.998.4 retransmission mode. As a consequence, xTUs supporting multiple xDSL Recommendations in conjunction with [ITU-T G.998.4] will use the configured value regardless of the xDSL operating mode actually being selected at LINIT. + +#### **7.3.2.13 Minimum impulse noise protection against SHINE for retransmission** + +If retransmission is used in a given transmit direction, the minimum INP against SHINE for retransmission (INPMIN\_SHINE\_RTX) parameter specifies the minimum INP against SHINE for the bearer channel if it is transported over DMT symbols with a subcarrier spacing of 4.312 5 kHz. The INP is expressed in DMT symbols with a subcarrier spacing of 4.312 5 kHz and can take any integer value from 0 to 63, inclusive. + +#### **7.3.2.14 Minimum impulse noise protection against SHINE for retransmission for systems using 8.625 kHz subcarrier spacing** + +If retransmission is used in a given transmit direction, the minimum INP against SHINE for retransmission for systems using 8.625 kHz subcarrier spacing (INPMIN8\_SHINE\_RTX) parameter specifies the minimum INP against SHINE for the bearer channel if it is transported over DMT symbols with a subcarrier spacing of 8.625 kHz. The INP is expressed in DMT symbols with a subcarrier spacing of 8.625 kHz and can take any integer value from 0 to 127, inclusive. + +#### **7.3.2.15 SHINE ratio for retransmission (SHINERATIO\_RTX)** + +If retransmission is used in a given transmit direction, the SHINE ratio for retransmission (SHINERATIO\_RTX) parameter specifies the SHINE ratio (see [ITU-T G.998.4] for details). + +The values range from 0 to 0.100 in increments of 0.001. + +#### **7.3.2.16 Minimum impulse noise protection against repetitive electrical impulse noise for retransmission** + +If retransmission is used in a given transmit direction, the minimum INP against repetitive electrical impulse noise (REIN) for retransmission (INPMIN\_REIN\_RTX) parameter specifies the minimum INP against REIN for the bearer channel if it is transported over DMT symbols with a subcarrier spacing of 4.312 5 kHz. The INP is expressed in DMT symbols with a subcarrier spacing of 4.312 5 kHz and can take any integer value from 0 to 7, inclusive. + +#### **7.3.2.17 Minimum impulse noise protection against repetitive electrical impulse noise for retransmission for systems using 8.625 kHz subcarrier spacing** + +If retransmission is used in a given transmit direction, the minimum INP against REIN for retransmission for systems using 8.625 kHz subcarrier spacing (INPMIN8\_REIN\_RTX) parameter specifies the minimum INP against REIN for the bearer channel if it is transported over DMT symbols with a subcarrier spacing of 8.625 kHz. The INP is expressed in DMT symbols with a subcarrier spacing of 8.625 kHz and can take any integer value from 0 to 13, inclusive. + +#### **7.3.2.18 Repetitive electrical impulse noise interarrival time for retransmission** + +If retransmission is used in a given transmit direction, the REIN interarrival time for retransmission (IAT\_REIN\_RTX) parameter specifies the interarrival time that shall be assumed for REIN protection. + +- The value 0 indicates an interarrival time derived from a REIN at 100 Hz +- The value 1 indicates an interarrival time derived from a REIN at 120 Hz + +#### **7.3.2.19 Channel configuration parameters for [ITU-T G.993.5]** + +##### **7.3.2.19.1 Target net data rate** + +If retransmission is not used in a given transmit direction, the target net data rate (TARGET\_NDR) parameter specifies the target net data rate as defined in [ITU-T G.993.5] of the bearer channel. + +The target net data rate is coded in steps of 1 000 bit/s. + +##### **7.3.2.19.2 Target expected throughput for retransmission** + +If retransmission is used in a given transmit direction, the target ETR for retransmission (TARGET\_ETR) parameter specifies the target ETR as defined in [ITU-T G.993.5] for the bearer channel. + +The target ETR is coded in steps of 1 000 bit/s. + +### **7.3.3 Synchronous transfer mode data path configuration parameters** + +No STM data path configuration parameters are defined. + +### **7.3.4 Asynchronous transfer mode data path configuration parameters** + +#### **7.3.4.1 IMA operation mode enable parameter** + +This parameter enables the inverse multiplexing over ATM (IMA) operation mode in the ATM data path. It indicates that the ATM data path shall comply with the requirements for IMA transmission, i.e., minimum amount of idle cells shall be inserted and no cell discard shall be enabled at the receiver. + +#### **7.3.4.2 Asynchronous transfer mode data path performance monitoring parameter thresholds** + +All supported ATM data path PM parameters (counters, see Table 7-3) shall have an individual 15 min and 24 h threshold parameter. + +### 7.3.5 Packet transfer mode data path configuration parameters + +#### 7.3.5.1 Packet transfer mode data path performance monitoring parameter thresholds + +All supported PTM data path PM parameters (counters, see Table 7-4) shall have an individual 15 min and 24 h threshold parameter. + +### 7.3.6 Data gathering configuration parameters + +#### 7.3.6.1 Logging depth event percentage per event – VTU-O + +The logging depth event percentage per event – VTU-O (LOGGING\_DEPTH\_EVENT\_PERCENTAGE\_Oi) parameter is the percentage of the data gathering event buffer assigned to event type *i* at the VTU-O. The ID, *i*, of the event type is defined in Table 11-43 of [ITU-T G.993.2]. + +#### 7.3.6.2 Logging depth event percentage per event – VTU-R + +The logging depth event percentage per event – VTU-R (LOGGING\_DEPTH\_EVENT\_PERCENTAGE\_Ri) parameter is the percentage of the data gathering event buffer assigned to event type *i* at the VTU-R. The ID, *i*, of the event type is defined in Table 11-43 of [ITU-T G.993.2]. + +#### 7.3.6.3 Logging depth for VTU-O reporting – VTU-R + +The logging depth for VTU-O reporting – VTU-R (LOGGING\_DEPTH\_REPORTING\_O) parameter is the logging depth that is requested for reporting the VTU-O event trace buffer in the CO-MIB, in number of 6-byte data gathering records. + +#### 7.3.6.4 Logging depth for VTU-R reporting – VTU-R + +The logging depth for VTU-R reporting – VTU-R (LOGGING\_DEPTH\_REPORTING\_R) parameter is the logging depth that is requested for reporting the VTU-R event trace buffer over the eoc channel, in number of 6-byte data gathering records. + +#### 7.3.6.5 Logging data report newer events first – VTU-R + +If true, the logging data report newer events first – VTU-R (LOGGING\_REPORT\_NEWER\_FIRST) parameter instructs the VTU-R to report newer events first, from the beginning of the event trace buffer. If false, this parameter instructs the VTU-R to report older events first, from the end of the event trace buffer. + +## 7.4 Inventory information + +### 7.4.1 xTU-C ITU-T G.994.1 vendor identifier + +The xTU-C ITU-T G.994.1 vendor ID is the vendor ID as inserted by the xTU-C in the ITU-T G.994.1 capabilities list (CL) message. It consists of 8 binary octets, including a country code followed by a (regionally allocated) provider code, as specified in [ITU-T T.35]. + +**Table 7-9 – Vendor identifier information block (8 octets)** + +| | +|-----------------------------------------------------------------| +| T.35 country code (2 octets) | +| T.35 provider code (vendor identification) (4 octets) | +| T.35 provider oriented code (vendor revision number) (2 octets) | + +The ITU-T G.994.1 vendor ID should typically identify the vendor of the xTU-C ITU-T G.994.1 functionality, whether implemented in hardware or software. It is not intended to indicate the system integrator. Further details are given in [ITU-T G.994.1]. + +### **7.4.2 xTU-R ITU-T G.994.1 vendor identifier** + +The xTU-R ITU-T G.994.1 vendor ID is the vendor ID as inserted by the xTU-R in the ITU-T G.994.1 capabilities list request (CLR) message. It consists of 8 binary octets, with the same format as the xTU-C ITU-T G.994.1 vendor ID. + +The ITU-T G.994.1 vendor ID should typically identify the vendor of the xTU-R ITU-T G.994.1 functionality, whether implemented in hardware or software. It is not intended to indicate the system integrator. Further details are given in [ITU-T G.994.1]. + +### **7.4.3 xTU-C system vendor identifier** + +The xTU-C system vendor ID is the vendor ID as inserted by the xTU-C in the overhead messages ([ITU-T G.992.3], [ITU-T G.992.4], [ITU-T G.992.5] and [ITU-T G.993.2]). It consists of 8 binary octets, with same format as the xTU-C ITU-T G.994.1 vendor ID. + +The xTU-C system vendor ID should typically identify the xTU-C system integrator. In this context, the system integrator usually refers to the vendor of the smallest field-replaceable unit. As such, the xTU-C system vendor ID may not be the same as the xTU-C ITU-T G.994.1 vendor ID. + +### **7.4.4 xTU-R system vendor identifier** + +The xTU-R system vendor ID is the vendor ID as inserted by the xTU-R in the EOC ([ITU-T G.992.1] and [ITU-T G.992.2]) and the overhead messages ([ITU-T G.992.3], [ITU-T G.992.4], [ITU-T G.992.5] and [ITU-T G.993.2]). It consists of 8 binary octets, with same format as the xTU-C ITU-T G.994.1 vendor ID. + +The xTU-R system vendor ID should typically identify the xTU-R system integrator. In this context, the system integrator usually refers to the vendor of the smallest field-replaceable unit. As such, the xTU-R system vendor ID may not be the same as the xTU-R ITU-T G.994.1 vendor ID. + +### **7.4.5 xTU-C version number** + +The xTU-C version number is the version number as inserted by the xTU-C in the overhead messages ([ITU-T G.992.3], [ITU-T G.992.4], [ITU-T G.992.5] and [ITU-T G.993.2]). It is for version control and is vendor specific information. It consists of up to 16 binary octets. + +### **7.4.6 xTU-R version number** + +The xTU-R version number is the version number as inserted by the xTU-R in the embedded operations channelEOC ([ITU-T G.992.1] and [ITU-T G.992.2]) or overhead messages ([ITU-T G.992.3], [ITU-T G.992.4], [ITU-T G.992.5] and [ITU-T G.993.2]). It is for version control. It consists of up to 16 American standard code for information interchange (ASCII) characters. The characters should be in the range of printable ASCII characters, i.e., the decimal code 32 to 126. It shall contain the xTU-R firmware version and the xTU-R model. Both shall be encoded in this order and separated by a space character, i.e., " ". + +The xTU-R version number of equipment prior to this Recommendation may contain up to 16 vendor specific binary octets. These should be replaced by the information specified above at the time of the next firmware or hardware update. + +NOTE – This field is intended to contain information about the firmware and model of the xTU-R physical layer interface (chipset). + +NOTE – The ASCII characters should be printable as the version number is intended to be displayed. + +### **7.4.7 xTU-C serial number** + +The xTU-C serial number is the serial number as inserted by the xTU-C in the overhead messages ([ITU-T G.992.3], [ITU-T G.992.4], [ITU-T G.992.5] and [ITU-T G.993.2]). It is vendor specific information. It consists of up to 32 ASCII characters. + +Note that the combination of system vendor ID and serial number creates a unique number for each xTU-C. + +### **7.4.8 xTU-R serial number** + +The xTU-R serial number is the serial number as inserted by the xTU-R in the EOC ([ITU-T G.992.1] and [ITU-T G.992.2]) or overhead messages ([ITU-T G.992.3], [ITU-T G.992.4], [ITU-T G.992.5] and [ITU-T G.993.2]). It consists of up to 32 ASCII characters. The characters should be in the range of printable ASCII characters, i.e., the decimal code 32 to 126. It shall contain the equipment serial number, the equipment model and the equipment firmware version. All shall be encoded in this order and separated by space characters, i.e., " ". + +The xTU-R serial number of equipment prior to this Recommendation may contain up to 32 vendor specific ASCII characters. These should be replaced by the information specified above at the time of the next firmware or hardware update. + +Note that the combination of system vendor ID and serial number creates a unique number for each xTU-R. + +NOTE – The ASCII characters should be printable as the serial number is intended to be displayed. + +### **7.4.9 xTU-C self-test result** + +This parameter specifies the xTU-C self-test result. It is coded as a 32-bit integer. The most significant octet of the self-test result is 00hex if the self-test is passed and 01hex if the self-test is failed. The interpretation of the other octets is vendor discretionary and can be interpreted in combination with ITU-T G.994.1 and system vendor IDs. + +### **7.4.10 xTU-R self-test result** + +This parameter specifies the xTU-R self-test result. It is coded as a 32-bit integer. The most significant octet of the self-test result is 00hex if the self-test is passed and 01hex if the self-test is failed. The interpretation of the other octets is vendor discretionary and can be interpreted in combination with ITU-T G.994.1 and system vendor IDs. + +### **7.4.11 xTU-C transmission system capabilities** + +This parameter specifies the xTU-C capability list of the different transmission system types. It is coded in a bit-map representation with the bits specified in clause 7.3.1.1.1. This parameter may be derived from the handshaking procedures specified in [ITU-T G.994.1]. + +### **7.4.12 xTU-R transmission system capabilities** + +This parameter specifies the xTU-R capability list of the different transmission system types. It is coded in a bit-map representation with the bits specified in clause 7.3.1.1.1. This parameter may be derived from the handshaking procedures specified in [ITU-T G.994.1]. + +### **7.4.13 Inventory information for [ITU-T G.993.5]** + +#### **7.4.13.1 Vectoring control entity identifier** + +For the line in a vectored group, the vectoring control entity (VCE) ID (VCE\_ID) uniquely identifies the VCE that manages and controls the vectored group to which the line belongs. It consists of one octet and valid ranges are from 1 to 255. A special value means the line is not in a vectored group. + +#### **7.4.13.2 Vectoring control entity port index** + +For the line in a vectored group, the VCE port index (VCE\_port\_index) is the physical index that uniquely identifies the VCE port to which the line is connected. It is an integer from 1 to the maximum number of lines supported by the VCE. + +NOTE – The combination of VCE ID and VCE port index creates a unique ID for each vectored VTU-O/-R. + +### **7.4.14 Inventory information for VDSL2-LR** + +#### **7.4.14.1 VTU-O VDSL2-LR support** + +The VTU-O VDSL2-LR support (VDSL2-LR\_SUPPORT\_O) parameter indicates the support of VDSL2-LR mode by the VTU-O. The parameter is set to 0 if VDSL2-LR mode is not supported and set to 1 if VDSL2-LR mode is supported. + +#### **7.4.14.2 VTU-R VDSL2-LR support** + +The VTU-R VDSL2-LR support (VDSL2-LR\_SUPPORT\_R) parameter indicates the support of VDSL2-LR mode by the VTU-R. The parameter is set to 0 if VDSL2-LR mode is not supported and set to 1 if VDSL2-LR mode is supported. + +### **7.4.15 Inventory information for STRONGFEXT MODE** + +#### **7.4.15.1 VTU-O STRONGFEXT mode support** + +The VTU-O STRONGFEXT mode support (STRONGFEXT\_MODE\_SUPPORT\_O) parameter indicates the support of operation according to [ITU-T G.993.5] Annex A by the VTU-O. The parameter is set to 0 if STRONGFEXT mode is not supported and set to 1 if STRONGFEXT mode is supported. + +#### **7.4.15.2 VTU-R STRONGFEXT mode support** + +The VTU-R STRONGFEXT mode support (STRONGFEXT\_MODE\_SUPPORT\_R) parameter indicates the support of operation according to [ITU-T G.993.5] Annex A by the VTU-R. The parameter is set to 0 if STRONGFEXT mode is not supported and set to 1 if STRONGFEXT mode is supported. + +## **7.5 Test, diagnostic and status parameters** + +NOTE – The requirement on how recent the AN MIB data are and on the update time for test parameters does not include the transfer time between the transceiver and the AN MIB. The transfer time is implementation specific. + +### **7.5.1 Line test, diagnostic and status parameters** + +#### **7.5.1.1 xDSL transmission system** + +This parameter specifies the transmission system in use. It is coded in a bit-map representation with the bits specified in clause 7.3.1.1.1. This parameter may be derived from the handshaking procedures defined in [ITU-T G.994.1]. + +#### **7.5.1.2 VDSL2 profile** + +This parameter specifies the profile in use. It is coded in a bit-map representation with the bits specified in clause 7.3.1.1.11. This parameter may be derived from the handshaking procedures specified in [ITU-T G.994.1]. + +#### **7.5.1.3 VDSL2 limit power spectral density mask and band plan** + +This parameter specifies the limit PSD mask and band plan in use. It is coded in a bit-map representation with the bits specified in clause 7.3.1.2.16. + +#### **7.5.1.4 VDSL2 US0 PSD mask** + +This parameter specifies the US0 PSD mask in use. It is coded in a bit-map representation with the bits specified in clause 7.3.1.2.18. This parameter may be derived from the handshaking procedures specified in [ITU-T G.994.1]. + +#### 7.5.1.5 Line power management state + +The line has four possible power management states, numbered 0 to 3 and corresponding to the following. + +L0 – Synchronized – This line state (L0) is when the line has full transmission (i.e., showtime) + +L1 – Power down data transmission – This line state (L1) is when there is transmission on the line but the net data rate is reduced (e.g., only for OAM and higher layer connection and session control). This state applies to [ITU-T G.992.2] only + +L2 – Power down data transmission – This line state (L2) is when there is transmission on the line, but the net data rate is reduced (e.g., only for OAM and higher layer connection and session control). This state applies to [ITU-T G.992.3] and [ITU-T G.992.4] only + +L3 – No-power – This line state (L3) is when there is no power transmitted on the line at all. + +NOTE – This configuration parameter maps to the OperStatus of the line, which is part of the GeneralInformationGroup object group specified in [b-IETF RFC 2233], and may not need to be duplicated in the ADSL MIB. See also [b-IETF RFC 2662] and [b-IETF RFC 3440]. The operational status of the line is up in the L0, L1 or L2 state (i.e., during showtime) and is down in the L3 state (e.g., during (short) initialization and loop diagnostic mode). + +#### 7.5.1.6 Initialization success/failure cause + +This parameter indicates whether the last full initialization procedure was successful. If the last initialization procedure was not successful, this parameter provides the reason. It is coded as an integer in the 0 to 6 range, as follows. + +0 Successful + +1 Configuration error + +This error occurs with inconsistencies in configuration parameters. For example, when the line is initialized in an xDSL transmission system where an xTU does not support the configured maximum delay or the configured minimum or maximum data rate for one or more bearer channels + +2 Configuration not feasible on the line + +This error occurs if the minimum data rate cannot be reached on the line with the minimum noise margin, maximum PSD level, maximum delay and maximum bit error ratio for one or more bearer channels + +3 Communication problem + +This error occurs, for example, due to corrupted messages or bad syntax messages or if no common mode can be selected in the ITU-T G.994.1 handshaking procedure or due to a timeout + +4 No peer xTU detected + +This error occurs if the peer xTU is not powered or not connected or if the line is too long to allow detection of a peer xTU + +5 Any other or unknown initialization failure cause + +6 ITU-T G.998.4 retransmission mode was not selected while RTX\_MODE = FORCED or with RTX\_MODE = RTX\_TESTMODE + +#### 7.5.1.7 Downstream last transmitted state + +This parameter represents the last successful transmitted initialization state in the downstream direction in the last full initialization performed on the line. Initialization states are specified in the individual xDSL Recommendations and are counted from 0 (if [ITU-T G.994.1] is used) or 1 + +(if [ITU-T G.994.1] is not used) up to showtime. This parameter must be interpreted along with the xDSL transmission system. + +This parameter is available only when, after a failed full initialization, the loop diagnostic procedures are activated on the line. Loop diagnostic procedures can be activated by the operator of the system (through the line state forced line configuration parameter) or autonomously by the xTU-C or xTU-R. + +#### **7.5.1.8 Upstream last transmitted state** + +This parameter represents the last successful transmitted initialization state in the upstream direction in the last full initialization performed on the line. Initialization states are specified in the individual xDSL Recommendations and are counted from 0 ([if ITU-T G.994.1] is used) or 1 (if [ITU-T G.994.1] is not used) up to showtime. This parameter must be interpreted along with the xDSL Transmission System. + +This parameter is available only when, after a failed full initialization, the loop diagnostic procedures are activated on the line. Loop diagnostic procedures can be activated by the operator of the system (through the line state forced line configuration parameter) or autonomously by the xTU-C or xTU-R. + +#### **7.5.1.9 Downstream line attenuation per band** + +The downstream line attenuation per band (LATNDs) parameter is specified per usable band. It is squared magnitude of the channel characteristics function $H(f)$ averaged over this band, and measured during loop diagnostic mode and initialization. The exact specification is included in the relevant xDSL ITU-T Recommendation. The downstream line attenuation ranges per band from 0 dB to +127 dB, with 0.1 dB steps. A special value indicates the line attenuation per band is out of range to be represented. + +For ADSL systems, a single parameter is specified as a single downstream band is usable. + +#### **7.5.1.10 Upstream line attenuation per band** + +The upstream line attenuation per band (LATNUs) parameter is specified per usable band. It is the squared magnitude of the channel characteristics function $H(f)$ averaged over this band and measured during loop diagnostic mode and initialization. The exact specification is included in the relevant xDSL ITU-T Recommendation. The upstream line attenuation ranges per band from 0 dB to +127 dB, with 0.1 dB steps. A special value indicates the line attenuation per band is out of range to be represented. + +For ADSL systems, a single parameter is defined as a single upstream band is usable. + +#### **7.5.1.11 Downstream signal attenuation per band** + +The downstream signal attenuation per band (SATNDs) parameter is specified per usable band. It is the measured difference between the total power transmitted in this band by the xTU-C and the total power received in this band by the xTU-R in this band during loop diagnostic mode, initialization and showtime. The exact specification is included in the relevant DSL ITU-T Recommendation. The downstream signal attenuation per band ranges from 0 dB to +127 dB, with 0.1 dB steps. A special value indicates the signal attenuation per band is out of the range to be represented. + +For ADSL systems, a single parameter is specified as a single downstream band is usable. + +NOTE – During showtime, only a subset of the subcarriers may be transmitted by the xTU-C, as compared to loop diagnostic mode and initialization. Therefore, the downstream signal attenuation value during showtime may be significantly lower than the downstream signal attenuation value during loop diagnostic mode and initialization. + +#### **7.5.1.12 Upstream signal attenuation per band** + +The upstream signal attenuation per band (SATNUs) parameter is specified per usable band. It is the measured difference, in decibels, between the total power transmitted in this band by the xTU-R and + +the total power received in this band by the xTU-C in this band during loop diagnostic mode, initialization and showtime. The exact specification is included in the relevant DSL ITU-T Recommendation. The upstream signal attenuation per band ranges from 0 dB to +127 dB, with 0.1 dB steps. A special value indicates the signal attenuation per band is out of the range to be represented. + +For ADSL systems, a single parameter is defined as a single upstream band is usable. + +NOTE – During showtime, only a subset of the subcarriers may be transmitted by the xTU-R, as compared to loop diagnostic mode and initialization. Therefore, the upstream signal attenuation value during showtime may be significantly lower than the upstream signal attenuation value during loop diagnostic mode and initialization. + +#### **7.5.1.13 Downstream signal-to-noise ratio margin** + +The downstream signal-to-noise ratio margin (SNRMds) is the maximum increase, in decibels, of the noise power received at the xTU-R, such that the BER requirements are met for all downstream bearer channels. The downstream SNR margin ranges from –64 dB to +63 dB, with 0.1 dB steps. A special value indicates the parameter is out of range to be represented. The same SNRMds format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT SNRMds and NEXT SNRMds. + +NOTE – The downstream SNR margin measurement at the xTU-R may take up to 10 s. + +##### **7.5.1.13.1 Far-end crosstalk downstream signal-to-noise ratio margin** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, downstream SNR margin (see clause 7.5.1.13) measured during FEXTR duration at ATU-R is specified as the FEXT downstream signal-to-noise ratio margin (FEXT SNRMds). + +##### **7.5.1.13.2 Near- end crosstalk downstream signal-to-noise ratio margin** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, downstream SNR margin (see clause 7.5.1.13) measured during NEXTR duration at ATU-R is specified as the NEXT downstream signal-to-noise ratio margin (NEXT SNRMds). + +#### **7.5.1.14 Downstream signal-to-noise ratio margin per band** + +This parameter is specified per usable band. The downstream signal-to-noise ratio margin per band (SNRMpbds) is the maximum increase, in decibels, of the noise power received at the xTU-R, such that the BER requirements are met for all downstream bearer channels. The SNRMpbds ranges from –64 dB to +63 dB, with 0.1 dB steps. A special value indicates the parameter is out of the range to be represented. + +NOTE – The SNRMpbds measurement at the xTU-R may take up to 10 s. + +#### **7.5.1.15 Actual downstream signal-to-noise ratio mode (ACTSNRMODEds)** + +The actual downstream signal-to-noise ratio mode (ACTSNRMODEds) parameter indicates whether the transmitter referred virtual noise is active on the line in the downstream direction. If ACTSNRMODEds equals 1, the virtual noise is inactive. If ACTSNRMODEds equals 2, the virtual noise is active. If ACTSNRMODEds equals 4, the virtual noise together with the virtual noise scaling factor is active. + +#### **7.5.1.16 Upstream signal-to-noise ratio margin** + +The upstream signal-to-noise ratio margin (SNRMus) is the maximum increase, in decibels, of the noise power received at the xTU-C, such that the BER requirements are met for all upstream bearer channels. The SNRMus ranges from –64 dB to +63 dB, with 0.1 dB steps. A special value indicates the parameter is out of the range to be represented. The same SNRMus format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT SNRMus and NEXT SNRMus. + +NOTE – The SNRMus measurement at the xTU-C may take up to 10 s. + +##### **7.5.1.16.1 Far-end crosstalk upstream signal-to-noise ratio margin** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, upstream SNR margin (see clause 7.5.1.16) measured during FEXTC duration at ATU-C is specified as the FEXT upstream signal-to-noise ratio margin (FEXT SNRMus). + +##### **7.5.1.16.2 Near- end crosstalk Upstream signal-to-noise ratio margin** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, upstream SNR margin (see clause 7.5.1.16) measured during NEXTC duration at ATU-C is specified as the NEXT upstream signal-to-noise ratio margin (NEXT SNRMus). + +#### **7.5.1.17 Upstream signal-to-noise ratio margin per band** + +This parameter is specified per usable band. The upstream signal-to-noise ratio margin per band (SNRMpbus) is the maximum increase in decibels of the noise power received at the xTU-C, such that the BER requirements are met for all upstream bearer channels. The SNRMpbus ranges from –64 dB to +63 dB, with 0.1 dB steps. A special value indicates the parameter is out of the range to be represented. + +NOTE – The SNRMpbus measurement at the xTU-C may take up to 10 s. + +#### **7.5.1.18 Actual upstream signal-to-noise ratio mode** + +The actual upstream signal-to-noise ratio mode (ACTSNRMODEus) parameter indicates the type of virtual noise that is active on the line in the upstream direction. If ACTSNRMODEus equals 1, the virtual noise is inactive. If ACTSNRMODEus equals 2, the transmitter referred virtual noise is active. If ACTSNRMODEus equals 3, the receiver referred virtual noise is active. If ACTSNRMODEus equals 4, the receiver referred virtual noise together with the virtual noise scaling factor is active. + +#### **7.5.1.19 Downstream maximum attainable data rate** + +The downstream maximum attainable data rate (ATTNDRds) parameter indicates the maximum downstream net data rate currently attainable by the xTU-C transmitter and the xTU-R receiver. The rate is coded in steps of 1 000 bit/s. The same ATTNDRds format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT ATTNDRds and NEXT ATTNDRds. + +##### **7.5.1.19.1 Far-end crosstalk downstream maximum attainable data rate** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the maximum downstream net data rate (see clause 7.5.1.19) calculated from FEXT downstream $\text{SNR}(f)$ (see clause 7.5.1.28.3.1) is specified as the FEXT downstream maximum attainable data rate (FEXT ATTNDRds). + +##### **7.5.1.19.2 Near- end crosstalk downstream maximum attainable data rate** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the maximum downstream net data rate (see clause 7.5.1.19) calculated from NEXT downstream $\text{SNR}(f)$ (see clause 7.5.1.28.3.2) is specified as the NEXT downstream maximum attainable data rate (NEXT ATTNDRds). + +#### **7.5.1.20 Upstream maximum attainable data rate** + +The upstream maximum attainable data rate (ATTNDRus) parameter indicates the maximum upstream net data rate currently attainable by the xTU-R transmitter and the xTU-C receiver. The rate is coded in steps of 1 000 bit/s. The same ATTNDRus format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT ATTNDRus and NEXT ATTNDRus. + +##### **7.5.1.20.1 Far-end crosstalk upstream maximum attainable data rate** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the maximum upstream net data rate (see clause 7.5.1.20) calculated from FEXT upstream $\text{SNR}(f)$ + +(see clause 7.5.1.28.6.1) is specified as the FEXT upstream maximum attainable data rate (FEXT ATTNDRus). + +##### **7.5.1.20.2 Near- end crosstalk upstream maximum attainable data rate** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the maximum upstream net data rate (see clause 7.5.1.20) calculated from NEXT upstream SNR( $f$ ) (see clause 7.5.1.28.6.2) is specified as the NEXT upstream maximum attainable data rate (NEXT ATTNDRus). + +#### **7.5.1.21 Downstream actual power spectral density** + +The downstream actual power spectral density (ACTPSDds) parameter is the average downstream transmit PSD over the used subcarriers (subcarriers to which downstream user data are allocated) delivered by the xTU-C at the U-C reference point, at the instant of measurement. The PSD level ranges from $-90$ dBm/Hz to $0$ dBm/Hz, with $0.1$ dBm/Hz steps. A special value indicates the parameter is out of range to be represented. The same ACTPSDds format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT ACTPSDds and NEXT ACTPSDds. + +NOTE – The ACTPSDds is the sum, in decibels, of the REFPSDds and RMSGIids. See clause 8.5.1 of [ITU-T G.992.3]. + +##### **7.5.1.21.1 Far-end crosstalk downstream actual power spectral density** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the average downstream transmit PSD over the used subcarriers (see clause 7.5.1.21) calculated from the REFPSDds and RMSGIids for FEXTR duration is specified as the FEXT downstream actual power spectrum density (FEXT ACTPSDds). + +##### **7.5.1.21.2 Near- end crosstalk downstream actual power spectral density** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the average downstream transmit PSD over the used subcarriers (see clause 7.5.1.21) calculated from the REFPSDds and RMSGIids for NEXTR duration is specified as the NEXT downstream actual power spectral density (NEXT ACTPSDds). + +#### **7.5.1.22 Upstream actual power spectral density** + +The upstream actual power spectral density (ACTPSDus) parameter is the average upstream transmit PSD over the used subcarriers (subcarriers to which upstream user data are allocated) delivered by the xTU-R at the U-R reference point, at the instant of measurement. The PSD level ranges from $-90$ dBm/Hz to $0$ dBm/Hz, with $0.1$ dBm/Hz steps. A special value indicates the parameter is out of the range to be represented. The same ACTPSDus format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT ACTPSDus and NEXT ACTPSDus. + +NOTE – The upstream actual power spectrum density is the sum, in deciBels, of the REFPSDus and RMSGIus. See clause 8.5.1 of [ITU-T G.992.3]. + +##### **7.5.1.22.1 Far-end crosstalk upstream actual power spectral density** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the average upstream transmit PSD over the used subcarriers (see clause 7.5.1.22) calculated from the REFPSDus and RMSGIus for FEXTC duration is specified as the FEXT upstream actual power spectral density (FEXT ACTPSDus). + +##### **7.5.1.22.2 Near- end crosstalk upstream actual power spectral density** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the average downstream transmit PSD over the used subcarriers (see clause 7.5.1.22) calculated from the REFPSDus and RMSGIus for NEXTC duration is specified as the NEXT upstream actual power spectral density (NEXT ACTPSDus). + +#### **7.5.1.23 Estimated upstream power back-off electrical length** + +##### **7.5.1.23.1 VTU-O estimated upstream power back-off electrical length** + +The VTU-O estimated upstream power back-off electrical length (UPBOKLE) parameter contains the estimated electrical length expressed in decibels at 1 MHz, $kl_0$ (see O-UPDATE in clause 12.3.3.2.1.2 of [ITU-T G.993.2]). This is the final electrical length that would have been sent from the VTU-O to the VTU-R if the electrical length was not forced by the CO-MIB. The value ranges from 0 dB to 128 dB, in steps of 0.1 dB. + +##### **7.5.1.23.2 VTU-R estimated upstream power back-off electrical length** + +The VTU-R estimated upstream power back-off electrical length (UPBOKLE-R) parameter contains the electrical length estimated by the VTU-R expressed in decibels at 1 MHz. This is the value contained in the message R-MSG1 (see clause 12.3.3.2.2.1 of [ITU-T G.993.2]). The value ranges from 0 dB to 128 dB, in steps of 0.1 dB. + +##### **7.5.1.23.3 VTU-O estimated upstream power back-off electrical length per band (UPBOKLE-pb)** + +This parameter is a vector of UPBO electrical length per-band estimates for each supported upstream band, expressed in decibels at 1 MHz ( $kl_0$ ) calculated by the VTU-O, based on separate measurements in the supported upstream bands excluding USO. The value ranges from 0 dB to 128 dB in steps of 0.1 dB, with special value 204.7, which indicates that the estimate is greater than 128 dB. This parameter is required for the alternative electrical length estimation method (ELE-M1). + +##### **7.5.1.23.4 VTU-R estimated upstream power back-off electrical length per band (UPBOKLE-R-pb)** + +This parameter is a vector of UPBO electrical length per-band estimates for each supported downstream band, expressed in decibels at 1 MHz ( $kl_0$ ) calculated by the VTU-R, based on separate measurements in the supported downstream bands. The value ranges from 0 dB to 128 dB in steps of 0.1 dB, with special value 204.7, which indicates that the estimate is greater than 128 dB. This parameter is required for the alternative electrical length estimation method (ELE-M1). + +##### **7.5.1.23.5 UPBO downstream receiver signal level threshold (RXTHRSHds)** + +This parameter reports the downstream received signal level threshold value used in the alternative electrical length estimation method (ELE-M1) in clause 7.2.1.3.2.2. This parameter represents an offset from –100 dBm/Hz, and ranges from –64 dB to 0 dB in steps of 1 dB. + +##### **7.5.1.23.6 UPBO upstream receiver signal level threshold (RXTHRSHus)** + +This parameter reports the upstream received signal level threshold value used in the alternative electrical length estimation method (ELE-M1) in clause 7.2.1.3.2.2. This parameter represents an offset from –100 dBm/Hz, and ranges from –64 dB to 0 dB in steps of 1 dB. + +##### **7.5.1.23.7 "Actual Alternative Electrical Length Estimation Mode" (ACT-AELE-MODE)** + +This parameter reports the actual AELE-MODE used in clause 7.2.1.3.2.1 of [ITU-T G.993.2]. The value of this parameter is 0, 1, 2 or 3. + +#### **7.5.1.24 Downstream actual aggregate transmit power (ACTATPds)** + +This parameter is the total amount of transmit power delivered by the xTU-C at the U-C reference point, at the instant of measurement. The total output power level ranges from –31 dBm to +31 dBm, with 0.1 dB steps. A special value indicates the parameter is out of the range to be represented. The same ACTATPds format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT ACTATPds and NEXT ACTATPds. + +NOTE – The downstream nominal aggregate transmit power may be taken as a best estimate of the parameter. See clause 8.12.3.8 of [ITU-T G.992.3] and clause 10.3.4.2.1 of [ITU-T G.993.2]. + +##### **7.5.1.24.1 Far-end crosstalk downstream actual aggregate transmit power (FEXT ACTATPds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the total amount of transmit power (see clause 7.5.1.24) calculated from PSDs measured during FEXTR duration at ATU-R is specified as the FEXT downstream actual aggregate transmit power (FEXT ACTATPds). + +##### **7.5.1.24.2 Near- end crosstalk downstream actual aggregate transmit power (NEXT ACTATPds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the total amount of transmit power (see clause 7.5.1.24) calculated from PSDs measured during NEXTR duration at ATU-R is specified as the NEXT downstream actual aggregate transmit power (NEXT ACTATPds). + +#### **7.5.1.25 Upstream actual aggregate transmit power (ACTATPus)** + +This parameter is the total amount of transmit power delivered by the xTU-R at the U-R reference point, at the instant of measurement. The total output power level ranges from –31 dBm to +31 dBm, with 0.1 dB steps. A special value indicates the parameter is out of the range to be represented. The same ACTATPus format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT ACTATPus and NEXT ACTATPus. + +NOTE – The upstream nominal aggregate transmit power may be taken as a best estimate of the parameter. See clause 8.12.3.8 of [ITU-T G.992.3] and clause 10.3.4.2.1 of [ITU-T G.993.2]. + +##### **7.5.1.25.1 Far-end crosstalk upstream actual aggregate transmit power (FEXT ACTATPus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the total amount of transmit power (see clause 7.5.1.25) calculated from PSDs measured during FEXTC duration at ATU-C is specified as the FEXT upstream actual aggregate transmit power (FEXT ACTATPus). + +##### **7.5.1.25.2 Near- end crosstalk upstream actual aggregate transmit power (NEXT ACTATPus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the total amount of transmit power (see clause 7.5.1.25) calculated from PSDs measured during NEXTC duration at ATU-C is specified as the NEXT upstream actual aggregate transmit power (NEXT ACTATPus). + +#### **7.5.1.26 Channel characteristics function per subcarrier** + +This function is specified in clauses 8.12.3.1 of [ITU-T G.992.3] and clause 11.4.1.1.1 of [ITU-T G.993.2]. + +NOTE – In case of ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, see clause C.8.12.3.1 of [ITU-T G.992.3], in addition to clause 8.12.3.1 of [ITU-T G.992.3]. + +For [ITU-T G.993.2], the value of NSus and NSds are the indices of the highest supported upstream and downstream subcarriers, respectively, according to the selected profile (see clause 6 of [ITU-T G.993.2]). For ADSL, NSus is equal to NSCus-1 and NSds is equal to NSCds-1. + +##### **7.5.1.26.1 Downstream H(f) linear representation scale (HLINSCds)** + +This parameter is the scale factor to be applied to the downstream Hlin(*f*) values. It is represented as an unsigned integer in the range from 1 to $2^{16} - 1$ . This parameter is only available after a loop diagnostic procedure. + +##### 7.5.1.26.2 Downstream H(f) linear subcarrier group size (HLINGds) + +This parameter is the number of subcarriers per group used to report HLINpsds. The valid values are 1, 2, 4, 8 and 16. For ADSL, this parameter is equal to one and, for VDSL2, it is equal to the size of a subcarrier group used to compute these parameters (see clause 11.4.1 of [ITU-T G.993.2]). + +NOTE – The values of the subcarrier group size parameters (HLING, HLOGG, QLNG and SNRG) may not all be independent. + +##### 7.5.1.26.3 Downstream H(f) linear representation (HLINpsds) + +This parameter is an array of complex values in linear scale for downstream Hlin(*f*). Each array entry represents the Hlin( $f = i \times \text{HLINGds} \times \Delta f$ ) value for a particular subcarrier group index *i*, ranging from 0 to MIN(NSds,511). The Hlin(*f*) is represented as $((\text{HLINSCds}/2^{15}) \times ((a(i) + j \times b(i))/2^{15}))$ , where *a(i)* and *b(i)* are signed integers in the $(-2^{15} + 1)$ to $(+2^{15} - 1)$ range. A special value indicates that no measurement could be done for this subcarrier group because it is out of the passband or that the attenuation is out of the range to be represented. This parameter is only available after a loop diagnostic procedure. + +##### 7.5.1.26.4 Downstream H(f) logarithmic measurement time (HLOGMTds) + +This parameter contains the number of symbols used to measure the downstream Hlog(*f*) values. It is represented as an unsigned integer in the range from 1 to $2^{16} - 1$ . + +After a loop diagnostic procedure, this parameter shall contain the number of symbols used to measure the downstream Hlog(*f*). It should correspond to the value specified in the Recommendation (e.g., the number of symbols in a 1 s time interval for [ITU-T G.992.3]). + +##### 7.5.1.26.5 Downstream H(f) logarithmic subcarrier group size (HLOGGds) + +This parameter is the number of subcarriers per group used to report HLOGpsds. The valid values are 1, 2, 4, 8 and 16. For ADSL, this parameter is equal to one and, for VDSL2, it is equal to the size of a subcarrier group used to compute these parameters (see clause 11.4.1 of [ITU-T G.993.2]). + +##### 7.5.1.26.6 Downstream H(f) logarithmic representation (HLOGpsds) + +This parameter is an array of real values in decibels for downstream Hlog(*f*). Each array entry represents the real Hlog( $f = i \times \text{HLOGGds} \times \Delta f$ ) value for a particular subcarrier group subcarrier index *i*, ranging from 0 to MIN(NSds,511). The real Hlog(*f*) value is represented as $(6 - m(i)/10)$ , where *m(i)* is an unsigned integer in the range from 0 to 1 022. A special value indicates that no measurement could be done for this subcarrier group because it is out of the passband or that the attenuation is out of range to be represented. + +##### 7.5.1.26.7 Upstream H(f) linear representation scale (HLINSCus) + +This parameter is the scale factor to be applied to the upstream Hlin(*f*) values. It is coded in the same way as the related downstream parameter. This parameter is only available after a loop diagnostic procedure. + +##### 7.5.1.26.8 Upstream H(f) linear subcarrier group size (HLINGus) + +This parameter is the number of subcarriers per group used to report HLINpus. The valid values are 1, 2, 4 and 8. For ADSL, this parameter is equal to one and, for VDSL2, it is equal to the size of a subcarrier group used to compute these parameters (see clause 11.4.1 of [ITU-T G.993.2]). + +##### 7.5.1.26.9 Upstream H(f) linear representation (HLINpus) + +This parameter is an array of complex values in linear scale for upstream Hlin(*f*). It is coded in the same way as the related downstream parameter. This parameter is only available after a loop diagnostic procedure. + +##### **7.5.1.26.10 Upstream $H(f)$ logarithmic measurement time (HLOGMTus)** + +This parameter contains the number of symbols used to measure the upstream $H\log(f)$ values. It is an unsigned integer in the range from 1 to $2^{16} - 1$ . + +After a loop diagnostic procedure, this parameter shall contain the number of symbols used to measure the upstream $H\log(f)$ . It should correspond to the value specified in the Recommendation (e.g., the number of symbols in a 1 s time interval for [ITU-T G.992.3]). + +##### **7.5.1.26.11 Upstream $H(f)$ logarithmic subcarrier group size (HLOGGus)** + +This parameter is the number of subcarriers per group used to report HLOGpsus. The valid values are 1, 2, 4 and 8. For ADSL, this parameter is equal to one and, for VDSL2, it is equal to the size of a subcarrier group used to compute these parameters (see clause 11.4.1 of [ITU-T G.993.2]). + +##### **7.5.1.26.12 Upstream $H(f)$ logarithmic representation (HLOGpsus)** + +This parameter is an array of real values, in decibels, for upstream $H\log(f)$ . It is coded in the same way as the related downstream parameter. + +#### **7.5.1.27 Quiet line noise power spectral density per subcarrier** + +This function is specified in clauses 8.12.3.2 of [ITU-T G.992.3] and 11.4.1.1.2 of [ITU-T G.993.2]. + +NOTE – In the case of ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, see clause C.8.12.3.2 of [ITU-T G.992.3], in addition to clause 8.12.3.2 of [ITU-T G.992.3]. + +##### **7.5.1.27.1 Downstream quiet line noise power spectral density measurement time (QLNMTds)** + +This parameter contains the number of symbols used to measure the downstream $QLN(f)$ values. It is an unsigned integer in the range from 1 to $2^{16} - 1$ . The same QLNMTds format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT QLNMTds and NEXT QLNMTds. + +After a loop diagnostic procedure, this parameter shall contain the number of symbols used to measure the downstream $QLN(f)$ . It should correspond to the value specified in the Recommendation (e.g., the number of symbols in a 1 s time interval for [ITU-T G.992.3]). + +###### **7.5.1.27.1.1 Far-end crosstalk downstream quiet line noise power spectral density measurement time (FEXT QLNMTds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the number of symbols used to measured FEXT downstream $QLN(f)$ (see clause 7.5.1.27.3.1) is specified as the FEXT downstream quiet line noise PSD measurement time (FEXT QLNMTds). + +###### **7.5.1.27.1.2 Near- end crosstalk downstream quiet line noise power spectral density measurement time (NEXT QLNMTds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the number of symbols used to measured NEXT downstream $QLN(f)$ (see clause 7.5.1.27.3.2) is specified as the NEXT downstream quiet line noise PSD measurement time (NEXT QLNMTds). + +##### **7.5.1.27.2 Downstream $QLN(f)$ subcarrier group size (QLNGds)** + +This parameter is the number of subcarriers per group used to report QLNpsds. The valid values are 1, 2, 4, 8 and 16. For ADSL, this parameter is equal to one and, for VDSL2, it is equal to the size of a subcarrier group used to compute these parameters (see clause 11.4.1 of [ITU-T G.993.2]). + +##### **7.5.1.27.3 Downstream $QLN(f)$ (QLNpsds)** + +This parameter is an array of real values in decibels with reference to 1 mW per hertz for downstream $QLN(f)$ . Each array entry represents the $QLN(f = i \times QLNGds \times \Delta f)$ value for a particular subcarrier group index $i$ , ranging from 0 to $\text{MIN}(\text{NSds}, 511)$ . The $QLN(f)$ is represented as $(-23 - n(i)/2)$ , where + +$n(i)$ is an unsigned integer in the range from 0 to 254. A special value indicates that no measurement could be done for this subcarrier group because it is out of the passband or that the noise PSD is out of range to be represented. The same QLNpsds format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT QLNpsds and NEXT QLNpsds. + +###### **7.5.1.27.3.1 Far-end crosstalk downstream QLN(*f*) (FEXT QLNpsds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, downstream QLN(*f*) (see clause 7.5.1.27.3) measured during FEXTR duration at ATU-R is specified as the FEXT downstream QLN(*f*) (FEXT QLNpsds). + +###### **7.5.1.27.3.2 Near- end crosstalk downstream QLN(*f*) (NEXT QLNpsds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, downstream QLN(*f*) (see clause 7.5.1.27.3) measured during NEXTR duration at ATU-R is specified as the NEXT downstream QLN(*f*) (NEXT QLNpsds). + +##### **7.5.1.27.4 Upstream quiet line noise power spectral density measurement time (QLNMTus)** + +This parameter contains the number of symbols used to measure the upstream QLN(*f*) values. It is an unsigned integer in the range from 1 to $2^{16} - 1$ . The same QLNMTus format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT QLNMTus and NEXT QLNMTus. + +After a loop diagnostic procedure, this parameter shall contain the number of symbols used to measure the upstream QLN(*f*). It should correspond to the value specified in the Recommendation (e.g., the number of symbols in a 1 s time interval for [ITU-T G.992.3]). + +###### **7.5.1.27.4.1 Far-end crosstalk upstream quiet line noise power spectral density measurement time (FEXT QLNMTus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the number of symbols used to measure FEXT upstream QLN(*f*) (see clause 7.5.1.27.6.1) is specified as the FEXT upstream quiet line noise PSD measurement time (FEXT QLNMTus). + +###### **7.5.1.27.4.2 Near- end crosstalk upstream quiet line noise power spectral density measurement time (NEXT QLNMTus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the number of symbols used to measure NEXT upstream QLN(*f*) (see clause 7.5.1.27.6.2) is specified as the NEXT upstream quiet line noise PSD measurement time (NEXT QLNMTus). + +##### **7.5.1.27.5 Upstream QLN(*f*) subcarrier group size (QLNGus)** + +This parameter is the number of subcarriers per group used to report QLNpsus. The valid values are 1, 2, 4 and 8. For ADSL, this parameter is equal to one and, for VDSL2, it is equal to the size of a subcarrier group used to compute these parameters (see clause 11.4.1 of [ITU-T G.993.2]). + +##### **7.5.1.27.6 Upstream QLN(*f*) (QLNpsus)** + +This parameter is an array of real values in decibels with reference to 1 mW per hertz for upstream QLN(*f*). It is coded in the same way as the related downstream parameter. The same QLNpsus format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT QLNpsus and NEXT QLNpsus. + +###### **7.5.1.27.6.1 Far-end crosstalk upstream QLN(*f*) (FEXT QLNpsus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, upstream QLN(*f*) (see clause 7.5.1.27.6) measured during FEXTC duration at ATU-C is specified as the FEXT upstream QLN(*f*) (FEXT QLNpsus). + +#### **7.5.1.27.6.2 Near- end crosstalk upstream $QLN(f)$ (NEXT $QLNpsus$ )** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, upstream $QLN(f)$ (see clause 7.5.1.27.6) measured during NEXTC duration at ATU-C is specified as the NEXT upstream $QLN(f)$ (NEXT $QLNpsus$ ). + +#### **7.5.1.28 Signal-to-noise ratio per subcarrier** + +This function is specified in clauses 8.12.3.3 of [ITU-T G.992.3] and 11.4.1.1.3 of [ITU-T G.993.2]. + +NOTE – In case of ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, see clause C.8.12.3.3 of [ITU-T G.992.3], in addition to clause 8.12.3.3 of [ITU-T G.992.3]. + +##### **7.5.1.28.1 Downstream signal-to-noise ratio measurement time (SNRMTds)** + +This parameter contains the number of symbols used to measure the downstream $SNR(f)$ values. It is an unsigned integer in the range from 1 to $2^{16} - 1$ . The same SNRMTds format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT SNRMTds and NEXT SNRMTds. + +After a loop diagnostic procedure, this parameter shall contain the number of symbols used to measure the downstream $SNR(f)$ . It should correspond to the value specified in the Recommendation (e.g., the number of symbols in a 1 s time interval for [ITU-T G.992.3]). + +##### **7.5.1.28.1.1 Far-end crosstalk downstream signal-to-noise ratio measurement time (FEXT SNRMTds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the number of symbols used to measure FEXT downstream $SNR(f)$ values (see clause 7.5.1.28.3.1) is specified as the FEXT downstream SNR measurement time (FEXT SNRMTds). + +##### **7.5.1.28.1.2 Near- end crosstalk downstream signal-to-noise ratio measurement time (NEXT SNRMTds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the number of symbols used to measure NEXT Downstream $SNR(f)$ values (see clause 7.5.1.28.3.2) is specified as the NEXT downstream SNR measurement time (NEXT SNRMTds). + +##### **7.5.1.28.2 Downstream $SNR(f)$ subcarrier group size (SNRGds)** + +This parameter is the number of subcarriers per group used to report SNRpsds. The valid values are 1, 2, 4, 8 and 16. For ADSL, this parameter is equal to one and, for VDSL2, it is equal to the size of a subcarrier group used to compute these parameters (see clause 11.4.1 of [ITU-T G.993.2]). + +##### **7.5.1.28.3 Downstream $SNR(f)$ (SNRpsds)** + +This parameter is an array of real values in decibels for downstream $SNR(f)$ . Each array entry represents the $SNR(f = i \times SNRGds \times \Delta f)$ value for a particular subcarrier group index $i$ , ranging from 0 to $MIN(NSds, 511)$ . The $SNR(f)$ is represented as $(-32 + snr(i)/2)$ , where $snr(i)$ is an unsigned integer in the range from 0 to 254. A special value indicates that no measurement could be done for this subcarrier group because it is out of the passband or that the SNR is out of range to be represented. The same SNRpsds format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT SNRpsds and NEXT SNRpsds. + +##### **7.5.1.28.3.1 Far-end crosstalk downstream $SNR(f)$ (FEXT SNRpsds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, downstream $SNR(f)$ (see clause 7.5.1.28.3) measured during FEXTR duration at ATU-R is specified as the FEXT downstream $SNR(f)$ (FEXT SNRpsds). + +#### **7.5.1.28.3.2 Near-end crosstalk downstream SNR(*f*) (NEXT SNRpsds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, downstream SNR(*f*) (see clause 7.5.1.28.3) measured during NEXTR duration at ATU-R is specified as the NEXT downstream SNR(*f*) (NEXT SNRpsds). + +#### **7.5.1.28.4 Upstream signal-to-noise ratio measurement time (SNRMTus)** + +This parameter contains the number of symbols used to measure the upstream SNR(*f*) values. It is an unsigned integer in the range from 1 to $2^{16} - 1$ . The same SNRMTus format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT SNRMTus and NEXT SNRMTus. + +After a loop diagnostic procedure, this parameter shall contain the number of symbols used to measure the upstream SNR(*f*). It should correspond to the value specified in the Recommendation (e.g., the number of symbols in a 1 s time interval for [ITU-T G.992.3]). + +#### **7.5.1.28.4.1 Far-end crosstalk upstream signal-to-noise ratio measurement time (FEXT SNRMTus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the number of symbols used to measure FEXT upstream SNR(*f*) values (see clause 7.5.1.28.6.1) is specified as the FEXT upstream SNR measurement time (FEXT SNRMTus). + +#### **7.5.1.28.4.2 Near- end crosstalk upstream signal-to-noise ratio measurement time (NEXT SNRMTus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the number of symbols used to measure NEXT upstream SNR(*f*) values (see clause 7.5.1.28.6.2) is specified as the NEXT upstream SNR measurement time (NEXT SNRMTus). + +#### **7.5.1.28.5 Upstream SNR(*f*) subcarrier group size (SNRGus)** + +This parameter is the number of subcarriers per group used to report SNRpsus. The valid values are 1, 2, 4 and 8. For ADSL, this parameter is equal to one and, for VDSL2, it is equal to the size of a subcarrier group used to compute these parameters (see clause 11.4.1 of [ITU-T G.993.2]). + +#### **7.5.1.28.6 Upstream SNR(*f*) (SNRpsus)** + +This parameter is an array of real values in decibels for upstream SNR(*f*). It is coded in the same way as the related downstream parameter. The same SNRpsus format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT SNRpsus and NEXT SNRpsus. + +#### **7.5.1.28.6.1 Far-end crosstalk upstream SNR(*f*) (FEXT SNRpsus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, upstream SNR(*f*) (see clause 7.5.1.28.6) measured during FEXTC duration at ATU-C is specified as the FEXT upstream SNR(*f*) (FEXT SNRpsus). + +#### **7.5.1.28.6.2 Near- end crosstalk upstream SNR(*f*) (NEXT SNRpsus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, upstream SNR(*f*) (see clause 7.5.1.28.6) measured during NEXTC duration at ATU-C is specified as the NEXT upstream SNR(*f*) (NEXT SNRpsus). + +### **7.5.1.29 Bits and gains allocation per subcarrier** + +#### **7.5.1.29.1 Downstream bits allocation (BITSpsds)** + +This parameter defines the downstream bits allocation table per subcarrier. It is an array of integer values in the 0 to 15 range for subcarriers 0 to NSds. The same BITSpsds format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT BITSpsds and NEXT BITSpsds. + +The reported bits of subcarriers out of the downstream MEDLEY set shall be set to 0. + +This parameter shall be reported with the most recent values when read over the Q-interface. + +#### **7.5.1.29.1.1 Far-end crosstalk downstream bits allocation (FEXT BITSpsds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the downstream bits allocation table per subcarrier (see clause 7.5.1.29.1) used during FEXTR duration is specified as the FEXT downstream bits allocation (FEXT BITSpsds). + +#### **7.5.1.29.1.2 Near- end crosstalk downstream bits allocation (NEXT BITSpsds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the downstream bits allocation table per subcarrier (see clause 7.5.1.29.1) used during NEXTR duration is specified as the NEXT downstream bits allocation (NEXT BITSpsds). + +#### **7.5.1.29.2 Upstream bits allocation (BITSpsus)** + +This parameter specifies the upstream bits allocation table per subcarrier. It is an array of integer values in the 0 to 15 range for subcarriers 0 to NSus. The same BITSpsus format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT BITSpsus and NEXT BITSpsus. + +The reported bits of subcarriers out of the upstream MEDLEY set shall be set to 0. + +This parameter shall be reported with the most recent values when read over the Q-interface. + +#### **7.5.1.29.2.1 Far-end crosstalk upstream bits allocation (FEXT BITSpsus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the upstream bits allocation table per subcarrier (see clause 7.5.1.29.2) used during FEXTC duration is specified as the FEXT upstream bits allocation (FEXT BITSpsus). + +#### **7.5.1.29.2.1 Near- end crosstalk upstream bits allocation (NEXT BITSpsus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the upstream bits allocation table per subcarrier (see clause 7.5.1.29.2) used during NEXTC duration is specified as the NEXT upstream bits allocation (NEXT BITSpsus). + +#### **7.5.1.29.3 Downstream gains allocation (GAINspds)** + +This parameter specifies the downstream gains allocation table per subcarrier. It is an array of integer values in the 0 to 4 093 range for subcarriers 0 to NSds. The gain value is represented as a multiple of 1/512 on linear scale. The same GAINspds format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT GAINspds and NEXT GAINspds. + +The reported gains of subcarriers out of the downstream MEDLEY set shall be set to 0. + +This parameter shall be reported with the most recent values when read over the Q-interface. + +#### **7.5.1.29.3.1 Far-end crosstalk downstream gains allocation (FEXT GAINspds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the downstream gains allocation table per subcarrier (see clause 7.5.1.29.3) used during FEXTR duration is specified as the FEXT downstream gains allocation (FEXT GAINspds). + +#### **7.5.1.29.3.2 Near- end crosstalk downstream gains allocation (NEXT GAINspds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the downstream gains allocation table per subcarrier (see clause 7.5.1.29.3) used during NEXTR duration is specified as the NEXT downstream gains allocation (NEXT GAINspds). + +#### **7.5.1.29.4 Upstream gains allocation (GAINSpsus)** + +This parameter specifies the upstream gains allocation table per subcarrier. It is an array of integer values in the 0 to 4093 range for subcarriers 0 to NSus. The gain value is represented as a multiple of 1/512 on linear scale. The same GAINSpsus format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT GAINSpsus and NEXT GAINSpsus. + +The reported gains of subcarriers out of the upstream MEDLEY set shall be set to 0. + +This parameter shall be reported with the most recent values when read over the Q-interface. + +##### **7.5.1.29.4.1 Far-end crosstalk upstream gains allocation (FEXT GAINSpsus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the upstream gains allocation table per subcarrier (see clause 7.5.1.29.4) used during FEXTC duration is specified as the FEXT upstream gains allocation (FEXT GAINSpsus). + +##### **7.5.1.29.4.2 Near- end crosstalk upstream gains allocation (NEXT GAINSpsus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the upstream gains allocation table per subcarrier (see clause 7.5.1.29.4) used during NEXTC duration is specified as the NEXT upstream gains allocation (NEXT GAINSpsus). + +#### **7.5.1.29.5 Downstream transmit spectrum shaping (TSSpsds)** + +This parameter contains the downstream transmit spectrum shaping parameters expressed as the set of breakpoints exchanged during ITU-T G.994.1. Each breakpoint consists of a subcarrier index and the associated shaping parameter. The shaping parameter is an integer value in the 0 to 126 range. It is represented as a multiple of -0.5 dB. A special value indicates that the subcarrier is not transmitted. The same TSSpsds format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT TSSpsds and NEXT TSSpsds. + +##### **7.5.1.29.5.1 Far-end crosstalk downstream transmit spectrum shaping (FEXT TSSpsds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the downstream transmit spectrum shaping parameter set per subcarrier (see clause 7.5.1.29.5) used during FEXTR duration is specified as the FEXT downstream transmit spectrum shaping (FEXT TSSpsds). + +##### **7.5.1.29.5.2 Near- end crosstalk downstream transmit spectrum shaping (NEXT TSSpsds)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the downstream transmit spectrum shaping parameter set per subcarrier (see clause 7.5.1.29.5) used during NEXTR duration is specified as the NEXT downstream transmit spectrum shaping (NEXT TSSpsds). + +#### **7.5.1.29.6 Upstream transmit spectrum shaping (TSSpsus)** + +This parameter contains the upstream transmit spectrum shaping parameters expressed as the set of breakpoints exchanged during ITU-T G.994.1. Each breakpoint consists of a subcarrier index and the associated shaping parameter. The shaping parameter is an integer value in the 0 to 126 range. It is represented as a multiple of -0.5 dB. A special value indicates that the subcarrier is not transmitted. The same TSSpsus format shall be applied to ITU-T G.992.3 and ITU-T G.992.5 Annex C FEXT TSSpsus and NEXT TSSpsus. + +##### **7.5.1.29.6.1 Far-end crosstalk upstream transmit spectrum shaping (FEXT TSSpsus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the upstream transmit spectrum shaping parameter set per subcarrier (see clause 7.5.1.29.6) used during FEXTC duration is specified as the FEXT upstream transmit spectrum shaping (FEXT TSSpsus). + +#### **7.5.1.29.6.2 Near- end crosstalk upstream transmit spectrum shaping (NEXT TSSpsus)** + +For ITU-T G.992.3 (ADSL2) Annex C and ITU-T G.992.5 (ADSL2plus) Annex C, the upstream transmit spectrum shaping parameter set per subcarrier (see clause 7.5.1.29.6) used during NEXTc duration is specified as the NEXT upstream transmit spectrum shaping (NEXT TSSpsus). + +#### **7.5.1.29.7 Downstream MEDLEY reference power spectral density (MREFPSDds)** + +This parameter shall contain the set of breakpoints exchanged in the MREFPSDds fields of the O-PRM message of ITU-T G.993.2. The format shall be as specified in [ITU-T G.993.2]. + +#### **7.5.1.29.8 Upstream MEDLEY reference power spectral density (MREFPSDus)** + +This parameter shall contain the set of breakpoints exchanged in the MREFPSDus fields of the R-PRM message of [ITU-T G.993.2]. The format shall be as specified in [ITU-T G.993.2]. + +#### **7.5.1.30 Downstream trellis use (TRELLISds)** + +This parameter reports whether trellis coding is in use in the downstream direction. It is represented as one bit coded as 0 if the trellis is not used and as 1 if the trellis is used. + +#### **7.5.1.31 Upstream trellis use (TRELLISus)** + +This parameter reports whether trellis coding is in use in the upstream direction. It is represented as one bit coded as 0 if the trellis is not used and as 1 if the trellis is used. + +#### **7.5.1.32 Actual cyclic extension (ACTUALCE)** + +This parameter reports the cyclic extension used on the line. It is coded as an unsigned integer from 2 to 16 in units of $N/32$ samples, where $2N$ is the IDFT size. + +#### **7.5.1.33 Actual rate adaptation mode** + +##### **7.5.1.33.1 Actual downstream rate adaptation mode (ACT-RA-MODEds)** + +This parameter indicates the actual active RA-MODE in the downstream direction. + +If ACT-RA-MODEds equals 1, the link is operating in RA-MODE 1 (MANUAL). + +If ACT-RA-MODEds equals 2, the link is operating in RA-MODE 2 (AT\_INIT). + +If ACT-RA-MODEds equals 3, the link is operating in RA-MODE 3 (DYNAMIC). + +NOTE 1 – In [ITU-T G.992.3] ACT-RA-MODEds=3 corresponds to SRA supported. In [ITU-T G.993.2] ACT-RA-MODEds=3 corresponds to SRA supported by both XTUs in the downstream direction, but SOS not supported by both XTUs in the downstream direction. + +If ACT-RA-MODEds equals 4, the link is operating in RA-MODE 4 (DYNAMIC with SOS). + +NOTE 2 – In [ITU-T G.992.3] ACT-RA-MODEds=4 is not defined. In [ITU-T G.993.2] ACT-RA-MODEds=4 corresponds to SOS and SRA supported by both XTUs in the downstream direction. + +##### **7.5.1.33.2 Actual upstream rate adaptation mode (ACT-RA-MODEus)** + +This parameter indicates the actual active RA-MODE in the upstream direction. + +If ACT-RA-MODEus equals 1, the link is operating in RA-MODE 1 (MANUAL). + +If ACT-RA-MODEus equals 2, the link is operating in RA-MODE 2 (AT\_INIT). + +If ACT-RA-MODEus equals 3, the link is operating in RA-MODE 3 (DYNAMIC). + +NOTE 1 – In [ITU-T G.992.3] ACT-RA-MODEus=3 corresponds to SRA supported. In [ITU-T G.993.2] ACT-RA-MODEus=3 corresponds to SRA supported by both XTUs in the upstream direction, but SOS not supported by both XTUs in the upstream direction. + +If ACT-RA-MODEus equals 4, the link is operating in RA-MODE 4 (DYNAMIC with SOS). + +NOTE 2 – In [ITU-T G.992.3] ACT-RA-MODEus=4 is not specified. In [ITU-T G.993.2] ACT-RA-MODEus=4 corresponds to SOS and SRA supported by both XTUs in the upstream direction. + +#### **7.5.1.34 Actual impulse noise protection of the robust overhead channel** + +##### **7.5.1.34.1 Downstream actual impulse noise protection of the robust overhead channel (ACTINP-ROC-ds)** + +This parameter reports the actual INP of the ROC in the downstream direction expressed in multiples of $T_{4k}$ in the L0 state. + +In the L1 or L2 states, the parameter contains the value in the previous L0 state. + +The value is coded in fractions of $T_{4k}$ with a granularity of 0.1. The range is from 0 to 25.4. A special value indicates an ACTINP-ROC-ds higher than 25.4. + +##### **7.5.1.34.2 Upstream actual impulse noise protection of robust overhead channel (ACTINP-ROC-us)** + +This parameter reports the actual INP of the ROC in the upstream direction expressed in multiples of $T_{4k}$ in the L0 state. + +In the L1 or L2 states, the parameter contains the value in the previous L0 state. + +The value is coded in fractions of $T_{4k}$ with a granularity of 0.1. The range is from 0 to 25.4. A special value indicates an ACTINP-ROC-us higher than 25.4. + +#### **7.5.1.35 Actual signal-to-noise ratio margin of robust overhead channel** + +##### **7.5.1.35.1 Downstream actual signal-to-noise ratio margin of robust overhead channel (SNRM-ROC-ds)** + +This parameter reports the actual signal-to-noise margin of the ROC in the downstream direction. The format is identical to the format of the line status parameter SNRM (see clause 7.5.1.13). + +##### **7.5.1.35.2 Upstream actual signal-to-noise ratio margin of robust overhead channel (SNRM-ROC-us)** + +This parameter reports the actual signal-to-noise margin of the ROC in the upstream direction. The format is identical to the format of the line status parameter SNRM (see clause 7.5.1.16). + +#### **7.5.1.36 Update request flags and time stamps of test parameters** + +##### **7.5.1.36.1 Update request flag for near-end test parameters (UPDATE-TEST-NE)** + +This parameter is defined to force an update of the near-end test parameters that can be updated during showtime. The parameter is configurable over the Q-interface and the valid values are 0 and 1. When this parameter is set (its value is changed from 0 to 1), the near-end test parameters shall be updated in the AN MIB within 10 s. The update request flag for the near-end test parameters is defined in the AN MIB and is independent of any autonomous update process in the system. The parameter shall be reset (its value changed back to 0) by the AN after a period shorter than 3 min to allow reception of another update request. The 3 min period starts since the last time the flag was set (externally or by an autonomous process in the system). This applies only to the elements maintained in the AN (see the last paragraph of clause 7). + +##### **7.5.1.36.2 Update request flag for far-end test parameters (UPDATE-TEST-FE)** + +This parameter is specified to force an update of the far-end test parameters that can be updated during showtime. The parameter is configurable over the Q-interface and the valid values are 0 and 1. When this parameter is set (its value is changed from 0 to 1), the far-end test parameters shall be updated in the AN MIB within 30 s. The update request flag for the far-end test parameters is specified in the AN MIB and is independent of any autonomous update process in the system. The parameter shall be + +reset (its value changed back to 0) by the AN after a period shorter than 3 min to allow reception of another update request. The 3 min period starts since the last time the flag was set (externally or by an autonomous process in the system). This applies only to the elements maintained in the AN (see the last paragraph of clause 7). + +#### **7.5.1.36.3 Date/time-stamping of near-end test parameters (STAMP-TEST-NE)** + +This parameter is specified in the AN MIB and indicates the date/time when the near-end test parameters that can change during showtime were last updated. This date/time-stamp shall include information on the year, month, day, hour, minute and second of the last update. + +#### **7.5.1.36.4 Date/time-stamping of far-end test parameters (STAMP-TEST-FE)** + +This parameter is specified in the AN MIB and indicates the date/time when the far-end test parameters that can change during showtime were last updated. This date/time-stamp shall include information on the year, month, day, hour, minute and second of the last update. + +#### **7.5.1.37 On-line reconfiguration time stamps** + +##### **7.5.1.37.1 Date/time-stamping of last successful downstream on-line reconfiguration operation (STAMP-OLR-ds)** + +This parameter indicates the date/time of the last successful OLR execution in the downstream direction that has modified the bits or gains. This date/time-stamp shall include information on the year, month, day, hour, minute and second of the last OLR. + +##### **7.5.1.37.2 Date/time-stamping of last successful upstream on-line reconfiguration operation (STAMP-OLR-us)** + +This parameter indicates the date/time of the last successful OLR execution in the upstream direction that has modified the bits or gains. This date/time-stamp shall include information on the year, month, day, hour, minute and second of the last OLR. + +#### **7.5.1.38 Retransmission used (RTX\_USED)** + +This parameter specifies whether ITU-T G.998.4 retransmission is used (i.e., active in showtime) in a given transmit direction. The parameter in downstream is RTX\_USED\_ds, and the parameter in upstream is RTX\_USED\_us. In [ITU-T G.992.3] and [ITU-T G.992.5] only the downstream parameter RTX\_USED\_ds is relevant, the value in the upstream direction shall be ignored. In [ITU-T G.993.2], both parameters are relevant. + +- 1: RTX in use +- 2: RTX not in use, due to RTX\_MODE = FORBIDDEN +- 3: RTX not in use, because it is not supported by the XTU-C +- 4: RTX not in use, because it is not supported by the XTU-R +- 5: RTX not in use, because it is not supported by the XTU-C and XTU-R + +This parameter shall also be reported in the case of RTX\_MODE = RTX\_FORCED with INIT FAILURE or with RTX\_MODE = RTX\_TESTMODE with INIT FAILURE. + +NOTE – In the latter case, this parameter will give detailed information on top of the INIT FAILURE reason code. + +#### **7.5.1.39 Test parameters for [ITU-T G.993.5]** + +##### **7.5.1.39.1 Downstream XLIN scale (XLINSCds)** + +This parameter is the scale factor to be applied to the downstream Xlinpsds values. It is represented as an unsigned integer in the range from 1 to $2^{16} - 1$ . + +#### 7.5.1.39.2 Downstream XLIN subcarrier group size (XLINGds) + +This parameter is the number of subcarriers per group used to report Xlinpsds. The valid values are 1, 2, 4, 8, 16, 32, and 64. XLINGds should equal the sub-sampling factor used to estimate the crosstalk channel for cancellation. This value may be different from $F\_sub$ (see [ITU-TG.993.5] for the definition of $F\_sub$ ). + +#### 7.5.1.39.3 Downstream XLIN bandedges (XLINBANDSds) + +XLINBANDSds contains pairs of (start\_subcarrier\_index, stop\_subcarrier\_index) for every band in which XLINpsds is reported. + +#### 7.5.1.39.4 Downstream far-end crosstalk coupling (XLINpsds) + +For each given VCE port index $k$ , this parameter is a one-dimensional array of complex values in linear scale for downstream FEXT coupling coefficients $Xlinds(f)$ originating from the loop connected to the VCE port $k$ into the loop for which $Xlinds(f)$ is being reported. Each array entry represents the $Xlinds(f = n \times \Delta f)$ value for a particular subcarrier index $n$ . The $Xlinds(f = n \times \Delta f)$ value is represented as $((XLINSCds/2^{15}) \times ((a(n) + j \times b(n))/2^{15}))$ , where $a(n)$ and $b(n)$ are signed integers in the $(-2^{15} + 1)$ to $(+2^{15} - 1)$ range. A special value indicates that no measurement could be done from line $k$ into this line for subcarrier $n$ . Another special value indicates that there is no phase information and the magnitude of $Xlinds(f = n \times \Delta f)$ is $((XLINSCds/2^{15}) \times (a(n)/2^{15}))$ . + +The format of XLINpsds is defined in [ITU-T G.993.5]. + +#### 7.5.1.39.5 Upstream XLIN scale (XLINSCus) + +This parameter is the scale factor to be applied to the upstream Xlinpsus values. It is represented as an unsigned integer in the range from 1 to $2^{16} - 1$ . + +#### 7.5.1.39.6 Upstream XLIN subcarrier group size (XLINGus) + +This parameter is the number of subcarriers per group used to report Xlinpsus. The valid values are 1, 2, 4, 8, 16, 32, and 64. + +#### 7.5.1.39.7 Upstream XLIN bandedges (XLINBANDSus) + +XLINBANDSus contains pairs of (start\_subcarrier\_index, stop\_subcarrier\_index) for every band in which XLINpsus is reported. + +#### 7.5.1.39.8 Upstream far-end crosstalk coupling (XLINpsus) + +For each given VCE port index $k$ , this parameter is a one-dimensional array of complex values in linear scale for upstream FEXT coupling coefficients $Xlinus(f)$ originating from the loop connected to the VCE port $k$ into the loop for which $Xlinus(f)$ is being reported. Each array entry represents the $Xlinus(f = n \times \Delta f)$ value for a particular subcarrier index $n$ . The $Xlinus(f = n \times \Delta f)$ value is represented as $((XLINSCus/2^{15}) \times ((a(n) + j \times b(n))/2^{15}))$ , where $a(n)$ and $b(n)$ are signed integers in the $(-2^{15} + 1)$ to $(+2^{15} - 1)$ range. A special value indicates that no measurement could be done from line $k$ into this line for subcarrier $n$ . Another special value indicates that there is no phase information and the magnitude of $Xlinus(f = n \times \Delta f)$ is $((XLINSCus/2^{15}) \times (a(n)/2^{15}))$ . + +The format of XLINpsus is defined in [ITU-T G.993.5]. + +### 7.5.1.40 Actual re-initialization policy (ACT RIPOLICY) + +#### 7.5.1.40.1 Actual downstream re-initialization policy (ACTRIPOLICYds) + +This parameter indicates the actual RIPOLICY in use in the downstream direction. + +A value of 0 indicates the line is operating in RIPOLICYds 0, a value of 1 indicates the line is operating in RIPOLICYds 1. + +#### **7.5.1.40.2 Actual upstream re-initialization policy (ACTRIPOLICYus)** + +This parameter indicates the actual RIPOLICY in use in the upstream direction. + +A value of 0 indicates the line is operating in RIPOLICYus 0, a value of 1 indicates the line is operating in RIPOLICYus 1. + +#### **7.5.1.41 Attainable net data rate diagnostic parameters** + +##### **7.5.1.41.1 Attainable net data rate actual method (ATTNDR\_ACTMETHOD)** + +This parameter indicates the actual ATTNDR method used for calculation of the ATTNDR in the downstream and upstream direction. + +The valid values are identical to the values of the line configuration parameter ATTNDR\_METHOD. + +##### **7.5.1.41.2 Attainable net data rate downstream actual impulse noise protection (ATTNDR\_ACTINPds)** + +If retransmission is not used in the downstream direction, this parameter indicates the actual INP used in the improved calculation of the ATTNDR in the downstream direction. + +If retransmission is used in the downstream direction, this parameter indicates the actual INP against SHINE used in the improved calculation of the ATTNDR in the downstream direction. + +The format and valid values are identical to the values of the channel status parameter ACTINP. + +##### **7.5.1.41.3 Attainable net data rate upstream actual impulse noise protection (ATTNDR\_ACTINPus)** + +If retransmission is not used in the upstream direction, this parameter indicates the actual INP used in the improved calculation of the ATTNDR in the upstream direction. + +If retransmission is used in the upstream direction, this parameter indicates the actual INP against SHINE used in the improved calculation of the ATTNDR in the upstream direction. + +The format and valid values are identical to the values of the channel status parameter ACTINP. + +##### **7.5.1.41.4 Attainable net data rate downstream actual impulse noise protection against repetitive electrical impulse noise (ATTNDR\_ACTINP\_REINds)** + +If retransmission is used in the downstream direction, this parameter reports the actual INP against REIN used in the improved calculation of the ATTNDR in the downstream direction. + +The format and valid values are identical to the values of the channel status parameter ACTINP\_REIN. + +##### **7.5.1.41.5 Attainable net data rate upstream actual impulse noise protection against repetitive electrical impulse noise (ATTNDR\_ACTINP\_REINus)** + +If retransmission is used in the upstream direction, this parameter reports the actual INP against REIN used in the improved calculation of the ATTNDR in the upstream direction. + +The format and valid values are identical to the values of the channel status parameter ACTINP\_REIN. + +##### **7.5.1.41.6 Attainable net data rate downstream actual delay (ATTNDR\_ACTDELAYds)** + +This parameter indicates the actual delay used in the improved calculation of the ATTNDR in the downstream direction. + +The value is coded in with a granularity of 0.1 ms. The range is from 0 ms to 25.4 ms. A special value indicates an actual delay higher than 25.4 ms. + +#### **7.5.1.41.7 Attainable net data rate upstream actual delay (ATTNDR\_ACTDELAYus)** + +This parameter indicates the actual delay used in the improved calculation of the ATTNDR in the upstream direction. + +The value is coded in with a granularity of 0.1 ms. The range is from 0 ms to 25.4 ms. A special value indicates an actual delay higher than 25.4 ms. + +#### **7.5.1.42 Aggregate achievable net data rate** + +##### **7.5.1.42.1 Near-end aggregate achievable net data rate (AGGACHNDR\_NE)** + +This parameter reports the aggregate achievable net data rate of the VTU-O as specified in [ITU-T G.998.4]. The value is coded in steps of 1 000 bit/s. A special value indicates that the aggregate achievable net data rate value is reported as being undefined. + +##### **7.5.1.42.2 Far-end aggregate achievable net data rate (AGGACHNDR\_FE)** + +This parameter reports the aggregate achievable net data rate of the VTU-R as specified in [ITU-T G.998.4]. The value is coded in steps of 1 000 bit/s. A special value indicates that the aggregate achievable net data rate value is reported as being undefined. + +#### **7.5.1.43 Line status parameters for G.993.5** + +##### **7.5.1.43.1 Actual vectoring mode (ACTVECTORMODE)** + +This parameter reports the vectoring initialization type of the line. + +If ACTVECTORMODE equals 0, the line is initialized in a mode different from that of Annex X or Annex Y of [ITU-T G.993.2]. + +If ACTVECTORMODE equals 1, the line is initialized in Annex X of [ITU-T G.993.2]. + +If ACTVECTORMODE equals 2, the line is initialized in Annex Y of [ITU-T G.993.2]. + +If ACTVECTORMODE equals 3, the line is initialized in [ITU-T G.993.5]. + +#### **7.5.1.44 Line status parameter for VDSL2-LR** + +##### **7.5.1.44.1 VDSL2-LR actual operation type (VDSL2-LR\_ACTOPTYPE)** + +This parameter reports the actual operation type of VDSL2-LR. + +If VDSL2-LR\_ACTOPTYPE equals 0, the line does not operate in VDSL2-LR mode. + +If VDSL2-LR\_ACTOPTYPE equals 1, the line operates according to the short loop operation type of VDSL2-LR. + +If VDSL2-LR\_ACTOPTYPE equals 2, the line operates according to the medium loop operation type of VDSL2-LR. + +If VDSL2-LR\_ACTOPTYPE equals 3, the line operates according to the long loop operation type of VDSL2-LR. + +For detailed specification of this parameter, see clause B.10.2.1 of [ITU-T G.993.5]. + +#### **7.5.1.45 Line status parameter for STRONGFEXT MODE** + +##### **7.5.1.45.1 Actual STRONGFEXT mode (STRONGFEXT\_ACTMODE)** + +This parameter reports the use of STRONGFEXT mode. + +If STRONGFEXT\_ACTMODE equals 0, the line is not initialized with operation according to [ITU-T G.993.5] Annex A. + +If STRONGFEXT\_ACTMODE equals 1, the line is initialized with operation according to [ITU-T G.993.5] Annex A. + +#### **7.5.1.46 Loop diagnostics mode status** + +The LDS parameter reports the status of the loop diagnostics mode procedures. + +The parameter is of type enumeration, with the following valid values: + +- inactive: the loop diagnostics mode procedures are inhibited, failed or successfully completed; +- loop-diagnostics-ongoing: the loop diagnostics mode procedures are ongoing. + +Upon the near-end xTU being forced to perform the loop diagnostic mode procedures, LDS shall become "loop-diagnostics-ongoing". + +Upon failure or successful completion of the loop diagnostics mode procedures, LDS shall become "inactive" and the AN/data processing unit (DPU) ME shall send a notification to the NMS. + +#### **7.5.1.47 Loop diagnostics mode results status** + +The loop diagnostics mode results status (LDR) parameter reports the status of the loop diagnostics mode results. + +The parameter is of type enumeration, with the following valid values: + +- no-loop-diagnostics-results-available: no measurement results are available when no loop diagnostics mode procedures has been performed yet or after loop diagnostics mode results have been deleted; +- loop-diagnostics-failed-results-invalid: loop diagnostics mode results are invalid after the most recent loop diagnostics mode procedures failed; +- loop-diagnostics-succeeded-results-valid: loop diagnostics mode results are valid after the most recent loop diagnostics mode procedures succeeded. + +### **7.5.2 Channel status parameters** + +#### **7.5.2.1 Actual data rate** + +If retransmission is not used in a given transmit direction: + +- in the L0 state, this parameter reports the actual net data rate at which the bearer channel is operating at; +- in the L1 or L2 states, the parameter contains the net data rate in the previous L0 state. + +If retransmission is used in a given transmit direction: + +- in the L0 state, this parameter reports the ETR (as specified in [ITU-T G.998.4]) at which the bearer channel is operating; +- in the L2 state, the parameter contains the ETR (as specified in [ITU-T G.998.4]) in the previous L0 state. + +The data rate is coded in steps of 1 000 bit/s. + +This parameter shall be reported with the most recent values when read over the Q-interface. + +#### **7.5.2.2 Previous data rate** + +If retransmission is not used in a given transmit direction, this parameter reports the previous net data rate the bearer channel was operating at just before the latest net data rate change event occurred, excluding all transitions between L0 state and L1 or L2 states. + +If retransmission is used in a given transmit direction, this parameter reports the previous ETR (as specified in [ITU-T G.998.4]) the bearer channel was operating at just before the latest ETR change event occurred, excluding all transitions between L0 state and L1 or L2 states. + +A rate change can occur at a power management state transition, e.g., at full or short initialization, fast retrain or power down or at a dynamic rate adaptation. The rate is coded in steps of 1 000 bit/s. + +### 7.5.2.3 Actual delay + +If retransmission is not used in a given transmit direction, this parameter is the actual one-way interleaving delay introduced by the PMS-TC between the $\alpha$ and $\beta$ reference points excluding delay in the L1 and L2 state. In the L1 and L2 state, the parameter contains the interleaving delay in the previous L0 state. For ADSL, this parameter is derived from the $S$ and $D$ parameters as $\lceil S \times D \rceil / 4$ ms, where $S$ is the symbols per codeword, and $D$ is the interleaving depth and the ceiling brackets $\lceil \dots \rceil$ denote rounding to the higher integer. For [ITU-T G.993.2], this parameter shall be computed according to the formula in clause 9.7 of [ITU-T G.993.2]. + +If retransmission is used in a given transmit direction, this parameter specifies the actual value of the time-independent component of the delay due to retransmission only (see [ITU-T G.998.4] for detailed specification). + +The actual delay is coded in milliseconds (rounded to the nearest millisecond). + +### 7.5.2.4 Actual impulse noise protection (ACTINP) + +If retransmission is not used in a given transmit direction, this parameter reports the actual INP on the bearer channel in the L0 state. In the L1 or L2 state, the parameter contains the INP in the previous L0 state. + +For [ITU-T G.992.1], this value is computed according to the formula specified in this Recommendation based on the actual framing parameters. For [ITU-T G.992.3] and [ITU-T G.992.5], this value is estimated by the xTU receiver. It is identical to the $INP\_act_n$ for the corresponding bearer channel as defined in these Recommendations (clauses K.1.7, K.2.7 and K.3.7 of [ITU-T G.992.3]). For [ITU-T G.993.2], the method of reporting this value is according to the INPREPORT parameter. + +The value is coded in fractions of DMT symbols with a granularity of 0.1 symbols. The range is from 0 to 25.4. A special value indicates an ACTINP higher than 25.4. + +If retransmission is used in a given transmit direction, this parameter reports the actual INP against SHINE (under specific conditions detailed in [ITU-T G.998.4]) on the bearer channel in the L0 state. In the L2 state, the parameter contains the INP in the previous L0 state. + +The value is coded in fractions of DMT symbols with a granularity of 0.1 symbols. + +The range is from 0 to 204.6. A special value indicates an ACTINP of 204.7 or higher. + +#### 7.5.2.4.1 Special requirements for [ITU-T G.992.1] + +For [ITU-T G.992.1], the reporting of ACTINP is optional. If reported, the ACTINP value of a bearer mapped in the interleaved path shall be computed by the formula: + +$$ACTINP = \left( \frac{1}{2} \right) \times (S \times D) \times \left( \frac{R_I}{N_I} \right)$$ + +where $S$ , $D$ , $R_I$ and $N_I$ are defined in [ITU-T G.992.1]. The ACTINP value of a bearer mapped in the fast path shall be 0. + +### **7.5.2.5 Impulse noise protection reporting mode (INPREPORT)** + +This parameter reports the method used to compute the ACTINP. If set to 0, the ACTINP is computed according to the INP\_no\_erasure formula (see clause 9.6 of [ITU-T G.993.2]). If set to 1, the ACTINP is the value estimated by the xTU receiver. + +### **7.5.2.6 Actual framer settings** + +#### **7.5.2.6.1 Actual size of Reed-Solomon codeword (NFEC)** + +This parameter reports the actual Reed-Solomon codeword size used in the latency path in which the bearer channel is transported. The value is coded in bytes. It ranges from 0 to 255. + +#### **7.5.2.6.2 Actual number of Reed-Solomon redundancy bytes (RFEC)** + +This parameter reports the actual number of Reed-Solomon redundancy bytes per codeword used in the latency path in which the bearer channel is transported. The value is coded in bytes. It ranges from 0 to 16. The value 0 indicates no Reed-Solomon coding. + +#### **7.5.2.6.3 Actual number of bits per symbol (LSYMB)** + +This parameter reports the actual number of bits per symbol assigned to the latency path in which the bearer channel is transported. This value does not include trellis overhead. The value is coded in bits. The range of valid values is from 0 to 131071. + +#### **7.5.2.6.4 Actual interleaving depth (INTLVDEPTH)** + +This parameter reports the actual depth of the interleaver used in the latency path in which the bearer channel is transported. The value ranges from 1 to 4 096 in steps of 1. The value 1 indicates no interleaving. + +#### **7.5.2.6.5 Actual interleaving block length (INTLVBLOCK)** + +This parameter reports the actual block length of the interleaver used in the latency path in which the bearer channel is transported. The value ranges from 4 to 255 in steps of 1. + +#### **7.5.2.6.6 Actual number of Reed-Solomon codewords per data transfer unit (RSPERDTU)** + +This parameter reports the actual number of Reed-Solomon codewords per DTU used in the latency path in which the bearer channel is transported. The value ranges from 1 to 64 in steps of 1. + +### **7.5.2.7 Actual latency path (LPATH)** + +This parameter reports the index of the actual latency path in which the bearer is transported. The valid values are 0, 1, 2, 3. For [ITU-T G.992.1], the FAST path shall be mapped to the latency index 0, and the INTERLEAVED path shall be mapped to the latency index 1. + +### **7.5.2.8 Actual net data rate (ACTNDR)** + +Independent whether retransmission is used or not in a given transmit direction: + +- in the L0 state, this parameter reports the net data rate (as specified in [ITU-T G.992.3], [ITU-T G.992.5] or [ITU-T G.993.2]) at which the bearer channel is operating; +- in the L2 state, the parameter contains the net data rate (as specified in [ITU-T G.992.3], [ITU-T G.992.5] or [ITU-T G.993.2]) in the previous L0 state. + +The data rate is coded in steps of 1 000 bit/s. + +This parameter shall be reported with the most recent values when read over the Q-interface. + +This parameter is optional if [ITU-T G.998.4] is not supported. + +#### **7.5.2.9 Actual impulse noise protection against repetitive electrical impulse noise (ACTINP\_REIN)** + +If retransmission is used in a given transmit direction, this parameter reports the actual INP against REIN (under specific conditions detailed in [ITU-T G.998.4]) on the bearer channel in the L0 state. In the L2 state, the parameter contains the INP in the previous L0 state. + +The value is coded in fractions of DMT symbols with a granularity of 0.1 symbols. + +The range is from 0 to 25.4. A special value indicates an ACTINP\_REIN of 25.5 or higher. + +### **7.5.3 Data gathering line test, diagnostic and status parameters** + +#### **7.5.3.1 Logging depth – VTU-O (LOGGING\_DEPTH\_O)** + +This parameter is the maximum depth of the entire data gathering event buffer at the VTU-O, in number of 6-byte data gathering records. + +#### **7.5.3.2 Logging depth – VTU-R (LOGGING\_DEPTH\_R)** + +This parameter is the maximum depth of the entire data gathering event buffer at the VTU-R, in number of 6-byte data gathering records. + +#### **7.5.3.3 Actual logging depth for reporting – VTU-O (ACT\_logging\_depth\_reporting\_O)** + +This parameter is actual logging depth that is used for reporting the VTU-O event trace buffer in the CO-MIB, in number of 6-byte data gathering records. + +#### **7.5.3.4 Actual logging depth for reporting – VTU-R (ACT\_logging\_depth\_reporting\_R)** + +This parameter is actual logging depth that is used for reporting the VTU-R event trace buffer over the eoc channel, in number of 6-byte data gathering records. + +#### **7.5.3.5 Event trace buffer – VTU-O (EVENT\_TRACE\_BUFFER\_O)** + +This parameter is the event trace buffer containing the event records that originated at the VTU-O. + +#### **7.5.3.6 Event trace buffer – VTU-R (EVENT\_TRACE\_BUFFER\_R)** + +This parameter is the event trace buffer containing the event records that originated at the VTU-R. + +### **7.6 Network management elements partitioning** + +This clause specifies the network management elements which correspond to the specific management interfaces. + +- Q-interface: Management interface towards the xTU-C, from the network side perspective. The xTU-C provides its near-end (at xTU-C) and far-end (at xTU-R) parameters for the system operator to read and write +- U-C-interface: Management interface towards the xTU-C, from the xTU-R perspective. The xTU-C provides its near-end parameters (xTU-R far-end) for the xTU-R to read +- U-R-interface: Management interface towards the xTU-R, from the xTU-C perspective. The xTU-R provides its near-end parameters (xTU-C far-end) for the xTU-C to read +- T/S-interface: Management interface towards the xTU-R, from the premises side perspective. The xTU-R provides its near-end (at xTU-R) and far-end (at xTU-C) parameters for the subscriber to read and write +- G-interface: Management interface towards the xTU-R, from the NMS perspective. The xTU-R provides its near-end (at xTU-R) and far-end (at xTU-C) parameters for the NMS to read + +The U-C and U-R management interfaces represent the network management elements to be supported through the OAM communications channel specified in this Recommendation (see clause 6). The exchange between the xTU-C and xTU-R of some or all of these network management elements may already be obtained by the EOC commands defined in the respective Recommendations. + +The parameters at the management interfaces are described in two categories. Each category is presented by two tables. The first table (e.g., Table 7-10 for line failures) indicates the status of the parameter at the corresponding management interface as: + +- R: read only +- W: write only +- R/W: read and write +- (M): mandatory +- (O): optional + +If the status of the parameter over the G-interface is not explicitly stated, it is identical to the status of the same parameter over the T/S-interface. + +NOTE – Some management elements are useful only when optional features of the physical layer Recommendation are supported by the xTUs. + +The far-end fault and PM over the Q-interface is equivalent to the near-end fault and PM over the T/S-interface. The near-end fault and PM over the Q-interface is equivalent to the far-end fault and PM over the T/S-interface. Over the Q-interface, near-end fault and PM applies to the upstream direction only and far-end PM applies to the downstream direction only. Over the T/S-interface, near-end fault and PM applies to the downstream direction only and far-end PM applies to the upstream direction only. + +The second table for each category (e.g., Table 7-11 for line failures) indicates for which Recommendations the management element is relevant. A "Y" in a column means that this MIB element is relevant for the specified Recommendation over at least one of the interfaces. The column labelled with [ITU-T G.998.4] indicates the MIB elements that are relevant in addition to those relevant to the xDSL Recommendation associated with [ITU-T G.998.4]. + +**Table 7-10 – Line failures** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|-----------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| Near-end (xTU-C) failures | | | | | | +| Loss of signal (LOS) | 7.1.1.1.1 | R (M) | R (O) | | R (O) | +| Loss of frame (LOF) | 7.1.1.1.2 | R (M) | R (O) | | R (O) | +| Loss of power (LPR) | 7.1.1.1.3 | R (M) | R (O) | | R (O) | +| Loss of margin (LOM) | 7.1.1.1.4 | R (M) | R (O) | | R (O) | +| Far-end (xTU-R) failures | | | | | | +| Loss of signal (LOS-FE) failure | 7.1.1.2.1 | R (M) | | R (O) | R (O) | +| Loss of frame (LOF-FE) failure | 7.1.1.2.2 | R (M) | | R (O) | R (O) | +| Loss of power (LPR-FE) failure | 7.1.1.2.3 | R (M) | | R (O) | R (O) | +| Loss of margin (LOM-FE) failure | 7.1.1.2.4 | R (M) | | R (O) | R (O) | +| Initialization failures | | | | | | +| Line init (LINIT) failure | 7.1.1.3 | R (M) | | | R (O) | + +**Table 7-11 – Support of line failures per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | +|---------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Near-end failures | | | | | | | +| Loss of signal (LOS) | Y | Y | Y | Y | Y | Y | +| Loss of frame (LOF) | Y | Y | Y | Y | Y | Y | +| Loss of power (LPR) | Y | Y | Y | Y | Y | Y | +| Loss of margin (LOM) | Y | Y | Y | Y | Y | Y | +| Far-end failures | | | | | | | +| Loss of signal (LOS-FE) failure | Y | Y | Y | Y | Y | Y | +| Loss of frame (LOF-FE) failure | Y | Y | Y | Y | Y | Y | +| Loss of power (LPR-FE) failure | Y | Y | Y | Y | Y | Y | +| Loss of margin (LOM-FE) failure | Y | Y | Y | Y | Y | Y | +| Initialization failures | | | | | | | +| Line init (LINIT) failure | Y | Y | Y | Y | Y | Y | + +**Table 7-12 – Asynchronous transfer mode data path failures** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|-------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| Near-end (xTU-C) failures | | | | | | +| No cell delineation (NCD) failure | 7.1.4.1.1 | R (M) | R (O) | | | +| Loss of cell delineation (LCD) failure | 7.1.4.1.2 | R (M) | R (O) | | | +| Far-end (xTU-R) failures | | | | | | +| No cell delineation (NCD-FE) failure | 7.1.4.2.1 | R (M) | | R (O) | | +| Loss of cell delineation (LCD-FE) failure | 7.1.4.2.2 | R (M) | | R (O) | | + +**Table 7-13 – Support of Asynchronous transfer mode data path failures per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | +|-------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Near-end failures | | | | | | | +| No cell delineation (NCD) failure | Y | Y | Y | Y | Y | Y | +| Loss of cell delineation (LCD) failure | Y | Y | Y | Y | Y | Y | +| Far-end failures | | | | | | | +| No cell delineation (NCD-FE) failure | Y | Y | Y | Y | Y | Y | +| Loss of cell delineation (LCD-FE) failure | Y | Y | Y | Y | Y | Y | + +**Table 7-14 – Line configuration profile** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|-----------------------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| Line/xTU state | | | | | | +| xTU transmission system enabling (XTSE) | 7.3.1.1.1 | R/W (M) | | | R (O) | +| ATU impedance state forced (AISF) | 7.3.1.1.2 | | | | R/W (M) | +| Power management state forced (PMSF) | 7.3.1.1.3 | R/W (M) | | | R/W (M) | +| Power management state enabling (PMMode) | 7.3.1.1.4 | R/W (M) | | | | +| L0-TIME | 7.3.1.1.5 | R/W (M) | R (O) | | | +| L2-TIME | 7.3.1.1.6 | R/W (M) | R (O) | | | +| L2-ATPR | 7.3.1.1.7 | R/W (M) | R (O) | | | +| L2-ATPRT | 7.3.1.1.9 | R/W (M) | R (O) | | | +| Loop diagnostic mode forced (LDSF) | 7.3.1.1.8 | R/W (M) | | | R/W (M) | +| Automode cold start forced | 7.3.1.1.10 | R/W (M) | | | R/W (O) | +| VDSL2 profiles enabling (PROFILES) | 7.3.1.1.11 | R/W (M) | | | R (O) | +| RIPOLICYds | 7.3.1.1.12.1 | R/W (O) | R(O) | | | +| RIPOLICYus | 7.3.1.1.12.2 | R/W (O) | | | | +| REINIT_TIME_THRESHOLDDds | 7.3.1.1.13.1 | R/W (O) | R(O) | | | +| REINIT_TIME_THRESHOLDDus | 7.3.1.1.13.2 | R/W (O) | | | | +| Power and spectrum usage | | | | | | +| MAXNOMPSD ds | 7.3.1.2.1 | R/W (M) | R (O) | | | +| MAXNOMPSD us | 7.3.1.2.2 | R/W (M) | R (O) | | | +| MAXNOMATP ds | 7.3.1.2.3 | R/W (M) | R (O) | | | +| MAXNOMATP us | 7.3.1.2.4 | R/W (M) | R (O) | | | +| MAXRXPWR us | 7.3.1.2.5 | R/W (M) | R (O) | | | +| CARMASK ds | 7.3.1.2.6 | R/W (M) | R (O) | | | +| CARMASK us | 7.3.1.2.7 | R/W (M) | R (O) | | | +| VDSL2-CARMASK | 7.3.1.2.8 | R/W (M) | R (O) | | | +| PSDMASK ds | 7.3.1.2.9 | R/W (M) | R (O) | | | +| RFIBANDS | 7.3.1.2.10 | R/W (M) | R (O) | | | +| Upstream PSD mask selection | 7.3.1.2.11 | R/W (M) | R (O) | | | +| PSDMASK us | 7.3.1.2.12 | R/W (M) | R (O) | | | +| DPBOSHAPED | 7.3.1.2.13 | R/W (M) | R (O) | | | +| UPBOSHAPED (UPBOPSD-pb, UPBOKL, UPBOKLF) | 7.3.1.2.14 | R/W (M) | R (O) | | | +| UPBOSHAPED (UPBOKLREF-pb) | 7.3.1.2.14 | R/W (O) | R (O) | | | +| UPBOSHAPED (AELE-MODE, UPBOELMT) | 7.3.1.2.14 | R/W (O) | R(O) | | | +| VDSL2 PSD mask class selection (CLASSMASK) | 7.3.1.2.15 | R/W (M) | | | | +| VDSL2 limit PSD masks and band plans enabling (LIMITMASK) | 7.3.1.2.16 | R/W (M) | | | R (O) | +| VDSL2 US0 disabling (US0DISABLE) | 7.3.1.2.17 | R/W (M) | | | | +| VDSL2 US0 PSD masks (US0MASK) | 7.3.1.2.18 | R/W (M) | | | R (O) | +| Noise margins | | | | | | +| TARSNRM ds | 7.3.1.3.1 | R/W (M) | R (O) | | | + +**Table 7-14 – Line configuration profile** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|-----------------------------------------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| TARSNRM us | 7.3.1.3.2 | R/W (M) | R (O) | | | +| MAXSNRM ds | 7.3.1.3.3 | R/W (M) | R (O) | | | +| MAXSNRM us | 7.3.1.3.4 | R/W (M) | R (O) | | | +| MINSNRM ds | 7.3.1.3.5 | R/W (M) | R (O) | | | +| MINSNRM us | 7.3.1.3.6 | R/W (M) | R (O) | | | +| Rate adaptation | | | | | | +| RA-MODE ds | 7.3.1.4.1 | R/W (M) | R (O) | | | +| RA-MODE us | 7.3.1.4.2 | R/W (M) | R (O) | | | +| RA-USNRM ds | 7.3.1.4.3 | R/W (O) | R (O) | | | +| RA-USNRM us | 7.3.1.4.4 | R/W (O) | R (O) | | | +| RA-UTIME ds | 7.3.1.4.5 | R/W (O) | R (O) | | | +| RA-UTIME us | 7.3.1.4.6 | R/W (O) | R (O) | | | +| RA-DSNRM ds | 7.3.1.4.7 | R/W (O) | R (O) | | | +| RA-DSNRM us | 7.3.1.4.8 | R/W (O) | R (O) | | | +| RA-DTIME ds | 7.3.1.4.9 | R/W (O) | R (O) | | | +| RA-DTIME us | 7.3.1.4.10 | R/W (O) | R (O) | | | +| Overhead | | | | | | +| MSGMIN us | 7.3.1.5.1 | R/W (O) | R (O) | | | +| MSGMIN ds | 7.3.1.5.2 | R/W (O) | R (O) | | | +| Cyclic extension | | | | | | +| CEFLAG | 7.3.1.6.1 | R/W (M) | R (O) | | | +| Transmitter referred virtual noise | | | | | | +| SNRMODEds | 7.3.1.7.1 | R/W (M) | R (O) | | R (M) | +| SNRMODEus | 7.3.1.7.2 | R/W (M) | R (O) | | | +| VNd | 7.3.1.7.3 | R/W (O) | R (O) | | R (M) | +| FEXT TXREFVNd | 7.3.1.7.3.1 | R/W (O) | R (O) | | R (M) | +| NEXT TXREFVNd | 7.3.1.7.3.2 | R/W (O) | R (O) | | R (M) | +| VNu | 7.3.1.7.4 | R/W (O) | R (O) | | R (M) | +| RXREFVNSFus | 7.3.1.7.5 | R/W (O) | | | | +| TXREFVNSFds | 7.3.1.7.6 | R/W (O) | | | | +| Near-end (xTU-C) performance monitoring thresholds (15 min interval) | | | | | | +| FECS-L threshold 15 min | 7.3.1.8 | R/W (O) | R (O) | | | +| ES-L threshold 15 min | 7.3.1.8 | R/W (M) | R (O) | | | +| SES-L threshold 15 min | 7.3.1.8 | R/W (M) | R (O) | | | +| LOSS-L threshold 15 min | 7.3.1.8 | R/W (O) | R (O) | | | +| UAS-L threshold 15 min | 7.3.1.8 | R/W (M) | R (O) | | | +| "lefr" defect seconds threshold 15 min | 7.3.1.8 | R/W (M) | | | | +| Near-end (xTU-C) performance monitoring thresholds (24 h interval) | | | | | | +| FECS-L threshold 24 h | 7.3.1.8 | R/W (O) | R (O) | | | +| ES-L threshold 24 h | 7.3.1.8 | R/W (M) | R (O) | | | +| SES-L threshold 24 h | 7.3.1.8 | R/W (M) | R (O) | | | + +**Table 7-14 – Line configuration profile** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|------------------------------------------------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| LOSS-L threshold 24 h | 7.3.1.8 | R/W (O) | R (O) | | | +| UAS-L threshold 24 h | 7.3.1.8 | R/W (M) | R (O) | | | +| "leftr" defect seconds threshold 24 h | 7.3.1.8 | R/W (M) | | | | +| Far-end (xTU-R) performance monitoring thresholds (15 min interval) | | | | | | +| FECS-LFE threshold 15 min | 7.3.1.8 | R/W (O) | R (O) | | | +| ES-LFE threshold 15 min | 7.3.1.8 | R/W (M) | R (O) | | | +| SES-LFE threshold 15 min | 7.3.1.8 | R/W (M) | R (O) | | | +| LOSS-LFE threshold 15 min | 7.3.1.8 | R/W (O) | R (O) | | | +| UAS-LFE threshold 15 min | 7.3.1.8 | R/W (M) | R (O) | | | +| "leftr" defect seconds threshold 15 min | 7.3.1.8 | R/W (M) | | | | +| Far-end (xTU-R) performance monitoring thresholds (24 h interval) | | | | | | +| FECS-LFE threshold 24 h | 7.3.1.8 | R/W (O) | R (O) | | | +| ES-LFE threshold 24 h | 7.3.1.8 | R/W (M) | R (O) | | | +| SES-LFE threshold 24 h | 7.3.1.8 | R/W (M) | R (O) | | | +| LOSS-LFE threshold 24 h | 7.3.1.8 | R/W (O) | R (O) | | | +| UAS-LFE threshold 24 h | 7.3.1.8 | R/W (M) | R (O) | | | +| "leftr" defect seconds threshold 24 h | 7.3.1.8 | R/W (M) | | | | +| Initialization performance monitoring thresholds (15 min interval) | | | | | | +| Full inits threshold 15 min | 7.3.1.8 | R (M) | R (O) | | | +| Failed full inits threshold 15 min | 7.3.1.8 | R (M) | R (O) | | | +| Short inits threshold 15 min | 7.3.1.8 | R (O) | R (O) | | | +| Failed short inits threshold 15 min | 7.3.1.8 | R (O) | R (O) | | | +| Initialization performance monitoring thresholds (24 h interval) | | | | | | +| Full inits threshold 24 h | 7.3.1.8 | R (M) | R (O) | | | +| Failed full inits threshold 24 h | 7.3.1.8 | R (M) | R (O) | | | +| Short inits threshold 24 h | 7.3.1.8 | R (O) | R (O) | | | +| Failed short inits threshold 24 h | 7.3.1.8 | R (O) | R (O) | | | +| Short interruption performance monitoring thresholds (24 h interval) | | | | | | +| SPONT_INTRPT threshold 24 h | 7.3.1.8 | R(O) | R(O) | | | +| INM configuration parameters | | | | | | +| INMIATODs | 7.3.1.9.1 | R/W (O) | | R/W (O) | R (O) | +| INMIATOU s | 7.3.1.9.1 | R/W (O) | | | | +| INMIATSds | 7.3.1.9.2 | R/W (O) | | R/W (O) | R (O) | +| INMIATSus | 7.3.1.9.2 | R/W (O) | | | | +| INMCCds | 7.3.1.9.3 | R/W (O) | | R/W (O) | R (O) | +| INMCCus | 7.3.1.9.3 | R/W (O) | | | | +| INM_INPEQ_MODEds | 7.3.1.9.4 | R/W (O) | | R/W (O) | R (O) | +| INM_INPEQ_MODEus | 7.3.1.9.4 | R/W (O) | | | | +| INM_INPEQ_FORMATds | 7.3.1.9.5 | R/W (O) | | | | +| INM_INPEQ_FORMATus | 7.3.1.9.5 | R/W (O) | | | | +| INM_ENABLE | 7.3.1.9.6 | R/W (O) | | | | + +**Table 7-14 – Line configuration profile** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|------------------------------------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| SOS configuration parameters | | | | | | +| SOS-TIME-ds | 7.3.1.10.1 | R/W (O) | R (O) | | | +| SOS-TIME-us | 7.3.1.10.2 | R/W (O) | | | | +| SOS-NTONES-ds | 7.3.1.10.3 | R/W (O) | R (O) | | | +| SOS-NTONES-us | 7.3.1.10.4 | R/W (O) | | | | +| SOS-CRC-ds | 7.3.1.10.5 | R/W (O) | R (O) | | | +| SOS-CRC-us | 7.3.1.10.6 | R/W (O) | | | | +| MAX-SOS-ds | 7.3.1.10.7 | R/W (O) | R (O) | | | +| MAX-SOS-us | 7.3.1.10.8 | R/W (O) | | | | +| SNRMOFFSET-ROC-ds | 7.3.1.10.9 | R/W (O) | R (O) | | | +| SNRMOFFSET-ROC-us | 7.3.1.10.10 | R/W (O) | | | | +| INPMIN-ROC-ds | 7.3.1.10.11 | R/W (O) | R (O) | | | +| INPMIN-ROC-us | 7.3.1.10.12 | R/W (O) | | | | +| Retransmission | | | | | | +| RTX_MODE | 7.3.1.11 | R/W (M) | | | | +| LEFTR_THRESH | 7.3.1.12 | R/W (M) | | | | +| ITU-T G.993.5 specific (Vectoring) | | | | | | +| Vectoring frequency-band control upstream (VECTOR_BAND_CONTROLus) | 7.3.1.13.1 | R/W (M) | | | | +| Vectoring frequency-band control downstream (VECTOR_BAND_CONTROLds) | 7.3.1.13.2 | R/W (M) | | | | +| FEXT cancellation line priorities upstream (FEXT_CANCEL_PRIORITYus) | 7.3.1.13.3 | R/W (O) | | | | +| FEXT cancellation line priorities downstream (FEXT_CANCEL_PRIORITYds) | 7.3.1.13.4 | R/W (O) | | | | +| FEXT cancellation enabling/disabling upstream (FEXT_CANCEL_ENABLEus) | 7.3.1.13.5 | R/W (M) | | | | +| FEXT cancellation enabling/disabling downstream (FEXT_CANCEL_ENABLEds) | 7.3.1.13.6 | R/W (M) | | | | +| XLINGREQds | 7.3.1.13.7 | R/W(M) | | | | +| XLINGREQus | 7.3.1.13.8 | R/W(M) | | | | +| VECTORMODE_ENABLE | 7.3.1.13.9 | R/W(O) | | | | +| MAXDELAYOCTET split | | | | | | +| MDOSPLIT | 7.3.1.14 | R/W(O) | | | | +| ATTNDR configuration parameters | | | | | | +| ATTNDR_METHOD | 7.3.1.15.1 | R/W(O) | | | | +| ATTNDR_MDOSPLIT | 7.3.1.15.2 | R/W(O) | | | | +| VDSL2-LR configuration parameter | | | | | | +| VDSL2-LR_ENABLE | 7.3.1.16.1 | R/W(M) | | | | +| STRONGFEXT MODE configuration parameter | | | | | | +| STRONGFEXT_MODE | 7.3.1.17.1 | R/W(M) | | | | + +**Table 7-15 – Support of line configuration parameters per Recommendation** + +| Category/
element | [ITU-T
G.992.1] | [ITU-T
G.992.2] | [ITU-T
G.992.3] | [ITU-T
G.992.4] | [ITU-T
G.992.5] | [ITU-T
G.993.2] | [ITU-T
G.998.4] | [ITU-T
G.993.5] | +|------------------------------------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------| +| Line/xTU state | | | | | | | | | +| xTU transmission system enabling (XTSE) | Y | Y | Y | Y | Y | Y | | | +| ATU impedance state forced (AISF) | | | Y
(Annex A) | Y
(Annex A) | Y
(Annex A) | | | | +| Power management state forced (PMSF) | Y | Y | Y | Y | Y | Y | | | +| Power management state enabling (PMMode) | Y | Y | Y | Y | Y | Y | | | +| L0-TIME | | | Y | Y | Y | | | | +| L2-TIME | | | Y | Y | Y | | | | +| L2-ATPR | | | Y | Y | Y | | | | +| L2-ATPRT | | | Y | Y | Y | | | | +| Loop diagnostic mode forced (LDSF) | | | Y | Y | Y | Y | | | +| Automode cold start forced | | | Y | Y | Y | Y | | | +| VDSL2 profiles enabling (PROFILES) | | | | | | Y | | | +| RIPOLICYds | | | | | | Y | | | +| RIPOLICYus | | | | | | Y | | | +| REINIT_TIME_THRESH
OLDds | | | | | | Y | | | +| REINIT_TIME_THRESH
OLDus | | | | | | Y | | | +| Power and spectrum usage | | | | | | | | | +| MAXNOMPSD ds | | | Y | Y | Y | Y
(Note 5) | | Y
(Note 4) | +| MAXNOMPSD us | | | Y | Y | Y | Y
(Note 5) | | Y
(Note 4) | +| MAXNOMATP ds | | | Y | Y | Y | Y | | | +| MAXNOMATP us | | | Y | Y | Y | | | | +| MAXRXPWR us | | | Y | Y | Y | | | | +| CARMASK ds | | | Y | Y | Y | | | | +| CARMASK us | | | Y | Y | Y | | | | +| VDSL2-CARMASK | | | | | | Y | | | +| PSDMASK ds | | | | | Y | Y | | | +| RFIBANDS | | | | | Y | Y | | | +| Upstream PSD mask selection | | | Y | | Y | | | | +| PSDMASK us | | | Y
(Annexes J/M) | | Y
(Annexes J/M) | Y | | | +| DPBOSHAPED | | | | | Y | Y | | | +| UPBOSHAPED
(UPBOPSD-pb, UPBOKL,
UPBOKLF) | | | | | | Y | | | +| UPBOSHAPED
(UPBOKLREF-pb) | | | | | | Y | | | + +**Table 7-15 – Support of line configuration parameters per Recommendation** + +| Category/
element | [ITU-T
G.992.1] | [ITU-T
G.992.2] | [ITU-T
G.992.3] | [ITU-T
G.992.4] | [ITU-T
G.992.5] | [ITU-T
G.993.2] | [ITU-T
G.998.4] | [ITU-T
G.993.5] | +|-----------------------------------------------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------| +| UPBOSHAPED (AELE-MODE, UPBOELMT) | | | | | | Y | | | +| VDSL2 PSD mask class selection (CLASSMASK) | | | | | | Y | | | +| VDSL2 limit PSD masks and band plans enabling (LIMITMASK) | | | | | | Y | | | +| VDSL2 US0 disabling (US0DISABLE) | | | | | | Y | | | +| VDSL2 US0 masks enabling (US0MASK) | | | | | | Y
(Annex A) | | | +| Noise margins | | | | | | | | | +| TARSNRM ds | Y | Y | Y | Y | Y | Y | | | +| TARSNRM us | Y | Y | Y | Y | Y | Y | | | +| MAXSNRM ds | Y | Y | Y | Y | Y | Y | | | +| MAXSNRM us | Y | Y | Y | Y | Y | Y | | | +| MINSNRM ds | Y | Y | Y | Y | Y | Y | | | +| MINSNRM us | Y | Y | Y | Y | Y | Y | | | +| Rate adaptation | | | | | | | | | +| RA-MODE ds | | Y | Y | Y | Y | Y | | | +| RA-MODE us | | Y | Y | Y | Y | Y | | | +| RA-USNRM ds | | Y | Y | Y | Y | Y | | | +| RA-USNRM us | | Y | Y | Y | Y | Y | | | +| RA-UTIME ds | | Y | Y | Y | Y | Y | | | +| RA-UTIME us | | Y | Y | Y | Y | Y | | | +| RA-DSNRM ds | | Y | Y | Y | Y | Y | | | +| RA-DSNRM us | | Y | Y | Y | Y | Y | | | +| RA-DTIME ds | | Y | Y | Y | Y | Y | | | +| RA-DTIME us | | Y | Y | Y | Y | Y | | | +| Overhead | | | | | | | | | +| MSGMIN us | | | Y | Y | Y | Y | | | +| MSGMIN ds | | | Y | Y | Y | Y | | | +| Cyclic extension | | | | | | | | | +| CEFLAG | | | | | | Y | | | +| Transmitter referred virtual noise | | | | | | | | | +| SNRMODEds | | | Y | | Y | Y | | | +| SNRMODEus | | | Y | | Y | Y | | | +| VNdS | | | Y | | Y | Y | | | +| FEXT TXREFVNdS | | | Y | | Y | | | | +| NEXT TXREFVNdS | | | Y | | Y | | | | +| VNus | | | Y
(Note 1) | | Y
(Note 1) | Y
(Note 1) | | | +| RXREFVNSFus | | | | | | Y | | | +| TXREFVNSFds | | | | | | Y | | | + +**Table 7-15 – Support of line configuration parameters per Recommendation** + +| Category/
element | [ITU-T
G.992.1] | [ITU-T
G.992.2] | [ITU-T
G.992.3] | [ITU-T
G.992.4] | [ITU-T
G.992.5] | [ITU-T
G.993.2] | [ITU-T
G.998.4] | [ITU-T
G.993.5] | +|----------------------------------------------------------------------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------| +| Near-end performance monitoring thresholds (15 min interval) | | | | | | | | | +| FECS-L threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| ES-L threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| SES-L threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| LOSS-L threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| UAS-L threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| "lefr" defect seconds
threshold 15 min | | | | | | | Y | | +| Near-end performance monitoring thresholds (24 h interval) | | | | | | | | | +| FECS-L threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| ES-L threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| SES-L threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| LOSS-L threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| UAS-L threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| "lefr" defect seconds
threshold 24 h | | | | | | | Y | | +| Far-end performance monitoring thresholds (15 min interval) | | | | | | | | | +| FECS-LFE threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| ES-LFE threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| SES-LFE threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| LOSS-LFE threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| UAS-LFE threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| "lefr" defect seconds
threshold 15 min | | | | | | | Y | | +| Far-end performance monitoring thresholds (24 h interval) | | | | | | | | | +| FECS-LFE threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| ES-LFE threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| SES-LFE threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| LOSS-LFE threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| UAS-LFE threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| "lefr" defect seconds
threshold 24 h | | | | | | | Y | | +| Initialization performance monitoring thresholds (15 min interval) | | | | | | | | | +| Full inits threshold 15 min | Y | Y | Y | | Y | Y | | | +| Failed full inits threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| Short inits threshold 15 min | | Y | Y | Y | Y | Y | | | +| Failed short inits threshold 15 min | | Y | Y | Y | Y | Y | | | +| Initialization performance monitoring thresholds (24 h interval) | | | | | | | | | +| Full inits threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| Failed full inits threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| Short inits threshold 24 h | | Y | Y | Y | Y | Y | | | + +**Table 7-15 – Support of line configuration parameters per Recommendation** + +| Category/
element | [ITU-T
G.992.1] | [ITU-T
G.992.2] | [ITU-T
G.992.3] | [ITU-T
G.992.4] | [ITU-T
G.992.5] | [ITU-T
G.993.2] | [ITU-T
G.998.4] | [ITU-T
G.993.5] | +|-----------------------------------------------------------------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------| +| Failed short inits threshold
24 h | | Y | Y | Y | Y | Y | | | +| Short interruption performance monitoring thresholds (24 h interval) | | | | | | | | | +| SPONT_INTRPT threshold
24 h | | | | | | Y | | | +| INM configuration parameters | | | | | | | | | +| INMIATODs | | | Y | | Y | Y | | | +| INMIATous | | | | | | Y | | | +| INMIATSds | | | Y | | Y | Y | | | +| INMIATSus | | | | | | Y | | | +| INMCCds | | | Y | | Y | Y | | | +| INMCCus | | | | | | Y | | | +| INM_INPEQ_
MODEds | | | Y | | Y | Y | | | +| INM_INPEQ_
MODEus | | | | | | Y | | | +| INM_INPEQ_FORMATds | | | | | | Y | | | +| INM_INPEQ_FORMATus | | | | | | Y | | | +| INM_ENABLE | | | | | | Y | | | +| SOS configuration parameters | | | | | | | | | +| SOS-TIME-ds | | | | | | Y | | | +| SOS-TIME-us | | | | | | Y | | | +| SOS-NTONES-ds | | | | | | Y | | | +| SOS-NTONES-us | | | | | | Y | | | +| SOS-CRC-ds | | | | | | Y | | | +| SOS-CRC-us | | | | | | Y | | | +| MAX-SOS-ds | | | | | | Y | | | +| MAX-SOS-us | | | | | | Y | | | +| SNRMOFFSET-ROC-ds | | | | | | Y | | | +| SNRMOFFSET-ROC-us | | | | | | Y | | | +| INPMIN-ROC-ds | | | | | | Y | | | +| INPMIN-ROC-us | | | | | | Y | | | +| Retransmission | | | | | | | | | +| RTX_MODE | | | | | | | Y | | +| LEFTR_THRESH | | | | | | | Y | | +| ITU-T G.993.5 specific (Vectoring) | | | | | | | | | +| VECTOR_BAND_
CONTROLus | | | | | | | | Y | +| VECTOR_BAND_
CONTROLds | | | | | | | | Y | +| FEXT_CANCEL_
PRIORITYus | | | | | | | | Y | +| FEXT_CANCEL_
PRIORITYds | | | | | | | | Y | +| FEXT_CANCEL_
ENABLEus | | | | | | | | Y | + +**Table 7-15 – Support of line configuration parameters per Recommendation** + +| Category/
element | [ITU-T
G.992.1] | [ITU-T
G.992.2] | [ITU-T
G.992.3] | [ITU-T
G.992.4] | [ITU-T
G.992.5] | [ITU-T
G.993.2] | [ITU-T
G.998.4] | [ITU-T
G.993.5] | +|------------------------------------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------| +| FEXT_CANCEL_
ENABLEds | | | | | | | | Y | +| XLINGREQds | | | | | | | | Y | +| XLINGREQus | | | | | | | | Y | +| VECTORMODE_
ENABLE | | | | | | Y
(Note 3) | | Y | +| MAXDELAYOCTET split | | | | | | | | | +| MDOSPLIT | | | | | | Y | | | +| ATTNDR configuration parameters | | | | | | | | | +| ATTNDR_
METHOD | | | | | | Y | | Y
(Note 2) | +| ATTNDR_
MDOSPLIT | | | | | | Y | | Y
(Note 2) | +| VDSL2-LR configuration parameter | | | | | | | | | +| VDSL2-LR_ENABLE | | | | | | Y
(Note 5) | | Y
(Note 4) | +| STRONGFEXT MODE configuration parameter | | | | | | | | | +| STRONGFEXT_MODE | | | | | | | | Y
(Note 6) | + +NOTE 1 – In SNRM\_MODE = 3 or 4 (Receiver referred virtual noise), this parameter is only defined for [ITU-T G.993.2]. +NOTE 2 – Those parameters apply only to ITU-T G.998.4 when used in conjunction with ITU-T G.993.2. +NOTE 3 – This parameter applies only when Annex X or Annex Y is supported. +NOTE 4 – This parameter applies only when Annex B is supported. +NOTE 5 – This parameter applies only when Annex D is supported. +NOTE 6 – This parameter applies only when Annex A is supported. + +**Table 7-16 – Channel configuration profile** + +| Category/element | Specified
in clause | Q-
interface | U-C
interface | U-R
interface | T/S
interface | +|--------------------------------------|------------------------|-----------------|------------------|------------------|------------------| +| Data Rate | | | | | | +| Minimum data rate | 7.3.2.1.1 | R/W (M) | R (O) | | | +| Minimum reserved data rate | 7.3.2.1.2 | R/W (O) | R (O) | | | +| Maximum data rate | 7.3.2.1.3 | R/W (M) | R (O) | | | +| Rate adaptation ratio | 7.3.2.1.4 | R/W (O) | R (O) | | | +| Minimum data rate in low power state | 7.3.2.1.5 | R/W (M) | R (O) | | | +| MIN-SOS-DR | 7.3.2.1.6 | R/W (O) | R (O) | | | +| MINETR_RTX | 7.3.2.1.8 | R/W (M) | | | | +| MAXETR_RTX | 7.3.2.1.9 | R/W (M) | | | | +| MAXNDR_RTX | 7.3.2.1.10 | R/W (M) | | | | +| DELAYMAX_RTX | 7.3.2.1.11 | R/W (M) | | | | +| DELAYMIN_RTX | 7.3.2.1.12 | R/W (M) | | | | +| INPMIN_SHINE_RTX | 7.3.2.1.13 | R/W (M) | | | | +| INPMIN8_SHINE_RTX | 7.3.2.1.14 | R/W (M) | | | | +| SHINERATIO_RTX | 7.3.2.1.15 | R/W (M) | | | | + +**Table 7-16 – Channel configuration profile** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--------------------|---------------|---------------|---------------| +| INPMIN_REIN_RTX | 7.3.2.16 | R/W (M) | | | | +| INPMIN8_REIN_RTX | 7.3.2.17 | R/W (M) | | | | +| IAT_REIN_RTX | 7.3.2.18 | R/W (M) | | | | +| Maximum interleaving delay | 7.3.2.2 | R/W (M) | R (O) | | | +| Minimum impulse noise protection (INPMIN) | 7.3.2.3 | R/W (M/O) (Note 1) | R (O) | | | +| Minimum impulse noise protection 8 kHz (INPMIN8) | 7.3.2.4 | R/W (M) | R (O) | | | +| FORCEINP | 7.3.2.5 | R/W (M/O) (Note 2) | | | | +| Maximum bit error ratio | 7.3.2.6 | R/W (M) | R (O) | | | +| Data rate threshold upshift | 7.3.2.8.1 | R/W (M) | | | | +| Data rate threshold downshift | 7.3.2.8.2 | R/W (M) | | | | +| Maximum delay variation (DVMAX) | 7.3.2.9 | R/W (O) | | | | +| Channel initialization policy selection (CIPOLICY) | 7.3.2.10 | R/W (O) | | | | +| Near-end (xTU-C) performance monitoring thresholds (15 min interval) | | | | | | +| CV-C threshold 15 min | 7.3.2.7 | R/W (O) | R (O) | | | +| FEC-C threshold 15 min | 7.3.2.7 | R/W (O) | R (O) | | | +| Near-end (xTU-C) performance monitoring thresholds (24 h interval) | | | | | | +| CV-C threshold 24 h | 7.3.2.7 | R/W (O) | R (O) | | | +| FEC-C threshold 24 h | 7.3.2.7 | R/W (O) | R (O) | | | +| Far-end (xTU-R) performance monitoring thresholds (15 min interval) | | | | | | +| CV-CFE threshold 15 min | 7.3.2.7 | R/W (O) | R (O) | | | +| FEC-CFE threshold 15 min | 7.3.2.7 | R/W (O) | R (O) | | | +| Far-end (xTU-R) performance monitoring thresholds (24 h interval) | | | | | | +| CV-CFE threshold 24 h | 7.3.2.7 | R/W (O) | R (O) | | | +| FEC-CFE threshold 24 h | 7.3.2.7 | R/W (O) | R (O) | | | +| ITU-T G.993.5 specific (Vectoring) | | | | | | +| Target net data rate (TARGET_NDR) | 7.3.2.19.1 | R/W (M) | | | | +| Target expected throughput (TARGET_ETR) | 7.3.2.19.2 | R/W (M) | | | | +| NOTE 1 – This parameter is R/W (O) on the Q-interface for [ITU-T G.992.1] and R/W (M) for all other ITU-T Recommendations that support it.
NOTE 2 – This parameter is R/W (M) on the Q-interface for [ITU-T G.993.2] and R/W (O) for all other ITU-T Recommendations that support it. | | | | | | + +**Table 7-17 – Support of channel configuration parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | [ITU-T G.993.5] | +|-----------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Data rate | | | | | | | | | +| Minimum data rate (Note) | Y | Y | Y | Y | Y | Y | | | +| Minimum reserved data rate (Note) | | Y | Y | Y | Y | Y | | | +| Maximum data rate (Note) | Y | Y | Y | Y | Y | Y | | | +| Rate adaptation ratio | Y | Y | Y | Y | Y | Y | | | +| Minimum data rate in low power state (Note) | | Y | Y | Y | Y | | | | +| MIN-SOS-DR (Note) | | | | | | Y | | | +| Maximum interleaving delay (Note) | Y | Y | Y | Y | Y | Y | | | +| Minimum impulse noise protection (INPMIN) (Note) | Y | | Y | Y | Y | Y | | | +| Minimum impulse noise protection 8 kHz (INPMIN8) (Note) | | | | | | Y | | | +| FORCEINP (Note) | | | Y | | Y | Y | | | +| Maximum bit error ratio (Note) | | | Y | Y | Y | | | | +| Data rate threshold upshift (Note) | Y | Y | Y | Y | Y | | | | +| Data rate threshold downshift (Note) | Y | Y | Y | Y | Y | | | | +| Maximum delay variation (DVMAX) (Note) | | | | | | Y | | | +| Channel initialization policy selection (CIPOLICY) (Note) | | | Y | | Y | Y | | | +| MINETR_RTX | | | | | | | Y | | +| MAXETR_RTX | | | | | | | Y | | +| MAXNDR_RTX | | | | | | | Y | | +| DELAYMAX_RTX | | | | | | | Y | | +| DELAYMIN_RTX | | | | | | | Y | | +| INPMIN_SHINE_RTX | | | | | | | Y | | +| INPMIN8_SHINE_RTX | | | | | | | Y | | +| SHINERATIO_RTX | | | | | | | Y | | +| INPMIN_REIN_RTX | | | | | | | Y | | + +**Table 7-17 – Support of channel configuration parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | [ITU-T G.993.5] | +|----------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| INPMIN8_REIN_RTX | | | | | | | Y | | +| IAT_REIN_RTX | | | | | | | Y | | +| Near-end performance monitoring thresholds (15 min interval) | | | | | | | | | +| CV-C threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| FEC-C threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| Near-end performance monitoring thresholds (24 h interval) | | | | | | | | | +| CV-C threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| FEC-C threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| Far-end performance monitoring thresholds (15 min interval) | | | | | | | | | +| CV-CFE threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| FEC-CFE threshold 15 min | Y | Y | Y | Y | Y | Y | | | +| Far-end performance monitoring thresholds (24 h interval) | | | | | | | | | +| CV-CFE threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| FEC-CFE threshold 24 h | Y | Y | Y | Y | Y | Y | | | +| ITU-T G.993.5 specific (Vectoring) | | | | | | | | | +| TARGET_NDR | | | | | | | | Y | +| TARGET_ETR | | | | | | | | Y | +| NOTE – The parameter is not applicable to [ITU-T G.992.3] or [ITU-T G.992.5] and [ITU-T G.993.2] when retransmission is enabled. | | | | | | | | | + +**Table 7-18 – Asynchronous transfer mode data path configuration profile** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|-----------------------------------------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| IMA configuration | | | | | | +| IMA operation mode enable parameter | 7.3.4.1 | R/W (M) | | | | +| Near-end (xTU-C) performance monitoring thresholds (15 min interval) | | | | | | +| HEC-P threshold 15 min | 7.3.4.2 | R/W (O) | R (O) | | | +| CD-P threshold 15 min | 7.3.4.2 | R/W (O) | R (O) | | | +| CU-P threshold 15 min | 7.3.4.2 | R/W (O) | R (O) | | | +| IBE-P threshold 15 min | 7.3.4.2 | R/W (O) | R (O) | | | +| Near-end (xTU-C) performance monitoring thresholds (24 h interval) | | | | | | +| HEC-P threshold 24 h | 7.3.4.2 | R/W (O) | R (O) | | | +| CD-P threshold 24 h | 7.3.4.2 | R/W (O) | R (O) | | | +| CU-P threshold 24 h | 7.3.4.2 | R/W (O) | R (O) | | | +| IBE-P threshold 24 h | 7.3.4.2 | R/W (O) | R (O) | | | + +**Table 7-18 – Asynchronous transfer mode data path configuration profile** + +| Category/element | Specified in clause | Q- interface | U-C interface | U-R interface | T/S interface | +|----------------------------------------------------------------------------|---------------------|--------------|---------------|---------------|---------------| +| Far-end (xTU-R) performance monitoring thresholds (15 min interval) | | | | | | +| HEC-PFE threshold 15 min | 7.3.4.2 | R/W (O) | R (O) | | | +| CD-PFE threshold 15 min | 7.3.4.2 | R/W (O) | R (O) | | | +| CU-PFE threshold 15 min | 7.3.4.2 | R/W (O) | R (O) | | | +| IBE-PFE threshold 15 min | 7.3.4.2 | R/W (O) | R (O) | | | +| Far-end (xTU-R) performance monitoring thresholds (24 h interval) | | | | | | +| HEC-PFE threshold 24 h | 7.3.4.2 | R/W (O) | R (O) | | | +| CD-PFE threshold 24 h | 7.3.4.2 | R/W (O) | R (O) | | | +| CU-PFE threshold 24 h | 7.3.4.2 | R/W (O) | R (O) | | | +| IBE-PFE threshold 24h | 7.3.4.2 | R/W (O) | R (O) | | | + +**Table 7-19 – Support of asynchronous transfer mode data path configuration parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | +|---------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| IMA configuration | | | | | | | +| IMA operation mode enable parameter | | | Y | Y | Y | | +| Near-end performance monitoring thresholds (15 min interval) | | | | | | | +| HEC-P threshold 15 min | Y | Y | Y | Y | Y | Y | +| CD-P threshold 15 min | Y | Y | Y | Y | Y | Y | +| CU-P threshold 15 min | Y | Y | Y | Y | Y | Y | +| IBE-P threshold 15 min | Y | Y | Y | Y | Y | Y | +| Near-end performance monitoring thresholds (24 h interval) | | | | | | | +| HEC-P threshold 24 h | Y | Y | Y | Y | Y | Y | +| CD-P threshold 24 h | Y | Y | Y | Y | Y | Y | +| CU-P threshold 24 h | Y | Y | Y | Y | Y | Y | +| IBE-P threshold 24 h | Y | Y | Y | Y | Y | Y | +| Far-end performance monitoring thresholds (15 min interval) | | | | | | | +| HEC-PFE threshold 15 min | Y | Y | Y | Y | Y | Y | +| CD-PFE threshold 15 min | Y | Y | Y | Y | Y | Y | +| CU-PFE threshold 15 min | Y | Y | Y | Y | Y | Y | +| IBE-PFE threshold 15 min | Y | Y | Y | Y | Y | Y | +| Far-end performance monitoring thresholds (24 h interval) | | | | | | | +| HEC-PFE threshold 24 h | Y | Y | Y | Y | Y | Y | +| CD-PFE threshold 24 h | Y | Y | Y | Y | Y | Y | +| CU-PFE threshold 24 h | Y | Y | Y | Y | Y | Y | +| IBE-PFE threshold 24 h | Y | Y | Y | Y | Y | Y | + +**Table 7-20 – Line inventory** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|--------------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| xTU-C ITU-T G.994.1 vendor ID | 7.4.1 | R (M) | R (O) | | R (O) | +| xTU-R ITU-T G.994.1 vendor ID | 7.4.2 | R (M) | | R (O) | R (O) | +| xTU-C system vendor ID | 7.4.3 | R (M) | R (O) | | R (O) | +| xTU-R system vendor ID | 7.4.4 | R (M) | | R (O) | R (O) | +| xTU-C version number | 7.4.5 | R (M) | R (O) | | R (O) | +| xTU-R version number | 7.4.6 | R (M) | | R (O) | R (O) | +| xTU-C serial number | 7.4.7 | R (M) | R (O) | | R (O) | +| xTU-R serial number | 7.4.8 | R (M) | | R (O) | R (O) | +| xTU-C self-test result | 7.4.9 | R (M) | R (O) | | R (O) | +| xTU-R self-test result | 7.4.10 | R (M) | | R (O) | R (O) | +| xTU-C transmission system capabilities | 7.4.11 | R (M) | R (O) | | R (O) | +| xTU-R transmission system capabilities | 7.4.12 | R (M) | | R (O) | R (O) | +| ITU-T G.993.5 specific (Vectoring) | | | | | | +| VCE ID (VCE_ID) | 7.4.13.1 | R (M) | | | | +| VCE port index (VCE_port_index) | 7.4.13.2 | R (M) | | | | +| VDSL2-LR specific | | | | | | +| VTU-O VDSL2-LR_SUPPORT | 7.4.14.1 | R(M) | | | | +| VTU-R VDSL2-LR_SUPPORT | 7.4.14.2 | R(M) | | | | +| STRONGFEXT MODE specific | | | | | | +| VTU-O STRONGFEXT MODE support | 7.4.15.1 | R(M) | | | | +| VTU-R STRONGFEXT MODE support | 7.4.15.2 | R(M) | | | | + +**Table 7-21 – Support of line inventory information per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.993.5] | +|----------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| xTU-C ITU-T G.994.1 vendor ID | Y | Y | Y | Y | Y | Y | | +| xTU-R ITU-T G.994.1 vendor ID | Y | Y | Y | Y | Y | Y | | +| xTU-C system vendor ID | Y | Y | Y | Y | Y | Y | | +| xTU-R system vendor ID | Y | Y | Y | Y | Y | Y | | +| xTU-C version number | Y | Y | Y | Y | Y | Y | | +| xTU-R version number | Y | Y | Y | Y | Y | Y | | +| xTU-C serial number | Y | Y | Y | Y | Y | Y | | +| xTU-R serial number | Y | Y | Y | Y | Y | Y | | +| xTU-C self-test result | Y | Y | Y | Y | Y | Y | | +| xTU-R self-test result | Y | Y | Y | Y | Y | Y | | +| xTU-C transmission system capabilities | Y | Y | Y | Y | Y | Y | | +| xTU-R transmission system capabilities | Y | Y | Y | Y | Y | Y | | + +**Table 7-21 – Support of line inventory information per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.993.5] | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| ITU-T G.993.5 specific (Vectoring) | | | | | | | | +| VCE_ID | | | | | | | Y | +| VCE_port_index | | | | | | | Y | +| VDSL2-LR specific | | | | | | | | +| VTU-O VDSL2-LR_SUPPORT | | | | | | Y
(Note 2) | Y
(Note 1) | +| VTU-R VDSL2-LR_SUPPORT | | | | | | Y
(Note 2) | Y
(Note 1) | +| STRONGFEXT MODE specific | | | | | | | | +| VTU-O STRONGFEXT MODE SUPPORT | | | | | | | Y
(Note 3) | +| VTU-R STRONGFEXT MODE SUPPORT | | | | | | | Y
(Note 3) | +| NOTE 1 – This parameter applies only when Annex B is supported.
NOTE 2 – This parameter applies only when Annex D is supported.
NOTE 3 – This parameter applies only when Annex A is supported. | | | | | | | | + +**Table 7-22 – Line performance monitoring parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|---------------------------------------------------------------------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| Near-end (xTU-C) performance monitoring parameters (current and previous 15 min interval) | | | | | | +| FECS-L counter 15 min | 7.2.1.1.1 | R (M) | R (O) | | | +| ES-L counter 15 min | 7.2.1.1.2 | R (M) | R (O) | | R (O) | +| SES-L counter 15 min | 7.2.1.1.3 | R (M) | R (O) | | R (O) | +| LOSS-L counter 15 min | 7.2.1.1.4 | R (M) | R (O) | | | +| UAS-L counter 15 min | 7.2.1.1.5 | R (M) | R (O) | | | +| "leftr" defect seconds counter 15 min | 7.2.1.1.6 | R (M) | | | | +| Error-free bits counter 15 min | 7.2.1.1.7 | R (M) | | | | +| MINEFTR 15 min | 7.2.1.1.8 | R (M) | | | | +| MAXEFTR 15 min | 7.2.1.1.9 | R (O) | | | | +| Near-end (xTU-C) performance monitoring parameters (current and previous 24 h interval) | | | | | | +| FECS-L counter 24 h | 7.2.1.1.1 | R (M) | R (O) | | | +| ES-L counter 24 h | 7.2.1.1.2 | R (M) | R (O) | | R (O) | +| SES-L counter 24 h | 7.2.1.1.3 | R (M) | R (O) | | R (O) | +| LOSS-L counter 24 h | 7.2.1.1.4 | R (M) | R (O) | | | +| UAS-L counter 24 h | 7.2.1.1.5 | R (M) | R (O) | | | +| "leftr" defect seconds counter 24 h | 7.2.1.1.6 | R (M) | | | | +| Error-free bits counter 24 h | 7.2.1.1.7 | R (M) | | | | +| MINEFTR 24 h | 7.2.1.1.8 | R (M) | | | | +| MAXEFTR 24 h | 7.2.1.1.9 | R (O) | | | | + +**Table 7-22 – Line performance monitoring parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|---------------------------------------------------------------------------------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| Far-end (xTU-R) performance monitoring parameters (current and previous 15 min interval) | | | | | | +| FECS-LFE counter 15 min | 7.2.1.2.1 | R (M) | | R (O) | | +| ES-LFE counter 15 min | 7.2.1.2.2 | R (M) | | R (O) | R (O) | +| SES-LFE counter 15 min | 7.2.1.2.3 | R (M) | | R (O) | R (O) | +| LOSS-LFE counter 15 min | 7.2.1.2.4 | R (M) | | R (O) | | +| UAS-LFE counter 15 min | 7.2.1.2.5 | R (M) | | R (O) | | +| "left" defect seconds counter 15 min | 7.2.1.2.6 | R (M) | | | | +| Error-free bits counter 15 min | 7.2.1.2.7 | R (M) | | | | +| MINEFTR 15 min | 7.2.1.2.8 | R (M) | | | | +| MAXEFTR 15 min | 7.2.1.2.9 | R (O) | | | | +| Far-end (xTU-R) performance monitoring parameters (current and previous 24 h interval) | | | | | | +| FECS-LFE counter 24 h | 7.2.1.2.1 | R (M) | | R (O) | | +| ES-LFE counter 24 h | 7.2.1.2.2 | R (M) | | R (O) | R (O) | +| SES-LFE counter 24 h | 7.2.1.2.3 | R (M) | | R (O) | R (O) | +| LOSS-LFE counter 24 h | 7.2.1.2.4 | R (M) | | R (O) | | +| UAS-LFE counter 24 h | 7.2.1.2.5 | R (M) | | R (O) | | +| "left" defect seconds counter 24 h | 7.2.1.2.6 | R (M) | | | | +| Error-free bits counter 24 h | 7.2.1.2.7 | R (M) | | | | +| MINEFTR 24 h | 7.2.1.2.8 | R (M) | | | | +| MAXEFTR 24 h | 7.2.1.2.9 | R (O) | | | | +| Initialization performance monitoring counters (current and previous 15 min interval) | | | | | | +| Full inits counter 15 min | 7.2.1.3.1 | R (M) | R (O) | | | +| Failed full inits counter 15 min | 7.2.1.3.2 | R (M) | R (O) | | | +| Short inits counter 15 min | 7.2.1.3.3 | R (O) | R (O) | | | +| Failed short inits counter 15 min | 7.2.1.3.4 | R (O) | R (O) | | | +| Initialization performance monitoring counters (current and previous 24 h interval) | | | | | | +| Full inits counter 24 h | 7.2.1.3.1 | R (M) | R (O) | | | +| Failed full inits counter 24 h | 7.2.1.3.2 | R (M) | R (O) | | | +| Short inits counter 24 h | 7.2.1.3.3 | R (O) | R (O) | | | +| Failed short inits counter 24 h | 7.2.1.3.4 | R (O) | R (O) | | | +| Short interruption performance monitoring counters (current and previous 24 h interval) | | | | | | +| LPR_INTRPT counter 24 h | 7.2.1.8.1 | R (O) | | | | +| HRI_INTRPT counter 24 h | 7.2.1.8.2 | R (O) | | | | +| SPONT_INTRPT counter 24 h | 7.2.1.8.3 | R (O) | | | | +| Near-end (xTU-C) impulse noise performance monitoring counters (current and previous 15 min interval) | | | | | | +| INMINPEQ1..17-L counter 15 min | 7.2.1.4.1 | R (O) | | | | +| INMIAT0..7-L counter 15 min | 7.2.1.4.3 | R (O) | | | | +| INMME-L counter 15 min | 7.2.1.4.2 | R (O) | | | | +| Near-end (xTU-C) impulse noise performance monitoring counters (current and previous 24 h interval) | | | | | | +| INMINPEQ1..17-L counter 24 h | 7.2.1.4.1 | R (O) | | | | +| INMIAT0..7-L counter 24 h | 7.2.1.4.3 | R (O) | | | | + +**Table 7-22 – Line performance monitoring parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|--------------------------------------------------------------------------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| INMME-L counter 24 h | 7.2.1.4.2 | R (O) | | | | +| Far-end (xTU-R) impulse noise performance monitoring counters (current and previous 15 min interval) | | | | | | +| INMINPEQ1..17-LFE counter 15 min | 7.2.1.5.1 | R (O) | | R (O) | | +| INMIAT0..7-LFE counter 15 min | 7.2.1.5.3 | R (O) | | R (O) | | +| INMME-LFE counter 15 min | 7.2.1.5.2 | R (O) | | R (O) | | +| Far-end (xTU-R) impulse noise performance monitoring counters (current and previous 24 h interval) | | | | | | +| INMINPEQ1..17-LFE counter 24 h | 7.2.1.5.1 | R (O) | | R (O) | | +| INMIAT0..7-LFE counter 24 h | 7.2.1.5.3 | R (O) | | R (O) | | +| INMME-LFE counter 24 h | 7.2.1.5.2 | R (O) | | R (O) | | +| Near-end (xTU-C) initiated OLR performance monitoring counters (current and previous 15 min interval) | | | | | | +| SOS-SUCCESS-NE counter 15 min | 7.2.1.6.1 | R (O) | | | | +| SRA-SUCCESS-NE counter 15 min | 7.2.1.6.2 | R (O) | | | | +| Near-end (xTU-C) initiated OLR performance monitoring counters (current and previous 24 h interval) | | | | | | +| SOS-SUCCESS-NE counter 24 h | 7.2.1.6.1 | R (O) | | | | +| SRA-SUCCESS-NE counter 24 h | 7.2.1.6.2 | R (O) | | | | +| Far-end (xTU-R) initiated OLR performance monitoring counters (current and previous 15 min interval) | | | | | | +| SOS-SUCCESS-FE counter 15 min | 7.2.1.7.1 | R (O) | | | | +| SRA-SUCCESS-FE counter 15 min | 7.2.1.7.2 | R (O) | | | | +| Far-end (xTU-R) initiated OLR performance monitoring counters (current and previous 24 h interval) | | | | | | +| SOS-SUCCESS-FE counter 24 h | 7.2.1.7.1 | R (O) | | | | +| SRA-SUCCESS-FE counter 24 h | 7.2.1.7.2 | R (O) | | | | + +**Table 7-23 – Support of line performance monitoring parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | +|------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Near-end performance monitoring parameters (current and previous 15 min interval) | | | | | | | | +| FECS-L counter 15 min | Y | Y | Y | Y | Y | Y | | +| ES-L counter 15 min | Y | Y | Y | Y | Y | Y | | +| SES-L counter 15 min | Y | Y | Y | Y | Y | Y | | +| LOSS-L counter 15 min | Y | Y | Y | Y | Y | Y | | +| UAS-L counter 15 min | Y | Y | Y | Y | Y | Y | | +| "leftr" defect seconds counter 15 min | | | | | | | Y | +| Error-free bits counter 15 min | | | | | | | Y | +| MINEFTR 15 min | | | | | | | Y | +| MAXEFTR 15 min | | | | | | | Y | +| Near-end performance monitoring parameters (current and previous 24 h interval) | | | | | | | | +| FECS-L counter 24 h | Y | Y | Y | Y | Y | Y | | + +**Table 7-23 – Support of line performance monitoring parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | +|----------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| ES-L counter 24 h | Y | Y | Y | Y | Y | Y | | +| SES-L counter 24 h | Y | Y | Y | Y | Y | Y | | +| LOSS-L counter 24 h | Y | Y | Y | Y | Y | Y | | +| UAS-L counter 24 h | Y | Y | Y | Y | Y | Y | | +| "leftr" defect seconds counter 24 h | | | | | | | Y | +| Error-free bits counter 24 h | | | | | | | Y | +| MINFTR 24 h | | | | | | | Y | +| MAXFTR 24 h | | | | | | | Y | +| Far-end performance monitoring parameters (current and previous 15 min interval) | | | | | | | | +| FECS-LFE counter 15 min | Y | Y | Y | Y | Y | Y | | +| ES-LFE counter 15 min | Y | Y | Y | Y | Y | Y | | +| SES-LFE counter 15 min | Y | Y | Y | Y | Y | Y | | +| LOSS-LFE counter 15 min | Y | Y | Y | Y | Y | Y | | +| UAS-LFE counter 15 min | Y | Y | Y | Y | Y | Y | | +| "leftr" defect seconds counter 15 min | | | | | | | Y | +| Error-free bits counter 15 min | | | | | | | Y | +| MINFTR 15 min | | | | | | | Y | +| MAXFTR 15 min | | | | | | | Y | +| Far-end performance monitoring parameters (current and previous 24 h interval) | | | | | | | | +| FECS-LFE counter 24 h | Y | Y | Y | Y | Y | Y | | +| ES-LFE counter 24 h | Y | Y | Y | Y | Y | Y | | +| SES-LFE counter 24 h | Y | Y | Y | Y | Y | Y | | +| LOSS-LFE counter 24 h | Y | Y | Y | Y | Y | Y | | +| UAS-LFE counter 24 h | Y | Y | Y | Y | Y | Y | | +| "leftr" defect seconds counter 24 h | | | | | | | Y | +| Error-free bits counter 24 h | | | | | | | Y | +| MINFTR 24 h | | | | | | | Y | +| MAXFTR 24 h | | | | | | | Y | +| Initialization performance monitoring counters (current and previous 15 min interval) | | | | | | | | +| Full inits counter 15 min | Y | Y | Y | Y | Y | Y | | +| Failed full inits counter 15 min | Y | Y | Y | Y | Y | Y | | +| Short inits counter 15 min | | Y | Y | Y | Y | Y | | +| Failed short inits counter 15 min | | Y | Y | Y | Y | Y | | + +**Table 7-23 – Support of line performance monitoring parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | +|---------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Initialization performance monitoring counters (current and previous 24 h interval) | | | | | | | | +| Full inits counter 24 h | Y | Y | Y | Y | Y | Y | | +| Failed full inits counter 24 h | Y | Y | Y | Y | Y | Y | | +| Short inits counter 24 h | | Y | Y | Y | Y | Y | | +| Failed short inits counter 24 h | | Y | Y | Y | Y | Y | | +| Short interruption performance monitoring counters (current and previous 24 h interval) | | | | | | | | +| LPR_INTRPT counter 24 h | | | | | | Y | | +| HRI_INTRPT counter 24 h | | | | | | Y | | +| SPONT_INTRPT counter 24 h | | | | | | Y | | +| Near-end impulse noise performance monitoring counters (current and previous 15 min interval) | | | | | | | | +| INMINPEQ 1..17-L counter 15 min | | | | | | Y | | +| INMIAT 0..7-L counter 15 min | | | | | | Y | | +| INMME-L counter 15 min | | | | | | Y | | +| Near-end impulse noise performance monitoring counters (current and previous 24 h interval) | | | | | | | | +| INMINPEQ 1..17-L counter 24 h | | | | | | Y | | +| INMIAT 0..7-L counter 24 h | | | | | | Y | | +| INMME-L counter 24 h | | | | | | Y | | +| Far-end impulse noise performance monitoring counters (current and previous 15 min interval) | | | | | | | | +| INMINPEQ 1..17-LFE counter 15 min | | | Y | | Y | Y | | +| INMIAT 0..7-LFE counter 15 min | | | Y | | Y | Y | | +| INMME-LFE counter 15 min | | | Y | | Y | Y | | +| Far-end impulse noise performance monitoring counters (current and previous 24 h interval) | | | | | | | | +| INMINPEQ 1..17-LFE counter 24 h | | | Y | | Y | Y | | +| INMIAT 0..7-LFE counter 24 h | | | Y | | Y | Y | | +| INMME-LFE counter 24 h | | | Y | | Y | Y | | +| Near-end (xTU-C) initiated OLR performance monitoring counters (current and previous 15 min interval) | | | | | | | | +| SOS-SUCCESS-NE counter 15 min | | | | | | Y | | +| SRA-SUCCESS-NE counter 15 min | | | | | | Y | | + +**Table 7-23 – Support of line performance monitoring parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | +|-------------------------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Near-end (xTU-C) initiated OLR performance monitoring counters (current and previous 24 h interval) | | | | | | | | +| SOS-SUCCESS-NE counter 24 h | | | | | | Y | | +| SRA-SUCCESS-NE counter 24 h | | | | | | Y | | +| Far-end (xTU-R) initiated OLR performance monitoring counters (current and previous 15 min interval) | | | | | | | | +| SOS-SUCCESS-FE counter 15 min | | | | | | Y | | +| SRA-SUCCESS-FE counter 15 min | | | | | | Y | | +| Far-end (xTU-R) initiated OLR performance monitoring counters (current and previous 24 h interval) | | | | | | | | +| SOS-SUCCESS-FE counter 24 h | | | | | | Y | | +| SRA-SUCCESS-FE counter 24 h | | | | | | Y | | + +**Table 7-24 – Channel performance monitoring parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|------------------------------------------------------------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| Near-end (xTU-C) performance monitoring counters (current and previous 15 min interval) | | | | | | +| CV-C counter 15 min | 7.2.2.1.1 | R (M) | R (O) | | | +| FEC-C counter 15 min | 7.2.2.1.2 | R (M) | R (O) | | | +| RTXUC-C counter 15 min | 7.2.2.1.3 | R (M) | R (O) | | | +| RTXTX-C counter 15 min | 7.2.2.1.4 | R (M) | R (O) | | | +| Near-end (xTU-C) performance monitoring counters (current and previous 24 h interval) | | | | | | +| CV-C counter 24 h | 7.2.2.1.1 | R (M) | R (O) | | | +| FEC-C counter 24 h | 7.2.2.1.2 | R (M) | R (O) | | | +| RTXUC-C counter 24 h | 7.2.2.1.3 | R (M) | R (O) | | | +| RTXTX-C counter 24 h | 7.2.2.1.4 | R (M) | R (O) | | | +| Far-end (xTU-R) performance monitoring counters (current and previous 15 min interval) | | | | | | +| CV-CFE counter 15 min | 7.2.2.2.1 | R (M) | | R (O) | | +| FEC-CFE counter 15 min | 7.2.2.2.2 | R (M) | | R (O) | | +| RTXUC-CFE counter 15 min | 7.2.2.2.3 | R (M) | | R (O) | | +| RTXTX-CFE counter 15 min | 7.2.2.2.4 | R (M) | | R (O) | | +| Far-end (xTU-R) performance monitoring counters (current and previous 24 h interval) | | | | | | +| CV-CFE counter 24 h | 7.2.2.2.1 | R (M) | | R (O) | | +| FEC-CFE counter 24 h | 7.2.2.2.2 | R (M) | | R (O) | | +| RTXUC-CFE counter 24 h | 7.2.2.2.3 | R (M) | | R (O) | | +| RTXTX-CFE counter 24 h | 7.2.2.2.4 | R (M) | | R (O) | | + +**Table 7-25 – Support of channel performance monitoring parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | +|----------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Near-end performance monitoring counters (current and previous 15 min interval) | | | | | | | | +| CV-C counter 15 min | Y | Y | Y | Y | Y | Y | | +| FEC-C counter 15 min | Y | Y | Y | Y | Y | Y | | +| RTXUC-C counter 15 min | | | | | | | Y | +| RTXTX-C counter 15 min | | | | | | | Y | +| Near-end performance monitoring counters (current and previous 24 h interval) | | | | | | | | +| CV-C counter 24 h | Y | Y | Y | Y | Y | Y | | +| FEC-C counter 24 h | Y | Y | Y | Y | Y | Y | | +| RTXUC-C counter 24 h | | | | | | | Y | +| RTXTX-C counter 24 h | | | | | | | Y | +| Far-end performance monitoring counters (current and previous 15 min interval) | | | | | | | | +| CV-CFE counter 15 min | Y | Y | Y | Y | Y | Y | | +| FEC-CFE counter 15 min | Y | Y | Y | Y | Y | Y | | +| RTXUC-CFE counter 15 min | | | | | | | Y | +| RTXTX-CFE counter 15 min | | | | | | | Y | +| Far-end performance monitoring counters (current and previous 24 h interval) | | | | | | | | +| CV-CFE counter 24 h | Y | Y | Y | Y | Y | Y | | +| FEC-CFE counter 24 h | Y | Y | Y | Y | Y | Y | | +| RTXUC-CFE counters 24 h | | | | | | | Y | +| RTXTX-CFE counters 24 h | | | | | | | Y | + +**Table 7-26 – Asynchronous transfer mode data path performance monitoring parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|------------------------------------------------------------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| Near-end (xTU-C) performance monitoring counters (current and previous 15 min interval) | | | | | | +| HEC-P counter 15 min | 7.2.4.1.1 | R (M) | R (O) | | | +| CD-P counter 15 min | 7.2.4.1.2 | R (M) | R (O) | | | +| CU-P counter 15 min | 7.2.4.1.3 | R (M) | R (O) | | | +| IBE-P counter 15 min | 7.2.4.1.4 | R (M) | R (O) | | R (O) | +| Near-end (xTU-C) performance monitoring counters (current and previous 24 h interval) | | | | | | +| HEC-P counter 24 h | 7.2.4.1.1 | R (M) | R (O) | | | +| CD-P counter 24 h | 7.2.4.1.2 | R (M) | R (O) | | | +| CU-P counter 24 h | 7.2.4.1.3 | R (M) | R (O) | | | +| IBE-P counter 24 h | 7.2.4.1.4 | R (M) | R (O) | | R (O) | +| Far-end (xTU-R) performance monitoring counters (current and previous 15 min interval) | | | | | | +| HEC-PFE counter 15 min | 7.2.4.2.1 | R (M) | | R (O) | | +| CD-PFE counter 15 min | 7.2.4.2.2 | R (M) | | R (O) | | +| CU-PFE counter 15 min | 7.2.4.2.3 | R (M) | | R (O) | | +| IBE-PFE counter 15 min | 7.2.4.2.4 | R (M) | | R (O) | R (O) | + +**Table 7-26 – Asynchronous transfer mode data path performance monitoring parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|---------------------------------------------------------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| Far-end (xTU-R) performance monitoring counters (current and previous 24 h interval) | | | | | | +| HEC-PFE counter 24 h | 7.2.4.2.1 | R (M) | | R (O) | | +| CD-PFE counter 24 h | 7.2.4.2.2 | R (M) | | R (O) | | +| CU-PFE counter 24 h | 7.2.4.2.3 | R (M) | | R (O) | | +| IBE-PFE counter 24 h | 7.2.4.2.4 | R (M) | | R (O) | R (O) | + +**Table 7-27 – Support of asynchronous transfer mode data path performance monitoring parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | +|----------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Near-end performance monitoring counters (current and previous 15 min interval) | | | | | | | +| HEC-P counter 15 min | Y | Y | Y | Y | Y | Y | +| CD-P counter 15 min | Y | Y | Y | Y | Y | Y | +| CU-P counter 15 min | Y | Y | Y | Y | Y | Y | +| IBE-P counter 15 min | Y | Y | Y | Y | Y | Y | +| Near-end performance monitoring counters (current and previous 24 h interval) | | | | | | | +| HEC-P counter 24 h | Y | Y | Y | Y | Y | Y | +| CD-P counter 24 h | Y | Y | Y | Y | Y | Y | +| CU-P counter 24 h | Y | Y | Y | Y | Y | Y | +| IBE-P counter 24 h | Y | Y | Y | Y | Y | Y | +| Far-end performance monitoring counters (current and previous 15 min interval) | | | | | | | +| HEC-PFE counter 15 min | Y | Y | Y | Y | Y | Y | +| CD-PFE counter 15 min | Y | Y | Y | Y | Y | Y | +| CU-PFE counter 15 min | Y | Y | Y | Y | Y | Y | +| IBE-PFE counter 15 min | Y | Y | Y | Y | Y | Y | +| Far-end performance monitoring counters (current and previous 24 h interval) | | | | | | | +| HEC-PFE counter 24 h | Y | Y | Y | Y | Y | Y | +| CD-PFE counter 24 h | Y | Y | Y | Y | Y | Y | +| CU-PFE counter 24 h | Y | Y | Y | Y | Y | Y | +| IBE-PFE counter 24 h | Y | Y | Y | Y | Y | Y | + +**Table 7-28 – Line test, diagnostic and status parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | G-interface | +|------------------------------------|---------------------|-------------|---------------|---------------|---------------|-------------| +| xDSL transmission system | 7.5.1.1 | R (M) | | | R (O) | R (O) | +| VDSL2 profile | 7.5.1.2 | R (M) | | | R (O) | R (O) | +| VDSL2 limit PSD mask and band plan | 7.5.1.3 | R (M) | | | R (O) | R (O) | +| VDSL2 US0 PSD mask | 7.5.1.4 | R (M) | | | R (O) | R (O) | + +**Table 7-28 – Line test, diagnostic and status parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | G-interface | +|---------------------------------------------|---------------------|-------------|---------------|---------------|---------------|-------------| +| Power management state | 7.5.1.5 | R (M) | | | R (O) | R (O) | +| RTX_USED_ds | 7.5.1.38 | R (M) | | | | | +| RTX_USED_us | 7.5.1.38 | R (M) | | | | | +| Initialization | | | | | | | +| Success/Failure cause | 7.5.1.6 | R (M) | | | R (M) | R (M) | +| Last state transmitted downstream | 7.5.1.7 | R (M) | | | R (M) | R (M) | +| Last state transmitted upstream | 7.5.1.8 | R (M) | | | R (M) | R (M) | +| Attenuation | | | | | | | +| LATNDs | 7.5.1.9 | R (M) | | R (O) | R (M) | R (M) | +| LATNus | 7.5.1.10 | R (M) | R (O) | | R (M) | R (M) | +| SATNDs | 7.5.1.11 | R (M) | | R (O) | R (M) | R (M) | +| SATNus | 7.5.1.12 | R (M) | R (O) | | R (M) | R (M) | +| Signal-to-noise ratio margin | | | | | | | +| SNRMds | 7.5.1.13 | R (M) | | R (O) | R (M) | R (M) | +| FEXT SNRMds | 7.5.1.13.1 | R (M) | | R (O) | R (M) | R (M) | +| NEXT SNRMds | 7.5.1.13.2 | R (M) | | R (O) | R (M) | R (M) | +| SNRMpbds | 7.5.1.14 | R (M) | | R (O) | R (M) | R (M) | +| ACTSNRMODEds | 7.5.1.15 | R (M) | | R (O) | R (M) | R (M) | +| SNRMus | 7.5.1.16 | R (M) | R (O) | | R (M) | R (M) | +| FEXT SNRMus | 7.5.1.16.1 | R (M) | R (O) | | R (M) | R (M) | +| NEXT SNRMus | 7.5.1.16.2 | R (M) | R (O) | | R (M) | R (M) | +| SNRMpbus | 7.5.1.17 | R (M) | R (O) | | R (M) | R (M) | +| ACTSNRMODEus | 7.5.1.18 | R (M) | R (O) | | R (M) | R (M) | +| Attainable data rate | | | | | | | +| ATTNDRds | 7.5.1.19 | R (M) | R (O) | | R (M) | R (M) | +| FEXT ATTNDRds | 7.5.1.19.1 | R (M) | R (O) | | R (M) | R (M) | +| NEXT ATTNDRds | 7.5.1.19.2 | R (M) | R (O) | | R (M) | R (M) | +| ATTNDRus | 7.5.1.20 | R (M) | | R (O) | R (M) | R (M) | +| FEXT ATTNDRus | 7.5.1.20.1 | R (M) | | R (O) | R (M) | R (M) | +| NEXT ATTNDRus | 7.5.1.20.2 | R (M) | | R (O) | R (M) | R (M) | +| Actual power spectral density | | | | | | | +| ACTPSDds | 7.5.1.21 | R (M) | R (O) | | | R (O) | +| FEXT ACTPSDds | 7.5.1.21.1 | R (M) | R (O) | | | R (O) | +| NEXT ACTPSDds | 7.5.1.21.2 | R (M) | R (O) | | | R (O) | +| ACTPSDus | 7.5.1.22 | R (M) | | R (O) | | R (O) | +| FEXT ACTPSDus | 7.5.1.22.1 | R (M) | | R (O) | | R (O) | +| NEXT ACTPSDus | 7.5.1.22.2 | R (M) | | R (O) | | R (O) | +| Upstream power back-off | | | | | | | +| UPBOKLE | 7.5.1.23.1 | R (M) | R (O) | | | R (O) | +| UPBOKLE-R | 7.5.1.23.2 | R (O) | R (O) | | | R (O) | + +**Table 7-28 – Line test, diagnostic and status parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | G-interface | +|-----------------------------------------------|---------------------|-------------|---------------|---------------|---------------|-------------| +| UPBOKLE-pb | 7.5.1.23.3 | R (O) | R (O) | | | | +| UPBOKLE-R-pb | 7.5.1.23.4 | R (O) | R (O) | | | R (O) | +| RXTHRSHds | 7.5.1.23.5 | R (O) | R (O) | | | R (O) | +| RXTHRSHus | 7.5.1.23.6 | R (O) | R (O) | | | | +| ACT-AELE-MODE | 7.5.1.23.7 | R (O) | | | | | +| Actual aggregate transmit power | | | | | | | +| ACTATPds | 7.5.1.24 | R (M) | | R (O) | R (M) | R (M) | +| FEXT ACTATPds | 7.5.1.24.1 | R (M) | | R (O) | R (M) | R (M) | +| NEXT ACTATPds | 7.5.1.24.2 | R (M) | | R (O) | R (M) | R (M) | +| ACTATPus | 7.5.1.25 | R (M) | R (O) | | R (M) | R (M) | +| FEXT ACTATPus | 7.5.1.25.1 | R (M) | R (O) | | R (M) | R (M) | +| NEXT ACTATPus | 7.5.1.25.2 | R (M) | R (O) | | R (M) | R (M) | +| Channel characteristics per subcarrier | | | | | | | +| HLINSCds | 7.5.1.26.1 | R (M) | R (O) | | R (M) | R (M) | +| HLINGds | 7.5.1.26.2 | R (M) | R (O) | | R (M) | R (M) | +| HLINpsds | 7.5.1.26.3 | R (M) | R (O) | | R (M) | R (M) | +| HLOGMTds | 7.5.1.26.4 | R (M) | R (O) | | R (M) | R (M) | +| HLOGGds | 7.5.1.26.5 | R (M) | R (O) | | R (M) | R (M) | +| HLOGpsds | 7.5.1.26.6 | R (M) | R (O) | | R (M) | R (M) | +| HLINSCus | 7.5.1.26.7 | R (M) | | R (O) | R (M) | R (M) | +| HLINGus | 7.5.1.26.8 | R (M) | | R (O) | R (M) | R (M) | +| HLINpsus | 7.5.1.26.9 | R (M) | | R (O) | R (M) | R (M) | +| HLOGMTus | 7.5.1.26.10 | R (M) | | R (O) | R (M) | R (M) | +| HLOGGus | 7.5.1.26.11 | R (M) | | R (O) | R (M) | R (M) | +| HLOGpsus | 7.5.1.26.12 | R (M) | | R (O) | R (M) | R (M) | +| Quiet line noise PSD per subcarrier | | | | | | | +| QLNMTds | 7.5.1.27.1 | R (M) | R (O) | | R (M) | R (M) | +| FEXT QLNMTds | 7.5.1.27.1.1 | R (M) | R (O) | | R (M) | R (M) | +| NEXT QLNMTds | 7.5.1.27.1.2 | R (M) | R (O) | | R (M) | R (M) | +| QLNGds | 7.5.1.27.2 | R (M) | R (O) | | R (M) | R (M) | +| QLNpsds | 7.5.1.27.3 | R (M) | R (O) | | R (M) | R (M) | +| FEXT QLNpsds | 7.5.1.27.3.1 | R (M) | R (O) | | R (M) | R (M) | +| NEXT QLNpsds | 7.5.1.27.3.2 | R (M) | R (O) | | R (M) | R (M) | +| QLNMTus | 7.5.1.27.4 | R (M) | | R (O) | R (M) | R (M) | +| FEXT QLNMTus | 7.5.1.27.4.1 | R (M) | | R (O) | R (M) | R (M) | +| NEXT QLNMTus | 7.5.1.27.4.2 | R (M) | | R (O) | R (M) | R (M) | +| QLNGus | 7.5.1.27.5 | R (M) | | R (O) | R (M) | R (M) | +| QLNpsus | 7.5.1.27.6 | R (M) | | R (O) | R (M) | R (M) | +| FEXT QLNpsus | 7.5.1.27.6.1 | R (M) | | R (O) | R (M) | R (M) | +| NEXT QLNpsus | 7.5.1.27.6.2 | R (M) | | R (O) | R (M) | R (M) | + +**Table 7-28 – Line test, diagnostic and status parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | G-interface | +|----------------------------------------------------|---------------------|-------------------|---------------|---------------|-------------------|-------------------| +| Signal-to-noise ratio per subcarrier | | | | | | | +| SNRMTds | 7.5.1.28.1 | R (M) | R (O) | | R (M) | R (M) | +| FEXT SNRMTds | 7.5.1.28.1.1 | R (M) | R (O) | | R (M) | R (M) | +| NEXT SNRMTds | 7.5.1.28.1.2 | R (M) | R (O) | | R (M) | R (M) | +| SNRGds | 7.5.1.28.2 | R (M) | R (O) | | R (M) | R (M) | +| SNRpsds | 7.5.1.28.3 | R (M) | R (O) | | R (M) | R (M) | +| FEXT SNRpsds | 7.5.1.28.3.1 | R (M) | R (O) | | R (M) | R (M) | +| NEXT SNRpsds | 7.5.1.28.3.2 | R (M) | R (O) | | R (M) | R (M) | +| SNRMTus | 7.5.1.28.4 | R (M) | | R (O) | R (M) | R (M) | +| FEXT SNRMTus | 7.5.1.28.4.1 | R (M) | | R (O) | R (M) | R (M) | +| NEXT SNRMTus | 7.5.1.28.4.2 | R (M) | | R (O) | R (M) | R (M) | +| SNRGus | 7.5.1.28.5 | R (M) | | R (O) | R (M) | R (M) | +| SNRpsus | 7.5.1.28.6 | R (M) | | R (O) | R (M) | R (M) | +| FEXT SNRpsus | 7.5.1.28.6.1 | R (M) | | R (O) | R (M) | R (M) | +| NEXT SNRpsus | 7.5.1.28.6.2 | R (M) | | R (O) | R (M) | R (M) | +| Bit allocation per subcarrier | | | | | | | +| BITSpsds | 7.5.1.29.1 | R (M) | R (O) | | | R (O) | +| FEXT BITSpsds | 7.5.1.29.1.1 | R (M) | R (O) | | | R (O) | +| NEXT BITSpsds | 7.5.1.29.1.2 | R (M) | R (O) | | | R (O) | +| BITSpsus | 7.5.1.29.2 | R (M) | | R (O) | | R (O) | +| FEXT BITSpsus | 7.5.1.29.2.1 | R (M) | | R (O) | | R (O) | +| NEXT BITSpsus | 7.5.1.29.2.2 | R (M) | | R (O) | | R (O) | +| Gain scaling per subcarrier | | | | | | | +| GAINspds | 7.5.1.29.3 | R (M) | R (O) | | | | +| FEXT GAINspds | 7.5.1.29.3.1 | R (M) | R (O) | | | | +| NEXT GAINspds | 7.5.1.29.3.2 | R (M) | R (O) | | | | +| GAINspus | 7.5.1.29.4 | R (M) | | R (O) | | | +| FEXT GAINspus | 7.5.1.29.4.1 | R (M) | | R (O) | | | +| NEXT GAINspus | 7.5.1.29.4.2 | R (M) | | R (O) | | | +| TSSpsds | 7.5.1.29.5 | R (M) | R (O) | | | | +| FEXT TSSpsds | 7.5.1.29.5.1 | R (M) | R (O) | | | | +| NEXT TSSpsds | 7.5.1.29.5.2 | R (M) | R (O) | | | | +| TSSpsus | 7.5.1.29.6 | R (M) | R (O) | | | | +| FEXT TSSpsus | 7.5.1.29.6.1 | R (M) | R (O) | | | | +| NEXT TSSpsus | 7.5.1.29.6.2 | R (M) | R (O) | | | | +| MREFPSDds | 7.5.1.29.7 | R (M) | R (O) | | | R (O) | +| MREFPSDus | 7.5.1.29.8 | R (M) | R (O) | | | R (O) | +| Trellis use | | | | | | | +| TRELLISds | 7.5.1.30 | R (M/O)
(Note) | | R (O) | R (M/O)
(Note) | R (M/O)
(Note) | + +**Table 7-28 – Line test, diagnostic and status parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | G-interface | +|---------------------------------------------------------------|---------------------|----------------|---------------|---------------|----------------|----------------| +| TRELLISus | 7.5.1.31 | R (M/O) (Note) | R (O) | | R (M/O) (Note) | R (M/O) (Note) | +| Cyclic extension | | | | | | | +| ACTUALCE | 7.5.1.32 | R (M) | | | | R (M) | +| Actual rate adaptation mode | | | | | | | +| ACT-RA-MODEds | 7.5.1.33.1 | R (O) | | | | R (O) | +| ACT-RA-MODEus | 7.5.1.33.2 | R (O) | | | | R (O) | +| Actual impulse noise protection of ROC | | | | | | | +| ACTINP-ROC-ds | 7.5.1.34.1 | R (O) | | | | R (O) | +| ACTINP-ROC-us | 7.5.1.34.2 | R (O) | | | | R (O) | +| Actual SNR margin of ROC | | | | | | | +| SNRM-ROC-ds | 7.5.1.35.1 | R (O) | | | | R (O) | +| SNRM-ROC-us | 7.5.1.35.2 | R (O) | | | | R (O) | +| Update request flags and time stamps of test parameter | | | | | | | +| UPDATE-TEST-NE | 7.5.1.36.1 | R/W (O) | | | | | +| UPDATE-TEST-FE | 7.5.1.36.2 | R/W (O) | | | | | +| STAMP-TEST-NE | 7.5.1.36.3 | R (O) | | | | | +| STAMP-TEST-FE | 7.5.1.36.4 | R (O) | | | | | +| OLR time stamps | | | | | | | +| STAMP-OLR-ds | 7.5.1.37.1 | R (O) | | | | | +| STAMP-OLR-us | 7.5.1.37.2 | R (O) | | | | | +| ITU-T G.993.5 specific (Vectoring) | | | | | | | +| XLINSCds | 7.5.1.38.1 | R (M) | | | | | +| XLINGds | 7.5.1.38.2 | R (M) | | | | | +| XLINBANDSds | 7.5.1.38.3 | R (M) | | | | | +| XLINpsds | 7.5.1.38.4 | R (M) | | | | | +| XLINSCus | 7.5.1.38.5 | R (M) | | | | | +| XLINGus | 7.5.1.38.6 | R (M) | | | | | +| XLINBANDSus | 7.5.1.38.7 | R (M) | | | | | +| XLINpsus | 7.5.1.38.8 | R (M) | | | | | +| Actual RI_POLICY | | | | | | | +| ACTRIPOLICYus | 7.5.1.40.1 | R(O) | | | | | +| ACTRIPOLICYds | 7.5.1.40.2 | R(O) | | | | | +| ATTNDR Diagnostic parameters | | | | | | | +| ATTNDR_ACT_METHOD | 7.5.1.41.1 | R(O) | | | | | +| ATTNDR_ACTINPds | 7.5.1.41.2 | R(O) | | R(O) | | | +| ATTNDR_ACTINPus | 7.5.1.41.3 | R(O) | R(O) | | | | +| ATTNDR_ACTINP_REINds | 7.5.1.41.4 | R(O) | | R(O) | | | +| ATTNDR_ACTINP_REINus | 7.5.1.41.5 | R(O) | R(O) | | | | +| ATTNDR_ACTDELAYds | 7.5.1.41.6 | R(O) | | R(O) | | | +| ATTNDR_ACTDELAYus | 7.5.1.41.7 | R(O) | R(O) | | | | + +**Table 7-28 – Line test, diagnostic and status parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | G-interface | +|--------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-------------|---------------|---------------|---------------|-------------| +| Aggregate Achievable Net Data Rate | | | | | | | +| AGGACHNDR_NE | 7.5.1.42.1 | R(O) | | | | | +| AGGACHNDR_FE | 7.5.1.42.2 | R(O) | | | R(O) | | +| Line status parameters for ITU-T G.993.5 | | | | | | | +| ACTVECTORMODE | 7.5.1.43.1 | R(O) | | | R(O) | | +| VDSL2-LR status parameter | | | | | | | +| VDSL2-LR_ACTOPTTYPE | 7.5.1.44.1 | R(M) | | | R(M) | | +| STRONGFEXT MODE status parameter | | | | | | | +| STRONGFEXT_ACTMODE | 7.5.1.45.1 | R(M) | | | R(M) | | +| Loop diagnostic parameters | | | | | | | +| Loop diagnostic mode status (LDS) | 7.5.1.46 | R(O) | | | R(O) | R(O) | +| Loop diagnostic mode results status (LDR) | 7.5.1.47 | R(O) | | | R(O) | R(O) | +| NOTE – These parameters are R (M) on the Q-interface for [ITU-T G.993.2] and R (O) for all other ITU-T Recommendations which support them. | | | | | | | + +**Table 7-29 – Support of line test, diagnostic and status parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | [ITU-T G.993.5] | +|------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| xDSL transmission system | Y | Y | Y | Y | Y | Y | | | +| VDSL2 profile | | | | | | Y | | | +| VDSL2 limit PSD mask and band plan | | | | | | Y | | | +| VDSL2 US0 PSD mask | | | | | | Y
(Annex A) | | | +| Power management state | Y | Y | Y | Y | Y | Y | | | +| RTX_USED_ds | | | | | | | Y | | +| RTX_USED_us | | | | | | | Y | | +| Initialization | | | | | | | | | +| Success/Failure cause | Y | Y | Y | Y | Y | Y | | | +| Last state transmitted downstream | | | Y | Y | Y | Y | | | +| Last state transmitted upstream | | | Y | Y | Y | Y | | | +| Attenuation | | | | | | | | | +| LATNdS | Y | Y | Y | Y | Y | Y | | | +| LATNus | Y | Y | Y | Y | Y | Y | | | +| SATNdS | | | Y | Y | Y | Y | | | + +**Table 7-29 – Support of line test, diagnostic and status parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | [ITU-T G.993.5] | +|-----------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| SATNus | | | Y | Y | Y | Y | | | +| Signal-to-noise ratio margin | | | | | | | | | +| SNRMds | Y | Y | Y | Y | Y | Y | | | +| FEXT SNRMds | | | Y | | Y | | | | +| NEXT SNRMds | | | Y | | Y | | | | +| SNRMpbds | | | | | | Y | | | +| ACTSNRMODEds | | | Y | | Y | Y | | | +| SNRMus | Y | Y | Y | Y | Y | Y | | | +| FEXT SNRMus | | | Y | | Y | | | | +| NEXT SNRMus | | | Y | | Y | | | | +| SNRMpbus | | | | | | Y | | | +| ACTSNRMODEus | | | | | | Y | | | +| Attainable data rate | | | | | | | | | +| ATTNDRds | Y | Y | Y | Y | Y | Y | | | +| FEXT ATTNDRds | | | Y | | Y | | | | +| NEXT ATTNDRds | | | Y | | Y | | | | +| ATTNDRus | Y | Y | Y | Y | Y | Y | | | +| FEXT ATTNDRus | | | Y | | Y | | | | +| NEXT ATTNDRus | | | Y | | Y | | | | +| Actual power spectral density | | | | | | | | | +| ACTPSDds | | | Y | Y | Y | | | | +| FEXT ACTPSDds | | | Y | | Y | | | | +| NEXT ACTPSDds | | | Y | | Y | | | | +| ACTPSDus | | | Y | Y | Y | | | | +| FEXT ACTPSDus | | | Y | | Y | | | | +| NEXT ACTPSDus | | | Y | | Y | | | | +| Upstream power back-off | | | | | | | | | +| UPBOKLE | | | | | | Y | | | +| UPBOKLE-R | | | | | | Y | | | +| UPBOKLE-pb | | | | | | Y | | | +| UPBOKLE-R-pb | | | | | | Y | | | +| RXTHRSHds | | | | | | Y | | | +| RXTHRSHus | | | | | | Y | | | +| ACT-AELE-MODE | | | | | | Y | | | +| Actual aggregate transmit power | | | | | | | | | +| ACTATPds | Y | Y | Y | Y | Y | Y | | | +| FEXT ACTATPds | | | Y | | Y | | | | +| NEXT ACTATPds | | | Y | | Y | | | | +| ACTATPus | Y | Y | Y | Y | Y | Y | | | +| FEXT ACTATPus | | | Y | | Y | | | | + +**Table 7-29 – Support of line test, diagnostic and status parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | [ITU-T G.993.5] | +|-----------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| NEXT ACTATPus | | | Y | | Y | | | | +| Channel characteristics per subcarrier | | | | | | | | | +| HLINSCds | | | Y | Y | Y | Y | | | +| HLINGds | | | | | | Y | | | +| HLINpsds | | | Y | Y | Y | Y | | | +| HLOGMTds | | | Y | Y | Y | Y | | | +| HLOGGds | | | | | | Y | | | +| HLOGpsds | | | Y | Y | Y | Y | | | +| HLINSCus | | | Y | Y | Y | Y | | | +| HLINGus | | | | | | Y | | | +| HLINpsus | | | Y | Y | Y | Y | | | +| HLOGMTus | | | Y | Y | Y | Y | | | +| HLOGGus | | | | | | Y | | | +| HLOGpsus | | | Y | Y | Y | Y | | | +| Quiet line noise PSD per subcarrier | | | | | | | | | +| QLNMTds | | | Y | Y | Y | Y | | | +| FEXT QLNMTds | | | Y | | Y | | | | +| NEXT QLNMTds | | | Y | | Y | | | | +| QLNGds | | | | | | Y | | | +| QLNpsds | | | Y | Y | Y | Y | | | +| FEXT QLNpsds | | | Y | | Y | | | | +| NEXT QLNpsds | | | Y | | Y | | | | +| QLNMTus | | | Y | Y | Y | Y | | | +| FEXT QLNMTus | | | Y | | Y | | | | +| NEXT QLNMTus | | | Y | | Y | | | | +| QLNGus | | | | | | Y | | | +| QLNpsus | | | Y | Y | Y | Y | | | +| FEXT QLNpsus | | | Y | | Y | | | | +| NEXT QLNpsus | | | Y | | Y | | | | +| Signal-to-noise ratio per subcarrier | | | | | | | | | +| SNRMTds | | | Y | Y | Y | Y | | | +| FEXT SNRMTds | | | Y | | Y | | | | +| NEXT SNRMTds | | | Y | | Y | | | | +| SNRGds | | | | | | Y | | | +| SNRpsds | | | Y | Y | Y | Y | | | +| FEXT SNRpsds | | | Y | | Y | | | | +| NEXT SNRpsds | | | Y | | Y | | | | +| SNRMTus | | | Y | Y | Y | Y | | | +| FEXT SNRMTus | | | Y | | Y | | | | +| NEXT SNRMTus | | | Y | | Y | | | | + +**Table 7-29 – Support of line test, diagnostic and status parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | [ITU-T G.993.5] | +|-----------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| SNRGus | | | | | | Y | | | +| SNRpsus | | | Y | Y | Y | Y | | | +| FEXT SNRpsus | | | Y | | Y | | | | +| NEXT SNRpsus | | | Y | | Y | | | | +| Bit allocation per subcarrier | | | | | | | | | +| BITSpsds | | | Y | Y | Y | Y | | | +| FEXT BITSpsds | | | Y | | Y | | | | +| NEXT BITSpsds | | | Y | | Y | | | | +| BITSpsus | | | Y | Y | Y | Y | | | +| FEXT BITSpsus | | | Y | | Y | | | | +| NEXT BITSpsus | | | Y | | Y | | | | +| Gain scaling per subcarrier | | | | | | | | | +| GAINspds | | | Y | Y | Y | Y | | | +| FEXT GAINspds | | | Y | | Y | | | | +| NEXT GAINspds | | | Y | | Y | | | | +| GAINspus | | | Y | Y | Y | Y | | | +| FEXT GAINspus | | | Y | | Y | | | | +| NEXT GAINspus | | | Y | | Y | | | | +| TSSspds | | | Y | Y | Y | | | | +| FEXT TSSspds | | | Y | | Y | | | | +| NEXT TSSspds | | | Y | | Y | | | | +| TSSspus | | | Y | Y | Y | | | | +| FEXT TSSspus | | | Y | | Y | | | | +| NEXT TSSspus | | | Y | | Y | | | | +| MREFPSDds | | | | | | Y | | | +| MREFPSDus | | | | | | Y | | | +| Trellis use | | | | | | | | | +| TRELLISds | Y | | Y | Y | Y | Y | | | +| TRELLISus | Y | | Y | Y | Y | Y | | | +| Cyclic extension | | | | | | | | | +| ACTUALCE | | | | | | Y | | | +| Actual rate adaptation mode | | | | | | | | | +| ACT-RA-MODEds | | | | | | Y | | | +| ACT-RA-MODEus | | | | | | Y | | | +| Actual impulse noise protection of ROC | | | | | | | | | +| ACTINP-ROC-ds | | | | | | Y | | | +| ACTINP-ROC-us | | | | | | Y | | | +| Actual SNR margin of ROC | | | | | | | | | +| SNRM-ROC-ds | | | | | | Y | | | +| SNRM-ROC-us | | | | | | Y | | | + +**Table 7-29 – Support of line test, diagnostic and status parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | [ITU-T G.993.5] | +|----------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Update request flags and time stamps of test parameter | | | | | | | | | +| UPDATE-TEST-NE | | | | | | Y | | | +| UPDATE-TEST-FE | | | | | | Y | | | +| STAMP-TEST-NE | | | | | | Y | | | +| STAMP-TEST-FE | | | | | | Y | | | +| OLR time stamps | | | | | | | | | +| STAMP-OLR-ds | | | | | | Y | | | +| STAMP-OLR-us | | | | | | Y | | | +| ITU-T G.993.5 specific (Vectoring) | | | | | | | | | +| XLINSCds | | | | | | | | Y | +| XLINGds | | | | | | | | Y | +| XLINBANDSds | | | | | | | | Y | +| XLINpsds | | | | | | | | Y | +| XLINSCus | | | | | | | | Y | +| XLINGus | | | | | | | | Y | +| XLINBANDSus | | | | | | | | Y | +| XLINpsus | | | | | | | | Y | +| Actual RI POLICY | | | | | | | | | +| ACTRIPOLICYus | | | | | | Y | | | +| ACTRIPOLICYds | | | | | | Y | | | +| ATTNDR Diagnostic parameters | | | | | | | | | +| ATTNDR_ACTMET HOD | | | | | | Y | | Y
(Note 1) | +| ATTNDR_ACTINPds | | | | | | Y | | Y
(Note 1) | +| ATTNDR_ACTINPus | | | | | | Y | | Y
(Note 1) | +| ATTNDR_ACTINP_ REINds | | | | | | Y | | Y
(Note 1) | +| ATTNDR_ACTINP_ REINus | | | | | | Y | | Y
(Note 1) | +| ATTNDR_ACTDEL AYds | | | | | | Y | | Y
(Note 1) | +| ATTNDR_ACTDEL AYus | | | | | | Y | | Y
(Note 1) | +| Aggregate Achievable Net Data Rate | | | | | | | | | +| AGGACHNDR_NE | | | | | | | | Y
(Note 2) | +| AGGACHNDR_FE | | | | | | | | Y
(Note 2) | +| Line status parameters G.993.5 | | | | | | | | | +| ACTVECTORMODE | | | | | | Y
(Note 3) | | Y | + +**Table 7-29 – Support of line test, diagnostic and status parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | [ITU-T G.993.5] | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| VDSL2-LR status parameter | | | | | | | | | +| VDSL2-LR_ACTOPTTYPE | | | | | | Y
(Note 5) | | Y
(Note 4) | +| STRONGFEXT MODE status parameter | | | | | | | | | +| STRONGFEXT_AC
TMODE | | | | | | | | Y
(Note 6) | +| Loop diagnostic parameters | | | | | | | | | +| Loop diagnostic mode status (LDS) | | | Y | Y | Y | Y | | | +| Loop diagnostic mode results status (LDR) | | | Y | Y | Y | Y | | | +| NOTE 1 – Those parameters apply only to ITU-T G.998.4 when used in conjunction with ITU-T G.993.2.
NOTE 2 – Those parameters apply only to ITU-T G.998.4 when ITU-T G.993.5 is selected.
NOTE 3 – This parameter applies only when Annex X or Annex Y is supported.
NOTE 4 – This parameter applies only when Annex B is supported.
NOTE 5 – This parameter applies only when Annex D is supported.
NOTE 6 – This parameter applies only when Annex A is supported. | | | | | | | | | + +**Table 7-30 – Channel test, diagnostic and status parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | G-interface | +|-------------------------------------|---------------------|---------------------|---------------|---------------|---------------|-------------| +| Actual data rate | 7.5.2.1 | R (M) | | | R (O) | R (O) | +| Previous data rate | 7.5.2.2 | R (M) | | | R (O) | R (O) | +| Actual interleaving delay | 7.5.2.3 | R (M) | | R (O) | R (O) | R (O) | +| ACTINP | 7.5.2.4 | R (M/O)
(Note 2) | | R (O) | R (O) | R (O) | +| INPREPORT | 7.5.2.5 | R (M) | | R (O) | R (O) | R (O) | +| ACTNDR | 7.5.2.8 | R (M) | | R (O) | R (O) | R (O) | +| ACTINP_REIN | 7.5.2.9 | R (M) | | R (O) | R (O) | R (O) | +| Actual framer setting | | | | | | | +| NFEC | 7.5.2.6.1 | R (M/O)
(Note 1) | | R (O) | | R (O) | +| RFEC | 7.5.2.6.2 | R (M/O)
(Note 1) | | R (O) | | R (O) | +| LSYMB | 7.5.2.6.3 | R (M/O)
(Note 1) | | R (O) | | R (O) | +| INTLVDEPTH | 7.5.2.6.4 | R (M/O)
(Note 1) | | R (O) | | R (O) | +| INTLVBLOCK | 7.5.2.6.5 | R (M) | | R (O) | | R (O) | +| RSPERDTU | 7.5.2.6.6 | R (M) | | R (O) | | R (O) | + +**Table 7-30 – Channel test, diagnostic and status parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | G-interface | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------------------|---------------|---------------|---------------|-------------| +| Actual latency path | | | | | | | +| LPTH | 7.5.2.7 | R (M/O)
(Note 1) | | R (O) | | R (O) | +| NOTE 1 – These parameters are R (M) on the Q-interface for [ITU-T G.993.2] and R (O) for all other ITU-T Recommendations, which support them.
NOTE 2 – This parameter is R (O) on the Q-interface for [ITU-T G.992.1] and R (M) for all other ITU-T Recommendations that support it. | | | | | | | + +**Table 7-31 – Support of channel test, diagnostic and status parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | +|------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Actual data rate | Y | Y | Y | Y | Y | Y | | +| Previous data rate | Y | Y | Y | Y | Y | Y | | +| Actual interleaving delay | Y | Y | Y | Y | Y | Y | | +| ACTINP | Y | | Y | Y | Y | Y | | +| INPREPORT | | | | | | Y | | +| ACTNDR | | | | | | | Y | +| ACTINP_REIN | | | | | | | Y | +| Actual framer setting | | | | | | | | +| NFEC | Y | Y | Y | Y | Y | Y | | +| RFEC | Y | Y | Y | Y | Y | Y | | +| LSYMB | Y | Y | Y | Y | Y | Y | | +| INTLVDEPTH | Y | Y | Y | Y | Y | Y | | +| INTLVBLOCK | | | | | | Y | | +| RSPERDTU | | | | | | | Y | +| Actual latency path | | | | | | | | +| LPTH | Y | Y | Y | Y | Y | Y | | + +**Table 7-32 – Packet transfer mode data path failures** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|--------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| Near-end (xTU-C) failures | | | | | | +| Out of sync (OOS) failure | 7.1.5.1.1 | R (M) | R (O) | | | +| Far-end (xTU-R) failures | | | | | | +| Far-end out of sync (OOS-FE) failure | 7.1.5.2.1 | R (M) | | R (O) | | + +**Table 7-33 – Support of packet transfer mode data path failures per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | +|--------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Near-end failures | | | | | | | +| Out of sync (OOS) failure | | | Y | | Y | Y | +| Far-end failures | | | | | | | +| Far-end out of sync (OOS-FE) failure | | | Y | | Y | Y | + +**Table 7-34 – Packet transfer mode data path performance monitoring parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|-------------------------------------------------------------------------------------------------------|---------------------|-------------|---------------|---------------|---------------| +| Near-end (xTU-C) performance monitoring counters (current and previous 15 min interval) | | | | | | +| CRC-P counter 15 min | 7.2.5.1.1 | R (M) | R (O) | | | +| CRCP-P counter 15 min | 7.2.5.1.1 | R (M) | R (O) | | | +| CV-P counter 15 min | 7.2.5.1.2 | R (M) | R (O) | | | +| CVP-P counter 15 min | 7.2.5.1.2 | R (M) | R (O) | | | +| Near-end (xTU-C) performance monitoring counters (current and previous 24 h interval) | | | | | | +| CRC-P counter 24 h | 7.2.5.1.1 | R (M) | R (O) | | | +| CRCP-P counter 24 h | 7.2.5.1.1 | R (M) | R (O) | | | +| CV-P counter 24 h | 7.2.5.1.2 | R (M) | R (O) | | | +| CVP-P counter 24 h | 7.2.5.1.2 | R (M) | R (O) | | | +| Far-end (xTU-R) performance monitoring counters (current and previous 15 min interval) | | | | | | +| CRC-PFE counter 15 min | 7.2.5.2.1 | R (M) | | R (O) | | +| CRCP-PFE counter 15 min | 7.2.5.2.1 | R (M) | | R (O) | | +| CV-PFE counter 15 min | 7.2.5.2.2 | R (M) | | R (O) | | +| CVP-PFE counter 15 min | 7.2.5.2.2 | R (M) | | R (O) | | +| Far-end (xTU-R) performance monitoring counters (current and previous 24 h interval) | | | | | | +| CRC-PFE counter 24 h | 7.2.5.2.1 | R (M) | | R (O) | | +| CRCP-PFE counter 24 h | 7.2.5.2.1 | R (M) | | R (O) | | +| CV-PFE counter 24 h | 7.2.5.2.2 | R (M) | | R (O) | | +| CVP-PFE counter 24 h | 7.2.5.2.2 | R (M) | | R (O) | | + +**Table 7-35 – Support of packet transfer mode data path performance monitoring parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | +|-----------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Near-end performance monitoring counters (current and previous 15 min interval) | | | | | | | +| CRC-P counter 15 min | | | Y | | Y | Y | +| CRCP-P counter 15 min | | | Y | | Y | Y | +| CV-P counter 15 min | | | Y | | Y | Y | +| CVP-P counter 15 min | | | Y | | Y | Y | + +**Table 7-35 – Support of packet transfer mode data path performance monitoring parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | +|---------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Near-end performance monitoring counters (current and previous 24 h interval) | | | | | | | +| CRC-P counter 24 h | | | Y | | Y | Y | +| CRCP-P counter 24 h | | | Y | | Y | Y | +| CV-P counter 24 h | | | Y | | Y | Y | +| CVP-P counter 24 h | | | Y | | Y | Y | +| Far-end performance monitoring counters (current and previous 15 min interval) | | | | | | | +| CRC-PFE counter 15 min | | | Y | | Y | Y | +| CRCP-PFE counter 15 min | | | Y | | Y | Y | +| CV-PFE counter 15 min | | | Y | | Y | Y | +| CVP-PFE counter 15 min | | | Y | | Y | Y | +| Far-end performance monitoring counters (current and previous 24 h interval) | | | | | | | +| CRC-PFE counter 24 h | | | Y | | Y | Y | +| CRCP-PFE counter 24 h | | | Y | | Y | Y | +| CV-PFE counter 24 h | | | Y | | Y | Y | +| CVP-PFE counter 24 h | | | Y | | Y | Y | + +**Table 7-36 – Packet transfer mode data path configuration profile** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T-/S-interface | +|-----------------------------------------------------------------------------|---------------------|-------------|---------------|---------------|----------------| +| Near-end (xTU-C) performance monitoring thresholds (15 min interval) | | | | | | +| CRC-P threshold 15 min | 7.3.5.1 | R/W (O) | R (O) | | | +| CRCP-P threshold 15 min | 7.3.5.1 | R/W (O) | R (O) | | | +| CV-P threshold 15 min | 7.3.5.1 | R/W (O) | R (O) | | | +| CVP-P threshold 15 min | 7.3.5.1 | R/W (O) | R (O) | | | +| Near-end (xTU-C) performance monitoring thresholds (24 h interval) | | | | | | +| CRC-P threshold 24 h | 7.3.5.1 | R/W (O) | R (O) | | | +| CRCP-P threshold 24 h | 7.3.5.1 | R/W (O) | R (O) | | | +| CV-P threshold 24 h | 7.3.5.1 | R/W (O) | R (O) | | | +| CVP-P threshold 24 h | 7.3.5.1 | R/W (O) | R (O) | | | +| Far-end (xTU-R) performance monitoring thresholds (15 min interval) | | | | | | +| CRC-PFE threshold 15 min | 7.3.5.1 | R/W (O) | R (O) | | | +| CRCP-PFE threshold 15 min | 7.3.5.1 | R/W (O) | R (O) | | | +| CV-PFE threshold 15 min | 7.3.5.1 | R/W (O) | R (O) | | | +| CVP-PFE threshold 15 min | 7.3.5.1 | R/W (O) | R (O) | | | +| Far-end (xTU-R) performance monitoring thresholds (24 h interval) | | | | | | +| CRC-PFE threshold 24 h | 7.3.5.1 | R/W (O) | R (O) | | | +| CRCP-PFE threshold 24 h | 7.3.5.1 | R/W (O) | R (O) | | | +| CV-PFE threshold 24 h | 7.3.5.1 | R/W (O) | R (O) | | | +| CVP-PFE threshold 24 h | 7.3.5.1 | R/W (O) | R (O) | | | + +**Table 7-37 – Support packet transfer mode data path configuration parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | +|----------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Near-end performance monitoring thresholds (15 min interval) | | | | | | | +| CRC-P threshold 15 min | | | Y | | Y | Y | +| CRCP-P threshold 15 min | | | Y | | Y | Y | +| CV-P threshold 15 min | | | Y | | Y | Y | +| CVP-P threshold 15 min | | | Y | | Y | Y | +| Near-end performance monitoring thresholds (24 h interval) | | | | | | | +| CRC-P threshold 24 h | | | Y | | Y | Y | +| CRCP-P threshold 24 h | | | Y | | Y | Y | +| CV-P threshold 24 h | | | Y | | Y | Y | +| CVP-P threshold 24 h | | | Y | | Y | Y | +| Far-end performance monitoring thresholds (15 min interval) | | | | | | | +| CRC-PFE threshold 15 min | | | Y | | Y | Y | +| CRCP-PFE threshold 15 min | | | Y | | Y | Y | +| CV-PFE threshold 15 min | | | Y | | Y | Y | +| CVP-PFE threshold 15 min | | | Y | | Y | Y | +| Far-end performance monitoring thresholds (24 h interval) | | | | | | | +| CRC-PFE threshold 24 h | | | Y | | Y | Y | +| CRCP-PFE threshold 24 h | | | Y | | Y | Y | +| CV-PFE threshold 24 h | | | Y | | Y | Y | +| CVP-PFE threshold 24 h | | | Y | | Y | Y | + +**Table 7-38 – Data gathering configuration profile** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | +|-----------------------------------|---------------------|-------------|---------------|---------------|---------------| +| Data gathering | | | | | | +| LOGGING_DEPTH_EVENT_PERCENTAGE_Oi | 7.3.6.1 | R/W (O) | | | | +| LOGGING_DEPTH_EVENT_PERCENTAGE_Ri | 7.3.6.2 | R/W (O) | | R/W (O) | | +| LOGGING_DEPTH_REPORTING_O | 7.3.6.3 | R/W (O) | | | | +| LOGGING_DEPTH_REPORTING_R | 7.3.6.4 | R/W (O) | | R/W (O) | | +| LOGGING_REPORT_NEWER_FIRST | 7.3.6.5 | R/W (O) | | R/W (O) | | + +**Table 7-39 – Support of data gathering configuration parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | [ITU-T G.993.5] | +|-----------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Data gathering | | | | | | | | | +| LOGGING_DEPTH_EVENT_PERCENTAGE_Oi | | | | | | Y | | | +| LOGGING_DEPTH_EVENT_PERCENTAGE_Ri | | | | | | Y | | | +| LOGGING_DEPTH_REPORTING_O | | | | | | Y | | | +| LOGGING_DEPTH_REPORTING_R | | | | | | Y | | | +| LOGGING_REPORT_NEWER_FIRST | | | | | | Y | | | + +**Table 7-40 – Data gathering reporting parameters** + +| Category/element | Specified in clause | Q-interface | U-C interface | U-R interface | T/S interface | G-interface | +|-------------------------------|---------------------|-------------|---------------|---------------|---------------|-------------| +| LOGGING_DEPTH_O | 7.5.3.1 | R (O) | | | | | +| LOGGING_DEPTH_R | 7.5.3.2 | R (O) | | R (O) | | R (O) | +| ACT_logging_depth_reporting_O | 7.5.3.3 | R (O) | | | | | +| ACT_logging_depth_reporting_R | 7.5.3.4 | R (O) | | | | R (O) | +| EVENT_TRACE_BUFFER_O | 7.5.3.5 | R (O) | | | | | +| EVENT_TRACE_BUFFER_R | 7.5.3.6 | R (O) | | R (O) | | R (O) | + +**Table 7-41 – Support of data gathering reporting parameters per Recommendation** + +| Category/element | [ITU-T G.992.1] | [ITU-T G.992.2] | [ITU-T G.992.3] | [ITU-T G.992.4] | [ITU-T G.992.5] | [ITU-T G.993.2] | [ITU-T G.998.4] | [ITU-T G.993.5] | +|-------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| LOGGING_DEPTH_O | | | | | | Y | | | +| LOGGING_DEPTH_R | | | | | | Y | | | +| ACT_logging_depth_reporting_O | | | | | | Y | | | +| ACT_logging_depth_reporting_R | | | | | | Y | | | +| EVENT_TRACE_BUFFER_O | | | | | | Y | | | +| EVENT_TRACE_BUFFER_R | | | | | | Y | | | + +# Appendix I + +## Processing examples + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Illustration of transmitter processing + +``` +#define INIT 0xFFFF +#define FLAG 0x7E +#define ESC 0x7D +#define INV 0x20 +#define GENPOL 0x8408 + +unsigned char msg[1024], temp; /* 8 bit unsigned char */ +unsigned short int crc; /* 16 bit unsigned integer */ +int N, j, msglen; + +{ + crc = INIT; + msg[0] = 0xFF; + crc = update_crc(msg[0], crc); + msg[1] = 0x03; + crc = update_crc(msg[1], crc); + N = 2; + j = 0; + while (j < msglen) + { + temp = xmit_msg_byte(j++); + crc = update_crc(temp, crc); + if ( (temp == FLAG) || (temp == ESC) ) + { + msg[N] = ESC; + msg[N+1] = temp ^ INV; + N = N + 2; + } + else + { + msg[N] = temp; + N = N + 1; + } + } + crc = ~crc; + msg[N] = crc & 0x00FF; + msg[N+1] = (crc >> 8) & 0x00FF; + xmit_msg(); +} + +unsigned short int update_crc(unsigned char new_byte, unsigned short int +crc_reg) +{ + int i; + crc_reg = crc_reg ^ new_byte; + for (i=0; i<8; i++) + if (crc_reg & 0x0001) + crc_reg = (crc_reg>>1) ^ GENPOL; + else + crc_reg = crc_reg >> 1; + return (crc_reg); +} +``` + +## I.2 Illustration of receiver processing + +![](08f5fade508b5badd6175fa5e482132f_img.jpg) + +word +crc, rxbyte, i, N +byte +msg[1024] + +FLAG 0x7E +ESC 0x7D +INV 0x20 +GENPOL 0x8408 +INIT 0xFFFF +GOOD 0xF0B8 + +ESC^INV +FLAG^INV + +``` + +graph TD + Start(( )) --> Init1[rxbyte = rxbyte ^ INV;] + Init1 --> CRC[ + crc = crc ^ rxbyte; + for (i=0; i<8; i++) + if (crc & 0x0001) + crc = (crc>>1) ^ GENPOL; + else crc = crc>>1; +] + CRC --> MsgN[ + msg[N] = rxbyte; + N=N+1; +] + MsgN --> GetByte1[rxbyte = getbyte();] + GetByte1 -- ESC --> GetByte2[rxbyte = getbyte();] + GetByte1 -- FLAG --> GoodCheck[ + if ((crc==GOOD) && (N>=6)) + { + N = N - 2; + deliver (msg, N); + } +] + GetByte1 -- other --> GetByte1 + GetByte2 -- other --> GetByte2 + GetByte2 -- FLAG --> Init2[ + crc = INIT; + N = 0; +] + Init2 -- Initialize --> Init1 + Init2 --> GetByte3[rxbyte = getbyte();] + GetByte3 -- other --> GetByte3 + GetByte3 -- FLAG --> Init2 + +``` + +N +msg[0] message length +msg[1] address field (0xFF) +msg[2] control field (0x03) +msg[3] protocol identifier +msg[4..N-1] encapsulated message + +G.997.1(09)\_Fl.2 + +## Appendix II + +### Downstream power back-off + +(This appendix does not form an integral part of this Recommendation.) + +#### II.1 Introduction + +Figure II.1 shows a physical layer reference model that illustrates the application of DPBO. The objective of the method is to reduce the downstream power injected by the xTU-C at a flexibility point (remote node, cabinet) to the same level as would be expected to be found at the same point in the cable if the signal was injected at the exchange. So the degree of DPBO is controlled by a frequency dependent function of the electrical length of the cable (E-side length) from the exchange to the flexibility point. The method applies power back-off over a range of frequencies, but excludes higher frequencies that the exchange-hosted systems cannot reliably exploit. + +![Figure II.1 – Physical layer reference model. The diagram shows a physical layer reference model. On the left, a dashed box labeled 'Exchange' contains an 'LT' (Line Terminal) block. A solid line representing the cable extends from the 'LT' to a second dashed box labeled 'Flexibility point'. Above this cable segment, a double-headed arrow is labeled 'E-side length'. Inside the 'Flexibility point' box, the cable connects to another 'LT' block. From this 'LT' block, two solid lines extend to the right, each leading to an 'NT' (Network Terminal) block. The top 'NT' block is labeled 'Customer 1' and the bottom 'NT' block is labeled 'Customer 2'. In the bottom right corner of the diagram area, the text 'G.997.1(09)_FII.1' is present.](9d47fe89bc71acebde670ea760ee6ffb_img.jpg) + +Figure II.1 – Physical layer reference model. The diagram shows a physical layer reference model. On the left, a dashed box labeled 'Exchange' contains an 'LT' (Line Terminal) block. A solid line representing the cable extends from the 'LT' to a second dashed box labeled 'Flexibility point'. Above this cable segment, a double-headed arrow is labeled 'E-side length'. Inside the 'Flexibility point' box, the cable connects to another 'LT' block. From this 'LT' block, two solid lines extend to the right, each leading to an 'NT' (Network Terminal) block. The top 'NT' block is labeled 'Customer 1' and the bottom 'NT' block is labeled 'Customer 2'. In the bottom right corner of the diagram area, the text 'G.997.1(09)\_FII.1' is present. + +**Figure II.1 – Physical layer reference model** + +This method does not exclude other methods of DPBO, using direct configuration of the parameter PSDMASKds. + +A three parameters model of the loop insertion loss has been found to be satisfactory, i.e., $H(f, L) = (a + b \times \sqrt{f} + c \times f) \times L$ dB where $L$ is a metric of electrical length of the E-side cable. Using this model, it has been found possible to track the insertion loss of the predominant gauges of E-side copper pairs with one set of parameters. + +The resulting PSD mask for cabinet-based transmitters is a function of a number of parameters that are set by the NMS. The DPBO control information flows for generating the PSD mask are illustrated in Figure II.2. The modification of the downstream PSD mask is done in the ME of the access node. Without DPBO, the mask (PSDMASKds) used at the cabinet is the appropriate remote PSD mask specified in the relevant xDSL standard. With DPBO, a modified PSDMASKds is generated as a function of the E-side electrical length, maximum useful signal, the cable model parameters and the exchange PSD mask. Additionally, the modified PSD mask is subject to a low frequency override PSD mask that applies independently of DPBOESEL. + +![Flowchart of downstream power back-off control information flows. It shows inputs from 'Per customer' (E-side electrical length) and 'Network wide' (Cable model MUS, Exchange PSD mask, Remote PSD mask) converging at a junction. The junction feeds into 'MIB', which then feeds into 'ITU-T G.997.1'. 'ITU-T G.997.1' feeds into 'xTU-C'. A box labeled 'PSDMASKds' receives input from 'Remote PSD mask' and feeds into the junction. A box labeled 'Modified PSDMASKds' receives input from 'ITU-T G.997.1' and feeds into 'xTU-C'. The diagram is labeled 'G.997.1(19)_FII.2'.](fc7c83167c4e9e614f40e52b39ef735d_img.jpg) + +Flowchart of downstream power back-off control information flows. It shows inputs from 'Per customer' (E-side electrical length) and 'Network wide' (Cable model MUS, Exchange PSD mask, Remote PSD mask) converging at a junction. The junction feeds into 'MIB', which then feeds into 'ITU-T G.997.1'. 'ITU-T G.997.1' feeds into 'xTU-C'. A box labeled 'PSDMASKds' receives input from 'Remote PSD mask' and feeds into the junction. A box labeled 'Modified PSDMASKds' receives input from 'ITU-T G.997.1' and feeds into 'xTU-C'. The diagram is labeled 'G.997.1(19)\_FII.2'. + +**Figure II.2 – Downstream power back-off control information flows** + +## II.2 Description of the downstream power back-off method + +The configuration parameters of the DPBO defined in this Recommendation are summarized in Table II.1. + +**Table II.1 – Downstream power back-off configuration parameters** + +| Parameter | Description | +|---------------|--------------------------------------------------------------------| +| DPBOEPSD | Exchange site maximum PSD mask | +| DPBOPSDMASKds | Overall maximum PSD mask limit when DPBO is applied | +| DPBOESEL | Electrical length of exchange to cabinet cable | +| DPBOESCMA | E-side cable model parameter A | +| DPBOESCMB | E-side cable model parameter B | +| DPBOESCMC | E-side cable model parameter C | +| DPBOMUS | Assumed minimum usable PSD mask of exchange signals at remote site | +| DPBOFMIN | Lower bound on the DPBO frequency span | +| DPBOFMAX | Upper bound on the DPBO frequency span | +| DPBOLFO | Low frequency PSD mask override | + +If there exists a violation of monotonic frequency sequence in the set of breakpoints $\text{PSDMASKds}(t_i, \text{PSD}_i)$ , such that $t_d > t_{d+1}$ , then the first step is to derive $\text{DPBOPSDMASKds}$ and $\text{DPBOLFO}$ from the set of breakpoints $\text{PSDMASKds}$ where: + +$$\text{DPBOPSDMASKds}(t_i, \text{PSD}_i) = \text{PSDMASKds}(t_i, \text{PSD}_i), \quad 0 < i \leq d$$ + +$$\text{DPBOLFO}(t_i, \text{PSD}_i) = \text{PSDMASKds}(t_i, \text{PSD}_i), \quad d < i \leq 32$$ + +If the frequency sequence in the set of breakpoints $\text{PSDMASKds}(t_i, \text{PSD}_i)$ is monotonic, then $\text{DPBOLFO}$ is assumed to be everywhere $\leq -91.5 \text{ dBm/Hz}$ . + +The next step in generating the backed-off transmit PSD mask is to generate the predicted downstream exchange signal PSD mask ( $\text{PEPSD}(f)$ ) at the remote site: + +$$\text{PEPSD}(f) = \text{DPBOEPD}(f) - \left( \text{DPBOESCMA} + \text{DPBOESCMB} \cdot \sqrt{f} + \text{DPBOESCMC} \cdot f \right) \cdot \text{DPBOESEL}$$ + +The assumed MUF from the exchange is the highest frequency $f$ such that: + +$$\text{PEPSD}(f) > \text{DPBOMUS}$$ + +Applying the DPBO mechanism directly will result in a practically difficult brick wall transition at the MUF. This is alleviated by introducing a minimum PSD mask between DPBOFMIN and DPBOFMAX with a smoother transition at the MUF and an overall noise floor of $-91.5$ dBm on the low frequency. The minimum PSD mask also implements the low frequency PSD mask override by taking the maximum of the DPBOLFO and the noise floor. The minimum PSD mask (DPBOMPSD( $f$ )) is therefore defined between DPBOFMIN and $F_1 = \min(\text{DPBOFMAX}, \text{MUF})$ as: + +$$\text{DPBOMPSD}(f) = \begin{cases} \max[\text{DPBOLFO}(f), -91.5] \text{ dBm/Hz} & \text{for } f \leq F_1 - 175 \text{ kHz} \\ \max[\text{DPBOLFO}(f), \frac{11.5}{175}(f - F_1) - 80] \text{ dBm/Hz} & \text{for } F_1 - 175 \text{ kHz} < f < F_1 \end{cases}$$ + +where $f$ is expressed in kilohertz. + +DPBO is then applied to PSDMASKds( $f$ ) in this band to create the overall downstream PSD mask for equipment at the remote flexibility point. + +$$\text{RESULTMASKds}(f) = \begin{cases} \max[\min(\text{DPBOPSDMASKds}(f), \text{PEPSD}(f)), \text{DPBOMPSD}(f)] & \text{DPBOFMIN} \leq f \leq F_1 \\ \text{DPBOPSDMASKds}(f) & \text{Otherwise} \end{cases}$$ + +Figure II.3 shows the PSD mask and the resultant mask with DPBO applied. + +![Figure II.3: Creation of the mask with downstream power back-off. The graph plots PSD level (Y-axis) against Frequency (X-axis). The Y-axis has labels for -91.5 dBm/Hz and DPBOMUS. The X-axis has a label for F1. A shaded region represents the 'Resultant PSD mask with DPBO applied'. A solid line represents the 'Assumed Exchange PSD mask'. A dashed line represents the 'Predicted Attenuated Exchange PSD mask'. A dash-dot line represents the 'Maximum Remote PSD mask'. A dotted line represents the 'Low frequency PSD mask override'. A circle highlights a detail of the resultant mask near F1, showing a 175kHz transition width. The 'DPBO Span' is indicated by a double-headed arrow between two vertical dashed lines. The text 'G.997.1(09)_FII.3' is in the bottom right corner.](a57d566566ac81d4832e5000924f5e84_img.jpg) + +Legend: + +- Assumed Exchange PSD mask +- - - - Predicted Attenuated Exchange PSD mask +- . - . Maximum Remote PSD mask +- . - . Low frequency PSD mask override +- ▨ Resultant PSD mask with DPBO applied + +Figure II.3: Creation of the mask with downstream power back-off. The graph plots PSD level (Y-axis) against Frequency (X-axis). The Y-axis has labels for -91.5 dBm/Hz and DPBOMUS. The X-axis has a label for F1. A shaded region represents the 'Resultant PSD mask with DPBO applied'. A solid line represents the 'Assumed Exchange PSD mask'. A dashed line represents the 'Predicted Attenuated Exchange PSD mask'. A dash-dot line represents the 'Maximum Remote PSD mask'. A dotted line represents the 'Low frequency PSD mask override'. A circle highlights a detail of the resultant mask near F1, showing a 175kHz transition width. The 'DPBO Span' is indicated by a double-headed arrow between two vertical dashed lines. The text 'G.997.1(09)\_FII.3' is in the bottom right corner. + +Figure II.3 – Creation of the mask with downstream power back-off + +## Bibliography + +- [b-ITU-T I.361] Recommendation ITU-T I.361 (1999), *B-ISDN ATM layer specification*. +- [b-ITU-T I.432.x] Recommendations ITU-T I.432.x-series, *B-ISDN user-network interface – Physical layer specification*. +- [b-ITU-T M.2100] Recommendation ITU-T M.2100 (2003), *Performance limits for bringing-into-service and maintenance of international multi-operator PDH paths and connections*. +- [b-ITU-T M.2101] Recommendation ITU-T M.2101 (2003), *Performance limits for bringing-into-service and maintenance of international multi-operator SDH paths and multiplex sections*. +- [b-ITU-T M.2120] Recommendation ITU-T M.2120 (2002), *International multi-operator paths, sections and transmission systems fault detection and localization procedures*. +- [b-ATIS 0600413] ATIS 0600413-2009, *Network to customer installation interfaces – Asymmetric digital subscriber line (ADSL) metallic interface*. +- [b-ETSI TS 101 388] ETSI TS 101 388 V1.4.1 (2007-08), *Access terminals transmission and multiplexing (ATTM); Access transmission systems on metallic access cables; Asymmetric digital subscriber line (ADSL) – European specific requirements [Recommendation ITU-T G.992.1 modified]*. +- [b-IEEE 802.3] IEEE Std 802.3-2018, *IEEE Standard for Ethernet*. +- [b-IETF RFC 1700] IETF RFC 1700 (1994), *Assigned numbers*. +- [b-IETF RFC 2233] IETF RFC 2233 (1997), *The interfaces group MIB using SMIPv2*. +- [b-IETF RFC 2662] IETF RFC 2662 (1999), *Definitions of managed objects for the ADSL lines*. +- [b-IETF RFC 3440] IETF RFC 3440 (2002), *Definitions of extension managed objects for asymmetric digital subscriber lines*. +- [b-ISO/IEC 13239] ISO/IEC 13239:2002, *Information technology – Telecommunications and information exchange between systems – High-level data link control (HDLC) procedures*. + + + + + +## 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.9972-201006-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/G/T-REC-G.9972-201006-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..401f8e3a2fbf5d52c9ba35bfaf7ee5ca44e9e1d4 --- /dev/null +++ b/marked/G/T-REC-G.9972-201006-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c27d19087aa0e99d32c00be9648c13ffb4b3ed004b74b7ac04603577a28b0b5 +size 25378 diff --git a/marked/G/T-REC-G.9972-201006-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg b/marked/G/T-REC-G.9972-201006-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5bed2a123e6b70d02459f1cfaf5765e479d1f4a --- /dev/null +++ b/marked/G/T-REC-G.9972-201006-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3cfe10628a09a6fc9aa090e24a9a3f40443ff9b69c73270574f22922506f9dc +size 23668 diff --git a/marked/G/T-REC-G.9972-201006-I_PDF-E/239211fa511b4ffa685b54b5132ec927_img.jpg b/marked/G/T-REC-G.9972-201006-I_PDF-E/239211fa511b4ffa685b54b5132ec927_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28aa5605af224d68b7f40bd30751485fe83c6272 --- /dev/null +++ b/marked/G/T-REC-G.9972-201006-I_PDF-E/239211fa511b4ffa685b54b5132ec927_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ba2411af0d483ece418ba2c52cfa809e645252c51727879c456cce8e25a0565 +size 39406 diff --git a/marked/G/T-REC-G.9972-201006-I_PDF-E/29f586959675cafdf81cf934954908eb_img.jpg b/marked/G/T-REC-G.9972-201006-I_PDF-E/29f586959675cafdf81cf934954908eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e796a2f5487e14ca274d0d8766e98e47f6864e0 --- /dev/null +++ b/marked/G/T-REC-G.9972-201006-I_PDF-E/29f586959675cafdf81cf934954908eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f8572d6e3a52866c78aee0beef99d41b7ada736b6f371eee9ec39b930e5b6d1 +size 62020 diff --git a/marked/G/T-REC-G.9972-201006-I_PDF-E/58de972a8c79c238b69cbeeafcc8d5fb_img.jpg b/marked/G/T-REC-G.9972-201006-I_PDF-E/58de972a8c79c238b69cbeeafcc8d5fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fef543e7be0e5a430f3a64d54eb2dfbab55cac01 --- /dev/null +++ b/marked/G/T-REC-G.9972-201006-I_PDF-E/58de972a8c79c238b69cbeeafcc8d5fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7b4212320ee699468480adc19d1bb2e89fec403a14cd0a72d73de2f81747ca3 +size 51560 diff --git a/marked/G/T-REC-G.9972-201006-I_PDF-E/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/G/T-REC-G.9972-201006-I_PDF-E/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79bf3900332a816f280d5eda7d5a76a07b4185da --- /dev/null +++ b/marked/G/T-REC-G.9972-201006-I_PDF-E/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9acaa844d58b1ec90c78342747c6f17aea64a9ca4dc9fa83bf197ef64a9977bb +size 90534 diff --git a/marked/G/T-REC-G.9972-201006-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/G/T-REC-G.9972-201006-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dad02182b30e94f721c7f50726f60641c96df521 --- /dev/null +++ b/marked/G/T-REC-G.9972-201006-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45bf920a7798c0111eed0c87f3f277105f8935167814eaedd42f96a3f983bba0 +size 4024 diff --git a/marked/G/T-REC-G.9972-201006-I_PDF-E/a430996a9e8993deb0c6b25da234744b_img.jpg b/marked/G/T-REC-G.9972-201006-I_PDF-E/a430996a9e8993deb0c6b25da234744b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f5166ac51d764d7022c533ab437a85b6fa69b57 --- /dev/null +++ b/marked/G/T-REC-G.9972-201006-I_PDF-E/a430996a9e8993deb0c6b25da234744b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b2597af6b3f83532e329144a6703092a8adc2c9550793403e7712a447017a43 +size 28073 diff --git a/marked/G/T-REC-G.9972-201006-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg b/marked/G/T-REC-G.9972-201006-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0039e8604df307e3958bbdf9483e4e14d189ab01 --- /dev/null +++ b/marked/G/T-REC-G.9972-201006-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e908eaef41010509f338e2cf9a6941b110d82b09260a31a95776ec0f12d7553 +size 54722 diff --git a/marked/G/T-REC-G.9972-201006-I_PDF-E/b38d03866fe3a710ce4ef0d3f0db86aa_img.jpg b/marked/G/T-REC-G.9972-201006-I_PDF-E/b38d03866fe3a710ce4ef0d3f0db86aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6015e37a2a8a05dde8abbb72705bcf74721ea465 --- /dev/null +++ b/marked/G/T-REC-G.9972-201006-I_PDF-E/b38d03866fe3a710ce4ef0d3f0db86aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c1e268c18024ca56d89989dd721b77e6b8463e03a0eb85d8101f8d2d6824927 +size 41957 diff --git a/marked/G/T-REC-G.9972-201006-I_PDF-E/ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg b/marked/G/T-REC-G.9972-201006-I_PDF-E/ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8f65d1fc0388cbd258656228b65db2169571ec2 --- /dev/null +++ b/marked/G/T-REC-G.9972-201006-I_PDF-E/ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2330cb2d480fa287ec73e1846559f62f4e2c92aa3d388657b18fb7d5dd97abd9 +size 23711 diff --git a/marked/G/T-REC-G.9972-201006-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/G/T-REC-G.9972-201006-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92eaf93775fa65fefc62abd372d16471cd408a59 --- /dev/null +++ b/marked/G/T-REC-G.9972-201006-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14ae3d55d2b7aeb7d8f9fb204124f3a74578a042ce170492604d313ebb2f41e5 +size 87791 diff --git a/marked/G/T-REC-G.9972-201006-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/G/T-REC-G.9972-201006-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dec0cff73ae1ae0e3c2d53bef11cf092ef9585f --- /dev/null +++ b/marked/G/T-REC-G.9972-201006-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e71be2c8a5b01c0afd4e1816995c801071486404765a4730283eeae00bc0fcf +size 26039 diff --git a/marked/G/T-REC-G.9978-201811-I_PDF-E/raw.md b/marked/G/T-REC-G.9978-201811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..40ab40468d361ee576260022daaf2856fbee6ad2 --- /dev/null +++ b/marked/G/T-REC-G.9978-201811-I_PDF-E/raw.md @@ -0,0 +1,2479 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.9978** + +(11/2018) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Access networks – In premises networks + +--- + +**Secure admission in a G.hn network** + +Recommendation ITU-T G.9978 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in blue. + +ITU logo + +International +Telecommunication +Union + +# 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.9978 + +# Secure admission in a G.hn network + +## Summary + +Recommendation ITU-T G.9978 specifies the various secure admission methods for a node to enter a G.hn domain, including media access control (MAC) authorization-based secure admission, generic pairing, auto-pairing and passphrase-based secure admission. This latest revision includes new use cases. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.9978 | 2018-02-09 | 15 | 11.1002/1000/13341 | +| 2.0 | ITU-T G.9978 | 2018-11-29 | 15 | 11.1002/1000/13779 | + +## Keywords + +G.hn, pairing, push button, secure admission, security. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2019 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 3 | +| 6 Secure admission methods..... | 4 | +| 6.1 Media access control authorization-based secure admission procedure ..... | 5 | +| 6.2 Admission through generic pairing mechanism ..... | 19 | +| 6.3 Secure admission through a passphrase-based procedure ..... | 52 | +| 6.4 Admission through the auto-pairing mechanism..... | 56 | +| 7 Secure admission methods selection ..... | 60 | +| 7.1 Information on secure supported admission methods ..... | 60 | +| 7.2 Interoperability between secure admission methods..... | 61 | +| 8 Management message OPCODEs ..... | 62 | +| Bibliography..... | 63 | + + + +# Recommendation ITU-T G.9978 + +## Secure admission in a G.hn network + +# 1 Scope + +This Recommendation specifies secure admission methods that are needed for a G.hn node to establish a secure domain (SD) and admit other G.hn nodes to the SD. These methods include media access control (MAC) authorization-based Nsecure admission, push button pairing, auto-pairing and passphrase-based secure admission. The Recommendation also specifies the mechanism for selecting appropriate secure admission methods and addresses interactions between these different secure admission methods. + +# 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.9961] Recommendation ITU-T G.9961 (2015), *Unified high-speed wireline-based home networking transceivers – Data link layer specification*. + +[ISO/IEC 8859-1] International Standard ISO/IEC 8859-1:1998, *Information technology – 8-bit single-byte coded graphic character sets – Part 1: Latin alphabet No. 1*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 auto-pairing:** A pairing operation that starts automatically when an unconnected node is powered on. + +**3.2.2 default non-secure domain name:** The domain name specified as the default to be used in a non-secure domain. + +**3.2.3 generic pairing:** Any pairing operation different from auto-pairing. Generic pairing can be started with push buttons or any other mechanism (console command, messages, web interface, etc.) that generates push events. + +**3.2.4 joining node:** A non-secure node that is in the process of either creating a secure domain or entering an already existing secure domain. + +**3.2.5 MAC authorization-based secure admission:** Authentication method for admitting nodes in a secure domain that is based on the comparison of the registration identifier [REGID; media access control (MAC) address] of the registering node with a list of authorized MAC addresses. + +**3.2.6 multi-node pairing:** Pairing procedure that allows several non-secure nodes to join a secure domain during a single pairing window. + +- 3.2.7 non-secure domain (NSD):** Domain where communication between nodes is not encrypted. +- 3.2.8 non-secure domain name:** The domain name used in a non-secure domain. +- 3.2.9 non-secure node:** A node that has not been authenticated. It can be connected to other nodes, with non-encrypted traffic, or not connected to any node, i.e., unconnected. +- 3.2.10 non-secure active node:** A non-secure node that can communicate with other nodes using non-encrypted traffic. +- 3.2.11 pairing window:** The time during which non-secure nodes can be authenticated in order to be admitted to a secure domain during an auto-pairing or generic pairing procedure. +- 3.2.12 pairing window duration:** The length of time that the pairing window remains open. +- 3.2.13 passphrase:** Human-readable pattern that is used by some standard admission methods to generate the G.hn password. +- 3.2.14 password (PW):** A standard 96-bit parameter that is used in the G.hn authentication procedure. +- 3.2.15 PUSH event:** Event used to trigger a pairing or unpairing operation. +NOTE – See PUSH-P event and PUSH-R event. +- 3.2.16 PUSH-P event:** Event used to trigger the start of a pairing operation. +- 3.2.17 PUSH-R event:** Event used to trigger an unpairing operation to remove a node from a secure domain and return it to the unconnected state. +- 3.2.18 remote authenticator (RA):** Optional function that resides outside the G.hn domain and that may perform some security controller (SC) functions and may control the operation of the SC (e.g., decide which nodes can be authenticated based on pre-specified criteria). +- 3.2.19 secure admission procedure:** Process to establish a secure domain or to include a new node in a secure domain through a standard admission method. +- 3.2.20 secure domain:** Domain where communication between nodes is encrypted. +- 3.2.21 secure domain master:** The domain master of a secure domain. +- 3.2.22 secure domain name (SDN):** The domain name of a secure domain. It shall be different from the default non-secure domain name and the unconnected domain name. +- 3.2.23 secure endpoint:** Any of the endpoints of a secure domain. +- 3.2.24 secure node:** Node that is part of a secure domain. +- 3.2.25 security controller (SC):** Function of a node that manages authentication and key management (AKM) procedures within a G.hn domain. +- 3.2.26 single-node pairing:** Pairing procedure allowing the limitation of the inclusion of new non-secure nodes in a secure domain to one for each run of the procedure. The pairing window closes when one node is authenticated and joins the secure domain. +- 3.2.27 successful pairing operation:** A pairing operation during which a node either creates or joins a secure domain consisting of at least two nodes. +- 3.2.28 user interface (UI) node:** The node connected to a device that allows the user to select which nodes are added or removed to or from a secure domain in a media access control (MAC) authorization operation. It can be selected by using any type of user interface, graphical or not. +- 3.2.29 unconnected domain name:** The domain name used in an unconnected node. It shall be set to "UNCONNECTED". +- 3.2.30 unconnected node:** A non-secure node that does not belong to any domain and that is not connected to any other node. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------------------| +| AE | Application Entity | +| AKM | Authentication and Key Management | +| ASCII | American Standard Code for Information Exchange | +| DM | Domain Master | +| DN | Domain Name | +| EP | Endpoint | +| GUI | Graphical User Interface | +| LSB | Least Significant Bit | +| MA | Medium Access | +| MAC | Media Access Control | +| MAP | Medium Access Plan | +| MAP-D | Medium Access Plan-Default | +| MMPL | Management Message Parameter List | +| MPDU | Medium access control Protocol Data Unit | +| MSB | Most Significant Bit | +| NMK | Network Membership Key | +| NSD | Non-Secure Domain | +| PC | Personal Computer | +| PSDM | Permanent Secure Domain Master | +| PW | Password | +| RA | Remote Authenticator | +| REGID | Registration Identifier | +| RMAP | Relayed Medium Access Plan | +| SC | Security Controller | +| SD | Secure Domain | +| SDN | Secure Domain Name | +| TMPDM | Temporal Domain Master | +| TV | Television | +| TXOP | Transmission Opportunity | +| UI | User Interface | + +# 5 Conventions + +None. + +# 6 Secure admission methods + +An [ITU-T G.9961] domain may operate in either non-secure mode or secure mode. Nodes may also be in unconnected state, with the domain name (DN) set as "UNCONNECTED" and not belonging to any domain. + +The DN of a non-secure domain (NSD) shall be the default non-secure domain name and the communication is not encrypted. In an NSD, nodes do not need to go through an authentication and key management (AKM) procedure to be admitted (security mode set to zero in Table 8-17 of [ITU-T G.9961]). The DN of all nodes in a secure domain (SD) shall be different from the default NSD and also different from the unconnected DN, and the communication shall be encrypted. In an SD, all the nodes shall go through an AKM procedure to be admitted (security mode set to one in Table 8-17 of [ITU-T G.9961]). The nodes of an SD are configured with a secure domain name (SDN) and password (PW). A PW is a 96-bit parameter as described in clause 9.2.2.2.2 of [ITU-T G.9961] that is used in the G.hn authentication procedure as described in clause 9.2.2.1 of [ITU-T G.9961]. Each joining node that is configured with this SDN and PW can register and be authenticated by the SD. The configured PW enables the registering node to successfully authenticate to the SD. The authentication procedure provides the authenticated node with encryption keys to encrypt or decrypt the data traffic. + +The default non-secure domain name is beyond the scope of the Recommendation. SDNs are also beyond the scope of this Recommendation, but they shall not be an empty string and they shall not be the same as the default non-secure domain name or the unconnected domain name. DNs shall be $\leq 32$ characters excluding the NULL string termination character (see Note 1 to Table 8-74 of [ITU-T G.9961]). + +NOTE – HomeGrid Forum uses "HomeGrid" as the default non-secure domain name [b-HomeGrid]. + +A secure node may be configured with an SDN and PW directly by the operator or user, automatically configured during a pairing procedure as specified in clause 6.2.2, or by MAC address authorization as specified in clause 6.1.2. + +A node that is configured with an unconnected domain name shall not establish a domain and shall wait in unconnected state until it has been configured with a DN or until it has been admitted to an SD by any secure admission procedure. + +The state machine depicted in Figure 6-1 provides a general overview for the basic states of the secure admission protocol. + +![Figure 6-1 – Secure admission state machine. The diagram shows two main network environments: Non-secure network (blue circle) and Secure network (green circle). The Non-secure network contains a 'Non-secure operational state'. The Secure network contains 'Unconnected state', 'Auth. State', and 'Secure operational state'. Transitions include: 'Device off' to 'Boot phase'; 'Power up device' to 'Boot phase'; 'Boot phase' to 'Non-secure operational state' (Reset), 'Unconnected state' (Not authenticated), and 'Auth. State' (Already authenticated); 'Non-secure operational state' to 'Boot phase' (Reset); 'Unconnected state' to 'Auth. State' (Pairing Event); 'Auth. State' to 'Unconnected state' (Pairing failed); 'Auth. State' to 'Secure operational state' (Pairing Ok); 'Secure operational state' to 'Unconnected state' (Push R event); and 'Secure operational state' to 'Auth. State' (Reset).](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Boot phase: Device off + Boot phase --> Non-secure operational state: Power up device + Boot phase --> Unconnected state: Not authenticated + Boot phase --> Auth. State: Already authenticated + Non-secure operational state --> Boot phase: Reset + Unconnected state --> Auth. State: Pairing Event + Auth. State --> Unconnected state: Pairing failed + Auth. State --> Secure operational state: Pairing Ok + Secure operational state --> Unconnected state: Push R event + Secure operational state --> Auth. State: Reset + +``` + +Figure 6-1 – Secure admission state machine. The diagram shows two main network environments: Non-secure network (blue circle) and Secure network (green circle). The Non-secure network contains a 'Non-secure operational state'. The Secure network contains 'Unconnected state', 'Auth. State', and 'Secure operational state'. Transitions include: 'Device off' to 'Boot phase'; 'Power up device' to 'Boot phase'; 'Boot phase' to 'Non-secure operational state' (Reset), 'Unconnected state' (Not authenticated), and 'Auth. State' (Already authenticated); 'Non-secure operational state' to 'Boot phase' (Reset); 'Unconnected state' to 'Auth. State' (Pairing Event); 'Auth. State' to 'Unconnected state' (Pairing failed); 'Auth. State' to 'Secure operational state' (Pairing Ok); 'Secure operational state' to 'Unconnected state' (Push R event); and 'Secure operational state' to 'Auth. State' (Reset). + +G.9978(18)\_F6-1 + +**Figure 6-1 – Secure admission state machine** + +## 6.1 Media access control authorization-based secure admission procedure + +This clause defines a secure admission method based on MAC authorization that enables the user to create a secure G.hn domain and add G.hn devices to an existing secure G.hn domain through an application entity (AE), such as a smart television (TV) or a personal computer (PC). + +The mechanisms described in clauses 6.1.1 and 6.1.2 apply to nodes that use the MAC authorization mechanism to get authorized to access the network. Nodes that have already been authorized and therefore have the corresponding encryption keys are not subject to this process and shall be treated as described in clause 8.6.1 of [ITU-T G.9961]. + +### 6.1.1 Use cases + +This clause describes the use cases for secure admission through MAC authorization, which is based on the comparison of the REGID (MAC address) of the registering node with a list of authorized MAC addresses. See Table 6-1. + +**Table 6-1 – Use cases for secure admission through MAC authorization** + +| Use Case | Description | +|----------|------------------------------------------------------------------------------------------------------------------------| +| 1 | A user converts a non-secure domain to a new secure domain | +| 2 | A user selects one or more nodes in a non-secure domain to establish a secure domain – including the domain master | +| 3 | A user selects one or more nodes in a non-secure domain to establish a secure domain – not including the domain master | +| 4 | A user adds nodes to an existing secure domain by selecting the nodes from a list displayed on the screen | +| 5 | A user adds nodes by configuring information about the new node(s) in the user interface (UI) node | +| 6 | A user removes one or more nodes from a domain | +| 7 | A user adds nodes by confirming node information of the joining nodes at the user interface node | + +The use cases described in clauses 6.1.1.1 to 6.1.1.7 depict possible implementations of a graphical user interface (GUI) that assumes that the external GUI is able to discover all the G.hn nodes that are connected to the physical medium. It also assumes that by checking the box, users select the nodes they want to include in a G.hn domain. Nodes for which the user does not check the box are excluded from the domain. This basic GUI is just provided as a guideline for possible implementations. + +#### 6.1.1.1 Use case 1 – A user converts a non-secure domain to a new secure domain + +In this use case, the user activates an application on the TV screen to display all registered nodes, and selects all the nodes in the list to convert the domain to an SD as illustrated in Figure 6-2. + +![Figure 6-2: The user converts a non-secure domain to a new secure domain. The diagram shows a transition from 'Non-secure domain A' to 'Secure domain B'. In domain A, there are four nodes: 1 (yellow circle), DM (white circle), 2 (white circle), and 3 (white circle). A TV screen displays a list with checkboxes for DM, Node 1, Node 2, Node 3, and Node 4, all of which are checked. An arrow labeled 'The user select all the nodes' points to domain B, which contains the same nodes but is shaded blue. A small figure of a person is shown next to the TV screen in domain A. The text 'G.9978(18)_F6-2' is in the bottom right corner.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +Figure 6-2: The user converts a non-secure domain to a new secure domain. The diagram shows a transition from 'Non-secure domain A' to 'Secure domain B'. In domain A, there are four nodes: 1 (yellow circle), DM (white circle), 2 (white circle), and 3 (white circle). A TV screen displays a list with checkboxes for DM, Node 1, Node 2, Node 3, and Node 4, all of which are checked. An arrow labeled 'The user select all the nodes' points to domain B, which contains the same nodes but is shaded blue. A small figure of a person is shown next to the TV screen in domain A. The text 'G.9978(18)\_F6-2' is in the bottom right corner. + +**Figure 6-2 – The user converts a non-secure domain to a new secure domain** + +#### 6.1.1.2 Use case 2 – A user selects one or more nodes in a non-secure domain to establish a secure domain (including the domain master) + +In this use case, the user activates an application on the TV screen to display all registered nodes, and selects some of the nodes, including the DM and a number of endpoint (EP) nodes, e.g., the DM, node 1 and node 2 in the list as shown in Figure 6-3, to create a new domain. + +NOTE – The user may not know which node is the current DM, This clause covers the case where the DM has been selected. The case that the DM is not selected by the user is described in clause 6.1.1.3. + +The remaining nodes that are not selected by the user will run a DM recovery procedure and stay in non-secure mode. + +![Diagram illustrating the selection of nodes to form a secure domain, including the domain master.](4e4be0bd8b235167902f2c03e41da651_img.jpg) + +The diagram shows a user interacting with a smart TV screen to select nodes for a secure domain. The TV screen displays a list with checkboxes: DM (checked), Node 1 (checked), Node 2 (checked), Node 3 (unchecked), and Node 4 (unchecked). Below the list, it says "TV screen". + +On the left, "Non-secure domain A" contains nodes 1 (yellow, selected), 2, 3, 4, and a Domain Master (DM). Arrows point from this domain to two outcomes on the right: + +- Secure domain B**: Contains node 1 (yellow) and the DM. +- Non-secure domain A**: Contains nodes 3 and 4, with node 3 designated as "The new DM". + +A caption below the arrows states: "The user selects the DM and node 1, 2 via the smart TV to create a secure domain." + +G.9978(18)\_F6-3 + +Diagram illustrating the selection of nodes to form a secure domain, including the domain master. + +**Figure 6-3 – The user selects one or more nodes in a non-secure domain to establish a secure domain (including the domain master)** + +#### 6.1.1.3 Use case 3 – A user selects a part of the nodes in a non-secure domain to establish a secure domain (not including the domain master) + +In this use case, the user activates an application on the TV screen to display all registered nodes, and selects one or more EP nodes, e.g., node 1, 2 and 4 in the list as shown in Figure 6-4, to create a new domain. + +The rest nodes that are not selected by the user will stay in the non-secure mode. + +NOTE – In use cases 1, 2 and 3, the user interface (UI) node is selected by default. + +![Diagram illustrating the selection of nodes to form a secure domain, excluding the original domain master.](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +The diagram shows a user interacting with a smart TV screen to select nodes for a secure domain. The TV screen displays a list with checkboxes: DM (unchecked), Node 1 (checked), Node 2 (checked), Node 3 (unchecked), and Node 4 (checked). Below the list, it says "TV screen". + +On the left, "Non-secure domain A" contains nodes 1 (yellow, selected), 2, 3, 4, and a Domain Master (DM). Arrows point from this domain to two outcomes on the right: + +- Secure domain B**: Contains nodes 1 (yellow), 2, and 4, with node 1 designated as "The new DM". +- Non-secure domain A**: Contains node 3 and the original DM. + +A caption below the arrows states: "The user selects node 1, 2 and 4 via the smart TV to create a secure domain." + +G.9978(18)\_F6-4 + +Diagram illustrating the selection of nodes to form a secure domain, excluding the original domain master. + +**Figure 6-4 – A user selects one or more nodes in a non-secure domain to establish a secure domain (not including the domain master)** + +#### 6.1.1.4 Use case 4 – A user adds nodes to an existing secure domain by selecting the nodes from a list displayed on the screen + +In this use case, the user activates an application on the TV screen to request adding nodes to an SD. The UI node (e.g., the G.hn node that is associated with the smart TV) will collect information about joining nodes and display the list of possible joining nodes on the screen. Then users can select the nodes they want to add and add them to the existing SD. + +Figure 6-5 illustrates this use case. + +![Diagram illustrating Use case 4: A user adds nodes to an existing secure domain by selecting the nodes from a list displayed on the screen.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram shows a user interacting with a smart TV to add nodes to a secure domain. On the left, a 'Secure domain A' contains a yellow node '1' and a 'DM' node. Below it, nodes '2' and '3' are also in the domain. To the right, nodes '4' and '5' are in an 'Unconnected state'. A 'TV screen' displays a list: DM, Node 1, Node 2, Node 3, Node 4 (unauthenticated), and Node 5 (unauthenticated). Nodes 4 and 5 have green checkmarks. An arrow points from the TV screen to the right side of the diagram, where nodes '4' and '5' have been added to 'Secure domain A'. Text below the arrow reads: 'The user adds nodes via the smart TV, and selects nodes 4 and 5.' The diagram is labeled 'G.9978(18)\_F6-5'. + +Diagram illustrating Use case 4: A user adds nodes to an existing secure domain by selecting the nodes from a list displayed on the screen. + +Figure 6-5 – The user adds nodes to an existing secure domain by selecting the nodes from a list displayed on the screen + +#### 6.1.1.5 Use case 5 – A user adds nodes by configuring information about the joining node(s) in the user interface node + +In this use case, the user can configure information about authorized joining nodes in the UI node (e.g., via the webpage), and the UI node will convey the information to the DM. The DM will then allow the registration of these nodes. Figure 6-6 illustrates this use case. + +![Diagram illustrating Use case 5: A user adds nodes by configuring information about the joining node(s) in the user interface node.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +The diagram shows a user configuring information for joining nodes. On the left, 'Secure domain A' contains nodes '1' (yellow), 'DM', '2', '3', and '4'. Nodes '5' and '6' are in an 'Unconnected state'. A 'TV screen' has an arrow pointing to it with the text: 'The user configures the REGID of node 5 and 6, e.g., inputs the MAC address of nodes 5 and 6.' An arrow points from the TV screen to the right side, where nodes '5' and '6' have been added to 'Secure domain A'. The diagram is labeled 'G.9978(18)\_F6-6'. + +Diagram illustrating Use case 5: A user adds nodes by configuring information about the joining node(s) in the user interface node. + +Figure 6-6 – The user adds nodes by configuring information about the joining node(s) in the user interface node + +#### 6.1.1.6 Use case 6 – A user removes one or more nodes from a domain + +In this use case, the user activates an application on the TV screen to display all registered nodes, and selects the EP nodes he wants to remove from the domain. Figure 6-7 illustrates this use case. + +![Diagram illustrating the removal of nodes from a secure domain.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) + +The diagram shows a user interacting with a TV screen to manage nodes in a secure domain. On the left, a 'Secure domain A' contains a yellow node '1' (DM), and nodes '2', '3', and '4'. A 'TV screen' displays a list: DM, Node 1, Node 2, Node 3 (checked), Node 4 (checked). Arrows point from the checked nodes to an 'Unconnected state' on the right. Text below the arrows states: 'The user selects nodes 3 and 4 to remove them from domain A.' The right side shows 'Secure domain A' with nodes '1' (DM) and '2', and nodes '3' and '4' outside the domain boundary. A code 'G.9978(18)\_F6-7' is in the bottom right. + +Diagram illustrating the removal of nodes from a secure domain. + +**Figure 6-7 – The user removes one or more nodes from a secure domain** + +#### 6.1.1.7 Use case 7 – A user adds nodes by confirming the node information of the joining nodes at the user interface node + +In this case, when the new node first powers on, it broadcasts a message to notify the network of its existence. When the DM receives the message, it will notify the UI node of the existence of the new node, and the AE will pop up a message on the TV screen indicating that the new node exists and asking if the new node is allowed to join the secure domain. The new node is allowed to join the secure domain if the user authorizes it to do so. + +![Diagram illustrating the addition of a new node to a secure domain.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +The diagram shows a user adding a new node to a secure domain. On the left, 'Secure domain A' contains nodes '1' (DM), '2', and '3'. Node '4' is outside, labeled 'New node power on'. A 'TV screen' displays: 'Node 4 exist, whether allow it to join in secure domain A' with a checked box. Text next to the user says: 'The user receives notification that new node 4 exist'. An arrow points to the right side, labeled 'The user allows node 4 to join in secure domain A'. The right side shows 'Secure domain A' containing nodes '1' (DM), '2', '3', and '4'. A code 'G.9978(11-18)\_F6-8' is in the bottom right. + +Diagram illustrating the addition of a new node to a secure domain. + +**Figure 6-8 – AE pops up a message on the TV screen to notify of the existence of a new node, and the user chooses to whether allow it join the secure domain or not** + +NOTE – Other nodes in the neighbourhood may also receive the notification message, and pop up the message on the TV screen. Vendors should implement vendor discretionary means to avoid security issues related to this. + +### **6.1.2 Secure admission description** + +The user may use an AE to secure an NSD, to include new nodes in an existing SD and to remove nodes from an existing SD. + +#### **6.1.2.1 Secure admission protocol for creating a secure domain** + +In order to convert an NSD to an SD or create an SD via an AE that shows all registered nodes, users shall select the nodes that they wish to add to the SD. + +The application shall send the list of the authorized nodes, composed of the nodes that are selected by the user to create an SD, to the attached G.hn node (i.e., the UI node). + +If the UI node is not included in the list of authorized nodes, the procedure shall be aborted and an error message presented to the user. + +If the DM is included in the list of authorized nodes (see clauses 6.1.1.1 and 6.1.1.2), the UI node shall send an ADM\_UI\_MACauthorization.req message to its DM. The ADM\_UI\_Pairing.req message shall include the list of the authorized nodes' MAC addresses selected by the user. + +On receipt of an ADM\_UI\_MACauthorization.req message, the DM shall reply with an ADM\_UI\_MACauthorization.cnf message to the UI node within 100 ms, and then generate a SDN and a PW and send an ADM\_SecureDomain.req message to all authorized registered nodes in the domain to inform them that the domain has converted into an SD. The ADM\_SecureDomain.req message shall include the newly generated SDN, the PW for authentication and the SC REGID. + +If the UI node does not receive an ADM\_UI\_MACauthorization.cnf message from the DM within 200 ms, the UI node shall repeat the request. If, after the second request, the proxy node still does not receive the ADM\_UI\_MACauthorization.cnf message within 200 ms, the request to create an SD fails. + +On receipt of the ADM\_SecureDomain.req message, the receiving node shall confirm receipt by replying with an ADM\_SecureDomain.cnf message within 100 ms. The receiving node shall adopt the new SDN and PW. + +After the DM receives ADM\_SecureDomain.cnf message from all its addressed nodes, or a 200 ms timeout expires, it shall start to transmit the medium access plan (MAP) with the new SDN. + +On receipt of the MAP with the new SDN, each node shall start the authentication procedure specified in [ITU-T G.9961]. + +NOTE 1 – The nodes that are not included in the list of authorized nodes shall stay in non-secure mode, and they may perform the DM recovery procedure as specified in clause 8.6.6.2 of [ITU-T G.9961]. + +The protocol diagram of the secure admission for use case 1 and 2 is presented in Figure 6-9. + +![Sequence diagram showing secure admission for use case 1 and 2. Lifelines: DM, Node 1 (UI EP), and Node 2. The process involves authorization requests, domain creation requests, and final MAP transmission. All nodes transition to a 'Domain is secure' state.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +sequenceDiagram + participant DM + participant Node1 as Node 1 (UI EP) + participant Node2 as Node 2 + + Note right of Node1: User selects all the nodes or some of the nodes (including the DM) in the domain to create a secure domain. + Node1->>DM: ADM_UI_MACauthorization.req + DM-->>Node1: ADM_UI_MACauthorization.cnf + Node1->>DM: ADM_SecureDomain.req + DM-->>Node1: ADM_SecureDomain.cnf + DM->>Node2: ADM_SecureDomain.req + Node2-->>DM: ADM_SecureDomain.cnf + DM->>Node2: MAP is transmitted with new domain name + + Note left of DM: Domain starts to be secure + DM-->>DM: Domain is secure + Node1-->>Node1: Domain is secure + Node2-->>Node2: Domain is secure + +``` + +G.9978(11-18)\_F6-9 + +Sequence diagram showing secure admission for use case 1 and 2. Lifelines: DM, Node 1 (UI EP), and Node 2. The process involves authorization requests, domain creation requests, and final MAP transmission. All nodes transition to a 'Domain is secure' state. + +**Figure 6-9 – Protocol diagram describing secure admission for use case 1 and 2** + +If the DM is not included in the list of authorized nodes (see clause 6.1.1.3), the UI node shall send an ADM\_UI\_MACauthorization.req message to all the nodes in the list. After receipt of the list of authorized nodes, every authorized node shall reply to the UI node within 200 ms with an ADM\_UI\_MACauthorization.cnf message and then rank its DM capabilities based on the criteria as specified in clause 8.6.6.3 of [ITU-T G.9961]. The highest ranking authorized node shall become a new DM of a new SD by generating a random SDN and a PW and start transmitting MAPs with the generated DN. + +The authorized node that detects the MAP or relayed medium access plan (RMAP) of an SD from one of the authorized nodes shall register in the new DM within 1 s and the new DM shall send them the PW for authentication if it accepts their registration request. After 1 s, the new DM shall stop the registration of these authorized nodes. + +If an authorized node fails to detect the MAP from the highest ranking authorized node after a 1 s timeout, it shall return to the state it was before it received the ADM\_UI\_MACauthorization.req message from the UI node, which could be an unconnected state or a non-secure operational state. + +NOTE 2 – Whether the DM is selected by the user or not, the UI node shall be selected by default and become the SC of the new SD. + +Figure 6-10 is the protocol diagram of the secure admission for use case 3. + +![Sequence diagram for secure admission for use case 3. Lifelines: DM, Node 2, Node 1 (UI node), Node 3, Node 4 (the new DM). The process involves MAC authorization requests and confirmations, followed by MAP transmission and registration requests/confirmations. Nodes 2, 1, and 4 are shown becoming 'Registered to the secure domain'.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +sequenceDiagram + participant DM + participant Node2 as Node 2 + participant Node1 as Node 1 (UI node) + participant Node3 + participant Node4 as Node 4 (the new DM) + + Note right of Node1: User selects node 1, 2, 4 to create a secure domain (not including the DM) + Node1->>Node2: ADM_UI_MACauthorization.req + Node1->>Node4: ADM_UI_MACauthorization.req + Node2-->>Node1: ADM_UI_MACauthorization.cnf + Node4-->>Node1: ADM_UI_MACauthorization.cnf + Note right of Node1: MAP is transmitted with new domain name, including MAC authorization info sub-field + Node1->>Node2: Registration request + Node1->>Node4: Registration request + Node2-->>Node1: Registration confirmation with PW and SC REGID + Node4-->>Node1: Registration confirmation with PW and SC REGID + Note left of Node2: Registered to the secure domain + Note left of Node1: Registered to the secure domain + Note right of Node4: Domain is secure + +``` + +G.9978(11-18)\_F6-10 + +Sequence diagram for secure admission for use case 3. Lifelines: DM, Node 2, Node 1 (UI node), Node 3, Node 4 (the new DM). The process involves MAC authorization requests and confirmations, followed by MAP transmission and registration requests/confirmations. Nodes 2, 1, and 4 are shown becoming 'Registered to the secure domain'. + +**Figure 6-10 – Protocol diagram describing secure admission for use case 3** + +#### 6.1.2.2 Secure admission protocol for adding nodes to an existing secure domain + +Users may add new nodes to an existing SD by: + +- activating an application on the AE to request adding nodes and selecting the nodes they wish to include in this SD in a list (see clause 6.1.1.4), or +- configuring the information (e.g., inputting the MAC addresses) of the nodes they wish to include via the UI node (see clause 6.1.1.5). + +##### 6.1.2.2.1 Adding nodes by user selection + +If the user activates an application to request adding nodes to an SD, the AE shall trigger the attached G.hn node (i.e., the UI node) to send an ADM\_UI\_MACauthorization.ind message to the DM. If the UI node is the SC of this SD or it has been authorized by the SC, it can send the ADM\_UI\_MACauthorization.ind message directly. If the proxy node has not been authorized by the SC, the UI node shall request authorization by the SC before it sends the ADM\_UI\_MACauthorization.ind message to the DM. In order to get authorized by the SC, the UI node shall send the SC a SC\_UI\_Authorization.req message, which shall be encrypted using the NSC key. The SC shall reply with an SC\_UI\_Authorization.cnf message to the UI node to indicate whether the request is accepted. If the SC accepts the authorization request from the UI node, it shall send a SC\_UI\_Authorization.ind message to the DM to inform the UI node of the authorization. + +After receiving the indication message, the DM shall open a window to allow registration of the nodes that do not have the PW, only if it has already received the SC\_UI\_Authorization.ind message from the SC indicating that the UI node has been authorized. During this time window, the DM shall broadcast the MAP frames with the RegistrationOffer field set to one. The nodes in unconnected states that can detect the MAP or RMAP frames from this SD shall register in the DM. The DM shall send the list of these nodes to the UI node by sending an ADM\_UI\_MACauthorization.rsp message when the time window expires. Besides these nodes, the DM shall also include information about neighbouring nodes that have been detected from an NSD in an ADM\_UI\_MACauthorization.rsp message. + +NOTE – The DM collects information about neighbouring nodes, including the REGID and DN as specified in [ITU-T G.9961]. + +After receiving the ADM\_UI\_MACauthorization.rsp message, the AE associated with the UI node displays the list of nodes in this message on the screen. Users can then select the nodes they wish to add. The application shall send the list of authorized nodes selected by the user to the attached G.hn node, which will trigger the UI node to send an ADM\_UI\_MACauthorization.req message to the DM. The "RequestReason" field of the ADM\_UI\_MACauthorization.req message shall be set to 316. + +On receipt of the ADM\_UI\_MACauthorization.req message, the DM shall reply to the UI node within 100 ms with an ADM\_UI\_MACauthorization.cnf message and then send an ADM\_SecureDomain.req message, which includes the PW for authentication, to the authorized nodes that have registered on it. The DM shall also distribute an MAC authorization information subfield to the Medium Access Plan-Default (MAP-D) frames for 120 s, which includes collected information about neighbouring nodes that have registered in an NSD. A node in an NSD shall monitor MAP-D frames from neighbouring domains and, if it detects that its information is included in the MAC authorization information subfield in the MAP-D frames, it shall leave the NSD and register in the SD. + +On receipt of the ADM\_SecureDomain.req message, the receiving node shall confirm receipt by replying with an ADM\_SecureDomain.cnf message within 100 ms. The receiving node shall use the PW and DN to complete authentication with the SC. The nodes that are not selected by the user shall be rejected by the DM. + +If a node in an NSD detects a MAP-D or RMAP-D frame from an SD that includes its information in the MAC authorization subfield, it shall try to register in the SD. If the DM of this SD receives the registration request from this node, it shall send the PW in the registration confirmation to this node. + +Figure 6-11 is the protocol diagram of the secure admission for use case 4. + +![Sequence diagram for secure admission (Figure 6-11). Lifelines: DM, UI EP node, Non-secure active EP node, Unconnected node. The diagram shows the interaction between these entities for node registration and authentication.](a734898ce18e972938949637c32a34f4_img.jpg) + +``` + +sequenceDiagram + participant DM + participant UI_EP_node as UI EP node + participant Non_secure_active_EP_node as Non-secure active EP node + participant Unconnected_node as Unconnected node + + Note left of DM: Open a window to allow +the registration of nodes +that do not own PW + DM->>UI_EP_node: ADM_UI_MACauthorization.ind + Note right of UI_EP_node: User starts to include +new nodes to the domain + DM->>Unconnected_node: MAP with "RegistrationOffer" field set to 1 + Unconnected_node->>DM: Registration request + DM->>Unconnected_node: Registration confirmation + DM->>UI_EP_node: ADM_UI_MACauthorization.rsp + Note right of UI_EP_node: User selects the nodes he +wishes to include into the +domain + UI_EP_node->>DM: ADM_UI_MACauthorization.req + DM->>UI_EP_node: ADM_UI_MACauthorization.cnf + DM->>Unconnected_node: ADM_SecureDomain.req + Unconnected_node->>DM: ADM_SecureDomain.cnf + DM->>Non_secure_active_EP_node: MAP including the MAC authorization information sub-field + Non_secure_active_EP_node->>DM: Registration request + DM->>Non_secure_active_EP_node: Registration confirmation including the PW + Note left of DM: Close the window and +stop allowing the +registration of nodes that +do not have PW. + Note right of Non_secure_active_EP_node: Authentication +to the SC + Note right of Unconnected_node: Authentication +to the SC + +``` + +G.9978(11-18)\_F6-11 + +Sequence diagram for secure admission (Figure 6-11). Lifelines: DM, UI EP node, Non-secure active EP node, Unconnected node. The diagram shows the interaction between these entities for node registration and authentication. + +**Figure 6-11 – Protocol diagram describing secure admission for use case 4** + +##### 6.1.2.2.2 Adding nodes by user configuration + +If users configure the information (i.e., input the MAC address) of the nodes they wish to include in the existing domain on the AE that is associated with the G.hn UI node, the AE shall trigger the attached G.hn node (i.e., the UI node) to send an ADM\_UI\_MACauthorization.req message to its DM. The ADM\_UI\_MACauthorization.req message shall include the list of the MAC addresses of the authorized nodes input by the user and the "RequestReason" field shall be set to 416. + +If the UI node is the SC of this SD or it has been authorized by the SC, it can send the ADM\_UI\_MACauthorization.req message directly. If the UI node has not been authorized by the SC, the UI node shall request to be authorized by the SC before it sends the ADM\_UI\_MACauthorization.req message to the DM. In order to get authorized by the SC, the UI node shall send the SC a SC\_UI\_Authorization.req message, which shall be encrypted using the NSC key. The SC shall reply with an SC\_UI\_Authorization.cnf message to the UI node to indicate whether the request is accepted. If the SC accepts the authorization request from the UI node, it shall send an SC\_UI\_Authorization.ind message to the DM to inform the UI node of the authorization. + +On receipt of the ADM\_UI\_MACauthorization.req message, the DM shall reply to the UI node within 100 ms with an ADM\_UI\_MACauthorization.cnf message only if it has already received the ADM\_UI\_Authorization.ind message from the SC indicating that the UI node has been authorized. The DM shall then include a MAC authorization information auxiliary subfield in the MAP-D frames, which includes information about the authorized nodes in the list. During 120 s, only the authorized nodes and the nodes that have a valid PW are allowed to register in the new SD. + +When a node detects an MAP-D or RMAP-D frame that includes the MAC authorization information auxiliary subfield, it shall check whether it is included in this auxiliary subfield. If its MAC address matches the information in this auxiliary subfield, it shall send the registration request to the DM according to the registration procedure specified in [ITU-T G.9961]. On receipt of the registration message from an authorized node, the DM shall also check whether the registering node is an authorized node, the DM shall send the authorized registering node an ADM\_DmRegistrResponse.cnf message including the PW for authentication and reject the registration request from any node that is not included in the authorized nodes. + +After 120 s, the DM shall remove the MAC authorization information auxiliary subfield from the MAP-D frame and stop allowing the registration of these authorized nodes. + +Figure 6-12 is the protocol diagram of the secure admission for use case 5. + +![Sequence diagram showing the secure admission process for use case 5. The diagram involves three main entities: DM, UI EP node, and Joining EP. The process starts with the UI EP node sending an ADM_UI_MACauthorization.req message to the DM. The DM responds with an ADM_UI_MACauthorization.cnf message. The DM then sends a MAP including the MAC authorization information sub-field to the Joining EP. The Joining EP sends a Registration request to the DM. The DM responds with a Registration confirmation with PW. Finally, the Joining EP sends an Authentication to the SC message.](e636d7ccca0ad14c6b95201404324823_img.jpg) + +``` +sequenceDiagram + participant DM + participant UI_EP_node as UI EP node + participant Joining_EP as Joining EP + Note right of UI_EP_node: User configures the information of nodes he wishes to include into the domain to the proxy EP + UI_EP_node->>DM: ADM_UI_MACauthorization.req + DM-->>UI_EP_node: ADM_UI_MACauthorization.cnf + DM->>Joining_EP: MAP including the MAC authorization information sub-field + Joining_EP->>DM: Registration request + DM-->>Joining_EP: Registration confirmation with PW + Note right of Joining_EP: Authentication to the SC +``` + +G.9978(11-18)\_F6-12 + +Sequence diagram showing the secure admission process for use case 5. The diagram involves three main entities: DM, UI EP node, and Joining EP. The process starts with the UI EP node sending an ADM\_UI\_MACauthorization.req message to the DM. The DM responds with an ADM\_UI\_MACauthorization.cnf message. The DM then sends a MAP including the MAC authorization information sub-field to the Joining EP. The Joining EP sends a Registration request to the DM. The DM responds with a Registration confirmation with PW. Finally, the Joining EP sends an Authentication to the SC message. + +Figure 6-12 – Protocol diagram describing secure admission for use case 5 + +##### 6.1.2.2.3 Adding nodes by user confirmation + +If a new node powers on in the home network, it will broadcast an ADM\_SelfNotify.ind message with its REGID "A" to notify of its existence. When the DM receives this ADM\_SelfNotify.ind message, it sends an ADM\_UINewNodeExist.ind message with REGID "A" to the UI node. The AE that is associated with G.hn UI node will pop up a message with REGID "A" to let the user know that a new node is joining the network. If the user accepts that the new device can join the secure domain, the UI node shall send an ADM\_UI\_MACauthorization.ind message to the DM. + +After receiving the indication message, the DM shall open a window to allow registration of this node with REGID "A", only if it has already received the SC\_UI\_Authorization.req message from the SC indicating that the UI node has been authorized. During this time window, the DM shall broadcast the MAP frames with the RegistrationOffer field set to two and the "RegistrationRestrict" field set to REGID "A". The nodes that work with REGID "A" shall register in the DM. + +After the new unconnected node receives the registration confirmation message, it shall send an ADM\_SecureDomain.req message, which includes the PW for authentication, to the authorized nodes that have registered on it. The DM shall also distribute a MAC authorization information subfield to the Medium Access Plan-Default (MAP-D) frames for 120 s, which includes collected information about neighbouring nodes that have registered in an NSD. A node in an NSD shall monitor MAP-D frames from neighbouring domains and, if it detects that its information is included in the MAC authorization information subfield in the MAP-D frames, it shall leave the NSD and register in the SD. + +On receipt of the ADM\_SecureDomain.req message, the receiving node shall confirm receipt by replying with an ADM\_SecureDomain.cnf message. The receiving node shall use the PW and DN to complete authentication with the SC. The nodes that do not work with REGID "A" shall be rejected by the DM. + +![Sequence diagram illustrating the secure admission process for use case 7. The diagram shows interactions between DM, UI node, and Unconnected node. The DM receives an ADM_SelfNotify.ind from the Unconnected node, sends an ADM_UINewNodeExist.ind to the UI node, and then an ADM_UI_MACauthorization.req to the DM. The DM opens a window to allow registration of the node with REGID 'A'. The DM then sends a MAP frame with 'RegistrationOffer' field set to 2 and 'RegistrationRestrict' field set to REGID 'A' to the Unconnected node. The Unconnected node sends a Registration request to the DM, which responds with a Registration confirmation. The Unconnected node then sends an ADM_SecureDomain.req to the DM, which responds with an ADM_SecureDomain.cnf. The Unconnected node then performs authentication to the SC. Finally, the DM closes the window and stops allowing the registration of the node with MAC addr 'A'.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +``` + +sequenceDiagram + participant DM + participant UI node + participant Unconnected node + + Note left of DM: Open a window to allow the registration of node with REGID "A" + Unconnected node->>DM: ADM_SelfNotify.ind + DM->>UI node: ADM_UINewNodeExist.ind + Note right of UI node: User receive the notify with MAC addr A and confirm to start to include this new node to the domain + UI node->>DM: ADM_UI_MACauthorization.req + DM->>Unconnected node: MAP with "RegistrationOffer" field set to 2 and "RegistrationRestrict" field set to REGID "A" + Unconnected node->>DM: Registration request + DM->>Unconnected node: Registration confirmation + Unconnected node->>DM: ADM_SecureDomain.req + DM->>Unconnected node: ADM_SecureDomain.cnf + Note right of Unconnected node: Authentication to the SC + Note left of DM: Close the window and stop allowing the registration of node with MAC addr "A" + +``` + +G.9978(11-18)\_F6-13 + +Sequence diagram illustrating the secure admission process for use case 7. The diagram shows interactions between DM, UI node, and Unconnected node. The DM receives an ADM\_SelfNotify.ind from the Unconnected node, sends an ADM\_UINewNodeExist.ind to the UI node, and then an ADM\_UI\_MACauthorization.req to the DM. The DM opens a window to allow registration of the node with REGID 'A'. The DM then sends a MAP frame with 'RegistrationOffer' field set to 2 and 'RegistrationRestrict' field set to REGID 'A' to the Unconnected node. The Unconnected node sends a Registration request to the DM, which responds with a Registration confirmation. The Unconnected node then sends an ADM\_SecureDomain.req to the DM, which responds with an ADM\_SecureDomain.cnf. The Unconnected node then performs authentication to the SC. Finally, the DM closes the window and stops allowing the registration of the node with MAC addr 'A'. + +Figure 6-13 – Protocol diagram describing secure admission for use case 7 + +#### 6.1.2.3 Removing nodes from a domain through MAC authorization + +Users may remove nodes through the AE that shows them the registered nodes. Users select the nodes that they wish to remove from the domain. The application shall send the list of the nodes to be removed to the attached G.hn node and trigger the node to send an ADM\_UI\_MACauthorization.req message to its DM. The ADM\_UI\_MACauthorization.req message shall include the list of the authorized nodes' MAC Address selected by the user and the "RequestReason" field shall be set to 516. + +On receipt of the ADM\_UI\_MACauthorization.req message, the DM shall reply to the UI node within 100 ms with an ADM\_UI\_MACauthorization.cnf message and then force the resignation of the nodes in the received ADM\_UI\_MACauthorization.req message according to the procedure specified in [ITU-T G.9961]. + +#### 6.1.2.4 MAC authorization secure admission protocol messages + +The following clauses specify the messages to support the MAC authorization secure admission protocol. + +##### 6.1.2.4.1 Format of ADM\_UI\_MACauthorization.req + +The ADM\_UI\_MACauthorization.req message shall be sent by the UI node to the DM or other EP nodes to convey list of the authorized nodes during the MAC authorization secure admission process. + +The format of the management message parameter list (MMPL) of the ADM\_UI\_MACauthorization.req message shall be as shown in Table 6-2. + +**Table 6-2 – Format of the management message parameter list of the ADM\_UI\_MACauthorization.req message** + +| Field | Octet | Bits | Description | +|---------------|--------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RequestReason | 0 | [3:0] | 0 16 : Convert a non-secure domain to a secure domain
1 16 : Select some of the nodes to create a secure domain (including the DM)
2 16 : Select some of the nodes to create a secure domain (not including the DM)
3 16 : Include nodes to a secure domain according to the user's selection
4 16 : Include nodes to a secure domain by configure the info of these nodes
5 16 : Remove nodes from a domain
6 16 : Include a node with a specific REGID in a secure domain after confirmation from the user
7 16 -F 16 – Reserved by ITU-T | +| Reserved | | [7:4] | Reserved by ITU-T (Note) | +| NumAuthNodes | 1 | [7:0] | The number of authorized nodes | +| REGID1 | 2 to 7 | [47:0] | The REGID of the first authorized node | +| ... | ... | ... | ... | +| REGIDN | Var | [47:0] | The REGID of the N th authorized node | + +NOTE – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. + +##### 6.1.2.4.2 Format of ADM\_UI\_MACauthorization.cnf + +The ADM\_UI\_MACauthorization.cnf message shall be sent by the DM or EP nodes to the UI nodes to confirm receipt of the ADM\_UI\_MACauthorization.req message. + +The MMPL of the ADM\_UI\_MACauthorization.cnf message is empty. + +##### 6.1.2.4.3 Format of ADM\_SecureDomain.req + +The ADM\_SecureDomain.req message shall be sent by the DM to the authorized node to convey the PW and other parameters of the domain for authentication. + +The format of the MMPL of the ADM\_SecureDomain.req message shall be as shown in Table 6-3. + +**Table 6-3 – Format of the MMPL of the ADM\_SecureDomain.req message** + +| Field | Octet | Bits | Description | +|------------|----------|---------|---------------------------------------------------------------------------------------------------------------------------------------------| +| DomainName | 0 to 31 | [255:0] | This field shall indicate the 32-octet domain name represented in American standard code for information exchange (ASCII) characters (Note) | +| Password | 32 to 43 | [95:0] | This field shall include the user password for node authentication for this domain name | +| SCRegID | 44 to 51 | [47:0] | This field shall include the REGID of the SC of the domain | + +NOTE – The ASCII characters shall be mapped on to the bytes of the domain name in the following way: + +- the least significant bit (LSB) of the 7-bit ASCII character is mapped on to bit b0 of the corresponding byte of the domain name; +- the most significant bit (MSB) of all bytes shall be set to zero; +- the first ASCII character of the domain name shall be mapped on to the least significant byte of the domain name (e.g., if the domain name is "Network", the first ASCII character is letter "N" that shall be mapped at byte 0 of the domain name); +- if the number of provided ASCII characters is less than 32, the rest of the domain name field bytes shall be set to 0016. + +##### 6.1.2.4.4 Format of ADM\_SecureDomain.cnf + +The ADM\_SecureDomain.cnf message shall be sent by the joining node in response to an ADM\_SecureDomain.req message. + +The MMPL of the ADM\_SecureDomain.cnf message is empty. + +##### 6.1.2.4.5 Format of ADM\_UI\_MACauthorization.ind + +The ADM\_UI\_MACauthorization.ind message shall be sent by the UI node to the DM to report that the user wishes to include nodes in the domain. The DM shall then open a registration window to allow the registration of the nodes that do not have the PW. + +The MMPL of the ADM\_UI\_MACauthorization.ind message is empty. + +##### 6.1.2.4.6 Format of ADM\_UI\_MACauthorization.rsp + +The ADM\_UI\_MACauthorization.rsp message shall be sent by the DM to the UI node in response to the ADM\_UI\_MACauthorization.ind message to provide information about the registered node(s) that do not have the PW. + +The format of the MMPL of the ADM\_UI\_MACauthorization.rsp message shall be as shown in Table 6-4. + +**Table 6-4 – Format of the MMPL of the ADM\_UI\_MACauthorization.rsp message** + +| Field | Octet | Bits | Description | +|------------|-------|--------|---------------------------------------------------------------------| +| NumNodes | 0 | [7:0] | The number of the nodes that the DM collects for the user to select | +| NodeRegID1 | 1 | [47:0] | The REGID of the first node | +| ... | ... | ... | ... | +| NodeRegIDN | Var | [47:0] | The REGID of the N th node | + +##### **6.1.2.4.7 Format of SC\_UI\_Authorization.req** + +The SC\_UI\_Authorization.req message shall be sent by a node to the SC to request to be authorized as the UI node for MAC authorization-based secure admission. + +The format of the MMPL of the SC\_UI\_Authorization.req message shall be as shown in Table 6-5. + +**Table 6-5 – Format of the MMPL of the SC\_UI\_Authorization.req message** + +| Field | Octet | Bits | Description | +|--------------|---------|--------|----------------------------------------------------------------------| +| DeviceID | 0 | [7:0] | The DEVICE_ID of the node requesting to be authorized as the UI node | +| RegID | 1-6 | [47:0] | The REGID of the node requesting to be authorized as the UI node | +| NumAuthNodes | 7 | [7:0] | The number of the nodes authorized by the user | +| RegID1 | 8 to 13 | [47:0] | The REGID of the first authorized node | +| ... | ... | ... | ... | +| RegIDN | Var | [47:0] | The REGID of the N th authorized node | + +##### **6.1.2.4.8 Format of SC\_UI\_Authorization.cnf** + +The SC\_UI\_Authorization.cnf message shall be sent by the SC in response to the received SC\_UI\_Authorization.req message. + +The format of the MMPL of the SC\_UI\_Authorization.cnf message shall be as shown in Table 6-6. + +**Table 6-6 – Format of the MMPL of the SC\_UI\_Authorization.cnf message** + +| Field | Octet | Bits | Description | +|------------|-------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| StatusCode | 0 | [7:0] | Value that indicates whether or not the request has been accepted by the SC:
00 16 = Success (the request is accepted)
01 16 = Failure (no reason provided)
02 16 -FF 16 = Reserved by ITU-T | + +##### **6.1.2.4.9 Format of SC\_UI\_Authorization.ind** + +The SC\_UI\_Authorization.ind message shall be sent by the SC to the DM to report that an EP node has been authorized as a UI node for MAC authorization-based secure admission. + +The format of the MMPL of the SC\_UI\_Authorization.ind message shall be as shown in Table 6-7. + +**Table 6-7 – Format of the MMPL of the SC\_UI\_Authorization.ind message** + +| Field | Octet | Bits | Description | +|----------|-------|--------|-------------------------------------------------------| +| DeviceID | 0 | [7:0] | The DEVICE_ID of the node requesting to be authorized | +| RegID | 1-6 | [47:0] | The REGID of the node requesting to be authorized | + +##### **6.1.2.4.10 Format of ADM\_SelfNotify.ind** + +The ADM\_SelfNotify.ind message will be broadcast to the network by a new unconnected node to notify of its existence and inform of its REGID. + +The format of the management message parameter list (MMPL) of the ADM\_SelfNotify.ind message shall be as shown in Table 6-8. + +**Table 6-8 – Format of the management message parameter list of the ADM\_SelfNotify.ind message** + +| Field | Octet | Bits | Description | +|-------|-------|--------|-------------------------------------| +| REGID | 6 | [47:0] | REGID (MAC address) of the new node | + +##### **6.1.2.4.11 Format of ADM\_UINewNodeExist.ind** + +The ADM\_UINewNodeExist.ind message shall be sent by the DM to the UI node to convey the REGID of the new unconnected node. + +The format of the management message parameter list (MMPL) of the ADM\_UINewNodeExist.ind message shall be the same as that of the ADM\_SelfNotify.ind message, as shown in Table 6-8. + +## **6.2 Admission through generic pairing mechanism** + +This clause defines a secure admission method that enables establishment of an SD that requires minimal user intervention and avoids the use of a computer to configure a secure G.hn network. This kind of mechanism is commonly known as push-button security (or pairing) and is already available in many existing home networking technologies. This pairing method addresses special requirements that are derived from the special characteristics of G.hn domains. This pairing mechanism supports two pairing modes: single-node pairing mode, to add a single non-secure node to a SD per pairing operation; and multi-node pairing mode that enables several non-secure nodes to enter the SD during the same pairing window. A G.hn domain may work exclusively in only one mode. The pairing mechanism in single-node mode and in multi-node pairing mode shall address the use cases that are specified in clause 6.2.1. When more than one button needs to be pushed, the order of pushing these buttons is irrelevant. + +The mechanisms described in clauses 6.2.1 and 6.2.2 apply to nodes that use the generic pairing mechanism to get authorization to access the network. Nodes that have already been authenticated and therefore have the corresponding encryption keys are not subject to this process and shall be treated as described in clause 8.6.1 of [ITU-T G.9961] (i.e., they will be accepted even if the pairing window is closed). + +### 6.2.1 Use cases + +Clauses 6.2.1.1 to 6.2.1.10 describe the behaviour of the different nodes of a domain in different situations. See Table 6-9. + +**Table 6-9 – Use cases for secure admission through a push-button mechanism** + +| Use case | Description | Comments | +|----------|------------------------------------------------------------------------------------------------------------------------------------|----------| +| 1-a | Single-node pairing mode – Convert a non-secure domain to a new secure domain through generic pairing | | +| 1-b | Single-node pairing mode – Add a node in an unconnected state to a secure domain | | +| 2-a | Single-node or multi-node pairing mode – Add a node from a non-secure domain to an existing secure domain | | +| 2-b | Single-node or multi-node pairing mode – Add a node that is in an unconnected state to an existing secure domain | | +| 3 | Single-node or multi-node pairing mode – A node that was already paired is switched off and switched on again | | +| 4 | Single-node or multi-node pairing mode. Power up of a node that is configured with unconnected domain name | | +| 5 | Multi-node pairing mode – Convert a non-secure domain into a secure domain | | +| 6 | Multi-node pairing mode – Add multiple nodes from a default domain or in unconnected state into a secure domain | | +| 7-a | Fault case – Single-node or multi-node pairing mode – User sends only the PUSH_P event on one node of a non-secure domain | | +| 7-b | Fault case – Single-node or multi-node pairing mode – User sends only the PUSH_P event on one node that is in an unconnected state | | +| 8 | Fault case – Single-node or multi-node pairing mode – User sends the PUSH_P only on one node in a secure domain | | +| 9 | Fault case In single-node pairing mode – User tries to add two nodes within one pairing window | | +| 10 | PUSH_R case – User triggers PUSH_R event on a node in a secure domain | | +| 11 | Single node pairing by user confirmation | | + +#### 6.2.1.1 Use case 1-a – Convert a non-secure domain to a secure domain through generic pairing + +This use case refers to single-node pairing mode, it includes a deployment of nodes that were installed at a home as an NSD with a default non-secure domain name (after power up, the nodes may be configured to create an NSD with a default non-secure domain name). + +After this NSD is established, the user can convert the NSD to an SD by the generic pairing procedure. + +Through push button mechanism, the user adds nodes to the domain one by one. Each pairing procedure adds a node to the domain + +The user sends the PUSH\_P event to two nodes in the NSD. As a result, the two nodes establish a new SD, with a new SDN as illustrated in Figure 6-14 (Step 1). + +![Figure 6-14: Use case 1-a: Step 1 – User converts a non-secure domain to a secure domain. The diagram shows a user sending 'Push_P' signals to nodes 2 and 5 in a non-secure domain A. These nodes then form a new secure domain B. Domain A contains nodes 1, 2, 3, 4, and 5. Domain B contains nodes 2 and 5. The transition is indicated by a large arrow pointing from the initial state to the final state.](043e64d41a3368d138ace3816fd26469_img.jpg) + +**Use case 1-a: Step 1** + +The user pushes on two nodes in the non-secure domain A and they create a new secure domain B + +Node 2 and node 5 create a new secure domain B + +Push\_P Push\_P + +A - non-secure domain + +B - secure domain + +A - non-secure domain + +G.9978(11-18)\_F6-14 + +Figure 6-14: Use case 1-a: Step 1 – User converts a non-secure domain to a secure domain. The diagram shows a user sending 'Push\_P' signals to nodes 2 and 5 in a non-secure domain A. These nodes then form a new secure domain B. Domain A contains nodes 1, 2, 3, 4, and 5. Domain B contains nodes 2 and 5. The transition is indicated by a large arrow pointing from the initial state to the final state. + +**Figure 6-14 – Use case 1-a: Step 1 – User converts a non-secure domain to a secure domain** + +In order to convert the entire NSD to an SD, the user has to continue the generic pairing procedure by triggering the push button event in each node of the NSD and in one of the nodes from the SD as illustrated in Figure 6-15 (Step 2). + +![Figure 6-15: Use case 1-a: Step 2 – The user removes a node from the non-secure domain to the secure domain. The diagram shows the user sending 'Push_P' signals to node 1 in domain A and node 2 in domain B. Node 1 then joins domain B. Domain A contains nodes 1, 3, 4. Domain B contains nodes 1, 2, 5. The transition is indicated by a large arrow pointing from the initial state to the final state.](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +**Use case 1-a: Step 2** + +The user pushes on a node in the secure domain and on a node in the non-secure domain + +The node from the non-secure domain joins the secure domain + +Push\_P Push\_P + +B - secure domain + +A - non-secure domain + +B - secure domain + +A - non-secure domain + +G.9978(11-18)\_F6-15 + +Figure 6-15: Use case 1-a: Step 2 – The user removes a node from the non-secure domain to the secure domain. The diagram shows the user sending 'Push\_P' signals to node 1 in domain A and node 2 in domain B. Node 1 then joins domain B. Domain A contains nodes 1, 3, 4. Domain B contains nodes 1, 2, 5. The transition is indicated by a large arrow pointing from the initial state to the final state. + +**Figure 6-15 – Use case 1-a: Step 2 – The user removes a node from the non-secure domain to the secure domain** + +After the user runs the generic pairing procedure with the last node in the NSD, the last node is added to the SD and the NSD disappears as illustrated in Figure 6-16 (Step 3). + +![Diagram for Use case 1-a: Step 3. The left side shows a user figure between two domains. The user is sending 'Push_P' events to node 1 in 'B - secure domain' and node 3 in 'A - non-secure domain'. Domain B is an oval containing nodes 1, 2, 4, and 5. Domain A is a blue shaded oval containing node 3. Arrows point from the left state to the right state. On the right, 'A - non-secure domain is vanished' (represented by a hatched oval), and node 3 has moved into 'B - secure domain', which now contains nodes 1, 2, 3, 4, and 5.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +**Use case 1-a: Step 3** + +The user push on a node in the secure domain and on a node in the non-secure domain + +The node from the non-secure domain joins to the secure domain + +Push\_P + +Push\_P + +1 2 3 4 5 + +B + +B - secure domain + +A + +A - non-secure domain + +A - non-secure domain is vanished + +G.9978(11-18)\_F6-16 + +Diagram for Use case 1-a: Step 3. The left side shows a user figure between two domains. The user is sending 'Push\_P' events to node 1 in 'B - secure domain' and node 3 in 'A - non-secure domain'. Domain B is an oval containing nodes 1, 2, 4, and 5. Domain A is a blue shaded oval containing node 3. Arrows point from the left state to the right state. On the right, 'A - non-secure domain is vanished' (represented by a hatched oval), and node 3 has moved into 'B - secure domain', which now contains nodes 1, 2, 3, 4, and 5. + +**Figure 6-16 – Use case 1-a: Step 3 – The entire domain becomes secure domain** + +##### 6.2.1.1.1 Use case 1-b – Add a node in unconnected state to a secure domain + +This use case is a subcase of case 1-a. It refers to single-node pairing mode. + +This use case describes a node that is configured to work only in an SD and therefore it is configured with an unconnected DN. Such a node, after power up, shall stay in an UNCONNECTED state, waiting for a PUSH\_P event. During the time the node is waiting for the PUSH\_P event, it shall not join any NSD and it shall not transmit any MAP frames. + +#### 6.2.1.2 Use case 2-a – Add a node from a non-secure domain to an existing secure domain + +This use case refers to the single-node pairing mode and the multi-node pairing mode, where the user wants to add a new node to an SD. The secure domain already exists. The initial state of the joining node can be EP or DM. + +The user has to send the PUSH\_P event to a new node and the PUSH\_P to one of the nodes of the SD. On pairing completion, the new node joins the SD. See Figure 6-17. + +![Diagram for Use case 2-a. The left side shows a user figure sending 'Push_P' events to node 1 in 'B - secure domain' and to 'A new node DM' located outside the domain. Domain B contains nodes 1, 2, 3, and 4. Arrows point to the right side where 'The new node from the non-secure domain joins the secure domain'. In the final state, node 5 (the former DM node) is now inside 'B - secure domain', which contains nodes 1, 2, 3, 4, and 5.](4af57aad638888edf2062306f8a54a6c_img.jpg) + +**Use case 2-a** + +The user pushes on a node in the secure domain and on the new node + +The new node from the non-secure domain joins the secure domain + +Push\_P + +Push\_P + +1 2 3 4 5 + +B + +B - secure domain + +A new node DM + +G.9978(11-18)\_F6-17 + +Diagram for Use case 2-a. The left side shows a user figure sending 'Push\_P' events to node 1 in 'B - secure domain' and to 'A new node DM' located outside the domain. Domain B contains nodes 1, 2, 3, and 4. Arrows point to the right side where 'The new node from the non-secure domain joins the secure domain'. In the final state, node 5 (the former DM node) is now inside 'B - secure domain', which contains nodes 1, 2, 3, 4, and 5. + +**Figure 6-17 – Use case 2-a: A new node is added to a secure domain** + +##### 6.2.1.2.1 Use case 2-b – Add a node that is in an unconnected state to an existing secure domain + +This use case refers to single-node mode and multi-node pairing mode. It is subcase of case 2-a. + +The use case describes an SD where the user wants to add a new node that is in an unconnected state. A node is in an unconnected state when it is configured with an unconnected domain name. The user has to trigger the PUSH\_P event in the new node and in one of the nodes in the SD. On pairing completion, the new node is added to the SD. See Figure 6-18. + +![Diagram illustrating Use case 2-a: A new node in an UNCONNECTED state is added to a secure domain. The diagram shows a 'B - secure domain' containing nodes 1, 2, 3, and 4. A user triggers the PUSH_P event on node 1 and on a new node (labeled 'I') in an idle state. The new node then joins the secure domain, becoming node 5.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +The diagram, titled "Use case 2-a", illustrates the process of adding a new node to a secure domain. On the left, a "B - secure domain" is shown as a purple oval containing four nodes: 1 (highlighted in yellow), 2, 3, and 4. A user icon is shown pushing a button labeled "Push\_P" which points to node 1. Another "Push\_P" button points to a new node labeled "I" (highlighted in yellow) outside the domain, with the text "A new node in idle state" below it. An arrow points from the secure domain to the right, where the same "B - secure domain" now contains nodes 1, 2, 3, 4, and 5 (highlighted in yellow). Text above this domain states "The new node from the unsecure domain joins to the secure domain". A small code "G.9978(11-18)\_F6-18" is in the bottom right corner. + +Diagram illustrating Use case 2-a: A new node in an UNCONNECTED state is added to a secure domain. The diagram shows a 'B - secure domain' containing nodes 1, 2, 3, and 4. A user triggers the PUSH\_P event on node 1 and on a new node (labeled 'I') in an idle state. The new node then joins the secure domain, becoming node 5. + +**Figure 6-18 – Use case 2-b: A new node in an UNCONNECTED state is added to a secure domain** + +#### 6.2.1.3 Use case 3 – A node that was already paired is switched on again + +This use case refers to the single-node mode and to the multi-node pairing mode. + +After power up, the powering-up node shall join the secure domain it was member of before power-down. + +A node that is member of an SD (after successful pairing) that is turned off and then turned on again shall follow the default G.hn procedure for registration and authentication (clauses 8.6.1.1 and 9.2.2, Authentication to the domain of [ITU-T G.9961]). + +#### 6.2.1.4 Use case 4 – Power up of a node with an unconnected domain name + +This use case is applicable to the single-node mode and to the multi-node pairing mode. + +This case describes a node that is configured with an unconnected domain name. In this case, such a node is allowed to operate only within an SD. Such a node, after power up, shall stay in an UNCONNECTED state, waiting for a PUSH\_P event. During the time that this node is waiting for the PUSH\_P event, it shall not join any domain and it shall not become a DM. + +#### 6.2.1.5 Use case 5 – In multi-node pairing mode, convert a non-secure domain into a secure domain + +This use case refers to the multi-node pairing mode. All nodes that detect the PUSH\_P event will establish a secure domain. + +In this use case, in order to convert an NSD to an SD, the user has to trigger the PUSH\_P event in all nodes in the NSD within one pairing window. + +One of the nodes becomes the DM of a new established secured domain and the other nodes join the SD as illustrated in Figure 6-19. + +![Figure 6-19: Use case 5 diagram showing the conversion of a non-secure domain to a secure domain.](5414f65867392f05ba0063b208eeb5e1_img.jpg) + +**Use case 5** + +The user sends the PUSH\_P event of all the nodes of the non-secure domain A + +The domain is converted to be secure domain with new domain name + +A - non-secure domain + +B - secure domain + +A - non-secure domain is vanished + +G.9978(11-18)\_F6-19 + +The diagram illustrates 'Use case 5'. On the left, a non-secure domain 'A' (blue oval) contains five nodes numbered 1 to 5. A user icon is shown sending 'PUSH\_P' events (represented by four overlapping circles) to all five nodes. An arrow points to the right, where domain 'A' is shown as a faded, hatched oval with the text 'A - non-secure domain is vanished'. Above it, a new secure domain 'B' (purple oval) contains the same five nodes (1, 2, 3, 4, 5), now highlighted in yellow. The text 'The domain is converted to be secure domain with new domain name' is present. The label 'B - secure domain' is below the new domain. + +Figure 6-19: Use case 5 diagram showing the conversion of a non-secure domain to a secure domain. + +**Figure 6-19 – Use case 5: In multi-node pairing mode convert a non-secure domain to a secure domain** + +#### 6.2.1.6 Case 6 – Multi-node pairing mode: Add multiple nodes from a default domain or in an unconnected state + +This use case refers to the multi-node pairing mode. + +All the nodes from the non-secure domain or in unconnected state that detect the PUSH\_P event shall join the secure domain. + +A user triggers the PUSH\_P event in a node of the SD and, within one pairing window, triggers the PUSH\_P event in several nodes of an NSD or in an UNCONNECTED state. All the nodes from the NSD where a PUSH\_P event was triggered shall join the SD. See Figure 6-20. + +![Figure 6-20: Use case 6 diagram showing multi-node generic pairing.](24c9e038a791677ed33100667b64f7e6_img.jpg) + +**Use case 6** + +The user pushes on a node in a secure domain and on some nodes from a non-secure domain + +The triggered nodes from the non-secure domain joins to the secure domain + +B - secure domain + +A - non-secure domain + +G.9978(11-18)\_F6-20 + +The diagram illustrates 'Use case 6'. On the left, a secure domain 'B' (purple oval) contains nodes 1, 2, 3, and 4. A non-secure domain 'A' (blue oval) contains nodes 1, 2, 3, 4, and 5. A user icon is shown sending 'Push\_P' events (represented by three overlapping circles) to node 1 in domain 'B' and to nodes 2, 4, and 5 in domain 'A'. Arrows point to the right. Domain 'B' now contains nodes 1, 2, 3, 4, 5, 6, and 7, with nodes 5, 6, and 7 highlighted in yellow. The text 'The triggered nodes from the non-secure domain joins to the secure domain' is present. Domain 'A' now contains only nodes 1 and 3. The label 'B - secure domain' is below the updated domain, and 'A - non-secure domain' is below the remaining nodes. + +Figure 6-20: Use case 6 diagram showing multi-node generic pairing. + +**Figure 6-20 – Use case 6 – Multi-node generic pairing** + +#### 6.2.1.7 Fault case 7-a – PUSH\_P event on only one node of a non-secure domain + +This fault case is applicable to the single-node mode and to the multi-node pairing mode. The node stays in a non-secure domain. + +In this fault case, the user triggers the PUSH\_P event on only one node of an NSD. In this fault case, nothing should happen. + +This case is considered as a faulty case, because the user does not complete the pairing procedure. In this case, after the pairing window has expired, the node shall ignore the PUSH\_P event and shall return to its previous state (i.e., the state it was before the PUSH\_P event). See Figure 6-21. + +![Diagram for Fault case 7-a showing a user triggering a PUSH_P event on a node in a non-secure domain, which then returns to its previous state after the pairing window expires.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +The diagram is titled "Fault case 7-a". It shows a user icon with a "Push\_P" callout pointing to node 2 in a group of five nodes (1, 2, 3, 4, 5) labeled "A" inside a blue oval. Below the oval is the text "A - non-secure domain". An arrow labeled "After pairing window expired" points to the same group of nodes, where node 2 is no longer highlighted. The text "G.9978(11-18)\_F6-21" is in the bottom right corner. + +Diagram for Fault case 7-a showing a user triggering a PUSH\_P event on a node in a non-secure domain, which then returns to its previous state after the pairing window expires. + +Figure 6-21 – Fault case 7-a + +##### 6.2.1.7.1 Fault case 7-b – PUSH\_P event on only one node that is in an unconnected state + +This fault case is a subcase of 5-a. It refers to a case where the user triggers the PUSH\_P event on only one node that is in an unconnected state. After the pairing window duration, the node stays in an unconnected state. + +In such a scenario nothing should happen. + +This case is considered as a faulty case because the user does not complete the pairing procedure. In this case, the node shall ignore the PUSH\_P event and return to its previous state before the PUSH\_P event was triggered (i.e., as a node in an unconnected state waiting for a PUSH\_P event). See Figure 6-22. + +![Diagram for Fault case 7-b showing a user triggering a PUSH_P event on a node in an unconnected state, which remains in that state after the pairing window expires.](f64e1e0997695248c0cd4122c5b1a170_img.jpg) + +The diagram is titled "Use case 7-b". It shows a user icon with a "Push\_P" callout pointing to a yellow oval labeled "I". Below the oval is the text "A node in unconnected state". A long arrow labeled "After pairing window expired the node is again in Unconnected state" points to the same yellow oval labeled "I". The text "G.9978(11-18)\_F6-22" is in the bottom right corner. + +Diagram for Fault case 7-b showing a user triggering a PUSH\_P event on a node in an unconnected state, which remains in that state after the pairing window expires. + +Figure 6-22 – Fault case 7-b + +#### 6.2.1.8 Fault case 8 – PUSH\_P event on only one node in a secure domain + +This use case refers to the single-node mode and to the multi-node pairing mode. + +The node will open or ask the DM to open the pairing window, and then close it after the pairing window duration with no other action. + +In this case, a PUSH\_P event is triggered on only one node in an SD, without completing any pairing procedure. In this case, the triggered node shall inform its DM about the PUSH\_P event without any change in the domain. See Figure 6-23. + +![Diagram for Fault case 8 showing a user triggering a PUSH_P event on one node in a secure domain, which then expires without joining.](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +The diagram illustrates Fault case 8. On the left, a user icon is shown with a 'Push\_P' button pointing to node 2 within a purple oval labeled 'A - secure domain'. Nodes 1, 3, 4, and 5 are also in the domain. An arrow labeled 'After pairing window expired' points to the right side, where the same domain 'A' is shown with node 2 no longer highlighted, indicating the pairing window has closed without a change in the domain. + +G.9978(11-18)\_F6-23 + +Diagram for Fault case 8 showing a user triggering a PUSH\_P event on one node in a secure domain, which then expires without joining. + +Figure 6-23 – Fault case 8 + +#### 6.2.1.9 Fault case 9 – User tries to add two nodes within one pairing window + +This use case refers only to the single-node pairing mode. + +Only one of the nodes from the non-secure domain shall join the secure domain, and the other node shall not create its own secure domain and shall return to its previous state before the PUSH\_P event. + +In this case, the user triggers the PUSH\_P event in two nodes that are in an NSD and in one node of an SD. The first node that successfully completed the pairing procedure shall join the SD. The second node shall be rejected by the SD and shall return to its previous state before the PUSH\_P event. See Figure 6-24. + +![Diagram for Fault case 9 showing a user trying to add two nodes from a non-secure domain to a secure domain, where only one succeeds.](80ec3bf791fd8eb41f73a420c2122529_img.jpg) + +The diagram illustrates Fault case 9. A user icon is shown with two 'PUSH\_P' buttons. One button points to node 1 in a purple oval labeled 'B - secure domain'. The other button points to node 4 in a blue oval labeled 'A - non-secure domain'. Text above the user says: 'The user wants to add non secure nodes to a secure domain. He pushes on two non-secure nodes and on one node of a secure domain'. An arrow from node 1 points to a new state where node 5 is highlighted in the purple domain 'B', with text 'Node 2 of the non-secure domain joins to the secure domain'. Another arrow from node 4 points to a new state of the blue domain 'A' where node 4 is not highlighted, with text 'Node 4 is rejected and stays non-secure'. + +G.9978(11-18)\_F6-24 + +Diagram for Fault case 9 showing a user trying to add two nodes from a non-secure domain to a secure domain, where only one succeeds. + +Figure 6-24 – Fault case 9 + +#### 6.2.1.10 Use case 10 – User triggers PUSH\_R event on a node in a secure domain + +In this case, the user triggers the PUSH\_R event on a node that is in an SD network. + +After triggering the PUSH\_R event, the node shall resign from the domain, and move into unconnected state. + +When a node that belongs to an SD receives a PUSH\_R event, it shall initiate a self-resignation procedure from its current domain and, without waiting for any confirmation from the DM, it shall move to IDLE state and set its DN and PW to the default values. + +#### 6.2.1.11 Use case 11 – Single node pairing by user confirmation + +In this case, when a new node first powers on, it will broadcast a message to notify the network of its existence. When DM receives the message, it will trigger a Flash-E event, such as light flashing on the DM, asking whether the new node is allowed to join the secure domain. If the user chooses to agree to it, the user will push a button, and the new node will join the secure domain. + +![Diagram illustrating the Flash-E event to notify the existence of a new node and the user's decision to allow it to join the secure domain.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +The diagram illustrates the process of a new node joining a secure domain. On the left, a 'B - secure domain' contains nodes 1, 2, 3, and 4. Node 1 is highlighted in yellow. A user icon is shown with two circular buttons labeled 'Flash\_E' and 'Push\_P'. An arrow points from the user's 'Flash\_E' button to node 1. Above the user, text reads: 'The user receives notification that new node 5 exists by Flash-E event'. Below the domain, a new node labeled '5' is shown with the text 'A new node power on'. An arrow points from node 5 towards the domain. On the right, the domain 'B - secure domain' now contains nodes 1, 2, 3, 4, and 5. Node 5 is highlighted in yellow. Above this domain, text reads: 'The new node join in B - secure domain'. A large arrow points from the left domain to the right domain. In the bottom right corner of the diagram, there is a small label: 'G.9978(11-18)\_F6-25'. + +Diagram illustrating the Flash-E event to notify the existence of a new node and the user's decision to allow it to join the secure domain. + +**Figure 6-25 – Flash\_E event to notify the existence of a new node. The user chooses whether allow it join in secure domain by PUSH\_P event** + +NOTE – Nodes in the neighbourhood may also receive the notification message and trigger the Flash-E event. The vendor should implement vendor discretionary means to avoid security issues related to this. + +### 6.2.2 Secure admission by generic pairing + +A generic pairing mechanism enables the user to convert an NSD to an SD or to add one or more unconnected nodes to an SD by a simple push event operation, without the need for any computer communication with the nodes in the domain. + +Both single-node pairing and multi-node pairing modes shall be supported. A domain shall operate in only one of these, according to its configuration. Single-node pairing is specified in clause 6.2.2.1 and multi-node pairing is specified in clause 6.2.2.2. See Table 6-10. + +**Table 6-10 – System parameters for the pairing mechanism** + +| Parameter | Description | Medium | | | | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------| +| | | Power-line baseband | Coax baseband (BB) | Coax radio frequency (RF) | Phone line | +| T PAIRING (Note) | Pairing window that starts after a PUSH_P event. During this period, the DM shall confirm the registration pairing request | 60-300 s | 60-300 s | 60-300 s | 60-300 s | +| T EP_INTERVAL | The interval that a joining node is acting as an EP trying to pair with a secure domain until it shall alternate with a temporary domain master | 1 s | 1 s | 1 s | 1 s | +| T TMPDM_INTERVAL | Period of time that a joining node during a pairing procedure shall act as temporary domain master before it alternates with an EP node for scanning | Random value in the range 4-8 s | Random value in the range 4-8 s | Random value in the range 4-8 s | Random value in the range 4-8 s | + +NOTE – The value of $t_{\text{PAIRING}}$ is vendor discretionary and is usually fixed by an external entity (e.g., HomeGrid Forum, [b-HomeGrid]). + +#### 6.2.2.1 Single-node pairing procedure description + +The single-node pairing procedure is used to convert an NSD to an SD or to add an unconnected node or a node from an NSD to an SD. In order to convert an NSD to an SD, the user should trigger the PUSH\_P event in two nodes of the NSD within the $t_{\text{PAIRING}}$ time period. During the pairing procedure, one of the two pairing nodes should become the DM of the new established SD and the other should register with this DM and become a member of this new established SD. + +In order to add a node that is not in an SD to an existing SD, the user should trigger the PUSH\_P event in the non-secure node and in one of the nodes of the SD. + +A node that is not in an SD that detects a PUSH\_P event cannot know in advance if it should register in an existing SD or if it should establish a new SD. Therefore, on detection of the PUSH\_P event, it should try to pair with any detected SD for $t_{\text{PAIRING}}$ time. After this time expires, it shall establish an SD, but it shall also temporally monitor the network transmissions looking for already established SDs until successful completion of the pairing procedure or expiry of $t_{\text{PAIRING}}$ . During this period, the DM acts therefore as a "temporary DM". + +In order to establish an SD, the node shall create a random SDN and it shall transmit MAPs to enable any potential node to pair with it. In parallel with acting as a temporary DM, the node shall scan for MAPs of other SDs and may decide to register in another domain as an EP node. + +If the node tries only to register in an SD and it is actually the case where the user wishes to establish an SD, both triggered nodes would scan for MAPs of an SD without having any DM transmitting MAPs of an SD and able to accept their registration request. For this reason, only one of the triggered nodes should become a DM. + +The temporary DM behaviour can be implemented either by making use of the $t_2$ timing described in clause 8.6.6.1.1 of [ITU-T G.9961] or by implementing a mechanism to alternate between the DM and EP states described in clause 6.2.2.1.1.1. + +##### 6.2.2.1.1 Alternating between domain master and endpoint states + +Due to the fact that there is no arbitrary way to define which of the two triggered nodes shall be the DM of the new SD, each node should alternate on detection of a PUSH\_P event between: + +- acting as a temporary DM to enable the other node to pair with it; +- registering in any detected SD. + +This behaviour should last until successful completion of the pairing procedure or expiry of $t_{PAIRING}$ . + +The temporary DM shall act alternately as a temporary DM for several seconds and as a registering node for another period of time. In order to ensure that during the time that one of the pairing nodes is acting as a temporary DM the other node is in the phase of scanning for an SD, the following timing scheme shall be used. + +The period of time that the pairing node is acting as a temporary domain shall be longer than the period of time that it is acting as an EP node in the scanning phase. The period of time that a node shall act as a temporary DM shall be randomly selected within the range from 1 s to 4 s while the time that a node shall be in a scanning state as registering EP node shall be fixed at 1 s. This way, the scanning node will always detect the second pairing node in its temporary DM state as illustrated in following time schema. The pairing opportunity arrows in Figure 6-26 illustrate the opportunity that each registering node has to detect the temporary DM. + +![Timing scheme for temporary domain master and endpoint state alternation (Figure 6-26).](875c6f4f441fdd3ca7e1908fd1582983_img.jpg) + +The diagram shows two horizontal timelines for 'Pairing node 1' and 'Pairing node 2'. Both nodes start with a 'Push\_P event' (indicated by a red 'P' in a box). Node 1 initially acts as an EP, then alternates between 'TMP DM' and 'EP' states. Node 2 initially acts as a 'TMP DM', then alternates between 'EP' and 'TMP DM' states. Red double-headed arrows labeled 'Pairing opportunity' connect the 'EP' state of one node to the 'TMP DM' state of the other, showing multiple chances for them to meet. The diagram is labeled 'G.9978(11-18)\_F6-26' in the bottom right. + +Timing scheme for temporary domain master and endpoint state alternation (Figure 6-26). + +**Figure 6-26 – Timing scheme for temporary domain master and endpoint state alternation** + +Figure 6-27 illustrates a pairing between node 2 and node 1 that was successfully completed when node-2 was acting as a temporary DM and node-1 was acting as an EP. After the pairing is successfully completed, both nodes stop alternating and the temporary DM continues as a temporal DM while the EP continues as an EP node. + +![Timing scheme for temporary domain master and endpoint state alternation after successful pairing (Figure 6-27).](05d8710f69c476939295486ab1440350_img.jpg) + +This diagram shows the state after a successful pairing. 'Pairing node 1' (EP) and 'Pairing node 2' (TMP DM) have completed their initial alternating phases. Node 1 remains in the 'EP' state, and Node 2 remains in the 'TMP DM' state. A single red double-headed arrow labeled 'Pairing opportunity' is shown between them, indicating the successful pairing. The diagram is labeled 'G.9978(11-18)\_F6-27' in the bottom right. + +Timing scheme for temporary domain master and endpoint state alternation after successful pairing (Figure 6-27). + +Scenario of success pairing between node 1 as EP and node 2 as TMP DM. +After successful registration node 2 continue to be TMPDM and node 1 continue as EP + +**Figure 6-27 – Timing scheme for temporary domain master and endpoint state alternation** + +##### 6.2.2.1.2 Example in a state machine of a PUSH\_P event in single-node pairing mode + +Figure 6-28 illustrates the state machine of a node that is in unconnected mode or a member of an NSD after a PUSH\_P event is triggered in single-node pairing mode. + +The procedure in this example makes use of the alternation between DM and EP states described in clause 6.2.2.1.1. + +![State machine diagram for a node triggered by a PUSH_P event in single-node pairing mode. The diagram shows 9 states (A-I) and their transitions based on events like PUSH_P, T_PAIRING expiration, T_EP expiration, T_TMPDM expiration, and successful pairings with SD, PSDM, or EP.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +stateDiagram-v2 + [*] --> A + A --> B: PUSH_P event + B --> A: T_PAIRING expiration + B --> F: T_EP expiration + B --> C: Pairing completed successfully with PSDM + B --> E: Pairing completed successfully with SD + F --> A: T_PAIRING expiration + F --> G: Pairing completed successfully with EP + F --> H: T_TMPDM expiration + G --> A: EP re-registration timeout expired + G --> H: T_PAIRING expiration + H --> I: The previous EP re-registered with the PSDM + H --> A: T_PAIRING expiration + I --> A: T_PAIRING expiration + C --> A: PSDM rejects the pairing request due to one node has already paired + C --> E: Pairing completed successfully with PSDM + C --> B: T_PAIRING expiration + E --> A: T_PAIRING expiration + E --> B: Pairing completed successfully with SD + E --> C: Pairing completed successfully with SD + E --> I: T_PAIRING expiration + +``` + +EP – End point node + DM – Domain master + NSD – Non secure domain + SD – Secure domain + TMPDM – Temporal DM + PSDM – Permanent secure DM + +G.9978(11-18)\_F6-28 + +State machine diagram for a node triggered by a PUSH\_P event in single-node pairing mode. The diagram shows 9 states (A-I) and their transitions based on events like PUSH\_P, T\_PAIRING expiration, T\_EP expiration, T\_TMPDM expiration, and successful pairings with SD, PSDM, or EP. + +**Figure 6-28 – State machine for a node triggered by a PUSH\_P event in the single-node pairing mode** + +The following list describes each state of the state machine illustrated in Figure 6-28 and the events that make the node transitions from one state to the next according to the event. + +- A. **Unconnected mode or node in an NSD** – This state is that for a node that is in an unconnected state or for a node that is in an NSD. After a PUSH\_P event, the node changes to state B. + +- B. **EP tries pairing with any SD** – In this state, the EP node scans for any SD for a TEP interval (1 s). If it detects a secure DM, it shall try to pair with the DM of the SD. One of four events can make the node leave this state. +- 1) **TEP expiry** – The TEP interval has expired. On this event, the EP stops acting as an EP and starts acting as a temporary DM in the state: **F. (TMPDM)**. + - 2) **Pairing successfully completed with a TMPDM (temporal domain master)** – The EP node successfully completed a pairing procedure with a temporary DM. This event transitions the EP to state C. [EP tries pairing only with a permanent secure domain master (PSDM)]. + - 3) **Pairing successfully completed with a PSDM** – The EP successfully completed a pairing procedure with a PSDM. This event transitions the EP to the final state: EP in an SD. + - 4) **TPAIRING expiry** – the timer that counts the pairing windows has expired. This event transitions the EP to state A where it was before the PUSH\_P event. This means that the pairing procedure is ended without any successful pairing. + +Figure 6-29 illustrates the algorithm of the EP in state B. + +![Flowchart illustrating the algorithm for state B: Endpoint tries pairing with any secure domain. The process starts in State A and transitions to State B via Push_P_EV. Inside State B, it sets timers, scans for a secure domain MAP, and handles pairing registration. Transitions lead to State F (TMPDM), State C (paired with TMPDM), or State E (permanent secure domain).](145d00f59802048185303f15937ea65c_img.jpg) + +``` + +graph TD + StateA["State A. +Node in a non secure domain or +in IDLE state"] -- "Push_P_EV" ---> B_Entry(( )) + subgraph StateB [STATE B] + B_Entry --> SetPT["Set PAIRING-Timer to TPAIRING"] + SetPT --> SetET["Set EP-Timer to TEP-Interval"] + SetET --> Scan["Scan for a secure domain MAP until secured +MAP is received or EP-Timer is expired"] + Scan --> ET_Expired{Is EP-Timer expired} + ET_Expired -- Yes --> StateF + ET_Expired -- No --> SendReq["Send pairing registration request to the detected DM"] + SendReq --> PosResp{Is +positive pairing registration +response received} + PosResp -- Yes --> DMIsPSDM{Is the DM is PSDM} + PosResp -- No --> PT_Expired{Is +PAIRING-Timer expired} + DMIsPSDM -- Yes --> StateE + DMIsPSDM -- No --> StateC + PT_Expired -- Yes --> StateA + PT_Expired -- No --> Scan + end + StateF["State F +TMPDM"] -- "T_TMPDM Timeout" --> B_Entry + StateC["State C. +Node is EP after successfully +paired with temporal domain +master and now it is +trying to pair with a PSDM"] + StateE["State E. +Node becomes an +EP in a permanent +secure domain"] + style StateB fill:#d9ead3,stroke:#333,stroke-width:1px + style StateE fill:#93c47d,stroke:#333,stroke-width:1px + +``` + +Flowchart illustrating the algorithm for state B: Endpoint tries pairing with any secure domain. The process starts in State A and transitions to State B via Push\_P\_EV. Inside State B, it sets timers, scans for a secure domain MAP, and handles pairing registration. Transitions lead to State F (TMPDM), State C (paired with TMPDM), or State E (permanent secure domain). + +Figure 6-29 – Algorithm for state B: Endpoint tries pairing with any secure domain + +- C. **EP tries pairing only with a PSDM** – In this state, the EP is already paired with the temporary DM and acts as a normal registered node, including the execution of the authentication procedure specified in [ITU-T G.9961]. During this state, the EP shall continue to try to pair with any other detected PSDM in order to avoid fault case 9, when the user wants to add a node to an SD, but it pushes buttons on two nodes that are not in the SD and on one node from the SD. In such a case, the node shall return to state A. On one of the following four events, the node may transition from this state to another state. +- 1) **Pairing successfully completed with a PSDM** – The EP node successfully completed a pairing procedure with a PSDM. This event transitions the EP to final state E. The EP is in an SD. + - 2) **T\_PAIRING expiry** – The timer that counts the pairing windows has expired. This event transits the EP to intermediate state D. The EP tries to re-register with a TMPDM. + - 3) **The PSDM rejected the pairing due to one node already being paired** – The responding PSDM rejects the pairing request because it had just closed its pairing window since it had successfully completed the pairing procedure with another node. (A PSDM shall send this rejection when it receives a pairing request within the last T\_PAIRING but had already paired successfully with another node.) + +Figure 6-30 illustrates the algorithm of the EP in state C. + +![Flowchart for State C: EP tries pairing only with a permanent secure domain master. The process starts at State B, transitions to State C upon successful pairing with TMPDM. Inside State C, it scans for a secure domain MAP. If detected (not TMPDM), it sends a registration request. If rejected due to another pairing, it checks if the DM is PSDM. If Yes, it becomes an EP in a secure domain (State E). If No, it checks if the PAIRING-Timer expired. If Yes, it re-registers with the TMPDM (State D). If No, it loops back to scanning. If a positive response is received, it transitions to State A.](77959075c823bb5169480d7b8ff82a63_img.jpg) + +``` + +graph TD + StateB[State B] -- "Pairing with TMPDM is successfully completed" --> Entry(( )) + subgraph StateC [STATE C] + Entry --> Scan[Scan for secure domain MAP until secured MAP is received or PAIRING-Timer is expired] + Scan --> IfMapDetected{If A MAP of secure domain is detected (not the TMPDM)} + IfMapDetected -- No --> Join(( )) + IfMapDetected -- Yes --> SendRequest[Send pairing registration request to the detected DM] + SendRequest --> IsPositiveResponse{Is positive pairing registration response received} + IsPositiveResponse -- Yes --> IsPSDM{Is the DM is PSDM} + IsPositiveResponse -- No --> IsRejected{Is Rejected due to another pairing is JUST completed} + IsRejected -- Yes --> IsPSDM + IsRejected -- No --> IsTimerExpired{Is PAIRING-Timer expired} + IsTimerExpired -- Yes --> Exit[ ] + IsTimerExpired -- No --> Join + IsPSDM -- Yes --> Exit + end + Exit --> StateD[State D. Node re-register with the TMPDM] + Exit --> StateA[State A] + Exit --> StateE[State E. Node becomes an EP in a secure domain] + style Entry fill:red,stroke:none + style Join fill:none,stroke:none + style Exit fill:none,stroke:none + style StateE fill:#90EE90,stroke:none + +``` + +G.9978(11-18)\_F6-30 + +Flowchart for State C: EP tries pairing only with a permanent secure domain master. The process starts at State B, transitions to State C upon successful pairing with TMPDM. Inside State C, it scans for a secure domain MAP. If detected (not TMPDM), it sends a registration request. If rejected due to another pairing, it checks if the DM is PSDM. If Yes, it becomes an EP in a secure domain (State E). If No, it checks if the PAIRING-Timer expired. If Yes, it re-registers with the TMPDM (State D). If No, it loops back to scanning. If a positive response is received, it transitions to State A. + +**Figure 6-30 – Algorithm for state C: EP tries pairing only with a permanent secure domain master** + +- D. **EP re-registers with a TMPDM** – In this state, the EP node shall try to re-register with its original TMPDM that it had already paired with in event B 2). There are two events that trigger a transition from this state, as follows. +- 1) **The EP re-registers successfully with its TMPDM** – This event shall trigger a transition of the EP to final state E. + - 2) **The EP fails to re-register with its TMPDM** – The EP retries to re-register with its TMPDM expired (the TMPDM is off). This event shall abort the pairing procedure and transition the EP to final state A. + +See Figure 6-31. + +![Flowchart for State D: Endpoint re-registers with a temporal domain master](befcd1fc29f753206dbe01036a9dca5e_img.jpg) + +**Figure 6-31 – Algorithm for state D: Endpoint re-registers with a temporal domain master** + +``` + +graph TD + StateC[State C.] -- "T_PAIRING Expired" --> StateD + subgraph StateD [STATE D] + StartD(( )) --> SetTimer[Set T_Re-Registration Timer to T_Re-Registration_TO] + SetTimer --> Sync[Synchronize with the TMPDM and transmit send Re-Registration request to TMPDM] + Sync --> CheckResp{Is positive Re-Registration response received} + CheckResp -- No --> CheckTimer{T_Re-Registration Timer is expired} + CheckTimer -- No --> Sync + CheckTimer -- Yes --> StateA[State A] + CheckResp -- Yes --> StateE[State E. Node becomes an EP in a permanent secure domain] + end + +``` + +Flowchart for State D: Endpoint re-registers with a temporal domain master + +E. **EP in SD** – This is a final state for the node. In this state, the node has finally completed the pairing procedure and has become a member of an SD. In this state, the node starts the authentication procedure. + +F. **TMPDM** – In this state the EP starts acting as a temporary DM for a period of time of a TMP\_Interval. The first time that the EP transits to this state it shall generate a random DN and a PW. One of the following four events make the node transition from this state. + +- 1) **T\_TMPDM expiry** – The timer that counts the interval that the node shall act as a temporary DM has expired. On this event, the temporary DM shall stop acting as a temporary DM and switch to act as an EP node in state B. (EP tries pairing with any SD.) +- 2) **Pairing successfully completed with an EP** – An EP node has successfully completed the pairing procedure with this temporary DM. This event makes the temporary DM transition to state G. TMPDM after successful pairing. +- 3) **T\_PAIRING expiry** – The timer that counts the pairing windows has expired. This event shall abort the pairing procedure and make the node transition to state A where it was before the PUSH\_P event (unconnected mode or a node in an NSD). + +34 Rec. ITU-T G.9978 (11/2018) + +Figure 6-32 illustrates the algorithm of the TMPDM in state F. + +![Flowchart of the TMPDM algorithm in state F. The process starts at State B, enters State F (TMPDM), becomes a Temporal DM, checks if the domain name is NDDN, randomizes it if not, sets a timer, transmits MAPs, checks for a registration request, and either succeeds (State G) or fails (State A) based on timer and window expiration.](70a863dc6cd47bac82c12162a9479aac_img.jpg) + +``` + +graph TD + StateB[State B.] -- "T_EP_Interval time out" --> Entry(( )) + subgraph STATE_F [STATE F +TMPDM] + Entry --> BecomeDM[Become a Temporal DM] + BecomeDM --> IsNDDN{Is +domain name is NDDN} + IsNDDN -- No --> RandomizeNDDN[Randomize a NDDN (non default domain name)] + IsNDDN -- Yes --> Join(( )) + RandomizeNDDN --> Join + Join --> RandomizeTimer[Randomize T_TMPDM_interval (1-4 seconds) +Set TMP_DM_timer to T_TMPDM_interval] + RandomizeTimer --> Join2(( )) + Join2 --> TransmitMAPs[Transmit MAPs with the NDDN and try to +receive registration request frames] + TransmitMAPs --> IsRequest{Is +pairing registration +request received} + IsRequest -- Yes --> Success[Send positive Reg-Rsp with +TMPDM indication and +the password +Store the EP information +Store the NDDN and password] + IsRequest -- No --> IsTimerExpired{Is +TMP_DM_timer +expired} + IsTimerExpired -- Yes --> Exit(( )) + IsTimerExpired -- No --> IsWindowExpired{Is +TPAIRING window +expired} + IsWindowExpired -- Yes --> Exit + IsWindowExpired -- No --> TransmitMAPs + end + Exit --> StateG[State G +TMPDM after +successful pairing] + Exit --> StateA[State A +IDLE or NSD] + Exit --> StateB + +``` + +The flowchart illustrates the algorithm for the TMPDM in state F. It begins at State B, where a 'T\_EP\_Interval time out' event triggers the transition to State F (TMPDM). Inside State F, the first step is to 'Become a Temporal DM'. A decision diamond asks 'Is domain name is NDDN'. If 'No', it proceeds to 'Randomize a NDDN (non default domain name)'. If 'Yes', it skips this step. Both paths lead to a junction point. The next step is 'Randomize T\_TMPDM\_interval (1-4 seconds)' and 'Set TMP\_DM\_timer to T\_TMPDM\_interval'. This is followed by another junction point. The next step is 'Transmit MAPs with the NDDN and try to receive registration request frames'. A decision diamond asks 'Is pairing registration request received'. If 'Yes', it proceeds to 'Send positive Reg-Rsp with TMPDM indication and the password', 'Store the EP information', and 'Store the NDDN and password', leading to State G. If 'No', it proceeds to a decision diamond 'Is TMP\_DM\_timer expired'. If 'Yes', it exits State F. If 'No', it proceeds to a decision diamond 'Is TPAIRING window expired'. If 'Yes', it exits State F. If 'No', it loops back to the 'Transmit MAPs' step. Upon exiting State F, the algorithm can lead to State G (TMPDM after successful pairing) or State A (IDLE or NSD), and it also loops back to State B. + +Flowchart of the TMPDM algorithm in state F. The process starts at State B, enters State F (TMPDM), becomes a Temporal DM, checks if the domain name is NDDN, randomizes it if not, sets a timer, transmits MAPs, checks for a registration request, and either succeeds (State G) or fails (State A) based on timer and window expiration. + +G.9978(11-18)\_F6-32 + +Figure 6-32 – Algorithm for state F. TMPDM + +G. **TMPDM after successful pairing** – In this state, the temporary DM continues to act as a temporary DM until T\_PAIRING expiry. The temporary DM shall allocate a dedicated transmission opportunity (TXOP) for the registered EP for scanning and pairing with other potential DMs. The following events shall make the node transition from this state. + +- 1) **Re-registration event** – The EP successfully completed the re-registration procedure. The EP completed its pairing procedure and therefore the temporary DM shall be converted to a PSDM. +- 2) **T\_PAIRING expiry** – The timer that counts whether the pairing window has expired. This event makes the TMPDM transition to the intermediate state **H. PSDM conditional**. + +H. **PSDM conditional** – This is an intermediate state in which the temporary DM becomes a conditioned PSDM, because it depends whether the EP that paired with it successfully in state F is still relevant and this EP did not pair meanwhile with another PSDM. In this state, the DM shall use the DN that it previously generated in state F. (TMPDM). The DM shall set a timer T\_Re\_Register that counts the timeout until the EP re-register with the DM. The timeout shall be specified according to the time of the pairing procedure that was executed in state F as determined by the formula: + +$$\text{timeout} = \text{T\_PAIRING} - (\text{Pairing\_t} - \text{Start\_window\_t}) + 1 \text{ s}$$ + +Pairing\_t is the time when the pairing procedure with the EP is started. Start\_window\_t is the time when the node was triggered by a PUSH\_P event. The following events shall transition the node from this state. + +- 1) **The EP re-registered with the PSDM** – The EP that paired previously with the DM while it was in state F has re-registered with the DM. This event indicates to the DM that the EP has successfully completed a pairing procedure with it. Therefore the conditioned PSDM can be a PSDM. This event transitions the node to a final state **I. PSDM**. +- 2) **EP re-registration timeout expired** – This event occurs when the timer for re-registration of the EP with the conditional PSDM has expired. This can happen, for example, if the EP is successfully paired with the actual PSDM. + +See Figure 6-33. + +![Flowchart for State H conditional PSDM algorithm. It starts at State G, transitions to State H on T_PAIRING expiration. Inside State H, it becomes a conditional PSDM, sets a timer, and continues active. If a re-registration request is received, it sends a positive response and goes to State I. If the timer expires, it goes to State A. Otherwise, it loops back to continue active.](798679874d1c29f8343506a156c79d7e_img.jpg) + +``` + +graph TD + StateG[State G.] -- "T_PAIRING expiration" --> EntryH(( )) + subgraph StateH [STATE H conditional PSDM] + EntryH --> Become[ Become a conditional PSDM continue with the same domain name and password ] + Become --> SetTimer[ Set T_RE-Registration Timer to T_RE_REGISTRATION_TimeOut ] + SetTimer --> Join(( )) + Join --> Continue[ Continue active as PSDM ] + Continue --> IsRequest{ Is Re-registration request received } + IsRequest -- Yes --> SendResponse[ Send positive Reg-Rsp with to the EP ] + IsRequest -- No --> IsTimerExpired{ Is T_Re-Registration Timer expired } + IsTimerExpired -- Yes --> ExitH[ ] + IsTimerExpired -- No --> Join + end + SendResponse --> StateI[State I PSDM] + ExitH --> StateA[State A. IDLE or NSD] + style EntryH fill:none,stroke:none + style Join fill:none,stroke:none + style ExitH fill:none,stroke:none + style StateG fill:#92D050,stroke:#000 + style StateH fill:#ADD8E6,stroke:#000 + style StateI fill:#0070C0,color:white,stroke:#000 + style StateA fill:#E0E0E0,stroke:#000 + style Become fill:#E0E0E0,stroke:#000 + style SetTimer fill:#E0E0E0,stroke:#000 + style Continue fill:#E0E0E0,stroke:#000 + style IsRequest fill:#E0E0E0,stroke:#000 + style SendResponse fill:#E0E0E0,stroke:#000 + style IsTimerExpired fill:#E0E0E0,stroke:#000 + style G9978[ G.9978(11-18)_F6-33 ] + style G9978 fill:none,stroke:none + +``` + +Flowchart for State H conditional PSDM algorithm. It starts at State G, transitions to State H on T\_PAIRING expiration. Inside State H, it becomes a conditional PSDM, sets a timer, and continues active. If a re-registration request is received, it sends a positive response and goes to State I. If the timer expires, it goes to State A. Otherwise, it loops back to continue active. + +**Figure 6-33 – Algorithm for a state H conditional permanent secure domain master** + +- I. **PSDM** – This is a final state where the conditional secure DM becomes a PSDM after it receives a re-registration request from its EP. In this state, the PSDM shall use the DN and PW that it used in state F and in state H. + +A node that starts a generic pairing procedure shall complete the pairing procedure in one of the following possible states. + +- The node successfully joins an SD as an EP node (state E). +- The node working as a temporary DM becomes a permanent secure DM (state I). +- After expiry of the pairing window period without any successful completion of the pairing procedure, the triggered node returns to the state it was before the PUSH\_P event (state A). + +A PSDM shall operate after a PUSH\_P event as specified in the algorithm depicted in Figure 6-34. + +After a PUSH\_P event, the PSDM shall enter into a pairing state. It shall exit from the pairing state on successful completion of a pairing procedure or expiry of the T\_PAIRING timer. If the PSDM exits the pairing state after successful completion of a pairing procedure before T\_PAIRING has expired and it receives other pairing requests from another node, it shall answer with a rejection response due to another pairing procedure having completed already. + +![Flowchart illustrating the algorithm for a permanent secure domain master after a PUSH_P event. The process starts in the PSDM state, transitions to the PSDM in PAIRING STATE upon a Push_P_EV event, and then returns to the PSDM state after handling the pairing registration.](cbb2d311b20781a595488445ded48d0a_img.jpg) + +``` + +graph TD + subgraph PSDM + Start(( )) --> Push_P_EV[Push_P_EV] + end + subgraph PSDM_PAIRING_STATE [PSDM in PAIRING STATE] + Push_P_EV --> Block[Block detection of additional Push_P event +Set the T_PAIRING timer +Open the acceptance pairing window] + Block --> Join1(( )) + Join1 --> IfReg1{If pairing registration is received} + IfReg1 -- No --> TExpired1{T_PAIRING is expired} + TExpired1 -- No --> Join1 + TExpired1 -- Yes --> CloseWindow[Close the pairing window] + IfReg1 -- Yes --> SendPos[Send positive registration response with password +Close the acceptance pairing window] + CloseWindow --> Join2(( )) + SendPos --> Join2 + Join2 --> Unblock[UnBlock detection of Push_P event] + end + subgraph PSDM_NORMAL [PSDM] + Unblock --> Join3(( )) + Join3 --> NormalPSDM[Normal PSDM activity] + NormalPSDM --> IfReg2{If pairing registration is received} + IfReg2 -- Yes --> TExpired2{T_PAIRING is expired} + TExpired2 -- No --> SendNeg[Send negative registration response with already one node is paired indication] + TExpired2 -- Yes --> SendReg[Send the reg response with reject registration response with pairing window is closed] + SendNeg --> Join4(( )) + SendReg --> Join4 + Join4 --> NormalPSDM + end + +``` + +The flowchart is divided into three main sections: **PSDM**, **PSDM in PAIRING STATE**, and **PSDM**. + +- PSDM (Initial State):** The process starts with a red circle and a red arrow labeled **Push\_P\_EV**. +- PSDM in PAIRING STATE:** + - The first step is a box: "Block detection of additional Push\_P event", "Set the T\_PAIRING timer", and "Open the acceptance pairing window". + - Next is a blue circle connector. + - Then a decision diamond: "If pairing registration is received". + - If **No**, it goes to a decision diamond: "T\_PAIRING is expired". + - If **No**, it loops back to the blue circle connector. + - If **Yes**, it goes to a box: "Close the pairing window". + - If **Yes**, it goes to a box: "Send positive registration response with password", "Close the acceptance pairing window". + - Both "Close the pairing window" and "Send positive registration response..." lead to another blue circle connector. + - From this connector, it goes to a box: "UnBlock detection of Push\_P event". +- PSDM (Normal State):** + - The "UnBlock detection of Push\_P event" box leads to a blue circle connector. + - From this connector, it goes to a box: "Normal PSDM activity". + - Then a decision diamond: "If pairing registration is received". + - If **Yes**, it goes to a decision diamond: "T\_PAIRING is expired". + - If **No**, it goes to a box: "Send negative registration response with already one node is paired indication". + - If **Yes**, it goes to a box: "Send the reg response with reject registration response with pairing window is closed". + - Both "Send negative registration..." and "Send the reg response..." lead to a final blue circle connector. + - From this connector, it loops back to the "Normal PSDM activity" box. + +Flowchart illustrating the algorithm for a permanent secure domain master after a PUSH\_P event. The process starts in the PSDM state, transitions to the PSDM in PAIRING STATE upon a Push\_P\_EV event, and then returns to the PSDM state after handling the pairing registration. + +G.9978(11-18)\_F6-34 + +**Figure 6-34 – Algorithm for a permanent secure domain master after a PUSH\_P event** + +Figure 6-35 illustrates an example of faulty usage of the pairing mechanism by a user that triggered the PUSH\_P event on four nodes that were in an unconnected state and on the DM of an SD. In single-node mode, the required result is that only one node shall join the SD and the rest of the triggered nodes return to the unconnected state. The pairing mechanism described in the foregoing + +solves this faulty use case by having one node that joins the SD and the rest of the nodes return to the unconnected state. + +![Sequence diagram illustrating the algorithm for a state H conditional permanent secure domain master. The diagram shows interactions between PSDM, Node 1, Node 2, Node 3, and Node 4. Node 1 acts as a TMPDM for Node 2, and Node 3 acts as a TMPDM for Node 4. Node 2 then pairs with the PSDM, informing Node 1. Node 4 attempts to pair with the PSDM but is rejected because Node 2 is already paired, informing Node 3.](878d9539700bd792e7d12ad6f1203c5d_img.jpg) + +The diagram illustrates the following sequence of events: + +- Node 1 (TMPDM) and Node 2:** Node 1 sends a **Push\_P** message to Node 2. Node 2 responds with **Pairing**. A **Pairing window** is established. Node 2 sends a **Push\_P** message to the **PSDM**. The **PSDM** responds with **Successful pairing**. Node 2 then informs Node 1 (labeled **EP in SD**) that it has successfully paired with the **PSDM**. Node 1 returns to the **IDLE** state. +- Node 3 (TMPDM) and Node 4:** Node 3 sends a **Push\_P** message to Node 4. Node 4 responds with **Pairing**. A **Pairing window** is established. Node 4 sends a **Push\_P** message to the **PSDM**. The **PSDM** responds with **Rejected pairing due to already completed**. Node 4 then informs Node 3 (labeled **EP informs its TMP DM about a rejection pairing from SPDm**) that it was rejected. Node 3 returns to the **IDLE** state. +- PSDM and Node 1:** At the bottom, the **PSDM** sends a **Push\_P** message to Node 1. Node 1 responds with **Rejected pairing due to window close**. + +Brackets on the right side of the diagram indicate the duration of the **Pairing window** for each pair of nodes. + +Sequence diagram illustrating the algorithm for a state H conditional permanent secure domain master. The diagram shows interactions between PSDM, Node 1, Node 2, Node 3, and Node 4. Node 1 acts as a TMPDM for Node 2, and Node 3 acts as a TMPDM for Node 4. Node 2 then pairs with the PSDM, informing Node 1. Node 4 attempts to pair with the PSDM but is rejected because Node 2 is already paired, informing Node 3. + +G.9978(11-18)\_F6-35 + +**Figure 6-35 – Algorithm for a state H conditional permanent secure domain master** + +In this scenario, node 2 pairs with node 1 that is acting as a TMPDM. Then, node 3 pairs with node 4 that is acting as a TMPDM. Later, when node 2 successfully pairs with the PSDM, node 2 informs its temporary DM that it has registered successfully with a PSDM. The temporary DM, on receipt of this message, shall return to the UNCONNECTED state. Later, node 4 that tries to pair with the PSDM is rejected due to pairing being already successfully completed with another node (node 2). On receipt of this rejection from the PSDM, node 4 informs its temporary DM that it was rejected by a PSDM for the following reason "Pairing registration rejected due to pairing being already completed with another node" and returns to the unconnected mode. The temporary DM on receipt of this message also returns to the UNCONNECTED state. + +##### 6.2.2.1.3 Pairing registration protocol in the single-node pairing mode + +The protocol of the pairing registration enables a node to register with an SD during the pairing procedure. The pairing registration protocol diagram is presented in Figure 6-36. + +![Figure 6-36: Pairing registration protocol diagram in the single-node pairing mode. The diagram shows the interaction between a DM (Domain Manager) and a Joining node. The process starts with a 'User push-button event' on the DM, which opens a pairing acceptance window. The DM then scans for a secure DM. The Joining node also receives a 'User push-button event' and scans for a secure DM. Once a secure DM is detected, the Joining node sends an ADM_NodeRegistrRequest.req message to the DM. The DM responds with an ADM_DmRegistrResponse.cnf message. The DM then closes the pairing acceptance window. Finally, both the DM and the Joining node engage in an ITU-T G.9961 Authentication (clause 9.2) protocol. Annotations indicate that the pairing window is open until the pairing is received up to T_PAIRING, and the user has T_PAIRING seconds to push the other node PUSH_P.](e22af684d8e56d4c61e61bb5ddac1087_img.jpg) + +``` + +sequenceDiagram + participant DM + participant Joining node + Note over DM, Joining node: User push-button event + rect rgb(144, 238, 144) + Note left of DM: Open pairing acceptance window + end + Note right of Joining node: User push-button event + Joining node->>Joining node: Scan for secure DM + Note over Joining node: Secure MAP is detected + Joining node->>DM: ADM_NodeRegistrRequest.req + DM->>Joining node: ADM_DmRegistrResponse.cnf + Note left of DM: Close pairing acceptance window + DM<->Joining node: Authentication protocol (clause 9.2 of ITU-T G.9961) + +``` + +The diagram illustrates the sequence of events for single-node pairing registration. On the left, the DM (Domain Manager) receives a 'User push-button event', which triggers the opening of a pairing acceptance window. A green vertical bar indicates this window, which remains open until the pairing is received up to $T_{\text{PAIRING}}$ . The DM then scans for a secure DM. On the right, the Joining node also receives a 'User push-button event' and scans for a secure DM. Once a secure DM is detected by the Joining node, it sends an **ADM\_NodeRegistrRequest.req** message to the DM. The DM responds with an **ADM\_DmRegistrResponse.cnf** message. After receiving the response, the DM closes the pairing acceptance window. Both the DM and the Joining node then engage in an **ITU-T G.9961 Authentication (clause 9.2)** protocol. A bracket on the right indicates that the user has $T_{\text{PAIRING}}$ seconds to push the other node **PUSH\_P**. + +Figure 6-36: Pairing registration protocol diagram in the single-node pairing mode. The diagram shows the interaction between a DM (Domain Manager) and a Joining node. The process starts with a 'User push-button event' on the DM, which opens a pairing acceptance window. The DM then scans for a secure DM. The Joining node also receives a 'User push-button event' and scans for a secure DM. Once a secure DM is detected, the Joining node sends an ADM\_NodeRegistrRequest.req message to the DM. The DM responds with an ADM\_DmRegistrResponse.cnf message. The DM then closes the pairing acceptance window. Finally, both the DM and the Joining node engage in an ITU-T G.9961 Authentication (clause 9.2) protocol. Annotations indicate that the pairing window is open until the pairing is received up to T\_PAIRING, and the user has T\_PAIRING seconds to push the other node PUSH\_P. + +**Figure 6-36 – Pairing registration protocol diagram in the single-node pairing mode** + +A node that is not a member of an SD that is triggered by a **PUSH\_P** event shall try to register only with an SD, by sending an **ADM\_NodeRegistrRequest.req** message to a detected secure DM. The **ADM\_NodeRegistrRequest.req** message shall include the **PairingReq** field, in addition to all the parameters that are specified in clause 8.6.1.1.1 of [ITU-T G.9961]. + +NOTE – The security status of the domain is indicated in the security-related domain info subfield (see Table 8-85.9 of [ITU-T G.9961]). + +On receipt of the **ADM\_NodeRegistrRequest.req** message, the DM shall process the registration request and shall reply within **REG\_RESP\_TIME** to the node with an **ADM\_DmRegistrResponse.cnf** message. + +If the DM receives the registration request message while it was within a pairing window, the **ADM\_DmRegistrResponse.cnf** message shall include the following fields: + +- a status flag with a success registration indication; +- a PW needed for the authentication procedure (clause 9.2 of [ITU-T G.9961]); +- a non-zero **DEVICE\_ID** for the registering node assigned by the DM; +- all other relevant configuration data as specified in [ITU-T G.9961]. + +On receipt of the **ADM\_DmRegistrResponse.cnf** message, the registering node shall identify the **ADM\_DmRegistrResponse.cnf** message based on its **REGID** field and adopt the DN of the domain that replied positively and its new assigned **DEVICE\_ID**. The registering node shall use the PW included in the **ADM\_DmRegistrResponse.cnf** message for the authentication procedure as specified in clause 9.2 of [ITU-T G.9961]. + +If the registration request is not received within an open pairing window, the secure DM shall reject the registration request by replying to the registering node with an ADM\_DmRegistrResponse.cnf message that contains the status flag set to zero and an extended rejection code 316 that indicates that the registration request is rejected for the reason that the "pairing window is closed" as specified in Table 8-15.1 of [ITU-T G.9961]. + +If the registration request is received within an open pairing window, but after another successful pairing, then the DM shall reject the registration request by replying to the registering node with a ADM\_DmRegistrResponse.cnf message that contains the status flag set to zero and an extended rejection code 416 that indicates that the registration request is rejected for the reason that "pairing has just been successfully completed with another node" as specified in Table 8-15.1 [ITU-T G.9961]. This code shall be sent up to 5 s after the window has been closed if the DM needs to reject a pairing request. After this time, the code used to reject a pairing request because the window is closed shall revert to 316. + +In the case of rejection, the DEVICE\_ID shall be set to zero. + +The ADM\_DmRegistrResponse.cnf message shall include all the other fields as specified in clause 8.6.1.1.1 of [ITU-T G.9961] and shall be sent as specified in clause 8.6.1.1.1 of [ITU-T G.9961] [medium access (MA) priority associated with medium access control protocol data unit (MPDU) priority = 7]. + +If the registering node does not receive an ADM\_DmRegistrResponse.cnf message from the DM within 1 s, the node shall retry registration within REG\_RETRY\_TIMEOUT. If the joining node does not receive a response after MAX\_REG\_ATTEMPTS registration attempts, the node shall scan and try to detect another DM. + +If the joining node was rejected by the secure DM, due to a closed pairing window, the node shall scan and try to detect another secure DM. The node shall continue to retry registration with all detected secure DMs during $t_{\text{PAIRING}}$ . If the node does not receive a positive registration response after the $t_{\text{PAIRING}}$ period has expired, it shall return to its state before the PUSH\_P event was detected. + +Figure 6-37 shows the operation of a DM in an SD on receipt of the PUSH\_P event in a single-node pairing mode. + +![Flowchart showing the operation of a Domain Master (DM) in a secure domain upon a PUSH_P event. The process starts at a top box 'DM of a secure domain'. A red arrow labeled 'Push_P_EV' points down to a red circle inside a large box labeled 'PSDM in PAIRING STATE'. Inside this box, the flow goes through: 1. A rectangle: 'Block detection of additional Push_P event, Set the T_PAIRING timer, Open the pairing window'. 2. A diamond: 'If registration (pairing) is received'. If 'No', it goes to another diamond 'T_PAIRING is expired'. If 'Yes', it goes to a diamond 'If pairing window is open'. 3. From 'If pairing window is open', 'Yes' leads to 'Send positive registration response with password, close the pairing window', and 'No' leads to 'Send negative registration response with already one node is paired indication'. 4. Both paths from the window check meet at a blue circle junction, which then leads to the 'T_PAIRING is expired' diamond. 5. If 'T_PAIRING is expired' is 'Yes', it leads to 'UnBlock detection of Push_P event' then 'Set the reject registration response with pairing window is closed'. 6. Finally, the flow exits the large box to a bottom box 'Secure DM'.](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +``` + +graph TD + DM[DM of a secure domain] -- "Push_P_EV" --> PSDM + subgraph PSDM [PSDM in PAIRING STATE] + Start(( )) --> Block[Block detection of additional Push_P event +Set the T_PAIRING timer +Open the pairing window] + Block --> IfReg{If registration (pairing) is received} + IfReg -- No --> IfExp{T_PAIRING is expired} + IfReg -- Yes --> IfWin{If pairing window is open} + IfWin -- Yes --> Pos[Send positive registration response with password +close the pairing window] + IfWin -- No --> Neg[Send negative registration response with already one node is paired indication] + Pos --> J1(( )) + Neg --> J1 + J1 --> IfExp + IfExp -- Yes --> UnBlock[UnBlock detection of Push_P event] + UnBlock --> Reject[Set the reject registration response with pairing window is closed] + end + Reject --> SecureDM[Secure DM] + style DM fill:#b4a7d6 + style PSDM fill:#d9d2e9 + style SecureDM fill:#b4a7d6 + style Start fill:red + style J1 fill:#3d85c6 + +``` + +G.9978(11-18)\_F6-37 + +Flowchart showing the operation of a Domain Master (DM) in a secure domain upon a PUSH\_P event. The process starts at a top box 'DM of a secure domain'. A red arrow labeled 'Push\_P\_EV' points down to a red circle inside a large box labeled 'PSDM in PAIRING STATE'. Inside this box, the flow goes through: 1. A rectangle: 'Block detection of additional Push\_P event, Set the T\_PAIRING timer, Open the pairing window'. 2. A diamond: 'If registration (pairing) is received'. If 'No', it goes to another diamond 'T\_PAIRING is expired'. If 'Yes', it goes to a diamond 'If pairing window is open'. 3. From 'If pairing window is open', 'Yes' leads to 'Send positive registration response with password, close the pairing window', and 'No' leads to 'Send negative registration response with already one node is paired indication'. 4. Both paths from the window check meet at a blue circle junction, which then leads to the 'T\_PAIRING is expired' diamond. 5. If 'T\_PAIRING is expired' is 'Yes', it leads to 'UnBlock detection of Push\_P event' then 'Set the reject registration response with pairing window is closed'. 6. Finally, the flow exits the large box to a bottom box 'Secure DM'. + +**Figure 6-37 – Domain master of a secure domain operation on a PUSH\_P event** + +During the $t_{\text{PAIRING}}$ period, the secure DM shall handle only one registration procedure with one joining node and shall respond with a registration response with a negative indication that it has already committed to a pairing procedure with one joining node. During the $t_{\text{PAIRING}}$ period, the secure DM shall ignore any new PUSH\_P events. After expiry of the $t_{\text{PAIRING}}$ period or after the acceptance of a new node into the network, the secure DM shall unblock receipt of the PUSH\_P event. + +##### 6.2.2.1.4 Informing the domain master about a PUSH\_P event + +The user may trigger the PUSH\_P event on any arbitrary node in an SD and on the joining node in order to start the pairing mechanism. On detection of the PUSH\_P event, the triggered EP node in the SD shall send an ADM\_NodeReportPUSH\_P.ind message (see Table 6-11) to its DM to report about + +the PUSH\_P event. On receipt of the ADM\_NodeReportPUSH\_P.ind message, the secure DM shall respond with the ADM\_NodeReportPUSH\_P.rsp message to the EP node to confirm receipt of the ADM\_NodeReportPUSH\_P.ind message and immediately open the pairing window to accept a potential registration with a pairing request. + +The secure DM will inform the rest of the nodes in the SD by an ADM\_PairingWindow.ind broadcast message of the opening and closing of the pairing window. + +Figure 6-38 shows the pairing registration protocol via a UI EP node in the single-node pairing mode. + +![Sequence diagram for pairing registration. Lifelines: DM, EP1, EP2, Joining node. The process starts with a 'User push-button event' at EP1. DM opens a pairing window and sends ADM_NodeReportPUSH_P.ind to EP1. EP1 responds with ADM_NodeReportPUSH_P.rsp. DM then broadcasts ADM_PairingWindow.ind (open) to EP2 and the Joining node. The Joining node performs a 'Scan for secure DM' after another 'User push-button event'. DM receives ADM_NodeRegistrRequest.req from the Joining node, responds with ADM_DmRegistrResponse.cnf, and then broadcasts ADM_PairingWindow.ind (close). The DM and Joining node then execute an 'Authentication protocol (clause 9.2 of ITU-T G.9961)'. Annotations include 'Open pairing acceptance window', 'The pairing window is open until the pairing is received up to T_PAIRING', 'Close pairing acceptance window', and 'The user has T_PAIRING seconds to push the other node PUSH_P'.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +Sequence diagram for pairing registration. Lifelines: DM, EP1, EP2, Joining node. The process starts with a 'User push-button event' at EP1. DM opens a pairing window and sends ADM\_NodeReportPUSH\_P.ind to EP1. EP1 responds with ADM\_NodeReportPUSH\_P.rsp. DM then broadcasts ADM\_PairingWindow.ind (open) to EP2 and the Joining node. The Joining node performs a 'Scan for secure DM' after another 'User push-button event'. DM receives ADM\_NodeRegistrRequest.req from the Joining node, responds with ADM\_DmRegistrResponse.cnf, and then broadcasts ADM\_PairingWindow.ind (close). The DM and Joining node then execute an 'Authentication protocol (clause 9.2 of ITU-T G.9961)'. Annotations include 'Open pairing acceptance window', 'The pairing window is open until the pairing is received up to T\_PAIRING', 'Close pairing acceptance window', and 'The user has T\_PAIRING seconds to push the other node PUSH\_P'. + +Figure 6-38 – Protocol diagram for pairing registration via a user interface in the single-node pairing mode + +###### 6.2.2.1.4.1 Message: ADM\_NodeReportPUSH\_P.ind + +Table 6-11 – Payload of an ADM\_NodeReportPUSH\_P.ind message + +| Field | Octet | Bits | Description | +|--------------|-------|-------|---------------------------------------------------------| +| OpenDeviceID | 0 | [7:0] | DEVICE_ID of the EP node that triggered a PUSH_P event. | + +###### 6.2.2.1.4.2 Message: ADM\_NodeReportPUSH\_P.rsp + +This message has no payload. + +###### 6.2.2.1.4.3 Message: ADM\_PairingWindow.ind + +This is a broadcast message that the DM sends to all nodes in the SD to indicate when the pairing window opens or closes (see Table 6-12). It can be used to manage LEDs or any other indication of the state of the pairing window at the network level. + +**Table 6-12 – Payload of an ADM\_PairingWindow.ind message** + +| Field | Octet | Bits | Description | +|-------|-------|-------|----------------------------------------------------------------------------------------------------------| +| Code | 0 | [7:0] | Code is 1 when window closes.
Code is 2 when window opens.
The rest of values are reserved by ITU. | + +##### 6.2.2.1.5 Pairing registration protocol in the single-node pairing mode by user confirmation + +If the new node powers on in the home network, it will broadcast an ADM\_SelfNotify.ind message with its REGID "A" to notify of its existence. If the DM receives this ADM\_SelfNotify.ind message, it shall send an ADM\_UINewNodeExist.ind message with REGID "A" to the UI node. The AE that is associated with the G.hn UI node will trigger a FLASH\_E event to let the user know that a new node is joining the network. At the same time, the pairing window is opened for a *tPAIRING* period. If the users confirm that the new device can join the secure domain, and on detection of the PUSH\_P event within the pairing window, the triggered UI node shall send an ADM\_UI\_MACauthorization.ind message to the DM. + +After receiving the indication message, the DM shall open a window to allow registration of this node with REGID "A", only if it has already received the SC\_UI\_Authorization.req message from the SC indicating that the UI node has been authorized. During this time window, the DM shall broadcast the MAP frames with the RegistrationOffer field set to two and "RegistratioRestrict" field set to REGID "A". The nodes that work with this REGID "A" shall register in the DM. + +After the new unconnected node receives the registration confirmation message, it shall send an ADM\_SecureDomain.req message, which includes the PW for authentication, to the authorized nodes that have registered on it. The DM shall also distribute a MAC authorization information subfield to the Medium Access Plan-Default (MAP-D) frames for 120 s, which includes collected information about neighbouring nodes that have registered in an NSD. A node in an NSD shall monitor MAP-D frames from neighbouring domains and, if it detects that its information is included in the MAC authorization information subfield in the MAP-D frames, it shall leave the NSD and register in the SD. + +On receipt of the ADM\_SecureDomain.req message, the receiving node shall confirm receipt by replying with an ADM\_SecureDomain.cnf message. The receiving node shall use the PW and DN to complete authentication with the SC. The nodes that are not working with the REGID "A" shall be rejected by the DM. + +![Sequence diagram for pairing registration in single-node mode. Lifelines: DM, UI node, Unconnected node. The process involves opening a registration window, sending a notification, receiving a request, sending a MAP, receiving a registration request and confirmation, sending a secure domain request and confirmation, and finally authenticating to the SC.](dbd074feb5cce1300f42f91da8f673d1_img.jpg) + +``` + +sequenceDiagram + participant DM + participant UI node + participant Unconnected node + + Note over DM: Open a window to allow +the registration of node +with REGID "A" + Unconnected node->>DM: ADM_SelfNotify.ind + DM->>UI node: ADM_UINewNodeExist.ind + Note over UI node: The pairing window is open +until the pairing is received +up to Tpairing + UI node->>DM: FLASH_E event + UI node->>DM: User PUSH_P event + DM->>UI node: ADM_UIMACAuthorization.req + DM->>Unconnected node: MAP with "RegistrationOffer" field set to 2 and "RegistrationRestrict" field set to REGID "A" + Unconnected node->>DM: Registration request + Unconnected node->>DM: Registration confirmation + DM->>Unconnected node: ADM_SecureDomain.req + DM->>Unconnected node: ADM_SecureDomain.cnf + Note over DM: Close the window and +stop allowing the +registration of node +with MAC addr "A" + Note over Unconnected node: Authentication to the SC + +``` + +G.9978(11-18)\_F6-39 + +Sequence diagram for pairing registration in single-node mode. Lifelines: DM, UI node, Unconnected node. The process involves opening a registration window, sending a notification, receiving a request, sending a MAP, receiving a registration request and confirmation, sending a secure domain request and confirmation, and finally authenticating to the SC. + +**Figure 6-39 – Pairing registration protocol diagram in the single-node pairing mode by user confirmation** + +#### 6.2.2.2 Pairing registration in the multi-node pairing mode + +The pairing registration procedure under the multi-node pairing mode is used to enable the user to add one or more non-secure nodes to an SD within one $t_{\text{PAIRING}}$ period. The pairing registration procedure is the same as in single-node pairing mode except that the DM shall close the pairing acceptance window only after the $t_{\text{PAIRING}}$ window period has expired to enable several nodes to register within one $t_{\text{PAIRING}}$ period. Figure 6-40 is the protocol diagram of pairing registration in the multi-node pairing mode. In this example, the user triggers the PUSH\_P event on one of the secure nodes of the SD, which informs its DM about it. + +![Protocol diagram of pairing registration in the multi-node pairing mode. Lifelines: DM, EP1, EP2, Joining node 1, Joining node 2. The sequence shows a user push-button event at EP1 triggering the DM to open a pairing window. Joining nodes then scan for a secure DM, send registration requests, receive responses, and perform authentication protocols.](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +``` + +sequenceDiagram + participant DM + participant EP1 + participant EP2 + participant JN1 as Joining node + participant JN2 as Joining node + + Note over EP1: User push-button event + EP1->>DM: ADM_NodeReportPUSH_P.ind + DM->>EP1: ADM_NodeReportPUSH_P.rsp + DM->>EP1: ADM_PairingWindow.ind (open) + DM->>EP2: ADM_PairingWindow.ind (open) + + Note over JN1: User push-button event + Note over JN1: Scan for secure DM + JN1->>DM: ADM_NodeRegistrRequest.req + DM->>JN1: ADM_DmRegistrResponse.cnf + DM->>EP1: ADM_PairingWindow.ind (close) + DM->>EP2: ADM_PairingWindow.ind (close) + + rect rgb(240, 240, 240) + DM<->JN1: ITU-T G.9961 Authentication (clause 9.2) + end + + Note over JN2: User push-button event + Note over JN2: Scan for secure DM + JN2->>DM: ADM_NodeRegistrRequest.req + DM->>JN2: ADM_DmRegistrResponse.cnf + DM->>EP1: ADM_PairingWindow.ind (close) + DM->>EP2: ADM_PairingWindow.ind (close) + + rect rgb(240, 240, 240) + DM<->JN2: ITU-T G.9961 Authentication (clause 9.2) + end + +``` + +G.9978(11-18)\_F6-40 + +Protocol diagram of pairing registration in the multi-node pairing mode. Lifelines: DM, EP1, EP2, Joining node 1, Joining node 2. The sequence shows a user push-button event at EP1 triggering the DM to open a pairing window. Joining nodes then scan for a secure DM, send registration requests, receive responses, and perform authentication protocols. + +**Figure 6-40 – Protocol diagram of pairing registration in the multi-node pairing mode** + +On receipt of the PUSH\_P event, the DM shall open the pairing window for a period of $t_{PAIRING}$ . + +On receipt of an ADM\_NodeRegistrRequest.req message, the DM shall process the registration request and shall reply within REG\_RESP\_TIME to the requesting node with an ADM\_DmRegistrResponse.cnf message. + +If the DM receives the registering request message while it is within a pairing window, the ADM\_DmRegistrResponse.cnf message shall include the following fields: + +- a status flag with a success registration indication; +- a PW needed for the authentication procedure (clause 9.2 of [ITU-T G.9961]); +- a non-zero DEVICE\_ID for the registering node assigned by the DM; +- all other relevant configuration data as specified in [ITU-T G.9961]. + +On receipt of the ADM\_DmRegistrResponse.cnf message, the registering node shall identify the ADM\_DmRegistrResponse.cnf message based on its REGID field and adopt the DN of the domain that replied positively and its new assigned DEVICE\_ID. The registering node shall use the PW included in the ADM\_DmRegistrResponse.cnf message for the authentication procedure as specified in clause 9.2 of [ITU-T G.9961]. + +If the DM receives a registration request while its pairing window is closed, it shall reject the registration request by replying to the joining node with a ADM\_DmRegistrResponse.cnf message that contains the status flag set to zero and an extended rejection code 0x3 that indicates that the registration request is rejected for the reason that "pairing window is closed" and the DEVICE\_ID shall be set to zero. + +During the $t_{\text{PAIRING}}$ period, the DM shall block any other PUSH\_P events and shall ignore any new PUSH\_P events. After expiry of the $t_{\text{PAIRING}}$ period, the DM shall unblock receipt of new PUSH\_P event and close the pairing acceptance window. + +Figure 6-41 shows the state machine of a secure DM after a PUSH\_P event. + +![State machine diagram of a secure domain master (PSDM) after a PUSH_P event. The diagram shows transitions between states based on events like Push_P_EV and timer expirations, including blocking/unblocking events and sending registration responses.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +``` + +stateDiagram-v2 + state "PSDM" as PSDM1 + state "PSDM in PAIRING STATE" as PAIRING_STATE + state "PSDM" as PSDM2 + + PSDM1 --> PAIRING_STATE : Push_P_EV + + state PAIRING_STATE { + [*] --> Actions1 + Actions1 : Block detection of additional Push_P event +Set the T_PAIRING timer +Open the acceptance pairing window + Actions1 --> IfRegReceived1 + state IfRegReceived1 <> + note right of IfRegReceived1 : If pairing registration is received + IfRegReceived1 --> SendPositive : Yes + SendPositive : Send positive registration response with DEVICE_ID and password + IfRegReceived1 --> IfExpired : No + state IfExpired <> + note left of IfExpired : T_PAIRING is expired + IfExpired --> IfRegReceived1 : No + IfExpired --> CloseWindow : Yes + CloseWindow : Close the pairing window + CloseWindow --> Unblock + SendPositive --> Unblock + Unblock : UnBlock detection of Push_P event + } + + PAIRING_STATE --> PSDM2 + + state PSDM2 { + [*] --> NormalActivity + NormalActivity : Normal PSDM activity + NormalActivity --> IfRegReceived2 + state IfRegReceived2 <> + note right of IfRegReceived2 : If pairing registration is received + IfRegReceived2 --> NormalActivity : No + IfRegReceived2 --> SendReject : Yes + SendReject : Send the reg response with reject registration response with pairing window is closed + SendReject --> NormalActivity + } + +``` + +State machine diagram of a secure domain master (PSDM) after a PUSH\_P event. The diagram shows transitions between states based on events like Push\_P\_EV and timer expirations, including blocking/unblocking events and sending registration responses. + +G.9978(11-18)\_F6-41 + +**Figure 6-41 – State machine of a secure domain master after a PUSH\_P event** + +##### 6.2.2.2.1 Conversion of a non-secure domain to a secure domain in the multi-node pairing mode + +The multi-node pairing mode enables the user to convert an entire NSD to an SD by triggering the PUSH\_P event on all nodes of the domain. Figure 6-42 illustrates the way an NSD is converted into an SD in multi-node pairing mode. + +NOTE 1 – Figure 6-42 shows a particular sequence of PUSH\_P events. However, any other sequence of PUSH\_P events is also valid. + +NOTE 2 – The sequence in Figure 6-42 makes use of the DM and EP state alternation mechanism described in clause 6.2.2.1.1. + +![Protocol diagram of pairing registration in the multi-node pairing mode. The diagram shows five nodes (Node 3, Node 2, Node 1, Node 4, Node 5) and their states over time. Node 3 is the DM A, and Nodes 2, 1, 4, and 5 are EP nodes (a2, a1, a3, a4). The diagram illustrates the sequence of events for pairing registration, including the opening and closing of the pairing window, and the registration of EP nodes with the DM. A 'Figures dictionary' at the bottom explains the color coding and symbols used.](195611c20b2dc7ed0fa3033392e22908_img.jpg) + +The diagram shows a vertical timeline for five nodes: Node 3 (DM A), Node 2 (EP node a2), Node 1 (EP node a1), Node 4 (EP node a3), and Node 5 (EP node a4). + +Node 3 (DM A) starts with a 'Temp DM pairing window is open' (light green) and a 'User push button event' (red triangle). It then transitions to 'Constant DM pairing window is open' (dark green). A bracket indicates 'The pairing window is open for 120 seconds'. Finally, it shows a 'Close pairing acceptance window' (grey). + +The EP nodes (Nodes 2, 1, 4, 5) follow a sequence: they start by 'EP scanning for secure MAPs for Tsearch' (yellow cross-hatch), triggered by a 'User push button event' (red triangle). They then move to 'EP registering with secure DM' (blue diagonal stripes) while communicating with the DM (indicated by 'Pairing' arrows). Finally, they reach the state 'EP registered and paired with secure DM' (solid orange). + +**Figures dictionary** + +- Temp DM pairing window is open +- Constant DM pairing window is open +- DM pairing window is close +- EP scanning for secure MAPs for Tsearch +- EP registering with secure DM +- EP registered and paired with secure DM +- ▲ User push button event + +G.9978(11-18)\_F6-42 + +Protocol diagram of pairing registration in the multi-node pairing mode. The diagram shows five nodes (Node 3, Node 2, Node 1, Node 4, Node 5) and their states over time. Node 3 is the DM A, and Nodes 2, 1, 4, and 5 are EP nodes (a2, a1, a3, a4). The diagram illustrates the sequence of events for pairing registration, including the opening and closing of the pairing window, and the registration of EP nodes with the DM. A 'Figures dictionary' at the bottom explains the color coding and symbols used. + +**Figure 6-42 – Protocol diagram of pairing registration in the multi-node pairing mode** + +In Figure 6-42, node 3 is the first to trigger the PUSH\_P event. It starts scanning for an SD. After $t_0$ it becomes a temporary DM of a new SD (DM A). Node 1 is the second to be triggered by the PUSH\_P event; it starts scanning for an SD and it detects MAPs transmitted by temporary DM A. Then node 1 registers with DM A and after completion of the registration procedure becomes an EP node in domain A (as node a1). Then node 2 is the third to be triggered by the PUSH\_P event. It starts scanning for an SD and it detects MAPs transmitted by temporary DM A. Node 2 conducts the registration procedure with DM A and after completion of the registration procedure becomes an EP node in domain A (as node a2). Then node 4 is triggered by the PUSH\_P event and does the same and becomes an EP node in domain A (as node a3). Then node 5 is triggered by the PUSH\_P event and it does the same and becomes an EP node in domain A (as node a4). Successful completion of the multi-node pairing procedure results in a new SD A. + +During multi-node pairing procedures where pairing is performed among several nodes simultaneously, faulty cases where several SDs are created may occur. This can happen because during the pairing open window, more than one node might become a temporary DM, with a unique random DN, some nodes register with one temporary DM while other nodes register with another temporary DM. This kind of scenario leads to creation of two SDs with two different DNs as illustrated in Figure 6-43. + +NOTE 3 – Figure 6-43 shows a particular sequence of PUSH\_P events. However, any other sequence of PUSH\_P events is also valid. + +NOTE 4 – The sequence in Figure 6-43 makes use of the DM and EP state alternation mechanism described in clause 6.2.2.1.1. + +![Diagram of multi-node pairing procedure resulting in two secure domains. The diagram shows five nodes (Node 1-5) and their interactions over time. Node 3 (DM A) and Node 4 (DM B) are temporary DMs. Node 1 (EP node a1) and Node 2 (EP node a2) pair with Node 3. Node 5 (EP node b1) pairs with Node 4. A 'Figures dictionary' at the bottom explains the color coding: green for open pairing windows, yellow for EP scanning, blue for EP registering, orange for EP registered, and red triangles for user push button events. A dashed line indicates the end of the 120-second pairing window.](a2251e3bbfcd726b68cc50b091e53b02_img.jpg) + +The diagram illustrates the multi-node pairing procedure across two secure domains, A and B. + +Domain A consists of Node 3 (DM A), Node 2 (EP node a2), and Node 1 (EP node a1). Node 3 initiates pairing with Node 2. Node 1 then registers with Node 3. + +Domain B consists of Node 4 (DM B) and Node 5 (EP node b1). Node 4 initiates pairing with Node 5. + +A 'Figures dictionary' at the bottom defines the visual states: + + +- Green vertical bar: Temp DM pairing window is open +- Green vertical bar: Constant DM pairing window is open +- Grey vertical bar: DM pairing window is close +- Yellow hatched bar: EP scanning for secure MAPs for Tsearch +- Blue hatched bar: EP registering with secure DM +- Orange hatched bar: EP registered and paired with secure DM +- Red triangle: User push button event + + Annotations indicate that the pairing window is open for 120 seconds and that a 'Close pairing acceptance window' occurs at the end of this period. + +Diagram of multi-node pairing procedure resulting in two secure domains. The diagram shows five nodes (Node 1-5) and their interactions over time. Node 3 (DM A) and Node 4 (DM B) are temporary DMs. Node 1 (EP node a1) and Node 2 (EP node a2) pair with Node 3. Node 5 (EP node b1) pairs with Node 4. A 'Figures dictionary' at the bottom explains the color coding: green for open pairing windows, yellow for EP scanning, blue for EP registering, orange for EP registered, and red triangles for user push button events. A dashed line indicates the end of the 120-second pairing window. + +**Figure 6-43 – Multi-node pairing procedure that results in two secure domains** + +In Figure 6-43, node 3 becomes temporary DM of domain A and node 4 becomes temporary DM of domain B. Node 1 registers on temporary DM A and becomes EP node a1 in SD A. Node 2 registers on temporary DM A and becomes EP node a2 in SD A. Node 5 registers on temporary DM B and becomes EP node b1 in SD B. + +In order to avoid the problem described in the previous paragraphs, each temporary DM that completes a registration procedure successfully with one of its nodes may follow the procedure described in clause 6.2.2.2.1.1. + +###### **6.2.2.2.1.1 Merging of secure domains with temporary DMs** + +If this procedure is followed, the DM shall not become immediately a permanent DM, but it shall continue acting as a temporary DM until the expiry of the current pairing window. The temporary DM following the procedure described in clause 6.2.2.1.1 shall allocate a dedicated TXOP for the registered EP for scanning and pairing with other potential DMs. This temporary DM shall also use this TXOP to scan for other potential DMs. During this time, if the temporary DM detects MAPs from other temporary DMs, it shall register on the detected DM's domain as an EP node. In this procedure, any registered node that loses its temporary DM shall scan for MAPs from other DM and shall try to register with it. + +Figure 6-44 illustrates the merge procedure. + +NOTE – Figure 6-44 shows a particular sequence of PUSH\_P events. However, any other sequence of PUSH\_P events is also valid. + +![Sequence diagram of the multi-node pairing procedure. It shows four vertical lifelines: Target DM A, Node 2, Joining DM B, and Node 4. The process involves 'Temp DM' and 'Permanent DM' states, 'EP' (Endpoint) markers, 'Open pairing acceptance window', 'Registration with pairing' messages, 'MAP' detection, 'ITU-T G.9961 authenticating', and 'Close pairing acceptance window'. A note indicates the pairing window is open for 120 seconds. The final state shows two secure domains: one with DM A and EP node a4, and another with DM B and EP nodes a2 and a3.](c0b9e5fc63e19306394e0d4249da62cd_img.jpg) + +The diagram illustrates the multi-node pairing procedure across four lifelines: Target DM A, Node 2, Joining DM B, and Node 4. + +1. **Target DM A** starts in a 'Temp DM A' state with an 'EP' at the top. It has an 'Open pairing acceptance window'. + +2. **Node 2** (labeled 'EP node a2' at the bottom) is in an 'EP in domain A' state. + +3. **Joining DM B** starts in a 'Temp DM B' state with an 'EP' at the top. It also has an 'Open pairing acceptance window'. + +4. **Node 4** (labeled 'EP node a3' at the bottom) is in an 'EP in domain B' state. + +Sequence of events: + +- Node 2 sends 'Registration with pairing' to Target DM A. + +- Node 4 sends 'Registration with pairing' to Joining DM B. + +- Target DM A detects 'MAP B is detected' from Node 4. + +- Node 4 performs 'ITU-T G.9961 authenticating' with Target DM A. + +- Target DM A detects 'MAP A is detected' from Node 2. + +- Node 2 performs 'ITU-T G.9961 authenticating' with Target DM A. + +- Target DM A sends 'Registration with pairing' to Node 4. + +- Target DM A sends 'Registration with pairing' to Node 2. + +- Joining DM B detects 'MAP A is detected' from Target DM A. + +- Target DM A performs 'ITU-T G.9961 authenticating' with Joining DM B. + +- Joining DM B sends 'Close pairing acceptance window' to Target DM A. + +- Target DM A transitions to 'Permanent DM' state. + +- A note indicates 'The pairing window is open for 120 seconds'. + +Final states: + +- Target DM A (Permanent DM) is connected to Node 2 (EP node a2) and Joining DM B (EP node a4). + +- Joining DM B (Permanent DM) is connected to Node 4 (EP node a3) and Target DM A (EP node a2). + +Sequence diagram of the multi-node pairing procedure. It shows four vertical lifelines: Target DM A, Node 2, Joining DM B, and Node 4. The process involves 'Temp DM' and 'Permanent DM' states, 'EP' (Endpoint) markers, 'Open pairing acceptance window', 'Registration with pairing' messages, 'MAP' detection, 'ITU-T G.9961 authenticating', and 'Close pairing acceptance window'. A note indicates the pairing window is open for 120 seconds. The final state shows two secure domains: one with DM A and EP node a4, and another with DM B and EP nodes a2 and a3. + +Figure 6-44 – Multi-node pairing procedure that results in two secure domains + +## 6.3 Secure admission through a passphrase-based procedure + +In this procedure, the user sets up an SD by entering a passphrase (made up of ASCII characters) into each of the nodes it wants to connect to the domain. This passphrase is converted into a PW that is then converted into a domain-wide key that is used for encryption of communications between the nodes of the domain. + +### 6.3.1 Use cases + +This clause describes use cases for secure admission through a passphrase-based procedure. See Table 6-13. + +**Table 6-13 – Use cases for secure admission through a passphrase** + +| Use case | Description | Comments | +|----------|-----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | A user creates a secure domain with two nodes | The user creates a secure domain with two nodes by configuring them to work in secure mode | +| 2 | Join a node to existing secure domain | Every node for addition to the secure domain requires configuration with the same secure parameters as specified in the existing secure domain | + +#### **6.3.1.1 Use case 1 – A user creates a secure domain with two nodes** + +The user sets up an SD by configuring the same passphrase (ASCII) into each of the nodes it wants to connect to the domain. + +The user configures node 1 with the following parameters. + +- Secure mode – The security mode of the node may already be set to "secure mode" by the node's vendor. +- DN – The user may either configure the domain to use a non-default DN of its choosing, or it may use the default DN already specified by the node's vendor (i.e., the user does not need to configure the DN). +- User-specified passphrase in ASCII format – The way the user introduces the passphrase is vendor discretionary. + +After configuring the passphrase, the node shall derive a PW from the passphrase as specified in clause 6.3.2.1. An encryption key shall then be derived from the PW as specified in clause 6.3.2.2, as shown in Figure 6-45. + +![Diagram titled 'Use case 1: Step 1' showing the initial configuration of a non-secure domain 'A' containing two nodes, 1 and 2. A user icon is shown configuring node 1. An arrow points to the next state where node 1 is highlighted, with a note: 'The PW should be derived from the configured passphrase and then the NMK is generated from the PW in node 1'.](b774dfc5023e15e9c352b97ca25a56d4_img.jpg) + +The diagram illustrates the first step of creating a secure domain. On the left, a blue oval labeled 'A - non-secure domain' contains two nodes, 1 and 2. A user icon is shown with a callout 'Configure node' pointing to node 1. A large arrow points to the right, where the same oval now has node 1 highlighted in yellow. A text box next to it states: 'The PW should be derived from the configured passphrase and then the NMK is generated from the PW in node 1'. + +Diagram titled 'Use case 1: Step 1' showing the initial configuration of a non-secure domain 'A' containing two nodes, 1 and 2. A user icon is shown configuring node 1. An arrow points to the next state where node 1 is highlighted, with a note: 'The PW should be derived from the configured passphrase and then the NMK is generated from the PW in node 1'. + +G.9978(11-18)\_F6-45 + +**Figure 6-45 – Step 1: A user creates a secure domain with two nodes** + +The user configures node 2 with the following parameters. + +- Secure mode – The security mode of the node may already be set to "secure mode" by the node's vendor. +- DN – The user may either configure the domain to use a DN of its choosing, or it may use the name already specified by the node's vendor (i.e., the user does not need to configure the DN). +- User-specified passphrase in ASCII format – The way the user introduces the passphrase is vendor discretionary. + +After configuring the passphrase, the node shall derive a PW from the passphrase as specified in clause 6.3.2.1. An encryption key shall then be derived from the PW as specified in clause 6.3.2.2. + +Node 1 and node 2 establish an SD as shown in Figure 6-46. + +![Diagram for Use case 1: Step 2. It shows three stages of domain creation. Stage 1: A non-secure domain A contains node 1 (white circle) and node 2 (yellow circle). A user icon is shown with a 'Configure node' callout pointing to node 2. Stage 2: The same domain A, with a text box stating 'The PW should be derived from the configured passphrase and then the NMK is generated from the PW in node 2'. Stage 3: A secure domain B (purple oval) containing nodes 1 and 2. Arrows indicate a sequential process. A code 'G.9978(11-18)_F6-46' is in the bottom right.](cac61a60141d0335b4ae7a081f6b18d4_img.jpg) + +**Use case 1: Step 2** + +The user configures node 2 with secure parameters + +Configure node + +The PW should be derived from the configured passphrase and then the NMK is generated from the PW in node 2 + +A - non-secure domain + +A - non-secure domain + +B - secure domain + +G.9978(11-18)\_F6-46 + +Diagram for Use case 1: Step 2. It shows three stages of domain creation. Stage 1: A non-secure domain A contains node 1 (white circle) and node 2 (yellow circle). A user icon is shown with a 'Configure node' callout pointing to node 2. Stage 2: The same domain A, with a text box stating 'The PW should be derived from the configured passphrase and then the NMK is generated from the PW in node 2'. Stage 3: A secure domain B (purple oval) containing nodes 1 and 2. Arrows indicate a sequential process. A code 'G.9978(11-18)\_F6-46' is in the bottom right. + +**Figure 6-46 – Step 2: A user creates a secure domain with two nodes** + +#### 6.3.1.2 Use case 2 – Join a node to an existing secure domain + +This use case refers to a scenario where the user wants to add an additional node to an SD that was created by the passphrase method. + +The user configures node 3 with the secure parameter as specified in clause 6.3.1.1. + +After configuring the passphrase, the node shall derive a PW from the passphrase as specified in clause 6.3.2.1. An encryption key shall then be derived from the PW as specified in clause 6.3.2.2. + +Figure 6-47 illustrates use case 2 procedures. + +![Diagram for Use case 2. It shows three stages of joining a node to an existing secure domain. Stage 1: A secure domain B (purple oval) contains nodes 1 and 2 (white circles). A user icon is shown with a 'Configure' callout pointing to node 3 (yellow circle). Stage 2: The same domain B, with a text box stating 'PW should derived from the configured passphrase and then encryption key is generated from the PW in node 3'. Stage 3: The same domain B, with a text box stating 'Node 3 joins secure domain B'. Arrows indicate a sequential process. A code 'G.9978(11-18)_F6-47' is in the bottom right.](b5987d63203a5fa601921039922ac520_img.jpg) + +**Use case 2** + +The user configures node 3 with secure parameters + +Configure + +PW should derived from the configured passphrase and then encryption key is generated from the PW in node 3 + +Node 3 joins secure domain B + +B - secure domain + +B - secure domain + +B - secure domain + +G.9978(11-18)\_F6-47 + +Diagram for Use case 2. It shows three stages of joining a node to an existing secure domain. Stage 1: A secure domain B (purple oval) contains nodes 1 and 2 (white circles). A user icon is shown with a 'Configure' callout pointing to node 3 (yellow circle). Stage 2: The same domain B, with a text box stating 'PW should derived from the configured passphrase and then encryption key is generated from the PW in node 3'. Stage 3: The same domain B, with a text box stating 'Node 3 joins secure domain B'. Arrows indicate a sequential process. A code 'G.9978(11-18)\_F6-47' is in the bottom right. + +**Figure 6-47 – Join a node to an existing secure domain** + +### 6.3.2 Secure admission description + +The user sets up an SD by configuring the same passphrase (ASCII) into each of the nodes it wants to connect to the domain. + +In order to set up an SD, users need to perform the following configuration for each node they wish to connect to the SD. + +- 1) Configure the node to work in secure mode. The security mode of the node may already be set to "secure mode" by the node's vendor. +- 2) Configure a DN. Users may either configure the domain to use a DN of their choosing or they may use the name already specified by the node's vendor (i.e., the user does not need to configure the DN). +- 3) The user introduces a user-specified passphrase to the node in ASCII format. The way the user introduces the passphrase is vendor discretionary. + +After configuring the passphrase, the node shall derive a PW from the passphrase as specified in clause 6.3.2.1. An encryption key shall then be derived from the PW as specified in clause 6.3.2.2. + +An EP node configured to secure mode shall only try to register on a DM indicating it is operating in secure mode (indicated in MAP-Ds by the bit of the security-related domain info subfield, see clause 8.8.5.16 of [ITU-TG.9961]) and having the same configured DN. + +#### 6.3.2.1 Generation of the password from the user-introduced passphrase + +- The passphrase is a user-specified chain of characters with the following characteristics. + - Chain length: 12 ASCII characters (C0C1C2...CN...C11) + - Valid characters: [a-z];[A-Z];[0-9] +- The PW is a 96-bit binary chain: (b0b1...b95) + +Each character of the passphrase is converted into its 8-bit binary equivalent following [ISO/IEC 8859-1], starting from C0. The MSB of the binary representation corresponds to the first bit of the byte: + +##### Example + +- Passphrase: GhnCertf2013 +- ASCII codes: + +| Character | G | h | n | C | e | r | t | f | 2 | 0 | 1 | 3 | +|------------------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------| +| ASCII code (hex) | 47 | 68 | 6E | 43 | 65 | 72 | 74 | 66 | 32 | 30 | 31 | 33 | +| ASCII code (bin) | 01000111 | 01101000 | 01101110 | 01000011 | 01100101 | 01110010 | 01110100 | 01100110 | 00110010 | 00110000 | 00110001 | 00110011 | + +- PW: +**0100011101101000011011100100001101100101011100100111010001100110001100100** +**011000000011000100110011** + +#### 6.3.2.2 Generation of the domain-wide key from the password + +The network membership key (NMK) is derived from the PW by: + +- the first 96 bits of the NMK are the 96 bits of the PW. +- the next 32 bits are the repetition of the first 32 bits of the PW. + +##### Example + +- PW: +**0100011101101000011011100100001101100101011100100111010001100110001100100** +**011000000011000100110011** + +– NMK +**0100011101101000011011100100001101100101011100100111010001100110001100100** +**011000000011000100110011010001110110100000110111001000011** + +## **6.4 Admission through the auto-pairing mechanism** + +This clause defines a pairing method that enables establishment of an SD that requires minimal user intervention. + +This pairing method is based on automatic flow where a node that is not paired triggers the PUSH\_P event automatically once it has been plugged into the network and tries to create or join an SD within a pairing window time. + +### **6.4.1 Use cases** + +This clause describes the use cases for secure admission through auto-pairing. See Table 6-14. + +**Table 6-14 – Use cases for secure admission through auto-pairing** + +| Use case | Description | Comments | +|----------|------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| 1 | A user creates a secure domain with multi-nodes | The nodes that are plugged into the network during the pairing window time shall create a secured domain | +| 2 | A user adds a node to an existing domain after the pairing window time has expired | The nodes that are plugged into the network after the pairing window time has expired shall move to the unconnected state | +| 3 | Fault case – The user plugs only one node into the network | The node will open the auto-pairing timer and once the timer has expired the node should move into the unconnected state | + +NOTE – The blue bubbles in Figures 6-44 and 6-45 refer to nodes that are in unconnected mode or nodes in an NSD. + +#### **6.4.1.1 Use case 1 – A user creates a domain with multi-nodes** + +In this case, in order to join nodes to an existing SD the user has to plug all nodes into the network within one pairing window time. + +An SD with nodes 1, 2, 3 and 4 is established as illustrated in Figure 6-48. + +![Diagram titled 'Use case 1' showing the creation of a secure domain. On the left, a user icon is shown plugging nodes 1, 2, 3, and 4 into a blue oval labeled 'A - non-secure domain'. Above the nodes are four bubbles with the text 'Plug on'. An arrow points to the right, where a purple oval labeled 'B - secure domain' contains nodes 1, 2, 3, 4, and 5. Text above the right oval states 'Node 1, 2, 3 and 4 create secure domain B'. Text at the top left of the diagram states 'The user plug node 1, 2, 3 and 4 into the network during the pairing window time'.](9cd7ec4a653f07d02def283cb6f2309e_img.jpg) + +Diagram titled 'Use case 1' showing the creation of a secure domain. On the left, a user icon is shown plugging nodes 1, 2, 3, and 4 into a blue oval labeled 'A - non-secure domain'. Above the nodes are four bubbles with the text 'Plug on'. An arrow points to the right, where a purple oval labeled 'B - secure domain' contains nodes 1, 2, 3, 4, and 5. Text above the right oval states 'Node 1, 2, 3 and 4 create secure domain B'. Text at the top left of the diagram states 'The user plug node 1, 2, 3 and 4 into the network during the pairing window time'. + +G.9978(11-18)\_F6-48 + +**Figure 6-48 – A user creates a domain with multi-nodes** + +#### 6.4.1.2 Use case 2 – A user adds a node to an existing secure domain after the pairing window time has expired + +In this case, the user plugs node 3 into the network after the pairing window of the SD has expired. If node 3 does not find any secure DM with an auto-pairing window open, it shall move to the unconnected state as illustrated in Figure 6-49. + +![Diagram for Use case 2 showing a user adding node 3 to an existing secure domain B after the pairing window has expired.](107c8e1abcb7033ad244e30e7a910045_img.jpg) + +The diagram, titled "Use case 2", illustrates a scenario where a user attempts to add a new node to an existing secure domain after the pairing window has expired. On the left, a text box states: "The user plugs node 3 into the network in an existing secure domain (nodes 1 and 2) after the pairing window timer has expired". Below this, a person icon is shown with a "Plug on" button, with an arrow pointing to node 3. Node 3 is inside a purple oval labeled "B - secure domain" along with nodes 1 and 2. An arrow points from node 3 to another purple oval on the right, also labeled "B - secure domain", which contains nodes 1 and 2. A text box next to node 3 in the second oval states: "As node 3 does not find a secure DM with an open pairing window, it should move to the unconnected state". The diagram is labeled "G.9978(11-18)\_F6-49" at the bottom right. + +Diagram for Use case 2 showing a user adding node 3 to an existing secure domain B after the pairing window has expired. + +**Figure 6-49 – A user adds a node to an existing domain after the pairing window time has expired** + +In order to complete the admission process to SD B, node 3 shall follow the procedure described in clause 6.2.1.2.1. + +#### 6.4.1.3 Use case 3 – Fault case – The user plugs only one node into the network + +In this fault case, the user plugs only one node into the network. + +In this fault case, nothing should happen. This case is considered to be a faulty case because the user does not complete the pairing procedure. In this case, after the pairing window has expired the node shall move to the unconnected state, as illustrated in Figure 6-50. + +![Diagram for Use case 3 showing a user plugging only one node into the network, which then moves to an unconnected state after the autopairing window expires.](31ef15d175af5babdbf4d2fbac884c1b_img.jpg) + +The diagram, titled "Use case 3", illustrates a fault case where a user plugs only one node into the network. On the left, a text box states: "The user plug only one node into the network". Below this, a person icon is shown with a "Plug on" button, with an arrow pointing to node 1. An arrow points from node 1 to another node 1 on the right. A text box next to the second node 1 states: "After autopairing window expired the node should move into unconnected state". The diagram is labeled "G.9978(11-18)\_F6-50" at the bottom right. + +Diagram for Use case 3 showing a user plugging only one node into the network, which then moves to an unconnected state after the autopairing window expires. + +**Figure 6-50 – Fault case – The user plugs only one node into the network** + +### 6.4.2 Secure admission by pairing in an auto-pairing scenario + +A pairing mechanism in an auto-pairing scenario enables the user to convert an NSD to an SD or to add one or more nodes to an SD, just by plugging them into the network. + +Table 6-15 lists system parameters for the pairing mechanism in an auto-pairing scenario. + +**Table 6-15 – Parameters for pairing mechanism in an auto-pairing scenario** + +| Parameter | Description | Medium | | | | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------| +| | | Power-line baseband | Coax BB | Coax RF | Phone line | +| $t_{\text{PAIRING}}$ | Pairing window that starts after a PUSH_P event is triggered, after plugging the node into the network. During this period, the DM shall confirm the registration pairing request | 60-300 s | 60-300 s | 60-300 s | 60-300 s | +| T_EP_INTERVAL | The interval during which a pairing node acts as an EP trying to pair with a secure domain until it shall alternate to a temporary domain master | Random value in the range 0-10 s | Random value in the range 0-10 s | Random value in the range 0-10 s | Random value in the range 0-10 s | +| T_TMPDM_INTERVAL | Period of time during which a node in a pairing procedure shall act as a temporary domain master before it alternates to an endpoint node for scanning | Random value in the range 4-8 s | Random value in the range 4-8 s | Random value in the range 4-8 s | Random value in the range 4-8 s | + +NOTE – The value of $t_{\text{PAIRING}}$ is vendor discretionary and is usually fixed by an external entity (e.g., HomeGrid Forum, [b-HomeGrid]). + +The procedure for the auto-pairing scenario shall be the same as specified in clause 6.2.2.1 except for the following differences: + +- 1) the pairing window time ( $t_{\text{PAIRING}}$ ) shall be as specified in Table 6-15; +- 2) the pairing event is triggered once the node (that is not paired) has been plugged into the network. + +#### 6.4.2.1 Pairing registration in an auto-pairing scenario + +The protocol of the pairing registration in an auto-pairing scenario shall work similarly to that specified in clause 6.2.2.2, except for the following two differences: + +- 1) the pairing window time ( $t_{\text{PAIRING}}$ ) should be as specified in Table 6-15; +- 2) the pairing event is triggered once the node (that is not paired) is plugged into the network. + +The pairing registration protocol diagram is presented in Figure 6-51. + +![Sequence diagram of the pairing registration process in an auto-pairing scenario. It shows three lifelines: DM, Joining node 1, and Joining node 2. The process starts with a DM opening a pairing window. A Joining node sends a registration request, which the DM responds to. Then, the DM authenticates with the Joining node using the ITU-T G.9961 authentication protocol. A second Joining node then joins the network, and the DM authenticates it as well. The pairing window closes after the second node is authenticated.](352d21d1e740e4a58cb17ab8656cfad8_img.jpg) + +``` + +sequenceDiagram + participant DM + participant JN1 as Joining node + participant JN2 as Joining node + + Note over DM: User plugs a node +in the network + Note left of DM: Open pairing +acceptance window + rect rgb(144, 238, 144) + DM->>DM: + end + + Note over JN1: User plugs a node +in the network + JN1->>JN1: Scan for +secure DM + Note right of JN1: Secure MAP is +detected + JN1->>DM: ADM_NodeRegistrRequest.req + DM->>JN1: ADM_DmRegistrResponse.cnf + + Note over DM,JN1: ITU-T G.9961 Authentication (clause 9.2) + DM<->JN1: Authentication protocol (clause 9.2 of ITU-T G.9961) + + Note over JN2: User plugs a node +in the network + Note right of JN2: The user has T_PAIRING +seconds to plug the +other node PUSH_P + JN2->>JN2: Scan for +secure DM + Note right of JN2: Secure MAP is +detected + + Note over DM,JN2: ITU-T G.9961 Authentication (clause 9.2) + DM<->JN2: Authentication protocol (clause 9.2 of ITU-T G.9961) + + Note left of DM: Close pairing +acceptance window + +``` + +The diagram illustrates the sequence of events for pairing registration in an auto-pairing scenario. It features three main entities: a Domain Manager (DM) and two Joining nodes. + 1. \*\*DM Pairing Window\*\*: The DM opens a pairing acceptance window upon being plugged into the network. This window remains open until the pairing of the second node is received or until the expiration of the $T_{PAIRING}$ timer. + 2. \*\*First Joining Node Registration\*\*: A Joining node is plugged into the network, detects the Secure MAP, and scans for a secure DM. It sends an `ADM_NodeRegistrRequest.req` to the DM, which responds with an `ADM_DmRegistrResponse.cnf`. + 3. \*\*First Authentication\*\*: The DM and the first Joining node perform an ITU-T G.9961 Authentication (clause 9.2) exchange. + 4. \*\*Second Joining Node Registration\*\*: A second Joining node is plugged into the network. The user has $T_{PAIRING}$ seconds to plug this node (PUSH\_P). It also detects the Secure MAP and scans for a secure DM. + 5. \*\*Second Authentication\*\*: The DM and the second Joining node perform another ITU-T G.9961 Authentication (clause 9.2) exchange. + 6. \*\*Pairing Window Closure\*\*: After the second node is authenticated, the DM closes the pairing acceptance window. + The diagram is labeled with 'G.9978(11-18)\_F6-51' at the bottom right. + +Sequence diagram of the pairing registration process in an auto-pairing scenario. It shows three lifelines: DM, Joining node 1, and Joining node 2. The process starts with a DM opening a pairing window. A Joining node sends a registration request, which the DM responds to. Then, the DM authenticates with the Joining node using the ITU-T G.9961 authentication protocol. A second Joining node then joins the network, and the DM authenticates it as well. The pairing window closes after the second node is authenticated. + +**Figure 6-51 – Pairing registration process in an auto-pairing scenario** + +On plugging a DM into the network, it shall open the pairing window for a period of $t_{PAIRING}$ . + +On receipt of an `ADM_NodeRegistrRequest.req` message, the DM shall process the registration request and shall reply within `REG_RESP_TIME` to the requesting node with an `ADM_DmRegistrResponse.cnf` message. + +If the DM receives the registering request message while it is within a pairing window, the `ADM_DmRegistrResponse.cnf` message shall include the following fields: + +- a status flag with a success registration indication; +- a PW needed for the authentication procedure (see clause 9.2 of [ITU-T G.9961]); +- a non-zero `DEVICE_ID` for the registering node assigned by the DM; +- all other relevant configuration data as specified in [ITU-T G.9961]. + +On receipt of the `ADM_DmRegistrResponse.cnf` message, the joining node shall identify the `ADM_DmRegistrResponse.cnf` message based on its `REGID` field and adopt the DN of the domain that replied positively and its new assigned `DEVICE_ID`. The joining node shall use the PW included in the `ADM_DmRegistrResponse.cnf` message for the authentication procedure as specified in clause 9.2 of [ITU-T G.9961]. + +If the DM receives a registration request while its pairing window is closed, it shall reject the registration request by replying to the registering node with a `ADM_DmRegistrResponse.cnf` message that contains the status flag set to zero and an extended rejection code 0x3 that indicates that + +the registration request is rejected for the reason that "pairing window is closed" and the DEVICE\_ID shall be set to zero. + +During the $t_{\text{PAIRING}}$ period, the DM shall block any other PUSH\_P events and shall ignore any new PUSH\_P events. After expiry of the $t_{\text{PAIRING}}$ period, the DM shall unblock receipt of new PUSH\_P events and close the pairing acceptance window. + +#### 6.4.2.2 Conversion of a non-secure domain to a secure domain in an auto-pairing scenario + +The multi-node pairing mode enables the user to convert an entire NSD to an SD by triggering a PUSH\_P event on all the nodes of the domain. This procedure in an auto-pairing scenario shall be the same as that specified in clause 6.2.2.2.1, except for the following differences: + +- 1) the pairing window time ( $t_{\text{PAIRING}}$ ) shall be as specified in Table 6-15; +- 2) the pairing event is triggered once the node (that is not paired) has been plugged into the network. + +# 7 Secure admission methods selection + +## 7.1 Information on secure supported admission methods + +The DM of the domain is the entity responsible for selecting which admission methods are accepted for a node to request the admission in the domain. The default accepted secure methods for a domain shall be the secure admission methods supported by the first DM since creation of the domain. The new DM shall not change the accepted admission methods when the DM changes. + +The DM shall publish the list of accepted admission methods through the AdmissionMethodsInfo subfield: the security-related auxiliary information field of the MAP-D. The contents of this field shall follow the format presented in Table 7-1. + +**Table 7-1 – Format of AdmissionMethodsInfo subfield** + +| Field | Octet | Bits | Description | +|-------------------------------------------------------------------------------------------------------------|-------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GeneralMethods | 0 | [7:0] | Bitmap representing different methods that are accepted to admit a new node into the domain. Bit 0 represents the LSB. When the bit is set to one, the corresponding methods are accepted as a valid method. When the bit is set to zero, the method is not accepted as a valid method.
Bit 0: Admission through passphrase (see clause 6.3).
Bit 1: Admission through Auto-pairing (see clause 6.4).
Bit 2-7: Reserved by ITU-T (Note) | +| PushButtonMethods | 1 | [7:0] | Bitmap representing different methods that are accepted to admit a new node into the domain. Bit 0 represents the LSB. When the bit is set to one, the corresponding methods are accepted as a valid method. When the bit is set to zero, the method is not accepted as a valid method.
Bit 0: Admission through generic pairing – Single-node pairing mode (see clause 6.2.2.1).
Bit 1: Admission through generic pairing – Multi-node pairing mode (see clause 6.2.2.2).
Bit 2-7: Reserved by ITU-T (Note) | +| MACMethods | 2 | [7:0] | Bitmap representing different methods that are accepted to admit a new node into the domain. Bit 0 represents the LSB. When the bit is set to one, the corresponding methods are accepted as a valid method. When the bit is set to zero, the methods is not accepted as a valid method.
Bit 0: Admission through MAC authorization (see clause 6.1).
Bit 1-7: Reserved by ITU-T (Note) | +| NOTE – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. | | | | + +## 7.2 Interoperability between secure admission methods + +This Recommendation specifies multiple secure admission methods for G.hn networks and one or more secure admission methods are allowed to be used in the same domain. The DM shall publish the list of secure admission methods that are used by its domain in the MAP-D (see clause 7.1). + +A secure G.hn domain compliant with this Recommendation shall use at least one of the secure admission methods specified in this Recommendation. It may also enable use of multiple secure admission methods simultaneously. + +If a node that wants to register in the G.hn domain does not support any of the admission methods specified in the received MAP-D, it shall not try to register on the domain. + +The auto-pairing method and passphrase-based method are used to create an SD. The generic pairing method can also be used to create an SD if an SD is not created successfully through an auto-pairing method (i.e., nodes are in the unconnected state). + +If auto-pairing is not supported, an NSD may be created. By using any one of the passphrase-based, generic pairing and MAC authorization methods, the NSD can be converted into an SD or parts of the nodes in the NSD can form an SD. + +If multiple secure admission methods are used simultaneously, a node and a DM shall act in accordance with the following rules for interoperability: + +- a node shall ignore the PUSH\_P events that are triggered during the auto-pairing process; +- the unconnected node that is capable of supporting the MAC authorization method and generic method shall search for MAP frames from any SD and be ready to join an SD through a MAC authorization method until it detects the PUSH\_P event; +- during the generic pairing window time, if an unconnected node that is capable of supporting the MAC authorization method and generic method detects any secured MAP that contains a MAC authorization information subfield that includes information matching its REGID (see clause 6.1.2.2.2) or any secured MAP with the "Registrationoffer" field set to 1 (see clause 6.1.2.2.1), it shall register in this domain with the "PairingReq" field of the ADM\_NodeRegistrRequest.req message set to 1; +- during the generic pairing window time, if a non-secure active node that is capable of supporting the MAC authorization method and generic method detects any secured MAP that contains a MAC authorization information subfield that includes information matching its REGID, it shall register in this domain with the "PairingReq" field of ADM\_NodeRegistrRequest.req message set to 1; +- if the DM of an SD that enables the use of both generic pairing and MAC authorization methods is triggered with a PUSH\_P event during the MAC authorization process (see clause 6.1.2.2), it shall open a generic pairing window in parallel (see clause 6.2.2); +- for a node that has registered on a secure DM during the MAC authorization process, either by detecting the secure MAP with the "Registrationoffer" field set to 1 (see clause 6.1.2.2.1) or by detecting the secure MAP contains a MAC authorization information subfield that includes information matching its REGID (see clause 6.1.2.2.2), if it is triggered with PUSH\_P events, it shall ignore the PUSH\_P events; +- a node shall join the domain if it is configured with the passphrase and other related parameters of this domain bypassing other secure admission methods; +- the node that is configured with a passphrase and other related parameters shall ignore the PUSH\_P events that are triggered before it become a member of the corresponding domain. + +# 8 Management message OPCODEs + +Management message OPCODEs are formatted as 12-bit unsigned integers. Valid values of OPCODEs are presented in Table 8-1. + +**Table 8-1 – OPCODEs of management messages** + +| Category | Message name | OPCODE (hex) | Description | MMPL Reference | +|------------------------|-----------------------------|--------------|---------------------------------------------------------------------------------------------------------|-------------------| +| Secure Admission (B0X) | ADM_UI_MACauthorization.req | B00 | Report the DM about the list of authorized nodes | Clause 6.1.2.4.1 | +| | ADM_UI_MACauthorization.cnf | B01 | Confirm receiving the ADM_UI_MACauthorization.req message | Clause 6.1.2.4.2 | +| | ADM_SecureDomain.req | B02 | Send PW and related parameters to the joining nodes | Clause 6.1.2.4.3 | +| | ADM_SecureDomain.cnf | B03 | Confirm receiving the ADM_SecureDomain.req message | Clause 6.1.2.4.4 | +| | ADM_UI_MACauthorization.ind | B04 | Report the DM about the MAC authorization event | Clause 6.1.2.4.5 | +| | ADM_UI_MACauthorization.rsp | B05 | Response to the ADM_UI_MACauthorization.ind message | Clause 6.1.2.4.6 | +| | SC_UI_Authorization.req | B06 | Request to be authorized as a proxy node by the SC for MAC authorization-based secure admission. | Clause 6.1.2.4.7 | +| | SC_UI_Authorization.cnf | B07 | Confirm receiving the SC_UI_Authorization.req message | Clause 6.1.2.4.8 | +| | SC_UI_Authorization.ind | B08 | Report the new proxy node for MAC authorization-based secure admission. | Clause 6.1.2.4.9 | +| | ADM_SelfNotify.ind | B09 | Broadcast by new unconnected node to the network to notify the existence of the new node with its REGID | Clause 6.1.2.4.10 | +| | ADM_UINewNodeExist.ind | B0A | Sent from the DM to the UI node to convey the REGID of the new unconnected node | Clause 6.1.2.4.11 | +| Reserved | Reserved | B0B-BFF | Reserved by ITU | | + +# Bibliography + +- [b-ITU-T G.9960] Recommendation ITU-T G.9960 (2015), *Unified high-speed wireline-based home networking transceivers – System architecture and physical layer specification.* +- [b-ITU-T G.9962] Recommendation ITU-T G.9962 (2014), *Unified high-speed wire-line based home networking transceivers – Management specification.* +- [b-HomeGrid] HomeGrid Forum (2014). *Any wire. Anywhere. It just works.* Geneva: HomeGrid Forum. + + + + + + +# 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/T/T-REC-T.100-198811-I_PDF-E/05c9994c1f5daf53d0d9b107657d7a17_img.jpg b/marked/T/T-REC-T.100-198811-I_PDF-E/05c9994c1f5daf53d0d9b107657d7a17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89f40bf295611813fe3363a095394c6d5aee232d --- /dev/null +++ b/marked/T/T-REC-T.100-198811-I_PDF-E/05c9994c1f5daf53d0d9b107657d7a17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a7322ca9c47fa70997944d7aa3b3b78d1c053650871b7748478fd51bc676848 +size 1718 diff --git a/marked/T/T-REC-T.100-198811-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/T/T-REC-T.100-198811-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a6ad206156d2ced8fb704573daf8a4e0f1c97f3 --- /dev/null +++ b/marked/T/T-REC-T.100-198811-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df14c3a43b2441a05a266657f9346c6729222b0b0b5ccca0074d51292c339769 +size 19763 diff --git a/marked/T/T-REC-T.100-198811-I_PDF-E/1630bfd9ebf9b95faec11ae6cdfd9c0a_img.jpg b/marked/T/T-REC-T.100-198811-I_PDF-E/1630bfd9ebf9b95faec11ae6cdfd9c0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d102c07916c4d7798847a585861dafea12e21733 --- /dev/null +++ b/marked/T/T-REC-T.100-198811-I_PDF-E/1630bfd9ebf9b95faec11ae6cdfd9c0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21ca695b477e8cfd7bde7b95480e017381ee7809fc9f7d3e729c2a7462a82007 +size 1583 diff --git a/marked/T/T-REC-T.100-198811-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg b/marked/T/T-REC-T.100-198811-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..852c816a8e9934d4e8ac50df68f70b8c300d5b45 --- /dev/null +++ b/marked/T/T-REC-T.100-198811-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3b1755d9bdc6ec92c278783c9db6a257f36abce2fc12909159568fd8246fb70 +size 15116 diff --git a/marked/T/T-REC-T.100-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/T/T-REC-T.100-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bee77a7310a14253d134941ffca8832e7e0d6294 --- /dev/null +++ b/marked/T/T-REC-T.100-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f4ad019e7fc91e306bfbc1ef9d89a00172f7d0087d75da0c7d6e47fa2c52c34 +size 7464 diff --git a/marked/T/T-REC-T.100-198811-I_PDF-E/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/T/T-REC-T.100-198811-I_PDF-E/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e076c8c5aaf4c9e4c2b21a5167b6851a7d626ee8 --- /dev/null +++ b/marked/T/T-REC-T.100-198811-I_PDF-E/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5bd38266af2cf5cc5bc922589a9cfaa8f0ec0c63fa9a7042b5e6171709f1126 +size 130239 diff --git a/marked/T/T-REC-T.100-198811-I_PDF-E/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/T/T-REC-T.100-198811-I_PDF-E/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf6e80ded68cffc420af16b6a5ff544048bc20c8 --- /dev/null +++ b/marked/T/T-REC-T.100-198811-I_PDF-E/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df0f9b03cd558395e15fa30fe92929d3cf4d157cda57f74a2f01fbe6f39b21f5 +size 30911 diff --git a/marked/T/T-REC-T.100-198811-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/T/T-REC-T.100-198811-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daa53bbb265e993d9b221f25405a8c728628511e --- /dev/null +++ b/marked/T/T-REC-T.100-198811-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:061f9869c6d93fd7547e76545450bd6e57a0d8ae4ea7f5986e6f18ef35565a9a +size 59562 diff --git a/marked/T/T-REC-T.100-198811-I_PDF-E/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg b/marked/T/T-REC-T.100-198811-I_PDF-E/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94f0fb262b5cf82eaebd6badfd08d6ab36aa74cd --- /dev/null +++ b/marked/T/T-REC-T.100-198811-I_PDF-E/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6da44adbf83c0ba6f870325fb06c63c52879cd2587f3c3fb2fdf545346c6e59d +size 31446 diff --git a/marked/T/T-REC-T.100-198811-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/T/T-REC-T.100-198811-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1ef23bbda8467c8c79d9f52738c2af14d887c52 --- /dev/null +++ b/marked/T/T-REC-T.100-198811-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24a2adda0db9bcf63471b40de3b0434b3b050aa1bd792c33a1e866b1ce5e4e48 +size 5799 diff --git a/marked/T/T-REC-T.134-199802-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg b/marked/T/T-REC-T.134-199802-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5aa40e44d852a208d8719a63a52bef88f924938a --- /dev/null +++ b/marked/T/T-REC-T.134-199802-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:851d9165788b729058bc3ec96614fc4e967c2c0a120ea98ddc2e3b4f46e821f9 +size 93624 diff --git a/marked/T/T-REC-T.134-199802-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/T/T-REC-T.134-199802-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c3b2397f6e41047d55e53ae3132463cb25a354e --- /dev/null +++ b/marked/T/T-REC-T.134-199802-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4fcfd496b629234712fa52dc90c9f6694f3694af865f6a7562c928c2fa89cb7 +size 8191 diff --git a/marked/T/T-REC-T.134-199802-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/T/T-REC-T.134-199802-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc739e7489b40fd7014c6233b173bfed3712c422 --- /dev/null +++ b/marked/T/T-REC-T.134-199802-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5dc1eaa52391dacac725d8125b3e4c6e9aa4edf052cd46ec099ae4ee73046b9c +size 8161 diff --git a/marked/T/T-REC-T.134-199802-I_PDF-E/c803f6f6e2c49429d2951832bd0f208d_img.jpg b/marked/T/T-REC-T.134-199802-I_PDF-E/c803f6f6e2c49429d2951832bd0f208d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b40adccdbd780bd4afd4f26984bf54af2a2b3d1 --- /dev/null +++ b/marked/T/T-REC-T.134-199802-I_PDF-E/c803f6f6e2c49429d2951832bd0f208d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa44bd53738379783728ef9768452337ab80f73aa2c7b5d38776a0a874a8246a +size 10343 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/08246879b7e3340f5c7af67ca43e48ff_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/08246879b7e3340f5c7af67ca43e48ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf12857c35797fc2f92f64457ed2f409fd2d663c --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/08246879b7e3340f5c7af67ca43e48ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0a64d9b4ee27a4e650334c384aca5d61d40fa5b4182edca955c3cdb18d29c9f +size 123037 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/28583b06f211df822423d245dfad776f_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/28583b06f211df822423d245dfad776f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30214a70b1904d4c7ce1e7001ca9b04c3e725152 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/28583b06f211df822423d245dfad776f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf5da520a0917a5337dfb51334f237851137efcc72a252dc99162d5e0196b1ca +size 67275 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c3b2397f6e41047d55e53ae3132463cb25a354e --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4fcfd496b629234712fa52dc90c9f6694f3694af865f6a7562c928c2fa89cb7 +size 8191 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/33af44bc1e5166e9cc1f4f29077ee09b_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/33af44bc1e5166e9cc1f4f29077ee09b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cc51814074b31d9e082f87590cdd7b034c1be26 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/33af44bc1e5166e9cc1f4f29077ee09b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8169fc5c94c906909d2ab3f2645eb9e44c6cbd865864c88fd50c30033f3b757 +size 42404 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/33cbd34b2ff74e39d12fae4db73f5b41_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/33cbd34b2ff74e39d12fae4db73f5b41_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8383a45e7940616eadf11d6f4a2039fd30c2f0a4 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/33cbd34b2ff74e39d12fae4db73f5b41_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c10a89a2ba82aedad5fc5ecc193e96495f2e9998b572b1e4be21d68b0a77536 +size 80771 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a39dd098ec07f0b880af3e2ebf1cc401b9c8d45d --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2b27db89ad07a5d280f808bf9a46b59c9a554986c28712b92767f4862994038 +size 35446 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/34b381406f073080ef510a32772b2612_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/34b381406f073080ef510a32772b2612_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdbc4f123e930aa29246522fbe5d0f985cb13542 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/34b381406f073080ef510a32772b2612_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c79e1632b65d85e3d745526e85726b09d80d228b15294ce4e3d05e9cb665097 +size 58684 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32c9a3d5a37ea33fd10c6ff3c9162f0945f5479d --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63a5bd1b5f4dc5aea5b42c386038a40726c38240449151fc2dd4eca27d1207d7 +size 52151 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/46c9f96273985599bf874713263feb52_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/46c9f96273985599bf874713263feb52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b77f48f0859814aaf2799e9b68acd3e9b2090138 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/46c9f96273985599bf874713263feb52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1853f120b70120ae6494544e05fa34333c8e858def39b3fedffbbbf6826b4369 +size 52403 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/48adb97a6a4a14b039450192f25cc1e0_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/48adb97a6a4a14b039450192f25cc1e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c68aa22e911bfd926ed6087a3501c555d13f6671 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/48adb97a6a4a14b039450192f25cc1e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db83cd8b890a9f7113949149b415fc4e492693cadb85b751379e2c9a34fa0f83 +size 38545 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/4e453d478a82d0f883c69bbf1a6afe41_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/4e453d478a82d0f883c69bbf1a6afe41_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1eff8396e346d7e2a34456992f07020af7795d60 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/4e453d478a82d0f883c69bbf1a6afe41_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4fdaff58bd0bec7830a6acbac436289b9bf5a1e7ecb39264ec5ab040805dc87 +size 108157 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6399da9ea8ba885af89ab17d23be1bb8a91f7a69 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e0cc9c6310521bde7457a54d044a804df0ee3ffca3e1584f1e5ac34f9de9fca +size 90457 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/5509e6ec160899dd306e462bb6a3643b_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/5509e6ec160899dd306e462bb6a3643b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b64b8bb768bcc21ad36946219246f232b1862847 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/5509e6ec160899dd306e462bb6a3643b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0278f1709edbb66be59afa052ba784733a133c9c5f2fb21106dbcf0688627db1 +size 24417 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..587c8d83515fa77ac129fa681627869047b672d7 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a29701355eae9ff2918f3880bd28635b06a9459e6e5dbc6f6ae7973b58e273a4 +size 71450 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0639bcbd716ecb4d4a9b446b08fb0d392d08399 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8eb88122d25bef98ead6fdb99bb19ccd028f831cd213499cc0c08bdfe3295e1 +size 46683 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/6a8b298a198b8ca2067f7adf3c8c6317_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/6a8b298a198b8ca2067f7adf3c8c6317_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91102fe2b2aa90094a9a3d15ac6aebddf2fb504b --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/6a8b298a198b8ca2067f7adf3c8c6317_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f4c2d62f72dce3f0fb07e79105d6b009f04c8c39acb3e56a9ede8e9e4b431f4 +size 157262 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/6f46eccb86e008f8bc7af8ea3ab806a7_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/6f46eccb86e008f8bc7af8ea3ab806a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c190422480725728f4ebe391403d7fdec9fb0530 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/6f46eccb86e008f8bc7af8ea3ab806a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ce5084d17a11785cf3b22432fea3e301e842bfb3a3c5eafd0ad13fc2da380a7 +size 39113 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baf88cdec820ed79f12e1216333677ef52675e3f --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3eb329616eb1137824b562bf9cbb62d1e8c49b279be7c66f4a0ef22ca2356d0f +size 49076 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/733da1815169d31c06238e8cd6ae23f2_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/733da1815169d31c06238e8cd6ae23f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad38c581e621a05416c3c855d4b15f5cd910bdd2 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/733da1815169d31c06238e8cd6ae23f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a518250d06a745f879346ee27594ef7793c99a379e93cddba9628d8e4086ea4d +size 61065 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..067f792b79efe52a2bdf57f77ea0377e751bbc8b --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65250ace6055fe65931cb5121829c0010d8f2e606bbb29a142cd51c69b28e404 +size 100117 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/886963464425186f4a465fa8155d2a3c_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/886963464425186f4a465fa8155d2a3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93d46c8488ca20f414c79a1436890aa2198a7c75 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/886963464425186f4a465fa8155d2a3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3874aef1ebadcbbdb442935aaf9d4c08b9b136e86f853d81f03680a0e6effe8 +size 39993 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/99bc201efaff9a7c0a66a617b474a29c_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/99bc201efaff9a7c0a66a617b474a29c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1801082f258e651e451a52784d6f3b2cddfc1dc7 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/99bc201efaff9a7c0a66a617b474a29c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28fe42a67fdb056c373c6fcf1a5cd948aad35918d7aedf8355982ea88a5bbb93 +size 14840 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9d2b4db0e036f668cecbabd4ab888a09d77d305 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1065d43876084423c79402740af36e0c58db53875ccc6045378b83aa55264dca +size 48895 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbf0af10fdc455767491686e6b28b7f617b35682 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7729f560e5968025da8c4038d5c2460e343eb4c6d3423d0dd38b99f73d4270f +size 14577 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f37ffb0f132eb101bb5ddbe809768e70126e5056 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:585e896e99b490fd6355dc0200009af4abf7ffd9aa2030b16eb8d3a51c3f0fae +size 93734 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/b18c13296cba7ef8a7113fc1b8ac6ef1_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/b18c13296cba7ef8a7113fc1b8ac6ef1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..335a3efae8e302433749b0b9604e53da8a411209 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/b18c13296cba7ef8a7113fc1b8ac6ef1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:353040ce629f72724f1ab8f74bdb1a6f02d06f96d2f6709fcd67ed14f0a7d748 +size 11441 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/b3e20b3a7c662b6f564c2b92175a2909_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/b3e20b3a7c662b6f564c2b92175a2909_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95c63b0c8920d8a86954d9fa6564215b0483f27b --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/b3e20b3a7c662b6f564c2b92175a2909_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:484ad0a609d54f104a6314d92996d1d4b1bd656a979367dacc336510c71bdd93 +size 8380 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/b441ce2f4621bf0259ef1965a02eebea_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/b441ce2f4621bf0259ef1965a02eebea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d95848434aee49c1dcbc15511b6b3edaf83f961 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/b441ce2f4621bf0259ef1965a02eebea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0af8732a15108dbd20a768a3c61f69576b18a76e6d3901b5ac34874676cbe13 +size 27033 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/b6453246018f11d6b771d4e0a3976328_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/b6453246018f11d6b771d4e0a3976328_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d42a014a43dfc4c7288330ce3b2e120e35f533cf --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/b6453246018f11d6b771d4e0a3976328_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad08f2bedac556f0a99b0178ea7fb17e2d9cc4ddef2afae57e88680419b4f20b +size 85187 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/c803f6f6e2c49429d2951832bd0f208d_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/c803f6f6e2c49429d2951832bd0f208d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b0c85b922fc3f5cbb3ebeb9b896d4ae474ec0c2 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/c803f6f6e2c49429d2951832bd0f208d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8f6efe7e846c79df2d21dfdc13dae54637d6ccf59d909b40c3bd610799251a3 +size 11321 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/dbe8aad2b5ea5fdf87cc3a21e496e1b9_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/dbe8aad2b5ea5fdf87cc3a21e496e1b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bed14e5a7a4fda46f8fabebcd801caa3f3586cc --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/dbe8aad2b5ea5fdf87cc3a21e496e1b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8763ceeaf6f75501c4e166116cc02aa9f15751192958d98717985eaeeff29bcb +size 69212 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/dd49b205277adfeab9df64f5dc4c402c_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/dd49b205277adfeab9df64f5dc4c402c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bde07e88bd2297ca1318b90a7158aad93da7952 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/dd49b205277adfeab9df64f5dc4c402c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de008554f47938a3af1c9d75d74a853ba77eb093947cd6c7efdf1b83642fa289 +size 49430 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d21d4f40b6abb159d919bc7f0be6d26701135e6 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b1ffe2590ae74c6906c188fb53d13bfe9de243bf5530bbe9639475ceadc8e32 +size 48264 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a41f7125d2c1330559469443c64c76ef96eb9d5 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22ad84047d50ba6fefe5a25d4bc56803c14e5121d182793162e5b4852d15d9c2 +size 140645 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ba4af32b3cbc36f37847c21f5a5372800c764db --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c2160442750ea0b35ae6c60137bbfbb5281342d19bbea75318137372d5289d8 +size 44913 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0750050318b5281c7205918802c5dd43daf97d6 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fd13c4a2f575ecc01f0134b1c3749575f1d515b4a179dc52053c7a067f98a74 +size 54019 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea8099ab54766725223d92194c643c6e45c3229e --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0aaf4bdd999f2c2809bfce3cf5318537b4b7905a6f908d85e923bb2ddd3d21b3 +size 25085 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a64177a5e119c2ea16f942d95b82663ac4bb460d --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a8b14e84a915b9042138e9a5f8d321bae943c39304c4bab831d93d8d3bc4c5a +size 51986 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/f10dc32e3673e1392029a49e958a9d6c_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/f10dc32e3673e1392029a49e958a9d6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d03dd8d12b7ebc429562ed96afcf534c6fb24379 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/f10dc32e3673e1392029a49e958a9d6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7386d95a466baacdb5899eb62783098698b0c9021fc3841e3edc6a3876a479a3 +size 21537 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d76f26ee4ca28ba4b1099cd9da4723b9b1503b0 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dcdb95f1abb28635979c420716a9807f17b51aa3641ea12efddce4d9fcb427e +size 55339 diff --git a/marked/T/T-REC-T.180-199806-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/T/T-REC-T.180-199806-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6897e07c4246d0853f1533a3a897c2a65fbefa09 --- /dev/null +++ b/marked/T/T-REC-T.180-199806-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:436b8773c389e1ee29e96cc95633ba4df819af815d80b4a96bdacc8eb7d6859c +size 118263 diff --git a/marked/T/T-REC-T.192-199806-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/T/T-REC-T.192-199806-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b41dab139bdb44ea22674cd58deef3c08ff0af5 --- /dev/null +++ b/marked/T/T-REC-T.192-199806-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cf9c44e22979d465d0471eebcaa0760e7dcf1016e135fd053843db1f55f9045 +size 57919 diff --git a/marked/T/T-REC-T.192-199806-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/T/T-REC-T.192-199806-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10970c8f0b99b6df28830231f43c3c40d5cde910 --- /dev/null +++ b/marked/T/T-REC-T.192-199806-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87cc1f315e8389164dead6b4510a86f58e12ba3bd7332c1655096c4c494eb0f3 +size 62122 diff --git a/marked/T/T-REC-T.192-199806-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/T/T-REC-T.192-199806-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3ba7f79770190d448575e9bd3bc3bd2a6b52e7b --- /dev/null +++ b/marked/T/T-REC-T.192-199806-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8c32def0c06f087a0599e4ca5e98de970a5701af4644e767e056761df5ef7bc +size 69187 diff --git a/marked/T/T-REC-T.431-199209-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/T/T-REC-T.431-199209-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e24cdeea3484f3390e92532dce20845a0f1585ec --- /dev/null +++ b/marked/T/T-REC-T.431-199209-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccf789e546b1830a068eedf8828c34dbb504736f7959b0e5ae36d75ae84e33c1 +size 8329 diff --git a/marked/T/T-REC-T.431-199209-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/T/T-REC-T.431-199209-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..953b534bb6943f7796e0f6d133cce814c299c19e --- /dev/null +++ b/marked/T/T-REC-T.431-199209-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:260c7a8f46dbf28fca62da5e3d608730f98930415fbf9d1af099504bb506056e +size 91281 diff --git a/marked/T/T-REC-T.431-199209-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/T/T-REC-T.431-199209-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38faf30d95eaccddc614c888d274eca28cdbd3e1 --- /dev/null +++ b/marked/T/T-REC-T.431-199209-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14c832aa02a870101bc5360e3aca43a40e399ac4eda51b8e3b010db02219a4f6 +size 6000 diff --git a/marked/T/T-REC-T.431-199209-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/T/T-REC-T.431-199209-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..769e76dbf9a69405cd9a53318d24705c30bb444d --- /dev/null +++ b/marked/T/T-REC-T.431-199209-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0c59b0818b6e587faa69a282de1065d2e60d9cf4bee431f7427569b0c23e79f +size 115292 diff --git a/marked/T/T-REC-T.435-199508-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/T/T-REC-T.435-199508-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3e4362c9db9ededc211c88dcf82acc8b5c0702b --- /dev/null +++ b/marked/T/T-REC-T.435-199508-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15330500494b42b953a0fd70166f10e5545157034ad829f557ff58a0d611a5d6 +size 16876 diff --git a/marked/T/T-REC-T.435-199508-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/T/T-REC-T.435-199508-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..515d97f48e535801c2948b4b873dae826c20bb35 --- /dev/null +++ b/marked/T/T-REC-T.435-199508-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a57954249de548b6afa5f6ad3a24cc6602a7ecca3b86bcfe59910869c17139da +size 26344 diff --git a/marked/T/T-REC-T.435-199508-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/T/T-REC-T.435-199508-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f48cc2e2e7552425e84bfc52afc9d2e30610aea1 --- /dev/null +++ b/marked/T/T-REC-T.435-199508-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff7323025f6f062857fd09fc5f8c56176a525b19b328322ef865bda687732fe3 +size 8259 diff --git a/marked/T/T-REC-T.435-199508-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg b/marked/T/T-REC-T.435-199508-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..247a2425e28d8663e1a857c69af7677653f13257 --- /dev/null +++ b/marked/T/T-REC-T.435-199508-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9c3a7d5a20d1f15940b25aa39454508647f2595fd3022ad2c1a15aee0b10298 +size 117803 diff --git a/marked/T/T-REC-T.435-199508-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg b/marked/T/T-REC-T.435-199508-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f82e22d0e0c92f19dbf309925a70fc4232be4b32 --- /dev/null +++ b/marked/T/T-REC-T.435-199508-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba8442ad81b54fa93afbc4695c0ce65b2b8b1eb3f43614fe519d3129184fa40b +size 78758 diff --git a/marked/T/T-REC-T.435-199508-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/T/T-REC-T.435-199508-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc32c2f646fab95fea0785739073ede03fb22a05 --- /dev/null +++ b/marked/T/T-REC-T.435-199508-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83a07dfb6b5af8525025d3054d10e2451df82e4977ea3faa2c5f05c7afecc6e2 +size 22669 diff --git a/marked/T/T-REC-T.435-199508-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/T/T-REC-T.435-199508-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..decad8703fa49f61fbc2b1ef469881de330e18cc --- /dev/null +++ b/marked/T/T-REC-T.435-199508-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:033c713495763479b05cd63f20f897df8680bb2be339d580ed3cff666d6a74e3 +size 15650 diff --git a/marked/T/T-REC-T.435-199508-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/T/T-REC-T.435-199508-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..925a6da9016ab5c3c24e4b223a82c1560c46987d --- /dev/null +++ b/marked/T/T-REC-T.435-199508-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0edf3a33fd5feb277b32cc4a3d0ac5f60215f5d29b150d1e2125c3157b76d09 +size 21333 diff --git a/marked/T/T-REC-T.50-199209-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/T/T-REC-T.50-199209-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc06acbd2e74bee504ebbcb0998df1ac3a0dded5 --- /dev/null +++ b/marked/T/T-REC-T.50-199209-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fe39cddfdcac5a57bffb9cbf5ebd65eaa6f3b1dd64467184c6644c737370234 +size 5771 diff --git a/marked/T/T-REC-T.50-199209-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/T/T-REC-T.50-199209-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..275e240f2f3094624469ab2a3cad00d8f2e3e931 --- /dev/null +++ b/marked/T/T-REC-T.50-199209-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4683fff5fc2b5ed6ba71b36ef4c233f0dde78abd802aea182021a479b1d37ce3 +size 8337 diff --git a/marked/T/T-REC-T.50-199209-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/T/T-REC-T.50-199209-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..654c035e41300ddd46643fd41d6410f5b5a60062 --- /dev/null +++ b/marked/T/T-REC-T.50-199209-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d63355b01fb0fb45b9b0bc610d4da7fd8e3b2a892ba7ad7aee63eb380d08b06 +size 20044 diff --git a/marked/T/T-REC-T.562-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/T/T-REC-T.562-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e192ff8b6e90f8248a74823561c0bbc5b40c7b2b --- /dev/null +++ b/marked/T/T-REC-T.562-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62f947da13b16f74e0abb3ea63021fd0dc450927b4eef61cb31568f0addab4a8 +size 7332 diff --git a/marked/T/T-REC-T.562-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/T/T-REC-T.562-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6447d815bfd73ee60c3df7fee98e8bfde0eb0a1b --- /dev/null +++ b/marked/T/T-REC-T.562-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2485c7f4c9aa813f28ca8d9873a3ab88cac91f4bff6af300bb0056c64d3ee012 +size 29044 diff --git a/marked/T/T-REC-T.562-198811-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/T/T-REC-T.562-198811-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..236f73855ea9b11a005d468664ea73a06b0112d1 --- /dev/null +++ b/marked/T/T-REC-T.562-198811-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a307f15b6da918abd67fd21f52b72b9516cd2bdd99e34c4e2cdae87148aedc3d +size 28496 diff --git a/marked/T/T-REC-T.562-198811-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/T/T-REC-T.562-198811-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06f90f3c9886f5c14aaaf0b60e0852789d931630 --- /dev/null +++ b/marked/T/T-REC-T.562-198811-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:990397279771351ef97bfd6e94fd1bdc979c58adbf6f152d6a65acd69ced7fc2 +size 28498 diff --git a/marked/T/T-REC-T.62bis-199303-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/T/T-REC-T.62bis-199303-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a086a1090a243bd47762940fd7d214e1b91be359 --- /dev/null +++ b/marked/T/T-REC-T.62bis-199303-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e29b65c6728801cb3fcae009d541705a574ba9fe359c3cb6cdd44aa060ae0988 +size 262947 diff --git a/marked/T/T-REC-T.62bis-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/T/T-REC-T.62bis-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75f5e355a1fdcbd794b1a3a89ce8a6f615813db8 --- /dev/null +++ b/marked/T/T-REC-T.62bis-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61be215ab0c9490bb653a0b8431706481d26ed7738c5a3c4d7577d6c180cb027 +size 8309 diff --git a/marked/T/T-REC-T.62bis-199303-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/T/T-REC-T.62bis-199303-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ec172437812cb75fd7e67424310c3be2e66becd --- /dev/null +++ b/marked/T/T-REC-T.62bis-199303-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cea636ea5fc452c262ba46382736fe92c70bc071a93302a0475175bad457bb2 +size 280350 diff --git a/marked/T/T-REC-T.62bis-199303-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/T/T-REC-T.62bis-199303-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21edbcb7bc7145d6fb24db893a030603a3c87cd5 --- /dev/null +++ b/marked/T/T-REC-T.62bis-199303-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b583f7b4025dc5166213986b87d6651b0841468dacc534938fc2101023950e87 +size 194988 diff --git a/marked/T/T-REC-T.62bis-199303-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg b/marked/T/T-REC-T.62bis-199303-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..449714826f240727835494367ec4435803818e8a --- /dev/null +++ b/marked/T/T-REC-T.62bis-199303-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc7f3c3ab37ae5274182ca4cbc15be620c167cf6f09ef5e96a77805f2fd1b0b0 +size 12441 diff --git a/marked/T/T-REC-T.701.11-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/T/T-REC-T.701.11-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd7c24e83d75a6b1baa7fb4210f76345166390c9 --- /dev/null +++ b/marked/T/T-REC-T.701.11-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5866ab521163bd4f911ae6e27d0a1cf1f491c665e9b87b7d7076098a143f4bff +size 3944 diff --git a/marked/T/T-REC-T.701.11-202009-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/T/T-REC-T.701.11-202009-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40b3bcf1688dbe5aed44c6d73911e15ca0eebdbc --- /dev/null +++ b/marked/T/T-REC-T.701.11-202009-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9c624b4c69c802b1fe1c52b6b2b528d9695b6c132405d8c6ceaaa573458ce11 +size 37204 diff --git a/marked/T/T-REC-T.71-198811-I_PDF-E/2a16bc72fa4d0150523532baaa0ecfad_img.jpg b/marked/T/T-REC-T.71-198811-I_PDF-E/2a16bc72fa4d0150523532baaa0ecfad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..863a20414c7c7b0bc2085eb71183b9571cf38c02 --- /dev/null +++ b/marked/T/T-REC-T.71-198811-I_PDF-E/2a16bc72fa4d0150523532baaa0ecfad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ca6d49af24d923285f27c9cc8745a17a5ea82ad9f8e5b2992e420ec3f85f48a +size 18944 diff --git a/marked/T/T-REC-T.71-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/T/T-REC-T.71-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66412856f54ae0b24854202e8f031f6a04b88ee0 --- /dev/null +++ b/marked/T/T-REC-T.71-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7cafe25d563af62a326eb0e9930129524893e0fb16cb431aacd25f8ed54ed31 +size 7392 diff --git a/marked/T/T-REC-T.71-198811-I_PDF-E/38518d5d1f1c1f0d28a4ed8932714786_img.jpg b/marked/T/T-REC-T.71-198811-I_PDF-E/38518d5d1f1c1f0d28a4ed8932714786_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f291b62361913097fe9b3d9e4473487e24e7762 --- /dev/null +++ b/marked/T/T-REC-T.71-198811-I_PDF-E/38518d5d1f1c1f0d28a4ed8932714786_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39e65fb77b022f11c71156746962ff2d5e058191d69714b55064b6daefb276ea +size 1586 diff --git a/marked/T/T-REC-T.71-198811-I_PDF-E/4c762280fc3cf84826d3a0bb06c9d672_img.jpg b/marked/T/T-REC-T.71-198811-I_PDF-E/4c762280fc3cf84826d3a0bb06c9d672_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da99f8ce15ac02083b99c3c5d7e80da1dabb9469 --- /dev/null +++ b/marked/T/T-REC-T.71-198811-I_PDF-E/4c762280fc3cf84826d3a0bb06c9d672_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15221a3514b532d1504b1ac4ad92ebfc20e05569e3d48e89c0c084e729eebaec +size 1611 diff --git a/marked/T/T-REC-T.71-198811-I_PDF-E/500e48496fed548d511acf1b81418f11_img.jpg b/marked/T/T-REC-T.71-198811-I_PDF-E/500e48496fed548d511acf1b81418f11_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f52be85c92b810243a6548940c188e67a43dabf --- /dev/null +++ b/marked/T/T-REC-T.71-198811-I_PDF-E/500e48496fed548d511acf1b81418f11_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13776905f52cc8ac178a5eeef8a6eb46c7890afa95061b26389c283064646667 +size 2053 diff --git a/marked/T/T-REC-T.71-198811-I_PDF-E/5e364519788f202284db85f4ab2f3fd5_img.jpg b/marked/T/T-REC-T.71-198811-I_PDF-E/5e364519788f202284db85f4ab2f3fd5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ce38afab9dd20f17aa2d74ca78aa85ec417173e --- /dev/null +++ b/marked/T/T-REC-T.71-198811-I_PDF-E/5e364519788f202284db85f4ab2f3fd5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f5fb033a56243150266615022de5d74ac0d1bf76ccd09991ba144d52a6b9d20 +size 2036 diff --git a/marked/T/T-REC-T.71-198811-I_PDF-E/7ca3e7ecfe7105a58461c65ae98ef9b3_img.jpg b/marked/T/T-REC-T.71-198811-I_PDF-E/7ca3e7ecfe7105a58461c65ae98ef9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61d9cba4471ac856d16398ca6711a91699fd1e05 --- /dev/null +++ b/marked/T/T-REC-T.71-198811-I_PDF-E/7ca3e7ecfe7105a58461c65ae98ef9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2ef085c92f13d8fd68985a08be8632ca59c49a4580dcfdc9c40d8322b27f43e +size 1979 diff --git a/marked/T/T-REC-T.71-198811-I_PDF-E/897b2bcc4ab1a492cbee936e7829252b_img.jpg b/marked/T/T-REC-T.71-198811-I_PDF-E/897b2bcc4ab1a492cbee936e7829252b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8117cbeab591825365047233343dbcb0c9a549a --- /dev/null +++ b/marked/T/T-REC-T.71-198811-I_PDF-E/897b2bcc4ab1a492cbee936e7829252b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6474ca56aedd972b4bc77db8b914e7ff03b86fbacf5ec5e23ecede0b00c9df3 +size 1610 diff --git a/marked/T/T-REC-T.71-198811-I_PDF-E/917a6b5d4a0965b5ce7b1c98f86fb95a_img.jpg b/marked/T/T-REC-T.71-198811-I_PDF-E/917a6b5d4a0965b5ce7b1c98f86fb95a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..584f808b07eb799f61073faa7f38aacee4288500 --- /dev/null +++ b/marked/T/T-REC-T.71-198811-I_PDF-E/917a6b5d4a0965b5ce7b1c98f86fb95a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a0eeb076cb64e62022916c9d45cd63ac102888d5874bb977917cb4cf0f8666f +size 1905 diff --git a/marked/T/T-REC-T.71-198811-I_PDF-E/aa81b9b80bd1e3d723922b3a033564a2_img.jpg b/marked/T/T-REC-T.71-198811-I_PDF-E/aa81b9b80bd1e3d723922b3a033564a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c3b9b215d14634548271f87242847d078b545f4 --- /dev/null +++ b/marked/T/T-REC-T.71-198811-I_PDF-E/aa81b9b80bd1e3d723922b3a033564a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad499378f9240847bfb36028a09dcc614a952ed8074f4e915ec5431e7a63ad8f +size 77960 diff --git a/marked/T/T-REC-T.71-198811-I_PDF-E/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg b/marked/T/T-REC-T.71-198811-I_PDF-E/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01422a5a923a1fd4c51b5065b5dd9a31f317eeda --- /dev/null +++ b/marked/T/T-REC-T.71-198811-I_PDF-E/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cc0c15cca99f37aa58060ecd94da8530594aadc7036efbfa88d50efefbbedab +size 25071 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/09036266c6dba47efb2613ceaebe2b19_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/09036266c6dba47efb2613ceaebe2b19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99d4a08b0311b0c3fb42fdd76d866683eea4578b --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/09036266c6dba47efb2613ceaebe2b19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f986f7dd3248b5cff930d295fbdde50afd53d2d3de009c428bda751d3199766 +size 6605 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67fbe57e1358c62d75449b350c3dc30d4e356fa0 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:061c914b9891601b1005d60b55efd8aacddda6021f2ed9e101e6ddd6bbc9c646 +size 18176 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..674cb4e4838c86e56e47a0d0bb6fcdd5d945cb10 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a23ec00f637f8ffc53078bff86fa29d06c70578c4c448bbc08e8b5ce341000c4 +size 38047 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/124c6108c63173818afb8ed49521e22d_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/124c6108c63173818afb8ed49521e22d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e73166af9cfa672aa52910e19ddd2579144e8a2 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/124c6108c63173818afb8ed49521e22d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e38b0babb23a921598ca026a7db4d5703c51857589a4bd8eda2da950936a96a +size 45177 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..160161f4fa0dfa42dbdf261f6900832a08868856 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30ec2e56044992271abd125f345768f9d22d6f7856f53939df3bc8293685d227 +size 13191 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/36893f120533bae3be68e122656b1708_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/36893f120533bae3be68e122656b1708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d01cb02b3d6fdf272794bec15b0633b244e4f0bd --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/36893f120533bae3be68e122656b1708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bb7af46ca269b4e2ca1cc9da51a1900c83507dc716b3197b65879c4c794a833 +size 11863 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/404924fde6a708196214ae2da3819428_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/404924fde6a708196214ae2da3819428_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21ea348d35b92b74dfc315d17fd3539fbc263d66 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/404924fde6a708196214ae2da3819428_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:457ff12e537127cc3165c57abf9b883156b70bc3ec24769015409c7795e8f6cf +size 8743 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/487c58c79e44e6cf98b6368b6667b9c6_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/487c58c79e44e6cf98b6368b6667b9c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6db0586a977e044b0c8d1e6ab66f6c86674e6d79 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/487c58c79e44e6cf98b6368b6667b9c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42bed9d827a329ec0f76e7b7d3197fb9ea14bce73f5393c2f704ebe01bcaca75 +size 37069 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/48adb97a6a4a14b039450192f25cc1e0_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/48adb97a6a4a14b039450192f25cc1e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdbc4de04ed15e2430902cf6ee4656b313a2fa1d --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/48adb97a6a4a14b039450192f25cc1e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d16e937859c69783a2e2159105768aaba17cf32b255af5c2130e1a6cbcc31b6f +size 5071 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8703c766720b7ef1d2688fefc30c0ca6cae7e00f --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52d15b7cf8b2a89c3c7877b2719bb2ac56a890d6a98b84b41e3d31042bc73e80 +size 78056 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/51167ecef86d85cdc6dde05a3afb74b8_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/51167ecef86d85cdc6dde05a3afb74b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a5764df7ec817cf9a12d8769a64984a5285512d --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/51167ecef86d85cdc6dde05a3afb74b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b824c03780c951891b683a3b52a6d5bce5fb3d599e5e0c4003d79474d9f6091d +size 11967 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8fb50e6c856eda74c23eb7337c54fe744adf7932 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6223951d9a41f210928ee7c12cf0e021f9598e5637d0afccdcf86f37dd208c35 +size 49532 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/67114ecf6da13c97a89aeff0d86885d5_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/67114ecf6da13c97a89aeff0d86885d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1b2bad5686c4b75a4915ac4770aaba338377e92 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/67114ecf6da13c97a89aeff0d86885d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50102d0b7bbc6b6b4799632cbff352424fec75acda22912490c04ea898535ae4 +size 22815 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee814cbd626697f4f917a95d646dd70964cea582 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:feed82121fa83af4bb1527e8fc974b28ccbf4e9eadf3d3595c95a1902f36d339 +size 5625 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d892384746019af8eb9d4ee8c66fa4955ef68ca --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55605ffeb2ed18079930a46c6a387f43052ade2305920da05bdfd3e01c37488e +size 59465 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a48afc5c0a88af1d747a06fa064b06b7ac534628 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8afd6de9e361b80443b4bf74faa58cb033d43b6d198c8dbeb499ad681d00ae2b +size 17878 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/90183a52275501da5a0fd5c63d837009_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/90183a52275501da5a0fd5c63d837009_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11409ff612321ddc65028f7ea180ffe0c9d942d4 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/90183a52275501da5a0fd5c63d837009_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79368e8e6763ce882e3241971a68ceda4258eb101695bb8eb9d9bbe90a3017a8 +size 18331 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a26668bb62e2b2b46998267bc90deb81cd17ede --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae8f0524cf0ffe3103f46c6e9e8d588a54dc8f9588841286efca0c1d1079c68b +size 9439 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f2eb5f599c68458d19f53669227d31363dffb24 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95947df351aec25acebff3e3baef4dc19fd6ba6958c0185f05ff18ac8ecc9ab4 +size 75350 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d37a2b158b7e7dd6f6039f7b92313f4fa8435e83 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1c6620f2db8b96e6fec0a4f216f6a0d037a03f1462014db9e51a8c8f16ef02d +size 17238 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/a320e67b369bfde4a5fa360b100da55c_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/a320e67b369bfde4a5fa360b100da55c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f54afd0138ae8319b1b1b7701805339c1fefab3 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/a320e67b369bfde4a5fa360b100da55c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a680a00bc7d693293c71e32381d25db81e72fc6249832bf6474bafa994ccd97 +size 6289 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/a48a54b8213bb20f6db241f20824bb51_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/a48a54b8213bb20f6db241f20824bb51_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4d8969f805414689ab79cfd08c333d454d482b3 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/a48a54b8213bb20f6db241f20824bb51_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:636c3839edff955a5b6208530b05fa1c983ab153d90f00216517a7a99478b988 +size 7074 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e60c4e31174694b5da0256b4a365dec7ea3c6bab --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce0494965b119d13995300a5a58ccd554d40edae4f0c432f2f806b8f26d77858 +size 48160 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/b0d322b2e75c75e1f21bfc0df841beaa_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/b0d322b2e75c75e1f21bfc0df841beaa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b93a6837751014ccf0361b5f5f6fb97fdcadc34f --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/b0d322b2e75c75e1f21bfc0df841beaa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae1cd3b595bc03f0e6ca108b411a0432f613587793fb94cd22c82346b5e640e6 +size 27185 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/b9cfcba6591488c6a29a844db4f052eb_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/b9cfcba6591488c6a29a844db4f052eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8680515bf36713b9fc663f1473b64cc6956d2c64 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/b9cfcba6591488c6a29a844db4f052eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36cc0105d8a90f6351d8bd62e96107a1876a231506e94bc9f564345845eeb70e +size 34700 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/c3254408eadbf152632a8faf16310722_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/c3254408eadbf152632a8faf16310722_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92b04005abde32cc71e537259beb785d4ed41b40 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/c3254408eadbf152632a8faf16310722_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9095d313f0734fcfb7a3fb4ad20cd68d7d432655e0136b733aa64c75b84498e3 +size 94954 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/c78f017dab5586c098c5d7c6a8f1d432_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/c78f017dab5586c098c5d7c6a8f1d432_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8eebaed8ed5e5276c639fee0bdb641b6beb7d239 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/c78f017dab5586c098c5d7c6a8f1d432_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d65a183bfd45126689da1c99e823809860b8802be9220146b4feabef9857d98 +size 65247 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/df935fc9efbd024af4ba77e46bb0bb19_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/df935fc9efbd024af4ba77e46bb0bb19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..252a22c17fe85e34eda551aa729edad2fdf777b7 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/df935fc9efbd024af4ba77e46bb0bb19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:484e14a13197e48045a8225facac4a3afe0a5968c293843dbadbdc5db7c847a6 +size 12431 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..445ff0411192694dbf9bc5b92db27b1dced70cc0 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3e96d496272e6ae38f08226513f34d401fa05129575f4e85836c8a3d2a20211 +size 48033 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/e35f25e0b66752d4179a4cb108a3fb5a_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/e35f25e0b66752d4179a4cb108a3fb5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1d2aa3dfdbe4bc0a06458c839bac6e10d7061d2 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/e35f25e0b66752d4179a4cb108a3fb5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f7c078355ed3c18879cc2214c5f0f8a37876a0547bcd4a20b765371f8afcf29 +size 10972 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/ed99c577aacc48b3e3ef5060d0048041_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/ed99c577aacc48b3e3ef5060d0048041_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8884fd400bbc06f3834a1c37ef6062713e12b1a9 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/ed99c577aacc48b3e3ef5060d0048041_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:926b11ef2524dee2df54cb32e99b96bfa20c27484e83842b51c7e663a6b71339 +size 11916 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/f087d3f5d298b3b1634d13ff17879e41_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/f087d3f5d298b3b1634d13ff17879e41_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..655b5bf1b74262c049b17ddfe5ab5fa403949262 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/f087d3f5d298b3b1634d13ff17879e41_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e764109e9f12f28980b6d81ef91132ab2c2ddd7d0d071a1e24f705a7cf4e118 +size 21197 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/f0a97d0d3818a253c1d2a009966081b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae34aa2a7271b26716e3b8e3c9921c9de4ac0b3d --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/f0a97d0d3818a253c1d2a009966081b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:500bd3f32f1acbf839adfcd2cbe5128d04f6c54a55a0e726a73968b83a04bfc7 +size 85511 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb1e55f44989c4e8a3453408bead348dc58b1e8b --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bee93ba05c91653df68efcd61119b13914c0016b473ee1a9ad1fb4b2e7e19c5a +size 27385 diff --git a/marked/T/T-REC-T.808-202212-I_PDF-E/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/marked/T/T-REC-T.808-202212-I_PDF-E/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..620e095a4a26ac89a7024ed3fd29318de9937623 --- /dev/null +++ b/marked/T/T-REC-T.808-202212-I_PDF-E/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29b2328abe001fa84564afb4882de3e8eb10c4a3189e90c41df918aaf7815434 +size 7397 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dcf9e578d51ded873f53e0bc8e7f3c1f8916495 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85a5c3c6a40d745015d2ed6d3a745799e103f849002aefd6d331d6ed95e16a0b +size 62606 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d72bc493b44d58c673e074b73af314c065bc1c10 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77be9e4089149f20e7093e7141656e45f4214ae95548f794cb8f7a9c0e921f90 +size 112318 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c8e345f589c3dde013b2db66e836cef1e7decc0 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4634a39fbf0d93cd0fe54024bdaf02ddd412a60eb7d32bc4b40d3d3516d04c7 +size 26811 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/1e8c50ad4fca7f315a407347dd5091cc_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/1e8c50ad4fca7f315a407347dd5091cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5c4f0f389a9f2ea83a30ecf5c8bebd74ecd4d62 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/1e8c50ad4fca7f315a407347dd5091cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf49bf9a2e0666f19b882f39f9326405fa36af483eb8c6a5e38f254793bd1999 +size 33726 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8645e65ec73303bb83890a501376a29c7580ddf --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:700511086e9a081a31c7eb69c466a07452d8c5b449ed149c2425f3e9ff0f0fa3 +size 51926 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43ec715ab2b273676af403892d727e142478c92f --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:084856274756e36f715649478b43998689b25485bbe424122480e2b88b5a09c2 +size 18067 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f522d81955bd966a0d4a7f92eb4b82b63cc900b --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c790f6511500ca6ebffef506e094d6182d8f40d4d6fce9d786ad4c5b49a0f756 +size 33796 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8765a84e9b4b28aec132edba81cb939bef3206ca --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a56d903fff770e1a045b2818d854916e38a00ea7ffa9faf4a0345e3fe0586cf +size 84202 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d89c21888b84305e02b63637e5f581f197c09ea4 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:920e96c749f2e5dd3e01d14ec1f81e6058f6ece72d2ba29eb85e3a25a2923ce5 +size 9440 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/5879500ca01e1a2521654beff6c289a4_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/5879500ca01e1a2521654beff6c289a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8b59c06f2115fb02100d4a4c17c64a4053e0c5e --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/5879500ca01e1a2521654beff6c289a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53f42c9ce3cd5027614545ed5af5b302d5884408026754564dab1c12620c7989 +size 11926 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ddbd7c65ee4b5b61958f322b94cf4201f455281 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70cb48b4d568ff1e2e6f3be2e28f171e93241f410a8dcbc18df9ec482e3c894f +size 15426 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3d29ee3bd6ea6a43a61ea2c22229ceaed0928c9 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9b77c0718874f75af734196224b65468e4918f2ccc89ac4f22df71d2a0854e2 +size 43126 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2320cbb71f067a8c3b5b8b6901f3d649e2bda9f7 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d9c62c260178d774d5b827575698363b02b3f484002b1fcd0ceaf2f23637ab4 +size 94679 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88b713aedb2ba10a4f7e3391c096ce2be763a811 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbc861e6ca99d4bc6e4b3eee2f391720085354ea7627c9e4481d9b4bd5ff991a +size 12180 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8284d76f62ed83384ca830abb4e558ab1c5795c4 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2368cc4c1fbcfae98ee5411925d7118371e083fc9969863b0b23ca18271cfa77 +size 28250 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..beb0b0d2ccfb6603315a91f14847bce28fd320c6 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:383b4c5176de6d69849f6ed87bcebcf5f4a2ee5dd52d0a0be37b03460988d4d7 +size 11694 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86f56d419b116826d0f8612d9af8966932e735f7 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ca63e1a65d8a19e012716a94bba880212ed45f40af60189472071ea6d40c775 +size 15032 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba1834b2de9e81bb1062bcc22dbcd078c3e110c5 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e1304f8e1e5b631735e0c0907a15a4f13647e8633361d97b0ac54fc18664f08 +size 41601 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a59cbdd85f878db1e239a120312b17384ffa161 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:850f879da36fc524187ffd338ce20ad8aaa9f53ad62da36b97aa30a1da8df179 +size 18302 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c81033b747feaeb50a951c6df28b2d57d981bea --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e499257e3db31b653aa2d98770bd2a18f1d71fc4f5fc55e94cf7f1324b7fb90 +size 19422 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b952930fe5de6c467855165f258122c4cac6269b --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cb1d9c5ab342754c7ac69f5ffdc69bef1c18afe62d1e2b52de34d995bbc5d76 +size 33665 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/ae375ead8aa673286b534e079e9a8533_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/ae375ead8aa673286b534e079e9a8533_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bded779ccbd47ac80afc398b20a6969052283b3 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/ae375ead8aa673286b534e079e9a8533_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f24a7492ed13f34fb5bd8b1e5cb734c5bd76891e60c189437f69244740b6fe06 +size 22235 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/b44f89b176c971c7dd264c07bfef2c2a_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/b44f89b176c971c7dd264c07bfef2c2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06936ef6250494222bdf507caf44606502dd0cf0 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/b44f89b176c971c7dd264c07bfef2c2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe0a9fd54f58dc685d5080d624568618b7c1444ff3440f1a0610fef4d7edc2b5 +size 8545 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42b728673954d121f603ff293a967eba4789abef --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85c96635c0ff7ef5d31492b50d0d5186d4cdaa585f61fdb15e2b381928a0b8c8 +size 21593 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..397036782f74c4a6ca1eb4d5bac05244ef736a72 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e1dd0c4239ad5d8bf1e9f344f935d16b7898798483f3116a1ab6f2281faba08 +size 32135 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..598b336673421c2fd88725d5c08f050a6e1e5a39 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ddbefb427eb624dc3cd45ba114f3b0a588b55530278cd4b677986f792760717 +size 53765 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26182409426a72a9c07c4ada0912c4377429fe48 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abadcf533ad21e23ce04cc47d4013c54ef5788cf80ec7a1a3b20b379a066a289 +size 4349 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2286c65e132e0b844953142fb61bd1b3e50bb248 --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a477d153ffbbb935f2e3001fc7280fc6c297871cc0e8acf9c903b2b111df3d2 +size 22803 diff --git a/marked/T/T-REC-T.810-200605-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg b/marked/T/T-REC-T.810-200605-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56f350d0b063ad5dfde1447bd3717f93b7ea80ed --- /dev/null +++ b/marked/T/T-REC-T.810-200605-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83a854db95c9b9d39bf4a66765a595f14f08d2625973a4ae2a56d6a76264fd86 +size 46943 diff --git a/marked/T/T-REC-T.813-201206-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/T/T-REC-T.813-201206-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fd4c57cadb1a56aed184d722bd0b51b5817a2c6 --- /dev/null +++ b/marked/T/T-REC-T.813-201206-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb6588bb60816a0c94a18c44b751ef5ee7cc10e835c8451f6e4c43575bf72376 +size 50701 diff --git a/marked/T/T-REC-T.813-201206-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/T/T-REC-T.813-201206-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f45582132badc928bf177439155684ae9306425 --- /dev/null +++ b/marked/T/T-REC-T.813-201206-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39bdc79f648aaa33379b58bc0db36a7ef1ebf6b2a5f69f1342078615bc779528 +size 34798 diff --git a/marked/T/T-REC-T.813-201206-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg b/marked/T/T-REC-T.813-201206-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e632414da88fa3a13d3523e307ea8456ffb43dde --- /dev/null +++ b/marked/T/T-REC-T.813-201206-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf6cb265714af962adce8f3a43051a05bd8456fd4b49d65b96a429148497c53a +size 69311 diff --git a/marked/T/T-REC-T.813-201206-I_PDF-E/63e0c22852c26699d0bd095a2d796bab_img.jpg b/marked/T/T-REC-T.813-201206-I_PDF-E/63e0c22852c26699d0bd095a2d796bab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42c11f20578b4826fcf2cfe64ce96527da74d84b --- /dev/null +++ b/marked/T/T-REC-T.813-201206-I_PDF-E/63e0c22852c26699d0bd095a2d796bab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebf425c1fb1555536b4ae6ce7edae260b64f008c0614660d15dbe0919e0f0439 +size 36712 diff --git a/marked/T/T-REC-T.813-201206-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/T/T-REC-T.813-201206-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba64b9d008cdd56b64538c14e9cd7161f19e7a41 --- /dev/null +++ b/marked/T/T-REC-T.813-201206-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf5d337593b35131439be5cc7554afad18964cd41b8c1e0fdc0efccb9446dd8a +size 6625 diff --git a/marked/T/T-REC-T.813-201206-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg b/marked/T/T-REC-T.813-201206-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28194472deed9433b654a2ba50d02e445612628f --- /dev/null +++ b/marked/T/T-REC-T.813-201206-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bbd581f3dfea4f0082b24e6c58ab175c4aa4e728708f83f2deaa8ea02bf9dee +size 59128 diff --git a/marked/T/T-REC-T.813-201206-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/marked/T/T-REC-T.813-201206-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0ceb2213e67dbad7b86f90d63975a1fea989caf --- /dev/null +++ b/marked/T/T-REC-T.813-201206-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1cb5fba666fe1ebf5034afd89c815b416a793e158aa2e4075af458234644dbf +size 52035 diff --git a/marked/T/T-REC-T.813-201206-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/T/T-REC-T.813-201206-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a0ac2b1a5b62bff5206bb56de726f529fc8cfdb --- /dev/null +++ b/marked/T/T-REC-T.813-201206-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59600045de73480cbc36eb78ad4fce4e0e49485f7984ce55723b4144c82ae7c8 +size 87845 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfdc74f7a89230dcde009e379721398562ce4a02 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abacc511bba2a4be4d9c7a379b7a2bff4829f22e0a1ab2ff26425767080ed2a7 +size 23535 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/04dc3838022e96d8d5548bb1b777b38c_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/04dc3838022e96d8d5548bb1b777b38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4168e139fd052803953942ab1b39ab32fae2d6d1 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/04dc3838022e96d8d5548bb1b777b38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9672f63dc8517bbd3decf6cb2f2cb6a52fa6062a4f452b7518a8e65c3c69a36 +size 13918 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/05d8710f69c476939295486ab1440350_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/05d8710f69c476939295486ab1440350_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64ce1b4bdc2959424df89889329d0bd5a494bb6c --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/05d8710f69c476939295486ab1440350_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9f05928ce339068bebb8b3b7fea94912bd8a6db10cbbea0aa18f788f392661a +size 61425 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da85db0cbac971af1499818cbb0d81bf9b7d3ea1 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63db319427d373f231907db2b0223e57d93e887849172d95860cb4633b50b900 +size 14670 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/0af1ba85ab6e4e50befbef3d63e017dc_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/0af1ba85ab6e4e50befbef3d63e017dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0281e5005bfa8e72d6b4c50f8977217de6e7ee5 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/0af1ba85ab6e4e50befbef3d63e017dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:950aa46c05fbae738dbcae3b33cdcafb4d99e1fb54f4fea0e8d7f23dabf8564e +size 10514 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..963768f835eeca52fd55a78dd81ff16fedc12a9c --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78ab247e1a6ae5e6f7a34ccc0894dff3e910b55cca8d48437b726d2c88c7e066 +size 8906 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/0fa5b60804100c3aead10404f9f226f9_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/0fa5b60804100c3aead10404f9f226f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f06adc192e997fe2246615a3461b4fc976eb603 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/0fa5b60804100c3aead10404f9f226f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d87589e6d8467eeb4cd29d14929e98d8da0b314076908e43a820a7ad2af5519e +size 67806 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..704f661801d6e4ee1f61f9ed64714b13c89ffb17 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2c66895651ee5cdc4d5fbdcb37966e2f20329d70c09a19512de2cdd25ddca6b +size 83658 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c961f110b6ae23e66b38483cc7158db1c8b06ce --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ecf2d4630637f93c58f8f2e33dbf6c1e87f82614e454c13caa9247637157962 +size 137919 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/2a25e8bc21554c0efceda1a8ccf57db3_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/2a25e8bc21554c0efceda1a8ccf57db3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..962beff00fecc6200229f1a2ca15e287ea6dd7e7 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/2a25e8bc21554c0efceda1a8ccf57db3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bcd3d81816f746756fcf952e7a30a71229014c29fe755023ed0f28a3a718f2e +size 31010 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/2cc973099f02f2cc67558feea3b18cde_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/2cc973099f02f2cc67558feea3b18cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0fa552e124d8db16349b44ba7c81c1761d23159 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/2cc973099f02f2cc67558feea3b18cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c120b543519f93bd4549f426a431a20075c9c77ddae49bd266d8c253a0ce034 +size 37521 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/3ae74a33759ae31781f484406db4feed_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/3ae74a33759ae31781f484406db4feed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91cfcf54c9af74098e4d2295125c18eb61de3a6b --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/3ae74a33759ae31781f484406db4feed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3206085d2660433d488d9d03158000ab90ea179b374b1a39c6af45c63fa5d0ea +size 40777 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ca0c4016ac6b533f84bc65a8aa38f437009cd67 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:004b7e6389c30cd29c35a93009602184fb9ea140b7e19c1aae76aaa858fc2927 +size 10770 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f970e8a660c37eb828f9bda7cd7a92de76c86a4 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d72b54874bd7f869d974f763315c78f1adc55e06551512a255c83785bd56d287 +size 41778 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/4260aa4a7ece77c411597094c9d197bd_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/4260aa4a7ece77c411597094c9d197bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c47d30aea5bb9ac6a48471c25877053e6a602989 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/4260aa4a7ece77c411597094c9d197bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e9393f99de60305fa61a5925a33aba61f5b85d4c0ea7f8b500146540fcc3c1b +size 6604 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3edbe8175f36d1434b838efe0208269803faf1ea --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21ff9f7f0c699166468d5d836203efa2cd577089ce0fd9ba6b37dda7df489a0a +size 55178 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afa589c3065fd132e144704dc42890d442a546e0 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:292dd56b894eacbf25010f72b388493d829d87f86f0c6459d518180a3d050cf1 +size 17077 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/5500ab73cf84ccc0055eecf28889b4db_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/5500ab73cf84ccc0055eecf28889b4db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33abeddb0c123f3be9cf089d3fb7a307a2196658 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/5500ab73cf84ccc0055eecf28889b4db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68048f6a5952d1c7e963f7e9805a203f7f528143f4ac6e66dfc84710138efe5a +size 58561 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/62a4c9055642dbb00663e633332f04d3_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/62a4c9055642dbb00663e633332f04d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf154da70717c6ece00d3183e3d8410472575d5c --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/62a4c9055642dbb00663e633332f04d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9f7eca9412a267295b118718c8dcac899130c2bcc55c812b78dd991583ee749 +size 39439 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/645cfdb7a7e02c3b04b20d83aed890c3_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/645cfdb7a7e02c3b04b20d83aed890c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d337d5257eaef43b9499a98f135b2da7805d0bc --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/645cfdb7a7e02c3b04b20d83aed890c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1f17c3695f1d57aa365ebe3542357bfa92e25179a5fc6dc73daa94705f5e0e0 +size 19328 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/6470d350326789d5306eabcb76533951_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/6470d350326789d5306eabcb76533951_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..184bf51af2937b141efdd2a01b79b8026a5e0802 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/6470d350326789d5306eabcb76533951_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36d75a5246923ddb75d95a29cd837c3eb0afe94473ab8ca1662935188e53e921 +size 62630 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/67f9de2f1a2e5acf0d35a9adbcbd2d22_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/67f9de2f1a2e5acf0d35a9adbcbd2d22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83e8b9c89d84e8097731c7b0c748e460140c4a54 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/67f9de2f1a2e5acf0d35a9adbcbd2d22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:012f2479dd2a858df6d38446478023de184dba85ae1461f192fbf4c827aeb125 +size 13939 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45d42098653f06bc57d871083e5a007182ec9155 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd26c4585f53fce224e94aba70b8390c89d01b2d47594616004a34486f1dbb36 +size 83582 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3f253e7d813a37b5079136f9c60b6ad77d09af2 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa253237cd0a1efafb76daa311a8d97439350e5b5284954ab9f4cb72dbc196e1 +size 139871 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b86eef55f619d66e77bf180f5460d94410b0c1b4 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d9493b59caf3f8f3767c4bd61f8a5c34bcb3a4191f268f916c7fe852366725f +size 43253 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/74d23510f27b21403a7be84820821863_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/74d23510f27b21403a7be84820821863_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1070fbe572b2a419b0526a44814a4c3721dd7367 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/74d23510f27b21403a7be84820821863_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bf823ea08681a2d3965216d49f453679cb07fb5bcf10bd7133c8212b3228fef +size 55008 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b0ab29561af1334cf1d7a00e5f832dbec10641b --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdb46ff86e690635a83106ff2d8ce1a179b3a9c9cd19069b1c0f035cdb573972 +size 18324 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/7c6f50098db177c4ce9b137442170382_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/7c6f50098db177c4ce9b137442170382_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df411eeab72dde57b8be2cf747980bc407aded4c --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/7c6f50098db177c4ce9b137442170382_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06301aab018a3ccff76c59cb13bd767a16c8966109231b8768188fc4db5279ec +size 36265 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..517016210e5660810d79f70e502edbb526ab1e99 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6983f3972c49313973417993ff5b8d370a37a1194e8dea5c06e44481fcf9ab1 +size 43893 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ebdaa6ebca7da37d4056c3905c4df79174e4ccd --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:902759e7616c174f37545b1457baa77f7884d66c84c2c2b9fcfd4509d28db59e +size 43205 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bcdf90803b02479028015cedacf5cc2e3c5e0e0 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fc9f778da6ad6597839eb06accd30b8a1e2a111963f84c0aee0c158605370fd +size 64632 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/8e395c7d3a0249c410ef3c5a4f666170_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/8e395c7d3a0249c410ef3c5a4f666170_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47152451a8159d7a68e344acb83de80eaa0446b1 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/8e395c7d3a0249c410ef3c5a4f666170_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:832e4fbbf00066d50fc6b80e9e6e14b45af09a812a805eceeef5b3b514d2ac99 +size 88505 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/99ff399927193b5527d8283e2a74747b_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/99ff399927193b5527d8283e2a74747b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c83094481d7d9d220d1d38fca58b7ab7e458382 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/99ff399927193b5527d8283e2a74747b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39813184922f8f39631ac05ea7cfbba7798d733a4215ce8a6597e729feffae9a +size 47124 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/9ff1b32449ea068bba9647d71904bd59_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/9ff1b32449ea068bba9647d71904bd59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0712c86ed94a9a0a2c0c1414eed2e91f4408406d --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/9ff1b32449ea068bba9647d71904bd59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6c6658724d30da88b5a854c8dd96df7d8ec5f34062a2512b6a8751627831b58 +size 63214 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/a48a54b8213bb20f6db241f20824bb51_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/a48a54b8213bb20f6db241f20824bb51_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92ec8b9d30d1657475b287421aa02af16ea9ce3b --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/a48a54b8213bb20f6db241f20824bb51_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98c33fcdc94f3bd68dbd68e343dd2e69bc84eaa1fb299ec7e1356aa9030a78d7 +size 4880 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/a848a8de7c2614546db51319bd55328f_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/a848a8de7c2614546db51319bd55328f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08c571c0e75b0eabf51a296e87a66bbce684e0bf --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/a848a8de7c2614546db51319bd55328f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:330501c46e8e155b4ab729ea37c3512602ebeeaa8b81d2c49553146dba33dba6 +size 27991 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/b05bae46f7079e5c9b1da38adb2319e8_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/b05bae46f7079e5c9b1da38adb2319e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e72aa315aa8137bc3bd7e1bbada54a33ed05927b --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/b05bae46f7079e5c9b1da38adb2319e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a22628b01932f3357a8dbf44daf53ccdbf28791f9d71418e193b98dc52c80518 +size 37670 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..073af326f38a97c16affe2ba21aee081ffcf13c5 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9040cfe5585b3526ab7f03b6c1e0a48172e2800f828d298f1f8687dacea4a096 +size 17084 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/cd141897aa368dbbaa398ace230cdd85_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/cd141897aa368dbbaa398ace230cdd85_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71569b1b9255fd1f727774686215c81818e50e8a --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/cd141897aa368dbbaa398ace230cdd85_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3c4b17ba88e64bafeedef99632e5691e81ffba655215754eb31d476df8728fa +size 22923 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..982e01542a7f1e09ba1142f275039956a7d502a2 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9407ffdc6dfdd0f81ee09f910f18fe9a7331e45ed02f64e57c113086a5958bb3 +size 20364 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/fcdcb5991d671cadf547dd3fbfe13486_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/fcdcb5991d671cadf547dd3fbfe13486_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53e40c6635974b16cc7395f038d704668d20dcd6 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/fcdcb5991d671cadf547dd3fbfe13486_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:130ec314438394654de73042b5f91a7b65a981aff3c01853c234004166f22446 +size 71344 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/fd76efce549d3713543bb5ed9b023c2e_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/fd76efce549d3713543bb5ed9b023c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcce0ed6c169a4eff553cd1ad6a7ec585d1f1e04 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/fd76efce549d3713543bb5ed9b023c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbfb37feff492d86d11027dde4aa33a882b228d3b5a70d5cd7f38bff34ff43e0 +size 69291 diff --git a/marked/T/T-REC-T.816-202302-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/T/T-REC-T.816-202302-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6df6bf9260cda8fa3fcaadaf677145c419a7cdd0 --- /dev/null +++ b/marked/T/T-REC-T.816-202302-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac037cf37949236d7be6e63b3b6cca3af8f4d0b58d59a2d358f3f2988045380c +size 39474